Related
Never like to have to resort to posting myself but I've had a decent look around the web and can't seem to find a solid solution to my problem so I'm hoping to get some specific help
So I have a UK MZ601 3G Motorola Xoom which was happily running Moray 2.2.1 and had been rooted using the universal root method. Decided to update to 2.2.2 and now my Xoom is stuck in a boot-loop on the custom rippling water boot animation.
The tablet hangs on the first line when trying to boot into recovery so for all my efforts cannot access CWM and perform a hard reset and fresh rom install.
I've tried - and I'm assuming I'm correct in thinking this means I cannot get the Xoom to any stage where I can use adb to attempt to get in to recovery or push files to the system etc. this way.
From what I've read on other forum posts - booting holding volume up and power puts the device into an 'RSD' state which is another method of reflashing the device? I've read this requires an 'SBF' file - which I have seen for download - but believe it only works for the US models?
I've left the boot screen looping overnight - so its not an issue of it just being slow. Because of the custom boot screen I obviously can't return it to the shop as I presume its an obvious warranty void?
Would massively appreciate any help in bringing whats looking increasingly like a £500 paper weight back to life.
Thanks
crozuk said:
Never like to have to resort to posting myself but I've had a decent look around the web and can't seem to find a solid solution to my problem so I'm hoping to get some specific help
So I have a UK MZ601 3G Motorola Xoom which was happily running Moray 2.2.1 and had been rooted using the universal root method. Decided to update to 2.2.2 and now my Xoom is stuck in a boot-loop on the custom rippling water boot animation.
The tablet hangs on the first line when trying to boot into recovery so for all my efforts cannot access CWM and perform a hard reset and fresh rom install.
I've tried - and I'm assuming I'm correct in thinking this means I cannot get the Xoom to any stage where I can use adb to attempt to get in to recovery or push files to the system etc. this way.
From what I've read on other forum posts - booting holding volume up and power puts the device into an 'RSD' state which is another method of reflashing the device? I've read this requires an 'SBF' file - which I have seen for download - but believe it only works for the US models?
I've left the boot screen looping overnight - so its not an issue of it just being slow. Because of the custom boot screen I obviously can't return it to the shop as I presume its an obvious warranty void?
Would massively appreciate any help in bringing whats looking increasingly like a £500 paper weight back to life.
Thanks
Click to expand...
Click to collapse
When you press volume up and power, and hold it, it reboots, yeah? Then you wait about three seconds on dual core screen and tap volume down...what happens then? Do you see android recovery in upper left? Or starting fastboot protocol? Where does it hang? Just trying to see where things are going wrong. If you can get into starting fastboot protocol you are in good shape. If you can get into cwm recovery you should be in great shape. Check out the Xoom Heaven thread in General for some info on recovery.
You are most likely far from bricked...almost all of us have recovered from worse situations than you are in now so just keep cool.
okantomi said:
When you press volume up and power, and hold it, it reboots, yeah? Then you wait about three seconds on dual core screen and tap volume down...what happens then? Do you see android recovery in upper left? Or starting fastboot protocol? Where does it hang? Just trying to see where things are going wrong. If you can get into starting fastboot protocol you are in good shape. If you can get into cwm recovery you should be in great shape. Check out the Xoom Heaven thread in General for some info on recovery.
You are most likely far from bricked...almost all of us have recovered from worse situations than you are in now so just keep cool.
Click to expand...
Click to collapse
Thanks for your reply - tried numerous times getting into recovery - get stuck with one line of 'starting fastboot protocol' and seems to hang there.
Have experience rooting and flash etc. and have obviously used adb in the past.
If I could just get to recovery - or a state where I could use adb I would be fine. But as I said in my first post - looks like I can only access an 'RSD' state.
Is there any other way of getting adb access from my PC? All the help for bricked xooms seems to concern US models - and don't want to try anything that will completely write it off!
Thanks again for your help.
Quick update -
Have retried Fastboot - stuck on 'Starting Fastboot protocol support'
Tried Android Recovery - got stuck on a black screen for a long long time but finally booted!
Wiped and re-installed what I know to be a kosher ROM! Was a scary moment there but thanks for your help and reassurance!
crozuk said:
Quick update -
Have retried Fastboot - stuck on 'Starting Fastboot protocol support'
Tried Android Recovery - got stuck on a black screen for a long long time but finally booted!
Wiped and re-installed what I know to be a kosher ROM! Was a scary moment there but thanks for your help and reassurance!
Click to expand...
Click to collapse
If you are still rooted and all, just for safety's sake, make sure to do another nandroid backup and save it to your micro sdcard. Backup, backup, backup. Then also make sure that you have a compatible cwm recovery installed, that will let you access your microsd card. It sounds like you're alright, so, cool.
Hey guys,
Forgive me for being frantic and (probably) not taking the steps needed to research this issue, or not taking the time to do so, but I'm sure you can all presumably imagine -if you've not been in this situation before- that it SUCKS not having a phone in this day in age...
My problem: Atrix 2 (Rooted + CWM Recovery) now won't boot passed the "M" Motorola logo upon start up. It won't even allow me to access the factory Android Recovery by holding down Volume Up, Volume Down, and Power. I think I inadvertently bricked the phone? (Hope not!)
Further, the "M" Motorola logo is skewed in appearance, like its not even loading correctly. I'm not sure what to do. This is my first time rooting and getting experienced with custom ROMS.
Anyone able to help this helpless sap?
Thanks is advance to your replies...
Step 1 is where you tell what you did to get into the state you are in. You wouldn't believe how far it goes toward fixing something if you know how it got broken.
Sent from my MB865 using XDA
If you have CWM recovery on boot can't you just do a battery pull? You do NOT want to let that thing bootloop forever until the battery dies.
The End.
KEB64 said:
If you have CWM recovery on boot can't you just do a battery pull? You do NOT want to let that thing bootloop forever until the battery dies.
The End.
Click to expand...
Click to collapse
Agreed pull the battery. If you run out of juice you'll be in some serious trouble.
Did you try to flash the fkz? Unless you have CWM on Boot it's the only way you can get your phone working.
Okay, sorry for not giving a full rundown on what stupidity on my part cause all of this. Let me start by saying that (sadly) I am a great big n00b when it comes to Linux, and I thought that despite my research online I would sort of explore the CWM Recovery 'Advanced' sections.
I downloaded ROM Toolbox from the Play Store, and installed a custom boot animation, and replaced -or thought I was- the startup "M" logo with something else. This is what concerned me: After re-booting, the "M" logo was all crazy looking, with a "stretched" "M" logo over the top of the "regular" logo.
So, I uninstalled the app, but the logo was still all messed up. So, I used Root Uninstaller to get rid of the ROM Toolbox files, still no resolve to the crazy boot logo.
So, I went into CWM Recovery Advanced, and wiped everything. The Dalvik, cache, System, Data, etc... didn't think that it would -what appears to have happened- wipe out the OS on the phone.
I tried pulling the battery, and re-booting, won't boot passed the skewed "M" logo still. Tried getting into Android Recovery, and it looks to go through the recovery goes through its thing, but never boots normally afterward.
Sorry for being such an idiot, I really shouldn't have messed with this while half asleep, and again I can't apologize enough for being such a stupid n00b.
I can attach an image of the boot logo if that helps, but I'm worried I am just S.O.L. at this point...
Also, not sure what an FKZ is. I tried to install a 2.3.6 apk file to my wife's SD card on her phone and booting from the file after putting the SD card into mine. Still nothing.
pull the battery, put it back in, and hold vol up and down while turning on. choose ap fastboot at the menu. go to the thread in my signature and under the mirrors there is also a download of the return to stock script. run it while in fastboot and plugged in with usb. DO NOT pull the chord until it is done. when it is you should be good.
Apex_Strider said:
Okay, sorry for not giving a full rundown on what stupidity on my part cause all of this. Let me start by saying that (sadly) I am a great big n00b when it comes to Linux, and I thought that despite my research online I would sort of explore the CWM Recovery 'Advanced' sections.
I downloaded ROM Toolbox from the Play Store, and installed a custom boot animation, and replaced -or thought I was- the startup "M" logo with something else. This is what concerned me: After re-booting, the "M" logo was all crazy looking, with a "stretched" "M" logo over the top of the "regular" logo.
So, I uninstalled the app, but the logo was still all messed up. So, I used Root Uninstaller to get rid of the ROM Toolbox files, still no resolve to the crazy boot logo.
So, I went into CWM Recovery Advanced, and wiped everything. The Dalvik, cache, System, Data, etc... didn't think that it would -what appears to have happened- wipe out the OS on the phone.
I tried pulling the battery, and re-booting, won't boot passed the skewed "M" logo still. Tried getting into Android Recovery, and it looks to go through the recovery goes through its thing, but never boots normally afterward.
Sorry for being such an idiot, I really shouldn't have messed with this while half asleep, and again I can't apologize enough for being such a stupid n00b.
I can attach an image of the boot logo if that helps, but I'm worried I am just S.O.L. at this point...
Also, not sure what an FKZ is. I tried to install a 2.3.6 apk file to my wife's SD card on her phone and booting from the file after putting the SD card into mine. Still nothing.
Click to expand...
Click to collapse
Yeah wiping the system partition is a no no unless you flash another rom afterwards. Do like ikrasner says and you should be back to normal.
Sent from my MB865 using XDA
Thanks for all the help guys, I really hope that something positive comes about this... though, to go without mention, I certainly need more knowledge on WTH I am doing to my phone: understanding flashing ROMS, what dangers come with rooting, and a vast array of other "all things root" that I need to learn up on.
I will try to install from SD card the 2.3.5 zip tonight, but will it (the phone) look for the newest 2.3.6 OTA update and try to ask me to install? How does that work after rooting, will I re-brick my clearly bricked phone all over again?
As always, thanks for all your replies in advance -you guys really know what's going on here!
can you read chinese?
Maybe I can solve your question,but poor of my english.
and what is your phone type?
at&t hktw or china ?
Sent from my ME865 using xda premium
Apex_Strider said:
Thanks for all the help guys, I really hope that something positive comes about this... though, to go without mention, I certainly need more knowledge on WTH I am doing to my phone: understanding flashing ROMS, what dangers come with rooting, and a vast array of other "all things root" that I need to learn up on.
I will try to install from SD card the 2.3.5 zip tonight, but will it (the phone) look for the newest 2.3.6 OTA update and try to ask me to install? How does that work after rooting, will I re-brick my clearly bricked phone all over again?
As always, thanks for all your replies in advance -you guys really know what's going on here!
Click to expand...
Click to collapse
It should ask you to install 2.3.6. Just go into setting>about phone>check for updates. Or you could go and install one of the roms that are based on 2.3.6 such as Lithium Sonya or SCv5.
Okay gang, perhaps I'm just certifiably dumb, or I am simply just not doing this correctly. I downloaded the "Returntostock2.3.5.script" zip file and copied it to my wife's SD card to 'apply update from sdcard' option from the Android Recovery area by holding Vol Up, Vol Down, & Power buttons. What I got was this:
--Install /sdcard ...
Finding update package...
Opening update package...
Verifying update package...
E:signature verification failed
Installation aborted.
I tried to just plug the USB into the phone and run the 2.3.5. script from there. but again- I'm stuck in the crazy skewed "M" logo startup screen with nothing following. That's all the phone will do at this point, other than my getting into Android Recovery.
I'm not sure how or what fastboot is, or how it works. If the phone is plugged into the USB, it will only boot the stupid screwed up "M" logo screen. Noting else.
Apex_Strider said:
Okay gang, perhaps I'm just certifiably dumb, or I am simply just not doing this correctly. I downloaded the "Returntostock2.3.5.script" zip file and copied it to my wife's SD card to 'apply update from sdcard' option from the Android Recovery area by holding Vol Up, Vol Down, & Power buttons. What I got was this:
--Install /sdcard ...
Finding update package...
Opening update package...
Verifying update package...
E:signature verification failed
Installation aborted.
I tried to just plug the USB into the phone and run the 2.3.5. script from there. but again- I'm stuck in the crazy skewed "M" logo startup screen with nothing following. That's all the phone will do at this point, other than my getting into Android Recovery.
I'm not sure how or what fastboot is, or how it works. If the phone is plugged into the USB, it will only boot the stupid screwed up "M" logo screen. Noting else.
Click to expand...
Click to collapse
do not flash this. unzip it on your computer, choose to boot into fast boot in the same place you chose recovery, then run the .bat file that was in the zip.
Sent from my MB865 using XDA
What that file does is reflash your system.img, basically restoring your phone to factory default. And just as a sidenote you cannot flash things with the standard Android Recovery. You need CWM.
did you try apboot mode and ise fastboot to flash system.img ?
Sent from my ME865 using xda premium
Still not working... not sure how to flash from fastboot. I don't have any options to run a file from there, or at least not sure ow to go about that.
Fastboot sample, hope will help you.
http://bbs.gfan.com/mobile/android-3701449-1-1.html
Sent from my ME865 using xda premium
dickluo said:
Fastboot sample, hope will help you.
http://bbs.gfan.com/mobile/android-3701449-1-1.html
Sent from my ME865 using xda premium
Click to expand...
Click to collapse
So, if I'm looking at this correctly, I need to open command prompt from my computer, and type the commands in from there?
I don't think my computer is recogzining the phone in any way, as I cannot get into the 'manage usb connections' options.
If I have the 2.3.5.script downloaded on my desktop, and l plug my phone in after launching AP Fastboot on the phone, will the computer know where to flash the file to?
I know, I'm a dolt... please bear with me, I really need to get this thing working again -I feel naked without my phone!
Apex_Strider said:
So, if I'm looking at this correctly, I need to open command prompt from my computer, and type the commands in from there?
I don't think my computer is recogzining the phone in any way, as I cannot get into the 'manage usb connections' options.
If I have the 2.3.5.script downloaded on my desktop, and l plug my phone in after launching AP Fastboot on the phone, will the computer know where to flash the file to?
I know, I'm a dolt... please bear with me, I really need to get this thing working again -I feel naked without my phone!
Click to expand...
Click to collapse
Before using the restore script you need to install the usb drivers for your mb865, you can get those from here: http://www.motorola.com/staticfiles/Support/Experiences/Global_Drivers/MotoHelper_2.1.40_Driver_5.5.0.exe
Next unzip the Return to Stock 2.3.5 Fastboot SCRIPT.zip to anywhere you like in your pc (example: C:\RestoreScript\ )
Next connect your phone with the usb cable to the pc and get into fastboot mode for this in your phone press volume down + volume up + power it should appear a screen with some options, use the volume down key of your phone to navigate through the menu until you see the Fastboot option, then enter by pressing the volume up key, this will show you some messages and the finally it should said usb connected.
Then open the folder where you extracted the Return to Stock 2.3.5 Fastboot SCRIPT files and search a .bat file call "Stock Restore" then run the file (double click on it) and it should open a command promt screen with some instructions if the phone is connected correctly and you installed the drivers correctly then in some point the screen will show you the id of your device and it will wait you to press the enter key to start the proccess, press key enter wait all the proccess until the program said to you its finished, after that it will reboot your phone and install the stock 2.3.5 when it boots up you should see the android logo and a progress bar filling up.
when it's done wait the reboot and your phone should be ok.
hope this helps.
jfrank1485 said:
Before using the restore script you need to install the usb drivers for your mb865, you can get those from here: http://www.motorola.com/staticfiles/Support/Experiences/Global_Drivers/MotoHelper_2.1.40_Driver_5.5.0.exe
Next unzip the Return to Stock 2.3.5 Fastboot SCRIPT.zip to anywhere you like in your pc (example: C:\RestoreScript\ )
Next connect your phone with the usb cable to the pc and get into fastboot mode for this in your phone press volume down + volume up + power it should appear a screen with some options, use the volume down key of your phone to navigate through the menu until you see the Fastboot option, then enter by pressing the volume up key, this will show you some messages and the finally it should said usb connected.
Then open the folder where you extracted the Return to Stock 2.3.5 Fastboot SCRIPT files and search a .bat file call "Stock Restore" then run the file (double click on it) and it should open a command promt screen with some instructions if the phone is connected correctly and you installed the drivers correctly then in some point the screen will show you the id of your device and it will wait you to press the enter key to start the proccess, press key enter wait all the proccess until the program said to you its finished, after that it will reboot your phone and install the stock 2.3.5 when it boots up you should see the android logo and a progress bar filling up.
when it's done wait the reboot and your phone should be ok.
hope this helps.
Click to expand...
Click to collapse
jfrank1485,
This stepped me through the entire process without any confusion! Everything is back to normal! Hooray and three Huzzahs!
Also, many many thanks to dickluo, farshad525hou, lkrasner, mtnlion, and KEB64!
You guys really saved my stupid (you know what) on this deal! Next order of business: figure out what the heck I am doing before doing ANYTHING!
Problem solved, my world has regained sanity, and my phone is back to life!
You guys are the best, thank you all so much!!!
Apex_Strider said:
jfrank1485,
This stepped me through the entire process without any confusion! Everything is back to normal! Hooray and three Huzzahs!
Also, many many thanks to dickluo, farshad525hou, lkrasner, mtnlion, and KEB64!
You guys really saved my stupid (you know what) on this deal! Next order of business: figure out what the heck I am doing before doing ANYTHING!
Problem solved, my world has regained sanity, and my phone is back to life!
You guys are the best, thank you all so much!!!
Click to expand...
Click to collapse
I'm glad it work , keep it at hand before doing anything to your phone, it really helps
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....
Hello, friends at XDA!
My dad has a MyTouch 4G Slide. I didn't want to root it because, ironically, I wanted him to have better support and not end up with a bunch of questions from T-Mobile, should he ever need support. I'm now regretting that decision; his future devices will be rooted out of the box...
The phone, in its current state, will get as far as the splash screen. It will sit there for about 20 seconds, and then turn the screen off. After another ten seconds or so, the phone goes back to the splash screen again.
I can get myself into the bootloader, which is still S-ON. That works reliably, but it's still a bit of a dead end. It checks for a baseband update on the phone, and upon not finding an applicable file on the SD card, spits me back into the fastboot menu. Naturally, I went for the recovery environment. I was able to get to it last night, but even that was a bit shallow in that I got to the red triangle screen, but no menu options were presented. Still, I figured that the recovery environment would allow me to run Unrevoked or similar, but when I came home the phone was camping out on the "waiting for device..." screen, to no avail.
My goal was to root in order to install a recovery environment; I know that ClockWorkMod and TWRP both allow for data to be backed up from within the recovery environment. There are call logs and contacts (no, they're not synced with Exchange or Google) that would be greatly appreciated if I could recover before I perform a factory reset as T-Mobile has instructed me to do.
Is there a way I can flash a recovery environment onto this phone using only the access provided by the phone's search for a baseband update from the bootloader?
Thank you for your time and assistance in this matter.
Joey
Unfortunately no, if you can't boot to os and have stock recovery then you have no adb access which means chances of recovering any data is nil
The red triangle is stock recovery, some combo of buttons (like volume up and down) will bring you options but I forget which ones
Hopefully a factory reset will bring your phone a live as you need to get to the os just to unlock your bootloader so you can flash a custom recovery and root the phone
Sent from my Nexus 4 using xda premium
I always root my phone so I'm not sure but,
You can try to start the device by pressing the power and volume - key at the same time.
Then connect to the pc and try the toolkit.
Maybe others can comment if this wil work.
Sent from my HTC One X using xda app-developers app
No Solution
Hey guys,
by some miracle I managed to get the phone working JUST long enough to run a MyBackup Pro task on it; T-Mobile performed a warranty swap on the phone. There was no consistent solution to it though, but thanks for the input everyone.
Joey
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...