Related
Sometimes I completely wipe my device before puting a rom on it, when I got my Gnex obviously because it had no removable sd card I couldnt remove it and format it.
I used this command yesterday to wipe my rooted N4 and it wont boot, I've flashed a stock image to get it up and running again and for testing purposes tried it again but with a different rooted rom, same outcome.
1) Does anyone know why this would be?
2) Is there a better way to completely wipe my device without causing this problem
Thanks in advance
on fastboot erase userdata
Hello.
I think I got into a similar problem as you did.
I wanted to write JOP40D using the google factory images on my Nexus 4, and in the process I also used a combination of fastboot -w as well as fastboot erase userdata. Now my phone won't boot up completely.
I wanted to ask you if/how you managed to recover to stock...
I personally tried using google's stock factory images for Nexus 4 (from developers.google.com), without success.
Thanks in advance.
Re: on fastboot erase userdata
FYI, Nexus 4 Toolkit did it for me.
1) The problem is the google factory image script does not reformat userdata && cache. These stay damaged from the initial fastboot erase operation done within the same script sequence. The Toolkit does 'reformat' them.
Not sure why this happens, may be from a bad erase that does not trigger reformatting, but it probably has to do with the version of fastboot you run on your PC versus the fastboot backend phone daemon. I posted online about this and hope to get some answers.
2) There must be a way to trigger this reformatting of userdata && cache...
boy3dfx said:
FYI, Nexus 4 Toolkit did it for me.
1) The problem is the google factory image script does not reformat userdata && cache. These stay damaged from the initial fastboot erase operation done within the same script sequence. The Toolkit does 'reformat' them.
Not sure why this happens, may be from a bad erase that does not trigger reformatting, but it probably has to do with the version of fastboot you run on your PC versus the fastboot backend phone daemon. I posted online about this and hope to get some answers.
2) There must be a way to trigger this reformatting of userdata && cache...
Click to expand...
Click to collapse
Sorry for the late reply only just seen it, so there's def a problem then and not something im doing wrong...
you might wanna update the sdk, when i used the same commands adb said someting like "you mean format" and processed the command without isssues
Stretlow said:
Sometimes I completely wipe my device before puting a rom on it, when I got my Gnex obviously because it had no removable sd card I couldnt remove it and format it.
I used this command yesterday to wipe my rooted N4 and it wont boot, I've flashed a stock image to get it up and running again and for testing purposes tried it again but with a different rooted rom, same outcome.
1) Does anyone know why this would be?
2) Is there a better way to completely wipe my device without causing this problem
Thanks in advance
Click to expand...
Click to collapse
1) Doing this on my Atrix 2 also causes a bootloop. I'm assuming it's because it is completely erasing the data partition instead of formatting it.
2) Try using fastboot format userdata (this works for me), or use the toolkit/a custom recovery to do your wiping.
Sent from my MB865 using xda premium
boy3dfx said:
FYI, Nexus 4 Toolkit did it for me.
1) The problem is the google factory image script does not reformat userdata && cache. These stay damaged from the initial fastboot erase operation done within the same script sequence. The Toolkit does 'reformat' them.
Not sure why this happens, may be from a bad erase that does not trigger reformatting, but it probably has to do with the version of fastboot you run on your PC versus the fastboot backend phone daemon. I posted online about this and hope to get some answers.
2) There must be a way to trigger this reformatting of userdata && cache...
Click to expand...
Click to collapse
Yes, there is a way to format partitions. The most recent version of fastboot supports this command.
Code:
fastboot format <partition>
So it works like this:
Code:
#format userdata
fastboot format userdata
#format cache
fastboot format cache
comminus said:
Yes, there is a way to format partitions. The most recent version of fastboot supports this command.
Code:
fastboot format <partition>
So it works like this:
Code:
#format userdata
fastboot format userdata
#format cache
fastboot format cache
Click to expand...
Click to collapse
Thanks! I was stuck at the endless boot logo after trying to restore with the factory image via fastboot. This got me back to normal booting.
Ok so I updated my SDk last night and typed (without quotes) "fastboot erase userdata" it gave me a message saying DID YOU MEAN FASTBOOT FORMAT USERDATA" then it completed the action however my phone still didnt boot.
Sorry for my ADB noobness but just to clarify...
I used to type exactly as this "fastboot erase userdata"
And now I have to type this
"fastboot format userdata" which should fix the issue, Erase all userdata (media, pictures etc) and boot the device
Thanks again chaps
boy3dfx said:
FYI, Nexus 4 Toolkit did it for me.
1) The problem is the google factory image script does not reformat userdata && cache. These stay damaged from the initial fastboot erase operation done within the same script sequence. The Toolkit does 'reformat' them.
Not sure why this happens, may be from a bad erase that does not trigger reformatting, but it probably has to do with the version of fastboot you run on your PC versus the fastboot backend phone daemon. I posted online about this and hope to get some answers.
2) There must be a way to trigger this reformatting of userdata && cache...
Click to expand...
Click to collapse
^^^ This, I have been going crazy trying to figure out the issue with the hanging boot. The format makes it boot everytime.
The problems are being caused when fastboot erase is used to delete the contents of the partition.
FASTBOOT ERASE IS NOT NEEDED ON THE NEXUS 4 (only the Nexus 7 uses fastboot erase to wipe the partitions before flashing).
If flashing manually just use the google script supplied with the stock image to flash correctly (from the jop40d build. If flashing jop40c then use the correct image names for that):
fastboot flash bootloader bootloader-mako-makoz10l.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.33.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot -w update image-occam-jop40d.zip
Or use the Nexus 4 Toolkit to do it all automatically and properly
Mark.
[removed].
sdkmanager
android_sdk/tools/bin
Hello all,
I left a similar post in a couple other threads, and thought maybe someone here might have some insight into my problem.
Been running AICP rom (no custom kernel except the one that comes with AICP) with f2fs on /data and /cache for several months on 16GB grouper. About a month or so ago, the wife installed a game that wouldn't run on this hardware (King's Paradise Bay), and I uninstalled it. It left a file in /data/data/....etc that couldn't stat in TWRP, so no nandroid backups since then. I figured I'd just backup user data with TiBkp and wipe with fresh install of latest AICP when time permitted.
The other night I noticed the N7 was boot looping, getting to the stage where the boot animation dims. The boot anim would hang and after several seconds the Google unlock splash screen would come up and the N7 would try to boot again.
I can get into TWRP and bootloader with no problem. However, when TWRP comes up, the log shows the red entries for 2 files that can't stat, which has been this way since that game was uninstalled. I cannot seem to wipe *any* partition, and when I attempt to format or wipe userdata in TWRP, the N7 spontaneously reboots. Manually attempting to wipe/format/etc. via FastBoot doesn't work, with error message showing after trying to flash bootloader. Also, I can't change /data or /cache back to ext4. I am able to successfully read, write, and delete files on the N7 via computer USB MTP connection.
If the N7's flash memory has somehow become corrupted, is there a way to completely erase/format/whatever so that this wonderful device can become usable again? Any help would be greatly appreciated.
Thanks in advance.
Hello,
don't flash Bootloader via Fastboot. You should do this commands:
Code:
fastboot erase cache
fastboot erase userdata
fastboot erase system
fastboot erase boot
Trafalgar Square said:
Hello,
don't flash Bootloader via Fastboot. You should do this commands:
Code:
fastboot erase cache
fastboot erase userdata
fastboot erase system
fastboot erase boot
Click to expand...
Click to collapse
Yes, I have attempted all these commands, followed by flashing with either fastboot or TWRP with no success. Fastboot reports success, but partitions are not erased.
I have the same problem. The Nexus Root Toolkit can not flashign. It succeeds only boot TWRP. In TWRP computer sees the files from the tablet.I could not rename and delete. Wipe the TWRP and stock recovery displays the status OK, and the files are deleted. Fastboot shows that uploads, but all files remain unchanged.
Hi,
I have a Nexus 4 which was flashed with Lollipop 5.1.1.
My problem started when, after letting the battery completely drain and then trying to turn the phone on again, I got stuck on the message "Android is starting... optimizing apps" for days. I tried rebooting and factory format with no success.
I also tried formatting it through TWRP, but I got the message "Unable to mount /cache". After that, I tried flashing older factory images but only got my phone to work with the oldest version of jelly bean available by google developers page (4.2.2). After I got it to work, I tried to OTA update it to 4.3, but the same message "Android is starting ... optimizing apps" came back.
I had no other choice but to fastboot format it and flash it again with 4.2.2.
Any ideas on what could possibly be causing this? I thought it might be some problem in the cache partition but haven't found a way to fix it or if it's even possible to. Apparently everything's working with 4.2.2 but I'd love to go back to 5.1.1!
Thanks in advance!
dont dirty flash the factory image. make a clean factory image flash
After flashing stock KK or LP, are you also flashing userdata.img and then booting into stock recovery to format/wipe data before booting the ROM for the first time?
audit13 said:
After flashing stock KK or LP, are you also flashing userdata.img and then booting into stock recovery to format/wipe data before booting the ROM for the first time?
Click to expand...
Click to collapse
Haven't tried that, I'll give it a go and post the results here!
I've also noticed the phone isn't receiving any signal and it doesn't display the IMEI anymore..
The lack of an imei is a definite problem. Try flashing the stock LP or KK ROM and check for the imei.
audit13 said:
The lack of an imei is a definite problem. Try flashing the stock LP or KK ROM and check for the imei.
Click to expand...
Click to collapse
Did a clean factory image flash of Lollipop 5.1.1, booted into twrp recovery (I'm not sure how to go back to stock recovery) to wipe the data and got the following message:
E: UnMount: Unable to find partition for path '/sdcard'
E: Mount: Unable to find partition for path '/sdcard'
Updating partition details...
E: Unable to mount '/cache'
...done
E: Unable to mount '/cache'
Full SELinux support is present
E: Unable to mount '/cache'
E: Unable to mount '/cache'
MTP Enabled
Formatting Data using make_ext4fs function.
Ypu may need to reboot recovery to be able to use /data again.
Updating partition details...
E: Unable to mount '/cache'
...done
After that I rebooted the phone and it's been stuck on bootloop again since then.
When you flash a stock ROM, did you flash the recovery.img? Sometimes, I find that only stock recovery can properly format the cache. When flashing my Nexus 5 to stock from a custom ROM, I get an error message when I boot into stock recovery that the cache has an invalid format. Once I perform a factory wipe, the cache is properly formatted and wiped.
audit13 said:
When you flash a stock ROM, did you flash the recovery.img? Sometimes, I find that only stock recovery can properly format the cache. When flashing my Nexus 5 to stock from a custom ROM, I get an error message when I boot into stock recovery that the cache has an invalid format. Once I perform a factory wipe, the cache is properly formatted and wiped.
Click to expand...
Click to collapse
Yeah, I flashed the images for boot, recovery, system, userdata and cache separately. I'll look up how to get back into stock recovery now and I'll try what you've said!
If recovery.img was flashed, the phone should not have TWRP, it should be a stock recovery. If stock recovery cannot be flashed, this leads to me believe that something is wrong with the memory chip.
audit13 said:
If recovery.img was flashed, the phone should not have TWRP, it should be a stock recovery. If stock recovery cannot be flashed, this leads to me believe that something is wrong with the memory chip.
Click to expand...
Click to collapse
I tried it again, flashed everything including recovery, went into stock recovery mode and wiped the data. Apparently its back to being stuck on bootloop
Use fastbot commands to erase cache and userdata. Then use fastboot to flash the userdata.img file, boot directly to recovery, and wipe again.
audit13 said:
Use fastbot commands to erase cache and userdata. Then use fastboot to flash the userdata.img file, boot directly to recovery, and wipe again.
Click to expand...
Click to collapse
Did it, still stuck on bootloop... Not sure if it can be somehow related but I got this message when I booted into recovery
The recovery screen looks correct because, after flashing userdata.img, you must format in stock recovery.
I am at a loss as to why 4.2.2 works while kk and LP do not.
audit13 said:
The recovery screen looks correct because, after flashing userdata.img, you must format in stock recovery.
I am at a loss as to why 4.2.2 works while kk and LP do not.
Click to expand...
Click to collapse
Ah, thanks for the help, anyway!
If someone else knows what to do.. The phone is now back to the initial message "android is starting... optimizing apps". Kinda of losing hope now
I've done this to my Nexus 5 once, too.
You basically screwed your cache partition.
Boot into the bootloader. Hook the phone up to your pc and open the command prompt.
Enter these commands:
fastboot erase cache
fastboot format cache
fastboot reboot-bootloader
When successful boot into recovery and the errors should be gone.
You should be able to flash a new rom now.
playitlouder said:
I've done this to my Nexus 5 once, too.
You basically screwed your cache partition.
Boot into the bootloader. Hook the phone up to your pc and open the command prompt.
Enter these commands:
fastboot erase cache
fastboot format cache
fastboot reboot-bootloader
When successful boot into recovery and the errors should be gone.
You should be able to flash a new rom now.
Click to expand...
Click to collapse
This got rid of the unable to mount cache error, flashed the rom again but it's still stuck on bootloop :/
thafuchs said:
This got rid of the unable to mount cache error, flashed the rom again but it's still stuck on bootloop :/
Click to expand...
Click to collapse
Okay. Progress
You have probably already nuked all your data. So I would suggest erasing and formatting everything again and then flash the newest factory image.
Enter bootloader again, on your pc do the following:
fastboot erase system
fastboot format system
fastboot erase data
fastboot format data
fastboot reboot-bootloader
Then grab the factory image, open the flash_all.bat file in an text editor (either use windows notepad, or grab notepad++).
You have to "cd" to the directory of your factory image. I would suggest to type "c:" *press enter* then cd *pull the folder that contains the factory image into the command prompt* *press enter*.
If you type "dir" now you should get your factory image directory.
Now just type in every command from the flash_all.bat one by one. Report, if there are any errors.
playitlouder said:
Okay. Progress
You have probably already nuked all your data. So I would suggest erasing and formatting everything again and then flash the newest factory image.
Enter bootloader again, on your pc do the following:
fastboot erase system
fastboot format system
fastboot erase data
fastboot format data
fastboot reboot-bootloader
Then grab the factory image, open the flash_all.bat file in an text editor (either use windows notepad, or grab notepad++).
You have to "cd" to the directory of your factory image. I would suggest to type "c:" *press enter* then cd *pull the folder that contains the factory image into the command prompt* *press enter*.
If you type "dir" now you should get your factory image directory.
Now just type in every command from the flash_all.bat one by one. Report, if there are any errors.
Click to expand...
Click to collapse
Okay, got some errors on the way... trying to erase data failed (Remote: partition table doesnt exist), format data failed too (formatting is not supported for filesystem with type ' '.)
Also, on the last command:
.\fastboot -w update .\image-occam-lmy48t.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.img'
[...]
checking version-bootloader
FAILED
Device version-bootloader is 'MAKOZ10o'
Update requires 'MAKOZ30f'
Rebooted and its now stuck on google logo
Sorry, you should have typed: (it obviously cannot format something that is not there )
fastboot erase userdata
fastboot format userdata
Have you flashed the bootloader?
Have you rebooted after flashing the bootloader?
fastboot flash bootloader bootloader-mako-makoz30f.img
fastboot reboot-bootloader
Don't forget to also flash the radio.
These "does not contain" errors are normal.
playitlouder said:
Sorry, you should have typed: (it obviously cannot format something that is not there )
fastboot erase userdata
fastboot format userdata
Have you flashed the bootloader?
Have you rebooted after flashing the bootloader?
fastboot flash bootloader bootloader-mako-makoz30f.img
fastboot reboot-bootloader
Don't forget to also flash the radio.
These "does not contain" errors are normal.
Click to expand...
Click to collapse
Okay, I've flashed bootloader, rebooted, flashed radio, rebooted, typed the update command but the checking of bootloader version failed again.. rebooted and its back to being stuck on google logo
Hello guys,
Sorry for my bad English
My phone just turned off even if the battery is almost full. When I turned it on its stuck in a boot loop. Sometimes it's goes to a screen where it would say process not responding. It's still on the stock ROM and recovery. I didn't try to root it or flash anything on it.
I tried some troubleshooting like flashing the firmware from the Asus website but it didn't work. Please help
Have you try flashing from Micro SD card in stock recovery?
M Huzaifah said:
Have you try flashing from Micro SD card in stock recovery?
Click to expand...
Click to collapse
Thank you for the reply bro. I already did and it's still not working.
To reset the phone in cases like this, one could also use fastboot.
Boot in fastboot mode by pressing VolumeUp button while switching on the phone, then connect the phone to a PC with a usb cable (you must have fastboot/adb drivers installed). You can now open a command prompt and use the commands:
Code:
fastboot erase cache
fastboot erase userdata
fastboot erase system
The second command erase all the user's data on the phone.
The last command erases the operating system and you must install the full firmware in zip format from the recovery afterward (with a microSD card or with a PC via ADB sideload).
you can install custom recovery?
I had a boot loop issue too. I could solve it by entering fastboot and trying using the defaut roms boot.img through fastboot. You can extract the boot.img from any firmware image file from the Asus site.
Code:
fastboot boot boot.img
BubuXP said:
To reset the phone in cases like this, one could also use fastboot.
Boot in fastboot mode by pressing VolumeUp button while switching on the phone, then connect the phone to a PC with a usb cable (you must have fastboot/adb drivers installed). You can now open a command prompt and use the commands:
Code:
fastboot erase cache
fastboot erase userdata
fastboot erase system
The second command erase all the user's data on the phone.
The last command erases the operating system and you must install the full firmware in zip format from the recovery afterward (with a microSD card or with a PC via ADB sideload).
Click to expand...
Click to collapse
After these commands, had to do a wipe data/factory reset prior to update from sd card (adb sideload not work at alll).
but no luck, keep boot looping...
---------- Post added at 11:26 PM ---------- Previous post was at 11:23 PM ----------
sofamensch said:
I had a boot loop issue too. I could solve it by entering fastboot and trying using the defaut roms boot.img through fastboot. You can extract the boot.img from any firmware image file from the Asus site.
Code:
fastboot boot boot.img
Click to expand...
Click to collapse
this command result error:
downloading 'boot.img'...
OKAY [ 0.796s]
booting...
FAILED (remote: unlock device to use this command)
finished. total time: 0.802s
used this instead: fastboot flash boot boot.img (with boot.img extracted from firmware)
target reported max download size of 268435456 bytes
sending 'boot' (24547 KB)...
OKAY [ 0.813s]
writing 'boot'...
OKAY [ 0.733s]
finished. total time: 1.550s
but my case is serious, giving up
maybe you should unlock the bootloader before trying those commands
why don't u try, adb sideload option once, give it a try
i dont know what firmware my dads ze550kl is...
and it is bootlooping continously....
what is best files to flash via recovery update from sd card method?
i want to save my dads internal memory
Try this:
fastboot boot recovery.img
Click to expand...
Click to collapse
This may result an error if you don't flash the right file,it depends on your firmware version. I have a file that works on lolipop (twrp.).
I had the same issue, as my device was on warranty period i took it to the service centre and they said the mother board is damaged
Im facing the same problem I installed a new ROM from SD card and it was successfully done but the phone is still stuck in boot loop and unfortunately my USB debugging is disabled my bootloader is locked and my phone is not rooted and it's in stock recovery can anyone please help me
BubuXP said:
To reset the phone in cases like this, one could also use fastboot.
Boot in fastboot mode by pressing VolumeUp button while switching on the phone, then connect the phone to a PC with a usb cable (you must have fastboot/adb drivers installed). You can now open a command prompt and use the commands:
Code:
fastboot erase cache
fastboot erase userdata
fastboot erase system
The second command erase all the user's data on the phone.
The last command erases the operating system and you must install the full firmware in zip format from the recovery afterward (with a microSD card or with a PC via ADB sideload).
Click to expand...
Click to collapse
heyy, even i deleted recovery by using
fastboot erase recovery
then, after that my phone stucked on fastboot mode..
and when i flash the recovery , it finished propery but there is nothing happen in my phone still stucked into fastboot mode..
when i press power+volume(-) only fastboot mode is opened..
what to do now??
how to reinstall bootloader (recovery or twrp)??
plz help guyzz//:crying::crying:
I face the same bootloop problem with my mother's cellphone. The bootloader is locked and USB debug is disabled.
I tried to flash stock img via adb sideload, and although it succeed, after factory reset in Recovery (and pull battery several time) I could finally get into the "setup wizard" of Android system.
However, the system will go into bootloop again when the wizard goes to "wifi" setup. The phone will not go into setup wizard again unless I do a factory reset (and battery pull) again...
It seems there are some hardware failure at Wifi component (Since I already erase all \data, \cache), and this failure caused reboot of the system...
Any idea?
mayankarya837 said:
heyy, even i deleted recovery by using
fastboot erase recovery
then, after that my phone stucked on fastboot mode..
and when i flash the recovery , it finished propery but there is nothing happen in my phone still stucked into fastboot mode..
when i press power+volume(-) only fastboot mode is opened..
what to do now??
how to reinstall bootloader (recovery or twrp)??
plz help guyzz//:crying::crying:
Click to expand...
Click to collapse
hey did u finnd any solution for this>???
hello all,
my yureka(a05510) CAN boot into bootloader and recovery,
Ive tried flashing roms, different recoveries(twrp v3.00 and 2.8), formatting data, mount, resizing partitions, annabathinas method, flashing fastboot images(cm-12.0-YNG1TAS0W0-tomato-signed-fastboot.zip) through fastboot commands and batch files like flash-all.bat (lots of times) and even YGDP method for flashing stock firmware(gives unknown error:5 last error:997 msg: CP8675_I02_P1 , download failed please try again.) i even tried writing emmc img to micro sd(i believe used when phone does not boot into fastboot mode, though NOT my case) and hoped it would change something but that failed too.
please help. thanks in advance.
is your problem solved ? because i am facing the same issue right now and i am not able to find any way out
Pranay_619 said:
is your problem solved ? because i am facing the same issue right now and i am not able to find any way out
Click to expand...
Click to collapse
Fastboot erase system
Fastboot erase cache
Fastboot erase userdata
Sent from my AO5510 using Tapatalk