I hate having to post this here, but I'm really at a dead end troubleshooting.
My third time rooting an EVO (2nd time with the current Auto-Root method) went a bit south and I wound up with somewhat of a brick, which I've been able to nurse slowly back to health. Unfortunately, I'm left with a seemingly healthy phone that consistently reboots about 30 seconds after the stock ROM loads. I've seen reboots like this on the EVO previously, once when I restored a Titanium Backup made on an AOSP ROM onto a Sense ROM and once when I flashed a radio/PRI update with an incompatible kernel.
This particular phone was brand new in-the-box and I didn't do anything to it outside of the failed root attempt.
The bootloader can see and read from the SD card as I am able to flash PC36IMG files - I can also connect to and run the RUU utility while in FASTBOOT USB mode. I cannot however connect via ADB, as I keep getting a "error: device not found" message when I run the "adb shell" command.
Here is my bootloader info:
SUPERSONIC EVT3 SHIP S-ON
HBOOT 2.10.0001
MICROP-041f
TOUCH PANEL-AMTEL224_16ab
RADIO-2.15.00.11.19
Oct 15 2010,12:07:00
I have verified the following information during the short time my phone is actually booted up (these are the same settings I had out of the box, before starting the rooting process):
Kernel: 2.6.32.17-gee557fd
Build Number: 3.70.651.1 CL294884
Software: 3.70.651.1
PRI: 1.90_003
PRL: 60677
I do not have a custom recovery loaded, if I select Recovery from the bootloader menu it will give me the EVO/red exclamation point message - I can then hit volume up + Power and it will take me to the default recovery so I can wipe data/cache and flash update.zip files. I have wiped data and cache from this stock recovery many times, as well as Clear Data from the HBOOT.
I have run the RUU successfully a couple of times and I still get consistent reboots from the stock ROM. I have also flashed the PC36IMG made from the 3.70.651.1 OTA with the same result.
Is there anything else that could be causing some kind of software conflict and thus the reboots?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
First, I recommend that you attempt to re-flash your HBOOT. You can download HBOOT v2.10.0001 from http://forum.xda-developers.com/showthread.php?t=715485
After that, I recommend that you re-root your device using unrevoked. It's quick and simple and you can find the information from http://unrevoked.com/#evo
Afterwards, I recommend that you flash amon RA v2.3 over the ClockWorkMod that unrevoked will put on your device. You can get amon RA v2.3 from http://forum.xda-developers.com/showthread.php?t=705026
Now attempt to flash a rooted ODEXED version of the stock HTC rom. You can get it from http://forum.xda-developers.com/showthread.php?t=874251
Hopefully, these steps will help solve your problem with your rebooting. Let us know if you were successful or not. Have a great weekend.
Related
hello everyone
i have a problem with entering to the recovery via Rom manager
i have a desire with slcd screen
i rooted the phone with unrevoked with custom img:
recovery-clockwork-2.5.0.1-bravo-slcd
when it get to the recovery the root process stop and it seems fine...
i can go to nandroid and back up... i have full access to sd card
but when i try to get to the recovery again it put this massge:
Clockworkmod recovery v2.5.0.1
Finding update package...
Opening update packge...
Verifiying update packge....
E:failed t oseek in /cache/update.zip (Invaild argument)
E:signature verification failed
Installation aborted.
still, i can flash zip files and reboot the phone and all that
but im affried the root process dident go well....
anyone know how to slove this problem ???
i understood from the manual that the update.zip sppouse to be in the img file (thats what i saw on youtube)...
plz help..
ty.
Have you tried to re-root the phone?
If you rooted using unrevoked, just hold vol down and power when the device is off, and choose recovery from the menu, rom manager uses a fake flash method and isnt needed if you have a custom recovery installed
Sent from my HTC Desire using Tapatalk
well thats the problem i cant go to recovery via hboot only via rom manager
i used this guide:
http://forum.xda-developers.com/showthread.php?t=748618
i rooted the phone somthing like 10 times !
i think its a problem with the slcd screen root....
anyone encounter this problem ????
btw i have hboot 0.83.0001
help!!!!
plz.
i noticed you quoted "Clockworkmod recovery v2.5.0.1".
is this correct?
this seems like an old version - have you tried 2.5.0.7? i have used this with no problems.
yea its correct thats what i got from the guide for the slcd rood on the unrevoked way
do i need to root it again with an newer version of the custom img on the unrevoked
or just try to flash a zip file from the recovery ?
btw where can i get it ? can u post a link plz ?
thnx
Download amon-ra recovery, can be found in the android development section. Then boot up your phone and load unrevoked. Within unrevoked select custom recovery and select amon ra. Problems solved
/edit link to amon ra http://forum.xda-developers.com/showpost.php?p=9207011&postcount=1
Works! thnx man
with amon-ra
i dident try the clockworkmod 2.5.0.7 because i dident find an active link to download from....
the only thing that sucks is that i cant use the Vol +/- to switch options only the trackball.
but thats another problem....
2.5.1.8 is actually the latest ClockworkMod Recovery. Here is the latest update, I believe it was updated early last month. I know you now have Amon-RA, but I'll put it here for anyone else who may happen to stumble across this thread looking for help.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hello, I tried today to s-off my desire but failed so i gave up but ended up with the usb-brick issue, no problems here, lots of tutorials, but I accidentally updated my phone OTA from HTC and now I don't have amon-ra recovery anymore, only the android recovery which needs signed packages. I do have the SU app installed, so I guess my phone is still rooted, but I am unable to install a recovery in order to unbrick my phone. The only thing that is working is "fastboot", but can't flash a new rom, can't flash a new recovery.
Any ideas? I really don't want to sent my phone to a service...
LE: If I try to install any app from any source, including Market, my phone restarts, fast restarts actually...
tried unrevoked? this installs clockwork recovery mod.
or android flasher -attched
doesnt your phone needs to be ON with unrevoked? from there you must plug it in whith unrevoked opened on your PC.
But you can always try. I highly doubt your phone is unfixable, itll be allright.
Tried to re-root my phone but because my usb connection doesn't work anymore, the unrevoked program doesn't "see" my phone. The only thing that i need, in my opinion is an root explorer packed as a signed zip that the original android recovery can flash and i may be able to regain usb functionality.
you should try a differnt PC and do the process. I had a similar issue sometime back and when I changed the PC i was working on it worked.
That doesn't make much sense because the problem is in my phone, not in my computer...
Latest update: I prepared my phone for service, managed to flash a shipped rom without root, so there is no sign on it that I rooted it or flashed another custom rom/recovery. Still can't access the phone via usb so unrevoked still not a solution. Any new ideas before I say bye-bye to my Desire ?
HyperL said:
That doesn't make much sense because the problem is in my phone, not in my computer...
Latest update: I prepared my phone for service, managed to flash a shipped rom without root, so there is no sign on it that I rooted it or flashed another custom rom/recovery. Still can't access the phone via usb so unrevoked still not a solution. Any new ideas before I say bye-bye to my Desire ?
Click to expand...
Click to collapse
You should try this :
- usb debugging mode ON
- install VWM ( virtual ware machine ) and boot with the .img of the hboot needed at http://alpharev.nl
- the device should be plugged and the aplharev hboot pushed with the last clockworkworld recovery
if not working, unfortunately not so many solutions but you still can try to unbrick the usb and then you will "unrevoked" easily your desire !
Take a look on alpharev developers chat for bricked phones
Hope it helps
My last piece of work
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Nothing posted on xda or other android forums worked so today I handed my Desire to my carrier because I still have warranty . I hope they don't find any of my modifications , I did un-rooted it so it should be stock enough for them
Something I do not understand :
Last time I USB bricked my phone, I went to hboot, then fastboot, and entered the fastboot commande :
Code:
fastboot oem enableqxdm 0
as stated in many tuto.
This re-enables the USB, and then, you may again flash any recovery via unrevoked.
Actually that command re-enables the micro-sd controller, not the usb.
Hi guys, i have decided to get my desire back to stock and i have the asian RUU that i download from xda.
I am rooted with s-off and amonra recovery. Im on the Stock rooted ROM w/ A2SD.
1) Went to fastboot and into fastboot_USB mode and then ran RUU from PC
2) at arnd 59% it gave me an error error 110: File Open Error (is this a RUU corrupted of what?)
3) Then it went into a half-bricked mode where theres 4 exclaimation marks on the 4 corners
lucky i managed to recover into last working state again. (adb coundnt detect my phone; it works with my S2)
I went on to format phone from Settings, but my apps, etc are still there.
Can anyone tell me what to do and where to start?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
What hboot partition have you.got?
Sent from my HTC Desire using xda premium
i didnt touch the partition table. i just ran alpharev s-off only.
just tried this downgrading tool.
http://forum.xda-developers.com/showthread.php?t=768256
how it stucks at the green HTC logo w/ white background.
Tried to run a RUU but error 170 USB error
EDIT: Somehow everything went smoothly on my laptop and im back to stock. but i gotta un s-off.
S-off:
Ran the Same RUU but now error 131: Customer ID error, however when i went into bootloader, its already S-off
ok just a summary of what happened and issues i faced and resolved for future references
Im coming from stock rooted ROM w/ app2sd, root, s-off, amonra recovery and i wanna go back to stock.
*I lost my gold card as my sd card was corrupted.
1) Ran the downgrade tool from this thread: http://forum.xda-developers.com/showthread.php?t=768256 (luckily i passed w/o the goldcard)
2) When booting up, i was stucked at the green HTC logo
3) Ran the RUU file: RUU_Bravo_Froyo_HTC_WWE_2.29.405.5_Radio_32.49.00. 32U_5.11.05.27_release
from http://forum.xda-developers.com/showthread.php?t=695667
4) At this stage, ROM, recovery is back to Stock. Except s-off.
5) Using help from this link : http://forum.xda-developers.com/showthread.php?t=1275632
flashed the bravo_downgrader and HBOOT became alpharev unlock and I ran the same RUU
6) I used the same RUU but it says Customer ID error but when i checked my bootload, i was alrdy S-on
Hello devs,
my HTC Desire Z broke over night.
The phone still works, boots and runs as expected, but the Screen is dead, although the Touchscreen is still working (PatternUnlock working and so on).
I want to send it in for warranty repair, but I still have flashed Clockwork Recovery with S-OFFand Cyanogen 9 RC1 and root.
That's the reason why I want to flash the original image PC10IMG via fastboot.
How can I access the bootloader and boot into fastboot?
I tried:
Volume Down and waiting long enough (~45s) and then pressed Power to access Fastboot, but it doesn't work.
(I think the clockwork menu is presented instead of the android bootloader menu, which I don't know by minds).
Debug mode is off on the phone, so "adb reboot fastboot" does not work
Can someone with a Desire Z and Clockwork Recovery flashed give an step-by-step instruction how to boot into fastboot if your screen is dead?
Thank you in advance.
me|kor
Here you go, perfect guide for you: [GUIDE] Returning to stock, unroot. Also with broken screen/digitizer
-Nipqer
Nipqer said:
Here you go, perfect guide for you: [GUIDE] Returning to stock, unroot. Also with broken screen/digitizer
-Nipqer
Click to expand...
Click to collapse
That's what I tried already, but sadly it doesn't work due to Clockwork Recovery I think.
My device reboots when I press power after one minute, which makes sense if this screenshot represents my menu.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
In the ClockworkMod in this screenshot is fastboot not listed and I couldn't find a screenshot of the advanced menu nor the complete menu structure where fastboot was listed.
I'm using the most recent version of Clockwork Rom Manager and Recovery Image
Should be 5.0.2.7 I think.
You don't need to use recovery at all with my guide.
You can go straight to fastboot mode, from powered down, by holding the Trackpad while powering on, then you can use your computer to talk to it and send a rom to flash.
-Nipqer
Nipqer said:
You don't need to use recovery at all with my guide.
You can go straight to fastboot mode, from powered down, by holding the Trackpad while powering on, then you can use your computer to talk to it and send a rom to flash.
-Nipqer
Click to expand...
Click to collapse
Thank you very much I didn't knew the Trackpad shortcut and didn't find / oversee it in your guide.
That was the one I needed.
You made my day!
:fingers-crossed:
Yeah I don't think I mentioned it in my guide, as the guide is also written for Ace/Glacier, which don't have trackpads.
I'm glad you managed to get it sorted
-Nipqer
Hello
So here is the situation. A friend of mine recently dug up his 5 year old HTC One M8 and he would like to access the data saved on that device.
However, when powering on, the device quickly boots into fastboot. Upon choosing the "hboot" option, the phone quickly boots into yet another instance of fastboot, this time however the option to boot into recovery has appeared. Unfortunately however, when choosing to boot into recovery, the phone just simply returns to fastboot.
What is curious about this is that he never really modified the phone at all or the recovery (stock recovery should be installed).
Therefore the bootloader is locked . Interestingly, fastboot displays the following information when booting:
Code:
*** Software status: Modified ***
** LOCKED ***
** Security Warning ***
M8_UL PVT SHIP S-ON
HBOOT- 3.19.0.0000
RADIO-1.29.214500021.12G
OpenDSP-v 51.2.2-00593-M8974_FO.1015
OS-6.12.401.4
eMMC-boot 2048MB
Dec 17 2015,14:15:48.0
I am mostly at a loss here.. Do you people maybe have an idea on how to fix this issue?
Supposedly the phone hasn't been touched for 5 years now and even before that long hiatus, essential files haven't been touched. The phone is locked and has never been rooted.. Apart from it sitting in a drawer for 5 years, there should be nothing unusual about it.
Could the flash memory have degraded over that long time? If so, that would be an absolute first for me.
Do you guys have any solutions on how to access the file system somehow?
Some pictures of the boot process:
Fastboot shortly after powering on the device:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
After choosing "HBOOT" from the previous screen, this comes up, adding the option to boot into recovery (which does not work):
Curious: After pressing the power button to turn on the device, this text appears for a split second:
"Software Modified" on a device that has never been rooted/modified typically means the OS has been corrupted. This is consistent with the fact that the phone will not boot to OS. We've seen this on both devices that are used on a regular basis, as well as some sitting idle for a long time. The storage that holds the OS is not completely foolproof.
Unfortunately, recovering data from such a device (can't boot to OS, never modified - no custom recovery) is unlikely, and probably impossible. Methods to restore the OS will wipe the data on the phone. And the data is not accessible without a working OS.
Also, stock recovery isn't terribly useful. So the absence of stock recovery means very little either way.