Database Users

Updated to 2.3.3- Help me Root

Just updated last night to 2.3.3. I tried the GingerBreak tool but it doesn't work. I only really want to root it to increase the memory card speed. Any help appreciated. Thanks.

Not possible "the easy way".
You need to unlock the bootloader, and use fastboot to flash kanzones rooted system image.
http://forum.xda-developers.com/showthread.php?t=1098736

I wish i could but my play won't go into fastboot mode.

NielDK said:
Not possible "the easy way".
You need to unlock the bootloader, and use fastboot to flash kanzones rooted system image.
http://forum.xda-developers.com/showthread.php?t=1098736
Click to expand...
Click to collapse
well, i think i can only hope for "the easy way" to update...
reading through the step scare me away..

don't mind doing it the hard way but it won't go in fastboot mode.

mikesoftwiz said:
don't mind doing it the hard way but it won't go in fastboot mode.
Click to expand...
Click to collapse
Are you following these steps?
1. Turn your phone off and disconnect the USB cable
2. Hold down the search button
3. Plug in your USB cable
4. The notification light should turn blue.
You're in fastboot mode!

i know the procedure, but it doesn't go. it just turns on. The only thing that works is back button with green light.

Is it sim locked to a network? If so then ya you probably never will get into fastboot
Sent from my R800i using XDA App

was locked but I got the unlocking code from the network provider....

Well that's great, but what you should do is flash the UK generic fw(found around here) then install gingerbreak and root, then after that run the ota update and it'll do its thing when its done you should be left with 2.3.3 rooted. Unless your bootloader is unlocked then you can just fastboot the rooted img. Hope this helps you man!
Sent from my R800i using XDA App

Do u think Gingerbreak will be updated to accommodate 2.3.3... do we have any news on this?

crimsonnight said:
Do u think Gingerbreak will be updated to accommodate 2.3.3... do we have any news on this?
Click to expand...
Click to collapse
hardly think so, exploit was fixed, and the developers of the exploit made it like a proof of concept, already stated no further development will be done. Note that chainfire was not the one making the exploit, he made the apk utilizing the exploit.
Sent from my GT-I9100 using XDA Premium App

[Guide][Unlock][Root]HTC EVO4g, unlock and root with HTCdev and su binaries

I am getting a ton of hits on my blog for this link! Please if you use the link, say hi to me or click the thanks button or at least leave feed back!
Also, ads help me out and want to do more writing!!!
Thank you everyone!
Click to expand...
Click to collapse
I decided to downgrade everything on my device and take the latest OTA, including the 2.18 hboot. This version is unlockable through the HTCdev website. From there you can simply flash a custom recovery and install the su binaries.
I have guides written up, on both, on my blog, and encourage you to check them out!
To unlock your bootloader, start HERE. Credit to HTCdev obviously for their attempt to give their customers what they want.
Next, to flash recovery and install su binaries check out THIS. Credit to chainsDD for his awesome work and continued devotion to root.
Note: This will not give you S-off, this does come with some limitations but I have not been hindered too much. The one thing I have not been able to do is flash a custom splash screen, because you have to do it through bootloader and it will not get past security. Other wise you can flash anything you would normally do in recovery.
My goal in doing this was to gain the experience, as many of the newer HTC devices only have this option available to them and I want to see the ins and outs as well as the downsides. I know there are methods of reverting back to froyo and using unrEVOked, which is tempting but I like the knowledge.
I already feel much more comfortable with SDK, fastboot and adb commands. This makes me feel more in tune with the Android OS and more comfortable to begin delving into development. I am a curious person and like to know what is going on with my device.
A discussion here would also be welcomed, for anything relating to using the unlocked bootloader. I will be glad to share my findings and try out some of the other things people are doing in order to use the phone in this state.
First off, any ideas on getting the splash screen changed? I was thinking, maybe a flashable zip? Or pushing through fastboot?

You won't be able to change the splash screen without S-OFF. You can only update the partitions that HTC has unlocked, which are boot, system, and recovery. The others still require signature verification, which means an unsigned zip won't write successfully. I don't know of any way around that, besides the obvious method of downgrading the HBOOT/Baseband and using a full NAND unlock method.

