Database Users

No! I bricked my phone!!

I just rooted my Mytouch a couple days ago and everything worked perfect and i did it without bricking my phone. I was trying to get the supercsdiv4 rom, but i needed to flash the lateset radio and heres where the problem started. the radio tried to flash was 2.22.23.02. I used the recovery image to flash it and then when i rebooted the phone it stayed stuck at the splash screen and i cant get into fastboot or recovery anymore. it just boot to the splash screen and stays there. I know i cant get my phone back but i want to know what i did wrong so that i dont ever do it again. maybe it was because the radio i had was a 32a radio and this radio i tried to flash might have been 32b but im not sure why that wouldn't work if my phone is 32b
here was my system
pvt 32b
Hboot 1.33.2005
radio 3.22.20.17

have you tried taking the battery out for a bit.. relax a while, then put it back in and try to get into recovery mode (home and power)

this actually happened yesterday and my phone was off the whole time so it has had plenty of time to rest. My phone is truly bricked

well im sorry to hear that, but i have no idea what you did wrong, unless you did flash a 32a over a 32b or the other way around, im sure that could really mess up the phone.
may be a useless idea but have you tried a hard reset
1. With the phone turned off, press and hold the HOME and BACK buttons.
2. Briefly press the END CALL/POWER button while continuing to press the HOME and BACK buttons.
3. When you see the screen with the 3 Android
images, release the HOME and BACK buttons, and then press the TRACKBALL.
i have no idea if it will do anything but might as well explore EVERYTHING.

