Related
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 xda. i need your help. im desperate. i dont know what else to do with my moto g here's what happened:
first of all, i dropped my moto g into the water.
right after i got it out, it startet bootlooping. then it turned off by itself after almost an hour had passed.
i put it in a bag full of rice for the rest of the night and almost the whole following day. then i plugged it into the wall charger, and it wouldnt charge at all. the only sign of life was the blinking led.
so i took it to Movistar-Peru for repair, and told me the obvious: water damage was not covered in the warranty, then my phone was returned to me.
so i decided to tear it down by myself.
everything was looking fine. the water indicators were red, but everything was clean except for the battery socket: there was mineral condensation around it. i wiped it out, cleaned it away and then the phone would actually charge the battery icon displayed normally.
so i let it charge for 3 hours and after it was completely charged i turned it on. just to run into a black screen after the bootnimation.
good news is it actually can boot into fastboot mode and can access recovery menu.
i did some research here, and seemed like my phone needed a full stock flash (that´s what i thought). i decided to unlock the bootloader, using motorola unique code. (i thought it may be needed for flashing, but it seems it is not necessary)
in recovery, my sdcard folders display normally, i can wipe data/factory reset it normally, BUT when i try to erase cache partition, the phone reboots.
so i started flashing my device through fastboot. i should mention that before i dropped it into the water, i had installed 4.4.2 ota update. but whenever i tried to flash a 4.4.2 rom, i got hab check failed for sysyem, for recovery and sometimes for boot.
now, i've tried several official motorola signed jelly bean roms (nextel br, movistar sp, claro ar, etc etc) including original Movistar Pe jb rom (which ive already flashed uncountable times) with no errors on flashing, but neither of them got me passed the black screen after bootanimation. (the phone is not off, cause the backlight remains on). the only way of getting out of it is rebooting into fastboot mode again (volume- and power).
i've also tried relocking the bootloader, and the process gives me no errors (the word "locked" displays by the end, though the phone then reboots into the "warning bl unlcked" screen) , but regardless of that and the relocking process turning out okay, status code 3 is displayed in menu, meaning the bl wasnt really relocked..?)
in short:
-dropped into water, started bootloop, then it turned itself off.
-next day it would display black screen after bootnimation, no matter what i did.
-if i choose wipe cache partition, the phone reboots.
-i've flashed it "sucsessfully" several times, still runs into a black screen after bootnimation.
-i've unlocked the boootloader
-if i try to reclock: process turns out okay("locked" word by the end), but status code remains being 3.
-i dont care about backups, i had nothing important in my phone (gdrive ftw)
my concearns are:
-possible hardware unrepairable damage
-bootloader got corrupted
-mineral condensation is still there deep inside the components
-maybe gpu? emmc corrupted? semi brick? idk..
my questions are:
-what can i do from now?
-i've read that a new bootloader can be flashed into the phone. risk of bricking my phone?
-if the bootloader is the problem, flashing a new one would solve it?
-in general, what am i doing wrong in all of this? has my phone any chance of functioning normally, at all?
please help me , i miss my phone, i got it for christmas, it is my first smartphone and i woudl like to bring it back to life if possible. thank you for reading.
I can help!
My girlfriend dropped her Moto G in water too, and it also started showing a black screen after the boot animation. I just managed to fix it.
Even if you have done some of this stuff, do it again anyway.
1-Power phone off
2-Press and hold volume down key for 3 seconds, then press the power key, then release both
3-You will see the boot options menu
4-Press the volume down key to scroll to RECOVERY, then press volume up to select it
5-You will see the Motorola logo, then after 10-30 seconds (maybe longer), you will see a Android logo with an exclamation symbol
6-Press and hold the Volume Up key for 10 seconds, then tap the power button
7-You will see a new menu
8-Use the Volume down key to scroll to Wipe data/factory reset, and then press the power key to select it.
9-Then use the volume down key to select yes, and use the power button to confirm
10-Let the phone format, then press the power key to reboot.
Once the phone has switched back on, wait and see what happens. If the Motorola logo comes on and then stays on for ages WAIT! It takes ages, but the phone will come back to life normally and be working in a few minutes! If you see a black screen again:
Repeat steps 1-7
When you see the new menu again, this time select the cache wipe option (it's the last option on the list)
Let the phone wipe and then it should reboot
This time you will defo see the Motorola logo on the screen for ages. Just keep waiting and press nothing. Hopefully after a minute or 2 it will then take you to the welcome screen
Hope this helped. I couldnt find any advice so had to experiment haha
Thank you for replying to my problem
i have already done your steps uncountable times.
every time i try to wipe cache, the phone reboots. it does not wipe anything at all, it just instantly reboots. then bootanimation, then black screen again, but nothing happens. not even after 2 minutes, after 5 or 10. nothing. just black screen until battery drains completely from continously powering the backlight. do you think maybe the water hardware-bricked my phone? also, im ocassionally getting blue screens out of a sudden, then the phone powers itself off.
Ah, ok, sorry my suggestion didn't help. I had exactly the same problem, so surprised this didn't help you. After being dropped in water, all I got was a black screen after the initial start animation. I don't really know much about phones tbh, I just managed to fix mine through trial and error. My girlfriends phone was initially sent to a shop for repair, and although the guy couldn't fix it, he said there was no signs of water damage. Not really sure then why the phone stopped working, but the method I suggested did work for me. I don't think there was anything else I tried. It's worth mentioning maybe that it took 6 weeks before I could fix the phone. Maybe it took that long to fully dry out? Straight after the accident though the phone was put in a bowl of rice for days so it should have been dried pretty quick. Don't really know what else to suggest, sorry I couldn't be more help. Have faith though, I reckon it'll come back to life soon
thank you for posting a reply and thank you for your advice. i appreciatte the attention given. i will further try some other methods in hope of a solution.
Your bootloader is working fine, dont touch it.
Unlock the bootloader and try to install cwm or twrp recovery, mount and format /data , /cache , /system through the recovery (if you manage it get recovery working ofc).
After that download mfastboot and flash stock rom with it.
Btw if you ever put anything into bag of rise, DON'T CLOSE the bag, you`ll probably do more damage than good this way.It should be done in open-air conditions.
liveroy said:
Your bootloader is working fine, dont touch it.
Unlock the bootloader and try to install cwm or twrp recovery, mount and format /data , /cache , /system through the recovery (if you manage it get recovery working ofc).
After that download mfastboot and flash stock rom with it.
Btw if you ever put anything into bag of rise, DON'T CLOSE the bag, you`ll probably do more damage than good this way.It should be done in open-air conditions.
Click to expand...
Click to collapse
are you sure it has nothing to do with the bootloader? now that you mention this.. can a 4.4.2 bl load a 4.3 rom successfully? and moreover, if i flash another bl, it will overwrite my original one right? is there eny problem on that? i am asking because no matter what i do, regardless of the "locked!" message, the menu keeps showing code status 3.
what happens if i flash the recovery and cant mount or flash any rom? or if the black screen persist after that?
and i wish i had known the rice trick before, cause i kept the bag closed for almost a day :s
grahameaddicott said:
My girlfriend dropped her Moto G in water too, and it also started showing a black screen after the boot animation. I just managed to fix it.
Even if you have done some of this stuff, do it again anyway.
1-Power phone off
2-Press and hold volume down key for 3 seconds, then press the power key, then release both
3-You will see the boot options menu
4-Press the volume down key to scroll to RECOVERY, then press volume up to select it
5-You will see the Motorola logo, then after 10-30 seconds (maybe longer), you will see a Android logo with an exclamation symbol
6-Press and hold the Volume Up key for 10 seconds, then tap the power button
7-You will see a new menu
8-Use the Volume down key to scroll to Wipe data/factory reset, and then press the power key to select it.
9-Then use the volume down key to select yes, and use the power button to confirm
10-Let the phone format, then press the power key to reboot.
Once the phone has switched back on, wait and see what happens. If the Motorola logo comes on and then stays on for ages WAIT! It takes ages, but the phone will come back to life normally and be working in a few minutes! If you see a black screen again:
Repeat steps 1-7
When you see the new menu again, this time select the cache wipe option (it's the last option on the list)
Let the phone wipe and then it should reboot
This time you will defo see the Motorola logo on the screen for ages. Just keep waiting and press nothing. Hopefully after a minute or 2 it will then take you to the welcome screen
Hope this helped. I couldnt find any advice so had to experiment haha
Click to expand...
Click to collapse
It worked for me, Thanks
liveroy said:
Your bootloader is working fine, dont touch it.
Unlock the bootloader and try to install cwm or twrp recovery, mount and format /data , /cache , /system through the recovery (if you manage it get recovery working ofc).
After that download mfastboot and flash stock rom with it.
Click to expand...
Click to collapse
ok i did what you said, i tried to flash cwm and fastboot presented no problems, (output is "okay"), but un the phone screen there's a message "mismatched partition size (recovery)", and when i enter recovery, it boots normal STOCK recovery!! i donw know whats happening. i renamed the cwm image to cwm.img and typed in these commands:
fastboot erase recovery
fastboot flash recovery cwm.img
then i clicked recovery option in the bootloader menu... but it booted into stock recovery!! this is so confusing
Now
mfastboot flash partition gpt.bin
mfastboot flash fsg fsg.mbn
at first since it seems you got partitions a bit messed for some reason.
Then flash everything in order, skip those 2
Also if you are really suspcious about the bl is not working fine, just flash motoboot.img from the same version of android you need.
thank you i will proceed to try what you said. though i have a question: is it possible for the bootloader to be overwritten with a previous version?
and what does it mean when the phone outputs "hab check failed for boot/recovery/system (etc)" ? i sometimes get those errors when flashing other region (official) roms
liveroy said:
Now
mfastboot flash partition gpt.bin
mfastboot flash fsg fsg.mbn
at first since it seems you got partitions a bit messed for some reason.
Then flash everything in order, skip those 2
Also if you are really suspcious about the bl is not working fine, just flash motoboot.img from the same version of android you need.
Click to expand...
Click to collapse
i tried what you said and it is all the same. i choose "recovery" after flashing a custom recovery image, but it boots into stock recovery. any ideas on what might be going on?? is it possible for water damage to cause this behaviour ?
tenjou_89 said:
i tried what you said and it is all the same. i choose "recovery" after flashing a custom recovery image, but it boots into stock recovery. any ideas on what might be going on?? is it possible for water damage to cause this behaviour ?
Click to expand...
Click to collapse
Hmm, maybe leave the recovery aside for now and try to boot a 4.3 ROM (stock one).
Also you cannot downgrade to bootloader afaik, but the newer ones work fine with 4.3 ROMs.
I don't think that the eMMC got damaged, cos nothing will work then.I really can't say if your problems are coming from the water dip or it's just the Moto G being stubborn if you do even one thing the wrong way.
PS. How do you flash the recovery?
fastboot erase recovery
fastboot flash recovery recovery.bin
fastboot reboot bootloader
This way?
what about the ram? a guy on some other forum said that maybe the ram got damaged to a point where only a part of it is now writable, and it gets flooded just before the complete boot up of the system, wichi is why the phone would then crash and display a black screen. what do you think about that theory?
i am going to try with 4.3 roms now. oficial and custom and post the results.
liveroy said:
PS. How do you flash the recovery?
fastboot erase recovery
fastboot flash recovery recovery.bin
fastboot reboot bootloader
This way?
Click to expand...
Click to collapse
yes, exactly that way.
edit: except i have images instead of bins, so:
fastboot erase recovery
fastboot flash recovery recovery.img
fastboot reboot bootloader
Typo of mine, should be .img
About that RAM theory, it really doesn't sound viable to me, but who knows.
If I have to guess, I would say it's probably some crucial component failing to initialize properly and the kernel halts the system.
hmmm do you know of a method of checking for the conditions of individual hardware componets through a pc? like probing or running a full check of everything, not just the emmc..?
These seem not to work.
But if you find the correct details, maybe there is something to test in the service menu.
I have the same problem without water damage. I guess its the 4.4 OTA bug.
Tried reflashing the firmware i already have but of no use.
Mine shows the Blue Motorola logo and then doesn't show the boot animation.
Please can anyone help me out :'(
Hello everybody here at XDA, ( this is my first post here so bare with me here)(english is not my native language either)
My device:
Nexus 5 - hammerhead D821(H) 16GB
BL version - HHZ12h
BB version M8974A-2.0.50.2.26
Secure boot enabled
lock state unlocked
today i got a "broken" nexus 5 that is in boot loop with the google logo and it wont boot into any .img
At the start i read the pinned posts and found this tutorial: http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
followed it step by step. but unfortunatly it didnt help my situation. there werent any errors or such kind.
i also tried this tutorial with other images but nothing worked.
When i go to the recovery mode and press the power button the phone get into the google logo and i can see some sort of strange stripes in like a milisecond but then it just gets into the boot loop.
i really think ive tried everything accept for relocking the bootloader but cant imaging that this could be the problem.
If you guys need more info please just ask me.
Hope you guys can help me out here.
Martin
Really thought XDA forums would be able to help me.
Any admins or mods or any other veteran that could help me out?
If that's not working for you, you can try using the Nexus Root Toolkit just to be sure.
If that doesn't work, than it could be hardware related, and not much you can do about that.
Hi All,
I have boot-loop problem for Nexus5 as described earlier .
As I was able to boot in Fastboot
I went for factory reset, and saw FAILED (remote: flash write failure).
I have tried to flash countless time with same error.
Then I read this thread and considered phone memory is toasted.
LG service-center have quoted me around $180 for mother board replacement.
Today I tried twrp project to boot in openrecovery and start an adb shell.
I was able to see file system of my phone.
These following folders are empty:
/boot
/cache
/data
In system folder there is only bin folder and which is empty.
/system
I have gotten this far, is internal memory roasted
Any direction or suggestions welcomed :good:
mesh120673 said:
Hi All,
I have boot-loop problem for Nexus5 as described earlier .
As I was able to boot in Fastboot
I went for factory reset, and saw FAILED (remote: flash write failure).
I have tried to flash countless time with same error.
Then I read this thread and considered phone memory is toasted.
LG service-center have quoted me around $180 for mother board replacement.
Today I tried twrp project to boot in openrecovery and start an adb shell.
I was able to see file system of my phone.
These following folders are empty:
/boot
/cache
/data
In system folder there is only bin folder and which is empty.
/system
I have gotten this far, is internal memory roasted
Any direction or suggestions welcomed :good:
Click to expand...
Click to collapse
Are you sure your bootloader is unlocked?
When you boot the phone in Fastboot mode, does the "lock state" say UNLOCKED?
If so, then yeah, your internal memory could be huffed.
spookytay said:
Are you sure your bootloader is unlocked?
When you boot the phone in Fastboot mode, does the "lock state" say UNLOCKED?
If so, then yeah, your internal memory could be huffed.
Click to expand...
Click to collapse
It says Locked.
I unlock it using ./fastboot oem unlock
I just got my N5 and was messing around. Rooted it and loaded a rom, but it would just seem to hang at the spinning dots forever. Though I didn't wait THAT long like some users did and had success.
I can't find the link I used, but googling around should get you there. I ended up restoring a factory image via fastboot. I ended up using THIS PROGRAM to root the phone. This program also has a restore option and gives an option to check in case you are in boot loop status. Give it a shot.
Yes I do believe you have to unlock the bootloader as well.
Nurmi_CEO said:
I just got my N5 and was messing around. Rooted it and loaded a rom, but it would just seem to hang at the spinning dots forever. Though I didn't wait THAT long like some users did and had success.
I can't find the link I used, but googling around should get you there. I ended up restoring a factory image via fastboot. I ended up using THIS PROGRAM to root the phone. This program also has a restore option and gives an option to check in case you are in boot loop status. Give it a shot.
Yes I do believe you have to unlock the bootloader as well.
Click to expand...
Click to collapse
Yes the bootloader must be unlocked before you can do ANYTHING to the phone, it's what's there to protect it from being hacked/changed or whatever. So before you can write anything to your phone, you need to make sure you OEM UNLOCK the bootloader.
[Solved!] Nexus 5 boot loop at Google logo
I found a solution on Youtube comment (can't post url, too new user).
You just have to press quickly the Power button durint 1-2 minutes (continue untill the Android animation start, don't stop when the Google logo appear)3
As crazy as it sounds, IT WORKS
Wow .. i had the exact same problem (Startup loop on Nexus 5 that shows the Google logo and restarts, over and over), and i pressed the power button quicky about 30 or 40 time until after I saw the startup animation and my phone came back to life. I have been charging it with cables other than the one that came with the phone for a few months now, and it has been acting strangely while plugged in (randomly clicking things on the screen, and enabling my camera and taking pictures on its own, etc.). So, to avoid problems in the future, I think I'll invest in a wireless charger. Thanks JackNUMBER for the easy solution. I hope this works for others as well. Saved me a trip to the store.
First of all, I'm pretty noob this days on Android so I'm very sorry guys, also english is not my first language.
My nexus was working great until today. I ended a Whatsapp Call and get a black screen, phone looks frozen (happened before). Reboot it and works fine for 5-10 minutes, after that it started to reboot itself the whole time in bootlop, stuck in the rom intro, after the Google text. My rom is one of the very first roms from Slim Roms, I'm sorry I don't remember the Android Version, but is "old".
I can access to the recovery mode tho. I tried to wipe dalvik cache and the TWRP failed, wipe and factory reset, fail as well... I don't know what else to do. I don't have any image to install in the sd, or any backup. Windows 10 recognize an "android" but can't access to it so I can't copy any file to it.
Is my phone dead or can I do something? I love this phone :crying:
Any help please? I tried using ADB and get to copy some files into the phone but still every time I try to do a wipe cache, factory reset or what ever I get a Unable to mount Data / Cache / Storage... every time the same error.
I google it and found that some people could fix that error by repairing the file system and select ext4. But I can't do that, my TWRP build is quite old (v2.6.3.4) and doesn't have that option here. Any suggestions?
Thanks btw
Me again
I've been reading forums for more than 7 hours today and trying different solutions, and nothing. But found this guy here https://androidforums.com/threads/is-my-nexus-5-dead.1099076/
He basically had the same issue as me few years ago, exactly the same, He didn't find any luck apparently.
How is it possible that a phone that can get access to TWRP or copy/flash files via ADB/Fastboot can't be saved? Theoretically in this case this is not a hard bricked, right? So? This is so so weird
It's possible that portions of the internal memory are damaged.
The only thing left to try is flash a stock ROM using ADB commands. I recommend trying a KK ROM.
No OS but twrp working
Hello friend.
If I have understood your problem correctly then you have twrp working but no os.
I found that there is an option in twrp to enable MTP. once you do that you will be able to access it. While the phone is in recovery mode connect it to the computer and it will get recognized and you can transfer zip file to it and then flash a new os.
Cheers!
audit13 said:
It's possible that portions of the internal memory are damaged.
The only thing left to try is flash a stock ROM using ADB commands. I recommend trying a KK ROM.
Click to expand...
Click to collapse
I tried that already, it does the installation thing but always fail in the end
mevrik_007 said:
Hello friend.
If I have understood your problem correctly then you have twrp working but no os.
I found that there is an option in twrp to enable MTP. once you do that you will be able to access it. While the phone is in recovery mode connect it to the computer and it will get recognized and you can transfer zip file to it and then flash a new os.
Cheers!
Click to expand...
Click to collapse
Also tried that: new rom+ gapps via usb adb and the TWRP says Failed...
I mean I still have OS because every single time I try to turn on my phone the animation screen of the Slim Rom goes in. The problem is I can't install anything new, no new rom, no factory image, no new version of TWRP, I can't wipe data or cache or do a factory reset because I get a big red Failed always. Feelsbad
ekeixdurden said:
I tried that already, it does the installation thing but always fail in the end
Also tried that: new rom+ gapps via usb adb and the TWRP says Failed...
I mean I still have OS because every single time I try to turn on my phone the animation screen of the Slim Rom goes in. The problem is I can't install anything new, no new rom, no factory image, no new version of TWRP, I can't wipe data or cache or do a factory reset because I get a big red Failed always. Feelsbad
Click to expand...
Click to collapse
Try this: lock the bootloader and reboot back into the bootloader. If the bootloader remains locked, that's a good sign. If the bootloader is unlocked, that is a bad sign.
audit13 said:
Try this: lock the bootloader and reboot back into the bootloader. If the bootloader remains locked, that's a good sign. If the bootloader is unlocked, that is a bad sign.
Click to expand...
Click to collapse
I tried that with the Nexus root tool kit and the bootloader still is unlocked
ekeixdurden said:
I tried that with the Nexus root tool kit and the bootloader still is unlocked
Click to expand...
Click to collapse
Tells me that the memory chip is defective and needs to be replaced.
Indicates to me that the chip had lost its write capability.
audit13 said:
Tells me that the memory chip is defective and needs to be replaced.
Indicates to me that the chip had lost its write capability.
Click to expand...
Click to collapse
Shieeeet... So nothing to do I guess? I already ordered a new phone but if I can save this beauty would be great
It would be great to fix it but the simplest solution may be to buy a nexus 5 with a smashed screen and working motherboard. I've done this before and it's worked out well because the nexus 5 is pretty old by today's phone standards so I got it cheap.
hmm not a bad idea at all. Thank you!
I was trying to flash a rom in TWRP and received and error - This was the error "Failed to mount '/system' (Invalid Argument).
I then Advanced>Wipe> Delvik, Cache, Data, Internal storage, System and Vendor (a few times). Then i went to the System Partition and Repaired it, then changed the file type from EXT4 to EXT2 then back to EXT4 and rebooted the phone.
The screen does not want to turn on now, the tablet does come on and i am able to send Fastboot commands to it.
What ive tried
1. Holding the power button till it turns off and on.
2. Plugging in the charger and then holding the power button to cycle power.
3. Opened the tab and removed the battery, held the power button, reconnected the battery and turned the device on.
4. Disconnected the battery and plugged into computer.
5. Shorted the Test point and connected the device to the PC (once with the battery connect and without it connected).
6. Reloaded the bootloader with fastboot.
7. Tried to flash TWRP and stock recovery (i did the steps that would put the phone into fastboot mode but im not 100% if it actually goes into Fastboot mode), i get the following error - "FAILED (remote: partition length get error)".
The device receives fastboot commands without me having to attempt to put into into fastboot mode (i.e. Once the device turns on, it receives fastboot commands).
8. I tried to recover using HiSuite but it says that my device is not supported (after i loaded LineageOS to the device, my Tab was being identified as a P8 Lite on my PC, i think this may be the reason why HiSuite says its not supported).
9. Removed the screens connector (with battery connector disconnected) and did a power cycle, then reconnected both.
I don't have access to the Internal storage or SD card when the device is connected to my PC.
Im not sure what else to do, im hoping that some one can help me with this.
As I can see you're proud owner of a totally bricked tablet.
My recommendation: Take it to authorized servíce center and let them try to fix it.
jwoegerbauer said:
As I can see you're proud owner of a totally bricked tablet.
My recommendation: Take it to authorized servíce center and let them try to fix it.
Click to expand...
Click to collapse
Hahaha, thank you thank you, i do appreciate the humor. I would most likely avoid the service center option, it would probably cost me the same amount or less to buy a new motherboard and install (also probably less time and stress).
For anyone that may come across this thread, i havent been able to fully try this method, but i think the below guide may be a solution to unbricking your Mediapad (possibly other devices if you loosely use the same methods).
Downgrade/Unbrick Huawei device (if other methods doesn't work)
This is Generic guide for Unbricking or Downgrading Huawei devices with Kirin 960 CPU. Most probably very similar steps can be done for Kirin 970, but i don't have device to test. At the end i did attach my files, that i used for CMR-W09. This...
forum.xda-developers.com