I have read the guide and searched for 5 hours and still can't find an answer.
I have a windows 7 computer with the SDK and all drivers installed properly and have both the factory images downloaded from Google. The extracted factory image has been placed in my SDK folder platform-tools. I have been trying to flash the bootloader via fastboot commands. The computer recognizes the nexus 7 and gives me the proper serial number when I do "fastboot devices". I then run through all the commands in the "Guide flashing a factory image", fastboot erase boot, fastboot erase cache, fastboot erase recovery, fastboot erase system, fastboot erase userdata and see that all the commands finish. When I get to fastboot flash bootloader bootloader-grouper-4.13.img the command prompt just hangs and does nothing. In the upper left corner of the Nexus 7 I see signature match but the command line reads sending 'bootloader' <2096 KB>...
OKAY [ 0.265s]
writing 'bootloader'....
I am lost as to what to do. Should I try the command fastboot reboot-bootloader even though I may not have properly flashed the bootloader.img????
Thanks for any help, I have been playing with this since yesterday.
Why did you erase cache, system, recovery etc? Weren't you just updating your hboot?
Usualy not wise to loose power while updating firmware, but if you've been at it for a day you soon will as I don't believe you can charge through bootloader mode.
When flashing through fastboot the update won't take effect until you reboot, if its hung for a while (I mean a real long while as this may not be safe) why not unplug usb, replug, then fastboot flash a recovery quick.
Now get a new download of whatever spl you can find with md5sums. Download and make sure the md5 matches
Now flash that hboot and see what happens
Sent from my HTC Vision using xda premium
I read a lot about problems with that 4.xx bootloader.
Try flashing one of the 3.xx bootloaders from 4.1.x factory images.
Related
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
PROBLEM SOLVED! I used another pc, my usb ports were the problem! I recently got my Nexus 7 (2012), wi-fi only , I unlocked it's bootloader, installer TWRP recovery, and rooted it. For all these operations i used the N7 toolkit , because back then, I was a noob. The rooted tablet (4.2.2) worked Perfectly! But, after about 3 months, it's "volume down" button stopped working. I rebooted it, but it went in bootloader, instead of normal system. So I just select "Start" and it was in Safe Mode! OK, my "volume down" didn't work in Safe Mode (and bootloader mode) neither! And every time I reboot it, it goes to bootloader! I thought that it was a software problem confused , so I began flashing a new ROM. I didn't want to use the toolkit because everyone says that it's bad . I downloaded AndroidSDK, I re-downloaded the ADB and Fastboot drivers, and I downloaded the newer version of the bootloader (4.23, .img) . Tablet was already in bootloader and I connected it to the PC. In platform-tools folder I ran the "fastboot devices" command, and It was able to see it . So I copied the bootloader img to the same folder, and I ran "fastboot flash bootloader bootloader-grouper-4.23.img" . Then I rebooted it into bootloader again. IT WORKED! But, it didn't solve the "volume down" problem. My rooted 4.2.2 and TWRP were still on the system. Everytime I power off the tablet, and then hold the "Power" button, it goes into bootloader. It was that button issue causing that. Then I decided to take it to the service (same place where I bought iw the unloct) , but I couldn't because if they saked bootloader, non-stock recovery and the root, the wouldn't accept the warranty . I decided to download the latest 4.3 stock android, and stock recovery, flash them, and lock the bootloader. I downloaded 4.3 stock from google's official site, (nakasi-jwr66y) and I used the flash-all.bat command that came with it.
.bat command looks like this:
PATH=%PATH%;"%SYSTEMROOT%\System32"
fastboot oem unlock
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader-grouper-4.23.img
fastboot reboot-bootloader
ping -n 10 127.0.0.1 >nul
fastboot -w update image-nakasi-jwr66y.zip
echo Press any key to exit...
pause >nul
exit
I ran it. It successfully did the oem unlock (it was already unlocked) , all the erase commands, and flash bootloader command. But it was stuck on
"fastboot -w update image-nakasi-jwr66y.zip" . It stays steady for about 30secs , and than it says
"sending 'system' (x-kb)"
After some time it just says Data transfer failure(too manly links) ...
I tried the same process billion more times, but same error :/
I tried
-Re-downloading and installing the drivers
-Changing the usb ports, and microUSB cables,
-Restarting the pc (of course)
-Re-downloading the nakasi-jwr66y
-Downloading the twrp recovery (it successfully flashes it)
-Re-downloading the whole SDK
But it DOESN'T WORK? What should I do? Is the volume-down issue hardware or software ?
Sorry for my bad English :////////
P.S. What is the difference between "fastboot flashall" and "fastboot update" ?
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>???
I seem to have an issue that appears frequently, yet I cant find an answer.
This is a fix to Remote: FileWriteFailed
So, I was trying to reflash stock again for multirom and it fails. It can erase everything yet cannot flash anything. Basically:
Writing 'bootloader' (remote: (FileWriteFailed))
It shows up Signature Match, so I decided to continue
It sends boot, boot flashes
Anything else, I get the same Remote FileWriteFailed.
I thought that my partitions killed themselves again, so I tried flashing TWRP
Fails with same error.
I looked and found I can just boot it. So I tried and get this:
Command: fastboot boot twrp.img
downloading boot.img...
FAILED (command write failed (No error)
Restarted bootloader to try again
Recovery flashed. Im feeling confident
I go and try to update via update image
Flash bootloader OKAY
Command: fastboot update -w image-nakasi-ktu84p.zip
Archive doesnt contain *.sig
Checks everything, makes partitions
Everythings okay
Fix is (if you have sdk already)
So, basically, you have to erase System, cache, userdata, boot and recovery with fastboot erase.
Then find your factory image from google and download it
Extract everything and move the image-nakasi-*****.zip and bootloader.img to your sdk folder
Flash bootloader
Use command: fastboot update -w image-nakasi-*****.zip
Wait
Hello, I am trying to flash TWRP to my zenfone, I managed to do it once by some miracle with the exact same setup as I have now.
by typing fastboot devices I get K6AXB7616289*** fastboot
but if I try to flash anything with the phone connected I get no output at all.
If I try to flash with the phone disconnected I get <waiting for any device> and no change when I connect it.
In both of these cases when I disconnect the phone I get:
Sending 'recovery' (31332 KB) FAILED (Write to device failed (No such device))
fastboot: error: Command failed
It is overall wonky and seems to change depending on nothing. Sometimes while writing sudo fastboot reboot bootloader I get to the bootloader as expected, but sometimes I get an error but still manage to get to the bootloader and other times it boots up normally.
I am running ParrotOS from a USB
I also posted in here as my problem is very similar but I hope this post resurrects this particular topic: https://forum.xda-developers.com/t/...but-fastboot-devices-is-working-fine.4295449/
What commands are you using?
Fastboot flash boot boot.img?
The boot.img could be the twrp.img renamed to boot. Img but it should be to recovery I believe.
Fastboot flash recovery twrp.img
Yeah im writing fastboot flash recovery and then the path to my twrp.img. I managed to flash it once after a lot of struggle but now I can't do it again.
After posting I saw that I'm using a USB 3 port and my laptop doesn't have a usb 2 one so I think that might be the issue.
Considering I can get three different outputs from the same command in the span of a couple seconds I think that the problem might be hardware related. I can update once I get my hands on a USB 2 port.
Kaynejulian said:
What commands are you using?
Fastboot flash boot boot.img?
The boot.img could be the twrp.img renamed to boot. Img but it should be to recovery I believe.
Fastboot flash recovery twrp.img
Click to expand...
Click to collapse
I have now tried with a USB 2 port and there is no change.
I have had issue when the phones in fastboot and I'm able to flash via his method. Using platform tools I copy all my IMg's into the folder then open a command prompt window in that folder and fastboot reboot bootloader or fastboot reboot fastboot. Which I learned the hardway is fastbootd mode and then and only then did it actually flash. I also learned the hardway that you boot directly from in fastboot mode or it all just cycles back.
Fastboot reboot.
What version zenfone model and what is system is it running?
If your device is running android 10 or newer then is a different process as you'll need to flash the super.img rather than individual imgs like system vendor product ect
Tue shore image also means it matters where you flash the img
Get a fastboot getvar all printout to me and I'll do what I can to help u get it running again