Database Users

Bricked cdma htc hero after ruu 1.56

i ran the ruu update when i got my phone and went to 90 percent then error 110 missing file,
now it only goes to fastboot menu with no options to select from, ive tried the ruu from sdk and same error,
so if any help i can get from you guys would be greatly appreciated,
ive looked all over the google.com and have come up with no luck on how to fix this ,
i know its like the radio image that doesnt flash or something, also in sdk i cant adb to recognize device.
please help ive been to geekfor.me and no help there,
if it helps the phone is a with google stamp on it. well lets see how this thread goes from here.

Try re-downloading the ruu.
What rom were you coming from?

I haven't found anyone that has a solution to the 110 file error when flashing the RUU...
I as well as a few other gave up hope and have all since gotten replacement Heros.
The main crux of the issue is that the fastboot you are booting into will not allow adb commands and hence will never allow the RUU to install completely.
Hate to say it, but figure out a way to exchange the phone for a new one, you are stuck in an infinite loop of 110 errors...
R

Hi again R.
Yes, error 110 is a nasty one indeed. It's the reason I am hesitant to root Hero #2. I still have my 110'd Hero and am (so far unsuccessfully) hacking it back to health.
@turboek99: Yes, what rom did you have installed? Mine was modaco 2.2

gibsontest said:
Hi again R.
Yes, error 110 is a nasty one indeed. It's the reason I am hesitant to root Hero #2. I still have my 110'd Hero and am (so far unsuccessfully) hacking it back to health.
@turboek99: Yes, what rom did you have installed? Mine was modaco 2.2
Click to expand...
Click to collapse
I already re-rooted both of my phones again and am playing with ROMs, LOL so although I know what the concerns are with RUU, I'm just hoping that I can not mess things up so much that a RUU would be my only choice. My only issue is I cannot deal with the phone being as slow as it was and without Root and a ROM, I feel like I'd rather go get something else... So I have no choice but to play with fire...
The way I see it, if I can keeep these stable long enough and something finally does happen, I only hope the Supersonic is out and I an "forced" to upgrade
R

Didnt know that about ruu...sucks.
Just noticed ur screenname,turboed b16?..u take it out to the tracks or run it in the streets?.....ima take a guess and say u stay in socal?lol

johndoehizzle said:
Didnt know that about ruu...sucks.
Just noticed ur screenname,turboed b16?..u take it out to the tracks or run it in the streets?.....ima take a guess and say u stay in socal?lol
Click to expand...
Click to collapse
Kcarpenter <- Turbo b16 '94 Coupe. Uber Fun down "The Dragon"

I'll probably brick my phone intentionally when the Supersonic or the next-gen Sprint android comes out so I have an excuse to upgrade.

Anyway... back on topic. Try flashing recovery image from ADB like this:
Code:
adb remount
It should then say remount succeded.
Code:
adb push recovery.img /sdcard
adb shell
cd /sdcard
flash_image recovery recovery.img
reboot recovery
and then flash a custom ROM. I actually made that mistake when I first rooted.

Kcarpenter said:
Kcarpenter <- Turbo b16 '94 Coupe. Uber Fun down "The Dragon"
Click to expand...
Click to collapse
Niiice.i got 2 ej1's. One auto.the other stick.i used to run that one all the time,had a turboed gsr swap with type r head.got rid of it n back to a single cam...i recently got it stolen too..stereo n black slips with brand new tires got jacked lol.left it sitting on the ground..

Kcarpenter said:
Kcarpenter <- Turbo b16 '94 Coupe. Uber Fun down "The Dragon"
Click to expand...
Click to collapse
Mistamike <- 2001 Integra Type R

HeroMeng said:
Anyway... back on topic. Try flashing recovery image from ADB like this:
Code:
adb remount
It should then say remount succeded.
Code:
adb push recovery.img /sdcard
adb shell
cd /sdcard
flash_image recovery recovery.img
reboot recovery
and then flash a custom ROM. I actually made that mistake when I first rooted.
Click to expand...
Click to collapse
there in lies the problem, after you get the 110 error you have no more ADB. it boots into a fastboot that does not have ADB support
so the real problem is how to re-enable ADB commands, then reflashing should be simple and straight-forward...
R

