Database Info

Restore magic to Out of box condition

Hope someone can help with a few things
i have a UK Magic on vodafone, updated to crb43
Then I wanted to try the google ion rom (not haykuro, the image released elsewhere) as it was faster and had voide dialing
I used the new-recovery to install it, booting it from fastboot rather than flashing it. I made a nandroid backup first.
Anyways, I wanted to go back to default rom and OTA updates, so thought i'd restore my backup.
\
I've done this, but had to flash the new haykuro spl...
My question is will i get OTA updates with this SPL?
I cant find the stock spl anywhere for download, whats the hard spl - does it exist for the magic or just the dream???
Basically i just want the simplicity i started with not bothered with root.

really? no one knows?

dazcox5181 said:
really? no one knows?
Click to expand...
Click to collapse
Hi dazcox5181,
The answer is a few posts below yours.
I haven't tried myself as I'm very happy with my rooted Magic.
http://forum.xda-developers.com/showpost.php?p=3857151&postcount=10

Thanks, I thought that might have something to do with it.
Now back to Voda system, data and recovery with the spl linked above. Should that now get me back to being tied to vodafones OTA updates?
I'm new to Android, so I'm not sure how much of a restriction / or not this is? Are OTA updates common/regular/likely to add anything worthwhile (well, I guess cupcake was...but you probably all had that anyway)

Thanks, with a bit more research I finally stumbled on the solution.
Had to restore to crb17 from the link on the thread above, and then flash the original recovery in fastboot, then the OTA update to crb43 worked perfectly!
Phew!
I'll probably re-root sooner or later, can't help but play around on this device :0 so much more to play with than my iPhone he he
Apologies if this thread annoys anyone who says I should have searched better to start with, I did, and read many threads but theres a lot to take in!
Anyways, maybe someone else has same problem and this might have helped

and to make it easier for future searchers could you compile a detailed list of step-by-step instructions for doing this? Could be handy for a wiki somewhere

OK, will add details later, but briefly
To restore to factory:
1) Download and follow instructions to flash the crios spl (one with older version reported)
2) Download and follow included instructions to flash the SFR CRB17 image using included recovery.img (boot dont flash it)
3) Download and flash original recovery image (again from crios) can be found at thread linked earlier in this one.
Reboot, and go through usual setup etc OTA update will be on its way
Be sure to remove any update.zip from your SD before attempting ther OTA update, ie before first boot if possible
It's actually really easy now I know how, and took about 20min in total (probably less)

Where do you get the SFR CRB17?

f34r said:
Where do you get the SFR CRB17?
Click to expand...
Click to collapse
Here : http://wiki.smartphonefrance.info/firmware-htcmagic.ashx

Is there no hope for 1.6 users on a UK voda magic?

Hi folks.
I am desperate to get Cyanogens mod on my phone but I can't downgrade to 1.5 because i'm on 1.6 with a UK vodafone Magic (32B).
Any chance a serious andoid expert could step in and tell me:
Will there be a new image made to fix this issue?
is there a method I will understand? It says on the Cyanogen Wiki that there has been "some success" with my version but I can't find where it says how to downgrade for my version
I keep hearing about gold card or summink but i'm a noob and I don't have the foggiest idea where to start.
Please help!! and try to make your responses understandable

