Develop Bugs

Consistent reboots / USB and adb acting up ... when rooting goes bad

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.

[Q] Failed to unroot, un S-off my desire

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

"Failed to boot to recovery mode..." - Suggestions?

Hi Everyone!
It's been a long time since I posted here. Just got an M9 and having a few issues, It's obviously been flashed with custom ROMs before, is S-OFF and unlocked.
Unfortunately I can't get into the recovery, Ideally I'd like to return to a close to stock ROM. It throws up this message when I try to get in:
"Failed to boot to recovery mode... This build is for development purposes only..."
Download mode says "SD NOT MOUNTED" at the bottom (I don't know if that's normal)
I've tried to install various versions of TWRP via fastboot to no avail!
I've flashed lots of ROMs to my M8 before with no problems, but just having trouble as I don't know what's been changed on this phone! Any help much appreciated!
Few more details pulled from download mode:
htc_himauhl PVT S-OFF
CID-ORANG001
LK-1.0.0.0000
firmware version: 0x7
{
"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"
}

Solved. Just had to flash TWRP, then go straight to recovery before getting to OS by holding UP/DOWN as it rebooted. Tiny little quirk!

what do you meen had to flash

I have a problem like that but I can't boot to download mode either. I get the message "failed to boot to download mode" then at the bottom "this build is for development purposes only ...". Please help!

Redfox511 said:
I have a problem like that but I can't boot to download mode either. I get the message "failed to boot to download mode" then at the bottom "this build is for development purposes only ...". Please help!
Click to expand...
Click to collapse
Flash Twrp 2.9.0.1 "if you're rooting it".
Beamed in by telepathy.

shivadow said:
Flash Twrp 2.9.0.1 "if you're rooting it".
Beamed in by telepathy.
Click to expand...
Click to collapse
The thing is I didn't have usb debugging enabled when the device crashed and started a boot loop. Now I'm stuck in the bootloader and I don't know what to do? Any advice?

Redfox511 said:
The thing is I didn't have usb debugging enabled when the device crashed and started a boot loop. Now I'm stuck in the bootloader and I don't know what to do? Any advice?
Click to expand...
Click to collapse
In bootloader mod you have to use fastboot not adb.
Adb is only for OS or TWRP.
So you can try to flash recovery in bootloader with
fastboot flash recovery filename.img
then try to boot from recovery to download mode

airplane mode does not turn off after phone drops

airplane mode does not turn off after phone drops
android 6.0.1 stock rom , not rooted ... all of them default
{
"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"
}

It's likely a hardware issue, if it occurred right after the phone dropped.
You can try factory reset (wipe data). Or you can try RUU, if your version M8 has an RUU. But if it is still stuck in airplane mode after that, it's probably hardware damage.

redpoint73 said:
It's likely a hardware issue, if it occurred right after the phone dropped.
You can try factory reset (wipe data). Or you can try RUU, if your version M8 has an RUU. But if it is still stuck in airplane mode after that, it's probably hardware damage.
Click to expand...
Click to collapse
im try factory reset but can not fix.
haw can i flash rru files? (needs root or unlockbootloader?)

cervantes said:
haw can i flash rru files? (needs root or unlockbootloader?)
Click to expand...
Click to collapse
Neither. In fact, unlocked bootloader will prevent RUU for installing in most cases.
RUU will work fine on a stock (unmodified) device. But not all M8 versions have RUU. I'll need more info to try to find an RUU for you. If you know how, connect phone to PC, reboot to bootloader-fastboot mode, and do command: fastboot getvar all
Post the results (delete IMEI and serial number before posting).
If you don't know how to use fastboot, then reboot to bootloader and tell me what it says for:
Whether it says LOCKED, RELOCKED or UNLOCKED (it will say one of those near the top of the bootloader screen)
Hboot number
Radio baseband number
OS number
S-on or S-off (it will say one of the other)

redpoint73 said:
Neither. In fact, unlocked bootloader will prevent RUU for installing in most cases.
RUU will work fine on a stock (unmodified) device. But not all M8 versions have RUU. I'll need more info to try to find an RUU for you. If you know how, connect phone to PC, reboot to bootloader-fastboot mode, and do command: fastboot getvar all
Post the results (delete IMEI and serial number before posting).
If you don't know how to use fastboot, then reboot to bootloader and tell me what it says for:
Whether it says LOCKED, RELOCKED or UNLOCKED (it will say one of those near the top of the bootloader screen)
Hboot number
Radio baseband number
OS number
S-on or S-off (it will say one of the other)
Click to expand...
Click to collapse
sending phone repair service , service say need to change motherboard

Data recovery attempt off of 5 year old phone

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.