Related
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?
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.
Hi all,
I've been trying to install an OS on a G1 for about 2 hours now. I have gone through about 20 posts and followed instructions to the T. I own a pc repair company and I post regularly to some windows and general computer repair forums, so I'm pretty technical. Since I'm 100% stuck, I'm hoping one of you can help.
I don't know anything about the history of the phone, but it currently boots to the rainbow bootloader screen:
DREA100 PVT 32B
HBOOT-0.95.0000
CPLD-4
RADIO-2.22.19.261
Serial0
I can drop the NBH file from DREAIMG-RC29.zip off of google's android file list into the root of the SD card and get the radio back to 1.22 no problem. I have actually tried 4 different versions of RC29 and all seem to work the same.
I have downloaded about 5 different versions of Android 1.5 (as well as 2 versions of 1.1, and a few of 1.6), changed them to update.zip, and attempted to load the OS and every single one of them fails*(see below for error) in the step "Verifying update package..." EXCEPT signed-kila-ota-148830.de6a94ca.zip. This one actually goes through all of the installation steps without erroring, tells me to hit home+back to reboot, says its updating the radio, goes to a screen with an image of a box pushing an arrow into a phone.... but then it reboots to the rainbow bootloader screen again!
*Error from above: E:Failure at line2: assert file_contains("SYSTEM:build.prop".... MORE ... Installation aborted.
When I reboot the phone now, it immediately tries to reload dreaimg.nbh. If I delete dreaimg.nbh off the SD card, the rainbow screen flashes (very quickly) to a gray screen that says "Loading.... No Image File!"
I know the phone isn't technically "bricked" because I'm able to interact with it, it reboots when I hold green+red+menu, but it sure seems like I'm in an infinite loop at this point.
My only goal is to get an OS loaded on this phone. ANY OS at this point.
Any suggestions on steps I can take? Need any other information?
Thanks alot for taking the time to read my post. I appreciate your time.
Thread moved inside G1 General.
sffan15 said:
Hi all,
I've been trying to install an OS on a G1 for about 2 hours now. I have gone through about 20 posts and followed instructions to the T. I own a pc repair company and I post regularly to some windows and general computer repair forums, so I'm pretty technical. Since I'm 100% stuck, I'm hoping one of you can help.
I don't know anything about the history of the phone, but it currently boots to the rainbow bootloader screen:
DREA100 PVT 32B
HBOOT-0.95.0000
CPLD-4
RADIO-2.22.19.261
Serial0
I can drop the NBH file from DREAIMG-RC29.zip off of google's android file list into the root of the SD card and get the radio back to 1.22 no problem. I have actually tried 4 different versions of RC29 and all seem to work the same.
I have downloaded about 5 different versions of Android 1.5 (as well as 2 versions of 1.1, and a few of 1.6), changed them to update.zip, and attempted to load the OS and every single one of them fails*(see below for error) in the step "Verifying update package..." EXCEPT signed-kila-ota-148830.de6a94ca.zip. This one actually goes through all of the installation steps without erroring, tells me to hit home+back to reboot, says its updating the radio, goes to a screen with an image of a box pushing an arrow into a phone.... but then it reboots to the rainbow bootloader screen again!
*Error from above: E:Failure at line2: assert file_contains("SYSTEM:build.prop".... MORE ... Installation aborted.
When I reboot the phone now, it immediately tries to reload dreaimg.nbh. If I delete dreaimg.nbh off the SD card, the rainbow screen flashes (very quickly) to a gray screen that says "Loading.... No Image File!"
I know the phone isn't technically "bricked" because I'm able to interact with it, it reboots when I hold green+red+menu, but it sure seems like I'm in an infinite loop at this point.
My only goal is to get an OS loaded on this phone. ANY OS at this point.
Any suggestions on steps I can take? Need any other information?
Thanks alot for taking the time to read my post. I appreciate your time.
Click to expand...
Click to collapse
I don't fully understand the issue.. You can get to the stock SPL, you can get to recovery to flash an update.zip, but you can't get it to boot the main system?
Yes, I guess that is the issue.
It seems to load the 1.5 OS I mentioned in my original post just fine, but the phone wont boot into anything but the SPL.
It acts as if there isn't a main system to boot to.
I'm also wondering if there is anything else that should be on the SD card other than update.zip and DREAIMG.spl?
Thanks for your help golden
thats weird, fist time ive seen a problem like this...
I've never seen this either.. usually when dreams get stuck in an spl loop a broken button is the culprit, but since you can get into recovery normally that seems unlikely. This is going to be really hard to diagnose and fix from a stock spl and recovery as well..
Did this phone ever work or did it come to you in this state?
Right? I have really done alot of work previous to posting here, and I only found one other person with the exact same issue. Unfortunately no one had an answer for him either. I never like to bug forums if I don't absolutly have to :/
According to the eBay post, the phone worked fine but broke when the previous owner tried to root it himself.
My dad purchased the phone assuming I would be able to fix it (laughs).
I would be willing to try just about anything at this point, if anyone has any crazy suggestions on how to get the phone to boot to an OS.
Is there any way to 100% wipe everything on the phone, like EVERYTHING, and start fresh? Or is that essentially what you're doing when you boot to recovery mode, tell it to reset to factory, and then reinstall the DREAIMG file?
Before I call TMo and play dumb, this being my first Android and all, I just want make sure this is Bricked.... :/
Playing around flashing different radio, SPL, recovery... etc I was in the middle of flashing a sappimg.zip and it started tossing Fail-PU all over at that time I was still in fastboot and still able to keep trying again and again but, then I made the mistake of unplugging it and doing a battery pull.
Now it does not turn back on. It does charge, it's fully charged now (goes from Orange to Green) but as soon as I touch the power button the LED goes off and I can't do a thing till I do a battery pull.
The only thing I can do is get the LED to go blue by holding the trackball and hitting power <end call>. But I've searched arounnd and can't find anything to do in this 'mode'.
So.... Bricked?
Yes sire....
Yup. You have a brick. What spl and radio combo were you using (or trying to use) during the flashing process? What instructions were you following that was too difficult to follow?
I guess the guy would have expected some hints HOW to "convert" his brick back to a phone. Or at least some comment - what's the blue-led mode (hboot?) and if that can help somehow?
This said, I'm shamefully accepting myself being dumb and bricking my phone just an hour ago... I only managed to reflash the hboot image .2005, and afterwards the phone is stuck.
I've followed this thread:
http://forum.cyanogenmod.com/topic/...r-new-radiospl/page__view__findpost__p__96630
my bad I must have made sure my recovery works at least...
Binary100100 said:
Yup. You have a brick. What spl and radio combo were you using (or trying to use) during the flashing process? What instructions were you following that was too difficult to follow?
Click to expand...
Click to collapse
i dont recall what i was doing at this point but, i think i was flashing between the 3/22 and the 2.22 radio and back and forht between the 2010 SPL and the Stock 3009? it think it was
i think i'm just getting too mixed up in here with what seems to be 3 or 4 different myTouch flavors out there, w/o a jack, w/ a jack, 32A, 32B... one rom for 32B will work fine on 32A but one for 32A will bomb out on a 32A if there a wrong radio/spl etc......
i think in the end i was trying to flash a 32A to my new v1.2 32A w/jack and it failed, i then tried to recover it with the update.zip on my goldcard and thats when it blew up with thte FAIL-PU ... ... .... brick.
on another note, that night i called TMo to get a replacement, it showed up Next day. start to Root it again and try another ROM, managed to do that fine had Cryogen up and running then tried another one i think it was a 32B yoshi's or somethign ... not sure it also worked fine.
then i noticed i could not get out of headset mode, i quick search nad fown it was a known issue probably hardware ehhh, so i'm using the RUU to flash it back to Stock before calling to get another replace ment and blam FAIL-PU all over WARNING then... brick....
so now we're on myTouch 3G 1.2 #3 and i think i'll leave it alone for now and let the daughter really get to use her phone for a while..... before i b rick it again
i bricked my second one. Got the warranty one in the mail today. Not gonna mess with it this time. Thats what my HD2 is for.
Hey everyone.
I was rooting my MyTouch 3g w/3.5mm this morning. I'm following the instructions from here ( http://theunlockr.com/2010/03/11/how-to-root-the-mytouch-1-2-and-fender-mytouch/ ). I had apparently messed up when I was at the restart after flashing sappimg.zip onto the phone and was stuck at the HTC Magic Screen. I restarted my phone by holding down the Reject Call + Volume Down key and told it to flash sappimg.zip onto the phone again so I could redo it correctly. Unfortunately, it's stuck at the "[1] SYSTEM - UNZIPPING" stage. I'm afraid to turn it off because it says to not power off the device.
So, yeah, have I bricked my phone or is there a way to restart this process so I can successfully root?
Thanks much, and have a happy holiday.
EDIT: This sort of resolved itself, but now I can't get into recovery mode. :/
Rhaseo said:
Hey everyone.
I was rooting my MyTouch 3g w/3.5mm this morning. I'm following the instructions from here ( http://theunlockr.com/2010/03/11/how-to-root-the-mytouch-1-2-and-fender-mytouch/ ). I had apparently messed up when I was at the restart after flashing sappimg.zip onto the phone and was stuck at the HTC Magic Screen. I restarted my phone by holding down the Reject Call + Volume Down key and told it to flash sappimg.zip onto the phone again so I could redo it correctly. Unfortunately, it's stuck at the "[1] SYSTEM - UNZIPPING" stage. I'm afraid to turn it off because it says to not power off the device.
So, yeah, have I bricked my phone or is there a way to restart this process so I can successfully root?
Thanks much, and have a happy holiday.
Click to expand...
Click to collapse
So your flashing the engineering spl for the first time or are you flashing the stock spl back?
Binary100100 said:
So your flashing the engineering spl for the first time or are you flashing the stock spl back?
Click to expand...
Click to collapse
I'm flashing the engineering spl onto there for the first time.
It appears that being stuck at the Magic screen is normal according to a different (but similar) guide from the Cyanogen Wiki. Would it irreparably damage my phone if I removed the battery despite it being at the "Unzipping" screen for Sappimg (as I was unzipping sappimg for a second time) and proceeding with CyanogenMod's guide instead?
EDIT: It appears my phone just turned off on it's own (battery probably died). I'm going to try CyanogenMod's instructions and see if that works.
EDIT 2: So, I reflashed it with the sappimg that Cyanogen has on his wiki. So everything was smooth sailing until I got to the Recovery step. I cannot, for the life of me, to get it to boot in recovery mode. I hold HOME+POWER but nothing pops up.
EDIT 3: And it appears as if I've bricked it.
Rhaseo said:
I'm flashing the engineering spl onto there for the first time.
It appears that being stuck at the Magic screen is normal according to a different (but similar) guide from the Cyanogen Wiki. Would it irreparably damage my phone if I removed the battery despite it being at the "Unzipping" screen for Sappimg (as I was unzipping sappimg for a second time) and proceeding with CyanogenMod's guide instead?
EDIT: It appears my phone just turned off on it's own (battery probably died). I'm going to try CyanogenMod's instructions and see if that works.
EDIT 2: So, I reflashed it with the sappimg that Cyanogen has on his wiki. So everything was smooth sailing until I got to the Recovery step. I cannot, for the life of me, to get it to boot in recovery mode. I hold HOME+POWER but nothing pops up.
EDIT 3: And it appears as if I've bricked it.
Click to expand...
Click to collapse
Will the rom start? If so, you didn't brick it.
Do you have the Engineering SPL on it? What SPL version do you currently have on there? Remember that if you have the T-Mobile US MyTouch w/3.5mm jack then you MUST have 32B recovery and radio and STOCK (1.33.0013) SPL before flashing a custom rom.
Best way to do it is to flash your custom recovery (I suggest Clockwork Recovery for Mytouch/ION devices) by fastboot.
Afterwards then flash your stock (S-ON) SPL back and then boot to recovery to flash your rom.
REMEMBER!!! YOU DO NOT HAVE A 32a DEVICE! DESPITE WHAT THE SPL SAYS... IT'S NOT TECHNICALLY A 32a DEVICE!!! You MUST treat is as a 32b.
Binary100100 said:
Will the rom start? If so, you didn't brick it.
Do you have the Engineering SPL on it? What SPL version do you currently have on there? Remember that if you have the T-Mobile US MyTouch w/3.5mm jack then you MUST have 32B recovery and radio and STOCK (1.33.0013) SPL before flashing a custom rom.
Best way to do it is to flash your custom recovery (I suggest Clockwork Recovery for Mytouch/ION devices) by fastboot.
Afterwards then flash your stock (S-ON) SPL back and then boot to recovery to flash your rom.
REMEMBER!!! YOU DO NOT HAVE A 32a DEVICE! DESPITE WHAT THE SPL SAYS... IT'S NOT TECHNICALLY A 32a DEVICE!!! You MUST treat is as a 32b.
Click to expand...
Click to collapse
Oh, wow. That explains why I bricked the phone. The Amon_RA Recovery I put on there was 32a... I'm an idiot.
The phone won't start up at all. :/ Looks like I'm out $100 or so.
Thanks for that, though. I was going to give you a "Thanks" but it appears the button has disappeared for me.
Rhaseo said:
Oh, wow. That explains why I bricked the phone. The Amon_RA Recovery I put on there was 32a... I'm an idiot.
The phone won't start up at all. :/ Looks like I'm out $100 or so.
Thanks for that, though. I was going to give you a "Thanks" but it appears the button has disappeared for me.
Click to expand...
Click to collapse
Can you still get into fastboot?
Binary100100 said:
Can you still get into fastboot?
Click to expand...
Click to collapse
Nope. It won't turn on at all.
Rhaseo said:
Nope. It won't turn on at all.
Click to expand...
Click to collapse
Won't boot, no recovery, no fastboot.
If it looks like a brick, if it sounds like a brick then it's probably...
I have a similar problem. I purchased this phone and it just almost works. It boots into fastboot just fine but not recovery. Here are the specifics as they stand now.
Sapphire unknown 32A ship S-on H
CLD 13
Radio 3.22.20.17
May 8 2009, 21:02:32
I made a good gold card...tried the 2010 spl...still hangs during unzip step of the flash process. Any other ROM and I get a main version older error.
Fastboot info version main 2.53.707.2
cid T-MOB010
Any help would be greatly appreciated.
Nice job on probably bricking your phone. You've got the myTouch 1.2 which means you just flashed an incompatible radio. Congratulations!!! I honestly not sure what to tell you. Which sappimg are you trying to use to get the engineering SPL?
Like i said...it was like this when I bought it.
I'm going to try to do a poorman's JTAG...wish me luck.
jonk26.2 said:
wish me luck.
Click to expand...
Click to collapse
Good luck! You can do it!
If you have any questions along the way, please don't hesitate to ask.
JTAG did in fact de-brick my MT3G 1.2 (bought from ebay) the first time I tried it. I made the mistake of flashing the stock ROM, so I would get to the "touch the android to begin" screen and couldn't get any further without a data plan. It wasn't until I probably flashed the wrong sappimg in a root attempt that I started experiencing the stuck at unzipping/FAIL-PU/remote signature verify fail problem...
FYI, I tried flashing radio 2.22.28.25 (the one from the OTA) using JTAG and the radata command, and it fixed my USB. I haven't experiemented much beyond that, but I'm planning to try some more things this weekend.
Moderators, I'd like to suggest merging this thread with http://forum.xda-developers.com/showthread.php?t=773368 and http://forum.xda-developers.com/showthread.php?t=771622 since they all seem to be discussing the same problem.