Database Users

Seeking advice rooting MyTouch 1.2 (HTC Magic 32a)

Hello all, thank you for this great resource and any insight you can provide.
I need some of your wisdom, as I've been banging my head against a brick wall for about two weeks now, trying to root my T-Mobile MyTouch 1.2 (HTC Magic) with the 3.5" jack.
I did a couple hours of homework and began the process, but currently am stuck at the HTC Magic splash screen on normal boot up. I cannot boot into recovery; I have tried flashing both the Amon Ra versions, H and G. I can, however, boot into hboot and fastboot menu options, so it my understanding that my phone is salvageable with the right tools and process. Unfortunately, I was given bad advice—or incorrectly followed good advice—and now all the instructions I find to restore functionality to my phone don't go smoothly.
I've spent countless hours trying proposed found threads here (mostly) and other resources, but while the solutions sound like the apply to my hardware, they fail to complete successfully.
I have created two goldcards, both appear to work, as I have been able to flash a sappimg.zip image initially, but currently trying to flash again to remedy problems hangs and requires me to pull the battery. It usually hangs at the initial unzipping or at updating radio_v2. Via fastboot, I have been able to flash the stock hboot.nbo and reflash different versions. I was able to flash to the stock radio once, but have had problems trying to reflash images, trying to correct the issue.
These details have read different things at different stages in trying proposed solutions, but currently the info on fastboot menu reads:
SAPPHIRE UNKNOWN 32A SHIP S-ON H
HBOOT-1.33.0009 (SAPP31000)
CPLD-13
RADIO-6.35.10.18
At this moment, I've stopped trying to find answers on the forum because I've spent countless hours failing and more importantly, fear that if I continue applying incorrect solutions, I will irreversibly damage my phone. I hope that someone can provide some advice tailored to my situation.
Thank you for reading and for your reply. I understand that any advice I receive is at my own risk to follow.

Option one: flash the .nbo file for te engineerings 1.33.2010 spl and thz flash the g recovery.
Option two: flash the sappimg to revert back to stock then stsrt all over again
Option three: flash the stock sappimg and stay at stock thanking jesus you didnt **** anything up.
Sent from my HTC Magic using XDA App

You did not read the mytouch 1.2 rooting guide correctly. This phone can only run stock spl and radio. Read the guide at the unlockr. After using the goldcard you should have flashed stock spl and radio using fastboot.

