Related
Hey,
I recently unlocked my phone using HTCDev.com and rooted it.
At first I couldn't get CWM Recovery on it using ROMManager (even though Rommanager said it was installed it loaded to the default recovery) but I got it on there using adb.
Now when I try to flash any Rom it'll just get stuck on the white screen with green HTC text.
When I restore to my backup of the default rom it'll just boot as normal.
I have HBoot 2.00.0002 (Sense 3.0 update) S-ON (unlocked).
I tried flashing it using Rommanager, CWMRecovery, manually wiping the Cache, Data and Dalvik using CWM, I tried flashing in CWM and I tried both MIUI and Cyanogenmod.
Anyone knows what I'm doing wrong?
RichieHeijmans said:
Hey,
I recently unlocked my phone using HTCDev.com and rooted it.
At first I couldn't get CWM Recovery on it using ROMManager (even though Rommanager said it was installed it loaded to the default recovery) but I got it on there using adb.
Now when I try to flash any Rom it'll just get stuck on the white screen with green HTC text.
When I restore to my backup of the default rom it'll just boot as normal.
I have HBoot 2.00.0002 (Sense 3.0 update) S-ON (unlocked).
I tried flashing it using Rommanager, CWMRecovery, manually wiping the Cache, Data and Dalvik using CWM, I tried flashing in CWM and I tried both MIUI and Cyanogenmod.
Anyone knows what I'm doing wrong?
Click to expand...
Click to collapse
Yes. Unlocking with htcdev leaves your device S-ON, and stops the rom installers from flashing boot.img. So you're left with custom rom, and stock 3.0 kernel. Might work with sense 3.0, but flash any 3.5 rom and you're stuck at boot.
You need to:
- open the custom rom and extract boot.img
- flash the custom rom by the usual way
- flash boot.img manually using fastboot (look for instructions here in xda)
- and....
- ...
- wait for it...
- ...
- search first before you start a new thread. This has been answered many times here in this sub-forum.
Cheers
Or at least look in the index (see the last link at end of my Sig) this is covered by one of the guides
Swyped from my Desire S using XDA Premium
Hi!
I just flashed CyanogenMod 7.1 ROM, and then flashed it's boot.img with "fastboot flash boot" and that worked well! But i did'n like that rom, so i restored Hyperion ROM in cwm recorvery and it did stuck on the htc -logo. I thought that may be the CyanogenMod boot images fault, and i flashed Hyperions boot image and then it booted normally!
So, until I get my phone S-Off(now unlocked via htcdev) do I need always flash a new boot image if I dont come from ROM wich have same kernel that the ROM what I'm flashing?
Sorry for my english!
TooByAas said:
Hi!
I just flashed CyanogenMod 7.1 ROM, and then flashed it's boot.img with "fastboot flash boot" and that worked well! But i did'n like that rom, so i restored Hyperion ROM in cwm recorvery and it did stuck on the htc -logo. I thought that may be the CyanogenMod boot images fault, and i flashed Hyperions boot image and then it booted normally!
So, until I get my phone S-Off(now unlocked via htcdev) do I need always flash a new boot image if I dont come from ROM wich have same kernel that the ROM what I'm flashing?
Sorry for my english!
Click to expand...
Click to collapse
You have summed it up well. The answer is Yes till you get s-off.
Sent from my HTC Desire S using XDA App
To the Guru of this forum. After my last rom flashing my device is keeping booting into recovery :crying:. Is it briked ? If so my only hope is the unbricking project ? Thanks in advance.
What recovery are you running?
Can you use the power menu within recovery to boot into bootloader?
Also, please provide as much pertinent info as possible, ie: rom you flashed, firmware, s-off or s-on, locked or unlocked. With your description it's basically like saying, "my car makes a noise all the time. what is causing it?".
Its not bricked.If u can enter recovery
Sent from my HTC sensation
Sorry you are right:
What recovery are you running? 4Ext
Can you use the power menu within recovery to boot into bootloader? yes
The device is HTC unlocked with S-On.
Rom JBMIUI v4.1 2.8.31 R2.
HBOOT 1.27.0000
firmware 3.33.401.6
I've format everything but SD. Restored the most recent back up done today before flashing. Once it reboots HTC logo comes up once, black screen, HTC logo, 4Ext is coming up saying that smartflash it is set to update the boot partition on next system start asking if this should be removed.
I've downloaded and installed again PG58IMG *different files using bootloader
I've founded a 3.33.401.6-Unsecured-Boot.img,+Root+Busybox zip file that can be installed via recovery but it did not help.
At this point I need a bit of help to look into the right direction and I'm not sure that Unbrick_Pyramid is the right way.
Thanks again.
Try turning off smartflash and flash a 3.33 stock rom to see if it will boot.
What was your last working setup, and what were you trying to install?
Sent from my HTC Sensation 4G using Tapatalk 2
Hi. Manage to flash a stock 3.33.
It stopped to reboot straight into recovery.
Sits now on HTC logo now for about 10 mins. I plan to let him run for 1 hr and see what happens.
Was thinking to install CWM on the basis that could be a 4ext recovery issue, toughs?
GROGG88 said:
Try turning off smartflash and flash a 3.33 stock rom to see if it will boot.
What was your last working setup, and what were you trying to install?
Sent from my HTC Sensation 4G using Tapatalk 2
Click to expand...
Click to collapse
If you can install clockworkmod that may help.
Tge device isnt getting the message that it has already booted into recovery once. So something may be jacked up with 4ext.
Clockwork may bypass all that when it doesnt know what to do with that signal to run smartflash.
Worst case scenario...put a full pm58img containing a rom and recovery on the sf card and flash that through bootloader.
You should still be able to get to bootloader as the device looks for that option first.
Sent from my HTC Sensation using xda app-developers app
Hallo. Ok installed CWM. Can please direct me to a full pm58img as you mentioned ? Thx.
Skipjacks said:
If you can install clockworkmod that may help.
Tge device isnt getting the message that it has already booted into recovery once. So something may be jacked up with 4ext.
Clockwork may bypass all that when it doesnt know what to do with that signal to run smartflash.
Worst case scenario...put a full pm58img containing a rom and recovery on the sf card and flash that through bootloader.
You should still be able to get to bootloader as the device looks for that option first.
Sent from my HTC Sensation using xda app-developers app
Click to expand...
Click to collapse
DiscreteTask said:
Hallo. Ok installed CWM. Can please direct me to a full pm58img as you mentioned ? Thx.
Click to expand...
Click to collapse
And did that help? Are you able to get into recovery without errors now? If so you should be able to flash a fresh version of any ROM.
Try that first. Get any ROM. Flash it. See if it boots.
If you have successfully replaced 4EXT I will bet a fresh flash of a ROM will now boot.
Also worth a shot is replacing or upgrading the firmware, as that could be what's sending the phone into recovery on each boot (though this is less likely that 4EXT just being broken)
Flash a firmware PM58IMG like 3.32 or 3.33 and see if that helps.
But for starters, put a fresh ROM on the SD card and flash it with CWM. (BE SURE IT'S A ROM THAT DOESN'T REQUIRE 4EXT!!)
Once you've got it all fixed you can switch back to 4EXT. I have a feeling it was just the copy you were running that got botched. The software itself is solid and stable. A new copy shoudl work fine now.
CWM v5.0.2.0 was installed fine.
3.33 firmware installed once again.
Using this I've installed ROM that I already did in the past w/o luck, they all sit on the HTC logo. Is like the initial boot sequence is broken. Is boot.img part of the firmware or ROM ?
Trying to download some additional ones.
Thanks,
Skipjacks said:
And did that help? Are you able to get into recovery without errors now? If so you should be able to flash a fresh
version of any ROM.
Try that first. Get any ROM. Flash it. See if it boots.
If you have successfully replaced 4EXT I will bet a fresh flash of a ROM will now boot.
Also worth a shot is replacing or upgrading the firmware, as that could be what's sending the phone into recovery on each boot (though this is less likely that 4EXT just being broken)
Flash a firmware PM58IMG like 3.32 or 3.33 and see if that helps.
But for starters, put a fresh ROM on the SD card and flash it with CWM. (BE SURE IT'S A ROM THAT DOESN'T REQUIRE 4EXT!!)
Once you've got it all fixed you can switch back to 4EXT. I have a feeling it was just the copy you were running that got botched. The software itself is solid and stable. A new copy shoudl work fine now.
Click to expand...
Click to collapse
DiscreteTask said:
CWM v5.0.2.0 was installed fine.
3.33 firmware installed once again.
Using this I've installed ROM that I already did in the past w/o luck, they all sit on the HTC logo. Is like the initial boot sequence is broken. Is boot.img part of the firmware or ROM ?
Trying to download some additional ones.
Thanks,
Click to expand...
Click to collapse
The more details you give, the better the answers will be. Don't consider any detail too small.
What do you mean you installed ROM's that you had done in the past? Do you mean you are trying to restore a backup made with 4EXT?
That won't work. You need to flash a fresh version of the ROM after wiping.
Also, CWM won't install some ROM's that you may have used in the past. What ROM are you trying to install?
The HTC logo that first pops up when you hit the power button is part of the firmware.
Make sure you do a full wipe of everything but the SD card from within CWM. Get whatever's causing the problem off that way. Then flash a fresh install of a ROM from scratch.
Hi.
I did not use any backup only fresh ROMs: ARHD, Elegantia, but also stock ROMs I could find.
I've tried also some PG58IMG with ROM included.
Cheers.
Skipjacks said:
The more details you give, the better the answers will be. Don't consider any detail too small.
What do you mean you installed ROM's that you had done in the past? Do you mean you are trying to restore a backup made with 4EXT?
That won't work. You need to flash a fresh version of the ROM after wiping.
Also, CWM won't install some ROM's that you may have used in the past. What ROM are you trying to install?
The HTC logo that first pops up when you hit the power button is part of the firmware.
Make sure you do a full wipe of everything but the SD card from within CWM. Get whatever's causing the problem off that way. Then flash a fresh install of a ROM from scratch.
Click to expand...
Click to collapse
Arhd and elegencia wont work with cwm. So there is your isdue. Try cm9 or 10 to see if you can boot one of those.
Sent from my HTC Sensation using xda app-developers app
Hallo, after trying all option the following did work for me:
- re-lock bootloader via fastboot oem lock
- apply stock ROM founded in this list http://forum.xda-developers.com/showthread.php?t=1074559
- rebooted fine
I guess that HTC RUU had some superpower and erase and installed whatever file(s) were corrupted.
Now I'm on stock 3.6 - fw 3.33.401.106 - radio 11.76A.3504.00UU_11.24A.3504.31_M
HBOOT 1.29 - S-ON - Relocked.
Standard Recovery.
Now I'm reading how to return my device to S-OFF w/o damaging it again.
Many thanks to skipjacks & groog88 :good:
Skipjacks said:
Arhd and elegencia wont work with cwm. So there is your isdue. Try cm9 or 10 to see if you can boot one of those.
Sent from my HTC Sensation using xda app-developers app
Click to expand...
Click to collapse
I have S3 right here and I tried flashing Trickdroid ICS, JB as well as JellyBean Official TWRP zip.
It is S-ON, so after flashing the zip, I go to fastboot and flash boot.img.
I did it already 2-3 times with every rom, but every time I get boot loop. Phone restarts as soon as the first HTC logo disappears.
What is wrong with that?
Do you have the latest TWRP 2.4.1.0 ? (did you try reflashing your recovery?)
What android did you have before unlocking your bootloader? 4.0.3 or 4.0.4?
(and don`t panic If nothing works there is always a solution by relocking your phone and flash the ruu for your phone from here)
http://www.androidfiles.org/ruu/?dir=VilleC2
take a look here:
http://forum.xda-developers.com/showpost.php?p=37498221&postcount=309
impactor said:
I have S3 right here and I tried flashing Trickdroid ICS, JB as well as JellyBean Official TWRP zip.
It is S-ON, so after flashing the zip, I go to fastboot and flash boot.img.
I did it already 2-3 times with every rom, but every time I get boot loop. Phone restarts as soon as the first HTC logo disappears.
What is wrong with that?
Click to expand...
Click to collapse
What's was you on before flashing a custom rom? because just a guess but I think it was 4.0.3 if that is so then try TrickDroid for S3 and get v3 which is 4.0.3 so should work.
It was stock, but I didn't check the version before flashing.
So, TD 3.0, then TD 5.0 and it will work?
By the way, what is better? TD 5.0 or JellyBean Official TWRP?
impactor said:
It was stock, but I didn't check the version before flashing.
So, TD 3.0, then TD 5.0 and it will work?
By the way, what is better? TD 5.0 or JellyBean Official TWRP?
Click to expand...
Click to collapse
No only v3 but if you can get an RUU thats more up to date then do that and the v4/5 should work.
So you didn't install a custom kernal before
Sent from my KFTT using xda premium
KindleFireGuy said:
So you didn't install a custom kernal before
Sent from my KFTT using xda premium
Click to expand...
Click to collapse
Em what he said he did.
You cannot flash S4 roms with an S3 phone, have you made sure that the Roms you flash are specifically assigned for S3? Cuz most are S4
Thanks, guys. That was HBOOT problem. I flashed latest RUU and then I was able to use JB roms.
I am terribly sorry to bump this thread but it is EXACTLY what I need. I read through it and am slightly confused with what you guys said.
Here's my situation:
I have a HTC Evo 3D and have tried running multiple ROMs and on every ROM I run into a boot loop. I use TWRP 2.2.0 and boot that onto my phone using the code "Fastboot boot twrp-shooter.img", then from there I go into TWRP and add the ROM to the root of my SDcard. Then I use TWRP to wipe my cache, delvik cache, system, and do a factory reset. Then I go to install from SDcard and install my desired ROM that I am trying. It is successful and when I reboot it shows the HTC logo, then the loading screen for the ROM, then it goes black, then back to the HTC logo and it continues to loop the same booting sequence over and over.
Am I doing something wrong? Is there something different that I should use or do?
I've been trying to figure out this issue for more than 36 hours and I am borderline psycho right now, I really need answers!
pcout64 said:
I am terribly sorry to bump this thread but it is EXACTLY what I need. I read through it and am slightly confused with what you guys said.
Here's my situation:
I have a HTC Evo 3D and have tried running multiple ROMs and on every ROM I run into a boot loop. I use TWRP 2.2.0 and boot that onto my phone using the code "Fastboot boot twrp-shooter.img", then from there I go into TWRP and add the ROM to the root of my SDcard. Then I use TWRP to wipe my cache, delvik cache, system, and do a factory reset. Then I go to install from SDcard and install my desired ROM that I am trying. It is successful and when I reboot it shows the HTC logo, then the loading screen for the ROM, then it goes black, then back to the HTC logo and it continues to loop the same booting sequence over and over.
Am I doing something wrong? Is there something different that I should use or do?
I've been trying to figure out this issue for more than 36 hours and I am borderline psycho right now, I really need answers!
Click to expand...
Click to collapse
1. check if you are s-on or s-off. If you are s-on, you will also need to flash the kernel (boot.img) from a computer (after you flash the zip)
2. make sure your rom is compatible with your phone
asdfasdfvful said:
1. check if you are s-on or s-off. If you are s-on, you will also need to flash the kernel (boot.img) from a computer (after you flash the zip)
2. make sure your rom is compatible with your phone
Click to expand...
Click to collapse
I already know that I am s-on, and that all I need is the RUU because all I want is to get right the hell back to stock. The problem is that I can't find a RUU that is compatible with my phone!! Your help searching for one would be amazing!!
HTC Evo 3D CDMA Sprint
Mainver: 2.95.652.5
CID: SPCS_002
pcout64 said:
I already know that I am s-on, and that all I need is the RUU because all I want is to get right the hell back to stock. The problem is that I can't find a RUU that is compatible with my phone!! Your help searching for one would be amazing!!
HTC Evo 3D CDMA Sprint
Mainver: 2.95.652.5
CID: SPCS_002
Click to expand...
Click to collapse
Still new to xda, but check this out?
http://forum.xda-developers.com/wiki/HTC_Evo_3D/CDMA
(ctrl + f and find "ruu")
My mainver is not listed, I have already seen this page
The page was last edited in November of 2012, I think it's a bit out of date
Well I've been trying to install miui 3.2.22 for sometime now and after many issues with it not booting I finally got it to boot but now it gets to the optimizing apps screen and once it finishes it says starting apps and just stays there. I've let it sit for over a half hour with no luck. Any ideas?
Sent from my One X using xda app-developers app
avery.0 said:
Well I've been trying to install miui 3.2.22 for sometime now and after many issues with it not booting I finally got it to boot but now it gets to the optimizing apps screen and once it finishes it says starting apps and just stays there. I've let it sit for over a half hour with no luck. Any ideas?
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
What firmware? S-on or S-off?
Bottom line, reflash the boot.img fromt the rom. If you're on 1.14 hboot you'll need to fastboot flash it. That issue seems to come from an issue with the Kernel not flashing properly for one reason or another. You could also try updating or downgrading your TWRP if you're using TWRP as I understand 2.4 had some issues with wiping which could be causing this aswell.
Hope this helps, if you need mroe clarification, post more details about your phone and I or someone else will surely be glad to help.
Thanks for the suggestions. Flashing the boot.img from the original ROM causes booting issues for me. I've had to flash rohans kernel for it to even boot past the splash screen. I'm on hboot 1.14 with s off and using the latest version of twrp
Sent from my One X using xda app-developers app
avery.0 said:
Thanks for the suggestions. Flashing the boot.img from the original ROM causes booting issues for me. I've had to flash rohans kernel for it to even boot past the splash screen. I'm on hboot 1.14 with s off and using the latest version of twrp
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Then either you are not wiping properly or twrp isn't. I don't know about MIUI, what version of Android it is etc, but with Some 4.1 asop/aokp roms, I would be stuck at that screen unless I used B5 as the more up to date kernels did not work for me. (vc or no vc) stuck at the same screen as u. This was really only the case for PA 2.54 that I encountered.
In any case, try flashing an earlier 2.3 version of twrp, wipe cache, dalvik and factory reset, then reflash the stock boot.img using fastboot. Since you are S-OFF I would recommend coming off 1.14 hboot to 1.09. Just makes life a little easier. I am not certain on having S-OFF and 1.14 if you can just flash normally after or not. I was experimenting with S-OFF on my own device and while S-OFF is useful, I am not sure that it completely fixes not needing to flash boot.img using fastboot or if it just makes it easier to downgrade to 1.09 whereby you would certainly not need to use fastboot.
Hopefully someone with first hand experience and not just theoretical knowledge can give some extra advice.
exad said:
Then either you are not wiping properly or twrp isn't. I don't know about MIUI, what version of Android it is etc, but with Some 4.1 asop/aokp roms, I would be stuck at that screen unless I used B5 as the more up to date kernels did not work for me. (vc or no vc) stuck at the same screen as u. This was really only the case for PA 2.54 that I encountered.
In any case, try flashing an earlier 2.3 version of twrp, wipe cache, dalvik and factory reset, then reflash the stock boot.img using fastboot. Since you are S-OFF I would recommend coming off 1.14 hboot to 1.09. Just makes life a little easier. I am not certain on having S-OFF and 1.14 if you can just flash normally after or not. I was experimenting with S-OFF on my own device and while S-OFF is useful, I am not sure that it completely fixes not needing to flash boot.img using fastboot or if it just makes it easier to downgrade to 1.09 whereby you would certainly not need to use fastboot.
Hopefully someone with first hand experience and not just theoretical knowledge can give some extra advice.
Click to expand...
Click to collapse
hmm well I went back to twrp 2.3.3.0 wiped everything flashed the rom, gapps, and rohans kernel on first boot wouldnt boot past boot animation just sat there. rebooted and now im stuck on starting apps screen again. I'll try flashing the boot.img and see if that gets it to work and if it doesnt maybe an earlier version of rohans kernel. Ive never had this problem before
exad said:
Then either you are not wiping properly or twrp isn't. I don't know about MIUI, what version of Android it is etc, but with Some 4.1 asop/aokp roms, I would be stuck at that screen unless I used B5 as the more up to date kernels did not work for me. (vc or no vc) stuck at the same screen as u. This was really only the case for PA 2.54 that I encountered.
In any case, try flashing an earlier 2.3 version of twrp, wipe cache, dalvik and factory reset, then reflash the stock boot.img using fastboot. Since you are S-OFF I would recommend coming off 1.14 hboot to 1.09. Just makes life a little easier. I am not certain on having S-OFF and 1.14 if you can just flash normally after or not. I was experimenting with S-OFF on my own device and while S-OFF is useful, I am not sure that it completely fixes not needing to flash boot.img using fastboot or if it just makes it easier to downgrade to 1.09 whereby you would certainly not need to use fastboot.
Hopefully someone with first hand experience and not just theoretical knowledge can give some extra advice.
Click to expand...
Click to collapse
ahhh! flashig b5 worked:laugh: thanks a ton!
avery.0 said:
ahhh! flashig b5 worked:laugh: thanks a ton!
Click to expand...
Click to collapse
Glad i could help!
Please Help! I have a HTC One X At&t unlocked phone with lot of issues. I decided to install custom ROM on this phone. I am a newbie in the world of rooting, flashing etc. I follow some directions and I was able to unlock my boot loader then installed twrpv.2.6. I tried to flash one custom rom that I found in web, during flashing twrp give me a message "Your phone is not rooted. You want to flash SuperSu. When I confirm and reboot the system, phone stuck in htc logo screen with white back ground. I guess my phone lacking super user permission. Is there any way I can fix my phone?
I tried to manually put su and other files into this phone but its lacking following directories
menorah said:
Please Help! I have a HTC One X At&t unlocked phone with lot of issues. I decided to install custom ROM on this phone. I am a newbie in the world of rooting, flashing etc. I follow some directions and I was able to unlock my boot loader then installed twrpv.2.6. I tried to flash one custom rom that I found in web, during flashing twrp give me a message "Your phone is not rooted. You want to flash SuperSu. When I confirm and reboot the system, phone stuck in htc logo screen with white back ground. I guess my phone lacking super user permission. Is there any way I can fix my phone?
I tried to manually put su and other files into this phone but its lacking following directories
Click to expand...
Click to collapse
You haven't provided enough information. What are your bootloader details? What ROM did you flash?
Have you looked at the Evita FAQ thread? It's stickied at the top of the q&a section you're posting in, I can almost guarantee it contains the solution to your problem.
Your issue isn't with the phone not being rooted, the error message you got in TWRP would have resolved that.
Its highly likely that your issue is that if you are s-on, you neglected to flash boot.img separately using fastboot. By far, the #1 reason for bootloops after flashing a new ROM.
More Details
Here few more details about my phone-
BootLoader- Evita
Recovery - TWRP V 2.6
S- ON - Tried S-Off by flashing PJ8312000-OneX but phone was stuck at the htc logo with black screen
Tried to install SuperSu from chainfire - Installed successfully but when I reboot the system phone stuck at the HTC screen with white background
Phone had AT&T ROM for HTC One XL and I was using T-Mobile simcard. Phone started hang down and restart multiple times when its AT&T hot spot later its been happened randomly. So I decided get ride of AT&T rom and flash custom rom. Following custom roms I tried so far
1. cm-10.2.1-endeavoru- cyanogenmod 10.2(Evita) - I wiped sdcard,data before this installation. Installation failed (I guess its require S-OFF)
2. EVITA_UL_JB_50_S_TMO_DE_5.08.111.2_By_Turge - T-Mobile stock ROM for One XL- Germany -Installation was success but TWRP give me a message "Phone not rooted, flash supersu, when I flash it , phone stuck at HTC logo with white background
3. cm-11-20140218-NIGHTLY-evita - cyanogenmod 11(Evita) - Failed
4. Android_Revolution_HD-One_X_33.1 - This one come with a installer (aroma i guess), I thought finally.... but when the system reboot, its stuck again on the same screen.
Few screen shots are attached
menorah said:
Here few more details about my phone-
BootLoader- Evita
Recovery - TWRP V 2.6
S- ON - Tried S-Off by flashing PJ8312000-OneX but phone was stuck at the htc logo with black screen
Tried to install SuperSu from chainfire - Installed successfully but when I reboot the system phone stuck at the HTC screen with white background
Phone had AT&T ROM for HTC One XL and I was using T-Mobile simcard. Phone started hang down and restart multiple times when its AT&T hot spot later its been happened randomly. So I decided get ride of AT&T rom and flash custom rom. Following custom roms I tried so far
1.cm-10.2.1-endeavoru- cyanogenmod 10.2(Evita) - I wiped sdcard,data before this installation. Installation failed (I guess its require S-OFF)
2.EVITA_UL_JB_50_S_TMO_DE_5.08.111.2_By_Turge - T-Mobile stock ROM for One XL- Germany -Installation was success but TWRP give me a message "Phone not rooted, flash supersu, when I flash it , phone stuck at HTC logo with white background
3.cm-11-20140218-NIGHTLY-evita - cyanogenmod 11(Evita) - Failed
4.Android_Revolution_HD-One_X_33.1 - This one come with a installer (aroma i guess), I thought finally.... but when the system reboot, its stuck again on the same screen.
Few screen shots are attached
Click to expand...
Click to collapse
Well, where should I start. What do you mean when you say the phone was stuck at the HTC logo on black screen after flashing the PJ8312000-OneX.zip?
Now onto the ROMs you've flashed.
1. The problem is this: cm-10.2.1-endeavoru-. Can you see what's wrong with that? Maybe the fact that it says Endeavoru in the filename when you don't have the Endeavoru phone, you have the Evita. You're lucky that ROM didn't brick you.
2. You most likely just needed to flash the boot.img from that ROM through fastboot. At least that one is meant for our phone though.
3. This ROM is for our phone as well. Your problem with that one is that you're using the wrong recovery. You need the unofficial modified TWRP 2.6.3.0 from our Original Android Development section to flash KitKat ROMs.
4. And here's another ROM that isn't for our phone.
I'm not sure where you found those two ROMs that aren't for our phone.
My guess is that you've somehow stumbled into the the HTC One X Endeavoru forum, don't ever go into that forum, not a single thing there is compatible with our phone. You're extremely lucky you haven't bricked after flashing two incompatible ROMs, you should buy a lottery ticket.
Do yourself a huge favour and stay within our device forum (HTC One XL / at&t One X Evita), here's the main page, bookmark this:
One XL Main Page
http://forum.xda-developers.com/forumdisplay.php?f=1538
And here are our two development sections:
One XL Android Development
http://forum.xda-developers.com/forumdisplay.php?f=1541
One XL Original Android Development
http://forum.xda-developers.com/forumdisplay.php?f=1726
Only ever download ROMs from those two sections.
Please read the Evita FAQ thread I mentioned before, your answers are there. You should also read my How-To Guide For Beginners thread, it contains information you probably desperately need. Both of those are linked in my signature.
Sent from my Evita
menorah said:
2. EVITA_UL_JB_50_S_TMO_DE_5.08.111.2_By_Turge - T-Mobile stock ROM for One XL- Germany -Installation was success but TWRP give me a message "Phone not rooted, flash supersu, when I flash it , phone stuck at HTC logo with white background
Click to expand...
Click to collapse
The TWRP message is appearing as it should, as the ROM is not rooted (as mentioned right in the top post of the thread for this ROM) and TWRP will show this any time you flash an unrooted ROM. Whether you pick the option for TWRP to root (I use this ROM, and that is what I picked) or not, this is not the cause of your boot issue.
Its more likely your issue is that you didn't extract and flash boot.img manually via fastboot. This is required for s-on, and if you don't know what this means, its absolutely the cause for why your phone won't boot.
Refer to timmaaa's guide for details:
http://forum.xda-developers.com/showthread.php?t=2593382
Thanks
redpoint73 said:
Your issue isn't with the phone not being rooted, the error message you got in TWRP would have resolved that.
Its highly likely that your issue is that if you are s-on, you neglected to flash boot.img separately using fastboot. By far, the #1 reason for bootloops after flashing a new ROM.
Click to expand...
Click to collapse
Thanks Brother! You saved my phone. I was very close to get a new phone. After I flash boot.img, phone was able to getout of bootloop and flashed the rom EVITA_UL_JB_50_S_TMO_DE_5.08.111.2_By_Turge.
Now if i want to do a different rom cm-11-20140218-NIGHTLY-evita just do the same steps? push the rom to sdcard, extract boot.img from from rom and flash boot.img?
Thanks
timmaaa said:
Well, where should I start. What do you mean when you say the phone was stuck at the HTC logo on black screen after flashing the PJ8312000-OneX.zip?
Now onto the ROMs you've flashed.
1. The problem is this: cm-10.2.1-endeavoru-. Can you see what's wrong with that? Maybe the fact that it says Endeavoru in the filename when you don't have the Endeavoru phone, you have the Evita. You're lucky that ROM didn't brick you.
2. You most likely just needed to flash the boot.img from that ROM through fastboot. At least that one is meant for our phone though.
3. This ROM is for our phone as well. Your problem with that one is that you're using the wrong recovery. You need the unofficial modified TWRP 2.6.3.0 from our Original Android Development section to flash KitKat ROMs.
4. And here's another ROM that isn't for our phone.
I'm not sure where you found those two ROMs that aren't for our phone.
My guess is that you've somehow stumbled into the the HTC One X Endeavoru forum, don't ever go into that forum, not a single thing there is compatible with our phone. You're extremely lucky you haven't bricked after flashing two incompatible ROMs, you should buy a lottery ticket.
Do yourself a huge favour and stay within our device forum (HTC One XL / at&t One X Evita), here's the main page, bookmark this:
One XL Main Page
http://forum.xda-developers.com/forumdisplay.php?f=1538
And here are our two development sections:
One XL Android Development
http://forum.xda-developers.com/forumdisplay.php?f=1541
One XL Original Android Development
http://forum.xda-developers.com/forumdisplay.php?f=1726
Only ever download ROMs from those two sections.
Please read the Evita FAQ thread I mentioned before, your answers are there. You should also read my How-To Guide For Beginners thread, it contains information you probably desperately need. Both of those are linked in my signature.
Sent from my Evita
Click to expand...
Click to collapse
Thanks a lot! I was able to flash the second rom EVITA_UL_JB_50_S_TMO_DE_5.08.111.2_By_Turge.I extracted the rom, flash boot.img. I didn't realize that, there are multiple model for this phone. I thought only one HTC One X. I wanna try cyanogenmod 11 and I already have TWRP 2.6.3.0. So just do the some steps?
Yes, the same steps exist for any ROM you want to flash. Make sure you also flash gapps when you're installing an aosp ROM.
Sent from my Evita
menorah said:
Thanks Brother! You saved my phone. I was very close to get a new phone.
Click to expand...
Click to collapse
You're welcome. And just so you know, this phone is virtually always recoverable, as long as the screen comes on. Its just a matter of trouble shooting what you did wrong, and performing the correct steps. Usually pretty simple to get the phone bootable, as long as the screen comes on at all. So in the future, don't panic. Just take some deep breaths, and come on here and do some research, or ask if you can't find the answer.