Captain_Throwback said:
You won't be able to change the splash screen without S-OFF. You can only update the partitions that HTC has unlocked, which are boot, system, and recovery. The others still require signature verification, which means an unsigned zip won't write successfully. I don't know of any way around that, besides the obvious method of downgrading the HBOOT/Baseband and using a full NAND unlock method.
Click to expand...
Click to collapse
So where is the splash screen located? I am fairly new to the insides of this stuff, really just dl and flash what sounds good.
Could you make a signed zip that would push the image?

imheroldman said:
So where is the splash screen located? I am fairly new to the insides of this stuff, really just dl and flash what sounds good.
Could you make a signed zip that would push the image?
Click to expand...
Click to collapse
Not exactly sure, but I think it has it's own home (separate from the unlocked partitions, that is). And we cannot make a signed zip that will update a locked partition because we don't have HTC's signature.

Wouldn't you be able to change the splash image 1 from a ruu with the splash screen and then run the ruu to get the splash screen
Sent from my swiper using XDA App

evo4gnoob said:
Wouldn't you be able to change the splash image 1 from a ruu with the splash screen and then run the ruu to get the splash screen
Sent from my swiper using XDA App
Click to expand...
Click to collapse
An RUU still authenticates through the bootloader and needs to have HTC's signature. There aren't any EVO HTC-signed RUUs with a splash screen different than the one we have.

Captain_Throwback said:
An RUU still authenticates through the bootloader and needs to have HTC's signature. There aren't any EVO HTC-signed RUUs with a splash screen different than the one we have.
Click to expand...
Click to collapse
If you go to the 3vo forums I believe there is a workaround for hboot 1.5 so I think it can be applied to us also
Sent from my swiper using XDA App

evo4gnoob said:
If you go to the 3vo forums I believe there is a workaround for hboot 1.5 so I think it can be applied to us also
Sent from my swiper using XDA App
Click to expand...
Click to collapse
Can you find it?

I am getting a ton of hits on my blog for this link! Please if you use the link, say hi to me or click the thanks button or at least leave feed back!
Also, ads help me out and want to do more writing!!!
Thank you everyone!

[How to] Unlock the Nexus 9 Bootloader and Root

Hey everyone, made a tutorial showing how to unlock the bootloader on your Nexus 9! I'll make rooting videos and more soon enough.
Hope they help.
How to unlock the bootloader:
https://www.youtube.com/watch?v=AJEORWbf658
How to root the Nexus 9:
http://youtu.be/5jwoPx5mB7Y
Unboxing and hands on:
https://www.youtube.com/watch?v=8K5WAmwRH7o

Doing it as soon as i get home .

That's the first nexus device I've seen that doesn't use Google's bootloader, very interesting!
Sent from my Nexus 10 using Tapatalk

Good news: You can unlock the bootloader under the development tab in settings. http://www.androidpolice.com/2014/1...-6-9-requires-checking-box-developer-options/

lary50 said:
Good news: You can unlock the bootloader under the development tab in settings. http://www.androidpolice.com/2014/1...-6-9-requires-checking-box-developer-options/
Click to expand...
Click to collapse
Thanks for that, I kept getting permission denied. All is well now ?

I wonder what HTC means when they say ,"this *may* void your warranty" when unlocking the bootloader. Did the all the other nexus devices say that in the bootloader before they were unlocked?

Deltadroid said:
Did the all the other nexus devices say that in the bootloader before they were unlocked?
Click to expand...
Click to collapse
My nexus 4 did.

I guess it's fine as long as it's not being permanently marked with some bit set somewhere so their service department can see. The device can be locked again.

pantmunu said:
Doing it as soon as i get home .
Click to expand...
Click to collapse
same there but them i get it i will
Edit: no need to set up adb or fastboot
i have ubuntu haha

Deltadroid said:
I wonder what HTC means when they say ,"this *may* void your warranty" when unlocking the bootloader. Did the all the other nexus devices say that in the bootloader before they were unlocked?
Click to expand...
Click to collapse
They did. Although you can just type fastboot oem lock and it should relock the bootloader without wiping any data.

Will wait till root is available to unlock it

mk92595 said:
Will wait till root is available to unlock it
Click to expand...
Click to collapse
No way. Unlocking wipes the device, but rooting doesnt. I plan to unlock mine the second I get it. That way I can start loading data and stuff onto it and start using it. Then, when root is available, I don't have to wipe my data at that point to do it becuase I was already proactive about unlocking the bootloader.

