Database Users

[Q] Problems flashing recovery

I've achieved permroot via the tutorial and am using a mac, but so far have not been able to flash a recovery to be able to do ROMs. Whenever I do the fastboot command
./fastboot flash recovery recovery.img
< waiting for device >
I get that, and it does nothing. Any ideas what's going wrong?

Have you set your phone to Fastboot mode? You have to select fastboot from the bootloader, just a guess

Did you place the recovery image in the sdk tools folder?
powered by the tears of a million orphaned alpacas...

Yep it's in the proper folder. Putting the phone in fastboot mode? I haven't heard of that. It is plugged in with USB debug on. I leave it on the main screen.

If you're following bcnice's instructions and you hopefully have the fastboot.exe in a folder you put into your Windows path (AdroidSDK\platform-tools)
You just cd to the directory where the recovery.img is (on the PC) power your phone off, turn on while holding volume down (bootloader) select fastboot (I believe is says something like fastboot-usb when it's ready, then just type in the command:
fastboot flash recovery recovery.img
you will see the transfer happen then you boot into recovery (on the phone) and if you got it right it will now be a black background with green font
go to backup/recovery, select recovery, there's your Nandroid!
I just did this today so I feel your pain but I've already flashed a new ROM and the OC'd kernel so I'm sure you can get the hang of it. Fun fun fun.
Edit: Sorry, didn't see you were using a mac... I have no experience with those. It may be in your best interest to have the recovery.img in the same folder your fastboot.exe is

You know you don't have to fastboot to do recovery..you can just push the files
Sent from my PG06100 using XDA App

Or...
1) Download the recovery you want (either CW 2.5 or CW 3.0).
2) Download Rom Manager from the Market.
3) Flash Clockwork Recovery from the Rom Manager main menu. (Make sure you select HTC EVO CDMA).
4) Open File Explorer, go to ClockworkMod/download/mirror1.kanged.net/recoveries and rename the recovery file to "recovery-clockwork-3.0.0.5-supersonic1.img.
5) Move the recovery file that YOU want into this folder, and rename it to "recovery-clockwork-3.0.0.5-supersonic.img.
6) Open Rom Manager and Flash Alternate Recovery.
7) Flash ClockworkMod Recovery (select HTC EVO CDMA again), and it will flash the correct recovery image compatible w/ our EVO Shift.
This set up works w/ any of our recoveries out now or going forward. Simply rename the file each time. Hopefully ClockworkMod will add our recovery to the base soon and we won't have to go through this step, but for now, this is an alternate way to flash recovery for those of you not wishing to use Fastboot, and want to do things directly from your phone.

