Related
http://img27.imageshack.us/img27/2034/img20101102213315.jpg
Here is the picture of the 2.02 S-OFFed
It has a custom recovery on it now. More info to come.
If this has been figured out already sorry again!
!!!UPDATE!!!
Whats Completed,
S-OFF
Custom Recovery
ENG Bootloader.
HBOOT 2.02.0000 is completely cracked.
Advantage of hboot 2.02 > 0.76?
[email protected] said:
Advantage of hboot 2.02 > 0.76?
Click to expand...
Click to collapse
THIS !!!!!!!! >
2.02 is non engineering hboot... so i would think there is not much point... but than again... i think probably 99% of us dont even touch those options.
Uh nothing that i know of, except that HBOOT 2.02 that i have found will NOT downgrade to .76 as they patched it, I tried the eng-PC36IMG.zip, unrevoked etc. They do not root, nand unlock and install recovery.
eng-PC36IMG.zip skips installing the bootloader wich is the HBOOT.
Unrevoked Errors out and will not get past the HBOOT and throws a error saying lost connection.
So far can not downgrade the stupid hboot. This is what happens.
http://img215.imageshack.us/img215/1126/img20101102215418.jpg
amoamare said:
http://img27.imageshack.us/img27/2034/img20101102213315.jpg
Here is the picture of the 2.02 S-OFFed
It has a custom recovery on it now. More info to come.
If this has been figured out already sorry again!
Click to expand...
Click to collapse
How did you get s off? Ive been trying everything for the past week
You cant downgrade as of yet to HBoot 76.
You can get S-Offed as of now that lets you install a custom recovery etc.
amoamare said:
You cant downgrade as of yet to HBoot 76.
You can get S-Offed as of now that lets you install a custom recovery etc.
Click to expand...
Click to collapse
How did you do it?
Hex edit? Cough cough.
Like i said, more info will be released in a bit. I'm waiting for a response from someone.
kenny21 said:
How did you get s off? Ive been trying everything for the past week
Click to expand...
Click to collapse
If you have s-off then you should be able to make a PC36IMG.zip out of one of these hboots found here http://forum.xda-developers.com/showthread.php?t=801568
It will flash the PC36IMG.zip just fine, but its bypassing the boot everytime.
amoamare said:
It will flash the PC36IMG.zip just fine, but its bypassing the boot everytime.
Click to expand...
Click to collapse
so, will this fix let us root the phone and load recovery and flash roms again? im so tired of being stock lol.
Yes, right now i have ClockworkMod recovery on it.
You can flash custom roms to the phone.
Only thing is i want to put the eng0.79 bootloader on there
amoamare said:
Yes, right now i have ClockworkMod recovery on it.
You can flash custom roms to the phone.
Only thing is i want to put the eng0.79 bootloader on there
Click to expand...
Click to collapse
could we have an ETA on your fix? i would love to try it before i go to sleep ;(
Like i said just waiting on a message from someone and will post from there.
amoamare said:
Like i said just waiting on a message from someone and will post from there.
Click to expand...
Click to collapse
Thanks for the effort. I bought an Evo today with 2.02 Hboot on it. I was afraid to be stuck with stock for a long time.
Ok 2.02 has been successfully cracked all the way.
http://d.imagehost.org/0355/IMG_20101102_233241.jpg
ENG bootloader has been loaded on. All fastboot cmds are restored. Sweet.
My phone was made s-off via xtc clip.
It's rooted with superoneclick (couldn't get unrevoked to work).
ROM Manager is in the superuser list and has been granted root access.
In ROM Manager I click "flash clockworkmod recovery", select "HTC Buzz (Wildfire)" and it says "successfully downloaded clockworkmod recovery".
But every time I click "reboot into recovery" I just get a black screen with a phone in the middle and a red triangle.
I then have to remove the battery to get the phone back on.
Any ideas folks ?
I read somewhere that the current version of ROM manager doesn't work with Android 2.2.
Is this right ?
I tried an older version and it appeared to try and install clockwork recovery for a few seconds then I got a black screen with a phone and a red question mark.
try flashing custom recovery with PC49IMG process. get the file from here.
http://forum.xda-developers.com/showpost.php?p=12188132&postcount=15
and one more thing, if u get issues with flashing custom roms then try to use different version of recovery.
issues like amend scripting.......
Thanks for the reply.
I tried putting the PC49IMG.zip file in the root of the sd card but when I go into HBOOT it says ....
CID incorrect !
Update Fail !
Do I need to do a factory reset ?
scobodon said:
Thanks for the reply.
I tried putting the PC49IMG.zip file in the root of the sd card but when I go into HBOOT it says ....
CID incorrect !
Update Fail !
Do I need to do a factory reset ?
Click to expand...
Click to collapse
CID error after making S-OFF huh ?
U do have another option. Can try an official RUU of ur region with the radio Radio_13.53.55.24H_3.35.19.25
this gives u hboot 0.80 . Then u can root the phone with unrevoked (use version 3.2).
Would this be ok ?
http://rom.tat.tw/wildfire/extracte...19.25_release_151892_signed_101410_003737.zip
scobodon said:
Would this be ok ?
http://rom.tat.tw/wildfire/extracte...19.25_release_151892_signed_101410_003737.zip
Click to expand...
Click to collapse
The one specific for ur region (if it is there) is more preferable. However it will also be ok.
And better get it from shipped roms website if u havent started the download yet.
here: http://www.shipped-roms.org/shipped/Buzz/
Thanks for the list.
So, is it just a case of running the exe with my phone connected ?
scobodon said:
Thanks for the list.
So, is it just a case of running the exe with my phone connected ?
Click to expand...
Click to collapse
Yes certainly. Connect the phone under charge mode.
No luck.
Got a "customer id error" in the Windows program.
scobodon said:
No luck.
Got a "customer id error" in the Windows program.
Click to expand...
Click to collapse
Sorry, cant go further. That might be due to region. I think there might be ur region RUU in that website there. Don't know completely to solve cid errors. Probably a gold card might be the solution.
But there are solutions for cid errors. Go with this thread (same one as earlier), it might help u. http://forum.xda-developers.com/showthread.php?t=993102
Thanks again for all your help so far, much appreciated.
I found a multi region RUU with the same kernel as the one I'm on.
Do you think flashing this will allow me to then flash one of the older RUUs ?
Also, if I do this will it make my phone s-on again ?
scobodon said:
Thanks again for all your help so far, much appreciated.
I found a multi region RUU with the same kernel as the one I'm on.
Do you think flashing this will allow me to then flash one of the older RUUs ?
Also, if I do this will it make my phone s-on again ?
Click to expand...
Click to collapse
When ur phone has S-OFF (by xtc clip) u can flash any wildfire RUU of ur region (i mean downgrading hboot is also possible). Yes u can flash older RUU also, that's what u attempted to do with that WWE ruu.
Once u do S-OFF by xtc clip, then u can't get back to S-ON in any way. XTC clip directly wipes off the secure flag in the radio NVRAM. So, AFAIK, there is no way for u (by xtc clip) to get back to S-ON even when u flash an updated hboot.
But alpharev2 (not yet released for wildfire) will patch the hboot to make it think that the secure flag is off. So, if done by alpharev S-OFF is not permanent. When done S-OFF with alpharev, then if u flash an updated hboot, the phone returns to S-ON. This is not the case with u.
Tried the RUU with the same kernel that's on my phone but got the "customer ID error" again.
I'm starting to think something went wrong when they used the xtc clip.
When I get the red triangle in HBOOT, if I press vol up + power I get the message "failed to verify signature".
I thought having s-off was supposed to bypass the signature checks
scobodon said:
Tried the RUU with the same kernel that's on my phone but got the "customer ID error" again.
I'm starting to think something went wrong when they used the xtc clip.
When I get the red triangle in HBOOT, if I press vol up + power I get the message "failed to verify signature".
I thought having s-off was supposed to bypass the signature checks
Click to expand...
Click to collapse
AFAIK, after S-OFF it should skip the signature check. That is how we can flash the custom recovery through PC49IMG process.
There is a full guide of XTC clip rooting in the development section. If u think something went wrong when they used xtc clip, u might get an answer there. link: http://forum.xda-developers.com/showthread.php?t=1057524
And also one more link to what we can do after S-OFF here.
link: http://forum.xda-developers.com/showpost.php?p=13025129&postcount=3
In that try the fastboot flash recovery command. May be a hope
Woo hoo, success !!
I made a goldcard and the RUU installed fine.
I now have Android 2.1 and HBOOT 0.80.0007.
I guess the goldcard is where I was going wrong.
Edit : Just got unrevoked to work first time too.
And now I've got CM7 installed !!!
A very happy bunny.
Many thanks again for the help and advice.
Wouldn't have got it working without this forum.
That's fine.
Sent from my HTC Wildfire using XDA App
Posting this to get it out in the community for anyone who wants it. This is the shipping hboot 1.04 patched to give s-off identical to the current ENG hboot everyone is using as well as including the ENG commands and fastboot flash/erase support. Obviously if you have a perfectly running device there might be no reason to flash this. For those who are yet to flash a hboot you might choose this instead since it's newer and we don't know what flaws could have been fixed from the older ENG release.
This will likely accompany our official root release for the device when we finish it.
I have tested this to be working on my phone, as well as another developers device so it should be safe. You however take full responsibility for anything that goes wrong with this flash as with any aftermarket mod.
IMPORTANT NOTE:
For those not aware, the thunderbolt is not a true s-off device. The ENG hboot or this patched hboot give you fake s-off while the radio is screaming s-on... This doesn't mean much, but DO NOT flash a hboot that isn't patched or you'll be stuck.
UPDATE 8/1/2011: This has been updated to now block normal hboot flashing to make it much safer. It's still wise to not arbitrarily flash things but you should rest a little more at ease now.
Thread update (not a new version):
Here is the commands to re-flash hboot after installing this:
"fastboot oem mw 8d08ac54 1 31302E30"
"fastboot flash hboot whateverhbootfile.nb0"
where whateverhbootfile.nb0 is in your path, you can get this file by unzipping the PG05IMG.zip with a hboot in it
(BE CAREFUL WITH THIS, YOUR PHONE WILL FLASH TETRIS.EXE AS A BOOTLOADER IF YOU ASK IT TO)
Enjoy.
Sweet thanks
Sent from my ADR6400L using XDA Premium App
Thank you sir, I shall try this soon.
This is not newer than the ENG, its actually the same version number. The ENG one came from a 1.12.605.6 eng ruu (same as shipping)
Will this block hboot flashing like the alpharevx one (please say yes)
Shadowmite said:
Posting this to get it out in the community for anyone who wants it. This is the shipping hboot 1.04 patched to give s-off identical to the current ENG hboot everyone is using as well as including the ENG commands and fastboot flash/erase support. Obviously if you have a perfectly running device there might be no reason to flash this. For those who are yet to flash a hboot you might choose this instead since it's newer and we don't know what flaws could have been fixed from the older ENG release.
This will likely accompany our official root release for the device when we finish it.
I have tested this to be working on my phone, as well as another developers device so it should be safe. You however take full responsibility for anything that goes wrong with this flash as with any aftermarket mod.
IMPORTANT NOTE:
For those not aware, the thunderbolt is not a true s-off device. The ENG hboot or this patched hboot give you fake s-off while the radio is screaming s-on... This doesn't mean much, but DO NOT flash a hboot that isn't patched or you'll be stuck.
Enjoy.
Click to expand...
Click to collapse
Ah, I guess I was under the impression it was older from what I was told. Regardless I never ran that one. Currently it doesnt block hboot flash, but I'll look into that patch next. I guess we'd want to block hboot from zip files but not from fastboot flash in order to protect soff while still having a way to return to stock.
Shadowmite said:
Ah, I guess I was under the impression it was older from what I was told. Regardless I never ran that one. Currently it doesnt block hboot flash, but I'll look into that patch next. I guess we'd want to block hboot from zip files but not from fastboot flash in order to protect soff while still having a way to return to stock.
Click to expand...
Click to collapse
I ended up not releasing the older one, as I had both (im not sure if joshua was given both or not).
Once you add blocking hboot flash (artificially high version number does it i think??) would it be ok to place in my guide until (if/when) yall release a package? (I intend to remove mine once a reliable "auto" is out).
Flashed for fun and it works great.
Having another method of root may not mean much to Tbolt owners now but it will once devices start shipping with GB.
Great to have you guys working on this.
so this a a way to root in the future for GB owners? just want to make sure so i dont flash if i dont need to because i am already rooted
Shadowmite said:
Ah, I guess I was under the impression it was older from what I was told. Regardless I never ran that one. Currently it doesnt block hboot flash, but I'll look into that patch next. I guess we'd want to block hboot from zip files but not from fastboot flash in order to protect soff while still having a way to return to stock.
Click to expand...
Click to collapse
excellent! i personally would love a permanent s-off patch. ill be watching this thread,thank you kind sir.
thanks,Shadowmite
Shadowmite said:
Posting this to get it out in the community for anyone who wants it. This is the shipping hboot 1.04 patched to give s-off identical to the current ENG hboot everyone is using as well as including the ENG commands and fastboot flash/erase support. Obviously if you have a perfectly running device there might be no reason to flash this. For those who are yet to flash a hboot you might choose this instead since it's newer and we don't know what flaws could have been fixed from the older ENG release.
This will likely accompany our official root release for the device when we finish it.
I have tested this to be working on my phone, as well as another developers device so it should be safe. You however take full responsibility for anything that goes wrong with this flash as with any aftermarket mod.
IMPORTANT NOTE:
For those not aware, the thunderbolt is not a true s-off device. The ENG hboot or this patched hboot give you fake s-off while the radio is screaming s-on... This doesn't mean much, but DO NOT flash a hboot that isn't patched or you'll be stuck.
Enjoy.
Click to expand...
Click to collapse
Hey,
Might you guys post your IDB of this hboot? or send it to me via PM? or somehow. Id love to see the breakdown of the file you guys reversed.
and what patches. Thanks!
Thanks shadowmite. I followed your work way back in the 6600 days...
Sent from my ADR6400L using Tapatalk
running it now,no issues. used it to flash a recovery,and change my radios. also verified it has the same available fastboot commands.
feel free let me know if you need any kind of feedback,or help with testing. id be more thaN happy to help test a permanent patch
Ok, updated main post with new updated hboot. Now patched to block normal hboot flashes which should make it a lot safer. To test, flash the update, then try flashing it again. The second one should not take.
yes! thank you kind sir. so,if im understanding correctly,it will prevent the flash of any other hboot,including the original engineering one?
downloaded and about to flash
scotty1223 said:
yes! thank you kind sir. so,if im understanding correctly,it will prevent the flash of any other hboot,including the original engineering one?
downloaded and about to flash
Click to expand...
Click to collapse
Correct. I figure eventually someone might need to flash back to a original and ill eventually toss up instructions how to do this. For now, this should block everything we've seen for the device to date.
Is revolutionary working on root for the thunderbolt? Will it give us true s-off?
from the first post,no it will not give us true s-off. im running it now,tried flashing the stock s-on hboot and the old eng hboot and it blocked them both
next question: if one installed a stock recovery,and accepted an OTA... would this prevent hboot from being overwritten there as well?
Yes it should always block hboot unless they do something purposeful to overcome the block method. I'll post a command in the first post sometime next week that will allow you to overwrite hboot should you want to.
NO LONGER TAKING Q'S. HAVE MOVED TO X8 FORUM!! HI everyone. i have started this thread as i didnt know what to do when i first had to send my wildfire back for repairs. first download the attatched zip. unzip to desktop and make sure u have got the drivers for your bootloader interface already installed. to do this you will need just two things. the zip you have just downloaded and the HBOOT which i included inside the ziped file. once extracted run the java file named S-ON.jar and plug your phone in and turn on fastboot. once connected make sure you click on check connection. once you have done that you should see your serial number appear. okay your ready to go. look for the first tab and click on it. then click on HBOOT/SPL. locate the HBOOT file you inzipped with the S-ON tool and then click it. once done just click on flash HBOOT/SPL. once done you will see it says FLASH HBOOT/SPL/SUCCESS. thanks for takuing time to look at my GUIDE and i hope it helps you. just remember one thing only flash the new HBOOT after you have installed the RUU which is android 2.2.1 so you can root again. and remember you can also get S-OFF again the exact same way
BEFORE you attempt to flash new HBOOT to gain s-on. please click start on your pc then goto run then in the dialog box type CMD. then you will have a pop-up it will be your command promt. in the command promt type
C:\fastboot>fastboot oem mb 9C068490 1 30 then hit enter. then open the s-on tool and flash the new HBOOT. then it will flash without FAIL. sorry for not realising this earlyer. and happy flashing.
comment if you need the bootloader drivers and i will upload them if requested thanks again everyone. and i would like to thank the acctuall creator of the programme thanks again briliant work on all sides.
i wil try it my Wildfire
here are the bootloader interface drivers..
enjoy thank me if this method helped you in your Quest to gain s-on
Did it worked for someone? I need to S-ON my wildfire, because i want to sell it
Edit: The WinRun.bat and LinuxRun.sh are wrong. They call the FastbootCommanderV.1.5.jar file, but they should call S-ON.jar
Question: What is eng hboot in your warning when the programm starts? I have the AlphaRev hboot 6.01.1002, will it work?
yesw i have done it on 5 diff wildfires i GUARENTEE it works mate hit me up on my thanks button
like i said this is not my programme i just found it very usefull to gain s-on. the only other way apart from this is to do it via the command promt on windows. which sucks as only a few people acctually know how to use this method. you dont need any of the linux stuff or win.bat. this method is for windows users only
For windows users only !!
this will only work on windows. wilol not work on linux. i am trying to get the programme to work on linux but to no avail. i will keep on trying but its just not capable of doing it. also please do NOT rename the HBOOT.NbO file if you do rename it then it will not flash and will not work.
i tried it, but when i will flash the hboot, i get this error:
Flashing "hboot" - PLEASE WAIT.
"hboot" flash FAILURE.
The device shows me: not roll back hboot version
DO NOT rename the file.
if you rename the file you will get a error. also make sure u have put your phone back to the stock RUU that is android 2.2.1 BEFORE you try this method
These are the RUU you need
go to this site and download the RUU that is used for your phone okay. go to this link and download the one for your phone. http://shipped-roms.com/index.php?category=android&model=Buzz
i have done this. my phone has 2.2.1 stock and i did not rename the file.
I think, i cant flash the hboot, because the alpharevx hbootversion is higher than the stock hboot...i think i read it somewhere...
no thats wrong the other way it to push it to the phone using fastboot and windows command prompt. this is the only 2 ways of gaining s-on again. trust me i have done it on my wildfire and 5 others and worked 1st time everytime
i will be shortly taking a video of me using this programme to gain s-on then you will all be able to see it working. it will not be untill my partner gets home but asoon as its uploaded i will share the url and let you all see that this way works 100% it is maybe somthing you are doing wrong ???? have you unzipped it to a sub fol;der on your desktop ????? and did you run it as admin ?? and if yes to them both. did you 1.rename the HBOOT file ?? or 2. did you move it out of the unzipped folder ???/
i trust you, but it get an error xD
edit: yes...i am an informatic specialist..i should know, what i should do and not..
lol. i dont know what to suggest then. it is odd because it has work flawlessly everythime i have flashed HBOOT/SPL. hmm i dont know then. i have done this method over 15 times to my own wildfire just to make sure it work 100% and could be used by other people. it has worked with alpharevx HBOOT and revelutionarys HBOOT which are both 6.01.1002 so its really weird it never worked for you :S
Strange...
An idea: I have the hboot from alpharevx from a very early closed irc beta. maybe this hboot is in some way locked. Can i flash the hboot with revolutionary again and use your tool? maybe the revolutionary hboot is different to the early closed irc beta :/
aslong as you know what your doing yes. it is possible. if you can get the revelutionary HBOOT then it will flash. then you should be able to flash the s-on HBOOT no problem
revolutionary dont let me flash their hboot -.- they say, i already s-off, so no flash needed -.-
ah i see, you said "if i can get the revolutionary hboot"...yep, i dont think, i can get the hboot
do you know the commands for flash the hboot manually?
do you know how to use command promt in windows ????
cant believe im posting this but here it goes.
couple days ago i had a working phone(mytouch 3g us) running on yoshi rom. now i cant even get into recovery. pwr+home. but able to fastboot.
I had sapphire PVT 32B ship s-on g
HBOOT- 1.33.0013d (sapp30000)
cpld-10
radio 2.22.27.08
oct 21 2009
so i was able to get S-OFF and install eng rom 2005
Now **** hit the fan. Since i couldn't get into recovery i was able to use fastboot commander. tried to fix what i did and now this is what i have 3 days later of trying to get it back to normal. Failure sums it up!!
sapphire PVT 32A ship s-on g
HBOOT- 1.33.0013d (sapp30000)
cpld-10
radio- 6.35.16.19
oct 21 2009
I get into fast boot and i cant even update anything. i try and it says check signature failed. What ever nbh file i put on the phone it gets stuck on updating radio, bar is almost filled to the top but sits there forever, till batter dies.
Any help would be great thanks in advance
Omg. Why did you flash inappropriate radio? Only magics 32a are compatible with 6.35.xx.xx
You can try flash ruu 2.53.707.2 from my library: http://forum.xda-developers.com/showthread.php?p=6109097 (requires goldcard)
It has eng hboot and you will able to restore 32b combo next step, but chances are so small...
P.s. If you will have success with 2.53.707.2, then I will write next step. Do not do fast actions.
Sent from my A7-040 using Tapatalk
This issue has been answered multiple times, and I personally have spent many hours solving and documenting the issue.
Do a search and you will conquer :0)
hey i tried that ruu it gave me wrong id for the phone..
since i have the tmobile i tried 54) 3.12.531.1 T-Mobile USA FRG83D
and been waiting for the radio to update been its updating at 55%
what other ruu can i try?
Mum i tried a search any hints as to what ot search for specifically via your user name
thanks
mumilover said:
This issue has been answered multiple times, and I personally have spent many hours solving and documenting the issue.
Do a search and you will conquer :0)
Click to expand...
Click to collapse
i found some of your posts i cannot adb at all only fast boot. i installed the adb drivers and could never get adb devices to list anything. only fastboot devices worked.
i even tried the above ruu posted and now im stuck in ruu
what is on your screen now? ruu mode?
kayelzhl said:
what is on your screen now? ruu mode?
Click to expand...
Click to collapse
yess can you say paper weight!?!! haaha
check your pm
Has this story success?
5[Strogino] said:
Has this story success?
Click to expand...
Click to collapse
no. unable to create gold card and still stuck in ruu. guess the phone is a gonner
tlipur said:
no. unable to create gold card
Click to expand...
Click to collapse
You can create goldcard with any HTC phone. Ask friends, neighbors. This operation is safe. You need insert your own sdcard to friend's phone, read cid, generate goldcard image and paste it onto your sdcard.
5[Strogino] said:
You can create goldcard with any HTC phone. Ask friends, neighbors. This operation is safe. You need insert your own sdcard to friend's phone, read cid, generate goldcard image and paste it onto your sdcard.
Click to expand...
Click to collapse
What really was not aware thought it would have to be done by the same make model phone.
Ok ill try to make a gold card have a droid incredible that i can use.
After i make the gold card what would i need to do next? Im still stuck in ruu with a chip at the bottem with a circle and line going through it.
Thanks
tlipur said:
What really was not aware thought it would have to be done by the same make model phone.
Ok ill try to make a gold card have a droid incredible that i can use.
After i make the gold card what would i need to do next? Im still stuck in ruu with a chip at the bottem with a circle and line going through it.
Thanks
Click to expand...
Click to collapse
make a gold card, use the guide one the page "htcdev",(i cant post address) it will kick your phone out of RUU, if you are lucky enough to have a custom recovery before you got into this problem, then you can bring your phone back to life. btw, i have a magic 32A and stucked in the ruu before.
kayelzhl said:
make a gold card, use the guide one the page "htcdev",(i cant post address) it will kick your phone out of RUU, if you are lucky enough to have a custom recovery before you got into this problem, then you can bring your phone back to life. btw, i have a magic 32A and stucked in the ruu before.
Click to expand...
Click to collapse
Whenyou say guide is it for making the gold card or to get out of ruu? If its a guide for the gold card I'm going to use the one posted on addictive tips. Gold card made what's the next step?
How long did it take you to get it out of ruu ?
Mmm... http://forum.xda-developers.com/showpost.php?p=23599950&postcount=2
tlipur said:
Whenyou say guide is it for making the gold card or to get out of ruu? If its a guide for the gold card I'm going to use the one posted on addictive tips. Gold card made what's the next step?
How long did it take you to get it out of ruu ?
Click to expand...
Click to collapse
no, gold card is easy to make when you have an android device, the guide i mean is how to kick your phone out of ruu, which may need a gold card. so before you do the guide on htcdev, make the gold card first. since i cant post address here, i will pm it to you about the guide.
5[Strogino] said:
Mmm... http://forum.xda-developers.com/showpost.php?p=23599950&postcount=2
Click to expand...
Click to collapse
heya i tried running the ruu and it not able to find my phone. im able to fastboot devices and get it listed. i tried running it before the first time and i think it picked it up. i ran the tmobile one just to see if it picks it up and it did.
im going to try another pc real quick; Ok tried the other pc same result, t mobile ruu picked it up.
Went back to 1st pc uninstalled all driver programs related to phone. cleaned out registry and temp.
Checked with USBDeview, non listed. installed drivers that are from sdk tools, android bootloader interface.
ran it again still dident pick it up but tmoible ruu again picked it up.
So its. Gonner then eh?
0. Go into fastboot mode
1. Check connection by command
Code:
fastboot devices
It should return serial number
2. Run RUU 2.53.707.2
3. Navigate to windows temporary directory and search for rom.zip
4. Check twice that is 2.53.707.2 archive (you can unpack files and view hboot via notepad, you will see something like 1.33.2010 ENG S-OFF)
5. Copy rom.zip into folder with fastboot.exe (from Android SDK Tools), close RUU
6. Run
Code:
fastboot flash zip rom.zip
Just gave it a shot it passed sig, header,info then stopped at checking model id
Remote 41 model id check fail.
I used gold card tool 0.0.5 to get cid then went to rev skils dl the image and used the same prog to create the gold card via patch mmc.