Database Users

WTF is an SPL?!

LOL I have this:
SAPPHIRE PVT 32B SHIP S-ON G
HBOOT-1.33.0006 (SAPP30000)
CPLD-10
Radio-2.22.19.261
May 27 2009, 19:06:41
Click to expand...
Click to collapse
I think it's a perfected SPL but who knows.. Satan?
I want to update my lame ass SPL to one of these bad boys:
Haykuro's "Death" SPL
OR
Magic SPL HBOOT Collection
From these Awesome Website and Also Awesome, I've narrowed down the steps to Victory!
Here's what my Brain thinks:
1.) Download an SPL (i.e Haykuro's "Death" SPL).
2.) Transfer to SD Card.
3.) Go into Recovery Mode (Amon_Ra-v1.5.2G)
4.) Scroll down to "Flash zip from sdcard".
5.) Flash Haykuro's "Death" SPL.
6.) Reboot system now and wait for it to enter Recovery Mode again.
8.) Check for new SPL, and you're done?
My Q's:
1.) Are my steps horribly wrong and could possibly brick my phone?
2.) No wiping required?
3.) If it gets stuck on Formatting CACHE for a long long long time..what to do?

your rooted
SAPPHIRE PVT 32B SHIP S-ON G
so i doubt you can get to recovery

sitimber said:
your rooted
SAPPHIRE PVT 32B SHIP S-ON G
so i doubt you can get to recovery
Click to expand...
Click to collapse
Yes, I know I'm rooted. I just want to update my spl to the latest. And I can definitely get to recovery mode, was just flashing a couple of roms earlier.
Give me some help, bro!

i am also confused. I have a mytouch 3g with a "perfect" (1.33.0006)SPL... what does that mean? what cant I do with this SPL that I can do with a danger SPL? I already have CM Recovery 1.4 + latest Cyanogen Mod rom...

Man, if you don't know what an SPL is, then you're "so 2000 and late." Haha sorry, I had to man

k but instead of sounding smart cause you know something us people who are late dont... how bout explaining?

kareeem said:
Man, if you don't know what an SPL is, then you're "so 2000 and late." Haha sorry, I had to man
Click to expand...
Click to collapse
Hahahaha and that beat goes zoooom zoooom zooom
kareeem stop making jokes help us out, LOL
What's your current SPL, and how did you install it?

melterx12 said:
k but instead of sounding smart cause you know something us people who are late dont... how bout explaining?
Click to expand...
Click to collapse
I only said that line because it was the only one i could find that fit with the lyrics I don't even have an Android device so there's your answer.

this is so frustrating ive googled this for almost an hour and I still cant find anything that explains exactly what a non perfect SPL does and how to go about flashing it and which one to flash!

melterx12 said:
this is so frustrating ive googled this for almost an hour and I still cant find anything that explains exactly what a non perfect SPL does and how to go about flashing it and which one to flash!
Click to expand...
Click to collapse
Haha yeah same here bro.
Hope someone can enlighten us about how they upgraded their spl.

All I know is that its short for "splash image" and has something to do with the boot up process. My dad is a programer (during a coversation about android and linux) explained the SPL to me during Fourth of July but I was a little too drunk to care and pay attention.

well actually SPL stands for Second Program Loader. That much i know for sure. I also know that its the equivalent of a bootloader. what i DONT know and neither does anyone else by the looks of it (lol), is what the difference is between a perfect SPL and a Danger SPL, and how to go about flashing a danger SPL for mytouch 3g? and which danger SPL is the best?

BoomBoomPOW said:
LOL I have this:
I think it's a perfected SPL but who knows.. Satan?
I want to update my lame ass SPL to one of these bad boys:
Haykuro's "Death" SPL
OR
Magic SPL HBOOT Collection
From these Awesome Website and Also Awesome, I've narrowed down the steps to Victory!
Here's what my Brain thinks:
1.) Download an SPL (i.e Haykuro's "Death" SPL).
2.) Transfer to SD Card.
3.) Go into Recovery Mode (Amon_Ra-v1.5.2G)
4.) Scroll down to "Flash zip from sdcard".
5.) Flash Haykuro's "Death" SPL.
6.) Reboot system now and wait for it to enter Recovery Mode again.
8.) Check for new SPL, and you're done?
My Q's:
1.) Are my steps horribly wrong and could possibly brick my phone?
2.) No wiping required?
3.) If it gets stuck on Formatting CACHE for a long long long time..what to do?
Click to expand...
Click to collapse
Some people can be d!cks in this forum. Your steps are right from all that I know. Changing your SPL is an at your own risk sort of venture, though. Haven't even had the balls to do it myself yet. But, first, do try to use the search function in these forums. Pretty new myself but have good luck finding the resources I need through search. Lastly, here are a couple of links that have helped my in regard to SPL research. The first is more general and worth reading through the comments. The second one specifically relates to you...
http://forum.xda-developers.com/showthread.php?t=548218
http://forum.xda-developers.com/showthread.php?t=570659&highlight=hboot
Good Luck. Hope it helps.