RTessi said:
there in lies the problem, after you get the 110 error you have no more ADB. it boots into a fastboot that does not have ADB support
so the real problem is how to re-enable ADB commands, then reflashing should be simple and straight-forward...
R
Click to expand...
Click to collapse
Well, you can flash in fastboot... but that never worked for me.

I'm on this same boat and have been trying to find a solution. Luckily I just recently got my phone and am planning on taking it in. I did seem to find a thread where someone fixed this but they didn't say how... I messaged the guy who helped that person out but he hadn't replied yet. Forum dot ppcgeeks dot com/showthread.php?t=111587 Hope it is ok to post the link otherwise I apologize. I would really like to get my hero fixed if possible. I have a sprint hero 1.56.651.2 and used the signed RUU that's on a few threads. At first, I kept getting the connection error while trying to do the RUU, I wish I would have stopped here. But I finally got the RUU to detect and start. it was at around 85% when it moved on to the next thing after user settings I believe and it gave me the ERROR[110]. I've tried the holding volume down and powering on and many other keys but no luck.

finally got it replaced
well i got a replacement phone so kinda happy now, too bad it s a refurb unit as opposed to the brand new unit i f'ked up before. well off to what i was when i fked up my other one.haha

Heh, ditto. I got a brand spanken new one though. This time I made a backup before I soiled it.

flashed 2.1 ruu anyway to fake sprint signature on update.zip?

So I went ahead and just did it ran the ruu. So i been trying ways to unroot this as much as my not so experienced self is. Well first i tried to replace the rom.zip with an older one as if that was done it would be the easiest way. well replaced it but it didn't successfully flash once it got to the flash bootloader part. Then I booted to recovery and first thing it said was E:can't archive /cache/recovery/command. So I tried to apply update.zip it started to go through but got a signature failure. Anyways any help with this would be great
new pri 2.20_003

thatguythatdid said:
So I went ahead and just did it ran the ruu. So i been trying ways to unroot this as much as my not so experienced self is. Well first i tried to replace the rom.zip with an older one as if that was done it would be the easiest way. well replaced it but it didn't successfully flash once it got to the flash bootloader part. Then I booted to recovery and first thing it said was E:can't archive /cache/recovery/command. So I tried to apply update.zip it started to go through but got a signature failure. Anyways any help with this would be great
new pri 2.20_003
Click to expand...
Click to collapse
Throw it into the toilet and get a warranty replacement quick, before all the phones have 2.1.
Other then that, the only way to find root would be to have a good knowledge of linux, kernels, c, etc, and find known linux exploits and go down the list and try them.

robchaos said:
Throw it into the toilet and get a warranty replacement quick, before all the phones have 2.1.
Other then that, the only way to find root would be to have a good knowledge of linux, kernels, c, etc, and find known linux exploits and go down the list and try them.
Click to expand...
Click to collapse
I'm getting a new one today from craigslist so if I never post again then I'll be one of those when craigslist goes wrong stories on the news.
Also I never got the warranty from sprint I got the warranty from radioshack because they said that they cover everything but water damage. So right before I threw it off my roof I called radioshack to make sure they would cover it they said they only cover wear and tear and software.
I still would like to know how to make an sign an update zip though so I can flash it through recovery.

thatguythatdid said:
I'm getting a new one today from craigslist so if I never post again then I'll be one of those when craigslist goes wrong stories on the news.
Also I never got the warranty from sprint I got the warranty from radioshack because they said that they cover everything but water damage. So right before I threw it off my roof I called radioshack to make sure they would cover it they said they only cover wear and tear and software.
I still would like to know how to make an sign an update zip though so I can flash it through recovery.
Click to expand...
Click to collapse
First of all, do you have mac or windows?

