It took me almost 3 days of constantly trying to unbrick my tablet, so I thought I would post a quick guide of how I ended up doing it.
I only had Fastboot access.. (No ADB, nothing else...) due to my Recovery and Bootloader being corrupted and a failed NVflash installation. Nevertheless, I then proceeded to try hundreds of different things (flashing a straight up blob would not work no matter how many times I tried).
I finally found a solution, I downloaded the oldest blob I could find (and through a lot of work finding a compiler, compiled a BlobExtractor) I then found the bootloader and flashed it using the command.
fastboot -i 0x0b05 flash bootloader bootloader.bin
This got me to a state where I was able to flash a new Stock ASUS JB blob with
fastboot -i 0x0b05 flash system blob
This should restore it completely.
Hope this saves someone a ton of time and money... I will attach the bootloader.bin (as I frankly could not find ANY stock/custom bootloaders for this tablet ANYWHERE)
No Guarantees, but if your soft-bricked with conditions like above... might as well give it a try. :good:
not work!
damn'it again the bootloader is unrecoverable (Error is "Unrecoverable bootloader error (0x000000)") and system not start. However thank you!!! :good:
riderskull said:
damn'it again the bootloader is unrecoverable (Error is "Unrecoverable bootloader error (0x000000)") and system not start. However thank you!!! :good:
Click to expand...
Click to collapse
Were you actually able to over-write the bootloader in the first place? This may be a stupid question, but did you extract the bootloader.bin from the Rar? Note that this is a 9.4.3.30 bootloader, so actually booting with this isn't going to be possible for some but it will setup fastboot conditions enough where you can push in stock blob.
I used a JB 10.6.1.8 blob afterwards.
You may also try flashing the stock recovery file (along side the bootloader)
I'll try to help out more if I can...
I was getting InvalidSize errors when trying to flash a blob on the AndroidRoot bootloader.
iamsobored said:
Were you actually able to over-write the bootloader in the first place? This may be a stupid question, but did you extract the bootloader.bin from the Rar? Note that this is a 9.4.3.30 bootloader, so actually booting with this isn't going to be possible for some but it will setup fastboot conditions enough where you can push in stock blob.
I used a JB 10.6.1.8 blob afterwards.
You may also try flashing the stock recovery file (along side the bootloader)
I'll try to help out more if I can...
I was getting InvalidSize errors when trying to flash a blob on the AndroidRoot bootloader.
Click to expand...
Click to collapse
I extract the bootloader.bin my current versione of bootloader is (if i don't make error) : 1.00e. Released by "WW_epad-10.6.1.8-20130225" A03
How do I know if I am able to overwrite the bootloader ?
riderskull said:
I extract the bootloader.bin my current versione of bootloader is (if i don't make error) : 1.00e. Released by "WW_epad-10.6.1.8-20130225" A03
How do I know if I am able to overwrite the bootloader ?
Click to expand...
Click to collapse
hmm... it did not overwrite then.... you extracted the bin then put it in your folder with fastboot...then ran the command i gave? what output did fastboot give?
I tried flashing this, but my fastboot screen just freezes. Have to manually hold down power to reset, once reset is done I get
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Windows\System32>cd C:\android\sdk\platform-tools
C:\android\sdk\platform-tools>adb reboot-bootloader
(Have to do this to get to bootloader screen, I have infinite bootloop to recovery which has SD mount errors and everything)
C:\android\sdk\platform-tools>fastboot -i 0x0b05 flash bootloader bootloader.bin
sending 'bootloader' (1002 KB)...
(Stuck like this until I reset)
FAILED (data transfer failure (Too many links))
finished. total time: 73.202s
(after manual reset since screen freezes, I let it sit for like 4 minutes since its only a 1002kb file)
---------- Post added at 05:59 PM ---------- Previous post was at 05:57 PM ----------
Also, I have no attached devices under ADB Devices, installed all the right drivers. But its okay, I have new motherboard coming in, just experimenting with this one.
pyovue - If you have ADB access then unbricking it should be easy as you can push and edit any file on the system with it as well as fastboot? Or can ADB & Fastboot not mount (not just the sdcard) anything? If you don't care what happens to your tablet MB, then try this....
fastboot -i 0x0b05 erase system
fastboot -i 0x0b05 erase recovery
Then reboot (this should rid you of your bootloop to recovery and nothing should start)
Then download the stock ASUS Rom (from ASUS, look under Firmware)
Then try sending it with fastboot -i 0x0b05 flash system blob (you will have to extract two zips from the firmware files until you get to a file called "blob" then put it in your fastboot)
I almost guarantee if you have fastboot/adb working there is ALWAYS a way to fix it... only a hardbrick is impossible to fix.
That won't work for people who bricked their tabs with wrong recoveries. They can't use fastboot..
iamsobored said:
pyovue - If you have ADB access then unbricking it should be easy as you can push and edit any file on the system with it as well as fastboot? Or can ADB & Fastboot not mount (not just the sdcard) anything? If you don't care what happens to your tablet MB, then try this....
fastboot -i 0x0b05 erase system
fastboot -i 0x0b05 erase recovery
Then reboot (this should rid you of your bootloop to recovery and nothing should start)
Then download the stock ASUS Rom (from ASUS, look under Firmware)
Then try sending it with fastboot -i 0x0b05 flash system blob (you will have to extract two zips from the firmware files until you get to a file called "blob" then put it in your fastboot)
I almost guarantee if you have fastboot/adb working there is ALWAYS a way to fix it... only a hardbrick is impossible to fix.
Click to expand...
Click to collapse
Yeah, as soon as I use
fastboot -i 0x0b05 flash system blob
The bootloader screen freezes, longest I had it up was 20mins, and battery died, will try again too see if theres any results. Using any type of adb push or pull or even checking the sdcard's directory cant be allowed cause of no adb devices attached.
I duno if im hard bricked, or soft. When I had CWM 6.0.1.3, I couldnt mount anything. So I used
fastboot -i 0x0b05 erase system
fastboot -i 0x0b05 erase recovery
fastboot -i 0x0B05 erase userdata
fastboot -i 0x0B05 erase boot
They were all successful, through adb, and my recovery is now gone. So it boots straight to the white Asus logo screen(Not the flashy animated one), and freezes there. I can hold down while reset to get to bootloader. Flashing stock blob file now, ill post results later, gona leave it on for at least 1 hour. tehehe.
pyovue said:
Yeah, as soon as I use
fastboot -i 0x0b05 flash system blob
The bootloader screen freezes, longest I had it up was 20mins, and battery died, will try again too see if theres any results. Using any type of adb push or pull or even checking the sdcard's directory cant be allowed cause of no adb devices attached.
I duno if im hard bricked, or soft. When I had CWM 6.0.1.3, I couldnt mount anything. So I used
fastboot -i 0x0b05 erase system
fastboot -i 0x0b05 erase recovery
fastboot -i 0x0B05 erase userdata
fastboot -i 0x0B05 erase boot
They were all successful, through adb, and my recovery is now gone. So it boots straight to the white Asus logo screen(Not the flashy animated one), and freezes there. I can hold down while reset to get to bootloader. Flashing stock blob file now, ill post results later, gona leave it on for at least 1 hour. tehehe.
Click to expand...
Click to collapse
Welp, no go. It seems to erase files okay, but not writing files. Oh well. New motherboard will be here tomorrow.
pyovue said:
I tried flashing this, but my fastboot screen just freezes. Have to manually hold down power to reset, once reset is done I get
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Windows\System32>cd C:\android\sdk\platform-tools
C:\android\sdk\platform-tools>adb reboot-bootloader
(Have to do this to get to bootloader screen, I have infinite bootloop to recovery which has SD mount errors and everything)
C:\android\sdk\platform-tools>fastboot -i 0x0b05 flash bootloader bootloader.bin
sending 'bootloader' (1002 KB)...
(Stuck like this until I reset)
FAILED (data transfer failure (Too many links))
finished. total time: 73.202s
(after manual reset since screen freezes, I let it sit for like 4 minutes since its only a 1002kb file)
---------- Post added at 05:59 PM ---------- Previous post was at 05:57 PM ----------
Also, I have no attached devices under ADB Devices, installed all the right drivers. But its okay, I have new motherboard coming in, just experimenting with this one.
Click to expand...
Click to collapse
I'm having a very similar issue, except I'm able to get a "successful" fastboot return from my command prompt. I can only access the bootloader by running "adb reboot-bootloader" My bootloader menu also freezes once the write portion of fastboot starts. I've tried re-loading CWM and loading up TWRP. Everything I've tried always just boots to CWM. My SDCard fails to mount (I can mount manually) and I'm getting "Can't mount /cache/..." errors in CWM. I haven't braved the deletion of the recovery since CWM is all I can get in to.
Any suggestions? Am I out of luck?
after give it
Code:
fastboot reboot
, in the terminal i have this response
Code:
ERROR: could not clear input pipe; result e00002ed, ignoring...
ERROR: could not clear output pipe; result e00002ed, ignoring....
rebooting...
and tablet is freeze. Any solution ?
riderskull said:
after give it
Code:
fastboot reboot
, in the terminal i have this response
Code:
ERROR: could not clear input pipe; result e00002ed, ignoring...
ERROR: could not clear output pipe; result e00002ed, ignoring....
rebooting...
and tablet is freeze. Any solution ?
Click to expand...
Click to collapse
yeah, happens to me too
matt95 said:
yeah, happens to me too
Click to expand...
Click to collapse
Same sort of problem is with me......:crying: any solution please!!!!!!!
I have exactly the same problem and I tried every hint from xdadevelopers.
I hope some one can help us to reanimate our TF300T. I would be very grateful for any information.
I tried the following ...
Code:
fastboot -i 0x0B05 erase cache
fastboot -i 0x0B05 erase userdata
fastboot -i 0x0b05 erase system
fastboot -i 0x0b05 erase recovery
fastboot -i 0x0B05 erase boot
fastboot -i 0x0B05 reboot-bootloader
fastboot -i 0x0b05 flash system blob
... and then my TF300 freeze.
just a friendly bump, though i'm looking into my warranty now...would be great if there was a way to use fastboot to turn off secure/encryption stuff and to make sure its unlocked...our possible way to re-partition...don't even know if that would be helpful...
iamsobored said:
I finally found a solution, I downloaded the oldest blob I could find (and through a lot of work finding a compiler, compiled a BlobExtractor) I then found the bootloader and flashed it using the command.
Click to expand...
Click to collapse
What blob extractor did you use?
---------- Post added at 08:32 PM ---------- Previous post was at 08:05 PM ----------
Nevermind, it was BlobTools.
Everyone please note you will be flashing an ICS bootloader!!!
If you are not on ICS or have Nvflash installed you may wish to blobunpack your own JB bootloader using blobtools.
Please read the OP carefully to see if this truly applies to your tablet.
I will place proper links to blobtools when I'm not on my tablet.
forum.xda-developers.com/showpost.php?p=35208962&postcount=14
When attempting to flash the bootloader I get a FileReadFailed.
When attempting to flash the system it gets stuck sending system. I have left it alone for over 2hrs with no change.
Any ideas?
I can't wait to get home and try this
Sent from my SCH-I535 using xda app-developers app
Related
Wanting to go back to stock on the nexus 7. I have downloaded the factory image but for the life of me cannot figure out how to flash it. I am in the bootloader and i've extracted the image to my adb and fastboot directory. there is a "flash-all.sh" file but I'm unsure what to do with it. Any help would be appreciated. Thanks.
I personally don't remember how to use the .sh files.
But open the file with a text editor such as Notepad++, and you'll see the commands the script will run. You can run them manually.
sh files are purely for Linux users (it's the equivalent of batch files in Windows). Just run the commands in the sh file in your command prompt (or alter them so that it matches your fastboot).
I downloaded the images and looked at the script. Here is what it does.
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader-grouper-3.34.img
fastboot reboot-bootloader
<Wait for it to reboot>
fastboot -w update image-nakasi-jrn84d.zip
And you're done.
Thanks to all three of you. I am now back to stock. I appreciate the help at this crazy hour in the morning.
chris.wueste said:
Thanks to all three of you. I am now back to stock. I appreciate the help at this crazy hour in the morning.
Click to expand...
Click to collapse
Help asap....trying to flash stock file... in adb, I've typed all fast boot commands...I get an error at the " boot loader boot loader grouper" command. It says error, cannot load etc.
gmen78 said:
Help asap....trying to flash stock file... in adb, I've typed all fast boot commands...I get an error at the " boot loader boot loader grouper" command. It says error, cannot load etc.
Click to expand...
Click to collapse
Are you still stuck? What is going on at the moment? What have you tried? PM me if you would rather.
Ya I'm still stuck....tried using wugfresh toolkit to get back to stock but drivers ain't working correctly. I'd rather just flash stock Google image if possible and be done.
Sent from my Galaxy Nexus using Tapatalk 2
Can you use ADB and Fastboot???
Do you know how to use ADB and Fastboot???
If you are stuck returning to stock, I have just posted a full guide in the development section. I just did it myself to make sure that it works. Enjoy.
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.
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
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, 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