Dont worry...
Hi there
I think is possible what you're trying to do, but in order to change your rom you don't need downgrading nowadays (HTC are not PSPs, hehe).
I have a magic from Vodafone ES, and what you have to do first is check your model, can be 32A (HTC) or 32B (Vodafone, less ram in cell phone), so you'll probably have 32B like me.
After this, you need Android SDK and drivers to connect your device usb, load a modified SPL via ADB/fastboot (there's a thread in the forum with the HBOOT collection, you need one of those in your cell in order to change the rom).
Summarizing:
1. check if 32B
2. get Android SDK to use the commands fastboot/ADB
3. replace SPL
4. continue with the cyano's wiki
I followed this: http://www.htcmania.com/showthread.php?t=74683 (sorry is in spanish and a bit outdated, but the apps you need like the SDK are in there, and you have some screenshots, you can skip the root part since cyano's mod is rooted already).
About the goldcard method, I dont know because mine hadn't had perfect SPL, I only had trouble with the usb driver, and downloaded HTC sync (look for it on google if you need) and adb/fastboot detected my device.
A good idea is to install a recovery image once you change your SPL, I personally recommend Amon_RA's recovery 1.5.2.
Last but not least, these explanations are the basics, I know it sounds like chinese to you but read more posts in the forum, there's a cyanogen flashing guide as well, with all the information and these steps you'll do fine.
Hope you'll succeed, let me know your issues

I do understand reasonably well but you cannot use the guide on here with a UK magic as the SAPPH.img file or whatever has an incorrect ID. it's at this point the process cannot be completed.
Thanks so much for your lengthy reply but in this case I believe my phone is unique and the problem cannot be be as easily resolved as you suggest. I must downgrade to 1.5.
Are any of the extreme android geeks able to shed light on this?

I can shed light on you as I have a Vodafone HTC Magic 32B. I used the instructions at the link below and got my phone back to Cupcake, but oddly enough I used the MyTouch instructions and searched online for a suitable sappimg.nbh file as the one they provided didn't work for me. Now I am running Qteknology MagicSense Hero ROM with working LEDs. Forget about ADB, SDK and the Goldcard method... I am sure you want the simplest way to unroot so you can get back to 1.5 and the reroot to whatever you like. Here it is: http://theunlockr.com/2009/10/15/how-to-root-a-donut-phone-android-1-6/

This is great news but I have tried that method with the sappimg.nbh and it says incorrect ID every time.
Are you using a UK vodafone magic then? If so, where did you find a SAPPIMG that worked?
Please try and remember!

It doesn't matter that your phone is a UK Vodafone Magic.. if you google sappimg.nbh and download a few until you get the one you need you will have your phone reverted back to it original state... ready to root. If you stop your search after one attempt you will not have done all you needed to do. You don't have to know any codes or get another SD card.. just put some effort into it from your computer. Google is your friend.

but being a bit of a noob to all this, surely trying sappimg files at random might risk bricking my phone? I heard there was a good sappimg for all but my version of the phone which is why I mentioned it.
Maybe someone on here has a sappimg known to work with my phone?
But yes, i'm off to do some intense googling.
Thanks

Hi
I have a UK Voda Magic and I followed this http://forum.xda-developers.com/showthread.php?t=579328 and worked perfectly for me

It truly is lovely of you all to try and help and I appreciate it but I suspect you have not read my comments properly.
Those of you that have commented here were only able to get it to work because you were flashing from/rooting from a 1.5 cupcake build. Once the OTA 1.6 donut update is on a UK magic it cannot be downgraded and so all comments thus far are superfluous. contrary to other comments it is necessary to flash SAPPIMG.nbh first and this does not work on my phone - incorrect CID.
Is there anyone on here that can help with MY issue?
Thanks.

Strange, because I have no issues flashing UK Voda 1.6 phones, just fastboot and use ADB to load recovery image, then flash whatever 32B ROM I like (Dwangs 1.17.1 is great). I did a work collegues before Christmas and his phone had never been modified, only received the OTA update from 1.5 to 1.6 around October time.

I'm on it. That's the way I used to flash roms back when i first got my magic. Now i've been thrown by all the simple guides to put cyanogen and I thought the sappimg method was the only way. I'll just download the sdk and get on my merry way

I don't understand what the issue is? I have a UK vodafone 32B and have been flitting between CM's mods, Hero mods backwards and forwards with no issues whatsoever?
I'm on CM's latest right now (well, a few back now 4.2.11 latest), just followed the instructions and it worked....?

I certainly did read your OP correctly and I also was on 1.6 when I followed the link I posted. In that link it has instructions on how to do it if you are on 1.5 OR 1.6

Started out with 1.5 Vodafone UK Magic which i've flashed many times using the fastboot boot cm-recovery-1.4.img method.
At one time i went back to stock 1.5 but let it update itself (OTA) to 1.6. Since then i've continued to flash new ROMs without problem.

Alfieg said:
but being a bit of a noob to all this, surely trying sappimg files at random might risk bricking my phone? I heard there was a good sappimg for all but my version of the phone which is why I mentioned it.
Maybe someone on here has a sappimg known to work with my phone?
But yes, i'm off to do some intense googling.
Thanks
Click to expand...
Click to collapse
hi alfieg
ive vodafone magic 32B with donut and perfect SPL, in present day, I tried all the guides and methods in many forums, without success, for example, if you follow the guide in wiki cyano, already the first step there are problems, how I try to update with sappimg. (cupcake 1.5) as the ends' update writes "main version is older," "update failed "... if you do not then a way to get cupcake is impossible to have root on magic 32b with donut and Perfect spl ....
Indeed in the wiki says, if you have donut Downgrading to 1.5 FAILED: HTC Magic Vodafone ES (Spain) (32B) Official 1.6 updated OTA "
wait a few geek we solve the problem ...

I don't see what the problem is. You should have been reverted back to 1.5 and flashing new ROMs. The instructions are simple.. someone else has done all the hard work.. all you have to do is download a file and hold your phone.

blackvyper said:
I don't see what the problem is. You should have been reverted back to 1.5 and flashing new ROMs. The instructions are simple.. someone else has done all the hard work.. all you have to do is download a file and hold your phone.
Click to expand...
Click to collapse
download a file, to make what? If you can not root for real?

Will you lot please listen to me!
There are two methods reccommended:
1) Flash the SAPPIMG.nbh to downgrade back to 1.5 - this does not work on a UK magic on vodafone 32B at all! It reports Invalid CID, update failed!
2) use the fastboot boot cm-recovery-1.4.img via the SDK - This does not work on my phone! - I have the device listed when I use "adb devices" so the drivers are ok but it hangs at <Waiting for device> when i try to fastboot boot cm-recovery-1.4.img!!!!!! No ammount of killing the server and remounting as per the cyano instructions works!!!!! in fact, it wont let me remount (Operation not permitted)!!!
If you don't understand please don't post. People who have not updated to 1.6 OTA and people who don't have a UK voda 32B - stop posting here.
Grrrr

