Hi, I was trying to flash stock 4.4.3 to my Nexus 5 using this method. Something happened and now it won't boot up past the "Google" splash screen with the padlock.
I decided to try using Nexus Root Tool v1.8.3 to flash it, using Back to Stock > Current status: Soft-Bricked/Bootloop. I saw that there is an older thread where someone had a similar issue, but I'm still fairly new (I'd say intermediate level) at this stuff and I don't understand what they're saying and I'm on the verge of freaking out because I do everything through my phone.
I can still access the Bootloader and Recovery, so I believe there's hope, but I keep trying over and over again and the command line keeps spitting out errors, then fastboot crashes. Please help! :crying:
I tried method #2 in this guide on XDA, and fastboot picks up my phone, but some of the commands are failing, stating "FAILED (command write failed (Invalid argument))" or "FAILED (command write failed (No such device or address))" or the error mentioned in the thread title.
After trying it, my phone is still bootlooping.
seems odd that bootloader and recovery flash fine
try, long shot, fastboot format userdata obviously you will lose data, but I think that's gone anyway.
or maybe better fastboot flash a custom recovery and boot to it via fastboot, see if you can repair from there with some adb commands
otherwise it seems your partitions are messed up, I think maybe a full .tot flash with lgtool is in order
175
meangreenie said:
seems odd that bootloader and recovery flash fine
try, long shot, fastboot format userdata obviously you will lose data, but I think that's gone anyway.
or maybe better fastboot flash a custom recovery and boot to it via fastboot, see if you can repair from there with some adb commands
otherwise it seems your partitions are messed up, I think maybe a full .tot flash with lgtool is in order
Click to expand...
Click to collapse
I tried
Code:
fastboot format userdata <directory>\userdata.img
and it failed (you can see it in the 2nd screenshot in the 2nd post). Don't I need to be rooted to be able to flash a custom recovery? I'd successfully unrooted before this mess occurred.
What's .tot flashing about? I'm willing to try that if flashing custom recovery is a lost cause.
you can flash a custom recovery as long as your unlocked, root is not needed.
looking at your screen shots shows that recovery is flashing ok.
Hi! You could try to upgrade your fastboot and adb binaries with your drivers as well. Use usb2.0 port only, and restart your PC
Tapatalk-kal küldve az én Nexus 5-el
meangreenie said:
you can flash a custom recovery as long as your unlocked, root is not needed.
looking at your screen shots shows that recovery is flashing ok.
Click to expand...
Click to collapse
I got TWRP v2.7.1.1 installed. How do I do repairs using adb commands?
bitdomo said:
Hi! You could try to upgrade your fastboot and adb binaries with your drivers as well. Use usb2.0 port only, and restart your PC
Tapatalk-kal küldve az én Nexus 5-el
Click to expand...
Click to collapse
Hi. How do I upgrade the binaries? I believe everything is up-to-date, though. I'd installed everything fresh yesterday, for the purpose of flashing 4.4.3.
Also, in case it's important, TWRP showed this (see attachment):
Dalae said:
I got TWRP v2.7.1.1 installed. How do I do repairs using adb commands?
Hi. How do I upgrade the binaries? I believe everything is up-to-date, though. I'd installed everything fresh yesterday, for the purpose of flashing 4.4.3.
Click to expand...
Click to collapse
Latest drivers for phone http://developer.android.com/sdk/win-usb.html
Latest adb and fastboot in the sdk/platform tools folder in android sdk http://developer.android.com/sdk/index.html. Copy use those binaries for the flashing process.
Oh sorry as I see from the pictures you already have teh latest of everything. You could try this http://forum.xda-developers.com/goo...orial-how-to-flash-factory-images-lg-t2713833
I don't know if you can repair it with adb commands, but there was a thread on the general section which had a lot of info on repairing the data partition, you might want to have a search for it.. I can't remember what it was called, sorry. .. maybe something like... corrupt data recovery
otherwise the tot method linked above should get you up and running quickly.
bitdomo said:
Latest drivers for phone http://developer.android.com/sdk/win-usb.html
Latest adb and fastboot in the sdk/platform tools folder in android sdk http://developer.android.com/sdk/index.html. Copy use those binaries for the flashing process.
Oh sorry as I see from the pictures you already have teh latest of everything. You could try this http://forum.xda-developers.com/goo...orial-how-to-flash-factory-images-lg-t2713833
Click to expand...
Click to collapse
meangreenie said:
I don't know if you can repair it with adb commands, but there was a thread on the general section which had a lot of info on repairing the data partition, you might want to have a search for it.. I can't remember what it was called, sorry. .. maybe something like... corrupt data recovery
otherwise the tot method linked above should get you up and running quickly.
Click to expand...
Click to collapse
Okay, thanks. I'll try the LG Flashtool. If I have any questions, I'll ask here. Either way, I'll post results.
I flashed the firmware and everything seems hunky-dorey. :victory: Thanks for your help, both of you. I realize that restoring device factory version is optional, but what's it about? As in, under what circumstances would I want to do this?
PS: When my phone booted up, it showed that the 4.4.3 OTA update is available. If I were to update would that have any effect on my device factory version?
Dalae said:
I flashed the firmware and everything seems hunky-dorey. :victory: Thanks for your help, both of you. I realize that restoring device factory version is optional, but what's it about? As in, under what circumstances would I want to do this?
PS: When my phone booted up, it showed that the 4.4.3 OTA update is available. If I were to update would that have any effect on my device factory version?
Click to expand...
Click to collapse
you have to restore your original factory device version if it bothers you that it is not your original . Btw the name of the tot file will be your new device factory version. if you flash a tot file which has the same name as your original factory device version then you have to do nothing
Tapatalk-kal küldve az én Nexus 5-el
bitdomo said:
you have to restore your original factory device version if it bothers you that it is not your original . Btw the name of the tot file will be your new device factory version. if you flash a tot file which has the same name as your original factory device version then you have to do nothing
Tapatalk-kal küldve az én Nexus 5-el
Click to expand...
Click to collapse
Ah, alright. Thanks! I don't really care that it's not the original, as long as it doesn't have any undesirable effects. And, just for the heck of it, here's what was in the log regarding the original and the result:
[15:46: 7] 11. device factory version = LGD820AT-00-V10a-NXS-XX-OCT-09-2013-KQS81M-USER-32G+0
[15:46: 7] 12. device factory out version = LGD820AT-00-V10a-NXS-XX-OCT-03-2013-KRS59B-FACTORY-XXG+0
I installed the 4.4.3 OTA and it went smoothly. I'm free to unlock my bootloader, root, and install custom recovery now, correct?
nice to see your up and running
yes. now you can unlock and root
just one thing to watch out for, after running the unlock command you must let your phone fully boot once. this is because the original recovery is needed to complete the process during boot up.
then your free to install a custom recovery and flash a root zip, supersu by chain fire recommended by me. then when booted install and run busybox from the playstore
Great, thanks! I rooted using NRT, which installed BusyBox Free for me.
Sent from my Nexus 7 using Tapatalk
I have been getting this kinda crap on my Nexus 7 2013 and Nexus Player when I upgrade between OS Versions.
The Fix is to open up the system update ZIP file, extract the individual partitions and flash SYSTEM.img manually
Code:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
I think it has to do with a Fastboot memory limitation or something. It could be an older version, but it seems it just can't flash everything at once. If you separate it out and flash each one separately, it works fine.
Related
I flashed a CM based ROM, and decided to get back to Slimkat. Opened my recovery ( Philz CWM ) wiped everything, and now tried to restore my nandroid ! And suddenly Im on Can't mount /sdcard ! I can't even flash a new ROM or do anything, I get stuck on Google's boot logo if I want to get to the ROM.
Let's note that I had no USB debug checked as I was only checking out the newly flashed ROM. So am I literally in a dead situation? Anyone please may help ?
Ensifolk said:
I flashed a CM based ROM, and decided to get back to Slimkat. Opened my recovery ( Philz CWM ) wiped everything, and now tried to restore my nandroid ! And suddenly Im on Can't mount /sdcard ! I can't even flash a new ROM or do anything, I get stuck on Google's boot logo if I want to get to the ROM.
Let's note that I had no USB debug checked as I was only checking out the newly flashed ROM. So am I literally in a dead situation? Anyone please may help ?
Click to expand...
Click to collapse
Clean fastboot install :/ Solved the issue for me
try and format cache. If still no luck, fastboot flash cache cache.img
rootSU said:
try and format cache. If still no luck, fastboot flash cache cache.img
Click to expand...
Click to collapse
Can I still fastboot even if I have no USB debugging enabled? The phone will interact with the commands normally? ( Since as I mentioned before I flashed the ROM only to check out and played with no settings at all, didnt know this is going to happen )
Ensifolk said:
Can I still fastboot even if I have no USB debugging enabled?
Click to expand...
Click to collapse
fastboot commands are done in the bootloader. USB debugging is an Android setting. The 2 are not related even in the slightest.
rootSU said:
fastboot commands are done in the bootloader. USB debugging is an Android setting. The 2 are not related even in the slightest.
Click to expand...
Click to collapse
Thank you sir ! Im sorry to go further saying that I have never used fastboot even thought this is my third nexus device, the regular way of me having a Nexus is using a toolkit on day one to Unlock/Root and then the rest is always done to me on a Recovery !
I am currently downloading the Factory Image to flash it via fastboot ( There are instructions on how to do that ) But will delete everything on my phone.
Is there a way I can save myself right now without any loss? Via fastboot commands? And how can I do it? ( Im really sorry for taking your time and mixing my inexperience )
You'd be a life saver hehe
Ensifolk said:
Thank you sir ! Im sorry to go further saying that I have never used fastboot even thought this is my third nexus device, the regular way of me having a Nexus is using a toolkit on day one to Unlock/Root and then the rest is always done to me on a Recovery !
I am currently downloading the Factory Image to flash it via fastboot ( There are instructions on how to do that ) But will delete everything on my phone.
Is there a way I can save myself right now without any loss? Via fastboot commands? And how can I do it? ( Im really sorry for taking your time and mixing my inexperience )
You'd be a life saver hehe
Click to expand...
Click to collapse
Dont flash the entire factory image.
just use the
fastboot flash cache cache.img
Then you won't wipe the device.
This is why not to use toolkits. fastboot is essential basic knowledge and using toolkits means you dont get to learn it
rootSU said:
Dont flash the entire factory image.
just use the
fastboot flash cache cache.img
Then you won't wipe the device.
This is why not to use toolkits. fastboot is essential basic knowledge and using toolkits means you dont get to learn it
Click to expand...
Click to collapse
You are totally right about that I should learn about it ! Hahaha. Okay, I opened a command promt and I am in the bootloader, where should I get the cache.img from? And should I place it in a certain folder? cause apparently I tried doing this command and it didn't work, I guess i have to get the cache.img from somewhere ( Im really sorry mate...Thanks again )
Ensifolk said:
You are totally right about that I should learn about it ! Hahaha. Okay, I opened a command promt and I am in the bootloader, where should I get the cache.img from? And should I place it in a certain folder? cause apparently I tried doing this command and it didn't work, I guess i have to get the cache.img from somewhere ( Im really sorry mate...Thanks again )
Click to expand...
Click to collapse
Have a read of the "how to flash a factory image" thread in general. Just remember, dont follow it blindly as you'll flash the whole factory image.
rootSU said:
Have a read of the "how to flash a factory image" thread in general. Just remember, dont follow it blindly as you'll flash the whole factory image.
Click to expand...
Click to collapse
Promise this is the last question I hope. I am actually on that page. I have downloaded the factory image BUT when I extract it via Winrar I only get a one file as an output (hammerhead-kot49h-factory-02006b99)
EDIT: I renamed the extracted file to .zip and extracted again, now I have the files displayed on that page...Trying to figure out now how to flash the cache.img
Ensifolk said:
Promise this is the last question I hope. I am actually on that page. I have downloaded the factory image BUT when I extract it via Winrar I only get a one file as an output (hammerhead-kot49h-factory-02006b99)
Click to expand...
Click to collapse
Extract it again.
Ensifolk said:
Promise this is the last question I hope. I am actually on that page. I have downloaded the factory image BUT when I extract it via Winrar I only get a one file as an output (hammerhead-kot49h-factory-02006b99)
Click to expand...
Click to collapse
Its a .tar file. Extract it again
...
I successfully flashed cache.img But the problem is still there in my recovery, can't mound /sdcard
Think I have to flash the whole factory image ? :-/
Ensifolk said:
I successfully flashed cache.img But the problem is still there in my recovery, can't mound /sdcard
Think I have to flash the whole factory image ? :-/
Click to expand...
Click to collapse
Maybe. Can you mount /data?
If so you can adb pull your photos etc off there from data/media/0 - otherwise no such luck
You can find instructions here if you need: http://forum.xda-developers.com/showthread.php?t=2534010
Ensifolk said:
I successfully flashed cache.img But the problem is still there in my recovery, can't mound /sdcard
Think I have to flash the whole factory image ? :-/
Click to expand...
Click to collapse
I think you'v nothing to loose by flashing the whole factory image. If /sdcard can't be mounted in this situation, I think that's because you did (or a toolkit) did something wrong and break it. I don't think that you'll be able to save anything.
(It's my point of view. Maybe somebody else has an idea ?)
rootSU said:
Maybe. Can you mount /data?
If so you can adb pull your photos etc off there from data/media/0 - otherwise no such luck
You can find instructions here if you need: http://forum.xda-developers.com/showthread.php?t=2534010
Click to expand...
Click to collapse
I cannot mount /data even after flashing cache.img - Hence I think I am dead by this stage and I can no more recover whatever I have on the phone. Factory image flashing then ?
Yep, I would
And there we go, I did it, phone back to life. Thank you guys ! A LOT! Appreciated ! pretty much !
Allow me to recall the scenario : I was on Slimkat, decided to try Mahdi Rom ( CM Based ), Backup before flashing, flashed, wanted to revert back. And this can't mount /sdcard there. No idea what could be it...
What recovery you guys recommend me to use ? - Lesson I learned today? I should know how to use fastboot and ditch the Toolkit galore.
Well, seems that you did'nt do anything wrong. Maybe a problem with the rom or something else occur.
Next time, maybe, do a backup and, then, copy it to your computer
For the recovery, I use CWM 6.0.0.4
Nexus 5 wont boot into Paranoid android, i was obviously rooted with CWM installed, i wiped the device installed a fresh copy of paranoid android then decided to do a internal storage wipe the fastboot oem unlock way. I did the wipe and rebooted but its stuck in Paranoid androids bootanimation? Can anyone help here?
Garner said:
Nexus 5 wont boot into Paranoid android, i was obviously rooted with CWM installed, i wiped the device installed a fresh copy of paranoid android then decided to do a internal storage wipe the fastboot oem unlock way. I did the wipe and rebooted but its stuck in Paranoid androids bootanimation? Can anyone help here?
Click to expand...
Click to collapse
Push or sideload a custom rom or flash the stock image i`d say. Or try a data factory reset in recovery first.
gee2012 said:
Push or sideload a custom rom or flash the stock image i`d say.
Click to expand...
Click to collapse
Thanks, I have done it the above way for some time now with various nexus devices, cant understand why its failed this time?
Garner said:
Thanks, I have done it the above way for some time now with various nexus devices, cant understand why its failed this time?
Click to expand...
Click to collapse
Maybe the OS got corrupted by the lock/unlock action. I personaly would never recommend that anyway.
gee2012 said:
Maybe the OS got corrupted by the lock/unlock action. I personaly would never recommend that anyway.
Click to expand...
Click to collapse
Possibly, what i did notice was that when it entered recovery after oem unlock CWM threw alot of mount errors up
Garner said:
Possibly, what i did notice was that when it entered recovery after oem unlock CWM threw alot of mount errors up
Click to expand...
Click to collapse
I would start from scratch and flash the stock image including userdata.img for a full wipe to erase all errors.
gee2012 said:
I would start from scratch and flash the stock image including userdata.img for a full wipe to erase all errors.
Click to expand...
Click to collapse
Gather i need the stock image from here https://developers.google.com/android/nexus/images#hammerhead never had to return to stock like this before
Garner said:
Gather i need the stock image from here https://developers.google.com/android/nexus/images#hammerhead never had to return to stock like this before
Click to expand...
Click to collapse
Yup KOT49H, good luck mate. Hope that will fix it.
gee2012 said:
Yup, good luck mate. Hope that will fix it.
Click to expand...
Click to collapse
Quick question can i flash paranoid android from adb sideload never used that feature before?
Garner said:
Nexus 5 wont boot into Paranoid android, i was obviously rooted with CWM installed, i wiped the device installed a fresh copy of paranoid android then decided to do a internal storage wipe the fastboot oem unlock way. I did the wipe and rebooted but its stuck in Paranoid androids bootanimation? Can anyone help here?
Click to expand...
Click to collapse
You have to do a facotry reset in cwm. I dont really know how cwm works but in twrp there are two options to wipe /data. The first ine actually wipes /data and reformats it while the second option just delete every file and folder except the /data/media folder which is the sdcard. You need to find the first option in cwm. Normally after unlock bl you should let the android boot up because the stock recovery does the formation right after the first boot of oem unlock.
Tapatalk-kal küldve az én Nexus 5-el
Garner said:
Quick question can i flash paranoid android from adb sideload never used that feature before?
Click to expand...
Click to collapse
Sure, but you would also flash the Gapps then in sideload too i guess. I would flash stock first however to restore the phone and partitions back to normal.
bitdomo said:
You have to do a facotry reset in cwm. I dont really know how cwm works but in twrp there are two options to wipe /data. The first ine actually wipes /data and reformats it while the second option just delete every file and folder except the /data/media folder which is the sdcard. You need to find the first option in cwm. Normally after unlock bl you should let the android boot up because the stock recovery does the formation right after the first boot of oem unlock.
Tapatalk-kal küldve az én Nexus 5-el
Click to expand...
Click to collapse
Did fastboot reboot but it just booted to recovery
Garner said:
Did fastboot reboot but it just booted to recovery
Click to expand...
Click to collapse
Try fastboot reboot bootloader.
Garner said:
Did fastboot reboot but it just booted to recovery
Click to expand...
Click to collapse
I think that fastboot reboot command overwrote the commands stored in the /misc partition which tells the phone to start recovery and to a factory reset.
Tapatalk-kal küldve az én Nexus 5-el
bitdomo said:
I think that fastboot reboot command overwrote the commands stored in the /misc partition which tells the phone to start recovery and to a factory reset.
Tapatalk-kal küldve az én Nexus 5-el
Click to expand...
Click to collapse
Now when it goes to reboot it says root is missing? root device?
Garner said:
Now when it goes to reboot it says root is missing? root device?
Click to expand...
Click to collapse
Yes, press install root if you flashed PA.
Garner said:
Now when it goes to reboot it says root is missing? root device?
Click to expand...
Click to collapse
You wiped /system too that is the reasone why the recovery tells you to install root and you stucked at pa boot logo. here are the 3 options you can do now:
adb push a rom zip to /sdcard
turn on adb sideload in recovery and adb sideload a rom zip
Enter to fastboot and flash factory images back.
for both adb you have to be in recovery and you have to install universal naked usb drivers 0.73 http://forum.xda-developers.com/showthread.php?t=2386956
Fot fastboot to flash factory images you need the latest usb drivers from google http://developer.android.com/sdk/win-usb.html and you need a factory image https://developers.google.com/android/nexus/images
All three method need to have adb and fastboot exes to be added to your path. If you havent done that read this topic http://forum.xda-developers.com/showthread.php?t=2588979
To flash factory images extract the downloaded file and double click on flash-all.bat
Tapatalk-kal küldve az én Nexus 5-el
gee2012 said:
Yes, press install root if you flashed PA.
Click to expand...
Click to collapse
Stuck on google logo just waiting for the official image to download 1 to 2 hours lol
bitdomo said:
You wiped /system too that is the reasone why the recovery tells you to install root and you stucked at pa boot logo. here are the 3 options you can do now:
adb push a rom zip to /sdcard
turn on adb sideload in recovery and adb sideload a rom zip
Enter to fastboot and flash factory images back.
for both adb you have to be in recovery and you have to install universal naked usb drivers 0.73 http://forum.xda-developers.com/showthread.php?t=2386956
Fot fastboot to flash factory images you need the latest usb drivers from google http://developer.android.com/sdk/win-usb.html and you need a factory image https://developers.google.com/android/nexus/images
All three method need to have adb and fastboot exes to be added to your path. If you havent done that read this topic http://forum.xda-developers.com/showthread.php?t=2588979
To flash factory images extract the downloaded file and double click on flash-all.bat
Tapatalk-kal küldve az én Nexus 5-el
Click to expand...
Click to collapse
Turned on adb sideload tried "adb sideload para" but cmd does not understand the command?
bitdomo said:
for both adb you have to be in recovery and you have to install universal naked usb drivers 0.73 http://forum.xda-developers.com/showthread.php?t=2386956
All three method need to have adb and fastboot exes to be added to your path. If you havent done that read this topic http://forum.xda-developers.com/showthread.php?t=2588979
Click to expand...
Click to collapse
@Garner
Tapatalk-kal küldve az én Nexus 5-el
Hi, I have had this issue for a while now where my custom recovery looses the ability to mount data, this is the message I get,
E: could not mount /data to set up /data/media path. When the problem occurs which can be going into to recovery from any custom rom I just reboot the phone again which has always rebooted ok, but I am worried that it may not reboot ok some time in the future breaking my phone.
I have tried all 3 custom recovery's so I don't think it's a recovery problem, anyone have any ideas what the problem may be.
Usually a problem with /cache. Wipe it a few times or fastboot flash stock cache.img
Sent from my Nexus 5 using Tapatalk
rootSU said:
Usually a problem with /cache. Wipe it a few times or fastboot flash stock cache.img
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Thanks, can I fastboot flash stock cache.img on any rom ?
maxal said:
Thanks, can I fastboot flash stock cache.img on any rom ?
Click to expand...
Click to collapse
Yeah, any ROM
Sent from my Nexus 5 using Tapatalk
rootSU said:
Yeah, any ROM
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Ok I have just done fastboot flash stock cache.img and I get a failed (remote: partition table doesn't exist) any idea what is wrong now.
maxal said:
Ok I have just done fastboot flash stock cache.img and I get a failed (remote: partition table doesn't exist) any idea what is wrong now.
Click to expand...
Click to collapse
fastboot flash cache cache.img
Tapatalk-kal küldve az én Nexus 5-el
maxal said:
fastboot flash stock cache.img
Click to expand...
Click to collapse
This wasn't the command. This was me telling you what to do. As you're already rooted, I expected you would know the command. See @bitdomo posted.
Please read up about fastboot
Sent from my Nexus 5 using Tapatalk
rootSU said:
This wasn't the command. This was me telling you what to do. As you're already rooted, I expected you would know the command. See @bitdomo posted.
Please read up about fastboot
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Thanks fastboot command worked that time. I normally use adb and fastboot commands but I have never had to use cache.img command before, Thanks again :good:
Update: I tried what rootSU said but it didn't resolve my problem so I tried one last thing which was to flash a factory image using the LG Flashtool and so far every thing seems fine. So should anyone else have the same problem that I had with their recovery give the LG Flashtool ago. Should my original fault reoccur I will post an update.
For what it's worth, I had the same issue as the OP. I didn't want to flash the .tot, because my computer was being weird(it said COM41 was in use, because I already used the LGFT for my G2, didn't want to risk it). Basically I just RMAed it, because all fixes were failing. Using e2fsck, flashing stock cache, etc. I could temporarily fix it by flashing a factory image, but when I flashed a new ROM, it would happen again. So if it keeps happening, just send it back. :good:
I would like to add to what Koopa777 said that flashing a factory image was just a tempory fix as I tried this several times, but so far so good the data issue has not re occured since I used the LG Flashtool.
maxal said:
I would like to add to what Koopa777 said that flashing a factory image was just a tempory fix as I tried this several times, but so far so good the data issue has not re occured since I used the LG Flashtool.
Click to expand...
Click to collapse
Cool, I'll keep that in mind in case the new one gets it. Could you try something for me though? PA 4.2 BETA 5 always set it off for me. It booted fine, but the recovery was always borked when I rebooted into recovery. If your's survives that, I think that it could definitely be the fix. :good:
Koopa777 said:
Cool, I'll keep that in mind in case the new one gets it. Could you try something for me though? PA 4.2 BETA 5 always set it off for me. It booted fine, but the recovery was always borked when I rebooted into recovery. If your's survives that, I think that it could definitely be the fix. :good:
Click to expand...
Click to collapse
No problem I will test PA 4.2 beta tomorrow for you.
I had the same problem on an installation of a kernel that didn't boot atop a CM rom. When it bootlooped, I went into recovery and found the infamous could not mount /data. I tried rootSU's recommendation about wiping cache several times and flashing a cache.img but it didn't work for me. I was about to do the whole factory stock image thing (and thus wipe my sdcard) when out of desperation to avoid that, I tried something that surprisingly succeeded. The following steps are for a newbie but presupposes a working knowledge of how to use adb and fastboot commands.
1. Download and copy a known stable ROM's zip file into your SDK's platform-tools, renaming it ROM.zip
2. Boot you phone into (TWRP 2.7.0.0) recovery
2. Choose ADB sideload in Advanced
3. From your computer's DOS prompt in the SDK platform-tools directory, type adb sideload ROM.zip
When it's done sideloading, it will flash
4. Choose reboot system
It will boot and get a series of FC's of android process and dialer
5. Hard reset into bootloader (hold down the power button until screen goes off (in like 7 secs) immediately hit vol-down) and choose recovery
Voila! Rebooted into recovery for me with data mounted as normal. No need to flash factory images!
Hope this helps and good luck!
I know that this thread is nearly a year old, but just wanted to report that my phone soft bricked when I flashed a kernel (without flashing the rom). TWRP (2.8.5) was unable to mount data, storage, /data/media. When I went into TWRP/Advanced/File Manager there was nothing in the sd card. After an ADB flash cache cache.img it was still the same. I decided to follow the @reeper000 post and it booted into the ROM i flashed (Slim Lollipop version) and it came up with only a couple errors. I was then able to go into TWRP and restore a nandroid backup and all is fine. I was sooooooo close to erasing data/restoring to a factory image!!!!!! THANKS, @reaper000!
Glad all well. I had 2 nasty surprises yesterday. First I flashed a nandroid
, only one I had. It kept going past 100 %on loading the data. Went to 300%! I'd one rom with Gapps I'd not tried so I thought saved.. Aghhhhhh Noo when it came on said playstore support missing. Had to tap like mad to get it off the screen in between putting my acc in. 2 hours later it linked and downloaded the missing file. Thank god. Then my baseband went! I was at my wits end. Decided I'd nothing to loose with a factory reset which fixed it. Good job as the new battery came today! Now I test backups and have two different ones
So I bought my shield tablet back in March, used it until about may I think. Was browsing the internet then it suddenly crashed and got stuck on the Nvidia boot screen. tried to reboot several times. Nothing. So I forgot about it and thought I would just google the reset option later when I had time. Now since June I have tried everything! From factory reset to fast boot and adb my pc won't even recognize my tablet. Also I never turned on usb dbugging cause I didn't even know what that was. I even gave it to the IT guys at work and they couldn't fix it. Now after reading everything there is to read on this problem and trying to fix it myself I'm stuck on the no command screen with the dead android robot. And now I hear there is a recall do to the battery, I can't even check what type I have. So if someone can please help me I would be much appreciative. Also this happened after updating to the latest OS.
okay so i was able to unlock the bootloader and start flashing but from fastboot flash recovery.img and beyond it says failed to write. any ideas of why?
Ace0169 said:
okay so i was able to unlock the bootloader and start flashing but from fastboot flash recovery.img and beyond it says failed to write. any ideas of why?
Click to expand...
Click to collapse
Can you flash twrp and boot to it?
Ace0169 said:
okay so i was able to unlock the bootloader and start flashing but from fastboot flash recovery.img and beyond it says failed to write. any ideas of why?
Click to expand...
Click to collapse
Hello,
Did you use "Fastboot flash recovery.img" as your command line??
I believe it is "Fastboot flash recovery recovery.img"
If you were able to unlock bootloader you're on the right track.
Sent from a Locked Bootloader
Yes I used "fastboot flash recovery recovery.img" but every command after that keeps telling me "failed to write file"
danjull said:
Can you flash twrp and boot to it?
Click to expand...
Click to collapse
I'm a complete noob when it comes to this stuff, what is twrp? Haha
Ace0169 said:
I'm a complete noob when it comes to this stuff, what is twrp? Haha
Click to expand...
Click to collapse
TWRP (Team Win Recovery Project) is a custom recovery that you can flash on your device. You can flash it like the stock recovery over fastboot. With TWRP you can make full system backups, installing roms or other stuff, wipe partitions and more. Keep trying to install the drivers on your pc. Try to use another usb slot or boot your pc into test mode to install the driver. If you can still access the bootloader, you have really good chances to rescue your device.
Okay will try that. Thanks man.
Ace0169 said:
Okay will try that. Thanks man.
Click to expand...
Click to collapse
I see what your doing wrong. You probably don't even have the recovery img to flash. That's why it's giving you a write error.
There is a tutorial in the general section, that should have all the files and links, etc etc that you'll need to flash TWRP/CWM recovery and root the device if you want
Here is the link:
http://forum.xda-developers.com/shi...k-recovery-images-ota-library-guides-t2988881
Sent from my Nexus 5
Mojar7070 said:
I see what your doing wrong. You probably don't even have the recovery img to flash. That's why it's giving you a write error.
There is a tutorial in the general section, that should have all the files and links, etc etc that you'll need to flash TWRP/CWM recovery and root the device if you want
Here is the link:
http://forum.xda-developers.com/shi...k-recovery-images-ota-library-guides-t2988881
Sent from my Nexus 5
Click to expand...
Click to collapse
If your referring to the recovery images from Nvidia website I have dowloaded that, also the correct drivers. Maybe there is something else I'm missing?
Ace0169 said:
If your referring to the recovery images from Nvidia website I have dowloaded that, also the correct drivers. Maybe there is something else I'm missing?
Click to expand...
Click to collapse
First off, let me ask, what is your end result for the tablet?? Are you trying to just go a Complete stock tablet or are you trying to do anything custom (ex. Custom rom, recovery etc etc)
I'm assuming that since you unlocked your Bootloader, your trying to do something custom.
Sent from a Locked Bootloader
Ace0169 said:
If your referring to the recovery images from Nvidia website I have dowloaded that, also the correct drivers. Maybe there is something else I'm missing?
Click to expand...
Click to collapse
Those official nVidia recovery images come with smaller .img files such as recovery.img, system.img, etc. You'll need to flash those one by one ("fastboot flash recovery recovery.img", then run "fastboot flash system system.img", etc. etc.) or you can just run the flashall script that I think is included in the nVidia images.
Otherwise, if you want to flash TWRP, you'll need to download the TWRP recovery (you can rename it to "twrp-recovery.zip"). Then you'll need to "fastboot flash twrp-recovery.zip" in order to flash the twrp recovery to your tablet.
Mojar7070 said:
First off, let me ask, what is your end result for the tablet?? Are you trying to just go a Complete stock tablet or are you trying to do anything custom (ex. Custom rom, recovery etc etc)
I'm assuming that since you unlocked your Bootloader, your trying to do something custom.
Sent from a Locked Bootloader
Click to expand...
Click to collapse
I want my tablet to boot again, it's completely unusable in its condition I've heard re flashing will fix it.
Ace0169 said:
I want my tablet to boot again, it's completely unusable in its condition I've heard re flashing will fix it.
Click to expand...
Click to collapse
OK. Then the link I gave earlier should help flash stock software onto your tablet.
However, that guide is only to go back to factory "state" Operating System wise. It may not help with hardware. Once your flash everything correctly but device still doesn't boot, its probably not software related.
Sent from my Nexus 5
Mojar7070 said:
OK. Then the link I gave earlier should help flash stock software onto your tablet.
However, that guide is only to go back to factory "state" Operating System wise. It may not help with hardware. Once your flash everything correctly but device still doesn't boot, its probably not software related.
Sent from my Nexus 5
Click to expand...
Click to collapse
so ive followed the steps in the link, and ive executed all the commands but when i get to fasboot flash system system.img it says write failed. also all the commands beyond that one. ive got to be missing something. i have the image from nvidia developer, all the drivers, and my fastboot recognizes my device. has anyone encountered this before?
Ace0169 said:
so ive followed the steps in the link, and ive executed all the commands but when i get to fasboot flash system system.img it says write failed. also all the commands beyond that one. ive got to be missing something. i have the image from nvidia developer, all the drivers, and my fastboot recognizes my device. has anyone encountered this before?
Click to expand...
Click to collapse
After you unlocked the device but before trying to flash anything else on the device, try putting the shield into Fastboot mode. At the bootloader, select fastboot using the volume buttons.
koop1955 said:
After you unlocked the device but before trying to flash anything else on the device, try putting the shield into Fastboot mode. At the bootloader, select fastboot using the volume buttons.
Click to expand...
Click to collapse
Select "fastboot protocol"? Is that correct?
Ace0169 said:
Select "fastboot protocol"? Is that correct?
Click to expand...
Click to collapse
So i selected "fastboot protocol" it blipped for a second then brought me back to the bootloader. tried flashing again and once i reached the fastboot flash system system.img it said write failed again. did it not engage the "fastboot protocol"?
Bringing you back to the bootloader was expected behavior. The "write fail" is a mystery to me. Sorry, that is all that I can offer.
koop1955 said:
Bringing you back to the bootloader was expected behavior. The "write fail" is a mystery to me. Sorry, that is all that I can offer.
Click to expand...
Click to collapse
@Ace0169 Same, not sure what else to tell you. Sorry sir.
Sent from a Locked Bootloader
So I got a pixel recently. I unlocked the bootloader, installed TWRP, and rooted it. However, it's been a few years since I had an unlocked and rooted phone so I forgot that the OTA updates can't be applied. So I decided to go back to the factory image. A quick google search lead me to an article where they said I could select the Full Unroot option in the settings of SuperSU and it would attempt to restore the stock boot image and recovery image. So I did that, and ended up in a boot loop.
Well, then I decided to try flashing the entire factory images from google, using the flash-all.bat file they provide. It seems to flash the bootloader and the radio fine, but when it comes to the part where it flashes everything in the "image-sailfish-nde63l.zip" (I picked this build because it was the one I was on when the pixel arrived) folder it says "Error: failed to load 'image-sailfish-nde63l.zip': not enough space."
I can still get to the TWRP recovery, and I can get to the bootloader, but currently nothing else seems to work. Please, can anyone help me?
UPDATE: The issue was outdated adb and fastboot. I had 1.0.32, once I had the latest versions (1.0.36 right now) I could fix everything.
UPDATE: So I extracted boot and system from the zip file and manually flashed those. It boots now, but when it does it says there are errors with the device and to contact the manufacturer, also a lot of dialog boxes pop up saying various processes have stopped.
I think that if I manually flash the rest of the contents of the zip folder it will work, but there are a lot of files and I'm not sure which partition to flash them too, or which one's are needed. Does anyone know how to manually do what the flash-all.bat script does? Flashing bootloader, radio, system, and boot are not enough it seems. If you read the script it's just doing a 'fastboot -w update' on the zip file.
I hope what I'm saying makes sense. Thanks.
Did you try flashing the stock boot.img to both slots before going back to stock?
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
This is what chainfire recommended in his supersu post when he was talking about flashing twrp. Maybe try doing that and then try using the flashall script. Also make sure your download is not corrupt or something. https://plus.google.com/+Chainfire/posts/CBL8pnKtA8F
Evo_Shift said:
Did you try flashing the stock boot.img to both partitions before going back to stock?
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
This is what chainfire recommended in his supersu post when he was talking about flashing twrp. Maybe try doing that and then try using the flashall script. Also make sure you download is not corrupt or something.
Click to expand...
Click to collapse
No, I didn't do any flashing myself before going back to stock. I selected the "Full unroot" option in SuperSU, based on the first result when googling "unroot pixel".
As soon as I did that I was stuck in a bootloop and I tried to restore the factory images according to the google webpage, but that's when I get the error.
Doing what you said doesn't work either, not even redownloading the image.
Actually, now it's worse. When I select recovery from fastboot menu it shows "No command" with a broken android. So twrp is gone now too.
If anyone can help me at all, that would be amazing, thanks.
UPDATE: So I extracted boot and system from the zip file and manually flashed those. It boots now, but when it does it says there are errors with the device and to contact the manufacturer, also a lot of dialog boxes pop up saying various processes have stopped.
I think that if I manually flash the rest of the contents of the zip folder it will work, but there are a lot of files and I'm not sure which partition to flash them too, or which one's are needed. Does anyone know how to manually do what the flash-all.bat script does? Flashing bootloader, radio, system, and boot are not enough it seems. If you read the script it's just doing a 'fastboot -w update' on the zip file.
I hope what I'm saying makes sense. Thanks.
th3p3r50n said:
Actually, now it's worse. When I select recovery from fastboot menu it shows "No command" with a broken android. So twrp is gone now too.
If anyone can help me at all, that would be amazing, thanks.
Click to expand...
Click to collapse
This happened to me too. That's my current situation. Have adb and fastboot still but can't figure out what steps to fix it.
I think you should focus on why the flash all didn't work. Do you have the latest fastboot? Did you check the md5 of the downloaded rom image? What OS it's your computer running?
How do we verify latest fastboot. I thought that was my issue but don't see where this can be found. I have latest minimal adb and fastboot installed.
fracman said:
How do we verify latest fastboot. I thought that was my issue but don't see where this can be found. I have latest minimal adb and fastboot installed.
Click to expand...
Click to collapse
The commands <adb version> and <fastboot --version> seem to return version numbers. My setup returns:
Android Debug Bridge version 1.0.36
Revision fd9e4d07b0f5-android
and
fastboot version fd9e4d07b0f5-android
respectively
Thank you cntryby429. I assumed I was using the latest versions because I had just installed them through the SDK Manager, turns out I was using version 1.0.32. I found the latest version of Minimal ADB and Fastboot and the flash-all script worked fine. I still had a few issues though, so I did a factory reset and then ran the flash-all script again. Now everything works perfectly again. Thanks so much!