Database Info

The G1 Night Light (READ FIRST IF YOU BRICKED YOUR PHONE)

Many people complain that they have "bricked" their phones when they really haven't. This thread will hopefully help reduce the questions on all of our useful threads.
How to tell if your phone is bricked:
1.) When you try to turn it on, nothing happens?
2.) Camera+Power does nothing.
3.) Home+Power does nothing.
4.) You flashed the SPL BEFORE the radio
If you answered yes to any of the above 4, you are bricked. You probably need a new board in the phone. Read more here: http://forum.xda-developers.com/showthread.php?t=516440 It has been confirmed that you WILL brick your phone if you attempt to downgrade your radio after flashing the new SPL. Not sure why you would want to anyways...
How to tell if you just need to re-flash:
1.) Your phone is stuck on the g1 logo
2.) Your phone is stuck in a boot loop
3.) Home+Power boots into recovery
If you answered yes to the above then you are NOT bricked. You have the G1 Night Light. This is (usually) a very easy fix.
The usual scenario is: You just upgraded your radio and/or the SPL on your phone and now you are trying to turn it on with no luck.
How to fix: After you upgrade your radio and/or SPL, you need to wipe a rom on the phone. For a plain almost stock feeling rom, checkout http://jf.andblogs.net/2009/05/24/jfv151-images-are-out/ if you are looking for hero, checkout the tutorial at g1upgrade.com.
I have also noticed when you flash hero, it will stay on the g1 logo for 5 or 6 minutes and then it'll finally start loading. Make sure your not being impatient and give it several minutes if you have just flashed a rom.
Last step:
If you have installed a new radio, then spl, then a new rom and you STILL get the g1 screen. Try it all over again. You probably didn't do something right. You don't need to ask questions in 30 different threads, your issue is not unique. You just need to search for some answers.

*Saved for future posts*

Edit:

Thanks! Updated.

I flashed the SPL before the radio whenever Haykuro released the Hero ROM and I didn't brick my device. Guess that I just got lucky. Thank goodness I know better now. haha

it's possible you flashed the radio prior to the SPL, only a loooong ways back.

