CONFIRMED!! BRICKS: Radio and SPL + New SAFETY theory - G1 Android Development

Another theory (unconfirmed, but seems logical): Safely change between ANY SPLs using recovery.
http://forum.xda-developers.com/showpost.php?p=6535848&postcount=87
The short version: You go into recovery, set it to write the new radio/hboot update.zip, then before rebooting, WIPE THE RECOVERY PARTITION. When it reboots in boot-recovery mode after updating the radio/hboot, it'll fail properly and force you into fastboot rather than ending up in limbo. This *should* be safe, even against mismatched radio/spl.
This is the (confirmed) theory regarding the relationships between the radio/hboot/recovery:
That ALL radios are compatible with ALL SPLs.
That bricks are NOT caused by radio/spl incompatibility, but by FAILURE TO BOOT RECOVERY.
I realize that that sounds bold and goes against the grain and what people think that they know.
Up until now, there have been some wild theories about bricks. One of the early ones is that there was a relation between the mainboard code and the chance of bricking -- specifically, that a mainboard labeled as "DVT" will brick whereas a mainboard labeled as "PVT" will not. This theory, though still widely believed, is FALSE. There are conclusive reports of DVT boards being successfully loaded with the deathspl. The simple fact that there are very very FEW DVT boards in the wild contributes to the lack of proof.
A second, and much more conclusive theory, is that the RADIO version affects the chances of bricking. While in general, having a 2.x or 3.x radio seems to reduce the chances of bricking, there are STILL observable instances of bricks despite this. In other threads, I have referred to the "unknown factor" that triggers this.
While I haven't been able to isolate this unknown factor, I have been able to come to a theory regarding overall radio compatibility based on the results of experimentation by forum member ezterry, who has been able to both successfully REVERSE a brick, as well as ESCAPE the current rogers firmware lockdown.
His work can be found in the following two threads:
http://forum.xda-developers.com/showthread.php?t=591048
http://forum.xda-developers.com/showthread.php?t=649431
Specifically, the results are as follows;
Observed in a BRICKED PHONE containing a 1.x radio and deathspl:
The phone was jammed into boot mode 3 -- recovery, and ignored boot-time signals to alter boot mode -- specifically, the camera button, which should, under normal circumstances, activate FASTBOOT. It appears that boot-time signals are ignored when the device is not in normal boot mode. The solution was from bluelight mode (trackball+power) to override a security lockout using jtag, and force it into fastboot using serial console. And yes, the deathspl's fastboot mode was successfully activated from a boot through a 1.x radio.
What is not clear at this moment is why a recovery boot is unsuccessful. This is the unknown factor. Under certain circumstances, I'm sure that the specific recovery image installed may not be compatible with either the radio or the spl -- this could be due to an EBI 0/1 kernel issue. Or possibly some effect of the deathspl's partition remapping. I suggest a possibility that the radio/spl *combination* may not be compatible with the recovery. In any event, the solution may be to FORCE the thing to go to FASTBOOT mode upon reboot and then using fastboot to flash known good system images. This, though not isolating the unknown factor, will make it irrelevant.
First, I suggest flashing radio and SPL using FASTBOOT ONLY.
Second, I suggest WIPING ALL PARTITIONS (obviously with the exception of radio and spl) -- this is supposed to force the device into fastboot mode, HOWEVER, it is not clear if this would work in the event that the device is already stuck in recovery-boot. It might.
THIRD, I suggest completing this step with a "fastboot reboot-bootloader".
Also note this:
Under normal circumstances, when leaving fastboot mode, the device should be configured for a NORMAL BOOT. I therefore introduce another possibility: That when using FASTBOOT to install the radio and/or SPL, you are GUARANTEED NOT TO BRICK (not guaranteed at this point since it has not been verified). A normal bootup will obviously fail, however, when rebooting from a "softbrick", it will again try normal boot mode -- which means that it WILL accept boot time signals, like the CAMERA button to enter fastboot.
Specifics on boot mode:
There are three selectable boot modes;
Normal boot,
recovery boot,
fast boot.
Normal boot mode is fine since it will accept boot time signals. Fast boot mode is fine since it will both allow you to flash anything you want as well as clear any set boot flags. It is only the RECOVERY boot mode that is dangerous. In fact, it is SO dangerous, that in my opinion, it should NOT be possible to set this flag. Recovery mode should ONLY be accessible through boot-time signalling.
So the solution to avoid bricking is in ENSURING that the device does NOT get the "recovery" boot mode flag set. The other solution is in developing (as ezterry has expressed a desire to do...) an SPL that IGNORES the boot mode 3.

I feel smarter just from reading all of that.
+1

I wish there was a thread "like" button like on fb lol nice thoery