No need to downgrade
Alfieg said:
Hi folks.
I am desperate to get Cyanogens mod on my phone but I can't downgrade to 1.5 because i'm on 1.6 with a UK vodafone Magic (32B).
Any chance a serious andoid expert could step in and tell me:
Will there be a new image made to fix this issue?
is there a method I will understand? It says on the Cyanogen Wiki that there has been "some success" with my version but I can't find where it says how to downgrade for my version
I keep hearing about gold card or summink but i'm a noob and I don't have the foggiest idea where to start.
Please help!! and try to make your responses understandable
Click to expand...
Click to collapse
I have a New Zealand Vodafone Magic 32B and they share the same Hboot 1.33.0004 (SAPP10000) SPL with the UK (and NL and AU) vodafone phones. That means they are VERY easy to load alternate ROMs onto. The horrible stuff many Americans and others have to go through to root their phones isn't required for us.
You do need to get the Android SDK installed and talking properly to your phone.
Assuming you have the SDK set up and you can see your USB-connected phone listed when you enter the "adb devices" command, then the rest should be easy. See the Cyanogen Mod wiki for the details. You want the section on "non-Tmobile 32B magics" on this page:
http://wiki.cyanogenmod.com/index.php/Full_Update_Guide_-_MT3G/Magic_Firmware_to_CyanogenMod
It starts with:
"Non-TMobile 32B Magics
If the above doesn't work for you, don't despair. Some non-US Magics are shipped with a fastboot compatible SPL installed. If you see 3 skateboarding androids when you boot to fastboot, you should be able to do the following:"
..............
This is the part you want to pay attention to, assuming you have the SDK installed properly. Our phones are actually MUCH easier to load others ROM on because we have those fastboot-enabled SPLs already in place and this is the first, BEST way for us to do it.
Whatever you do, do NOT flash the "Danger SPL". There is no need to for an HTC Magic with the Hboot 1.33.0004 (SAPP10000) SPL.
If you're hopelessly lost at this point, seek hands-on local help. You don't know enough to do this by yourself without risking screwing up. if no one can help you, then take your time. Learn the stuff you need to know....Being in a hurry is a great way to go wrong. I spent 3 months reading and thinking about it before I loaded my first ROM. Much of the advice is for the Dream / G1 or locked MyTouch3G or Magic 32B phone from telcos who lock them....and simply isn't relevant for the HTC Magic 32B from Vodafone. the single section I'm pointing you to above is all we need to get it done.
Finally, here is my own "simple guide" for getting loading alternate ROMs on a Vodafone HTC Magic 32B. This is about OUR phone...and should work if you work your way through it.
http://truthseekernz.blogspot.com/2009/11/simple-guide-to-loading-new-roms-on.html
You don't need to worry about "gold cards" and all that stuff. You'll be flashing an already rooted ROM and you will have backed up your un-rooted original load with "nandroid" before you change ANYTHING. That backup is your path back to the way your phone was before you rooted it by flashing an already rooted system ROM. in loading ROMs like Cyanogen's you're not baking a cake, you're buying one....so you don't need to know how to make one, you just need to know where to get one and how to serve it....if that analogy makes sense.
Simply, you start by: fastboot boot RA-recovery-1.5.2G.img:
Then, from the recovery menu of functions you do these steps:
1. Backup (nandroid)
2. Wipe system / data
3. Wipe cache
4. flash from any zip on sdcard (the one you want to flash today, you may have put several different ROM images in /sdcard)
5. reboot to brave new world.
6. Make a backup copy on your PC of the /sdcard/nandroid folder on your sdcard so you won't lose it accidentally if your sdcard is corrupted, lost or stolen.
Done.
To save time and let you backup / flash ROMs anywhere you happen to be standing, you can flash Amon-RA's recovery onto your phone or you can load it via fastboot every time and leave the default recovery in place. The very first nandroid backup you made will have backed up the factory recovery image as well as the factory system image as they were at the time you backed them up. So they can be restored if you want to at some point update them with an OTA update. I suspect Vodafone / HTC will be rolling out an Android 2.0 / 2.1 update to Magic phones at some point. If they don't that would be a black mark against them....something to remember when thinking about buying any future phone from anyone: "WILL THEY SUPPORT IT FOR THE SAME 2 YEARS YOU'VE SIGNED UP FOR".
If the answer isn't YES......then that's worth remembering. Vodafone / HTC's record so far is good. The last OTA update was barely 3 months ago.