NetrixTardis said:
You did not read the mytouch 1.2 rooting guide correctly. This phone can only run stock spl and radio. Read the guide at the unlockr. After using the goldcard you should have flashed stock spl and radio using fastboot.
Click to expand...
Click to collapse
I tried the files and process indicated on Unlockr several times. The files and process located here: theunlockr.com/2010/03/11/how-to-root-the-mytouch-1-2-and-fender-mytouch/
Attempting again, just now, I run into the same roadblock as reported in my initial post: Immediately after clicking the action button to execute the update, the process hangs at 'Unzipping' on step [1] SYSTEM, where the progress bar never moves, and pulling the battery is the only thing that works (unfortunately, since I'm warned not to power off the device!).

knny1491 said:
Option one: flash the .nbo file for te engineerings 1.33.2010 spl and thz flash the g recovery.
Click to expand...
Click to collapse
Thank you so much for your response.
Attempting option 1, I get the following messaging in the terminal while trying to flash the hboot.img (not nb0, is this wrong?) downloaded from the 'Magic SPL HBOOT collection' thread located here: forum.xda-developers.com/showthread.php?t=529019
sending 'hboot' (512 KB)... OKAY
writing 'hboot'... INFOsignature checking...
FAILED (remote: signature verify fail)
In the previous reply to another helpful commenter I describe another error I get while attempting to update the sappimg provided by Unlockr.
Further insight is very much appreciated.

so this is the second time I'm seeing this exact problem... this is keeping me from rooting this mytouch. but last time i saw this problem I believe it was solved.. i can't remember where i saw it though! I'll look and look until i find it then i'll post it here!
but in the mean time you can try unrooting it until the problem is solved?
http://forum.xda-developers.com/showthread.php?t=665814

lbsk8addict said:
last time i saw this problem I believe it was solved.. i can't remember where i saw it though! I'll look and look until i find it then i'll post it here!
Click to expand...
Click to collapse
Thank you! I hope that you do.
lbsk8addict said:
but in the mean time you can try unrooting it until the problem is solved?
forum.xda-developers.com/showthread.php?t=665814
Click to expand...
Click to collapse
I've visited that thread before in my days of lurking, but didn't attempt it (I don't think—I've tried so many things, it's hard to remember fully at this point).
I think all I have right now are goldcards. I hope a stock SD card isn't needed, or I'll have to figure out how to restore a Kingston microSD or buy another.
Thanks again for all of your input.

lbsk8addict said:
but in the mean time you can try unrooting it until the problem is solved?
forum.xda-developers.com/showthread.php?t=665814
Click to expand...
Click to collapse
Follow up, attempting to update to MT3G 1.2 Sappimg (BUILD# 2.10.531.4) downloaded via that link, I encounter the second error documented in my initial post, the update process hangs at updating step [2] RADIO_V2. The red progress bar stops at about 95%. Pulling the battery out is the only way to escape.
I think, and this is just a gut-level guess, that my problem stems from a corrupt radio version. Any one have an opinion or advice about that?
After pulling the battery and booting back into fastboot, my versioning reads as follows:
SAPPHIRE PVT 32A SHIP S-ON G
HBOOT-1.33.0013 (SAPP31000)
CPLD-13
RADIO 6.35.10.18

You have a 32a radio with a 32b spl, during the root process you are supposed to be able to revert that. What we need to do is get you onto an eng spl so you can fastboot erase radio, fastboot flash radio, then flash the correct hboot aka the stock one. Right now you cant fastboot or anything aka you are semi bricked. Only thing i can say is let it sit o the charger for as long as possible for the sappimg update and pray lots n lots.
Sent from my HTC Magic using XDA App

knny1491 said:
You have a 32a radio with a 32b spl, during the root process you are supposed to be able to revert that.
Click to expand...
Click to collapse
Thank you so much for the follow up. I wish the news were better!
How can you tell that I have a 32b SPL? By the errors I'm experiencing? The SAPP310000? Just guesses here. I don't see that on my phone so, I'm curious to learn.
knny1491 said:
What we need to do is get you onto an eng spl so you can fastboot erase radio, fastboot flash radio, then flash the correct hboot aka the stock one. Right now you cant fastboot or anything aka you are semi bricked. Only thing i can say is let it sit o the charger for as long as possible for the sappimg update and pray lots n lots.
Click to expand...
Click to collapse
Are you advising my to sit on my hands, keeping my phone charged, until, hopefully, the development community comes up with a new sappimg solution? Or are you saying to preform the 1.33.2010 engineering SPL update until success or my phone dies?

I was stating to do the update where it freezes or hangs on the radio and let it sit for a crazy amount of time with praers, the spl version is defing by the numbers i the 1.33.0013 etc area, 32a users have 1.76.xxxx sp numbers while 32b users have 1.33.xxxx and after looking i see you are on the stouch 1.2 spl which is why fastbooting anything will not work. Quick question though did you try flashing te spl and radio BEFORE the recovery?
Sent from my HTC Magic using XDA App

knny1491 said:
I was stating to do the update where it freezes or hangs on the radio and let it sit for a crazy amount of time with praers, the spl version is defing by the numbers i the 1.33.0013 etc area, 32a users have 1.76.xxxx sp numbers while 32b users have 1.33.xxxx and after looking i see you are on the stouch 1.2 spl which is why fastbooting anything will not work.
Click to expand...
Click to collapse
Thank you for the reply. Good to know, as I was under the impression that all T-Mobile MyTouch 1.2 phones were 32A, and 1.33.0013 was the desired and appropriate version for 32A.
knny1491 said:
Quick question though did you try flashing te spl and radio BEFORE the recovery
Click to expand...
Click to collapse
I initially tried followed the procedure here: http://wiki.cyanogenmod.com/index.php/Full_Update_Guide_-_Fender/1.2
Where, I updated the SAPPIMG via goldcard, then through fastboot, I flashed the radio, hboot, and recovery. But, I wasn't able to boot to recovery after that process, for whatever reason, so I began trying other procedures from other sources, which in all likelihood took me further away from the solution instead of closer.
If the current attempt of updating radio_v2 until success or power battery dies (which has been hung for about 30 minutes so far) does not end successfully, should I try flashing a different hboot or radio? Or any other suggestions?
Thanks again for your continued help. I'm going to try to get some more attention to this thread to hopefully get more possible solutions.

If the radio doesnt flash then we have to question why the recovery didnt load, the g version is the correct version given there is only one spl for us 1.2 users and it is a google spl. That is why you flash radio then spl then recovery in that order so nothing messes up. The thing is you have to flash a radio before spl, yet you hav the spl yet NOT THE RADIO which leaves me to believe you accidentalky did the spl first n not the radio first.
Sent from my HTC Magic using XDA App

knny1491 said:
If the radio doesnt flash then we have to question why the recovery didnt load, the g version is the correct version given there is only one spl for us 1.2 users and it is a google spl. That is why you flash radio then spl then recovery in that order so nothing messes up. The thing is you have to flash a radio before spl, yet you hav the spl yet NOT THE RADIO which leaves me to believe you accidentalky did the spl first n not the radio first.
Click to expand...
Click to collapse
Okay, thanks so much for the continued insight.
I think, I flashed the radio down to original, but encountered some problem, misdiagnosed it, and flashed it back up again. Now it's been about 3 weeks of messing with this phone for a couple hours a day, so, unfortunately, it's hard to remember all that I've tried. If what you're saying is true, then yes, I must have accidentally flashed the SPL before the radio. Is there a remedy for this? I've been pouring over this forum searching for "can't flash radio" (forum.xda-developers.com/search.php?searchid=39519193&pp=25&page=1) and so far I've read people claiming to have had successfully deleting their radios completely and reinstalling. Is this an option? Any other suggestions?
I will PayPal $30 to you, anyone who can give me a solution to where this phone is working and rooted. Alternatively, I live in Los Angeles, if anyone can recommend a good, knowledgeable, phone repair shop.

it's really strange why that didn't work for you.
My steps were as follows:
**make sure phone is fully charged**
pre 1) create goldcard
1) place sappimg.zip on gold card
2) boot phone with goldcard to flash using Vold down + power
3) let it reboot - should boot up to the "htc magic" logo -- for me it never loaded back up to stock 1.6, I had to pull the battery.
4) boot to fastboot using back + power
5) connect phone to PC and verified it was recognized using "fastboot devices"
6) make sure you have stock radio and spl in your Android SDK's \tools
7) performed the following:
fastboot flash radio radio.img (or whatever the filename you have for the stock radio)
fastboot flash hboot hboot.nb0 (or whatever the filename you have for the stock hboot)
fastboot flash recovery recovery.img (or whatever the filename you have for amon_ra or clockwork or cm recovery)
fastboot reboot-bootloader (to make sure that stock radio and SPL are loaded again)
8) reboot to recovery using home+power
*from this point on, you no longer need to use your goldcard
9) have new ROM .zip on root of your SD card, option flash from zip
10) ???
11) profit