My name is Sheldon and I support this message.
Recently bricked a G1 for the first time (And I have done many SPL/Radio flashes before on multiple G1's) and it was only during reboot into recovery after a flash that the battery got pulled by mistake causing it to brick.
Reason I support this theory is because at that moment the phone was flagged to recovery boot and did not complete this process successfully after flashing a new SPL. It was the ENG spl I was flashing too.
A+ on the write up to OP.

+1 nice theory and well written out

Not so sure about any SPL + radio combination working.
Specifically there were some really weird cases of bricks for users flashing new radio and SPL for Magic (1.76.X HBOOT, 6.35.X RADIO) on a 32B Magic. Afterwards their ROM authentication always failed for some reason.
So there are combination that actually do not work?

I have to admit, I feel cleverer after reading the whole thing
+1 for good writeup.

xxmonsterx said:
I wish there was a thread "like" button like on fb lol nice thoery
Click to expand...
Click to collapse
Sorry, digression:
Can we petition for one? Seriously, I have been seeing comments on having a 'like' button over XDA since the new revamp.

I might disagree with this theory because my g1 used to run with a broken recovery image. A couple of months ago I tried to figure out what was the max size of an recovery image. A way of testing this was by flashing an image that was very large and seeing how much will be copied. So let's say the recovery image can only be up to 10 mb but instead I flashed a 70 mb image. It will get flashed but no error massage will appear. So then I rebooted and went into recovery mode. It didn't work out and got stuck on a black screen. So I rebooted, reflashed ra-recovery image, test it out, and it worked out perfectly. Sadly I didn't recovery any speific amount of size for the recovery image. If the android OS runs much like a computer, First it will check the bios, bootloader, recovery, and then load the rom, or start to run the enviroment for the android operating system. Can someone check what those the update-script say in the deathspl.

Hrm ... didn't see this thread was made
may want to check out my update.
http://forum.xda-developers.com/showpost.php?p=6037188&postcount=398

mohsinkhan47 said:
.... Sadly I didn't recovery any speific amount of size for the recovery image. If the android OS runs much like a computer, First it will check the bios, bootloader, recovery, and then load the rom, or start to run the enviroment for the android operating system.
Click to expand...
Click to collapse
"The phone was jammed into boot mode 3 -- recovery, and ignored boot-time signals to alter boot mode -- specifically, the camera button, which should, under normal circumstances, activate FASTBOOT. It appears that boot-time signals are ignored when the device is not in normal boot mode."
I maybe completely off but here is why I support this theory:
G1's don't have a "BIOS" to be checked upon starting that determine where or what type of boot up to perform so you can quickly change the settings by pressing F2 to say "Boot Normal Boot first, then Fastboot, then Recovery, etc" like a computer can. What the OP is stating is that when the phone is bricked, it could be due to it being "Flagged" at trying to boot into recovery and not taking ANY other boot commands....even if the Recovery Image may have been corrupted (which if it did have a BIOS like a computer it would attempt to boot the next in line option you've set if previous option failed)...so this causes the phone to be rendered useless ie: Bricked.
SOOO thats why the last part of the original post says it would be nice to develop (if possible) a SPL that would not allow this flag to be set at Boot recovery thus helping avoid possible bricks. Since if it can't flag Boot Recovery, then if the image were corrupted it would at least accept other boot signals for Normal boot and FastBoot which in turn allow you to fix said failed image.
Does any of that make sense? its late and I feel like I'm rambling.

the way i had envisioned it was IPL (radio) having a list of boot locations for SPL. Remember that SPL is the one that listens to user-input boot modes. The radios that are not compatible with the death spl were released before this spl was released (remember, it was originally the sapphire spl). Since the dream and sapphire share radio chipsets, the dream was able to use sapphire spls once a radio capable of booting it (starting with 2.22.19.26I) and had that particular spl available in it's boot list, then the spl could be booted with the appropriate parameters. Since on earlier radios the SPL hadn't been created yet, it wasn't on the list of the spls allowed to boot.
I haven't studied spl/ipl much codewise, but my findings come from theoretical analysis of spls among other htc handsets (my idea originally came from trying to figure out a hex-hack to spls that allowed them to be booted by any radio, then we could toss an android spl into a winmo device and have it boot the linux kernel).
The boot modes mentioned are spl dependent, so if the ipl can't find an spl, then the only option is to get the ipl to find the spl and boot it.
The real question would then be, how is the ipl finding the spl, and is there something we can do with spls (again, as a hex-hack) so that the appropriate value is returned to ipl when trying to boot spl and to boot that spl?
---edit---
Further (this had occurred to me before but I just remembered), keep this in mind, all dream IPLS are capable of booting all Dream SPLs, regardless of board version (not to delve into t-mo dream and rogers dream, different radio, so for this purpose, different device). I'm pretty sure too that, had there been as many IPLs/SPLs for the sapphire, the same would have been true (and we'd have more death spls to try on the dream).
What that tells me is that whatever the IPLs of all radios are reading for in SPLs, it's present across stock/eng/hard SPLs. If that thing that is being read from or booted to in those SPLs can be copied over to the Death SPL, then we'd have a death SPL that's bootable by all radios. Doesn't fix any current bricks though >.<

mohsinkhan47 said:
I might disagree with this theory because my g1 used to run with a broken recovery image. A couple of months ago I tried to figure out what was the max size of an recovery image. A way of testing this was by flashing an image that was very large and seeing how much will be copied. So let's say the recovery image can only be up to 10 mb but instead I flashed a 70 mb image. It will get flashed but no error massage will appear. So then I rebooted and went into recovery mode. It didn't work out and got stuck on a black screen. So I rebooted, reflashed ra-recovery image, test it out, and it worked out perfectly. Sadly I didn't recovery any speific amount of size for the recovery image. If the android OS runs much like a computer, First it will check the bios, bootloader, recovery, and then load the rom, or start to run the enviroment for the android operating system. Can someone check what those the update-script say in the deathspl.
Click to expand...
Click to collapse
When you went into broken recovery, you did so using the HOME-POWER boot-time signal rather than using the forced/stuck mode. Therefore your observations don't relate to the issue at hand.

Sheldonjace said:
"The phone was jammed into boot mode 3 -- recovery, and ignored boot-time signals to alter boot mode -- specifically, the camera button, which should, under normal circumstances, activate FASTBOOT. It appears that boot-time signals are ignored when the device is not in normal boot mode."
I maybe completely off but here is why I support this theory:
G1's don't have a "BIOS" to be checked upon starting that determine where or what type of boot up to perform so you can quickly change the settings by pressing F2 to say "Boot Normal Boot first, then Fastboot, then Recovery, etc" like a computer can. What the OP is stating is that when the phone is bricked, it could be due to it being "Flagged" at trying to boot into recovery and not taking ANY other boot commands....even if the Recovery Image may have been corrupted (which if it did have a BIOS like a computer it would attempt to boot the next in line option you've set if previous option failed)...so this causes the phone to be rendered useless ie: Bricked.
SOOO thats why the last part of the original post says it would be nice to develop (if possible) a SPL that would not allow this flag to be set at Boot recovery thus helping avoid possible bricks. Since if it can't flag Boot Recovery, then if the image were corrupted it would at least accept other boot signals for Normal boot and FastBoot which in turn allow you to fix said failed image.
Does any of that make sense? its late and I feel like I'm rambling.
Click to expand...
Click to collapse
Yes. Sortof. Except that you mistake what a BIOS is. You are assuming the BIOS to be the setup program, whereas the BIOS is actually the first bootloader, at about the same level as some of the stuff in the radio image. The SPL on the phone would be roughly equivalent to GRUB.
Now as it happens, the phone's firmware actually *does* share some interesting similarities with your computer's bios -- specifically, that it *does* allow for you to flag different conditions. The problem with it is that it lacks the convenient SETUP program that your computer has... Note that it ***DOES*** have a setup program still though -- BLUE LIGHT MODE!!! Only problem is that we don't know the "password" for blue light mode! So it is like having a blank hard disk, a bios configured to boot that blank hard disk, and a PASSWORD you don't know on the bios configurations!

jubeh said:
the way i had envisioned it was IPL (radio) having a list of boot locations for SPL. Remember that SPL is the one that listens to user-input boot modes. The radios that are not compatible with the death spl were released before this spl was released (remember, it was originally the sapphire spl). Since the dream and sapphire share radio chipsets, the dream was able to use sapphire spls once a radio capable of booting it (starting with 2.22.19.26I) and had that particular spl available in it's boot list, then the spl could be booted with the appropriate parameters. Since on earlier radios the SPL hadn't been created yet, it wasn't on the list of the spls allowed to boot.
I haven't studied spl/ipl much codewise, but my findings come from theoretical analysis of spls among other htc handsets (my idea originally came from trying to figure out a hex-hack to spls that allowed them to be booted by any radio, then we could toss an android spl into a winmo device and have it boot the linux kernel).
The boot modes mentioned are spl dependent, so if the ipl can't find an spl, then the only option is to get the ipl to find the spl and boot it.
The real question would then be, how is the ipl finding the spl, and is there something we can do with spls (again, as a hex-hack) so that the appropriate value is returned to ipl when trying to boot spl and to boot that spl?
Click to expand...
Click to collapse
That is actually the same way that I *used* to envision it.
Which has now been PROVEN incorrect. Or at least not applicable to the dream-bricks.
ezterry has conducted an experiment in the jtag thread based on this theory I have presented here. What he found is that a 1.x radio ***IS*** able to boot 1.33.2005 SPL SUCCESSFULLY!!!!
In other words, this theory I have presented has been confirmed through experimentation!
We don't know if this combination is suitable for actually booting a kernel, but we DO know that when flashing this combination in a manner where the recovery-boot flag is NOT set, that we ARE able to get into fastboot mode and flash the radio image! Meaning NOT BRICKED!!!! Despite a radio/SPL combination that was previously assumed to be a GUARANTEED brick!
Further (this had occurred to me before but I just remembered), keep this in mind, all dream IPLS are capable of booting all Dream SPLs, regardless of board version (not to delve into t-mo dream and rogers dream, different radio, so for this purpose, different device). I'm pretty sure too that, had there been as many IPLs/SPLs for the sapphire, the same would have been true (and we'd have more death spls to try on the dream).
What that tells me is that whatever the IPLs of all radios are reading for in SPLs, it's present across stock/eng/hard SPLs. If that thing that is being read from or booted to in those SPLs can be copied over to the Death SPL, then we'd have a death SPL that's bootable by all radios. Doesn't fix any current bricks though >.<
Click to expand...
Click to collapse
Keeping in mind of course, that there is still a possibility of a radio/SPL mismatch brick, what I believe at this point is that EVERY 32A/B radio image can be installed in conjunction with EVERY 32A/B SPL withOUT any kind of risk of bricking!
As long as the boot-recovery flag is NOT SET!!!!

xaueious said:
Not so sure about any SPL + radio combination working.
Specifically there were some really weird cases of bricks for users flashing new radio and SPL for Magic (1.76.X HBOOT, 6.35.X RADIO) on a 32B Magic. Afterwards their ROM authentication always failed for some reason.
So there are combination that actually do not work?
Click to expand...
Click to collapse
I wouldn't consider that weirdness to actually be a brick. At least not of the same caliber as the dream bricks where it won't respond to anything. Lets call something like that -- "borked".
Reason I wouldn't want to call it bricked is that it is still responding and doing *something*, despite the fact that what it does is failing.
In this case, you cite an authentication failure... suggesting that the 1.76.X SPL is *not an engineering SPL*. Use of a non-engineering SPL, I believe, will always leave you vulnerable to signatures and authentication errors.
I also have to believe that if the 1.76.X SPL *was* an engineering SPL, then it wouldn't worry about authentication.
My first recommendation to everyone is that they ALWAYS use an engineering SPL (i.e. with UNLOCKED FASTBOOT). In fact, the FIRST thing I would recommend to ANYONE rooting their phone is that their first step be to flash a "compatible" engineering SPL -- by compatible, I mean if your stock SPL was 0.95.0000, then you first flash SPL 0.95.3000 by whatever means necessary -- if it gets jammed into boot-recovery using such a similar SPL, then it won't be a brick. Following that, one can change to ANY engineering SPL using FASTBOOT to again be guaranteed not to brick.
If there is no engineering SPL available that is similar enough to the stock SPL to guarantee that the recovery will be compatible, then all bets are off -- in that case, you could end up borked.

xxmonsterx said:
I wish there was a thread "like" button like on fb lol nice thoery
Click to expand...
Click to collapse
erlern said:
Sorry, digression:
Can we petition for one? Seriously, I have been seeing comments on having a 'like' button over XDA since the new revamp.
Click to expand...
Click to collapse
If you look at the top of the screen, you will find a "rate thread" tab.

lbcoder said:
Yes. Sortof. Except that you mistake what a BIOS is. You are assuming the BIOS to be the setup program, whereas the BIOS is actually the first bootloader, at about the same level as some of the stuff in the radio image. The SPL on the phone would be roughly equivalent to GRUB.
Now as it happens, the phone's firmware actually *does* share some interesting similarities with your computer's bios -- specifically, that it *does* allow for you to flag different conditions. The problem with it is that it lacks the convenient SETUP program that your computer has... Note that it ***DOES*** have a setup program still though -- BLUE LIGHT MODE!!! Only problem is that we don't know the "password" for blue light mode! So it is like having a blank hard disk, a bios configured to boot that blank hard disk, and a PASSWORD you don't know on the bios configurations!
Click to expand...
Click to collapse
Thank you kind sir for clearing that up for me!
I'm thrilled to hear this is confirmed to be true as well.

Wow. Way to keep an open mind, both OP and ezterry. So any time we change radio or SPL versions you recommend doing so through fastboot instead of recovery zip flashes?

r4d14n7 said:
Wow. Way to keep an open mind, both OP and ezterry. So any time we change radio or SPL versions you recommend doing so through fastboot instead of recovery zip flashes?
Click to expand...
Click to collapse
Unless you know FOR CERTAIN WITHOUT ANY DOUBT WHATSOEVER that the recovery image you currently have installed will work with the new radio or SPL that you are flashing, then ABSOLUTELY I suggest (1) sticking with fastboot, and (2) sticking with engineering SPLs (of whichever variety you prefer, be it 0.95.3000 or 1.33.2xxx).
The cases where you DO KNOW with absolute certainty that you will have no compatibility issues is when changing the SPL from a "consumer" version to ***ITS*** corresponding "engineering" version, i.e. from 0.95.0000->0.95.3000 or from 1.33.0005->1.33.2005.
You should ONLY use recovery IF you have this degree of certainty.
Note: 1) I would recommend that you ***NEVER*** write a radio image using recovery, (2) ONLY EVER update from consumer SPL to ITS corresponding engineering SPL using recovery.
If you are running (any radio) + (consumer SPL) and are ABLE to use recovery to update to (same radio) + (engineering SPL corresponding to consumer SPL), then you can be certain that it ***WILL*** work.
So the process for going from, for example, a current version tmobile firmware right through to 1.33.2005 SPL + whatever is this:
1) ROOT as normal (i.e. RC29NBH+telnet, install custom recovery image)
2) copy engineering SPL 0.95.3000 update.zip to sdcard, reboot recovery, write 0.95.3000 -- this is safe because you KNOW that the recovery is compatible/functional with 0.95.x000 since that's what you have and you are using recovery,
3) reboot in FASTBOOT mode,
4) fastboot flash the desired SPL and/or radio image.
Doing this, I personally guarantee to within 99.999999% that, barring unexpected errors, like power failure during write or other equipment failure, that this procedure will *definitely not brick* (to within 99.999999% certainty -- I leave myself 0.000001% uncertainty, so don't hold me accountable).

Related

Kaiser intermittently stuck in SPL? - Possible solution and prevention!

so, I had some people contact me about the above problem. apparently some kaisers have this for some reason: they for no reason enter bootloader screen and won't boot OS.
the usual mtty commands ("set 16 0", "set 14 0") do not seem to help, and the whole thing is intermittent, sometimes you can still get the OS to boot. (NickCollision mentioned shorting the battery terminals after removing the battery helps for a while)
I patched the 3.29.Hard HardSPL (and the 3.56 too) to remove all enterbootloader reasons other than the usual stuff, keyboard combination and ruunbh tag.
both 3.29 and 3.56 will now say .Hard2 where the 2 means it is patched version =) so it will be less confusing to users.
UPDATE: you can try using force-usb SPL versions now, see new attachments!
UPDATE2: you can try 1.0.olipof-nostuckinspl-force-usb version and 3.31 hardspl (new hardspl, asked for by some users, of course with all these features)
3.29 is still very strongly recommended over 3.56, unless you have OS freezing issues with 3.29.
download from attachment and flash with SSPL to fix problem if you can get the OS booting at least once. also strongly recommended to flash this for prevention even if you have no problems yet!
what to do if you are still stuck in SPL - in that case, the spl overwrite protection will not let you flash. you should try to get the OS booting at least once. try with USB in, or after battery removal-reinsertion, those help increase chances.
if that doesn't work out, then see below what to do in that case:
the kaisdiagtest1.zip or the kaisdiagSD.zip in attachments may help solving the problem of reflashing the SPL to the patched version, if you absolutely can't get the OS to boot at least once.
the one of these allows you to reflash SPL via USB connection, the other one allows you to reflash from microSD card. this SD one is strongly recommended especially if you have problems with USB connection in SPL. it is also much more automatic.
usage STEP BY STEP (only if you cannot get the OS to boot not even one time!).
for diag and flash via microSD:
1. format a microSD to fat32 (use a card reader on a PC), copy the image to it from the KAISDIAGSD.zip in attachment (extracted filename KAISDIAG.NBH). this is basically an SSPL patched to load from SD without booting OS and then it will autoflash my hardspl again from SD.
2. put one of my hardspl's on the card too (in attachment, 3.29.Hard2 or 3.56.Hard2, 3.29 recommended). name this file as KAISIMG.NBH!!!
3. insert the microSD in the kaiser, then reset kaiser.
4. it should say Loading / Update in progress then reboot to a screen saying SPL 1.00.OliNex.
5. it should now flash in the KAISIMG.NBH. and will reset.
6. at this point it should boot to the OS, if it doesn't, then flash an OS. (of course delete the previous KAISDIAG.NBH and KAISIMG.NBH from the sd card and remove sd unless you opt to flash the OS from sd too)
for diag and flash via USB:
1. format a microSD to fat32 (use a card reader on a PC), copy the image to it from the kaisdiagtest1.zip (extracted filename KAISDIAG.NBH). this is basically an SSPL patched to load from SD without booting OS.
2. insert the microSD in the kaiser, then reset kaiser.
3. it should say Loading / Update in progress then reboot to a screen saying SPL 1.00.OliNex.
4. it should then work with RUU over USB (has USB force patch). but test with mtty first, make sure to disable usb connection in Activesync/WMDC! if PC doesn't see the device, try a USB replug. also, the USB should be plugged in all the time (except for when you replug)!
5. if it seems to have a good connection, then please now flash one of the SPL's posted in this post. after that you will be able to boot OS (of course reflash OS if you need to but the *first* flash *must be* SPL).
6. if this doesn't work (i.e. USB connection won't go), then go and check the SD version of the diag image, if you haven't already.
Wow Great work.
Thank you very much for your hard work! Going to sticky this for the time being.
Damnn,m nice work.
Thanks for this.
I have added it to my Wiki page on what to do if you get stuck at the bootloader. (Kaiser_Stuck_at_bootloader).
Anything you spot wrong with it feel free to modify (I asked GSLEON to take a look, but I don't know if he's had time).
Thanks
Dave
I can tell you that it does work and it did fix my kaiser!
Great work!
Nice!
I don't use the SPL, other than the one that came with my phone.
(Warranty....don't want to take a chance). Come October, when the warranty expires, I'll probably start flashing some of the cooked ones, plus, the Raphael
will probably be around by then.
I love you cmonex, let me know if you broke up with olipro
whats your thoughts on using the different SPL's to fix the random freezing issues that seem to hit the kaiser? I know my phone seems to work best with the newest SPL thats out right now from Jocky but it all could be in my head!
----Thank you cmonex, once again you show that your one of the amazing forces behind Xda! I hope there are little girls out there that want to be just like you when they grow up! That would be so cool a bunch of mini cmonex's running around we would have no issues with are WM devices then!
sakajati said:
I love you cmonex, let me know if you broke up with olipro
Click to expand...
Click to collapse
lol, sorry, no chance
austinsnyc said:
whats your thoughts on using the different SPL's to fix the random freezing issues that seem to hit the kaiser? I know my phone seems to work best with the newest SPL thats out right now from Jocky but it all could be in my head!
Click to expand...
Click to collapse
most probably that was because the older SPL's formatted nand too aggressively, so the end of the OS might get erased, which is no good. wasn't a problem before but the new OS's are bigger, so it affects them more likely.
as for the SPL versions, I don't really recommend 3.56 SPL, 3.29 seems much better in terms of available commands (though neither has task 2a for frankenkaiser fun ). did someone have any good experience with the 3.56 over 3.29? - I wonder why it is an option.
cmonex can u post the patch for the 3.56 it would be greatly appreciated, thanx
Get a new battery. The reason for this problem is the power manager keeps reseting the watchdog timer. Depending on when that happens the unit will either constantly reboot or enter bootload.
For some reason the BatSense line goes high and stays high. I haven't dissected the battery yet, but replacing it solved the problem.
htcfan2008 said:
For some reason the BatSense line goes high and stays high. I haven't dissected the battery yet, but replacing it solved the problem.
Click to expand...
Click to collapse
Not discounting the theory, just wanted to say that I had swapped out battery's during my testing with cmonex. So two diff battery's, same problem? Unlikely. As cmonex indicated shorting the terminals did have a positive effect, so you may be on to somthing re: the batsense line. Just that swapping batteries had no effect in my experience.
oOoOo my batsense is tingling hehe
Where the two batteries...
Nick Collision said:
Not discounting the theory, just wanted to say that I had swapped out battery's during my testing with cmonex. So two diff battery's, same problem? Unlikely.
Click to expand...
Click to collapse
...Samsung brand made in China, and both more than six month old? Then quite possibly they're both bad. (I forgot to mention in my other post that I replaced the battery with a non-HTC brand.) One way to tell is look at the battery edge on: if it has a bulge in the middle or looks "swollen" all around then it surely is bad.
I have found that using a non-HTC car or wall charger almost always and rather quickly kills the battery. It's not the charger voltage but the charging current profile that's the problem.
Anyway, good luck.
the bootloader can enter tricolour screen for a couple reasons other than the usual key combination or nbhload / enterbootloader tags in flash:
- if CPLD function returns 0xF
- or if debugboard is detected for whatever reason
- other configdata in flash tells it to do so
the last one can be excluded, because the problem is intermittent, and flash contents should be permanent.
then, I had Nick Collision run info 7 (which calls the same function), and it doesn't return 0xF, so maybe the second one.
I don't know what would cause that though, this battsense line sounds interesting.
to ofcourseimnaked: OK, i will do that soon.
Don't have a Kaiser SPL handy, but it must be using the same boot tags as Trin/Herm.
ClrRUUTagGoToOS
ClearGotoULTag
DeviceWarmBoot
CELoadComplete
NbhLoadSuccess
EnterBootloader
GoUpdateLoader
DeviceColdBoot
SetRuuNbhUpdate
These tags are programmed into flash to force boot in required mode.
Is this the config data you are referring to?
One other thing...
SPL and OS kernel debug log is stored in flash too, the reason for soft reset may be found in the log? It should be possible to dump the log with procdump once device boots to OS.
Don't know the offset for Kaiser Should be in the next block after the block with CID and boot tags though.
stepw said:
Don't have a Kaiser SPL handy, but it must be using the same boot tags as Trin/Herm.
ClrRUUTagGoToOS
ClearGotoULTag
DeviceWarmBoot
CELoadComplete
NbhLoadSuccess
EnterBootloader
GoUpdateLoader
DeviceColdBoot
SetRuuNbhUpdate
These tags are programmed into flash to force boot in required mode.
Is this the config data you are referring to?
Click to expand...
Click to collapse
yes, those mainly, and some flags.
but the issue is not them.
stepw said:
One other thing...
SPL and OS kernel debug log is stored in flash too, the reason for soft reset may be found in the log? It should be possible to dump the log with procdump once device boots to OS.
Don't know the offset for Kaiser Should be in the next block after the block with CID and boot tags though.
Click to expand...
Click to collapse
you mean task 37? btw, reset wasn't an issue here, but if someone shows up with a device constantly rebooting, we can look into that too..
note, CID is not really accessible directly from SPL anymore, MSM7xxx. (though right now I'm having fun finally dumping the protected radio nand)
Please explain me what it exacly is.
Is it better, most recent and fixed for Bootloader mode stuck version of HardSPL 3.29 which we can found on 'jockyw2001' thread?
Is it still HardSPL which let me flash any ROM for HTC Kaiser?
Thanks for all explains. Best regards.

Tell me if I got this right (my explanation for noobs about ROM flashing)

Some guy on another forum was asking me for help on customizing an AT&T Tilt (HTC Kaiser to you international folks) he just bought. This was my explanation. If it's not too much trouble, I would like for you experts to peruse it and tell me if it I got it all right.
Here is what I wrote to him:
Everything about customizing it can be found here: http://forum.xda-developers.com/forumdisplay.php?f=378
If you want to flash a ROM, start by reading this post: http://forum.xda-developers.com/showthread.php?t=433835
I'll spell out the process a little bit, though, so it's easier to grasp. First and foremost, there is a ROM. The ROM is basically an amalgam of other components. The three important ones are: SPL (I'll get to that), OS (yes, operating system), and Radio (tells your phone how to connect to networks). Now, when you first turn on your phone, there is a thing called an IPL (initial program loader) that checks to see that everything is in order on the hardware end (if you know computers, think of it as POST). After that, it passes control of the phone to the SPL (secondary program loader), which verifies that your ROM and OS is not corrupted, accepts triggers for other commands, and then loads and passes control of the machine to the OS.
The key is to tell the SPL that your ROM is not corrupted and that it is OK to load it. Obviously a legitimate ROM by AT&T or HTC will do the trick, but suppose you want one of the fancy ROMs out there, you'll have to trick the SPL a bit. There are two ways of doing this: (1) HardSPL and (2) SoftSPL.
A HardSPL is a "permanent" solution. It replaces your SPL; it's basically a cracked version of your SPL that removes the integrity checks that would normally be done. It's referred to as a permanent solution because it will not undo itself, nor can it be undone even if you flash a stock ROM (by AT&T or HTC), but there are ways of reverting back to the original SPL if necessary (I made this package that contains everything necessary, including instructions, on how to do this).
A SoftSPL (AKA SSPL, USPL - UpdateSPL, JSPL - JumpSPL ... all the same thing as far as I know) is a temporary solution that is basically done for the purpose of loading HardSPLs, but you can flash ROMs with it as well (this is generally not recommended, though). It's a standalone EXE file that you will load onto your phone. When executed, it will unload your OS, and load up a cracked SPL. This will allow you to flash an illegitimate ROM to your phone, namely a ROM that replaces your SPL with a cracked one.
After that, you're golden. You can SIM unlock your phone (if that hasn't been done already) if you want. You can SuperCID it (CID is Country ID; a SuperCID is tantamount to using a "region 0" DVD player), but that's not necessary for you, personally; only useful if you sell to someone overseas. You can start flashing custom ROMs that are pieced together by the fine folks at that forum I linked above.
In short:
1. Transfer SoftSPL to phone.
2. Run SoftSPL.
3. Flash HardSPL.
4. Flash custom ROM.​
Thoughts?
you could have given a simple answer
read the wiki and Search
Click to expand...
Click to collapse
jk lol, you listed the step very well
Its good to see you did so research already i just have a few "corrections" per say......
The spl just tells the phone that if there is a bad flash it needs to revert to the boot loader (basically what you said, but i made it a little simpler to understand for those reading)
jump spl is if you have a problem (such as the kaiser white screen issue) to jump start the spl flash
soft spl only protects the until you flash a new rom (kind of like a disposable hard spl)
Hard spl is permanent as stated
use this link to find out how to flash your first rom.
http://forum.xda-developers.com/showthread.php?t=433835
(this is the same as the second link you provided)
the link other link you provided is only for the kaiser rom section (therefore not everything there will work for every phone)
"In short" ,
You really only need to hard spl before flashing a rom (unless you prefer soft spl, or have problems flashing and need jump spl)

[NOT WORKING] Switch 1.76.0007 'Perfected' SPL to 1.76.2007 "Engineering' SPL!!!

NOTE: THIS MIGHT NOT WORK IF YOU INSTALLED THE HTC RUU USING A GOLD CARD IN THE FIRST PLACE... I'M LOOKING FOR TESTERS TO CONFIRM THIS.
I tried this when I first ended up with 1.76.0007, and it worked, but I didn't want to take a chance trying it again. I thought it was just a coincidence or my eyes were playing tricks on me. I was scared that I would brick my phone...
I finally got the guts to try it again and it worked!
Here's how...
You'll need:
- HTC 2.53.707.2 Test Build SAPPIMG.zip (Thanks Amon_RA!!)
http://rapidshare.com/files/267446145/2.53.707.2_-_sappimg.zip
- 1.76.2007 'Engineering' SPL
http://rapidshare.com/files/313034025/update-hboot-1.76.2007-signed.zip
- 6.35.07.29 32A Radio Image
http://rapidshare.com/files/313035429/radio-6.35.07.29-32A.zip
- Amon_RA Hero Recovery
http://forum.xda-developers.com/showthread.php?t=561124
- Gold Card
http://forum.xda-developers.com/showthread.php?t=572683
Caveats!!!
- Your splash screen will be changed to the HTC MAGIC screen and not your wireless provider's screen. I know of no way to change this.
- This might brick your phone... I was sweating bullets when I was running this on my phone because I wasn't sure it would work, and I'm still not 100% sure this will work for everyone. YMMV
Steps:
- Create your Gold Card! This is not just a suggestion. You need a proper gold card before starting. I used the card that came with my phone and it worked fine.
- Back up whatever you can from your existing setup. You can't go back and can't recovery anything here. Google sync should backup most of your stuff though.
- Shut off your phone and put the 2.53.707.2-sappimg.zip file on your gold card. Make sure it's named 'sappimg.zip'. Put the gold card in your phone.
- Turn on your phone using VolDown and Power. It will boot into HBOOT mode and within 10 seconds will scan your SD card. Do not press anything at this point! It will find SAPPIMG.zip only if it is named SAPPIMG.zip and not SAPPIMG.zip.zip... Get it? As it's loading SAPPIMG.zip it will show a blue progress bar on the right hand side of the screen.
- It will then check that SAPPIMG.zip is not corrupt.
- When prompted 'Do you want to start update?', press in on the trackwheel (Action key).
- The process will update the SYSTEM, USERDATA, BOOT, BOOTLOADER (SPL), RADIO_V2, RECOVERY and SPLASH.
At this point, you now have 3.22.20.17 32A Radio image and 1.33.2010 Engineering SPL. You can now flash any 32A Recovery and ROM and carry on like nothing happened and you didn't make a big mistake by flashing the HTC RUU. Next time don't be so impatient!
If you decide to stick with this Radio and SPL then I suggest flashing the Amon_RA 32A Recovery and picking a 32A ROM to run.
If you want to flash new HTC 3.03 ROMs using the 1.76.2007 Eng SPL and the new radio, then continue on. There are advantages to this, but at this point it's not for rookies.
Steps
- Download the recovery image, radio image and SPL (hboot) update into a folder of their own.
- Put the update-hboot-1.76.2007-signed.zip onto your SD card.
- Open a command prompt, navigate to the folder you saved all of the files in. This assumes that your Android SDK Tools folder is in your PATH environment variable)
- Boot your phone it fastboot by holding Back and Power.
- Once in FASTBOOT USB, type in these commands, hitting enter after each one.
Code:
fastboot flash radio radio.img
fastboot flash recovery recovery-RA-hero-v1.3.2.img
- Once it's finished, turn off your phone by pressing MENU.
- Start up your phone into recovery mode by holding Home and pressing Power.
- Apply the update-hboot-1.76.2007-signed.zip update.
- NOTE THAT THE RECOVERY REQUIRES YOU TO PRESS THE HOME KEY TO SELECT AN OPTION.
- Reboot your phone using the recovery option. Your phone will reboot back into recovery, and will format the CACHE. Don't worry about this, it's supposed to happen. If it doesn't boot back into recovery after a few minutes, pull the battery and power it on while holding the HOME key.
- Once it's booted into recovery mode, shut off your phone by pulling the battery.
- Start it back up into FASTBOOT mode by holding Back and pressing Power.
- You should now see the following on the screen:
Code:
SAPPHIRE PVT 32A ENG S-OFF H
HBOOT-1.76.2007
CPLD-12
RADIO-6.35.07.29
Aug 21 2009,18:19:15
If your phone doesn't display exactly this information, then you might have made a mistake along the way and should consider yourself lucky that your phone boots at all. Try again from the beginning.
At this point, you can enter the recovery menu and run the CursorSense update.zip from:
http://forum.xda-developers.com/showthread.php?t=592856
This was probably the closest I came to bricking my phone, but I'm sure it works now.
Good luck and happy rooting!
That won't work because if you Flashed via RUU it'll say that your version is older.
If you only flashed SPL/radio and not rest of the ROM i guess it could work.
it can break the Perfected SPL?
When i was flashed the sense-ui by htc?
mkrle said:
That won't work because if you Flashed via RUU it'll say that your version is older.
If you only flashed SPL/radio and not rest of the ROM i guess it could work.
Click to expand...
Click to collapse
You might have a point here... I thinks that maybe I didn't think this through entirely...
Would anybody be willing to test? Just to see...
Thanks,
Quite tempting to try, as I did flash via the RUU. Will look into it.
cursordroid said:
You might have a point here... I thinks that maybe I didn't think this through entirely...
Would anybody be willing to test? Just to see...
Thanks,
Click to expand...
Click to collapse
Main Version is older....
I've tried it, didn't work, but again who knows it might work for someone. There was a guy who said he got s-off SPL from a regular RUU so you never know.
Main version is older...
Main Version is older
I tried it on HBOOT-1.76.0007 (SAPP10000)
Hong Kong Sense Update from 17/11/09
Same problem NOTHING NEW:
Main Version is older
main version is older, flashed with RUU
i know 2.53.707 sappimg.zip file saved a few people, they also flashed official ruu, but get spl info like this: 1.76.0007(SAPP*****), and s-off.
but for most of us, we get this: 1.76.0007(SAPP10000), and s-on. therefore, we trying to use 2.53.707 sappimg.zip file and get "main version is older, update failed". and, if we use fastboot, it says "remote: not allow".
the only difference is the SAPP model text following 1.76.0007. if it's *****(all "*" symbols, not means any key), security is off, no version check, and it work! if it's 10000(maybe 50000 is also the same but i'm not sure), we stucked at version check.
so, what can we do...
tigerdigi said:
i know 2.53.707 sappimg.zip file saved a few people, they also flashed official ruu, but get spl info like this: 1.76.0007(SAPP*****), and s-off.
but for most of us, we get this: 1.76.0007(SAPP10000), and s-on. therefore, we trying to use 2.53.707 sappimg.zip file and get "main version is older, update failed". and, if we use fastboot, it says "remote: not allow".
the only difference is the SAPP model text following 1.76.0007. if it's *****(all "*" symbols, not means any key), security is off, no version check, and it work! if it's 10000(maybe 50000 is also the same but i'm not sure), we stucked at version check.
so, what can we do...
Click to expand...
Click to collapse
yes, i also found some person get this: spl info like this: 1.76.0007(SAPP*****), and s-off, if in this state, they can flash any rom/spl/radio.
can anybody find how to go to this state? if we can, we can do anything.
I dont know any thing further other than I got 0007 and s-on
so, all I can do is bump...
I have SAP***** for some time, even before i flashed 1.76 SPL but it's s-on, so i think it's not directly related.
P.S. I think i got SAP**** by playing around with different radios and all i can say is *don't* change (especially downgrade) radio unless you're sure what you're doing and/or have a matching SPL.
still no luck searching for a root cure for 1.76.0007
I accidentaly posted this to another thread (http://forum.xda-developers.com/showpost.php?p=5196720&postcount=7) although it was meant to be posted here:
I was missing the Android Market wich didnt come with the Singapore RUU so just downloaded the the HK RUU, ran it with a gold card (dont know if thats really neccesary) and got Market.
The point being - if people are on the Singapore official update, would it be somehow possible to "patch" the HK RUU files from the temporary folders where it stores the files for the update? To say, replace the original HBOOT with an ENG HBOOT (possibly *.2007?)?
Since Singapore rom version is lower than the HK one..:
Singapore: ROM Version: 3.03.728.4(For Indonesia, Malaysia& Vietnam only)
HK-E: ROM Version: 3.03.990.6
..possibly it would skip the "wrong main version" or whatever it says during the update..?
Am I onto something here?
No because the (zip) files are signed and perfect SPL won't accept flashing them if they are modified.
so is there a newer spl yet?
jamesyb0i said:
so is there a newer spl yet?
Click to expand...
Click to collapse
nobody, help we. amon_ra, and all the developers.. because don't help us??? we need help!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
We need either kernel exploit to get root, or HTC signed RUU with 3.x ROM and s-off SPL. period.

What the f did i do?! and how do i fix it?

So i think i know what i did wrong, but is there anyway to fix it? I have a 32b which i rooted with the "recovery-RA-sapphirev1.5.2H", then i tried to update the radio with the "update-radio-32A-6.35.08.29-signed" (i didnt read the "32A"). Then i tried to reboot the phone and it got stuck on the "Mytouch 3g" green start up screen, i cant get to the recovery image by holding home+end.
My understanding (please correct me if im wrong) to get the new Nexus ROM was that i had to;
1) Go the the 1.5.2 recovery image & wipe
2) Partition the card (and convert Ext2 to Ext3 or Ext4 depending on the ROM), reboot
3) Flash the new Radio, then reboot
4) Wipe, Flash the new SPL, then reboot
5) Wipe, flash the new ROM, and reboot
Im sure what i did was noobish...
Previously i had been using the 1.3.2 immage and had loaded Hero ROM's and tweeked Cupcake ROM's just fine, it was only when i had to update the radio and SPL was it that i found difficulty, mostly because i found too many and didnt know which one to use.
PLEASE HELP!!!
I'm willing to try anything. I hope i can get this fixed by this afternoon =,(
My first guess is that you are f**ked!
Only 2 "Nexus" roms I know that require new radio are for the 32A. And only new radio I know is for the 32A Magic!
Don't know where you got the instructions to upgrade your radio, but the ones I read stated that you have to flash radio, hboot, recovery in this sequence, and THEN reboot. Also, your recovery should be for 32B, dunno how you missed that one.
Try this: find your old radio image, your old hboot and recovery, boot in fastboot mode (back+power) and type in the following commands from the Android SDK tool directory:
Code:
fastboot flash radio your_radio.img <enter>
fastboot flash hboot your_hboot.img <enter>
fastboot flash recovery your_recovery.img <enter>
fastboot erase system -w <enter>
fastboot reboot-bootloader <enter>
You should now have rebooted back in fastboot mode. If that worked, try to reboot into recovery and see that works.
Once in recovery you can restore or flash another 32B rom.
See here for Engineering hboot images.
Download recovery for 32B
I found the link on theunlockr.com
developers.com/showthread.php?t=598973
And found instructions on youtube "ECLAIR 2.1 ROM REVIEW AND TUTORIAL !!!" and tweaked it slightly because i found a recovery image for my sapphire which didn't support either the spl or the radio, i forget... I've been up since 3am on Wednesday because of work and school, and now its 9am Thursday.
I was reading that 32b ROMs were working for the 32a, so i thought i might try a 32a since none of the links on Amon_RA's page developers.com/showthread.php?t=529019 were working for me.
I cant get to the fast boot menu... so that way doesnt work
Some_Biker_Guy said:
I'm willing to try anything. I hope i can get this fixed by this afternoon =,(
Click to expand...
Click to collapse
I think you are rather screwed. I believe the phone boots up the radio image before the bootloader and therefore you can't even get to flash a new recovery or radio image as the boot process is halted because of the defective radio image.
The only salvation I know if is a JTAG connection. This involves open up and soldering stuff to the mainboard of your phone. Since you're asking you probably not familiar with it I wouldn't recommend it to you.
you have a mytouch 3g right? if so, you flashed the wrong radio image. you flashed the ra(blahblahblah)H! not the ra(blah)G! "H" IS FOR HTC BRANDED "G" IS FOR GOOGLE BRANDED (THE MT3G). so that is your first issue. try to boot into fastboot and flash the RIGHT RECOVERY IMAGE.
wow as soon as I looked at this thread, you made so many mistakes on the first sentence lol. I hope you learn to read and not rush things next time ^^ Recovery H = 32A, Radio says 32A, and you have a 32B and now you can't get into fastboot? I'm 99.9999% sure it's bricked, but correct me if I'm wrong! 32B roms work for 32A when you port them over. Seems like you did almost no research at all.
You're understanding of what to do is right, but you didnt pick ANY of the right files
KAwAtA said:
wow as soon as I looked at this thread, you made so many mistakes on the first sentence lol. I hope you learn to read and not rush things next time ^^ Recovery H = 32A, Radio says 32A, and you have a 32B and now you can't get into fastboot? I'm 99.9999% sure it's bricked, but correct me if I'm wrong! 32B roms work for 32A when you port them over. Seems like you did almost no research at all.
You're understanding of what to do is right, but you didnt pick ANY of the right files
Click to expand...
Click to collapse
I agree with KAwAtA. You pretty much did the right steps (kinda) but you got the wrong files and now you got a nice brick. You should do research and know how to tell if your phone is 32A or 32B, why you should never flash the wrong radio/spl for your type of phone, and what ROMs are compatible with your hardware and why you should never flash the ROMs for another piece of hardware.
Well look on the bright side, since you bricked your magic, instead of trying out the "Nexus" ROMs, you can now buy a Nexus One for real but do not ROOt it because you might flash a 32B radio on it and make that a fancy brick.
damn sorry bro. does sound like everything that could have gone wrong went wrong for you. i also went to theunlockr to root my phone and add roms to it but i read those instructions like 3 times and watched the videos a few times when i first did it. oh well, you'll learn from this at any rate.
AndroidNoobie said:
Well look on the bright side, since you bricked your magic, instead of trying out the "Nexus" ROMs, you can now buy a Nexus One for real
Click to expand...
Click to collapse
that lucky SOB!
you can't get into recovery, that's fine, but can you boot into hboot and fastboot mode? if so, your phone will be fine, just have to fastboot flash the right junk on
Some_Biker_Guy said:
So i think i know what i did wrong, but is there anyway to fix it? I have a 32b which i rooted with the "recovery-RA-sapphirev1.5.2H", then i tried to update the radio with the "update-radio-32A-6.35.08.29-signed" (i didnt read the "32A"). Then i tried to reboot the phone and it got stuck on the "Mytouch 3g" green start up screen, i cant get to the recovery image by holding home+end.
My understanding (please correct me if im wrong) to get the new Nexus ROM was that i had to;
1) Go the the 1.5.2 recovery image & wipe
2) Partition the card (and convert Ext2 to Ext3 or Ext4 depending on the ROM), reboot
3) Flash the new Radio, then reboot
4) Wipe, Flash the new SPL, then reboot
5) Wipe, flash the new ROM, and reboot
Im sure what i did was noobish...
Previously i had been using the 1.3.2 immage and had loaded Hero ROM's and tweeked Cupcake ROM's just fine, it was only when i had to update the radio and SPL was it that i found difficulty, mostly because i found too many and didnt know which one to use.
PLEASE HELP!!!
I'm willing to try anything. I hope i can get this fixed by this afternoon =,(
Click to expand...
Click to collapse
Well, I BRICKED BRICKED BRICKED my other mytouch. Im talking where the computer wouldn't recognize it, wouldn't charge, turn on, splash screen, NOTHING. Wasn't the battery. If you can get to the screen (where you hold down volume and power) you can probably recover it. DON'T know if this would work but it may be worth a try read this link to get it un-rooted and then retry. http://theunlockr.com/2009/08/22/how-to-unroot-your-mytouch-3g/
iluvmymytouch said:
Well, I BRICKED BRICKED BRICKED my other mytouch. Im talking where the computer wouldn't recognize it, wouldn't charge, turn on, splash screen, NOTHING. Wasn't the battery. If you can get to the screen (where you hold down volume and power) you can probably recover it. DON'T know if this would work but it may be worth a try read this link to get it un-rooted and then retry. http://theunlockr.com/2009/08/22/how-to-unroot-your-mytouch-3g/
Click to expand...
Click to collapse
maybe u already tried.
dan-htc-touch said:
you can't get into recovery, that's fine, but can you boot into hboot and fastboot mode? if so, your phone will be fine, just have to fastboot flash the right junk on
Click to expand...
Click to collapse
he already said that he couldnt get into fastboot mode. most likely its a brick..
oshizzle1991 said:
you have a mytouch 3g right? if so, you flashed the wrong radio image. you flashed the ra(blahblahblah)H! not the ra(blah)G! "H" IS FOR HTC BRANDED "G" IS FOR GOOGLE BRANDED (THE MT3G). so that is your first issue. try to boot into fastboot and flash the RIGHT RECOVERY IMAGE.
Click to expand...
Click to collapse
I tried the "G" and it didn't work, so i tried the "H" and it worked. Fastboot didn't work...
Thanks everyone for you input... this is my reply to everyone since i cant reply to one/ a few at a time.
1) I knew how to root my phone, and did it multiple times. I also unrooted it a few times as well (just to get a fresh start and make sure i knew how to). I also loaded many different ROM's onto it including Hero and tweaked cupcake ROM's
2) Fast boot did not work, and the computer would not recognize the phone at any point.
3) The unlockr did a good job with instructions on how to root and unroot then loading the hero and cupcake rom's onto it but it had no explanation for loading the nexus rom onto it, although it did feature a link on where to get it. therefore i tried to piece together ways to update the radio and spl (this is where it all went to hell). i figured out that that is what i needed to do to run the nexus rom.
ok, ok now i know, wait for a full set of instructions for my specific phone to try to put the newest and coolest rom onto my phone... :/
4) i got it all taken care of, got "new" phone for free! so glad it worked out.