melterx12 said:
this is so frustrating ive googled this for almost an hour and I still cant find anything that explains exactly what a non perfect SPL does
Click to expand...
Click to collapse
your google-fu is weak old man!!
http://wiki.xda-developers.com/index.php?pagename=HTC_Sapphire_Hacking#sec01
"Perfect" SPL Revisions (that prevent us hacking)
Currently HBOOT-1.33.0006 and HBOOT-1.33.0010 are the known 'Perfect SPL' revisions on the Sapphire handsets that we know of.
It is not possible to fastboot a ROM using these and you need to wait until someone has hacked it.
Edit (12 Aug 2009) : Now you can! Refer to How-To - Fix that perfected SPL - Root the T-Mobile myTouch 3G
So what is an SPL anyway? What does it do?
The SPL, or Second Program Loader, is essentially the Android bootloader. It's job is more than just loading the Android OS - it also offers several other boot options, including Recovery mode, Fastboot, and HBOOT modes, and ultimately it's the SPL that allows manipulation of the flash nand on your device. Part of the SPL's job is to ensure that the data flashed to the device is correct. Most of the current shipping SPLs (apart from the "Perfect SPL's) let us flash a complete ROM image, but don't let us flash a recovery rom or boot image as it checks the verification signature. Haykuro has modified the SPL's available to remove this check and this is what the Engineering SPL's available offer. As the SPL is so crucial to the handset though, you have to be very careful when flashing it as if it's updated incorrectly then you may be incapable of restoring it without specialised hardware and knowledge. You essentially have a very expensive brick
Click to expand...
Click to collapse

looktall said:
your google-fu is weak old man!!
Click to expand...
Click to collapse
Off topic, but thanks for posting. I wish more people were this patience and helpful. Kudos. Especially on the comedy inoffensive flame.

ive already seen that article, but it still does not explain what i want to know. I already know what an SPL does, but what does a Danger SPL do that my perfect SPL cant. is it worth flashing my SPL? which one should i flash and how? I cant find answers to these questions.

ok ive just foudn a bit of info saying that a danger SPL allows you to flash hero ROMS onto your mytouch.. but WTF??? Ive already flashed 2 different Hero ROMS onto my mytouch with no problems and I have a Perfect SPL. the only reason i didnt keep em was cause the device was slow! So wtf is going on with my phone? what am I missing here rofl

The "Danger" (or "Death") SPL is Haykuro's 1.33.2005 and there is only one. It changed the nand partitions sizes (or sth like that) on the G1 and that was why it is required to run Hero ROMs on it. It's not required to run Hero ROMs on the Magic though. What you're talking about are "Engineering" SPLs and the main difference with stock SPL is that, AFAIK, they bypass security checks to allow the flashing of unsigned update packages. Also, I think only Engineering and non-perfected SPLs allow the use of the fastboot protocol, the possibility to flash recovery images directly and the use of Nandroid to make backups.
To me it's all about unlocking everything but I could have lived with my stock non-perfected SPL as I could already do everything I wanted.
Signature checking is not necessary a bad thing. Perfected SPL is a different story as it really reduces you possibilities but I know there are workarounds.

swissp said:
The "Danger" (or "Death") SPL is Haykuro's 1.33.2005 and there is only one. It changed the nand partitions sizes (or sth like that) on the G1 and that was why it is required to run Hero ROMs on it. It's not required to run Hero ROMs on the Magic though. What you're talking about are "Engineering" SPLs and the main difference with stock SPL is that, AFAIK, they bypass security checks to allow the flashing of unsigned update packages. Also, I think only Engineering and non-perfected SPLs allow the use of the fastboot protocol, the possibility to flash recovery images directly and the use of Nandroid to make backups.
To me it's all about unlocking everything but I could have lived with my stock non-perfected SPL as I could already do everything I wanted.
Signature checking is not necessary a bad thing. Perfected SPL is a different story as it really reduces you possibilities but I know there are workarounds.
Click to expand...
Click to collapse
Very informative. I was able to perform a Nandroid backup successfully while still on the "perfected SPL" so what's up with that? I guest I'll just stick with my perfected stock SPL for now, until I find a really great rom I want to flash but requires a non-perfected/eng spl.

BoomBoomPOW said:
Very informative. I was able to perform a Nandroid backup successfully while still on the "perfected SPL" so what's up with that? I guest I'll just stick with my perfected stock SPL for now, until I find a really great rom I want to flash but requires a non-perfected/eng spl.
Click to expand...
Click to collapse
That's why I said "I think"... fortunately I've never had a perfected SPL and I can only repeat what others have been saying about it. Can you restore the backup too?
As you'd already noticed, information on the subject is quite vague but you are right anyway, the only reason to change SPL should be if the ROM you want to install requires it ;-)

Downgrading from DangerSPL?

Now that Firerat has figured out how to easily fit stuff on G1 and T-mobile MT3G phones without DangerSPL, I'm thinking of downgrading to the base engineering SPL. I have a few questions though, since I don't feel like bricking my phone.
First off, fastboot info:
SAPPHIRE PVT 32B
HBOOT - 1.33.2005 (Danger, I believe)
Radio - 2.22.23.02
First off, where would I find a non-danger engineering SPL? Are the SPL's in this thread the ones I should be looking for? http://forum.xda-developers.com/showthread.php?t=529019
Also, are there any benefits of sticking with Danger SPL (other than extra 30 megs system) and since it's now easier to fit this stuff on non Danger, will there be more benefits in reverting back to the original Engineer SPL?
In addition, if I DO decide to flash back to a non-danger SPL, would I have to use recovery or fastboot? I'm assuming they'd be a match, but I'd like to do whichever way is more safe.
Edit: Oh crap, just noticed I posted this in the wrong section. I own a MT3G, but I installed danger way back when they first rooted it when following a tutorial. Should I be looking at a different engineering spl?
Sorry for all of the stupid questions.

DangerSPL is not required for the MT3G in the first place, so I'm not sure why you installed it in the first place.
From what I know, there is no downside to being on Danger, so I don see why downgrading to an engineering spl is necessary
If you do decide to do it, do it through recovery not fastboot

PurpleFries said:
DangerSPL is not required for the MT3G in the first place, so I'm not sure why you installed it in the first place.
From what I know, there is no downside to being on Danger, so I don see why downgrading to an engineering spl is necessary
If you do decide to do it, do it through recovery not fastboot
Click to expand...
Click to collapse
You got it the wrong way bud.
Read the Brick confirmation thread by lbcoder.
flashing radios and recoveries (incompatible ones) through recovery is how bricks happen.

