Database Users

mytouch 1.2 recovery broken

On test seven, went to flash Amun ras new recovery, didn't know that flashing a recovery is broken in this so now I am stuck with a broken recovery. I tried flashing it via adb shell didn't work, you guys have any suggestions?

Flash the 2010 Engineering SPL, flash recovery, then revert to stock SPL.

Flash via Terminal Emulator. I had to do the same thing.

Guess ill do yhat. I was hoping there was another way cuz i do not like flashing an spl via anything but fastboot lol.

C0dy said:
Flash the 2010 Engineering SPL, flash recovery, then revert to stock SPL.
Click to expand...
Click to collapse
I have the similar problem, i can't access the recovery, i can use the phone, or in the computer (adb) but i don't know how i can flash this without access to the recovery.

p10l1n said:
I have the similar problem, i can't access the recovery, i can use the phone, or in the computer (adb) but i don't know how i can flash this without access to the recovery.
Click to expand...
Click to collapse
Download Terminal Emulator if you don't already have it.
Then follow these steps.
Code:
Copy recovery-RA-sapphire-v1.7.0G.img to the root of your sdcard
start the terminal app
#flash_image recovery /sdcard/recovery-RA-sapphire-v1.7.0G.img

Flashing recoveries is broken in t7 so that wont wrk. What i wanna know is if fladhing an spl via terminal is.

knny1491 said:
On test seven, went to flash Amun ras new recovery, didn't know that flashing a recovery is broken in this so now I am stuck with a broken recovery. I tried flashing it via adb shell didn't work, you guys have any suggestions?
Click to expand...
Click to collapse
Do you have any access via fastboot? You could do a nandroid restore via fastboot then flash a recovery img... if not flashing an spl via goldcard method would work to let you fastboot flash a rom and recovery image.. perhaps..
I of course could be way off but I'm trying to help you brain storm.

What are the commands to nand restore via fastboot?

depends if you've done a backup via the recovery tool or the fastbooter.
If you did it on your recovery screen and it saved to the sd card you'll need to copy these files from the NAND folder in your sd card
Code:
data.img
system.img
boot.img
saved then in the /tools area of where ever you set up AndroidSDK. in my case it's /AndroidSDK/Tools/ (might be different for you)
Once that's done flashing codes are below. if you did NAND via fastbooter just use these codes.
Code:
fastboot devices (make sure it sees you)
fastboot flash system system.img
it will say Sending, then writing and say OKAY if it was successful
then type
fastboot flash userdata data.img
wait for the second OKAY and type
fastboot flash boot boot.img
wait for the second OKAY and type
fastboot reboot
Hopefully that works for you.

Ah okay that was simple, idk why I didn't think of it. I'm setting up sdk on my buddies laptop right now n then I'm going to get this thing breathin correctly again.

knny1491 said:
Ah okay that was simple, idk why I didn't think of it. I'm setting up sdk on my buddies laptop right now n then I'm going to get this thing breathin correctly again.
Click to expand...
Click to collapse
me too, hope it works out for you. if it doesn't I'll keep brain storming with you.

I'm just REALLY trying not to go throguh the root process again lol, I think I'm just going to adb shell the SPL and then fastboot the recovery given its the easiest way I can think of.

I also just thought of the idea that you could simply do
Code:
fastboot erase recovery
fastboot flash recovery (recoverynamehere)

I need to flash the ENG spl first, which I am doing right now lol.

What is the appropriate command for flashing the spl? I did this:
adb shell
mount /sdcard
cd /sdcard/
flash_image hboot hboot.img
and via terminal:
su
flash_image hboot /sdcard/hboot.img
It said it couldn't find the hboot partition, my guess is I need to figure out what the correct partition name is.

Anybody know the command?

Heellllloo? Lol need some help here

Anyone got anything?

Fixed
-------------------------------------
Sent via the XDA Tapatalk App

[Q] MT3G bad recovery flash, stuck

Hi,
I have a mt3g, TMobile. CyanogenMod 6.1.0, ClockWork recovery. Used ROM Managed to flash Amon Ra recovery, since I needed to re-calibrate the battery. It asked me to pick phone model, picked Ion/MyTouch 3G. After reboot:
- Stuck on splash screen if I try to go to recovery
- When booted up - a bunch of force closures, keeps playing a ringtone over and over and...
Everything I tried to do through ROM Manager didn't help.
Any help is appreciated.
Thanks.

truss said:
Hi,
I have a mt3g, TMobile. CyanogenMod 6.1.0, ClockWork recovery. Used ROM Managed to flash Amon Ra recovery, since I needed to re-calibrate the battery. It asked me to pick phone model, picked Ion/MyTouch 3G. After reboot:
- Stuck on splash screen if I try to go to recovery
- When booted up - a bunch of force closures, keeps playing a ringtone over and over and...
Everything I tried to do through ROM Manager didn't help.
Any help is appreciated.
Thanks.
Click to expand...
Click to collapse
Do you still have root? If you can get into ROM manager, reflash clockwork recovery, then wipe cache, dalvik, and run a fix permissions. That should get you back up and running long enough to try again to flash amon ra.
Not sure if the oem spl will let you fastboot flash a new recovery but that's your most reliable bet.
It sounds like it might be time to do a full wipe and reflash anyway. Have you heard of Ohsaka's SuperWipe?

I tried reflashing Clockwork through ROM Manager. It says "root granted", "clockwork flashed" immediately. When I try to boot into recovery - I get stuck on green MyTouch screen forever. Battery pull is the only way out.
I guess the problem is that I cannot get to any recovery anymore. Any ideas?

Do you have fastboot. If so you can flash recovery from there.

kodjo said:
Do you have fastboot. If so you can flash recovery from there.
Click to expand...
Click to collapse
Can I do that through adb shell? I don't think I built fastboot.

