Database Users

Tips for fixing a bad SPL flash - AKA phone stuck on G1 logo

Hi All,
So, today I tried installing Haykuro's latest SPL and ion rom, when low and behold, my phone was stuck at the G1 logo. Searching this and other sites offered no solution. I wasn't about to lose my hardware hacker cred and get a new phone... so, away I fiddle. I finally got the phone into recovery, after many reboots, and looong power/homekey presses. Once in recovery, I did the following.
put the hardspl update.zip on SD
Reboot, still frozen
wiped
rerun Haykuro's new SPL
DID NOT REBOOT - Wiped data
rerun radio firmware
Again, did not reboot - wiped data.
Pushed the ion firmware
Rebooted, and my g1 once again works.
Props to Haykuro - You are the man!
Tracy

not to be disrespectful or rude but HOW did you get phone to recovery, many people are stuck on the G1 screen and have tried pressing hoome+power for hours on end and yet nothing, so what did you do differently. if all you did was press home+power then you weren't bricked

to replicate again, I have to do again
I didn't have recovery at first. I spent quite a bit of time (about 4 hours).
At one point, I had the phone plugged into my desktop.. it was on the g1 logo for 20 mins, when usb hardware detection warned about an unknown device.. after that point, recovery worked, but took the 'pull battery, reinsert, press and hold home, then press and release power' sequence to activate.

Tracyl1975 said:
I didn't have recovery at first. I spent quite a bit of time (about 4 hours).
At one point, I had the phone plugged into my desktop.. it was on the g1 logo for 20 mins, when usb hardware detection warned about an unknown device.. after that point, recovery worked, but took the 'pull battery, reinsert, press and hold home, then press and release power' sequence to activate.
Click to expand...
Click to collapse
So either you phone is not actually "bricked", i.e. SPL update was successful, but OS update is not. OR bricked phones are actually working, but taking much longer to finish self-check or something.
Tracy, what radio version do you have?

For what its worth, I suspect that the phones are taking far longer to finish their self checks, just from what I saw.
I 'bricked' it before loading the new OS, and the phone had a functioning OS prior to this.
radio is 2.22.19.26I

Is that the radio you have on it now or the radio you had on it *before*?

Both.
I updated the radio when I rooted it.

