Related
Hello all, thank you for this great resource and any insight you can provide.
I need some of your wisdom, as I've been banging my head against a brick wall for about two weeks now, trying to root my T-Mobile MyTouch 1.2 (HTC Magic) with the 3.5" jack.
I did a couple hours of homework and began the process, but currently am stuck at the HTC Magic splash screen on normal boot up. I cannot boot into recovery; I have tried flashing both the Amon Ra versions, H and G. I can, however, boot into hboot and fastboot menu options, so it my understanding that my phone is salvageable with the right tools and process. Unfortunately, I was given bad advice—or incorrectly followed good advice—and now all the instructions I find to restore functionality to my phone don't go smoothly.
I've spent countless hours trying proposed found threads here (mostly) and other resources, but while the solutions sound like the apply to my hardware, they fail to complete successfully.
I have created two goldcards, both appear to work, as I have been able to flash a sappimg.zip image initially, but currently trying to flash again to remedy problems hangs and requires me to pull the battery. It usually hangs at the initial unzipping or at updating radio_v2. Via fastboot, I have been able to flash the stock hboot.nbo and reflash different versions. I was able to flash to the stock radio once, but have had problems trying to reflash images, trying to correct the issue.
These details have read different things at different stages in trying proposed solutions, but currently the info on fastboot menu reads:
SAPPHIRE UNKNOWN 32A SHIP S-ON H
HBOOT-1.33.0009 (SAPP31000)
CPLD-13
RADIO-6.35.10.18
At this moment, I've stopped trying to find answers on the forum because I've spent countless hours failing and more importantly, fear that if I continue applying incorrect solutions, I will irreversibly damage my phone. I hope that someone can provide some advice tailored to my situation.
Thank you for reading and for your reply. I understand that any advice I receive is at my own risk to follow.
Option one: flash the .nbo file for te engineerings 1.33.2010 spl and thz flash the g recovery.
Option two: flash the sappimg to revert back to stock then stsrt all over again
Option three: flash the stock sappimg and stay at stock thanking jesus you didnt **** anything up.
Sent from my HTC Magic using XDA App
You did not read the mytouch 1.2 rooting guide correctly. This phone can only run stock spl and radio. Read the guide at the unlockr. After using the goldcard you should have flashed stock spl and radio using fastboot.
NetrixTardis said:
You did not read the mytouch 1.2 rooting guide correctly. This phone can only run stock spl and radio. Read the guide at the unlockr. After using the goldcard you should have flashed stock spl and radio using fastboot.
Click to expand...
Click to collapse
I tried the files and process indicated on Unlockr several times. The files and process located here: theunlockr.com/2010/03/11/how-to-root-the-mytouch-1-2-and-fender-mytouch/
Attempting again, just now, I run into the same roadblock as reported in my initial post: Immediately after clicking the action button to execute the update, the process hangs at 'Unzipping' on step [1] SYSTEM, where the progress bar never moves, and pulling the battery is the only thing that works (unfortunately, since I'm warned not to power off the device!).
knny1491 said:
Option one: flash the .nbo file for te engineerings 1.33.2010 spl and thz flash the g recovery.
Click to expand...
Click to collapse
Thank you so much for your response.
Attempting option 1, I get the following messaging in the terminal while trying to flash the hboot.img (not nb0, is this wrong?) downloaded from the 'Magic SPL HBOOT collection' thread located here: forum.xda-developers.com/showthread.php?t=529019
sending 'hboot' (512 KB)... OKAY
writing 'hboot'... INFOsignature checking...
FAILED (remote: signature verify fail)
In the previous reply to another helpful commenter I describe another error I get while attempting to update the sappimg provided by Unlockr.
Further insight is very much appreciated.
so this is the second time I'm seeing this exact problem... this is keeping me from rooting this mytouch. but last time i saw this problem I believe it was solved.. i can't remember where i saw it though! I'll look and look until i find it then i'll post it here!
but in the mean time you can try unrooting it until the problem is solved?
http://forum.xda-developers.com/showthread.php?t=665814
lbsk8addict said:
last time i saw this problem I believe it was solved.. i can't remember where i saw it though! I'll look and look until i find it then i'll post it here!
Click to expand...
Click to collapse
Thank you! I hope that you do.
lbsk8addict said:
but in the mean time you can try unrooting it until the problem is solved?
forum.xda-developers.com/showthread.php?t=665814
Click to expand...
Click to collapse
I've visited that thread before in my days of lurking, but didn't attempt it (I don't think—I've tried so many things, it's hard to remember fully at this point).
I think all I have right now are goldcards. I hope a stock SD card isn't needed, or I'll have to figure out how to restore a Kingston microSD or buy another.
Thanks again for all of your input.
lbsk8addict said:
but in the mean time you can try unrooting it until the problem is solved?
forum.xda-developers.com/showthread.php?t=665814
Click to expand...
Click to collapse
Follow up, attempting to update to MT3G 1.2 Sappimg (BUILD# 2.10.531.4) downloaded via that link, I encounter the second error documented in my initial post, the update process hangs at updating step [2] RADIO_V2. The red progress bar stops at about 95%. Pulling the battery out is the only way to escape.
I think, and this is just a gut-level guess, that my problem stems from a corrupt radio version. Any one have an opinion or advice about that?
After pulling the battery and booting back into fastboot, my versioning reads as follows:
SAPPHIRE PVT 32A SHIP S-ON G
HBOOT-1.33.0013 (SAPP31000)
CPLD-13
RADIO 6.35.10.18
You have a 32a radio with a 32b spl, during the root process you are supposed to be able to revert that. What we need to do is get you onto an eng spl so you can fastboot erase radio, fastboot flash radio, then flash the correct hboot aka the stock one. Right now you cant fastboot or anything aka you are semi bricked. Only thing i can say is let it sit o the charger for as long as possible for the sappimg update and pray lots n lots.
Sent from my HTC Magic using XDA App
knny1491 said:
You have a 32a radio with a 32b spl, during the root process you are supposed to be able to revert that.
Click to expand...
Click to collapse
Thank you so much for the follow up. I wish the news were better!
How can you tell that I have a 32b SPL? By the errors I'm experiencing? The SAPP310000? Just guesses here. I don't see that on my phone so, I'm curious to learn.
knny1491 said:
What we need to do is get you onto an eng spl so you can fastboot erase radio, fastboot flash radio, then flash the correct hboot aka the stock one. Right now you cant fastboot or anything aka you are semi bricked. Only thing i can say is let it sit o the charger for as long as possible for the sappimg update and pray lots n lots.
Click to expand...
Click to collapse
Are you advising my to sit on my hands, keeping my phone charged, until, hopefully, the development community comes up with a new sappimg solution? Or are you saying to preform the 1.33.2010 engineering SPL update until success or my phone dies?
I was stating to do the update where it freezes or hangs on the radio and let it sit for a crazy amount of time with praers, the spl version is defing by the numbers i the 1.33.0013 etc area, 32a users have 1.76.xxxx sp numbers while 32b users have 1.33.xxxx and after looking i see you are on the stouch 1.2 spl which is why fastbooting anything will not work. Quick question though did you try flashing te spl and radio BEFORE the recovery?
Sent from my HTC Magic using XDA App
knny1491 said:
I was stating to do the update where it freezes or hangs on the radio and let it sit for a crazy amount of time with praers, the spl version is defing by the numbers i the 1.33.0013 etc area, 32a users have 1.76.xxxx sp numbers while 32b users have 1.33.xxxx and after looking i see you are on the stouch 1.2 spl which is why fastbooting anything will not work.
Click to expand...
Click to collapse
Thank you for the reply. Good to know, as I was under the impression that all T-Mobile MyTouch 1.2 phones were 32A, and 1.33.0013 was the desired and appropriate version for 32A.
knny1491 said:
Quick question though did you try flashing te spl and radio BEFORE the recovery
Click to expand...
Click to collapse
I initially tried followed the procedure here: http://wiki.cyanogenmod.com/index.php/Full_Update_Guide_-_Fender/1.2
Where, I updated the SAPPIMG via goldcard, then through fastboot, I flashed the radio, hboot, and recovery. But, I wasn't able to boot to recovery after that process, for whatever reason, so I began trying other procedures from other sources, which in all likelihood took me further away from the solution instead of closer.
If the current attempt of updating radio_v2 until success or power battery dies (which has been hung for about 30 minutes so far) does not end successfully, should I try flashing a different hboot or radio? Or any other suggestions?
Thanks again for your continued help. I'm going to try to get some more attention to this thread to hopefully get more possible solutions.
If the radio doesnt flash then we have to question why the recovery didnt load, the g version is the correct version given there is only one spl for us 1.2 users and it is a google spl. That is why you flash radio then spl then recovery in that order so nothing messes up. The thing is you have to flash a radio before spl, yet you hav the spl yet NOT THE RADIO which leaves me to believe you accidentalky did the spl first n not the radio first.
Sent from my HTC Magic using XDA App
knny1491 said:
If the radio doesnt flash then we have to question why the recovery didnt load, the g version is the correct version given there is only one spl for us 1.2 users and it is a google spl. That is why you flash radio then spl then recovery in that order so nothing messes up. The thing is you have to flash a radio before spl, yet you hav the spl yet NOT THE RADIO which leaves me to believe you accidentalky did the spl first n not the radio first.
Click to expand...
Click to collapse
Okay, thanks so much for the continued insight.
I think, I flashed the radio down to original, but encountered some problem, misdiagnosed it, and flashed it back up again. Now it's been about 3 weeks of messing with this phone for a couple hours a day, so, unfortunately, it's hard to remember all that I've tried. If what you're saying is true, then yes, I must have accidentally flashed the SPL before the radio. Is there a remedy for this? I've been pouring over this forum searching for "can't flash radio" (forum.xda-developers.com/search.php?searchid=39519193&pp=25&page=1) and so far I've read people claiming to have had successfully deleting their radios completely and reinstalling. Is this an option? Any other suggestions?
I will PayPal $30 to you, anyone who can give me a solution to where this phone is working and rooted. Alternatively, I live in Los Angeles, if anyone can recommend a good, knowledgeable, phone repair shop.
it's really strange why that didn't work for you.
My steps were as follows:
**make sure phone is fully charged**
pre 1) create goldcard
1) place sappimg.zip on gold card
2) boot phone with goldcard to flash using Vold down + power
3) let it reboot - should boot up to the "htc magic" logo -- for me it never loaded back up to stock 1.6, I had to pull the battery.
4) boot to fastboot using back + power
5) connect phone to PC and verified it was recognized using "fastboot devices"
6) make sure you have stock radio and spl in your Android SDK's \tools
7) performed the following:
fastboot flash radio radio.img (or whatever the filename you have for the stock radio)
fastboot flash hboot hboot.nb0 (or whatever the filename you have for the stock hboot)
fastboot flash recovery recovery.img (or whatever the filename you have for amon_ra or clockwork or cm recovery)
fastboot reboot-bootloader (to make sure that stock radio and SPL are loaded again)
8) reboot to recovery using home+power
*from this point on, you no longer need to use your goldcard
9) have new ROM .zip on root of your SD card, option flash from zip
10) ???
11) profit
NetrixTardis said:
it's really strange why that didn't work for you.
My steps were as follows:
**make sure phone is fully charged**
pre 1) create goldcard
1) place sappimg.zip on gold card
2) boot phone with goldcard to flash using Vold down + power
Click to expand...
Click to collapse
Thank you for your continued feedback!
I think you've listed the standard recipe for rooting this phone. I believe you. Unfortunately, something in my phone has gone askew (certainly my error) at this point and the "standard" just isn't working now. As is, and for the past 3 weeks, the process you describe dies at step 2. It hangs while updating RADIO_v2 (at whatever position in the list of updates it is for a given SAPPIMG file). Also, attempting to flash a stock radio.img via fastboot also hangs. Both updates send just fine, but hang at updating around 95%.
I've also been getting some advice from another member, knny1491. On this page, above, you'll see he hypothesises what my error is:
knny1491 said:
If the radio doesnt flash then we have to question why the recovery didnt load, the g version is the correct version given there is only one spl for us 1.2 users and it is a google spl. That is why you flash radio then spl then recovery in that order so nothing messes up. The thing is you have to flash a radio before spl, yet you hav the spl yet NOT THE RADIO which leaves me to believe you accidentalky did the spl first n not the radio first.
Click to expand...
Click to collapse
That sounds plausible that I did flash things in the wrong order. I'll accept that. I've been messing with it so much, I'm lucky it works at all. So now, and still, my question is where to go from here? Do you know anything about this radio/SPL relationship and how to remedy this current conflict, NetrixTardis?
Thanks again.
Possibly try to re download the sappimg from the mgic spl thread?
I was just thinking, if your goal at this point is to have the phone usable again regardless of root; why not try the RUU exe ? If i unserstand what it does, it should flash the phone back to stock (radio, spl, recovery,ROM etc). You'll have a phone as if you just unboxed it.
Thats if i understand what the ROM Upgrade Utility (RUU) does correctly. Someone should be able to correct me...
NetrixTardis said:
I was just thinking, if your goal at this point is to have the phone usable again regardless of root; why not try the RUU exe ? If i unserstand what it does, it should flash the phone back to stock (radio, spl, recovery,ROM etc). You'll have a phone as if you just unboxed it.
Thats if i understand what the ROM Upgrade Utility (RUU) does correctly. Someone should be able to correct me...
Click to expand...
Click to collapse
Thanks for the idea! I'll do some research on that. If anyone else can give any insight into if this may help restore my phone, please chime in!
I'd like root, but anything that gets the basic utility of the phone back would be great at this point (I've been using a old razr as a replacement while mine is hosed). I think an official 2.2 update is coming out from T-Mobile soon. I can wait for that.
NetrixTardis said:
Thats if i understand what the ROM Upgrade Utility (RUU) does correctly. Someone should be able to correct me...
Click to expand...
Click to collapse
If this is a good potential solution, could someone please direct me to which RUU to use? I've located the "[ROM] Official HTC Sapphire/Magic/MT3G RUU ROM Links" thread here: forum.xda-developers.com/showthread.php?t=659403
There really is a great abundance of options. I'm guessing I should go for the latest [MT3G 1.2] download which is:
36) [xda-ftp] [4shared] 2.10.531.4 T-Mobile USA DRD35
36) 2.10.531.4 1.33.0013G 2.22.23.02 N T-MOB010
I'll want a few hours or perhaps a day before attempting this process, in hopes that some helpful reader will provide his input if this is a good or bad thing to do as far as getting the phone working again.
Thanks!
The phonecompany 3 updated my phone, when it went for repairs, so now it has that horrible HTC Sense on it. It asked them to remove it, but they refuse, and actually IN the shop tell me to hack it.
Now my question comes, because no-one seems to know anything about this.
I have tried searching the internet, and this forum, but information on how to do it, seems to be different from the people you ask.
I have a 3 mobile HTC Magic 32A branded HTC.
Radio 6.35.x
CPLD-12
HBOOT 1.76.0009
What is required? I have read something that I need to replace the "SPL". Is that the HBOOT, or what? I have found some guides that refer to me as to going into my command prompt and somehow comunicating with my phone... how on earth is that possible?
This is where I am right now, and the more I search and read, the more confused I get, so I hope someone can clarify the process of rooting a magic. i have rooted my old Desire before (Not mine anymore), with a so-called "risk-free" guide. Easy as pi, once you read 5 lines, and downloaded 2 files.
Please clarify this for me, before I loose my hair over this.
EDIT: I have the phone rooted, with an app called "Universal AndRoot". It seems to have root, but no matter what bootloader I try clockworkmod or RA, the first crashes, and reboots the phone, the lather freezes within seconds... is it proper rooted, or just "half"?
What to do?
AntaeusDK said:
The phonecompany 3 updated my phone, when it went for repairs, so now it has that horrible HTC Sense on it. It asked them to remove it, but they refuse, and actually IN the shop tell me to hack it.
Now my question comes, because no-one seems to know anything about this.
I have tried searching the internet, and this forum, but information on how to do it, seems to be different from the people you ask.
I have a 3 mobile HTC Magic 32A branded HTC.
Radio 6.35.x
CPLD-12
HBOOT 1.76.0009
What is required? I have read something that I need to replace the "SPL". Is that the HBOOT, or what? I have found some guides that refer to me as to going into my command prompt and somehow comunicating with my phone... how on earth is that possible?
This is where I am right now, and the more I search and read, the more confused I get, so I hope someone can clarify the process of rooting a magic. i have rooted my old Desire before (Not mine anymore), with a so-called "risk-free" guide. Easy as pi, once you read 5 lines, and downloaded 2 files.
Please clarify this for me, before I loose my hair over this.
EDIT: I have the phone rooted, with an app called "Universal AndRoot". It seems to have root, but no matter what bootloader I try clockworkmod or RA, the first crashes, and reboots the phone, the lather freezes within seconds... is it proper rooted, or just "half"?
What to do?
Click to expand...
Click to collapse
those are not bootloaders... those are recovery images.
You have a 32A, which means that you need an EBI1 recovery image. You are probably installing EBI0 recoveries, which won't work.
Thank you for clarifying.
So clockworkmod are "EBI0" recoveries.
What are "EBI1" recoveries then?
Use the recovery from this thread http://forum.xda-developers.com/showthread.php?t=816345
PS: Your phone is running what is called "New radio"/NR/6.35. If you want to run stock Cyanogenmod or anything like that you need to downgrade your radio and SPL. A good FroYo ROM for 6.35 is FroyoRider.
recovery-AR-magic+-1.7.0.1?
How do I install it? With RecoveryFlasher?
There are instructions on amonra thread to install recovery different ways. Prob through terminal for u would be easy
Sent from my HTC Magic SparksMod using XDA App
johnson8cyl said:
There are instructions on amonra thread to install recovery different ways. Prob through terminal for u would be easy
Sent from my HTC Magic SparksMod using XDA App
Click to expand...
Click to collapse
amonra? I am not sure what that means, but I will search the internet for how to install a recovery image on ones phone (32A HTC Magic)
I type this in a terminal "flash_image recovery /sdcard/1.7.0.1.img" without quotes, yes I renamed it.
It says: erroroutput[usage: flash_image partition file.img
What am I doing wrong now?
Nobody knows?
Do u have ask set up and the ability to fastboot flash recovery? I would do that
Sent from my HTC Magic SparksMod using XDA App
If I have what?
Sorry. Gotta love auto spell. I typed sdk. U have to have android sdk to set up adb to control your phone through your computer. Then u can use fastboot flash. First u need an Eng spl with the right radio to use it.
Sent from my HTC Magic SparksMod using XDA App
Sounds awfully complicated.
Thanks for clarifying however.
So my wife just upgraded her phone and i was left with a stock MyTouch 3g with 3.5mm headphone jack and I thought I would expand my Android knowledge base and see what I could do with it. I am not knew to Android and I have a Samsung Vibrant that I can pretty much do whatever I want with. The Galaxy line is extremely easy compared to this device.
So I did my fair share or reading and research and was able to root the phone with Universal Androot and installed busybox via titanium backup. I downloaded ROM manager from the market and flashed clockwork recovery. I used recovery to installl CM 5.0.8 DS and once it reboots in wont load past the mytouch splash.
This is what I started with:
SAPPHIRE PVT 32A SHIP S-ON G
HBOOT-1.33.0013
CPLD-13
RADIO-2.22.23.02
Oct 21 2009, 22:33:27
And this is what it reads now:
SAPPHIRE UNKNOWN 32B ENG S-OFF H
HBOOT-1.33.2010 (SAPP31000)
CPLD-13
RADIO-2.22.23.02
Jun 2 2009, 17:27:03
I read that Binary said that it is really a 32B not an A so to stick with the B ROMs. I can also access fastboot and recovery.
The easy part with the Vibrant is that if I screw up the phone you can just simply Odin back to stock and start over, but the mytouch is a little more complex than that. So basically I want to get back to stock and start over. There are so many threads and links that say user friendly but I didn't find it quite user friendly. I must just be spoiled with the Galaxy.
Any help would be greatly appreciated. It's not a rush or it's not my daily driver. Just a toy phone now to learn on.
Thanks!
mod edit because of inaccurate information.
So you are saying if I just follow the normal root guide for the fender 1.2 that I should be good?
Sent from my GT-I9000 using XDA App
CBATESY said:
usually any of the 3.5mm jack phones are 32a devices. 32b is the original mt3g. ones with the jack in the top is a mt3g 1.2 or 32a. If you have recovery working you can use that to restore back to factory or installed sapping.img
here something to help you out .
http://wiki.cyanogenmod.com/index.php?title=HTC_Magic
Click to expand...
Click to collapse
NO! Damn it! Listen to me everybody! The 1.2 device (Fender, etc) are a 32A/32B hybrid. The ONLY thing that makes this phone ANY different than the regular 23B MyTouch devices is the additional ram. That's it! You CANNOT fit a 32A ROM on the device because it lacks the internal storage. Even if you COULD the kernel for that rom would require a 32A radio. You cannot use a 32A radio because the 1.33.0013 32A s-ON spl requires the 32B radio. And it requires a 32B radio else it will brick. The 1.33.0013 is the S-ON stock SPL that the phone requires to use the memory map. If you try the Engineering SPL (1.33.2010 32B S-ON) the phone might boot, but you will not have touch screen or the use of the headphone jack because of the different drivers and memory map. When you flash the Engineering SPL it will read 32B because that is what is needed to flash the custom recovery and roms. However your device will not work properly because it's a 32A/32B hybrid. You need the 32A stock firmware (1.33.0013 S-ON) for the phone to operate. You also need the appropriate 32B radio and rom as well.
I have the phone and I've had it since it's release. I started off by making custom roms for it and ports before roms were using VoxLuna's driver patch. Trust me when I say that I know a little about this damn phone!
You know what... to hell with it. Do whatever you want. Don't be sending me private messages begging for help when you brick your device because you think it's a 32A.
custom ported rom #1
custom ported rom #2
custom ported rom #3
custom rom #1
They all require 1.33.0013 S-ON with 32B radio.
offdutyninja808 said:
SAPPHIRE UNKNOWN 32B ENG S-OFF H
HBOOT-1.33.2010 (SAPP31000)
Click to expand...
Click to collapse
The problem. You forgot to mention that you also flashed a non-perfected SPL at some point before flashing CM 5.0.8. You need to get that fixed. Luckily you can fix it without a goldcard since you've already got S-OFF.
Download these:
hboot.nb0 for myTouch 1.2 only
Amon Ra 1.7.0-G Recovery
Go to this URL and follow the steps to get ADB setup if you don't already have it. Then go here and follow steps 7, 8, and 9. In step 7, you should only need to run:
fastboot flash hboot hboot.nb0 (the 0 at the end of this line is a zero not an oh).
fastboot flash recovery recovery.img
fastboot reboot-bootloader
After that just reflash CM 5.0.8, although I'm using CM 6.1 and it's just as good, but with the perks of Android 2.2. I would suggest reading through that thread I linked to get more familiarity.
Lastly, I will warn you that this isn't the easiest way to get your phone fixed, but this is the way that I learned about my phone, so it should help you out in that aspect. I'm sure mumilover or someone else may come along with a simpler solution.
If you have any problems, let us know here.
Binary100100 said:
NO! Damn it! Listen to me everybody! The 1.2 device (Fender, etc) are a 32A/32B hybrid. The ONLY thing that makes this phone ANY different than the regular 23B MyTouch devices is the additional ram. That's it! You CANNOT fit a 32A ROM on the device because it lacks the internal storage. Even if you COULD the kernel for that rom would require a 32A radio. You cannot use a 32A radio because the 1.33.0013 32A s-ON spl requires the 32B radio. And it requires a 32B radio else it will brick. The 1.33.0013 is the S-ON stock SPL that the phone requires to use the memory map. If you try the Engineering SPL (1.33.2010 32B S-ON) the phone might boot, but you will not have touch screen or the use of the headphone jack because of the different drivers and memory map. When you flash the Engineering SPL it will read 32B because that is what is needed to flash the custom recovery and roms. However your device will not work properly because it's a 32A/32B hybrid. You need the 32A stock firmware (1.33.0013 S-ON) for the phone to operate. You also need the appropriate 32B radio and rom as well.
I have the phone and I've had it since it's release. I started off by making custom roms for it and ports before roms were using VoxLuna's driver patch. Trust me when I say that I know a little about this damn phone!
You know what... to hell with it. Do whatever you want. Don't be sending me private messages begging for help when you brick your device because you think it's a 32A.
Click to expand...
Click to collapse
And I thought the Vibrant forums were hostile. I am glad that you have had your phone for so long and I am quite sure you know what you are talking about. Like I stated, this phone is just sitting around the house collecting dust and thought I would mess with it. If I brick it... great. If I make it the fastest MyTouch it can be... great.
Don't get me wrong, I appreciate what you and all the other developers and contributors do for random users like myself, but give a guy a break. You have to admit that this phone is a little dated and it's like knowing how to run Windows Vista and 7 then going back to do the same things on a Commadore.
DonJuan692006 said:
The problem. You forgot to mention that you also flashed a non-perfected SPL at some point before flashing CM 5.0.8. You need to get that fixed. Luckily you can fix it without a goldcard since you've already got S-OFF.
Download these:
hboot.nb0 for myTouch 1.2 only
Amon Ra 1.7.0-G Recovery
Go to this URL and follow the steps to get ADB setup if you don't already have it. Then go here and follow steps 7, 8, and 9. In step 7, you should only need to run:
fastboot flash hboot hboot.nb0 (the 0 at the end of this line is a zero not an oh).
fastboot flash recovery recovery.img
fastboot reboot-bootloader
After that just reflash CM 5.0.8, although I'm using CM 6.1 and it's just as good, but with the perks of Android 2.2. I would suggest reading through that thread I linked to get more familiarity.
Lastly, I will warn you that this isn't the easiest way to get your phone fixed, but this is the way that I learned about my phone, so it should help you out in that aspect. I'm sure mumilover or someone else may come along with a simpler solution.
If you have any problems, let us know here.
Click to expand...
Click to collapse
Exactly, all he needs is a custom G recovery (which he should have) and then flash the 1.33.0013 stock spl BACK on. Afterwards, he can flash any 32B rom he wants and it should work as long as it's later than CM-4.2.15.
DonJuan692006 said:
The problem. You forgot to mention that you also flashed a non-perfected SPL at some point before flashing CM 5.0.8. You need to get that fixed. Luckily you can fix it without a goldcard since you've already got S-OFF.
Download these:
hboot.nb0 for myTouch 1.2 only
Amon Ra 1.7.0-G Recovery
Go to this URL and follow the steps to get ADB setup if you don't already have it. Then go here and follow steps 7, 8, and 9. In step 7, you should only need to run:
fastboot flash hboot hboot.nb0 (the 0 at the end of this line is a zero not an oh).
fastboot flash recovery recovery.img
fastboot reboot-bootloader
After that just reflash CM 5.0.8, although I'm using CM 6.1 and it's just as good, but with the perks of Android 2.2. I would suggest reading through that thread I linked to get more familiarity.
Lastly, I will warn you that this isn't the easiest way to get your phone fixed, but this is the way that I learned about my phone, so it should help you out in that aspect. I'm sure mumilover or someone else may come along with a simpler solution.
If you have any problems, let us know here.
Click to expand...
Click to collapse
Thank you for the non-violent approach. I know how it is when you have a new guy just blowing his phone up and he goes screaming for help. Not what I was trying to do. Just tinkering with a new device to get some more know-how under the belt.
Much appreciated, Don!
I will let you know what I can get accomplished with your advice.
offdutyninja808 said:
And I thought the Vibrant forums were hostile. I am glad that you have had your phone for so long and I am quite sure you know what you are talking about. Like I stated, this phone is just sitting around the house collecting dust and thought I would mess with it. If I brick it... great. If I make it the fastest MyTouch it can be... great.
Don't get me wrong, I appreciate what you and all the other developers and contributors do for random users like myself, but give a guy a break. You have to admit that this phone is a little dated and it's like knowing how to run Windows Vista and 7 then going back to do the same things on a Commadore.
Click to expand...
Click to collapse
He wasn't fussing at you, he was getting at the other guy for feeding you false information.
Sent from my HTC Magic using Tapatalk
My apologies, Binary. Following forums over time you tend to see so much hostility over pretty much nothing. It's a learning experience. Just as I had to learn my other phone, some things the hard way, I will be able to steer people in the right direction and help others after I get this one down.
offdutyninja808 said:
And I thought the Vibrant forums were hostile. I am glad that you have had your phone for so long and I am quite sure you know what you are talking about. Like I stated, this phone is just sitting around the house collecting dust and thought I would mess with it. If I brick it... great. If I make it the fastest MyTouch it can be... great.
Don't get me wrong, I appreciate what you and all the other developers and contributors do for random users like myself, but give a guy a break. You have to admit that this phone is a little dated and it's like knowing how to run Windows Vista and 7 then going back to do the same things on a Commadore.
Click to expand...
Click to collapse
I'm not trying to be hostile but all of the information is available here in the forums. The developers, senior members and moderators like myself have spent HUNDREDS OF HOURS making sure it can be referenced one way or another. They are in stickies and even in MY SIGNATURE. The only other thing we can do for you is do it ourselves! Yet even with a clean and clear explaination this still comes up. We even get some people that post threads saying that they bricked their phones because they thought for sure it was a 32A and they try to hold me responsible. I will be happy to forward some hateful e-mails to you that I get at least 2 or 3 times a week average because people couldn't find the information... yet... if they followed rule #1 of the forums... they wouldn't have the problem.
Look... at least you got the right information and avoided bricking your phone. But I really hate repeating myself over and over again with the same information so I need to be tougher to get my point across otherwise other members will likely use the wrong information and end up breaking their phones... which I will not be held liable for!
DonJuan692006 said:
He wasn't fussing at you, he was getting at the other guy for feeding you false information.
Sent from my HTC Magic using Tapatalk
Click to expand...
Click to collapse
Right on Don. I'm not angry at you OffDutyNinja808 however the other guy (CBATESY) should be warned that I could give him an infraction for giving out bad information.
Binary100100 said:
Right on Don. I'm not angry at you OffDutyNinja808 however the other guy (CBATESY) should be warned that I could give him an infraction for giving out bad information.
Click to expand...
Click to collapse
On another note, Don, I made a new sticky thread just for this issue.
Feel free to add your wisdom to it.
http://forum.xda-developers.com/showthread.php?t=893004
Okay... so I followed Don's instructions and the phone now says:
SAPPHIRE PVT 32A SHIP S-ON G
HBOOT-1.33.0013 (SAPP31000)
CPLD-13
RADIO-2.22.23. 02
I tried flashing the same CM and it gets past the mytouch splash but doesn't go past the next loading X screen.
From what you guys said everything is looking right. Any thing look out of ordinary or sound crazy from what i'm saying?
Thanks again!
Sent from my GT-I9000 using XDA App
offdutyninja808 said:
Okay... so I followed Don's instructions and the phone now says:
SAPPHIRE PVT 32A SHIP S-ON G
HBOOT-1.33.0013 (SAPP31000)
CPLD-13
RADIO-2.22.23. 02
I tried flashing the same CM and it gets past the mytouch splash but doesn't go past the next loading X screen.
From what you guys said everything is looking right. Any thing look out of ordinary or sound crazy from what i'm saying?
Thanks again!
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Loading X screen?
What rom are you trying to install?
What kernel?
And now i'm in like tube socks! I just woke up and tried it again and it booted right up.
Binary, it was the same CM 5.0.8-DS. As far as the kernel goes, I didn't flash any separate. The X boot screen I mentioned is the Nexus One load screen (I believe).
The only thing that I did differently this morning was wipe/factory reset, then davlik.
Okay... so from my understanding now:
I have to have a perfected SPL, not an engineering SPL.
I have to use the custom (AMAN RA) recovery and never use ClockworkMod.
Ensure that any other roms I want are 32b.
Now as far as the radio goes, is it best to stay with the radio it came with?
Again, thanks for the advice!
Sent from my GT-I9000 using XDA App
DonJuan692006 said:
The problem. You forgot to mention that you also flashed a non-perfected SPL at some point before flashing CM 5.0.8. You need to get that fixed. Luckily you can fix it without a goldcard since you've already got S-OFF.
Download these:
hboot.nb0 for myTouch 1.2 only
Amon Ra 1.7.0-G Recovery
Go to this URL and follow the steps to get ADB setup if you don't already have it. Then go here and follow steps 7, 8, and 9. In step 7, you should only need to run:
fastboot flash hboot hboot.nb0 (the 0 at the end of this line is a zero not an oh).
fastboot flash recovery recovery.img
fastboot reboot-bootloader
After that just reflash CM 5.0.8, although I'm using CM 6.1 and it's just as good, but with the perks of Android 2.2. I would suggest reading through that thread I linked to get more familiarity.
Lastly, I will warn you that this isn't the easiest way to get your phone fixed, but this is the way that I learned about my phone, so it should help you out in that aspect. I'm sure mumilover or someone else may come along with a simpler solution.
If you have any problems, let us know here.
Click to expand...
Click to collapse
Don, two things...
1. I searched through the ROM bible and didn't find any place to download 6.1.
2. When I try to download the Google Apps from the page you sent me the link to yesterday, it asks for a user name and password. I have 5.0.8 up and running, but with no market and things like that.
Thanks!
Okay... I am now running FroyoRedux-1.9.5 with the Galaxy theme. Everything is smooth as butter.
I fixed the links in the post I pointed you to and updated them to what you news for CM 6.1
Sent from my HTC Magic using Tapatalk
offdutyninja808 said:
And now i'm in like tube socks! I just woke up and tried it again and it booted right up.
Binary, it was the same CM 5.0.8-DS. As far as the kernel goes, I didn't flash any separate. The X boot screen I mentioned is the Nexus One load screen (I believe).
The only thing that I did differently this morning was wipe/factory reset, then davlik.
Okay... so from my understanding now:
I have to use the custom (AMAN RA) recovery and never use ClockworkMod.
Now as far as the radio goes, is it best to stay with the radio it came with?
Again, thanks for the advice!
Click to expand...
Click to collapse
You can use clockwork. I use it without any problems. Some people like AmonRa better though. If you run CM6 there have been issues about people not being able to flash the recovery for some reason. Just keep trying and it will stick eventually. Just make sure that you flash the one for MyTouch/Ion devices.
Radio - keep the one that your using.
Roms - 32B ONLY
Should have just left my phone alone, it was working fine the way it was. Anyway, I flashed a bad SPL/RADIO combo and things just don't work anymore. I can get on Fastboot, but when I try to use it it says "remote not allowed," horrible. So, I can't boot into recovery or regular. I'm stuck with fastboot.
I've read multiple old threads about this, but I don't know if there is any new method to fixing it? Besides getting a new phone?
Hi, I try to help if i can, it will be good if you let members know your phone details like eg. 32A or 32B o fender 1.2, current radio and spl. What you did to flash the radio and spl. Do you have androidsdk on your computer coz you can push thru adb while your phone is in fastboot mode. Can also try searching using the keyword "unbrick" thru the general thread. Hope this helps.
Your not bricked. Need all your information from fastboot.
Sent from my HTC Glacier using Tapatalk
SAPPHIRE PVT 32A SHIP S-ON G
HBOOT-1.33.0013
CPLD-13
RADIO-6.35.16.19
I have the sdk and other various tools. I flashed the wrong combo and tried to repair with sappimg.zip. It restored me to the current settings above.
Before I was:
SAPPHIRE PVT 32A ENG S-OFF H
HBOOT-1.76.2007
CPLD-13
RADIO-6.35.16.19
;
sounds like your have a Magic 32a. You flashed a perfected SPL of 1.33.0013 which is only for 32b/mytouch 1.2 32a hybrids. This SPL does not have ability for fastboot. You will need to either flash your new SPL via recovery or via Goldcard.
I'm going to try the goldcard method.
Update: How would I get the CID for my phone through Fastboot?
Use a friends phone?
Sent from my Gingerbread on Sapphire using XDA Premium App
Not a bad idea, does he need to have the same phone?
You can't get the SD card CID from fastboot. Man did you screw up. First and foremost you have a myTouch 1.2 which there is a stickied thread on the first page about. Secondly, you screwed yourself trying to use the sappimg. You had an engineering SPL before so you could have just flashed the correct SPL/radio combo from fastboot and would have been good to go. Now you'll have to make a goldcard and flash a new sappimg that will flash back a 32A SPL thatbis compatible with that radio, and then flash the correct ones. I've only seen that done once by mumilover but he hasn't been around for a while and I don't know when he'll be back. Still go ahead and make the goldcard. You'll need to borrow a working Android phone from someone to do that part.
Sent from my HTC Glacier using Tapatalk
Sorry been gone for a while... got a newborn child :0)
You know.. family first, android second!
For the OP. Run this command:
Code:
fastboot getvar version-main
Congratz man. When I ran that command I got:
version-main: 2.10.531.4
Your lucky day...
Follow this post: http://forum.xda-developers.com/showpost.php?p=11946470&postcount=30
From this thread: http://forum.xda-developers.com/showthread.php?t=968829
But on the last step you need a different rom... wait i'll upload it
Here you go:
http://rapidshare.com/files/454052569/2.10.531.4.zip
Use ths above instead of the nbh file i had... it's the stock file for your device.
NB: as i wrote.. if you succeed in getting the eng spl (1.33.2010) then you have no need for this file... then just post the fastboot info here and wait for instructions... i'm sure that DonJuan692006 will take good care of you
mumilover said:
Here you go:
http://rapidshare.com/files/454052569/2.10.531.4.zip
Use ths above instead of the nbh file i had... it's the stock file for your device.
NB: as i wrote.. if you succeed in getting the eng spl (1.33.2010) then you have no need for this file... then just post the fastboot info here and wait for instructions... i'm sure that DonJuan692006 will take good care of you
Click to expand...
Click to collapse
Forgot to tell you need to rename it to sappimg.zip
And I need the GC?
Mr. An0nym0u5 said:
And I need the GC?
Click to expand...
Click to collapse
What? 10 char
Mr. An0nym0u5 said:
And I need the GC?
Click to expand...
Click to collapse
Yes you need a gold card
I need the Goldcard for the post that mumilover came up with?
Yeah, pardon me. Closing on a house in two days so my head isn't all there.
Thank you all. :]
Sorry for creating new thread if there is some solution available on this. But I have searched everywhere and tried lot of things nothing works
Here is my hboot info
SAPPHIRE PVT 32B SHIP S-ON G
HBOOT-1.33.0007 (SAPP30000)
CPLD-10
RADIO-2.22.23.02
JUL 31 2009, 15:49:25
I had CyanogenMod 6 which became slow so I tried to reboot in recovery while USB was connected it didnt get into recovery mode and after reboot its stuck on CyanogenMod boot logo. When I try home + power it boots without going into recover mode and gets stuck in boot loop of CyanogenMod screen. I kept it on till the battery drained (almost 8 hrs 2-3 times) so dont think its issue with keeping it on for longer time.
So far I have tried all possible spamming.zip and spamming.nbh none of them work either get wrong model ID or update failed. I am not able to log in through ADB. adb devices doesnt show me any devices. But when i try fastboot devices i see my phone. But i can not push anything it says remote not allowed.
I tried goldcard but I cant get to the system files so cant swap the hex digits to create goldcard. I know someone would have a better idea.
Need some help from the experts .. please. Its been more than 2 weeks trying out all possible solutions but no luck.
Can you still boot into the rom you had installed?
Sent from my shad0w's sapphire using XDA Premium App
tvall said:
Can you still boot into the rom you had installed?
Sent from my shad0w's sapphire using XDA Premium App
Click to expand...
Click to collapse
If you mean boot and start the phone no I am not able to do that it gets stuck on cyanogen boot screen. I am able to boot in HBOOT and FASTBOOT though.
Have u tried fastboot flashing a new recovery? Just to see if u lost it somehow then try to boot into it.
Sent from my HTC Magic using XDA App
johnson8cyl said:
Have u tried fastboot flashing a new recovery? Just to see if u lost it somehow then try to boot into it.
Sent from my HTC Magic using XDA App
Click to expand...
Click to collapse
He has s-on. If he could do that then this would be easy to fix
Sent from my shad0w's sapphire using XDA Premium App
Oh yeah. You're correct....... duh. Can he use someone else's gold card?
Sent from my HTC Magic using XDA App
happened to my mytouch 3g
it happened to me last week like that, the only thing that saves my was run the 1.5 SAPPIMG.nbh so i'm back to stock again then re-do everything allover
danxtian said:
it happened to me last week like that, the only thing that saves my was run the 1.5 SAPPIMG.nbh so i'm back to stock again then re-do everything allover
Click to expand...
Click to collapse
Can you point me to the file? I have used lots of sappimg.nbh so far none worked so dont mind trying this one. Hope thats the solution for me.
johnson8cyl said:
Have u tried fastboot flashing a new recovery? Just to see if u lost it somehow then try to boot into it.
Sent from my HTC Magic using XDA App
Click to expand...
Click to collapse
No it says remote not allowed.
Rambad said:
Can you point me to the file? I have used lots of sappimg.nbh so far none worked so dont mind trying this one. Hope thats the solution for me.
Click to expand...
Click to collapse
for the old mytouch 3g
http://www.megaupload.com/?d=DQWW0Y9N
for mytouch 1.2
http://www.4shared.com/file/E2zhvzIr/SAPPIMG_Sapphire_T-Mobile_US_2.html
i got them from theunlockr website, hope they works for you..
danxtian said:
for the old mytouch 3g
http://www.megaupload.com/?d=DQWW0Y9N
for mytouch 1.2
http://www.4shared.com/file/E2zhvzIr/SAPPIMG_Sapphire_T-Mobile_US_2.html
i got them from theunlockr website, hope they works for you..
Click to expand...
Click to collapse
Tried again I get Main version older for original and model ID incorrect with mytouch 1.2
ooow sorry to hear that, well i guess you will need to get a goldcard..
danxtian said:
ooow sorry to hear that, well i guess you will need to get a goldcard..
Click to expand...
Click to collapse
I am unable to do that because I cant see my device in adb. Is there some way I can send my phone to t-mobile or htc and they can reset to factory setting? I am surprised that there is not a way to just flash rom with factory settings.
do you know anybody that have a HTC phone? i'm pretty sure some of your friends have one coz HTC phone are almost everywhere nowadays
Simple.... run these commands to establish your current status.
Based on your answers, i can properly asses your situation.
Code:
fastboot getvar version-main
fastboot getvar cid
Maybe we can fix this without the use of goldcard.
mumilover said:
Simple.... run these commands to establish your current status.
Based on your answers, i can properly asses your situation.
Code:
fastboot getvar version-main
fastboot getvar cid
Maybe we can fix this without the use of goldcard.
Click to expand...
Click to collapse
Thanks for your help, this is what I see. Fingers crossed
version-main: 1.92.531.1
cid: T-MOB010_Y∞²
Please recheck that version nr... you are sure its 1.92 or is it 1.94?
Download this:
https://rapidshare.com/files/433519738/1.94.531.1.nbh
rename it to sappimg.nbh
But it on the sdcard and flash it using hboot mode (hold volume - and power together. The "-" sign symbolize decrease of volume).
It should get you back to stock :0)
mumilover said:
Download this:
https://rapidshare.com/files/433519738/1.94.531.1.nbh
rename it to sappimg.nbh
But it on the sdcard and flash it using hboot mode (hold volume - and power together. The "-" sign symbolize decrease of volume).
It should get you back to stock :0)
Click to expand...
Click to collapse
You are the man (or Women) it worked smooth I am now back on 2.2 with official t-mobile update. I hope this helps others who are still looking for a solution.