cal3thousand said:
You got it the wrong way bud.
Read the Brick confirmation thread by lbcoder.
flashing radios and recoveries (incompatible ones) through recovery is how bricks happen.
Click to expand...
Click to collapse
Probably, but I've never had a bad experience flashing an SPL through recovery. Never once used fastboot. I very rarely actually can. Also, you run the risk of a brick ANY TIME you flash one. As for OP, just flash a new Engineering SPL. There's no real brick with those. I mean, yes you CAN, but just make sure it's not corrupted when you download it new SPL. Check MD5 Sum. There's no radio-spl brick with those. (As far as I know.) And, yes, those are the SPLs you want if you have a myTouch.

PurpleFries said:
DangerSPL is not required for the MT3G in the first place, so I'm not sure why you installed it in the first place.
Click to expand...
Click to collapse
I don't know. I followed the tutorial word by word when it was first figured out how to root the MT3G. I literally had that handset for a week before anyone had done anything with it.
Thanks for the responses.
Edit: Bit the bullet and did it. No problems. Made sure to check the MD5 every time I moved the file, used fastboot. Couldn't have been easier and everything is working perfectly.

Seeking advice rooting MyTouch 1.2 (HTC Magic 32a)

Hello all, thank you for this great resource and any insight you can provide.
I need some of your wisdom, as I've been banging my head against a brick wall for about two weeks now, trying to root my T-Mobile MyTouch 1.2 (HTC Magic) with the 3.5" jack.
I did a couple hours of homework and began the process, but currently am stuck at the HTC Magic splash screen on normal boot up. I cannot boot into recovery; I have tried flashing both the Amon Ra versions, H and G. I can, however, boot into hboot and fastboot menu options, so it my understanding that my phone is salvageable with the right tools and process. Unfortunately, I was given bad advice—or incorrectly followed good advice—and now all the instructions I find to restore functionality to my phone don't go smoothly.
I've spent countless hours trying proposed found threads here (mostly) and other resources, but while the solutions sound like the apply to my hardware, they fail to complete successfully.
I have created two goldcards, both appear to work, as I have been able to flash a sappimg.zip image initially, but currently trying to flash again to remedy problems hangs and requires me to pull the battery. It usually hangs at the initial unzipping or at updating radio_v2. Via fastboot, I have been able to flash the stock hboot.nbo and reflash different versions. I was able to flash to the stock radio once, but have had problems trying to reflash images, trying to correct the issue.
These details have read different things at different stages in trying proposed solutions, but currently the info on fastboot menu reads:
SAPPHIRE UNKNOWN 32A SHIP S-ON H
HBOOT-1.33.0009 (SAPP31000)
CPLD-13
RADIO-6.35.10.18
At this moment, I've stopped trying to find answers on the forum because I've spent countless hours failing and more importantly, fear that if I continue applying incorrect solutions, I will irreversibly damage my phone. I hope that someone can provide some advice tailored to my situation.
Thank you for reading and for your reply. I understand that any advice I receive is at my own risk to follow.

Option one: flash the .nbo file for te engineerings 1.33.2010 spl and thz flash the g recovery.
Option two: flash the sappimg to revert back to stock then stsrt all over again
Option three: flash the stock sappimg and stay at stock thanking jesus you didnt **** anything up.
Sent from my HTC Magic using XDA App

You did not read the mytouch 1.2 rooting guide correctly. This phone can only run stock spl and radio. Read the guide at the unlockr. After using the goldcard you should have flashed stock spl and radio using fastboot.

