Database Users

[How-To] Fix perfected SPL (fastboot remote: not allow)

The following instructions :
will void all warranties of your phone!
will erase all your userdata!
will change your current ROM/SPL!
will change your current splash screen!
could brick your phone!
Proceed at your own risk!
The "trick" in fixing a perfected SPL is to fastboot a goldcard which contains a sappimg.nbh/zip that has :
an non-perfected SPL (preferably an engineerings SPL).
a ROM with a version that is HIGHER than your current ROM version.
Steps
Create a Goldcard.
Copy the required sappimg.nbh/zip to the Goldcard.
Boot your phone while holding the VOLUME-DOWN key.
Press the ACTION KEY (=trackball) to start the update.
Wait until the update completes and press the ACTION KEY (=trackball) to reboot your phone.
(Upgrade to the rooted ROM of your choice).
NBH/ZIP
ROM v2.53.707.2 (Engineerings SPL v1.33.2010) - MD5 : F9674D19BE5F949D0D9DC99714D210E3
ROM v2.16.707.3 (NON-Perfected stock SPL v1.33.0009) - MD5 : DC391E4A3FC57861D7197C151176ED96
ROM v2.16.151.1 (NON-Perfected stock SPL v1.33.0009) - MD5 : ADA4924293EFF619B05BB397446F862D
Credits
Aug-14-2009 : v2.53.707.2 (ekindangen)
Aug-14-2009 : v2.16.707.3 (ekindangen)
Aug-12-1009 : v2.16.151.1
Please inform us in case you have found a higher-version NBH/ZIP/RUU with a non-perfected SPL!

Thanks for the neat instructions, will this work for any HTC magic phone with Perfected SPL ,i have a HTC magic Indian version
SPL: 1.33.0010
Build number: 2.16.720.2
Thanks waiting eagerly for you answer

spatali said:
Thanks for the neat instructions, will this work for any HTC magic phone with Perfected SPL ,i have a HTC magic Indian version
SPL: 1.33.0010
Build number: 2.16.720.2
Thanks waiting eagerly for you answer
Click to expand...
Click to collapse
Yes, download v2.53.707.2, put it on a goldcard and flash

Amon_RA said:
Yes, download v2.53.707.2, put it on a goldcard and flash
Click to expand...
Click to collapse
Awesome thanks alot Amon_RA, freedommmm finalllly!

spatali said:
Awesome thanks alot Amon_RA, freedommmm finalllly!
Click to expand...
Click to collapse
Don't thank me, thank ekindangen for the ROM !

Amon_RA said:
Don't thank me, thank ekindangen for the ROM !
Click to expand...
Click to collapse
THANKS ekindangen you rock! , btw what are the chances of bricking of phone ? , just worried abit, noobie here

Amon_RA:
i successfully created a goldcard and i flashed my MyTouch too, but i kept getting "failed" when i tried to fastboot the recovery image. This was using the original sappimg.zip provided in the 'how-to' instructions.
Should i retry with one of the higher NBH/ZIPs?

Does this work with 1.33.2006 as well

funfobia said:
Does this work with 1.33.2006 as well
Click to expand...
Click to collapse
1.33.2006 is an engineerings SPL... it is already "non-perfected"

So this would work for the mytouch 1.33.0006?

HMmm it dint not ask me for the upgrade, i successful created the goldcard and put in sappimg.zip file it in, booted holding power+volume down, it doesnt ask me for upgradation

spatali said:
HMmm it dint not ask me for the upgrade, i successful created the goldcard and put in sappimg.zip file it in, booted holding power+volume down, it doesnt ask me for upgradation
Click to expand...
Click to collapse
Try it with a normal SD card, if that one picks up the sappimg.zip it means that your goldcard is corrupted/bad.

Amon_RA said:
Try it with a normal SD card, if that one picks up the sappimg.zip it means that your goldcard is corrupted/bad.
Click to expand...
Click to collapse
Oh yeah thanks it picked it up , i have a sandisk and a some card by the name kingmax, so both these wont work ? which brand is preferrable ?

Flashing done, i have a s-off spl now \0/, how do i load a custom rom now?! can you please point me to the right direction. A ROM with all google apps

