Related
Alright, so HTC released the sense UI update to 32A in Europe some days ago. After searching around I figured how to flash it without getting stuck at perfect SPL. Therefore; I'd like to say that this is very little my own work. I only wrote everything I found here.
I'd like to thank these people/sites for learning me this:
Radix999, for his page in the wiki.
TheUnlockr, for fantastic guides about rooting.
cursordroid, for the correct order to flash radio/hboot.
vmaxada, for how to get rom.zip and rom1.zip.
Read everything before trying if you don't want to risk your phone.
You will need engineerings SPL before doing this. Means it won't revert the perfect one.
Disclaimer:
I'm not responsible for anything may happen to your phone during this update.
Only apply this on a sapphire 32A.
There's always a risk when flashing images to your phone, but if you follow the instructions, you should be fine.
This update will give you:
HBOOT-1.76.2007
RADIO-6.35.08.29
ROM version 3.05.401.3
Alright, so what you'll first need is the files. There's two ways to get these. First one, would be to download them (defiantly easiest). The second would be to fetch them from HTC's update file, I'll write this only for learning purposes, so if you're not interested in learning, do it the first way.
opinion 1
Download the files
I've collected everything for you in one file.
RUU_Sapphire_HTC_Europe_3.05.401.3_release_signed_NoDriver(eng spl).rar (mirror) password: for xda
Extract the files to somewhere you'll find them. Like C:\AndroidSDK\tools.
opinion 2
Fetching the files yourself
Doing it this way will take a lot longer than the first, but you'll learn more.
Here you'll need two files:
The official update file, RUU_Sapphire_HTC_Europe_305401 (mirror) and the SPL version, hboot-1.76.2007.
Copy the hboot-1.76.2007 to somewhere you'll find it, like C:\AndroidSDK\tools.
Boot your phone into fastboot mode (back+power) and connect it to your computer using USB. Run the file you downloaded, RUU_Sapphire_HTC_Europe_305401, and continue until it's done displaying "Confirming info about the Android phone" (I'm not sure if it's exactly the same displayed, but it should have the same meaning). When it's done with that, STOP, don't cancel, but don't do anything further.
Keep the update window open, and go to Start - Run, then type in %temp%. Search for "rom*.zip". You should get rom.zip and rom1.zip as results. Copy both the files to your desktop. Cancel the update.
Note: People have reported the files won't open with the built-in zip extractor in Windows, you'll might need WinRAR.
Open the two zip files. Extract the following files to the same place where you putted the hboot-1.76.2007:
Code:
boot.img
radio.img
recovery.img
system.img
userdata.img
After doing this you're done with getting the files.
Flashing
Now you're done with most of the work, everything left is flashing.
Boot your phone to fastboot (back+power), and connect it to your computer. Open up terminal (cmd) and "cd it" to the directory where you have the system files.
Code:
cd C:\AndroidSDK\tools
Then type in this, to check your phone is connected.
Code:
fastboot devices
If you get a serial number, your phone is connected and you can proceed.
Now, type in the following and hit enter after every line:
Code:
fastboot flash radio radio.img
fastboot flash hboot hboot-1.76.2007.img
fastboot flash recovery recovery.img
fastboot erase system –w
fastboot reboot-bootloader
Now your phone should reboot into fastboot. Make sure you have HBOOT-1.76.2007 and RADIO-6.35.08.29. If you have that, you can type in the rest:
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot reboot
Now your phone will reboot, and you'll have the official sence UI, but still engineerings SPL!
As you may have noticed, my English isn't perfect. If you see something wrong with my grammar please tell me what's wrong.
If you want a custom recovery, you'll have to install a Hero recovery. I recommend RA-hero-v1.5.2.
First of all this is old news already explained by Cursordroid who, i can see, you didnt not bother to thank! Trying to take credit for something that someone else did is not a good idea.
Secondly, your info is wrong. You will not end up with that version of the radio but with 6.35.08.29, nor is there rom2.zip but rom1.zip (at least for me it was that way). By flashing the new radio, people will be confined to using official 3.03/3.05 ROM, CursorSense, Cursor's t-mobile fender rom and some other roms (1-2 more exist currently) that i did not test. Otherwise a downgrade to the old radio is required! (e.g for running CM you need to downgrade the radio).
Did actually need another post on this topic??
The mirror I'm using is screwed at the moment, uploading takes longer then I expected.
eyegor said:
First of all this is old news already explained by Cursordroid who, i can see, you didnt not bother to thank! Trying to take credit for something that someone else did is not a good idea.
Secondly, your info is wrong. You will not end up with that version of the radio but with 6.35.08.29, nor is there rom2.zip but rom1.zip (at least for me it was that way). By flashing the new radio, people will be confined to using official 3.03/3.05 ROM, CursorSense, Cursor's t-mobile fender rom and some other roms (1-2 more exist currently) that i did not test. Otherwise a downgrade to the old radio is required! (e.g for running CM you need to downgrade the radio).
Click to expand...
Click to collapse
Where did I try to take credits from him? I fixed the wrong info (sorry about that). Also, where did he explain this? I know he explained how to get this radio, SPL and Hero recovery. But nothing about the official sence ROM?
fregor said:
Did actually need another post on this topic??
Click to expand...
Click to collapse
Where's the other topic about this?
He did some time ago make a toping regarding flashing 3.03 without getting stuck with the perfected spl. After making CursorSense however he eventually deleted his 3.03 thread.
You did not directly state that you were to be credited for this work but you did not thank him for doing it either. And all you did was "steal" (steal because you failed to thank the man) his method.
eyegor said:
He did some time ago make a toping regarding flashing 3.03 without getting stuck with the perfected spl. After making CursorSense however he eventually deleted his 3.03 thread.
You did not directly state that you were to be credited for this work but you did not thank him for doing it either. And all you did was "steal" (steal because you failed to thank the man) his method.
Click to expand...
Click to collapse
Alright. I'll thank him, but for what?
In other news, I still can't manage to upload the files (crappy outline I guess). I, however, added links to the same files. They are not uploaded by me though.
perfected spl
can we use this method if we already updated to a perfecter spl (1.76.0010)?
WTF
Hey dude!!!
You forgot to mention me under the thanks to, part that you don't even have!!
I hope you feel good about yourself!
and you searched? No! You asked me!
This is last time I'm helping you!!
Still... this is not for us who have already been stuck with perfected SPL...
Can I use these instructions if I have hboot-1.33.0010 (sapp10000)? or do I need to use goldcard to get 1.33.2010 first?
Thank you
Nope you will need eng spl to fastboot...
But he forgot to write anything about that!!
So you need the 2010 before you can even start...
Yeah, I thought so too...
Thanks
ralle.gade said:
Hey dude!!!
You forgot to mention me under the thanks to, part that you don't even have!!
I hope you feel good about yourself!
and you searched? No! You asked me!
This is last time I'm helping you!!
Click to expand...
Click to collapse
Look at the date I posted this thread, 22th. I asked you my first question the 23rd.
All the info I needed to write this, i found on the wiki (thanks radix), the unlockr, and other places.
What was I supposed to thank you for anyway?
Mine have perfect SPL
SAPPHIRE PVT32A SHIP S-ON H
HBOOT-1.76.0007 (SAPP10000)
If I'm upgrade this rom by using gold card, can I have a new SPL?
guys, after i installed this rom,,,i installed the ra recovery 1.5.2H, and when i tri to acess to the recovery it blocked!!! no way to rebbot....i have to remove the battery..i tried several times...always happen the same...
any idea?
zouky007 said:
guys, after i installed this rom,,,i installed the ra recovery 1.5.2H, and when i tri to acess to the recovery it blocked!!! no way to rebbot....i have to remove the battery..i tried several times...always happen the same...
any idea?
Click to expand...
Click to collapse
What recovery image did you use?
As far as I can tell you need the hero version for this rom/radio. So I'm thinking you used the sapphire version.
muuu said:
What recovery image did you use?
As far as I can tell you need the hero version for this rom/radio. So I'm thinking you used the sapphire version.
Click to expand...
Click to collapse
Yes. Flash the RA-hero-v1.5.2 recovery using:
Code:
fastboot flash recovery recovery-RA-hero-v1.5.2.img
shokuhawan said:
Mine have perfect SPL
SAPPHIRE PVT32A SHIP S-ON H
HBOOT-1.76.0007 (SAPP10000)
If I'm upgrade this rom by using gold card, can I have a new SPL?
Click to expand...
Click to collapse
No. You'll need engineerings SPL. Try this.
Any ideas whats going on with my unit? It seems to be crashing when writing the radio. I see the red bar go all the way to the top, and then it just sits there forever... any ideas?
gunigugu said:
Any ideas whats going on with my unit? It seems to be crashing when writing the radio. I see the red bar go all the way to the top, and then it just sits there forever... any ideas?
Click to expand...
Click to collapse
Did you flash it in the correct order? If not, try flash back to a hboot that suits with your current radio. Then flash this radio.
In other news, I finally managed to upload the files myself.
So i think i know what i did wrong, but is there anyway to fix it? I have a 32b which i rooted with the "recovery-RA-sapphirev1.5.2H", then i tried to update the radio with the "update-radio-32A-6.35.08.29-signed" (i didnt read the "32A"). Then i tried to reboot the phone and it got stuck on the "Mytouch 3g" green start up screen, i cant get to the recovery image by holding home+end.
My understanding (please correct me if im wrong) to get the new Nexus ROM was that i had to;
1) Go the the 1.5.2 recovery image & wipe
2) Partition the card (and convert Ext2 to Ext3 or Ext4 depending on the ROM), reboot
3) Flash the new Radio, then reboot
4) Wipe, Flash the new SPL, then reboot
5) Wipe, flash the new ROM, and reboot
Im sure what i did was noobish...
Previously i had been using the 1.3.2 immage and had loaded Hero ROM's and tweeked Cupcake ROM's just fine, it was only when i had to update the radio and SPL was it that i found difficulty, mostly because i found too many and didnt know which one to use.
PLEASE HELP!!!
I'm willing to try anything. I hope i can get this fixed by this afternoon =,(
My first guess is that you are f**ked!
Only 2 "Nexus" roms I know that require new radio are for the 32A. And only new radio I know is for the 32A Magic!
Don't know where you got the instructions to upgrade your radio, but the ones I read stated that you have to flash radio, hboot, recovery in this sequence, and THEN reboot. Also, your recovery should be for 32B, dunno how you missed that one.
Try this: find your old radio image, your old hboot and recovery, boot in fastboot mode (back+power) and type in the following commands from the Android SDK tool directory:
Code:
fastboot flash radio your_radio.img <enter>
fastboot flash hboot your_hboot.img <enter>
fastboot flash recovery your_recovery.img <enter>
fastboot erase system -w <enter>
fastboot reboot-bootloader <enter>
You should now have rebooted back in fastboot mode. If that worked, try to reboot into recovery and see that works.
Once in recovery you can restore or flash another 32B rom.
See here for Engineering hboot images.
Download recovery for 32B
I found the link on theunlockr.com
developers.com/showthread.php?t=598973
And found instructions on youtube "ECLAIR 2.1 ROM REVIEW AND TUTORIAL !!!" and tweaked it slightly because i found a recovery image for my sapphire which didn't support either the spl or the radio, i forget... I've been up since 3am on Wednesday because of work and school, and now its 9am Thursday.
I was reading that 32b ROMs were working for the 32a, so i thought i might try a 32a since none of the links on Amon_RA's page developers.com/showthread.php?t=529019 were working for me.
I cant get to the fast boot menu... so that way doesnt work
Some_Biker_Guy said:
I'm willing to try anything. I hope i can get this fixed by this afternoon =,(
Click to expand...
Click to collapse
I think you are rather screwed. I believe the phone boots up the radio image before the bootloader and therefore you can't even get to flash a new recovery or radio image as the boot process is halted because of the defective radio image.
The only salvation I know if is a JTAG connection. This involves open up and soldering stuff to the mainboard of your phone. Since you're asking you probably not familiar with it I wouldn't recommend it to you.
you have a mytouch 3g right? if so, you flashed the wrong radio image. you flashed the ra(blahblahblah)H! not the ra(blah)G! "H" IS FOR HTC BRANDED "G" IS FOR GOOGLE BRANDED (THE MT3G). so that is your first issue. try to boot into fastboot and flash the RIGHT RECOVERY IMAGE.
wow as soon as I looked at this thread, you made so many mistakes on the first sentence lol. I hope you learn to read and not rush things next time ^^ Recovery H = 32A, Radio says 32A, and you have a 32B and now you can't get into fastboot? I'm 99.9999% sure it's bricked, but correct me if I'm wrong! 32B roms work for 32A when you port them over. Seems like you did almost no research at all.
You're understanding of what to do is right, but you didnt pick ANY of the right files
KAwAtA said:
wow as soon as I looked at this thread, you made so many mistakes on the first sentence lol. I hope you learn to read and not rush things next time ^^ Recovery H = 32A, Radio says 32A, and you have a 32B and now you can't get into fastboot? I'm 99.9999% sure it's bricked, but correct me if I'm wrong! 32B roms work for 32A when you port them over. Seems like you did almost no research at all.
You're understanding of what to do is right, but you didnt pick ANY of the right files
Click to expand...
Click to collapse
I agree with KAwAtA. You pretty much did the right steps (kinda) but you got the wrong files and now you got a nice brick. You should do research and know how to tell if your phone is 32A or 32B, why you should never flash the wrong radio/spl for your type of phone, and what ROMs are compatible with your hardware and why you should never flash the ROMs for another piece of hardware.
Well look on the bright side, since you bricked your magic, instead of trying out the "Nexus" ROMs, you can now buy a Nexus One for real but do not ROOt it because you might flash a 32B radio on it and make that a fancy brick.
damn sorry bro. does sound like everything that could have gone wrong went wrong for you. i also went to theunlockr to root my phone and add roms to it but i read those instructions like 3 times and watched the videos a few times when i first did it. oh well, you'll learn from this at any rate.
AndroidNoobie said:
Well look on the bright side, since you bricked your magic, instead of trying out the "Nexus" ROMs, you can now buy a Nexus One for real
Click to expand...
Click to collapse
that lucky SOB!
you can't get into recovery, that's fine, but can you boot into hboot and fastboot mode? if so, your phone will be fine, just have to fastboot flash the right junk on
Some_Biker_Guy said:
So i think i know what i did wrong, but is there anyway to fix it? I have a 32b which i rooted with the "recovery-RA-sapphirev1.5.2H", then i tried to update the radio with the "update-radio-32A-6.35.08.29-signed" (i didnt read the "32A"). Then i tried to reboot the phone and it got stuck on the "Mytouch 3g" green start up screen, i cant get to the recovery image by holding home+end.
My understanding (please correct me if im wrong) to get the new Nexus ROM was that i had to;
1) Go the the 1.5.2 recovery image & wipe
2) Partition the card (and convert Ext2 to Ext3 or Ext4 depending on the ROM), reboot
3) Flash the new Radio, then reboot
4) Wipe, Flash the new SPL, then reboot
5) Wipe, flash the new ROM, and reboot
Im sure what i did was noobish...
Previously i had been using the 1.3.2 immage and had loaded Hero ROM's and tweeked Cupcake ROM's just fine, it was only when i had to update the radio and SPL was it that i found difficulty, mostly because i found too many and didnt know which one to use.
PLEASE HELP!!!
I'm willing to try anything. I hope i can get this fixed by this afternoon =,(
Click to expand...
Click to collapse
Well, I BRICKED BRICKED BRICKED my other mytouch. Im talking where the computer wouldn't recognize it, wouldn't charge, turn on, splash screen, NOTHING. Wasn't the battery. If you can get to the screen (where you hold down volume and power) you can probably recover it. DON'T know if this would work but it may be worth a try read this link to get it un-rooted and then retry. http://theunlockr.com/2009/08/22/how-to-unroot-your-mytouch-3g/
iluvmymytouch said:
Well, I BRICKED BRICKED BRICKED my other mytouch. Im talking where the computer wouldn't recognize it, wouldn't charge, turn on, splash screen, NOTHING. Wasn't the battery. If you can get to the screen (where you hold down volume and power) you can probably recover it. DON'T know if this would work but it may be worth a try read this link to get it un-rooted and then retry. http://theunlockr.com/2009/08/22/how-to-unroot-your-mytouch-3g/
Click to expand...
Click to collapse
maybe u already tried.
dan-htc-touch said:
you can't get into recovery, that's fine, but can you boot into hboot and fastboot mode? if so, your phone will be fine, just have to fastboot flash the right junk on
Click to expand...
Click to collapse
he already said that he couldnt get into fastboot mode. most likely its a brick..
oshizzle1991 said:
you have a mytouch 3g right? if so, you flashed the wrong radio image. you flashed the ra(blahblahblah)H! not the ra(blah)G! "H" IS FOR HTC BRANDED "G" IS FOR GOOGLE BRANDED (THE MT3G). so that is your first issue. try to boot into fastboot and flash the RIGHT RECOVERY IMAGE.
Click to expand...
Click to collapse
I tried the "G" and it didn't work, so i tried the "H" and it worked. Fastboot didn't work...
Thanks everyone for you input... this is my reply to everyone since i cant reply to one/ a few at a time.
1) I knew how to root my phone, and did it multiple times. I also unrooted it a few times as well (just to get a fresh start and make sure i knew how to). I also loaded many different ROM's onto it including Hero and tweaked cupcake ROM's
2) Fast boot did not work, and the computer would not recognize the phone at any point.
3) The unlockr did a good job with instructions on how to root and unroot then loading the hero and cupcake rom's onto it but it had no explanation for loading the nexus rom onto it, although it did feature a link on where to get it. therefore i tried to piece together ways to update the radio and spl (this is where it all went to hell). i figured out that that is what i needed to do to run the nexus rom.
ok, ok now i know, wait for a full set of instructions for my specific phone to try to put the newest and coolest rom onto my phone... :/
4) i got it all taken care of, got "new" phone for free! so glad it worked out.
Hi,
I thought id flash my 32b with the latest rom today, so i downloaded it off here (said it was for a 32b) and flashed my phone...
1: its not for a 32b its for a 32a
2: its now stuck in RUU USB mode
3: i can communicate to it with fastboot but can not load a recovery file as it just hangs where it should have rebooted into the recovery image,
4: its using 1.76.0009 spl which is a perfect one.
5: PLEASE does anyone know how i might be able to UN-Brick my phone ?
6: I cant make a gold card as i can't get the CID for my SD card
PLEASE HELP
EDIT: There is an update on HTCs UK site. Just download and install that and you should be fine.
thanks for the reply,
Unfortunately im from NZL and my serial number doesnt work
and my phone is a 32b and that update is for a 32a
Used Haret to get CID
I also bricked my Magic yesterday, using an official RUU.exe. And I had the same problem in obtaining the CID, but luckily I could get around it as follows:
I still have an old HTC Touch Cruise (aka Polaris 100) and installed an Android version which booted from Haret. Once it was running I could obtain a terminal window and do a cat for the CID file. I tried to access it via ADB, but that did not succeed.
There are several distributions described in the Polaris forums, your mileage might vary with other models.
So if you know somebody with an HTC phone (WM) try to find an Android distribution for it, put it on your SD card and run haret. It is non-destructive and allows you to read the CID. After obtaining the CID, I reformatted the SD card and folowed the instructions here: Create gold card.
After inserting the Gold card, I could continue the RUU update and now I have a Magic with HTC Sense.
thanks for that, im glad to see im not alone, im trying to find a program for linux / mac / windows which will give me my CID for my SD card but can't find one anywhere
When you put the goldcard in and turned your phone on it boot from it automatically ?
gymmy said:
thanks for that, im glad to see im not alone, im trying to find a program for linux / mac / windows which will give me my CID for my SD card but can't find one anywhere
When you put the goldcard in and turned your phone on it boot from it automatically ?
Click to expand...
Click to collapse
If u have a nokia hacked can use the ReadCID aplications.
thanks i have found a friend with a touch HD on android so i am going to get that tomorrow and make up a gold card ,... Ill report back with the results.
Thanks to everyone for your help todate
gymmy said:
thanks i have found a friend with a touch HD on android so i am going to get that tomorrow and make up a gold card ,... Ill report back with the results.
Thanks to everyone for your help todate
Click to expand...
Click to collapse
hello, I had the same problem with the help of my colleagues from the Bulgarian, I fixed it without gold for cadets karta.Chek you just made the phone had such a site where you are setting up your serial number and go to where it e.sled enter the site and the HTC looking for old phone si.Download to update it if you go with the serial number if you do not poke around the net, Russians are brothers powwow original RUU, most important is to find for your original RUU telefon.Shtom find it, you put the USB cable and it puskash.This of me I hope I helped you
Wait... how did you manage to install a RUU for 32A on a 32B without goldcard?
sindrefyrn said:
Wait... how did you manage to install a RUU for 32A on a 32B without goldcard?
Click to expand...
Click to collapse
my platform is 32A end I dont creat cold card just a original RUU from HTC sait
my phone is TIM brandet and i download TIM RUU and my phone downupgade then
Just an update to how the recovery is going
Well i created a goldcard which has fixed my issue with the Custom ID check and i have managed to Down grade my hboot to 1.76.0008 and my radio phone is still having a personalliy issue and thinks its a 32a and its NOT !! when it gets to unzipping the system it just hangs there, in fact it sits there all day until the battery dies and indicator doesnt shift on phone from 0 so with the RUU it makes it to 81% if i can get a sappimg for a 32b which desent flash the system but only the radio and hboot would be great (I think) , issue is that when i try and make one, it comes up with Signature Verfiy Fail
HELP
Not even 32A users can downgrade 1.76.0008 right now except for the SU edition, which you cannot boot. You have a brick.
The same problem
http://www.youtube.com/watch?v=PlH_yhgRiwo
I have found a way around that im now working again, its all about the order that things get flashed to your phone.
I found an RUU that flashed everything 1st apart from the rom which is flashed last. As long as you have a gold card you can do this.
When it gets to flashing the system over its crashes... thats ok, take the battery out of your phone and reflash, your 32a s-on H becomes a 32b s-on H and then the system will flash over ok.
So... I have a skitzo phone at the moment with a saudi rom on it, but at least its working... HOW EVER.... these bloody alarms keep waking me up to do my prays hahahaa i thought that was kinda funny...
SO... now i just need to copy a sappimg onto my gold card and flash off that which ill do tonight
Ill give a full detailed HOWTO with links to the files once im back to normal.
Its taken me about 3 full days and about 3gig of downloads to get this sorted. If you dont have a gold card then your SCREWED... well not totally you need to get another phone eg android or a windows mobile 6.5 with eaRET on it works also
gymmy said:
I have found a way around that im now working again, its all about the order that things get flashed to your phone.
I found an RUU that flashed everything 1st apart from the rom which is flashed last. As long as you have a gold card you can do this.
Here's why I thought you had a definite brick:
When it gets to flashing the system over its crashes... that's ok, take the battery out of your phone and reflash, your 32a s-on H becomes a 32b s-on H and then the system will flash over ok.
So... I have a skitzo phone at the moment with a saudi rom on it, but at least its working... HOW EVER.... these bloody alarms keep waking me up to do my prays hahahaa i thought that was kinda funny...
SO... now i just need to copy a sappimg onto my gold card and flash off that which ill do tonight
Ill give a full detailed HOWTO with links to the files once im back to normal.
Its taken me about 3 full days and about 3gig of downloads to get this sorted. If you dont have a gold card then your SCREWED... well not totally you need to get another phone eg android or a windows mobile 6.5 with eaRET on it works also
Click to expand...
Click to collapse
Now I am very curious. Where did you get this RUU? I still don't see how you fixed it. I'm looking forward to seeing you detail this.
The new RUUs come in 2 zip files - the first with the radio and hboot and the other with the rest of the files. You can rename them as sappimg.zip to try to flash them from RUU, since they are signed by HTC.
However, as far as I know those RUUs are for 32A only. If you had HBOOT 1.76.0008, 0009 or 0010, you can not flash a lower version ROM even with a gold card. The SPL/HBOOT and radio combination actually seems to work on the 32B. However, you would need to be able to boot to a custom recovery somehow to do anything special. The system.img on the 32A RUUs I thought were too big for 32B. So if you were able to flash you must have had enough space on the 32B and I was wrong. I wonder why people are getting stuck though.
The reason I called a brick is because the only available 32B HBOOT have lower ROM version strings (2.x series ROM) than the 32A RUUs (3.x series ROM version string). I still don't know if 32A RUUs actually work on 32B.
You can flash the 3.05 series SPLs all you want, but they are all perfected. The only other option for the 32A Magic was booting to the leaked 3.04 ROM with SU in the system image, but you would not be able to flash that. So are you saying that it actually works?
Anyways please report back
xaueious said:
Now I am very curious. Where did you get this RUU? I still don't see how you fixed it. I'm looking forward to seeing you detail this.
The new RUUs come in 2 zip files - the first with the radio and hboot and the other with the rest of the files. You can rename them as sappimg.zip to try to flash them from RUU, since they are signed by HTC.
However, as far as I know those RUUs are for 32A only. If you had HBOOT 1.76.0008, 0009 or 0010, you can not flash a lower version ROM even with a gold card. The SPL/HBOOT and radio combination actually seems to work on the 32B. However, you would need to be able to boot to a custom recovery somehow to do anything special. The system.img on the 32A RUUs I thought were too big for 32B. So if you were able to flash you must have had enough space on the 32B and I was wrong. I wonder why people are getting stuck though.
The reason I called a brick is because the only available 32B HBOOT have lower ROM version strings (2.x series ROM) than the 32A RUUs (3.x series ROM version string). I still don't know if 32A RUUs actually work on 32B.
You can flash the 3.05 series SPLs all you want, but they are all perfected. The only other option for the 32A Magic was booting to the leaked 3.04 ROM with SU in the system image, but you would not be able to flash that. So are you saying that it actually works?
Anyways please report back
Click to expand...
Click to collapse
No they dont work and hence why it bricked the phone, the good part is that it never flashed the rom so I was sweet with getting the phone back. Prior to flashing it was 32b 1.33.0010 eng s-off G, then 32a 1.33.0009 s-on H and now is a 32b 1.33.0010 s-on H... rom is 2.56.??.? which ill have to look up later when im back home either way its gone from a 32b to a 32a stuck in RUU USB (due to not enough room to flash the rom) back to a 32b which works just is all arabic.
With the GOLD card it allowed me to flash a different Custom ID on to my phone, replaced the Radio and SPL and which then changed the phone from 32a to 32b, I even reversed it and did it again to makesure it wasnt a fluke and it wasnt. if it wasnt for the fact that the order of the flashing occured the way i did i wouldnt have been able to fix it as it would tried and flash the SYSTEM b4 it would flash everything else which would make it hang !
As soon as ive rooted the current rom (which is harder than i expected due to the rom version) ill do a write up on how to fix it as there are a few steps inbetween.
.
Wait so you never flashed 1.76.x did you. You just had 1.33.0009 and you typed it wrong in your first post?
If so we don't need a walk through for that. The one at unlocker.net would have served you perfectly.
what walk through was that, ill re 32a it again and ill let you know that it was.
just an update ,
Yes it was spl 1.76.0009
i have since flashed the phone with 2.56.494.7 and now have to wait until someone gets a rooted version of this rom or releases a later gold card version of sappimg.nbh or sappimg.zip to cut a long story short this is what happened.
1: flashed a Sence-IU for a 32b (but it wasnt it was for a 32a)
2: ended up with 1.76.0009 and the radio which goes along with it.
3: now reads 32a s-on H
4: made a goldcard
5: had to flash with 2.56.494.7
6: first flash of this rom replaced the SPL with 1.33.0010 (perfected)
7: screen now reads 32b s-on H
8: rom failed to flash
9: re-run the update of 2.56.494.7 and the phone flashes and reboots
10: cant root the phone until a newer version of sappimg.nbh is released
11: can use the phone but the arab applications dont allow the market
12: now its a waiting game.
Hope this helps others with bricked phone... If i had to do this again i wouldnt have flashed the 2nd time with 2.56.494.7 but instead a different RUU for the 32B this would have ment i would have been able to root the phone... Live and lean !
.
I have used the guides in this post to fix a friend's 32B Magic, which he had flashed with an RUU for 32A Magic. It works just fine.
I installed 32A (6.35.10.18) radio on my Tmobile mytouch 32B by mistake.
Before doing this I had my phone rooted and SPL (1.33.2005 i think). Now fast boot shows its a 32A device . Now not able to run recovery mode.
I am not able to revert it back to 32B radio.
Tried to unroot but it says version is older(with gold card).
Some one please help me......
betaboy said:
I installed 32A (6.35.10.18) radio on my Tmobile mytouch 32B by mistake.
Before doing this I had my phone rooted and SPL (1.33.2005 i think). Now fast boot shows its a 32A device . Now not able to run recovery mode.
I am not able to revert it back to 32B radio.
Tried to unroot but it says version is older(with gold card).
Some one please help me......
Click to expand...
Click to collapse
You should be able to flash a radio image from fastboot. All you would need is to connect via USB. The phone will show 'fastboot usb' instead of 'fastboot'. You'll need the android sdk in order to go any further. Place the radio you want in the tools folder of the sdk so that it's easier to get to. Bring up a command prompt and navigate to the tools folder.
For me it looks like this:
cd\
cd androidSDK/tools
From there you'll need to make sure that the android drivers are installed properly. You can do this just by typing this:
fastboot devices
This will bring up a serial number if the drivers are installed correctly. If not you'll need to get the appropriate drivers. I believe I found mine during the gold card root process on the Unlockr's site.
As soon as your computer is talking to your phone it's simple.
In your command prompt simply type the following:
fastboot update <radio.img>
fastboot reboot
This will reboot the phone and it should reflash the radio. I've never had to do this so I don't know if it is going to work. Take these words with a grain of salt though... this could still brick your phone. Who knows? Next time just make sure you have the appropriate files. Especially when dealing with radio and spl. You're lucky your phone even turns on.
Good luck!
yeah i did the same last night, but mine is stuck with RUU USB and since the SPL is perfect i cant do anything as i get a signature verify fail or remote: can not do message
If you find a solution id be very interested.
Cheers.
Hi phantommusik,
Thanks for your response. This what I get when I do update radio.imp
"EOCD not found, not Zip
error: failed to access zipdata in '☺'"
No clue what it means
I am by no means an expert on the 32B Magic, but...
Try creating a Goldcard. There are instructions on this forum.
Then, even if your phone is stuck in RUU mode, you should be able to apply this RUU for the 32B Vodafone Magic.
http://forum.xda-developers.com/showthread.php?t=640283
I warn you though, you might end up with an unrootable phone. But at least it will work.
EDIT: Pay careful attention to these steps. Make sure a goldcard is in your phone before starting.
- Download and run the RUU executable
- When the wizard is at step 1, open a file search dialog
- Look for a file named rom.nbh (should be in %temp% folder)
- Copy the rom.nbh to another folder and rename it to SAPPIMG.NBH
- Close the wizard
- Copy the sappimg.nbh to the root of your SDCard
- Power down your phone
- Boot your phone while pressing "volume down"
- It will ask you to update (wait a bit till the question pops up)
- Press trackball to start update
- After update press trackball again to reboot
Sorry!
betaboy said:
Hi phantommusik,
Thanks for your response. This what I get when I do update radio.imp
"EOCD not found, not Zip
error: failed to access zipdata in '☺'"
No clue what it means
Click to expand...
Click to collapse
I know exactly what that means!!! It means I didn't give you complete instructions! My bad! When you are flashing anything from recovery or fastboot it has to be a .zip file or .nbh. I'm not entirely sure what needs to happen in order to get it to read it but you could try sticking that radio in a .zip file with NO COMPRESSION. You might want to take a look at some of the other threads in here to see what they have to say about putting just a radio in a zip file! I would suggest downloading a radio update that is already a zip file!
Hope this helps!
One friend of mine did exactly the same thing. I used the instructions on this post and I managed to get him his 32B Magic back.
becareful flashing this rom, it is perfected and you cant root it and if you can i wanna know how !
I tried updating the new RUU when in fastboot, but there was an error saying incorrect id.
Then I coppied rom.zip file and renames it to sappimg.zip, hboot hung when updating RADIO_V2.
Please help me, its ok even if cant root the phone.
gymmy said:
becareful flashing this rom, it is perfected and you cant root it and if you can i wanna know how !
Click to expand...
Click to collapse
Listen. If you really don't know, stop misleading people. You can't root this ROM, but you can install one that is already rooted. This ROM has the kernel fault that allows flashrec to install a custom recovery ROM. From then on you can do whatever you like with your phone, even revert it back to 32B. Amon_Ra's ROM for 32B Magic is a good place to start. Read here the post my friend wrote to thank me about getting his Magic back (It's translated from Greek, hence the bad English).
betaboy said:
I tried updating the new RUU when in fastboot, but there was an error saying incorrect id.
Then I coppied rom.zip file and renames it to sappimg.zip, hboot hung when updating RADIO_V2.
Please help me, its ok even if cant root the phone.
Click to expand...
Click to collapse
You' ll need a goldcard to use this. Stop doing things that can mess up your phone even more (like sappimg.zip etc). Just use the instructions in the link I posted before. About rooting please read my reply @gummy just above.
When I ran "RUU Sapphire HTC Arabic Etisalat" the installation got sturck at 77% (updating radio).
I removed the batter and plugged it back, now the phone got struck in RUU mode couldnt go to fastboot....... does it mean its bricked?
betaboy said:
When I ran "RUU Sapphire HTC Arabic Etisalat" the installation got sturck at 77% (updating radio).
I removed the batter and plugged it back, now the phone got struck in RUU mode couldnt go to fastboot....... does it mean its bricked?
Click to expand...
Click to collapse
Repeat the process with the RUU. It did the same thing, when I used it and after 1 or 2 tries the ROM was flashed properly.
Hi,
My phone was working fine till i tried to revert to old radio and spl to use the superD rom. Ive used many roms and all works fine. When i did the revert my recovery stopped working, so i tried going back to the higher radio and spl and still my recovery doesnt work, i press home and end call and insteasd of going to recovery it just sits there with the htc magic logo for 5 mins then reboots and loops. I have no OS on the phone now so I cant boot into O/S or recovery so I thought id try to install an RUU that I know lets me change the SPL and radio. I thought the only way would be in fastboot so I went into fastboot and loaded the RUU in windows and get the errors "the ROM update utility cannot update your android phone" and
"please get the correct ROM update utility & try again". Now my fastboot has a little picture of a processor(I think) with a red cross through it and now I cant even change the SPL or radio as I keep getting the error "FAILED (remote: signature verify fail)" this is so frustrating and I really need my phone . I am not smart enough to fix this so if someone could PLEASE help i would be greatly appreciative, thanks.
In fasboot I have the little processor photo with a red cross and the following info.
SAPPHIRE PVT 32A SHIP S-ON H
HBOOT-1.76.008(SAPP10000)
CPLD-12
RADIO-6.35.08.29
Nov 3 2009, 15:56:29
***Update***
Now I can only get into fastboot, even when I just turn the phone on. Please view this link of the photo of my phone to see what I mean, thanks.
http://i43.tinypic.com/2n1ylwk.jpg
I dont think you bricked it as long as you can enter fastboot..
Actually I dont know what you should do.. hopefully someone can help you.
Good luck
Screwing around with different radio versions almost guarantees a bricking if you don't know what you're doing.
I got your fastboot info, but what exact phone is it?
MicroMina said:
I dont think you bricked it as long as you can enter fastboot..
Actually I dont know what you should do.. hopefully someone can help you.
Good luck
Click to expand...
Click to collapse
Hi MicroMina,
Thanks for the reply. I hope someone can help me too im really stuck here. I have attached a photo in my first post, not sure its even fastboot anymore I can access
kbeezie said:
Screwing around with different radio versions almost guarantees a bricking if you don't know what you're doing.
I got your fastboot info, but what exact phone is it?
Click to expand...
Click to collapse
Hi kbeezie,
Its a HTC Magic 32A. I got it on a plan from Three(hutchinson) Australia.
My phone was working fine up until I used the radio and SPL for this topic
http://forum.xda-developers.com/showthread.php?t=605239
I was trying to downgrade(revert) when the problem happend. Updating/reverting had the same outcome which is where I am at now, thanks
ddmmh said:
Hi kbeezie,
Its a HTC Magic 32A. I got it on a plan from Three(hutchinson) Australia.
My phone was working fine up until I used the radio and SPL for this topic
http://forum.xda-developers.com/showthread.php?t=605239
I was trying to downgrade(revert) when the problem happend. Updating/reverting had the same outcome which is where I am at now, thanks
Click to expand...
Click to collapse
Well you can probably try to revert the phone back to it's original RUU:
http://forum.xda-developers.com/showthread.php?t=659403
There's a Hutchinson, Au one on the list.
kbeezie said:
Well you can probably try to revert the phone back to it's original RUU:
http://forum.xda-developers.com/showthread.php?t=659403
There's a Hutchinson, Au one on the list.
Click to expand...
Click to collapse
Hi kbeezie,
Thanks for the reply but I already tried to do that but i keep getting the errors "the ROM update utility cannot update your android phone" and
"please get the correct ROM update utility & try again". . Long story short up until 3 days ago I was using the Aus hutching RUU from that post. It was unhackable up until 2 days ago when there was a solution for the spl.0009-0010. I applied the method to revert to a non perfected SPL( i believe its called) i had root/recovery.. i even played around with a few roms but ultimatley i wanted to use the superD rom so I had to revert back to an old radio and SPL and thats when all this nightmare began, any other suggestions?? or any other info I can provide for you? Thanks.
ddmmh said:
Hi kbeezie,
Thanks for the reply but I already tried to do that but i keep getting the errors "the ROM update utility cannot update your android phone" and
"please get the correct ROM update utility & try again". . Long story short up until 3 days ago I was using the Aus hutching RUU from that post. It was unhackable up until 2 days ago when there was a solution for the spl.0009-0010. I applied the method to revert to a non perfected SPL( i believe its called) i had root/recovery.. i even played around with a few roms but ultimatley i wanted to use the superD rom so I had to revert back to an old radio and SPL and thats when all this nightmare began, any other suggestions?? or any other info I can provide for you? Thanks.
Click to expand...
Click to collapse
If you had it working... why did you bother to flash the radio?
kbeezie said:
If you had it working... why did you bother to flash the radio?
Click to expand...
Click to collapse
Because to run the superD rom you need to have old radio and spl. As soon as I went to revert i started having the problems of not getting into recovery and the phone hanging on the htc magic and rebooting in a loop. At that point in time the fastboot didnt have a lock on it(see picture in first post) When i tried to use the RUU is when I REALLY started having big problems and the fastboot had that little lock image and now the only thing the phone does is go into fastboot no matter if i power on or hold home and power or volume and power... hope this sheds a bit more light on the situation thanks
ddmmh said:
Because to run the superD rom you need to have old radio and spl. As soon as I went to revert i started having the problems of not getting into recovery and the phone hanging on the htc magic and rebooting in a loop. At that point in time the fastboot didnt have a lock on it(see picture in first post) When i tried to use the RUU is when I REALLY started having big problems and the fastboot had that little lock image and now the only thing the phone does is go into fastboot no matter if i power on or hold home and power or volume and power... hope this sheds a bit more light on the situation thanks
Click to expand...
Click to collapse
I never had to deal with the RUU screen, and googling isn't revealing any new info. There's a good chance you effectively bricked the phone. The only other thing I can think of in regards to RUU images, is if perhaps the phone wasn't originally intended for Australia (as such would be a different RUU image).
kbeezie said:
I never had to deal with the RUU screen, and googling isn't revealing any new info. There's a good chance you effectively bricked the phone. The only other thing I can think of in regards to RUU images, is if perhaps the phone wasn't originally intended for Australia (as such would be a different RUU image).
Click to expand...
Click to collapse
Hmm i see, does the SPL or radio determine this? Because like i said earlier I was using the latest RUU for hutchinson AUS which installed fine so I believe thats not the issue, the only problem was the perfected SPL which was finally cracked a few days ago. I never thought id actually brick my phone. Do you think theres nothing I can do? I tried googling a locked fastboot with no results either, is this the first problem of its kind that you know of?
While in fastboot; can you see the device from adb devices?
The safest thing to do would be to go back to the provider's code... just make sure it is the one for your model.
Carlos1970 said:
While in fastboot; can you see the device from adb devices?
The safest thing to do would be to go back to the provider's code... just make sure it is the one for your model.
Click to expand...
Click to collapse
Hi Carlos,
No I cannot see any devices when i CMD adb devices
When you say go back to the providers code do you mean the RUU? If so then ive tried this without success(last one not original). If not can you explain what you mean? thanks
...and you have the SDK and USB drivers installed; correct? I run WinXP and the ADB driver was not automatically installed; had to be installed manually.
"fastboot devices" should work; does that one show anything?
Wow, amazing. Don't try to help when you yourself are not completely sure about what you are saying.
ADB will NEVER recognize your phone in fastboot mode - hence FASTBOOT commands were created!
do "fastboot devices" while in fastboot , not "adb devices"
eyegor said:
Wow, amazing. Don't try to help when you yourself are not completely sure about what you are saying.
ADB will NEVER recognize your phone in fastboot mode - hence FASTBOOT commands were created!
do "fastboot devices" while in fastboot , not "adb devices"
Click to expand...
Click to collapse
The problem of course is those who don't know what they're talking bout wouldn't know that?
And yet they talk. (not directed at Carlos, he did in fact tell the OP to try fastboot devices as well, only later)
OK so I mispoke... The point I was trying to make was that the USB drivers had to be properly installed to get any output out of ADB.
Either through adb devices or fastboot devices it would be good to know if there is any comm over the usb port. If so; the best thing to do might be to reflash the provider's code.
So back to the issue. I found this thread from earlier in the year; I didn't go through all the messages but it is your same problem.
"My HTC Magic Stuck in RUU Screen after failed ROM upgrade"
Search for thread 625604
Hope it helps.
Carlos1970 said:
OK so I mispoke... The point I was trying to make was that the USB drivers had to be properly installed to get any output out of ADB.
Either through adb devices or fastboot devices it would be good to know if there is any comm over the usb port. If so; the best thing to do might be to reflash the provider's code.
So back to the issue. I found this thread from earlier in the year; I didn't go through all the messages but it is your same problem.
"My HTC Magic Stuck in RUU Screen after failed ROM upgrade"
Search for thread 625604
Hope it helps.
Click to expand...
Click to collapse
Hi Carlos and everyone thanks for your input.
I read through that post and all related posts but there wasnt really much of a solution.
I CAN access fastboot devices so i tried to flash a recovery via fastboot it starts to write then I get an error "FAILED (remote: 12 signature verify fail).
I think because I have S-ON? So i was thinking if there was a way to turn S-OFF would I be able to flash a custom recovery via fastboot??? Cheers
BUMP ^ ^
$20 into paypal account for anyone can give me a solution to fix this 100%.