NetrixTardis said:
You did not read the mytouch 1.2 rooting guide correctly. This phone can only run stock spl and radio. Read the guide at the unlockr. After using the goldcard you should have flashed stock spl and radio using fastboot.
Click to expand...
Click to collapse
I tried the files and process indicated on Unlockr several times. The files and process located here: theunlockr.com/2010/03/11/how-to-root-the-mytouch-1-2-and-fender-mytouch/
Attempting again, just now, I run into the same roadblock as reported in my initial post: Immediately after clicking the action button to execute the update, the process hangs at 'Unzipping' on step [1] SYSTEM, where the progress bar never moves, and pulling the battery is the only thing that works (unfortunately, since I'm warned not to power off the device!).

knny1491 said:
Option one: flash the .nbo file for te engineerings 1.33.2010 spl and thz flash the g recovery.
Click to expand...
Click to collapse
Thank you so much for your response.
Attempting option 1, I get the following messaging in the terminal while trying to flash the hboot.img (not nb0, is this wrong?) downloaded from the 'Magic SPL HBOOT collection' thread located here: forum.xda-developers.com/showthread.php?t=529019
sending 'hboot' (512 KB)... OKAY
writing 'hboot'... INFOsignature checking...
FAILED (remote: signature verify fail)
In the previous reply to another helpful commenter I describe another error I get while attempting to update the sappimg provided by Unlockr.
Further insight is very much appreciated.

so this is the second time I'm seeing this exact problem... this is keeping me from rooting this mytouch. but last time i saw this problem I believe it was solved.. i can't remember where i saw it though! I'll look and look until i find it then i'll post it here!
but in the mean time you can try unrooting it until the problem is solved?
http://forum.xda-developers.com/showthread.php?t=665814

lbsk8addict said:
last time i saw this problem I believe it was solved.. i can't remember where i saw it though! I'll look and look until i find it then i'll post it here!
Click to expand...
Click to collapse
Thank you! I hope that you do.
lbsk8addict said:
but in the mean time you can try unrooting it until the problem is solved?
forum.xda-developers.com/showthread.php?t=665814
Click to expand...
Click to collapse
I've visited that thread before in my days of lurking, but didn't attempt it (I don't think—I've tried so many things, it's hard to remember fully at this point).
I think all I have right now are goldcards. I hope a stock SD card isn't needed, or I'll have to figure out how to restore a Kingston microSD or buy another.
Thanks again for all of your input.

lbsk8addict said:
but in the mean time you can try unrooting it until the problem is solved?
forum.xda-developers.com/showthread.php?t=665814
Click to expand...
Click to collapse
Follow up, attempting to update to MT3G 1.2 Sappimg (BUILD# 2.10.531.4) downloaded via that link, I encounter the second error documented in my initial post, the update process hangs at updating step [2] RADIO_V2. The red progress bar stops at about 95%. Pulling the battery out is the only way to escape.
I think, and this is just a gut-level guess, that my problem stems from a corrupt radio version. Any one have an opinion or advice about that?
After pulling the battery and booting back into fastboot, my versioning reads as follows:
SAPPHIRE PVT 32A SHIP S-ON G
HBOOT-1.33.0013 (SAPP31000)
CPLD-13
RADIO 6.35.10.18

You have a 32a radio with a 32b spl, during the root process you are supposed to be able to revert that. What we need to do is get you onto an eng spl so you can fastboot erase radio, fastboot flash radio, then flash the correct hboot aka the stock one. Right now you cant fastboot or anything aka you are semi bricked. Only thing i can say is let it sit o the charger for as long as possible for the sappimg update and pray lots n lots.
Sent from my HTC Magic using XDA App

knny1491 said:
You have a 32a radio with a 32b spl, during the root process you are supposed to be able to revert that.
Click to expand...
Click to collapse
Thank you so much for the follow up. I wish the news were better!
How can you tell that I have a 32b SPL? By the errors I'm experiencing? The SAPP310000? Just guesses here. I don't see that on my phone so, I'm curious to learn.
knny1491 said:
What we need to do is get you onto an eng spl so you can fastboot erase radio, fastboot flash radio, then flash the correct hboot aka the stock one. Right now you cant fastboot or anything aka you are semi bricked. Only thing i can say is let it sit o the charger for as long as possible for the sappimg update and pray lots n lots.
Click to expand...
Click to collapse
Are you advising my to sit on my hands, keeping my phone charged, until, hopefully, the development community comes up with a new sappimg solution? Or are you saying to preform the 1.33.2010 engineering SPL update until success or my phone dies?

I was stating to do the update where it freezes or hangs on the radio and let it sit for a crazy amount of time with praers, the spl version is defing by the numbers i the 1.33.0013 etc area, 32a users have 1.76.xxxx sp numbers while 32b users have 1.33.xxxx and after looking i see you are on the stouch 1.2 spl which is why fastbooting anything will not work. Quick question though did you try flashing te spl and radio BEFORE the recovery?
Sent from my HTC Magic using XDA App

knny1491 said:
I was stating to do the update where it freezes or hangs on the radio and let it sit for a crazy amount of time with praers, the spl version is defing by the numbers i the 1.33.0013 etc area, 32a users have 1.76.xxxx sp numbers while 32b users have 1.33.xxxx and after looking i see you are on the stouch 1.2 spl which is why fastbooting anything will not work.
Click to expand...
Click to collapse
Thank you for the reply. Good to know, as I was under the impression that all T-Mobile MyTouch 1.2 phones were 32A, and 1.33.0013 was the desired and appropriate version for 32A.
knny1491 said:
Quick question though did you try flashing te spl and radio BEFORE the recovery
Click to expand...
Click to collapse
I initially tried followed the procedure here: http://wiki.cyanogenmod.com/index.php/Full_Update_Guide_-_Fender/1.2
Where, I updated the SAPPIMG via goldcard, then through fastboot, I flashed the radio, hboot, and recovery. But, I wasn't able to boot to recovery after that process, for whatever reason, so I began trying other procedures from other sources, which in all likelihood took me further away from the solution instead of closer.
If the current attempt of updating radio_v2 until success or power battery dies (which has been hung for about 30 minutes so far) does not end successfully, should I try flashing a different hboot or radio? Or any other suggestions?
Thanks again for your continued help. I'm going to try to get some more attention to this thread to hopefully get more possible solutions.

If the radio doesnt flash then we have to question why the recovery didnt load, the g version is the correct version given there is only one spl for us 1.2 users and it is a google spl. That is why you flash radio then spl then recovery in that order so nothing messes up. The thing is you have to flash a radio before spl, yet you hav the spl yet NOT THE RADIO which leaves me to believe you accidentalky did the spl first n not the radio first.
Sent from my HTC Magic using XDA App

knny1491 said:
If the radio doesnt flash then we have to question why the recovery didnt load, the g version is the correct version given there is only one spl for us 1.2 users and it is a google spl. That is why you flash radio then spl then recovery in that order so nothing messes up. The thing is you have to flash a radio before spl, yet you hav the spl yet NOT THE RADIO which leaves me to believe you accidentalky did the spl first n not the radio first.
Click to expand...
Click to collapse
Okay, thanks so much for the continued insight.
I think, I flashed the radio down to original, but encountered some problem, misdiagnosed it, and flashed it back up again. Now it's been about 3 weeks of messing with this phone for a couple hours a day, so, unfortunately, it's hard to remember all that I've tried. If what you're saying is true, then yes, I must have accidentally flashed the SPL before the radio. Is there a remedy for this? I've been pouring over this forum searching for "can't flash radio" (forum.xda-developers.com/search.php?searchid=39519193&pp=25&page=1) and so far I've read people claiming to have had successfully deleting their radios completely and reinstalling. Is this an option? Any other suggestions?
I will PayPal $30 to you, anyone who can give me a solution to where this phone is working and rooted. Alternatively, I live in Los Angeles, if anyone can recommend a good, knowledgeable, phone repair shop.

it's really strange why that didn't work for you.
My steps were as follows:
**make sure phone is fully charged**
pre 1) create goldcard
1) place sappimg.zip on gold card
2) boot phone with goldcard to flash using Vold down + power
3) let it reboot - should boot up to the "htc magic" logo -- for me it never loaded back up to stock 1.6, I had to pull the battery.
4) boot to fastboot using back + power
5) connect phone to PC and verified it was recognized using "fastboot devices"
6) make sure you have stock radio and spl in your Android SDK's \tools
7) performed the following:
fastboot flash radio radio.img (or whatever the filename you have for the stock radio)
fastboot flash hboot hboot.nb0 (or whatever the filename you have for the stock hboot)
fastboot flash recovery recovery.img (or whatever the filename you have for amon_ra or clockwork or cm recovery)
fastboot reboot-bootloader (to make sure that stock radio and SPL are loaded again)
8) reboot to recovery using home+power
*from this point on, you no longer need to use your goldcard
9) have new ROM .zip on root of your SD card, option flash from zip
10) ???
11) profit