okay sounds like you soft bricked your phone.
and from what i understood, you had the phone plugged in all while trying to get into recovery mode and at the g1 screen.
first off, UNPLUG the phone from the charger or usb.
(i had this 'soft brick' issue when i was trying to flash H's SPL but i had the phone plugged in, only after i unplugged it and wiped and re-flash everything, things started to work and no issue with a continuous g1 screen loading)
hopefully you have JFv1.43 recovery image or Cyanogen's 1.1.
hopefully you flashed the newest radio prior to H's SPL.

dvt or pvt?

Tracyl1975 said:
Hi All,
So, today I tried installing Haykuro's latest SPL and ion rom, when low and behold, my phone was stuck at the G1 logo. Searching this and other sites offered no solution. I wasn't about to lose my hardware hacker cred and get a new phone... so, away I fiddle. I finally got the phone into recovery, after many reboots, and looong power/homekey presses. Once in recovery, I did the following.
put the hardspl update.zip on SD
Reboot, still frozen
wiped
rerun Haykuro's new SPL
DID NOT REBOOT - Wiped data
rerun radio firmware
Again, did not reboot - wiped data.
Pushed the ion firmware
Rebooted, and my g1 once again works.
Props to Haykuro - You are the man!
Tracy
Click to expand...
Click to collapse
THANK YOU!!
My phone was a brick after I had flashed hardspl and then danger spl, I wasnt thinking, over it and thought it was done for good..But I found your post and this worked! My G1 is back to life now
I flashed an older version of cm, 4.0.4 to make sure everything would go as smoothly as possible but do you think I could flash one of my nandroid backups that has cyan's 4.2.7.1 firmware on it? I dont want to risk getting another brick but I'm not sure if restoring a nan backup will screw everything up again?
again, thanks for your help

this thread reminds me of bigfoot/nessie/ufo sightings videos I don't think either of you actually "bricked" your phones...seriously, they would be worth their weight in plastic if they were. Either way, glad to hear you have them running properly

I had a similar problem when flashing the spl. I fixed it with fastboot:
Code:
#fastboot erase recovery
#fastboot flash recovery [I]recovery_file.img[/I]

G1 stuck at boot screen

G1 stuck at boot screen, after radio rom upgrade? Is there solution?

can you enter recovery, fastboot, what spl do you have, did you flash the spl first, what file did you flash, what type of phone do you have (region). Did you try to wipe and reflash?

I hope what you flash was truly a radio not an SPL.

any news on this yet??? man you should ALWAYS know what your doing,
if in DOUBT, get on here and SHOUT
flashing stuff you dont know is a quick way of bricking your phone but i have a feeling i know what you have done here are you trying to flash CyanogenMod if so what version and what version are you flashing from?
brit

Please igord? Share with us what happened? Is it bricked? Where was a mistake and which tutorial did you follow? Thanks.

The same thing happened to me, I was trying to root my phone last night and when I flashed the Danger SPL the phone installed it and requested a reboot. Rebooted and now the phone is stuck on the T-Mobile G1 screen. Tried to boot into recovery, doesn't work. Tried to boot holding camera + power, doesn't work. Assumed the phone is bricked so I did the only thing I could think of...
Called HTC customer service today, my phone is still covered under the HTC warranty. I lied to the representative on the phone saying I got an OTA update and now the phone wont go past the T-Mobile G1 screen. She gave me a RMA # and told me to send the phone in since it is still under the HTC warranty and that if the tech finds out what is wrong (and considers it a "factory" problem) they will fix it at no cost. If the tech feels the problem is a non-warranty problem, they will call and tell me how much it will cost to fix. With the HTC warranty, they said they REPAIR not REPLACE the phone.
Has anyone sent their phone into HTC when it was bricked? If so what was the outcome?

CaseyB14 said:
The same thing happened to me, I was trying to root my phone last night and when I flashed the Danger SPL the phone installed it and requested a reboot. Rebooted and now the phone is stuck on the T-Mobile G1 screen. Tried to boot into recovery, doesn't work. Tried to boot holding camera + power, doesn't work. Assumed the phone is bricked so I did the only thing I could think of...
Called HTC customer service today, my phone is still covered under the HTC warranty. I lied to the representative on the phone saying I got an OTA update and now the phone wont go past the T-Mobile G1 screen. She gave me a RMA # and told me to send the phone in since it is still under the HTC warranty and that if the tech finds out what is wrong (and considers it a "factory" problem) they will fix it at no cost. If the tech feels the problem is a non-warranty problem, they will call and tell me how much it will cost to fix. With the HTC warranty, they said they REPAIR not REPLACE the phone.
Has anyone sent their phone into HTC when it was bricked? If so what was the outcome?
Click to expand...
Click to collapse
did you make sure that you flashed over the new radio first?

No I didn't flash the new radio because the guy that was helping me told me I did not have to. He said the old radio would be fine with the Danger SPL. But it doesn't matter now because the phone is bricked and has already been shipped to HTC.
**Has anyone ever sent their bricked G1 to HTC under warranty for repair? If so what was the outcome?**

CaseyB14 said:
No I didn't flash the new radio because the guy that was helping me told me I did not have to. He said the old radio would be fine with the Danger SPL. But it doesn't matter now because the phone is bricked and has already been shipped to HTC.
**Has anyone ever sent their bricked G1 to HTC under warranty for repair? If so what was the outcome?**
Click to expand...
Click to collapse
....you should punch that guy....its been posted everywhere that old radio
+ new spl = best/fastest way to brick
A lot of people here have sent their spl bricked phones to htc. the mainboard is usually replaced or a replacement phone is sent (usually the latter)

Yea...once I get it back I will be rooting my phone the correct way. And read more posts about how to do it successfully.
Do you know if they consider it covered under warranty though? (FREE to fix?)

CaseyB14 said:
Yea...once I get it back I will be rooting my phone the correct way. And read more posts about how to do it successfully.
Do you know if they consider it covered under warranty though? (FREE to fix?)
Click to expand...
Click to collapse
Yes it should be covered. At most, they will charge a $39 triage fee

Okay cool! Thanks so much for all your help! =) Lemme tell you I was soooooo upset when my phone got bricked, because it was a BRAND NEW phone (I bought from someone off Craigslist who just had the phone sitting in the box in his closet) and the same day I bought it the same day it got bricked. That's why I'm hoping it will be covered under warranty. I'll keep my fingers crossed and keep everyone posted when I hear back from HTC once they receive my phone and diagnose the problem.

