32A stuck at Splash, no USB connection or HBOOT - myTouch 3G, Magic General

Hey everyone,
it so happened yesterday that after successfully toying around with some pre-made ROMs I tried to flash my Magic with the Google I/O Device recovery and apparently bricked it in the process. But let me start at the beginning.
What I had running fine was Anrdoid 2.0 for the 32A from here. Under the hood I was running Amon_RAs recovery "recovery-RA-sapphire-v1.5.1H.img" from here and my SPL was the Engineering SPL 1.33.2010 from here. Everything was working fine so far and I was happy toying around with the Android 2.0 goodness.
However, ultimately I wanted to deploy my custom built of Android 1.6 from the source repository. Therefore my first step was to make sure that the vanilla Android 1.6 without modifications works on the device. What I did is I went to the HTC developer site for the Google I/O Device here and downloaded the system image for Android 1.6, called "signed-google_ion-img-14721.zip". I fastbooted system, boot and (the empty) userdata that were in that package, to not much avail. The device would be stuck at the Vodafone splash (mine is a Vodafone branded 32A). I made sure to wipe everything and fastbooted those again, just to make sure. Again no results. Then I wanted to fastboot the whole package instead of the individual imgs with "fastboot update <file> -w". The consistency check then told me:
checking version-bootloader... FAILED
Device version-bootloader is '1.33.2010'.
Update requires '1.33.2005' or '1.33.0005' or '1.33.3004' or '1.33.3005'.
I happily got SPL .2005 from the above link, and installed through the Amon's recovery image. Just in case I tried to boot the device, but it didn't do much. So I went ahead and tried to fastboot update the package again. It then told me:
checking version-baseband... FAILED
Device version-baseband is '3.22.20.17'.
Update requires '2.22.19.26I'.
I was a little sceptical but went back to the HTC developer site and downloaded the radio that it cried for, named "ota-radio-2_22_19_26I.zip". I installed that again through Amon's recovery image (which is awesome btw, thank you very much!). It seemed rather successful but after a reboot the device would still not boot, nothing new to me. However, when I wanted to enter fastboot (back key), HBOOT (vol down key) or recovery (home key), nothing would happen anymore, it was just stuck at the red Vodafone splash and fastboot which would usually spring open right away would just trigger the regular boot.
I went through dozens of forum posts where people describe the same problem and it appears that no one found a solution so far. When I press the ball it comes up with a black screen and a blue LED. It also happily charges when I connect it to a charger or USB, but that is about as much as I can do. Plugging/unplugging a million times and trying different combinations of button presses and battery insert/removals didn't bring it back to life, either. The device is not connecting over USB (not as an Android or unknown device or anything) so that adb or fastboot are useless.
Have I bricked my phone? Does anyone have a solution? Please take the time to read the whole post before replying because I took the time to describe my problem and the steps I took in detail.
I'm also curious what exactly went wrong, can someone enlighten me? From what I could tell the HTC developer device (Google I/O) is a 32A so the hardware should be identical. What was my mistake?
I'd appreciate any input you guys might have!