NetrixTardis said:
it's really strange why that didn't work for you.
My steps were as follows:
**make sure phone is fully charged**
pre 1) create goldcard
1) place sappimg.zip on gold card
2) boot phone with goldcard to flash using Vold down + power
Click to expand...
Click to collapse
Thank you for your continued feedback!
I think you've listed the standard recipe for rooting this phone. I believe you. Unfortunately, something in my phone has gone askew (certainly my error) at this point and the "standard" just isn't working now. As is, and for the past 3 weeks, the process you describe dies at step 2. It hangs while updating RADIO_v2 (at whatever position in the list of updates it is for a given SAPPIMG file). Also, attempting to flash a stock radio.img via fastboot also hangs. Both updates send just fine, but hang at updating around 95%.
I've also been getting some advice from another member, knny1491. On this page, above, you'll see he hypothesises what my error is:
knny1491 said:
If the radio doesnt flash then we have to question why the recovery didnt load, the g version is the correct version given there is only one spl for us 1.2 users and it is a google spl. That is why you flash radio then spl then recovery in that order so nothing messes up. The thing is you have to flash a radio before spl, yet you hav the spl yet NOT THE RADIO which leaves me to believe you accidentalky did the spl first n not the radio first.
Click to expand...
Click to collapse
That sounds plausible that I did flash things in the wrong order. I'll accept that. I've been messing with it so much, I'm lucky it works at all. So now, and still, my question is where to go from here? Do you know anything about this radio/SPL relationship and how to remedy this current conflict, NetrixTardis?
Thanks again.

Possibly try to re download the sappimg from the mgic spl thread?

I was just thinking, if your goal at this point is to have the phone usable again regardless of root; why not try the RUU exe ? If i unserstand what it does, it should flash the phone back to stock (radio, spl, recovery,ROM etc). You'll have a phone as if you just unboxed it.
Thats if i understand what the ROM Upgrade Utility (RUU) does correctly. Someone should be able to correct me...

NetrixTardis said:
I was just thinking, if your goal at this point is to have the phone usable again regardless of root; why not try the RUU exe ? If i unserstand what it does, it should flash the phone back to stock (radio, spl, recovery,ROM etc). You'll have a phone as if you just unboxed it.
Thats if i understand what the ROM Upgrade Utility (RUU) does correctly. Someone should be able to correct me...
Click to expand...
Click to collapse
Thanks for the idea! I'll do some research on that. If anyone else can give any insight into if this may help restore my phone, please chime in!
I'd like root, but anything that gets the basic utility of the phone back would be great at this point (I've been using a old razr as a replacement while mine is hosed). I think an official 2.2 update is coming out from T-Mobile soon. I can wait for that.

NetrixTardis said:
Thats if i understand what the ROM Upgrade Utility (RUU) does correctly. Someone should be able to correct me...
Click to expand...
Click to collapse
If this is a good potential solution, could someone please direct me to which RUU to use? I've located the "[ROM] Official HTC Sapphire/Magic/MT3G RUU ROM Links" thread here: forum.xda-developers.com/showthread.php?t=659403
There really is a great abundance of options. I'm guessing I should go for the latest [MT3G 1.2] download which is:
36) [xda-ftp] [4shared] 2.10.531.4 T-Mobile USA DRD35
36) 2.10.531.4 1.33.0013G 2.22.23.02 N T-MOB010
I'll want a few hours or perhaps a day before attempting this process, in hopes that some helpful reader will provide his input if this is a good or bad thing to do as far as getting the phone working again.
Thanks!

[MISC] Major news on SIM unlocking and radio S-OFF

This has been in progress for a while. If you follow the G2 forums, then you'll know that there have been big problems with G2 phones that have been unlocked via unlock codes, with those unlocked phones then not being able to find a network at all.
It looks like the guys on #G2ROOT have cracked S-OFF for radio. This is *not* the same as the current S-OFF that we have from HBOOT. Apparently it should help to prevent semi-bricking via incorrect flashing of older ROMs.
The article in the Wiki explains all. Documentation about the procedures should be coming soon. We will of course have to make sure it's fine on the DZ too :
http://forum.xda-developers.com/wik...Subsidy_Unlock.2C_SuperCID.2C_and_Radio_S-OFF

nice gives all those "bricked" g2's hope

Radio S-OFF is permanent S-OFF?
So no more warranty? Damn.
I'll stick to the stock ROM for a while with root, then HBOOT S-OFF, but never radio S-OFF.
I like warranty. Never know when you'll need it.

DanWilson said:
Radio S-OFF is permanent S-OFF?
So no more warranty? Damn.
I'll stick to the stock ROM for a while with root, then HBOOT S-OFF, but never radio S-OFF.
I like warranty. Never know when you'll need it.
Click to expand...
Click to collapse
I imagine it'll still be possible to reverse it. From a scan of the IRC logs (though of course I might have missed important stuff), it looks like you just need to write the correct data to the right area of a partition to get the radio S-OFF. So surely you can un-do that by writing the previous data ?

Documentation on this is now up, see http://forum.xda-developers.com/showthread.php?t=855764
Bear in mind that the instructions are for the G2 right now, so if you try this out on a DZ there's a high chance of a permanent brick ! But hopefully someone will sort out a verified method for the DZ soon

I would not advise people do this form of S-OFF unless they really need to anyway, its harder to come back from (if you did semi-brick) and holds more risks.

Lennyuk said:
I would not advise people do this form of S-OFF unless they really need to anyway, its harder to come back from (if you did semi-brick) and holds more risks.
Click to expand...
Click to collapse
But when an easier way to do it comes along (which is being worked on, I believe), a full S-OFF will be a lot safer, because then it won't be so easy to brick your phone by simply flashing an old RUU.

steviewevie said:
But when an easier way to do it comes along (which is being worked on, I believe), a full S-OFF will be a lot safer, because then it won't be so easy to brick your phone by simply flashing an old RUU.
Click to expand...
Click to collapse
people should not be flashing an old RUU anyway!
anyone who is silly enough to do that gets a brick for a reason.
Always either flash the latest ruu, or restore a nandroid of stock and flash an ota it offers, these are the safest ways.
You will get more bricks from people doing radio s-off than the s-off + ruu method gives.

Lennyuk said:
I would not advise people do this form of S-OFF unless they really need to anyway, its harder to come back from (if you did semi-brick) and holds more risks.
Click to expand...
Click to collapse
You're an ass-talker. You talk through your ass, blow hot air, and have no idea what you're talking about.
1) it is SAFER,
2) it is EASIER to come back from,
3) it is SAFER.
Why is it safer? Because it does NOT require writing the hboot or radio! You can blow p7 out and android will still boot, which means that you have the opportunity to fix it if something goes wrong.
A bad flash of the radio or hboot and you're dead.

For those who might not have seen it yet, there's now a fully documented procedure on how to do this to your DZ (and yes, it's been tested on the DZ too).
As has been said, this is a safer method to get S-OFF (letting you flash custom ROMs) than the previous method of putting on an engineering hboot.
See http://forum.xda-developers.com/showthread.php?t=857390

DanWilson said:
Radio S-OFF is permanent S-OFF?
So no more warranty? Damn.
I'll stick to the stock ROM for a while with root, then HBOOT S-OFF, but never radio S-OFF.
I like warranty. Never know when you'll need it.
Click to expand...
Click to collapse
all i do for warrenty with modded phones is feed 12-20 volts ( from a wall adapter) into the battery contacts and tost the main board and bring it back as dead they send me a new one no questions asked cause the phone is dead...even did this with a htc ppc6800 that i smashed the screen in and thay warrenteyed it no prob....this is on bell in canada....
666

I was following your discussion on bricking because of flashing ruus but for some reason it doesn't apply to me. I had an Asian WWE 1.34.707.5 (shipped with my phone) then I flashed it with Asian WWE 1.34.707.3 RUU and it didn't brick my phone.

[GUIDE] REVONE, MOONSHINE & RUMRUNNER Pre-S-OFF Steps.... READ FIRST

