• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Soft brick? :( stuck in bootloop

E

ericm92

Lurker
Hello,

I recently rooted for my first time, unlocked w/S-ON, but for some reason a lot of the ICS roms I have been running will glitch and bootloop. The most recent one began bootlooping before I could remove PH981.img so now I can't even access recovery to wipe my phone. I think I messed up and did not relock and install new firmware, instead I had tried to do it while still unlocked.

Please help! Phone will connect to computer but I don't get drive access. Thank you!
 
Hey, welcome to AF! I am going to move this to the All Things Root section, they will be better able to answer your question in there. Thanks for Understanding.
 
ericm92 said:
Hello,

I recently rooted for my first time, unlocked w/S-ON, but for some reason a lot of the ICS roms I have been running will glitch and bootloop. The most recent one began bootlooping before I could remove PH981.img so now I can't even access recovery to wipe my phone. I think I messed up and did not relock and install new firmware, instead I had tried to do it while still unlocked.

Please help! Phone will connect to computer but I don't get drive access. Thank you!
Click to expand...

Could you provide us with a little more info? What ICS roms have you tried installing and what is the one now? Aso what firmware verson are you on?
 
Do you have a card reader or another phone you can stick the sd card into? Those are the two easiest ways to remove the IMG.zip.
 
ericm92 said:
Hello,

I recently rooted for my first time, unlocked w/S-ON, but for some reason a lot of the ICS roms I have been running will glitch and bootloop. The most recent one began bootlooping before I could remove PH981.img so now I can't even access recovery to wipe my phone. I think I messed up and did not relock and install new firmware, instead I had tried to do it while still unlocked.

Please help! Phone will connect to computer but I don't get drive access. Thank you!
Click to expand...

as was said,put your card into a card reader to remove PH98IMG. you can then get to recovery to fix your issue.

you prolly need to falsh the old firnmware patch if you are on GB firmware(hboots 2.05,2.10,2.11) and want to run ICS roms.

i personally would advise that you do not install the leak ruu to get the newer firmware. leaks are leaks,and may not be good :eek: if you are s-on,there is no way to revert back to the GB firmware. wait till ICS is oficially release,and then install the release version to upgrde fimrware.

on to your prollem. once youve remover ph98img,you can launch recovery from fastboot and fix your prollem a couple different ways:
1)full wipe and restore a backup
2)full wipe and reinstall a rom. you can install a GB rom,wich will not require any patches,or flash an ics rom,followed by the old firmware patch.

if youre unfamiliar with launching recovery from fastboot:
1)place your recovery image into your folder containing adb/fastboot
2)place the phone in "fastboot" mode(power on into hboot,choose fastboot from menu)
3)use this command to launch recovery:
fastboot boot recoveryname.img

example,using an image called"recovery-amon-3.15" the command is:
fastboot boot recovery-amon-3.15.img

launching recovery in this manner,lets the recovery install kernels,where a permanent mounte recovery can not(htcdev does not allow recovery partion to write to boot partition). this will let you restore backups,and even flash roms(if they are set up for s-off flashing) just like an s-off phone. with s-on,a a recovery installed in the recovery partition will rwquire a kernel to be flashed seperately in hboot or fastboot,if there is a kernel change.

hope that helps :)
 