I am sorry about your brick.. But Google I/O device is not a 32a device, it's 32b The link below explains the issue in details.. Thanks to Xanadux (if i got it right.. )
http://wiki.xda-developers.com/index.php?pagename=HTC_Sapphire
And it looks like it got bricked after the Radio update.. which could be because there was something specific hardcoded for Vodefone or supported by the device hardware, and when you flashed the Google IO Radio Image (which has a differeng GSM freq. as you can see from http://developer.htc.com/google-io-device.html) it bricked..
I hope someone comes up with a solution.. I was planning to flash my Google IO device with the HTC Magic Radio flash, I guess it's not the best idea..

Hm now that you say it, it seems quite obvious that the "Google" I/O Device would be a 32B, which is "Google" branded. Mh. Oh well, I guess for some reason I didn't see it. Well, it would of course be great if someone would come up with a solution, but at least I know now what I did wrong. Thanks for the hint about the different frequencies!

Same boat....
2of11 said:
Hey everyone,
it so happened yesterday that after successfully toying around with some pre-made ROMs I tried to flash my Magic with the Google I/O Device recovery and apparently bricked it in the process. But let me start at the beginning.
What I had running fine was Anrdoid 2.0 for the 32A from here. Under the hood I was running Amon_RAs recovery "recovery-RA-sapphire-v1.5.1H.img" from here and my SPL was the Engineering SPL 1.33.2010 from here. Everything was working fine so far and I was happy toying around with the Android 2.0 goodness.
However, ultimately I wanted to deploy my custom built of Android 1.6 from the source repository. Therefore my first step was to make sure that the vanilla Android 1.6 without modifications works on the device. What I did is I went to the HTC developer site for the Google I/O Device here and downloaded the system image for Android 1.6, called "signed-google_ion-img-14721.zip". I fastbooted system, boot and (the empty) userdata that were in that package, to not much avail. The device would be stuck at the Vodafone splash (mine is a Vodafone branded 32A). I made sure to wipe everything and fastbooted those again, just to make sure. Again no results. Then I wanted to fastboot the whole package instead of the individual imgs with "fastboot update <file> -w". The consistency check then told me:
checking version-bootloader... FAILED
Device version-bootloader is '1.33.2010'.
Update requires '1.33.2005' or '1.33.0005' or '1.33.3004' or '1.33.3005'.
I happily got SPL .2005 from the above link, and installed through the Amon's recovery image. Just in case I tried to boot the device, but it didn't do much. So I went ahead and tried to fastboot update the package again. It then told me:
checking version-baseband... FAILED
Device version-baseband is '3.22.20.17'.
Update requires '2.22.19.26I'.
I was a little sceptical but went back to the HTC developer site and downloaded the radio that it cried for, named "ota-radio-2_22_19_26I.zip". I installed that again through Amon's recovery image (which is awesome btw, thank you very much!). It seemed rather successful but after a reboot the device would still not boot, nothing new to me. However, when I wanted to enter fastboot (back key), HBOOT (vol down key) or recovery (home key), nothing would happen anymore, it was just stuck at the red Vodafone splash and fastboot which would usually spring open right away would just trigger the regular boot.
I went through dozens of forum posts where people describe the same problem and it appears that no one found a solution so far. When I press the ball it comes up with a black screen and a blue LED. It also happily charges when I connect it to a charger or USB, but that is about as much as I can do. Plugging/unplugging a million times and trying different combinations of button presses and battery insert/removals didn't bring it back to life, either. The device is not connecting over USB (not as an Android or unknown device or anything) so that adb or fastboot are useless.
Have I bricked my phone? Does anyone have a solution? Please take the time to read the whole post before replying because I took the time to describe my problem and the steps I took in detail.
I'm also curious what exactly went wrong, can someone enlighten me? From what I could tell the HTC developer device (Google I/O) is a 32A so the hardware should be identical. What was my mistake?
I'd appreciate any input you guys might have!
Click to expand...
Click to collapse
Unfortunately me and you are in the same boat, I was trying to do the same to the same by flashing my spl 2010 to 2005 and just like that im stuck at boot logo with no access at all. . . tried all kinds of button, it still vibrates when you press power but thats all the love im getting from this magic.. . .by the way, it this is what i think it is.. . this will be brick # 2... . .f*ckin ey right?? . .well lets hope some genius come up with some crazy azz solution.. . ..

Another Bricke HTC Magic
Same problem than 2of11, I also flashed the wrong radio image. Did you get any solution?
Cheers, there is always a reason to buy a new better phone.. but wich one will it be?

Sorry, but I did not find a solution, the phone stayed bricked and was then changed.

Hello,
I have a PVT 32B (HTC Magic Vodafone) and just updated the RADIO to the same version as I had before, just because HTC says it. now I wanted to flash the image with
Code:
$ fastboot update signed-google_ion-img-14721.zip
and got
Code:
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: 1.33.2010
Baseband Version.....: 2.22.19.26I
Serial Number........: XXXXXXXXX
--------------------------------------------
checking product... OKAY
checking serialno... OKAY
checking product... OKAY
checking version-bootloader... FAILED
Device version-bootloader is '1.33.2010'.
Update requires '1.33.2005' or '1.33.0005' or '1.33.3004' or '1.33.3005'.
So I searched for one of these bootloader versions and ended up at this post, which tells me to be careful I think my phone still works, because it booted correctly after RADIO update. Is it save to update the bootloader and load the image from htc.developers if I have a 32B? And if so are the "SPLs" from the post (#529019) of Amon_RA good for me, or where can I get the appropriate HBOOT version?

white_gecko said:
Hello,
Is it save to update the bootloader and load the image from htc.developers if I have a 32B? And if so are the "SPLs" from the post (#529019) of Amon_RA good for me, or where can I get the appropriate HBOOT version?
Click to expand...
Click to collapse
So I was also working with a Vodafone Magic, but if I remember this correctly, mine was a 32A, where as the Google I/O device is a 32B. So maybe the hardware changed over time? In any case, be VERY careful and have someone confirm that you are indeed handling the same kind of device as the Google I/O. There should be a "Google" branding on the back of 32B devices, but I haven't been toying around with this for a while and may provide outdated information. Have you checked this link?
Code:
wiki.xda-developers.com/index.php?pagename=HTC_Sapphire
For what it's worth, I was able to use the Engineering SPLs that were posted here:
Code:
forum.xda-developers.com/showthread.php?t=529019
without any trouble. Keep in mind that maybe we are talking about different devices, though.
Hope that helps.

Yes I'm sure, that I have a 32B and in Wikipedia article to "HTC Magic" I've read, that the I/O has also the 32B. But could there also be other differences, which could cause that I brick the phone?
the en.wikipedia "Htc_magic" said:
* Two different hardware platforms exist for this phone (they require different boot images and wireless LAN kernel modules):
- The PVT32A, with a Qualcomm MSM7200A ARM11 processor and 288 MB RAM,
- The PVT32B, with a Qualcomm MSM7201A ARM11 processor, and 192MB RAM.
The only models that use the 32B platform are the original T-Mobile myTouch 3G (v1.2 of this phone, released in Feb 2010, switched to the 32A), the Vodafone Magic and the Google Ion developer phone.
Click to expand...
Click to collapse
Now I have installed a different Image so I'm not in such big temptation to update the HBOOT, but I would also like to try the developer images.

Well the good news, guys, is that the G1/dream has been de-bricked successfully, and due to the similarity of the hardware it's a safe bet that the mytouch/magic is not far off. The bad news is that it will likely require someone who has specialized equipment who knows what they are doing.

Related

G1 32b flashed to dream 32a rom,can't flash back

I have a black G1 with a 32b board,I found a rom online that was for the rogers dream,I didn't think it would flash the recovery image too,so I flashed it thinking if it didn't work I would be able to just flash to a different rom. That didn't work. it boots up as a rogers dream,and is fully working,but I can't flash back to anything else because it's a stock recovery image,and even though I had the engineering spl,it messed that up too,it still shows the skateboarding androids,but with a cyan stripe at the top of the screen and it won't even flash the htc images for the dev phone,or the normal rc29 DREAIMG.nbh. anyone have any ideas? fastboot tells me remote not allow,bootloader to the DREAIMG.nbh says either main version old,or model id mismatch,most of the time it's the main version thing though,and the recovery thing tells me no signature found if I try to flash the htc images and verification failed if I try to flash anything else that i've tried. anyone have any ideas? it was the 911 mandatory update from rogers that was supposed to also add sense if that helps anyone any.
1) THERE IS NO SUCH THING AS A 32A DREAM!!!!
32A means SOME HTC MAGIC, and ALL HTC HERO.
ALL DREAM 100% WORLDWIDE are 32B
*** NO EXCEPTIONS.
2) You need to provide more information: WHAT did you flash to the device.... SPECIFICALLY. And HOW DOES EVERYTHING IDENTIFY ITSELF, i.e. SPL, BASEBAND, KERNEL, etc., does the "su" command work?
3) I have ZERO expectations for you. Anyone with a screen name of "msnuser" is not worthy of android.
it's the rom from comment 102 on this page:androidforums.com/rogers/38624-rogers-update-911-fix-rogers-htc-dream-magic-ready-3.html the rom says on the recovery screen dream PVT-32A and it used to be PVT-32B. Not sure how it worked or how it booted,but the phone says it has 87mb free on the internal storage and it runs a lot quicker than it did on any rom I've ever used before,I just miss my rooted apps. I traded phones with my brother because he never uses rooted apps anyway,he was running stock tmobile firmware and was glad to have a faster os.

