I just got my Nexus 5 a while ago and I just unlocked the bootloader and flashed TWRP and as soon as I opened TWRP it basically crashed and rebooted the phone is a boot loop but now when I go to TWRP the log says Unable to mount /data and I can't do anything. Does anyone have the solution? I knew I shouldn't have rooted -_-
Have you flashed a stock cache.img yet? Thats usually the first thing to try.
Sent from my Nexus 5 using Tapatalk
Uhh
Not yet right now I'm currently using Wug's Toolkit and seeing if that helps then i'll try that. Do you have the link by any chance?
OH thank GAWD its working again thanks for your help though
what did you do in the toolkit?
Generally the consensus here is to not use toolkits. There are 2-3 "Johnny Opposite" members, but the masses of senior members see them as a bad thing.
I explain what happend.
You opened bootloader, but you flashed twrp instead of start the phone to let stock recovery finish the formating. You flashed twrp and rebooted to twrp. Twrp found the commands in the memory or on the misc partition to do a factory reset then reboot, but that format command is not compatible with twrp, so that commamd was skipped and then twrp rebooted your, because that was the next command in the line. Now your started booting with an unformated cache and data partition. The easiest way to solve the issue is to do a format data in twrp to format data partition then a factory reset to format cache.
So In the toolkit I basically flashed the stock rom and it basically factory reset EVERYTHING so now its working again thanks for the help! Now to try this over again
killerkyman said:
So In the toolkit I basically flashed the stock rom and it basically factory reset EVERYTHING so now its working again thanks for the help! Now to try this over again
Click to expand...
Click to collapse
Ok thanks. It is best to do those steps manually
Sent from my Nexus 5 using Tapatalk
Yeah so I forgot to reboot before flashing recovery and entering that so now that I crossed that bridge I don't have to worry Wooh thank goodness I thought I totally messed up
Related
Hi guys,
got my nexus 5 yesterday and wanted to flash AOSP. But at some time, something might have broken, because now I get a bootloop after factory reseting via Kwongger Nexus5 Toolkit, ADB sideload via CWM, via zip, ... I tried everything, wiped everything, erased anything via fastboot. When I boot into CWM, there are messages like "E: cant mount cache, invalid argument", so my prediction is, that something bad happened to partition table or likely.
Does anyone have any idea how I can fix this? I searched the whole internet up and down, comparing to other devices like nexus 4 which I use right now.
Every idea is well-appreciated ALOT :good:
Natural_born_chilla said:
Hi guys,
got my nexus 5 yesterday and wanted to flash AOSP. But at some time, something might have broken, because now I get a bootloop after factory reseting via Kwongger Nexus5 Toolkit, ADB sideload via CWM, via zip, ... I tried everything, wiped everything, erased anything via fastboot. When I boot into CWM, there are messages like "E: cant mount cache, invalid argument", so my prediction is, that something bad happened to partition table or likely.
Does anyone have any idea how I can fix this? I searched the whole internet up and down, comparing to other devices like nexus 4 which I use right now.
Every idea is well-appreciated ALOT :good:
Click to expand...
Click to collapse
Best thing to do imo atm is to flash a factory image in fastboot and reroot afterwards bro.
gee2012 said:
Best thing to do imo atm is to flash a factory image in fastboot and reroot afterwards bro.
Click to expand...
Click to collapse
Tried that like 500x times with different factory images, right from google, from toolkit etc., tried using fastboot, flash-all.bat from google factory images and flashed via adb sideload. Same thing everytime. Boot loop and it won't work ...
Edit: found this a minute ago http://forum.xda-developers.com/showpost.php?p=47170893&postcount=291
Natural_born_chilla said:
Tried that like 500x times with different factory images, right from google, from toolkit etc., tried using fastboot, flash-all.bat from google factory images and flashed via adb sideload. Same thing everytime. Boot loop and it won't work ...
Edit: found this a minute ago http://forum.xda-developers.com/showpost.php?p=47170893&postcount=291
Click to expand...
Click to collapse
Go into recovery and clear the caches and do a data factory reset and see if it boots, if it doesn`t go into fastboot and flash a Google factory image. A good advice = DO NOT USE TOOKITS. Good luck bro
So I just wiped my cache and dalvik in TWRP and now I have no radio, no IMEI, no storage.. I think it borked my partitions. Tried flashing the factory image to no avail. It failed on the radio and I still have no storage.
Is there any way to recover from this?
EDIT: I was able to fix it as easily as I caused it. Check the 4th post. More detailed instructions on the 3rd post of page 2.
_MetalHead_ said:
So I just wiped my cache and dalvik in TWRP and now I have no radio, no IMEI, no storage.. I think it borked my partitions. Tried flashing the factory image to no avail. It failed on the radio and I still have no storage.
Is there any way to recover from this?
Click to expand...
Click to collapse
There is no way you simply wiped cache and dalvik. That doesn't even come close to touching your IMEI.
Why did you go to clear your cache / dalvik in the first place? Describe anything you did in terms of installing apps, flashing, wiping, etc.
leblvin said:
There is no way you simply wiped cache and dalvik. That doesn't even come close to touching your IMEI.
Why did you go to clear your cache / dalvik in the first place? Describe anything you did in terms of installing apps, flashing, wiping, etc.
Click to expand...
Click to collapse
All I did was flash a zip to change the dpi of my navbar. I've flashed the same zip a couple times before. Wiped cache + dalvik and it hung up for a while, screen went black for 5 minutes then the phone rebooted into its current state. I realize that wiping the caches doesn't touch the IMEI or anything like that, but what if the version of TWRP I have is buggy?
So knowing that yes, that is all I did, is there any way to fix it?
After a bit of googling I got it fixed. Apparently sometimes TWRP will cause some havok with the partitions when wiping cache. I just updated to the latest TWRP, wiped the cache again and everything came back up. Weird.
Always run the very recovery latest version.
a hammerhead wrote this.
Might be worth backing up your EFS partition to be on the safe side!
Nandroid backup is your best friend
beekay201 said:
Always run the very recovery latest version.
a hammerhead wrote this.
Click to expand...
Click to collapse
Yup, didnt bother to check before.
EddyOS said:
Might be worth backing up your EFS partition to be on the safe side!
Click to expand...
Click to collapse
Agreed. First thing I'm gonna do when I get home from work.
gd6noob said:
Nandroid backup is your best friend
Click to expand...
Click to collapse
I have a recent nandroid. What good is it though if recovery can't see my storage where the nandroid was saved?
Sent from my Moto X
_MetalHead_ said:
After a bit of googling I got it fixed.
Click to expand...
Click to collapse
Well, whatever you do, don't share your find here in case someone else ever has the same problem.
GldRush98 said:
Well, whatever you do, don't share your find here in case someone else ever has the same problem.
Click to expand...
Click to collapse
I did share it. Read the rest of the post you quoted. Derp.
Sent from my Moto X
_MetalHead_ said:
lApparently sometimes TWRP will cause some havok with the partitions when wiping cache
Click to expand...
Click to collapse
I don't know about you, but this is just what I look for in a recovery
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
rootSU said:
I don't know about you, but this is just what I look for in a recovery
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
Click to expand...
Click to collapse
It's a TWRP exclusive feature.
_MetalHead_ said:
After a bit of googling I got it fixed. Apparently sometimes TWRP will cause some havok with the partitions when wiping cache. I just updated to the latest TWRP, wiped the cache again and everything came back up. Weird.
Click to expand...
Click to collapse
Big thank you for this, I thought I was boned. I was trying to flash 4.4.1 but forgot that I had modified the screen density in the build.prop and so I got an error, tried to wipe the cache, thought it had hung up, got impatient and VERY stupid and forced the phone to reboot. SDCard was entirely inaccessible, couldn't connect to AT&T, everything was screwed up and everything I could find told me that wiping everything back to stop and losing the data was my only option. I had a week-old TiBu on my dropbox, which isn't bad but not great either. Nandroid, of course, inaccessible along with the SDcard. Your trick of updating TWRP (I had 2.6.3.2, latest is 2.6.3.4) and then wiping the cache again worked perfectly.
To anyone who comes across this, here's a quick overview:
1. Download the latest TWRP at http://teamw.in/project/twrp2/205
2. Boot your phone into Fastboot mode (Vol Down + Power from off, I think...worked for me)
3. Make sure your phone is plugged in via USB.
4. Open a command prompt in the folder you put TWRP in (ADB needed, obviously), type:
fastboot flash recovery imagename.img
For example:
fastboot flash recovery openrecovery-twrp-2.6.3.4-hammerhead.img
5. Only took a couple seconds until it was finished. Used the volume buttons to highlight Restart Recovery, hit power to reboot into recovery.
Wipe > Advanced Wipe, wipe what you need to wipe, viola, it was working at this point for me. Rebooted the phone, everything's back to normal. (it went through the "Optimizing apps" things on boot-up which took a few minutes, but everything is where I left it).
reynwrap582 said:
Big thank you for this, I thought I was boned. I was trying to flash 4.4.1 but forgot that I had modified the screen density in the build.prop and so I got an error, tried to wipe the cache, thought it had hung up, got impatient and VERY stupid and forced the phone to reboot. SDCard was entirely inaccessible, couldn't connect to AT&T, everything was screwed up and everything I could find told me that wiping everything back to stop and losing the data was my only option. I had a week-old TiBu on my dropbox, which isn't bad but not great either. Nandroid, of course, inaccessible along with the SDcard. Your trick of updating TWRP (I had 2.6.3.2, latest is 2.6.3.4) and then wiping the cache again worked perfectly.
To anyone who comes across this, here's a quick overview:
1. Download the latest TWRP at http://teamw.in/project/twrp2/205
2. Boot your phone into Fastboot mode (Vol Down + Power from off, I think...worked for me)
3. Make sure your phone is plugged in via USB.
4. Open a command prompt in the folder you put TWRP in (ADB needed, obviously), type:
fastboot flash recovery imagename.img
For example:
fastboot flash recovery openrecovery-twrp-2.6.3.4-hammerhead.img
5. Only took a couple seconds until it was finished. Used the volume buttons to highlight Restart Recovery, hit power to reboot into recovery.
Wipe > Advanced Wipe, wipe what you need to wipe, viola, it was working at this point for me. Rebooted the phone, everything's back to normal. (it went through the "Optimizing apps" things on boot-up which took a few minutes, but everything is where I left it).
Click to expand...
Click to collapse
Yeah man, I was certain I was gonna need a new phone. Glad this helped you. I'm going to update the OP with a link to your post so more inexperienced users can benefit. Thanks for typing it out.
_MetalHead_ said:
So I just wiped my cache and dalvik in TWRP and now I have no radio, no IMEI, no storage.. I think it borked my partitions. Tried flashing the factory image to no avail. It failed on the radio and I still have no storage.
Is there any way to recover from this?
EDIT: I was able to fix it as easily as I caused it. Check the 4th post. More detailed instructions on the 3rd post of page 2.
Click to expand...
Click to collapse
I remember you from the HTC one forums! Figures you already messed up your Nexus 5... Lol
Sent from my Nexus 5 using Tapatalk
MrGriffdude said:
I remember you from the HTC one forums! Figures you already messed up your Nexus 5... Lol
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Hey now, it wasn't my fault! Lol
Sent from my Nexus 5 using XDA Premium 4 mobile app
I restart my phone because it did a lot of time to reset cache. I regered the time I did it but was late.
Now my phone opens but does not have mobile network and cannot access my /sdcard/
From recovery I can see my sdcard. What can I Do?
Are you fully stock? If so, then format /cache partition and then perform a factory reset via stock recovery.
If you aren't fully stock, and use a custom recovery then I would suggest you to perform a factory reset from the custom recovery (it won't wipe internal sd)..
If it still doesn't work then you need to go back to fully stock by flashing the factory images from Google.
- Sent from an IceCold Hammerhead!
Yep, just keep wiping / formatting cache until it fixes or fastboot flash the stock cache.img
Sent from my Nexus 5 using Tapatalk
vin4yak said:
Are you fully stock? If so, then format /cache partition and then perform a factory reset via stock recovery.
If you aren't fully stock, and use a custom recovery then I would suggest you to perform a factory reset from the custom recovery (it won't wipe internal sd)..
If it still doesn't work then you need to go back to fully stock by flashing the factory images from Google.
- Sent from an IceCold Hammerhead!
Click to expand...
Click to collapse
I am not stock at all. I thought if I could copy sdcard to otg before all these.
pagratios said:
I am not stock at all. I thought if I could copy sdcard to otg before all these.
Click to expand...
Click to collapse
Just flash the stock recovery via fastboot and then format cache multiple times until it successfully formats! Your data won't be lost.
Since you rebooted before the cache was formatted, it has ended in a messed up /cache partition.
If you want to backup data, you can use adb pull from recovery...
See above
Edit.. By that I meant my previous post
Sent from my Nexus 5 using Tapatalk
rootSU said:
Yep, just keep wiping / formatting cache until it fixes or fastboot flash the stock cache.img
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
It says cannot mount cache.
vin4yak said:
Just flash the stock recovery via fastboot and then format cache multiple times until it successfully formats! Your data won't be lost.
Since you rebooted before the cache was formatted, it has ended in a messed up /cache partition.
If you want to backup data, you can use adb pull from recovery...
Click to expand...
Click to collapse
Now. I am pulling my data and then I'll flash stock.
I have a backup before the mistake. If I restore it?
pagratios said:
It says cannot mount cache.
Click to expand...
Click to collapse
In fastboot? That is an unknown error in fastboot to me.
Sent from my Nexus 5 using Tapatalk
pagratios said:
It says cannot mount cache.
Now. I am pulling my data and then I'll flash stock.
I have a backup before the mistake. If I restore it?
Click to expand...
Click to collapse
You can try to restore the backup but I doubt if it will solve the issue. However, there's no harm in trying..
The cache partition is messed up.. It needs to be formatted first. That's why I suggested you to go back to stock recovery and format cache...
I have tried wiping cache on Philz Touch and twrp and it didn't solve my problem. I had to format the cache partition using the stock recovery and voila! Everything was fixed.
vin4yak said:
You can try to restore the backup but I doubt if it will solve the issue. However, there's no harm in trying..
The cache partition is messed up.. It needs to be formatted first. That's why I suggested you to go back to stock recovery and format cache...
I have tried wiping cache on Philz Touch and twrp and it didn't solve my problem. I had to format the cache partition using the stock recovery and voila! Everything was fixed.
Click to expand...
Click to collapse
Yes but if you're flashing stock recovery fastboot you may aswell flash cache.img instead which is a well documented fix in this forum
Sent from my Nexus 5 using Tapatalk
rootSU said:
In fastboot? That is an unknown error in fastboot to me.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
My bad. I understand to have done this from TWRP. I haven't tried yet to do something from fastboot due to the backup.
rootSU said:
Yes but if you're flashing stock recovery fastboot you may aswell flash cache.img instead which is a well documented fix in this forum
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Yeah. I guess it will save some time and will be relatively easy for the OP!
pagratios said:
My bad. I understand to have done this from TWRP. I haven't tried yet to do something from fastboot due to the backup.
Click to expand...
Click to collapse
Flashing the stock cache.img won't wipe your saved data or backups.. There's no harm in trying.. However, if you're skeptical, adb pull all your important stuff and then do the flashes!
Finally I flashed cache.img and seems that everything is good again. Thank you for your help.
I have recently been having problems with TWRP, when I factory reset to install a new rom it rests just fine then when I go to install the new rom the phone reboots and when it has restarted it hasn't actually wiped anything. Is there a better option for a recovery everyone would recommend?
Did you flash the recovery in the twrp app? Reason I asked is cause the app wanted to flash mine to the wrong partition.
Sent from my HTC6525LVW using XDA Premium 4 mobile app
xsteven77x said:
Did you flash the recovery in the twrp app? Reason I asked is cause the app wanted to flash mine to the wrong partition.
Sent from my HTC6525LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I did it through fastboot
Use fastboot erase and fastboot format <partition>
Sent from my HTC6525LVW using XDA Premium 4 mobile app
Rushing said:
Use fastboot erase and fastboot format <partition>
Sent from my HTC6525LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I'm not real familiar with using fastboot, when I put this recovery on and unlocked the phone was the first time I ever used it. So how would I go about doing that and what does it do
Clockworkmod
Clockworkmod recovery is available for the M8 but it is not the official version. Link: http://forum.xda-developers.com/showthread.php?t=2708520
reaper420 said:
I have recently been having problems with TWRP, when I factory reset to install a new rom it rests just fine then when I go to install the new rom the phone reboots and when it has restarted it hasn't actually wiped anything. Is there a better option for a recovery everyone would recommend?
Click to expand...
Click to collapse
TWRP works just fine here. Which version do you have installed? Sure you flashed TWRP for the M8???
And what do you mean with "hasn't wiped anything"?
You do a factory wipe (default under Wipe menu) and when you boot your apps are still there, you don't have to go through setup?
After performing a factory wipe, go to Advanced and save the recovery log. Post it here.
berndblb said:
TWRP works just fine here. Which version do you have installed? Sure you flashed TWRP for the M8???
And what do you mean with "hasn't wiped anything"?
You do a factory wipe (default under Wipe menu) and when you boot your apps are still there, you don't have to go through setup?
After performing a factory wipe, go to Advanced and save the recovery log. Post it here.
Click to expand...
Click to collapse
Yeah it doesn't wipe anything the phone restarts and all my apps and their data is still intact. I just finished recovering from a bad situation. I flashed philz touch recovery using flashify and when I went to the recovey to do a backup the screen went black and booted staight into the hboot screen, every time I tried to reboot the phone it would send me to the hboot screen. I finally got twrp back by fasboot from my computer it was the newest twrp I got to flash I believe 2.7.1.0 I tried to restore a backup but all it would was restore the system and stop when it got to system data. I even tried flashing a new rom and that failed also. I then installed the other twrp 2.7.0.2 because I read most people are still ueing it because of problems with theother one. The phone still wouldn't boot or flash a rom but I got the restore to work by choosing not to restore data after rebooting two or three times the phone finally rebooted and all my apps and their data were still the even though I tried to install and new rom three or four times. Im a little worried now about trying to flash anything now. Im not new to android but my last phone was rock solid and I never had to deal with this many head aches. Thanks for any insite you can offer and sorry for such a long post
https://docs.google.com/file/d/0B620epsnenvUMlB4MkRiSUpFd2c/edit?usp=docslist_api
here is this recovery log from the last time I tried to do a factory reset.
reaper420 said:
https://docs.google.com/file/d/0B620epsnenvUMlB4MkRiSUpFd2c/edit?usp=docslist_api
here is this recovery log from the last time I tried to do a factory reset.
Click to expand...
Click to collapse
That file downloads as 0 kb
QUOTE=berndblb;54407730]That file downloads as 0 kb [/QUOTE]
I tried a reset again (which didn't work) then I tried for a log and the phone just reboots the second I touch the slider to make a log
ok I can get a log if I dont do anything else so I have a log before the attempt to factory reset but I can't get one after I try to reset. Will that do any good
https://docs.google.com/file/d/0B620epsnenvUeER0aERrYlRSUUU/edit?usp=docslist_api
RUU back to stock using the thread in the development forum. At the end of following the RUU instructions it gives you the option you flash a recovery. Select yes and flash twrp
Hi folks.
I'm facing a really weird problem. My friend's N5 doesn't want to boot with Lollipop, it shows the boot animation, but nothing happens, more than an hour and nothing.
I tried to flash back to kit kat. It indeed booted, but just to say that the camera and gallery has stopped, and gallery couldn't find any storage. When I go to the storage section in the settings, it doesn't show the pictures, music and other sources, just available space, cache and apps.
I tried to flash a custom rom to, but they all give me bootloops.
I never had this problems with my n4, so i don't know what to do anymore.
Any solutions?
Flash lollipop with fastboot. Then boot into the stock recovery and do a factory reset. Everything will be fine.
Sent from my Nexus 9 using XDA Free mobile app
I've already tried that, didn't work :crying:
Floydroider said:
I've already tried that, didn't work :crying:
Click to expand...
Click to collapse
You flashed the factory image with FASTBOOT and still had this problem? You sure?
Hmm. Try fastboot formatting all the partitions and then flashing the image again. Can't hurt.
_MetalHead_ said:
You flashed the factory image with FASTBOOT and still had this problem? You sure?
Click to expand...
Click to collapse
Yes, i'm absolutely sure. I'm used to use fastboot to flash my Nexus 4. I downloaded the proper factory image from Google and flashed it using both flash-all.bat and manual input in the cmd.
I tried to erase the partitions, format using TWRP, and install a custom ROM.
With twrp I can see the the internal storage partition, and even mount it to access by computer. But when the device boots, it just can't see the partition.
I put a song in the internal storage with twrp just to test, and when the device booted it didnt recognize the song, but when I got back to recovery, it was still there.
It seens that the problem is in the internal storage, but I don't know how to fix, and what could have caused it.
* Sorry, my english is bad :/
Floydroider said:
Yes, i'm absolutely sure. I'm used to use fastboot to flash my Nexus 4. I downloaded the proper factory image from Google and flashed it using both flash-all.bat and manual input in the cmd.
I tried to erase the partitions, format using TWRP, and install a custom ROM.
With twrp I can see the the internal storage partition, and even mount it to access by computer. But when the device boots, it just can't see the partition.
I put a song in the internal storage with twrp just to test, and when the device booted it didnt recognize the song, but when I got back to recovery, it was still there.
It seens that the problem is in the internal storage, but I don't know how to fix, and what could have caused it.
* Sorry, my english is bad :/
Click to expand...
Click to collapse
Try wiping cache in TWRP.
Wakamatsu said:
Hmm. Try fastboot formatting all the partitions and then flashing the image again. Can't hurt.
Click to expand...
Click to collapse
Tried that. I first used fastboot erase, didn't work, and then I use twrp to format to another fs. After that, I flashed the image again. Still nothing.
_MetalHead_ said:
Try wiping cache in TWRP.
Click to expand...
Click to collapse
I have wiped everything lots of times.
It's the first time I have a hard time trying to fix an android phone...
Now I flashed kitkat image again. It booted but with the storage problem. Then I update via notification, and it stuck in lollipop boot animation.
I will let it booting through the night. Or it boots after a couple of hours or the battery dies.
Floydroider said:
I have wiped everything lots of times.
It's the first time I have a hard time trying to fix an android phone...
Click to expand...
Click to collapse
Yeah this seems kinda crazy. Usually when stuff gets messed up like this a factory image clears it up. In your case, I honestly don't know what else to recommend. Sorry I can't be of more help.
Replace internal storage, nothing else you can do
Nothing worked in the end. My friend will send the phone to tech support.
Thank you guys for the help.
:good: