Database Users

Why upgrade the SPL?

It is just the boot loader (Second Program Loader) correct?
If i have a boot loader that is capable of applying update.zip files why should i change that?
I have no fear of bricking, can always re-root from scratch.
Thank you for your time.

if a new SPL has features you desire (bigger system partition...allowing foreign builds, etc., etc.)...that aren't in your current SPL
if you have hardSPL and are satisfied w/ the size of your system partition, leave it be. it's the best one for you at this time

alapapa said:
(bigger system partition)
Click to expand...
Click to collapse
Thats all i needed to hear.
Thank you for your answer.

ekeefe41 said:
Thats all i needed to hear.
Thank you for your answer.
Click to expand...
Click to collapse
you should rethink your lack of fear of "bricking"
if the SPL doesn't apply correctly, there is no restore from backup or re-rooting at this time.
make sure you have a PVT board first and chances are lower for mishaps

alapapa said:
you should rethink your lack of fear of "bricking"
if the SPL doesn't apply correctly, there is no restore from backup or re-rooting at this time.
make sure you have a PVT board first and chances are lower for mishaps
Click to expand...
Click to collapse
Will do
i have read all the guides, have the latest firmware, and have 2 sdcards to play with.
Thank you.
(need to wait for work to slow down before i can play)

I have finished, no issues.
How do i repartition for more /system?

ekeefe41 said:
I have finished, no issues.
How do i repartition for more /system?
Click to expand...
Click to collapse
if you flashed Haykuro's "special" spl, it should have done it on its own.

DREAM PVT 32B ENG S-OFF
HBOOT-1.33.2005 (DREA10000)
CPLD-4
RADIO-2.22.19.26I
APR 20 2009, 15:30:43
FASTBOOT
<MORE CRAP I AM TOO LAZY TO TYPE>
So yea, gonna try the new ion build

I wonder where the new spl came from... i also wonder why people just tend to update things they dont know @#$! about which may cause a bricked phone...
I also wonder why someone would put it online and recommend people to update without knowing it could harm someones phone....
A lot of threads get killed because sources can not be verified and such, but a spl which causes a lot of bricked phones is still online.... Until there is a 100% proven way to update the new spl ( if its even a new spl for the dream ) I would like mods to consider to take it offline or remove the download links from this forum, like they do with some roms ( which cant cause any real harm ).
I hope you people all thought about how this new SPL could potentially brick your phone when a new Radio comes along just as using the old radio with this SPL could brick your phone.

Is the new 1.33.2005 spl backwards compatible with older roms? I am trying to find the jf rom that has nandroid as part of the recovery console and Im going to have to flash each one till I find the rom with it but I want to make sure the spl will work with the older builds.
Or if anyone knows where I can get the recovery image with nandroid, that would be appreciated!
Thanks
Kevin

rogro82 said:
I wonder where the new spl came from... i also wonder why people just tend to update things they dont know @#$! about which may cause a bricked phone...
I also wonder why someone would put it online and recommend people to update without knowing it could harm someones phone....
A lot of threads get killed because sources can not be verified and such, but a spl which causes a lot of bricked phones is still online.... Until there is a 100% proven way to update the new spl ( if its even a new spl for the dream ) I would like mods to consider to take it offline or remove the download links from this forum, like they do with some roms ( which cant cause any real harm ).
I hope you people all thought about how this new SPL could potentially brick your phone when a new Radio comes along just as using the old radio with this SPL could brick your phone.
Click to expand...
Click to collapse
I tend to agree. The way these phones are setup, recovering from a failed ROM flash is safe and easy. But flashing an SPL that was made for a different device is just asking for trouble IMO. Until someone comes up with a working JTAG, I'm sticking with HardSPL.

Attempt to fix my phone

First, my problem started with either updating to the new JFv1.43 recovery, or flashing the new SPL from Haykuro.
Symptoms:
1. Everytime I flash a new ROM, wipe or no wipe, I come back stuck at the T-Mobile G1 boot screen. The only way I've found to get through is to take out battery and boot into ADB (the Camera + Power screen) and "fastboot flash boot boot.img". This almost always work.
2. Nandroid stopped working. Nandroid always errors during the process of backing up, and I'd only have splash1.img and splash2.img in the nandroid folder of my SD card. Kind of want to try reflashing the JFv1.43, or even go back to 1.42 (can't find) for troubleshooting. Also not sure if this would affect the new SPL and cause a brick.
3. "Insufficient storage available" with Dude's and Cyanogen's builds. I'm not sure if this one is related to recovery or SPL. This might be caused by past attempts at doing apps2sd (I've done both symlink and unionfs).
Anyways, losing Nandroid has lost me a lot of time with trying out new ROM's, I'd really like to get it fixed. The boot stuck is a nuisance, but much less troublesome than losing Nandroid.

Its the SPL.

lbcoder said:
Its the SPL.
Click to expand...
Click to collapse
So then I'm stuck in this situation? Since the SPL can't be downgraded.

cigar3tte said:
So then I'm stuck in this situation? Since the SPL can't be downgraded.
Click to expand...
Click to collapse
I'm not positive (***so dont do this without researching***) but i think it would be possible to flash to a different one ( i mean, you flashed another SPL over the original one, right? ).
There is a "mega-thread" that has information on all the SPL's and their features/updates. If the info is anywhere, it's prob in there. Search in the Dev forum.

tr.slate said:
I'm not positive (***so dont do this without researching***) but i think it would be possible to flash to a different one ( i mean, you flashed another SPL over the original one, right? ).
There is a "mega-thread" that has information on all the SPL's and their features/updates. If the info is anywhere, it's prob in there. Search in the Dev forum.
Click to expand...
Click to collapse
As far as I can remember, that is where I read that you can't flash the older SPL over the new one.

cigar3tte said:
as far as i can remember, that is where i read that you can't flash the older spl over the new one.
Click to expand...
Click to collapse
damn the man!

cigar3tte said:
As far as I can remember, that is where I read that you can't flash the older SPL over the new one.
Click to expand...
Click to collapse
I could be wrong, but the key is not flashing an older RADIO with the newer spl.
You should still be able to go back to hardspl with no issues.

cigar3tte said:
As far as I can remember, that is where I read that you can't flash the older SPL over the new one.
Click to expand...
Click to collapse
I have flashed from the New H SPL to the HardSPL i originally had on the phone when I found out people were having trouble with the SPL. I install the NEW SPL again to run Hero, but you CAN flash it back to the older SPL I would recomend HARDSPL though.
*not responsible if this doesn't work but I was able to do this without any trouble. Was just a bit nerve racking.

i am 99% sure the above post is correct, don't flash a different radio, but you can flash another SPL right over the Haykuro SPL. i would double check that as there is a 1% chance it will totally screw your phone and i don't wanna be the guy that told you to do something that bricked your phone, but it should work. just to be safe you should make sure splash1 is the t-mo g1 screen so if it stops you can call t-mo

i flashed from the latest haykuro spl 1.33.2005 , to the original t-mobile spl HBOOT-0.95.0000. I fastbooted and it was showing the original spl installed.

How to intentionally brick your G1?

Here's my problem:
1) I had rooted my phone in the past.
2) I need to do a warranty return for a bad touchscreen and keyboard
3) I'm unable to flash back to stock because the home key is "stuck", so I can
only boot into recovery mode.
Is it possible to brick the phone so that it get stuck at the T-mobile loading screen before it default boots to the recovery screen?
If so, what is the most reliable way to brick my phone when all I have access to is the recovery mode?

fastboot flash a corrupt boot.img.

coolbho3000 said:
fastboot flash a corrupt boot.img.
Click to expand...
Click to collapse
That would be my first choice as well... except that I can only get to recovery mode, even when I hold down the camera button.
Closest thing I can do is flash an update.zip

my touch screen died today thank god for a trackball lol

g1junky said:
my touch screen died today thank god for a trackball lol
Click to expand...
Click to collapse
That's what I was thinking... I figure I'd just use my phone as-is until the replacement arrived, then I'd flash it back to stock before returning it...
If it's just a bad touch screen, they'll replace it without much fuss for next to free (just $10 shipping). Which is a very fair deal... unless you rooted your phone (boo!).
Then the home key got "stuck"... what bad luck... It's obvious when you turn it on that it's been rooted because of the custom recovery image... I'd rather make it a bit harder for them to determine my warranty's void instead of just having to turn it on.
@coolbho3000: I noticed that a boot.img file is included in some random update.zip (JFv1.3_RC8.zip) I just downloaded... Any idea what to hexedit on it to ensure it'll brick if I do an update through recovery mode? Or should I just pull the battery during the update (many times if need be)?
Update: I tried randomly screwing with the boot.img file using notepad++, but the damn phone won't use it for the update because the digest failed during the verification process. I also pulled the battery out during the part when it says it's writing the boot.img file (twice) without success -- although in this case, 'success' would be a bricked phone.
Why is this phone so hard to brick? Others just look at their g1 and can brick it...

I managed to brick my phone! It was harder than I thought (well, considering my many failed attempts), but here's how I did it:
I downloaded haykuro's 1.33.2005 special spl, renamed it to update.zip, and updated the g1 with it through the recovery panel. It's now permanently stuck at the T-mobile G1 screen. Worked for me, YMMV.
If that didn't work, my next two ideas were:
1) Very powerful magnet... high power speakers, or something else that puts out a lot of EM radiation (I'm sure I'd think of something). These things must have a low tempest rating.
2) Microwave (but that smells like desperation)
Hope this helps others in the same boat. I'll update with the bad news if they do, in fact, figure out I had rooted my phone anyways. I'm sure it's possible, yet probably unlikely. Otherwise, no news is good news.

Be glad you didnt have a custom spalsh image lol

Daemonjax said:
Here's my problem:
1) I had rooted my phone in the past.
2) I need to do a warranty return for a bad touchscreen and keyboard
3) I'm unable to flash back to stock because the home key is "stuck", so I can
only boot into recovery mode.
Is it possible to brick the phone so that it get stuck at the T-mobile loading screen before it default boots to the recovery screen?
If so, what is the most reliable way to brick my phone when all I have access to is the recovery mode?
Click to expand...
Click to collapse
Pretty simple. First do a recovery to factory settings using the camera and the start button. then copy the latest SPL from this website,
in the instructions it says that you have to flash the latest radio first, don't do that, just flash the SPL... reboot, voila, you have just successfully BRICKED ur phone..

Daemonjax said:
1) Very powerful magnet... high power speakers, or something else that puts out a lot of EM radiation (I'm sure I'd think of something). These things must have a low tempest rating.
2) Microwave (but that smells like desperation)
Click to expand...
Click to collapse
Magnets don't emit electromagnetic radiation -_-;;
A much easier way would just be to take a moderately high dc voltage (say ~48v) and fry part of the processor.

Daemonjax said:
I managed to brick my phone! It was harder than I thought (well, considering my many failed attempts), but here's how I did it:
I downloaded haykuro's 1.33.2005 special spl, renamed it to update.zip, and updated the g1 with it through the recovery panel. It's now permanently stuck at the T-mobile G1 screen. Worked for me, YMMV.
If that didn't work, my next two ideas were:
1) Very powerful magnet... high power speakers, or something else that puts out a lot of EM radiation (I'm sure I'd think of something). These things must have a low tempest rating.
2) Microwave (but that smells like desperation)
Hope this helps others in the same boat. I'll update with the bad news if they do, in fact, figure out I had rooted my phone anyways. I'm sure it's possible, yet probably unlikely. Otherwise, no news is good news.
Click to expand...
Click to collapse
You didn't have to hard brick it like that you know. There are other ways which will convince the warranty people just as well. Now it's really bricked.

