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
Related
Hi everyone,
I am French and I use a translator to talk to you, sorry for language mistakes.
I just ask for your help because at last my nexus one days is blocked.
When I go into TWRP he asks me a passeword and my internal memory shows 0MB
Unable to flash a rom stock, steps go well but it does not change anything in the nexus.
Unable to update bootloader, the old version back
I focused in fastboot and recovery (TWRP)
Do you have a solution?
Thanking you in advance
Loïc
Sounds like uv messed up the partitions. unsure if theres a fix on this
Try
fastboot flash cache cache.img
Where cache.img is from the factory image
jd1639 said:
Try
fastboot flash cache cache.img
Where cache.img is from the factory image
Click to expand...
Click to collapse
This is happening without any problems but it does not change the problem.
I'm lost ...
in TWRP i have
E:Unable to mount ' /cache'
E:Unable to mount ' /persist'
E:Unable to mount storage
Problems:
Internal-memory found in TWRP (internal storage: 0MB)
-In flash, everything seems to work well but the file does not replace those on the laptop (eg when I erase bootloader and flash I HHZ11K to replace HHZ11D there was the nexus, the ben 11D never deletes
-Unable to wipe dalvik Cache
TWRP-request a password, so I'm Cancel to use the recovery
Impossible to replace the recovery with a stock version everything seems ok but always returns TWRP
Thank you for your help
worfeur said:
Problems:
Internal-memory found in TWRP (internal storage: 0MB)
-In flash, everything seems to work well but the file does not replace those on the laptop (eg when I erase bootloader and flash I HHZ11K to replace HHZ11D there was the nexus, the ben 11D never deletes
-Unable to wipe dalvik Cache
TWRP-request a password, so I'm Cancel to use the recovery
Impossible to replace the recovery with a stock version everything seems ok but always returns TWRP
Thank you for your help
Click to expand...
Click to collapse
What version of twrp are you using?
jd1639 said:
What version of twrp are you using?
Click to expand...
Click to collapse
I use twrp 2.6.3.2
worfeur said:
I use twrp 2.6.3.2
Click to expand...
Click to collapse
Try to flash this in fastboot, fastboot flash recovery recovery.img. Where recovery.img is the file below. If it installs, wipe cache within it
http://d-h.st/nbu. It's 2.6.3.4
This very same thing happened to me this morning, and a friends Nexus 5 the other day. Not sure why but the fact that you are the third I have seen in the last few days is making me believe it's a common issue. It happened to me, I watched a movie, fell asleep, and woke up to "Type password to decrypt storage" message, and the same message you have in Recovery as well. To my knowledge, I never set a password, let alone while I slept.
What happened is somehow the "userdata" partition on the phone got corrupt. When this happens, for some reason it thinks the partition was encrypted. You can attempt to fix it with a repair utility, or
Go to the bootloader (Hold Volume Down and Power when turning the phone on) then install and use adb and type this
Code:
adb e2fsck /dev/block/platform/msm_sdcc.1/by-name/userdata
Or from recovery, run a command and and run
Code:
e2fsck /dev/block/platform/msm_sdcc.1/by-name/userdata
See if that works. If it does, your data will be fine. I did not find this fix until after I tried a full reset but it worked for my friend.
If that does not work, you will have to factory reset your phone. You will lose all data on the phone. Hopefully you have a backup. This worked for me.
Use tools from here:
https://developers.google.com/android/nexus/images#hammerhead
and follow instructions here http://forum.xda-developers.com/showthread.php?t=2513701
I see you mentioned you tried this, however you may want to try it again, and follow those steps, make sure to go to the Nexus 5's factory recovery after and "Reset to Factory". Likewise it needs to be run from bootloader, not recovery. And you must have unlocked bootloader.
**EDIT** What firmware were you running? CyanogenMod?
N5
1. you unlock it
2. recovery with software.
Thanks
Wergin said:
1. you unlock it
2. recovery with software.
Thanks
Click to expand...
Click to collapse
What firmware were you using prior to this happening? I would like to know as me and a friend were on CyanogenMod11 (CM11) and this happened to us as well. If CyanogenMod or TWRP is causing it, it should be reported as a bug.
worfeur said:
Hi everyone,
I am French and I use a translator to talk to you, sorry for language mistakes.
I just ask for your help because at last my nexus one days is blocked.
When I go into TWRP he asks me a passeword and my internal memory shows 0MB
Unable to flash a rom stock, steps go well but it does not change anything in the nexus.
Unable to update bootloader, the old version back
I focused in fastboot and recovery (TWRP)
Do you have a solution?
Thanking you in advance
Loïc
Click to expand...
Click to collapse
Why don't you try Clock work mod recovery. Sounds like twrp isn't meshing well with you device. I had issues with all the way to lastest version.Maybe CWM might help.
WoodburyMan said:
What firmware were you using prior to this happening? I would like to know as me and a friend were on CyanogenMod11 (CM11) and this happened to us as well. If CyanogenMod or TWRP is causing it, it should be reported as a bug.
Click to expand...
Click to collapse
Sorry, I do not know the firmware that was installed
It is a device used
habitformer said:
Why don't you try Clock work mod recovery. Sounds like twrp isn't meshing well with you device. I had issues with all the way to lastest version.Maybe CWM might help.
Click to expand...
Click to collapse
when I flash a custom-recovery (stock or cwn) TWRP 2.6.3.2 always returns
I had this same issue.
I went into fastboot and erased recovery and userdata, then ran the flashall.bat in the factory image.
TWRP had a Password. It happened after I tried to flash Cataclysm and it bootlooped (Forgot to check MD5's, not sure why a corrupt download flashed).
WoodburyMan said:
This very same thing happened to me this morning, and a friends Nexus 5 the other day. Not sure why but the fact that you are the third I have seen in the last few days is making me believe it's a common issue. It happened to me, I watched a movie, fell asleep, and woke up to "Type password to decrypt storage" message, and the same message you have in Recovery as well. To my knowledge, I never set a password, let alone while I slept.
What happened is somehow the "userdata" partition on the phone got corrupt. When this happens, for some reason it thinks the partition was encrypted. You can attempt to fix it with a repair utility, or
Go to the bootloader (Hold Volume Down and Power when turning the phone on) then install and use adb and type this
Code:
adb e2fsck /dev/block/platform/msm_sdcc.1/by-name/userdata
Or from recovery, run a command and and run
Code:
e2fsck /dev/block/platform/msm_sdcc.1/by-name/userdata
See if that works. If it does, your data will be fine. I did not find this fix until after I tried a full reset but it worked for my friend.
If that does not work, you will have to factory reset your phone. You will lose all data on the phone. Hopefully you have a backup. This worked for me.
Use tools from here:
https://developers.google.com/android/nexus/images#hammerhead
and follow instructions here http://forum.xda-developers.com/showthread.php?t=2513701
I see you mentioned you tried this, however you may want to try it again, and follow those steps, make sure to go to the Nexus 5's factory recovery after and "Reset to Factory". Likewise it needs to be run from bootloader, not recovery. And you must have unlocked bootloader.
**EDIT** What firmware were you running? CyanogenMod?
Click to expand...
Click to collapse
thank you for your help
I have access to adb fastboot mode by boot recovery.img (recovery stock google)
and using the control slidload ADB
but impossible to get the command line
but when I type ADB Devices, my phone is found
otherwise I can not do a stock restoration because the bootloader does not update (KKX11D then I flashed back KKX11K) when I do well:
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
Beauenheim said:
I had this same issue.
I went into fastboot and erased recovery and userdata, then ran the flashall.bat in the factory image.
TWRP had a Password. It happened after I tried to flash Cataclysm and it bootlooped (Forgot to check MD5's, not sure why a corrupt download flashed).
Click to expand...
Click to collapse
thank you I'll try it tonight but I think I already tried
worfeur said:
thank you I'll try it tonight but I think I already tried
Click to expand...
Click to collapse
In twrp 2.6.3.4 go into wipe and format data. You will lose all your data but should fix your problem
jd1639 said:
In twrp 2.6.3.4 go into wipe and format data. You will lose all your data but should fix your problem
Click to expand...
Click to collapse
the problem when another flash recovery is that the 2.6.3.2 version still returns
let me explain:
fastboot erase recovery
fastboot flash recovery recovery TWRP 2.6.3.4.img
* I go into the recovery but still 2.6.3.2
I feel that TWRP to secure or encrypted my internal memory
worfeur said:
the problem when another flash recovery is that the 2.6.3.2 version still returns
let me explain:
fastboot erase recovery
fastboot flash recovery recovery TWRP 2.6.3.4.img
* I go into the recovery but still 2.6.3.2
I feel that TWRP to secure or encrypted my internal memory
Click to expand...
Click to collapse
Can you format data in 2.6.3.2? I'm thinking you have a bigger problem as you've already tried to flash the factory image and it did not work.
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
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.
Hey everyone,
I've been tearing out my hair for the past 34 hours (with the exception of sleeping). I restarted my phone yesterday and it got stuck in the boot animation, for hours.
I have never unlocked my bootloader, or flashed any custom rom on this phone, so I was really shocked when this happened. So I took to these forums, because lurking here usually solves all my issues (thanks awesome people), and flashed the stock image as recommended-> bootloop -> factory reset in recovery mode -> bootloop-> repeated this all night and today with multiple flashing methods (fastboot using flash-all and flashing individually, no dice.
I was wondering if I was out of luck, seeing as though my phone just randomly did this to itself, without prior tampering, or if there was something I could try doing. I haven't tried any custom recoveries as I don't really know how that would help me if I am willing to flash back to stock and lose all my data.
I am able to boot into fastboot mode and go to recovery mode, so this indicates to me that my hardware is fine, unless I am wrong
Thanks, I would appreciate all the help I can get
Was fast boot one of those multiple flashing methods?
theesotericone said:
Was fast boot one of those multiple flashing methods?
Click to expand...
Click to collapse
Yeah, both using Flash-all and flashing each individual, Ill update post
ChunksOfLemon said:
Yeah, both using Flash-all and flashing each individual, Ill update post
Click to expand...
Click to collapse
And you didn't receive any errors at all while flashing them individually? If that's the case I'd fastboot format each partition first then flash it. If that doesn't work you're pretty much out of luck. Just so where on the same page it would go like this:
Code:
fastboot format system
fastboot flash system system.img
Then just repeat that for everything.
theesotericone said:
And you didn't receive any errors at all while flashing them individually? If that's the case I'd fastboot format each partition first then flash it. If that doesn't work you're pretty much out of luck. Just so where on the same page it would go like this:
Code:
fastboot format system
fastboot flash system system.img
Then just repeat that for everything.
Click to expand...
Click to collapse
I'll try this now and let you know
theesotericone said:
And you didn't receive any errors at all while flashing them individually? If that's the case I'd fastboot format each partition first then flash it. If that doesn't work you're pretty much out of luck. Just so where on the same page it would go like this:
Code:
fastboot format system
fastboot flash system system.img
Then just repeat that for everything.
Click to expand...
Click to collapse
Yeah, no luck there either
I guess I'll call LG in the morning
ChunksOfLemon said:
Yeah, no luck there either
I guess I'll call LG in the morning
Click to expand...
Click to collapse
First reboot to recovery and wipe cache.
theesotericone said:
First reboot to recovery and wipe cache.
Click to expand...
Click to collapse
Nothing is working, I'll check to see how much it'll be to repair
ChunksOfLemon said:
Nothing is working, I'll check to see how much it'll be to repair
Click to expand...
Click to collapse
Have you tried -> http://forum.xda-developers.com/google-nexus-5/general/guide-to-fix-persist-partition-t2821576 ?
beekay201 said:
Have you tried -> http://forum.xda-developers.com/google-nexus-5/general/guide-to-fix-persist-partition-t2821576 ?
Click to expand...
Click to collapse
OMG YES THIS WORKS! Thank you, I read that thread in my initial search, but it didn't seem to apply. But I just tried it and my device booted in like five minutes.
Thanks for helping me guys, don't need to buy another phone
My wife's Rooted Nexus 5, stock 6.0.1 phone has become unusable. After deleting some contacts she gets a popup that "Android.process.acore has stopped" every couple of seconds.
Searching for solutions on the web I've
Deleted her contacts data and cache
Deleted her contacts storage data and cache
Reset app preferences
Disabled contacts
And nothing stops it.
Is there a solution to this problem?
Thanks.
Is it possible to restore a working nandroid made on a different nexus 5 to the messed up nexus 5?
maybeme2 said:
My wife's Rooted Nexus 5, stock 6.0.1 phone has become unusable. After deleting some contacts she gets a popup that "Android.process.acore has stopped" every couple of seconds.
Searching for solutions on the web I've
Deleted her contacts data and cache
Deleted her contacts storage data and cache
Reset app preferences
Disabled contacts
And nothing stops it.
Is there a solution to this problem?
Thanks.
Is it possible to restore a working nandroid made on a different nexus 5 to the messed up nexus 5?
Click to expand...
Click to collapse
you need to flash again the stock rom. try using nexus toolkit.
https://forum.xda-developers.com/google-nexus-5/development/toolkit-wugs-nexus-root-toolkit-v1-8-3-t2517778
you can get the stock roms here.
https://forum.xda-developers.com/google-nexus-5/development/rom-android-m-preview-2-flashable-zip-t3157299
Thank you. I thought I might need to reflash the rom. I was trying to avoid it because flashing roms always makes me nervous. But I'll just have to do it.
Xposed is also installed on the phone. I assume I will need to uninstall that first too. Ugh!
maybeme2 said:
Thank you. I thought I might need to reflash the rom. I was trying to avoid it because flashing roms always makes me nervous. But I'll just have to do it.
Xposed is also installed on the phone. I assume I will need to uninstall that first too. Ugh!
Click to expand...
Click to collapse
Try flashing just the system image and not the whole rom. You'll be able to save all your apps and data that way.
Sent from my [device_name] using XDA-Developers Legacy app
jd1639 said:
Try flashing just the system image and not the whole rom. You'll be able to save all your apps and data that way.
Click to expand...
Click to collapse
That would be great!
Never done that. I'll search the web for just the 6.0.1 system image. I assume that's different from the "factory image" from https://developers.google.com/android/images
Could you point me in the right direction?
maybeme2 said:
That would be great!
Never done that. I'll search the web for just the 6.0.1 system image. I assume that's different from the "factory image" from https://developers.google.com/android/images
Could you point me in the right direction?
Click to expand...
Click to collapse
Download the factory image, it's a zip file. Extract it and inside is another zip file. Extract that too. Inside that are a number of .img files, one of which is the system.img. You'll use that one. Use fastboot to flash it, fastboot flash system system.img. If you've never used fastboot Google "15 second adb xda" The first thing that should pop up is a tool by Snoop05. That'll install fastboot and adb on your PC.
Sent from my [device_name] using XDA-Developers Legacy app
You are wonderful jd1639. Thank you very much.
What you suggested worked like a charm. I flashed the system.img successfully. Took no time.
Unfortunately, it did not solve the Android.process.acore bug.
So I decided to just flash the entire rom and go that route. That's where I ran into problems.
1. I did adb reboot bootloader
and then flash-all
which resulted in something about system img not found (even though I had moved everything into the same folder).
Now, the phone is now no longer rooted and I can no longer get into recovery. And adb reboot bootloader no longer works. I get "error device offline".
I'm not that knowledgeable in android and flashing and am stuck. What should I do?
Ok, solved the offline problem. Disconnected and reconnected the USB cable.
But still no go. Here's what I get with flash-all
For some reason my paste of the results won't show when I save.....
Essentially,
Ok, solved the offline problem. Disconnected and reconnected the USB cable.
But still no go. Here's what I get with flash-all
For some reason my paste of the results won't show when I save.....
Essentially, it says archive does not contain 'boot.sig', archive does not contain 'recovery.sig'.
Sorry, error.
maybeme2 said:
Sorry, error.
Click to expand...
Click to collapse
The no .sig stuff is normal and you don't need to worry about it. Just ignore it and let the flash continue and do its thing.
Let me know if that works.
Sent from my [device_name] using XDA-Developers Legacy app
Unfortunately, I can't ignore it because it stops with "press any key to exit". So I exit.
Wish you lived next door. I would be glad to pay you to do it.....
maybeme2 said:
Unfortunately, I can't ignore it because it stops with "press any key to exit". So I exit.
Wish you lived next door. I would be glad to pay you to do it.....
Click to expand...
Click to collapse
Does it flash anything before it gets to the press and key? It should flash the bootloader and modem before it gets to the .sig stuff. Or does it immediately go to the press any key? If it goes immediately to the press any key then it sound like the PC isn't recognizing the N5. If that's the case boot into the bootloader, press power and vol up and down keys at the same time. Once it boots into the bootloader then connect it to your PC. Then using fastboot issue the command, fastboot devices If your PC recognizes the N5 it'll spit out a long alpha/numeric number on your pc. About 16 characters long.
If you get the alpha/numeric then go to the folder of the second zip file you extracted. There should be boot, cache, etc image files. Then open a command window /power shell there and we'll flash all the partitions manually. Issue the following commands, one after the other once the previous one ends.
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash userdata userdata.img
If any of those don't work let me know which one.
Sent from my [device_name] using XDA-Developers Legacy app
Thank you again.
Thank you jd1639.
All the flashing worked when I did it sequentially as you suggested. Don't know why the batch file got stuck but no matter, you saved the day.
So it is now factory fresh. Please remind me how to root it.
Thank you so much for hanging in there to help a total stranger.
maybeme2 said:
Thank you jd1639.
All the flashing worked when I did it sequentially as you suggested. Don't know why the batch file got stuck but no matter, you saved the day.
So it is now factory fresh. Please remind me how to root it.
Thank you so much for hanging in there to help a total stranger.
Click to expand...
Click to collapse
No problem. To root download twrp for the N5. I Google teamwin nexus 5. It'll be a .img file. Also download supersu. Google supersu 2.82 sr5. To flash twrp boot into the bootloader and with fastboot flash it, fastboot flash recovery twrp.img. Twrp.img is the full file name of the download. Then boot into recovery (it'll be twrp). From recovery your PC will see the N5 and you'll be able to copy supersu to the download folder of the N5. Then flash it in twrp (install) supersu will be a zip file.
Sent from my [device_name] using XDA-Developers Legacy app
Problems never end.
1. I successfully flashed twrp.img using fastboot. But when I go to recovery I get the empty robot with the red exclamation mark. (No twrp recovery)
2. Other problem: the 32Gb nexus 5 now shows only 16Gb.
maybeme2 said:
Problems never end.
1. I successfully flashed twrp.img using fastboot. But when I go to recovery I get the empty robot with the red exclamation mark. (No twrp recovery)
2. Other problem: the 32Gb nexus 5 now shows only 16Gb.
Click to expand...
Click to collapse
Yep, you're having fun. The problem is twrp is not sticking. But first let's solve the memory issue, which is fairly common. The red ! Is the stock recovery. It's been awhile since I've messed with it so you might have to play around with it a little. When you get the ! Press and release the power and vol up keys. Timing is important so that's where the playing around comes in. It might be vol down or both vol. If you get it right it'll go into the stock recovery, don't ask why you need to mess with the keys and it won't just go into recovery and not go through the ! crap.
Anyway, once you get into recovery go to factory reset and reset the device. That will solve the memory issue.
Now to twrp, instead of flashing twrp you'll want to boot into it. Use fastboot and the command fastboot boot twrp.img. Once in twrp get supersu on your device and then flash it. Then go to reboot in twrp and boot into the bootloader. Then use fastboot to flash twrp, fastboot flash recovery twrp.img. Twrp should stick now.
Edit: to get into stock recovery it's power and both vol keys. Press, hold about 1/2 second, and release.
Sent from my [device_name] using XDA-Developers Legacy app
Yes I'm having fun...... (that's why non-experts are scared to do things which the experts say "not to it - which is true when everything works)
The 32Gb becoming 16 is a problem I encountered previously on another nexus 5. So I noted its solution : the fix is to wipe cache and data. Catch 22: how to do that when you can't get into recovery? I was going to search for a way to wipe cache and data using fastboot when I read your message.
I'll try to do what you advise. Fingers crossed.