truss said:
Can I do that through adb shell? I don't think I built fastboot.
Click to expand...
Click to collapse
Fastboot is a different mode. Boot into hboot (vol down + power I think) and then select fasboot from the menu. Then plug into computer. From a command prompt type:
fastboot flash recovery recovery.img
The recovery needs to be in your tools or platform-tools folder and named recovery.img for this to work. Otherwise it would be fastboot flash recovery c:\path\to\recoveryfilename.img. Make sense?
Link to Amon_Ra Recovery 1.7 for MT3G 32B. http://www.filefactory.com/file/caa48b0/n/recovery-RA-sapphire-v1.7.0G-cyan.img
Otherwise keep trying with ROM Manager. Might take a few attempts to get recovery to stick, even temporarily. It did for me. Flash once then flash again. There's also an option in ROM Manager settings to erase recovery prior to flashing. Check that and see if it helps.

Phateless said:
Fastboot is a different mode. Boot into hboot (vol down + power I think) and then select fasboot from the menu. Then plug into computer. From a command prompt type:
fastboot flash recovery recovery.img
The recovery needs to be in your tools or platform-tools folder and named recovery.img for this to work. Otherwise it would be fastboot flash recovery c:\path\to\recoveryfilename.img. Make sense?
Link to Amon_Ra Recovery 1.7 for MT3G 32B.
Otherwise keep trying with ROM Manager. Might take a few attempts to get recovery to stick, even temporarily. It did for me. Flash once then flash again. There's also an option in ROM Manager settings to erase recovery prior to flashing. Check that and see if it helps.
Click to expand...
Click to collapse
I appreciate your help.
When I try to flash recovery.img, I get this: error: cannot load `recovery.img`
When I try running fastboot with absolute path, I get: FAILED (remote: not allow). Is there a way to fix this?
Tried flashing through ROM Manager many times - no result.

truss said:
I appreciate your help.
When I try to flash recovery.img, I get this: error: cannot load `recovery.img`
When I try running fastboot with absolute path, I get: FAILED (remote: not allow). Is there a way to fix this?
Tried flashing through ROM Manager many times - no result.
Click to expand...
Click to collapse
Interesting... Where are you trying to flash recovery.img and getting that error? What method are you using? Are you sure you have the path to recovery.img correct?
As for fastboot, you need an S-OFF/engineering spl so I guess that's out.
What happens if you use Terminal Emulator?
su
flash_image recovery sdcard/recovery.img
Does that work? Keep at it, you have root so not all is lost. Eventually you will get there.
EDIT - make sure you rename the recovery to "recovery.img" and leave it on the root of your sdcard for my italicized instructions above to work. What ROM are you running? If flash_image doesn't work I need to know which version of the binary to give you.

Phateless said:
Interesting... Where are you trying to flash recovery.img and getting that error? What method are you using? Are you sure you have the path to recovery.img correct?
As for fastboot, you need an S-OFF/engineering spl so I guess that's out.
What happens if you use Terminal Emulator?
su
flash_image recovery sdcard/recovery.img
Does that work? Keep at it, you have root so not all is lost. Eventually you will get there.
EDIT - make sure you rename the recovery to "recovery.img" and leave it on the root of your sdcard for my italicized instructions above to work. What ROM are you running? If flash_image doesn't work I need to know which version of the binary to give you.
Click to expand...
Click to collapse
Thank you very much.
Running flash_image recovery command using adb shell a few times did the trick. I was able to boot to Amon RA recovery, wipe and flash CyanogenMod 6.1.0.

truss said:
Thank you very much.
Running flash_image recovery command using adb shell a few times did the trick. I was able to boot to Amon RA recovery, wipe and flash CyanogenMod 6.1.0.
Click to expand...
Click to collapse
Nice! Glad you got it sorted out.

[GUIDE]DZ Hboot on the G2 - Also: Update Recovery, Radio, and More Via Fastboot!

