Related
Applied the latest Rogers ROM...what a bad move...
Now my HTC Magic got stuck in RUU screen showing the following:
SAPPHIRE UNKNOWN 32A SHIP S-OFF H
HBOOT-1.76.0010 (SAPP50000)
CPLD-11
RADIO-6.35.10.18
Jan 14 2010, 00:14:58
RUU
I tried many ways to get rid of this screen but didn't work.
My phone original has the rogers 2.17.631.2 build, and I did a bad move to upgrade to Android 1.5.=( The RUU process flashed my HBOOT and RADIO, but as soon as it starts the "system" steps, the screen shows unzipping for over an hour and eventually failed. Now my phone will start up with the above screen only!! i can't get myphone startup in recovery mode or fastboot mode.
I tried re-run the RUU porgram on my PC and the tool still shows i have the old anroid build. Hence i know that i now have NEW HBOOT and RADIO but still the old Android build.
Is there a way for me to get out of this RUU screen? Any help is appreciated.
Is the security off (S-OFF) allows me to downgrade the SPL? If so, how can i do that given i can only boot my HTC Magic in this screen only.
One more side note, fastboot can detect the phone.
Urgently need help! Appreciated.
If you have constant security S-OFF, it accepts all ROMs and HBoot and RUU. Probably you have engineering Magic (not Hboot, the whole device)
1. Try this...
If fastboot can detect phone, so try flash Amon_RA Hero recovery http://forum.xda-developers.com/showthread.php?t=561124
fastboot flash recovery recovery.img
(recovery.img or other filename must be in folder with fastboot.exe)
Then start into recovery (Home + Power) and flash CursorSense
If you need original ROM (without root), so search forum for it
(it has been posted already). Just get rom1.zip (system.img, userdata.img and more...) and flash it (Saying again: official doesn't contain root)
2. Or try run another RUU
5[Strogino] said:
Oh... you have S_OFF after official upgrade, it isn't often to meet.
If fastboot can detect phone, so try flash Amon_RA Hero recovery
fastboot flash recovery recovery.img
(recovery.img or other filename must be in folder with fastboot.exe)
Then start into recovery (Home + Power) and flash CursorSense
If you need original ROM (without root), so search forum for it
(it has been posted already). Just get rom1.zip (system.img, userdata.img and more...) and flash it (Saying again: official doesn't contain root)
Click to expand...
Click to collapse
but the fastboot method requires engineering SPL, but my phone was upgraded to the perfected SPL. Shall I try the RA_Hero or RA_Sapphire ?
ngecw said:
but the fastboot method requires engineering SPL, but my phone was upgraded to the perfected SPL. Shall I try the RA_Hero or RA_Sapphire ?
Click to expand...
Click to collapse
Yes, common fastboot required to be engineering. But you have S-OFF now, so no checks.
use RA_Hero, cause you have radio 6.35.X.X
5[Strogino] said:
Yes, common fastboot required to be engineering. But you have S-OFF now, so no checks.
use RA_Hero, cause you have radio 6.35.X.X
Click to expand...
Click to collapse
Tried flashing the recovery.img (RA_Hero) but failed.
i typed fastboot flash recovery recovery.img [ renamed the file to recovery.img] but got the error...
sending 'recovery' <3362 KB>... OKAY
writing 'recovery'... FAILED <remote: image type not support>
Just to clarify more, the screen only shows "RUU USB" not "FASTBOOT" although fastboot can see my device... could that be the reason why it failed?
According to your 2nd suggestion, where can i find other RUU and how do i know which is the proper one?
ngecw said:
Applied the latest Rogers ROM...what a bad move...
Now my HTC Magic got stuch in RUU screen showing the following:
SAPPHIRE UNKNOWN 32A SHIP S-OFF H
HBOOT-1.76.0010 (SAPP50000)
CPLD-11
RADIO-6.35.10.18
Jan 14 2010, 00:14:58
RUU
I tried many ways to get rid of this screen but didn't work.
My phone original has the rogers 2.17.631.2 build, and I did a bad move to upgrade to Android 1.5.=( The RUU process flashed my HBOOT and RADIO, but as soon as it starts the "system" steps, the screen shows unzipping for over an hour and eventually failed. Now my phone will start up with the above screen only!! i can't get myphone startup in recovery mode or fastboot mode.
I tried re-run the RUU porgram on my PC and the tool still shows i have the old anroid build. Hence i know that i now have NEW HBOOT and RADIO but still the old Android build.
Is there a way for me to get out of this RUU screen? Any help is appreciated.
Is the security off (S-OFF) allows me to downgrade the SPL? If so, how can i do that given i can only boot my HTC Magic in this screen only.
One more side note, fastboot can detect the phone.
Urgently need help! Appreciated.
Click to expand...
Click to collapse
the rogers ROM is not working right. Too many crashes and so on .. so try this one
RUU_Sapphire_HTC_Europe_3.05.401.3_release_signed_NoDriver.exe
You can download it from HTC main site ...
Also, you have to keep in mind that you can RUU as many as you want. So do the procedure again and keep us posted if it's working. If not send me a PM and i'll resolve it step by step.
best of luck !
I have one Magic and it show in Bootloader :
PVT 32 S-OFF
1.76.0007 (SAPP*****).
Why the SAPP is SAPP*****? Is there something wrong?
Also, the device detected by fastboot is 1234567890... , not like other HTC Magic.
Now I get stuck with RUU Flash at 81% (Hong Kong RUU). --> When the device start to update system STEP. So the Magic now just show RUU, can connect by Fastboot but when use fastboot flash system or recovery, only can send to phone and write error.
Anybody help me to solve this?
ntphuong said:
I have one Magic and it show in Bootloader :
PVT 32 S-OFF
1.76.0007 (SAPP*****).
Why the SAPP is SAPP*****? Is there something wrong?
Also, the device detected by fastboot is 1234567890... , not like other HTC Magic.
Now I get stuck with RUU Flash at 81% (Hong Kong RUU). --> When the device start to update system STEP. So the Magic now just show RUU, can connect by Fastboot but when use fastboot flash system or recovery, only can send to phone and write error.
Anybody help me to solve this?
Click to expand...
Click to collapse
I do have the same problem with my RUU flash with the new Rogers RUU. Stuck at 81% when device starts updating at step[4] "system". Phone will show "unzipping" for over an hour and eventually failed with error code [155].
I tried the RUU_Sapphire_HTC_Europe_3.05.401.3_release_signed_ NoDriver.exe but still the same problem. Can anyone help here?
Did more investigation, and seems like both RUU ROMs i tried might not match the CID, hence the system ROM updating failed.
Now the question is, i am stuck in RUU and cannot use adb to check my CID now. How can i manually update the system ROM given i am in RUU mode only?
How can i manually update the HBOOT and RADIO if i am stuck in RUU screen? If the RUU program can automate the process in one click, is there program to allow me to update each individually? Note that i cannot get into fastboot mode.
Any advice? Thanks!
Help
ngecw said:
Did more investigation, and seems like both RUU ROMs i tried might not match the CID, hence the system ROM updating failed.
Now the question is, i am stuck in RUU and cannot use adb to check my CID now. How can i manually update the system ROM given i am in RUU mode only?
How can i manually update the HBOOT and RADIO if i am stuck in RUU screen? If the RUU program can automate the process in one click, is there program to allow me to update each individually? Note that i cannot get into fastboot mode.
Any advice? Thanks!
Click to expand...
Click to collapse
Same problem here. Can someone help?
Thanks in advance.
ntphuong said:
I have one Magic and it show in Bootloader :
PVT 32 S-OFF
1.76.0007 (SAPP*****).
Why the SAPP is SAPP*****? Is there something wrong?
Also, the device detected by fastboot is 1234567890... , not like other HTC Magic.
Now I get stuck with RUU Flash at 81% (Hong Kong RUU). --> When the device start to update system STEP. So the Magic now just show RUU, can connect by Fastboot but when use fastboot flash system or recovery, only can send to phone and write error.
Anybody help me to solve this?
Click to expand...
Click to collapse
I had a 32B G2,it was brikked at the first time when I ruu flash the rom(Sense official). G2 couldn't received any RUU rom.it would stop at 22%.
Today,when I ruu flash the rom（HTC_Europe_3.04.401.2）,I also found it stop at 81%.
SPL is updated to 1.76.0008 from 1.76.0007.
It seems much better than before. But it still could not accept the cmd "adb shell"
Hoping somebody could help us.
I used the following RUU after upgrading to sense RUU stopped at 81%
hxxp://suntharee.com/android/RUU_Sapphire_HTC_Asia_WWE_2.53.707.2_SEA_test_sign ed_NoDriver.exe
Here is another link, its the first RUU in this post:
hxxp://forum.xda-developers.com/showthread.php?t=548096
You will end up with an ENG SPL that allows you to flash what ever you want then.
I manually updated Radio and SPL and now using CursorSense ROM.
Obviously replace the "hxxp" with "http". Hope it helps at least some of you like it did for me.
Rugga said:
I used the following RUU after upgrading to sense RUU stopped at 81%
hxxp://suntharee.com/android/RUU_Sapphire_HTC_Asia_WWE_2.53.707.2_SEA_test_sign ed_NoDriver.exe
Here is another link, its the first RUU in this post:
hxxp://forum.xda-developers.com/showthread.php?t=548096
You will end up with an ENG SPL that allows you to flash what ever you want then.
I manually updated Radio and SPL and now using CursorSense ROM.
Obviously replace the "hxxp" with "http". Hope it helps at least some of you like it did for me.
Click to expand...
Click to collapse
I tried but already got stuck in the first step of unzipping system.img. Looks like this RUU will upgrade system first before HBOOT and RADIO, hence i am still stuck with Perfected SPL.
Given that my phone has security off (SOFF), is there way to downgrade my HBOOT?
I had the same problem when HK SenseUI appeared and I managed to pass the RUU screen with a gold-card. You will find tutorials in this forum.
Good luck!
vbucuroiu said:
I had the same problem when HK SenseUI appeared and I managed to pass the RUU screen with a gold-card. You will find tutorials in this forum.
Good luck!
Click to expand...
Click to collapse
Were you upgraded to the latest perfected SPL when the same problem happens? I had my goldcard configured properly, but everytime i run RUU, the process hang at 81%, which is the time when unzipping system.img happens.
I understanding the latest SPL is still yet hard to crack, but will my phone being S=OFF, can have some ways to get the system check bypassed?
Thanks!
Hi. I have the some problem. My magic stops at 81% (system - unzipping), or when i try with another RUU_.exe stops at 22% (system - unzipping).
S-ON.
Anyone can help us?
PS: Sorry for my english.
(
Nobody knows?
ONX said:
Nobody knows?
Click to expand...
Click to collapse
Same boat...
ONX said:
Hi. I have the some problem. My magic stops at 81% (system - unzipping), or when i try with another RUU_.exe stops at 22% (system - unzipping).
S-ON.
Anyone can help us?
PS: Sorry for my english.
Click to expand...
Click to collapse
What did you do??? 32B Magic not compatible with RUU Upgrades
What exactly do you have? You posted in one place - that you have 32B
But on picture you have 32A
I installing RUU_Sapphire_HTC_Europe_3.05.401.3_release_signed_NoDriver.exe
I make a goldcard for installing _HTC Magic_RUU_Sapphire_SMC_Voda_WWE_3.03.990.6_release_signed_NoDriver.exe (with this update can enter in fastboot and vol down + power) but stops when loading system.img
Sorry for my english.
Yes, i have 32B.
Before:
SAPPHIRE PVT 32B Ship S-ON H
HBOOT-1.33.0010 (SAPP10000)
CPLD 10
RADIO-3.22.20.17
Jun 2 2009 17.28.28
After:
SAPPHIRE PVT 32A SHIP S-ON H
HBOOT-1.76.007 (SAPP10000)
CPLD-10
RADIO-6.35.07.29
Aug 4 2009, 19:43:30
Please help!
My magic (32A) suddenly changed its hboot to S-ON!!
Info in fastboot mode:
SAPPHIRE PVT 32A ENG S-ON H
HBOOT-1.76.2007 (SAPP10000)
CPLD-12
RADIO-6.35.10.18
Now I can't flash anything in fastboot, I have RA recovery v1.5.3.1.
But I can't mount the sdcard for updating the hboot again.
I have goldcard, but usb connection error show up while verifying the phone..
Can anyone has same issue?
Thank you
littlestrong said:
Please help!
My magic (32A) suddenly changed its hboot to S-ON!!
Info in fastboot mode:
SAPPHIRE PVT 32A ENG S-ON H
HBOOT-1.76.2007 (SAPP10000)
CPLD-12
RADIO-6.35.10.18
Now I can't flash anything in fastboot, I have RA recovery v1.5.3.1.
But I can't mount the sdcard for updating the hboot again.
I have goldcard, but usb connection error show up while verifying the phone..
Can anyone has same issue?
Thank you
Click to expand...
Click to collapse
Damn, I hate members like you.
a) You don't even tell us what you did wrong
b) What does this have ANYTHING TO DO TO BELONG IN THE MAGIC DEVELOPMENT?
I am sorry that I did not mention the whole story.
Where should I post this message to? myTouch 3G, Magic General?
I am using "Super-Hero (Build By AhmgskMod)" before came into this situation, I found that the phone can boot, and looping in the htc Magic screen.
Show I tried to wipe and flash the rom again. I flashed the rom for 5-6 times, but it still won't boot..
At the last one I tried to flash another rom from XDA, I found the sdcard can't mount in recovery mode. And I go to fastboot mode, S-ON is observed.
I flash my phone with sappimg.zip in hboot mode (Sdcard file can be loaded). Now I am with the rom in (RUU_Sapphire_HTC_Europe_304401), but the sdcard is not mounted after I boot up my phone.
I believe that this issue is due to the S-ON hboot, I am finding some way to flash the hboot again (I tried -- fastboot NOT OK, recovery can't mount sd)
Seek for help. Thank you very much.
littlestrong said:
I am sorry that I did not mention the whole story.
Where should I post this message to? myTouch 3G, Magic General?
I am using "Super-Hero (Build By AhmgskMod)" before came into this situation, I found that the phone can boot, and looping in the htc Magic screen.
Show I tried to wipe and flash the rom again. I flashed the rom for 5-6 times, but it still won't boot..
At the last one I tried to flash another rom from XDA, I found the sdcard can't mount in recovery mode. And I go to fastboot mode, S-ON is observed.
I flash my phone with sappimg.zip in hboot mode (Sdcard file can be loaded). Now I am with the rom in (RUU_Sapphire_HTC_Europe_304401), but the sdcard is not mounted after I boot up my phone.
I believe that this issue is due to the S-ON hboot, I am finding some way to flash the hboot again (I tried -- fastboot NOT OK, recovery can't mount sd)
Seek for help. Thank you very much.
Click to expand...
Click to collapse
u still hav hero recovery??? ( custom recovery)
Yes, I have the hero recovery (custom), I flash in by boot the hero recovery in fastboot, and flash using:
adb push recovery.img /
adb shell flash_image recovery /recovery.img
The problem is I cannot access to sdcard in recovery mode, also can't use the sdcard when I boot up the phone.
Updated: I copy the rom.zip and rom1.zip from RUU update. The rom.zip container radio and hboot. Should I flash the rom.zip in hboot, to recovery the radio and hboot?
s-on + no sd card.
This problem seems to be experienced by many people in the process of upgrading to the new radio. I have experienced it myself and i never managed to solve it. Luckily i manafed to get a replacement phone. I am still afraid of upgrading the radio on my new device in fact. I think that this seems to be a common problem which deserves to be given more attention by the devs. I. Believe there were a couple of people on the forum who managed to fix it but they are few and far between.
fastboot oem enableqxdm 0
There's been quite a few SD card problem forum threads. Try harder next time.
xaueious, Thank you very much! Now I can access the sdcard! I will try harder to search in forum before asking question next time.
And thank you for the support of everyone in this post too.
This command was not recognized by the phone in my case. It's not always that simple to solve. It would be better to know what causes it in the first place so that people can avoid it.
xaueious said:
fastboot oem enableqxdm 0
There's been quite a few SD card problem forum threads. Try harder next time.
Click to expand...
Click to collapse
Now I can use the rom in (RUU_Sapphire_HTC_Europe_304401), I use hboot mode and flash the rom1.zip from the captioned rom (renamed to sappimg.zip)
But I can't start any custom rom for new radio from XDA here (installed in recovery mode, update from zip). It just stuck at the htc Magic screen, can't boot into phone.
My SPL/Hboot is still 1.76.2007 S-ON. I have tried flash the "update-hboot-1762007-signed.zip" in recovery mode, but the Hboot is still S-ON.
I believe the problem is due to the S-ON Hboot, so I can't start any custom rom. Any way I can turn the Hboot to S-OFF?
Thank you!
Update to Amon_RA's newest hero recovery. You should be able to mount your SD card in that.
Thank you sindrefyrn. I updated to the latest RA hero recovery.
I can mount sdcard with hero recovery 1.5.3.1 too.
But problem is I can't boot my phone with custom rom, only stock rom will work.
My ENG SPL 1.76.2007 is S-ON instead of S-OFF.
I will tried to flash the RUU update to replace my existing radio and SPL tomorrow, my home PC using win7 and can't verify my phone while RUU update, I will tried it tomorrow in office with winXP.
Hope it works, will report here.
littlestrong said:
Thank you sindrefyrn. I updated to the latest RA hero recovery.
I can mount sdcard with hero recovery 1.5.3.1 too.
But problem is I can't boot my phone with custom rom, only stock rom will work.
My ENG SPL 1.76.2007 is S-ON instead of S-OFF.
I will tried to flash the RUU update to replace my existing radio and SPL tomorrow, my home PC using win7 and can't verify my phone while RUU update, I will tried it tomorrow in office with winXP.
Hope it works, will report here.
Click to expand...
Click to collapse
You can flash a RUU with higher manversion then your previous ROM.
I often find that when I go into recovery my sdcard is not mounted. The solution (for me) is to:
adb shell
mount /sdcard
exit
And that's it.
No idea why the sdcard is mounted sometimes but not other times though
sindrefyrn said:
You can flash a RUU with higher manversion then your previous ROM.
Click to expand...
Click to collapse
Is that mean I can't downgrade my SPL and radio?
I can't use fastboot to flash my SPL and radio, because S-ON SPL not allow me to do so.
Could I copy the rom.zip from RUU which contain SPL and radio, then renamed it to sappimg.zip and flash in Hboot mode?
The only thing I want to do is change my SPL back to S-OFF. What can I do?
Thank you for your help.
update: Is there any SPL.zip I can use to flash my SPL in recovery mode?
update 2: I tried flash the ENG SPL 2007.zip in recovery mode, but it can't change my SPL back to S-OFF. Is it because the SPL are in same version, so, I am not upgrading my SPL by this action?
littlestrong said:
Is that mean I can't downgrade my SPL and radio?
I can't use fastboot to flash my SPL and radio, because S-ON SPL not allow me to do so.
Click to expand...
Click to collapse
No reason you can't downgrade your SPL and radio that way, as long as the mainver of the RUU you're flashing is newer than your current.
Could I copy the rom.zip from RUU which contain SPL and radio, then renamed it to sappimg.zip and flash in Hboot mode?
Click to expand...
Click to collapse
Yes, that's possible. However, the mainver still needs to be higher than your current.
The only thing I want to do is change my SPL back to S-OFF. What can I do?
Click to expand...
Click to collapse
If you haven't yet tried, apply this as normal trough recovery.
update: Is there any SPL.zip I can use to flash my SPL in recovery mode?
Click to expand...
Click to collapse
Yes, see above.
etibon said:
This command was not recognized by the phone in my case. It's not always that simple to solve. It would be better to know what causes it in the first place so that people can avoid it.
Click to expand...
Click to collapse
That only works with the 1.76.xxxx SPL, which he has.
From personal experience, I can tell you that I screwed my phone up by flashing hboot and radio in the wrong order.. Ultimately, it prevented me from flashing the Hero recovery... So basically, I was stuck with new SPL/Radio with Sapphire recovery for a while. But here is where things got worst: I attempted to flash BACK to the OLD SPL/Radio, which worked. However, somewhere along the way enableqxdm(1.76.x only) was turned ON, and stayed on. The only thing I was able to do was go back to the stock Rogers RUU (old radio), but left with no SD card which really sucks. When Sense was released for Rogers, I flashed the new ROM and Radio (via USB) and turned enableqxdm off. All fixed at the cost of being rooted
littlestrong; which ROMs are you trying to flash? There could be a really simple explanation as to why they don't work.
1. Did you WIPE data/dalvik/ext before flashing? <- this is pretty important
2. Flash a ROM specific to the new radio?
And if you're trying to reflash your radio and SPL, what errors do you get?
sindrefyrn:
I have tried update your SPL 1.76.2007 from recovery. It remain S-ON afterward.
So, I downgrade my SPL to 1.76.0007 and raido 6.35.07.xx from HK stock sense rom (Hboot mode -> sappimg.zip). The SPL and radio are successful downgraded. Then, I flash the SPL the 1.76.2007 in recovery. No luck.. SPL has been upgraded to 1.76.2007, but it is still S-ON..
pyee0124:
I flash all roms below with full wipe (all 5 wipes in recovery), they all are for new radio:
--[ROM][32A][6.35] SenseUI 2.1 based on DROID Eris dump. Both v01 and v02.
--Super-Hero (Build By AhmgskMod) [Based On Eris Dump].
--Eclair AME [Android 2.1] MADE BY ME [Only For New Radio] [28th Feb]
I also restore a nandroid backup which it was backup with Eclair AME rom, when my phone in good condition.
All the above roms can't boot up, all stop at htc Magic screen..
I search this forum and found 2 topics about making ENG SPL to S-OFF from S-ON.
1. Flash the nandroid backup boot.img file to the phone, might be one of them will make the SPL to be S-OFF.
2. Remove the battery for a couple of day, and leave the phone as it is .The phone might change to S-OFF itself.
Another problem, I can't flash my magic in RUU. ERROR 170 was found both in XP and win7. I tested it in computer with and without htc sync. I have install proper driver.
I have one more question, I can flash custom rom for new radio here in recovery mode. But all 3 roms I had tried won't boot up and stuck in htc Magic screen. Can anyone flash custom rom with S-ON SPL and found no problem in boot??
You should still be able to flash custom ROMS regardless of S-ON. One of the other things you should try is formatting your SD card again.. Try a full FAT32, then try partitioning afterwards. I found that I could only boot Ahmgsk with FAT32/Swap/Ext2.
pyee0124: I have flashed the [ROM][32A] CursorSense32A-1.2.6.1, it can boot up with my S-ON SPL.
I will test flashing others rom and see if I can use Android 2.1.
Hello,
I'm not an expert at modding and hacking but I can definately follow directions. I used a G1 for about a year and flashed it plenty of times with different roms, radios, and spls. I ended up getting a MyTouch 1.2 and proceeded to try to root it so that I can enjoy CM's great roms.
Followed the directions on the unlockr
Made the gold card and went to flash the sappimg.img from the site. The flash went through fine but the phone just got stuck at the HTC Magic screen. Now I know what my mistake was there. I didn't think it was a big deal and continued with the steps. Mainly because I didn't see any infomation on what to do if it doesn't go through. Flashed the radio, then went to the hboot. Received image update failed error message. Long story short, I experienced what having a brick feels like.
The reason I am explaining all of this is for people to learn from my mistakes and to get some clarification on what I am writing next.
I got the phone exchanged (only had it for a day) and began researching more to find out what I did wrong. I found this crypysmoker's thread.
And then I found the message:
READ READ READ. DO NOT download the SAPPimg.zip file it says on that page.
Get the top fixed SPL file 2010 from here
Click to expand...
Click to collapse
In my research, I discovered that the mytouch 1.2 has several spl's that have been hacked and not. I figured out that the file on theunlockr wasn't the fixed spl and that is mainly the reason for my brick and the frozen HTC Magic screen.
I want to enjoy the gifts that CM has to offer. Being stuck on normal 1.6 is well saddening to say the least. But I am worried about flashing the wrong spl and have the situation repeat again as I would figure I would be screwed this time around and wouldn't be able to get it replaced.
Can anyone provide more information about this? Can I flash the Engineerings SPL v1.33.2010 and not run into the same problem? I understand that there isn't a 100% certainty of working. Most of my searches show that more people have bricked this phone than any other.
Thanks in advance and sorry for the length.
Phone Info:
SAPPHIRE PVT 32A SHIP S-ON G
HBOOT-1.33.0013 (SAPP31000)
CPLD-13
RADIO-2.22.23.02
Well, I did it all again. Redownloaded all the files. Setup a new goldcard. This time I let it sit for over 45 mins. Never got past the HTC Magic Screen. Adb doesn't see it nor does the light come on to say that it is charging. Which would show me that it has indeed locked up.
Anyways it shut off on its own since it wasn't getting usb power and I guess the battery died. I'm still able to reboot back to hboot. I attempted to reflash the sappimg.zip file. Right now its going on 10 mins sitting on the
[1] SYSTEM - Unzipping
What I will add tho is that my info changed.
SAPPHIRE UNKNOWN 32A ENG S-OFF H
HBOOT-1.33.2010 (SAPP31000)
CPLD-13
RADIO-3.22.20.17
I tried reformatting the SD and recreated the Gold Card as I noticed some of the Hex changed but still getting the same issue.
the phone won't run anything other than spl 1.33.0013 and radio 2.22.23....w/e x)
Get the sappimg you had before and flash it in hboot mode which should give you spl 1.33.0013. In fastboot mode, flash your spl to 1.33.2010again, then flash radio 2.22.23 or w/e, then flash amon ra recovery, then flash stock spl (1.33.0013).
All the files you need are here: http://theunlockr.com/2010/03/11/how-to-root-the-mytouch-1-2-and-fender-mytouch/
The reason it wont boot up is because you have engineering spl and the wrong radio on. Again, it will only boot up with the stock radio and spl~!!!
hacker01 said:
the phone won't run anything other than spl 1.33.0013 and radio 2.22.23....w/e x)
Get the sappimg you had before and flash it in hboot mode which should give you spl 1.33.0013. In fastboot mode, flash your spl to 1.33.2010again, then flash radio 2.22.23 or w/e, then flash amon ra recovery, then flash stock spl (1.33.0013).
All the files you need are here: http://theunlockr.com/2010/03/11/how-to-root-the-mytouch-1-2-and-fender-mytouch/
The reason it wont boot up is because you have engineering spl and the wrong radio on. Again, it will only boot up with the stock radio and spl~!!!
Click to expand...
Click to collapse
I don't know where I would find the original stock sappimg. The one that is on the website is the sappimg that needs to go on when you are stock at the beginning.
Also my HBoot doesn't seem to be unzipping cause that is where it gets stuck. Is there a way to do it all from fastboot? Since I am currently stuck in the 2010 spl, can I flash the stock spl through fastboot without the radio?
I just don't get why I am having this problem. I followed that website to the letter. And I know that at this point if I attempt to flash the radio back to stock, I will completely brick it.
Since you dont want to flash the radio, flash the amon ra recovery FIRST. Then flash the stock spl. If it doesn't boot up, then you'll need to get the engineering spl back on again and flash stock radio (the one in the link).
hacker01 said:
Since you dont want to flash the radio, flash the amon ra recovery FIRST. Then flash the stock spl. If it doesn't boot up, then you'll need to get the engineering spl back on again and flash stock radio (the one in the link).
Click to expand...
Click to collapse
I couldn't flash the recovery in fastboot.
Tried Fastboot boot recovery recovery.img
Got an error message Recovery not found.
Wasn't sure if I wanted to try flashing the recovery before finding out if it can brick it. Like the original post says, my first MT1.2 I flash the spl from unlockr screen locked up but could get into fastboot so flashed the radio and then tried the spl like the directions say and I completely bricked it.
I don't want to make the same mistake twice.
Unfortunately, there's a chance of bricking every time you flash anything.
Anyways, this might be redundant but is the recovery imaged named recovery.img? Like you actually renamed it? If not, you'll have to type out the exact name.
hacker01 said:
Unfortunately, there's a chance of bricking every time you flash anything.
Anyways, this might be redundant but is the recovery imaged named recovery.img? Like you actually renamed it? If not, you'll have to type out the exact name.
Click to expand...
Click to collapse
No it wasn't named recovery.img, was just using it to save time. I did spell out the recovery's full name.
When you enter the command "fastboot devices" it shows a serial number right? And the recovery image is in your tools folder of your androidsdk folder?
Sorry for the redundant questions, we're just going back to the basics really quick right now.
hacker01 said:
When you enter the command "fastboot devices" it shows a serial number right? And the recovery image is in your tools folder of your androidsdk folder?
Sorry for the redundant questions, we're just going back to the basics really quick right now.
Click to expand...
Click to collapse
yup and yup
I see the problem. Your mobo is recognized as 32a S off H. You're recovery image is probably the G version. What you could do is download the H version and flash it although i doubt your phone will still boot up at that point.
You could try flashing the H version of amon ra's recovery image and afterwards, see if it boots up. Then, if it doesnt boot up, flash stock spl (1.33.0013) and see if it boots up.
I'm pretty sure your phone will end up not booting up and you'll eventually have to flash stock radio as well and then flash the G version recovery back on.
The reason your mobo is recognized as the H version and not the G version is because of the radio.
EDIT: I just realized I made a mistake. I meant to say the mobo is recognized as the H version because of the SPL, not the radio.
EpikFail said:
I couldn't flash the recovery in fastboot.
Tried Fastboot boot recovery recovery.img
Got an error message Recovery not found.
Wasn't sure if I wanted to try flashing the recovery before finding out if it can brick it. Like the original post says, my first MT1.2 I flash the spl from unlockr screen locked up but could get into fastboot so flashed the radio and then tried the spl like the directions say and I completely bricked it.
I don't want to make the same mistake twice.
Click to expand...
Click to collapse
Heres your problem. If recovery is not found then you didnt put it in your Androidsdk\tools folder did you? or did you rename it? Oooorr, you put it in there while adb was running and didnt restart it to see the file itself
crypysmoker said:
Heres your problem. If recovery is not found then you didnt put it in your Androidsdk\tools folder did you? or did you rename it? Oooorr, you put it in there while adb was running and didnt restart it to see the file itself
Click to expand...
Click to collapse
He already said that its in the tools folder.
hacker01 said:
I see the problem. Your mobo is recognized as 32a S off H. You're recovery image is probably the G version. What you could do is download the H version and flash it although i doubt your phone will still boot up at that point.
You could try flashing the H version of amon ra's recovery image and afterwards, see if it boots up. Then, if it doesnt boot up, flash stock spl (1.33.0013) and see if it boots up.
I'm pretty sure your phone will end up not booting up and you'll eventually have to flash stock radio as well and then flash the G version recovery back on.
The reason your mobo is recognized as the H version and not the G version is because of the radio.
Click to expand...
Click to collapse
Sorry for the last reply, I do all my hacking at work so my adb setup is there. So I did this.
fastboot devices
XXXXXXXXX fastboot
fastboot boot recovery recovery-RA-sapphire-c1.6.2G.img
cannot load 'recovery'
fastboot flash recovery recovery-RA-sapphire-c1.6.2G.img
send OKAY
write OKAY
Click to expand...
Click to collapse
Holding home+power, wouldn't boot into recovery. Seems to still be stuck. Went back to fastboot
fastboot flash hboot hboot.nb0
send OKAY
write OKAY
Click to expand...
Click to collapse
Still same thing so back to fastboot I go
fastboot radio radio.img
sending 'radio' <21504 KB>... FAILED <remote: not allowed>
Click to expand...
Click to collapse
My phone now reads
SAPPHIRE PVT 32A SHIP S-ON G
HBOOT-1.33.0013 (SAPP31000)
CPLD-13
RADIO-3.22.20.17
I can tell that the radio is still the old one. It seems the spl worked and put it back to stock but still no recovery and I guess I can't fastboot anything either.
So I assume I need to flash back eng spl and see if it will boot, right?
Even as the recovery and spl are compatible, you see that it still won't boot up. What you gotta do now is flash the engineering spl and do the same as before except flash the radio as well.
In the end, your mytouch should read:
SAPPHIRE PVT 32A SHIP S-ON G
HBOOT-1.33.0013 (SAPP31000)
CPLD-13
RADIO-2.22.23.02
The same as stock before EXCEPT this time, you'll have amon ra's recovery. That's when you know you're done. Just follow the guide from before and you'll be fine.
hacker01 said:
Even as the recovery and spl are compatible, you see that it still won't boot up. What you gotta do now is flash the engineering spl and do the same as before except flash the radio as well.
In the end, your mytouch should read:
SAPPHIRE PVT 32A SHIP S-ON G
HBOOT-1.33.0013 (SAPP31000)
CPLD-13
RADIO-2.22.23.02
The same as stock before EXCEPT this time, you'll have amon ra's recovery. That's when you know you're done. Just follow the guide from before and you'll be fine.
Click to expand...
Click to collapse
So I flashed the eng spl again. Still wouldn't boot. Got the same SAPPHIRE UNKNOWN 32A ENG S-OFF H
did:
fastboot flash recovery recovery-RA-sapphire-v1.6.2G.img
send OKAY
write OKAY
fastboot boot recovery
cannot load 'recovery'
Click to expand...
Click to collapse
I'm still worried about flashing the radio....
but I should fastboot the radio and then the hboot.nb0, right?
Solved
I would like to start out by saying, Thank you so much hacker01 for your help! You don't know how much I appreciate everything.
I was able to get it back working and fully running CM5.0.7
After I reloaded the eng spl, like I said, I was running into the same problems. Wouldn't boot, goes into fastboot, etc.
I grabbed the stock radio and spl NOT from the unlockr page this time but from the link on crypysmoker's thread.
fastboot flash radio radio.img
fastboot flash hboot hboot_7201A_1.33.0013G_091021.nbo
fastboot flash recovery recovery-RA-sapphire-v1.5.2G.img
fastboot reboot-bootloader
Click to expand...
Click to collapse
Just like it said and sure enough got into recovery! Flashed a rom and it booted up.
I know this technically isn't solved cause I really don't know what went wrong in the first place. I can ensure you that I can follow directions and did. The only thing that makes any sense is the files on theunlockr's website is bad. Guess we can just chalk it up to bad luck.
But if anyone wants to root their mytouch 1.2, crypysmoker's thread is definitely the way to go.
Thank you again hacker01! I hope I can pay it forward.
You did it right, it's just that any radio that is not 2.22.23 won't work with the mt3g 1.2/Fender LE right now. And no problem! Glad you got it up and running. Enjoy your mytouch
Mod. edit: not dev related, moved to general
Please, help!
I have the exact same problem: I was following the Unlockr's instructions, made the goldcard, flashed the sappimg without getting any errors, and now the phone is stuck on the htc magic boot screen. I am not experienced and now I am scared sh**less, because the phone belongs to my girlfriend Please, give me step-by-step instructions how to fix it, because I really dont want to improvise. The phone is MyTouch 1.2...
Thank you in advance!!!
SAPPHIRE UNKNOWN 32A ENG S-OFF H
HBOOT-1.33.2010 (SAPP31000)
CPLD-13
RADIO-3.22.20.17
So here are firstly the details
-------------------------------
SAPPHIRE PVT 32A ENG S-ON H
HBOOT -1.33.2010 (SAPP10000)
CPLD-12
RADIO-3.22.20.17
Jun 2 2009, 17:27:03
-------------------------------
As you can see above I have the engineering SPL but I am unable to flash via fastboot gives me the not verified error. I previously was stuck in a reboot loop which I finally got out by creating a goldcard and using 2.53.707.2_-_sappimg.zip. I am able to use the phone but thats about it. There is no access to sd card I have tried numerous cards and they don't work.
From Inside the Phone:
-------------------------------
Firmware version: 1.5
Baseband version: 62.525.20.18U_3.22.20.17
Kernel version: 2.6.27-cb85e129
[email protected] #3
Build Number: 2.53.707.2 146733 CL#37318 test-keys
---------------------------------
I would like to thank anyone in advance for their help. I have searched and been searching the forums for 2 days non-stop usually its stated that you need an Engineering SPL (which I guess I am already using) can't downgrade because I have no access to sdcard either. Please help........
Try going here and grabbing the sappimg from there, load it onto your goldcard, and flash it from hboot the same way you did the first time. There's another guy I was working with on here that tried to use the same engineering SPL and it didn't work, but I don't know if he ever tried that one. The sappimg I'm referring you too is the same one I used when I rooted my phone. Give it a shot and let us know back here.
DonJuan692006 said:
Try going here and grabbing the sappimg from there, load it onto your goldcard, and flash it from hboot the same way you did the first time. There's another guy I was working with on here that tried to use the same engineering SPL and it didn't work, but I don't know if he ever tried that one. The sappimg I'm referring you too is the same one I used when I rooted my phone. Give it a shot and let us know back here.
Click to expand...
Click to collapse
Thanks a lot I am going to grab it right now. Will update in a bit.
*UPDATE:*
No difference same as before cannot access sdcard and same SPL & Radio. No changes... :-(
Im a noob but I just recovered myself from a semi-brick.. What i did was to load the hero recovery back onto the phone via fast boot. flash hboot 1.76.2007 via recovery. Boot back into fastboot.
fastboot flash radio Radio_HTC_PVT_32A_3.22.20.17.img
fastboot flash hboot hboot-1.33.2005.img
fastboot flash recovery recovery-RA-sapphire-v1.7.0H.img
fastboot erase system -w
fastboot reboot-bootloader
check that you are running hboot 1.33.2005 radio 3.22.20.17
then flash your rom..
worked for me, maybe it will work for you. good luck
Alien-X said:
Im a noob but I just recovered myself from a semi-brick.. What i did was to load the hero recovery back onto the phone via fast boot. flash hboot 1.76.2007 via recovery. Boot back into fastboot.
fastboot flash radio Radio_HTC_PVT_32A_3.22.20.17.img
fastboot flash hboot hboot-1.33.2005.img
fastboot flash recovery recovery-RA-sapphire-v1.7.0H.img
fastboot erase system -w
fastboot reboot-bootloader
check that you are running hboot 1.33.2005 radio 3.22.20.17
then flash your rom..
worked for me, maybe it will work for you. good luck
Click to expand...
Click to collapse
Thanks for your help but as soon as I try loading I get the verification fails
D:\AndroidSDK\tools>fastboot flash flash hboot-1.76.2007.img
sending 'flash' (512 KB)... OKAY [ 0.493s]
writing 'flash'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 0.648s
Click to expand...
Click to collapse
Any other ideas? Appreciate all the help!
flash 1.76.2007 via recovery, not fastboot.
Link for Hboot 1.76.2007 ZIP
http://www.4shared.com/file/211145376/3da88b40/update-hboot-1762007-signed.html
another reason it might not be working is becuz your doing 'fastboot flash flash"
which if correct it should be 'fastboot flash hboot'
Did this solve your issue?
Sent from my HTC Magic using XDA App
Alien-X said:
Did this solve your issue?
Sent from my HTC Magic using XDA App
Click to expand...
Click to collapse
Sorry wasn't around. Thank you for responding.
Your right I was not using HBOOT but it didn't make a difference I still get the verification error using fastboot.
As you suggested I should try updating using recovery but like I said the SDcard is not detected. I used the "fastboot -c board_sapphire.disable_sdcard=0 boot recovery...*" and it detected the sd card when I try to update the using the zip file it gets stuck at Opening update package....
Any other options?
Alright, newb here.
Now that that is out of the way, let me get to the issue.
History: I was following a howto on theunlockr.com (or however it's spelled) for rooting my myTouch 3g w/ 3.5mm headphone jack. Created goldcard, put sappimg on it, booted phone into bootloader, nothing, didn't recognize the image file. Thinking that the file was bad, I downloaded another sappimg.zip file (which I realize now was a bad mistake). After realizing that the card needed to be empty (no files other than sappimg.zip), put JUST sappimg.zip on goldcard and it worked. It uploaded the zip to memory and flashed. Then it rebooted and was stuck at a Vodafone logo. No bootup, just hangs at logo (I've left it at that for a good 10 minutes, still nothing). I can't flash from fastboot, as the SPL does signature checking. I've tried fastbooting into a recovery image, but the four I've tried so far, won't get past the three droids skating logo (and that's if I use fastboot to erase system, boot, userdata, and cache, otherwise, they'll hang at the Vodafone logo too). I've also wiped every partition on the flash other than the bootloader.
Yesterday, I've even tried to run a couple of RUU's for the thing. I had a friend try all three T-Mobile RUU's for the myTouch (from the "[ROM] Official HTC Sapphire/Magic/MT3G RUU ROM Links" thread), all failed with some version (Different failures for each though).
Oh, also, I can't do the goldcard trick anymore, because when it tries to flash the rom, the SPL hangs on the system partition.
So, gentlemen, I do believe I'm screwed.
Any help towards getting it unscrewed (even back to stock) would be greatly appreciated.
Details:
Bootloader screen banner:
SAPPHIRE UNKNOWN 32A SHIP S-ON H
HBOOT-1.33.0009 (SAPP31000)
CPLD-13
RADIO-3.22.20.17
May 8 2009, 21:02:32
Recoveries tried:
recovery-RAv1.0H
recovery-RA-hero-v1.6.2
recovery-RA-magic-v1.3.2H
recovery-RA-sapphire-v1.7.0G
recovery-RA-sapphire-v1.7.0H
Nothing?
So, nothing???
Nevermind.
Sent from my HTC Magic using XDA App
ZeroSigea said:
So, nothing???
Click to expand...
Click to collapse
I also have a MT3G 1.2 with the symptoms you describe - hangs on unzipping the system image in sappimg.zip (2.10.531.3) and (2.10.531.4). Don't even think about trying to flash sappimg.nbh (1.94.531.1) - that got me a brick semi-recoverable via JTAG.
I have also seen the Fail-PU message appear when it tries to flash the system partition (when radio 2.22.23.02 was installed).
I found that you can successfully flash sappimg.zip (2.53.707.2 including eng spl 1.33.2010), but fastboot is useless since you get the (remote: signature verify fail) message. Needless to say, this rom doesn't boot successfully.
In addition to the symptoms you describe, the USB is also broken on my MT3G 1.2, so I would need a solution that doesn't use fastboot.
Has anybody else experienced this problem or something similar with their MT3G 1.2? I would like to collect as much information as I can about this problem. I have so far been unsuccessful in finding a solution
I have working JTAG on my MT3G 1.2, so I can easily softboot any SPL. See wiki.cyanogenmod.com/index.php?title=JTAG_for_Dream/Magic for more details.
I had an idea to edit the SPL so that it skips the signature check on any sappimg.zip file you give it, and easily flash a custom sappimg.zip. Another idea I had was to get it to skip checking the main version on any sappimg.zip file you give it.
Does anybody have any ARMv6 (ARM11) disassembly experience? I could only ever get arm-none-eabi-objdump to disassemble the SPL as a ARMv5 binary...
Does anybody have any idea what I'm talking about? Am I crazy?
stewdk said:
I have working JTAG on my MT3G 1.2, so I can easily softboot any SPL. See wiki.cyanogenmod.com/index.php?title=JTAG_for_Dream/Magic for more details.
I had an idea to edit the SPL so that it skips the signature check on any sappimg.zip file you give it, and easily flash a custom sappimg.zip. Another idea I had was to get it to skip checking the main version on any sappimg.zip file you give it.
Does anybody have any ARMv6 (ARM11) disassembly experience? I could only ever get arm-none-eabi-objdump to disassemble the SPL as a ARMv5 binary...
Does anybody have any idea what I'm talking about? Am I crazy?
Click to expand...
Click to collapse
I have some ideas that I would like to bounce off you...and I would be willing to provide a phone to try them on...then we could have something to offer because this seems to be a big problem for this phone. Please PM me.
Dude, the post is from September 2010... :0)
Good luck..
mumilover said:
Dude, the post is from September 2010... :0)
Good luck..
Click to expand...
Click to collapse
It may be an old post, but I'm still having the problem I described above
My phone is sitting right here collecting dust, JTAG still hooked up and everything.
jonk26.2, I got your PM. I'm interested.
I just need to get a working openocd installation up and running again - shouldn't take too long.
EDIT: I mean I'm interested in trying your ideas. No need to send me a phone.
Let me tell you where I am and what I am thinking.
I bought a 3.5mm phone on ebay that had this issue...stuck on fastboot screen. I could get into USB fastboot just fine...and could try the goldcard root process just fine...but had the same freeze on unzipping files that everybody else had. I had the brilliant idea that I could use fastboot to erase the bad files so it could unzip files...and in my haste I erased EVERYTHING...no fastboot no nothing...dead. Then I started looking around the site for JTAG and found your post and then I thought...maybe this is the way to start...absolutely wipe the slate clean and start over.
Anyway...my mobo is dead on this phone and I would like to try to fix it if you are game.
jonk26.2 said:
and in my haste I erased EVERYTHING...
Click to expand...
Click to collapse
If you erased the radio, then I'm afraid that even the current JTAG procedure won't help you much... Try seeing if blue LED light mode works - if it does, then you might still have hope. This is discussed in the JTAG thread http://forum.xda-developers.com/showthread.php?t=591048 and also at http://wiki.cyanogenmod.com/index.php?title=JTAG_for_Dream/Magic
I know the JTAG thread can be a bear to sift through, but it has a lot of good information, including what kind of equipment they use (I'm using a Stellaris EKC-LM3S6965 eval kit which doubles as a USB-serial adapter if you program it right).
Remember that the MT3G 1.2 3.5mm jack / Fender LE won't boot anything without the stock SPL and a known compatible radio (2.22.23.02 is one).
Yes...Blue LED...nothing else.
jonk26.2 said:
Yes...Blue LED...nothing else.
Click to expand...
Click to collapse
Then in theory un-bricking is possible via jtag and serial cable.
I'm not sure about this, but if your phone is in a condition like mine, then JTAG may only be able to bring it back to the limbo state we've been seeing. Symptoms of this are: 1. seeing something like fastboot remote signature verify fail when fastboot worked (even with an engineering SPL) and 2. stuck at unzipping the system image or getting Fail-PU when installing a sappimg.zip. And as far as I know this only applies to the MT3G 1.2 3.5mm jack.
Wow...
Haven't been on in a while and I come back and see that the thread did blossom into a full discussion. Nice. Sorry to leave y'all out in the dark for so long, but I've been busy (and distracted).
So, my solution was to get it replaced. Cheap, I know, but something had to be done. So, I got another MyTouch 3G and when I was feeling brave again, I tried a different route and went with Universal Androot to root the stock ROM in place and use ClockworkMod to flash CM6 onto the device. Awesome, it worked. So we (me and the girlfriend) enjoyed our MyTouch's until we got fed up with T-Mobile's service (crappy signal, where I live). Switched to AT&T and got a HTC Aria, which I suppose is the MyTouch's cousin.
I feel hopeless
I am also suffering the same problem.
I can access fastboot but I can do nothing [Perfect SPL].
I have created a working gold card but all I'm seeing is the frozen system extraction.
tried almost any possible howto's I can find on the net but to no avail.
due to my experiment on flashing sappimg.zip, I seem have a mutated radio/spl combo!
phone info(s):
SAPPHIRE PVT 32A SHIP S-ON H
HBOOT-1.76.0000 (SAPP31000)
CPLD-13
RADIO-6.35.08.29
Nov 3 2009, 15:56:29
Phone CID: T-MOB010E
Phone version-main: 2.53.707.2
having the same problem
I have tried every combination of firmwares known to man. I have got several to begin flashing, but all stick on the unzipping system. I messed it up by originally following another post for rooting the phone and didnt realize that this my touch 1.2 is special. Apparently the firmware I flashed it with is a 32A firmware and the spl and radio are no good for this phone. So now nothing will flash. Probably have to Jtag it...
I have the same problem.
Using eng spl 1.33.2009 and 1.33.2005 through JTAG on MT3G 1.2,
At first, if I used eng spl 1.33.2009, fastboot flash [partition] [partition.img]
I got: FAILED (remote: image update error).
After that, I switched to eng spl 1.33.2005, somehow I could use fastboot flash hboot boot.nb0 from T-Mobile_US_2.10.531.4. But I only flashed that and rebooted the system to see what happened. Then I cannot do it again.
(Remote) signature verify fail, when using
fastboot flash [partition] [partition.img]
Now using eng spl 1.33.2005, fastboot flash zip T-Mobile_US_2.10.531.4.zip, it only can flash radio.img.
using eng spl 1.33.2009, fastboot flash zip T-Mobile_US_2.10.531.4.zip, it only can flash hboot, boot, radio.img. splash, but stuck at sytem image.
Using eng spl 1.33.2009 through JTAG on MT3G 1.2,
1. Stuck at unzipping the system image.
Or
2. (Remote) signature verify fail, when using
fastboot flash [partition] [partition.img]
When the system was stucked at unzipping the system image, the serial cable continues to give message:
[MDDI_HW_ERR] mddi_queue_image timeout
[MDDI_HW_ERR] mddi_queue_image timeout
Something is broken.
I can only flash sappimg.zip with eng 1.33.2010, but it doesn't a working system.
Can anyone shine light on this one?
hubh98 said:
I have the same problem.
Using eng spl 1.33.2009 and 1.33.2005 through JTAG on MT3G 1.2,
At first, if I used eng spl 1.33.2009, fastboot flash [partition] [partition.img]
I got: FAILED (remote: image update error).
After that, I switched to eng spl 1.33.2005, somehow I could use fastboot flash hboot boot.nb0 from T-Mobile_US_2.10.531.4. But I only flashed that and rebooted the system to see what happened. Then I cannot do it again.
(Remote) signature verify fail, when using
fastboot flash [partition] [partition.img]
Now using eng spl 1.33.2005, fastboot flash zip T-Mobile_US_2.10.531.4.zip, it only can flash radio.img.
using eng spl 1.33.2009, fastboot flash zip T-Mobile_US_2.10.531.4.zip, it only can flash hboot, boot, radio.img. splash, but stuck at sytem image.
Using eng spl 1.33.2009 through JTAG on MT3G 1.2,
1. Stuck at unzipping the system image.
Or
2. (Remote) signature verify fail, when using
fastboot flash [partition] [partition.img]
When the system was stucked at unzipping the system image, the serial cable continues to give message:
[MDDI_HW_ERR] mddi_queue_image timeout
[MDDI_HW_ERR] mddi_queue_image timeout
Something is broken.
I can only flash sappimg.zip with eng 1.33.2010, but it doesn't a working system.
Can anyone shine light on this one?
Click to expand...
Click to collapse
man, if this IS thru JTAG..., I am losing hope
I still have hope.
I was able to bring it back to work once.
After fastboot flash zip T-Mobile_US_2.10.531.4.zip, stucked at unzipping the system image, I took off the battery and was able to flash sappimg.zip (T-Mobile_US_2.10.531.4) on SD card through hboot (stock 1.33.0013G) successfully. And system was working but SD card reader was disabled in android system, so I read that I need to root the system, and I followed the
http://theunlockr.com/2010/03/11/how-to-root-the-mytouch-1-2-and-fender-mytouch/
and installed the sappimg.zip with (eng spl 2010). Then eng spl 2010 flashed sappimg.zip (T-Mobile_US_2.10.531.4) and stuck at unzipping the system image. [However, it was worked at the very beginning when the MT3G 1.2 with froyo,~~~ Wrong! I didn't use the SAPPIMG with eng spl 2010 at that time, and I only used the universal androot to root the phone~~~ and before I bricked the phone when I used RUU to downgraded it back to Donut.~~This is true. ]
This can explain why I can flash sappimg.zip (T-Mobile_US_2.10.531.4) on SD card through hboot (stock 1.33.0013G) successfully at first place. So the sappimg.zip with (eng spl 2010) is halmful, because it updates the main version.
When I rebooted the system and used the stock spl 1.33.0013G to reflash (T-Mobile_US_2.10.531.4), I have the "main version is older" error.
It looks like each time it becomes worse, there are some kind of watchdog programs in the system?
Because of the hybrid nature of the MT3G 1.2 (32A hardware/32B ROM), the partitions probably messed up, because I saw "partition update failed".
I just cannot repeat the process, when I jtag the phone,
I also saw
[ERR] partition_read::Failed to read page 19072 or it is empty, when soft boot the system as
http://forum.xda-developers.com/showpost.php?p=5715534&postcount=214.
hubh98 said:
I still have hope.
I was able to bring it back to work once.
After fastboot flash zip T-Mobile_US_2.10.531.4.zip, stucked at unzipping the system image, I took off the battery and was able to flash sappimg.zip (T-Mobile_US_2.10.531.4) on SD card through hboot (stock 1.33.0013G) successfully. And system was working but SD card reader was disabled in android system, so I read that I need to root the system, and I followed the
http://theunlockr.com/2010/03/11/how-to-root-the-mytouch-1-2-and-fender-mytouch/
and installed the sappimg.zip with (eng spl 2010). Then eng spl 2010 flashed sappimg.zip (T-Mobile_US_2.10.531.4) and stuck at unzipping the system image. [However, it was worked at the very beginning when the MT3G 1.2 with froyo, and before I bricked the phone when I used RUU to downgraded it back to Donut.]
When I rebooted the system and used the stock spl 1.33.0013G to reflash (T-Mobile_US_2.10.531.4), I have the "main version is older" error.
It looks like each time it becomes worse, there are some kind of watchdog programs in the system?
Because of the hybrid nature of the MT3G 1.2 (32A hardware/32B ROM), the partitions probably messed up, because I saw "partition update failed".
I just cannot repeat the process, when I jtag the phone,
I also saw
[ERR] partition_read::Failed to read page 19072 or it is empty, when soft boot the system as
http://forum.xda-developers.com/showpost.php?p=5715534&postcount=214.
Click to expand...
Click to collapse
ok bro, I wish you luck on unbricking your phone, let us know if you succeeded!
Can any one help me check the main version of the original MT3G 1.2 before using the SAPPIMG.ZIP with eng spl 2010 (main version 2.53.707.2)?
fastboot getvar version-main
Even after I flashed back to T-Mobile_US_2.10.531.4 (stopped at system), the main version is still 2.53.707.2. I think the main version of T-Mobile_US_2.10.531.4
is 2.10.531.4. So the SAPPIMG.ZIP with eng spl 2010 (main version 2.53.707.2) is potentially harmful at least for some MT3G 1.2.
hubh98 said:
Can any one help me check the main version of the original MT3G 1.2 before using the SAPPIMG.ZIP with eng spl 2010 (main version 2.53.707.2)?
fastboot getvar version-main
Even after I flashed back to T-Mobile_US_2.10.531.4 (stopped at system), the main version is still 2.53.707.2. I think the main version of T-Mobile_US_2.10.531.4
is 2.10.531.4. So the SAPPIMG.ZIP with eng spl 2010 (main version 2.53.707.2) is potentially harmful at least for some MT3G 1.2.
Click to expand...
Click to collapse
I don't hold the unit now, but I hope someone here could lend a hand on this