ok so this isnt for 1.33.0006????? never got answered besides its an engineering spl. this means?

can anybody tell if now a hero rom could be put on this htc magic?

This method is only for 32A?
Or both 32A and 32B ？

this is great!
Glad I waited now for a better method for doing this. I almost did the goldcard with the other rom that was originally posted. This way I get a new ROM with no issues I can see. Much better solution. Thanks everyone. Today I buy the sd cards and a card reader here in Chennai and go play with the solution and new rom I've chosen. I have a second magic phone that was bought for me I flashed earlier with a Hero rom and I really like it. The first phone was bought by my company for use; but after seeing what was not on it, was really disappointed with Airtel.
Thanks everyone! This is the solution worth waiting for.

Man why does all custom roms get stuck at loading screen ?. I tried using RAv1.2.0 in Fastboot mode(without actually flashing it to phone) and then i use the "update from zip" option from it to load the new custom rom. it completes installation. Reboots. And then it gets stuck at second HTC Android Logo!!! tried two Roms
Amon Ra's RAv1.1.0H-signed-update
JACxHERO variant Hero ROM
What am i doing wrong? Is there a proper tutorial for flash rom properly. Do i need to flash my SPL to Engineering-SPL-HBOOT-1.33.2005-signed ?

Got it all done
The whole goldcard thing took me a few tries. Discovered that the sandisk that shipped with my Airtel India Magic would not work so got a few new cards and a card reader. I had to redo the goldcard a few times and I had gotten the whole cid thing wrong somehow so I redid that and got a new goldcard.img. I had to be a bit patient holding down the action key also.
Finally, was able to apply the non perfected engineering over the airtel and then this very nice rom:
http://forum.xda-developers.com/showthread.php?t=538645
Very nice seeing the Android in Blue letters when I rebooted the phone, having root on the phone, etc. Seeing the Android Market on the phone for the first time makes it all nicer. I'm glad I waited to get a way that allows me to try different stuff. Thanks everyone.
BTW, did all this on Ubuntu Linux. Only windows involved was the QMAT program running in Wine. Yay!

[Solved]HTC branded 32A semi-bricked (RUU mode only)

When I'm booting my Magic I'm getting into RUU mode. Not booting into recovery, not booting normal, and not booting to fastboot.
I could've flashed a new radio and hboot, but my SPL is perfected 1.33.0010. When I'm trying to flash an official update, I'm getting to the updating screen, the phone is rebooting into bootloader, but I'm getting this error:
[140]: bootloader version error
Click to expand...
Click to collapse
Any way to unbrick my phone?
Solution: Just applied a official RUU update with newer HBOOT.

Can you get in recovery mod?
hit me on gtalk

stian230 said:
Can you get in recovery mod?
hit me on gtalk
Click to expand...
Click to collapse
No.
Every combination boots to hboot. And added.
Edit: Still no luck unbricking. My phone is starting in bootloader, says RUU. Maybe that's not hboot. Not sure though. Fastboot finds my phone, but as I have perfect SPL, I can't flash anything.

You need a goldcard to put and engineered spl on it (my guess).

ruimoura said:
You need a goldcard to put and engineered spl on it (my guess).
Click to expand...
Click to collapse
The updating from sappimg wouldn't start in RUU mode. I solved it by applying the newest magic update. Now having perfect SPL, but maybe that's the best. For not getting temped risking my phone again.
Thanks for your answer anyway.

sindrefyrn said:
The updating from sappimg wouldn't start in RUU mode. I solved it by applying the newest magic update. Now having perfect SPL, but maybe that's the best. For not getting temped risking my phone again.
Thanks for your answer anyway.
Click to expand...
Click to collapse
Anyway, you got your Magic back, that's nice.
Cheers.

HBOOT .77 vs .79 How do I get .77 for OTA?

I followed the instructions here
http ://forum.xda-developers.com/showthread.php?t=766361
with no issues however, in step 3, after rebooting it looks like I am still rooted and CWM is still installed. It didnt flash my device but only updated the HBOOT. But my HBOOT still reads .79. SHouldnt it be .77 to be ready for the OTA? And all of my apps + settings are still intact. I am still rooted. Is this what its supposed to do? I thought it was supposed to flash the recov img.
And I verified that I get the red warning triangle.
My maine concern is the HBOOT: my HBOOT ver is .79 Shouldnt it be .77 to get the OTA update?
If so, how do I fix this?
Thanks
IncredibleC XC SHIP S-OFF
HBOOT-0.79.0000
MICROP-0417
TOUCH PANEL-ATMEL224_16ab
RADIO-1.00.03.04.06