*note this thread started out to post some general findings, and it has turned into a tutorial on fastboot, scroll through the first few posts to understand more if this first post seems confusing*
So in the past i decided to play with some sense ROMs that requires the Desire Z Hboot. last time i did this i flashed the Virtuous Team's PC10IMG.ZIP through Hboot to do this.
Of course I then had to reflash my radio and recovery and ROM of choice. Later I switched back to my G2 Hboot and again flashed radio, recovery and ROM of choice.
Well why do we have to do all these steps? For fun I decided to look around and see if i could just flash the SPL through fastboot and couldn't find an answer, so i asked a friend and got this response:
I'm not sure if you can flash the Hboot through fastboot, I don't know if anyone has tried it before.
I know the PC10IMG will work, so fastboot should as well, but can't guarantee it.
Though I would recommend removing that radio from the PC10IMG before flashing it, as it does throw up issues later on if you ever want to flash a stock PC10IMG.​
Click to expand...
Click to collapse
Well it works just fine, download the DZ Hboot in the PC10IMG.ZIP format from anywhere you want (its all over XDA) and then extracted all from the .zip.
boot your phone into fastboot and open CMD into the folder the Hboot was extracted to (if you haven't edited the path for fastboot make sure fastboot.exe is in the same folder as the Hboot) in CMD type
Code:
fastboot devices
as long as you see your phone listed here proceed (displayed as the serial #)
Code:
fastboot flash hboot hboot_7230_0.82.0000_100902.nb0
You're done! Well almost...
Code:
fastboot reboot-bootloader
now your phone should say
HBOOT-0.84.2000 (PC1010000)
and you notice your radio hasn't changed
now boot into recovery, you'll noticed it is also still intact, well mostly you should see something like this:
ATTN: recovery is in safe mode
this is because the following partition
is not accessible: "system"
Please enter the wipe menu and format system!
If you changed Hboot you should choose to
format all partitions (except SD card)​
Click to expand...
Click to collapse
so of course go ahead and do this
you probably wont be able to boot normally as your partitions have now changed so flash a ROM now via recovery, reboot and your golden
*Hope this helps someone... HAPPY FLASHING!
EDIT:
Well I have seen this question a lot lately (or at least similar questions) so I decided to clarify some things here and TO ADD A LINK
this will download the DZ Hboot from the cyanogen wiki (this is only the Hboot, not a shipped ROM)
You will be downloading a .zip format, so extract the image from here
the image will be named
hboot-eng.img
Click to expand...
Click to collapse
(in windows file extension may be hidden, take note that is important)
so when flashing via fastboot make sure if you use this to type
Code:
fastboot flash hboot hboot-eng.img
again you can name the image what you want so long as in your command you specify the file name
eg: i name the image dzhboot.84.img i would then enter the command
Code:
fastboot flash hboot dzhboot.84.img
also note these same steps can be used to flash the G2 Hboot found HERE:
just need to change the name of the image or what your command is
If any of the above links are down i have uploaded both Hboots to MY DROPBOX
*Know what you are doing* I have made a couple different PC10IMG.zip's to be flashed through your SPL. they contain the .19 radio, the rcdata for that, 4ext touch recovery v1.0.0.5RC6, and an engineering HBoot for either the G2 or the DZ. I do not recommend this method as manually flashing will teach you what you are doing and can help ensure there are no issues. If you are true s-off but do not have an engineering SPL then you may use one of these: POST 30 IN THIS THREAD
Click to expand...
Click to collapse
*If you have more questions feel free to ask here as i am not the best with tutorials

Good to hear that your experiment went out well without incidents.
Sent from my HTC Vision using xda premium

How Do You Use Fastboot?
I should learn to stop assuming everything... i understand that not everyone has used fastboot or adb before and therefore may not know how, but on the same note neither is rocket science and even a novice can figure this out quickly. Instead of teaching people on a case by case basis i decide to add some helpful tips here, i will attempt to be through without being too boring.
what is fastboot?
fastboot is a protocol designed to flash unsigned partitions to android phones directly into the phones flash memory. if you are familiar with adb think of it in the same way. if youre not, just understand it is a tool designed to help flash images such as recoveries, bootloaders, kernels, etc. to your android phone. for the most part you can not use fastboot unless you are rooted and have an engineering spl (hboot/bootloader) this is not a tutorial to root your phone so i will not explain this. but everything you need to know is here
how do i get fastboot?
fastboot.exe can be downloaded to your computer from googles sdk found
HERE download the proper package depending on what system you are using.
also
you will need the proper DRIVERS unless you already have them then you can skip this
ok i got it, whats next?
after you downloaded the sdk package to your pc (for the purpose of this tutorial i will assume you are running window 7 but most everything is the same in other windows os, linux, and apple) it should be downloaded to your pc to somewhere like
C:\android\android-sdk-windows\platform-tools
Click to expand...
Click to collapse
of course put it where youd like, just know where fastboot.exe lies
although not necessary, but to make it easier i really suggest doing these steps:
left click the windows (start) button > right click on computer > choose properties > go to advanced system settings > advanced tab > environmental variables > in the first box (user variables for _____) click new > name it
adb
Click to expand...
Click to collapse
> the value is the path from earlier
C:\android\android-sdk-windows\platform-tools
Click to expand...
Click to collapse
(yours may differ from this so double check it!) > in the second box (system variables) find a variable named
path
Click to expand...
Click to collapse
if one dosent exist make one > double click on it > at the very end of the variable value add the same line as before but with a ; in front of it. like this:
;C:\android\android-sdk-windows\platform-tools
Click to expand...
Click to collapse
alright click ok and you are done!
why did i just do all that?
well this allows you to open a command line from anywhere on your computer without changing directories to use fastboot. pretty much we told your pc that when you type
fastboot
Click to expand...
Click to collapse
or
adb
Click to expand...
Click to collapse
into a command lined, where to find it. as you learn how useful fastboot and adb are this will help a lot.
so i still dont know what to do or how to do it!
all right lets start simple, click the windows button and in the search field type
cmd
Click to expand...
Click to collapse
you will notice a window pop up that looks suspiciously like dos. View attachment 1386065here you will see a blinking cursor after your directory, lets try this type
Code:
fastboot
a whole bunch of probably unfamiliar stuff should now pop up (for the most part this is a list of commands that can be used in fastboot) if you get something like
fastboot is not recognized as internal or external command operable program or batch file
Click to expand...
Click to collapse
then we need to troubleshoot, but for now i will assume it worked.
now try typing
Code:
fastboot devices
and nothing will happen, why? because there isnt a device attached. make sure you have android debugging turned on in your phone, plug it into your computer and boot into fastboot mode. on the g2/desireZ hold volume down while powering on, if needed choose fastboot (not all phone do this the same way so if you dont know how, ask and i can help) again try typing
Code:
fastboot devices
this time you should have a list of attached devices, this is displayed as the serial number to each. being many commands will "do" things to your phone try typing
Code:
fastboot reboot
if your phone is now back and running your existing os, congratulations! you now at least have fastboot set up and working properly. now lets try a few things out and see why this can be so helpful!

do you want a new recovery? maybe 4ext?
being this is in the vision (g2/dz) forum many have clockwork recovery but have read about 4ext recovery, only they just arent sure how to get it on their mobile.
here is a quick tutorial on how to do just this, and in my opinion the easiest and the safest way.
First
download a version of 4ext recovery for the vision HERE this will be downloaded to your computer in a .zip, i suggest to put it in a folder named 4ext recovery inside whatever folder you have all your android downloads (roms, kernels, etc)
now extract the image from the .zip you will notice it has the image and the md5sum, make sure it is
d92610abb990a78c3721d9e47e60fc13
Click to expand...
Click to collapse
if not DO NOT FLASH IT, unlike flashing a bad rom, it can be very harmful to flash bad firmware to your phone, although unlikely if flashed through fastboot, it could leave you without a working recovery or even worse, hard brick your phone. im not giving the scary warning that you see in most roms as what i am telling you is safe, im just reminding you to understand what you are doing.
i get it, im ready for 4ext!
all right, lets start by finding the folder the extracted recovery is in. hold shift > right click in that folder > choose open command window here. now you will see your command line with the directory already set to this folder. at this point, if you havent already, boot your phone into fastboot mode and have it plugged in via usb. now type
Code:
fastboot devices
so long as you see your serial # go on (if you dont fix the path in environmental variables explained in the last post or just make sure fastboot.exe is in the same folder as the recovery.img)
now lets continue, type
Code:
fastboot erase recovery
it is best to start fresh so even though you can skip this command i recommend it. lets move on:
Code:
fastboot flash recovery recovery.img
the recovery image you extracted from the .zip should have been named recovery the above command should be altered if you changed the name (notice: if using windows it may appear the image is only named recovery, that would be because windows is hiding the file extension, the true file name would then be recovery.img)
all right, if it said complete your done! seriously its that easy! now type
Code:
fastboot reboot-bootloader
from here you can boot into your new recovery and play around. if coming from clockwork to 4ext on the vision for the first time you will be wowed! this has so many more features, is far more stable, and is truly worth donating to madmaxx82 for all his hard work.
if you like this recovery and want the latest and or to donate (buying the app for 2bucks in the market is a very reasonable donation and gives you a great app too!) go HERE and you will also find tips on how to use the recovery as well as links to flash a free version of his .apk or a link to download the paid. even if you cant right now, i highly suggest doing so in the future as developers may give their hard work to us for free on xda but we should understand that just because something is free doesnt mean we shouldnt pay for it.
of course this method can be used for flashing different recoveries on different phones as well. just understand what you are doing and be sure to flash the proper recovery to the proper phone.
happy flashing!

So you need to flash a new radio...
turns out this doesnt even occur to many people as an option, that is to flash a different radio to their mobile. true, when i got my g1 this was the first time i realized this was an option, prior to that i had only dumbphones and did not even know too much how cellular phones in general worked. so to clarify i am not speaking about the fm radio in your car rather flashing the proper firmware to control your cellular radio.
Everyone keeps saying the .19 radio is the best, is that true?
well yes and no, what is true for them may not be true for you. it does appear most people using a g2 or a dz in this forum find the 12.62.60.27_26.13.04.19 radio the best in terms of reception and battery life. but it is good to know that this still has to be determined on a case by case basis. what is amazing for some may be lackluster for others.
so if you feel you need to try a new one the .19 is a good place to start, but you may need to test others and usually you will need to test it for a day or so to know how good it is in comparison. usually it is better not to estimate but rather compare using apps such as Speed Test and Network Signal Info and Battery Monitor etc. just use what works for you
So i can flash a new radio via fastboot?
Yes, and its my preferred method of doing so. its fast, easy and safe. heres how:
download the .19 radio and store it on your computer in a place you can find easy.
*checking the md5sum is a good idea before flashing a rom, and a must when flashing firmware:
6CB937DD21DC2A42DEBB66190F38370F
Click to expand...
Click to collapse
turn on debugging on your phone, put in fastboot mode and plugged into computer via usb. now open cmd in the same folder as fastboot.exe
now in cmd type:
Code:
fastboot flash radio radio.img
if you downloaded multiple radios then i suggest renaming them, in this case you may need to change radio.img to something like radio19.img or whatever you named it
now again in cmd type:
Code:
fastboot reboot-bootloader
you are now in hboot and can verify it worked, congratulations! it was that easy!
for a whole list of radios for the vision go HERE there will be two forms of each radio to download, make sure you download the images only if you want to flash through fastboot. you will also find more info about the radios there.
if you are interested in more then take look HERE FOR ICS and HERE FOR GINGERBREAD edkeys has done great work and its worth at least reading up on it. again if it aint broke dont fix it, but i will say it worked well for me.
*any questions and comments are appreciated, sometimes i go into too much detail and sometimes too little so feel free to ask and/or comment

Just a thing you might want to consider adding, I generally always 'fastboot erase recovery' before flashing a new recovery. I don't think it makes much difference, but it can't hurt.
-Nipqer

cleanleness is next to...
thanks, i do as well and just overlooked/skipped it in the tutorial
although im sure it wouldnt make much of a difference if someone just flashed a new recovery over the old, but it is always best to erase as this will lessen the chance of a bad flash due to residual effects from the previous recovery. this goes with most everything in flash memory as so many peoples problems with a newly flashed rom are simply due to them not completely wiping the phone clean.
so when flashing a rom i am a firm believer in performing
Code:
fastboot -w
prior to the flash, as it is cleaner than wiping from recovery and even cleaner than most superwipe scripts. of course not every time i flash a rom or restore a backup im next to a computer. in this situation i do recommend to wipe from recovery and then flash SuperWipeG2+ext4 from recovery prior to flashing the rom or restoring a backup. of course most of the time when people flash new roms they are at a computer, in this case i recommend these quick steps prior to the flash:
put phone in fastboot mode and attach to computer
Code:
fastboot devices
just to make sure we are ready (looking for serial # here)
Code:
fastboot erase system -w
fastboot erase boot
so fresh and so clean
Code:
fastboot reboot-bootloader
from here just reboot to recovery and flash the new rom there.
*note - you can flash a rom to your phone through fastboot but i will put that in the next tutorial*

flashing a rom with fastboot
As promised... here you go!
now of course you can flash a rom through recovery, but why not have another way? maybe your recovery partition on your phone is corrupt? maybe you just want to say "i learned something new!" whatever your reason here are the simple steps:
To start:
we need to download the rom of choice to your computer. once complete find the folder that rom is in and open cmd to that directory (quickest way just hold shift and right click within that folder > open command window here) of course make sure your phone is plugged into computer and in fastboot mode.
Lets see how quick and easy this really is...
in the command line type:
Code:
fastboot devices
see your serial number and we know all is good
now lets type these commands:
Code:
fastboot erase system -w
fastboot erase boot
fastboot update superawesomerom.zip
of course replace <superawesomerom.zip> with the correct file name
and last but not least:
Code:
fastboot reboot
*its been a little while since i did this but the phone might automatically reboot after flash so no need to run the reboot command
as your phone boots into the new rom, pat yourself on the back...

can i restore a nandroid through fastboot?
of course! (why you would need to is irrelevant)
and here are the simple steps how:
well first you need to make a nandroid back up (unfortunately fastboot cant make a nandroid for you :crying: ) put it some where on your computer. personally i only keep maybe 3 or so nandroids on my phones sd card as why waste space. i do however keep almost all my nandroids on my computer separated into diffrent folders for different phones. so my path to a nandroid backup would be something like:
android/htcg2/nandroids/<nameofnandroid>
Click to expand...
Click to collapse
and the obvious stuff:
have phone plugged into pc via usb and in fastboot mode, open cmd and change directories to that folder where your nandroid is in (or again just hold shift and right click > open command window here)
once we are in:
in cmd type:
Code:
fastboot devices
all is good when serial number is displayed, now type:
Code:
fastboot erase system -w
fastboot erase boot
*this isnt 100% neccessary but im a firm believer in wiping before any flash, even a backup
Code:
fastboot flash userdata data.img
fastboot flash system system.img
fastboot flash boot boot.img
fastboot reboot
(of course change the image names if needed)
and you did it! :good: now you are almost a pro at using fastboot!
keep playing around, you'll get the hang of it and will quickly see that this is one of the best tools in the android sdk. it makes things much faster and easier and in many cases safer than the alternatives. any questions... feel free to ask!
Happy Flashing!
*as nipqer was so kind to point out, most newer recoveries archive nandroid backups in tar format by defult. this will not work with fastboot unfortunately.

for the restoring a nandroid, you gotta make sure the backups are done in yaffs2 format don't you? fastboot doesn't work with tar's as far as I know.
Clockworkmod 3.x and lower have the yaffs2 as default, but at least 5.x (and 4ext) use tar as default, but I know 4ext has a setting so you can change it.
-Nipqer

I believe you are correct. I haven't restored a nandroid via fastboot since the g1 days but that sounds about right. looking at my g2 nandroids some are in yaffs2 and some not, ill look into it and post a better explanation.
and it looks like every nandroid i made since i flashed 4ext recovery is saving everything as tars (except the boot and recover image) when i first rooted and used clockwork 3.x ? those backups were in yaffs2. it looks like one could change the settings in the 4ext app to change from tar archives to yaffs, but if all you are doing this for is to boot a backup from fastboot that is silly :silly:
so although it still is possible, it would not be worth the effort unless you were to do it for sheer fun. or if you still have an old android device lying around and want to try it out.
also if you updated to a new recovery and your old one used yaffs2 and the new one works with tar (i think twrp uses a modified tar/ext4 image called .win?) well you cant flash those old backups in your new recovery, but you can still flash them from fastboot. and then later do a nandroid with your new recovery in the proper format. so with this i guess there still may be a reason for someone to flash a nandroid via fastboot.
thanks for the heads up nipqer! id hate to make someone think they did something wrong when they didnt!
Sent from my HTC Vision using xda premium

Some other uses...
What else can i do with fastboot?
ADB has more (but different) capabilities than fastboot, but fastboot can still be handy. Heres an example: you went through the rooting process on your Vision a while back and cant recall if you sim unlocked it or if you gained super CID. well simple, lets:
open cmd, navagate to fastboot (no other folder/files necessary here) and type:
Code:
fastboot devices
and you should see your serial number, good
Code:
fastboot getvar cid
if you are sim unlocked and (superCID) then the output should read
cid: 11111111
Click to expand...
Click to collapse
if not, and you want it, then you will have to downgrade and rerun gfree etc. or you could beg tmobile for an unlock code or you can buy one from elsewhere. any way you go about it, this will tell you if it worked.
*super CID and sim unlock are not the same thing, i am just assuming if you have super CID then you also sim unlocked. (super CID lets you flash different software and firmware to your phone that initially may be locked to a specific carrier, sim unlocked allows you to use any GSM sim card no matter the carrier. although some require specific radio bands to fully work)
And more hypotheticals?
well to get your model id you would do the same only change the command to
Code:
fastboot getvar mid
out put will be something in the lines of
mid: PC1010000
Click to expand...
Click to collapse
there are reasons to change/fake your model id, maybe for apps in the market or to tweak a kernel... im not a developer so the purposes may be many or few on this.
Get a bunch of info quick:
Code:
fastboot getvar all
this give a slue of info such as radio, bootloader, imei, cid, secure flag (on/off) and more!
Speaking of kernels...
lets say you are a developer and have worked on a new kernel for your device, a quick and easy way to test it out may be to fastboot load the kernel:
Code:
fastboot erase boot
fastboot boot kernel ramdisk
*as always replace file/image names accordingly
after testing is completed:
Code:
fastboot flash:raw boot kernel ramdisk
fastboot reboot
test it out and see how things go! good luck!
as always, if you have questions or comments feel free to leave them here!
Happy Flashing!
*im thinking about adding a simple tutorial about ADB if anyone is interested let me know

If you flash from the g2 to the dz hboot thingie and have to reformat /system does it mean time to flash a new rom? And can you reflash a ext backup back since the partition info is different?

Yeah after updating to the dzhboot you will need to reformat, this will wipe your current Rom. But most often you should have no issue taking your nanadroid made while on the g2 hboot and restoring them to you phone with the new system partitions you get with the dzhboot.
As always make a backup of current set up via recovery, follow the steps listed in the first post and then flash either a new Rom or your nandroid. Also make sure to check the md5sums.
If you need any further help feel free to ask
Happy flashing!
Sent from my Desire Z using xda premium

Umm wow that was like super easy. Thanks for the guide. Going to have to read some about the radios and see about doing that next.....

no problem, many seem to either be afraid of using adb or fastboot mostly because they dont understand it and see other options to do the things they want (recovery)
but in reality both are quite easy to get used to and it really helps with the understanding of what you are doing. so im glad this guide is helping people not just get their phone the way they like it but also help understand the process.
as for the radio its just as simple as flashing the bootloader. mind you any time you flash firmware to your phone there is potential harm (unlike with flashing roms) so its not a great idea to just flash away for no reason. but fastboot is a very safe way of flashing firmware and as long as you check md5sums your good. also make sure never to do a battery pull during a flash or if something goes wrong just dont reboot until it is fixed, knowing these few things will ensure safe flashing through fastboot and help understand why firmware shouldnt be flashed through recovery.
so if you feel you could get better reception and/or battery life with a new radio by all means go for it! i for one found the .19 radio to be the best for me along with edkeys package. it seems many feel the same but the only way to know what works for you is to try it!
Happy Flashing!

I do agree it's not that hard once you have a clue. One thing I would say you may want to be a bit clearer on (at least me and my braindead self took a while to grasp it) is that you need to be in the bootloader to use the fastboot command. I am still learning about stuff and with the crazy hours I work and with 3 kids sometimes it takes me a while to get stuff done because I want to understand it before I do it. Although with your guide once I had time to sit down and do it it was like 15 mins tops and all was done. I need to read about the radio and edkeys(whatever that is...) and see about doing it. I think I have the .15 radio and it works ok although if I understand correctly wifi calling only works with the .19 radio and who knows it may fix my mms issues when I try ics roms.....

Thanks for the suggestion, ill add that in there, I always miss some little things! Edkeys is a member here on xda who did a lot of research on radios and WiFi calling, I linked a couple of his pages in my post on flashing the radio, I definitely suggest reading up on his work as he will explain it better than I. Also note some users have issue using WiFi calling and an old sim card, if you go to a local T-Mobile outlet they'll give you a free updated sim. I think the latest is 9177? Not sure but its written on the card.
Thanks for the suggestion!
Sent from my Desire Z using xda premium

demkantor said:
Thanks for the suggestion, ill add that in there, I always miss some little things! Edkeys is a member here on xda who did a lot of research on radios and WiFi calling, I linked a couple of his pages in my post on flashing the radio, I definitely suggest reading up on his work as he will explain it better than I. Also note some users have issue using WiFi calling and an old sim card, if you go to a local T-Mobile outlet they'll give you a free updated sim. I think the latest is 9177? Not sure but its written on the card.
Thanks for the suggestion!
Sent from my Desire Z using xda premium
Click to expand...
Click to collapse
C:\Users\Pesho\Desktop\recovery>fastboot devices
SH**SRT***** fastboot
C:\Users\Pesho\Desktop\recovery>fastboot erase recovery
erasing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 0.001s
C:\Users\Pesho\Desktop\recovery>fastboot reboot
rebooting...
finished. total time: 0.280s
C:\Users\Pesho\Desktop\recovery>
Click to expand...
Click to collapse
USB debugging is on.
I'm running Mimicry 1.5
root access is setted to apps and adb in the developer options in settings

what is your current bootloader information? can you write down the first few lines on the top of the screen?
Sent from my HTC Vision using xda premium

[Q] Bootloop on rebooting into recovery?

I rooted through cyanogenmod method, then unrooted (went back to stock 2.2.1) with the stock P15100.zip. I had another hardware issue with my phone (microphone failing) and thought it could be software. The mic was still broken and I wanted to root again so went through cyanogen method again flashing CWM. I was able to reboot once into recovery to flash synth's ICS. When I try to fully reboot, then reboot into recovery again, I got bootloop for a minute, then eventually booted into the rom. I tried flashing 4ext and same issue. I tried flashing CWM again from app and still have the issue. I'm just guessing recovery is corrupted and it needs to be formatted and re-flashed? Anyone know how to format recovery via adb and then push cwm or 4ext?
Any help much is appreciated.

You can flash a recovery through terminal emulator. As I recall, the commands are:
su
flash_image recovery recoveryname.img
Sounds like you might be having bigger issues, though. I hope your recovery partition isn't going kaput.
Jack_R1 might have an idea.

Man, Jack_R1 is still around these parts? But as for OP, definitely sounds like your recovery is corrupt. What you want to do is if you have any fastboot/ADB knowledge is you're going to want to download the recovery.img of your choice, name it "recovery.img" then place it in your ADB folder, plug your phone in in Fastboot mode and then type in the following commands:
Code:
Fastboot devices
it should show you a number followed by "fastboot" after this type
Code:
fastboot delete recovery
it should spew out how long it took followed by "recovery deleted" or something like that.
lastly you're going to flash the recovery that you downloaded. Type
Code:
fastboot flash recovery recovery.img
That should do it! PM me if you need any other help

Yes, I still visit here
OP, what phone do you have? You're writing a wrong name for PD15IMG.
In any case, if you indeed have PD15IMG - find "root for S-OFF users" thread in Development, get the PD15IMG with CWM from there, flash it just like you flashed return-to-stock package, and boot into recovery. If it doesn't work - it means that it's not the recovery that's corrupted.
And I suspect that you're just not understanding correctly what your phone does, and/or not actually booting into recovery.

Nicgraner said:
Man, Jack_R1 is still around these parts? But as for OP, definitely sounds like your recovery is corrupt. What you want to do is if you have any fastboot/ADB knowledge is you're going to want to download the recovery.img of your choice, name it "recovery.img" then place it in your ADB folder, plug your phone in in Fastboot mode and then type in the following commands:
Code:
Fastboot devices
it should show you a number followed by "fastboot" after this type
Code:
fastboot delete recovery
it should spew out how long it took followed by "recovery deleted" or something like that.
lastly you're going to flash the recovery that you downloaded. Type
Code:
fastboot flash recovery recovery.img
That should do it! PM me if you need any other help
Click to expand...
Click to collapse
I have used adb a bit (for root with cyanogen method). I'm guessing that the delete command will reformat the recovery partition? I'll give this a go when I get home and get back to ya. Thanks for the reply! Is there a way to download the 4ext recovery img file?
Edit:
I downloaded the CWM touch img and connected to the phone in fastboot. Was able to follow your instructions, but the command is erase not delete. When I put in the delete command it came up with the instructions and was able to figure it out. Flashed recovery and I can now boot into recovery every time from fastboot, terminal, adb, and from power prompt in rom! BOOYAH! Thanks a ton!

Jack_R1 said:
Yes, I still visit here
OP, what phone do you have? You're writing a wrong name for PD15IMG.
In any case, if you indeed have PD15IMG - find "root for S-OFF users" thread in Development, get the PD15IMG with CWM from there, flash it just like you flashed return-to-stock package, and boot into recovery. If it doesn't work - it means that it's not the recovery that's corrupted.
And I suspect that you're just not understanding correctly what your phone does, and/or not actually booting into recovery.
Click to expand...
Click to collapse
Hey Jack,
I have HTC Glacier. Was a typo for the PD15IMG name. I think I have a decent understanding of the phone, and most likely have a corrupted recovery partition. Seems that instead of just flashing a recovery over a recovery, I may need to reformat the partition and then flash? I'll try flashing the file you suggest and report back. If it is not the recovery that is corrupted, what else could be the issue? Possibly an issue with the bootloader not allowing the phone to boot into recovery? Thanks for the reply.

Flashing recovery isn't copying a file. When you flash IMG through bootloader, it is flashed just like what it is - a complete image. Formatting the partition doesn't do anything, since it has no "format" - the image flashed by the bootloader contains both the structure and the data, just like a CD/DVD image does, for example.
The possible options I can think of are:
1) Your recovery partition is physically bad - unlikely.
2) Your bootloader is corrupted - could possibly lead to you being unable to enter recovery.
3) Something that prevents your phone from entering recovery - i.e. a stuck button or something - or you're doing it wrong. I'm afraid that what you're describing as "phone bootloops for a minute and then boots a ROM" isn't really a bootloop - because these phones can't get out of bootloop on their own, if booting failed once - it'll fail always. Logcat can confirm this. I believe it's just the ROM that's booting normally when you try to enter recovery, so, in this case, since you didn't specify how exactly you're trying to enter recovery - it seems like you're either doing it wrong, or when you try to enter recovery you're not getting there.
To help people help you, please write down the exact way you're using when trying to enter recovery, and if you know more than one way - try them all (from bootloader, by adb reboot recovery, directly booting without flashing by "fastboot boot", etc). And post your HBOOT version.

