Related
To those with HTC Magic on Vodafone UK, with SPL 1.33.2005.
***Quick note - if you have tried to do Haykuro's root access method and found out that the reboot command didnt work, then keep reading as you would have installed SPL 1.33.2005 at the beggining of his method!
if you want to check then turn off your HTC Magc, and boot up fastboot (back + power) then just look at the top and see what it says! it should read like this:
SAPPIRE PVT 32A (or 32B) ENG S-OFF H
HBOOT-1.33.2005 (SAPP10000)
CPLD-10
RADIO-2.22.19.26I
certain parts of the fastboot stuff wont be identical to mine but as long as it says the same as what is in bold and underlined above, then you'll be all good!***
I had the same issues as you with my magic, such as following all of the instructions by haykuro then when it came to #reboot all I got was a uid error.
What I did after was hard reboot my device, downloaded the GoogleION (revision 2) ROM (ion-signed.zip) and installed it, I now have root access!
I am not finding any trouble with this rom, bluetooth, wifi, gps and accelerometer are working great and as for the audio problems, I haven't noticed any. This build is wildly fast and no laggy keyboard, no waiting between closing huge sms threads or closing heavy apps, you can have voice search and amazon mp3 also super user whitelist is also preinstalled.
ROM DOWNLOAD HERE: http://www.droiddeveloper.com/hrbuilds/ion-signed.zip
Installation instructions for ION:
*Follow the same proceedure as before with haycuro's method then when the REBOOT command fails, hard reboot, (take out battery from phone to turn off then put it back in and turn device on)
*reconnect phone to your computer and transfer the ion-signed.zip to your sdcard, either by mounting the card to the pc via the phone or by adb push method, just make sure you rename it 'update.zip'
*Enter revovery mode (home + power)
*make a nandroid backup
*select wipe all data
*select update from sdcard
*let setup complete then hit home + power to restart into GoogleION R2.
It is required to wipe your phone else you will get a bad install or things won't work and that would be bad!
Make sure to copy your nandroid backup to your pc, and then to a disc or memory stick as you will need this if you botch up any future updates or if you want to return to Vodagroans crappy ROM.
PM me if you want more info, or preferably, email me at [email protected]
Emaling me would get a faster response as google mail comes straight to our phones! Hope this helps and enjoy GoogleION!
JamesRead
HTC Magic
GoogleION (r2)
Rooted
OverClocked 527.3Mhz
Custom Splash
dxTop - Carbon Glow
HTC Dream
Haykuro 6.0.1H
Rooted
Overclocked 467.2Mhz
Custom Splash
Excellent guide, i rooted my Voda UK HTC Magic with no issues though?
good thing you wrote this today.
I got the same problem, got nowhere with reboot, and as following not being able to su in terminal.
Will try this
HTC Magic with ION
Hi. Thanks for this guide. I was having similar issues to that described after following the normal method. All is working well except no WIFI. bluetooth is working though. Anyone else having this prob?
thanks.
link to ion file missing
Hi does anyone know where I can download the google ion signed file from the link posted above doesn't work anymore, tried seaching but comes up with hacked roms.
After flashing google ion r2 rom. i can't use wifi and bluetooth. How can i do this
Thank
G1-Jr4G0N said:
To those with HTC Magic on Vodafone UK, with SPL 1.33.2005.
***Quick note - if you have tried to do Haykuro's root access method and found out that the reboot command didnt work, then keep reading as you would have installed SPL 1.33.2005 at the beggining of his method!
if you want to check then turn off your HTC Magc, and boot up fastboot (back + power) then just look at the top and see what it says! it should read like this:
Click to expand...
Click to collapse
Thanks dude, with your post and some other tuts i managed to make my own tut in my head.
And guess what.
Works like a dream . It's that kind of magic
TY again.
I Did haykuro's on my Vodafone HTC magic AUS not UK (but maybe the same?)
at the end of the rooting, the reboot command, and I just turned the phone off and on.
After that, I was able to get the root # using adb sheel, but thru the terminal, i always got $.
I read somewhere else thaty I needed to install another su binary, so i followed that precedure and now it's ok.
noobie qu: does this procedure replace the deafult rom with a custom one ?
yes it will replace it.
joopje said:
yes it will replace it.
Click to expand...
Click to collapse
thanks
is the ION rom (I assume the one it is replaced with) based on the latest android (i.e. is it more or less advanced then the stock vodafone uk one I have now ?)
colonel said:
thanks
is the ION rom (I assume the one it is replaced with) based on the latest android (i.e. is it more or less advanced then the stock vodafone uk one I have now ?)
Click to expand...
Click to collapse
I find that it adds an extra Google Voice Search. Further nothing special. Different keyboard and some other minor thingies. make a backup first than whipe and flash
G1-Jr4G0N said:
To those with HTC Magic on Vodafone UK, with SPL 1.33.2005.
***Quick note - if you have tried to do Haykuro's root access method and found out that the reboot command didnt work, then keep reading as you would have installed SPL 1.33.2005 at the beggining of his method!
if you want to check then turn off your HTC Magc, and boot up fastboot (back + power) then just look at the top and see what it says! it should read like this:
...............................
SAPPIRE PVT 32A (or 32B) ENG S-OFF H
Custom Splash
Click to expand...
Click to collapse
just curious
my vodafone magic (uk) went fine through the rooting experience - my phone is a 32b
then I read a post that said there is a different root image for the 32A and the 32B, the image for the 32A is here:
http://forum.xda-developers.com/showpost.php?p=3972848&postcount=6
I wonder if this is the cause of the problem you mention
as its nice to be able to root and have the option of keeping the stock vodafone firmware
Hey,
i had problem rooting my Australian Vodafone magic too, but the problem is that the shell command could not find "reboot" command.
To fix this i have to manually create a symbolic link with reboot and than i could run the reboot.
is quite easy to fix if the you type "reboot" and an error appear saying unknow command.
just add the symbolic link to the same area as "sync" and it should work.
Cheers
Hello, i got a newbie question too. My phone specs are as follows:
- HBOOT-1.33.0004 (SAPP10000) : Sapphire PVT 32B SHIP S-ON G : CPLD-10 Radio 2.22.19.26I.
Has anyone got the same model and give pointers or instaructions how to root successfully?
Thanks
Hi htcmagic, I actually have the same SAPL number and everything else is exactly the same as yours.
I got it from Vodafone UK. I was just going to post the same question here.
So, we both have a 32B model and SAPL 1.33.0004. Can anyone please recommend a good rooting guide for this phone? I am having a very hard time locating one.
Thanks a lot!
PhoenixAG said:
Hi htcmagic, I actually have the same SAPL number and everything else is exactly the same as yours.
I got it from Vodafone UK. I was just going to post the same question here.
So, we both have a 32B model and SAPL 1.33.0004. Can anyone please recommend a good rooting guide for this phone? I am having a very hard time locating one.
Thanks a lot!
Click to expand...
Click to collapse
I have used this page
http://www.androidiani.com/dispositivi-android/cellulari/guida-root-del-magic-2543
and translated to english and worked.
the only line i havent executed is
"adb shell flash_image recovery / sdcard / recovery-new.img"
because i ma not interested putting roms on my magic.
NOTE: THIS MIGHT NOT WORK IF YOU INSTALLED THE HTC RUU USING A GOLD CARD IN THE FIRST PLACE... I'M LOOKING FOR TESTERS TO CONFIRM THIS.
I tried this when I first ended up with 1.76.0007, and it worked, but I didn't want to take a chance trying it again. I thought it was just a coincidence or my eyes were playing tricks on me. I was scared that I would brick my phone...
I finally got the guts to try it again and it worked!
Here's how...
You'll need:
- HTC 2.53.707.2 Test Build SAPPIMG.zip (Thanks Amon_RA!!)
http://rapidshare.com/files/267446145/2.53.707.2_-_sappimg.zip
- 1.76.2007 'Engineering' SPL
http://rapidshare.com/files/313034025/update-hboot-1.76.2007-signed.zip
- 6.35.07.29 32A Radio Image
http://rapidshare.com/files/313035429/radio-6.35.07.29-32A.zip
- Amon_RA Hero Recovery
http://forum.xda-developers.com/showthread.php?t=561124
- Gold Card
http://forum.xda-developers.com/showthread.php?t=572683
Caveats!!!
- Your splash screen will be changed to the HTC MAGIC screen and not your wireless provider's screen. I know of no way to change this.
- This might brick your phone... I was sweating bullets when I was running this on my phone because I wasn't sure it would work, and I'm still not 100% sure this will work for everyone. YMMV
Steps:
- Create your Gold Card! This is not just a suggestion. You need a proper gold card before starting. I used the card that came with my phone and it worked fine.
- Back up whatever you can from your existing setup. You can't go back and can't recovery anything here. Google sync should backup most of your stuff though.
- Shut off your phone and put the 2.53.707.2-sappimg.zip file on your gold card. Make sure it's named 'sappimg.zip'. Put the gold card in your phone.
- Turn on your phone using VolDown and Power. It will boot into HBOOT mode and within 10 seconds will scan your SD card. Do not press anything at this point! It will find SAPPIMG.zip only if it is named SAPPIMG.zip and not SAPPIMG.zip.zip... Get it? As it's loading SAPPIMG.zip it will show a blue progress bar on the right hand side of the screen.
- It will then check that SAPPIMG.zip is not corrupt.
- When prompted 'Do you want to start update?', press in on the trackwheel (Action key).
- The process will update the SYSTEM, USERDATA, BOOT, BOOTLOADER (SPL), RADIO_V2, RECOVERY and SPLASH.
At this point, you now have 3.22.20.17 32A Radio image and 1.33.2010 Engineering SPL. You can now flash any 32A Recovery and ROM and carry on like nothing happened and you didn't make a big mistake by flashing the HTC RUU. Next time don't be so impatient!
If you decide to stick with this Radio and SPL then I suggest flashing the Amon_RA 32A Recovery and picking a 32A ROM to run.
If you want to flash new HTC 3.03 ROMs using the 1.76.2007 Eng SPL and the new radio, then continue on. There are advantages to this, but at this point it's not for rookies.
Steps
- Download the recovery image, radio image and SPL (hboot) update into a folder of their own.
- Put the update-hboot-1.76.2007-signed.zip onto your SD card.
- Open a command prompt, navigate to the folder you saved all of the files in. This assumes that your Android SDK Tools folder is in your PATH environment variable)
- Boot your phone it fastboot by holding Back and Power.
- Once in FASTBOOT USB, type in these commands, hitting enter after each one.
Code:
fastboot flash radio radio.img
fastboot flash recovery recovery-RA-hero-v1.3.2.img
- Once it's finished, turn off your phone by pressing MENU.
- Start up your phone into recovery mode by holding Home and pressing Power.
- Apply the update-hboot-1.76.2007-signed.zip update.
- NOTE THAT THE RECOVERY REQUIRES YOU TO PRESS THE HOME KEY TO SELECT AN OPTION.
- Reboot your phone using the recovery option. Your phone will reboot back into recovery, and will format the CACHE. Don't worry about this, it's supposed to happen. If it doesn't boot back into recovery after a few minutes, pull the battery and power it on while holding the HOME key.
- Once it's booted into recovery mode, shut off your phone by pulling the battery.
- Start it back up into FASTBOOT mode by holding Back and pressing Power.
- You should now see the following on the screen:
Code:
SAPPHIRE PVT 32A ENG S-OFF H
HBOOT-1.76.2007
CPLD-12
RADIO-6.35.07.29
Aug 21 2009,18:19:15
If your phone doesn't display exactly this information, then you might have made a mistake along the way and should consider yourself lucky that your phone boots at all. Try again from the beginning.
At this point, you can enter the recovery menu and run the CursorSense update.zip from:
http://forum.xda-developers.com/showthread.php?t=592856
This was probably the closest I came to bricking my phone, but I'm sure it works now.
Good luck and happy rooting!
That won't work because if you Flashed via RUU it'll say that your version is older.
If you only flashed SPL/radio and not rest of the ROM i guess it could work.
it can break the Perfected SPL?
When i was flashed the sense-ui by htc?
mkrle said:
That won't work because if you Flashed via RUU it'll say that your version is older.
If you only flashed SPL/radio and not rest of the ROM i guess it could work.
Click to expand...
Click to collapse
You might have a point here... I thinks that maybe I didn't think this through entirely...
Would anybody be willing to test? Just to see...
Thanks,
Quite tempting to try, as I did flash via the RUU. Will look into it.
cursordroid said:
You might have a point here... I thinks that maybe I didn't think this through entirely...
Would anybody be willing to test? Just to see...
Thanks,
Click to expand...
Click to collapse
Main Version is older....
I've tried it, didn't work, but again who knows it might work for someone. There was a guy who said he got s-off SPL from a regular RUU so you never know.
Main version is older...
Main Version is older
I tried it on HBOOT-1.76.0007 (SAPP10000)
Hong Kong Sense Update from 17/11/09
Same problem NOTHING NEW:
Main Version is older
main version is older, flashed with RUU
i know 2.53.707 sappimg.zip file saved a few people, they also flashed official ruu, but get spl info like this: 1.76.0007(SAPP*****), and s-off.
but for most of us, we get this: 1.76.0007(SAPP10000), and s-on. therefore, we trying to use 2.53.707 sappimg.zip file and get "main version is older, update failed". and, if we use fastboot, it says "remote: not allow".
the only difference is the SAPP model text following 1.76.0007. if it's *****(all "*" symbols, not means any key), security is off, no version check, and it work! if it's 10000(maybe 50000 is also the same but i'm not sure), we stucked at version check.
so, what can we do...
tigerdigi said:
i know 2.53.707 sappimg.zip file saved a few people, they also flashed official ruu, but get spl info like this: 1.76.0007(SAPP*****), and s-off.
but for most of us, we get this: 1.76.0007(SAPP10000), and s-on. therefore, we trying to use 2.53.707 sappimg.zip file and get "main version is older, update failed". and, if we use fastboot, it says "remote: not allow".
the only difference is the SAPP model text following 1.76.0007. if it's *****(all "*" symbols, not means any key), security is off, no version check, and it work! if it's 10000(maybe 50000 is also the same but i'm not sure), we stucked at version check.
so, what can we do...
Click to expand...
Click to collapse
yes, i also found some person get this: spl info like this: 1.76.0007(SAPP*****), and s-off, if in this state, they can flash any rom/spl/radio.
can anybody find how to go to this state? if we can, we can do anything.
I dont know any thing further other than I got 0007 and s-on
so, all I can do is bump...
I have SAP***** for some time, even before i flashed 1.76 SPL but it's s-on, so i think it's not directly related.
P.S. I think i got SAP**** by playing around with different radios and all i can say is *don't* change (especially downgrade) radio unless you're sure what you're doing and/or have a matching SPL.
still no luck searching for a root cure for 1.76.0007
I accidentaly posted this to another thread (http://forum.xda-developers.com/showpost.php?p=5196720&postcount=7) although it was meant to be posted here:
I was missing the Android Market wich didnt come with the Singapore RUU so just downloaded the the HK RUU, ran it with a gold card (dont know if thats really neccesary) and got Market.
The point being - if people are on the Singapore official update, would it be somehow possible to "patch" the HK RUU files from the temporary folders where it stores the files for the update? To say, replace the original HBOOT with an ENG HBOOT (possibly *.2007?)?
Since Singapore rom version is lower than the HK one..:
Singapore: ROM Version: 3.03.728.4(For Indonesia, Malaysia& Vietnam only)
HK-E: ROM Version: 3.03.990.6
..possibly it would skip the "wrong main version" or whatever it says during the update..?
Am I onto something here?
No because the (zip) files are signed and perfect SPL won't accept flashing them if they are modified.
so is there a newer spl yet?
jamesyb0i said:
so is there a newer spl yet?
Click to expand...
Click to collapse
nobody, help we. amon_ra, and all the developers.. because don't help us??? we need help!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
We need either kernel exploit to get root, or HTC signed RUU with 3.x ROM and s-off SPL. period.
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.
Hi I would like to know if anyone out there knows the solution to my problem.
I have a HTC Incredible S. And I gained s-off and rooted it. I flashed clockworkmod recovery many times before. I used Android revolutionary's rom and Nik's Trinity Sensation XL rom before. Now I've recently flashed a new rom, which is the RunnyDroid ROM by the pvteam. ( http://forum.xda-developers.com/showthread.php?t=1374852 )
Now I found another ROM that I would like to tryout. But I can't seem to get my phone into HBOOT. I always used revolutionary to get my phone into HBOOT ( they'll detect your device and it'll say your phone is already S-OFF and then they ask if I want to download clockwordmod recovery which I usually type Y )
But after flashing the runnydroid's rom, whenever I type Y in revolutionary, the program will stop working and it'll say windows detect a problem or something like that. I can't seem to get into HBOOT. Any help please? I'd appreciate it loads! THANKS IN ADVANCE!
Hi,
So the post in the Incredible S section says:
5. Pull out the battery and wait 5 seconds. Put the battery back in again. (This step is needed in case fast boot is enabled..)
6. Press vol down+power. HBoot (white screen with 3 android logos at the bottom) should load.
This is what I do on my Sensation as well...
Hope that helps.
[Q] [FIXED] Problem getting back into HBOOT for HTC Incredible S
hey thanks! That totally worked for me and I have just flashed a new rom ( CoreDroid )
But now I seem to have a new problem, I can't detect any signal at all. When I looked for the network under mobile networks, it says error while searching for networks. Do you know how to deal with that?