hmmm well this was my idea....if my phone ever goes wrong or sumthing.... i will just crack the screen lol. so they cant see if what software was on my phone...

the easiest thing to do is flash the danger spl before flashing the radio if u havent flashed the Danger SPL already. If u did, just flash an older SPL. That should do the trick

nephron said:
the easiest thing to do is flash the danger spl before flashing the radio if u havent flashed the Danger SPL already. If u did, just flash an older SPL. That should do the trick
Click to expand...
Click to collapse
Or if you already have Haykuro's SPL just downgrade your radio hehehe

nephron said:
the easiest thing to do is flash the danger spl before flashing the radio if u havent flashed the Danger SPL already. If u did, just flash an older SPL. That should do the trick
Click to expand...
Click to collapse
So if you have the danger/haykuro spl and want to downgrade that spl for w/e reason the phone will brick??? or are you trying to tell him to downgrade the radio?

turboyo said:
So if you have the danger/haykuro spl and want to downgrade that spl for w/e reason the phone will brick??? or are you trying to tell him to downgrade the radio?
Click to expand...
Click to collapse
If you use Haykuro's "Danger SPL" and will try to downgrade the radio, it should brick the phone for good.

Even if your camera button is broken you can still get to fastboot through ADB. Just open an adb shell (doesn't matter if it is recovery or not) and type:
#restart bootloader
and voila - you can get into fastboot mode and flsh whatever you want.

brian_v3ntura said:
hmmm well this was my idea....if my phone ever goes wrong or sumthing.... i will just crack the screen lol. so they cant see if what software was on my phone...
Click to expand...
Click to collapse
thats dumb as hell cuz if u crack ur screen u have to pay $130 deductable well at least in USA and if u send it back with out telling them the screen cracked u get to pay $370 restocking fee but ifd u just brick with spl u get free replacement just pay shipping which im about to do cuz my phone was ****ing up and i got replacement sent(20 bucks shipping thats it) but magically i fixed the phone but its rooted and fully working again so if new phone is PVT board then im bricking my phone and keeping new one.

I need help
Hey people I have a cracked G1 screen and a rooted firmware, I want to get a free warranty replacement by saying that the "Update Failed" and act like a total idiot to the tmobile people..
I also have Haykuro's latest radio and latest SPL, can someone give me clear guaranteed instructions on how to brick my fine cracked friend?
Oh, and I also want to make sure that the TMOBILE people cant go to cyanogens 1.4 Recovery image after this thing is bricked, so AANNY help would be appreciatede

housecat93 said:
Hey people I have a cracked G1 screen and a rooted firmware, I want to get a free warranty replacement by saying that the "Update Failed" and act like a total idiot to the tmobile people..
I also have Haykuro's latest radio and latest SPL, can someone give me clear guaranteed instructions on how to brick my fine cracked friend?
Oh, and I also want to make sure that the TMOBILE people cant go to cyanogens 1.4 Recovery image after this thing is bricked, so AANNY help would be appreciatede
Click to expand...
Click to collapse
Grab the RC29 file, name it DREAIMG.nbh, and flash via the bootloader. Since that will downgrade the radio to the 1.1 version, you will no longer have the 1.5 radio that 1.33.2005 requires

This has got to be the funniest topic I've read in awhile.
Good luck to all you seeking bricked phones. Haha.

Video of me bricking my Magic, what went wrong?

Hey guys,
Few of you in the cyanogenmod irc room the other night might have recalled me totally bricking my t-mobile mytouch by pulling the battery after a reboot... dumbest thing I have ever done. I consider myself a fairly knowledgeable linux geek, but unfortunately I panicked and did the worst possible thing, pulling my batt and completely bricking my phone.
I was installing the 4.1.999 cyanogen mod. Phone was so toast it wouldn't charge. Status led's wouldn't work, it was 100% toast. Fortunately I was able to have it replaced and would like to try again in a day or so.
Here is a video showing exactly what I did, please excuse the length of the video it goes from start to finish, backing up and flashing everything, up until the point where I pulled the battery. I'd love to know what I did wrong, so I can try again!
View the video here on vimeo -> http://vimeo.com/7022688

Ok, here's what you did wrong:
The first steps are good... You've installed the 1.6 update, then applyed the cyanogen rom... After that I've seen that it was installed a new radio... That might have killed your phone...
At least that appears to be the problem... But why a new radio was installed, no idea... (I don't think you did it on purpose)...

the phone you have there is a magic not a dream.For a start that dosnt help!! Other than that i think yiou have put Dream radio on the device, It not being a dream is the problem as when it detects its the wrong radio the phone goes into a safe mode where it wont turn on to save breaking it.
HTC might fix it under warranty as they did me but it WILL come back with perfect spl on.I have flashed the wrong radio on 2 phones yes 2! now i learn from my mistakes Oh and when/if it gets fixed and you bypass perfect spl, You cant put any ROM Other than donut based ones so no hero takes the fun out of flashing

All bricks I've seen are because you guys install new( in most cases wrong radio- from different phone or MotherBoard version) or changing SPL (exception: people with perfect SPL). I'm asking WHY you do this , WHAT FOR ? Putting different rom /rooting etc does NOT require changing anything and is simple as bread and butter, and you CAN'T damage the phone !! Sorry to see this I'm not 100% sure but it looks like you have flashed with wrong radio. As my predecessor said I think only HTC can fix it... To all people DO NOT TOUCH SPL AND RADIO IF YOU JUST WANT TO PUT HERO ROM OR ROOT THE PHONE (exception ppl with perfect SPL)

i accidently flashed the radio for ION on my 32A last week. got my phone fixed under warranty thank god. but i got the perfected SPL.
if you do get the perfected SPL, you dont really need to change your SPL to flash stuff on your phone.
just replace your recovery using the recovery flasher apk a.k.a the one click root.
reboot to recovery, flash a new ROM that is rooted.
then using the adb shell method, flash a new recovery permanently to your phone.
i have had no issues using that method since i got my perfected SPL.

whalesalad said:
Hey guys,
Few of you in the cyanogenmod irc room the other night might have recalled me totally bricking my t-mobile mytouch by pulling the battery after a reboot... dumbest thing I have ever done. I consider myself a fairly knowledgeable linux geek, but unfortunately I panicked and did the worst possible thing, pulling my batt and completely bricking my phone.
I was installing the 4.1.999 cyanogen mod. Phone was so toast it wouldn't charge. Status led's wouldn't work, it was 100% toast. Fortunately I was able to have it replaced and would like to try again in a day or so.
Here is a video showing exactly what I did, please excuse the length of the video it goes from start to finish, backing up and flashing everything, up until the point where I pulled the battery. I'd love to know what I did wrong, so I can try again!
View the video here on vimeo -> http://vimeo.com/7022688
Click to expand...
Click to collapse
after applying the 4.1.999 update you pressed the trackball to reboot your suppose to hold the home key while its rebooting on that step till the mytouch screen shows up also you need to wipe the ext. redo the last step then the my3g should be fine in other words reflash the cyanogen

u install wrong recovery
Install instructions for an HTC Magic (32B ONLY!!!)/ION/MyTouch3G
Same as above if you are using CM-Recovery 1.4.
OR
Same as above EXCEPT step 2
Download HTC ADP 1.6 DRC83 http://www.androidspin.com/downloads...ooted_base.zip
*You have to manually reboot MT3G and hold home.

he can use the ra recovery image it works because i used it on mine

Turns out I used the wrong recovery image before doing the cyanogen flash.
I followed this guide on my second phone (swapped out my old white one for a black mytouch) and am running 4.1.999 right now - http://forum.xda-developers.com/showpost.php?p=4666075&postcount=282

Help: Stuck at the G1 logo screen after flashing SPL

Ive rooted before but im trying to root a friends device...It's been a while since ive rooted mine so I was freshening up how to do it again. I followed the steps all the way to flashing the SPL...My friend was on android 1.6 with build number DMD64. I reverted to RC29 to root and when flashing the SPL...i flashed dangerspl in recovery. I rebooted and now it does not go past the G1 logo...i tried fastboot and boot into recovery but unsuccessful. Is this a brick? I'm really hoping not...any help would be appreciated, thanks.

Did you make certain the radio was up to date? Old radio with danger spl = brick. Sorry. If that's the case, your only option will be JTAG, which is a rather complex procedure.

I could have been certain that the radio was 2.x but not 100%. My friend's phone was at 1.6 before the reverting to rc29. Does reverting rc29 also revert the radio to 1.x?

Deadbolt said:
I could have been certain that the radio was 2.x but not 100%. My friend's phone was at 1.6 before the reverting to rc29. Does reverting rc29 also revert the radio to 1.x?
Click to expand...
Click to collapse
No it shouldnt, can you get into recovery mode? if you can then just flash the rom again and it should work just fine.

As far as I know, DREAIMG.nbh contains ROM, radio, recovery, SPL and splash screens. So yes, I'm 99% percent sure it downgraded your radio.
If that's a case, then you have nice brick.
Why do you ppl still bother with Haykuro? SafeSPL + MTD Partition Hack is the way to go!

raven_raven said:
As far as I know, DREAIMG.nbh contains ROM, radio, recovery, SPL and splash screens. So yes, I'm 99% percent sure it downgraded your radio.
If that's a case, then you have nice brick.
Why do you ppl still bother with Haykuro? SafeSPL + MTD Partition Hack is the way to go!
Click to expand...
Click to collapse
If the dreaimg.nbh file does downgrade the radio then i'm probably sol. It was my fault as I should've gone with the original hardspl before flashing the dangerspl right away. But I didnt think rc29 would downgrade the radio, thought it'd be safe.
Anyone know or know anyone that can do the jtag hack and try to recover the bricked G1? I looked up jtag and it sounds quite complicated to do myself. If anyone can do it, ill even pay a small fee for someone to do it. Thanks.

I have a question about this too. I too find myself in the same situation but i did not try to flash the dangerSPL. I was rooting and after i flashed hard spl and rebooted i got stuck on the G1 screen...I cant load into recovery or normal or even fast boot. Did i really just brick my phone? any help would be cool

Bottom Line....
Out of all the post, no one seems to give a straight answer. HTC G1 frozen on the bootup screen (T..Mobile G1 screen). Can the phone be fixed or NOT? If it can, how is this done? (factory G1)

If you can boot into Recovery (Home + Power) or Fastboot (Camera + Power) you can recover your phone. Otherwise you need to use JTAG, which with the right knowledge can recover just about anything. I'd search craigslist or similar sites for people that offer JTAG services. Every now and then an XDA member might offer it, but that would be in special circumstances, considering that there are a lot of people who might need it done.

funkeee said:
If you can boot into Recovery (Home + Power) or Fastboot (Camera + Power) you can recover your phone. Otherwise you need to use JTAG, which with the right knowledge can recover just about anything. I'd search craigslist or similar sites for people that offer JTAG services. Every now and then an XDA member might offer it, but that would be in special circumstances, considering that there are a lot of people who might need it done.
Click to expand...
Click to collapse
is it possiable for one to purchase said jtag hardware, and run the software on ones computer??

xxcrashxx said:
is it possiable for one to purchase said jtag hardware, and run the software on ones computer??
Click to expand...
Click to collapse
You'll also need to open up the phone and solder wires to the circuit board.