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.
Related
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.
I rooted and did s-off and installed a custom ROM about a year and a half ago when I first got my phone.
Last night I obviously missed a step when I tried to update my ROM to Cyanogenmod.
Stuck in Hboot loop. My phone is recognizable in adb when it's stuck at the white HTC screen. I can power into fastboot but the volume buttons don't work so I can't access any of those options.
When I type "adb devices: it says: HT0AMRV07945
When I type "fastboot devices" nothing is found
Here are some screenshots:
No buttons work on this screen so I have to go into Hboot:
{
"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"
}
I mistakenly hit up instead of down and said yes to updating:
This is the only screen where my volume and power buttons still work.
Looks like the prob is that you have 2 update.zip's find the duplicate and rename reflash rom after wiping to ensure a good flash. That should work I had same prob.
Sent from my HTC Vision using XDA
I can find the duplicate by removing the card from my phone and inserting it into my PC. After that I don't know how to wipe the phone and load a ROM from the hboot screen.
Or are you saying it should boot normally after I rename the duplicate update.zip?
Hmm... is there anything named PC10IMG.zip on your sd card?
Go into recovery
1) Remove all ZIP files from your SD card (only the files that are NOT contained in any folder). So your phone will not try to install anything when in HBOOT.
2) When adb is working you can boot into recovery using the following command:
adb reboot recovery
3) From recovery you can do:
Wipe cache partition
Install a new ROM
Install a new radio
4) While in the white HTC screen you can get some log messages from the phone using adb. Some examples:
adb logcat : Shows logcat information (phone log)
adb logcat *:V : Shows verbose logcat info
adb shell dmesg : Shows kernel messages
adb shell ps : Shows all running processes of your phone
5) When still stuck you can write me a private message at XDA
Best regards,
Catherall
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
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
I wanted to downgrade to 5.0 to unlock the bootloader and install a custom recovery and ROM. Used the official FW from the Asus page, installed it from within the OS (android MM stock). It all went as expected until at the end of the install it rebooted and got into the bootloader screen instead of booting normally. It won't go into recovery.
Phone will NOT turn on with power button + volume down button, not ever.
Power button + volume up does nothing, it turns the phone on just like the power button alone would do.
Once in the stock bootloader if I select [recovery mode] it will simply reset and go back to where I was. I never get the dead android error, it just go back to the bootloader select menu
I get this screen
{
"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 can I do? all the tutorials I seen either asume I can get into recovery or use power button + volume down button which in my case doesn't works
Find images of system, ifwi, recovery etc. and fastboot flash them. you can try first with recovery only. the adb command will be "fastboot flash recovery recovery.
img" just search the forum plenty of guides here
kojata said:
Find images of system, ifwi, recovery etc. and fastboot flash them. you can try first with recovery only. the adb command will be "fastboot flash recovery recovery.
img" just search the forum plenty of guides here
Click to expand...
Click to collapse
I looked at the guides, most require recovery on the phone to work (it doesnt here, just reboots back into the bootloader) and for some reason adb can't find this phone, tried on 2 different computers
BTW I tried with another android phone and adb worked just fine
How is it possible no computer can even tell this phone is connected at all?