Hello, total noob here (not even sure if I should post to this thread or start a new one so please forgive me if I'm breaking procedure). Trying to get rooted, I followed Scotty's excellent directions to get rooted. I had the superuser issue where it failed to install (installation aborted). I then kept reading and found out this is normal (just re-wipe and re-install). I went to get to recovery again and it will no longer allow me to get into the recovery image. It keeps giving me the following:

C:\mini-adb_vigor>fastboot boot recovery-ra-vigor-3.14-gnm.img
downloading 'boot.img'... FAILED (command write failed (Unknown error))
finished. total time: 0.637s

The superuser icon is there but it isn't working.

Please help on what I should do from here.
 
frank6773 said:
Hello, total noob here (not even sure if I should post to this thread or start a new one so please forgive me if I'm breaking procedure). Trying to get rooted, I followed Scotty's excellent directions to get rooted. I had the superuser issue where it failed to install (installation aborted). I then kept reading and found out this is normal (just re-wipe and re-install). I went to get to recovery again and it will no longer allow me to get into the recovery image. It keeps giving me the following:

C:\mini-adb_vigor>fastboot boot recovery-ra-vigor-3.14-gnm.img
downloading 'boot.img'... FAILED (command write failed (Unknown error))
finished. total time: 0.637s

The superuser icon is there but it isn't working.

Please help on what I should do from here.
Click to expand...
is the phone in fastboot(not hboot) and connected to the PC? amon is in the mini-adb_vigor folder? do you get your serial number back from "fastboot devices"?
 
Scotty,

Thanks for responding. I finally got into recovery and loaded this rom (Vigor_Stock_Doedexed_3.14.605.5). It looks like I am now in the same spot as with the person on this thread that I posted to, where it keeps going in loops re-booting. However, when I followed your instructions to flash a rom, I could not get it to flash the boot image, see below, so I finally unplugged it and rebooted it as it wasn't connected any longer, now I have the issue where it keeps rebooting. Do I do the same instructions as you told this person (delete the zip off the card and so on)?

C:\mini-adb_vigor>adb devices
List of devices attached
HT19TS205091 recovery


C:\mini-adb_vigor>adb reboot bootloader

C:\mini-adb_vigor>fastboot flash boot.img
unknown partition 'boot.img'
error: cannot determine image filename for 'boot.img'

C:\mini-adb_vigor>fastboot flash boot boot.img
sending 'boot' (3896 KB)... FAILED (remote: not allowed)
finished. total time: 0.003s

C:\mini-adb_vigor>fastboot flash boot boot.img
sending 'boot' (3896 KB)... FAILED (status read failed (Unknown error))
finished. total time: 443.279s

C:\mini-adb_vigor>
C:\mini-adb_vigor>adb devices
List of devices attached
 
Well, I kept persisting and now I think I'm further in the hole. I deleted the zip off the SD card but now cannot get into recovery. I also tried to go to "Factory Reset" to get it all back. Now it boots up, but as soon as I go to dial, it reboots on me. Please help!

C:\mini-adb_vigor>adb devices
List of devices attached
HT19TS205091 recovery

C:\mini-adb_vigor>adb reboot bootloader

C:\mini-adb_vigor>fastboot flash boot.img
unknown partition 'boot.img'
error: cannot determine image filename for 'boot.img'

C:\mini-adb_vigor>fastboot flash boot boot.img
sending 'boot' (3896 KB)... FAILED (remote: not allowed)
finished. total time: 0.003s

C:\mini-adb_vigor>fastboot flash boot boot.img
sending 'boot' (3896 KB)... FAILED (status read failed (Unknown error))
finished. total time: 443.279s

C:\mini-adb_vigor>
C:\mini-adb_vigor>adb devices
List of devices attached


C:\mini-adb_vigor>
C:\mini-adb_vigor>adb devices
List of devices attached
 
frank6773 said:
Well, I kept persisting and now I think I'm further in the hole. I deleted the zip off the SD card but now cannot get into recovery. I also tried to go to "Factory Reset" to get it all back. Now it boots up, but as soon as I go to dial, it reboots on me. Please help!

C:\mini-adb_vigor>adb devices
List of devices attached
HT19TS205091 recovery

C:\mini-adb_vigor>adb reboot bootloader

C:\mini-adb_vigor>fastboot flash boot.img
unknown partition 'boot.img'
error: cannot determine image filename for 'boot.img'

C:\mini-adb_vigor>fastboot flash boot boot.img
sending 'boot' (3896 KB)... FAILED (remote: not allowed)
finished. total time: 0.003s

C:\mini-adb_vigor>fastboot flash boot boot.img
sending 'boot' (3896 KB)... FAILED (status read failed (Unknown error))
finished. total time: 443.279s

C:\mini-adb_vigor>
C:\mini-adb_vigor>adb devices
List of devices attached


C:\mini-adb_vigor>
C:\mini-adb_vigor>adb devices
List of devices attached
Click to expand...

when you get the phone in fastboot,you need to do a "fastboot devices" to see if your connected.

is your bootloader unlocked? if not,are you s-off? youll need to flash an eng hboot,or the jpbear hboot,in order to use fastboot boot,and fastboot flash.

if you are locked and s-on,then you need to unlock :eek:;)

the the other option would be to just put your boot image onto your sd card as a PH98IMG file,and let flsh that way.

last and not least,if youre on GB firmware,you need to flash the "old firmware patch" so that ICS roms will work.

hope that helps :)
 