Rooting Official Magic Sense Update

Hi all,
I just updated my Magic (Hutchison/3, Australia) (32A) to the latest official HTC firmware with sense ui (I had cyanogen on there before but it was too buggy for my liking). However, it seems that this firmware has the "perfect" spl (HBOOT-1.76.0008, Radio 6.35.08.29). I was planning to root the phone without flashing a different rom but i of course need write access to /system. My plan was to boot amon-ra's recovery to do this, however when i try and boot it with "fastboot boot recovery-RA-sapphire-v1.6.2H.img", i get told "FAILED (remote: not allow)" (same deal for the hero version).
My idea is to download an old sappimg.nbh and start up the SPL on the phone, which displays some messages about looking for that file when it starts up. I assume this will flash an older SPL; then, i install the system part of the new ROM but not the radio/SPL somehow (is this possible?) then follow my initial plan for rooting the phone
However, from what i've read it seems messing with the SPL is pretty much the only way to brick the phone. Is what i suggest safe/will it work?
Thanks guys
greeklegend said:
Hi all,
I just updated my Magic (Hutchison/3, Australia) (32A) to the latest official HTC firmware with sense ui (I had cyanogen on there before but it was too buggy for my liking). However, it seems that this firmware has the "perfect" spl (HBOOT-1.76.0008, Radio 6.35.08.29). I was planning to root the phone without flashing a different rom but i of course need write access to /system. My plan was to boot amon-ra's recovery to do this, however when i try and boot it with "fastboot boot recovery-RA-sapphire-v1.6.2H.img", i get told "FAILED (remote: not allow)" (same deal for the hero version).
My idea is to download an old sappimg.nbh and start up the SPL on the phone, which displays some messages about looking for that file when it starts up. I assume this will flash an older SPL; then, i install the system part of the new ROM but not the radio/SPL somehow (is this possible?) then follow my initial plan for rooting the phone
However, from what i've read it seems messing with the SPL is pretty much the only way to brick the phone. Is what i suggest safe/will it work?
Thanks guys
Click to expand...
Click to collapse
unfortunately wont work... it wont allow you to flash an older spl...probably will have to wait till an official 2.1 update comes out and hope that it might be rootable..
And THAT will teach me to look before I leap! I guess I can live with this update because its actually a HUGE improvement over what I was using before (radio reception is much better, text correction in the browser,sense is win in general and its much snappier) and I can still do usb tethering. But still, WHY DID YOU DO THIS TO US HTC!!!
EDIT:
I tried taking the rom image from the RUU and using fastboot to boot the boot.img from that but not even that works! I was thinking to do something like init=/system/bin/sh... I don't suppose theres another way to supply cmdline parameters to the kernel?

Can this Magic/MT3G be saved?

Hey guys,
I have a Nexus One that I have rooted and put a number of different roms on. Of course this somehow makes my friends think I'm some pro at android roms and such.
A friend of mine, who apparently either misread instructions or just fouled it up, gave me a HTC Magic / MT3G to look at to see if I could get it working properly again. Here is the situation:
T-Mobile myTouch 3G (1.2 version)
When attempting to boot, it will land on a "HTC MAGIC" splash screen but not boot into android.
When attempting to go into recovery mode, it doesn't seem to have a custom recovery mode... but here is the info on the Fastboot screen:
SAPPHIRE UNKNOWN 32A ENG S-OFF H
HBOOT-1.33.2010 (SAPP31000)
CPLD-13
RADIO-3.22.20.17
Jun 2 2009, 17:27:03
I was trying to think of how I could investigate more, but aside from going into fastboot and hboot I don't know what to try really... I am used to using a custom recovery or being able to boot into android and use ADB.
What do you guys think? Hopeless? Or perhaps have some ideas of some things I could try to get this thing running?
http://forum.xda-developers.com/showthread.php?t=576768 this should help you out.
http://forum.xda-developers.com/showthread.php?t=576768 this should help you out.
Click to expand...
Click to collapse
These instructions, mark, is for 32B, looking at the bootloader info our friend posted, seems like his is a 32A. Or perhaps this is the problem?
I believe flashing the wrong ROM would brick the device.
Looks like 32B may be the google dev device, this one is the MT3G (I think 32A?).
Sorry my bad,but the the basic details are there to help you out.
Tried flashing RA recovery:
fastboot flash recovery ../../recovery-RA-sapphire-v1.7.0H.img
sending 'recovery' (4520 KB)... OKAY [ 1.720s]
writing 'recovery'... OKAY [ 2.375s]
finished. total time: 4.096s
Rebooted holding down back, but still appears to be regular recovery mode...
EDIT: I wonder... just read this:
"Use the H/G version if your Magic is HTC branded (PVT 32A board)/Google branded (PVT 32B board)."
This is from T-Mobile, which I guess means Google branded? Thus, it should say 32B in the recovery mode... but says 32A. Maybe I could get a different img onto the micro SD (32B version I guess) and try to hboot?
EDIT 2: Scratch that... looks like it is 32A motherboard... they changed for the 1.2 version.
Tried running the official RUU found here: http://forum.xda-developers.com/showthread.php?t=659403 but I guess that actually requires the device to be booted up fully... not in fastboot lol.
your friend installed the wrong radio and fastboot for his device
thats your problem - he is using the hboot and radio for NON - 3.5MM jack versions
those versions use the 2.x radio and spl is different as well... - You should look at threads about that device specifically... your friend obviously does not read and/or search enough and assumes old instructions are good for his device
http://forum.xda-developers.com/showthread.php?t=622530
edit: and yes - with some simple reading skills I pulled that thread out of the sticky rom bible and deduced how to fix the device
lol - you people need to learn to read more and ESPECIALLY your friend .... half the people with this device rooting it have no idea how to read/search for information
HUZZAH!! I managed to find a T-Mobile MT3G 1.2 shipping rom on some post on this forum (sorry for no credit, I've been scouring trying tons of different things... if anyone knows what I'm talking about, please reply for others!). I then had to get that on the microSD to install with hboot... The funny part is I couldn't find a microSD adapter, so I actually mcguyvered the most expensive microSD adapter ever... I used the HD2 I had laying around as the most expensive microSD adapter ever to move the rom onto the MY3G's card, haha.
technogecko6 said:
HUZZAH!! I managed to find a T-Mobile MT3G 1.2 shipping rom on some post on this forum (sorry for no credit, I've been scouring trying tons of different things... if anyone knows what I'm talking about, please reply for others!). I then had to get that on the microSD to install with hboot... The funny part is I couldn't find a microSD adapter, so I actually mcguyvered the most expensive microSD adapter ever... I used the HD2 I had laying around as the most expensive microSD adapter ever to move the rom onto the MY3G's card, haha.
Click to expand...
Click to collapse
you didnt really need to do that - if you just follow the instructions in the rooting guide it tells you how to fastboot the radio and spl you need and then gives further direction...
fastboot flash radio radio.img
fastboot flash hboot hboot_7201A_1.33.0013G_091021.nbo
fastboot flash recovery recovery-RA-sapphire-v1.5.2G.img
fastboot reboot-bootloader
the files are located in the link to cursordroids thread
le sigh - dunno why you didnt even bother to read the post?
you people are beyond helping...
I was typing my reply without even knowing your new post was there
This is a common problem with the new mytouch 1.2, I flash the radio and ect... PERFECTLY, just go ahead and try to flash amon ra's recovery, you should still be able to do that and do a full wipe and flash a rom...worked for me
Mod. edit: not dev related, moved to general