qbking77 said:
Hey everyone, made a tutorial showing how to unlock the bootloader on your Nexus 9! I'll make rooting videos and more soon enough.
Hope they help.
How to unlock the bootloader:
https://www.youtube.com/watch?v=AJEORWbf658
Unboxing and hands on:
https://www.youtube.com/watch?v=8K5WAmwRH7o
Click to expand...
Click to collapse
Hey great tutorial!
I got 1 problem.
I installed the latest android the latest sdk of android on my pc.
Followed the tutorial from you to setup adb. although its from 2011
and when i tried to do: 'adb devices' nothing happened.
The list stayed empty and my nexus 9 didn't have a pop up.
I had the nexus 9 unlocked with the screen on.

berendspruijt said:
Hey great tutorial!
I got 1 problem.
I installed the latest android the latest sdk of android on my pc.
Followed the tutorial from you to setup adb. although its from 2011
and when i tried to do: 'adb devices' nothing happened.
The list stayed empty and my nexus 9 didn't have a pop up.
I had the nexus 9 unlocked with the screen on.
Click to expand...
Click to collapse
Same there win 8
But I unlocked it
On Ubuntu

berendspruijt said:
Hey great tutorial!
I got 1 problem.
I installed the latest android the latest sdk of android on my pc.
Followed the tutorial from you to setup adb. although its from 2011
and when i tried to do: 'adb devices' nothing happened.
The list stayed empty and my nexus 9 didn't have a pop up.
I had the nexus 9 unlocked with the screen on.
Click to expand...
Click to collapse
If you're on Windows, it could be a driver problem. You can check on it in Windows device manager. If you need to install the driver, Open the Android SDK manager and make sure the USB driver is installed, and install any available updates. If that doesn't work, you can find the Google nexus USB driver by itself and install it using the windows device manager. You can search for the relevant step by step guides here on the forum or elsewhere online.

mrkvchm said:
No way. Unlocking wipes the device, but rooting doesnt. I plan to unlock mine the second I get it. That way I can start loading data and stuff onto it and start using it. Then, when root is available, I don't have to wipe my data at that point to do it becuase I was already proactive about unlocking the bootloader.
Click to expand...
Click to collapse
I already installed everything I need. also with ADB you can backup apps easily.

mk92595 said:
I already installed everything I need. also with ADB you can backup apps easily.
Click to expand...
Click to collapse
But you'll have to reinstall everything when you unlock the bootloader. I know its not hard to do with ADB, but I don't understand why you'd bother backing up and restoring everything when you can just unlock the bootloader right away and save yourself from wiping to root once you're already established on the device. Well, to each his own I guess.

If i unlock my nexus9 do i still get android OTA's?

hill67 said:
If i unlock my nexus9 do i still get android OTA's?
Click to expand...
Click to collapse
Yes

mrkvchm said:
But you'll have to reinstall everything when you unlock the bootloader. I know its not hard to do with ADB, but I don't understand why you'd bother backing up and restoring everything when you can just unlock the bootloader right away and save yourself from wiping to root once you're already established on the device. Well, to each his own I guess.
Click to expand...
Click to collapse
I already have my Nexus 9. Everything is already installed.

[INTERNATIONAL]Unlock Your Bootloader!

This process has been done with the HTC International version available in Australia.
Im sure everyone would appreciate follow up from others to confirm which versions of the phone this process works with.
The process below assumes a small amount of familiarity with HTC unlock process AND WILL WIPE THE DATA FROM YOUR PHONE!
The process is basically the same as ever with a few variations
Install adb
Go to http://www.htcdev.com/bootloader and sign up, click unlock bootloader
In the device selection drop-down select "any other supported device"
Boot into "Download Mode" - Which is the equivalent of fastboot. (shutdown your phone, hold power+volume down until you boot into this mode). This is the mode with the black background and red text
Connect phone to PC, and issue "fastboot oem get_identifier_token"
Copy the code into the returned by adb into space on HTCs website
Get the email, download the attachment and issue "fastboot flash unlocktoken Unlock_code.bin"

I'll wait for a S-OFF method
You won't need htcdev, your phone won't be registered over there.

Always good to know we can root the new flagship

Super-Veloce said:
I'll wait for a S-OFF method
You won't need htcdev, your phone won't be registered over there.
Click to expand...
Click to collapse
On Lollipop there's no such shortcut.. your device must be rooted before proceeding to S-OFF..