Ok... so my phone is stuck on the G1 screen... from reading all the posts trying to see if there was a possible solution I realized my phone may not be (completely) bricked????
I can NOT get into recovery BUt when I press <camera>+<power> I am able to get into another screen... bootloader I think???(3droids on skateboards) I press the <back> button... nothing happens.
HOW DID I GET INTO THIS MESS? I was trying to go from the CM pimped out recovery image to RA's recovery image because it had more features that I needed (ie..dalvik cache...)
I downloaded RA's recovery image... placed in the root of my SD card.
from the terminal... I typed
$su
#mount -a
#flash_image recovery /sdcard/recovery-RA-magic-v1.3.2H.img
#reboot
.. pressed <home>+<power> and wallah... I'm stuck.
Again... I have tried doing the search on my own... I have to admit... I only read about 10 random pages... I even did a general search on here and on google.
Please constructive suggestions are welcome...
If its bricked, its bricked I can accept that... Im beyond warranty but do have insurance.. just hoping since I can get to other screens there's still hope for MY SITUATION.

stuck @ tmo g1 screen
I was updating my radio and SPL following the guide here. I already had cyanogen recovery 1.4+JF installed, but followed the instructions as per the tut.
My phone stopped like it said so i took out the battery. I then proceeded to boot back into recovery and install Cyanogen mod 4.25(whatever the enwest one is now) and g1 will not boot past the t-mobile g1 screen.
I have adb control while stuck @ the tmo-g1 screen and I can get into fastboot.
What can I do to get my phone working again?
I tried to 'adb push' the radio update back into /sdcard/ but it says 'failed to copy update.zip to /sdcard/update.zip: read-only file system'
Fastboot says the following
DREAM PVT 32B ENG S-OFF
HBOOT 1.33.2005 (DREA10000)
CPLD-4
RADIO-2.22.19.26I
Thanks in advance

bzander28 said:
I was updating my radio and SPL following the guide here. I already had cyanogen recovery 1.4+JF installed, but followed the instructions as per the tut.
My phone stopped like it said so i took out the battery. I then proceeded to boot back into recovery and install Cyanogen mod 4.25(whatever the enwest one is now) and g1 will not boot past the t-mobile g1 screen.
I have adb control while stuck @ the tmo-g1 screen and I can get into fastboot.
What can I do to get my phone working again?
I tried to 'adb push' the radio update back into /sdcard/ but it says 'failed to copy update.zip to /sdcard/update.zip: read-only file system'
Fastboot says the following
DREAM PVT 32B ENG S-OFF
HBOOT 1.33.2005 (DREA10000)
CPLD-4
RADIO-2.22.19.26I
Thanks in advance
Click to expand...
Click to collapse
i suggest a reflash. Did you wipe before the flash?

I didnt wipe the first time. But I wiped after it stopped loading, and tried to reflash, but no improvement. Still stuck -_-;; also, is there any way to push files to my phone besides adb? I dont have a microSD reader with me at the moment so i cant get any other roms on the SD

Still, you can get it fixed (unbricked).
I'm in China and I got my g1 bricked days ago, then I fixed the phone by changing the NAND chip.
about $35 (or say RMB 250)

bzander28 said:
I didnt wipe the first time. But I wiped after it stopped loading, and tried to reflash, but no improvement. Still stuck -_-;; also, is there any way to push files to my phone besides adb? I dont have a microSD reader with me at the moment so i cant get any other roms on the SD
Click to expand...
Click to collapse
fastboot
You have the engineers spl now so I would suggest you fastboot the radio, erase the phone, and push over the recovery again. That would possibly fix your problem.
These are the commands:
fastboot flash radio radio.img
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
fastboot flash recovery recovery-RAv1.3.2G.img (the name here changes depending on which recovery you have)
You're going to want to put the radio and the recovery in the "tools" folder of your sdk
This happened to me when I first rooted my mytouch and it fixed it for me.