un-root a mt3g 1.2/fender

Hello...
I've been frantically googling and checking the forums, I have a mt3g 1.2 (3.5mm) that needs to be exchanged to t-mobile, I rooted following the stock fender w/ root method, and need to revert it back to the stock settings as shipped. So far, my search has turned up no resolve. I was hoping someone here could provide me with the proper sappimg.nbh to restore. I've got the one for the original MT3G, but it (as expected) damages touch-screen capabilities. Can someone please help?
As far as I know, it's not possible until T-Mobile releases an OTA update for either the Fender or MyTouch 3.5mm. That was explained in the rooting instructions here on XDA...
merlino211 said:
Hello...
I've been frantically googling and checking the forums, I have a mt3g 1.2 (3.5mm) that needs to be exchanged to t-mobile, I rooted following the stock fender w/ root method, and need to revert it back to the stock settings as shipped. So far, my search has turned up no resolve. I was hoping someone here could provide me with the proper sappimg.nbh to restore. I've got the one for the original MT3G, but it (as expected) damages touch-screen capabilities. Can someone please help?
Click to expand...
Click to collapse
If you use the stock rom http://www.theandroidkitchen.com/fileshare/MyTouch3g32A/?download=MT3G32AFender-1.0-fixed-signed.zip and then you should have touchscreen. It's only with custom roms that touchscreen does not work.
Couldn't you just flash the Mytouch splash image and turn in in like that?
It looks pretty stock after that.
shawn1224 said:
Couldn't you just flash the Mytouch splash image and turn in in like that?
It looks pretty stock after that.
Click to expand...
Click to collapse
... you got the splash image handy?
kbeezie said:
... you got the splash image handy?
Click to expand...
Click to collapse
you can find the stock mt3g splash screen if u search on here but not the fender one... i got the stock myt3g splash on my 1.2...
ceas909 said:
you can find the stock mt3g splash screen if u search on here but not the fender one... i got the stock myt3g splash on my 1.2...
Click to expand...
Click to collapse
That's what I'm saying though, no one seems to have the fender one. Far as the op's situation, might have tried flashing one of those "32A" roms, which obviously won't work at this point, probabbly best to just try the rom from my signature (the one linked as Rooted), which is basically the stock rom and touchscreen and all that should work.
kbeezie said:
That's what I'm saying though, no one seems to have the fender one. Far as the op's situation, might have tried flashing one of those "32A" roms, which obviously won't work at this point, probabbly best to just try the rom from my signature (the one linked as Rooted), which is basically the stock rom and touchscreen and all that should work.
Click to expand...
Click to collapse
yea he has a 1.2, so yea i think his best bet is to get the stock mt3g splash screen and the stock fender rom... the only problem is that between the fender and the 1.2 the build number is different..the 1.2 is 2.10.531.4 CL119339 release-keys where the fender is 2.10.531.3 CL111099 release-keys .... but a simple edit of the build prop could make it display the correct buid numbers in the about phone menu..
I've actually attempted to just replace the splash with the original mytouch splash. This can be achieved by applying a proper SPL that will allow it to be replaced... PROBLEM being that after repacing the SPL with the ones linked: theunlockr[.]com/2010/03/10/how-to-change-your-splash-screen/
Once this process is taken, the radio functions and all seems well, EXCEPT that now when I place calls, my speaker does nothing. Phones can receive the calls and hear me, but I hear nothing. the end result is to reflash the phone with the rooted rom, minus the mt3g splash... This part is where my frustration is kicking in as their guide claims this is specific for the fender/mt3g 1.2, but yet bricks the speaker somehow.
UPDATE!!
Click to expand...
Click to collapse
It appears that the guide on unlockr is wrong for this phone. I was successfully able to get the splash back on the phone by implementing the steps of adding the splash DURING the initial radio and recovery image restores, at which point the sappimg used is the engineering 2010. Once the splash was loaded at this point, I was able to continue with the install, install the rom, but a fresh install would *not* boot into the OS, just hung on a black screen after the animated "android" splash. Upon restoring a nandroid back-up, the phone booted to the OS in its formerly operational state, mt3g splash included.... I'm going to attempt a factory reset from the phones main options purely to see if it'll boot or hang on the black screen again.
Update 2.0
Click to expand...
Click to collapse
Methods were all successful, factory reset worked to bring the phone back to the android setup wizard WHILE retaining the splash screen with no blank screen as described earlier... Process was as followed:
Performing the unlockr guide; during the following steps:
fastboot flash radio radio.img
fastboot flash hboot hboot.nb0 (the 0 at the end of this line is a zero not an oh).
fastboot flash recovery recovery.img
fastboot reboot-bootloader
the phone is currently running the SPL for the Engineering SPL 1.33.2010... I modified the above process to reflect
fastboot flash splash1 splash.nb
fastboot flash radio radio.img
fastboot flash hboot hboot.nb0 (the 0 at the end of this line is a zero not an oh).
fastboot flash recovery recovery.img
fastboot reboot-bootloader
Recovered from the rooted fender stock image, which then took me to a blank screen. Recovered from a nandroid back-up, which restored the phone to my state just prior to (re)flashing. After nandroid backup is restored and successfully making calls, factory reset was done and test calls were successfully made from the freshly reset version of fender/wroot stock.... A bit hackish and unorthodox, but it answered the question I was so valiantly struggling to find resolve to.
It appears the stock fender /w root reverts the hboot version to the non-engineering, which functions fine with the speaker.... Hope this helps someone else who was in the same boat as me.
merlino211 said:
I've actually attempted to just replace the splash with the original mytouch splash. This can be achieved by applying a proper SPL that will allow it to be replaced... PROBLEM being that after repacing the SPL with the ones linked: theunlockr[.]com/2010/03/10/how-to-change-your-splash-screen/
Once this process is taken, the radio functions and all seems well, EXCEPT that now when I place calls, my speaker does nothing. Phones can receive the calls and hear me, but I hear nothing. the end result is to reflash the phone with the rooted rom, minus the mt3g splash... This part is where my frustration is kicking in as their guide claims this is specific for the fender/mt3g 1.2, but yet bricks the speaker somehow.
It appears that the guide on unlockr is wrong for this phone. I was successfully able to get the splash back on the phone by implementing the steps of adding the splash DURING the initial radio and recovery image restores, at which point the sappimg used is the engineering 2010. Once the splash was loaded at this point, I was able to continue with the install, install the rom, but a fresh install would *not* boot into the OS, just hung on a black screen after the animated "android" splash. Upon restoring a nandroid back-up, the phone booted to the OS in its formerly operational state, mt3g splash included.... I'm going to attempt a factory reset from the phones main options purely to see if it'll boot or hang on the black screen again.
Methods were all successful, factory reset worked to bring the phone back to the android setup wizard WHILE retaining the splash screen with no blank screen as described earlier... Process was as followed:
Performing the unlockr guide; during the following steps:
fastboot flash radio radio.img
fastboot flash hboot hboot.nb0 (the 0 at the end of this line is a zero not an oh).
fastboot flash recovery recovery.img
fastboot reboot-bootloader
the phone is currently running the SPL for the Engineering SPL 1.33.2010... I modified the above process to reflect
fastboot flash splash1 splash.nb
fastboot flash radio radio.img
fastboot flash hboot hboot.nb0 (the 0 at the end of this line is a zero not an oh).
fastboot flash recovery recovery.img
fastboot reboot-bootloader
Recovered from the rooted fender stock image, which then took me to a blank screen. Recovered from a nandroid back-up, which restored the phone to my state just prior to (re)flashing. After nandroid backup is restored and successfully making calls, factory reset was done and test calls were successfully made from the freshly reset version of fender/wroot stock.... A bit hackish and unorthodox, but it answered the question I was so valiantly struggling to find resolve to.
It appears the stock fender /w root reverts the hboot version to the non-engineering, which functions fine with the speaker.... Hope this helps someone else who was in the same boat as me.
Click to expand...
Click to collapse
Or you can just goto the thread in the link of my sig ("rooted"), you want to make sure when you're reading guides that they are for your specific phone, some people have bricked their fenders or 1.2 cuz they got the wrong radio/spl intended for the older MyTouch3G
I made sure to use the right guide on the unlockr, the problem came specifically from where they had the SLP change guide... Either way, problem is fixed now and it'll be in the hands of the t-mobile store tomorrow. If I ever doubtfully get a question about the root from them after it ships back, I'll play dumb and inquire if maybe someone else did it while it was waiting to ship
merlino211 said:
I made sure to use the right guide on the unlockr, the problem came specifically from where they had the SLP change guide... Either way, problem is fixed now and it'll be in the hands of the t-mobile store tomorrow. If I ever doubtfully get a question about the root from them after it ships back, I'll play dumb and inquire if maybe someone else did it while it was waiting to ship
Click to expand...
Click to collapse
i hope they dont catch the build number being different.. as i stated in eairler post the build nmbers in the about phone menu are different from the fender and the 1.2
ceas909 said:
i hope they dont catch the build number being different.. as i stated in eairler post the build nmbers in the about phone menu are different from the fender and the 1.2
Click to expand...
Click to collapse
In my experience most sales reps are completely ignorant of that kind of thing, changing the boot screen may be enough to make em go along with it. IF you're dealing directly with the company on the other hand that may be a different story.
It's being shipped back via the store under the 14 day buyers resource. I have had two of these so far, both have suffered from the screen oddly self-scrolling... Figure maybe a bad lot produced, as t-mobile tech support has not even heard of such a problem before. I finally settled on buying a nexus one, which arrives tomorrow. The store doesn't even check the phones out except to make sure all parts and accessories are contained in the box, there it will sit for (they said, roughly a week) before it's shipped back to T-mobile. By then, I figure liability of the phone is officially out of my hands.
merlino211 said:
It's being shipped back via the store under the 14 day buyers resource. I have had two of these so far, both have suffered from the screen oddly self-scrolling... Figure maybe a bad lot produced, as t-mobile tech support has not even heard of such a problem before. I finally settled on buying a nexus one, which arrives tomorrow. The store doesn't even check the phones out except to make sure all parts and accessories are contained in the box, there it will sit for (they said, roughly a week) before it's shipped back to T-mobile. By then, I figure liability of the phone is officially out of my hands.
Click to expand...
Click to collapse
I think you mean buyer's remorse, also I was under the impression that Limited Editions could not be 'returned' , merely exchanged or serviced.
If you don't have a contract, you could sell the phone once you put the working stock rooted rom onto it.
jesus... some of you really hurt my head over this phone.
So flashing the stock mytouch splash screen doesnt work if youre on a 1.2 or are most of you guys worrying because you have fenders?? Also can someone give me the mytouch splash screen???
You can find it here
http://theunlockr.com/2010/03/10/how-to-change-your-splash-screen/

Categories

Resources