You will be able to get the OTA fine with HBOOT .79

Berzerker7 said:
You will be able to get the OTA fine with HBOOT .79
Click to expand...
Click to collapse
Thanks for the quick reply. Id like to read up on that more. Is there a link that discusses this in further detail?
Also, whats the difference between .77 and .79?
Thanks again.

metalmachine said:
Thanks for the quick reply. Id like to read up on that more. Is there a link that discusses this in further detail?
Also, whats the difference between .77 and .79?
Thanks again.
Click to expand...
Click to collapse
There's not enough of a difference initially to have anyone look into the differences, so no one really knows.

metalmachine said:
I followed the instructions here
http ://forum.xda-developers.com/showthread.php?t=766361
with no issues however, in step 3, after rebooting it looks like I am still rooted and CWM is still installed. It didnt flash my device but only updated the HBOOT. But my HBOOT still reads .79. SHouldnt it be .77 to be ready for the OTA? And all of my apps + settings are still intact. I am still rooted. Is this what its supposed to do? I thought it was supposed to flash the recov img.
And I verified that I get the red warning triangle.
My maine concern is the HBOOT: my HBOOT ver is .79 Shouldnt it be .77 to get the OTA update?
If so, how do I fix this?
Thanks
IncredibleC XC SHIP S-OFF
HBOOT-0.79.0000
MICROP-0417
TOUCH PANEL-ATMEL224_16ab
RADIO-1.00.03.04.06
Click to expand...
Click to collapse
---If when you are going into recovery and you get the red triangle, and not clockworkmod recovery anymore, that should mean that you have stock recovery.
and your radio is stock.
Berzerker7 said:
You will be able to get the OTA fine with HBOOT .79
Click to expand...
Click to collapse
Thank you for this answer this was something I really needed to know as well, I did the same as the OP, was rooted, and downgraded with S-OFF hboot .79 and stock everything waiting for 2.2
Also can you help me out with this, I have all this but when I run S-ON and then tried to run the PB13IMG.zip to get the stock recovery back now, it says update failed main version is older.

You need to run that zip with S-OFF, it's unsigned, so it won't let you run it if it's not signed.

Berzerker7 said:
You need to run that zip with S-OFF, it's unsigned, so it won't let you run it if it's not signed.
Click to expand...
Click to collapse
I understand, thank you. How would I be able to do S-ON and stock recovery then for warranty purposes? I was unsuccessful finding this and would be highly appreciative if you could help me out here

BlazeD OnE said:
I understand, thank you. How would I be able to do S-ON and stock recovery then for warranty purposes? I was unsuccessful finding this and would be highly appreciative if you could help me out here
Click to expand...
Click to collapse
forum.xda-developers.com/showthread.php?t=752163

jsprake1 said:
forum.xda-developers.com/showthread.php?t=752163
Click to expand...
Click to collapse
I dont see how that helps?
thank you though.

RUU back to stock.
install cwm via PB31IMG.zip
S-ON.
RUU back to stock again.

Berzerker7 said:
RUU back to stock.
install cwm via PB31IMG.zip
S-ON.
RUU back to stock again.
Click to expand...
Click to collapse
Thanks, this helped me out.

HBOOT 2.02 S-OFF Finally!

http://img27.imageshack.us/img27/2034/img20101102213315.jpg
Here is the picture of the 2.02 S-OFFed
It has a custom recovery on it now. More info to come.
If this has been figured out already sorry again!
!!!UPDATE!!!
Whats Completed,
S-OFF
Custom Recovery
ENG Bootloader.
HBOOT 2.02.0000 is completely cracked.

Advantage of hboot 2.02 > 0.76?

[email protected] said:
Advantage of hboot 2.02 > 0.76?
Click to expand...
Click to collapse
THIS !!!!!!!! >

