Greetings!
I won't ask questions how its done (I have flashed custom roms for 2 years now), but now I've got a problem.
I'm Using HTC One X+ (ENRC2B_U, Hboot 1.72, Radio 3.1204.171.33, S-ON)
My problem now is that after last nighty cyanogenmod (20.05.2014) I cant boot my phone in recovery mode.
No one is working, CMW - not working (officialy bought), TWRP - not working (just black screen). I can boot my system using latest cyanogen. No errors in fastboot (fastboot flash recovery twrp.img), so I'm just little "confused" what to do next?
Can someone give me advice with this black screen problem? I also flashed original stock rom, it boot up, but customized stays black.
Best Regards to community.
Related
hi guys iive unlocked my evo with the htcdev mod and no problem has come out , bun i'm unable to run any recovery.
iìve tryed all cwm twrp and any i found on the site.
i try with fastboot method and abd, all say that the recovery vas written , no error but when i try to lunch recovery the phone show the htc logo stay 10/15 second then reboot the phone.
pls help me
Have you tried downloading the twrp pg86img.zip & make sure it's named PG86IMG.zip then put it on the root of you're sdcard, boot into bootloader and update that way?
CM powered EVO 3D, enough said.
luca73n said:
hi guys iive unlocked my evo with the htcdev mod and no problem has come out , bun i'm unable to run any recovery.
iìve tryed all cwm twrp and any i found on the site.
i try with fastboot method and abd, all say that the recovery vas written , no error but when i try to lunch recovery the phone show the htc logo stay 10/15 second then reboot the phone.
pls help me
Click to expand...
Click to collapse
when the device either hangs on the htc logo or reboots while on the htc logo, it means there is an issue with the actual kernel/ramdisk.
when dealing with a custom recovery, they should always boot without any issues. the best suggestion off the top of my head is to make sure if you're on the CDMA version, use the shooter recovery and if you're on the GSM version, use the shooteru version of the custom recovery.
otherwise, as suggested above, reflash the confirmed correct custom recovery for your device. there are a few ways to flash the custom recovery although, being you used the htc unlock method, regular custom recovery mode will not have write access to the boot/kernel partition.
if you're interested in loading any ROMs which come with kernels or separately flashing a custom kernel, there are essentially two complete methods:
1) use my Flash Image GUI app from normal android mode to flash the kernel. then flash the ROM from custom recovery.
2) use fastboot boot c:\android\cwm-recovery.img . this will temporarily boot the custom recovery and htc unlock will grant it write access to the kernel/boot partition. this command is different than fastboot flash recovery c:\android\cwm-recovery.img. the fastboot boot will temporarily boot into the custom recovery while fastboot flash will permanently write it into the recovery partition.
hope all the extra details make sense and helps!
Ummm.....Just my 2 cents, but it sounds as though the most basic possible problem has been overlooked here. You need to go into menu>settings>power and uncheck the "fast boot" box or do a battery pull, then try to boot into your bootloader to access recovery. With your phone completely powered down (fast boot unchecked or after battery pull), hold volume down and press power. That will put you in your bootloader with an option to boot recovery from there.
ok i'm a noob i've used thr shooter and not the shooteru cwm img, now all works
ty guys
Hi,
I've rooted my Flyer after reading several posts. I used the HTCdev way to root. Everything went fine.
Afterwards I wanted to install Leedroid. The red text on the forum post indicated that if the HTCdev way was used i needed to extract the boot.img and flash it using fastboot. Done that, then I wanted to boot into recovery but there is my problem, when i press recovery it shows me the white screen with green HTC letters.
I've tried to flash cwm from http://forum.xda-developers.com/showthread.php?p=14693680 using fastboot and it flashed. Still, when I select recovery i still get the white screen with the HTC letters.
Any help what I'm doing wrong?
Ok, I've fixed my problem and got back in my original rom.
What i did was extracting my image from my downloaded RUU and reflashed the boot and recovery images.
Glad I got it working again!
Hey,
I just tried to install an custom rom at my Android, i unlocked it on HTCdev`s site, but i think i was a little fast with the DooMLoRD_v2_ROOT-zergRush-busybox-su.zip
I then bootet the phone into fastboot, and did the command fastboot flash boot boot.img, this worked very fine but now the phone wont boot.
I think maybe the phone is unlocked, but it is S-ON. I have tried diffrent recovery modes with the fastboot flash recovery recovery.img etc, but none of them are working.
Now im sitting with a phone that wont boot at all, what to do?
Is it possible to keep going on with the custom rom install, or can i resett the phone into the stock rom?
-Thanks.
i just tried an factory resett, but when i do the HTC logo shows for about 5 secounds, then the phone turns black and nothing happens.
also tried to boot the phone in all modes, but it hangs on the htc quietly brilliant screen.
Not booting is usually the kernel. Try reflashing the kernel or another compatible one. The recovery.img should be placed where you have placed fastboot.exe normally on c:/android.
If the kernel and recovery flashed you should be able to access the bootloader and recovery by a button combo.
Sent from my PG86100 using xda app-developers app
junxracr said:
Not booting is usually the kernel. Try reflashing the kernel or another compatible one. The recovery.img should be placed where you have placed fastboot.exe normally on c:/android.
If the kernel and recovery flashed you should be able to access the bootloader and recovery by a button combo.
Sent from my PG86100 using xda app-developers app
Click to expand...
Click to collapse
Ok, i have tried to reflash the kernel but not realy sure how.
Been on HTCdev and downloaded orginal kernel, but how do i get this one the phone?
i hace tried to flash Clockwork recovery, but it dint help.
I have also tried to flash many diffrent boot.img, but none of them did work.
Is there any way to pull out the orginal boot.img or just install a new kernel?
-thanks
Hi All,
I have a HTC ONE X+ on O2 UK, it has HBOOT 1.72, S-ON, Radio-3.1204.171.33
I tried being clever and Rooted the phone following hasoon2000 instructions. It was so simple and worked so well i got cocky.
Successfully rooted and installed TWRP 2.6 recovery, used the phone for the whole of 5 minutes before deciding if that was so easy i may as well try flashing a ROM....
I tried CM11 snapshot 15/09/2014, it failed so i restored my back up and all was fine. On the CM wiki i read this bit ..
This device, if unlocked with HTCDev Unlock, must have its kernel flashed via fastboot. Extract boot.img from the CyanogenMod .zip package and flash it from the bootloader with: fastboot flash boot boot.img
Click to expand...
Click to collapse
So i did that, and now i am stuck in boot loop of the HTC quietly Brilliant screen.
I can get into recovery restore my backup but i am still stuck in a boot loop. I assume i need a boot.img with certain information to allow it to go any further. I tried the
RUU RUU_ENRC2B_U_JB_45_O2_UK_1.14.206.13_Radio_3.1204.167.31_release_289474_signed
Click to expand...
Click to collapse
but assume the problem is my HBOOT and Radio are more up to date. (Shows error on screen saying incompatible)
My ideal would be to have a working CM11 Snapshot or CM10.2 on the device, i would settle for stock and back to 4.2.2 and working.
Any help would be great.
Cheers
read this thread: http://forum.xda-developers.com/showthread.php?t=2510836
it tells you to use clockworkmod recovery and not twrp. atm you can't use twrp for kitkat based roms
hold power button until phone turns off. then turn on holding VOL-DOWN to enter bootloader.
now you can flash cwm recovery and boot.img extracted rom.zip
You can only flash a new kernel by booting in the bootloader.... Therefore, whenever you switch rom you'll have to flash kernel compatible to that particular rom.
So, enter bootloader, connect your phone and use command "fastboot flash boot <kernel path>"
crusader727 said:
read this thread: http://forum.xda-developers.com/showthread.php?t=2510836
it tells you to use clockworkmod recovery and not twrp. atm you can't use twrp for kitkat based roms
hold power button until phone turns off. then turn on holding VOL-DOWN to enter bootloader.
now you can flash cwm recovery and boot.img extracted rom.zip
Click to expand...
Click to collapse
Seemingly it was as simple as not being able to use twrp with the latest CM11. Thanks so much, happily on 4.4.4 now.
The thread was from 2012 and the twrp site seemed to indicate otherwise, but soon as i switched recovery it was sorted.
Cheers!
bighead85 said:
Seemingly it was as simple as not being able to use twrp with the latest CM11. Thanks so much, happily on 4.4.4 now.
The thread was from 2012 and the twrp site seemed to indicate otherwise, but soon as i switched recovery it was sorted.
Cheers!
Click to expand...
Click to collapse
Fixing TWRP is on my list of things to do...by the looks of it I need to get to it sooner rather than later
Hey guys i have a htc m8 with 4.4.4 unlocked bootloader s-on but can't get into twrp recovery anymore, every single time that i try it tried for about 10 seconds then boots back to the phone. Any suggestions?
nillyizback said:
Hey guys i have a htc m8 with 4.4.4 unlocked bootloader s-on but can't get into twrp recovery anymore, every single time that i try it tried for about 10 seconds then boots back to the phone. Any suggestions?
Click to expand...
Click to collapse
To be clear, you are in hboot, and when you select recovery, it just reboots to OS?
And you don't get a red triangle (stock recovery)?
If the above are true, try fastboot erase cache, and install TWRP again. This solves a great many instances of failure to boot into recovery. Or try a different TWRP version if it still doesn't work.