Alfieg said:
Will you lot please listen to me!
There are two methods reccommended:
1) Flash the SAPPIMG.nbh to downgrade back to 1.5 - this does not work on a UK magic on vodafone 32B at all! It reports Invalid CID, update failed!
2) use the fastboot boot cm-recovery-1.4.img via the SDK - This does not work on my phone! - I have the device listed when I use "adb devices" so the drivers are ok but it hangs at <Waiting for device> when i try to fastboot boot cm-recovery-1.4.img!!!!!! No ammount of killing the server and remounting as per the cyano instructions works!!!!! in fact, it wont let me remount (Operation not permitted)!!!
If you don't understand please don't post. People who have not updated to 1.6 OTA and people who don't have a UK voda 32B - stop posting here.
Grrrr
Click to expand...
Click to collapse
Get latest version of fastboot binary. I had problems with original one and htc magic. Drop fastboot.exe into the sdk tools folder.
Reboot your phone holding back and power simultaneously.
Then plug usb cable.
in Dos prompt go to sdk tools folder and type "fastboot devices"
if your device is listed you are good to go.
then "fastboot boot cm-recovery-1.4.img"

[32A] Install official sense UI (3.05.401.3) without getting perfect SPL!

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.

**SOLVED** Consolidated Info to HOPEFULLY Root Rogers 3.05.631.7 ROM-updating via RUU