Jack_R1 said:
Flashing recovery isn't copying a file. When you flash IMG through bootloader, it is flashed just like what it is - a complete image. Formatting the partition doesn't do anything, since it has no "format" - the image flashed by the bootloader contains both the structure and the data, just like a CD/DVD image does, for example.
The possible options I can think of are:
1) Your recovery partition is physically bad - unlikely.
2) Your bootloader is corrupted - could possibly lead to you being unable to enter recovery.
3) Something that prevents your phone from entering recovery - i.e. a stuck button or something - or you're doing it wrong. I'm afraid that what you're describing as "phone bootloops for a minute and then boots a ROM" isn't really a bootloop - because these phones can't get out of bootloop on their own, if booting failed once - it'll fail always. Logcat can confirm this. I believe it's just the ROM that's booting normally when you try to enter recovery, so, in this case, since you didn't specify how exactly you're trying to enter recovery - it seems like you're either doing it wrong, or when you try to enter recovery you're not getting there.
To help people help you, please write down the exact way you're using when trying to enter recovery, and if you know more than one way - try them all (from bootloader, by adb reboot recovery, directly booting without flashing by "fastboot boot", etc). And post your HBOOT version.
Click to expand...
Click to collapse
Sorry if I wasn't more descriptive. I really appreciate your help and everything you have done for this community. Seems the recovery was corrupted by the 4ext app. I was able to extract the recovery.img from the 4ext download and was able to flash it via fastboot. Everything boots properly now. HBoot is 0.85.2007 FYI. Thanks again!