[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

Installed cutom rom now stuck on google screen :(

Ive checked other nexus 7 threads... but this isn't the case.
My nexus 7 is stuck on the google Boot I cannot rub Fastboot or recovery from the toolkit .. nothing at all. It cant find the device .
When I plug in the usb it still makes the sound on windows and so on.
It happened when I was prepairing to install a Custom ROM using JROMFlasher..
I followed all the steps, and when it came to install the ROM to the SD card it just rebooted (transferred to quickly I thought)
And then Ever since it has Just been stuck on the google screen.
I am quite pissed :L
Any Ideas?

I would be quite pissed at your self for using a toolkit. this is a Nexus device and is easily unlocked manually with the proper tools that google provides themselves. Boot into fastboot mode (Hold Power and the two volume keys). Once in fastboot mode you can flash a recovery and then once in recovery you can adb push a ROM to the tablet and flash the ROM the correct way. You really should read up on how to do thing manually instead of resorting to the quick and easy method.
Download the zip located here : platform-tools.zip Extract the contents to a folder name the folder Nexus7 or whatever you want.
Once thats done go ahead and open a command prompt window in that folder you can do that by Shift+Right clicking inside the folder and selecting "Open Command Prompt Here" or if on XP then open CMD and
Code:
cd C:\Users\Name-of-User\Desktop\Nexus7
Once in the CMD issue the command
Code:
fastboot devices
To see if the computer recognizes the device in fastboot mode. It should spit out a gibberish looking code with ....... Device at the end.
Then you going to flash the recovery to do that you issue this command
Code:
fastboot flash recovery name-of-recovery.img
inside the zip the openrecovery-twrp-2.3.1.0.img that is what you will put in place of "name-of-recovery.img" it will show on the screen writing recovery when its done hit the volume up button until the "START" Turn to "Recovery Mode." Then hit the power button you will boot into recovery mode. Once in recovery mode place the ROM.zip you want to flash in the same folder as the stuff you extracted to.
Then issue this command
Code:
adb push Name-of-ROM.zip /data/media
Of course you will replace name-of-ROM.zip with the actual name of the ROM you are flashing. Make sure you also have a gapps packaged which can be found on goo.im/gapps/ latest package is gapps-jb-20121011-signed.zip you will want to adb push that as well.
IF all is done correctly you should be able to install that ROM please follow this procedure.
1. Go to Wipe
2. Factory Reset (this will delete all your apps and apps data not the sd card)
3.Wipe Cache Partition
4. Wipe Dalvik Cache
5. Format System
6. Go to install and find the two ROM.zip and Gapps package at the bottom of the root of the sd card (/sdcard0)
7. Select to flash the ROM and then the Gapps
8. Reboot
Click to expand...
Click to collapse
You should be good to go now.

ÜBER™ said:
I would be quite pissed at your self for using a toolkit. this is a Nexus device and is easily unlocked manually with the proper tools that google provides themselves. Boot into fastboot mode (Hold Power and the two volume keys). Once in fastboot mode you can flash a recovery and then once in recovery you can adb push a ROM to the tablet and flash the ROM the correct way. You really should read up on how to do thing manually instead of resorting to the quick and easy method.
Click to expand...
Click to collapse
Your a good man Yeah I'm not claiming to know anything about Android at all I have literally just started looking into how the system works.. But I have learnt from my quick attempt at everything mistake now.. Once again thanks.

QuantumCipher said:
Your a good man Yeah I'm not claiming to know anything about Android at all I have literally just started looking into how the system works.. But I have learnt from my quick attempt at everything mistake now.. Once again thanks.
Click to expand...
Click to collapse
Its all good wrote you up a quick guide follow that and it'll get you back on track .

ÜBER™ said:
Its all good wrote you up a quick guide follow that and it'll get you back on track .
Click to expand...
Click to collapse
It's flashing the Stock now Thanks for your time. And for also sending me in the right direction (Y)

QuantumCipher said:
It's flashing the Stock now Thanks for your time. And for also sending me in the right direction (Y)
Click to expand...
Click to collapse
Not really necessary but alright. remember going back to stock deletes the entire tablet memory So make sure to back up your important data.

ÜBER™ said:
Not really necessary but alright. remember going back to stock deletes the entire tablet memory So make sure to back up your important data.
Click to expand...
Click to collapse
It was formatted anyway there was no Important data .. Actually you maybe able to answer something for me.
When I rooted my Nexus before all this.. It was rooted as I done previous tests.
What do you use to move files to and from the tablet such as root files? As I want to modify the "X" boot logo animation. I noticed it is just a bunch of PNG images that need replacing..

QuantumCipher said:
It was formatted anyway there was no Important data .. Actually you maybe able to answer something for me.
When I rooted my Nexus before all this.. It was rooted as I done previous tests.
What do you use to move files to and from the tablet such as root files? As I want to modify the "X" boot logo animation. I noticed it is just a bunch of PNG images that need replacing..
Click to expand...
Click to collapse
Acutally its a zip of multiple components not just png's. The bootaniamtion.zip as a whole is what makes up that boot up animation. If you want to change the bootanimation you would replace that entire zip with one that you want. And then set the permissions and reboot. Some will even have a flashable. In order to modify system files you need root and a root explorer. There are multiple on the play store i would recommend Root Explorer if you have the money otherwise ES File Manager or Solid Explorer.

Bricked after wiping with twc
When I look for fastboot devices, nothing happens...
where do I go from here?

http://forum.xda-developers.com/showthread.php?p=35777264
Sent from my Nexus 7 using xda premium

[Tutorial] Root, Unlock, Recovery and flashing a Custom ROM

Just a quick step by step tutorial to get a Custom ROM working on your HTC One or if you just want to unlock and root!
This guide is especially for the new users, experienced HTC users should already be familiar with this process.
Step 1: Unlock
Go on http://www.htcdev.com and create yourself an account on HTCDEV.
Download these adb/fastboot files
Make a new folder on your C:/ drive called fastboot for example.
Extract the zip downloaded in step 2 to the new folder
Go Here http://www.htcdev.com/bootloader/ and select "All Other Supported Models" and "then begin unlock bootloader"
Yes, Tick both Boxes, Proceed
Skip up to step 8 as we have all we need for the first 7 steps
Power off your phone by holding the power button down for 10 seconds
Power your phone on by holding power and volume down
Highlight Fastboot With Volume+or- then press Power
Plug your phone into your PC and open a Command Prompt.
(windows XP - Click Start > Run > type CMD in box then press OK
(Windows 7 - Click Start > type CMD in search box then press Enter)
Change directory to your folder where we put fastboot files cd c:\fastboot
Type this into your command prompt window fastboot oem get_identifier_token
Select & copy the text as per step 9 on the HTCDev website
Paste your identifier token into the box at the bottom and submit
You Will Very Shortly Receive an email from HTCDev with a link to the second part of the instructions and your "Unlock_code.bin" attached
Download the "Unlock_code.bin" from the email and save it to the same folder that we extracted fastboot files to in step 2
Type this into your command prompt window fastboot flash unlocktoken Unlock_code.bin
The Display Will change on your phone, press Vol + to accept and power to confirm.
Step 2: Recovery
Download the Android SDK (optional)
Download the recovery of your choice, here a few links:
- CWM
- CWM 2
- TWRP
Place the Recovery file you downloaded where the fastboot.exe is (Either in the location of your downloaded fastboot drivers or in the Android SDK directory)
Now open the cmd and navigate to the folder where the Recovery File is located or just open a cmd with shift and right click at the correct directory
Now type:
fastboot flash recovery name_of_the_recovery.img
For example:
fastboot flash recovery recovery-clockwork-touch-6.0.2.8-m7.img
Now your recovery is installed
Step 3: Root
This step is only needed if you want a stock rooted ROM, if you want a custom ROM, skip this step.
Now root your phone with SuperSU by Chainfire or SuperUser by koush
Download SuperSU from this link or SuperUser from this link
Flash it with the Recovery:
Power off your device and then hold the VOL DOWN + Power to boot into the Bootloader
Navigate with VOL and Power to Recovery
Now flash the .zip:
- install zip from sdcard
- choose zip from sdcard
- select the downloaded SuperSU/SuperUser zip file and flash it
- Reboot now
Now you are able to flash any Custom ROM.
Step 4: Custom ROM
With htcdev unlock you need to flash the boot.img after every ROM installation
Note: Most of the custom ROMs have a script which lets the boot.img flash automatically with the ROM, so probably the steps after flashing the ROM are not needed.
If you are in a bootlop though, I recommend you to perform these steps and flash the boot.img with fastboot
Download the ROM you want to flash
Open the ROM zip with an archive manager and extract the boot.img out of it and place it in your fastboot directory
Copy the ROM to your sdcard
Now boot into bootloader again (explained above) and choose recovery with your volume keys and power button
In recovery wipe data and cache aka fullwipe before flashing your ROM if you are moving to a new base (for example from CyanogenMod to a Sense ROM, don't forget to backup your data files, like apps) (Often ROM chefs leave a note in their thread if a fullwipe is needed or not, just follow their advices)
Now flash your ROM by installing zip from sdcard
If this is finished, reboot and reboot into bootloader again
Connect your phone to your PC in fasboot mode (choose in bootloader with power button)
Open a cmd in your fastboot folder with your boot.img and type these two commands:
fastboot flash boot boot.img
fastboot erase cache
Then reboot your phone and wait some minutes to see your ROM booted
Enjoy
Video tutorials (for One S but the steps are the same):
Video-Tutorial by Flow-Wolf:
Bootloader Unlock:
Recovery Installation:
Root:
Custom ROM Installation:

I recommend using SuperUser by koush insted of SuperSU. I also made Super Boot to root stock ROM but I need someone with WWE HTC One...

I added a link for koush's SuperUser

hi
i done everything like its writen here, but i cant boot into recovery.. it cames the screen "entering recovery" and then the device is reboot

noob.fl said:
hi
i done everything like its writen here, but i cant boot into recovery.. it cames the screen "entering recovery" and then the device is reboot
Click to expand...
Click to collapse
Yes currently the recoveries are not working, be patient until they work, I will leave a note in the OP

thanks for responce - i will wait :laugh:
ist there any other opinion to put the su binary into system? maybee with adb?

noob.fl said:
thanks for responce - i will wait :laugh:
ist there any other opinion to put the su binary into system? maybee with adb?
Click to expand...
Click to collapse
adb can't write system on stock, you would need a modified boot.img

noob.fl said:
thanks for responce - i will wait :laugh:
ist there any other opinion to put the su binary into system? maybee with adb?
Click to expand...
Click to collapse
I have modified boot.img but it's from .401 ROM. You want to try?

mike1986. said:
I have modified boot.img but it's from .401 ROM. You want to try?
Click to expand...
Click to collapse
im since a longer time no more so familar with htc... can it harm my device or it does not care and the one will run? if cot my one since to day, and its a damn expensive device to brick it at first time... but if it works - je i will try
its like all other androiddevices to flash? fastboot flash boot boot.img?

noob.fl said:
im since a longer time no more so familar with htc... can it harm my device or it does not care and the one will run? if cot my one since to day, and its a damn expensive device to brick it at first time... but if it works - je i will try
its like all other androiddevices to flash? fastboot flash boot boot.img?
Click to expand...
Click to collapse
There is no chance to brick but there is a chance for bootloop

if got the softwarw nr 1.27.206.1 with kernel [email protected]#1 - will it works with your 401 kernel?

Can you pull the system partition so we can enjoy some stuff from the One on other HTC devices?

tell me how to do and i will share

http://d-h.st/2DO
Unpack and run the runme.bat
Dumping may need a while, upload it to dropbox for example
Imho all devs should work together here instead of trying to be the first guy with a deodexed stock ROM

these are just windowsfiles - does not working on my linux, sorry

torxx said:
http://d-h.st/2DO
Unpack and run the runme.bat
Dumping may need a while, upload it to dropbox for example
Imho all devs should work together here instead of trying to be the first guy with a deodexed stock ROM
Click to expand...
Click to collapse
Do i understand it right i do not need to install recovery to get the system dump?

Simply go to your adb dir and type that in terminal:
adb pull /system ./system
optional:
adb kill-server
7za a -tzip system.zip system\ -r (needs the 7za file)
rmdir system /s /q
to pack a zip

simpelsense said:
Do i understand it right i do not need to install recovery to get the system dump?
Click to expand...
Click to collapse
no, all through adb

noob.fl said:
these are just windowsfiles - does not working on my linux, sorry
Click to expand...
Click to collapse
Using ADB (I assume you already isntalled it)
adb devices
adb pull /system ./system
adb kill-server
It will write it in your ADB folder

torxx said:
no, all through adb
Click to expand...
Click to collapse
thought pulling system is a little more magic.

PROS NEED HELP!! Accidently messed up my phone! :(

So i was installing a rom and accidentally put to erase everything even internal sdcard when i did the wipe Now I cant even do anything but get on TWRP. When I reboot it just stays in google logo. PLEASE help me out and show me how I can put a ROM in my phone. Whoever helps me with correct information I will give you $50 through paypal or bitcoins if you wish.

Do you have a mac or PC?
If you have a Mac then DL "Android File Transfer" Connect your phone to your computer. Boot into TWRP. Your computer and Android File Transfer should see your phone. Drag a ROM .zip to your phone (and any other needed .zip's) flash the rom.
Bing bang boom
---------- Post added at 06:48 PM ---------- Previous post was at 06:48 PM ----------
SecurityBro said:
So i was installing a rom and accidentally put to erase everything even internal sdcard when i did the wipe Now I cant even do anything but get on TWRP. When I reboot it just stays in google logo. PLEASE help me out and show me how I can put a ROM in my phone. Whoever helps me with correct information I will give you $50 through paypal or bitcoins if you wish.
Click to expand...
Click to collapse
Do you have a mac or PC?
If you have a Mac then DL "Android File Transfer" Connect your phone to your computer. Boot into TWRP. Your computer and Android File Transfer should see your phone. Drag a ROM .zip to your phone (and any other needed .zip's) flash the rom.

You can either download and reflash the factory image via fastboot from google:
https://developers.google.com/android/ota
Or download your ROM of choice with the correct vendor image to your computer.
Then while in recovery on the phone and connected to your computer navigate to where you downloaded the ROM, open command prompt or terminal and
"adb push FILENAME.ZIP /sdcard" push all the files you'd like . After finished either reboot recovery from TWRP or adb reboot recovery.
This assumes you have adb installed and as a system variable. If you don't have it installed in PATH then place the files in the appropriate adb location and navigate to it in command prompt and issue the adb push command.

Guys i was able to flash the rom and gapps to my phone using this method:
....highonandroid.com/android-roms/how-to-copy-files-over-to-your-android-in-a-bootloop-with-no-os-using-adb/2/.....
the only thing now is how do i flash .img files such as bootload, vendor and radio files? When im in twrp it gives me 4 options and says "Select partition to flash image"
Boot
System Image
Vendor Image
Recovery
Please let me know where to flash them.

i forgot to mention i have a PC

also to the 2 people above please pm me your paypal address or bitcoin address. Will give you a little something.

Those are the only images you flash via recovery, boot is kernel, the others are self explanatory. Bootloader's are flashed via fastboot.
If you were able to push a ROM via adb just flash the .Zip and boot the ROM as normal.

SecurityBro said:
Guys i was able to flash the rom and gapps to my phone using this method:
....highonandroid.com/android-roms/how-to-copy-files-over-to-your-android-in-a-bootloop-with-no-os-using-adb/2/.....
the only thing now is how do i flash .img files such as bootload, vendor and radio files? When im in twrp it gives me 4 options and says "Select partition to flash image"
Boot
System Image
Vendor Image
Recovery
Please let me know where to flash them.
Click to expand...
Click to collapse
Hello, IMG files are flashed with fastboot from bootloader...
Why not starting fresh...
1 - first, power your phone down.
2 - press power + volume down to reboot to bootloader
3 - plug your phone to your computer
4 - download latest Google factory image here: https://developers.google.com/android/images
This is the latest 7.1.2 worldwide build: https://dl.google.com/dl/android/aosp/angler-n2g47h-factory-f1111327.zip
5 - unzip and navigate inside the folder and locate the flash-all.bat
6 - make sure your phone is in bootloader and properly connected
7 - double click on flash-all.bat and let it run until it reboots
Now you'll have a full stock with latest 7.1.2 to start with...
Just in case, i don't need money. If you still want to donate, choose a charity association of your choice and only send a copy of the receipt here. That will worth 100x more for me than a personal donation... :good:
Good luck...

SecurityBro said:
Guys i was able to flash the rom and gapps to my phone using this method:
....highonandroid.com/android-roms/how-to-copy-files-over-to-your-android-in-a-bootloop-with-no-os-using-adb/2/.....
the only thing now is how do i flash .img files such as bootload, vendor and radio files? When im in twrp it gives me 4 options and says "Select partition to flash image"
Boot
System Image
Vendor Image
Recovery
Please let me know where to flash them.
Click to expand...
Click to collapse
If your PC sees your phone when you are in TWRP then all you need to do is drag over a ROM .zip and the Vendor .img and then just flash them.
I often when doing a fresh fresh install erase everything including internal storage (SDcard) then drag over my needed files to flash and do so.
Since you have a PC i believe that Wang's (i forgot the exact name) toolkit can help you too.

Keep in mind: Really hard to kill a Nexus. If the bootloader is reachable you can always go straight to the stock and start again.
You can find a nice tut at Google's page:developers.google.com
Don't stress, there is (almost) always a way!