Doesn't matter, The RUU removes root and the ability to flash a custom recovery, doesn't it?

HeroMeng said:
First of all, do you have mac or windows?
Click to expand...
Click to collapse
Sorry messing with the phone. I got a pc windows 7 64 blah blah. I did try to manual update but it wont let me because it says that main version is older.

robchaos said:
Doesn't matter, The RUU removes root and the ability to flash a custom recovery, doesn't it?
Click to expand...
Click to collapse
Yes and no. While in the new recovery it gives you the ability to flash an update zip from your sd but I get signature fails if I could fake the signature then I could flash a rooted rom and carry out from there putting a new recovery image and so fourth

thatguythatdid said:
Yes and no. While in the new recovery it gives you the ability to flash an update zip from your sd but I get signature fails if I could fake the signature then I could flash a rooted rom and carry out from there putting a new recovery image and so fourth
Click to expand...
Click to collapse
What happens if you try flashing any of the released roms out there, like fresh rom? It is signed using test keys. That would be crazy if the new recovery lets you flash any signed rom, but I predict it's locked down to HTC's keys which are privately encrypted keys. You can't fake them.

flipzmode said:
What happens if you try flashing any of the released roms out there, like fresh rom? It is signed using test keys. That would be crazy if the new recovery lets you flash any signed rom, but I predict it's locked down to HTC's keys which are privately encrypted keys. You can't fake them.
Click to expand...
Click to collapse
I've tried only tried a couple so far it takes a sec though cuz I gotta reboot to put anything on and I'll try the fresh 2.0d
Justg tried the original fresh 2.od and got signature verification failed

Going to pick up my new phone so if any body has anyideas on how to root this when I get back let me know. When we gonna get a leak that lets you sign with htcs keys

thatguythatdid said:
Going to pick up my new phone so if any body has anyideas on how to root this when I get back let me know. When we gonna get a leak that lets you sign with htcs keys
Click to expand...
Click to collapse
It should be 1.5, so just root it w/ http://forum.xda-developers.com/showthread.php?t=583291 and you'll be good to go.

thatguythatdid said:
Going to pick up my new phone so if any body has anyideas on how to root this when I get back let me know. When we gonna get a leak that lets you sign with htcs keys
Click to expand...
Click to collapse
i may be crazy.... but if we find a way to root this 2.1 before they release it couldn't they then patch that exploit? maybe this is why they "leaked" it so we could have a chance to find any holes or exploits in the software/bootloader/recovery?

regaw_leinad said:
It should be 1.5, so just root it w/ http://forum.xda-developers.com/showthread.php?t=583291 and you'll be good to go.
Click to expand...
Click to collapse
I meant the one with the 2.1 on it
thedudejdog said:
i may be crazy.... but if we find a way to root this 2.1 before they release it couldn't they then patch that exploit? maybe this is why they "leaked" it so we could have a chance to find any holes or exploits in the software/bootloader/recovery?
Click to expand...
Click to collapse
you may be right I thought of it but I don't know how clever they are considering how long it's taken them to put out the same rom we had back in march

thatguythatdid said:
I meant the one with the 2.1 on it
Click to expand...
Click to collapse
Oh, sorry my bad

regaw_leinad said:
Oh, sorry my bad
Click to expand...
Click to collapse
No problem . I'm glad that devs are looking at this maybe we can have a solution before the problem

sandboxlove said:
so the new recovery lets you flash updates? their just asking for us to better their software, jesus...
Click to expand...
Click to collapse
What like their gonna do it? I heard the ssamsung 2.1 update didn't even have live wallpapers

go to cyanogens wiki page. and find where he manually replaces the /radio partition.
if you have fastboot you can manually replace every partition this way. including /recovery.
just an idea.