Going back to Sense from [RUU] Google Edition Conversion.Graffixync UPDATE 12th May

EDIT - UPDATED INSTRUCTIONS 12th May 2014
Due to the partition sizes being different in the GPE RUU it is not simply a case of flashing a sense rom in recovery. You will experience problems if you do this. This might involve getting the storage encrption message, bootloops, freezing etc etc.
This thread is specifically for users who have problems getting back to sense. Solution is below. If you have alternative solutions that have worked without issues please post.
I have tried to make them as simple as possible. This guide assumes you are S-Off otherwise how did you get here. (
This does not apply if you have installed a GPE ROM. You can flash as normal through recovery. (using instructions of new rom)
Thanks to @exad for his continuing support/assistance throughout the thread, as well as @graffixnyc for the GPE RUU and both he and @navalynt for finding the initial fixes.
It will be much easier if you have your new Rom on your external sdcard prior to starting this. It will also stop a number of problems if you have SuperCID (11111111) If you don't know how to - FASTBOOT Commands
1. Enter the command "fastboot oem readcid". Make and KEEP a note of your original CID.
2. Enter the command "fastboot oem writecid 11111111"
3. Enter the command "fastboot read cid" [it should confirm your CID is 11111111]
4. Press the volume down button twice on your phone and navigate to reboot bootloader, then hit power button to reboot the bootloader.
5. Bootloader will also say "CID-11111111" now to confirm (Thanks to @xl VipeR lx ) Also to @umjammerlammy for the GENTLE reminders to include this
Make sure the firmware file and twrp recovery are in your Android directory on your PC - Mine is
C:\Users\Grentuu\AppData\Local\Android\android-sdk\platform-tools\
During this process you may find that when you reboot the phone starts to boot into android. Mine did but simply had the GPE animated logo but never entered GPE. All you do is press Vol up and power for about 10 seconds to reset. As soon as it resets press vol down and power to get back to bootloader.
Flash 1.54.401.5 firmware from Here
Fastboot Method
Boot device into FASTBOOT mode either by adb reboot bootloader or Vol down & Power (device should show FASTBOOT USB)
Make sure the firmware file to be flashed is in your android folder
Open a command prompt from the folder where fastboot resides. (Hold shift key/right click in the dir to get menu - left click on Open Command Prompt here.)
Run the following commands:
fastboot oem rebootRUU (this will reboot the device into RUU mode in preparation for zip flashing)
fastboot flash zip 1.54.401.5-W_Splash.zip (the name of the zip should EXACTLY match the name of the file you're flashing)
It will fail the first time. Run the same command AGAIN until you see it has flashed successfully.
I repeat - Run the same command TWICE until you see it has flashed successfully.
Once complete, type fastboot reboot-bootloader The hyphen is required.
Some users have stated this firmware (1.54.401.5) did not work for them as they weren't GSM and reboots just threw them back to recovery. If this happens try a stock (your original e.g. T-mobile) firmware then follow the rest of the process.
Boot into stock recovery
Factory reset
Reboot into bootloader
Flash TWRP - command = fastboot flash recovery openrecovery-twrp-2.7.0.2-m8.img (The must match exactly the name of the recovery you are flashing and remember the recovery file must be in your android folder)
Boot into TWRP
Go into Wipe menu
do a full factory reset wipe
Reboot back into recovery
Install rom
Profit
These have worked for me everytime (Change count =19)

Thanks for this. I'm about to give it a shot now.
Sent from my HTC One_M8 using XDA Premium 4 mobile app
---------- Post added at 05:08 PM ---------- Previous post was at 04:40 PM ----------
For some reason the firmware wont flash in twrp. Should I sideload the firmware?
Sent from my GT-P5210 using XDA Premium 4 mobile app

To flash a firmware you must be in bootloader/fastboot mode.
Fastboot oem rebootRUU
Fastboot flash zip firmwarefilename.zip
Then again
Fastboot flash zip firmwarefilename.zip
Fastboot reboot-bootloader

exad said:
To flash a firmware you must be in bootloader/fastboot mode.
Fastboot oem rebootRUU
Fastboot flash zip firnwarefilename.zip
Then again
Fastboot flash zip firnwarefilename.zip
Fastboot reboot-bootloader
Click to expand...
Click to collapse
Thanks. Understood, I was just reviewing my steps for the conversion. I really just want to try out that new Sense rom and then I'll probably revert back. BRB...I'll let you know how it goes.

Bear in mind you must have S-off to flash a firmware that way.

exad said:
To flash a firmware you must be in bootloader/fastboot mode.
Fastboot oem rebootRUU
Fastboot flash zip firmwarefilename.zip
Then again
Fastboot flash zip firmwarefilename.zip
Fastboot reboot-bootloader
Click to expand...
Click to collapse
Those are the instructions in post 1 the original thread.
The issue is with people wanting to go back to sense

This thread is about returning to sense. Flashing a firmware is always the same. It's the firmware itself that's different...

Here is where I am at..
I converted to GP easily and it worked well.. I wanted to convert back so I installed twrp first, then through twrp installed the 1.54.401.5 firmware.
Installing that firmware removed twrp and the rom. So I am without an OS at all, and have stock recovery.
Is there anyway I can flash a custom recovery or a rom via the stock firmware/recovery?
My computer will not recognize adb devices. But it used to obviously.
I have an SD card.
Any help and I will be sooo grateful. (maybe even donate)
Thanks!

You can't flash a firmware through recovery... You can flash a stock recovery after the steps listed above if you like. See the stock backup thread.
You can flash any recovery through fastboot... Adb only works with the rom booted or with custom recovery booted.

Thanks will try it out.

exad said:
You can't flash a firmware through recovery... You can flash a stock recovery after the steps listed above if you like. See the stock backup thread.
You can flash any recovery through fastboot... Adb only works with the rom booted or with custom recovery booted.
Click to expand...
Click to collapse
So what do I do in this situation with no rom installed only 1.54 firmware and stock recovery.

Flash twrp

exad said:
Flash twrp
Click to expand...
Click to collapse
I have no rom installed, so it wont show in adb devices.

PunchLick said:
I have no rom installed, so it wont show in adb devices.
Click to expand...
Click to collapse
You flash recovery via fastboot, no need for a rom.
Just make sure you have the proper fastboot drivers from htc.

Dmaxon said:
You flash recovery via fastboot, no need for a rom.
Just make sure you have the proper fastboot drivers from htc.
Click to expand...
Click to collapse
ADB devices shows no devices. If i had custom recovery this would be so much easier, but im using 1.54.401.5 firmware with stock recovery and no ROM.
Just dont know what to do to get a working device again. All i can do is boot into stock recovery, hboot and fastboot.. but computer shows no device.

PunchLick said:
ADB devices shows no devices. If i had custom recovery this would be so much easier, but im using 1.54.401.5 firmware with stock recovery and no ROM.
Just dont know what to do to get a working device again. All i can do is boot into stock recovery, hboot and fastboot.. but computer shows no device.
Click to expand...
Click to collapse
I would recommend the All-In-One Toolkit. This will allow you to fastboot the recovery, even though the pc doesn't recognize it. This has worked for me in the past.
Meanwhile, I get the following error message when attempting to flash the 1.54...
Any suggestions guys???
Problem solved. I had not supercid. After I did that, I was able to successfully flash 1.54...

Why post steps if your not willing to help?
The steps in the OP can still cause issues for some people.
Sent from my HTC One_M8 using Tapatalk

Ideas4ya said:
I would recommend the All-In-One Toolkit. This will allow you to fastboot the recovery, even though the pc doesn't recognize it. This has worked for me in the past.
Meanwhile, I get the following error message when attempting to flash the 1.54...
Any suggestions guys???
Problem solved. I had not supercid. After I did that, I was able to successfully flash 1.54...
Click to expand...
Click to collapse
Can you elaborate a little on which options etc, because that sounds fantastic and would help me so much!

PunchLick said:
Can you elaborate a little on which options etc, because that sounds fantastic and would help me so much!
Click to expand...
Click to collapse
When you open the all in one...the 3rd option on the top right is what you need. Follow the step, even if fastboot says device is not connected, this will still send the recovery to your device as long as you're in the bootloader.

I will never understand why people play with there phones and have no understanding of adb and fastboot commands with the bootloader. if people would learn that first there wouldn't be so many threads when they get stuck. tool kits are bad it makes people lazy. but I appreciate the devs who make them