Before you start one note, this method only works if you succesfully flashed HSPL before and is intended as last help to unbrick your device.
If you have a untouched bricked stock rom on your device with a stock SPL don't try but just return it for repair.
More info about HSPL you can find here, credits to Cotulla and Bepe.
http://forum.xda-developers.com/showthread.php?t=611433
Please follow this steps carefully.
01.Download the rom here:
RUU_Leo_1_5_TMOUS_2.02.531.MASD_S__Radio_Signed_15.29.50.07U_2.06.50.04_TeleNav-5.5.42.zip
02.) Download attached MTTY
03.) Make a folder on your desktop in C:\
C:\Recovery\
C:\Recovery\TMOUS202\
04.) Put downloaded MTTY unzipped in C:\Recovery\.
05.) The unzipped T-MOUS 2.02 you copy to C:\Recovery\TMOUS202\.
06.) Extract the TMOUS 2.02 exe by right klicking it and choose extract.
07.) Remove all files extracted exept RUU_Signed.nbh
08.) Rename RUU_Signed.nbh to LEOIMG.nbh and copy it to your device storage card.
Now next steps I've used Windows XP and don't know how it works in other OS so you need to find out yourself sorry.
09.) Open MS ActiveSync\settings and disable USB connection.
10.) Take out sim card and storage card from your device.
11.) Next put your device in bootloader (volume down button + Power button) and connect to your pc.
12.) Open MTTY in the directory where you have copied it C:\Recovery\.
13.) Port you choose 'USB'and press ok.
14.) In the window that follows next type 'Task 29'(without the quotes) and press ENTER.
15.) MTTY will give you some errors in next Window but please ignore.
16.) Next disconnect your device from USB, take battery out and put your storage card in.
17.) Put battery back in and put the device in bootloader and follow the onscreen instruction to flash.
If this method worked for you then download a shipped rom that came with
your device from the factory website using your device serial and flash this rom from storage card
Follow the same steps (6,7,8) as you did before with this rom to get LEOIMG.nbh
Your back to factory rom.
Reminder, in order to flash a cooked rom again you need to flash Bepe and Cotulla's HSPL.
This method worked on a bricked European HD2 which gave us a radio fail message.
I'm pretty sure it will work for your TMOUS too.
FINGERS CROSSED!
A special thanks to Xmoo for the mirror and standbye help unbricking the device.
Succes, Laurentius26
Disclaimer
I don't take any responsibility for any conflict, fault, or damage caused by
this method. No warranties of any kind are given.
In somecases SPL 2.02 will lock your device. However, using a Goldcard did solve this issue.
So have a goldcard as back-up.
awesome. now people have slight hope..
Z51 said:
awesome. now people have slight hope..
Click to expand...
Click to collapse
Now we need people who have a bricked device to test it.
Thanks Xmoo, but everything better then a bricked device isn't?
Here's a good Tutorial thanks to Jagnet just incase people need a Goldcard:
http://forum.xda-developers.com/showthread.php?t=591314
Lock the device sounds scary but it actualy means the device is locked in the SPL (bootloader)
that comes with the T-Mob 2.02 rom not giving you the possibility to flash to another shipped rom.
xmoo said:
In somecases SPL 2.02 will lock your device. However, using a Goldcard did solve this issue.
So have a goldcard as back-up.
Click to expand...
Click to collapse
+1, fingers crossed this method unbricks the device for them.
xmoo said:
Now we need people who have a bricked device to test it.
Click to expand...
Click to collapse
the USB port doesn't show up in in mtty
ok it must be due to windows 7,
I will try with windows xp
whoops, i will edit later
Laurentius26 said:
Please follow this steps carefully.
01.) Download the exact rom below from here:
http://www.vbnfiles.com/xda/xmoo/Leo/TMOUS/
RUU_Leo_1_5_TMOUS_2.02.531.MASD_S__Radio_Signed_15.29.50.07U_2.06.50.04_TeleNav-5.5.42.zip
02.) Download attached MTTY
03.) Make a folder on your desktop in C:\
C:\Recovery\
C:\Recovery\TMOUS202\
04.) Put downloaded MTTY unzipped in C:\Recovery\.
05.) The unzipped T-MOUS 2.02 you copy to C:\Recovery\TMOUS202\.
06.) Extract the TMOUS 2.02 exe by right klicking it and choose extract.
07.) Remove all files extracted exept RUU_Signed.nbh
08.) Rename RUU_Signed.nbh to LEOIMG.nbh and copy it to your device storage card.
Now next steps I've used Windows XP and don't know how it works in other OS so you need to find out yourself sorry.
09.) Open MS ActiveSync\settings and disable USB connection.
10.) Take out sim card and storage card from your device.
11.) Next put your device in bootloader (volume down button + Power button) and connect to your pc.
12.) Open MTTY in the directory where you have copied it C:\Recovery\.
13.) Port you choose 'USB'and press ok.
14.) In the window that follows next type 'Task 29'(without the quotes) and press ENTER.
15.) MTTY will give you some errors in next Window but please ignore.
16.) Next disconnect your device from USB, take battery out and put your storage card in.
17.) Put battery back in and put the device in bootloader and follow the onscreen instruction to flash.
If this method worked for you then download a shipped rom that came with
your device from the factory website using your device serial and flash this rom from storage card
Follow the same steps (6,7,8) as you did before with this rom to get LEOIMG.nbh
Your back to factory rom.
Reminder, in order to flash a cooked rom again you need to flash Bepe and Cotulla's HSPL again.
This method worked on a bricked European HD2 which gave us a radio fail message.
I'm pretty sure it will work for your TMOUS too.
FINGERS CROSSED!
A special thanks to Xmoo for the mirror and standbye help unbricking the device.
Succes, Laurentius26
Click to expand...
Click to collapse
Great TUT!
Yes, this exact ROM (or 2.03) will work with the HD2 TMO USA model. Actually, I have found that this is the ONLY rom (LEOIMG.nbh) that will flash to my TMO USA HD2. Long story short...I flashed a ROM with a unwanted watermark and the only way (outside of goldcard) to get rid of the watermark was flashing 2.03.
NOTE: Currently, I have been unsuccessful in finding a way to flash this SPL. HSPL, SSPL, USPL, etc. has not worked. Otherwise, the stock ROM ain't half bad Working with xmoo on goldcard solution.
Check out my HD2 ROM 2.03 (SPL 2.02) thread for more details: http://forum.xda-developers.com/showthread.php?t=667499
task 29
Format BINFS start
Fill RSVD information for block 497 to 530
CE start start block=530, total block=7662
erase_page - error bad status: 0xB791E960
ERASE block 92 FAIL !!!
erase_page - error bad status: 0xB791E960
ERASE block 649 FAIL !!!
erase_page - error bad status: 0xB791E960
ERASE block 1210 FAIL !!!
erase_page - error bad status: 0xB791E960
ERASE block 1235 FAIL !!!
erase_page - error bad status: 0xB791E960
ERASE block 1593 FAIL !!!
erase_page - error bad status: 0xB791E960
ERASE block 1952 FAIL !!!
erase_page - error bad status: 0xB791E960
ERASE block 2178 FAIL !!!
erase_page - error bad status: 0xB791E960
ERASE block 2710 FAIL !!!
erase_page - error bad status: 0xB791E960
ERASE block 3628 FAIL !!!
erase_page - error bad status: 0xB791E960
ERASE block 3797 FAIL !!!
erase_page - error bad status: 0xB791E960
ERASE block 3910 FAIL !!!
erase_page - error bad status: 0xB791E960
ERASE block 3968 FAIL !!!
erase_page - error bad status: 0xB791E960
ERASE block 4172 FAIL !!!
erase_page - error bad status: 0xB791E960
ERASE block 4265 FAIL !!!
erase_page - error bad status: 0xB791E960
ERASE block 4267 FAIL !!!
erase_page - error bad status: 0xB791E960
ERASE block 4590 FAIL !!!
erase_page - error bad status: 0xB791E960
ERASE block 4671 FAIL !!!
erase_page - error bad status: 0xB791E960
ERASE block 4837 FAIL !!!
erase_page - error bad status: 0xB791E960
ERASE block 5054 FAIL !!!
erase_page - error bad status: 0xB791E960
ERASE block 5608 FAIL !!!
erase_page - error bad status: 0xB791E960
ERASE block 5709 FAIL !!!
erase_page - error bad status: 0xB791E960
ERASE block 6229 FAIL !!!
erase_page - error bad status: 0xB791E960
ERASE block 6286 FAIL !!!
erase_page - error bad status: 0xB791E960
ERASE block 6356 FAIL !!!
erase_page - error bad status: 0xB791E960
ERASE block 6538 FAIL !!!
erase_page - error bad status: 0xB791E960
ERASE block 6678 FAIL !!!
erase_page - error bad status: 0xB791E960
ERASE block 7212 FAIL !!!
erase_page - error bad status: 0xB791E960
ERASE block 7370 FAIL !!!
erase_page - error bad status: 0xB791E960
ERASE block 7513 FAIL !!!
TAG NOT FOUND !!! NOT CLEAR STORAGE !!!
Format BINFS end
Click to expand...
Click to collapse
thats was 15.) MTTY will give you some errors in next Window but please ignore.
but 16 and 17, are confusing to me.
NOTE: I did copy LEOIMG.nbh to my microSDcard
but booting in bootloader mode, doesn't do anything...
what am I doing wrong?
16.) Next disconnect your device from USB, take battery out and put your storage card in.
17.) Put battery back in and put the device in bootloader and follow the onscreen instruction to flash.
Just like I have written, don't be scared because Task 29 doesn't touch the bootloader.
And you MUST follow all steps otherwise this method won't work.
Raioneru said:
thats was 15.) MTTY will give you some errors in next Window but please ignore.
but 16 and 17, are confusing to me.
NOTE: I did copy LEOIMG.nbh to my microSDcard
but booting in bootloader mode, doesn't do anything...
what am I doing wrong?
Click to expand...
Click to collapse
ok, so I'm doing it, but still no success.I see the bootloader but nothing shows up.
How did you brick your device if I may ask?
Did you use HSPL before it bricked?
The only thing I can think of is that you are using a stock SPL and you aren't able to change as it's locked.
Can you tell me what SPL shows in your bootloader?
Raioneru said:
ok, so I'm doing it, but still no success.I see the bootloader but nothing shows up.
Click to expand...
Click to collapse
Laurentius26 said:
How did you brick your device if I may ask?
Did you use HSPL before it bricked?
The only thing I can think of is that you are using a stock SPL and you aren't able to change as it's locked.
Can you tell me what SPL shows in your bootloader?
Click to expand...
Click to collapse
PB81120 SS-B3
SPL-2.08.0000 8G XE
MicroP(LED) 0x05
MicroP(TOUCH) 0x40
thats what I said in the other thread, this is a brand new phone, I have never flashed it with HSPL
In that case there's nothing else then return it for repair.
Your SPL isn't hacked so it's good for warranty.
Raioneru said:
PB81120 SS-B3
SPL-2.08.0000 8G XE
MicroP(LED) 0x05
MicroP(TOUCH) 0x40
thats what I said in the other thread, this is a brand new phone, I have never flashed it with HSPL
Click to expand...
Click to collapse
ok thanks then,
too bad though
Sorry friend, but a stock SPL is locked and makes it impossible to flash a cooked rom or a rom in another language.
http://forum.xda-developers.com/showthread.php?t=653614
The only thing you can still try is to download the rom for your device using the TMob website and try to flash the rom using your pc.
If it's still stuck there then you need to return it.
My bad as well, as I should have mentioned it only works when you flashed HSPL and a cooked rom before, that's why I opened this thread to help people.
I will update page 1 with a warning.
Raioneru said:
ok thanks then,
too bad though
Click to expand...
Click to collapse
Thanks for confirm, hopefully you find a way to get out of SPL.
On the HTC HD2 we unbricked it was no problem to flash a stock rom from sd card afterwords.
Maybe you could try to use a sd card with Goldcard on it and then follow this method one more time?
fix4tv said:
Great TUT!
Yes, this exact ROM (or 2.03) will work with the HD2 TMO USA model. Actually, I have found that this is the ONLY rom (LEOIMG.nbh) that will flash to my TMO USA HD2. Long story short...I flashed a ROM with a unwanted watermark and the only way (outside of goldcard) to get rid of the watermark was flashing 2.03.
NOTE: Currently, I have been unsuccessful in finding a way to flash this SPL. HSPL, SSPL, USPL, etc. has not worked. Otherwise, the stock ROM ain't half bad Working with xmoo on goldcard solution.
Check out my HD2 ROM 2.03 (SPL 2.02) thread for more details: http://forum.xda-developers.com/showthread.php?t=667499
Click to expand...
Click to collapse
Laurentius26 said:
Sorry friend, but a stock SPL is locked and makes it impossible to flash a cooked rom or a rom in another language.
http://forum.xda-developers.com/showthread.php?t=653614
The only thing you can still try is to download the rom for your device using the TMob website and try to flash the rom using your pc.
If it's still stuck there then you need to return it.
My bad as well, as I should have mentioned it only works when you flashed HSPL and a cooked rom before, that's why I opened this thread to help people.
I will update page 1 with a warning.
Click to expand...
Click to collapse
I searched the T-Mo site and cannot find the stock ROM for HD2; do you know where it's hiding?
its not available on their website, but I think it i on the forum
Related
Hi !,
I'm tryin upgrade ROM with Siemens+ATT A3.0.9 (pocket pc 2002 to WM2003).
Manage to burn it to SD (inside XDA) with XDATool.
Then do hard reset..but bootloader 6.22 just ignore the SD and not
give option to load the new ROM inside the SD.
I found an opinion : to downgrade the bootloader to 5.15...but I hope
to maintain the 6.22 bootloader unless it is really need to downgrade the bootloader. Furthermore I don't know to patch or downgrade the bootloader
Here is my device info :
ROM version 3.20.06 ENG
ROM date 07/30/03
Radio version 4.21.01
Protocol version 32S54
Bootloader 6.22
So what should i do ? hope for assistance from somebody.
Try using XDAtools to directly flash your ROM ... if worked it will update your boot loader to 5.15
Ok, the main problem is that I have bootloader 6.22 as well and foolishly have upgraged to the T-Mobile Rom.
Since then I have tried using the Kitchen to make a "B" type rom but to no avail.
Plus since this rom has been isnatlled it will no longer accept any different types of Rom other than that of a "B" type rom. I can't even use the pther "Programme A / B" to flash my rom
so in other words. I am stuck until I can find a way to change the header string on a rom. or to find a way to download a "B" type rom.
Please note. I tried putting a "B" Type rom in to the header string section of the kitchens and it cooked it... But still isn't recognised by my device.
Hi
today wanted to flash my PVT32A with the new Taiwan rom with Sense .
I got the rom.zip file from htc , unzipped it and the just got dumb! tested to flash the new radio only (bad habit from old WM days)
fastboot flash radio radio.img
went well and then I restared the device
===> boot loop
I said OK! then I flashed it one more time
same command
Fastboot uploaded the radio.img to the phone and then the phone started to write it and just there the screen goes black!!!
I have the eng spl s-off
I tried to flash the old radio ===> SAME RESULT!
i testet fastboot erase radio
and then flashed again with same result.
any suggestion ? you don't need to explain every thing as a very very short hint/instruction will be appreciated too!
Edit
Fastboot boot recovery.img boots up and the menu comes up , one sec later it reboots!
shwan_3 said:
Hi
today wanted to flash my PVT32A with the new Taiwan rom with Sense .
I got the rom.zip file from htc , unzipped it and the just got dumb! tested to flash the new radio only (bad habit from old WM days)
fastboot flash radio radio.img
went well and then I restared the device
===> boot loop
I said OK! then I flashed it one more time
same command
Fastboot uploaded the radio.img to the phone and then the phone started to write it and just there the screen goes black!!!
I have the eng spl s-off
I tried to flash the old radio ===> SAME RESULT!
i testet fastboot erase radio
and then flashed again with same result.
any suggestion ? you don't need to explain every thing as a very very short hint/instruction will be appreciated too!
Edit
Fastboot boot recovery.img boots up and the menu comes up , one sec later it reboots!
Click to expand...
Click to collapse
I had this problem too, i "solved" it by flashing 3.03 from the .exe file... Now i am however stuck on a new perfect spl and no root... (but a good rom never the less)
Please move this thread.
Make room for the ROM development...thanks.
I'm a linux user and wife's Vista just don't want to work! will test .
If any body have another way to do this( avoiding p-spl) please tell!
Reignzone said:
Please move this thread.
Make room for the ROM development...thanks.
Click to expand...
Click to collapse
I think it has to do with rom devel. as I was testing and still am testing the new rom and radio ... to release TheNano ROM to Swedroid Swedish android community
tried to install from the exe file, the updater cant find the phone as it is only starting in recovery mode.
Is there any information about what steps the update utility takes to do the actual update so I can do them by hand .
what is the boo_special.img file for ?
hey, guys ... any suggestion?
http://forum.xda-developers.com/showthread.php?t=830758
Deleted. Didn't notice that this thread is ancient.
I'm new at installing custom ROMs, so I would like to know what do I need to install a custom ROM on my phone before jumping in to it, if there is already a thread please let me know, but I hate having to go through to figure out what I need.
My Phone:
OS: Android Froyo 2.2.1 from this post: http://forum.xda-developers.com/showthread.php?t=807899
Rooted via SuperOneClick: http://forum.xda-developers.com/showthread.php?p=13651805
FastBoot Info:
Sapphire PVT 32B S-ON G
HBoot-1.33.0013 (SAPP30000)
CPLID-10
Radio-2.22.28.25
Oct 21 2009,22:33:27
I would like to try out Gingerbread like COS-DS or Ginger Yoshi, but if those are not recomended for my phone, then the best recomended ROM.
Please let me know what preparations I need to get me started with this.
Thank You in advanced for all your help.
http://forum.xda-developers.com/showthread.php?t=794445
read that and then
you could try these:
http://forum.xda-developers.com/showthread.php?t=1025330
http://forum.xda-developers.com/showthread.php?t=932118
happy flashing buddy
What NBH should I use?
I read this post http://forum.xda-developers.com/showthread.php?t=529019 and I do have a fastboot remote: not allow (Perfected SPL), soi I went to the post linked (http://forum.xda-developers.com/showthread.php?t=548218) With my HBoot Info above, what NBH Should I Use?
A) ROM v2.53.707.2 (Engineerings SPL v1.33.2010)
B) ROM v2.16.707.3 (NON-Perfected stock SPL v1.33.0009)
C) ROM v2.16.151.1 (NON-Perfected stock SPL v1.33.0009)
D) Other? (Please specify and provide link)
Please consider I will be trying to flash Ginger Yoshi (http://forum.xda-developers.com/showthread.php?t=932118)
Thank You.
you'll need to update your spl buddy so follow this (this is the exact guide you need if you want ginger yoshi)
http://forum.xda-developers.com/showthread.php?t=909900
then go ahead and flash ginger yoshi
http://forum.xda-developers.com/showthread.php?t=932118
happy flashing
I Flashed Recovery!
I try to flash recovery and it doesn't work! ROM Manager say's it flashed the recovery but neither clockworkmod nor Amon_Ra works When I try to boot in to recovery it stays at the green MyTouch Spash Screen and nothing happens, and if I connect it to the USB port "FLASHBOOT USB" appears in the upper left corner, but I can't do anything... Here is my OS info, maybe it´s blocking the flahsinf of the custom recovery:
Android Version: 2.2.1
Baseband Version: 62.50SJ.20.17U_2.22.28.25
Kernel Version: 2.6.32.9-27237-gbe746fb [email protected] #1
Build Number: FRG83D
I googled and I tried flahsing the recovery via FastBoot and I get the Remote Not Allow eror and if I try Flas_Image I get the Stop (Signal) error and/or Invalid Instrucion error.
Edit: I took the flash_image file from the Ginger Yoshi ROM (opened the "Ginger+yoshi+1.1.zip" and took flash_image from system\bin\) pushed it to the sdcard, pushed the reovery.img and followed these steps:
mount -o remount, rw /system
cp /sdcard/flash_image /system/bin
cd /system/bin
chmod 777 flash_image
flash_image recovery /sdcard/recovery.img
now flash_image doesn't give me an "Illegal instruction" but gives me these:
mtd: read error at 0x00000000 (Out of memory)
mtd: read error at 0x00020000 (Out of memory)
mtd: read error at 0x00040000 (Out of memory)
mtd: read error at 0x00060000 (Out of memory)
mtd: read error at 0x00080000 (Out of memory)
mtd: read error at 0x000a0000 (Out of memory)
.
.
.
mtd: read error at 0x004e0000 (Out of memory)
error reading recovery: No space left on device
flashing recovery from /sdcard/recovery.img
mtd: write error at 0x00000000 (Out of memory)
mtd: re-read error at 0x00000000 (Out of memory)
.
.
.
mtd: re-read error at 0x004e0000 (Out of memory)
mtd: write error at 0x004e0000 (Out of memory)
mtd: re-read error at 0x004e0000 (Out of memory)
mtd: skipping write block at 0x004e0000
failed with error: -1
error writing recovery#
Also, I tried flashing RA Recovery from CM Mod and it read that it flashed OK, but when I try to boot to recovery (after waiting more than 1 minute) I plugged it in to the USB and noticed the green over red "FastBoot USB" on the upper left corner of the MyTouch 3G screen, so I tried fastboot devices and I got "HT98TP302788 fastboot"
After some serious googleing I found out that I need to flash_image as soon as the phone boots up so it can run seems that the the MT3G (32B) uses too much memory on 2.2.1 to fhasl_iamge to run I'm creating a nandroid backup and will proceed with the rest... wish me luck!
What options do I have?
I'm Running on Ginger Yoshi!
Woot! Thanks CH3NO2 for pointing me in the right direction!
Basically, I was trying to root my myTouch 3g. I kept getting error messages with fastboot and other things with my PC, SuperOneClick wasn't rooting my phone. I had downgraded to Cupcake 1.5 to do the entire process. I had been using sappimg.nbh files to downgrade and upgrade. But, somehow, I download the Vodaphone HTC Magic 1.5 file instead of the MyTouch 3g cupcake 1.5 file. I'm tired of trying to root my phone and having things go wrong. But I want to get my MyTouch Froyo 2.2.1 rom back, but I can not find any sappimg.nbh files that will let me restore it, it keep getting the "Main version is older, please reboot" error message. All I want is my 2.2.1 froyo rom back. How can I do this?
EDIT: Also, ROM Manager won't install on my version of android, and flashrec.apk isn't flashing any recovery images on my version of android either. I downloaded Universal Androot, and it says my phone has been rooted, and installed SuperUser. I just can't get a recovery image flashed, and can't get fastboot to do anything on my pc. Basically, whenever I flash something with fastboot, my command prompt says "Downloading recovery.img xxxxkb" and just hangs on that, while my phone, in fastboot mode, just sits there. It gets a progress bar, but never moves.
Is this a 32a or 32b board? It would be immensely helpful if you could list out everything it says at your fastboot screen.
Sent from my Sapphire/dream using XDA App
As TheBladeofFate suggested, please provide ALL fastboot info.. ALL
Also run these command in fastboot mode:
Code:
fastboot getvar version-main
fastboot getvar cid
We will take from there
mumilover said:
As TheBladeofFate suggested, please provide ALL fastboot info.. ALL
Also run these command in fastboot mode:
Code:
fastboot getvar version-main
fastboot getvar cid
We will take from there
Click to expand...
Click to collapse
Fastboot info:
Code:
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
Code:
c:\Android>fastboot getvar version-main
version-main: 2.16.151.1
finished. total time: 0.003s
c:\Android>fastboot getvar cid
cid: T-MOB010Å╥♠ÿ"
finished. total time: 0.002s
I have made a goldcard, but everytime I try to put a SAPPIMG.nbh/.zip on it, it still says "Main Version is Older" everytime I try to flash something else onto it..
Download this file:
https://rapidshare.com/files/436753940/2.53.707.2_-_sappimg.zip
1)rename the file to sappimg.zip
2)put it on the goldcard
3)start in hboot mode (hold volume - together with power. '-' = volume decrease)
4)The device should pick up the file, follow screen instructions and flash the sappimg.
5)once this has finished, you should restart and confirm you have 1.33.2010 as spl nr.
6)post here the progress and wait for further instructions
Still getting the "Main Version is Older" error message with this... :/
Cannot be... your version is 2.16.151.1 and the one i gave you is 2.53.707.2...
Simple math:
2.53.707.2 > 2.16.151.1
So either you have provided the wrong version or there is something completely wrong with your device...
My bad... it gave the "Model ID Incorrect" error this time, not the "Main Version is Older" one.
Could it be the goldcard? I've tried it using two different SanDisk cards and a Transcend card... I know certain card manufacturers won't work as a goldcard...
partyboynx2 said:
My bad... it gave the "Model ID Incorrect"
Click to expand...
Click to collapse
It's a faulty goldcard.
That error is the reason why you use a goldcard... to use a sappimg.zip from another model id :0)
Should I try remaking my goldcard? I just went to the website to make it, and the page seems to be down... or should I try a different brand of SD card with my original goldcard.img file?
Every goldcard.img is unique for the specific sdcard which you got the unique cid.
Thats why you can make a goldcard on one device and it will work on another... its sdcard specific... but you cannot take an image from sdcard to another sdcard...
Try to remake... try another sdcard... what ever...
As long as you get the "model id error" you are doing something wrong...
I made downloaded the QMAT (I think it is now called Rev Tools) to reverse the CID string. I'm getting the CID string from the Terminal Emulator app, then emailing it directly to my email, copying the string, pasting it in the Crypto Toolbox app, reversing the string, replacing the first two digits with 00, creating the goldcard.img, opening that and my sd card in HxD, replacing up to line 00000170 with the goldcard, saving, placing sappimg.zip on it, and hbooting the sappimg.zip. Still getting the Model ID error. I've done this with 4 different SD cards now... what could I be doing wrong?
Am I not supposed to replace the first two digits? I swear it says that in the instructions.. that seems like it could be my only error.
partyboynx2 said:
I made downloaded the QMAT (I think it is now called Rev Tools) to reverse the CID string. I'm getting the CID string from the Terminal Emulator app, then emailing it directly to my email, copying the string, pasting it in the Crypto Toolbox app, reversing the string, replacing the first two digits with 00, creating the goldcard.img, opening that and my sd card in HxD, replacing up to line 00000170 with the goldcard, saving, placing sappimg.zip on it, and hbooting the sappimg.zip. Still getting the Model ID error. I've done this with 4 different SD cards now... what could I be doing wrong?
Am I not supposed to replace the first two digits? I swear it says that in the instructions.. that seems like it could be my only error.
Click to expand...
Click to collapse
I think I know what happened. I wasn't clicking "Removable Disk (I" in HxD which is where my SD was mounted. I was clicking some other Removable Disk in the list.. Once I corrected this, I tried doing it, then my SD card kept saying to format it. Looks like I need to wait it out a few days until I can get a Kingston SD card :|
Sorry for the triple post. I got the Goldcard working finally. I followed all these steps and completed them all, and my spl is now the one that is noted.
Code:
1)rename the file to sappimg.zip
2)put it on the goldcard
3)start in hboot mode (hold volume - together with power. '-' = volume decrease)
4)The device should pick up the file, follow screen instructions and flash the sappimg.
5)once this has finished, you should restart and confirm you have 1.33.2010 as spl nr.
6)post here the progress and wait for further instructions
What do I do in the next step?
Sorry for the delay.
You now have eng spl = full control.
You need custom recovery: http://rapidshare.com/files/387932919/recovery-RA-sapphire-v1.7.0G.img
You need this radio: https://rapidshare.com/files/455782324/2.22.19.26I.img
You need fastboot commander: Get it from signature (v.1.1 and NOT magic)
You need this rom: http://android.d3xt3r01.tk/cyanogen/dream/update-cm-6.1.0-DS-signed.zip
You need gaps (google apps): http://android.d3xt3r01.tk/cyanogen/gapps/gapps-mdpi-tiny-20101020-signed.zip
1)
Flash the radio and recovery from the fastboot commander tool.
Restart into recovery: Hold home and power together.
2)wipe everything you can find
3)flash the rom
4)flash the gapps
5)restart into the system
6)enjoy and take a rest... you have been working to long.
Good luck
Hello,
can anyone suggest how to recover HTC magic after flashing Rogers RUU official over custom rom.
ROM update was aborted on updating system partition.
Problem is that I can't upload any part of rom because phone is now S-ON. I'am getting signature error.
Flashed RUU: 42) [xda-ftp] [4shared] 3.54.631.3 Rogers Canada + [SAPPIMG.ZIP format]
ADB is no longer possible. Only FASTBOOT and RUU USB.
See attched photo for fastboot details.
Thanks in advance.
pero256 said:
Hello,
can anyone suggest how to recover HTC magic after flashing Rogers RUU official over custom rom.
ROM update was aborted on updating system partition.
Problem is that I can't upload any part of rom because phone is now S-ON. I'am getting signature error.
Flashed RUU: 42) [xda-ftp] [4shared] 3.54.631.3 Rogers Canada + [SAPPIMG.ZIP format]
ADB is no longer possible. Only FASTBOOT and RUU USB.
See attched photo for fastboot details.
Thanks in advance.
Click to expand...
Click to collapse
I went through a similar problem. My 32A was in the same state except for the radio; I had no system installed, S-ON, RUU mode, and a radio/spl mismatch. It looks like you at least have a proper radio/spl combo.
Before we do anything else, try flashing the RUU again. Were you using the ZIP file or the EXE? Use the ZIP, at least you won't have to load up that crappy HTC interface.
If the RUU fails again, see if you can find the log file from the installation. It'll be on your system's drive, probably in "C:\ruu_log" or something like that. It can tell us what error it found.
In my case, we (mumilover and I) had to upgrade HBOOT and "sort of unlock it" using HTCDEV's method. Then we were able to install a custom recovery, and then everything got very easy.
Let's see if the simple things work before we have to do the harder things
Thnak you very much for hint with HTCDEV. Now I have at least fastboot
RUU image allways fail at signature error. OI have tried three of them. Same error.
I have run RUU under fastboot usb.
Also I can't flash recovery image even I have successfully unlocked hboot with htcdev.
C:\ADB>fastboot flash recovery recovery-clockwork-2.5.0.7-magic.img
sending 'recovery' (2642 KB)... OKAY [ 0.923s]
writing 'recovery'... FAILED (remote: not allow)
finished. total time: 0.926s
Any other idea ?
pero256 said:
Thnak you very much for hint with HTCDEV. Now I have at least fastboot
RUU image allways fail at signature error. OI have tried three of them. Same error.
I have run RUU under fastboot usb.
Also I can't flash recovery image even I have successfully unlocked hboot with htcdev.
C:\ADB>fastboot flash recovery recovery-clockwork-2.5.0.7-magic.img
sending 'recovery' (2642 KB)... OKAY [ 0.923s]
writing 'recovery'... FAILED (remote: not allow)
finished. total time: 0.926s
Any other idea ?
Click to expand...
Click to collapse
Could you give me the new details of the fastboot page? Your HBOOT version will have changed, and it will say "UNLOCKED" or "RELOCKED" at the top and S-ON. If it says "RELOCKED", try running the HTCDEV unlock command from fastboot again (you should still have the Unlock_code.bin file in your email) and then reboot.
Let's see how that goes.
DasBub said:
Could you give me the new details of the fastboot page? Your HBOOT version will have changed, and it will say "UNLOCKED" or "RELOCKED" at the top and S-ON. If it says "RELOCKED", try running the HTCDEV unlock command from fastboot again (you should still have the Unlock_code.bin file in your email) and then reboot.
Let's see how that goes.
Click to expand...
Click to collapse
I have attached Fastboot details.Status is: UNLOCKED.
But when I try to flash recovery I get an error message which I already wrote.
I think it is because of S-ON which is checking signature.
pero256 said:
I have attached Fastboot details.Status is: UNLOCKED.
But when I try to flash recovery I get an error message which I already wrote.
I think it is because of S-ON which is checking signature.
Click to expand...
Click to collapse
Sounds reasonable. I wish I kept better notes That way I wouldn't have to re-learn things every time.
I just want to make sure I understand the timeline of events:
You said you tried to flash an RUU over an existing custom ROM install, right?
What was the configuration of your phone before you tried the RUU and ran into trouble? If you were running a custom ROM, did you have a magic SPL or a custom recovery in order to install that custom ROM?
Anyway, on to the work:
Let's see if we can get an RUU to work now.
Go to the command prompt and run "fastboot getvar version-main" and let us know what it is, for future reference.
Once we know that, we can find a higher-numbered RUU from this list of Official RUUs.
I think I ended up using BrightStar Brazil, but anything higher than your phone's reported main version should work.
Have you made a goldcard? If you try to use an RUU and it complains about your CID, this will help.
Before you try to install an RUU, you will need to relock the bootloader using "fastboot oem lock" (you'll be able to unlock it again using the Unlock_token.bin)
Place the SAPPIMG.zip of the RUU in the root folder of your SD card and reboot into HBOOT (or reboot to fastboot and select HBOOT).
After a few seconds it should start scanning your SD card and then it will try to use the SAPPIMG.
Let us know.
Yes I had custom rom with s-off. But can't remeber which version.
Than I tried to install RUU: 42) [xda-ftp] [4shared] 3.54.631.3 Rogers Canada + [SAPPIMG.ZIP format]
Than I get error while flashing.
Strange thing is that I get this now:
C:\ADB>fastboot getvar version-main
version-main: 3.54.0.0
finished. total time: 0.001s
So it seems that I have lower version than I tried to install
I didn't try to use goldcard for now.
I have created Gold Card using this link: http://theunlockr.com/2010/03/10/how-to-create-a-goldcard/
I have to use another HTC phone (Wildfire) to get CID from HTC Magic SD card
I have tried to put 3.54.631.3 Rogers Canada rom as SAPPIMG.zip but HBOOT claims that there is no image.
I get: Loading...(SAPPIMG.zip) No image!
I forget to say that I have set HBOOT to RELOCKED state before using GOLD CARD and SAPPIMG.zip
pero256 said:
I forget to say that I have set HBOOT to RELOCKED state before using GOLD CARD and SAPPIMG.zip
Click to expand...
Click to collapse
1) Check the filename. Make sure it is "SAPPIMG.zip" exactly, with SAPPIMG in capital letters.
2) Run these fastboot commands and then switch back to HBOOT mode.
Code:
fastboot oem enableqxdm 0
fastboot oem eraseconfig
This procedure has fixed SD card problems in the past.
3) Check the SD card using a computer or another phone to be sure that the file is on the card. I've had Windows unmount the card improperly a few times, so that's a possibility.
4) Compare a checksum of the original ZIP file to the checksum of the ZIP on your SD card. I use 7-Zip to get the checksum, but there are other ways.
5) You can download another copy of the SAPPIMG.zip file.
It also helps to wave a dead chicken over the phone as an offering to the phone god.
Unfortuntly can't get goldcard to work.
I have used 3 different SD card.
1. 2GB
2. 2GB
3. 1GB
Non of them works.
Also everything is fine in the process of creating them.
Problem is about loading to phone SAPPIMG.zip of 3.54.631.3 Rogers Canada rom.
Phone starts to Checking..(SAPPIMG.zip) and then after some period of time stops and waits to press:
1. (back) FastBoot Mode
2. (send) Simlock
I have try to start another flash but get the same result.
So it seems that the gold card is not working as it should because phone is still checking uploaded rom image.
Is there some SD card that works 100% ?
pero256 said:
你好，
任何人都可以建议如何在通过自定义 rom 刷新 Rogers RUU 官方后恢复 HTC 魔法。
ROM 更新在更新系统分区时中止。
问题是我无法上传 rom 的任何部分，因为手机现在是 S-ON。我收到签名错误。
闪烁的 RUU：42) [xda-ftp] [4shared] 3.54.631.3 Rogers Canada + [SAPPIMG.ZIP 格式]
亚行不再可能。只有 FASTBOOT 和 RUU USB。
有关快速启动的详细信息，请参阅随附的照片。
提前致谢。
Click to expand...
Click to collapse
You use what method to let it enter FASTBOOT