Avalaunchmods said:
go to cyanogens wiki page. and find where he manually replaces the /radio partition.
if you have fastboot you can manually replace every partition this way. including /recovery.
just an idea.
Click to expand...
Click to collapse
Thanks for the idea just got my new phone still got the old one so I'm definitley gonna try some things now. Before I root the new one is there any info or anything someone might want from it. I don't know if it can help someone but it might. I'll wait till tonight to do it

Avalaunchmods said:
go to cyanogens wiki page. and find where he manually replaces the /radio partition.
if you have fastboot you can manually replace every partition this way. including /recovery.
just an idea.
Click to expand...
Click to collapse
Sweet link bro!

[Solved] T-Mobile OTA My touch 3G Update Files 1, 2 and 3 (?).

File 1 http://android.clients.google.com/packages/ota/tmobile_opal/894fb8631db9.hboot-1.33.0013.opal.zip
File 2 https://android.clients.google.com/...59adc603a3.signed-opal-ota-60505.e059adc6.zip
File 3 (Still Not sure what this file is)
https://android.clients.google.com/...17d.signed-opal-FRG83-from-DMD64.e3671133.zip
Here are the correct downloads. This update only works on the Original My Touch 3G. Not the My Touch 3G 3.5 or Fender Version.
I took these instructions from Smapdi's Post
Renamed 894fb8631db9.hboot-1.33.0013.opal.zip to update.zip and placed it into the root of my SD card. Rebooted into recovery and flashed it (Turn on with Home then Power Key to boot into recovery). The process restarted the phone a few times (DO NOT TOUCH THE THING ONCE YOU START THE FLASH!!!!!) and eventually booted into 1.6.
I rebooted into fastboot and saw HBOOT was now 1.33.0013 :-D
I then took e059adc603a3.signed-opal-ota-60505.e059adc6.zip and renamed it to update.zip and put it into the root of the SD card deleting the previous file. Repeated the same steps as before and the phone did the whole restart itself a few times thing and eventually booted to 2.2!!!
Great work guys!
Thanks for everyones help I hope you enjoy Froyo 2.2.
Stingerrray

Stingerrray said:
File 1 (I Think) https://android.clients.google.com/...17d.signed-opal-FRG83-from-DMD64.e3671133.zip
File 2 (I Know) https://android.clients.google.com/...59adc603a3.signed-opal-ota-60505.e059adc6.zip
The downloads worked for me can someone confirm that theses are the correct files. And maybe help with installation.
Thanks "Phateless"
Stingerrray
Click to expand...
Click to collapse
I do concur, the Philly Cheese Steak is quite delicious, however I find that nothing beats a good Cheeseburger!

Which one is which?
And do they need to be flashed in a specific order?

File one is new. File 2 is the one that has been out for a couple of days. I'm not sure on the install will test soon.

Stingerrray said:
File one is new. File 2 is the one that has been out for a couple of days. I'm not sure on the install will test soon.
Click to expand...
Click to collapse
ill go ahead and test this aswell, so tech i should flash file 2 then file 1 since that is the order they were released in?

Foo_Blyat said:
ill go ahead and test this aswell, so tech i should flash file 2 then file 1 since that is the order they were released in?
Click to expand...
Click to collapse
actually the I believe the first file is the spl and would be flashed first. Be careful.

XfooYen said:
actually the I believe the first file is the spl and would be flashed first. Be careful.
Click to expand...
Click to collapse
i thought file 1 should be flashed first aswell but to me it looked like the 2.2.1 update since theres a "FRG84-from-DMD64" line in the code.
anyone else care to maybe back that assumption up or throw in your own 2 cents, wouldnt mind a few opinions before i flash these files.
Both downloaded, both have been put onto the root of my sdcard. Just waiting on a guiding light before i boot into stock recovery and flash

I also have the files ready but I dont have the guts to flash. I barely use the MT3G lately but I dont want to risk a brick.

negative
Good news is the phone doesn't brick after trying to flash the first file. Bad news is it comes across an error. Apparently this is for a different phone. I got the error "E:Error in /sdcard/update.zip (Status 7)" with a bunch of other gibberish about buildprops before it ..
hope this helps someone ..

