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.
Related
I ran it according to farias instructions I thought. It flashed but now I cant install anything and I cannot write to the storage card or the phone, any cab i try to install is unsuccessful and I cannot save any files to the storage card or the phones memory.
And it appears that I cannot flash the rom again. Am I screwed?
What is you IPL / SPL? IS your phone a G3 or G4? Can you get to the bootloader? (turn off your phone (pull the battery if you have to) then hold the camera key down while you turn it on). You can flash directly to the bootloader (even though activesync won't connect.
BTW: If this stuff makes you nervous, you probably shouldn't be cooking... Your phone will do all sorts of weird stuff when you screw up a build. And you should really know how to recover from most things that can happen...
I have done this before, this is the first time I have ever had a problem. my IPL/SPL is 2.26. And the phone is unlocked.
beowolf said:
I have done this before, this is the first time I have ever had a problem. my IPL/SPL is 2.26. And the phone is unlocked.
Click to expand...
Click to collapse
ok, cool... wasn't sure... So can you get to the bootloader?
yes I can get to it
I am flashing back to the t-mobile 2.26 rom. Working so far, I will leave the cooking alone. Can you recommend a good wm6 rom that doesnt have any problems?
"doesn't have problems" is the catch
I'm partial to my own Crossbow Reloaded ones, but they aren't perfect. If you don't hit the keypad issue with 1.7 though, its pretty close
Core 2.0n is very good and nice and clean.
Also NBD and Wizard Mobile 6 are both supposed to work well.
The new "official" rom we are playing with is beta, but I have to say its really fast and we aren't seeing much wrong with it (but its only been 12 hours since its been released). There are a couple of issues that are fixed with cabs (CommManager for one).
As for cooking, you probably eith had something wrong in a .rgu or somesuch. Just takes a number of builds and flashes to get it right to where it boots (then you debug what you forgot in packages and start over )
Many of you are eagerly waiting for this: HardSPL v3.07, v3.28, v3.29 and v3.56...
Run a SSPL (aka JumpSPL) and then flash the HardSPL.
Practically all questions are answered in kyphur's excellent F.A.Q. in the next post
Brought to you by JockyW
Have fun !
EDIT:
* The "force USB" versions are only for a tiny minority who have USB connectivity issues.
* SPL3.56 is part of the latest AT&T Rom which is dated June 6. 2008
* SPL3.07 was included in a recent Vodafone RUU.
F.A.Q.
How to Install 3.2x.Hard SPL:
1. Plug the device into your PC
2. Copy Jump/Soft to your device. use JumpSPL If you have the "White Screen" issue, if you don't, you can use SSPL-KAIS.exe.
3. Take out your SD card & SIM Card.
4. Run Jump/Soft SPL on your device
5. Wait for the bootloader screen to appear and "USB" to show.
6. Right-click activesync, go into connection settings and ensure Allow USB Connections is unchecked
7. Unplug your device from the USB port, wait 5 - 20 seconds, plug it back in.
8. Run KaiserCustomRUU.exe and flash the SPL
If you have problems with the above process, try this:
1a. download the attached files
1b. pull out the battery and reinsert it (this step *is* important)
1c. connect your PC to phone with a USB cable
2. REMOVE SIM and SD CARDS !!
3. copy JumpSPL1.56-KAIS.exe to your device and run it (make sure the USB cable is still connected). If you still get a white screen then reset your device and now try JumpSPL1.93-KAIS.exe or JumpSPL1.94-KAIS.exe
4. after a few seconds "USB" appears on the phone display
5. unplug and replug the usb cable
6. deselect "Allow USB connections" in Activesync connection settings
7. now flash hardSPL (run KaiserCustomRUU.exe from flash-hardSPL.zip on your PC)
Notes:
With the JumpSPL you should *not* flash radio roms, OS roms or full roms. The JumpSPL is only needed to flash a HardSPL (or SPL)
FOR ANYONE WITH QUESTIONS ABOUT WHAT THIS IS FOR, WHY YOU WOULD NEED IT, OR HOW TO PERFORM SPL PROCEDURES: Read This Wiki page
Q: Can I use with with Wizard/Hermes/"Insert other device here"?
A: No, this is only for Kaiser/TyTN2/Tilts.
Q: Do I have to use Jump/Soft SPL?
A: Yes.
Q: Do I have to install HardSPL v1.x before installing HardSPL 3.x?
A: No, you can follow this process to install HardSPL 3.x on a factory device without ever installing HardSPL 1.x.
Q: Will I have to reflash my OS/Radio or set-up my software again after flashing this?
A: No, changing SPL doesn't touch either the Radio or OS.
Q: Do I have to use this BEFORE I flash a WM 6.1 Rom?
A: Not really, you can flash it before or after upgrading the OS/Radio to WM 6.1 but you may experience "Screen-Freeze" until you upgrade your HardSPL.
Q: Since this is SPL for HTC Branded Devices will it work with AT&T's Tilt?
A: Yes.
Q: Does this SPL support AT Command Mode?
A: No.
Q: Does the 3.2x HardSPL support "Task 2a" via MTTY?
A: No, HTC took it out.
Q: What is the difference between this & HardSPL v1.x?
A: HardSPL 3.x should be used with WM 6.1 Roms, HardSPL 1.x should be used with WM 6.0 Roms. Both HardSPL prevent you from accidently flashing a new SPL (you must use Jump/Soft SPL for this) and SuperCID your phone.
Q: What is the difference between 3.28 & 3.29 SPL?
A: Just speculation at the moment but there appears to be a minor change, possibly a hotfix. Both SPLs seem to work fine with all models & WM 6.1 Roms but 3.29 is included in the AT&T Rom and a few of the HTC Roms.
Q: Should I install 3.28 or 3.29?
A: Honestly it probably makes little difference but you can always check the SPL that shipped with the rom (or BaseRom if using a cooked Rom) you are running. I have AT&T Tilt running my Rom (using AT&T 3.51 Base) with 3.28 and have no problems including screen-freeze. Note: some members recommend 3.28 for HTC Roms & 3.29 for AT&T Roms.
Q: Does this HardSPL fix the "Screen-Freeze" in WM 6.1 Roms.
A: Yes, everyone using the new HardSPLs has reported it resolved the issue.
Q: What about WM 6.0 Roms?
A: Some users have reported having the "Screen-Freeze" issue on WM 6.0 Roms and fixing it with the New HardSPL. It's worth a try but definately recommended to use the same generation SPL & ROM in most cases.
Q: What about "Diamond" Roms?
A: As the Diamond Ports are WM 6.1 Roms and the SPL has the same effect, eliminates "Screen-Freeze".
Q: What was the cause of the freezings with the older hard-spl and what did you do to fix this
A: SPL initializes a lot of subsystems (power management, touch screen, lcd, etc). The newer SPL probably has contidional code that would handle variations in hardware (if they exist). I'd also think that the 3rd gen SPL would be geared more towards the 3rd gen OS & Radio needs which would explain the fix working as well as it does. Reminds me of the Wizards days when we were running 2nd & 3rd gen OS but had to stick to lower radios because we were intentionally not upgrading SPL (due to HTC Locks & such in the 2nd gen SPL).
Q: Can I flash this via SDCard?
A: Technically, you should be able to BUT flashing SPL is a "dangerous" process for your phone so you really should use KaiserCustomRUU.
Q: Where can I get Jump/Soft SPL?
A: http://forum.xda-developers.com/showthread.php?t=354061
Q: I can't flash a cooked Rom after installing 3.x.Hard SPL, help.
A: See the next question, if you didn't successfully change to SPL03.2x.Hard then try again.
Q: How can I be sure that I've successfully changed to SPL-3.x.Hard?
A: Get into your Bootloader (hold down camera+power buttons while inserting stylus for approximately 3-5 seconds). It should show SPL-3.28.Hard or SPL-3.29.Hard on the second line of text on your screen. If not then you didn't flash the new HardSPL, try again.
Q: Using Jump/Soft SPL shows "unknown device" when hooked up to usb.
A: Try the SSPL attached to the first post.
Q: Could you clarify what the "Force USB" does?
A: Some users managed to nuke configuration parameters which determine the default connection mode. They are stuck in serial mode. The "force usb" version of SPL corrects this. Of course it would be better to figure out which parameter(s) are at fault and correct these, but that would take time and experiments and more over a higher risk to really brick a device.
Q: I'm stuck in the Bootloader (Tri-Color) Screen with "ruunbh" text in the upper right corner.
A: To get rid of the RUNNBH error:
Download an ORIGINAL (not cooked ROM) for your device from here: http://wiki.xda-developers.com/index...me=Kaiser_ROMs
Choose one appropriate for your device (AT&T tilt / HTC TyTnII). 6.0 or 6.1 shouldn't matter.
Download that and flash it...it should work and get you back to a working phone. Then you will have to try the HardSPL procedure again.
Q: Does this "Security Unlock" my Phone?
A: No, Security Unlocked is something different from HardSPL.
Check here on how to do a security unlock: http://forum.xda-developers.com/showthread.php?t=361236
Here are the files that you will need to do the process:
http://www.4shared.com/file/46447471/7ae96b57/Jockyw2001_HardSPL_-_SuperCID.html
Just follow the steps in the supercid. I have included the .txt file that Jockyw2001 included.
Be sure to flash the "SPL-1.1.JockyW" as the process won't work while SPL-3.2x.Hard is installed.
Q: Where did my post in this thread go?
A: All useful information was consilidated into this single post. Everything else was deleted.
Troubleshooting:
When all else fails, try these...
Use a Windows XP Machine (not VISTA).
Delete all USB peripherals and root hubs from Device Manager, reboot, let everything be re-detected, reboot again and then plug your Tilt in again.
Make sure you have removed both the SDCard and your SIM Card.
HardSPL v3.29.0000 added
HardSPL v3.29.0000 added.
I don't know which one is better. The version number tells me that they prolly hotfixed an error in 3.28.
Enjoy!
hey Jocky! I kinda miss the SPL-1.1.JockyW tag in your SPL, lol.. donation coming in as promised!
Confirmation number: 6CM53141XF789163M
pfcsabre said:
hey Jocky! I kinda miss the SPL-1.1.JockyW tag in your SPL, lol.. donation coming in as promised!
Confirmation number: 6CM53141XF789163M
Click to expand...
Click to collapse
Thanks! First donation from 'old europe'
Work worthy of donation!!
New SPL has done the trick and eliminated the laggy freezes in L26 v3 for me!
Many thanks jocky......worthy of the small donation (Paypal Confirmation number: 99A446736N006110A) that I can afford and great stuff!
FAQ Updated, thread cleaned...
I'll be leaving Kudos, Donation notices & such after this but all Question/ Answers will get cleaned & integrated into the FAQ.
BTW, Jocky had mentioned that North America as consistantly been the lion's share of support for his work . I do encourage everyone who uses this to send a little something his way as it does take both time & skill to provide these tools. Even a couple of bucks goes a long way to show your appreciation.
kyphur said:
I'll be leaving Kudos, Donation notices & such after this but all Question/ Answers will get cleaned & integrated into the FAQ.
BTW, Jocky had mentioned that North America as consistantly been the lion's share of support for his work . I do encourage everyone who uses this to send a little something his way as it does take both time & skill to provide these tools. Even a couple of bucks goes a long way to show your appreciation.
Click to expand...
Click to collapse
Chaulk another one up for North America, donation sent, thanks Jocky!!!
Confirmation number: 7YH40824J6586891R
Donations
Just making sure N. America stay on top!
Nightly Thread Maintenance.
FAQ Updated....
Posts removed....
it worked!
worked without any issues...i did the 3.29 on dutty rom even doh i should do htc but reviews show little difference and i have att phone ... reponse is slight better i know for sure...but not AMAZING like people saying...will keep u updated!
Seems like Kyphur is a bit fast on the delete button
Anywhoo, just wanted to re-post that I've sent a small donation off to JockyW.
Unique Transaction ID #56B84509V76451713
Thanks for everything and keep up the great work!
_Alex_ said:
Seems like Kyphur is a bit fast on the delete button
Anywhoo, just wanted to re-post that I've sent a small donation off to JockyW.
Unique Transaction ID #56B84509V76451713
Thanks for everything and keep up the great work!
Click to expand...
Click to collapse
Hehe...Kypher would it be better to just lock this thread?
Mass deleting posts just doesn't sit well with me either.
probably less work for you too.
your call
Thanks, worked well as well. Now no freezes.
Kudos to kyphur for perfect moderation and orchestration of this thread and to all who donated of course. The fact that nearly all donations are from north-america is prolly because these SPLs are solving the AT&T rom issues.
Whatever, I appreciate it!
Yeah great work!! sure to donate..
It works like a charm. Happy to donate.
From the Netherlands 4M744925453729221
gqstatus0685 said:
Ok what I show is:
KAIS*0 MFG
SPL-1.0.0liPof
CPLD-8
I installed this L26 diamond V5 onto my device and it says includes newest version 3.29. Freezes like crazy and very annoying. I know it's fixable.
Click to expand...
Click to collapse
You didn't successfully install 3.2x.Hard SPL, you're still on the 1.0 version.
Try again, read the FAQ carefully, everything you need is (should) be there.
gqstatus0685 said:
Ok what I show is:
KAIS*0 MFG
SPL-1.0.0liPof
CPLD-8
I installed this L26 diamond V5 onto my device and it says includes newest version 3.29. Freezes like crazy and very annoying. I know it's fixable.
Click to expand...
Click to collapse
Your bootloader screen should show:
KAIS100
SPL-3.28.Hard
CPLD-8
or SPL-3.29.Hard if you've used 3.29.
Donation made!
confirmation nr. 9A097724M3643491F
Has anyone successfully flashed via microsd? My USB port has been dead for awhile now.
I'd like to fix my freezing problems.
Ok, so rapid short overview:
I tried to flash my O2 Stellar with the new HTC wm6.1 Kaiser ROM. The HTC website, for reasons unbeknowest to me would only give me the italian ROM, so I got the english variant off rapidshare.
Tried to flash, everything going well, until (at 0%) it turns around and says the ROM isn't compatible. I figure this requires some HardSPL goodness, but the installer for THAT jumps to 100% in seconds and doesn't seem to do much. Tried a soft SPL (SSPL-KAIS.. no white screen issue), hey-ho, presto! ROM tries to install.
...hangs at 15%, device reboots to the rainbow. Displays:
KAIS130
SPL-1.82.0000
CPLD-8
In the corner: RUUNBH
I've read ALL the other threads on this issue to try and restore the phone. I've tried ALL the O2 ROM dumps people have supplied (all two of them I could find) and every time it either had an error 262 (comms error) at 0%, or got as far as 1% or maybe 2% and then error 29-something (ROM not compatible/suitable for phone). O2 originals, cooked ROMs, HTC updated ROMs, ROMs for different vendors (those produced "wrong vendor" errors). NOTHING IS WORKING!! *tears out hair*
Apparently connecting with mtty and typing "boot" causes the device to try booting the original rom before the flash. I figure maybe I could boot it, copy the phone's OWN rom (c'mon, THAT rom would HAVE to work, right?!) and reflash it. So I fire up mtty, tell it to boot. But it doesn't. Instead, the screen sort of.. fades, between the SPL and pure white (looks almost like display is broken!) and mtty displays:
...OH. Ok, just tried again to copy mtty text and now it's booting.
This is what mtty displays as the phone boots:
Cmd>boot
InitDisplay: Display_Chip=1
No card inserted
OSSIReadBack ++
Read SI data from flash success
tail signature match
Checksum match
UserStorageSIPreload ++
Click to expand...
Click to collapse
Ok, focus of the thread changing, does anyone know if I could dump the ROM and flash it? I'm about to find out anyway but if someone knows this is foolish please let me know
Cheers, everyone.
Not looking good for you.
Sounds like you flashed a ROM into the SPL at a guess. You shouldn't flash anything except SPL's when you are in Soft SPL's (SSPL or JumpSPL).
Try PM'ing a guy called GSLEON3. He's a mod here and for a beer or two will probably set you right.
@GSLEON3, I really should figure some of this out someday myself. That way I can help rather than just pointing users to you.
EDIT:
You have tried the stuff in here first? http://forum.xda-developers.com/showthread.php?t=371154
Ta
Dave
DaveShaw said:
Sounds like you flashed a ROM into the SPL at a guess. You shouldn't flash anything except SPL's when you are in Soft SPL's (SSPL or JumpSPL).
Click to expand...
Click to collapse
In retrospect that's exactly what I did, yeah. Luckily the boot command worked on the fourth try (as above... guess perseverance gets results) and the phone worked enough for me to retry the HardSPL install (which worked). Then I was able to flash the O2 Stellar ROM found elsewhere in this forum which allowed the phone to boot normally again. THEN I was able to flash the english HTC Kaiser 6.1 WWE ROM.
That thread linking to MTTY techniques for formatting may have come in very useful, I will remember that one!
Go and "security unlock" your device now. It makes it almost unbrickable.
There is a app called FrankenKaiser which can re-install your SPL if you decide to format it (not that you would want to under normal circumstances)
Ta
Dave
There are now a large selection of Kaiser Hard SPL's floating about. I am making this thread as a collection for all of them and the instructions for flashing them.
Explanation
WM Version - Different SPL's perform better depending if you are running WM6.0 or WM6.1. If you are using a WM6.0 ROM, you should be using a WM6.0 Hard SPL (v1 is recommended). If you are using WM6.1 any 3.* SPL is recommended.
Hard SPL Version - Most WM6.1 ROM's are based of a 3.* release by HTC / ATT. The 3.* Hard SPL version should match this the best it can.
MFG - Manufacturing. This SPL supports more commands (such as rtask a)
jockyw2001 - Any Hard SPL made by jockyw2001 (WM6.1 versions)
cmonex - Any Hard SPL made by cmonex.
DaveShaw - Any bootloader patched by me. Will be the same as cmonex's because I copied her changes from previous versions - all credit to her .
Force USB - These SPL's have a fix to force the USB to work if it is not working for some reason.
nostuckinSPL - These SPL's have a fix to prevent you getting stuck at the bootloader as often.
Versions
Windows Mobile 6
-Hard SPL V1 (1.00.OliPof) [MFG] by pof / Olipro - Download and Instructions in the linked thread.
-Hard SPL V1.1 (1.1.JockyW) [MFG] by jockyw2001 - Download and Instructions in the linked thread.
-Hard SPL V1 nostuckinSPL Force USB [MFG] by cmonex - download only.
Windows Mobile 6.1 - All links are to the downloads, instructions to follow.
jockyw2001 (.hard)
3.07 Hard SPL / Force USB
3.28 Hard SPL / Force USB
3.29 Hard SPL / Force USB
3.56 Hard SPL / Force USB
cmonex (.hard2)
3.29 Hard SPL nostuckinSPL / Force USB
3.31 Hard SPL nostuckinSPL Force USB
3.56 Hard SPL nostuckinSPL / Force USB
DaveShaw (.hard)
3.34 Hard SPL nostuckinSPL Force USB
Instructions
If this is your first time flashing an SPL, take some time to read up on the other stickies (mskip's in particular) and wiki pages, this is more of a reference thread.
How to Install A Hard SPL:
Plug the device into your PC
Copy JumpSPL (either 1.56, 1.93 or 1.94) to your device.
Take out your SD card & SIM Card.
Run Jump SPL on your device
Wait for the bootloader screen to appear and "USB" to show.
Right-click activesync, go into connection settings and ensure Allow USB Connections is unchecked
Unplug your device from the USB port, wait 5 - 20 seconds, plug it back in.
Run KaiserCustomRUU.exe and flash the SPL
If you have problems with the above process, try this:
Download the attached files from the first instructions
Pull out the battery and reinsert it (this step *is* important)
Connect your PC to phone with a USB cable
REMOVE SIM and SD CARDS !!
Copy JumpSPL1.56-KAIS.exe to your device and run it (make sure the USB cable is still connected). If you still get a white screen then reset your device and now try JumpSPL1.93-KAIS.exe and if you still get a white screen then reset your device and now try JumpSPL1.94-KAIS.exe
After a few seconds "USB" appears on the phone display
Unplug and replug the usb cable
Deselect "Allow USB connections" in Activesync connection settings
Now flash hardSPL (run KaiserCustomRUU.exe on your PC)
Notes:
With the JumpSPL you should *not* flash radio roms, OS roms or full roms. The JumpSPL is only needed to flash a HardSPL (or SPL)
Upgrading SPL via SD Guide - Only works if you already have Hard SPL.
Make sure your microSD is Formatted to fat32 (you dont have to delete all files but it is safer if you do)
Download the SPL you want to flash from the links above.
Rename the NBH file you downloaded to KAISIMG.nbh.
Download KAISDIAG.nbh from here.
Insert the microSD Card into the phone
Hold in the Power and Camera buttons, then press the reset button with the stylus for about 3 seconds until the BootLoader screen appears
It should say Loading / Update in progress and then to a screen saying SPL 1.00.OliNex
It should now say Press Power Button to flash or just flash the KAISIMG.NBH and then reset
At this point it should boot to the OS, if it doesn't then flash an OS (delete the previous KAISDIAG.NBH and KAISIMG.NBH from the SD Card and use Flashing Rom from MicroSD Card method)
After the Operating System loads, DELETE the KAISDIAG.NBH and KAISIMG.NBH files
FOR ANYONE WITH QUESTIONS ABOUT WHAT THIS IS FOR, WHY YOU WOULD NEED IT, OR HOW TO PERFORM SPL PROCEDURES: Read This Wiki page
FAQ (Not 100% applicable to this but a good source).
Thanks (in order of appearance)
pof
Olipro
jockyw2001
cmonex
Kyphur
mskip
I'm off home now I might not be back on for a while.
Post any problems here and I'll update / clean up this thread when I get home.
Ta
Dave
Very nice! Thanks for putting it all in 1 place!
Removed. I flashed 3-4 times and it finally took. Thank you for your help. Anyone else have a preference on a HARD SPL?
Hyden121 said:
Removed. I flashed 3-4 times and it finally took. Thank you for your help. Anyone else have a preference on a HARD SPL?
Click to expand...
Click to collapse
Was just about to reply. Glad you sorted it. I've had problems changing SPL before. The second set of instructions using Jump SPL worked. Also cmonex's KAISDIAG.nbh method works everytime.
I'm using 3.34 Hard SPL for 2 reasons.
1. The ROM I'm using is is based on the 3.34 ROM.
2. I made it (with cmonex's help ).
Dave
I saw that. I am using it as well but was curious if the 3.56 SPL was better in anyway. Either way it is great to finally have a new SPL and it only took me 1 year.
thanks dave! i've flased it and all seems well. my keyboards only have 2 keys you have to press a bit more firmly than the rest rather than 9 with 3.29 so that's much better!
had trouble flashing via customruu so did the microsd card thing. kinda weird though, last night, i couldn't get the microsd approach going with 3.29cmonex. so i flashed via customruu and it worked. now with 3.34, i couldn't get the customruu to work, so i did the microsd approach. anyway, so long as it works!
Thanks DaveShaw, you've really helped new-to-Tytn2 people like me a lot. A good beginning to the ROM experiencing journey
3.34 hardSPL tested ok for my kaiser,thanks to Daveshaw.
nice post, can anyone post his/her experience with the SPLs, meaning if better speed, battery life,....etc
thx dude
Could you explain what is the major advantage of using your 3.34 HardSPL toward to the other Hard SPLs?
I still have no idea about those HardSPLs differences so I'm using latest(? 3.54).
Thank you.
kurobosi said:
Could you explain what is the major advantage of using your 3.34 HardSPL toward to the other Hard SPLs?
I still have no idea about those HardSPLs differences so I'm using latest(? 3.54).
Thank you.
Click to expand...
Click to collapse
All Kaiser ROMs (Cooked or not) are based on a Official release (some cooked roms are based on more than one). Here's a list of the official releases: Kaiser ROMs.
You'll notice the version numbers are all 3.* for the WM6.1 ROM's. People have noticed if you are using the SPL version that matches your ROM version you get less screen freezes.
Sometimes you can't match them perfectly, so a little trial and error can help you find the best match.
Hope this helps.
Dave
DaveShaw said:
All Kaiser ROMs (Cooked or not) are based on a Official release (some cooked roms are based on more than one). Here's a list of the official releases: Kaiser ROMs.
You'll notice the version numbers are all 3.* for the WM6.1 ROM's. People have noticed if you are using the SPL version that matches your ROM version you get less screen freezes.
Sometimes you can't match them perfectly, so a little trial and error can help you find the best match.
Hope this helps.
Dave
Click to expand...
Click to collapse
great work dave but i have to ask something...
is there such a thing as the ultimate spl? meaning it's a bit troublesome to keep changing spl's based on the original builds of our cooked roms...since they keep coming from different sources...
from ur experience, which spl is the stablest with the newer cooked roms..
i've been using cmonex's 3.29 since it came out and to me it seems compatible with any rom i throw at it...
is ur 3.34 the new 3.29 hard2?
mazin13 said:
great work dave but i have to ask something...
is there such a thing as the ultimate spl? meaning it's a bit troublesome to keep changing spl's based on the original builds of our cooked roms...since they keep coming from different sources...
from ur experience, which spl is the stablest with the newer cooked roms..
i've been using cmonex's 3.29 since it came out and to me it seems compatible with any rom i throw at it...
is ur 3.34 the new 3.29 hard2?
Click to expand...
Click to collapse
No idea. I've been using it for a while now but I don't flash cooked ROMs much at the moment
Try it for a bit and it you like it keep it
Only cmonex knows what's going on inside the SPLs.
Ta
Daev
Great work dave, seems you are quite good in organising things, Was missing such a nice piece of thread & must have started had I been so much in to it. Thanks again. Good luck.
DaveShaw said:
There are now a large selection of Kaiser Hard SPL's floating about. I am making this thread as a collection for all of them and the instructions for flashing them.
MOD EDIT Snip...
Click to expand...
Click to collapse
Hi! I have weird problem with HTC Kaiser (or HTC TyTn II).
At the boot of Windows Mobile 6.1 i got the message "the device is clearing storage..." and then the device shutdown, the right led is stuck in blue and when I try to Upgrading SPL via SD my phone stuck at white screen and said loading...
I'm confused so I write this problem here. everything I do fails including mtty process. what can i do, help me please.
Thanks for advice.
Greetings!
neilus said:
Hi! I have weird problem with HTC Kaiser (or HTC TyTn II).
At the boot of Windows Mobile 6.1 i got the message "the device is clearing storage..." and then the device shutdown, the right led is stuck in blue and when I try to Upgrading SPL via SD my phone stuck at white screen and said loading...
I'm confused so I write this problem here. everything I do fails including mtty process. what can i do, help me please.
Thanks for advice.
Greetings!
Click to expand...
Click to collapse
Sound's like the ROM is at fault rather than SPL.
Try a hard reset, if that doesn't work, try flashing a new ROM via the bootloader.
Thanks
Dave
DaveShaw said:
Sound's like the ROM is at fault rather than SPL.
Try a hard reset, if that doesn't work, try flashing a new ROM via the bootloader.
Thanks
Dave
Click to expand...
Click to collapse
Hi Dave, thanks to reply, as I said I think I try everything and everything I do fails including mtty process, I try flashing a new AT&T ROM via usb cable at the BootLoader screen and the process completed 100% and when restart of Windows Mobile 6.1, I got the message "the device is clearing storage..." and then the device make a strange "sound" and shutdown, I was Tried a hard reset, doesn't work, I tried flashing a hardspl via the bootloader but unsuccessful, when I try to Upgrading SPL via SD my phone stuck at white screen and said loading.... when I try to Upgrading SPL via SD with the same SD to another phone its work.
Thanks.
@neilus,
Since Dave mentioned ROM issue, I suggest you re-download again the ROM (just to make sure you got it clean and good) and re-flash. What was your O/S or ROM before flashing? The SPL is important to match the ROM version .. if you're from 6.0, then you need to flash a ROM that comes complete with SPL (such as OEM upgrade ROM)
Otherwise, go back to starting point and read through the newbies guide and this (especially for your stuck on white screen)
anagarika said:
@neilus,
Since Dave mentioned ROM issue, I suggest you re-download again the ROM (just to make sure you got it clean and good) and re-flash. What was your O/S or ROM before flashing? The SPL is important to match the ROM version .. if you're from 6.0, then you need to flash a ROM that comes complete with SPL (such as OEM upgrade ROM)
Otherwise, go back to starting point and read through the newbies guide and this (especially for your stuck on white screen)
Click to expand...
Click to collapse
Hi anagarika, look this:
model : KAIS1*0
SPL-1.93.0000
CPLD-8
I was flashing a new ROM via the bootloader, original AT&T rom, everything work fine at the flashing process and finish 100%, when the unit charge and swich on going to first windows logo screen and with sound switch itself off (the sound is named "LB" I think).
Thanks a lot.
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).