NetrixTardis said:
it's really strange why that didn't work for you.
My steps were as follows:
**make sure phone is fully charged**
pre 1) create goldcard
1) place sappimg.zip on gold card
2) boot phone with goldcard to flash using Vold down + power
Click to expand...
Click to collapse
Thank you for your continued feedback!
I think you've listed the standard recipe for rooting this phone. I believe you. Unfortunately, something in my phone has gone askew (certainly my error) at this point and the "standard" just isn't working now. As is, and for the past 3 weeks, the process you describe dies at step 2. It hangs while updating RADIO_v2 (at whatever position in the list of updates it is for a given SAPPIMG file). Also, attempting to flash a stock radio.img via fastboot also hangs. Both updates send just fine, but hang at updating around 95%.
I've also been getting some advice from another member, knny1491. On this page, above, you'll see he hypothesises what my error is:
knny1491 said:
If the radio doesnt flash then we have to question why the recovery didnt load, the g version is the correct version given there is only one spl for us 1.2 users and it is a google spl. That is why you flash radio then spl then recovery in that order so nothing messes up. The thing is you have to flash a radio before spl, yet you hav the spl yet NOT THE RADIO which leaves me to believe you accidentalky did the spl first n not the radio first.
Click to expand...
Click to collapse
That sounds plausible that I did flash things in the wrong order. I'll accept that. I've been messing with it so much, I'm lucky it works at all. So now, and still, my question is where to go from here? Do you know anything about this radio/SPL relationship and how to remedy this current conflict, NetrixTardis?
Thanks again.

