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
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
My nexus 5 was stock when i did a factory reset and something wrong happened and it was stuck on the android guy with the blue sphere thing.
So i decided to try and flash the factory image from Google but it gets stuck at erasing the cache. I have done it both by flash all and by doing each step independently. And its always stuck on clear cache
I then tried the cwm recovery and wiped the cache and tried installing CM11. CM11 was stuck in a bootloop
then i tried TWRP recovery but the phone would not load into it.
Then i tried the WugFresh Nexus Root Toolkit to flash stock and unroot and the phone still gets stuck on erasing cache
Any ideas? What should I try next?
Flash stock recovery and wipe cache and leave it doing that for as long as it takes.
rootSU said:
Flash stock recovery and wipe cache and leave it doing that for as long as it takes.
Click to expand...
Click to collapse
How long is reasonable?
I have waited 45 min in the past before losing patience
Could actually be a bit longer than that. Also, fastboot flash cache.img.on its own.
Thank You I will leave it running for a while and see what happens
It has been a little over an hour. How much longer should I wait?
Hard to say. Each time you interrupt it, you make it worse. Give it another hour. If that doesn't work, maybe try lg flash tool.
My mistake I might have interrupted it more then a few times yesterday. I probably made it fairly bad.
rootSU said:
Hard to say. Each time you interrupt it, you make it worse. Give it another hour. If that doesn't work, maybe try lg flash tool.
Click to expand...
Click to collapse
It has been erasing cache for about 12hrs should I give up on the idea it will do it and try the lg flash tool.
CoolRyder39 said:
It has been erasing cache for about 12hrs should I give up on the idea it will do it and try the lg flash tool.
Click to expand...
Click to collapse
Its probably the only option,
rootSU said:
Its probably the only option,
Click to expand...
Click to collapse
I get userdata erase fail when I run lg flash tool then it says We cant communicate.
Any other ideas
CoolRyder39 said:
I get userdata erase fail when I run lg flash tool then it says We cant communicate.
Any other ideas
Click to expand...
Click to collapse
If you use fastboot to lock the bootloader then reboot the bootloader, is it unlocked again? Please test
rootSU said:
If you use fastboot to lock the bootloader then reboot the bootloader, is it unlocked again? Please test
Click to expand...
Click to collapse
The bootloader is locked
CoolRyder39 said:
The bootloader is locked
Click to expand...
Click to collapse
should rule out nand failure then. All I can suggest is send it to LG, if you've already tried swapping USB cables and ports.
Thanks ill try different ones then give up haha
rootSU said:
should rule out nand failure then. All I can suggest is send it to LG, if you've already tried swapping USB cables and ports.
Click to expand...
Click to collapse
CoolRyder39 said:
Thanks ill try different ones then give up haha
Click to expand...
Click to collapse
Have you tried just formatting cache with fastboot? Tried multiple recoveries and wiping cache through them? If none of this works I'd bet your nand has a bad sector.
It can format erase and flash the cache no problem in fastboot it just wont do it at the end of the process of flashing a custom rom
rootSU said:
Its probably the only option,
Click to expand...
Click to collapse
I am having the same problem trying to flash to 5.0 or 5.0.1. It's to the point where Google says, "well, it's out of warranty, so send it to LG" and LG says, "send it to us and we'll tell you whether we'll charge you for a fix".
Pointer to the aforementioned "lg flash tool" - presumably different from the Google f/w at //developers.google.com/android/nexus/images - would be welcome.
Nexus 5 stuck on 'formatting /data' screen after factory image flashing
Sorry for the long post. I just want to ensure I am providing all relevant history.
I have a Nexus 5 (Hammerhead) 32gb device, stock with no rooting. I mean, I had never done anything special on it ever.
1. Recently I started getting Google Play Store related problems, first 194 error and then couple of days back 495 (I think). After trying switching on/off, clearing cache and some other similar ways to fix this, I decided to do a factory reset :crying:
2. I backed up all my data, and followed the documented steps for factory reset. The phone got stuck on 'erasing'. After waiting for over 24 hours, I finally figured out that this 'erasing' is not going to complete, ever.
3. So I again did some research and figured that I should do a fastboot recovery. Tried that with no difference. Recovery again took me to 'erasing' screen.
4. Some more research and then I decided to flash a factory image using ADB. I was (and still am) a complete newbie, so first I figured out what was ADB and how to get to it. After completing the installation, I found out Nexus 5 factory images. There was no mention of which ones to chose, so I just picked up the latest one.
This is what I really followed:
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
https://www.youtube.com/watch?v=DRp5jJO34PE
5. Having learnt my lessons, I read the flashing instructions many times and also watched some videos 3-4 times. Once I was confident that no more information was going to be had, and the phone was unlocked (fastboot oem unlock) I went ahead with the flashing. I did it step by step - bootloader, radio and they recovery image. The last one failed.
6. I did some more research and found a method which told me to unzip the last image and flash the component images one by one. I did. Success! However, the phone did not reboot by itself as the guide said it would. So I tried to boot it manually.
7. I did not get the dead android with red exclamation mark. Instead, I got an alive android with gears whirring on its tummy and back. Pressing power + vol-up button told me that this was the 'formatting /data' screen. I am unable to get past this screen. I am supposed to get to a screen where I can wipe data and cache etc. But I cannot get to it.
8. I have tried to wait it out (16 hours) and tried flashing the images again. Ultimately, I end up here.
9. I am unable to find any answers on what to do if stuck on this screen. So this is the end? Is my phone bricked? Is there anything else I can try? Will trying TWRP way help or is that just another way to same failure?
I would appreciate if there is anybody out there who can help me get my phone working again, or point me to a thread which helps me do it. Thanks!
Just wait it took me 5 hours of waiting
Try flashing Android 4.4.4 and see if that will boot. If that does not work try installing a custom recovery like TWRP, and do the wipes from there.
dicecuber said:
Just wait it took me 5 hours of waiting
Click to expand...
Click to collapse
I doubt it. 12 more hours have passed with no change.
eross said:
Try flashing Android 4.4.4 and see if that will boot. If that does not work try installing a custom recovery like TWRP, and do the wipes from there.
Click to expand...
Click to collapse
Thanks. I was thinking of trying TWRP anyway. I will try this today.
How does one select which image to flash? Is it always the latest one? In this case, how do I know which one is Android 4.4.4, and why are you recommending this specific one? I had purchased this phone in 2013 Feb (I think). So is there any specific image to be selected or the latest one is always to be picked?
Tom2403 said:
Thanks. I was thinking of trying TWRP anyway. I will try this today.
How does one select which image to flash? Is it always the latest one? In this case, how do I know which one is Android 4.4.4, and why are you recommending this specific one? I had purchased this phone in 2013 Feb (I think). So is there any specific image to be selected or the latest one is always to be picked?
Click to expand...
Click to collapse
UPDATE: Flashing 4.4.4. did not work. I again got the 'formatting /data' screen again instead of the phone booting up. However, the formatting screen with the android with diamond circling in the tummy also has a blue line below, possibly a progress bar. It is not growing though, just there... sizzling. Pressing power+vol-up buttons shows me that this is 'formatting /data' screen.
Will try custom recovery from TWRP now.
Tom2403 said:
UPDATE: Flashing 4.4.4. did not work. I again got the 'formatting /data' screen again instead of the phone booting up. However, the formatting screen with the android with diamond circling in the tummy also has a blue line below, possibly a progress bar. It is not growing though, just there... sizzling. Pressing power+vol-up buttons shows me that this is 'formatting /data' screen.
Will try custom recovery from TWRP now.
Click to expand...
Click to collapse
Reboot your phone into bootloader and download latest hammerhead 5.1.1 from Google. Extract everything and then extract the images. First use these commands
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
Then fastboot flash everything including bootloader.
Use this as a guide http://androidforums.com/threads/guide-how-to-flash-a-nexus-factory-image-manually.706533/
Then after finished reboot phone and leave it alone it will boot right up in 5-10 mins no need to go to recovery. In future don't format partitions.
try this: fastboot format cache
matt1515 said:
Reboot your phone into bootloader and download latest hammerhead 5.1.1 from Google. Extract everything and then extract the images. First use these commands
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
Then fastboot flash everything including bootloader.
Use this as a guide http://androidforums.com/threads/guide-how-to-flash-a-nexus-factory-image-manually.706533/
Then after finished reboot phone and leave it alone it will boot right up in 5-10 mins no need to go to recovery. In future don't format partitions.
Click to expand...
Click to collapse
Sorry for the late update. I was traveling over the weekend.
Thank you so much! Your post solved my issue. I wish I had this advice earlier!
First time it did not work, with reboot leading to a blank screen. Next time I following the guide completely, following the order in which different images were flashed. The phone went into boot animation for 5.1.1 and finally booted up, with all 32gb storage available.
Thanks again!
Tom2403 said:
UPDATE: Flashing 4.4.4. did not work. I again got the 'formatting /data' screen again instead of the phone booting up. However, the formatting screen with the android with diamond circling in the tummy also has a blue line below, possibly a progress bar. It is not growing though, just there... sizzling. Pressing power+vol-up buttons shows me that this is 'formatting /data' screen.
Will try custom recovery from TWRP now.
Click to expand...
Click to collapse
Tom2403 said:
Sorry for the late update. I was traveling over the weekend.
Thank you so much! Your post solved my issue. I wish I had this advice earlier!
First time it did not work, with reboot leading to a blank screen. Next time I following the guide completely, following the order in which different images were flashed. The phone went into boot animation for 5.1.1 and finally booted up, with all 32gb storage available.
Thanks again!
Click to expand...
Click to collapse
Glad to hear you got it up and running! No problem at all feels great to bring something f'd back to life.
Tom2403 said:
Sorry for the late update. I was traveling over the weekend.
Thank you so much! Your post solved my issue. I wish I had this advice earlier!
First time it did not work, with reboot leading to a blank screen. Next time I following the guide completely, following the order in which different images were flashed. The phone went into boot animation for 5.1.1 and finally booted up, with all 32gb storage available.
Thanks again!
Click to expand...
Click to collapse
I have same problem. I did everything that was written above but still my phone shows android with rotating cube on its tummy. Any ideas? Thanks in advance
dmuml10 said:
I have same problem. I did everything that was written above but still my phone shows android with rotating cube on its tummy. Any ideas? Thanks in advance
Click to expand...
Click to collapse
Go into bootloader and format the cache: fastboot format cache
inimaitimepass said:
Go into bootloader and format the cache: fastboot format cache
Click to expand...
Click to collapse
I did that but nothing changed. Still shows android with rotating gears.
Does anyone know what does that animation mean ?
dmuml10 said:
I did that but nothing changed. Still shows android with rotating gears.
Does anyone know what does that animation mean ?
Click to expand...
Click to collapse
How long did you leave at that? Sometimes it may take long time depending upon the storage size of your phone. Usually between 20 to 40 mins.
inimaitimepass said:
How long did you leave at that? Sometimes it may take long time depending upon the storage size of your phone. Usually between 20 to 40 mins.
Click to expand...
Click to collapse
I left it more than an hour.
Is it normal that my phone shows this Android animation after I flushed new factory image? Why is it trying to still "Format /data..." after new image flush?
Is there any other way to flush android factory image from scratch? I already used nexus root toolkit and fastboot
dmuml10 said:
I left it more than an hour.
Is it normal that my phone shows this Android animation after I flushed new factory image? Why is it trying to still "Format /data..." after new image flush?
Is there any other way to flush android factory image from scratch? I already used nexus root toolkit and fastboot
Click to expand...
Click to collapse
I'm really sorry that you are stuck in this mess. It is normal but more than 1 hour is way too much. I'm not sure about the causes, but you can try two more things and see how it goes. One is to use flash-all.bat script. If that didn't work then you can flash a custom ROM like Chroma and then try flashing the stock ROM.
inimaitimepass said:
I'm really sorry that you are stuck in this mess. It is normal but more than 1 hour is way too much. I'm not sure about the causes, but you can try two more things and see how it goes. One is to use flash-all.bat script. If that didn't work then you can flash a custom ROM like Chroma and then try flashing the stock ROM.
Click to expand...
Click to collapse
Thanks for help.
I flashed philz_touch recovery. From there I did factory reset and after that I executed this commands:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot flash bootloader "name of bootloader"
fastboot reboot-bootloader
fastboot flash radio "name of radio"
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot erase userdata
fastboot flash userdata userdata.img
fastboot reboot
Now my phone works.:victory:
dmuml10 said:
Now my phone works.:victory:
Click to expand...
Click to collapse
Good to hear. Weren't you using a custom recovery before philz'?
inimaitimepass said:
Good to hear. Weren't you using a custom recovery before philz'?
Click to expand...
Click to collapse
No. I only used stock recovery before philz.
As the title says that's what happened. i unlocked the bootloader and then flashed twrp with fastboot. booted into recovery said it was read only swiped to allow modifications then went to wipe so i could flash cm13 but it said cant mount internal storage object does not exist. also after rebooting into twrp multiple times i keeps saying the device is read only. anyone know what to do?
It keeps saying read only because it can't write configuration to the TWRP directory on internal storage... have you tried going into Mounts, untick the Mount Read Only box, and format or wipe the internal partition?
You should first boot to rom then to twrp internal storage will be inacessible because after unlocking bootloader userdata is cleared and we have to boot to rom so that it can setup the internal storage
@mjf042 That happened to me too. You need to go in TWRP, in Wipe > Tick Data and tap on Change Filesystem. You choose EXT4 and it's good ! Don't forget to flash a ROM.
acejavelin said:
It keeps saying read only because it can't write configuration to the TWRP directory on internal storage... have you tried going into Mounts, untick the Mount Read Only box, and format or wipe the internal partition?
Click to expand...
Click to collapse
ok i fixed the storage mounting problem but when i flash any rom i get stuck on boot logo. how long should it take? and is there something else i can do thank for your help
mjf042 said:
ok i fixed the storage mounting problem but when i flash any rom i get stuck on boot logo. how long should it take? and is there something else i can do thank for your help
Click to expand...
Click to collapse
The ROM's boot logo or the Moto "M" symbol?
If the ROM's boot logo, first boot can exceed 15 minutes, as long as it isn't looping just let it sit, seems like forever sometimes.
If it is getting stuck on the Moto M logo, that's a different story, let me know if that's the case.
acejavelin said:
The ROM's boot logo or the Moto "M" symbol?
If the ROM's boot logo, first boot can exceed 15 minutes, as long as it isn't looping just let it sit, seems like forever sometimes.
If it is getting stuck on the Moto M logo, that's a different story, let me know if that's the case.
Click to expand...
Click to collapse
ok yeah its the rom boot logo so i'll let it sit for awhile an see what happens. oh and it has not looped at all so i guess it just needs more time. thanks for your help
acejavelin said:
The ROM's boot logo or the Moto "M" symbol?
If the ROM's boot logo, first boot can exceed 15 minutes, as long as it isn't looping just let it sit, seems like forever sometimes.
If it is getting stuck on the Moto M logo, that's a different story, let me know if that's the case.
Click to expand...
Click to collapse
ive let it sit over an hour now and it still is at the cm13 boot logo. any ideas?
mjf042 said:
ive let it sit over an hour now and it still is at the cm13 boot logo. any ideas?
Click to expand...
Click to collapse
Yeah, that's too long... 30 minutes tops.
Wipe system, data, caches, and reflash I guess.
acejavelin said:
Yeah, that's too long... 30 minutes tops.
Wipe system, data, caches, and reflash I guess.
Click to expand...
Click to collapse
hey so i tried it a few more times and tried other roms and it just wont boot into anything. any ideas?
mjf042 said:
hey so i tried it a few more times and tried other roms and it just wont boot into anything. any ideas?
Click to expand...
Click to collapse
Restore backup, or flash stock image via fastboot, verify boot and start again...
acejavelin said:
Restore backup, or flash stock image via fastboot, verify boot and start again...
Click to expand...
Click to collapse
hey so i flashed stock and now the phone works again but my imei is 0 now. is there a way to fix that?
mjf042 said:
hey so i flashed stock and now the phone works again but my imei is 0 now. is there a way to fix that?
Click to expand...
Click to collapse
Reflash the modem and reboot...
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
And make sure each piece get a response of "OK"
acejavelin said:
Reflash the modem and reboot...
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
And make sure each piece get a response of "OK"
Click to expand...
Click to collapse
ok did what you said and every response had an ok but the imei is still 0. i use net10 as my carrier and they dont require the imei to use the sim so if i cant restore imei will it still work?
mjf042 said:
ok did what you said and every response had an ok but the imei is still 0. i use net10 as my carrier and they dont require the imei to use the sim so if i cant restore imei will it still work?
Click to expand...
Click to collapse
No, they don't require the IMEI, but the "tower" does so speak, it won't allow an IMEI of 0 to connect except for emergency calls.
I know there was a tutorial about recovering your IMEI when it is zero, just can't find it atm. And TWRP doesn't backup that partition either on osprey. :/
I am out of element here, I have heard of a few people dealing with this, but I have never had to, sorry I can't be of more help.
acejavelin said:
No, they don't require the IMEI, but the "tower" does so speak, it won't allow an IMEI of 0 to connect except for emergency calls.
I know there was a tutorial about recovering your IMEI when it is zero, just can't find it atm. And TWRP doesn't backup that partition either on osprey. :/
I am out of element here, I have heard of a few people dealing with this, but I have never had to, sorry I can't be of more help.
Click to expand...
Click to collapse
ok well thanks for all your help though :good: