Related
Hey guys, I have spent the last 8 hours trying to figure this out.
I have a MyTouch 3g 1.2 and I want to root it and install Cyanogen's new ROM. I have been following the rooting guide from TheUnlckr.com.
I am able to complete everything fine (I needed to substitute the sappimg for the Sapphire one to make it work), but it finally completed.
When I go to fastboot with SDK, I can see my device, so everything looks fine. However, when I go to flash the radio, hboot, and recovery images, I get a error that says:
Code:
C:\AndroidSDK\tools>fastboot flash radio radio.img
sending 'radio' <21504 KB>...FAILED <remote: not allow>
finished. total time: 0.016s
This is the pattern for each of the files I try to flash...
This is where I'm at, and I haven't even gotten to flashing the ROM yet. So, I currently just have a stock device. Can someone please help me out?
I tried using the following sappimg:
2.53.707.2_-_sappimg
SAPPIMG_Sapphire_T-Mobile_US_2.10.531.4_release_signed
the following SPL:
update.Engineering-SPL-HBOOT-1.33.2010-signed
the following recovery images:
recovery-RA-sapphire-v1.6.2G.img
flashrec-1.1.2-20090909.apk
flashrec-1.1.3-20091107-2
flashrec-20090815
I'm clearly all over the place now. Someone please point me in the right direction. I tried several different ways to fix it, but none of them worked. The most reason I tried was the method of using the flashrec to flash a recovery image while the phone is on, instead of fastbooting it. That didn't work because it kept saying it was the wrong image for the phone.
Thanks in advance guys. And believe me, I've been searching and searching.
Dane
before you can flash anything with fastboot, you have to shoehorn that engineering SPL into the phone somehow (probably have to make a goldcard, but I don't know for sure on the 1.2 mytouch)
which rooting guide are you using? (there are many different ones on unlockr, some of which are terribly obsolete)
also, flashrec isn't a recovery image, its a one-click rooting app that only works on android 1.5 (pretty sure the 1.2 mytouch only runs 1.6)
adavis159 said:
before you can flash anything with fastboot, you have to shoehorn that engineering SPL into the phone somehow (probably have to make a goldcard, but I don't know for sure on the 1.2 mytouch)
which rooting guide are you using? (there are many different ones on unlockr, some of which are terribly obsolete)
also, flashrec isn't a recovery image, its a one-click rooting app that only works on android 1.5 (pretty sure the 1.2 mytouch only runs 1.6)
Click to expand...
Click to collapse
This was the guide I was using. (I can't link to outside sites, so I'll just copy it as text) http://theunlockr.com/2010/03/11/how-to-root-the-mytouch-1-2-and-fender-mytouch/
I also successfully created a goldcard, and installed all the ADB stuff. The part that's hanging me up is the flashing of the recovery image via fastboot usb.
I'm so close! I have successfully rooted two other mytouch devices, but they were not the 1.2 version.
Any more help would be great!
Dane
danegerous said:
I am able to complete everything fine (I needed to substitute the sappimg for the Sapphire one to make it work), but it finally completed.
Click to expand...
Click to collapse
what "sapphire" image did you substitute? and what happened when you tried to use the sappimg that they gave you in the instructions?
When I tried using that image, it just said "wrong file for this phone" or something like that. I know the goldcard was done right, though, because it works with another sappimg. I'm trying to follow cryptsmoker's guide now. I'm going to try and use the engineering img/SPL now. We'll see how it goes.
Ok, now I'm getting frustrated.
Here is my info:
Sapphire PVT 32A Ship S-on G
Hboot-1.33.0013 (Sapp31000)
CPLD-13
RADIO-2.22.23.02
Oct 21 2009
I just got the Model ID incorrect!
Update Fail!
This happens with every sappimg I use except T-Mobile 2.10.531.4. I'm sure that's the stock one, so that's probably why. I'm just so ticked.
To clarify again, After I hboot the sappimg, I reboot and instead of being taken to the Magic screen, I'm taken to a standard MyTouch splash, then Android splash, then MyTouch setup screen. My touchscreen works the entire time. Is this because I basically just reinstalled the stock ROM?
I just can't seem to get ANY other sappimg to work beside the stock one. I've used three different goldcards and all of them work the exact same way.
Please help!
Dane
yeah, you are just reinstalling the stock files (stock SPL and radio)
just because the t-mobile sappimg works doesn't mean you made the goldcard right.
the point of the goldcard is to trick the phone into installing a non-stock sappimg, you could take a brand new SD card, put the stock sappimg on it and you would still be able to flash it using vol-down+power
open the goldcard.img in HxD and make sure it contains all the lines (including all of line 170), if it doesn't then you need to start over from the beginning (get cid again, reverse it again, get a new goldcard.img)
If goldcard.img is ok, open the sd card in HxD again and make sure all of the first 170 lines of the sd card match the goldcard.img
also, some SD cards just don't work for making goldcards. I used a lexar 1gb, and kingston 2gb cards are reported to work
I didn't paste over the entire 170 line while making the goldcard. I used the "select" feature and chose 0-170...that could be my mistake. Here we go again!
I actually never got this to work the first time. I was really excited since I heard I would be getting the T-Mobile update soon, but then I read a little further and saw that the 2.1 is not yet included...so, I will be figuring this out today, mark my words!
Wish me luck!
Dane
I had a similar problem and it was the goldcard. Although I had made the goldcard and it worked before, using the same goldcard I get the same error message as you. I made a new goldcard and it worked flawlessly to flash using fastboot. Make sure you are using one of the brands that are know to work.
OK, new problem now. I installed everything and got it all to work. I actually had the stock cm rom working (an out of date version from the unlockr). Well, I tried to update and I started by flashing the 6.35.16.19 radio. Apparently that worked but now nothing else will.
In the HBOOT screen, I see this:
SAPPHIRE PVT 32A SHIP S-ON G
HBOOT-1.33.0013 (SAPP31000)
CPLD-13
RADIO-6.35.16.19
Oct 21 2009,
Every time I try and update the Sappimg file, I get stuck at the updating phase of the radio_v2 portion. Please help guys, I don't know enough about this to figure it out and it's really killing me!
I figure I need to get back to the stock radio I started with (3.22 or whatever), but I can't. Even when I try to flash the radio in fastboot, it takes way too long and never finishes.
Your speedy replies are greatly appreciated.
Thanks
Dane
Got your pm.
Facts: STOP MESSING UP YOUR DEVICE.....
You are working in the blind... mixing bad spl and radio combos.....
So STOP what you doing and read and understand before you continue.
You can't just take any sappimg.zip and apply it... I has complete partitions layout... like the spl, radio, recovery ect...
So if you take whatever you find on the net and apply it, you will **** your device up... just like you did now...
Having the 6.35 radio and a perfected 1.33 spl... Just bad for business!
What is your current status:
Access to adb?
Access to fastboot?
Access to recovery?
Access to rom/system?
Also post fastboot info...
Then we can take it from there :0)
And for gods sake... STOP flashing stuff.
I have access to adb, fastboot, and hboot. No ROM/system or recovery.
Clarification: Since I cannot access the system of the phone, I do NOT have access to ADB. I cannot see the device when I type in 'adb devices' within the AndroidSDK\tools path.
Fastboot info:
SAPPHIRE PVT 32A ENG S-OFF H
HBOOT-1.76.2007 (SAPP31000)
CPLD-13
RADIO-6.35.10.18
Aug 21 2009
The radio used is: Radio_HTC_PVT_32A_6.35.10.18.img
the hboot: hboot-1.76.2007.nb0
the recovery: recovery-RA-hero-v1.6.2.img
I have since tried to go into one of your other threads and at least match up my SPL/Radio combo. Any and all help is greatly appreciated.
OK.... you are now in a god situation...
You have a good combo and eng spl...
We can work with this....
1) boot into fastboot
2)download the fastboot commander (magic).... check my signature
3)start the tool... does it print the device info?
If yes, do this:
Go to the magic 32A tab.
Push "flash old".
IF all successful, then go to "misc" tab and push "reboot device".
When device has rebooted, push "print device info".
Now copy all text and posted here...
IF you get ANY errors... DO NOT REBOOT, DO NOT CLOSE THE TOOL...
Just take the output + the content of the "actual tab" and post here....
Again, IF you get ANY errors... DO NOT REBOOT, DO NOT CLOSE THE TOOL!
If the tool does not print the device info, then post here...
mumilover said:
ok... don't do **** until i post back here... give me like 15 min.
Click to expand...
Click to collapse
I'm seriously just sitting here waiting. Thanks a ton. I'll buy you a beer.
just updated my last post
look up :0)
Now i'm the one waiting :0)
Sorry, my battery died, I'm running around to trying to piece everything together. Here I go...
Just do what i wrote.... Read, understand, read, understand, execute.
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!
Hi,
I am not all that new to rooting / flashing i've had a lot of experience but i think i've made a school boy error.
I rooted a HTC Magic last night and added the 1.5 Hero Rom.
this morning i looked for a later ROM and i found one from the unlockr.
the issue with this was that it required a radio flash. My 32B Magic is now flashed to 32A and i cannot even get into recovery mode OR re-flash the radio.img i had originally through fastboot.
Upon boot the Magic just comes up with the Mytouch 3G spash screen and nothing else.
Details:
Rooted using gold card method, fine.
Hero rom installed: fine.
Updating the ROM however, the radio was flashed to 32A and now i cannot get back into recovery mode.
Is there anything i can do? has anyone seen this before? I really don't want to keep using the motorola dext, sorting this magic out will make me happy.
Please help.
thanks.
you cant go in fastboot mode???
[edit]No, I can get to fastboot, i can get the opening my touch splash up but nothing is working from there. i've tried the arab rom but i can't get my pc to recognize. there has to be a way to flash this back...
[edit] update - Attempted to flash stock 32B Radio to get rid of the 32A that i think's causing the issue - fastboot flash radio.img... Sends radio OK but hangs on Writing radio, I get a black screen on the device. didn't work.
I don't want to ruin the mood any more than it is now, but I did practically the same thing; flashed 32B radio onto 32A Magic, and it was unrepairable in my country. Sold it for parts a few weeks later and got another one.
No fastboot, no boot at all, nothing. All that I was able to get was the blue led mode (trackball + power), and the only repair method was JTAG, which wasn't available to me.
That sucks.
From what I can gather this very well might be dead but everything I can find tells me as long as i can get into fastboot there must be something i can do.
At the moment I can use fastboot and HBOOT but i'm unable to get to a recovery or flash a stock radio.
so far i've tried every recovery/radio i can get my hands on. Hope i'm missing something and somebody is able to help.
flashing 32B to 32A does make me feel a bit spastic to be honest. it's a mistake I can never repeat with anything!
http://forum.xda-developers.com/showthread.php?t=754565
Try posting your thread again in the correct section.
EDIT: Tis the season and junk. I was about to move this to the TRASH but I took pity on you. I moved your thread to the correct section but the next new post that you create in the Development section that isn't related to development will be trashed. Final warning.
Appreciated, My bad. It's been a long and overly tiring day.
Info if it helps:
Sapphire PVT 32A SHIP S-ON H
HBOOT-1.33.0009 (SAPP10000)
RADIO-6.35.16.19
Tried flashing official rom, nothing.
I got ID Failed, same when i try usinb sappimg in hboot.
radio now half installs but failes on ID.
Felt i'd add to this in case anyone has any ideas.
cheers.
Hi,
I recommend that you download this switcher (http://forum.xda-developers.com/showthread.php?t=794450&highlight=eyegor). Only to use the files (HBOOT, RADIO and REVOVERY), again ONLY because of the files.
After download reboot on fastboot mode and flash: HBOOT, RADIO and RECOVERY, using this sequence.
Good luck,
I'm not sure if this will deal with 32B Magic that's been flashed to 32A but i'll give it a shot. thanks.
Unfortunately there was no luck with that or the Arabic RRU, The GUI Switcher method to flash the radio failed, now phone won't even turn on.
If it wasn't a brick before, it sure as hell is now. i'll chalk this one up as a mistake i think and just be more careful in future.
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
So, I rooted my fiances Mytouch 3G original and it's been so long I don't remember what I did. Now theres a one click methods, different numbers 32a and 32b and there's radios and all this other stuff I didn't have to worry about then (I think)
I updated her to the Betamod AOSP using the same method as I would do with my Vibrant and well it works, but the text messaging dictionary is in German and the battery life was horrible so I wanna take her to Yoshi 1.0 RC5.1, so I'm doing all this research to make sure I do it right (part of me wants to brick it so she'll get a new phone, she hates spending money on phones when they work) and she's overdue for a full upgrade.
I'm reading these guides and all these other things and I keep linking and linking and linking and it's kind of overwhelming. I think I had 6 or 7 tabs open before I decided to just start a thread. I wasn't sure if the threads I was reading applied to me. It was very confusing.
Can someone please just point me to the right direction.
I'm assuming with the research and reading I've done is that she needs the 32b roms and her radio and kernal I will have to look at when she gets home. I may need help finding that info, but please let me try and report it first.
I'm sorry if this is an annoying noob post, but if you guys can give me exactly what I need I will read about it.
vahdyx said:
So, I rooted my fiances Mytouch 3G original and it's been so long I don't remember what I did. Now theres a one click methods, different numbers 32a and 32b and there's radios and all this other stuff I didn't have to worry about then (I think)
I updated her to the Betamod AOSP using the same method as I would do with my Vibrant and well it works, but the text messaging dictionary is in German and the battery life was horrible so I wanna take her to Yoshi 1.0 RC5.1, so I'm doing all this research to make sure I do it right (part of me wants to brick it so she'll get a new phone, she hates spending money on phones when they work) and she's overdue for a full upgrade.
I'm reading these guides and all these other things and I keep linking and linking and linking and it's kind of overwhelming. I think I had 6 or 7 tabs open before I decided to just start a thread. I wasn't sure if the threads I was reading applied to me. It was very confusing.
Can someone please just point me to the right direction.
I'm assuming with the research and reading I've done is that she needs the 32b roms and her radio and kernal I will have to look at when she gets home. I may need help finding that info, but please let me try and report it first.
I'm sorry if this is an annoying noob post, but if you guys can give me exactly what I need I will read about it.
Click to expand...
Click to collapse
If it is a 32b you will need to update spl and radio but a link to a guide to that is in the ginger yoshi op. Everthing you need should be in the ginger yoshi op in fact. You can use Amon_Ra for the ext4 part, the thread for installing that is in the same forum as yoshi's just a few threads up. Hope that helps.
Get us the fastboot info and we'll get you taken care of. Is the phone still rooted?
Sent from my LG-P500 using Tapatalk
Thanks guys, here's her HBOOT info
32b and S-on
Hboot 1.33.0006
CPLD - 10
Radio 2.22.23.02
I don't know if you need anything else, but yes the phone is still rooted
I'll defer to DonJuan's expertise here but, I think you sould be fine following Yoshi's OP. Ginger Yoshi requires the new radio/spl combo but the steps are all there. If I understand correctly the ext partition is optional but highly recommended and will be required in future releases.
Okay before I proceed, I downloaded
update.Engineering-SPL-HBOOT-1.33.2010-signed
recovery-RA-sapphire-v1.7.0G
Ohsaka-SuperWipe_v2
radio
hboot
These are zips except the Recovery file. I'm gonna put them all on my SD card and flash them in recovery. Then I'm gonna flash the rom.
Good?
Superwipe first
Recovery second
hboot third
engineering hboot fourth
Radio 5th
Then the ROM
Wait, actually where did you get the hboot/radio files from? Need to make sure they're the right one's, but I actually think you may be on the right track.
If I'm not mistaken you shouldn't need the engineering spl if you are going to flash the radio and spl via recovery, you only need it if you are going to use fastboot to install them.
So (Again if I'm not mistaken):
1. Recovery
2. Superwipe
3. Radio
4. Hboot
5. Rom
The guide I used to upgrade my radio/spl seemed simplest, worked great. Sorry I'm not allowed to post links here yet but it is at cyanogenmod.com search for a thread called New radio dream +15MB EXTRA RAM! for HTC DREAM
Look for post by -Stevo- on page 2, he does "Amazing" work.
turkeyshark said:
If I'm not mistaken you shouldn't need the engineering spl if you are going to flash the radio and spl via recovery, you only need it if you are going to use fastboot to install them.
So (Again if I'm not mistaken):
1. Recovery
2. Superwipe
3. Radio
4. Hboot
5. Rom
Click to expand...
Click to collapse
Right, pending he has the right radio/SPL.
DonJuan692006 said:
Wait, actually where did you get the hboot/radio files from? Need to make sure they're the right one's, but I actually think you may be on the right track.
Click to expand...
Click to collapse
I got it from step number 3 from http://forum.xda-developers.com/showthread.php?t=909900
vahdyx said:
I got it from step number 3 from http://forum.xda-developers.com/showthread.php?t=909900
Click to expand...
Click to collapse
Should be all set then.
Well did the steps and bricked the phone, it's on an endless loop, it won't flash the ROM for some reason. So I'm happy, we're picking up a new HD7 tomorrow. LOL, I got my wish.
I booted into recovery, did a nandroid, flashed super wipe, flashed radio, flashed Hboot, flashed rom and rom gave me an error. Have no other rom on SD card so I can't do anything else. Nandroid restore doesn't do what I need it to do and won't fix the problem.
Here's what my Hboot says now
Sapphire PVT 32B Ship S-ON G
HBOOT 1.33.0013d
CPLD 10
Radio 2.22.27.08
Oct 21 2009
***Edit***
I forgot to wipe cache before installing ROM, dammit everything is fine! She's asleep now, so maybe I shouldn't tell her the mytouch is working now.