jauhien said:
On Lollipop there's no such shortcut.. your device must be rooted before proceeding to S-OFF..
Click to expand...
Click to collapse
Really?? Damn..

I keep getting:
Code:
C:\WINDOWS\system32>fastboot oem get_identifier_token
...
FAILED (remote: unknown command)
finished. total time: 0.007s
Tried it on 2 different systems :S

What mode was your phone in? Were you in download mode? Or in the bootloader?

daveh86 said:
What mode was your phone in? Were you in download mode? Or in the bootloader?
Click to expand...
Click to collapse
Ahhh...... I thought i was in download, but was in bootloader (still accept fastboot commands)
HTC Download mode says... "hTC download mode" up the top and is a black screen if any one else comes across this...

EndoSurf said:
Ahhh...... I thought i was in download, but was in bootloader (still accept fastboot commands)
HTC Download mode says... "hTC download mode" up the top and is a black screen if any one else comes across this...
Click to expand...
Click to collapse
Thanks, I've added a note in my comment that mentions that download mode is the one with black background and red text.

And how i will make it S-Off?

Richi207 said:
And how i will make it S-Off?
Click to expand...
Click to collapse
By being patient... the device is not even available in most regions yet, give developers a little time would you.

For Verizon test M9's, can't even pull identifier token. Fastboot command yields "FAILED (remote: unknown command)," which is interesting because I used fastboot to successfully flash TWRP then root.

jauhien said:
On Lollipop there's no such shortcut.. your device must be rooted before proceeding to S-OFF..
Click to expand...
Click to collapse
Is there a way to s-off? Ive seen some have already done it, but how?

Test devices come S-OFF.

hgoldner said:
Test devices come S-OFF.
Click to expand...
Click to collapse
Or you can give the Phone to a shop / repair centre to s-off it
In Germany you can do it at:
http://www.gsm-europe.de/epages/635...3/Products/htc_soff/SubProducts/htc_soff-0001
Its a shop in Berlin they do s-off and supercid
And they can do it on the Onde M9
Only bad thing they cant Unlock bootloader it without HTC Dev.
So You get your phone back with S-Off and with Super Cid but Boodloader is Locked and you must Unlock it via HTC dev
because for Unlock via Fastboot you need root on Android 5

I remember when I first unlocked the bootloader on the M7, I lost a couple stock apps. If anyone's tried the official HTC-DEV unlock method yet, are all apps intact?

Prasad said:
I remember when I first unlocked the bootloader on the M7, I lost a couple stock apps. If anyone's tried the official HTC-DEV unlock method yet, are all apps intact?
Click to expand...
Click to collapse
Didn't notice any loss after unlocking M9 ..

jauhien said:
Didn't notice any loss after unlocking M9 ..
Click to expand...
Click to collapse
Thank you! Now I can confidently proceed when the device arrives in a couple hours.

Richi207 said:
And how i will make it S-Off?
Click to expand...
Click to collapse
you're gonna have to wait a while for that

Been a long time since I unlocked a bootloader. But I don't lose any OTA functionality do I?
Sent from my HTC One M9 using XDA Free mobile app

Stuck on Google Logo, Can't Unlock Bootloader

Hey there.
So I tried to use the Nexus Root Toolkit to sideload the OTA, but now when I try to boot my phone it just shows the white google screen and doesn't do anything. I can use ADB and fastboot and get into the bootloader but I can't flash the factory image because I never checked the "Allow OEM Unlock" tick since I didn't plan on unlocking the bootloader. Can anyone help me out here?

Durvid said:
Hey there.
So I tried to use the Nexus Root Toolkit to sideload the OTA, but now when I try to boot my phone it just shows the white google screen and doesn't do anything. I can use ADB and fastboot and get into the bootloader but I can't flash the factory image because I never checked the "Allow OEM Unlock" tick since I didn't plan on unlocking the bootloader. Can anyone help me out here?
Click to expand...
Click to collapse
This is exactly why you should never mess with updates or flashing anything with a locked bootloader. If a factory reset doesn't fix it you're likely out of luck.

if your bootloader is locked still I can't see how flashing an OTA would effect this.
Have you tried to flash just the original bootloader from the android version on your device ( not the version you wish to update to )
Fastboot flash bootloader bootloader.img
DON'T USE A TOOL KIT ! UNLESS YOU KNOW WHAT YOU ARE DOING ! There where clear instructions on how to flash OTA's on this site and likely in the toolkit.
Unfortunately this is a case of NOT reading before doing things, I have yet to see anyone recover from this.
Best of luck tho, but it might be a lesson learned the hardway a.k.a RMA