1.33.2005

Hi all,
I'm a complete newbie. Most of you will have little patience for me but I'm hoping to find at least a couple of you willing to help me out. Here's my story. I thought it would be cool to by a used HTC Magic from Ebay to use with AT&T. The guy that sold it to me put Froyo on it and I was excited to have the latest Android on the phone.
I got it yesterday and the trouble started quasi immediately. I will post the exact things that happened as well as I can.
1. First the phone was rebooting on its own. It would make it as far as the home screen with the icons but if I tried to press anything, like contacts, it would reboot.
2. Then it eventually took me to the recovery screen where, after reading several threads, I downloaded the newest (not ROM, but whatever the first thing is on that page that you can update it).
3. Then the phone stopped rebooting itself but I couldn't get to the market or email because the dumbass that sold me the phone hadn't wiped his user info. So I googled again and was told to factory reset.
4. I tried factory reset 3 times and it did nothing.
5. Went back to the recovery page to see if that had anything that would help and I clicked Fix Permissions and let it run that.
6. Still no change when it came to wiping his user info.
7. Got frustrated and googled again. This time I saw a thread that said you should reboot using the up/down key and power. Did that.
Since then, I've had a blinking HTC green screen. At some point during this process I made it to what looks like a basic OS window from which I copied the following information:
sapphire pvt 32b eng s-off h
1.33.2005
radio-2.22.19.261
apr 20 2009, 15:30:43
hboot
What do you suggest I do now? I emailed the guy who sold me the phone because I figure if he put it on there, he can put it back. Or at least send me the files. Not sure he will care or want to help me. Besides, doesn't seem like he got it right.
I am willing to try to fix this myself but I don't want to start downloading files and flashing the phone only to destroy it. Guidance is needed.
Thank you in advance.
Seelier.
Metuchen, NJ
If the device actually booting then you should be alright, just sounds as if the guy who sold it to you flashed it with something crappy.
1.33.2005 is your SPL version, and that particular SPL version is what's referred to as an "engineering SPL" which allows you to flash roms and custom recoveries via fastboot (basically). For more info you can read here , but it doesn't overly concern you now.
To flash any roms yourself (more easily) you will need a custom recovery such as Amon_RA's Recovery, which you can download in this thread. Follow his instructions. You may already have this but you didn't say so.
Once you have done so, I suggest you install a ROM such as CyanogenMod, which you can get from here. Again, instructions on how-to flash it are in his thread. Essentially though, it is as follows:
- Put cyanogenmod rom on your SD card.
- Boot in to recovery screen (press the ON button whilst holding HOME)
- Wipe data/dalvik-cache
- Flash .zip from SD card & choose the file you put there
- Reboot the phone and wait patiently
Edit: Just to reassure, the things that tend to "brick" phones are flashing SPL and Radio updates, which you don't appear to need to do. Flashing roms very rarely causes devices to break, it is usually just the rom at fault.
Not Development related. Moved to General.
OP, next time you post make sure you post in the correct section or I'll close the thread.

