Related
So I've been running Cyanogen's latest for quite a while now, with no problems that aren't systematic to whatever version he's just come out with. I decided to try something else just for fun, so I tried flashing JAC's and Drizzy's Hero ROMs. And yes, I flashed the correct radio and spl prior to the ROM flash.
For some reason, neither will work. They both come up with some kind of error at a certain line, either 80 or 59, I believe. So, I restore my backup to Cyanogen, and I'm back in business no problem.
Anyone care to hazard a guess as to what's going on? Thanks.
nspbass
I had that issue before. Here is what I did:
Wipe + repartition(dont forget you need 3)
reupdate SPL -> used the OTA, the the hardSPL
that worked for me, give it a try and good luck
Yeah I would just say wipe everything, make sure you use parted to split your sdcard which should be class6 into fat32/ext2or3/linux-swap.
You need Haykuro's special SPL. If you don't have it you will get that error every time.
shaolinx said:
I had that issue before. Here is what I did:
Wipe + repartition(dont forget you need 3)
reupdate SPL -> used the OTA, the the hardSPL
that worked for me, give it a try and good luck
Click to expand...
Click to collapse
Diceman4 said:
You need Haykuro's special SPL. If you don't have it you will get that error every time.
Click to expand...
Click to collapse
Exactly, so how the hell did Shaolinx flash it with HardSPL?
AdrianK said:
Exactly, so how the hell did Shaolinx flash it with HardSPL?
Click to expand...
Click to collapse
I'm sure he's mistaken.
And to the OP can you tell us what spl you have (cam + power).
Here's what it says:
DREA100 PVT 32B
HBOOT-0.95.0000
CPLD-4
RADIO-1.22.12.29
Sep 2 2008
I assumed the HBOOT to refer to the SPL, which obviously isn't correct. So, I reflashed the SPL.
I think I did a bad thing. Phone won't boot to anything past the initial G1 screen. I thought this was only an issue if I had the incorrect radio. Thoughts?
nspbass
nspbass said:
Here's what it says:
DREA100 PVT 32B
HBOOT-0.95.0000
CPLD-4
RADIO-1.22.12.29
Sep 2 2008
I assumed the HBOOT to refer to the SPL, which obviously isn't correct. So, I reflashed the SPL.
I think I did a bad thing. Phone won't boot to anything past the initial G1 screen. I thought this was only an issue if I had the incorrect radio. Thoughts?
nspbass
Click to expand...
Click to collapse
I hate to break the news to you but that is not the correct radio...the newest radio is 2.22.19.26I
Looks like its time to call TMO and put on your lying cap...
Also just because it says HBOOT does not mean that it is Haykuros SPL. THe special SPL is 1.33.2005
nspbass said:
Here's what it says:
DREA100 PVT 32B
HBOOT-0.95.0000
CPLD-4
RADIO-1.22.12.29
Sep 2 2008
I assumed the HBOOT to refer to the SPL, which obviously isn't correct. So, I reflashed the SPL.
I think I did a bad thing. Phone won't boot to anything past the initial G1 screen. I thought this was only an issue if I had the incorrect radio. Thoughts?
nspbass
Click to expand...
Click to collapse
and you have the wrong radio since the new one is 2.22.19.26I
Diceman4 with your slightly faster connection
but basically tell them your got an update or something, and that when the phone rebooted that it would not pass the g1 screen. also make sure you sound as clueless as to what root or flashing or anything technical is.
Ok, before this was a problem, I downloaded and flashed the radio, then the SPL. Clearly, they didn't take for some reason.
Now, my question is this: what do I do now? I'm looking in the bricked phone threads, but I haven't found an answer yet. Any help? Thanks.
nspbass
david1171 said:
Diceman4 with your slightly faster connection
but basically tell them your got an update or something, and that when the phone rebooted that it would not pass the g1 screen. also make sure you sound as clueless as to what root or flashing or anything technical is.
Click to expand...
Click to collapse
I wouldnt even say you got an update, I would just say that the phone restarted on its own one day and then just froze at the G1 screen. Be sure to not use any terms like "flash" "bricked" "boot loop" or anything that makes it look like you know anything at all about phone hacking. David is right just make yourself sound as clueless as possible.
nspbass said:
Ok, before this was a problem, I downloaded and flashed the radio, then the SPL. Clearly, they didn't take for some reason.
Now, my question is this: what do I do now? I'm looking in the bricked phone threads, but I haven't found an answer yet. Any help? Thanks.
nspbass
Click to expand...
Click to collapse
There is no way to fix it, the board needs to be replaced. You need to call t-mobile, follow mine and David's instructions and try to get a new one under warrantee
nspbass said:
Ok, before this was a problem, I downloaded and flashed the radio, then the SPL. Clearly, they didn't take for some reason.
Now, my question is this: what do I do now? I'm looking in the bricked phone threads, but I haven't found an answer yet. Any help? Thanks.
nspbass
Click to expand...
Click to collapse
i assume you have a cyanogen recovery image with the trackball feature? if so, for the radio and spl flashes you have to do the keyboard commands to make it work, you can't use the trackball or recovery console to reboot. so you can't boot into recovery or bootloader? if you can't, you have a brick
Diceman4 said:
I wouldnt even say you got an update, I would just say that the phone restarted on its own one day and then just froze at the G1 screen. Be sure to not use any terms like "flash" "bricked" "boot loop" or anything that makes it look like you know anything at all about phone hacking. David is right just make yourself sound as clueless as possible.
Click to expand...
Click to collapse
Done! Should have the replacement by Tuesday. I'm a tard.
nspbass
shaolinx said:
I had that issue before. Here is what I did:
Wipe + repartition(dont forget you need 3)
reupdate SPL -> used the OTA, the the hardSPL
that worked for me, give it a try and good luck
Click to expand...
Click to collapse
You know that you can't install hero with hard spl right? For someone who has a site dedicated to Android you don't seem to have your **** straight - no offense. And he could have bricked his phone if he tried to do H's danger spl without having the correct radio. Be careful when you give advice, we don't need to HELP people brick there G1's.
Haha, that's what I get for assuming he had the right spl and radio when he said he did. But if you are getting G1 screen you aren't bricked, if you can get into bootloader(camera+power) you should be able to flash your way back in time then forward again. I guess it doesn't matter if you're already getting it replaced but I got my friends back when his was only loading to G1, a true brick wont turn on at all no matter what you press.
JoshHart said:
But if you are getting G1 screen you aren't bricked..
Click to expand...
Click to collapse
If you do brick you will get the G1 splash screen, just nothing else..
Huh, well I guess my friend got lucky that wasn't his problem. Learn something new every day.
JoshHart said:
Haha, that's what I get for assuming he had the right spl and radio when he said he did. But if you are getting G1 screen you aren't bricked, if you can get into bootloader(camera+power) you should be able to flash your way back in time then forward again. I guess it doesn't matter if you're already getting it replaced but I got my friends back when his was only loading to G1, a true brick wont turn on at all no matter what you press.
Click to expand...
Click to collapse
Check the brick threads and you will see that just cause you have the G1 screen doesn't mean you don't have a brick. Flashing the SPL before the Radio will brick your G1 and you will be stuck at the loading screen. That is really the only true bricks we are aware of yet, maybe your friend found another way to brick but if you do some studying you will see what I'm talking about.
This might be a dumb question and these might be the cause of all my FC's and lag. But when I see "require updated spl" does that mean update my HBOOT?
My current HBOOT is " HBOOT-1.33.0006" Am i out of date?
My stats are below.................
To be honest (and keep in mind I use a G1, so it may be different on the mt3g) I wouldnt be farting about with the spl, I causes more problems than its worth with people bricking phones.
I doubt the FC's arew caused by the SPL anyways, its mopre than likley something installed or something else, a re-install of the rom and app's would usually solve it.
thanks! I always see NEW SPL required blah blah! But no I cant brick my MT3g....especially if i only spent 50bucks on it!
lol mt3g users already have the SPL required by the "new spl required" roms....thats for G1 only specifications....
this is the g1 section after all lol
First of all, i am very sorry if i made a stupid Question because of my noobs. But i am preparing to flash DangerSPL onto my G1, and still dont know which radio should be chosen. I've been spending hours reading info from several posts on xda but cant find answer yet
There are two radios compatible with DangerSPL
2.22.23.02 for T-mobile/US
2.22.19.26i for Non-US
My current radio is 2.22.20.23
That's what I can't get through. My G1 is a QWERTZ one, which I guess it's a Non-US and 2.22.19.26i is better for me? But the first one is mentioned much more frequently in posts, means it's famous/or better than the other?
Please help me figure out
Thanks very much, and sorry again for my stupid Q
jilee said:
First of all, i am very sorry if i made a stupid Question because of my noobs. But i am preparing to flash DangerSPL onto my G1, and still dont know which radio should be chosen. I've been spending hours reading info from several posts on xda but cant find answer yet
There are two radios compatible with DangerSPL
2.22.23.02 for T-mobile/US
2.22.19.26i for Non-US
My current radio is 2.22.20.23
That's what I can't get through. My G1 is a QWERTZ one, which I guess it's a Non-US and 2.22.19.26i is better for me? But the first one is mentioned much more frequently in posts, means it's famous/or better than the other?
Please help me figure out
Thanks very much, and sorry again for my stupid Q
Click to expand...
Click to collapse
Ok, to be successful. You will need to FLASH the radio before the SPL.
You can find both the radio and SPL here http://code.google.com/p/sapphire-port-dream/
DO NOT attempt to downgrade your radio at anytime after installing this SPL as it WILL brick your phone.
If you have additional questions you can read up on the thread here >> http://forum.xda-developers.com/showthread.php?t=517593
and here
http://forum.xda-developers.com/showthread.php?t=625886
Please make sure you read all the posts first before you flash your phone. I hope that helped.
ok thanks much for your help
But those stuffs have been reading over and over by me, and i still can't find out which radio should i flash. The 2.22.23.02 (which refers to smth more common and used by more people) or the 2.22.19.26i ? The sapphire-port-dream website says that the 26i is the latest version
This my first time flashing radio and upgrading to DangerSPL, so i'm very scared of bricking =.= Can you figure out for me which one is for my phone ? Thanks ^^
BTW, my board is a PVT one, rooted, but the very first bootscreen contains a grey and blur G1 in the center and a "T-mobile" (with the red T and four white dots like in the logo of T-mobile) at the bottom of the screen. It's not the all-white-big-centered "T-mobile G1" like most of those i see on the google or youtube. Is there anything important ?
(I can't post images along with this bcause of the new member's restricted right, so i will attact them instead. The worse quality one is mine)
jilee said:
ok thanks much for your help
But those stuffs have been reading over and over by me, and i still can't find out which radio should i flash. The 2.22.23.02 (which refers to smth more common and used by more people) or the 2.22.19.26i ? The sapphire-port-dream website says that the 26i is the latest version
This my first time flashing radio and upgrading to DangerSPL, so i'm very scared of bricking =.= Can you figure out for me which one is for my phone ? Thanks ^^
BTW, my board is a PVT one, rooted, but the very first bootscreen contains a grey and blur G1 in the center and a "T-mobile" (with the red T and four white dots like in the logo of T-mobile) at the bottom of the screen. It's not the all-white-big-centered "T-mobile G1" like most of those i see on the google or youtube. Is there anything important ?
(I can't post images along with this bcause of the new member's restricted right, so i will attact them instead. The worse quality one is mine)
Click to expand...
Click to collapse
Splash screen can be changed. To check go to bootloader, power on the phone holding camera button and see what do you have..it will show if you have 32A or 32B board.
1.33.2003 is compatible with 1.x and 2.x radios
1.33.2005 is compatible with 2.x and 3.x radios
So 2.x radio is safest. The combination has to be maintained otherwise you can brick the phone.
DO NOT INSTALL DEATHSPL!!!!
There is NO REASON for it!
What people use it for is obtaining a different flash partition layout on the internal memory. THERE ARE BETTER WAYS TO ACCOMPLISH THIS!!!!!
http://forum.xda-developers.com/showthread.php?t=717874
The DEFAULT setup of this yields you a SYSTEM partition that is the SAME SIZE as deathspl, and a USERDATA partition that is ***FIFTEEN MEGABYTES LARGER*** than deathspl.
Install SPL 1.33.2003 (ending with a THREE) and any 2.X radio ***IN ANY ORDER IT DOESN'T MATTER***. ZERO brick risk, and SUPERIOR to deathspl.
Further information;
1) PVT/DVT, DESPITE what some of the feeble minded morons who don't know what they're talking about claim, ****IS IRRELEVANT****. There is *NO DIFFERENCE* between a PVT and a DVT.
2) ALL DREAMS (100% there is not a SINGLE exception) are 32B. The ONLY device where there is any question of whether it is a 32A or B is MAGIC.
Thanks so much lbcoder
It's because i think that deathspl is the only hope in order to get to Cyanogen or CaNNoN roms. And flashing radio and spl somehow is the most risky step :|
Did you mean that, by following that Firerat's guide, i am enabled to flash SPL 1.33.2003 and radio 2.xx in any order? Is 1.33.2003 deathspl or not ? And i want to flash CaNNoN CE 2.2.1, so is this good for me
^^ Thanks again
It doesn't appear that you bothered to read either what I said or the thread I linked you to. READ AGAIN!
There is NO BENEFIT TO DEATHSPL. It does NOTHING USEFUL. There are BETTER WAYS to accomplish the same thing that do NOT involve ANY kind of RISK!
jilee said:
It's because i think that deathspl is the only hope in order to get to Cyanogen or CaNNoN roms.
Click to expand...
Click to collapse
Anyone who things that is WRONG.
Did you mean that, by following that Firerat's guide, i am enabled to flash SPL 1.33.2003 and radio 2.xx in any order?
Click to expand...
Click to collapse
No. That is not a guide! It is a PROCESS, which has NOTHING to do with flashing radios or SPLs! It has to do with PARTITION TABLES.
Is 1.33.2003 deathspl or not ?
Click to expand...
Click to collapse
ABSOLUTELY NOT!!!
And i want to flash CaNNoN CE 2.2.1, so is this good for me
Click to expand...
Click to collapse
The SPL has NOTHING to do with what you can flash to the phone. You do NOT need deathSPL. It is POINTLESS. The ONLY thing you accomplish with the deathSPL is that you RISK BRICKING YOUR PHONE!
I suggest the 1.33.2003 SPL because it is a FULL ENGINEERING SPL that is 100% compatible with 0.95.x000 (the SPL that your phone SHIPPED WITH). **IT WILL NOT BRICK**.
Using the recovery-installable patches supplied by Firerat will enable you to flash ANY system image to your phone. NO EXCEPTION.
Ok ok. I am a stupid man, so please don't blame on me ^^
Let me ask a very last question. As i can see from your advise, after flashing those CustomMTD, i can flash ANY system image(ROMs) to my phone without upgrading to 2.xx or the pointless dealthy spl. Is it right? In other words, i still can use CM or CE roms with 0.95.x000 radio?
And is it harmful or not if i want to upgrade to 2.xx radio? (still want smth new :"> )
well, no one ?
0.95.x000 is default SPL, not radio.
You have to flash new SPL (if you're still on default), but not Haykuro/Death/Danger/Apocalipse (1.33.2005) which is not compatible with 1.x radios (and this is common reason of brick), but so called SafeSPL (1.33.2003) which has same low-level access to phone (fastboot, so it's giving you as much as 2005), but it is compatible either with 1.x radios and 2.x radios, so there is no chance to brick.
After you have engineering SPL (2003 or 2005, but in this case we're talking about 2003) you can use MTD Partition Hack to change partition layout on your phone (same thing that is Haykuro doing, but now you can manually resize them in order to get more place for apps in internal memory). This is needed for 2.1+ and Sense ROMs, because they do not fit in standard 70 mb /system partition (they need 90).
When you have both new SPL and /system big enough, you can flash EVERY ROM you want. If there is requirement for HaykuroSPL in OP of ROM thread, IGNORE IT. This is requirement for 90mb /system partition, which now can be achieved also by MTD PH.
Upgrading to 2.x radio is recommended, new radio means better signal reception and less battery drain.
Thank you very much raven. Your answer is very clear and kindly. So, now I have to flash SafeSPL, then MTD PH, and after that I can use any ROMs, and 2.x radio are optional (can flash or not, can flash after the safespl, it doesnt matter) right? I am so excited. Thanks again
I think this order is correct:
Custom recovery (Amon RA or Clockworkmod, ignore this step if you already have custom recovery)
SafeSPL
MTD PH (recovery patch)
ROM flash
MTD PH (ROM/boot patch)
Optional: 2.x radio.
I am glad to help and your thanks made my day . Just remember to put
Code:
90 2
in mtdpartmap.txt on root of sd card to prepare enough space for 2.x ROMs. You may also have to fake Haykuro SPL, which is simply done by editing mtdpartmap.txt in this way
Code:
90 2
spl 1.33.2005
Remember to patch recovery, wipe data&cache&system, reflash/nandbackup ROM and flash boot patch after every change in mtdpartmap.txt.
Thanks again ^^
But i still have a minor question before flashing all those stuffs. Raven please view this post :here and give me an advice whether i should continue according to lbcoder or not ?
quite useful infos. i was about to flash deathSPL, but the fact that the MTD layout gives me 15mb more space, not to mention it cant brick, seriously tempts me.
hey.
Im almost sure i just bricked my g1, just need to be sure.
I was running Death SPL and the last official radio, and had gsm\umts network connection problems.
Decided to upgrade the radio to the last one that came out recently, i did, the problem seem to be better but it got worse in time.
downgraded the radio, and tried around 15 different roms, all tries with the same outcome.
so after a lot of trial and error, i decided to get back to one the the first radios available, but i was afraid it would brick my phone so i read carefully about it
I had a realy hard time finding something but i everntually came across a couple threads that stated that it was ok to flash any radio, as long as the SPL was flashed first...
after reading that i downloaded a 1xxx radio and flashed via recovery...
result: stuck in the G1 screen...
My question: phone in the crapper right?
thanks for reading guys
mordockcs said:
i everntually came across a couple threads that stated that it was ok to flash any radio, as long as the SPL was flashed first...
Click to expand...
Click to collapse
No, what they said is that it is OK to flash anything as long as you use FASTBOOT INSTEAD OF RECOVERY, and that FULL FASTBOOT (with this ability) depended on having a 1.33.2xxx SPL.
With an SPL and RADIO that are incompatible with each other, it is impossible to successfully boot the kernel. Following a flash-hboot or flash-radio, the system is set (via writing the command field in the MISC partition) to boot-recovery. When in boot-recovery, the phone IGNORES all user inputs. The incompatible radio/spl fails to boot-recovery, and you're bricked.
USING FASTBOOT INSTEAD prevents the misc partition from being set to boot-recovery by writing the SPL or RADIO directly. As a result, when you reboot, though it still won't be able to boot a kernel, IT WILL RESPOND TO USER INPUTS and bring you into FASTBOOT mode... from where it is possible to, again, flash radio or spl.
Your failure is a result of failure to read properly.
SPL/radio compatibility:
0.95.xxxx, 1.33.x003: compatible with 1.x or 2.x radios.
1.33.xxxx (except 1.33.x003): compatible with 2.x or 3.x radios.
No exceptions.
I always suggest using the 1.33.2003 SPL since DREAM should always use either a 1.x or 2.x radio (except robbers in canada, because they are bastards, but you can load those with a 2.x radio just fine). 1.33.2003 is the strongest engineering SPL available, and fully compatible with the proper radios. There is NO ADVANTAGE to any other SPL -- no, you don't need to change your SPL to reallocate storage space.... in fact, limiting yourself to SPL changes to do this will tend to waste a lot more space (15 MB more available than 1.33.2005 gives you).
lbcoder said:
Your failure is a result of failure to read properly.
Click to expand...
Click to collapse
no its not...im pretty sure about what i read...if i stumble on the thread again ill PM you to prove it.
i already have a touch HD on the way so no harm done, i wish this was all the harm in our world...
but anyway now that its dead...lets fix it!
is there a way around it? i hear about jtaging a lot but i have never seen a tutorial on the web...
any insight on that would be delightful...seriously
but hey lbcoder thanks for enlightening me i appreciate it, i really do...thanks man
I recently flashed BiffMod2.0 to my rooted Rogers Dream using ezterry's EB1I port. I've got the DangerSPL, I've cleared the cache's and factory reset twice, but it keeps having this issue. When left for about 20 min to an hour, it'll lock up solid, whether I'm in the middle of something or its on standby -- and I can't shut it down until the battery is removed. If it freezes while locked, I can still hear the unlock screen working, and the buttons light up, but the screen stays blank. I thought it might have been an issue with the display, but it's also frozen solid with the screen on, while I was in the middle of using the phone.
Bad install or bad ROM?
Ya, 2.0 did that sometimes. it was so bad that I went back to 1.9.2. But then there was an update to 2.0.1 that fixed that, and now 2.1 is the latest. Try updating.
Several Zombies said:
I recently flashed BiffMod2.0 to my rooted Rogers Dream using ezterry's EB1I port. I've got the DangerSPL, I've cleared the cache's and factory reset twice, but it keeps having this issue. When left for about 20 min to an hour, it'll lock up solid, whether I'm in the middle of something or its on standby -- and I can't shut it down until the battery is removed. If it freezes while locked, I can still hear the unlock screen working, and the buttons light up, but the screen stays blank. I thought it might have been an issue with the display, but it's also frozen solid with the screen on, while I was in the middle of using the phone.
Bad install or bad ROM?
Click to expand...
Click to collapse
MAN, Biffmod needs Hard/Death/Haykuro's SPL not DANGER SPL (the one you got), it's not gonna work until you flash Death SPL in your phone
Before flashing, Turn off your phone & Press (Camera & Power), check which board you got (if it's PVT, then go for Death SPL (follow instructions, Stock > Root > Amon's Recovery > Radio Update > Death SPL > Biffmod) but if you got DVT board (as of me), never make a mistake of even downloading Hard/Death/Haykuro's SPL, they are not compatible with DVT phones, so avoid BRICKING your phone
rawfire said:
MAN, Biffmod needs Hard/Death/Haykuro's SPL not DANGER SPL (the one you got), it's not gonna work until you flash Death SPL in your phone
Before flashing, Turn off your phone & Press (Camera & Power), check which board you got (if it's PVT, then go for Death SPL (follow instructions, Stock > Root > Amon's Recovery > Radio Update > Death SPL > Biffmod) but if you got DVT board (as of me), never make a mistake of even downloading Hard/Death/Haykuro's SPL, they are not compatible with DVT phones, so avoid BRICKING your phone
Click to expand...
Click to collapse
Um, two problems. Death/danger spl are the same thing. It's the spl from the mt3g patched gor the g1. Also, the rom would be too big to install or wouldn't boot if there was a problem with the spl. There is a memory leak in biffmod 2.0, which causes the freeze. Update to 2.1.
Sent from my T-Mobile G1 using XDA App
Bigt2003 said:
Um, two problems. Death/danger spl are the same thing. It's the spl from the mt3g patched gor the g1. Also, the rom would be too big to install or wouldn't boot if there was a problem with the spl. There is a memory leak in biffmod 2.0, which causes the freeze. Update to 2.1.
Sent from my T-Mobile G1 using XDA App
Click to expand...
Click to collapse
They are same things mate but there's board difference (DVT/PVT) which actually matters in Danger & other SPLs
rawfire said:
They are same things mate but there's board difference (DVT/PVT) which actually matters in Danger & other SPLs
Click to expand...
Click to collapse
If they're *actually* the same they all work on the same type of board, wat you just said made no sense.
Also this is the second time I have accidentally given thanks because I'm used to having the quote button on the far right, ****ing hell.
atleast death SPL haven't worked for me on DVT board (it bricked my G1)
Cheers
rawfire said:
atleast death SPL haven't worked for me on DVT board (it bricked my G1)
Cheers
Click to expand...
Click to collapse
I think you'll find your inability to follow simple instructions bricked your phone, a phone can't brick itself it can only do what YOU tell it.