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.
Hey guys,
I have the original myTouch 3g (no 3.5mm jack).
I decided to unroot and go back to T-Mobile's original Froyo version (i know stupid idea). I attempted to use SAPPIMG.nbh file to go back to factory. Unfortunately, it didn't work so I tried using SAPPIMG.zip. Now I have a Vodaphone splash screen instead of the T-Mobile one. no access to recovery, or anything. I can access fastboot. Where did I go wrong?? (aside from wanting to un-root myself)
Any help would be appreciated!
Fastboot Screen reads:
SAPPHIRE PVT 32B SHIP S-ON H
HBOOT-1.33.0009 (SAPP30000)
CPLD-10
RADIO-3.22.20.17
May 8, 2009 21:02:32
well if u can access fast boot you can probably flash recovery again
fastboot flash recovery "recovery file.img"
or try to boot recovery
fastboot boot "recovery file.img"
I attempted to do that but I get a signature failed error and booting recovery file just leaves me stuck at the red Vodafone splash image. Nothing else comes on.
try finding the proper sapping.nbh file for your area / carrier.
place it in the root of your memory stick by its self. turn on your phone while holding vol down and let it flash the file. you should end up back on stock 1.5 i think just root again after. i had a similar problem like this like last week and had to start over =/
Ndokami said:
try finding the proper sapping.nbh file for your area / carrier.
place it in the root of your memory stick by its self. turn on your phone while holding vol down and let it flash the file. you should end up back on stock 1.5 i think just root again after. i had a similar problem like this like last week and had to start over =/
Click to expand...
Click to collapse
I have tried multiple different sappimg.nbh files. But the problem is that now it somehow has Vodafone files on it. So i'm not sure how to get it back to T-mobile.
Every time I try the SAPPIMG.nbh it gives me the following error: Main version is older.
If I try to use a SAPPIMG.zip I get the following error: Model ID incorrect. Everything sort of fails when it checks for the signature.
Also, when I try to upload amon ra recovery to recovery partition with fastboot I get remote: signature verify fail.
Wrong section!!!!
@crazy
You're new here... so let me warn you here and now. The Development section is for the members that want to post their work such as roms, scripts, hacks, etc. When I'm in a bad mood and I see posts in the development section that are not development related I normally just delete them. However, I'm in a good mood and decided to move it to GENERAL where it belongs. HOWEVER... next time it will dissappear. Please take a few minutes and carefully read over the forum rules and stickies before posting. We also have a search feature that works quite well (most of the time).
If I see that you posted a new thread about something that is found in a sticky, already been answered and can be found by using the search feature or against forum rules you're post will be deleted and you may even be subject to losing your membership.
Besides all of that... enjoy and welcome!
Thanks for your help @Binary.
I searched all through the forums and tried to flash a recovery through fastboot. NO go.
Next I tried the gold card method and with that I continue to get either Model ID incorrect or Main version is older. So here I am seeking guidance from everyone else who may know what I can try next.
Thanks in advance for all your help guys.
It seems like your Mytouch 3g haven't flashed recovery.img just choose a suitable image to flash. XD
Pal_Hwang said:
It seems like your Mytouch 3g haven't flashed recovery.img just choose a suitable image to flash. XD
Click to expand...
Click to collapse
How do I force flash the recovery image? Any time I try flashing any recovery image via fastboot the signature check fails. Is there an official recovery image that would work?
Any help guys? Still not running.
can you boot into system or not?
if yes,root your device and flash recovery.That's what I did yesterday.
if not,use SAPPIMG.nbh again,and then flash rec,radio/spl through fastboot.
i don't know if it helps,just try it.
edward0119 said:
can you boot into system or not?
if yes,root your device and flash recovery.That's what I did yesterday.
if not,use SAPPIMG.nbh again,and then flash rec,radio/spl through fastboot.
i don't know if it helps,just try it.
Click to expand...
Click to collapse
Thanks for your reply. I just attempted to boot into system and I can't. This is the error I get:
Code:
cannot load 'system'
I have tried multiple different versions of SAPPIMG.nbh and here is the error I get:
Code:
Main Version is older!
Update Fail!
crazydeo said:
Thanks for your reply. I just attempted to boot into system and I can't. This is the error I get:
Code:
cannot load 'system'
I have tried multiple different versions of SAPPIMG.nbh and here is the error I get:
Code:
Main Version is older!
Update Fail!
Click to expand...
Click to collapse
download this one and try it
http://www.mediafire.com/?jlm5hzzhmhk
i fixed mine with it.
edward0119 said:
download this one and try it
http://www.mediafire.com/?jlm5hzzhmhk
i fixed mine with it.
Click to expand...
Click to collapse
Woah woah woah dude. You can't just have someone flash a sappimg just because it worked for your device. He needs a specific one. That one may work, but there's the same percentage chance that it could also brick his phone.
Sent from my HTC Glacier using Tapatalk
crazydeo said:
Thanks for your reply. I just attempted to boot into system and I can't. This is the error I get:
Code:
cannot load 'system'
I have tried multiple different versions of SAPPIMG.nbh and here is the error I get:
Code:
Main Version is older!
Update Fail!
Click to expand...
Click to collapse
I tried your version and I still get the following error:
Code:
Main Version is older!
Update Fail!
DonJuan692006 said:
Woah woah woah dude. You can't just have someone flash a sappimg just because it worked for your device. He needs a specific one. That one may work, but there's the same percentage chance that it could also brick his phone.
Sent from my HTC Glacier using Tapatalk
Click to expand...
Click to collapse
Thanks Don Juan for the heads up and looking out, but i'm getting desperate at this point. I have read through almost all the threads on the forum regarding my issue. The only thing I haven't tried is the GoldCard method at this point. Unfortunately and quite bad on my part, I never made one. Now, attempting to make one without Android is almost impossible. I can't read the SD card CID on anything. I've tried a mac, windows XP, windows 7, I even tried Linux but nothing.
Any insights and words of wisdom are greatly appreciated.
crazydeo said:
Thanks Don Juan for the heads up and looking out, but i'm getting desperate at this point. I have read through almost all the threads on the forum regarding my issue. The only thing I haven't tried is the GoldCard method at this point. Unfortunately and quite bad on my part, I never made one. Now, attempting to make one without Android is almost impossible. I can't read the SD card CID on anything. I've tried a mac, windows XP, windows 7, I even tried Linux but nothing.
Any insights and words of wisdom are greatly appreciated.
Click to expand...
Click to collapse
Can you give me till tomorrow when I'll be able to sit down at a computer and give some proper guidance? One thing is for sure, if we have to make a goldcard you'll have to see if you can borrow an Android phone from a friend. What you can do in the meantime is get ANDROIDSDK installed, turn the phone on in fastboot mode plugged into the computer and run the folksingers commands from the ANDROIDSDK Tools folder
Code:
fastboot getvar version-main
Sent from my HTC Glacier using Tapatalk
DonJuan692006 said:
Woah woah woah dude. You can't just have someone flash a sappimg just because it worked for your device. He needs a specific one. That one may work, but there's the same percentage chance that it could also brick his phone.
Sent from my HTC Glacier using Tapatalk
Click to expand...
Click to collapse
I know that dude,it's just my suggestion.
crazydeo said:
I tried your version and I still get the following error:
Code:
Main Version is older!
Update Fail!
Click to expand...
Click to collapse
sorry then,I can't help anything.
DonJuan692006 said:
Can you give me till tomorrow when I'll be able to sit down at a computer and give some proper guidance? One thing is for sure, if we have to make a goldcard you'll have to see if you can borrow an Android phone from a friend. What you can do in the meantime is get ANDROIDSDK installed, turn the phone on in fastboot mode plugged into the computer and run the folksingers commands from the ANDROIDSDK Tools folder
Code:
fastboot getvar version-main
Sent from my HTC Glacier using Tapatalk
Click to expand...
Click to collapse
Thank you for helping me out Don Juan. I cannot thank you enough!
In the meantime I will ask around and see who has an Android I could borrow.
Here is the info you requested:
Code:
version-main: 2.16.151.1
So I have a MyTouch 3g w/ the 3.5mm... I'm no noob but obviously I'm farrr from expert because I've effectively softbricked my phone.
Can't get past splash screen (stuck in a boot loop @ the HTC logo). I can bring up hboot and I have fastboot access.. but that's about it. No ADB drivers, no goldcard, no recovery, nada.
When trying to push anything useful (like a recovery image) through fastboot, I get "failed: remote not allowed."
As for how I got into this mess, it started when I mixed up two SD's and ran an update.zip meant for a different phone. Ouchies Instead of immediately coming for help, I thought I could fix it by just unrooting back to cupcake. Ugh.. I seriously don't know what I was thinking.
Is there any hope left for me?
Info.....
SAPPHIRE PVT 32A SHIP S-ON G
HBOOT-1.33.0013 (SAPP31000)
CPLD-13
RADIO-2.22.23.03
Thanks so much in advance for any advice. Love this forum btw, long-time lurker & first time poster here
Update: I have recovery. I've tried factory reset, wiping cache, loading several different update.zip files.
When trying to load a recovery image through update.zip I get a verification error. Still can't load a rom.
I can get past the HTC logo now, but only the menu bar loads.. the rest of the UI doesn't, and I get a repeating "The process andriod.process.acore has stopped unexpectedly" error, along with a few other errors.... then it will shut down and go to HTC logo again, and bootloop. I have to factory reset to get past the bootloop again.
How can I load a custom recovery through recovery? I'm guessing that's my only solution right now.
Just flash 2.10.531.4 T-Mobile USA DRD35 RUU. It is official ROM (sure, your data will be deleted)
UPDATE 2: Okay, I think I know what my problem is, but I'm stuck once again.
This phone was originally rooted and running cyanogen. i mixed up two sd cards accidentally flashed a motorola rom when i was trying to reset, which was the big dumb mistake that led to me trying to fix it by unrooting, which may have been an even dumber decision lol... i know i know
i think ive got a radio/spl mismatch going on? and i still cant fix anything with no adb or debugging. and fastboot's not flashing anything... i'm about to take downtown and have someone look at it, but i really don't want to spend the $.. but the work im missing over this is $$ too haha. >_<
5[Strogino] said:
Just flash 2.10.531.4 T-Mobile USA DRD35 RUU. It is official ROM (sure, your data will be deleted)
Click to expand...
Click to collapse
Thanks.. I just tried that last night, fastboot won't pick it up, recovery is giving me errors. the exe won't do it either (but i'm not sure if that's related to the lack of adb drivers?) seems to be a permissions problem.. do i need s-off?
shortcat87 said:
i think ive got a radio/spl mismatch going on?
Click to expand...
Click to collapse
If you still have same hboot / radio as in your first post - you DON'T have mismatch
shortcat87 said:
I just tried that last night, fastboot won't pick it up
Click to expand...
Click to collapse
What error did you get?
You can run ruu but navigate into temporary directory and search for rom.nbh, copy to folder with fastboot.exe and close RUU
Then go into fastboot-mode and run
Code:
fastboot flash nbh rom.nbh
shortcat87 said:
do i need s-off?
Click to expand...
Click to collapse
NO
5[Strogino] said:
If you still have same hboot / radio as in your first post - you DON'T have mismatch
Click to expand...
Click to collapse
Thanks, that's good to know
What error did you get?
Click to expand...
Click to collapse
When flashing in hboot (goldcard and otherwise) - No error, just goes through initial loading of SAPPIMG.zip and then goes back to hboot screen like nothing happened
...in recovery - Displays E: can't open cache/recovery/command, allows to apply update.zip but then gives a failed verification error
...in fastboot - Remote: not allowed error, aborts installation
You can run ruu but navigate into temporary directory and search for rom.nbh, copy to folder with fastboot.exe and close RUU
Then go into fastboot-mode and run
Code:
fastboot flash nbh rom.nbh
Click to expand...
Click to collapse
Thanks, will try, though i haven't had success in fastboot yet
Found this post and will try that first & let you know how it goes. If nothing works, I'm looking to sell a MT3G 1.2 for someone to play with, because I can't afford to spend any more time messing with it myself