Database Info

HELP I CAN'T GET DREAIMG.NBH Installed!

I just tried to downgrade my G1 from RC33 v1.42 + Radio Update 1.22.14.11!!!
I think I made the mistake and downgraded my bootloader from SPL_Hard to Original RC29_ SPL, because I was having trouble getting the file Dreaimg.nbh, recognized after booting holding camera + power buttons.
After downgrading from SPL_Hard to Orig RC29, I was able to boot holding the camera + power buttons, and the process started, but just before completing I got an error, FAILED TO UPDATE TERMINATING, and now my phone only reboots to the SPL screen with this showing:
DREA100 PVT 32B RUUNBH
HBOOT-0.95.0000
CPLD-4
RADIO-1.22.14.11
SEP 2 2008
I believe it's has to due with the Radio Update 1.22.14.11...
I'm going to try using QMAT and follow the Inst from that same thread. If that doesn't help can someone offer some help???

Update!!!
QMAT worked,
I was able to follow the instruction from this Post:
http://forum.xda-developers.com/showthread.php?t=485364&highlight=QMAT
Only thing I did different was to use another G1 instead of WinCE dev.
Still Please Post replies on how I should have downgraded from RC33 1.42 + Radio-1.22.14.11, because I thought I lost my G1...

Haha I done the same thing. I was thinking brick when I done mine I downloaded a bad file so I had to buy a card reader to redo the file then update the phone.
Qtronix

Original Settings?

I'm not really much of a pro at hacking my phone, since I've only hacked my MyTouch3g twice. The first time, I ran a Hero ROM, which was pretty slow. The 2nd was JesterBlur, which is uberfast, but is lacking wifi.
I know this seem like a weird question, but is there a way to restore the MyTouch 3g back to it's original T-Mobile software after it's been unrooted?
It's not that I WANT to go back, since I'm quite content with Jesterblur, I just want to know a backup plan. Thanks~
[As a side note-- I unrooted my phone using the guide in TheUnlockr, and I have the recovery software below already installed.]
http://forum.xda-developers.com/showthread.php?t=530492

Here is a guide from the tmobile website
Remember using this guide will get you back to the default phone os
Download this http://rapidshare.com/files/269267171/SAPPIMG_Sapphire_TMUS_1.88.531.1_COC10_release_signed.nbh and rename it to sappimg.nbh
- Copy sappimg.nbh to your sd card but a goldcard may be necessary if you have changed your SPL.
- Power-off the mytouch
- Insert the goldcard or sd card depending on your SPL
- Power on while holding volume down (of fastboot your device and then press volume down)
- It should pick up the sappimg.zip and you should be able to flash it.
- Once the flashing is FULLY finished reboot your phone.
via: http://forums.t-mobile.com/t5/Operating-System-Software/How-to-unroot-your-MT3G/m-p/168918

[NOT WORKING] Switch 1.76.0007 'Perfected' SPL to 1.76.2007 "Engineering' SPL!!!

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.

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.

Need help!!! installed 32A radio on 32B phone

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.