IMPORTANT INFORMATION!
READ THIS BEFORE GOING TO THE S-OFF THREADS​
This simple guide is aimed at giving you the best chance at achieving S-OFF on your device. Although not all of the steps listed below are 100% necessary if you are failing to achieve S-OFF or still receiving errors of any sort then you either cannot S-OFF your phone or you haven't followed the guide. In my opinion your best hope for S-OFF is by using RUMRUNNER. It supports the largest amounts of firmware and the support is great.​
You should only use MOONSHINE/REVONE to S-Off if......
1. You are on or flash a STOCK Sense 5, Android 4.1 ROM! (NOTE: 4.2 Software may be OK however for your best chances use the oldest you possibly can!!)
2. Have an old un-patched 1.44 HBoot or If on T-Mob or AT&T and on Patched 1.44 HBoot you have downgraded using one of the guides provided at the bottom of this post. (NOTE: To my knowledge patched 1.44 HBoot's are most likely those dated from June 2013 onwards, to check this reboot to bootloader and find the date there.)
3. Use the up to date 0.2.1 revone (the older ones give false successes)
4. Are Rooted (Not necessary but seems to improve chances of success)
5. Have the correct Moonshine package for your exact firmware and software version! If your firmware is not on the site and there is no way of you getting a matching firmware then you can't use it!
6. Are not on stock 4.2 software upgraded via OTA. (NOTE: Custom 4.2 Software may be OK as long as your HBoot is still 1.44)
7. Are not using a GE ROM, 4.3 Rom or on stock 4.3 software
8. Are not on HBoot 1.54 or higher
9. Are NOT on HBoot 1.54 or higher
10. ARE NOT ON HBOOT 1.54 OR HIGHER
11. Are not an Idiot! (Most important of all)
Before you try RUMRUNNER you must.....
1. Ensure you are on 100% Stock firmware/software that is supported. (note:you may be rooted or have custom recovery they should not effect success)
2. Ensure that if your device is carrier branded you are running stock firmware/software for your carrier (i.e H3G = 2.24.771.3)
3. Have your bootloader unlocked!
4. Use the correct RumRunner package for your device firmware. If you are not then flash Stock software matching your correct carrier firmware before starting.
5. Have HTC Sync removed from your computer!
6. Have firewalls, antivirus and anything else turned off or un-installed! (Ensure to turn back on after completion )
7. Have read the RumRunner thread and Site HERE and know you can email them with your firmware version so maybe they can S-OFF your phone! But DO NOT pester them on their IRC channel, that is for support only!!
8. Have more then 40% battery life.....
9. Not be an idiot! (Always the most important point!)
Notes:
1. If it still isn't working try a different stock rom and re-flash your correct stock firmware and try RumRunner again
2. If RumRunner gets to pouring (5)... Or higher it's more then likely failed already.
3. Some branded firmware's might work with the international package i.e 2.24.111.3 works with the 2.24.401.1 rumrunner package.
Again as I stated earlier some of these may not apply but if you want to guarantee revone or moonshine to work then you should follow these rules! Also in addition to this. READ THE OP of the threads in question (and POST 2 of revone!) They are your bible and will tell you what to do.
If you aren't sure what S-OFF is, does, why you might need it or how to achieve it safely then you DO NOT NEED S-OFF. You could ruin your phone and you really should start with more basic things first!!
WARNING Going back to S-ON isn't necessary for warranty, just lock the bootloader and go back to a stock rom/recovery if you do decide to be crazy and go S-ON again you may receive back a non-s-offable device that isn't supported by any of the above methods... YOU HAVE BEEN WARNED
Error codes and what they mean (from my experience, and what I've read!) ;-
Error Code -1 = Potentially you need to try a different ROM or it could just be random and after a few tries and reboots it might work. A few people have reported that rebooting and using -p rather than -P has worked but I'm not convinced as -p isn't built as a command but you're free to try whatever you wish.
Error Code -2 = I've seen people report this but revone has actually worked so should you see this try and reboot and carry on, if not then try changing ROMs and try again.
Error Code -6 = More then likely you're on either a patched or a 1.54 HBoot and you're not going to be able to S-Off. If you reboot to bootloader and you're on 1.44 then you might be able to downgrade using one of the guides on xda. Xboarder's guide on rootzwiki for TMob is a good one. In addition you may be on the right 1.44 HBoot but the software/ROM you're running could be the issue. In any case run a stock RUU for your CID and you should be sorted.
Error Code 1 = I've had this myself and this basically means it's not ever going to work. I think it's a variant on the -6 Error. If you see this, you're out of luck IMO.
Link for T-Mobile Device HBoot Downgrade to enable S-OFF HERE
Link for AT&T Device HBoot Downgrade to enable S-OFF HERE
Additional Info (On Downgrading HBoot from 1.54 with S-ON)
If after reading this guide you're thinking OK so I need to downgrade my HBoot, then to clear things up here is a list of methods that categorically do not and will not work to downgrade your 1.54 HBoot to 1.44 HBoot if your device is S-ON regardless of how much you think it should work because it did on your old phone.
Note these methods WILL NOT WORK to downgrade HBoot from 1.54 to 1.44 while S-ON!
1. Running an old RUU for your device with a lower HBoot inside
2. Writing directly to any of the board or hboot partitions mmcblk0p4, mmcblk0p5, mmcblk0p12. This includes:-
a) dd'ing your hboot/board image, editing the version then dd'ing it back
b) dd'ing any other hboot/board image to your hboot partition mmcblk0p12
c) dd'ing anything to anything!! HBoot and board are WP from low boot and cannot be written to or modified at all unless S-OFF
d) chmodding mmcblk0p12, deleting it, editing it, or anything else you might thing could work
e) using recovery to flash to mmcblk0p12 using busybox and dd command.
f) anything else I missed (I hope you're getting the picture here anyway) Oh and note, if you try to dd and it says it worked.... It didn't!
3. Modifying and flashing an encrypted or decrypted rom.zip, firmware.zip, PN07IMG.zip or RUU.zip from recovery, fastboot or RUU mode
4. Flashing an old encrypted or decrypted rom.zip, firmware.zip, PN07IMG.zip or RUU.zip from recovery, fastboot or RUU mode
5. Using a Y-Cable with or without a goldcard to flash an old PN07IMG.zip
6. Using a Y-Cable with or without a goldcard to flash a modified PN07IMG.zip
7. Running a modified RUU with old or editied HBoot version
8. *Not totally proven yet* Trying to brick the phone by shutting it off during RUU.zip install at the HBoot writing stage. (This has only been tried once so far and didn't pay off, I would not advise trying this unless you are a "VERY" confident/crazy android user/dev)
I hope this helps clear things up, have a nice day and happy flashing ​

The War Horse said:
OK so following my post of pretty much exactly this on the revone thread it seems that a lot of people still aren't sure what's going on so here is my simple guide to follow BEFORE you try to S-OFF your phone or post in the Revone or Moonshine threads.
You should/can only use revone or Moonshine(potentially different as I am not as familiar but I'm pretty sure the same rule apply) to S-Off if;-
1. You are on or flash a STOCK Sense 5, Android 4.1 ROM before you try!
2. Have an old un-patched 1.44 HBoot or If on T-Mob or AT&T and on Patched 1.44 HBoot you have downgraded using one of the easy to find guides provided.
3. Use the up to date 0.2.1 revone (the older ones give false successes) <revone only>
4. Are Rooted (Not necessary but seems to improve chances of success) <revone only>
5. Have the correct Moonshine package for your exact firmware and software version! If your firmware is not on the site guess what..... You can't use it! <moonshine only>
6. Are not using a 4.2 ROM
7. Are not using a GE ROM
8. Are not on HBoot 1.54
9. Are not on HBoot 1.54
10. ARE NOT ON HBOOT 1.54
11. Are not an Idiot! (Most important of all)
Some of these may not apply but if you want to garuntee revone or moonshine to work then you should follow these rules! Also in addition to this. READ THE OP of the threads in question (and POST 2 of revone!) They are your bible and will tell you what to do.
Notes on Error codes (from my experience, and what I've read!) <revone only>;-
Error Code -1 = Potentially you need to try a different ROM or it could just be random and after a few tries and reboots it might work. A few people have reported that rebooting and using -p rather than -P has worked but I'm not convinced as -p isn't built as a command but you're free to try whatever you wish.
Error Code -2 = I've seen people report this but revone has actually worked so should you see this try and reboot and carry on, if not then try changing ROMs and try again.
Error Code -6 = More then likely you're on either a patched or a 1.54 HBoot and you're not going to be able to S-Off. If you reboot to bootloader and you're on 1.44 then you might be able to downgrade using one of the guides on xda. Xboarder's guide on rootzwiki for TMob is a good one.
Error Code 1 = I've had this myself and this basically means it's not ever going to work. I think it's a variant on the -6 Error. If you see this, you're out of luck IMO.
I hope this clears things up. Please feel free to post your error code findings should they be any different from what I have stated. Also anyone familiar with moonshine please feel free to add anything I might have missed. Cheers.
Sent by homing dragon......
Click to expand...
Click to collapse
Can I get s-off with HBOOT 1.54???????? (joking BTW lol)
cheers for this should stop certain muppets asking silly things

Aditional Information - SuperCID
On a separate note If you are on an updated HBoot but SuperCID (11111111) Then the above rules may not apply. If this is the case for you and you are SuperCID, S-ON on HBoot 1.54 or Higher then you may have to try a few different routes as SuperCID bypasses some things on occasions. You may well be able to downgrade your HBoot and S-OFF.

exocetdj said:
Can I get s-off with HBOOT 1.54???????? (joking BTW lol)
cheers for this should stop certain muppets asking silly things
Click to expand...
Click to collapse
Lets hope so. Mods moved it from the Origional Dev forum though and I have a feeling a lot of Muppets will totally bypass this forum and go there and still crack on blindly...... Maybe if this was a sticky then it would be missed less.... I dunno..... MODS?

The War Horse said:
Lets hope so. Mods moved it from the Origional Dev forum though and I have a feeling a lot of Muppets will totally bypass this forum and go there and still crack on blindly...... Maybe if this was a sticky then it would be missed less.... I dunno..... MODS?
Click to expand...
Click to collapse
Think maybe you should put the title of the thread entirely in capitals and surround it with *********s or ###s so not even the dumbest noob will miss it lol!

exocetdj said:
Think maybe you should put the title of the thread entirely in capitals and surround it with *********s or ###s so not even the dumbest noob will miss it lol!
Click to expand...
Click to collapse
HAHA, I did actually try this but it converted the lot to lowercase randomly.... I assume you're not allowed all capitals? lol

The War Horse said:
HAHA, I did actually try this but it converted the lot to lowercase randomly.... I assume you're not allowed all capitals? lol
Click to expand...
Click to collapse
damn i assume so!!!! anyway soz for clogging up ur thraed mate! Try the symbols ~~~ *** (it will look like you are swearing at em hahaha!)

exocetdj said:
damn i assume so!!!! anyway soz for clogging up ur thraed mate! Try the symbols ~~~ *** (it will look like you are swearing at em hahaha!)
Click to expand...
Click to collapse
No worries man. Just spread the word. I've asked a mod if it can be stickied so we'll see.

posted a friendly link to this thread in the soff ones lol!

just have a look:laugh:

The War Horse said:
No worries man. Just spread the word. I've asked a mod if it can be stickied so we'll see.
Click to expand...
Click to collapse
the noobs dont even notice the stickies, they will still answer questions

IINexusII said:
the noobs dont even notice the stickies, they will still answer questions
Click to expand...
Click to collapse
I know. I'm thinking that at least from now on noone has to answer the questions though. they can simply send them to this thread lol.
I'd be better if this was in the Orig Android Dev forum imo, that way when they jump in there head first they might see it!

The War Horse said:
I know. I'm thinking that at least from now on noone has to answer the questions though. they can simply send them to this thread lol.
I'd be better if this was in the Orig Android Dev forum imo, that way when they jump in there head first they might see it!
Click to expand...
Click to collapse
the ONLY way is for XDA to automatically redirect the noobs to this thread whenever they click on a S-OFF thread. otherwise they wont see it

IINexusII said:
the ONLY way is for XDA to automatically redirect the noobs to this thread whenever they click on a S-OFF thread. otherwise they wont see it
Click to expand...
Click to collapse
Now that would be something!!

1.54 s off
just go my phone s-off on 1.54 h boot,check fone fun shop.was only achieved today.

doohdah said:
just go my phone s-off on 1.54 h boot,check fone fun shop.was only achieved today.
Click to expand...
Click to collapse
S-Off via jtag or by an external paid source is completely different to revone or moonshine. For one they're a lot cheaper!
Also the company you mention has been offering S-Off on the one for while now.
Sent from my HTC One using Tapatalk 4

good!:good:

1.54.s off
The War Horse said:
S-Off via jtag or by an external paid source is completely different to revone or moonshine. Fit's the onlone they're a lot cheaper!
Also the company you mention has been offering S-Off on the one for while now.
Sent from my HTC One using Tapatalk 4
Click to expand...
Click to collapse
For your information the 1.54.s-off was only achieved yesterday and is.by java card,it my be more expensive than revone but its the only solution at this time.

doohdah said:
For your information the 1.54.s-off was only achieved yesterday and is.by java card,it my be more expensive than revone but its the only solution at this time.
Click to expand...
Click to collapse
But by java card it is always possible, that's how htc does it, even on for the one x some shops offer it....

doohdah said:
For your information the 1.54.s-off was only achieved yesterday and is.by java card,it my be more expensive than revone but its the only solution at this time.
Click to expand...
Click to collapse
It was achieved by java card the day the phone was made. Lol.... Java card isn't an exploit.
Sent from my HTC One using Tapatalk 4