has anyone tested these file yet with success?

PulldOvr said:
Good news is the phone doesn't brick after trying to flash the first file. Bad news is it comes across an error. Apparently this is for a different phone. I got the error "E:Error in /sdcard/update.zip (Status 7)" with a bunch of other gibberish about buildprops before it ..
hope this helps someone ..
Click to expand...
Click to collapse
if your sig is correct, you are in the wrong forums, no **** its "apparently for a different phone"

PulldOvr said:
Good news is the phone doesn't brick after trying to flash the first file. Bad news is it comes across an error. Apparently this is for a different phone. I got the error "E:Error in /sdcard/update.zip (Status 7)" with a bunch of other gibberish about buildprops before it ..
hope this helps someone ..
Click to expand...
Click to collapse
I got the same error message and installation aborted. I tried file #2 first. Rebooted and went back to normal. Mytouch 3g stock.....
Same thing happened when I flashed #1 .....

Foo_Blyat said:
if your sig is correct, you are in the wrong forums, no **** its "apparently for a different phone"
Click to expand...
Click to collapse
Before you continue being an ass had you thought about he is someone that upgraded from a mytouch 3g to a vibrant and still has his old mytouch? That is exactly what I did and I am still trying to update my mytouch.

Foo_Blyat said:
if your sig is correct, you are in the wrong forums, no **** its "apparently for a different phone"
Click to expand...
Click to collapse
My Vibrant runs off MT3G roms ...
On a serious note .. I have an original MyTouch 3g, a Cliq, a G1, and a Vibrant ... usually just lurk around these forums and try not to intervene too much because people are quick to become trolls on this site .. then they complain when no one will help them .. gee i wonder why ... learn to be a little nicer, and maybe we can get some work accomplished as a whole ...
and just to clarify, I tested this on an original MyTouch 3g, 1.33.006 SPL, (stock) and unrooted DMD64 build.
This made me think that a "...*** from DMD646" update file would work. I'll be sure to keep my testing to myself so i can avoid trolls like you.

Don't get your panties in a bunch...
I already tried 1.5 -> 2.2.1 and both builds of 1.6 -> 2.2.1, doesn't work in any order

I've tried to update with both files no luck. They are definitly part of the update. I did notice from an earlier post with photos that one file was looking to the system cache file for the other file. So just a thought maybe both files need to be in place before the update can take place. Maybe this could be the problem. Any thoughts on this?
Stingerrray
Sent from my T-Mobile G2 using XDA App

I thought that the first update was supposed to be 300-400kb? Where did you discover this link out of curiosity?

I saw the file name in another post with a view of a botched upgrade due to root. put the file name in the url for the other update and it was a valid url.
Sting
Sent from my T-Mobile G2 using XDA App

The post was here.
http://forum.xda-developers.com/showpost.php?p=8687201&postcount=175

First off any time you want to test if a file is legit or not ( coming from htc/google ) you can just test the keystore via command prompt if the java development kit and runtime is in your system path. Don't remember the code off hand.
Second I would really suggest either using someone elses update script or at least replace/delete most of it. As well as install su and busybox. Because it won't run in a custom recovery.
Enjoy if you can!

[Q] help me please!!!???

so a buddy of mine rooted his wifes eris, and sorta messed up the root, he can get to clockwork mod and all, BUT any rom he tries to flash will say error at line 9 or line 6 not enough space on device, aborting operation....
he also failed to make an nand back up so basically we are stuck in clockwork
someone help! how do we either fix this to flash a rom or unroot/return to stock this device??
we have tryed the RUU method but it doesnt reconize the drvice because we are in clock work
and we have try the pbm img but s=on so were locked out

If s=on then i dont think he got root

Cyostrife said:
If s=on then i dont think he got root
Click to expand...
Click to collapse
he followed the method on theunlockr.com
worked just fine for his eris, but his wifes is giving said errors...
with just bootloader and cwm avalible what can we do to fix this?