Thanks Scotty, ok now the bootloop is done and I still have some form of ICS but the dialer doesn't work (every time I dial it reboots). Phone calls coming in forces a reboot too.

I can get to fastboot (see below). Shows VIGOT PVT SHIP S-ON RL on the Hboot screen. Bootloader is unlocked. After this I do the attempt to get to recovery and I have the failures shown in the previous post. At this point, I just want to revert back to stock however I can. Can you tell me how to put the boot img as a PH98IMG file per your suggestion? I can put what I need directly on the SD card and can get to fastboot so please if you can put what file I need to copy to get back to start, I would be so grateful. I promise not to tinker until I learn much more in the future! :( I'm about ready to re-activate to my old phone (a Dinc that I had rooted/flashed so much easier than this).

C:\mini-adb_vigor>adb reboot bootloader

C:\mini-adb_vigor>fastboot devices
List of devices attached
HT19TS205091 fastboot

C:\mini-adb_vigor>fastboot flash boot boot.img
sending 'boot' (3896 KB)... FAILED (remote: not allowed)
finished. total time: 0.003s
 
you have not changed your kernel yet,so the best option to go back to stock is to just restore a backup. if you dont have one,you could flash a 2.01.605.11 based rom.

the ph98img containing the boot image is usually available to download from post where you download the rom.

again,if youre on GB firmware make sure youve flashed this old firmware patch in recovery

also,launching the recovery from fastboot,should let you simply flash the rom,if it is set up for the s-off crowd to install the boot image from recovery during the rom flash.

the critical issue is why these commands arent working for you,as from the info you provided,they should be.

again:
do you get a serial nuber back from fastboot devices?
are your recovery and boot images in the same folder with adb/fastboot? have you checkd the md5 of your recovery image?

the only things i can think of,at this point:
-make sure you have disabled htc sync,or any program capable of communicating with the phone
-try different usb cables and ports
-try a reboot of the pc
-try re-downloading mini-adb,maybe the fastboot utility as somehow become corrupt
 
Scotty, I can't thank you enough.

I do get a serial number back from fastboot. I recopied the recovery from the xda site and confirmed the md5 of the image. You're hint on other programs connecting unjarred my head! I think that is what might have been messing things up; I had the easy tether program set to auto connect (didn't realize that). I turned that off and am now restoring my backup. It worked! I am at least back to square one. I still have ICS envy but I have my phone back :-)

Do you think the easy tether was the source of the issue or was it more likely a corrupt recovery image (I hate when I change 2 things at once)?

Thanks again Scotty!
 
Glad you are back in business! I'd prolly point my finger at the easy tether program,as a corrupt recovery image would likely still have flashed,and then hung at the splash trying to boot to it,dep on the severity of the corruption. It would need to be pretty effed up to not be recognized as a flash able image(which is possible)

You should be able to hopefully flash your boot images now,if you want to try ics again. Just make sure you flash the old firmware patch right after flashing the rom :)
 
You must log in or register to reply here.
Back
Top Bottom