Related
Something went haywire when trying to update Amon_RA's new recovery image. I now can't get into recovery and my ROM wont load. All I have is fastboot. I need to load a new recovery image to get into recovery but haven't been able to using the ADB. I've tried the various methods I've seen online with no success. Any advice?
I only rooted my phone around 6 hours ago, so I'm hoping this is what you meant. I was able to use fastboot to boot into a recovery ROM. Try using:
fastboot boot XXX.img
That should allow you to boot straight into it.
Yes I can...will you try copy recovery to SDK\tools?
Reavern said:
I only rooted my phone around 6 hours ago, so I'm hoping this is what you meant. I was able to use fastboot to boot into a recovery ROM. Try using:
fastboot boot XXX.img
That should allow you to boot straight into it.
Click to expand...
Click to collapse
Its a .zip file tho. I've tried "fastboot flash_image recovery..." command but it didn't work.
SarDroid...huh? What do you mean?
staunty said:
Its a .zip file tho. I've tried "fastboot flash_image recovery..." command but it didn't work.
SarDroid...huh? What do you mean?
Click to expand...
Click to collapse
I think you can only flash official images using fastboot. I'm you can use "fastboot boot recovery.img" to load something like Cyanogen's recovery image you will get ADB access. From there you should be able to flash anything.
put recovery in your sdk tools folder
and boot to fastboot
and
fastboot flash recovery recoveryxxxx.img
also check Amon_RA's post where you got the recovery from it tells you how to do it
sitimber said:
put recovery in your sdk tools folder
and boot to fastboot
and
fastboot flash recovery recoveryxxxx.img
also check Amon_RA's post where you got the recovery from it tells you how to do it
Click to expand...
Click to collapse
OK, I'm still not having any luck. Here is what I've done...I found the .img file for a previous recovery image. All the newer ones seem to be .zip files. For the recovery image, it won't recognize a .zip. So, I put the "recovery-RA-dream-v1.3.2.img" image in my AndroidSDK\tools\ folder. Then, in fastboot, I did "fastboot flash recovery..." and it said okay. Rebooted but it still didn't reboot to recovery when I held down home button.
staunty said:
OK, I'm still not having any luck. Here is what I've done...I found the .img file for a previous recovery image. All the newer ones seem to be .zip files. For the recovery image, it won't recognize a .zip. So, I put the "recovery-RA-dream-v1.3.2.img" image in my AndroidSDK\tools\ folder. Then, in fastboot, I did "fastboot flash recovery..." and it said okay. Rebooted but it still didn't reboot to recovery when I held down home button.
Click to expand...
Click to collapse
do
Code:
fastboot boot recovery.img
let the phone reboot, dont touch and anything. you could also try
Code:
fastboot flash recovery recovery.img
have you unzipped the zip files they mght just be .img inside
I have the same issue. but when I follow the steps to flash or boot the recovery.img cmd prompt just says
sending 'recovery' <4166 kb>... FAILED <remote: not allow> finished.
cd to sdk tools (placed recovery.img here)
fastboot boot recovery.img
fastboot flash recovery recovery.img
tried it again and
Install androidsdk and get a copy of a recovery image for your device. Copy the .img to the tools folder in \androidsdk and rename file to recovery.img (for simplicity later). Connect the phone to PC with USB. Power up phone while holding volume down. Get to fastboot USB, open up command prompt (elevated if vista or 7) and cd to androidsdk\tools. then "fastboot erase recovery" then "fastboot flash recovery recovery.img" then "fastboot reboot".
HI,
before begining you must put the android sdk in the root of the c;/, and suitch off your phone , and hold the back bouton and the end call bouton until you see the 3 android in your fone so ,you try this command to see if the pc reconize your phone :
C:\AndroidSDK>fastboot devices
List of devices attached
XXXXXXXXXXXX fastboot
if you cannot see your IMEI listed you must instal the drivers utilities on your pc
if you see the pc listed the IMEI ,then you can flash the recovery .img .
-Place the recovery image downloaded into the androidsk/tools folder and rename it to recovery.img and try with this command :
fastboot flash recovery recovery.img
that all good luke
Hi guys, how I can achieve this with S-ON? I can't flash SPL because I haven't sdcard and using ADB don't know, any help on this?
I have the exact same issue.
I only have fastboot access however I always get remote: not allow. ( Perfect SPL )
Phone Stats
HTC Magic 32A S-ON H
HBOOT 1.76.0010 (SAPP50000)
CPLD-12
RADIO 6.35.16.19
I have created a gold card and tried flashing a sappimg.zip file but that gave me wrong model ID.
Anyone have any idea what I can do?
Does anyone have the link for the stock recovery for 2.2 build 318?
To flash it its just fastboot -i 0x413c flash recovery <image name> correct in fastboot mode?
Flash this via fastboot Stock_Recovery and you'll be able to re-flash the stock 318 rom.... I've tested it... It works
thx i appreciate it.
I might consider trying 318 with Perf fix. Heard good things about it. By the way, where can I get the stock 318 rom?
Spectre51 said:
Does anyone have the link for the stock recovery for 2.2 build 318?
To flash it its just fastboot -i 0x413c flash recovery <image name> correct in fastboot mode?
Click to expand...
Click to collapse
Not Android Development
Please Post in the correct Forums
Moving to General
Before asking for Anything next time can you please do a SEARCH
The Recovery has been posted many times
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.
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
I need the flashable stock rom for 2.21.40.30. Can someone give me the link
All the ROM downloads can be found here: https://www.asus.com/support/Download/39/1/0/2/96nqlxHp1VKV4Rdz/32/
Firmware you want:
WW SKU (recommended)
TW SKU
CN SKU
CHT SKU
It's always recommended to after downloading the ZIP (on any stock version), reboot to droidboot then:
Guide for Zenfone 5 (T00J - A501CG, T00F - A500CG) only!
From inside the ZIP, extract the files fastboot.img (note that sometimes fastboot.img comes as droidboot.img), recovery.img and ifwi.zip
From ifwi.zip extract the files dnx_fwr_ctp_a500cg.bin and ifwi_ctp_a500cg.bin
Now, flash the files in the following order (via droidboot):
NOTE: The first line below, the fastboot.img I mention is of 2.21.40.30, use this fastboot image to flash a dnx and a ifwi. Other ones may not work! As you using this version, I'm not sending you it separately
Code:
fastboot flash fastboot fastboot.img
fastboot reboot-bootloader
fastboot flash dnx dnx_fwr_ctp_a500cg.bin
fastboot flash ifwi ifwi_ctp_a500cg.bin
fastboot flash fastboot fastboot.img
fastboot flash recovery recovery.img
fastboot reboot-bootloader
It's also ULTRA recommended that you erase your data and cache:
Code:
fastboot erase data
fastboot erase userdata
fastboot erase cache
Now flash the ROM via adb sideload on recovery
I recommend doing this before flashing any stock ROM when coming from a custom ROM.
Thanks
No I meant flashable from TWRP recovery. I learned that method by heart
In cmd typing "adb devices" shows empty list.
all drivers are already installed.
my phone is not shown in 'adb usb" also.
help me