2.02 is non engineering hboot... so i would think there is not much point... but than again... i think probably 99% of us dont even touch those options.

Uh nothing that i know of, except that HBOOT 2.02 that i have found will NOT downgrade to .76 as they patched it, I tried the eng-PC36IMG.zip, unrevoked etc. They do not root, nand unlock and install recovery.

eng-PC36IMG.zip skips installing the bootloader wich is the HBOOT.
Unrevoked Errors out and will not get past the HBOOT and throws a error saying lost connection.

So far can not downgrade the stupid hboot. This is what happens.
http://img215.imageshack.us/img215/1126/img20101102215418.jpg

amoamare said:
http://img27.imageshack.us/img27/2034/img20101102213315.jpg
Here is the picture of the 2.02 S-OFFed
It has a custom recovery on it now. More info to come.
If this has been figured out already sorry again!
Click to expand...
Click to collapse
How did you get s off? Ive been trying everything for the past week

You cant downgrade as of yet to HBoot 76.
You can get S-Offed as of now that lets you install a custom recovery etc.

amoamare said:
You cant downgrade as of yet to HBoot 76.
You can get S-Offed as of now that lets you install a custom recovery etc.
Click to expand...
Click to collapse
How did you do it?

Hex edit? Cough cough.

Like i said, more info will be released in a bit. I'm waiting for a response from someone.

kenny21 said:
How did you get s off? Ive been trying everything for the past week
Click to expand...
Click to collapse
If you have s-off then you should be able to make a PC36IMG.zip out of one of these hboots found here http://forum.xda-developers.com/showthread.php?t=801568

It will flash the PC36IMG.zip just fine, but its bypassing the boot everytime.

amoamare said:
It will flash the PC36IMG.zip just fine, but its bypassing the boot everytime.
Click to expand...
Click to collapse
so, will this fix let us root the phone and load recovery and flash roms again? im so tired of being stock lol.

Yes, right now i have ClockworkMod recovery on it.
You can flash custom roms to the phone.
Only thing is i want to put the eng0.79 bootloader on there

amoamare said:
Yes, right now i have ClockworkMod recovery on it.
You can flash custom roms to the phone.
Only thing is i want to put the eng0.79 bootloader on there
Click to expand...
Click to collapse
could we have an ETA on your fix? i would love to try it before i go to sleep ;(

Like i said just waiting on a message from someone and will post from there.

amoamare said:
Like i said just waiting on a message from someone and will post from there.
Click to expand...
Click to collapse
Thanks for the effort. I bought an Evo today with 2.02 Hboot on it. I was afraid to be stuck with stock for a long time.

Ok 2.02 has been successfully cracked all the way.
http://d.imagehost.org/0355/IMG_20101102_233241.jpg
ENG bootloader has been loaded on. All fastboot cmds are restored. Sweet.

Having trouble installing clockwork recovery

My phone was made s-off via xtc clip.
It's rooted with superoneclick (couldn't get unrevoked to work).
ROM Manager is in the superuser list and has been granted root access.
In ROM Manager I click "flash clockworkmod recovery", select "HTC Buzz (Wildfire)" and it says "successfully downloaded clockworkmod recovery".
But every time I click "reboot into recovery" I just get a black screen with a phone in the middle and a red triangle.
I then have to remove the battery to get the phone back on.
Any ideas folks ?

I read somewhere that the current version of ROM manager doesn't work with Android 2.2.
Is this right ?
I tried an older version and it appeared to try and install clockwork recovery for a few seconds then I got a black screen with a phone and a red question mark.

try flashing custom recovery with PC49IMG process. get the file from here.
http://forum.xda-developers.com/showpost.php?p=12188132&postcount=15

and one more thing, if u get issues with flashing custom roms then try to use different version of recovery.
issues like amend scripting.......

Thanks for the reply.
I tried putting the PC49IMG.zip file in the root of the sd card but when I go into HBOOT it says ....
CID incorrect !
Update Fail !
Do I need to do a factory reset ?

scobodon said:
Thanks for the reply.
I tried putting the PC49IMG.zip file in the root of the sd card but when I go into HBOOT it says ....
CID incorrect !
Update Fail !
Do I need to do a factory reset ?
Click to expand...
Click to collapse
CID error after making S-OFF huh ?
U do have another option. Can try an official RUU of ur region with the radio Radio_13.53.55.24H_3.35.19.25
this gives u hboot 0.80 . Then u can root the phone with unrevoked (use version 3.2).

