Related
Ok - thanks for coming in and reading my post even though you could have skipped right on through.
I have purchased a used MT3G from craigslist (i know). I am a semi-knowledgeable "veteran" when it comes to rooting and flashing on the g1 - but the mytouch is totally new to me.
I have some SERIOUS SERIOUS concerns as to what my phone even is in the first place. I bought it with original TMobile packaging, phone says tmobile in the front and back - yet when I turn it on it's VODAFONE.
When I boot into recovery, I get the Triangle Exclamation with the phone. The rom is a 1.5 HTC rom and here is my fastboot info.
PVT 32B SHIP S-ON H
HBOOT - 1.33.0009 (SAPP30000)
CPLD - 10
RADIO - 3.22.20.17
May 8th 2009
HOWEVER - when I run the "one click root" - it says I have a 32A system. Eventually I followed the instructions for 1 click root using flash rec and flashed (downloaded) the Cyan 1.4.1a from the "recovery installer" (flashrec-1.1.2 2009-0909). They said my phone was 32A, I just went ahead and downloaded and installed - now I have the cyan recovery when I boot up my phone - I just can't flash ANY roms. I tried RAv 1.6 - for both 32B and 32A. 32A keeps rebooting my phone over and over, 32B just sits at the vodafone and hangs for 15 minutes.
After HOURS AND HOURS of reading the forms and the wiki - I'm at a complete impasse. I need some guidance. Do I have a 32A or 32B? Is it possible for 32A phones to show 32B in the fastboot? Some people need a "goldcard" to do this - I just used flashrec did I do something wrong? It seems as if some people are flashing roms with their regular SPLs - do I need engineering SPL - if so HOW do I flash SPL and radio without bricking.
I just want to flash some damn roms, or even get back to OEM and get my phone up to 1.6. It's such a bad feeling buying a phone, then bringing it home and you don't realize what you've gotten......I just want to get my phone rooted and start flashing roms and I've gotten this far.
ANY HELP GREATLY APPRECIATED!!!!!!!!
edit - the only way I've gotten my phone back to the stock HTC MAGIC rom is luckily upon first running of the CYAN recovery I did a nandroid backup and just restored to my backup after the failed rom flashes.
EDIT 2pm CST : I called T-Mobile, they can track your IMEI and Sim card every time you place a call - they CONFIRMED that my IMEI belonged to a TMOBILE MYTOUCH 3G and not any european phone. This leads me to my next question - is it possible to flash this HTC MAGIC rom onto a TMOBILE MYTOUCH 3G through fastboot, or something - WITHOUT a recovery, WITHOUT having root?
My MYTOUCH 3G is running VODAFONE everything, and it's definitely a EUROPEAN HTC MAGIC rom. Did someone install something on this phone before I got it. Please community - any help is appreciated.
A possible explanation is that someone followed Amon_RA's instructions partway through but did not finish. Specifically, they may have flashed the SPL, the recovery image for 32A and then a ROM for 32A. Since the phone is 32B, the recommendation is then to update the radio and recovery and ROM for 32B after it is rooted.
Perhaps this person rooted the phone, and then did not revert to 32B. Just a guess, though.
ok bro first lets calm down. everything is fine. all the information you need is right in front of you. first if its from europe it could be 32b and or 32a. so to check if you have root lets download a terminal app. if you dont have one pm and ill send you one. once we have that run it and type
su
if it asks for permission or just goes to
#
you are good. now type cat /proc/meminfo
for "MemTotal:" if it says 98024 or around there then you have a 32b. there that took care of what kind of board you have now we have radio and splash. your radio is .009. eng radio is .006. most likely the person that had the phone before only did have the steps. so go over them again with doing a "real" rooting. make a goldcard, get a good rec .img and have sdk working on your comp. if you need help i can help the best i can.
my touch 3g problem!! please help!!!
i bought a my touch 3g from craigslist. and when i turn it on it freezes up and says vodafone and it just stays there.. i need help to get it off can anyone help??? please
Turn it on while holding the Home key and tell us what you get? If you get a menu of options then you have a custom recovery image and you can flash a new rom ... if you just get an image of a ! then you have the stock recovery image.
Also turn it on while holding the back key, give us the information from that screen (also known as the fastboot screen) as this will tell us what recovery options are available to you.
I feel you man.
richboii8939 said:
i bought a my touch 3g from craigslist. and when i turn it on it freezes up and says vodafone and it just stays there.. i need help to get it off can anyone help??? please
Click to expand...
Click to collapse
I worked for T-Mobile and got a mytouch before launch. My MyTouch, During the 32B radio flash, fell off my desk, disconnected, and has been stuck where you are ever since.
doing MANY hours of research and trying VARIOUS different methods did not help. I since bought another, (and a nexus. DO NOT MISS THE MYTOUCH) rooted it and my original MT3G, is still stuck on Vodafone red boot screen, and has a hopefully semi-permanent place in the bottom of my shame drawer.
Mine will not respond to Goldcards, and is not picked up by ADB.
If you plug your phone in, on boot and it is recognized by ADB, then you have hope. If its completely shot like mine. I doubt you'll be able to revive it. Unless ive been missing something since July of last year. (I had it early lol).
If it is recognized.
I would...
-Get a 32B radio
-Open CMD in the radio's folder (Shift + Right click will add a button in your right click to Open Command Prompt There)
-Fastboot flash radio <insert file name here>.zip
-Adb will say "Waiting for Device"
-IF IT IS RECOGNIZED It should reboot into Fastboot and flash the Radio and you should be okay.
*Please correct me if I'm wrong. Im can root all day long, but i can barely explain it. XD*
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.
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.
well, where to start...i bought my MT3G 1.2 brand new because my original decided to have antenna issues (only cell antenna and only inside a building). so fast forward about a year, after rooting my NEW MT3G, I end up letting a friend use it til he can get a replacement for his. I get the phone back (after his dog bit through the screen) and another MT3G that is broke to use as a donor for the screen. swap screens, salvage other parts to fix my original, and boot up the 1.2.
now here is where it gets...interesting...to say the least. unlike before, where it booted to the MyTouch 3g splash screen, it now thinks it is an HTC Magic...i have been looking and unsuccessfully flashing builds TRYING to get it to what it was so i can upgrade the radio and actually know what i have again.
what would cause the phone to think it is a Magic? was it something in clockworkmod? can it be reversed? and why, for the love of god, can i not flash anything but EZGingerbread to it?
Details from the bootloader
SAPPHIRE PVT 32A SHIP S-ON G
HBOOT-1.33.0013 (SAPP31000)
CPLD-13
RADIO-2.22.23.02
Oct 21 2009,22:33:27
Any help would be greatly appreciated, cause im about to pull out what little hair i have left >_<
Sounds like fun!
If you haven't done yet: Download Android-SDK and install it (while installing choose Android SDK Tools, Android Platfrom-tools and Google USB Driver).
Connect your phone to usb and start it to bootloader (fastboot usb, back+power). Open a commandline on your computer and go to "...\android-sdk\platform-tools" depending on where you installed it. Then type
Code:
fastboot getvar cid
and
Code:
fastboot getvar version-main
and post the output here.
And please leave your hair where it belongs to! :laugh:
well....that wasnt too bad, i just get <waiting for device> and it hangs
even using CID Getter on the phone itself doesnt give me a CID like it does on my Glacier...i think something may be seriously messed up here >_<
Don't know why it may hang. Does the phone work properly? Maybe just the splash-screen was changed.
Have a look at this thread - there are all official roms for magic and so on. Having a look at your radio the stock-rom on your phone for now may be #56 or #57 (hboot 1.33.0013, radio 2.22.23.02). Only the OTA-update has newer versions.
I don't know if it's worth risking to brick the phone just for this update - only if it works properly at the moment.
It works properly as far as calls and texts and data, but I haven't been able to update the radio or hboot at all, it keeps giving a device id mismatch error
Sent from my HTC Glacier With Beats Audio using xda premium
What you can do:
- if you don't have a custom-recovery on your phone install one - try this guide without the optional stuff
- when done install the stock-rom for your phone (via custom-recovery) from official-rom-thread - i don't know if #56 or #57
- root and install custom-recovery again as shown above*
- then you may apply the OTA-update via custom-recovery (#58 from the official-rom-thread)
*I don't know if it's possible just to flash everything except recovery, then you wouldn't need to root it and install custom-recovery again.
That would be the newest versions for your phone.
I have ClockworkMod recovery already installed, and with this being my backup phone, I wouldn't be mad without root at all, though root is nice, I want it to be right lol
Sent from my Gingerbread on Sapphire
So you can flash your phone to official stock-rom and then update it to newest official-rom as i explained above. Or what should i tell you right now?
I tried to flash a stock rom, but with no success, when I get home I'll try again and post the error log
Sent from my HTC Glacier With Beats Audio using xda premium
SWEET!!! i got the fastboot commands to come through for me
fastboot getvar cid
cid: T-MOB010
fastboot getvar version-main
version-main: 2.53.707.2
And what happens when you try to flash "57) 2.10.531.4 T-Mobile USA DRD35" via custom-recovery (your recovery will be flashed too)?
That is a self installing executable file, when i try to run it, it tells me that it can not communicate with the device, and to make sure that the usb cable is connected and the phone is on, which it is both
so the 57) 2.10.531.4 T-Mobile USA DRD35 flash went finally, turns out, my phone didn't like it too much, because now, i am stuck at the HTC magic splash screen and i think it is bricked
I don't get it, that should have been the correct files for your phone. You're sure that it's a Mytouch 3g 1.2 and not the normal Mytouch 3g?
How did you flash the file?
If you search here you can find "tutorials" how to get the rom-files out of the RUU to flash it in hboot-mode.
Can you get into recovery-mode? What about hboot-mode?
It was a .exe file, so it ran from my computer, and I know it's a 1.2 because I couldn't afford the fender edition lol. Now it just hangs on the splash screen and won't let me do anything at all
Sent from my HTC Glacier using xda premium
I think it would have been better to extract the rom-file and flash it with hboot from sd-card... Then you should have been sure about what he flashed.
Maybe now you got some weird radio-system-whatever-mix and that's why it doesn't start.
Normaly you flashed the correct rom-file for your phone.
What you can try:
- remove battery for some time (5 minutes or whatever) and press power - then get the battery back in and try to start it again
- start the phone with Home+Back+Power or Menu+Back+Power (don't remember), in my case there was a menu to erase cache and so on, maybe this would work for you
- is your phone listed in "fastboot devices" when you power on your phone with Vol down+Power, Back+Power, Power, Home+Power or the combination from above? I read that some people are already in fastboot-mode and have text on their display when they see the logo, shown for example here (they had red text on red vodafone-logo):
http://www.android-hilfe.de/attachm...oter-vodafone-bildschirm-geloest-dsc00624.jpg
If not...
Does bluelight-mode work (i think it's trackball+power)? If so you can get it running with JTAG - you just need somebody who has the equipment and so on. Where are you from?