Related
I am trying to revert my us wifi xoom to stock
I can get in to fastboot
I can flash boot recovery and userdata
However every time I try and flash system it fails with failed to process command 0x20000000
I am currently running a rooted 3.2
Anyone have any ideas?
Thanks
Tim
What's your host OS, I flash my MZ601 (UK3g) via an elevated command prompt (Win7x64) and it works fine here.
I have this little lot in a batch file I run.
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
I am doing this in Mac OS but I can reboot and try it in windows
OK thanks for the tip the flash went fine in windows
What happens if you are rooted and accept the over the air update? Will it just unroot and return to stock without any problems?
Nexus 7 was rooted,unlocked bootloader and was running paranoid anroid 3.90+ i think . i plugged it into the computer to get a new rom using nexus root toolkit v1.7.2. i was asked to update a few things, so i clicked yes. i then tried to flash stock + unroot and chose 4.3 cause i wanted to try the new OS. but i guess something happened because when i turned my nexus 7 back on i was stuck on the load screen (GOOGLE image with a unlocked lock) i could cycle thru a few options using volume keys (start,recovery,power off) .all of them seemed useless as they would just bring me back to where i was.when clicking start "booting failed" come up on the upper left side. when trying to flash stock +unroot using NRT i get up to the sending "bootloader" part and my nexus 7 just freezes, how do i fix this. please and thanks
download the factory image from the google factory image and extract the archive.
try flashing the bootloader manualy with fastboot.
locate your fastboot binary and copy the bootloader image to that directory.
open a commandline in that directory and type
fastboot flash bootloader name-of-bootloader.img
after that you can try to flash the whole factory image with the flash-all.sh script.
Simple
dieselmonkeyy said:
i could cycle thru a few options using volume keys (start,recovery,power off) .all of them seemed useless as they would just bring me back to where i was.when clicking start "booting failed" come up on the upper left side.
Click to expand...
Click to collapse
Boot failed??? That's a bad flash of the stock ROM. I had the same problem at my first attempt trying to flash Stock ROM, but don't worry! Let's do this:
WARNING: Before you continue you are accepting that I'm not responsible of anything can happen to your Nexus and your battery is fully charged.
When you download the stock ROM you have to uncompress the zip file. You will find the bootloader and another zip.
Uncompress that zip file, put fastboot program, the bootloader and the files together.
Then start your Nexus into bootloader mode, connect it to your PC, open a console (cmd for Windows, Terminal for Linux and Mac OS X) and type this:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
WARNING: Your Nexus is FULLY EMPTY!!! Don't reboot it because it can get a full brick (It will not turn on any more).
Now type this:
fastboot flash bootloader bootloader-grouper-X.XX.img
NOTE: Replace X.XX with your version.
Now type:
fastboot reboot-bootloader
Your Nexus will reboot.
Type this:
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash system system.img #Will take a very long time. DON'T INTERRUPT THE PROCESS!!!!!
fastboot flash userdata userdata.img
Now reboot again with:
fastboot reboot-bootloader
Re-unlock bootloader to get a full wipe:
fastboot oem lock
Reboot again:
fastboot reboot-bootloader
And then unlock the bootloader:
fastboot oem unlock
Press "Yes" to the petition screen and reboot:
fastboot reboot
Ready the Nexus!
I had the same problem and I did this.
I hope I can help you.
Sorry for my bad English. I'm from Argentina and I'm learning.
Well,
Good luck!
MlucianoEze said:
Boot failed??? That's a bad flash of the stock ROM. I had the same problem at my first attempt trying to flash Stock ROM, but don't worry! Let's do this:
WARNING: Before you continue you are accepting that I'm not responsible of anything can happen to your Nexus and your battery is fully charged.
When you download the stock ROM you have to uncompress the zip file. You will find the bootloader and another zip.
Uncompress that zip file, put fastboot program, the bootloader and the files together.
Then start your Nexus into bootloader mode, connect it to your PC, open a console (cmd for Windows, Terminal for Linux and Mac OS X) and type this:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
WARNING: Your Nexus is FULLY EMPTY!!! Don't reboot it because it can get a full brick (It will not turn on any more).
Now type this:
fastboot flash bootloader bootloader-grouper-X.XX.img
NOTE: Replace X.XX with your version.
Now type:
fastboot reboot-bootloader
Your Nexus will reboot.
Type this:
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash system system.img #Will take a very long time. DON'T INTERRUPT THE PROCESS!!!!!
fastboot flash userdata userdata.img
Now reboot again with:
fastboot reboot-bootloader
Re-unlock bootloader to get a full wipe:
fastboot oem lock
Reboot again:
fastboot reboot-bootloader
And then unlock the bootloader:
fastboot oem unlock
Press "Yes" to the petition screen and reboot:
fastboot reboot
Ready the Nexus!
I had the same problem and I did this.
I hope I can help you.
Sorry for my bad English. I'm from Argentina and I'm learning.
Well,
Good luck!
Click to expand...
Click to collapse
what do i type into cmd inorder to be able to type
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
and get it to work. im a noob . thanks in advance
You have to be in the folder with fastboot inside else those commands will not work.
It will be easier if you put the images extracted from the zip into the zip together with the fastboot program.
If you don't understand yet I'll try to be more specific.
Sent from my Nexus 7 using xda app-developers app
dieselmonkeyy said:
what do i type into cmd inorder to be able to type
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
and get it to work. im a noob . thanks in advance
Click to expand...
Click to collapse
It can be intimidating... and the so-called tool-kits don't help you learn
I assume you are using Windows.
follow the unzip instructions from the previous poster. (not quoted here). note the directory.
find the directory containing your android tools... ADB.exe and FASTBOOT.exe.
transfer your unzipped files to this directory. Open your CMD prompt window and change to this directory if necessary.
plug in your Nexus.
type fastboot device at the prompt. MAKE SURE YOUR NEXUS 7 is listed (serial number)
proceed with the complete instructions from the previous poster.
that should do it.
YES!!!
thanks alot for the instructions, it worked!!! i hope people use ur instructions as reference if they have the same problem. THANKS ALOT!!!
dieselmonkeyy said:
thanks alot for the instructions, it worked!!! i hope people use ur instructions as reference if they have the same problem. THANKS ALOT!!!
Click to expand...
Click to collapse
I'm glad the problem is solved. Do not forget to click the THANKS button.
Sent from my Nexus 7 using xda app-developers app
Hello. My brother's Nex 7 is also has this issue. I cannot follow any of the steps as it gets stuck on erasing any of the partitions. I tried erasing those partitions in any order and they still get stuck. His device was stock and bootloader locked too. When I try to unlock the bootloader, it gets stuck as well at the erasing userdata part. I suspect a bad memory chip. Anyone else experience this?
Yes, mine is sticking on the (bootloader) erasing userdata on bootloader unlock as well.
It also sticks on any fastboot ERASE command.
Factory reset had a bunch of errors and no longer comes up. none of the FLASH commands work because the BOOTLOADER is locked.
And since it freezes on the unlocking bootloader commands I believe I am screwed.
This was a factory installed, never flashed, unlocked or rooted Nexus 7 wifi 2nd gen. After installing the 4.4.2 that popped up it loaded once then crashed and never loaded again
I have tried every tool I can find. They all stick on the erase part.
jophisdrazin said:
Yes, mine is sticking on the (bootloader) erasing userdata on bootloader unlock as well.
It also sticks on any fastboot ERASE command.
Factory reset had a bunch of errors and no longer comes up. none of the FLASH commands work because the BOOTLOADER is locked.
And since it freezes on the unlocking bootloader commands I believe I am screwed.
This was a factory installed, never flashed, unlocked or rooted Nexus 7 wifi 2nd gen. After installing the 4.4.2 that popped up it loaded once then crashed and never loaded again
I have tried every tool I can find. They all stick on the erase part.
Click to expand...
Click to collapse
Send your device for repair. My brother did so. My suspicions were correct. A faulty chip. They replaced the whole board, according to my brother.
Sent from my Nexus 7 using Tapatalk
Hi there,
I think I screwed in such a fashioned manner that I did not spot any spot to better expose my issue.
I run a Nexus 4 root which used to run fine with 4.3.
I did ota to Nexus 4.4 failure.
Then I did Efrant guide (without step 10) to go 4.4, it worked.
fastboot devices
fastboot reboot-bootloader
fastboot flash bootloader bootloader-mako-makoz20i.img
fastboot reboot-bootloader
fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.84.img
fastboot reboot-bootloader
fastboot flash system system44.img
fastboot flash boot boot44.img
fastboot flash recovery recovery44.img
fastboot format cache
fastboot reboot
I had really bad experience with kitkat. No notification, sms history gone, home virtual button not working (only blipping), same for the top right notification menu.
Well I thought going to 4.3 would be best.
I did 4.3 through the same steps with different archives and boot loop at the X.
Then I tried a 4.2.2 but I did a huge mistake, I did it with Nexus 7 files. After sweating a bit I got it back in fastboot mode.
Then I tried 4.3 occam and 4.4 occam. Bootloop, old style and new one.
Now I can try 4.2.2 or 4.4 with fastboot flash userdata userdata.img
Any clue?
Edit: From Efrants:
Note that some users indicate that they can't get past the X on boot. If this happens to you, reboot into the bootloader and select recovery. Then, when you see the Android with the red exclamation mark, hold power and press volume up to take you to the menu. Wipe cache. If that still doesn't work, boot back into recovery and do a factory reset (this will obviously delete all your data & files in /sdcard...).
I can go to the red exclamation mark.
Than all the combinations I do just reboot me. What is the trick? Power on then volume up? Power on and volume up at the same time? How long should I press?
Try this
Get proper files for let's say 4.3 mako
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
fastboot flash radio radio.img
fastboot flash bootloader bootloader.img
fastboot flash recovery recovery.img
The bootloader and radio being from stock ota from Google, recovery stable custom one
fastboot reboot-bootloader
Make sure all matches
Boot to recovery
Flash ROM of choice, use a 4.3, maybe slimbean
May need to sideload the ROM though
Sent from my Nexus 4 using XDA Premium 4 mobile app
demkantor said:
Try this
Get proper files for let's say 4.3 mako
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
fastboot flash radio radio.img
fastboot flash bootloader bootloader.img
fastboot flash recovery recovery.img
The bootloader and radio being from stock ota from Google, recovery stable custom one
fastboot reboot-bootloader
Make sure all matches
Boot to recovery
Flash ROM of choice, use a 4.3, maybe slimbean
May need to sideload the ROM though
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
OK I get the idea. By flashing the ROM of your choice what do you mean, flashing an OTA zip? I know how tosideload, just trying to understand what to flash.
I am about to try to flash a recovery (twrp) to wipe cache.
I tried and added system and boot.
/!\ fastboot erase system -w Erase all userdata I wanted to do that as a last option... Well now it is done...
The phone is now properly booting a 4.2.2 I will see tonight if I can get it to 4.3 or 4.4
ROM of choice is ROM of your choice, hence the recommendation for slimbean but only a recommendation
The fastboot erase system -w will cover wiping cache, but yeh still download and install the twrp image
Sent from my Nexus 7 using Tapatalk 2
demkantor said:
ROM of choice is ROM of your choice, hence the recommendation for slimbean but only a recommendation
The fastboot erase system -w will cover wiping cache, but yeh still download and install the twrp image
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Well thanks for your help.
I think that my first install of 4.4 was messy. I really suspect that I installed bad radio and or bootloader. Thank you google for giving same name to different versions. Or may be I got some corrupted stuff on userdata?
When I went back to 4.3 I dont know what went wrong, maybe only that cache issue?
Then messing with the nakasi img (call me stupid) could not do any good.
I took too much confidence in messing the previous upgrades and recovering without loosing personnal data...
Now I have a fresh start to think about it...
I've got one question and one question only: how do I install 4.3 again on my nexus 4 again. I have NEVER rooted or flashed my phone. Would really really appreciate all the help I can get.
omairanwar said:
I've got one question and one question only: how do I install 4.3 again on my nexus 4 again. I have NEVER rooted or flashed my phone. Would really really appreciate all the help I can get.
Click to expand...
Click to collapse
fastboot oem unlock
fastboot flash recovery recovery.img
reboot to recovery
flash rom of choice
There are many guides on rooting and fastboot, i would suggest staying away from any toolkit
as if you would like to learn, you wont from a toolkit.
the above take minuets and is far from a difficult task, its a nexus, its meant to be easy.
peek your nose around the forum a bit, you have any issues or are unsure just ask and id be glad to help
I was using 5.0.1, with stock bootloader, stock recovery, actually stock everything except SuperSU added.
I downloaded the 5.1 image from Google, and tried flashing it:
fastboot flash bootloader bootloader-mako-makoz30f.img
fastboot reboot-bootloader
fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1701.06.img
fastboot reboot-bootloader
fastboot update image-occam-lmy47o.zip
Got some missing sig errors, and "failed to allocate xxxxxxxxx bytes" error. Thus after searching for more information I ended up unpacking image-occam-lmy47o.zip and running:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash cache cache.img
Then rebooted. The result is an endless boot animation, regardless of anything I try. Tried restoring my TWRP backup, reflashing 5.1, reflashing 5.0.1, always the same. Last logcat line at boot:
E/kickstart( 233): Sahara protocol completed
Then it's just stuck there. For minutes. For tens of minutes. Looks like forever. Anyone else ever seen this problem, and happens to have a solution? (Preferably without losing my data)
Edit: After a few hours I restored the original (or so I hope) state, by wiping, then flashing 5.0.1, then restoring my backup. But now I don't dare to try flashing 5.1 again. Still would love to hear ideas from who might have seen this problem and knows a solution.
After you've flashed the factory image boot into the stock recovery and do a factory reset.
Sent from my Nexus 9 using XDA Free mobile app
IVBela said:
I was using 5.0.1, with stock bootloader, stock recovery, actually stock everything except SuperSU added.
I downloaded the 5.1 image from Google, and tried flashing it:
fastboot flash bootloader bootloader-mako-makoz30f.img
fastboot reboot-bootloader
fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1701.06.img
fastboot reboot-bootloader
fastboot update image-occam-lmy47o.zip
Got some missing sig errors, and "failed to allocate xxxxxxxxx bytes" error. Thus after searching for more information I ended up unpacking image-occam-lmy47o.zip and running:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash cache cache.img
Then rebooted. The result is an endless boot animation, regardless of anything I try. Tried restoring my TWRP backup, reflashing 5.1, reflashing 5.0.1, always the same. Last logcat line at boot:
E/kickstart( 233): Sahara protocol completed
Then it's just stuck there. For minutes. For tens of minutes. Looks like forever. Anyone else ever seen this problem, and happens to have a solution? (Preferably without losing my data)
Edit: After a few hours I restored the original (or so I hope) state, by wiping, then flashing 5.0.1, then restoring my backup. But now I don't dare to try flashing 5.1 again. Still would love to hear ideas from who might have seen this problem and knows a solution.
Click to expand...
Click to collapse
You only really need to flash the following (unless there is a new bootloader and radio):
fastboot flash boot boot.img
fastboot flash recovery recovery.img (if you are running custom recovery you can skip flashing this)
fastboot flash system system.img
metpage said:
You only really need to flash the following (unless there is a new bootloader and radio):
fastboot flash boot boot.img
fastboot flash recovery recovery.img (if you are running custom recovery you can skip flashing this)
fastboot flash system system.img
Click to expand...
Click to collapse
There was a new radio, but that worked (I accidentally booted normally after flashing it). The rest is the same that I did, except the cache, guess next time I'll try doing it without flashing that one. Do I not have to wipe the cache partition either? (And no custom recovery here, I boot TWRP from my PC via fastboot.)
Edit: Who understands this.... I tried it again tonight, flashed radio, then fastboot update image-occam-lmy47o.zip worked, no error this time, no unpacking, nothing. Just a successful update this time.
Guess that wipe was needed, maybe something was already corrupted before I tried flashing the first time.
Case closed.
Ok I messed up pretty bad this time.
I used my Moto X Pure 2015 for a couple months. Unlocked bootloader, rooted it and used a couple diff ROMs. My father liked the phone, so wanted to give it to him after restoring it to stock, meaning unroot, lock bootloader, restore to factory ROM. But somewhere along the way I messed up and dont know how. I may have tried to flash 5.1.1 when my phone was already updated OTA to 6.0 but I am not sure.
Now I am stuck in a bootloop. The Moto Android logo comes up and it keeps looping there. I can enter bootloader but cannot enter recovery. It goes back to the loop when I attempt to go to recovery mode. I tried flashing (with the Flash-All.bat) packages lying out there, but my device isnt recognized. It says device not found. I cant even restart bootloader through the adb command. I type adb devices in cmd and it says ADB devices attached, but I dont see my device displayed. But Device Manager lists my phone as Motorola ADB Device.
I took a chance and sent it to Motorola......................... surprise surprise...../s , they refused to fix it coz of the unlocked bootloader(even with a fee).
So, now I cant flash anything, I cant go to recovery, nor can get the phone to boot up.
Have I lost the device completely? I dont have any nandroid backups either.
Any help is greatly appreciated.
Ok. I made some progress. I Uninstalled my device drivers, reinstalled from the Motorola website. I am able to flash things from fastboot.
I did the following for MM6.0
adb reboot-bootloader
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
fastboot erase cache
fastboot erase userdata
fastboot reboot
Everything was successful.
Now I can boot into the OS.
But now my WIFI isnt working. I go to settings and try to turn it on, but it doesnt.
Can someone help me here>?
nikhilnagaraj24 said:
Ok. I made some progress. I Uninstalled my device drivers, reinstalled from the Motorola website. I am able to flash things from fastboot.
I did the following for MM6.0
adb reboot-bootloader
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
fastboot erase cache
fastboot erase userdata
fastboot reboot
Everything was successful.
Now I can boot into the OS.
But now my WIFI isnt working. I go to settings and try to turn it on, but it doesnt.
Can someone help me here>?
Click to expand...
Click to collapse
are you sure you flashed everything correctly?
I don't know directions or anything, but I can tell you from other posts on the moto x pure forum that your not the first to lose wifi after restoring stock. To my knowledge you need to down grade to the original factory Android version, not just 5.1 or whatever, it HAS to be the original Android version, AND original baseband and system version, then upgrade from there. Hour that helps a bit, but do some searching and I'm sure you will find what I mean.
Thanks for your reply guys. I eventually fixed it. I now am running the TruPure ROM and everything seems to be working fine.
Except the the MicroSD card that I had 'adopted' is now write protected. I am not finding any luck trying to salvage that. I dont care about my data on it, just want it to be usable. I read somewhere that the card, once adopted, will only work on that ROM that it was originally adopted on. I even tried flashing the other ROM (OrionOS) but no go. My phone doesnt recognize the card except in Recovery. Computer recognizes it but I cant do anything since it is write protected. I tried DISKPART, the regedit fix and a bunch of other stuff. Didnt help. Its a brand new card, so I dont believe the card has gone faulty. Any idea on how to fix it?
nikhilnagaraj24 said:
Thanks for your reply guys. I eventually fixed it. I now am running the TruPure ROM and everything seems to be working fine.
Except the the MicroSD card that I had 'adopted' is now write protected. I am not finding any luck trying to salvage that. I dont care about my data on it, just want it to be usable. I read somewhere that the card, once adopted, will only work on that ROM that it was originally adopted on. I even tried flashing the other ROM (OrionOS) but no go. My phone doesnt recognize the card except in Recovery. Computer recognizes it but I cant do anything since it is write protected. I tried DISKPART, the regedit fix and a bunch of other stuff. Didnt help. Its a brand new card, so I dont believe the card has gone faulty. Any idea on how to fix it?
Click to expand...
Click to collapse
if you had an sd card to pc adapter so you can format it from the pc?_?