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

Root Boot looped

ok i just sent the pm to scotty85 who is a very knowledgeable and hopefully will bring a second pair of eyes that might help see a way to fix it.

now you have a couple of issues that is making this a little harder to troubleshoot. one is that you have the latest firmware in your radio. it is one reason to never take an OTA(over the air update). we do not have a ruu(rom upgrade utility) with the current firmware from the ota(sprint has not and most likely will not release the source code). so there is not PC36IMG file or a ruu that will work.

the other issue is that we can't install a custom recovery. having one can help a great deal with issues like yours. but since we can't get there or even install one does not help. also another tool we could have used to help troubleshoot would be to use adb commands, but with a phone that is not bootable and no recovery, adb commands will not work. i was thinking that we can try and downgrade your misc partitions so that we can use a previous ruu, but we need adb commands to work.

at the moment i can't think of anything else that can be done to fix your phone. hopefully scotty85 has another trick up his sleeve as he seems to always have one.
 
hi dave! just a couple of things at this point... what OS were you originally using when you unlocked and tried to flash recovery? the comment above about using a win7 VM makes me thing you were using a mac or linux maching,but maybe thats an incorrect assumption.

assuming you were using a windows 7 or lower machine at first,i think we should work on fixing your driver issue. not to worry that usb debug isnt enabled,it has no bearing on using FASTBOOT and fastboot commands.

here are some basic troubleshooting driver steps:
troubleshooting connectivity issues:
-try a reboot of the PC
-try different usb cables and ports
-dont use a usb hub
-dont use usb 3.0
-make sure nothing capable of comunicating with the phone is enabled and running. htc sync,pdanet,easy tether,and even itunes have all been known to cause issues.
-windows 8 has been known to have issues. try a windows 7 or older machine

failing the above,
-i use these drivers for fastboot and adb(donwload and run as admin): http://downloads.unrevoked.com/HTCDriver3.0.0.007.exe

failing that,try manually updating the drivers in the following manner:
-put the phone in fastboot mode(select fastboot from the hboot menu)
-open device manager on the PC
-plug in phone,watch for it to pop up in device manager.
-update drivers with device manager,pointing the wizard to the extracted
driver download folder from above

note that you can check the connectivity of the phone,and make sure drivers are working by in the following manner:
-open cmd window. change to directory containing adb/fastboot utilities

-adb with the phone in the booted OS,usb debug enabled,enter:
adb devices in a cmd window

-fastboot with phone in fastboot,enter:
fastboot devices in cmd window

in either case,a properly connected phone with working drivers installed should report back the phones serial number.
Click to expand...

id rather not use a VM to mod potentially delicate parts of the phone,things dont always work they way theyre supposed to :eek:

once you get a response from fastboot devices then enter this command,and post its resulting output here:

fastboot getvar all

on to your prollem,it definately sounds like youve got some bad partitions,or some sort of hardware failure. try installing recovery again from a real PC,and not from the VM. if you can access it,thats awsome! if not,we can try launching recovery directly in to phone memory. the command is very similar:

fastboot boot recoveryimagename.img

i.e.,if youre recovery image is just named "recovery",then:
fastboot boot recovery.img

hopefully this will result in your recovery menu onscreen after the splash. if the phone hangs,or bootloops from this command,go ahead and try adb devices after a couple minutes.

if it doesnt work the first time,feel free to try it a few times,and with different recovery images. you can also try clockwork and Amon_Ra(tho i dont have links handy... if anyone does feel free to throw them up)

if was can get a recovery running,we can use adb to lower your main version so that we can run a lower build number ruu. if you simply have damaged partitions,then this should work,and the ruu will repair them,restoring the phone to normal operating status.

just holler if you have any questions :)
 
as an afterthot,if you have installed the entire sdk,make sure you were in the directory that contains the fastboot utility. alot of folks running the full sdk dump all the "platform tools" into the "tools" folder to eliminate the need to change back and forth to different directories
 
scotty85 said:
once you get a response from fastboot devices then enter this command,and post its resulting output here:

fastboot getvar all
Click to expand...

C:\sdk-tools>fastboot getvar all
getvar:all FAILED (command write failed (Unknown error))
finished. total time: 0.581s​

scotty85 said:
on to your prollem,it definately sounds like youve got some bad partitions,or some sort of hardware failure. try installing recovery again from a real PC,and not from the VM. if you can access it,thats awsome! if not,we can try launching recovery directly in to phone memory. the command is very similar:

fastboot boot recoveryimagename.img

i.e.,if youre recovery image is just named "recovery",then:
fastboot boot recovery.img

hopefully this will result in your recovery menu onscreen after the splash. if the phone hangs,or bootloops from this command,go ahead and try adb devices after a couple minutes.
Click to expand...

Both of these did the progress bar on the phone, and looked OK in the cmd window, but both continued to bootloop.

C:\sdk-tools>fastboot boot recovery.img
downloading 'boot.img'... OKAY [ 3.947s]
booting... OKAY [ 0.125s]
finished. total time: 4.072s​

C:\sdk-tools>fastboot boot recovery-clockwork-touch-5.8.0.1-supersonic.img
downloading 'boot.img'... OKAY [ 1.726s]
booting... OKAY [ 0.004s]
finished. total time: 1.731s​

This one made it hang on the white htc screen:

C:\sdk-tools>fastboot boot twrp-1.0.3-modified.img
downloading 'boot.img'... OKAY [ 2.868s]
booting... OKAY [ 0.004s]
finished. total time: 2.873s​

adb doesn't even see the phone.

C:\sdk-tools>adb devices
List of devices attached​

Argh..

Dave
 
well my friend, i think your phone is toast. adb will not work because you do not have a custom recovery.

you can't even get a getvar to print out. this to me seems like a hardware failure somewhere. i wish i had better news.
 
You must log in or register to reply here.
Back
Top Bottom