hutzdani said:
if your bootloader is locked still I can't see how flashing an OTA would effect this.
Have you tried to flash just the original bootloader from the android version on your device ( not the version you wish to update to )
Fastboot flash bootloader bootloader.img
DON'T USE A TOOL KIT ! UNLESS YOU KNOW WHAT YOU ARE DOING ! There where clear instructions on how to flash OTA's on this site and likely in the toolkit.
Unfortunately this is a case of NOT reading before doing things, I have yet to see anyone recover from this.
Best of luck tho, but it might be a lesson learned the hardway a.k.a RMA
Click to expand...
Click to collapse
I'll attempt this. Weirdly enough when I look at device info in adb it shows it as being on the newest version. But Yeah I'll attempt to flash what I was on before.
Yeah, I mean I've done this before with no issues on my Nexus 6 and there were no issues but that was unlocked when I got it. I just thought you didn't have to unlock the bootloader to sideload OTA's? I may be wrong.

hutzdani said:
if your bootloader is locked still I can't see how flashing an OTA would effect this.
Have you tried to flash just the original bootloader from the android version on your device ( not the version you wish to update to )
Fastboot flash bootloader bootloader.img
Click to expand...
Click to collapse
Yeah like I thought, "Device is locked. Cannot Flash Images"
I wish I had known they added that "Allow OEM Unlock" Switch in Lollipop. Would have solved my problem if I had that toggled.

Durvid said:
Yeah like I thought, "Device is locked. Cannot Flash Images"
I wish I had known they added that "Allow OEM Unlock" Switch in Lollipop. Would have solved my problem if I had that toggled.
Click to expand...
Click to collapse
You just said you had a nexus 6 unlocked, how did you not know the switch existed?

hutzdani said:
if your bootloader is locked still I can't see how flashing an OTA would effect this.
Have you tried to flash just the original bootloader from the android version on your device ( not the version you wish to update to )
Fastboot flash bootloader bootloader.img
DON'T USE A TOOL KIT ! UNLESS YOU KNOW WHAT YOU ARE DOING ! There where clear instructions on how to flash OTA's on this site and likely in the toolkit.
Unfortunately this is a case of NOT reading before doing things, I have yet to see anyone recover from this.
Best of luck tho, but it might be a lesson learned the hardway a.k.a RMA
Click to expand...
Click to collapse
akellar said:
You just said you had a nexus 6 unlocked, how did you not know the switch existed?
Click to expand...
Click to collapse
I bought it used on /r/hardwareswap and whoever I got it from had already unlocked it.

I know someone advised you to try to flash a bootloader, but it isn't going to work of your bootloader is locked. What build were you on and which OTA zip did you try to flash?

Heisenberg said:
I know someone advised you to try to flash a bootloader, but it isn't going to work of your bootloader is locked. What build were you on and which OTA zip did you try to flash?
Click to expand...
Click to collapse
I started on 6.0 MDB08L and was trying to flash 6.1 MMB29M

Durvid said:
I started on 6.0 MDB08L and was trying to flash 6.1 MMB29M
Click to expand...
Click to collapse
OK, but I need the name of the zip please.

Heisenberg said:
OK, but I need the name of the zip please.
Click to expand...
Click to collapse
Sorry, it's
533df5ddfa4297997634a8553f0122be5cca4c09.signed-angler-MMB29M-from-MDB08L.zip.
Grabbed it from here: https://www.reddit.com/r/Nexus6P/comments/3w6qzd/easy_how_to_sideload_ota_601/

Durvid said:
Sorry, it's
533df5ddfa4297997634a8553f0122be5cca4c09.signed-angler-MMB29M-from-MDB08L.zip.
Grabbed it from here: https://www.reddit.com/r/Nexus6P/comments/3w6qzd/easy_how_to_sideload_ota_601/
Click to expand...
Click to collapse
OK, just needed to make sure you had the right one. What have you done to troubleshoot so far?