Similar Problem (Partial Brick?)
Not to take anything away from clint1225 but
I have a similar problem and didn't want to start another thread.
I tried unrooting my devices using the method
described at theUnlockr.com. Everything was fine up until I tried using
their sappimg file (said it worked for all old magics).
At the hboot stage, it found the sappimg but the update failed.
However, the magic now says:
SPL-1.33.0006 (SAP50000)
Radio- 2.22.19.261
Ship S-On G.
It's a 32A version.
I had an engineering spl and 6.35xx radio before I attempted to unroot.
Oh I'm not able to access recovery but I can access
fastboot (computer can't find it though under "fastboot devices")
Other than that, it's stuck at the first splash screen.
Any advice/tips?
Sorry for the long post and thank you.
Good luck to you too, clint1225!

UPDATE *Similar Problem (Partial Brick?)*
In the adb, the serial number
of the htc magic is coming
up under "fastboot devices".
However, if I try to
flash a recovery for example, the adb
returns "remote access not allowed".
I've read about the gold card method
but my phone won't boot up properly
(stuck at splash screen) and I can't
access recovery. Only fastboot seems to be
working.
Any help is greatly appreciated.
Thanks!

Take it for what it's worth coming from a newb. But from my understanding if you can reach your phone with Fastboot your a NOT bricked. But this is what I have heard here on XDA, I haven't proven this myself.
Check around and hopefully with fastboot you can get your phone back. Good luck.

I did the exact same thing a few weeks back. I flashed a 3.22 radio over my 2.22 radio, thinking it's an upgrade but after it reboots, it wont get past the logo screen. I spent the whole day trying to find ways to recover it but cannot find any. Thank god I have warrenty on it so I went to the Tmobile store, told them I updated it and when it restart, it got stuck on the logo screen. They gave me a new phone and told me dont f-up this one. Now I'm afraid of updating my phone to the 6.something radio.

Update *Similar Problem (Partial Brick?)*...again.
MasterColdSoul and koolpre,
Thanks for the tips and luck!
I figured it wasn't a total brick so I searched
the whole day on google and xda.
What I can tell you is that I now have a functional phone.
I used the rogers "mandatory" update (2 sappimgs) to
get my phone (rogers 32a) working again (boots fully).
However, I now have the SPL 1.76.0010 which means
I've lost root functionality and it's harder to get root.
But I could use the phone to make a gold card and get root again.
Boy I'm glad this worked! I should have learned my lesson
but I will probably try to root, hehe!
Thanks to google search and xda community!

koolpre said:
I did the exact same thing a few weeks back. I flashed a 3.22 radio over my 2.22 radio, thinking it's an upgrade but after it reboots, it wont get past the logo screen. I spent the whole day trying to find ways to recover it but cannot find any. Thank god I have warrenty on it so I went to the Tmobile store, told them I updated it and when it restart, it got stuck on the logo screen. They gave me a new phone and told me dont f-up this one. Now I'm afraid of updating my phone to the 6.something radio.
Click to expand...
Click to collapse
just because the radio starts with bigger numbers doesn't make it an update. 3.22 was the old radio and 2.33.23.02 is the latest radio so you were actually downgrading your radio and thats why your phone brick. Just letting you know because you seem to be under the wrong impression. Dont make that mistake again. just do a little research to find the latest radio.

Bricked?? Flashing Rogers 2.1 RUU over CyanogenMod

A bunch of people with rooted phones are reporting that when they attempted to flash the 2.1 RUU overtop of CM6 they would get a signature error during the update process.
It's looking like the SPL is getting changed to 1.76.0010 and the radio is getting changed to 6.35.16.19 after which the update hangs with the signature error. Either recovery is failing during flash or is not replaced with this RUU but either way recovery is dead. and the RUU won't complete.
My opinion is that Amon-Ra recovery for the Magic is still on there and won't work because it won't work with that SPL/Radio combination. I've had one person report to me that he received the signature error even when attempting to manually flash the Amon-Ra Hero version onto the phone.
Also from a couple of pics that I've seen, it looks like the phone is stuck in RUU USB mode.
So are they bricked or is there a way for them to breathe life back into their phones?

This happened to me... my phone is currently stuck on the RUU screen and shows:
SAPPHIRE PVT 32A SHIP S-ON H
HBOOT-1.76.0008 (SAPP50000)
CPLD-12
RADIO-3.22.20.17
Nov 3 2009, 15:56:29
It seems I can also send files with flashboot, but everything comes back as Failed (remote: 12 signature verify fail).
Any suggestions to get out of this? Or am I firmly in the bricked category?
Thanks!

for others that r looking to flash the rogers stock rom.
Would it work if we flash rogers's old 1.5 911 RUU over CM6 first, then flash the new 2.1 RUU?
Obviously the 2nd step will be straight forward, but how about the first step?

do u guys heard sth called goldcard? make one and run the ruu again.

i have the issue, i am trying with a glodcard but i have a problem to get the cid of the sd card. because the phone is briked ! adb is not working
i will keep you inform if i found any solutions
edit :still not working any other idea !!! i cant find the way to get cid of sd card without adb...
finnaly i got the glodcard but the RUU is still not working ! error bad signature !

bricked 32A magic - bricked?

Hello,
I´ve got an issue with htc magic 32a, I read similar topics, but decided as it´s an specific case, to open a new thread... Here´s the whole story:
Phone originally:
HTC Magic / sapphire (32A) from Tim Brazil (bstar502)
BOOT LOADER: 1.76.0007
VERSION: 1.5 / CUPCAKE
FIRMWARE: 3.03.527.3 / 63.18.55.06HU_6.35.07.29
well, rooted the phone, no problems about it, but couldn´t get recovery recovery-RA-sapphire-v1.7.0H_32A.img to work, then I saw that hboot 1.76.xxx should use recovery-RA-hero-v1.6.2.img, and so I did it. Marvelous, recovery now working, selected hboot_1.33.2009_32A.zip, and flashed it from sd. oh, while phone was still working, made him a goldcard (kingston 2gb).
all seemed fine, but phone did not boot up, instead was hanging on 'htc magic', but could still enter fastboot. so I had the terrible idea to flash Engineering SPL 1.33.2004, which made it hang even earlier, and no fastboot available.
as a last attempt, I got rom from same cid as phone is, put it on goldcard, and hoped it flash, but.... nothing! goldcard with sappimg.zip inside, I reset it holding vlm down, but it´s the same as pushing only power button (tim logo on screen, and hangs in there).
so, aware of the situation, I ask the ones who can answer me for sure: do this phone have any chance to revive with 'normal' tools, or only by jtag?
br

[Q] HELP - Magic 32a Bricked! weird + Bad

hi,
i need ur guys opinion,
story goes
i have Magic 32a unlocked version.
then i root it to android 2.2.1 using the old radio / hboot combo.
then, i thought i want to update to android 2.3.1
now here is where the problem begins.
i accidently flashed the 32b radio on the phone. now the phone wouldnt go past the HTC Magic logo.
to fix this, i download the mytouch3G sappmig.img file and completely flash the phone over.
when i open fastboot it still using the 32b radio / hboot but this time the os loaded fine.
i install superandroot and superoneclick on the phone to root it
after rooting i tried flashing 32a radio / hboot but it say not allow.
next step i tried installing custom recovery and finally manage to do it using the flashrec app. i installed 32a recovery but it failed to boot it. i tried installing 32b recovery and it run fine.
now from the recovery itself i tried flashing 1.76 radio and the recovery unpack the file just fine. but when it says reboot, the 'Box with arrow and phone outside' image appear for a sec and then dissapear.
after that my htc magic is completely dead. pressing any button, pluging in usb cable or charger yield no effect (like a brick)
have i completely bricked my phone? please help.

Sad to say this, but yes.
You just had a bad radio flash...
Try JTAG.

i tried again after leaving the phone overnight, these are the only thing iam able to do with the phone:
trackball + power = blue led
long press power = led blink red once
plug in charger = battery charge indication light on, orange and then yellow indicating the battery is full.
and thats about it. no other button combo works. and fastboot devices and adb devices booth shows no device.
anyone doing this JTAG repair service?

bump...
im having the same problem...just posted my issue here: http://forum.xda-developers.com/showthread.php?t=959938
i have the blue LED as well...
i googled how to make a JTAG cable...but its really past my level of competence...
were you ever able to get your phone fixed?

you found any solid step by step guide to make the jtag? please post the link here. i want to explore further. tq.

i was having the same problem...initially all went well, manage to change the from SHIP S-on to ENG S-off. i brick my device right after updated the rom to froyo and thereafter unable to boot. everytime i booted my magic, i only sees the RUU (fastbot) page. i cant do adb command. luckily the fastboot flash command still work.
i have try flashing with a lot of different images but always got stuck @ either
FAILED (remote: 42 custom id check fail) or FAILED (remote: 12 signature verify fail). never go beyond that...after going thru so much hassle of finding the right image, i finally manage to get it up and running. it flashes by ROM to enclair (2.1), good enough for me to use whatapp..
specification of my Magic is 32A S-O; radio 6.35.16.19; hboot 1.76.0010
this is how i "unbrick"
Download the SAPPIMG from shipped-roms.com, download Brasil_SAPPIMG_3.54.zip
place the file in android sdk folder, where fastboot resided.
make sure your device is fully charged...
boot your device and connect it to the usb, you will sees RUU USB.
type this command fastboot flash zip XXXXXXX.zip
i hope this help...

Is this HTC Magic bricked?

Hello,
I recently tried to update the spl/radio to use a new rom on my HTC Magic 32A and after updating the spl the phone just hangs on the "HTC Magic" screen. Fastboot or Recovery wont start if I hold the buttons. Was just wondering if it is bricked or if it is possible to fix via cmd or so? I read alittle on jtag but I think if it came down to that Ill just buy a new phone cause this phone is not worth that much trouble.
I rooted the phone a year or so ago. First I had cyanogen but they dropped support so I switched too gingeryoshi but the wifi stopped working. It still connected to tmobile hotspot but I couldnt tether or connect to my wifi. So I thought of putting on Froyodragon. I updated too HBOOT-1.76.2007 but then it just hanged on reboot.
Thanks for any input.

Turn phone off (if you have bootloop then remove battery and place it back after 10-20 sec)
Turn on by pressing Back + Power - it's fastboot-mode
Write first 5 rows of info (all symbols are important)
If you do not have Android Sdk Tools configured - do it
Additionaly search for fastboot.exe - this utility can be absent from sdk tools
Connect phone to pc when it in fastboot-mode
Run
Code:
fastboot getvar cid
fastboot getvar cidnum
fastboot getvar version-main
Sent from my A7-040 using Tapatalk

hello,
I tired back+power, power+vol down, and power+home, they all just sit at the "HTC Magic" screen.

Did you remove battery before try and placed it back? If yes and any combination did not help -> 'brick'. Only JTAG can help.
What ROM did you have before?
And what ROM did you update?
There are no bricked phones when 32A phone updating with 32A official ROM. I don'y understand how you bricked your device.
Even if hboot updated but radio did not - there are some chances to restore...
Tell us how it happened?

same problem
Sir im also facing the same problem like this person is facing:
I guess that I've bricked my HTC magic phone. actually it was working fine but after when i flash Hboot file named (ISO-8859-1__STOCK-HBOOT) on it.
my device stop functioning not any key is working phone its not coming up in hboot loader screen by pressing vol down key+power key, not even in recovery mode. by pressing home key+ power key.
but if i press vol down+power key its not showing any hboot loader screen but if i use command prompt after that and use fastboot devices command its shows the device like in machine language
just like this:
D:\adb\tools>fastboot devices
?╞ñ?¿╥§?4:¶♫ fastboot
here are the details of my mobile. is there any way to fix this issue?
HT03VPB03044
SAPPHIRE PVT 32A SHIP S-ON G
HBOOT-1.33.0013
CPLD-13
RADIO-2.22.28.25
OCT 21 2009, 22:33:27
android 2.2.1
baseband version
62.50sj.20.17u_2.22.28.25
kernal version
2.6.32.9-g94b855e
[email protected] #1
buid number
3.56.531.1 CL300801 realase-keys
Sir i've also created gold card on my htc magic phone when it was working properly i've the image of gold card and the same card 512MB micro SD card which i used to create the gold card before but i dont know how it will work on the phone as it is not going into bool loader or in recovery mode.
please help me. i heard that if i got correct RUU file for this device i can troubleshoot the problem but in stock rom no any RUU file is working on it.
I've already tried there RUU ROM on this device:
RUU_Sapphire_T-Mobile_US_2.10.531.3_release_signed_NoDriver
RUU_Sapphire_T-Mobile_US_2.10.531.4_release_signed_NoDriver
RUU_Sapphire_T-Mobile_US_3.12.531.1_FRG83D_release_signed
RUU_Sapphire_TMUS_1.94.531.1_DMD6_release_signed_N oDriver
i request all the XDA member to help and troubleshoot this problem.
regards
Sandeep Deol

5[Strogino] said:
Did you remove battery before try and placed it back? If yes and any combination did not help -> 'brick'. Only JTAG can help.
What ROM did you have before?
And what ROM did you update?
There are no bricked phones when 32A phone updating with 32A official ROM. I don'y understand how you bricked your device.
Even if hboot updated but radio did not - there are some chances to restore...
Tell us how it happened?
Click to expand...
Click to collapse
Yes I removed the battery (only way i could turn it off). I stated most of this info in the first post but Ill try and state specifically what versions I had. When I first rooted I used Cyanogen Rom. It worked fine but they dropped support so I switched too Gingeryoshi. I dont remember what version. I tried to update it too 1.5 first but it didnt work but fastboot and recovery still worked so I decided to switch to a new rom instead and tried Froyodragon but it needed radio 6.35.16.19 and HBOOT-1.76.2007. So I wiped it then I did the HBOOT-1.76.2007 and after installing and rebooting is when it stopped working.

Crap, I just did this too... got a yellow arrow coming from a box onto an Android. I flashed a mismatched 6.35 radio (I guess?).
Can't boot to fastboot--can only boot to blue light mode (trackball+power) and phone will charge if connected by USB--but is never recognized by ADB or fastboot.

jmdsdf said:
Crap, I just did this too... got a yellow arrow coming from a box onto an Android. I flashed a mismatched 6.35 radio (I guess?).
Can't boot to fastboot--can only boot to blue light mode (trackball+power) and phone will charge if connected by USB--but is never recognized by ADB or fastboot.
Click to expand...
Click to collapse
Wait 5-10 minutes, "yellow arrow coming from box" equals unpack and flash. Phone should finish this process.
Try to load into hboot-mode: turn phone off (remove battery and place it back if bootlooping), then turn on by pressing Volumedown + power
In this mode you can flash full official rom in sappimg.zip format (or sappimg.nbh if you have 32b magic)
If phone doesn't load into any mode (except trackball + power) - then you have brick and only jtag can help.
Sent from my A7-040 using Tapatalk

But, it goes to a black screen about ten seconds after that.. sadly I think it needs to be jtagged and i will just give it away for parts.
I also tried the sapphire image trick, no luck.

those all sound like bricks..

problem with 32b - looping after rom.
Believe me, I tried a lot here and on google before posting here.
I tried to install a ROM on my htc magic 32b and certainly was not what I should.
Information from my device:
SAPPHIRE PVT 32B SHIP S-ON G
Hboot-1.33.0013 (SAPP30000)
CPLD-10
RADIO-2.22.28.25
OCT 21 2009,22:33:27
I've read very, very much. I read that I have to change the SHIP for ENG.
Also read about ruu, but I found a will for my device, nor know how to run.
First of all, my phone is only on LOOP. I can normally access the fastboot USB.
But does not accept commands, I believe it because of S-ON.
I do not know how to install an img it to get S-OFF.
Could someone help me get back my life device?
Thank you and with the help of google translator.

huahua!!!!
No one post about my problem...