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
i was able to successfully unlock bootloader, was able to flash a rom successfully, used that rom for a good couple days. then i decided to try a new rom InfectedROM Eternity™ | RLS_1.5 | NIGHTLYS | 3.0 & 3.5 | XE BEATS |(http://forum.xda-developers.com/showthread.php?t=1277431&highlight=stock+radio), so i went into recovery, wipe cache, dalvik, factory reset, system. then i flashed the new rom, new rom loaded but stuck in that roms boot screen.
i went back to recovery wiped everything out again, installed the 1st orig rom i installed, now it just loads to the htc boot screen, & every 30sec or so the htc boot screen would go off & come back on. i went to recovery wiped everything again, did nandroid restore, same results, any suggestions?
what im using:
unlocked bootloader
s -on
hboot 1.50
using teamwin recovery v2.0
Just wipe flash a new rom. Should be good to go
reaper24 said:
Just wipe flash a new rom. Should be good to go
Click to expand...
Click to collapse
already tried no luck
flyimages said:
already tried no luck
Click to expand...
Click to collapse
Did you apply any tweaks or different kernels? was your kernal that you are on now compatible with the rom that you had put on? The recovery your on, r you on 2.0 or the second releaese of 2.0?
You could try to reflash your recovery and then try to nandroid back. Or try a different kernel and or different rom and go from there. Kind of hard to diagnose bc not sure of exactly what you have done completely. If all else fails, search for the ruu and re apply the original rom and re root.
From my guess, it sounds as something that was applied didn't apply right. Again, not sure on all the details.. I know its not much to go on but good luck on it.
Look at the bright side, your obviously not bricked and if you have to re apply the original and start over, its not that bad. Just a little time out of the afternoon.
only update i did was the rom
tried about 2 more diff roms, still same issue
hmm.. i also choose the "system format" in twrp, would that have done some damage?
Are you using fastboot to boot into recovery? If not, and you're hboot 1.5, then that's your problem.
And wiping system wouldn't cause any issues as long as you flash a new ROM after wiping the system, before you reboot.
Sent from my HTC Evo 3D using Tapatalk
k2buckley said:
Are you using fastboot to boot into recovery? If not, and you're hboot 1.5, then that's your problem.
And wiping system wouldn't cause any issues as long as you flash a new ROM after wiping the system, before you reboot.
Sent from my HTC Evo 3D using Tapatalk
Click to expand...
Click to collapse
ah ok i manually go into hboot with the down volume + power. did "fastboot reboot-bootloader" into bootloader, wiped out everything & reinstall rom, still same issue.
Try extracting the boot.img from the zip file containing the rom and flashing it with with fastboot binary. If you have S-ON, CWM can't flash the boot partition so you'll get bootloops with any rom that needs a custom initrd.gz. You need to manually flash the boot partition.
flyimages said:
ah ok i manually go into hboot with the down volume + power. doing fastboot into bootloader now, so we'll see.
Click to expand...
Click to collapse
Yea, do adb reboot bootloader, and then do fastboot boot recovery.img.
You will need to make sure that you have a copy of your recovery.img in the folder that you are working out of when you issue the fastboot boot recovery.img command
Sent from my HTC Evo 3D using Tapatalk
k2buckley said:
Yea, do adb reboot bootloader, and then do fastboot boot recovery.img.
You will need to make sure that you have a copy of your recovery.img in the folder that you are working out of when you issue the fastboot boot recovery.img command
Sent from my HTC Evo 3D using Tapatalk
Click to expand...
Click to collapse
thanks all for the help, the "fastboot flash recovery recovery.img" was pretty much what i was missing!
wow didnt wonder somethin so small could cause something this big, i got everything up & running now!
flyimages said:
thanks all for the help, the "fastboot flash recovery recovery.img" was pretty much what i was missing!
wow didnt wonder somethin so small could cause something this big, i got everything up & running now!
Click to expand...
Click to collapse
glad to see your on the up and up
Okay, I'm having the same problem. No matter what I do, I get stuck in a boot loop after installing a rom. Extracting the boot.img and flashing in fastboot doesn't do a thing. My nand backups don't work either (get stuck at restoring boot).
Don't have any problems installing recovery and gaining root. I'm at a loss here. I really want to get my MIUI on!
Mes3 said:
Okay, I'm having the same problem. No matter what I do, I get stuck in a boot loop after installing a rom. Extracting the boot.img and flashing in fastboot doesn't do a thing. My nand backups don't work either (get stuck at restoring boot).
Don't have any problems installing recovery and gaining root. I'm at a loss here. I really want to get my MIUI on!
Click to expand...
Click to collapse
Are you booting your recovery from fastboot? Fastboot boot recovery.img. If not, boot.img won't flash. It's not necessary to flash the boot.img separately, just boot your recovery from fastboot and you'll be good.
Sent from my HTC Evo 3D using Tapatalk
Yup, definitely booting recovery from fastboot.
I had the same problem try to install new recovery VIA fastboot an wipe data/factory reset then flash new ROM u should be all set to go
Sent from EPIC JWOLF 1 using XDA App
ok so i have a htc evo 3d hboot 1.4 with s-off. my phone kept doing weird things like pushing buttons and scrolling thru pages while idle. so i decided to do a fresh rom flash. i got the bright idea to use the superwipe tool and it messed up my phone. i can go into boot loader but not to recovery because the tool wiped my clock work mod. so now i am stuck. pleas help!
Use fastboot to flash a new recovery image via boot loader/fast boot.
I believe the command is
Code:
fastboot flash recovery recovery.img
Sent from my AOSP 3VO
So I went to flash the Blackout Rom on my One X+ and forgot to flash the boot.img first. so my phone will not boot up. and when i boot into to flash the boot.img it says Battery too low for Flash. Can anyone help?
I can't even boot into recovery. Can someone please help?
I had this problem yesterday when i got my new phone. Flashed the rom but not the boot.img file. It bootlooped but as it turned off i pressed vol down and power and luckily it booted into the bootloader. If you can get into fastboot, flash the boot.img and then your phone should boot. Worked for me!
Good luck
Daking12794 said:
So I went to flash the Blackout Rom on my One X+ and forgot to flash the boot.img first. so my phone will not boot up. and when i boot into to flash the boot.img it says Battery too low for Flash. Can anyone help?
Click to expand...
Click to collapse
You need to flash the boot.img from that Rom.
Boot the phone straight into bootloader then go to fastboot mode and flash the new boot.img from your computer.
Sent from my HTC One X+ using xda premium
Every time I try and boot my desire to recovery it instead flashes the "entering recovery" screen for a second and spits me right back to fastboot. I have unlocked the bootloader using windroid toolkit v3.1 and even tried flashing twrp v3.1 via adb. It says that the flashing is completed successfully, but clearly it didn't as this problem persists.
Any ideas? I've even tried erasing the recovery partition, but I get remote: not allowed.