Heisenberg said:
OK, just needed to make sure you had the right one. What have you done to troubleshoot so far?
Click to expand...
Click to collapse
I've tied to flash stock, but can't do that due to the bootloader being locked, tried to just hard reset but it just does the same thing where it gets stuck on the Google logo. I checked the manufacture info in the toolkit and everything is clean. Tried to flash the old bootloader but like you said I can't flash since I'm locked. Not really sure what else to do :/

Durvid said:
I've tied to flash stock, but can't do that due to the bootloader being locked, tried to just hard reset but it just does the same thing where it gets stuck on the Google logo. I checked the manufacture info in the toolkit and everything is clean. Tried to flash the old bootloader but like you said I can't flash since I'm locked. Not really sure what else to do :/
Click to expand...
Click to collapse
Honestly, I think you're pretty much screwed unfortunately. You could talk to Google support and see if they'll RMA the phone.

Heisenberg said:
Honestly, I think you're pretty much screwed unfortunately. You could talk to Google support and see if they'll RMA the phone.
Click to expand...
Click to collapse
Yeah I think they would do it since I technically didn't void any warrantys or anything. I appreciate the help. What do I need to make sure to do if I do this again in the future? Definitely "Allow OEM Unlock", and do I have to unlock the bootloader? I was under the impression that you didn't have to to flash an OTA.

Durvid said:
Yeah I think they would do it since I technically didn't void any warrantys or anything. I appreciate the help. What do I need to make sure to do if I do this again in the future? Definitely "Allow OEM Unlock", and do I have to unlock the bootloader? I was under the impression that you didn't have to to flash an OTA.
Click to expand...
Click to collapse
Definitely unlock the bootloader, it isn't needed to flash an update via the stock recovery, but it is needed to get out of sticky situations like this. If your bootloader was unlocked now you'd be up and running in ten minutes.

Durvid said:
Sorry, it's
533df5ddfa4297997634a8553f0122be5cca4c09.signed-angler-MMB29M-from-MDB08L.zip.
Grabbed it from here: https://www.reddit.com/r/Nexus6P/comments/3w6qzd/easy_how_to_sideload_ota_601/
Click to expand...
Click to collapse
Hilarious that the top comment is mine telling you why doing this is a bad idea

Heisenberg said:
Definitely unlock the bootloader, it isn't needed to flash an update via the stock recovery, but it is needed to get out of sticky situations like this. If your bootloader was unlocked now you'd be up and running in ten minutes.
Click to expand...
Click to collapse
Yeah, I'll probably wait for the update over the air for a while and maybe if I feel reallly eager I'll just make sure I unlock and such. Annoying that you can't unlock via fastboot anymore without that toggle. I get that Google is trying to make Android super secure but It's not too useful for folks like us. Sure it's bricked a lot of devices.

akellar said:
Hilarious that the top comment is mine telling you why doing this is a bad idea
Click to expand...
Click to collapse
I've done it before with other devices. I wouldn't say it's inherently bad. It's just that there was one toggle that I wasn't aware of that caused the issue. You live and you learn.

THIS IS NOT MY IDEA !
I found this in a N9 thread and it worked according to the user with the issue, apply this with the correct t factory image ( do it with the version you have on your device not the one you tried to update to ! )
This might not work but its worth a try ! Before doing this read about ADB and Fastboot !!!!!!!!!!!!!!!! Try and understand the basics and know what the commands are doing to help backtrack e.C.t
If it does work - go to settings and allow OEM Unlock and USB debug !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Then go read from reputable sources how to flash images manually via adb !!!!!!!!!!!!!!!!!!!!!!!
I'd follow vomers guides.
Had this problem with another device cool thing to remeber is that on locked devices the only thing that is different is that there is a signature before the MAGIC header so the solution is to pull the android stock images from https://developers.google.com/android/nexus/images. Once done extract the images in both the zip and the tar that is inside the zip. You will see recovery.img inside the tar. One thing about the boot process of TWRP is that it enables adb in preboot meaning while in the boot loop you should have access to adb. With access to adb all you need to do is dd the images over the corresponding partitions: i.e.
PLEASE NOTE NOT FOR THE FEINT OF HEART. I AM NOT RESPONSIBLE FOR YOU BRICKING YOUR DEVICE.
Quote:
adb push recovery.img recovery.img
adb shell dd if=recovery.img of=/dev/block/<recoverymmcblock>
I dont know if the default recovery has adb push update so id probably recommend doing this on every partition thats inside the tar, i.e. system, boot.