mytouchguy said:
he followed the method on theunlockr.com
worked just fine for his eris, but his wifes is giving said errors...
with just bootloader and cwm avalible what can we do to fix this?
Click to expand...
Click to collapse
How full is the battery? I get errors if I try to flash and the battery is ~30% or less.

lp4261 said:
How full is the battery? I get errors if I try to flash and the battery is ~30% or less.
Click to expand...
Click to collapse
not sure, i was doing a remote help, i do alot of rooting for tmo phones ive just never seen this error... i plan to go help him in person just trying to get some advice
will it still charge with no rom? if so ill have him charge it overnight

mytouchguy said:
not sure, i was doing a remote help, i do alot of rooting for tmo phones ive just never seen this error... i plan to go help him in person just trying to get some advice
will it still charge with no rom? if so ill have him charge it overnight
Click to expand...
Click to collapse
I would assume so, but I'm still a novice. I just noticed this from my own experience.

lp4261 said:
I would assume so, but I'm still a novice. I just noticed this from my own experience.
Click to expand...
Click to collapse
what type of errors have you seen?
his says not enough space on device... could this relate the cwm bricking devices?
more so is the device bricked at this point or are we still ok?

mytouchguy said:
what type of errors have you seen?
his says not enough space on device... could this relate the cwm bricking devices?
more so is the device bricked at this point or are we still ok?
Click to expand...
Click to collapse
if u can power the device on , i believe it aint bricked

Can he get to hboot and usb from there. if so let me know and also can he get to recovery...
Sent from my froshedyo using XDA App

mytouchguy said:
what type of errors have you seen?
his says not enough space on device... could this relate the cwm bricking devices?
more so is the device bricked at this point or are we still ok?
Click to expand...
Click to collapse
That sounds like the type of stuff i would get. that or a push file via adb thing. It doesn't sound like a clockwork bricking. The problem with CWM is that it doesn't have the verification step that amon-ra does. Are you flashing roms from these forums? I trust the devs here, but I don't think I would flash a rom that isn't from here w/o a recommendation from one of the devs. I would plug the phone in and let it go for a bit and try again after it has a charge.

lp4261 said:
I would assume so, but I'm still a novice. I just noticed this from my own experience.
Click to expand...
Click to collapse
tazzpatriot said:
if u can power the device on , i believe it aint bricked
Click to expand...
Click to collapse
yes we can power on we can use cwm mod hell we can place a pbmimg on the sd card, it just wont read it because s=on at the time
in doing a massive google search
any chance this would work
http://www.droidforums.net/forum/hacking-help/37717-unroot-unbrick-using-sbf-post-ikithme.html
if not anyone got any ideas?

3 more questions
a: is there a way to get s=off without android loaded, between just the bootloader and cwm avalible? this way we can hopefully just use the pbmimg
B: is there a way to replace cwm with amon ra in this current state to use flashback21? http://forum.xda-developers.com/showthread.php?t=792026
and this is a really crazy thought but can we take the backup we created tonight from his eris... both phones are EXACTLY alike, purchased at the same time and all...and use it to flash in cwm to recover the dead phone?

there is way to flash S=OFF through recovery. Flash the file from here..

In order to use a nandroid from a different phone you need to change a few things to make it work. I read it somewhere. If I find it ill let ya know
Sent from my KaosGingerbread using XDA App

CCCP4ever said:
there is way to flash S=OFF through recovery. Flash the file from here..
Click to expand...
Click to collapse
This is only supposed to work if you have bootloader version 1.49. If you're lucky like me and have 1.47 it won't work. That's according to bftbo. He's tried both.

lp4261 said:
This is only supposed to work if you have bootloader version 1.47. If you're lucky like me and have 1.49 it won't work. That's according to bftbo. He's tried both.
Click to expand...
Click to collapse
ill have this on standby, idk what bootloader he has we kinda gave up for the night

