Related
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.
So, my device was running CM12.1 for a while and i've just decided to upgrade it (it had been a long time since I did that). Then I downloaded the latest version of the rom and flashed it, relentlessly.
Everything was OK until I realized my "Google play services" app was not working at all... I thought it was just a ROM malfunction and decided to factory reset my phone. However, it didn't work... My google play services was continuously "force closing" and I decided to just go back to stock firmware. Yeah... Just like that.
It was just too late when I realized that I was already running CM13 and I had just tried to downgrade my device (in the wrong way, of course). And just like that, I bricked my phone... SOFT BRICK
So, is there any way I can get out of that situation?!
How can I unbrick my device (is that even possible)?
Does your phone still turn on? Can you boot in Fastboot mode? Power on while holding vol down.
lost101 said:
Does your phone still turn on? Can you boot in Fastboot mode? Power on while holding vol down.
Click to expand...
Click to collapse
Yes, it does. Fastboot's still working fine. Recovery mode, however, shows me the image of the "android mascot" with it's belly opened up, but no options to choose.
Try flashing the factory firmware image for your model:
Firmware Images: http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Fastboot Tutorial: http://forum.xda-developers.com/showthread.php?t=2542219
lost101 said:
Try flashing the factory firmware image for your model:
Firmware Images: http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Fastboot Tutorial: http://forum.xda-developers.com/showthread.php?t=2542219
Click to expand...
Click to collapse
I tried to flash firmware stock 5.0.2 in my phone using minimal adb and fastboot after updating to CM13 and that's what led me into this situation.
Did it twice, actually, so... I think simply flashing won't do any good.
Should I try flashing 5.1 stock?? will that work?
Stormeagle said:
I tried to flash firmware stock 5.0.2 in my phone using minimal adb and fastboot after updating to CM13 and that's what led me into this situation.
Did it twice, actually, so... I think simply flashing won't do any good.
Should I try flashing 5.1 stock?? will that work?
Click to expand...
Click to collapse
Yes, use the 5.1 image. Extract the following files into the firmware image folder: https://www.androidfilehost.com/?fid=24269982086993793
Run command prompt from that folder. Post log - copy and paste contents of command prompt screen - take screenshots.
Fastboot is not user-friendly - it can completely fail - yet as far as you can tell, flashing has been an amazing success.
lost101 said:
Yes, use the 5.1 image. Extract the following files into the firmware image folder: https://www.androidfilehost.com/?fid=24269982086993793
Run command prompt from that folder. Post log - copy and paste contents of command prompt screen - take screenshots.
Fastboot is not user-friendly - it can completely fail - yet as far as you can tell, flashing has been an amazing success.
Click to expand...
Click to collapse
Should I flash it with all the commands or should I skip some? (That was common back when people were bricking their devices when updating to lollipop).
Stormeagle said:
Should I flash it with all the commands or should I skip some? (That was common back when people were bricking their devices when updating to lollipop).
Click to expand...
Click to collapse
Skip the motoboot.img command.
lost101 said:
Skip the motoboot.img command.
Click to expand...
Click to collapse
Nope... Still bootlooping... Looks like i'm gonna have a big night ahead of me...
Everything during the flashing process went "OKAY".
Stormeagle said:
Nope... Still bootlooping... Looks like i'm gonna have a big night ahead of me...
Everything during the flashing process went "OKAY".
Click to expand...
Click to collapse
Use mfastboot: https://www.androidfilehost.com/?fid=24052804347778493
lost101 said:
Use mfastboot: https://www.androidfilehost.com/?fid=24052804347778493
Click to expand...
Click to collapse
I'm thinking about flashing the 4.4.4 Stock ROM. Maybe if I do that, I can succesfully make my phone work... or totally brick it once and for all...
Hi all,
I'm after some help with a 1st gen Moto G. It belonged to my mother, and was happily running CM for years before dying on her one day. She posted it back to me months ago...I failed to fix it then, and I'm not having much luck this time either.
It sits on the bootloader ok, and I can fastboot interact with it, but although attempts to revert to stock, or update TWRP etc look like they've worked, nothing ever changes. It's as if its storage has gone read-only.
CM is still there, but bootloops 9 times out of 10. Occasionally it'll start properly, before rebooting seconds later, probably because it can't write anything and it crashes out.
I can however, boot (not flash) the latest TWRP and play around with that, but even simple file operations like trying to delete anything fails ("process ended with ERROR 1"). I've tried clearing, factory resetting, reformatting, etc, but nothing has an effect. CM and the old files are all still there.
I don't need this phone, nor the files on it - it'll go in the trash if it can't be fixed - so not worried about damaging it any way in an attempt to revive it
Thanks
Everything you describe suggests Emmc corruption. Threads are created about it regularly. It's an issue that can effect any android phone, and while age could be the key factor - my launch-day Falcon has never had an issue. There is no cure.
However, try the below just in case I am wrong.
Flash the latest Factory Firmware Image for your model using mFastboot. If this is not successful, it would help to see a log of the flashing process. Copy and paste command prompt screen. Take screenshots if necessary.
mFastboot download: https://www.androidfilehost.com/?fid=24052804347778493
Firmware Images: http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Fastboot Tutorial: http://forum.xda-developers.com/showthread.php?t=2542219
lost101 said:
Everything you describe suggests Emmc corruption.
Click to expand...
Click to collapse
Ah, interesting. It's not something I've come across before, so it's good to at least know what's (probably) wrong with it.
lost101 said:
However, try the below just in case I am wrong.
Flash the latest Factory Firmware Image for your model using mFastboot. If this is not successful, it would help to see a log of the flashing process. Copy and paste command prompt screen. Take screenshots if necessary.
Click to expand...
Click to collapse
Not sure if this was the best way, but I booted TWRP and attempted to install via ADB sideload (couldn't think of any other way to get the zip across).
fastboot transfered about 26% of the file before exiting.
TWRP reported:
Code:
installing zip file '/sideload/pacakge.zip'
>>> XT1032 Retail Europe 5.1 (Untouched) <<<
Installing Android
Please wait...
symlink: no of symlinks failed = 1
Updater process ended with ERROR: 7
imilne said:
Not sure if this was the best way, but I booted TWRP and attempted to install via ADB sideload (couldn't think of any other way to get the zip across).
Click to expand...
Click to collapse
Do as I instructed to remove all doubt of Emmc corruption.
I have the T-Mobile OnePlus 8. SIM/BL unlocked, converted to international firmware. FP worked the whole time during the conversion. Had issues with the modem, but that's a given an was sorted out.
I heavily rely on Google Pay because I'm lazy and rarely carry my wallet with me. I ended up installing EdXposed to see what has changed since the last time I used it years ago. There was a XStadia module that came in handy so that I could use Stadia on my data connection instead of WiFi. After using it for some time, I decided that having Xposed wasn't worth breaking SafetyNet over, so I uninstalled. Well for some reason, it didn't uninstall probably or something happened along the way that SN was still broken. So I figured the only way to fix is to factory data reset. Bad idea. These devices nowadays aren't like what they used to be. Ended up with multiple CrashDump screens. Ran into a crap ton of issues so I ended up used my the MSM tool to go back to the stock T-Mobile firmware, using the 10.5.7 fastboot ROM to go back to international, etc.
When I went back to international again, I noticed that my fingerprint sensor wasn't working so I followed the guide found here: https://forum.xda-developers.com/oneplus-8/how-to/guide-fix-persist-img-loss-finger-print-t4126455 The only thing I wasn't able to do was downgrade to an earlier OOS like 10.5.4 mentioned in the guides OP due to the phone not letting me. I tried the MSM 10.5.4 tool, and the 10.5.4 fastboot ROM. Both didn't work and gave me errors (I'm guessing because it's a branded device and certain critical partitions can't be overwritten). So I ended up pulling my broken persist from the T-Mobile stock rooted firmware, fastboot flashed 10.5.7, and went from there.
After some time, I finally had a working FP. Thanks again @antnyhills. When it was working, I thought that every time I used the FP, it gave me more errors than it actually unlocked the phone. So, I thought I'd be a little curious and see if doing the FP tests again would fix it. IT DID NOT. I ended up breaking it so bad, that now I get an error saying "fingerprint hardware not present". When I go to setup a new fingerprint, it says "enrollment was not completed. Fingerprint sensor error, please try again". If I go back to dismiss the error, the FP is still present, and when I press on it, the circle lights up, it just doesn't vibrate or register anything.
So, I followed the guide again. Again, nothing. Now I'm sitting here and nothing works. Camera doesn't work (black screen when opening), flashlight doesn't work, and I'm sure there's a few other things, just didn't mention. What do I do now? Get a hold of OnePlus and see if they'll replace my device? Is there a way to erase the Persist.img from the device and reflash it again somehow?
TL;DR: FP sensor broken, camera broken, after following broken persist.img guide.
antnyhills said:
Make sure you are using your original persist.img from your backup the first time you did this guide to transfer the two folders. If that fails. Flash your the same original back up persist.img and start the guide again.
Click to expand...
Click to collapse
Make sure you are using your original persist.img from your backup the first time you did this guide to transfer the two folders. If that fails. Flash your the same original back up persist.img and start the guide again.
If you get it working again, the FP sensor just as accurate as it was out of the box because you are using the factory calibrations.
When you set up your fingerprint it is not accurate at first but over time in learns you fingerprint even more and becomes more accurate and fast.
antnyhills said:
Make sure you are using your original persist.img from your backup the first time you did this guide to transfer the two folders. If that fails. Flash your the same original back up persist.img and start the guide again.
Click to expand...
Click to collapse
I did, multiple times to no avail. How do I go about flashing the persist.img? There are only a few options in TWRP. Two super, recovery, and boot.
I know, I remember reading somewhere that it learns every time. I should've just left it alone and let it do its thing, but of course I had to go and mess things up.
Is my flashlight and camera not working because of persist files?
When I got it working again using your guide, when I started tinkering around, even though my FP was working, when I rebooted, it said"fingerprint hardware not present". Now all of the apps that use FP don't even ask me if I want to use FP like it's not even there .
TheKnux said:
I did, multiple times to no avail. How do I go about flashing the persist.img?
Click to expand...
Click to collapse
Go to the bootloader.
Code:
fastboot reboot fastboot
This will take you to fastbootd. It will look like your recovery. You must have stock original recovery installed. TWRP will not work.
Code:
fastboot flash persist [INSERT YOUR PERSIST.IMG HERE]
Example:
Code:
fastboot flash persist C:\user\example\desktop\persist.img
Make sure you are flashing the persist.img from your original time you performed this guide. This will take you back to were you where before you ever performed the guide.
Then follow the guide one more time, follow it VERY CAREFULLY as there is a lot to go wrong.
Best of luck!
Edit: Also, I would assume your camera/flashlight broke because of your persist partition. Hence Why we are going to start from scratch with your original broken persist.img
antnyhills said:
Go to the bootloader.
This will take you to fastbootd. It will look like your recovery. You must have stock original recovery installed. TWRP will not work.
Example:
Make sure you are flashing the persist.img from your original time you performed this guide. This will take you back to were you where before you ever performed the guide.
Then follow the guide one more time, follow it VERY CAREFULLY as there is a lot to go wrong.
Best of luck!
Edit: Also, I would assume your camera/flashlight broke because of your persist partition. Hence Why we are going to start from scratch with your original broken persist.img
Click to expand...
Click to collapse
I'm not a noob at rooting/ROMing. I'm just new at doing this kind of stuff. Messing with critical files in the root directory. I appreciate you chiming in and helping me with this. I'll do what you said and report back. Appreciate everything you've done, including you helping me with this.
TheKnux said:
I'm not a noob at rooting/ROMing. I'm just new at doing this kind of stuff. Messing with critical files in the root directory. I appreciate you chiming in and helping me with this. I'll do what you said and report back. Appreciate everything you've done, including you helping me with this.
Click to expand...
Click to collapse
No worries. Eager to hear your update.
antnyhills said:
No worries. Eager to hear your update.
Click to expand...
Click to collapse
target reported max download size of 805306368 bytes
sending 'persist' (32768 KB)...
OKAY [ 0.703s]
writing 'persist'...
FAILED (remote: Flashing is not allowed for Critical Partitions
)
finished. total time: 0.718s
That is my error I get when following your instructions.
TheKnux said:
target reported max download size of 805306368 bytes
sending 'persist' (32768 KB)...
OKAY [ 0.703s]
writing 'persist'...
FAILED (remote: Flashing is not allowed for Critical Partitions
)
finished. total time: 0.718s
That is my error I get when following your instructions.
Click to expand...
Click to collapse
Make sure you do
Code:
fastboot reboot fastboot
Like I mentioned it should look like the stock recovery. When you do that does it take you to your stock recovery?
If you have discord, I'll PM you a link, might be easier to communicate.
antnyhills said:
Make sure you do
Code:
fastboot reboot fastboot
Like I mentioned it should look like the stock recovery. When you do that does it take you to your stock recovery?
If you have discord, I'll PM you a link, might be easier to communicate.
Click to expand...
Click to collapse
So to my knowledge, stock recovery is the screen with the OnePlus logo, some chinese words, and English and Fastboot is the screen that says the SoC name, device state, etc.
I even tried "fastboot flash persist_critical persist.img" and it didn't work. Also, fastboot reboot fastboot doesn't do anything. Fastboot reboot bootloader sends me to fastboot. Using Windows 10/PowerShell.
I do have Discord but it runs like crap on my PC (old laptop) and since my phone is down currently, this is the only way to talk.
TheKnux said:
So to my knowledge, stock recovery is the screen with the OnePlus logo, some chinese words, and English and Fastboot is the screen that says the SoC name, device state, etc.
I even tried "fastboot flash persist_critical persist.img" and it didn't work.
I do have Discord but it runs like crap on my PC (old laptop) and since my phone is down currently, this is the only way to talk.
Click to expand...
Click to collapse
Boot phone
Put persist.img on the root of your 'sdcard'
Code:
adb shell
Code:
su
Code:
dd if=/sdcard/persist.img of=/dev/block/bootdevice/by-name/persist
reboot
antnyhills said:
Boot phone
Put persist.img on the root of your 'sdcard'
Code:
adb shell
Code:
su
Code:
dd if=/sdcard/persist.img of=/dev/block/bootdevice/by-name/persist
reboot
Click to expand...
Click to collapse
Okay, that seems to have worked. I did that while on T-Mobile firmware. I just fastboot flashed the 10.5.7 international firmware, updating to 10.5.9 via OTA now, when it reboots, I'm going to install TWRP and Magisk, and push the persist.img again using the command you gave me once more for good measure then fix FP using your guide. On the flip side, once I pushed the persist.img using your command, my flashlight and camera works again, just not FP, yet. I'll report back after following your guide. Thank you again.
TheKnux said:
So to my knowledge, stock recovery is the screen with the OnePlus logo, some chinese words, and English and Fastboot is the screen that says the SoC name, device state, etc.
I even tried "fastboot flash persist_critical persist.img" and it didn't work. Also, fastboot reboot fastboot doesn't do anything. Fastboot reboot bootloader sends me to fastboot. Using Windows 10/PowerShell.
I do have Discord but it runs like crap on my PC (old laptop) and since my phone is down currently, this is the only way to talk.
Click to expand...
Click to collapse
You need to have the latest version of adb and fastboot from Google on your PC for "fastboot reboot fastboot" to work and be able to access fastbootd.
https://developer.android.com/studio/releases/platform-tools
Fastbootd is something new and different from bootloader. It allows flashing to all partitions (required due to dynamic partitioning in Android 10). However, it looks very similar to stock recovery (it actually uses stock recovery which is why it won't work with TWRP flashed). "fastboot reboot bootloader" sends you to bootloader, which is no longer the same as fastboot.
However, the instructions posted by @antnyhills will also work perfectly fine for restoring persist. That's the method I use (personally I try to avoid fastboot flash at all on this phone)
Your problem is you completely corrupted your persist.img. That's why you have a backup . Or now you'd be without sensors, camera, flashlight, etc until someone posted theirs but then you would never be able to fix fingerprint.
Once you have fingerprint working again, take a new backup of persist. Then no need to fix it again in the future if it gets messed up. Simply restore it.
starcms said:
You need to have the latest version of adb and fastboot from Google on your PC for "fastboot reboot fastboot" to work and be able to access fastbootd.
https://developer.android.com/studio/releases/platform-tools
Fastbootd is something new and different from bootloader. It allows flashing to all partitions (required due to dynamic partitioning in Android 10). However, it looks very similar to stock recovery (it actually uses stock recovery which is why it won't work with TWRP flashed). "fastboot reboot bootloader" sends you to bootloader, which is no longer the same as fastboot.
However, the instructions posted by @antnyhills will also work perfectly fine for restoring persist. That's the method I use (personally I try to avoid fastboot flash at all on this phone)
Your problem is you completely corrupted your persist.img. That's why you have a backup . Or now you'd be without sensors, camera, flashlight, etc until someone posted theirs but then you would never be able to fix fingerprint.
Once you have fingerprint working again, take a new backup of persist. Then no need to fix it again in the future if it gets messed up. Simply restore it.
Click to expand...
Click to collapse
I tried Googling for the latest adb/fastboot drivers but I already spent half the day restoring my persist and fixing my FP. I thought there would be a flasher like the 1.4.2 drivers but it wants me to install the sdk and install it through there. Not my top priority right now, next time I'm on my pc though I will for sure. The method @antnyhills told me to do to push the persist worked great, followed his guide again, fixed FP, and backed up persist with FP and all sensors working. Stored it in two places so I don't accidentally delete them lol. The updated drivers you're mentioning, that'll allow me to flash critical partitions in case I mess something up again next time?
Huge thanks to @antnyhills for coming in here and helping me out, and to you for giving me your two cents as well. I was so tempted to be a Karen and get T-Mobile and OnePlus on the phone to RMA my device. ?
TheKnux said:
I tried Googling for the latest adb/fastboot drivers but I already spent half the day restoring my persist and fixing my FP. I thought there would be a flasher like the 1.4.2 drivers but it wants me to install the sdk and install it through there. Not my top priority right now, next time I'm on my pc though I will for sure. The method @antnyhills told me to do to push the persist worked great, followed his guide again, fixed FP, and backed up persist with FP and all sensors working. Stored it in two places so I don't accidentally delete them lol. The updated drivers you're mentioning, that'll allow me to flash critical partitions in case I mess something up again next time?
Huge thanks to @antnyhills for coming in here and helping me out, and to you for giving me your two cents as well. I was so tempted to be a Karen and get T-Mobile and OnePlus on the phone to RMA my device.
Click to expand...
Click to collapse
It's not updated drivers. It's an updated version of adb and fastboot that fully supports all the new commands needed (such as "fastboot reboot fastboot"). I had provided a link. Just download and unzip to your adb directory on your PC and select replace all files when copying.
https://developer.android.com/studio/releases/platform-tools
starcms said:
It's not updated drivers. It's an updated version of adb and fastboot that fully supports all the new commands needed (such as "fastboot reboot fastboot"). I had provided a link. Just download and unzip to your adb directory on your PC and select replace all files when copying.
https://developer.android.com/studio/releases/platform-tools
Click to expand...
Click to collapse
Where would the adb directory be if I used the "adb and fastboot installer for windows" (or whatever it's called) found here on XDA? I'm guessing it's years old. I think it said version 1.4.2 or something.
Also, are you or @antnyhills on Telegram at all?
what was the final of this, i have the oneplus8 tmobile, and i want to convert to globla, but this issue scared me
Hi! My old phone is booting into fastboot mode, when I try to boot normally I get a black screen, the "Power off" button appears when I hold the power button. The bootloader is not unlocked and the phone was never rooted. Wiping the user partition does not help. It is visible in fastboot mode and I can enter stock recovery, though trying to adb sideload a stock rom returns an error (footer is wrong; signature verification failed). Trying to fastboot boot twrp or recovery.img doesn't work either. I've ran out of ideas, what should I do to get this phone to work?
Try flashing the stock ROM with fastboot. I'm pretty sure ADB doesn't let you flash onto your phone because using your phone with ADB means that it's still powered on - which can cause some issues. You can also try and unlock your bootloader through fastboot, and then flash a recovery and custom ROM.
Both failed. I attached the errors I recieved.
crepper4454 said:
Both failed. I attached the errors I recieved.
Click to expand...
Click to collapse
Try "fastboot bootloader unlock", maybe. Also: Is there a flashall.bat in the stock ROM folder? If there is: Connect your device while in fastboot, and double-click it.
crepper4454 said:
Both failed. I attached the errors I recieved.
Click to expand...
Click to collapse
Try this maybe. I know you can't wipe through the stock ROM, so, try the command: "fastboot -w". That'll wipe everything off the device.
[INDEX][Osprey][Merlin] Moto G Factory Firmware Images
Disclaimer: I am not responsible for anything that happens as a result of flashing these files. Your destiny is your own. Moto G (3rd Gen) Factory Firmware Images - Provided by Firmware TEAM - Please report broken links. New Mirrors welcome...
forum.xda-developers.com
I can wipe through stock recovery. I did fastboot -w and it cleared the cache and userdata partitions, they were already clean afaik. Typing fastboot bootloader unlock returns unknown command. There are no .bat files in my firmware. I can try downloading one from the site you linked, but I don't know what to do with it if fastboot flash does not work.
crepper4454 said:
I can wipe through stock recovery. I did fastboot -w and it cleared the cache and userdata partitions, they were already clean afaik. Typing fastboot bootloader unlock returns unknown command. There are no .bat files in my firmware. I can try downloading one from the site you linked, but I don't know what to do with it if fastboot flash does not work.
Click to expand...
Click to collapse
Try this: https://forum.xda-developers.com/t/guide-osprey-fastboot-flashing-factory-firmware-images.3187750/
It says there that the "preflash validation failed" error occurs when the firmware being flashed is older than the one already installed. I will try downloading a newer version and flashing it. Will update here.
Update: I have dowloaded a newer rom and tried to flash it. This time got different errors (picture attached, this went for every sparsechunk). I think I know the reason but I do not know how to solve it. This might not be the exact stock rom of this phone so I cannot flash it with a locked bootloader. Could someone help me finding the correct rom or suggest a different solution?
Yooooo. I have the Moto e5 Cruise and so does my wife. We bought them in 2018 from Cricket and last night hers went to emmc failure, also known scientifically as 'no worky' mode.
The phone would only load in fastboot and had tried to use my Moto RSD tool to reflash but the phone would not detect in anything but fastboot mode.. Here's where it gets interesting....
There is a piece of software called the Lenovo (which now owns Moto) Rescue and Smart Assistant that can reflash your phone back to factory, no matter your sub-variant (cricket, metro, etc). Without having a fresh backup on hand, you're going to be beholden to the last cloud sync or manual backup you have because all data will be wiped in the below process.
BTW: Just run the assistant as it seems to be the easiest 'back-to-stock/working' tool I can find. Going to fastboot alone yielded weird errors since i didn't have the unlock code for the 'fastboot oem unlock [code goes here]' command.
**RESTORATION PROCESS**
This will apply to multiple Lenovo/Moto Mobility devices. Unknown at this time how many have been impacted by this seemingly pre-planned failure on Lenovo's part.
If your phone is stuck in fastboot mode where MTK download mode does not load, nor does adb, follow these simple steps:
(NOTE: BACKUP YOUR FILES IF POSSIBLE)
1. Click the link above to be directed to the Lenovo software download page and run the installer on your PC (Sorry Mac users :'().
2. The software, once installed, will require you to sign up for OR link a google, fb, g+, etc account to it for purposes of creating a Lenovo ID. Once signed in, click on 'Rescue Now'.
3. With your phone in fastboot mode, allow the software to download the firmware for your phone.
4. Once the firmware has finished downloading and validating, click on 'Rescue Now' once again. Your phone will begin the reflashing process.
That... actually worked. The program found the required ROM and flashing went without problems. Thank you very much @kmt5150 .
crepper4454 said:
That... actually worked. The program found the required ROM and flashing went without problems. Thank you very much @kmt5150 .
Click to expand...
Click to collapse
No problemo! Glad it worked!