Database Users

Can you load a new recovery image via fastboot?

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?

[Q] problems with clockworkmod recovery (device almost dead)

ok, so i wanted to try Cyanogenmod 7.
i followed the steps:
1- rooted the device
2- downgraded to Froyo firmware
3- installed Cyanogenmod 7.20.
all worked fine for almost one week until i updated rom manager from the market.
since the the device led flickers in green and orange. I can get into clockworkmod recovery menu but it lasts for a few seconds and disappears. it appears again and so on.
adb devices returns:
List of devices attached
SH0BHRT09137 recovery
but because it's not stable the same command doesn't return any devices few seconds later.
what shall i do now ?

steps one and two i assume are switched around, try booting into fastboot
if your hboot is still stable you may have more luck here
fastboot works in similar ways as adb - so fastboot devices
if you see yours
then wipe and flash a new recovery via fastboot
fastboot -w
fastboot flash recovery recovery.img
fastboot reboot
(replace recovery.img with whatever name you give that recovery image)

demkantor said:
steps one and two i assume are switched around, try booting into fastboot
if your hboot is still stable you may have more luck here
fastboot works in similar ways as adb - so fastboot devices
if you see yours
then wipe and flash a new recovery via fastboot
fastboot -w
fastboot flash recovery recovery.img
fastboot reboot
(replace recovery.img with whatever name you give that recovery image)
Click to expand...
Click to collapse
Thanks for the info. after i installed fastboot and ran "fastboot devices" i don't get any devices.

are you in fastboot mode within hboot? does your phone say fastboot usb?
write down everything on your phone when you boot into bootloader

demkantor said:
are you in fastboot mode within hboot? does your phone say fastboot usb?
write down everything on your phone when you boot into bootloader
Click to expand...
Click to collapse
strange enough "adb reboot" go the device working ! not sure why it was stuck at ClockMod.
hope this thread help somebody later.

Returning to stock

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.

Nexus 7 Bricked??/Broken

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

YD201 Hardbrick...?

Hi everybody...I'm in trouble with my Yotaphone YD201.
I done format data with TWRP.
Then, I run these commands with Win10 for clean flash of RU144:
Code:
fastboot flash boot {Directory_firmware/boot.img}
fastboot flash -S 512M system {Directory_firmware/system.img}
fastboot flash recovery {Directory_firmware/recovery.img}
fastboot flash cache {Directory_firmware/cache.img}
fastboot flash modem {Directory_firmware/radio/NON-HLOS.bin}
fastboot flash sbl1 {Directory_firmware/radio/sbl1.mbn}
fastboot flash rpm {Directory_firmware/radio/rpm.mbn}
fastboot flash tz {Directory_firmware/radio/tz.mbn}
fastboot flash userdata {Directory_firmware/userdata.img}
fastboot flash aboot {Directory_file__emmc_appsboot.mbn}
fastboot reboot
After the last one, Screen gone black and nothing appends...
Now, adb and fastboot can't contact with Yota ("adb devices" give "<waiting for devices") .
Now, In Win devices, I can find " QHSUSB_BULK".
After some search, I found out that my phone is in a recovery mode of Qualcomm. Does anybody know how to unblock it? Problably I need of specific driver to contact with this phone. Thanks so much!
P.S.: do not esitate to contact me if my english is not clear =)

How about a method like this https://forums.oneplus.net/threads/solution-bricked-oneplus-one-recovery.306306/ but use Yotaphone files instead?

evilracer123 said:
How about a method like this (...) but use Yotaphone files instead?
Click to expand...
Click to collapse
This discussion uses Msm8974DownloadTool.exe from the directory of ColorOS but the wire connection does not work (the file is no longer available, from Mega).
Also, not sure if I can use Msm8974DownloadTool.exe with Yotaphone. Alternatively, what can I use?