Possibly try to re download the sappimg from the mgic spl thread?

I was just thinking, if your goal at this point is to have the phone usable again regardless of root; why not try the RUU exe ? If i unserstand what it does, it should flash the phone back to stock (radio, spl, recovery,ROM etc). You'll have a phone as if you just unboxed it.
Thats if i understand what the ROM Upgrade Utility (RUU) does correctly. Someone should be able to correct me...

NetrixTardis said:
I was just thinking, if your goal at this point is to have the phone usable again regardless of root; why not try the RUU exe ? If i unserstand what it does, it should flash the phone back to stock (radio, spl, recovery,ROM etc). You'll have a phone as if you just unboxed it.
Thats if i understand what the ROM Upgrade Utility (RUU) does correctly. Someone should be able to correct me...
Click to expand...
Click to collapse
Thanks for the idea! I'll do some research on that. If anyone else can give any insight into if this may help restore my phone, please chime in!
I'd like root, but anything that gets the basic utility of the phone back would be great at this point (I've been using a old razr as a replacement while mine is hosed). I think an official 2.2 update is coming out from T-Mobile soon. I can wait for that.

NetrixTardis said:
Thats if i understand what the ROM Upgrade Utility (RUU) does correctly. Someone should be able to correct me...
Click to expand...
Click to collapse
If this is a good potential solution, could someone please direct me to which RUU to use? I've located the "[ROM] Official HTC Sapphire/Magic/MT3G RUU ROM Links" thread here: forum.xda-developers.com/showthread.php?t=659403
There really is a great abundance of options. I'm guessing I should go for the latest [MT3G 1.2] download which is:
36) [xda-ftp] [4shared] 2.10.531.4 T-Mobile USA DRD35
36) 2.10.531.4 1.33.0013G 2.22.23.02 N T-MOB010
I'll want a few hours or perhaps a day before attempting this process, in hopes that some helpful reader will provide his input if this is a good or bad thing to do as far as getting the phone working again.
Thanks!

Can not boot or reflash HTC Magic 32A after flashing Rogers 2.1 over CM froyo (1.33.)

Hi
I have the following problem:
I've tested FroyoRedux Mod v1.9.5 with the requested radio and hboot. After that I've tried to install the original stock ROGERS 2.1 ROM. Now, the problems appeared. somehow I'm stack with the
1.76.0010 hboot, with security ON
Radio 3.22.20.17 (which should be 6.35.xx.xx) after flashing (don't ask why the update didn't take place because there was no error)
and the phone hangs at the ROGERS screen (just before start loading android).
I've tried reflash SAPPIMG from flashboot but it detects is already there and won't flash. I can not use fastboot from computer because security is ON, i don't have recovery installed because ROGERS rom took it away.
Any ideas on how I can fix this mess?
UPDATE: After reading tons of forum pots, seems I have found the source of the problem and seems that became a common issue: I've installed Rogers 2.1 manually over CM custom ROM with froyo (SPL 1.33.xxxx and RADIO 3.22.xx.xx) without knowing that Rogers will not update both RADIO and SPL.
Now all of us who did this need a solution. Anyone has an ideea?
Thanks

how did u install the rogers 2.1?
from the RUU?
u have a rogers magic+ phone?

blizard80 said:
how did u install the rogers 2.1?
from the RUU?
u have a rogers magic+ phone?
Click to expand...
Click to collapse
Hi, Yes, I've instaled Rogers 2.1 but not from RUU but from fastboot with SAPPIMG.zip

and u installed hboot from the ruu?
i think u must make a gold card... but wait for the experts

When I've installed the SAPPIMG using a goldcard, it automatically overwiten hboot, recovery and radio.
BTW: if I've formatted the goldcard, how can I create a new one now that i don't have a linux pc and i can only enter fastboot.
Thanks