Stuck at splash after rooting us tmo mt3g

Okay I'm lost, weary of trying things as I'm not 100% clear on alot of this stuff.
Here's what I did, I recently had tmo replace my original mt3g, sadly the replacement gave the version is older or whatever message. I've gone through the steps and now I'm stuck at the boot up splash screen. I'll post what i've done so far, hopefully someone can identify whats gone wrong and steer me
Ok I followed the instructions here:
h~p://theunlockr.com/2009/08/14/how-to-root-your-mytouch-3g/
h~p://theunlockr.com/2010/03/10/how-to-create-a-goldcard/
h~p://theunlockr.com/2009/10/06/how-to-set-up-adb-usb-drivers-for-android-devices/
That worked, the phone was rooted and booting.
I then installed the the AMON_RA recovery img and I've tried both flavors
recovery-RA-sapphire-v1.7.0H.img
recovery-RA-sapphire-v1.7.0G.img
I forget at this point, but I think the G didn't work for me, but i have H working.
From there I began following the instructions on cynogen mod to install...
h~p://forum.cyanogenmod.com/topic/394-cyanogenmod-5-for-dreammagic-mean-lean-pastry-machine-v508-06192010/
h~p://forum.cyanogenmod.com/topic/278-installation-support-line-cyanogenmod-5-for-dreammagic/
h~p://wiki.cyanogenmod.com/index.php?title=Full_Update_Guide_-_HTC_Magic_%2832B%29
I booted the the recovery, wiped everything, installed the cm base, then gapps and powered down and powered on, stuck at splash...
I've tried a few variances and just to make sure, i went back to recovery and installed the Rom-RAv1.1.0H-signed-update.zip again to make sure it was working. It booted right up.
Ok so here is my phones info from the vol down + power hboot menu
sapphire pvt 32b eng s-off h
hboot-1.33.2005(sapp30000)
radio-3.22.20.17
apr 20 2009,15:30:43
I'm not sure of what else to include, my minds melted at this point.
It was so easy to root my old mt3g, this new model just makes me feel like an idiot.
*edit* Here is the info from my phones settings>about with the Rom-RAv1.1.0H-signed-update.zip loaded
Model: Ion
Firmware 1.5
Baseband 62.525.20.18h_3.22.20.17
kernel 2.6.27-cb85e129
[email protected] #3
Build #
cr843
Hmm
Did you root your phone using the MyTouch Rooting guide? Or the MyTouch 1.2 (has 3.5 mm headphone jack) guide? From what it sounds like you got the updated model of the MT3G.
If you used the Rooting guide for the old model and you have the new one, you will have issues. Heres the link:
h~p://theunlockr.com/2010/03/11/how-to-root-the-mytouch-1-2-and-fender-mytouch/
If I'm right, you should have no issue re-rooting your phone.
Good luck, hope this helps.
<grin> that's another aspect of my mind melting yesterday, making sure i wasn't following instructions for the wrong version of the phone.
I have the original base model, no 3.5mm.
Tmo sent me the replacement phone about a month ago.
So that said, I think I followed the original versions instructions.
Flashing back to the old version
Rom-RAv1.1.0H-signed-update.zip
the phones worked fine all night and I got it doing the things i rooted for in the first place, sharing my cells inet to my laptop etc. so I can live with this until the weekend I suppose but still want to figure out why i couldn't get cynogen mod 5 running.
Okay i have an idea what might be going on, just my guess at this point.
I think i have mix matched mt3g-a and mt3g-b files.
Here's my thinking...
recovery-RA-sapphire-v1.7.0H.img - works
recovery-RA-sapphire-v1.7.0G.img - doesn't work, sits at splash screen
Rom-RAv1.1.0H-signed-update.zip - works, but shows up in settings>about Model = ION. I think Ion is the mt3g-a flavor...
I tried today to use flashrec, the first backup of my recovery failed. tried again it reported success. closed app opened and it gave me the option to flash the cyno recovery or restor mine, i flashed the CM and when i rebooted to the recovery it would just sit there at the splash screen. i could still boot normally and into the fastboot menu... I then went and downloaded the CM 5.08 install from a mirror.
I also tried the the newest cm v6 rc2, and update-cm-4.2.15.1-signed.zip
All stuck at splash on boot.
Fixed and working, I think it was my radio. I had a mirror post over ta the CM forums, and I was pointed to the correct radio and after flashing the radio and the g version of the recovery it came up, then flashed CM and Gapps and it worked...
I was also told to update my spl, but havn't done that part yet.
*edit* username is globeadue there, post should come up with a username search

Categories

Resources