Did what you said, everything went through without any problems, but it's still stuck at the t-mobile g1 screen -___-;;

bzander28 said:
Did what you said, everything went through without any problems, but it's still stuck at the t-mobile g1 screen -___-;;
Click to expand...
Click to collapse
how long did you wait? Also, did you flash the actual HTC android 1.6 OTA update before you flashed Cyanogen's?

brick? not sure

I have a friend that just true to update from cyanogen to an eclair Tom and wont power on any more. Just freezes on g1 screen. I was able to get into bootloader and flashed nbh and was successful but still wont power just hangs at g1. When I try to enter recovery shows g1 and then powers off. Any ideas. I can't get it working but am able to get to stock bootloader and flash nbh but no further. Any help would b appreciated.

A brick is when you can't boot into recovery or fastboot, if you can get to ether of those you can recover.

What am I doing wrong. Flashing nbh not fixing. And some times need to reinsert battery. A few times to turn on at all. And flashing nbh only sticks on g1. Can get to boot at all. Other then recovery. Desperate

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.

Mytouch 3g possibly bricked

so im trying to root my sisters mytouch 3g and it was originally 2.2.1 with a "perfect" spl, i used rom manager to flash clockwork mod, that failed and left me with no recovery, so i followed the guide to make a goldcard and was able to get it to the 2005 spl which showed s-off H (its a google branded phone) I was then able to flash clockworkmod recovery I then tried to flash cm6 to the phone and it just sat at the splash screen. I tried 2 other roms as well with the same results. Then i was reading more and it said the 2004 spl was s-off G so i went to flash that, it said flashing complete restart phone through menu to complete i did that and the update screen came up for a second then the screen went black.. Now i cant boot into hboot, recovery, or fastboot. Im thinking the phone is now bricked! Are there any other tricks to try and bring this thing back..I read somewhere about jtagging but could really find much about it. I need to get this thing working asap and dont even understand how this happened.. Ive hacked alot of things and this little phone as been the most confusing and time consuming thing to date. also if it helps it was radio version 3 something. When i try to boot using power and back the splash comes up and if i keep holding after about 4 seconds it reboots again, if i let go a second after the splash screen it just sits at the splash until i pull the battery after a few minutes.

franky_402 said:
so im trying to root my sisters mytouch 3g and it was originally 2.2.1 with a "perfect" spl, i used rom manager to flash clockwork mod, that failed and left me with no recovery, so i followed the guide to make a goldcard and was able to get it to the 2005 spl which showed s-off H (its a google branded phone) I was then able to flash clockworkmod recovery I then tried to flash cm6 to the phone and it just sat at the splash screen. I tried 2 other roms as well with the same results. Then i was reading more and it said the 2004 spl was s-off G so i went to flash that, it said flashing complete restart phone through menu to complete i did that and the update screen came up for a second then the screen went black.. Now i cant boot into hboot, recovery, or fastboot. Im thinking the phone is now bricked! Are there any other tricks to try and bring this thing back..I read somewhere about jtagging but could really find much about it. I need to get this thing working asap and dont even understand how this happened.. Ive hacked alot of things and this little phone as been the most confusing and time consuming thing to date. also if it helps it was radio version 3 something. When i try to boot using power and back the splash comes up and if i keep holding after about 4 seconds it reboots again, if i let go a second after the splash screen it just sits at the splash until i pull the battery after a few minutes.
Click to expand...
Click to collapse
Its a brick. I'll tell you now that you can find a step by step process on using JTAG in the Wiki, but its not an easy process. Your going to have to have some moderate electronic knowledge plus moderate knowledge of how the phone boots to get it working. Your better bet would be to have it replaced under the warranty or insurance if you have either. If not, your second best bet would be to find someone who already has a working JTAG setup and see if you can get them to help you out.
Sent from my Optimus T using Tapatalk.

dang another mt3g down noobs need to ask for help
here is a link to a jtag tutorial
best of luck