erismaster said:
In order to use a nandroid from a different phone you need to change a few things to make it work. I read it somewhere. If I find it ill let ya know
Sent from my KaosGingerbread using XDA App
Click to expand...
Click to collapse
awesome ill do a little looking myself and see, but thanks. figured it was a crazy but possible idea

mytouchguy said:
ill have this on standby, idk what bootloader he has we kinda gave up for the night
Click to expand...
Click to collapse
here's bftbo's answer to my question:
http://forum.xda-developers.com/showpost.php?p=10501766&postcount=69

within moments i found this...
anyone know how to achive this? both phones in this instance are the droid ERIS
http://androidforums.com/incredible...ansferring-nandroid-backup-another-phone.html

lp4261 said:
here's bftbo's answer to my question:
http://forum.xda-developers.com/showpost.php?p=10501766&postcount=69
Click to expand...
Click to collapse
any way to roll back the bootloader as he mentioned in the event that he has 1.49?
and this is a really stupid question , but im so brain fryed... how do we check his bootloader version?

S.O.S. bricked my Toshiba Thrive need a stock(or rooted) boot.img

I attempted to flash the Motorola Xoom rooted boot.img on my Thrive.
It didn't work.
I have been unable to find a stock(or rooted) version of the Thrive boot.img so I can unbrick my device.
Can someone please
1.Provide a working boot.img
or
2.Instruct me on how to extract it from an intact Thrive?
I guess its safe to assume anyone working on rooting would have a copy of it
I would really appreciate the help!
Edit: I have been looking for hours for information on how to extract the boot.img from a device like this and have been having no luck.

Can someone please help me?
I realize what I did was idiotic...
I'll never mess with anything that says "boot" again unless I really know what I'm doing.

This is why we need a dev forum!

someone with a working thrive please try this.
mmcblk0p11 is the boot partition of the atrix 4g
please replace mmcblk0p11 with the boot partition mount point of the toshiba thrive.
adb shell
su
dd if=/dev/block/mmcblk0p11 of=/mnt/sdcard-ext/boot.img
then post your boot.img here please

In the meantime, I'm getting a call back from level 2 tech Toshiba support in an hour. Trying to convince them to give me a copy of the recent firmware update. So "I can see what they changed, as there was no changelog".
Odds I succeed?

what is the exact model of the thrive?

Toshiba AT105-T1032
P/N PDA01U-00501F

lol while your at it ask for the sbk

joe ferreira said:
lol while your at it ask for the sbk
Click to expand...
Click to collapse
Hah, that would definitely make for a quick and easy root for the masses using stock recovery wouldn't it?

joe ferreira said:
someone with a working thrive please try this.
mmcblk0p11 is the boot partition of the atrix 4g
please replace mmcblk0p11 with the boot partition mount point of the toshiba thrive.
adb shell
su
dd if=/dev/block/mmcblk0p11 of=/mnt/sdcard-ext/boot.img
then post your boot.img here please
Click to expand...
Click to collapse
Someone tried this over at Thriveforums.org
here's what they said
""su" ? no root ... I get "su: permission denied""

Well, 2nd level tech support never called me back. Called back tech support and they PROMISED they'd call me back this time, in 2-3 hours.
Here's hoping this lands us an OTA update file

Natolx said:
Someone tried this over at Thriveforums.org
here's what they said
""su" ? no root ... I get "su: permission denied""
Click to expand...
Click to collapse
try superoneclick first
http://forum.xda-developers.com/showthread.php?t=803682

Natolx said:
Hah, that would definitely make for a quick and easy root for the masses using stock recovery wouldn't it?
Click to expand...
Click to collapse
I heard that the thrive comes with a unlocked bootloader?
The sbk is the boot loader and has nothing to do with root access.
with a unlocked bootloader we can root the thrive with the same fastboot flash preinstall process as the atrix.
has anyone figured out how to get to the menu for android recovery, fastboot, etc?