Would this be ok ?
http://rom.tat.tw/wildfire/extracte...19.25_release_151892_signed_101410_003737.zip

scobodon said:
Would this be ok ?
http://rom.tat.tw/wildfire/extracte...19.25_release_151892_signed_101410_003737.zip
Click to expand...
Click to collapse
The one specific for ur region (if it is there) is more preferable. However it will also be ok.
And better get it from shipped roms website if u havent started the download yet.
here: http://www.shipped-roms.org/shipped/Buzz/

Thanks for the list.
So, is it just a case of running the exe with my phone connected ?

scobodon said:
Thanks for the list.
So, is it just a case of running the exe with my phone connected ?
Click to expand...
Click to collapse
Yes certainly. Connect the phone under charge mode.

No luck.
Got a "customer id error" in the Windows program.

scobodon said:
No luck.
Got a "customer id error" in the Windows program.
Click to expand...
Click to collapse
Sorry, cant go further. That might be due to region. I think there might be ur region RUU in that website there. Don't know completely to solve cid errors. Probably a gold card might be the solution.
But there are solutions for cid errors. Go with this thread (same one as earlier), it might help u. http://forum.xda-developers.com/showthread.php?t=993102

Thanks again for all your help so far, much appreciated.
I found a multi region RUU with the same kernel as the one I'm on.
Do you think flashing this will allow me to then flash one of the older RUUs ?
Also, if I do this will it make my phone s-on again ?

scobodon said:
Thanks again for all your help so far, much appreciated.
I found a multi region RUU with the same kernel as the one I'm on.
Do you think flashing this will allow me to then flash one of the older RUUs ?
Also, if I do this will it make my phone s-on again ?
Click to expand...
Click to collapse
When ur phone has S-OFF (by xtc clip) u can flash any wildfire RUU of ur region (i mean downgrading hboot is also possible). Yes u can flash older RUU also, that's what u attempted to do with that WWE ruu.
Once u do S-OFF by xtc clip, then u can't get back to S-ON in any way. XTC clip directly wipes off the secure flag in the radio NVRAM. So, AFAIK, there is no way for u (by xtc clip) to get back to S-ON even when u flash an updated hboot.
But alpharev2 (not yet released for wildfire) will patch the hboot to make it think that the secure flag is off. So, if done by alpharev S-OFF is not permanent. When done S-OFF with alpharev, then if u flash an updated hboot, the phone returns to S-ON. This is not the case with u.

Tried the RUU with the same kernel that's on my phone but got the "customer ID error" again.
I'm starting to think something went wrong when they used the xtc clip.
When I get the red triangle in HBOOT, if I press vol up + power I get the message "failed to verify signature".
I thought having s-off was supposed to bypass the signature checks

scobodon said:
Tried the RUU with the same kernel that's on my phone but got the "customer ID error" again.
I'm starting to think something went wrong when they used the xtc clip.
When I get the red triangle in HBOOT, if I press vol up + power I get the message "failed to verify signature".
I thought having s-off was supposed to bypass the signature checks
Click to expand...
Click to collapse
AFAIK, after S-OFF it should skip the signature check. That is how we can flash the custom recovery through PC49IMG process.
There is a full guide of XTC clip rooting in the development section. If u think something went wrong when they used xtc clip, u might get an answer there. link: http://forum.xda-developers.com/showthread.php?t=1057524
And also one more link to what we can do after S-OFF here.
link: http://forum.xda-developers.com/showpost.php?p=13025129&postcount=3
In that try the fastboot flash recovery command. May be a hope

Woo hoo, success !!
I made a goldcard and the RUU installed fine.
I now have Android 2.1 and HBOOT 0.80.0007.
I guess the goldcard is where I was going wrong.
Edit : Just got unrevoked to work first time too.

And now I've got CM7 installed !!!
A very happy bunny.
Many thanks again for the help and advice.
Wouldn't have got it working without this forum.

That's fine.
Sent from my HTC Wildfire using XDA App