(If ROM installed via official HTC RUU- RUU_Sapphire_Rogers_WWE_3.05.631.7_R_release_signed_NoDriver.exe)
UPDATE!! **SOLVED** April 25, 2010
Download new RUU
http://www.multiupload.com/XQEH9NVGY7
Flash with Goldcard method http://theunlockr.com/2010/03/10/how-to-create-a-goldcard/
1. Download RUU linked above.
2. Install update using RUU.
3. Turn on phone and connect to computer.
4. Get RA recovery and SPL also linked above and drop them to sdcard root directory.
5. Run SDK: adb shell
6. Install recovery: flash_image recovery /sdcard/recovery-RA-hero-v1.6.2.img http://forum.xda-developers.com/showthread.php?t=561124
6. Turn off phone and turn on again holding Power+Home. RA Recovery should appear.
7. Flash zip from sdcard.
8. Use file: update-hboot-1762007-signed
9. Done. PSPL broken.
10. Build a shrine for orange_24
****************************************************
**Not Successfully Rooted: Feb. 2, 2010 (AFAIK)
I decided to start this thread because the info for again obtaining root, for those of us dumb enough to update to the official Rogers ROM 3.05.631.7 via the RUU, is all over the place in about a million different threads. My hope is that we can organize it all in 1 place.
At this point, yes, we all know we were impatient and newbs and everything else. Ok, lesson learned. So, lets move forward and try to get this thing rooted.
If you are a developer who has the talent to help root this ROM and have lost interest in the Magic or moved on to the Nexus One or Droid, we ask that you please try to spend a few moments on this and help out those of us who are really stuck here. Personally, I'm getting pretty desperate and thinking of even replacing the phone.
Please post what you've tried in attempting to again obtain root, your failures and hopefully successes.
*One Click Root: http://theunlockr.com/2009/08/29/how-to-root-the-htc-magic-in-one-click/ Cant' back up Recovery.img Error(Tried clicking the hidden Star next to "Back Up Recovery" and skipping this step...and just flashing recovery-RA-sapphire-v1.5.2H.img. Didn't work either) Tried with Amon_RA Hero recovery.img also, without success.
*Tried downgrading to Rogers' last official ROM via the RUU for (Rogers)_RUU_Sapphire_Rogers_WWE_2.17.631.2_release_signed_NoDriver.exe RUU would not let me proceed because the ROM was older than the one installed. Attempted several times both with and without a goldcard installed.
*ADB: Will see the device, initially, but a command of "adb remount" kills the connect. same with "adb root" **EDIT
*Fastboot: Error- Does not allow access
*Relentless Rooter: http://forum.xda-developers.com/showthread.php?t=556200 No luck obtaining root
*Fix Perfect SPL: http://forum.xda-developers.com/showthread.php?t=548218&highlight=create+gold+card With one GoldCard getting Update Fail error that SAPPIMG is older than one installed. When trying the other GC, get Update Fail Error that Model ID is incorrect. Tried 2 different micro sd cards, one Sandisk and one Patriot. The card was recognized by my pc after I was done creating the GoldCard, so unless I'm doing something wrong the GC was created properly. Is the goldcard.img supposed to dissapear or remain on the card after your copy/paste write/save to the sd card disk?
* Tried RUU for RUU_Sapphire_HTC_Europe_3.04.401.2_HTC_AT_test_signed_NoDriver.exe http://forum.xda-developers.com/showthread.php?t=625108 RUU would not let me proceed because the ROM was older than the one installed or Device ID was wrong. Attempted several times both with and without a goldcard installed.
*Tried RUU for RUU_Sapphire_HTC_Europe_3.05.401.3_release_signed_NoDriver.exe http://forum.xda-developers.com/showthread.php?t=621415 RUU would not let me proceed because the ROM was older than the one installed or Device ID was wrong. Attempted several times both with and without a goldcard installed.
*Tried RUU_Sapphire_HTC_Asia_WWE_2.53.707.2_SEA_test_signed_NoDriver.exe RUU would not let me proceed because the ROM was older than the one installed or Device ID was wrong. Attempted several times both with and without a goldcard installed.
I've probably tried a few more methods to obtain root. Those were all fails, too. I'll post the links, as well, when I find them again.
Hopefully this thread will lead us all in the right direction.
Here is the link to the same topic in the HTC Dream Forum-in case they find out something that might help us out: http://forum.xda-developers.com/showthread.php?t=625732