Why did you post this in Development?
I'll move it to General... but I fail to see how this is development related.

Binary100100 said:
Why did you post this in Development?
I'll move it to General... but I fail to see how this is development related.
Click to expand...
Click to collapse
sorry, i was reading in development and post the thread here from mistake

any solution please?

Now I can access teh memoy card again. Please give me a solution using RUU. Maybe a valid RUU which works on all devices because when I've tried to flash a RUU it sais whong RUU version and I must get another one.

No one can help?

http://rapidshare.com/files/421772202/SAPPIMG.nbh
Try flashing the above.... using a goldcard and from fastboot/hboot.

Thank you for answering
I will try now

I've tried it but it say "Main Version is older". Can you tell me how can I fix that or how to make a SAPPIMG.nbh file with Rogers update or even android 2.2. Or do you have such thing?
Thanks a lot.

Anyone with a solution please !?!?

Got your PM... normally i don't respond help request over pm, but i'll make an exception.
You need to redo your goldcard... all the errors you get points to a faulty goldcard.
You can post/pm the cid nr you get from the htc device + the reverse nr. you used to make the goldcard... then i can verify that you have done it correctly.
You should have made it work with the sappimg.img i have provided earlier....
All points to a bad made goldcard!

Thanks so much for your reply.
So, Let's get started . My SD CID is
035344535530324780109ac8ee0093aa
After using http://hexrev.soaa.me/
My reversed CID is
009300eec89a10804732305553445303
(first two zeros already present)
Now, I've used this code here http://psas.revskills.de/?q=goldcard
and get the goldcard in the attachment.
Can you check please?
Thanks a lot

Well all ok from here.
The only thing left is how you made the hex-changes to the goldcard...
Which guide did you follow?
Read your pm!

i have exactely the same problem so when you get the solution can post it please !!!

Sure I will

Try this...
http://rapidshare.com/files/424005789/sappimg.zip
Put it on the goldcard and reboot by holding volume_down + power.
Then let it work...
Make sure there is nothing else on the goldcard!
Do not rename or anything.
This sappimg.zip is the new rogers 2.1 update... it should work :0)
Please report back :0)

Having trouble installing clockwork recovery

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

[Q] HBoot versions

Hi guys,
I have a wildfire with CM7 (via unrevoked) HBoot 0.08.0008 and unfortunately this doesn't work with the AlphaRevX open beta .
I was wondering how to upgrade the HBoot version to "1.01.001" which is what works best with alpharevx?
Thanks for any help.

same here! mine is 0.80.0007

What i did
1. Nandroid back to stock rom
2. downloaded
RUU_Buzz_Froyo_HTC_WWE_2_22_405_1_Radio_13_55_55_24H_3_35_20_10_release_160191_signed.exe
from
http://shipped-roms.com/index.php?category=windows mobile&model=Buzz
Ran it from Pc to get the correct hboot 1.0
3. Downloaded
http://bit.ly/su2361ef
from this thread
http://forum.xda-developers.com/showthread.php?t=1105614&page=34
put file on a gold card
power up phone with the volume down ,let the .img file and the gold card do it`s thing
rest is up to you , i gave my phone a alpharev splashscreen and a CM7
MAybe possible with out the gold card i do not know ,
And you may want to get all your ducks in a row (dload needed files to gold card)

at first i was very sceptical about upgrading to hboot 1.x, but it worked like a charm.
one question though, has anyone tried alpharevx on 0.8x? what happened? just curious.

t0mas_ said:
at first i was very sceptical about upgrading to hboot 1.x, but it worked like a charm.
one question though, has anyone tried alpharevx on 0.8x? what happened? just curious.
Click to expand...
Click to collapse
Doesn't work. Says "Your device is not supported at this time". It was the first thing I tried.

still no luck! I've downloaded this RUU_Buzz_Froyo_HTC_WWE_2_22_405_1_Radio_13_55_55_2 4H_3_35_20_10_release_160191_signed.exe & ran via pc. & got an error, saying incompatible ruu... something like that. my phone is not branded (openline) do I need to create a goldcard? or do you know some ruu that i can used to? thanks in advanced.

oh the insanity

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.