Hello Guys,
I'm now in deep deep trouble as my Nexus 5 has got soft bricked and now stuck in a bootloop. Yesterday evening i unrooted my device, flashed everything to stock and locked the bootloader back because i was getting a really awful battery life upon rooting. Hence thought of reverting to stock. So flashed the stock image of 4.4.2 and setup my phone just like it came from a factory. Only thing i did this time was disable some Google Apps i.e Play News, Games & Magazines, Movies etc. Till midnight it was working too good with only a marginal battery drain on idle i.e 1% in 2 hrs or so.
Today morning when i woke up, i just entered the PIN code and unlocked the homescreen and then it just got stuck. I restarted my device and since then, its just stuck in a bootloop and whenever the phone tries to restart the OS, its gives numerous errors all related to Play sErvices and something like android.process.acore and Media.
I tried to factory reset by going through the stock recovery but even in that it gives the errors " Failed to mount /cache" and "Failed to mount /cache/recovery" with invalid arguments in the brackets.
Now i can't even flash stock as the Bootloader is in Locked State. I'm able to flash unlock Bootloader but when it asks to restart "fastboot reboot", it again gets stuck on the Google Play services error resulting again in locked state. That leaves me with a LOCKED BOOTLOADER, STOCK RECOVERY & NO USB DEBUGGING ENABLED.
What can i do now to get my device working people ? Feel like :crying: since its happened. Moreover, i can't RMA it as I'm now in a different country from where the phone wasn't purchased.
BBThumbHealer said:
Hello Guys,
I'm now in deep deep trouble as my Nexus 5 has got soft bricked and now stuck in a bootloop. Yesterday evening i unrooted my device, flashed everything to stock and locked the bootloader back because i was getting a really awful battery life upon rooting. Hence thought of reverting to stock. So flashed the stock image of 4.4.2 and setup my phone just like it came from a factory. Only thing i did this time was disable some Google Apps i.e Play News, Games & Magazines, Movies etc. Till midnight it was working too good with only a marginal battery drain on idle i.e 1% in 2 hrs or so.
Today morning when i woke up, i just entered the PIN code and unlocked the homescreen and then it just got stuck. I restarted my device and since then, its just stuck in a bootloop and whenever the phone tries to restart the OS, its gives numerous errors all related to Play sErvices and something like android.process.acore and Media.
I tried to factory reset by going through the stock recovery but even in that it gives the errors " Failed to mount /cache" and "Failed to mount /cache/recovery" with invalid arguments in the brackets.
Now i can't even flash stock as the Bootloader is in Locked State. I'm able to flash unlock Bootloader but when it asks to restart "fastboot reboot", it again gets stuck on the Google Play services error resulting again in locked state. That leaves me with a LOCKED BOOTLOADER, STOCK RECOVERY & NO USB DEBUGGING ENABLED.
What can i do now to get my device working people ? Feel like :crying: since its happened. Moreover, i can't RMA it as I'm now in a different country from where the phone wasn't purchased.
Click to expand...
Click to collapse
I had the same problem.
just download this :
http://liciousroms.com/nexus5_restore.html
and do this instructions :
INSTRUCTIONS::
1) Download and install DRIVERS
2) Download and extract Nexus_5_KOT49H_Restore.zip,
3) Turn on your phone, and connect your phone to the computer (make sure you have USB Debugging enabled on the tablet)
4) Open up folder where you extracted the Nexus_5_KOT49H_Restore.zip
5) Double Click on the "Recovery_Nexus7.bat" and follow the instructions,,,,it really is that easy! (watch video and follow along)
6) If your phone will not boot and you need to restore, boot your phone into fastboot (volume down and power) and click the "Dead_Nexus5.bat" file found in the folder
2) Download and extract Nexus_5_KOT49H_Restore.zip,
3) Turn on your phone, and connect your phone to the computer (make sure you have USB Debugging enabled on the tablet)
4) Open up folder where you extracted the Nexus_5_KOT49H_Restore.zip
5) Double Click on the "Recovery_Nexus7.bat" and follow the instructions,,,,it really is that easy! (watch video and follow along)
6) If your phone will not boot and you need to restore, boot your phone into fastboot (volume down and power) and click the "Dead_Nexus5.bat" file found in the folder
^ I can't enable USB debugging as i'm unable to boot into OS.
Guys please HELP ! I'm only looking upto XDA to rescue me out. :crying:
BBThumbHealer said:
Guys please HELP ! I'm only looking upto XDA to rescue me out. :crying:
Click to expand...
Click to collapse
Hi! Check this http://forum.xda-developers.com/goo...orial-how-to-flash-factory-images-lg-t2713833.
Tapatalk-kal küldve az én Nexus 5-el
^ I can't enable USB debugging as i'm unable to boot into OS.
Click to expand...
Click to collapse
Read this:
6) If your phone will not boot and you need to restore, boot your phone into fastboot (volume down and power) and click the "Dead_Nexus5.bat" file found in the folder
Click to expand...
Click to collapse
And try suggested instruction. You don't even need to boot into OS.
Rip95 said:
Read this:
And try suggested instruction. You don't even need to boot into OS.
Click to expand...
Click to collapse
The tool specifically asks for Unlocked Bootloader and like i've already mentioned, its in a lock state. To unlock that, i need to have USB debugging enabled which i can't enable as i'm not able to even see the lockscreen, just stuck in a bootloop. :crying: I'm able to launch the Fastboot Mode and also partially unlock the bootloader but as soon as i type the command "fastboot reboot", the device again goes into bootloop starting the cycle again
Any more suggestions guys or should i assume my Nexus to be a paperweight ?
BBThumbHealer said:
The tool specifically asks for Unlocked Bootloader and like i've already mentioned, its in a lock state. To unlock that, i need to have USB debugging enabled which i can't enable as i'm not able to even see the lockscreen, just stuck in a bootloop. :crying: I'm able to launch the Fastboot Mode and also partially unlock the bootloader but as soon as i type the command "fastboot reboot", the device again goes into bootloop starting the cycle again
Any more suggestions guys or should i assume my Nexus to be a paperweight ?
Click to expand...
Click to collapse
Go to the stock recovery and format cache.. Do it a couple of times till the /cache errors go away and then go to the bootloader and flash the stock factory images again. After flashing the stock images, don't boot it up, head over to the stock recovery and perform a factory reset and then reboot!
The tool specifically asks for Unlocked Bootloader and like i've already mentioned, its in a lock state. To unlock that, i need to have USB debugging enabled which i can't enable as i'm not able to even see the lockscreen, just stuck in a bootloop. I'm able to launch the Fastboot Mode and also partially unlock the bootloader but as soon as i type the command "fastboot reboot", the device again goes into bootloop starting the cycle again
Click to expand...
Click to collapse
You can use command in fastboot "fastboot oem unlock" to unlock then reboot in fastboot again, and try this instruction (since you unlocked you should be able to do this).
BBThumbHealer said:
The tool specifically asks for Unlocked Bootloader and like i've already mentioned, its in a lock state. To unlock that, i need to have USB debugging enabled which i can't enable as i'm not able to even see the lockscreen, just stuck in a bootloop. :crying: I'm able to launch the Fastboot Mode and also partially unlock the bootloader but as soon as i type the command "fastboot reboot", the device again goes into bootloop starting the cycle again
Any more suggestions guys or should i assume my Nexus to be a paperweight ?
Click to expand...
Click to collapse
Here:
bitdomo said:
Hi! Check this http://forum.xda-developers.com/goo...orial-how-to-flash-factory-images-lg-t2713833.
Tapatalk-kal küldve az én Nexus 5-el
Click to expand...
Click to collapse
(BTW you dont have to reboot after bl unlock.
fastboot oem unlock
then flash stock images iwhtout reboot)
What? USB Debugging doesn't have to be enabled. Bootloader unlocking is done from fastboot via 'fastboot oem unlock'.
bitdomo said:
Here:
(BTW you dont have to reboot after bl unlock.
fastboot oem unlock
then flash stock images iwhtout reboot)
Click to expand...
Click to collapse
Bitdomo tried you awesome tool which gave me a slight hope that could revive my Nexus but sadly it didn't :crying: Memory size is matched 32G but userdata erase fails and at last the Download FAIL error is there I just don't know what is preventing the Cache and User Data to erase. Same is the case in Stock Recovery as well.
Can you please get me a solution on this. Would be highly obliged :good:
GldRush98 said:
What? USB Debugging doesn't have to be enabled. Bootloader unlocking is done from fastboot via 'fastboot oem unlock'.
Click to expand...
Click to collapse
BBThumbHealer said:
Bitdomo tried you awesome tool which gave me a slight hope that could revive my Nexus but sadly it didn't :crying: Memory size is matched 32G but userdata erase fails and at last the Download FAIL error is there I just don't know what is preventing the Cache and User Data to erase. Same is the case in Stock Recovery as well.
Can you please get me a solution on this. Would be highly obliged :good:
Click to expand...
Click to collapse
unlock bootloader: fastboot oem unlock DONT restart
download twrp recovery
boot twrp recovery: fastboot boot path_to_twrp_recovery.img
wait until it boots up, if the phone restarts try again.
in wipe settings select format data type yes then ok, if it winished slide the bar to factory reset.
and in cmd terminal type: adb shell then cat /proc/partitions and post the a screenshot about that.
bitdomo said:
unlock bootloader: fastboot oem unlock DONT restart
download twrp recovery
boot twrp recovery: fastboot boot path_to_twrp_recovery.img
wait until it boots up, if the phone restarts try again.
in wipe settings select format data type yes then ok, if it winished slide the bar to factory reset.
and in cmd terminal type: adb shell then cat /proc/partitions and post the a screenshot about that.
Click to expand...
Click to collapse
Successfully unlocked bootloader finally and installed TWRP. Booted in TWRP and performed Data Wipe and it failed. Again unable to mount /cache /persist /data etc commands showed. Then it tried formatting using make_ext4fs function but it failed. Swiped for a factory reset and it failed.
Used your ADB command afterwards and it displayed first daemon started successfully on port 5037 and then error in cmd : device not found.
What next ?
EDIT : Just noticed on the TWRP screen that my internal storage space is being shown as Zero (0) MB Now does this means my flash storage has died ? If that's the case and i need to RMA it, how to relock the bootloader , reset tamper flag and load stock recovery so that google doesn't cause any warranty issues. Please help me in that case as well.
EDIT 2 : Using fastboot, tried flash stock cache.img and userdata.img, it failed. When i flash system.img it went through perfectly. Also, got to know that the steps which you mentioned earlier, TWRP was booted temporarily and bootloader was unlocked temporarily. So does this means i don't need to relock or flash back something ? And, if i've unlocked and relocked the bootloader numerous times, how do i reset tamper flag ?
BBThumbHealer said:
Successfully unlocked bootloader finally and installed TWRP. Booted in TWRP and performed Data Wipe and it failed. Again unable to mount /cache /persist /data etc commands showed. Then it tried formatting using make_ext4fs function but it failed. Swiped for a factory reset and it failed.
Used your ADB command afterwards and it displayed first daemon started successfully on port 5037 and then error in cmd : device not found.
What next ?
EDIT : Just noticed on the TWRP screen that my internal storage space is being shown as Zero (0) MB Now does this means my flash storage has died ? If that's the case and i need to RMA it, how to relock the bootloader , reset tamper flag and load stock recovery so that google doesn't cause any warranty issues. Please help me in that case as well.
EDIT 2 : Using fastboot, tried flash stock cache.img and userdata.img, it failed. When i flash system.img it went through perfectly. Also, got to know that the steps which you mentioned earlier, TWRP was booted temporarily and bootloader was unlocked temporarily. So does this means i don't need to relock or flash back something ? And, if i've unlocked and relocked the bootloader numerous times, how do i reset tamper flag ?
Click to expand...
Click to collapse
Read the stickies in the general section.. It will tell you how to reset the tamper flag.
- Sent from an IceCold Hammerhead!
BBThumbHealer said:
Successfully unlocked bootloader finally and installed TWRP. Booted in TWRP and performed Data Wipe and it failed. Again unable to mount /cache /persist /data etc commands showed. Then it tried formatting using make_ext4fs function but it failed. Swiped for a factory reset and it failed.
Used your ADB command afterwards and it displayed first daemon started successfully on port 5037 and then error in cmd : device not found.
What next ?
EDIT : Just noticed on the TWRP screen that my internal storage space is being shown as Zero (0) MB Now does this means my flash storage has died ? If that's the case and i need to RMA it, how to relock the bootloader , reset tamper flag and load stock recovery so that google doesn't cause any warranty issues. Please help me in that case as well.
EDIT 2 : Using fastboot, tried flash stock cache.img and userdata.img, it failed. When i flash system.img it went through perfectly. Also, got to know that the steps which you mentioned earlier, TWRP was booted temporarily and bootloader was unlocked temporarily. So does this means i don't need to relock or flash back something ? And, if i've unlocked and relocked the bootloader numerous times, how do i reset tamper flag ?
Click to expand...
Click to collapse
You could try one more thing. Format the /presist partition, For some reason it magically fixed other's devices, like for this guy and for an other in that same thread, but if you format it you will lose your wifi and bluetooth mac address, and some kind of DRM stuff. I made a tutorial how to fix wifi and bluetoot mac address problem after the formating, but I cant tell anything about the drm kind of files, because I still didnt get answers form the guys in that thread. That could mean they are experiencing no problems. Here is the zip which formats persist partition.
BBThumbHealer said:
The tool specifically asks for Unlocked Bootloader and like i've already mentioned, its in a lock state. To unlock that, i need to have USB debugging enabled which i can't enable as i'm not able to even see the lockscreen, just stuck in a bootloop. :crying: I'm able to launch the Fastboot Mode and also partially unlock the bootloader but as soon as i type the command "fastboot reboot", the device again goes into bootloop starting the cycle again
Any more suggestions guys or should i assume my Nexus to be a paperweight ?
Click to expand...
Click to collapse
please quote for me to the next time.
just run "Dead_Nexus" and it's will do all the whole thing though the bootloader...
Aviatar2 said:
please quote for me to the next time.
just run "Dead_Nexus" and it's will do all the whole thing though the bootloader...
Click to expand...
Click to collapse
I tried all sort of things before finally giving up. Ultimately sent the device for RMA. Thanks for your inputs as well
@bitdomo, i have realised it was a case of dead memory chip only. I managed to relock the bootloader and reset the tamper flag (oem device info showed Tamper as "false") but now my only cause of concern is the LG Flash Tool. When i flashed the KOT9H firmware, it changed the original device version as mine came with 4.4 OOTB instead of 4.4.2. Can Google refuse the RMA citing this now ? Rest all, the kernel, recovery, bootloader, tamper flag is all stock. I coudn't even change that back to the original device version as i couldn't transfer any zip to the internal storage as it was dead.
BBThumbHealer said:
I tried all sort of things before finally giving up. Ultimately sent the device for RMA. Thanks for your inputs as well
@bitdomo, i have realised it was a case of dead memory chip only. I managed to relock the bootloader and reset the tamper flag (oem device info showed Tamper as "false") but now my only cause of concern is the LG Flash Tool. When i flashed the KOT9H firmware, it changed the original device version as mine came with 4.4 OOTB instead of 4.4.2. Can Google refuse the RMA citing this now ? Rest all, the kernel, recovery, bootloader, tamper flag is all stock. I coudn't even change that back to the original device version as i couldn't transfer any zip to the internal storage as it was dead.
Click to expand...
Click to collapse
Google can't get your actual device factory version, because it is only visible with lg flashtool, and that tool is an internal lg software. Google has nothing to with that tool.
By the way this lgfalsh tool makes your phone offical, because this is the offical tool used in LG service centres!!!!
Can you imagine a guy at google who takes your phone flashes a custom recovery, reads back the misc partition and search for the factory device version in the hex code. Then he checks your phone serial number and sees 310K then denies your rma request because your device factory version cant be that because in oktober 2013 there were no 4.4.2? I think no.
But if it bothers you then, you can flash krt16m, or if your nexus 5 had to do big update ~150 mb ota update then flash kfs78n if your device is D821 or flash kqs81m if your device is D820. Converted roms work too without problems I have tested them.
bitdomo said:
Google can't get your actual device factory version, because it is only visible with lg flashtool, and that tool is an internal lg software. Google has nothing to with that tool.
By the way this lgfalsh tool makes your phone offical, because this is the offical tool used in LG service centres!!!!
Can you imagine a guy at google who takes your phone flashes a custom recovery, reads back the misc partition and search for the factory device version in the hex code. Then he checks your phone serial number and sees 310K then denies your rma request because your device factory version cant be that because in oktober 2013 there were no 4.4.2? I think no.
But if it bothers you then, you can flash krt16m, or if your nexus 5 had to do big update ~150 mb ota update then flash kfs78n if your device is D821 or flash kqs81m if your device is D820. Converted roms work too without problems I have tested them.
Click to expand...
Click to collapse
I have already sent the defective one for RMA so there's no question of flashing any files now. Google sends the new replacement device and and lieu of that they block temporarily the device's price for a period of 14-21 days in which the service centre ppl check for the issues what got the device in. And i think LG only is handling that as it made the device ? So my question still remains now can the LG guys intimate Google that the phone was flashed. ? But on the positive, the flash tool was of LG and it can't be turned unofficial What say ? I don't wish to pay again for a new device. If the service centre guys gives a thumbs up that phone indeed died as a result of hardware failure like emmc chip, then the card block is removed.
BTW, i am not aware whether Google itself handles the service or asks LG to do the same! Any inputs ?
Hi XDA- love your stuff. Have used these communities for 8 different devices - never with an issue. Sad to say my first was on a nexus.
Used WUGs toolkit to unlock my phone last week. Installed the drivers according to the instructions. Clicked "Unlock" and followed all the prompts, and that's as far as I got.
The handset rebooted to the "Upgrade Andoid" graphic, and when I pressed VOL/UP the prompt at the bottom displayed "Formatting /data". This continued the first time for about 12 hours (I went to bed and woke up with it).
Next day I searched every thread that might relate to my issue. Unrooting threads, flash-all.bat for 4.4.4 and 5.0. Attempted sideloads in ADB. Fastbooted the **** out of it. Used e2fsck thinking the partitions needed repairing and even that failed. No love anywhere.
Wondering if you guys could guide me through getting back to square one and how to get my phone running again. It's still got a lot of love to give and I'm not ready to give up on it yet.
When I run Flash-all.bat for 4.4.4 or 5.0 the scripts fail at "erasing cache". I've left it for over an hour and it's just stuck.
In fastboot if I run just the code on it's own it works fine. But when flashing through fastboot something fails.
I've loaded TWRP to try and see anything in there and to get adb shell working, but in TWRP it's unable to mount "/Data", "/Cache", and "storage". The total internal storage as reported by TWRP is 0MB.
When I go into WIPE - the following partitions are
System - 1009MB.
Data - 0MB
Davlik Cache - Invalid Partition
Internal Stor. - Invalid Partition
Cache - 0MB
If it makes a difference (which I wouldn't think it should) I was running 4.4.4 vanilla (unrooted/unlocked) in ART runtime.
Thanks in advance for the help - let me know if there's any other information I can supply to help you help me.
Sneddy32 said:
Hi XDA- love your stuff. Have used these communities for 8 different devices - never with an issue. Sad to say my first was on a nexus.
Used WUGs toolkit to unlock my phone last week. Installed the drivers according to the instructions. Clicked "Unlock" and followed all the prompts, and that's as far as I got.
The handset rebooted to the "Upgrade Andoid" graphic, and when I pressed VOL/UP the prompt at the bottom displayed "Formatting /data". This continued the first time for about 12 hours (I went to bed and woke up with it).
Next day I searched every thread that might relate to my issue. Unrooting threads, flash-all.bat for 4.4.4 and 5.0. Attempted sideloads in ADB. Fastbooted the **** out of it. Used e2fsck thinking the partitions needed repairing and even that failed. No love anywhere.
Wondering if you guys could guide me through getting back to square one and how to get my phone running again. It's still got a lot of love to give and I'm not ready to give up on it yet.
When I run Flash-all.bat for 4.4.4 or 5.0 the scripts fail at "erasing cache". I've left it for over an hour and it's just stuck.
In fastboot if I run just the code on it's own it works fine. But when flashing through fastboot something fails.
I've loaded TWRP to try and see anything in there and to get adb shell working, but in TWRP it's unable to mount "/Data", "/Cache", and "storage". The total internal storage as reported by TWRP is 0MB.
When I go into WIPE - the following partitions are
System - 1009MB.
Data - 0MB
Davlik Cache - Invalid Partition
Internal Stor. - Invalid Partition
Cache - 0MB
If it makes a difference (which I wouldn't think it should) I was running 4.4.4 vanilla (unrooted/unlocked) in ART runtime.
Thanks in advance for the help - let me know if there's any other information I can supply to help you help me.
Click to expand...
Click to collapse
What is the output of fastboot flash cache cache.img ?
You may need to flash cache.img and stock recovery.inmg and then try a manual wipe of /cache via stock recovery.
Sneddy32 said:
Hi XDA- love your stuff. Have used these communities for 8 different devices - never with an issue. Sad to say my first was on a nexus.
Used WUGs toolkit to unlock my phone last week. Installed the drivers according to the instructions. Clicked "Unlock" and followed all the prompts, and that's as far as I got.
The handset rebooted to the "Upgrade Andoid" graphic, and when I pressed VOL/UP the prompt at the bottom displayed "Formatting /data". This continued the first time for about 12 hours (I went to bed and woke up with it).
Next day I searched every thread that might relate to my issue. Unrooting threads, flash-all.bat for 4.4.4 and 5.0. Attempted sideloads in ADB. Fastbooted the **** out of it. Used e2fsck thinking the partitions needed repairing and even that failed. No love anywhere.
Wondering if you guys could guide me through getting back to square one and how to get my phone running again. It's still got a lot of love to give and I'm not ready to give up on it yet.
When I run Flash-all.bat for 4.4.4 or 5.0 the scripts fail at "erasing cache". I've left it for over an hour and it's just stuck.
In fastboot if I run just the code on it's own it works fine. But when flashing through fastboot something fails.
I've loaded TWRP to try and see anything in there and to get adb shell working, but in TWRP it's unable to mount "/Data", "/Cache", and "storage". The total internal storage as reported by TWRP is 0MB.
When I go into WIPE - the following partitions are
System - 1009MB.
Data - 0MB
Davlik Cache - Invalid Partition
Internal Stor. - Invalid Partition
Cache - 0MB
If it makes a difference (which I wouldn't think it should) I was running 4.4.4 vanilla (unrooted/unlocked) in ART runtime.
Thanks in advance for the help - let me know if there's any other information I can supply to help you help me.
Click to expand...
Click to collapse
Try what rootSU said to do and avoid using toolkits in the future. It seems that about 95% of the "help I bricked my phone!" threads stem from using toolkits.
Sent from my iPhone 6 using Tapatalk
In the past I've never used toolkits but figured by now they might be fairly reliable. Big mistake.
rootSU said:
What is the output of fastboot flash cache cache.img ?
You may need to flash cache.img and stock recovery.inmg and then try a manual wipe of /cache via stock recovery.
Click to expand...
Click to collapse
Is this what you mean?
Code:
c:\android-sdk\platform-tools>fastboot flash cache cache.img
target reported max download size of 1073741824 bytes
erasing 'cache'...
OKAY [ 0.577s]
sending 'cache' <13348 KB>...
OKAY [ 0.639s]
writing 'cache'...
OKAY [ 1.086s]
finished. total time: 2.305s
Booted into stock recovery - cache wipe complete. Rebooted and phone went into the Android Updating graphic (wiggly ears & cog). Just a cache partition wipe or factory reset?
Should I now attempt flashall.bat??
I'm using the LRX21o from the Google Dev website. I'm guessing at this point it makes no difference?
Yeah that's what I meant. Looks successful.
Next I guess flashing everything is next step.
So nothing changed, and I decided to give flash-all.bat another go. Same thing. Stalled on 'erasing cache'.
When I forced reboot the error "Too many links" came up.
I went back in and flashed cache.img thinking I might be able to finish off the job. No love. Back to the updating graphic.
Now when I try to go into recovery to start again it just goes into the upgrading graphic.
Bump...?
Return it.
Hi everyone I first want to sincerely thank everyone that will answer to try to help me solve these problems with my nexus.
So the other day my nexus suddenly decided to stop being awesome and it started to be a pain in the ass instead.
When I turn it on it just keeps loading the booting animation of android 6 marshmallowand it never turn on. I identified this problem as a "bootloop" and i tried solving it anyway but it's being really hard and i'm almost getting no results.
I first tried with going into recovery mode. from the fastboot the recovery mode won't start, pops out a died android with a red triangle on it. Pressing volume up and power from that screen got me to another menu. I tried wiping the cache and wipe all the datas/ factory resets but no results. the crappy marshmallow animation goes on till forever.
On the screen that follow the dead android appears the error: E: failed to mount /cache (Invalid argument).
After that i tried with the famous sdk tools.
I am able to unlock the bootloader with the command [fastboot oem unlock]. however after unlocking it, if I turn the phone off and on again it auto lock itself.
i tried to flash a recovery image with the command [fastboot flash recovery recovery.img] but it won't flash. I unlock the device first, and then i try to flash the images. it says ok after the sending but on the writing says FAILED <remote: flash write failure>
same things happen flashing anything else (android factory images etc.)
I can't use adb, i d need to put the usb debugging mode from the developer options but since I coulnd't turn it on I don't know how to turn this option on.
So i discovered existed a "download mode"
Apparently for the nexus5 you have to push volume up and then connect it to the usb to enter in it. I tried many times and it just don't go to download mode (is this the correct procedure??)
I installed the last google divers, no results.
I really don't know what to do, do you guys have any ideas about how to save it?
phone details:
hammerhead d821(E) 32GB
hw version- rev 11
bootloader version: hhz12k
Cheers
Mattia
I think your emmc chip has gone bad and that is why you are getting locked bootloader everytime you reboot the phone as it is not able to hold any memory.
I suggest RMA if its in warranty
tiapnn said:
Hi everyone I first want to sincerely thank everyone that will answer to try to help me solve these problems with my nexus.
So the other day my nexus suddenly decided to stop being awesome and it started to be a pain in the ass instead.
When I turn it on it just keeps loading the booting animation of android 6 marshmallowand it never turn on. I identified this problem as a "bootloop" and i tried solving it anyway but it's being really hard and i'm almost getting no results.
I first tried with going into recovery mode. from the fastboot the recovery mode won't start, pops out a died android with a red triangle on it. Pressing volume up and power from that screen got me to another menu. I tried wiping the cache and wipe all the datas/ factory resets but no results. the crappy marshmallow animation goes on till forever.
On the screen that follow the dead android appears the error: E: failed to mount /cache (Invalid argument).
After that i tried with the famous sdk tools.
I am able to unlock the bootloader with the command [fastboot oem unlock]. however after unlocking it, if I turn the phone off and on again it auto lock itself.
i tried to flash a recovery image with the command [fastboot flash recovery recovery.img] but it won't flash. I unlock the device first, and then i try to flash the images. it says ok after the sending but on the writing says FAILED
same things happen flashing anything else (android factory images etc.)
I can't use adb, i d need to put the usb debugging mode from the developer options but since I coulnd't turn it on I don't know how to turn this option on.
So i discovered existed a "download mode"
Apparently for the nexus5 you have to push volume up and then connect it to the usb to enter in it. I tried many times and it just don't go to download mode (is this the correct procedure??)
I installed the last google divers, no results.
I really don't know what to do, do you guys have any ideas about how to save it?
phone details:
hammerhead d821(E) 32GB
hw version- rev 11
bootloader version: hhz12k
Cheers
Mattia
Click to expand...
Click to collapse
OK so ur ennc chip is NOT dead, that little Android with the triangle is stock recovery, which u can do nothing with, ur going to need a PC, preferably running ubuntu or some other form of Linux with adb and fastboot installed, i cam help with that too if u need it, once u get that settled what u need to do is this, download TWRP for ur hammerhead and rename it recovery.img, place it in a folder u have access to. Open a terminal and connect ur nexus to the pc with USB cable, and boot into bootloader. Then type this into the terminal:
cd (folder with recovery.img in it)
fastboot reboot bootloader (this should boot u back into bootloader if ur device is connected right)
fastboot flash recovery recovery.img
fastboot reboot recovery
This will boot u to TWRP in which u can perform a factory reset, if this doesn't work and ur still in a bootloop, download ur fav rom and gaps and flash it, this will take care of everything
And there is no download mode on the nexus that would be bootloader mode, so let me get this right, what system are u on, and did u try manually formatting with ADB? What happens when u do, I would force format cache, system, boot, and userdata and then flash recovery, that might work
Sent from my Nexus 6 using Tapatalk
Hi all,
Last week my MOTO G gone... It was locked in Motorola screen. I let it discharger 0% so many times last week.
My device was bootloader locked, with no USB debugging.
Ok, i search a lot and found some information. I used the bellow link:
https://forum.xda-developers.com/moto-g/help/moto-g-bootup-problem-recovery-mode-t3122492/
I ran bootloader and try recovery option, but got "Boot up failed message"
I did the some steps: unlock bootloader and then I tried flash a rom in fastboot. No error message returns, but the device always stay in unlocked bottloader screen. I used XT1033 5.02, 5.1 roms but without success.
Then... Tried command:
mfastboot flash recovery twrp-3.2.1-0-falcon.img
But when I reboot phone and entered recovery, got "no command" error.
Following my link guide above, I tried the command:
mfastboot boot twrp-3.2.1-0-falcon.img
And success! I finally could enter in TWRP and backup all my data. Good!
But my sdcard is appearing as read only!
I tried:
WIPE option (Wipes Data, Cache and Dalvik),
Advanced WIPE option (the partitions before and Data and Internal Storage ),
and Format Data option - No success
I did all the steps with partition Data mounted and repeated it again unmounted, booting the device in each try.
I tried the option Repair or Change File System (/data is F2fs) and tried to change the partition to EXT4 - no success.
I tried the same commands described in page 7:
https://forum.xda-developers.com/moto-g/help/moto-g-bootup-problem-recovery-mode-t3122492/page7
and got the same results - no success.
I tried to use PUSH command, but it returns error failed to copy <filename> - read only file system.
Please, could you help me? Thanks in advance.
Your phone's eMMC chip probably died. You have no choice but to do a motherboard replacement. Or get just the chip replaced, but it's risky, since it involves resoldering and reballing BGAs.
Those frequent full discharges killed the chip, I suspect.
Since you've got your data backed up, I suggest you try either of these options.