i guess its time to play doctor with my new phone from rogers and swap the board from my old one.....

considering nothing works, i think any new idea would be a good idea

novadoc said:
considering nothing works, i think any new idea would be a good idea
Click to expand...
Click to collapse
like i said my idea was to swap my old motherboard into the new phone

you can give it a shot
but personally, unless you know exactly what your getting into, i wouldn't mess with the hardware

novadoc said:
you can give it a shot
but personally, unless you know exactly what your getting into, i wouldn't mess with the hardware
Click to expand...
Click to collapse
i already did it lol im more of a hardware then software

I know it might be nothing but when the Rogers RUU unpacks the img file loads as sappdimg and not sappimg. I don't know if the extra d in there means anything or if its something that shows up later.

I also try every method above and not luck also...

is there a possible way of tricking the system... with a higher build number and SPL with a custom installation from files that I see from one of the post where rogers send the user some files because they were running Win7?

I think that's the problem
We have the highest spl# and its perfected
So until someone gets their hands on a higher version than ours that is imperfect or engineering...
We are SOL, although I am hopeful someone is working on this for us.

shael said:
i already did it lol im more of a hardware then software
Click to expand...
Click to collapse
Did it work?

I have an Rogers HTC Magic and I didn't apply any update from Rogers since I bought it on June 2nd.
It's very strange that "adb devices" doesn't see the device?
have you enable the "USB debugging" ?
That part should work (when the devices is started).

novadoc said:
Did it work?
Click to expand...
Click to collapse
pfft ya ofcourse it worked... i have my older motherboard with my old rom and my old info all i did was swap the screen and case.... done deal... 5 min job lol

Would someone please report the radio and SPL versions (for the result of the 3.05.631.7 update)?

feisty_noodle said:
would someone please report the radio and spl versions (for the result of the 3.05.631.7 update)?
Click to expand...
Click to collapse
apphire pvt 32a ship s-on h
hboot-1.76.0010 (sapp50000)
cpld-12
radio-6.35.10.18

feisty_noodle said:
would someone please report the radio and spl versions (for the result of the 3.05.631.7 update)?
Click to expand...
Click to collapse
apphire pvt 32a ship s-on h
hboot-1.76.0010 (sapp50000)
cpld-12
radio-6.35.10.18

Well, until it gets cracked, here's something that will make you feel a little better about being stuck on this ROM.
Google Search by Voice, installable .apk from Euro Android Market. Just run the installer through Astro, etc., and G Search by Voice is back on the Search button of your phone. You might need to launch the app first via the icon in the app tray, then reboot the phone to make the search button recognize its there. But it will be there.
http://www.eclosion-android.com/com.google.android.voicesearch.apk
BTW, not my link in case mods want to get involved.
Enjoy!

i think the first step would be to getting ADB working again
any ideas?

novadoc said:
i think the first step would be to getting ADB working again
any ideas?
Click to expand...
Click to collapse
I can used adb devices to see my connected htc magic.... but other function permission not allow...

Is this thread in the Dream Forum a path to follow to try, or just a good way to brick your Magic? I haven't fully read through it to see if this is to keep root, if you already have it and flash the Rogers Dream ROM for data/ or to regain root if you flashed the official Rogers RUU with a Dream. The post says should work on all Rogers phones, but i feel a brick coming on for me.
http://forum.xda-developers.com/showpost.php?p=5480955&postcount=416

RUU USB boot screen

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.