My stock, untouched, unrooted HTC One S has randomly got itself stuck in a boot loop. It goes through the 'quietly brilliant' screen, onto the 'htc one' screen and then it restarts. I am desperately trying to recover my files and photos from the memory before I try a Factory Reset, because while these.threads mention ways to recover deleted files, these.posts from the OP suggest that it doesn't work for files lost to a factory reset.
Things I have tried:
Selecting the 'Recovery' option from the bootloader shows a black screen with green arrows on it for about 10s, but then the green arrows change to a red triangle with a '!' in it and it eventually reboots into the same loop.
Connecting to the phone using ADB over USB fails as the device is unseen. I believe this is failing because the phone is locked, and/or does not have USB debugging enabled on it??
The Fastboot tool does seem to be able to see my device, but from what I can tell fastboot is more used for flashing ROMs, and I'm not really trying to do this.
So my questions are:
Does anyone know of a way to access the files/folders on my device in its current state?
Since the SD card on the One S is fake, is there a way for me to fix the section of memory that boots the device, whilst leaving the storage bit untouched?
Any advice is greatly appreciated as I've got a lot of personal photos and videos on the device. I didn't think to back them up because on previous phones they've always been safely accessible on a physical card =(
Thanks in advance,
Tom
Hi Tom,
I'm not familiar with stock recovery, as I unlocked and rooted my device almost immediately. So I'm not really sure, but here are some suggestions anyway:
Try and see if vol-up or -down gets you in a state where you can get adb when booted into stock recovery.
You can also try and fastboot boot directly into a custom recovery image, but that may not be possible with a locked bootloader.
If not, I'm afraid you're SOL, since unlocking wipes the storage.
-Jobo
I cant think of any way to recover from this situation except reflash ruu but then your sd card is wiped. Did you not activate dropbox?
What about vol down and power, rebooting into HBOOT? Then can't you dd if sdcard of?
Or fastboot pull /sdcard/ C:\Users\User\Desktop\sdcard
Sent from my locked, tampered ville
I'm in the same situation, it happened on Thursday night (the 8th), when did your's start? I'm struggling to find a solution for this as well. The closest I've got to anything is that on Linux Ubuntu, when I book the phone connected to my laptop one the second (out of three) boot screens it recognizes the device as an inaccessible HTC Phone, disappearing then once it reboots. Nothing is accessible.
Thanks all for your replies. I'll try to respond in order...
@Jobo - Sorry to be a noob, but how do I boot into stock recovery? The Recovery option from the HBOOT screen fails like I said above. Regarding fastboot, does it let you boot into an image that is stored on your PC? Is that how it works? Obviously I'm not going to be able to get an image onto the phone without most likely wiping everything. FYI, my HBOOT screen says ***LOCKED*** on it, but the phone was bought outright so it is not locked by a provider.
@gazknight - I saw Dropbox more as a solution for the One S's limited storage capacity. Since I didn't expect to go over the fixed limit, I didn't really think I'd need the service. Backing up for security's sake would obviously have been a good idea but then I've never had a phone break quite so suddenly as this so I didn't think to do that.
@usaff22 - I can get into HBOOT successfully, but in this state (or whilst in the FASTBOOT menu) my SD card is not mounted and not visible over USB. Does the DD command require a mounted drive? Also, is it a LINUX command? I'm running Windows on my laptop, but with the Android SDK installed. I tried FASTBOOT PULL, but that's not a recognised command when I try it; listing the commands available only shows options like 'flash', 'erase', 'format', 'boot' etc.
@nickrr1 - Mine went bad just a few days before yours I think. I see what you mean, I think; on Windows, when I leave the phone connected via USB for the duration of its boot loop, a mounted drive does appear for just a few seconds, but if I click it it says "Please insert a disk" and then it's gone within a few seconds.
tommy_g003 said:
Thanks all for your replies. I'll try to respond in order...
@Jobo - Sorry to be a noob, but how do I boot into stock recovery? The Recovery option from the HBOOT screen fails like I said above. Regarding fastboot, does it let you boot into an image that is stored on your PC? Is that how it works? Obviously I'm not going to be able to get an image onto the phone without most likely wiping everything. FYI, my HBOOT screen says ***LOCKED*** on it, but the phone was bought outright so it is not locked by a provider.
@usaff22 - I can get into HBOOT successfully, but in this state (or whilst in the FASTBOOT menu) my SD card is not mounted and not visible over USB. Does the DD command require a mounted drive? Also, is it a LINUX command? I'm running Windows on my laptop, but with the Android SDK installed. I tried FASTBOOT PULL, but that's not a recognised command when I try it; listing the commands available only shows options like 'flash', 'erase', 'format', 'boot' etc.
Click to expand...
Click to collapse
Locked means the bootloader being locked/unlocked, not the SIM's state.
dd if of should work after typing adb shell. Have you tried flashing a recovery in fastboot? I need the sdcard partition number though, for the dd to work.
It is fastboot flash recovery recovery.img (recovery should be named recovery.img and placed in the fastboot folder)
Edit: tried this?
http://forum.xda-developers.com/showthread.php?p=25557817#post25850720
tommy_g003 said:
@Jobo - Sorry to be a noob, but how do I boot into stock recovery? The Recovery option from the HBOOT screen fails like I said above. Regarding fastboot, does it let you boot into an image that is stored on your PC? Is that how it works? Obviously I'm not going to be able to get an image onto the phone without most likely wiping everything. FYI, my HBOOT screen says ***LOCKED*** on it, but the phone was bought outright so it is not locked by a provider.
Click to expand...
Click to collapse
As I said, I'm not familiar with stock recovery and I don't have it installed.
After you select recovery from hboot, and before it reboots again, does it respond to the volume buttons?
Yes, you can fastboot boot into a recovery image without copying the file to the device:
fastboot boot recovery-cwm-ville.img (substitute the actual file name of the recovery image. but im not sure whether this requires an unlocked bootloader.)
As usaff22 pointed out, **LOCKED** means bootloader locked, not provider SIM locked.
usaff22 said:
Have you tried flashing a recovery in fastboot? I need the sdcard partition number though, for the dd to work.
Click to expand...
Click to collapse
He can not flash recoveries since his bootloader is locked.
The sdcard partition is /dev/block/mmcblk0p36
EDIT: Here is another thought:
Have you tried booting into safe mode? (Power on the device, when on the boot splash hold vol-down and keep holding until you feel a long buzz or until you see 'safe mode' in the lower left corner of the screen.) If not, you can try to fastboot erase cache and even fastboot erase userdata. This should not erase your sdcard, just your apps and app data, but it might get your device back into bootable state, if the bootloop was caused by a user app or some corrupted user data.
usaff22 said:
Edit: tried this?
http://forum.xda-developers.com/showthread.php?p=25557817#post25850720
Click to expand...
Click to collapse
That will erase the sdcard. The whole point of this thread is to save the sdcard contents.
touch of jobo said:
That will erase the sdcard. The whole point of this thread is to save the sdcard contents.
Click to expand...
Click to collapse
My bad. Sorry.
I wonder if the following will work:
dd if=/dev/block/mmcblk0p36 of=C:\Users\UserAccount\Desktop\
Have you tried the wipe user data option in HBOOT? Not clear storage, if I remember correctly there is another option to wipe user data.
usaff22 said:
I wonder if the following will work:
dd if=/dev/block/mmcblk0p36 of=C:\Users\UserAccount\Desktop\
Click to expand...
Click to collapse
It will not. dd must be run on the device. What would work (on a linux host) is this:
(adb shell dd if=/dev/block/mmc0p36) > ~/rescued_sdcard.img
But still .. you would need to be able to get an adb shell first.
Thanks so much for your time and suggestions on this. I've tried a few things now, but to no avail so far...
ADB - Still no luck with this. I think this is expected because of the state my phone is in... I have read that it needs to be actually booted up, and with USB Debugging enabled for it to work.
Safe Mode - No joy. I can use a long press of Volume Down to get a long buzz, but then it still reboots a few seconds later.
Recovery Boot - Selecting Recovery from the HBOOT menu and then pressing/holding the Volume Up and Down buttons does not seem to have any effect. I'm not sure exactly when I should be pressing them, but I have tried a few different methods and it always ends up on the same red triangle screen.
Fastboot - This does seem to be connecting, but because the damn thing is locked I'm getting access errors when I try to do anything useful...
fastboot erase cache works, but then rebooting normally or with safe mode both fail as usual.
fastboot erase userdata fails with a "remote: not allowed" error.
fastboot boot ville_recovery_signed.img posts success at reading the image file but then it fails at the 'booting' stage with the same remote access error.
HBOOT wipe - My only two options relating to data at the top level menu are 'FACTORY RESET' and 'CLEAR STORAGE'. I have not tried selecting either of these, so I am not sure of any deeper options, but I did research these options and it does seem like they will likely wipe my SD data. I am wondering though if maybe the FACTORY RESET might save my data on the SD partition. This is the opposite of what an HTC support guy told me though.
Also I found a report of another poor guy having the same issue this week. Add 'www' to the following: peoplesrepublicofcork.com/forums/showthread.php?p=4528285 (soz, I can't post links yet)
>_< Why didn't I just back up my photos & videos!?!
UPDATE:
So after a bit of back-and-forth with HTC's tech support over the last few days, I got some instructions from them to use the Factory Reset...
HTC: "...I would like you to perform a factory reset of the phone. This will erase all data saved to the memory of the phone, but will not clear the phone storage..."
ME: "...Will the Factory Reset really spare the 'storage' as suggested, or is this wording aimed at phones with a physical SD card?..."
HTC: "On the HTC One S there are 2 different types of storage. The phone memory and the internal storage of the phone. A factory reset will erase all data from the memory of the phone, but leave the phone storage intact, it is easiest if you think of phone storage as an internal SD Card. There are 2 settings on the phone which reflect this, a factory reset and the option to clear storage. If you choose a factory reset of the phone your internal storage should remain intact and your photos will not be wiped from the device."
So I did the Reset, and the phone now boots, but I've lost all my photos and videos. They don't show up on the phone; they don't show up on a mounted drive; they don't even show up using typical 'undelete' software on the mounted drive. Thanks for the great advice, HTC!
Now my last option is to follow this thread, but this will involve me knowingly voiding my warranty on a piece of hardware which I already know is potentially unreliable.
So I think I'm just going to give up....
What a drama...
@tommy_g003
How did things work out? Did you manage to recover your data after the factory reset?
I have exactly the same bootloop problem you described and I'm beyond despair. Over the past couple of weeks I've used an app on my phone (PCM recorder) to record interviews for my master thesis. I've backed up several of them, but not all... I have gone above and beyond to get these interviews and there is no way I'll be able to redo them. I really truly cannot lose these recordings!
I think at this point I'd rather even sacrifice my phone by physically removing the storage from it and somehow recovering the data from it, but I have no clue whether this is even possible.
I read a thread (androidforums. com/htc-wildfire-s/560123-unrooted-wildfire-s-bootloop-help. html - remove spaces in url) that describes how to re-flash the stock ROM when not rooted. Presumably this can fix the bootloop, while not deleting the internal storage. Does anybody know if something like this exists and works for the One S as well?
jazzmijnhv said:
I read a thread (androidforums. com/htc-wildfire-s/560123-unrooted-wildfire-s-bootloop-help. html - remove spaces in url) that describes how to re-flash the stock ROM when not rooted. Presumably this can fix the bootloop, while not deleting the internal storage. Does anybody know if something like this exists and works for the One S as well?
Click to expand...
Click to collapse
Running a RUU will erase your sdcard. So will unlocking your bootloader. Don't do it.
You can try booting up in Safe Mode (power down, boot back up and as soon as you see your boot splash (quietly brilliant) hold vol-down until youre fully booted.
You can try erasing your data and cache partitions in fastboot, and then booting back up.
Both of these suggestions were already offered in this thread so you probably tried already, but just to make sure.
Finally, you can look at the unbricking tutorial in the development forum, and see if the same method can be used to extract partition #36. Personally I've never had to unbrick/downgrade, but maybe someone familiar with the process can weigh in. If this is possible, you can then mount it and extract the files from it. Since you're not unlocked and you can't unlock (without losing your data) you'll have to be able to get into download mode by powering up holding vol-up.
I haven't really got any further with this. My One S now works, but I'm avoiding using it for now until I've imaged & extracted its storage for a salvage op (see the link in my post above) and I'm too lazy to go about rooting etc. right now in order to do this.
I had the exact same issue as you, multiple times now.
First time I did a factory reset and everything was erased (pics, videos, downloaded apps, etc).
After that I'm just doing clear storage - which removes all the apps that were installed and all configuration, but my photos, videos, and all other documents remain intact.
Fix bootloop without losing data
After my phone shut down because of the % of the battery, it was low, phone got stucked on samsung logo after power up. I dont want to lose data on my phone, how can i recover data first and then factory reset it, or to access device without losing data, is it possible? If its not, ill do the factory reset....
Related
Yesterday my phone started acting up. All running process crashed and not many was able to start. I had to constantly click "force close". I think this started after I installed the Google+ app, but not sure.
I have tried uninstalling all unnecessary apps, without luck. I then tried wiping to factory settings by using the Android menu, but without any changing. I then tried by holding vol+ and power, going in to recovery and wiping both to factory and app cache. This doesn't change anything either. By googling I can see some suggests to hold vol- and power, to get to a another wiping-functionality but this just boots my Nexus S to normal state - no menu appears.
Has anybody an idea of what I can do?
Edit: more info; if I click "Report" and investigate the message sent to Google, I see that error has something to do with SQLite-relatet classes. Which makes some sense, alot of my changes are reset each time the phone is rebooted. For instance did I miss a call a couple of hours before the phone went crazy - this is shown at each boot in the notification area eventhough I clear the area and/or goes to missed call section
Factory reset via menu does delete all your "custom" apps, so I'd say it's not one of the existing apps causing problems.
The way you describe function after your factory reset sounds like factory reset didn't work properly.
If you feel safe I'd recommend rather flashing 2.3.4 again using either Odin or the OTA zip from Google (requires open bootloader).
I think you're right that factory reset doesn't do what is expected. Once I click it, the phone reboots and shows the Android guy next to an unwrapping package. This lasts only 2 seconds, then it reboots itself again and goes into normal phone mode (where all the app-crashing starts again).
I have not flashed or rooted my phone before, but I will consider this now since my NS is pretty much a brick. Thank you for your swiftly response.
Edit: Shouldn't I get a menu, when I push and hold vol- button, while turning on the device? Right now it just boot as normal.
Before you use odin....try going into rom manager a reflashing clockwork! Ive had that android dude on my screeen but reflashibg via rom manager always fixed it. Try that
Sent from my Nexus S using XDA Premium App
Wow my Nexus has totally shut me out.
I cannot use ClockworkMod unfortunately since I am not able to root my phone. It is not detectable via USA (when I use vol+/pwr and connect USB). I am unable to check the USB Debugging option on the phone. Each time I check it, go to home-screen and back to the menu, it has de-selected it again. Also I noticed when I read the info that is sent to Google for all those app-crashes I get, I see SQLiteException and error in an SQLite.java file. So it seems like some database layer is broken.
I read one could copy the ClockWork.img to my phone and use the standard recovery option to flash the img (I think). But when I go into the recovery menu, the file is gone. When I boot the phone again, it has deleted the .img file - eventhough if I copy it to several different folders, they are all gone :-(.
I feel pretty screwed at the moment. How can I else wipe all data?
I'd recommend to check if your device is correctly identified in windows. Missing USB drivers might cause problems. Get the latest drivers and a guide from here.
If you succeed booting into fastboot properly (vol up and power) you can follow this guide. Get the latest cwm recovery.img here.
Last option would be to boot into download mode (vol up + vol down + power + plugging in usb cable) and use Odin from samfirmware.com
--
All options require correctly working USB drivers.
I managed to unlock the bootloader, by quickly turning on USB-debugging (before any processes started to crash) and install the drivers from this post:
http://forum.xda-developers.com/showpost.php?p=6819751&postcount=4
A reboot later, I got this message:
"System UIDs Inconsistent
UIDs on the system are inconsistent, you need to wipe your data partition or your device will be unstable."
Right below was a button saying "Im feeling lucky" (??)
I installed ClockworkMod using fastboot and tried "Fixing permissions" with no luck. I will try some ROM later on, and hope it will bring my phone back
Normally this error happens when you have a faulty app ruining your system, formating/deleting whole sdcard does usually fix this.
rentaric said:
Normally this error happens when you have a faulty app ruining your system, formating/deleting whole sdcard does usually fix this.
Click to expand...
Click to collapse
I can safely mount USB-storage and format the whole bunch?
I been sweating over this stupid issue all day now, all I want is a fac-reset :´(
Edit: "format /sdcard" using CWM didn't do anything
DennisRP said:
I can safely mount USB-storage and format the whole bunch?
I been sweating over this stupid issue all day now, all I want is a fac-reset :´(
Edit: "format /sdcard" using CWM didn't do anything
Click to expand...
Click to collapse
See I'm no expert on this whole thing. At this point I'd just flash a whole new system via Odin. Prolly not the smartest or safest option, but that's what I'd do because I don't know better. If that wouldn't fix it either, I'd return the phone on warranty
I was looking at Odin from the start, since nothing else seemed to be working.
So right now I got started on Odin. Followed the .pdf steps and flashed the bootloader at first succesfully. I was asked to remove the battery and re-connect my NS. Began downloading "pda" and "phone", but at around 10% a big fat red "fail" message appeared and now I just see the Google-logo on startup. I still cant flash any roms via fastboot.
Im too tired too right now, been working with this for 14 hours straight. I will look at it tomorrow evening. Thanks for your help rentaric
Weird, you're not the first one who had trouble running Odin using their guide.
Overall it's pretty simple.
Enter download mode. Vol up vol down and power at the same time while plugging in the USB cable. Start Odin, should show a yellow colored box with a port number. Uncheck everything but reset timer and auto reboot. Unzip the correct zip file from samfirmware.com (check if you got i9020 or i9023 and get the universal Odin exe), apply file from the folder accordingly. Bootloader and bootloader. Phone and modem. Pda and pda. Csc can remain empty (will change carrier info in fastboot).
Double check md5 hash to avoid broken files.
Sent from my Nexus S using XDA App
rentaric said:
Weird, you're not the first one who had trouble running Odin using their guide.
Click to expand...
Click to collapse
Of course I did not go to bed, how should I be able to sleep with a broken phone .
The firmware suggested on samfirmware.com for my phone, was 2.3.3 and some other version (my phone was 2.3.4.2/GRJ22 or something similar, I suspect that might be the cause. Also I unchecked everything, that might also have been of importance). The flash will always fail when everything was downloaded - it then said something about "remote" and "Loke" and then fail. But as I mentioned, I had succesfully flashed boot.img (2.3.3) thus no boot occured now. I googled the correct bootloader, used fastboot and was booting succesfully again.
I began looking more into the sdcard, as error-messages was leading me this way. To compress 4 hours of investigations into a few lines, it seems as my PBA is malfunctioning as other xda-members have experinced. Only solution is sending the phone to Samsung for a PBA replacement. I purchased the phone in Bestbuy USA and the danish Samsung partners are not too joyfull about this - I will contact Samsung and hope they can help me.
I experinced the exact same thing as this poor guy - http://forum.xda-developers.com/showthread.php?t=993403
Every thing you try to do to /sdcard is worthless.
Formatting (USB/using CWM/using adb shell linux commands) says "Succes" but nothing happens.
Copying files says "Succes" but nothing happens. If I boot phone into CWM, mount usb and upload new rom/apk/whatever and try to do a "install update.zip" it fails with some mounting errors.
Im ready to go cry in a corner - I really want this to be fixable via software, but I probably have to realize that this is a hardware issue.
Apparently Samsung doesn't offer worldwide warranty for cellularphones :´(. God it sucks to pay repair-expenses on a 1 month old mobile.
I have followed all of the procedures to reload my phone stuch on the splash screen, but have had no luck. Before I dispose of the phone, as it is in mint condition, I want to be sure there is no other options to update / reformat the bootloader
1. I have loaded the image for 2.2.1 AND 2.3.4 MULTIPLE TIMES
2. I have cleared the Cache's and no change
3. status on bootloader shows
GLACIAER PVT SHIP S-ON
HBOOT-09.0006
MICROP-0429
RADIO-26.13.04.19_M
eMMC-BOOT
Jul 15 2011, 16:45:17
I guess the last hope since th reloading the original images did not work is to reload / format the bootloader using ADB, but I believe that I have the wrong HBoot.
Is the phone eMMC bad and the phone bricked or is there something else to try?
johnmbailey said:
I have followed all of the procedures to reload my phone stuch on the splash screen, but have had no luck. Before I dispose of the phone, as it is in mint condition, I want to be sure there is no other options to update / reformat the bootloader
1. I have loaded the image for 2.2.1 AND 2.3.4 MULTIPLE TIMES
2. I have cleared the Cache's and no change
3. status on bootloader shows
GLACIAER PVT SHIP S-ON
HBOOT-09.0006
MICROP-0429
RADIO-26.13.04.19_M
eMMC-BOOT
Jul 15 2011, 16:45:17
I guess the last hope since th reloading the original images did not work is to reload / format the bootloader using ADB, but I believe that I have the wrong HBoot.
Is the phone eMMC bad and the phone bricked or is there something else to try?
Click to expand...
Click to collapse
When you try to flash PDwhatever.IMG, what does it tell you?
Glacier locked at Mytouch logo, without image load errors
THEindian said:
When you try to flash PDwhatever.IMG, what does it tell you?
Click to expand...
Click to collapse
It does not give any errors after flashing to 2.3.4, as it loads, verifies, then asks to load. It then successfully loads all pieces of the image, only to reboot to the same Mytouch logo screen.
When I use recovery, it can't mount anything, and when I wipe the Cache, it give arror that Ext3 is not compatible.
I reboot and factory restore in recovery, and gives the Ext3 compatibility message and can't mount anything.
I never receive any image loading errors, but I cannot load the 2.2.1 image, as it never give me a chance to say 'yes' to loading it.
If it doesn't work, care to sell it? I need a back and home button for mine lol
I also think my volume buttons will be gone soon, their starting to stick
Sent from my Dark Unicorn Resurrected v.2.5 using xda premium
siloner said:
If it doesn't work, care to sell it? I need a back and home button for mine lol
I also think my volume buttons will be gone soon, their starting to stick
Sent from my Dark Unicorn Resurrected v.2.5 using xda premium
Click to expand...
Click to collapse
The phone is in Mint Condition, so I hoped to resurrect it if at all possible, but if it is not possible I definitely will be selling it whole or in part.
johnmbailey said:
It does not give any errors after flashing to 2.3.4, as it loads, verifies, then asks to load. It then successfully loads all pieces of the image, only to reboot to the same Mytouch logo screen.
When I use recovery, it can't mount anything, and when I wipe the Cache, it give arror that Ext3 is not compatible.
I reboot and factory restore in recovery, and gives the Ext3 compatibility message and can't mount anything.
I never receive any image loading errors, but I cannot load the 2.2.1 image, as it never give me a chance to say 'yes' to loading it.
Click to expand...
Click to collapse
Thats really weird because usually if the emmc is dead, the image doesn't load completely in the bootloader. Have you tried calling tmo and telling them about your predicament? I know you are over warrenty but they might still help.
Glacier Stuck on Splash, now on StraightTalk service
THEindian said:
Thats really weird because usually if the emmc is dead, the image doesn't load completely in the bootloader. Have you tried calling tmo and telling them about your predicament? I know you are over warrenty but they might still help.
Click to expand...
Click to collapse
I am now on Straight Talk, so I no longer have a TMobile account to call about. My PAygo ended on Sunday with them.
Can I load anything from ADB with this version of the HBoot / Bootloader? Does the Ext3 mean it had a newer Rom, so I need to change to a supported type using ADB? IT almost looked like the Ext3 format was causing the problem. This also might be a red flag to support if it was not on a factory format. I inherited the phone, so I do not know the history.
Since it never finished booting, is there any way to use the original HTC.exe programs that install the RUU image?
Why are you s-on? Shouldn't you be s-off if you want to install a rom??
Have you tried rooting method again? As far as i know using the gfree method should not give you this issue,
Sent from my Arrows Z using xda app-developers app
Mytouuch 4g - stuck at splash screee
I bought phone from CL. As I suspected previous owner tried to mod the phone. It loads to splash screen. I can get into bootloader but can not select RECOVERY or FACTORY RESET. I tried the PD15IMG.ZIP but when i extracted hboot is 0.89 (and the following happens):
***LOCKED***
GLACIER PVT SHIP S-ON
HBOOT-0.90.0000
MICROP-0429
RADIO-26.13.04.19_M
eMMC-boot
PD15DIAG.ZIP
no image
PD15DIAG.nbh
no image
Main Version is older!
Update Fail!
Press<power> to reboot
I think i need the IMG that pertains to the HBOOT.
HELP PLEASE
Thank you all
Glacier is Stuch at Splash, so what are options after reloading img?
NeuroticallyYou said:
Why are you s-on? Shouldn't you be s-off if you want to install a rom??
Have you tried rooting method again? As far as i know using the gfree method should not give you this issue,
Sent from my Arrows Z using xda app-developers app
Click to expand...
Click to collapse
The phone is stuck at the splash, so what options do I have that load from SD or USB at the 'Stuck' splash or 'Bootloader'? Can I use the HTC EXE programs to reload the phone or do they require a 'fully booted' phone? Is there any way to load the engineered hboot / bootloader so that I can have ADB options?
johnmbailey said:
The phone is stuck at the splash, so what options do I have that load from SD or USB at the 'Stuck' splash or 'Bootloader'? Can I use the HTC EXE programs to reload the phone or do they require a 'fully booted' phone? Is there any way to load the engineered hboot / bootloader so that I can have ADB options?
Click to expand...
Click to collapse
ok let's calm down and not panic, something similar happened to me when i started rooting my first MT4G, did you try to root the phone? if not i will suggest you to do that with the cyanogenmod guide HERE but before you follow the guide try to boot into bootloader by shutting the phone down, leave it off for like 10 seconds then turn it on by pressing the power button+volume down key, you will enter into bootloader usually you will see 3 androis at the bottom of the screen on skateboards if you don't see that but instead the phone keeps booting into splash screen then try again until you enter bootloader, wihle in bootloader you need to tell me what options you get and what options are enabled, since you can't mount the SD card you will have to get an adapter to download all software needed on the SD card(remember you have to remove the sd card from the phone since you can't mount it). Proceed with the guide until you install a custom rom like CyanogenMod 7.
this type of errors can be reproduced easily for example on a rooted phone wipe the phone completely and reboot, the phone will do exactly the same your phone is doing another thing is i don't know what is this HTC.exe program you are talking about everything is done with the android SDK so before doing everything in the guide you need to download and isntall the android SDK.
it seems like the previous person tried to root but instead messed up the phone system, probably corrupted? like i said i have reproduced the same behaviour on my MT4G many times and by now i don't freak out like it was the first time, the thing that have saved me is the rooting guide, i know by experience that you CAN'T install a rom or anything if you are S-ON.
Bootloader options on Glacier Stuck at bootloader
NeuroticallyYou said:
ok let's calm down and not panic, something similar happened to me when i started rooting my first MT4G, did you try to root the phone? if not i will suggest you to do that with the cyanogenmod guide HERE but before you follow the guide try to boot into bootloader by shutting the phone down, leave it off for like 10 seconds then turn it on by pressing the power button+volume down key, you will enter into bootloader usually you will see 3 androis at the bottom of the screen on skateboards if you don't see that but instead the phone keeps booting into splash screen then try again until you enter bootloader, wihle in bootloader you need to tell me what options you get and what options are enabled, since you can't mount the SD card you will have to get an adapter to download all software needed on the SD card(remember you have to remove the sd card from the phone since you can't mount it). Proceed with the guide until you install a custom rom like CyanogenMod 7.
this type of errors can be reproduced easily for example on a rooted phone wipe the phone completely and reboot, the phone will do exactly the same your phone is doing another thing is i don't know what is this HTC.exe program you are talking about everything is done with the android SDK so before doing everything in the guide you need to download and isntall the android SDK.
it seems like the previous person tried to root but instead messed up the phone system, probably corrupted? like i said i have reproduced the same behaviour on my MT4G many times and by now i don't freak out like it was the first time, the thing that have saved me is the rooting guide, i know by experience that you CAN'T install a rom or anything if you are S-ON.
Click to expand...
Click to collapse
The 2.2.1 image does not load due to 'older version' error in the bootloader, so I renamed it so that it would stop at bootloader to test working options.
Glacier pvt ship s-on
HBOOT-0.89.0006
MICROCROP-0429
RADIO-26.13.04.19_M
cMMC-boot
Jul 15 2011, 16:45:17
HBOOT
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
IMAGE CRC
Fastboot of course works, as I am able to run the image load from SD card
REcovery works, but give the various mounting errors mentioned earlier
factory reset can be selected but does not change anything and it returns to the splash screen
I did not try simlock, as it looks irrelevant
image crc works and seems to check an image somewhere
When I select RECOVERY, Press UP Volume and Power to get past Triangle, it enters the recovery with all of the mount errors, and then the menu pops up
Androic System Recovery <3e>
Use volume .....
Select w Power....
Reboot System Now
Apply Update from SD card
Wipe data / Factory Reset
Wipe Cache Partition
Wiping DAta completes with Ext3 error, unable to mount anything, and unable to open errors, and returns to Recovery menu
Wiping Cache completes wipe with Ext3 error, unable to mount, unable to open and then reboots
Apply Update from SD Card also appears to fail
Rebooting by reason OEM
Cant mount
Count open
then it reboots
From what screens can you mount the 'drive' to use with ADB? When trying to run the ADB commands, I get the error device not found, so I either am not in the correct mode on the phone or I do not have the correct drivers. When coinnectd at the splash screen, my device manafer shows a Portable Device with Drive f:\ and the details show an Android Phone, but the drive is not visible or accessible by ADB.
When I start bootloader with Hboot at USB PLUG mode, the device manage on my computer changes to Android Bootloader device, but I still get 'Device Not Found' after executing the first ADB command. I then followed the info (I think) at http://forum.xda-developers.com/showthread.php?t=881324 with no success for ADB to work, so I something must be wrong.
It seems the S-ON option is not letting you go further, if it gave you a ext3 format error most likely is because the phone can't erase or rewrite the partition needed. Now I'm no expert on the hardware part but I put my small knowledge on that it have to do with the S-ON part of the phone.
Was the phone booting up properly before? If the phone can't boot to android then you can't use adb commands(for what I know) also the fact you don't have a custom recovery image will make it hard for you reinstall android.
I can probably make some time to help you but nothing is better than having the phone so I can troubleshoot. If you want we can chat on gmail to set up a remote session? Other than that I don't see how I can help you.
Sent from my Arrrows Z using xda app-developers app
FINAL Questions on Recovering Glacier MyTouch 4g stuck at Splash
NeuroticallyYou said:
It seems the S-ON option is not letting you go further, if it gave you a ext3 format error most likely is because the phone can't erase or rewrite the partition needed. Now I'm no expert on the hardware part but I put my small knowledge on that it have to do with the S-ON part of the phone.
Was the phone booting up properly before? If the phone can't boot to android then you can't use adb commands(for what I know) also the fact you don't have a custom recovery image will make it hard for you reinstall android.
I can probably make some time to help you but nothing is better than having the phone so I can troubleshoot. If you want we can chat on gmail to set up a remote session? Other than that I don't see how I can help you.
Sent from my Arrrows Z using xda app-developers app
Click to expand...
Click to collapse
Since the phone will not go pase the splash or bootloader / hboot.....
Questions:
1. Can the original manufacturer RUU - Rom Update Utility be downloaded somewhere and if so wouldn't it just need the phone in Bootloader mode?
2. For the ADB method, will it work with thge phone at the Bootloader screen, and if so what drivers arfe needed as the Android Bootloader ones do not work that are showing. Is these another setting beyond just the driver that needs to be set to use ADB?
3. Will a program like Odin that I used to recover my samsung image from bootloader work for these phones?
4. Does anyone have any ideas or should I just part out this Mint phone?
Please refer to previous posts for the details on what has already been tried....and what it is still doing.
johnmbailey said:
Since the phone will not go pase the splash or bootloader / hboot.....
Questions:
1. Can the original manufacturer RUU - Rom Update Utility be downloaded somewhere and if so wouldn't it just need the phone in Bootloader mode?
2. For the ADB method, will it work with thge phone at the Bootloader screen, and if so what drivers arfe needed as the Android Bootloader ones do not work that are showing. Is these another setting beyond just the driver that needs to be set to use ADB?
3. Will a program like Odin that I used to recover my samsung image from bootloader work for these phones?
4. Does anyone have any ideas or should I just part out this Mint phone?
Please refer to previous posts for the details on what has already been tried....and what it is still doing.
Click to expand...
Click to collapse
I don't know of an external app like odin that works for our phone. Also, there are no RUU's for the Glacier, only PD15IMG.zip files.
Since Mint MyTouch 4g Phone is Bricked, how much will work for Slide Version?
I saw an old post with a broken link for an RUU that was supposed to work on the Glacier called the panache. I finally found a working link and downloaded the RUU for Gingerbread, but when I ran it it gave and error that the battery was below 30%, even though fully charged and verified with my wall charger, and 2 usb chargers and 2 different batteries. I might try a powered USB hub, but this data on battery condition might have been stored on the phone somehow? If it could get the phone to work again, then a I could always reflash with a different ROM later.
If there is no hope of recovering this Mint MyTouch 4g Stuck on the splash screen, so can parts be used on the shift / slide version such as LCD / Digitizer, push buttons, or ????
It makes me sick to tear it apart.....
Any other thoughts?
Ran into similar problem
I ran into a similar problem with a message about the version number of the recovery image being wrong. This was a few weeks ago and I didn't keep a log of exactly how I fixed it but this is what I remember:
It turned out that during an attempt to root before I knew what I was doing I had changed the version number using the guide at the link below.
http://www.androidauthority.com/mytouch-4g-t-mobile-root-custom-recovery-74465/
That error message was misleading and the problem was instead due to the fact the phone was unlocked (although mine did say so on the bootloader screen.) HTC images have apparently been created to require a locked phone to successfully load. I relocked it in Fastboot USB mode with the command "fastboot oem relock" and was able to successfully load any version number after that.
Good luck.
Hello, have you tried using a different SD card?
Sent from my HTC Sensation 4G using xda app-developers app
Hi, I have a friend who has just smashed their Desire S whilst out on Sat.
Unfortunately, as the title says, they have no screen (touch doesnt appear to work either but no real way of telling!), not root, no USB debug and I have already checked and they didnt have their contacts set to sync with their google account but with the phone! :-/
Can anyone give any suggestions other than a screen replacement? They have already got an S3 on the way today so just want to be able to restore their contacts.
Cheers and thanks in advance!
I think this is definitely possible, but it may get very complicated.
Do you have adb in recovery (you'll have to boot into fastboot and blindly navigate to the recovery option)? Is the bootloader unlocked?
Aquous said:
I think this is definitely possible, but it may get very complicated.
Do you have adb in recovery (you'll have to boot into fastboot and blindly navigate to the recovery option)? Is the bootloader unlocked?
Click to expand...
Click to collapse
Thanks for replying Aquous!
I have just been given the phone today from a friend to try and help them out so im not sure on either? Do you have a desire s and would be able to tell me the button sequence to get into recovery to find out? As for the bootloader being unlocked, i very much doubt it as the phone was running a stock orange rom.
Any ideas?
Cheers,
It is unlikely indeed that you will be able to recover the data as the phone is. If you're in the UK (possible as the phone is on Orange) and fancy posting it then I can stick my LCD and touch panel on it for you so I can recover the data.
Also if u r in the uk, try a phone repair shop that has jtag, they should be able to pull any data off the phone.
radeonorama said:
Thanks for replying Aquous!
I have just been given the phone today from a friend to try and help them out so im not sure on either? Do you have a desire s and would be able to tell me the button sequence to get into recovery to find out? As for the bootloader being unlocked, i very much doubt it as the phone was running a stock orange rom.
Any ideas?
Cheers,
Click to expand...
Click to collapse
Then you probably don't have adb in recovery either.
We can try the easy way first: from the Google Play website (on your computer), download TalkBack to your phone and see if you can launch it blind. From there on, your phone will read to you what's on the screen
If you can't manage to do that, I have another option in mind but it's complicated and you may not be able to recover your contacts:
Unlock the bootloader via htcdev. This will wipe your data, but if you don't allow the rom to boot after the unlocking, this is OK.
Immediately after issuing the fastboot oem unlock command, HOLD DOWN THAT VOLUME - BUTTON. If the ROM is allowed to load, your data will be significantly harder, if not impossible, to recover.
If you held Vol - correctly after the unlock, you'll be in fastboot (if the phone vibrated, quickly pull the battery before the rom starts writing to the data partition).
From fastboot, boot a custom recovery ('fastboot boot recovery.img')
In this custom recovery, you have adb. Pull the data partition and run file recovery software to try to reconstruct the data that was on it but was wiped by the unlock process.
Purposefully not giving any clearer instructions than this, because if you don't know what you're doing the chances are very high that you're going to do it wrong and won't be able to recover the data.
Aquous said:
Then you probably don't have adb in recovery either.
We can try the easy way first: from the Google Play website (on your computer), download TalkBack to your phone and see if you can launch it blind. From there on, your phone will read to you what's on the screen
If you can't manage to do that, I have another option in mind but it's complicated and you may not be able to recover your contacts:
Unlock the bootloader via htcdev. This will wipe your data, but if you don't allow the rom to boot after the unlocking, this is OK.
Immediately after issuing the fastboot oem unlock command, HOLD DOWN THAT VOLUME - BUTTON. If the ROM is allowed to load, your data will be significantly harder, if not impossible, to recover.
If you held Vol - correctly after the unlock, you'll be in fastboot (if the phone vibrated, quickly pull the battery before the rom starts writing to the data partition).
From fastboot, boot a custom recovery ('fastboot boot recovery.img')
In this custom recovery, you have adb. Pull the data partition and run file recovery software to try to reconstruct the data that was on it but was wiped by the unlock process.
Purposefully not giving any clearer instructions than this, because if you don't know what you're doing the chances are very high that you're going to do it wrong and won't be able to recover the data.
Click to expand...
Click to collapse
Bloody legend!
Using the above coupled with Droid explorer i managed to pull everything she needed! Thanks so much for taking the time to help me out!
All the best!
radeonorama said:
Bloody legend!
Using the above coupled with Droid explorer i managed to pull everything she needed! Thanks so much for taking the time to help me out!
All the best!
Click to expand...
Click to collapse
Holy ****, you actually did this? And it WORKED? You, sir, have some serious balls! Gratz!
By the way, this has HUGE privacy implications
Aquous said:
Holy ****, you actually did this? And it WORKED? You, sir, have some serious balls! Gratz!
By the way, this has HUGE privacy implications
Click to expand...
Click to collapse
Yup, everything i needed off it worked.
I left it for a while as a last resort because of the risk of total data loss and bought a replacement screen which was DOA!
So you plan came into play and it really worked. It wasnt so hard as the steps you gave just helped me get the order right in my head rather than trying something and mucking it up even more!
Thanks again good sir! She was very pleased!
Good day ,
I've been looking around for solution in this forum for two days now and none has helped me solving the problem I'm having. Hopefully by posting more specific details on this thread, you guys could help me pinpoint what to do. My main goal is to backup all data from the internal storage if possible (the data in the SD cards are backed up fine) then proceed to possibly make the phone usable again.
The phone was initially somehow soft-brick (loop on bootloader - tampered, locked, security warning and S-ON). Tried all possible actions/options on the bootloader but none has worked out, it would just prompt me back to bootloader. I am really not sure, as to how it ended up soft-brick. The phone was bought through Vodafone Australia carrier and has never been rooted etc.
So following guide on from (forums.androidcentral.com/htc-one-m8/398427-htc-one-tampered-locked-security-warning-2.html), So from the guide I've done as followed:
- I understand I have to firstly unlocked the bootloader, which was done just fine. So after Unlocked, I could still boot to hboot and getting tampered, unlocked and S-ON (no security warning).
- Then I connect my phone to fastboot, flash twrp-2.8.5.0-k2_ul.img and clear the cache
- I then tried to access the recover mode
- The phone restarted and stuck on the HTC logo with "Starting recovery..." message at the top but nothing really loaded for a long while
- So then I tried to restart it but it just won't work, I then pulled out the battery and re-inserted it
- After that, the phone was just stuck on the battery symbol with solid orange light on (this occurs if the USB cable is connected to power or computer), I tried all button, buttons up/down power hold etc (I even tried that covering middle battery part and let the outer ones connected) but none helped
-- If I unplugged the USB cable, the battery symbol and the solid orange light would still persist until it runs out of battery
-- If I removed the battery then re-insert the battery without connecting to USB cable, it's not displaying anything regardless how long I pressed the buttons (I tried holding them for more than 3 minutes which I assumed enough?)
That's pretty much everything, I really hope someone could shed some light for me - the thing is the data is fairly crucial that it may even help me prove a legal case, where some physical threats were sent out to me. :crying:
Thanks for the assistance in advance!
Help anyone?
i guess that if you didn't break your phone as i did the datas are still there and so, have you a recovery installed like twrp ? if not do it with bootloader, all you have to do is access fastboot and recovery to use adb commands and copy datas, if you can't do that i'm afraid there is no much to do without erasing all..
colton49 said:
i guess that if you didn't break your phone as i did the datas are still there and so, have you a recovery installed like twrp ? if not do it with bootloader, all you have to do is access fastboot and recovery to use adb commands and copy datas, if you can't do that i'm afraid there is no much to do without erasing all..
Click to expand...
Click to collapse
Hi there,
Thanks for your response, so I could access fastboot before and installed TWRP, the phone became 'totally' unresponsive after I installed TWRP and restart the phone.
At first it's stuck on recovery screen loading screen, then it just won't show anything. At the moment, I am wondering if there is any way to recover the internal storage data. I have contacted local HTC service center about the issue and they recommended me to go back to Australia (where I bought the phone) since they don't sell this model here in Indonesia (nearest country selling this model would be Singapore or Malaysia) - so yeah not much help from them as well.
Any other thought?
One SV does not respond
sorry wrong topic...
I got the infamous broken power button that made the Nexus 5 restart endlessly.
I managed to fix it by bashing the phone on the button as per the many guides online and the power button now works fine.
However, it seems either the phone bricked or the flash memory died as the following happens:
- Stuck on endlessly trying to boot Android 6.0 (stuck on boot animation)
- Takes 10 minutes to boot into TWRP (gets stuck on blue screen). When it boots, it reads all storage as 0MB and there are errors trying to mount ALL of the partitions (data, system, cache, etc)
- Phone boots to fastboot. When trying to flash anything to it (I was trying factory 6.0 images manually), I get FAILED: (remote: flash write failure)
- Locking the bootloader from the fastboot menu works, however, when I restart the phone it is unlocked again
- Phone seems to be able to read data (it tried booting android, the TWRP recovery works) but it can't write ANYTHING to it
- I tried both fastboot erase and fastboot format. It fails to do both of these.
- I had the idea to next try and boot it into LG Download mode to flash it to stock using the LG Download tool. I cannot boot into Download mode, however, as pressing Volume_up + plugging phone into PC results in the battery icon for charging. This is the same behavior with my other Nexus 5 (running 6.0) I have.
How can I boot into Download mode on Android 6.0?
Possible the flash storage chip is fried? If so...why can I read fine from it?
It's almost as if it went into write-protect mode or wore out it's write-cycles of the flash.
It is out of warranty. Do I have any options short of a new phone?
UPDATE:
I was going around in TWRP when I noticed my /system partition is read (size and everything) and but cannot be wiped. It says it does it but when I check again, free size hasn't changed.
/data /cache and /persist though give tons of errors and I can't mount, format, etc.
Also tried following this guide
http://forum.xda-developers.com/goo...o-repairing-corrupted-data-partition-t2577447
However, after flashing Philz' recovery (which seems to work from fastboot as it says OK), rebooting fastboot, and selecting recovery it still boots TWRP
found any fix yet? I have the exact same problem
The emmc is damaged and requires a motherboard swap to resolve the issue. I went through this with two nexus 5 phones.
audit13 said:
The emmc is damaged and requires a motherboard swap to resolve the issue. I went through this with two nexus 5 phones.
Click to expand...
Click to collapse
the thing is that my pc recognizes the device properly. I can acces bootloader, twrp and download mode, so I don't think is totally bricked, as long as I can access bootloader. there must be something to do! It just can't mount data, cache and persist! sorry for bad english!
I have to go with that guy on this one, if your eMMC cant be written to, then its essentially bricked, because it requires the cache partition to be written to, to boot the operating system. You can replace the motherboard if your feeling brave.
The fact that the bootloader is unlocking and relocking on its own is one sign. The fact that the partitions cannot be access, formatted, or written to is another sign.
I gave up with my N5 and replaced the motherboard which completely solved the problem.
audit13 said:
The fact that the bootloader is unlocking and relocking on its own is one sign. The fact that the partitions cannot be access, formatted, or written to is another sign.
I gave up with my N5 and replaced the motherboard which completely solved the problem.
Click to expand...
Click to collapse
the thing is, I already replaced two motherboards, the other one was with blacklisted imei. I'm gonna try with the third one, not giving up on this phone!
Did the replacement motherboard exhibit the same behaviour? I suggest a motherboard replacement if every other part in the phone is working.
just a quick question, how did you solve the power button issue? I currently have the same problem and the phone restarts endlessly when plugged in to a charger.
can i boot my (dead emmc) nexus 5 from any external source?