Another thing to try if you are having issues is:
su
rm -r /system/sd/*
I was stuck in a boot loop and a quick ext3 wipe did the trick. The command should be able to be ran from console or terminal. You may need to mount /system with:
mount -t -rw,remount -o yaffs2 /dev/block/mtdblock3 /system
You would need to type that in between the commands above . I ran across this in another post but i think this is a good spot for it too .

Duplicate post...

thanx
At least I know now how to tell if I bricked my phone or just flashed it badly thanks for this.

youneek said:
How to tell if you just need to re-flash:
1.) Your phone is stuck on the g1 logo
Click to expand...
Click to collapse
many people who flashed the new SPL before the radio are stuck at the G1 splash logo, but cannot get to recovery or spl bootloader / fastboot mode regardless of what they do, so this bit might be misleading...
they aren't technically "bricked" b/c it's loading the radio rom, but it never hands off to the SPL, so there is currently no way of reloading either of those to make the device do anything useful -- essentially a brick

alapapa said:
many people who flashed the new SPL before the radio are stuck at the G1 splash logo, but cannot get to recovery or spl bootloader / fastboot mode regardless of what they do, so this bit might be misleading...
they aren't technically "bricked" b/c it's loading the radio rom, but it never hands off to the SPL, so there is currently no way of reloading either of those to make the device do anything useful -- essentially a brick
Click to expand...
Click to collapse
This is exactly what happened to me, it was a brick, sent for repair and they replaced the mainboard.

I have fixed 2 phones that had no recovery and stuck at the g1 screen. If someone has this problem message me and I'll help you fix.

Good Job
Sorry this is off topic. But...
Thank you for this thread!
Ok,
By the way, has anyone figured out what The difference in the baseband is?? I have a U in mine...

youneek said:
I have fixed 2 phones that had no recovery and stuck at the g1 screen. If someone has this problem message me and I'll help you fix.
Click to expand...
Click to collapse
really? if it can't get to recovery / fastboot mode nobody has published a fix w/o a hardware swap.
what's your method?

I will buy a bricked one off ebay and post the steps I do to get it back. I can only fix the "Night Light", I can't fix a truly bricked phone (yet).

digital006 said:
This is exactly what happened to me, it was a brick, sent for repair and they replaced the mainboard.
Click to expand...
Click to collapse
How and where did you sent for repair and how much does it cost? I have a bricked MyTouch3G at this moment. Did HTC took it?

not bricked just weird!
ok been reading on here ,not sure if i need to just reflash everything or sd issuse?i put the new raidio,then spl on !then put jacxrom on my phone worked great!then ran for a day.then tryed cyanogenmod 4.0 and loaded fine but got force closed issues at the google sign in so i wipe and went to jachero 1.2 loaded fine went to logo android and then htc ,but then the screen went to blank .like the as said g1 night light .so i went back to jacxrom 1.3 it loaded fine got stuck in t mobile g1 screen .ok i flashed again same thing. but this is the part if i take my memory card out it will boot up just fine!then put memory card back in but lol all apps are missing have reinstall them. i wipe every time.i have the latest raidio 22.19.26I).,spl 1.33.2005 .also the jacxrom is running fine when phones on .so any help please thanks .also when i put the spl on it loaded then said reboot so i did. after went back to recovery at the bottom it said formatting cach... but was setting there for a while so took battery out then booted phone .was it suposse to say done or not ! hope dont make any mad thanks for the info

bump

hey help me plz i have big problem
i forget hit alt+w when i install SPL then i press alt+s when SPL install i out battery then i put it my mobile don’t want open and when i holding down the Home and Power button don’t open recovery mode and i holding the End key and the Camera button don’t open boot loader plz help me plz

You aren't going to get any help with sentences that atrocious. Can you be more clear?

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.

un-root a mt3g 1.2/fender

Hello...
I've been frantically googling and checking the forums, I have a mt3g 1.2 (3.5mm) that needs to be exchanged to t-mobile, I rooted following the stock fender w/ root method, and need to revert it back to the stock settings as shipped. So far, my search has turned up no resolve. I was hoping someone here could provide me with the proper sappimg.nbh to restore. I've got the one for the original MT3G, but it (as expected) damages touch-screen capabilities. Can someone please help?

As far as I know, it's not possible until T-Mobile releases an OTA update for either the Fender or MyTouch 3.5mm. That was explained in the rooting instructions here on XDA...

merlino211 said:
Hello...
I've been frantically googling and checking the forums, I have a mt3g 1.2 (3.5mm) that needs to be exchanged to t-mobile, I rooted following the stock fender w/ root method, and need to revert it back to the stock settings as shipped. So far, my search has turned up no resolve. I was hoping someone here could provide me with the proper sappimg.nbh to restore. I've got the one for the original MT3G, but it (as expected) damages touch-screen capabilities. Can someone please help?
Click to expand...
Click to collapse
If you use the stock rom http://www.theandroidkitchen.com/fileshare/MyTouch3g32A/?download=MT3G32AFender-1.0-fixed-signed.zip and then you should have touchscreen. It's only with custom roms that touchscreen does not work.

Couldn't you just flash the Mytouch splash image and turn in in like that?
It looks pretty stock after that.

shawn1224 said:
Couldn't you just flash the Mytouch splash image and turn in in like that?
It looks pretty stock after that.
Click to expand...
Click to collapse
... you got the splash image handy?

kbeezie said:
... you got the splash image handy?
Click to expand...
Click to collapse
you can find the stock mt3g splash screen if u search on here but not the fender one... i got the stock myt3g splash on my 1.2...

ceas909 said:
you can find the stock mt3g splash screen if u search on here but not the fender one... i got the stock myt3g splash on my 1.2...
Click to expand...
Click to collapse
That's what I'm saying though, no one seems to have the fender one. Far as the op's situation, might have tried flashing one of those "32A" roms, which obviously won't work at this point, probabbly best to just try the rom from my signature (the one linked as Rooted), which is basically the stock rom and touchscreen and all that should work.

kbeezie said:
That's what I'm saying though, no one seems to have the fender one. Far as the op's situation, might have tried flashing one of those "32A" roms, which obviously won't work at this point, probabbly best to just try the rom from my signature (the one linked as Rooted), which is basically the stock rom and touchscreen and all that should work.
Click to expand...
Click to collapse
yea he has a 1.2, so yea i think his best bet is to get the stock mt3g splash screen and the stock fender rom... the only problem is that between the fender and the 1.2 the build number is different..the 1.2 is 2.10.531.4 CL119339 release-keys where the fender is 2.10.531.3 CL111099 release-keys .... but a simple edit of the build prop could make it display the correct buid numbers in the about phone menu..

I've actually attempted to just replace the splash with the original mytouch splash. This can be achieved by applying a proper SPL that will allow it to be replaced... PROBLEM being that after repacing the SPL with the ones linked: theunlockr[.]com/2010/03/10/how-to-change-your-splash-screen/
Once this process is taken, the radio functions and all seems well, EXCEPT that now when I place calls, my speaker does nothing. Phones can receive the calls and hear me, but I hear nothing. the end result is to reflash the phone with the rooted rom, minus the mt3g splash... This part is where my frustration is kicking in as their guide claims this is specific for the fender/mt3g 1.2, but yet bricks the speaker somehow.
UPDATE!!
Click to expand...
Click to collapse
It appears that the guide on unlockr is wrong for this phone. I was successfully able to get the splash back on the phone by implementing the steps of adding the splash DURING the initial radio and recovery image restores, at which point the sappimg used is the engineering 2010. Once the splash was loaded at this point, I was able to continue with the install, install the rom, but a fresh install would *not* boot into the OS, just hung on a black screen after the animated "android" splash. Upon restoring a nandroid back-up, the phone booted to the OS in its formerly operational state, mt3g splash included.... I'm going to attempt a factory reset from the phones main options purely to see if it'll boot or hang on the black screen again.
Update 2.0
Click to expand...
Click to collapse
Methods were all successful, factory reset worked to bring the phone back to the android setup wizard WHILE retaining the splash screen with no blank screen as described earlier... Process was as followed:
Performing the unlockr guide; during the following steps:
fastboot flash radio radio.img
fastboot flash hboot hboot.nb0 (the 0 at the end of this line is a zero not an oh).
fastboot flash recovery recovery.img
fastboot reboot-bootloader
the phone is currently running the SPL for the Engineering SPL 1.33.2010... I modified the above process to reflect
fastboot flash splash1 splash.nb
fastboot flash radio radio.img
fastboot flash hboot hboot.nb0 (the 0 at the end of this line is a zero not an oh).
fastboot flash recovery recovery.img
fastboot reboot-bootloader
Recovered from the rooted fender stock image, which then took me to a blank screen. Recovered from a nandroid back-up, which restored the phone to my state just prior to (re)flashing. After nandroid backup is restored and successfully making calls, factory reset was done and test calls were successfully made from the freshly reset version of fender/wroot stock.... A bit hackish and unorthodox, but it answered the question I was so valiantly struggling to find resolve to.
It appears the stock fender /w root reverts the hboot version to the non-engineering, which functions fine with the speaker.... Hope this helps someone else who was in the same boat as me.

merlino211 said:
I've actually attempted to just replace the splash with the original mytouch splash. This can be achieved by applying a proper SPL that will allow it to be replaced... PROBLEM being that after repacing the SPL with the ones linked: theunlockr[.]com/2010/03/10/how-to-change-your-splash-screen/
Once this process is taken, the radio functions and all seems well, EXCEPT that now when I place calls, my speaker does nothing. Phones can receive the calls and hear me, but I hear nothing. the end result is to reflash the phone with the rooted rom, minus the mt3g splash... This part is where my frustration is kicking in as their guide claims this is specific for the fender/mt3g 1.2, but yet bricks the speaker somehow.
It appears that the guide on unlockr is wrong for this phone. I was successfully able to get the splash back on the phone by implementing the steps of adding the splash DURING the initial radio and recovery image restores, at which point the sappimg used is the engineering 2010. Once the splash was loaded at this point, I was able to continue with the install, install the rom, but a fresh install would *not* boot into the OS, just hung on a black screen after the animated "android" splash. Upon restoring a nandroid back-up, the phone booted to the OS in its formerly operational state, mt3g splash included.... I'm going to attempt a factory reset from the phones main options purely to see if it'll boot or hang on the black screen again.
Methods were all successful, factory reset worked to bring the phone back to the android setup wizard WHILE retaining the splash screen with no blank screen as described earlier... Process was as followed:
Performing the unlockr guide; during the following steps:
fastboot flash radio radio.img
fastboot flash hboot hboot.nb0 (the 0 at the end of this line is a zero not an oh).
fastboot flash recovery recovery.img
fastboot reboot-bootloader
the phone is currently running the SPL for the Engineering SPL 1.33.2010... I modified the above process to reflect
fastboot flash splash1 splash.nb
fastboot flash radio radio.img
fastboot flash hboot hboot.nb0 (the 0 at the end of this line is a zero not an oh).
fastboot flash recovery recovery.img
fastboot reboot-bootloader
Recovered from the rooted fender stock image, which then took me to a blank screen. Recovered from a nandroid back-up, which restored the phone to my state just prior to (re)flashing. After nandroid backup is restored and successfully making calls, factory reset was done and test calls were successfully made from the freshly reset version of fender/wroot stock.... A bit hackish and unorthodox, but it answered the question I was so valiantly struggling to find resolve to.
It appears the stock fender /w root reverts the hboot version to the non-engineering, which functions fine with the speaker.... Hope this helps someone else who was in the same boat as me.
Click to expand...
Click to collapse
Or you can just goto the thread in the link of my sig ("rooted"), you want to make sure when you're reading guides that they are for your specific phone, some people have bricked their fenders or 1.2 cuz they got the wrong radio/spl intended for the older MyTouch3G

I made sure to use the right guide on the unlockr, the problem came specifically from where they had the SLP change guide... Either way, problem is fixed now and it'll be in the hands of the t-mobile store tomorrow. If I ever doubtfully get a question about the root from them after it ships back, I'll play dumb and inquire if maybe someone else did it while it was waiting to ship

merlino211 said:
I made sure to use the right guide on the unlockr, the problem came specifically from where they had the SLP change guide... Either way, problem is fixed now and it'll be in the hands of the t-mobile store tomorrow. If I ever doubtfully get a question about the root from them after it ships back, I'll play dumb and inquire if maybe someone else did it while it was waiting to ship
Click to expand...
Click to collapse
i hope they dont catch the build number being different.. as i stated in eairler post the build nmbers in the about phone menu are different from the fender and the 1.2

ceas909 said:
i hope they dont catch the build number being different.. as i stated in eairler post the build nmbers in the about phone menu are different from the fender and the 1.2
Click to expand...
Click to collapse
In my experience most sales reps are completely ignorant of that kind of thing, changing the boot screen may be enough to make em go along with it. IF you're dealing directly with the company on the other hand that may be a different story.

It's being shipped back via the store under the 14 day buyers resource. I have had two of these so far, both have suffered from the screen oddly self-scrolling... Figure maybe a bad lot produced, as t-mobile tech support has not even heard of such a problem before. I finally settled on buying a nexus one, which arrives tomorrow. The store doesn't even check the phones out except to make sure all parts and accessories are contained in the box, there it will sit for (they said, roughly a week) before it's shipped back to T-mobile. By then, I figure liability of the phone is officially out of my hands.

merlino211 said:
It's being shipped back via the store under the 14 day buyers resource. I have had two of these so far, both have suffered from the screen oddly self-scrolling... Figure maybe a bad lot produced, as t-mobile tech support has not even heard of such a problem before. I finally settled on buying a nexus one, which arrives tomorrow. The store doesn't even check the phones out except to make sure all parts and accessories are contained in the box, there it will sit for (they said, roughly a week) before it's shipped back to T-mobile. By then, I figure liability of the phone is officially out of my hands.
Click to expand...
Click to collapse
I think you mean buyer's remorse, also I was under the impression that Limited Editions could not be 'returned' , merely exchanged or serviced.
If you don't have a contract, you could sell the phone once you put the working stock rooted rom onto it.

jesus... some of you really hurt my head over this phone.

So flashing the stock mytouch splash screen doesnt work if youre on a 1.2 or are most of you guys worrying because you have fenders?? Also can someone give me the mytouch splash screen???

You can find it here
http://theunlockr.com/2010/03/10/how-to-change-your-splash-screen/

PLEASE Help - I think i bricked my phone. [SOLVED]

Hi,
My phone was working fine till i tried to revert to old radio and spl to use the superD rom. Ive used many roms and all works fine. When i did the revert my recovery stopped working, so i tried going back to the higher radio and spl and still my recovery doesnt work, i press home and end call and insteasd of going to recovery it just sits there with the htc magic logo for 5 mins then reboots and loops. I have no OS on the phone now so I cant boot into O/S or recovery so I thought id try to install an RUU that I know lets me change the SPL and radio. I thought the only way would be in fastboot so I went into fastboot and loaded the RUU in windows and get the errors "the ROM update utility cannot update your android phone" and
"please get the correct ROM update utility & try again". Now my fastboot has a little picture of a processor(I think) with a red cross through it and now I cant even change the SPL or radio as I keep getting the error "FAILED (remote: signature verify fail)" this is so frustrating and I really need my phone . I am not smart enough to fix this so if someone could PLEASE help i would be greatly appreciative, thanks.
In fasboot I have the little processor photo with a red cross and the following info.
SAPPHIRE PVT 32A SHIP S-ON H
HBOOT-1.76.008(SAPP10000)
CPLD-12
RADIO-6.35.08.29
Nov 3 2009, 15:56:29
***Update***
Now I can only get into fastboot, even when I just turn the phone on. Please view this link of the photo of my phone to see what I mean, thanks.
http://i43.tinypic.com/2n1ylwk.jpg

I dont think you bricked it as long as you can enter fastboot..
Actually I dont know what you should do.. hopefully someone can help you.
Good luck

Screwing around with different radio versions almost guarantees a bricking if you don't know what you're doing.
I got your fastboot info, but what exact phone is it?

MicroMina said:
I dont think you bricked it as long as you can enter fastboot..
Actually I dont know what you should do.. hopefully someone can help you.
Good luck
Click to expand...
Click to collapse
Hi MicroMina,
Thanks for the reply. I hope someone can help me too im really stuck here. I have attached a photo in my first post, not sure its even fastboot anymore I can access

kbeezie said:
Screwing around with different radio versions almost guarantees a bricking if you don't know what you're doing.
I got your fastboot info, but what exact phone is it?
Click to expand...
Click to collapse
Hi kbeezie,
Its a HTC Magic 32A. I got it on a plan from Three(hutchinson) Australia.
My phone was working fine up until I used the radio and SPL for this topic
http://forum.xda-developers.com/showthread.php?t=605239
I was trying to downgrade(revert) when the problem happend. Updating/reverting had the same outcome which is where I am at now, thanks

ddmmh said:
Hi kbeezie,
Its a HTC Magic 32A. I got it on a plan from Three(hutchinson) Australia.
My phone was working fine up until I used the radio and SPL for this topic
http://forum.xda-developers.com/showthread.php?t=605239
I was trying to downgrade(revert) when the problem happend. Updating/reverting had the same outcome which is where I am at now, thanks
Click to expand...
Click to collapse
Well you can probably try to revert the phone back to it's original RUU:
http://forum.xda-developers.com/showthread.php?t=659403
There's a Hutchinson, Au one on the list.

kbeezie said:
Well you can probably try to revert the phone back to it's original RUU:
http://forum.xda-developers.com/showthread.php?t=659403
There's a Hutchinson, Au one on the list.
Click to expand...
Click to collapse
Hi kbeezie,
Thanks for the reply but I already tried to do that but i keep getting the errors "the ROM update utility cannot update your android phone" and
"please get the correct ROM update utility & try again". . Long story short up until 3 days ago I was using the Aus hutching RUU from that post. It was unhackable up until 2 days ago when there was a solution for the spl.0009-0010. I applied the method to revert to a non perfected SPL( i believe its called) i had root/recovery.. i even played around with a few roms but ultimatley i wanted to use the superD rom so I had to revert back to an old radio and SPL and thats when all this nightmare began, any other suggestions?? or any other info I can provide for you? Thanks.

ddmmh said:
Hi kbeezie,
Thanks for the reply but I already tried to do that but i keep getting the errors "the ROM update utility cannot update your android phone" and
"please get the correct ROM update utility & try again". . Long story short up until 3 days ago I was using the Aus hutching RUU from that post. It was unhackable up until 2 days ago when there was a solution for the spl.0009-0010. I applied the method to revert to a non perfected SPL( i believe its called) i had root/recovery.. i even played around with a few roms but ultimatley i wanted to use the superD rom so I had to revert back to an old radio and SPL and thats when all this nightmare began, any other suggestions?? or any other info I can provide for you? Thanks.
Click to expand...
Click to collapse
If you had it working... why did you bother to flash the radio?

kbeezie said:
If you had it working... why did you bother to flash the radio?
Click to expand...
Click to collapse
Because to run the superD rom you need to have old radio and spl. As soon as I went to revert i started having the problems of not getting into recovery and the phone hanging on the htc magic and rebooting in a loop. At that point in time the fastboot didnt have a lock on it(see picture in first post) When i tried to use the RUU is when I REALLY started having big problems and the fastboot had that little lock image and now the only thing the phone does is go into fastboot no matter if i power on or hold home and power or volume and power... hope this sheds a bit more light on the situation thanks

ddmmh said:
Because to run the superD rom you need to have old radio and spl. As soon as I went to revert i started having the problems of not getting into recovery and the phone hanging on the htc magic and rebooting in a loop. At that point in time the fastboot didnt have a lock on it(see picture in first post) When i tried to use the RUU is when I REALLY started having big problems and the fastboot had that little lock image and now the only thing the phone does is go into fastboot no matter if i power on or hold home and power or volume and power... hope this sheds a bit more light on the situation thanks
Click to expand...
Click to collapse
I never had to deal with the RUU screen, and googling isn't revealing any new info. There's a good chance you effectively bricked the phone. The only other thing I can think of in regards to RUU images, is if perhaps the phone wasn't originally intended for Australia (as such would be a different RUU image).

kbeezie said:
I never had to deal with the RUU screen, and googling isn't revealing any new info. There's a good chance you effectively bricked the phone. The only other thing I can think of in regards to RUU images, is if perhaps the phone wasn't originally intended for Australia (as such would be a different RUU image).
Click to expand...
Click to collapse
Hmm i see, does the SPL or radio determine this? Because like i said earlier I was using the latest RUU for hutchinson AUS which installed fine so I believe thats not the issue, the only problem was the perfected SPL which was finally cracked a few days ago. I never thought id actually brick my phone. Do you think theres nothing I can do? I tried googling a locked fastboot with no results either, is this the first problem of its kind that you know of?

While in fastboot; can you see the device from adb devices?
The safest thing to do would be to go back to the provider's code... just make sure it is the one for your model.

Carlos1970 said:
While in fastboot; can you see the device from adb devices?
The safest thing to do would be to go back to the provider's code... just make sure it is the one for your model.
Click to expand...
Click to collapse
Hi Carlos,
No I cannot see any devices when i CMD adb devices
When you say go back to the providers code do you mean the RUU? If so then ive tried this without success(last one not original). If not can you explain what you mean? thanks

...and you have the SDK and USB drivers installed; correct? I run WinXP and the ADB driver was not automatically installed; had to be installed manually.
"fastboot devices" should work; does that one show anything?

Wow, amazing. Don't try to help when you yourself are not completely sure about what you are saying.
ADB will NEVER recognize your phone in fastboot mode - hence FASTBOOT commands were created!
do "fastboot devices" while in fastboot , not "adb devices"

eyegor said:
Wow, amazing. Don't try to help when you yourself are not completely sure about what you are saying.
ADB will NEVER recognize your phone in fastboot mode - hence FASTBOOT commands were created!
do "fastboot devices" while in fastboot , not "adb devices"
Click to expand...
Click to collapse
The problem of course is those who don't know what they're talking bout wouldn't know that?

And yet they talk. (not directed at Carlos, he did in fact tell the OP to try fastboot devices as well, only later)

OK so I mispoke... The point I was trying to make was that the USB drivers had to be properly installed to get any output out of ADB.
Either through adb devices or fastboot devices it would be good to know if there is any comm over the usb port. If so; the best thing to do might be to reflash the provider's code.
So back to the issue. I found this thread from earlier in the year; I didn't go through all the messages but it is your same problem.
"My HTC Magic Stuck in RUU Screen after failed ROM upgrade"
Search for thread 625604
Hope it helps.

Carlos1970 said:
OK so I mispoke... The point I was trying to make was that the USB drivers had to be properly installed to get any output out of ADB.
Either through adb devices or fastboot devices it would be good to know if there is any comm over the usb port. If so; the best thing to do might be to reflash the provider's code.
So back to the issue. I found this thread from earlier in the year; I didn't go through all the messages but it is your same problem.
"My HTC Magic Stuck in RUU Screen after failed ROM upgrade"
Search for thread 625604
Hope it helps.
Click to expand...
Click to collapse
Hi Carlos and everyone thanks for your input.
I read through that post and all related posts but there wasnt really much of a solution.
I CAN access fastboot devices so i tried to flash a recovery via fastboot it starts to write then I get an error "FAILED (remote: 12 signature verify fail).
I think because I have S-ON? So i was thinking if there was a way to turn S-OFF would I be able to flash a custom recovery via fastboot??? Cheers

BUMP ^ ^
$20 into paypal account for anyone can give me a solution to fix this 100%.