btw root is a part of the system.img not the boot.img
boot.img is the kernel

joe ferreira said:
I heard that the thrive comes with a unlocked bootloader?
The sbk is the boot loader and has nothing to do with root access.
with a unlocked bootloader we can root the thrive with the same fastboot flash preinstall process as the atrix.
has anyone figured out how to get to the menu for android recovery, fastboot, etc?
Click to expand...
Click to collapse
yes, that's how I bricked my tablet, by using fastboot to flash a xoom rootboot.img. Fastboot and recovery are available from simple menu by holding down power and volume up when booting up.
The fastboot is completely unlocked from the factory, you don't even have to issue an unlock command.

Did you take a look at android-dls wiki site they've got tut's for extracting the kernel, if you have access to a working thrive. I used it to retrieve my friend's phone's kernel after bricking mine during one of my first root attempts ever.
I will be getting the thrive soon (Cant wait) and will be attempting to extract the kernel out of the machine. I'll post it soon as I get it, seems to be in high demand right now. Glad to hear the bootloader comes unlocked out of the box. Hopefully you can get yours back up and running.

D3MN5PWN said:
Did you take a look at android-dls wiki site they've got tut's for extracting the kernel, if you have access to a working thrive. I used it to retrieve my friend's phone's kernel after bricking mine during one of my first root attempts ever.
I will be getting the thrive soon (Cant wait) and will be attempting to extract the kernel out of the machine. I'll post it soon as I get it, seems to be in high demand right now. Glad to hear the bootloader comes unlocked out of the box. Hopefully you can get yours back up and running.
Click to expand...
Click to collapse
Which tutorial, this one? Its the only related one I've been able to find and it doesn't mention how to pull the kernel off the device itself.
http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
Also, when are you expecting your Thrive? I have a feeling you are the only one working on this :/

Natolx said:
Which tutorial, this one? Its the only related one I've been able to find and it doesn't mention how to pull the kernel off the device itself.
Also, when are you expecting your Thrive? I have a feeling you are the only one working on this :/
Click to expand...
Click to collapse
Wed. Thurs at the latest... Well we need to get developers working on these things. I sense huge potential in this device, as I'm sure everyone else who has half a brain and picked it up did as well.
Is you recovery.img shot? or did you back it up at all? Normally you need someone to release the source for a .zip to appear even one for the stock rom. Google's taking its sweet time releasing the source codes. 3.0 was obtained through asus or was it acer... always get those two mixed up... after all. I think we may have to cool our heels till icecream comes out for developers to start doing their thing (or some big to release the source code).

D3MN5PWN said:
Wed. Thurs at the latest... Well we need to get developers working on these things. I sense huge potential in this device, as I'm sure everyone else who has half a brain and picked it up did as well.
Is you recovery.img shot? or did you back it up at all? Normally you need someone to release the source for a .zip to appear even one for the stock rom. Google's taking its sweet time releasing the source codes. 3.0 was obtained through asus or was it acer... always get those two mixed up... after all. I think we may have to cool our heels till icecream comes out for developers to start doing their thing (or some big to release the source code).
Click to expand...
Click to collapse
My recovery is fine, its just the kernel.
My level 2 tech support discussion was a mixed bag. The guy essentially said it was extremely odd that the firmware update wasn't on the website and that they hadn't even heard about it. He sent an e-mail out to his entire department to find out what's going on. Hopefully that gets sent up the pipeline and it shows up under thrive downloads on the support website.

joe ferreira said:
try superoneclick first
http://forum.xda-developers.com/showthread.php?t=803682
Click to expand...
Click to collapse
Looks like none of the oneclick roots work, someone on thriveforums posted this in response to my request.
"Sorry, I tried both the gingerbreak and psneuter versioins, neither worked.
Oh, and I also ran the "Check Drivers" and it said no issue found.
Also found z4root on theunlockr.com and tried it, appears to have hung up my Thrive."