I was trying to load up my gf's G1 and I had a cyans newest rom and pretty much all was working good. Now my friend decided to try the boot screen flasher to load a custom boot image and well it was not working so he said that it was the SPL and I told him that not to worry about it...But he did it anyway and now when the phone loads it stays on the G1 screen. I tried to load into recovery (home+power) to see if I could nandroid but no dice. Any Ideas...I would like this to work by time she gets home as I am creating a playboy theme for her phone.
P.S. I decided to let my friend know not to touch my phones by a nice punch in the arm
P.P.S. I know I should search for this but I am time crunching thanks to my friend and need to get this working again for her ASAP
I would give him a little more than a punch.... if he flashed the SPL
and you cant get to the SPL (Cam+Power) or recovery (Home+Power)
then your phone is bricked....
just so you know... the boot screen flasher has two options..one for the standard/engineering/hardspl and another for the haykuro SPL
Yeah When I do camera power I still get the G1 screen
Sorry but this is a brick. Not fixable.
Try not to actually kill your friend, but he definitely deserves a serious beating.
There is one thing that's worked on a few magics/sapphires, but I don't think anyone's had it work on a g1.. you might as well give it a try since it's literally your only shot: You need to have fastboot drivers already installed and working on your pc and a copy of the engineering or hardspl.. plug your phone in by usb but don't switch it on and execute this command:
Code:
fastboot flash hboot hboot.img
You should get the message "Waiting for device...", now hold [camera] power the phone on and hope. If it doesnt work, try pulling and reinserting the battery a few times. The idea is to get fastboot to recognise the phone before it trips up and start the flash, but as I said I don't know if this has ever worked on a g1. It has been reported that this is more likely to work with linux than windows as it reacts to usb devices much more quickly.
goldenarmZ said:
Sorry but this is a brick. Not fixable.
Try not to actually kill your friend, but he definitely deserves a serious beating.
There is one thing that's worked on a few magics/sapphires, but I don't think anyone's had it work on a g1.. you might as well give it a try since it's literally your only shot: You need to have fastboot drivers already installed and working on your pc and a copy of the haykuro spl.. plug your phone in by usb but don't switch it on and execute this command:
Code:
fastboot flash hboot hboot.img
You should get the message "Waiting for device...", now hold [camera] power the phone on and hope. If it doesnt work, try pulling and reinserting the battery a few times. The idea is to get fastboot to recognise the phone before it trips up and start the flash, but as I said I don't know if this has ever worked on a g1. It has been reported that this is more likely to work with linux than windows as it reacts to usb devices much more quickly.
Click to expand...
Click to collapse
fastboot only works in the spl though. the radio never calls the spl if the radios outdated.
also, why would you want to send haykuros spl back on the phone, when thats what caused it to brick in the first place.
can you link me to where the magic people got it to work? because i doubt their brick is the same as this
B-man007 said:
fastboot only works in the spl though. the radio never calls the spl if the radios outdated.
also, why would you want to send haykuros spl back on the phone, when thats what caused it to brick in the first place.
can you link me to where the magic people got it to work? because i doubt their brick is the same as this
Click to expand...
Click to collapse
to the first part of your statement: thats our best guess but noone REALLY knows, so if you dont want off the wall, maybe fix your phone solutions, then go else where
and i do agree that using HARDSPL versus haykuro would prolly be better idea, but its worth a shot nonetheless, depends all on where the fastboot code exisits and where exactly the phones hang, if you have some specific details that the rest of us are missing then do SHARE
and from what ive heard you'll need to be running linux for the reasons above (windows being slow as balls to do anything, and "security" {hostility} protocols applied to the usb bus)
B-man007 said:
fastboot only works in the spl though. the radio never calls the spl if the radios outdated.
also, why would you want to send haykuros spl back on the phone, when thats what caused it to brick in the first place.
can you link me to where the magic people got it to work? because i doubt their brick is the same as this
Click to expand...
Click to collapse
That's what I thought til I saw this thread too, but the magics were spl bricks or I wouldn't have even posted it You're right tho, I meant to recommend hardspl, not haykuro's.. slip of the fingers. I've edited the post.
I'll try to find the magic thread again.. I can't quite remember where it was though..
ESKIMOn00b said:
to the first part of your statement: thats our best guess but noone REALLY knows, so if you dont want off the wall, maybe fix your phone solutions, then go else where
and i do agree that using HARDSPL versus haykuro would prolly be better idea, but its worth a shot nonetheless, depends all on where the fastboot code exisits and where exactly the phones hang, if you have some specific details that the rest of us are missing then do SHARE
and from what ive heard you'll need to be running linux for the reasons above (windows being slow as balls to do anything, and "security" {hostility} protocols applied to the usb bus)
Click to expand...
Click to collapse
what do you mean by no one already knows? We do know. i dont think youve been following xda very closely.
read the the threads that relate to the spl because all that info is already shared. Heres the summary
IPL>SPL>Android
when the link from IPL>SPL is broken.... there is nothing
Fastboot is on the SPL.
Its not "the rest of us" that don't know this....its just you
@Golden
Im surprised that hasnt been looked at yet. However..the spl bricks are probably very different from the ones on the G1
reason being is that Magic users are using Magic radios and Magic SPLs
These G1 bricks are from using G1 Radio and ported Magic SPL's
Technically, any magic radio should be compatible any magic spl
their bricks would easier to fix as the proper software is probably still on there while g1 may or may not recognize the software such as the magic spl
Related
Hi. I flashes a signed-spl to my phone via update.zip, now the phone will not load in recovery, nor bootloader mode.
I have place a working .nbh (for BL mode)
and a working update.zip (for rec. mode) on my miniSD
if somebody could please assist me in getting this thing running again, that would be great. thanks!
I have exactly the same problem. Can anybody help?
Which spl did you flash......original, engineering, hard, or haykuro (danger)?
Please tell me you didn't flash the danger spl without installing the latest radio first....
http://forum.xda-developers.com/showthread.php?t=517593
oraeanast said:
Hi. I flashes a signed-spl to my phone via update.zip, now the phone will not load in recovery, nor bootloader mode.
I have place a working .nbh (for BL mode)
and a working update.zip (for rec. mode) on my miniSD
if somebody could please assist me in getting this thing running again, that would be great. thanks!
Click to expand...
Click to collapse
Sounds like you got an expensive paperweight!
Time for a new phone
i flashed spl-signed
whatever that is.. my phone was giving me a android.process.aboot (OR SOMETHING LIEK THAT) with an option to force close it only. I figured the SPL would help this situation.
oraeanast said:
i flashed spl-signed
whatever that is.. my phone was giving me a android.process.aboot (OR SOMETHING LIEK THAT) with an option to force close it only. I figured the SPL would help this situation.
Click to expand...
Click to collapse
No offense big guy but just downloading and flashing something that you had no idea about probably wasn't the best idea. Where did you get this mysterious SPL from? Perhaps we can help you trace it that way. It sounds as though you bricked though since you have little to offer in the way of retracing your steps so we can help you. What guide did you follow, what radio did you have?
What made you figure that an SPL upgrade would fix your force close error? Did you research any of this?
Yea just like what DirectMatrix said "What would make you think the spl would solve a FC issue".
DirectMatrix said:
No offense big guy but just downloading and flashing something that you had no idea about probably wasn't the best idea. Where did you get this mysterious SPL from? Perhaps we can help you trace it that way. It sounds as though you bricked though since you have little to offer in the way of retracing your steps so we can help you. What guide did you follow, what radio did you have?
What made you figure that an SPL upgrade would fix your force close error? Did you research any of this?
Click to expand...
Click to collapse
well i know that the SPLs allow installation of unfamiliar ROMs and allow them to work.. i did this before with a different one and it did the trick. that is why i repeated this process.
To be perfectly honest, this SPL was in my downloads folder and had worked before.. so i flashed it. I have attached the SPL so maybe somebody can check this out? I appolagize for my newbess and impulsiveness lol.
And i believe the radio was NOT v2 =[ i know thats bad..
THE ROM I FLASHED THIS ON TOP OF WAS JFV1.51_CRB43-ADP
oraeanast said:
well i know that the SPLs allow installation of unfamiliar ROMs and allow them to work.. i did this before with a different one and it did the trick. that is why i repeated this process.
To be perfectly honest, this SPL was in my downloads folder and had worked before.. so i flashed it. I have attached the SPL so maybe somebody can check this out? I appolagize for my newbess and impulsiveness lol.
THE ROM I FLASHED THIS ON TOP OF WAS JFV1.51_CRB43-ADP
Click to expand...
Click to collapse
The only SPL I have in my SPL folder that is that same file size is the haykuro danger SPL, so if you didn't update to the latest radio (2.22.19.26I) then I'm sorry to tell you, YOUR BRICKED!
oraeanast said:
well i know that the SPLs allow installation of unfamiliar ROMs and allow them to work.. i did this before with a different one and it did the trick. that is why i repeated this process.
To be perfectly honest, this SPL was in my downloads folder and had worked before.. so i flashed it. I have attached the SPL so maybe somebody can check this out? I appolagize for my newbess and impulsiveness lol.
And i believe the radio was NOT v2 =[ i know thats bad..
THE ROM I FLASHED THIS ON TOP OF WAS JFV1.51_CRB43-ADP
Click to expand...
Click to collapse
Yea thats the same spl I have on my pc that is the "danger" spl. Yep if you flashed that without having the newest radio then you are bricked my friend. And spl has nothing to do with allowing installation of unfamiliar roms. What that spl does is free up more space on our phones to be able to install the hero roms which are larger.
The md5sum of the SPL you posted is the same as Haykuro's danger SPL. What's quite worrying is that you had a 1.5 ROM but not the 1.5 radio, if you had the new radio you would not have bricked. I wouldn't be surprised if you had a few dropped calls on 1.5 ;-P You didn't read, flashed something you didn't know about and bricked. My sympathy for you = nil.
new thread idea
I was thinking on my drive home, maybe we should just start a thread titled
TO EVERYONE: FLASH THE RADIO BEFORE YOU FLASH THE DANGER SPL FOR THE MILLIONTH TIME!!!!!!
Just start the thread, have it stickied, and have it closed before anyone can post anything in it. Then people wouldn't even have to open a thread, they can just navigate to a forum and have it slap them in the face. Then of course the next logical step is just to start a forum with the same title, then all they have to do is get to the website.....the sad part is people will still brick..
My sympathy for Mr/Mrs. oraeanast ended quickly when I read:
i flashed spl-signed
whatever that is..
Click to expand...
Click to collapse
so I agree with AdrianK's ^^latest^^ post...
sucks for you man
and to be honest sounds like a case of the brickedfromnotflashingradio1stidus
jf4888 said:
sucks for you man
and to be honest sounds like a case of the brickedfromnotflashingradio1stidus
Click to expand...
Click to collapse
Nah, sounds more like brickedfromnotfollowinginstructionsandwarningspostedeverywhereitis...
h.nocturna said:
Nah, sounds more like brickedfromnotfollowinginstructionsandwarningspostedeverywhereitis...
Click to expand...
Click to collapse
awesome. im aware i ****ed it up but people telling me i ****ed up over and over doesn't really help either.
If anybody has ANY clue or discovers any where to reverse this.. or maybe force the phone into fastboot from the computer that'd be great
oraeanast said:
awesome. im aware i ****ed it up but people telling me i ****ed up over and over doesn't really help either.
If anybody has ANY clue or discovers any where to reverse this.. or maybe force the phone into fastboot from the computer that'd be great
Click to expand...
Click to collapse
Dude, you gotta calm down a little and try to understand where we're coming from. MODS, I know this is off topic but I feel I have to get this off my chest...>big breath<
[RANT]There are literally hundreds of places within this forum that tell you to flash the radio before the SPL. There are notes and warnings all over the ROM threads, there are hundreds, maybe thousands of posts regarding:
n00b: "I think I bricked"
person trying to help: "can you get into recovery"
n00b: "no, I was trying to flash the new SPL so I could get Hero"
person trying to help: "did you install the radio first"
n00b: "oh no, what's that"
Not to mention you, yourself, mention in your first few posts that you didn't know what it was, you just figured you'd flash it because you thought it would help with some kind of force close. When you do something like that, n00b or not, you are gonna take some flaming from the forum. Sorry this is just how these things work. There are thousands of people on these forums that spend weeks reading before they do anything to their phone, and there are just as many who read for 20 minutes and just start doing things. The very nature of a open forum of this type makes it difficult to have organized data. Everyone seems to understand that but some are unwilling to put in the time necessary to gather all the proper resources and data. Unfortunately, you seem like one of these poor people.[/RANT]
My only comfort to you now is go here and give your phone a proper burial....
DirectMatrix said:
Dude, you gotta calm down a little and try to understand where we're coming from. MODS, I know this is off topic but I feel I have to get this off my chest...>big breath<
[RANT]There are literally hundreds of places within this forum that tell you to flash the radio before the SPL. There are notes and warnings all over the ROM threads, there are hundreds, maybe thousands of posts regarding:
n00b: "I think I bricked"
person trying to help: "can you get into recovery"
n00b: "no, I was trying to flash the new SPL so I could get Hero"
person trying to help: "did you install the radio first"
n00b: "oh no, what's that"
Not to mention you, yourself, mention in your first few posts that you didn't know what it was, you just figured you'd flash it because you thought it would help with some kind of force close. When you do something like that, n00b or not, you are gonna take some flaming from the forum. Sorry this is just how these things work. There are thousands of people on these forums that spend weeks reading before they do anything to their phone, and there are just as many who read for 20 minutes and just start doing things. The very nature of a open forum of this type makes it difficult to have organized data. Everyone seems to understand that but some are unwilling to put in the time necessary to gather all the proper resources and data. Unfortunately, you seem like one of these poor people.[/RANT]
My only comfort to you now is go here and give your phone a proper burial....
Click to expand...
Click to collapse
My sentiments exactly... You've BRICKED your phone, not had a small glitch that we can fix. Its called brick for a reason because your phone is now only useful as a BRICK! Its not reversible at this time, nor would I suspect it to be reversible in the near future. Next time, read, read, read, read, read... and then read some more before you try to flash some mystery signed-spl.zip that you found on your computer...
yea i made the same mistake a few months back your fones at a better place now...No more updates, no more wipes or backups just ~peace~
would like to thank DirectMatrix for directing him to my **Obituaries** thread
-Plays taps
Well, everything fine i finally made all to work unroot and stuff and when to write the spl ( death spl ) my phone is dead, manifestation by not doing anything else but starting vibrating and showing me 't-mobile G1' bootup image, in rest nothing works, it doesen,t listen to any button push, is frozen, it even recharge battery when plugged in to the power supply wile closed. Please help me this is desperate i need working phone!!! Thank you!
If it doesn't go to bootloader or recovery, it's bricked. Gonna have to use ezterry's jtag method if you want it back:
http://forum.xda-developers.com/showpost.php?p=5911627&postcount=302
thank you this looks interesting but i am awake of 48 hours + hope to understand how to connect it by jtag and have the necessary.
I really don't see how anyone can flash the SPL without flashing the radio first....its in big huge red letters everywhere and its always mentioned to people who want to install the death spl.
At any rate....don't you need a working G1 to bring back a bricked one?
Here it was because i interrupted the writing process accidentally
Does that mean you pulled your battery during the SPL flash?
Yes, and the only thing is doing now is the usual vibe at boot and frozen on the screen with the boot image t-mobile g1 stupid and annoying.
G1ForFun said:
At any rate....don't you need a working G1 to bring back a bricked one?
Click to expand...
Click to collapse
No I don't think so.. as I understand it, you just need the jtag serial interface and a brick with the blue light mode working.
Well too much time it takes the jtag method and don't think i have all i need and i don't really want to start soldering to the mainboard, on htc with win mo i could do a hack to install from pc with ruu flasher on the old stuff but here there is nothing working and couldn't find enough details what is 'blue light mode' anyhow if still doesen't work with simple methods i'l pay someone with a gsm box compatible with this like otr or what is its name. And BTW shouldn't it be working with mini usb to serial converter too?
Started to root the phone went back to 1.5, worked fine, applied FlashRec.apk and Amon Ra’s Recovery Image installed all that correctly worked fine. Went to install a new radio and spl and applied spl and when i go to start the phone it gets stuck at the G1 boot screen. Tried to book into recovery mode nothing happens , tried to hard & soft reset nothing happens. Phone just stays stuck at the G1 left it on for an hour and still nothing. Please help in any way or ask for more info if need.
Thanks in advance.
if you flashed the danger spl before flashing the new radio, your phone got permanent brick and cannot be solved without JTAG or changing the motherboard.
OK- I have the same problem, except I flashed the wrong radio.
(I thought I needed to update it for a different ROM, but.)
No fastboot, no recovery-- If I hold down the trackball, the screen wont come on, but the blue LED does. Is that useful to me at all??
Can JTAG help me? or is there another way?
I was reading about mtty-- but i'm not sure if that'll work for my G1.
Anything to unbrick this--- I really need my phone for finals week which started to-day.
JTAG is your only option.
techn0crat said:
Can JTAG help me?
Click to expand...
Click to collapse
Yes
techn0crat said:
or is there another way?
Click to expand...
Click to collapse
No.. at least none known yet
techn0crat said:
I was reading about mtty-- but i'm not sure if that'll work for my G1.
Click to expand...
Click to collapse
MTTY is just a program to talk to the serial port; it is actually part of the JTAG solution as well .. but as mentioned it will not help you at this point in time.
techn0crat said:
Anything to unbrick this--- I really need my phone for finals week which started to-day.
Click to expand...
Click to collapse
JTAG.. but unless you live near me or one of the very very few others who are set up for jtag hacks.. and that person is confident enough not to make the main board of the phone one big solder blob [I am but I'm not sure if some of the others I've heard poke JTAG are as confident].. it will take you a large chunk of time to learn what is needed to make it work.. or longer than the finals in the mail.
Thus I recommend.. get a cheap phone at the stand at the mall.. and pass your finals before worrying about the brick.
Since everyone who has caused a brick has either (1) not properly followed the directions and warnings.. or (2) did something in haste missing an important step; it will be no good to race it together during finals.
this dream was sent to my friend as a replacement
never used
he gave it to me sayingit wont boot
it gets into fastboot
it says:
DREA100 PVT 32B
HBOOT-0.95.0000
CPLD-4
RADIO-1.22.12.29
Sep 2 2008
so i formatted his sdcard, got the DREAIMG.nbh put it on his sdcard, entered into fastboot, and it ran the install (rainbow screen) nothing was happening from there before i copied the DREAIMG.nbh to it, so at least this installed successfully)
then i rebooted (call-menu-power at same time) and still stuck at G1 screen after twenty minutes...whats happening here, anybody?
tnpapadakos said:
then i rebooted (call-menu-power at same time) and still stuck at G1 screen after twenty minutes...whats happening here, anybody?
Click to expand...
Click to collapse
Odd, the nbh files usually flash a full system.. thus while they might leave you with a rom you don't wish to have they usually will boot afterwards. You did let it fully flash all the partitions correct?
What nbh did you find/flash?
And. Can you still enter the spl or recovery.
ezterry said:
Odd, the nbh files usually flash a full system.. thus while they might leave you with a rom you don't wish to have they usually will boot afterwards. You did let it fully flash all the partitions correct?
What nbh did you find/flash?
And. Can you still enter the spl or recovery.
Click to expand...
Click to collapse
RC29 from the cm wiki, flashed successfully, nothing but fastboot screen, no boot, no recovery boot
weird
tnpapadakos said:
RC29 from the cm wiki, flashed successfully, nothing but fastboot screen, no boot, no recovery boot
weird
Click to expand...
Click to collapse
lol, wtf? wait... don't some phones need a goldcard for this?
r3s-rt said:
lol, wtf? wait... don't some phones need a goldcard for this?
Click to expand...
Click to collapse
yeah i dont know, all i know is i can ONLY getinto the bootloader, which is the ORIGINAL bootloader (0.95.0000)
what can i do with this thing?
what do i flash to it (cause it aint the RC29 DREAIMG.nbh)?
i refuse to lose
well only bootloader means nothing. you cold be getting a bad .nbh and the recovery partition could have something nasty on it. both of those not working doesn't automatically make it a brick. a working bootloader says everything is ok.
set up fastboot and fastboot a new recovery image.
then see if your recovery works. next time i don't respond, feel free to pm me again, lol. i really have a hard time keeping up with where i post.
of course: you can also fastboot a new spl:
http://code.google.com/p/android-roms/downloads/list?q=label:SPL
I recommend:
EngBootloader_v2_NoSigCheck.zip
That way you don't have to mess with that nasty danger spl and then you actually will be bricked.
Hi everyone really sorry for opening a new thread for a G1 brick.
My G1 has stuck at the T-Mobile screen and on pressing Camera+Power i cant get into fastboot to restore using the .nbh file.
I am not able to get into recovery using power+home key also.
There has to be a way to get my dream back....
please please please help
JTAG or go for a replacement. I'm guessing it's a DangerSPL brick, right?
Danger SPL
Yes dude....
i have done this so many time.....
this time i forgot to update the radio first and this is stuck....
Someone should have a solution for this....
I read many thread which say use it as a paperweight...
I am not loosing hope....
XDA Member will have some solution.....
Maybe you should try to keep current on developments.
There is NOT A SINGLE REASON to use the deathspl.
As for your "poll"... what do you expect to learn from something like this? Do you realize that any numbers you get will be completely MEANINGLESS?
lbcoder said:
Maybe you should try to keep current on developments.
There is NOT A SINGLE REASON to use the deathspl.
As for your "poll"... what do you expect to learn from something like this? Do you realize that any numbers you get will be completely MEANINGLESS?
Click to expand...
Click to collapse
By adding the poll I am just trying to avoid post which says hey even i have the same problem.
I was upgrading to cm 5 which needs deathspl.
chinmayfun said:
I was upgrading to cm 5 which needs deathspl.
Click to expand...
Click to collapse
Aaaaannnnnd.... it doesn't need it
http://forum.xda-developers.com/showthread.php?t=704560
lbcoder said:
There is NOT A SINGLE REASON to use the deathspl.
Click to expand...
Click to collapse
Sure there is as its one if the few full engineering spls. And I don't think your latest development will ever be quite as user friendly (however some more configuration it will be very close)
The real user friendly fix/patch for 1.33.2005 (those that know what they are doing can decide if any benifit of the spl exists) is an assertion statement in the recovery script to check the radio version is not one of the two common 1.x ones.
(the evil patch is to make the assertion somehow also autoinstall the lattest Rogers e911 patched rom if the user has the 1.x radio. Because atm the rogers rom appears to be very safe from the user messing up the boot chain.. actually we may need to "perfect" the spl a bit more I think it will let us erase hboot)
I am still a newb to the android scene - and do believe I as well made the same mistake - and have bricked my G1.
If eveything I've read is accurate, I can purchase a donor phone - broken screen, or other issues - so long as the mother board is still good.
Swap out the new mother board for the bricked one, and have a working phone again - right ?
Have an opportunity on a donor phone - have no issues pulling phones apart, and putting them back together
But just want to make sure I understand the basics
Thanks in advance for any replies
Motherboard only option ?
Is replacing the motherboard the only option left ?
I am not sure i would be able to do that
Worst day of my life i screwed up big time
Any help is appreciated.
Some tool to recover back to original.
I can understand there is no way to repair as I am not able to get into recovery nor fastboot so cant adb also...
youtube
i checked the below video bt this is kinda a complicated and nt a solution for me
chinmayfun said:
i checked the below video bt this is kinda a complicated and nt a solution for me
Click to expand...
Click to collapse
There is no tool to get it back except by the options listed above. If you are not going to switch the mobos in the G1 then you won't be able to do the other option either. There is no software that can bring your G1 back after a deathspl.
protomanez said:
There is no tool to get it back except by the options listed above. If you are not going to switch the mobos in the G1 then you won't be able to do the other option either. There is no software that can bring your G1 back after a deathspl.
Click to expand...
Click to collapse
Thanks....
i will have to plan out on buying a new android....
had waited for a long time to get tht android phone from a friend in usa....
now there are many android phones available in india.... will have to start saving some money.... cant live without an android....
hey,
i had the same prob.
only thing,
mine bricke in cause of a radio update,
i tried all which was in my head,
and all i can do
but after some nights spending to my phone i found this:
i copied my nand backup to root of sd,
and connected it to pc
first he told me, device not known
so i tried to boot the modified recovery,
and *tada* i was in recovery mode,
plz try and tell me if it fix your problem,
for mine it did
best regards,
psycho
Mine is also due to radio update dude, before flashing spl the radio has to be flashed i and forgot to do that.
Will try out your suggestion, just hoping that it work and my g1 is back to life.
Ne ways appreciate your suggestion.
Please let me know if you were able to get into recovery mode prior to putting the files on the sd card.
And if you could tell me the list of files (if u had nething other then the nand update) which you put on the sd card, i can replicate the exact process.
Thanks,
Chinmay
Hope
Is there any hope to get the G1 back to life from the Death SPL Brick ?
You should read instructions carefully man. Its not that hard. You should always verify that you have a compatible radio before flashing DangerSPL.
There is a method to recover your device and it involves a lot of time and patience. Google "JTAG".
Sent from my HTC Dream using XDA App
"JTAG".
me too, my G1 Bricked (Not able to fastboot). but i wanna know if the JTAG method work 100%.please.
Hi everybody,
I was trying to load the cyanogen mod to my G1
Had Android 1.6 and Radio 2.22.23.02
I downgraded to RC29 successfully
Rooted my phone
Loaded recovery-RA-dream-v1.7.0.img. Flashed successfully
Then started following instructions below:
wiki . cyanogenmod / index.php / DangerSPL_and_CM_5_for_Dream
I got stuck in step 6
It is probably because downgrading to RC29 also downgraded my radio version. I did not check the radio version again after I downgraded
Using danger.spl bricked the phone
I searched online and found some solutions with JTAG, but I am in Turkey and do not have access to purchasing these from ebay or the know-how to apply them (as you can tell from my mistake above!)
1) I found the below solution, but not sure if it will work:
code . google / p / android-roms / wiki / Unbrick
They say it will only work if you have soft-bricked your G1. I'm not sure
2) Others say I need to call T-mobile Customer care (where I purchased the phne from), but that was about a year and a half ago. How long is the warranty on the G1? 1 year or 2 years?
3) And yet others say use it paper-weight
Should I go for option 3?
What do you think?
Wiki Instructions
What is DangerSPL?
This SPL is actually a port of the Magic/MT3G (Sapphire)'s SPL to the Dream/G1. Called danger because not only does it wipe your data in the repartition process (data can be restored with Nandroid restore after flashing DangerSPL), it has a chance of bricking your phone if you would ever choose to downgrade the radio after flashing it (see below for compatible radios). Never flash a 1.x, 4.x, or 6.x radio with DangerSpl
It is not required for CyanogenMod versions 4.X (CM4) and below, but required for the CM5 series on the G1/Dream.
Why is it required for the CM5 series on G1/Dream?
The G1/Dream's /system partition was originally created to take ROMs up to 64MB. The CM5 series for the G1 & Magic/MT3G is currently too big to fit on this partition.
Why don't Magic/MT3G users have to apply it?
The Magic/MT3G (Sapphire)'s /system is set to take ROMs up to 96MB by default, so no SPL change is needed.
Is it dangerous?
While the method of applying it has been perfected over the course of its use, any modification of SPL/Radio/ROM carries with it an inherent risk. That being said, if you pay attention, follow instructions, and plan your approach, it is actually an easy process.
How do I check if I already have DangerSPL?
Boot into fastboot mode by turning the phone on while holding the camera button and pushing the power button. The second line contains your SPL version. If it ends in 2005 (eg 1.33.2005) then you have DangerSPL installed already. The line with RADIO tells the radio version, which is important if you don't have DangerSPL. To leave fastboot mode, press MENU+SEND+END at the same time.
Installation
Warnings
Make sure that you have a full battery during the steps below and at no point remove power from the device (i.e. no battery pulls!). See the first two bullets in troubleshooting regarding battery use after flashing CM5 and fixes for higher-than-expected battery drain.
There has been some development/debate over DVT/PVT and bricks. Optional reading (but still recommended): XDA forum
Prerequisites
A rooted G1/Dream
A compatible radio (IMPORTANT: If you just rooted, the RC29/RC7 install includes a 1.x radio and you MUST install one of the 2.x radios below before DangerSPL)
2.22.23.02 seems to get more bars for T-Mobile US customers, though non-US users might have better luck with 2.22.19.26i.
(HardSPL/Engineering Spl Users) Radio installations can be had by fastboot flash radio radio.img after extracting radio.img from the .zip
Either of the following radio versions is acceptable.
Radio 2.22.19.26I
Radio 2.22.23.02 (G1)
Rogers Dream users: A 3.X radio is Danger compatible (eg 3.22.26.17)
Failure to meet the Prerequisites WILL result in a BRICK!
Files required
Danger Spl
gapps-ds-ERE36B-signed.zip, Mirror1
Latest CM5 for Dream/Sapphire
ONLY Roger's Dream users: EBI1 kernel for 5.0.x
Steps
It has been brought up that Clockwork Recovery struggles with this guide, so Amon_ra is v1.7.0 recommended. If you have CM or older recovery, upgrade to Amon_Ra first.
Please if you need to diverge from these steps for any reason start over from step 1 when you return.
Boot into Fastboot (Power on the phone holding the camera button) This will either show a screen with dancing androids or a "rainbow" splash. Here you will find the hboot/radio version:
radio 1.x: You will need to upgrade this to a 2.x radio before running this process.. please upgrade and re-do this step (Ie. verify you see the updated radio in fastboot before continuing)
radio 2.x: You may press MENU+SEND+END at the same time and proceed (unless hboot-1.33.2005 is installed; indicating you already have dangerSPL)
radio 3.x: You may press MENU+SEND+END at the same time and proceed (unless hboot-1.33.2005 is installed; indicating you already have dangerSPL)
Copy DangerSPL (spl-signed.zip), CM 5.0.x, and gapps-ds-ERE36B (& Ebi1 port if required) to the root of your sdcard.
Reboot/Boot into your custom recovery by holding down the 'home' key before the G1 splash appears.
Make a Nandroid Backup (ext not required) (recommended for upgrading users, not required for freshly-rooted users)
Flash DangerSPL (spl-signed.zip). It will install and then ask you to reboot to finish the installation
Reboot as prompted at the bottom of the screen. This will finish installing DangerSPL and reboot back into recovery so you can flash your ROM.
Once back into recovery Wipe Data/Factory Reset
Flash CM 5.0.x THEN gapps-ds-ERE36B (& Ebi1 port if required); then reboot (Boot may take longer than normal)
Login to Android/Google as per usual
If you want to restore the nandroid backup (to attempt an unrecommended no-wipe upgrade between CM4.2 and CM5)
[Optional] Reboot to recovery, and issue a Nandroid Restore, then follow the regular instructions .
This command will attempt to restore user data.
Restoring will also restore your previous Firmware, so you have to follow the instructions to get 5.0.x again
Note: If this causes undesired consequences (ie bootloops, FC's, etc) then run Fix Permissions/'Fix UID Mismatches'.
***************************************
Instructions for the 'soft-brick' (I think)
How to Un-Brick Your Phone
(Method 1)
Ok so you're trying to put this really cool new custom ROM on your phone and then suddenly, your phone won't start up…well my friends, you have got yourself a bricked phone. The thing you worry about the entire time you're rooting, and flashing your phone, has now become reality. Well, fear no more, for I, CTDroidBeast have found a way to unbrick your device!
It's really easy. It's actually easier then rooting your phone, believe it or not.
Ok, you will need a new SD card, because I bet if you use the one out of your device your computer will not be able to read it. But if it does then HEY, you're in luck. You don't have to spend your money on a new SD card.
So let's get started.
Step 1: Turning Off Your Phone
Because you have a bricked phone, you can't just hold the power button. So if your phone is not already off then you're going to want to take out the battery.
Step 2: Preparing Our SD card
Take out your SD card and put it into an SD card reader or some type of other adapter so that we can view it from our computer. If you cannot view the SD card on your computer then you're going to need a new SD card.
Download DREAIMG-RC29.zip and unzip the file.
Reformat the SD card to FAT32 and copy the DREAIMG.nbh onto it.
Safely eject the SD card.
Put the SD card into your device.
Step 3: Wipe The Phone
Hold home and press the power button.
When you see the image of an ! mark, open your keyboard and press Alt + L if you cannot see any command options.
Do a factory reset by pressing Alt + W or just using the trackball.
When the reset is done, go ahead and hold the camera button and select the reboot system now option with your trackball.
Step 4: Flashing The Phone
Once the grey screen pops up (or the white screen if your phone was rooted with JesusFreke) it will ask you to hit a button to start installing the image…press that button. DO NOT DO ANYTHING TO STOP THIS PROCCESS. It will take about 8-12 minutes.
When the image has completed the installation (it will say completed), go ahead and press the green, red, and menu buttons at the same time. The phone will reboot.
And your done! Your phone is now unbricked!.
Please help!
YOU FAILED.
If you don't take the time to read and learn what you are doing, why should anyone take the time to help you?
WHY would you EVER install RC29? IDIOTIC MOVE!
WHY would you EVER install deathSPL? IDIOTIC MOVE!
I say you deserve what you got.
lbcoder said:
YOU FAILED.
If you don't take the time to read and learn what you are doing, why should anyone take the time to help you?
WHY would you EVER install RC29? IDIOTIC MOVE!
WHY would you EVER install deathSPL? IDIOTIC MOVE!
I say you deserve what you got.
Click to expand...
Click to collapse
I was just following the Wiki instructions ( Full Update Guide - G1/Dream Firmware to CyanogenMod ) here:
My radio before downgrading was 2.x, so I assumed it would still be the same after the RC29 downgrade, but it turns out the downgrade also dongrades the radio to 1.x
therefore death spl bricked the phone
I should have checked the radio version for a 2nd time before flashing death spl
Is there any way to fix this now??
HEARTBREAKER123 said:
I was just following the Wiki instructions ( Full Update Guide - G1/Dream Firmware to CyanogenMod )
Click to expand...
Click to collapse
You did not follow the instructions.
You deliberately skipped step one on the danger spl instructions. Put there so that those who didn't realize the radio had become downgraded didn't do what you just did. You also ignored the warnings on that page that rc29 installs the 1.x radio.
HEARTBREAKER123 said:
Is there any way to fix this now??
Click to expand...
Click to collapse
What part of not having the right radio will brick your device wasn't understood..
by all means hope your recovery is messed up and that you have access to fastboot when you attatch a USB wire.
Otherwise there is jtag. .. bit more complex than flash spl-signed.zip after being 100% sure a 2.x radio is installed however..
Another option is replace it.. some have found replacing the main board + daughter board of a working phone in bad cosmetic shape (screen cracked) a cheap alternative here than a brand new dream. Still requires reading the service manual to properly disassemble what you need without having a bit of a mess.. particularly if you skip a step.
My recommended solution is to find a phone you can deal with stock firmware buy it and sell the rest of your dream as is.. you want root you need to understand the instructions not just follow them.
Alright, well I think he got the point - he should have followed instruction better
I'll keep it as straight forward as possible, no there is not a way you can unbrick your phone without the JTAG tools. T-Mobile's warranty is only one year, afterwards they will not replace your device for any reason.
The soft brick solution you posted will not work, because you have a hard brick.
I believe you only have a couple of solutions.
a) Get a new G1
b) Buy an old G1, preferably one with a broken screen so its cheaper, and place the motherboard of that G1 into your current one
c) Work with some members of XDA and see if you can work out an arrangement to get you the JTAG tools, though this is unlikely to work and difficult to do.
I'm sorry that you have broken your G1, it's a terrible feeling to break your phone in this way where everything is physically still perfect. I believe your best bets are probably solution "a" or "b", you can shop around locally and see if you can find anything
Best of luck.
Thanks for the help.
I think I will try and get another G1 to see if I can replace the motherboards
HEARTBREAKER123 said:
Thanks for the help.
I think I will try and get another G1 to see if I can replace the motherboards
Click to expand...
Click to collapse
You know, if you're going to all the trouble of taking it apart and planning on essentially throwing the mainboard in the trash anyways, what do you really have to lose in attempting to jtag the thing? $2 worth of components and a couple hours of your time? Worst that happens is you fry it, in which case you were planning on trashing it anyway.
lbcoder said:
You know, if you're going to all the trouble of taking it apart and planning on essentially throwing the mainboard in the trash anyways, what do you really have to lose in attempting to jtag the thing? $2 worth of components and a couple hours of your time? Worst that happens is you fry it, in which case you were planning on trashing it anyway.
Click to expand...
Click to collapse
Like the OP said, he lives in Turkey and is unable to purchase these items on eBay.
SolemnWishing said:
Like the OP said, he lives in Turkey and is unable to purchase these items on eBay.
Click to expand...
Click to collapse
Turkey is NOT a back-woods country and there ARE LOTS of sources besides ebay. In fact, ebay is the LAST place you should look for electronic components.
I GUARANTEE that the required components can be purchased in STORES all over the place in Turkey.
lbcoder said:
You know, if you're going to all the trouble of taking it apart and planning on essentially throwing the mainboard in the trash anyways, what do you really have to lose in attempting to jtag the thing? $2 worth of components and a couple hours of your time? Worst that happens is you fry it, in which case you were planning on trashing it anyway.
Click to expand...
Click to collapse
$2? I thought Jtag cost like 70 bucks
racerxgt said:
$2? I thought Jtag cost like 70 bucks
Click to expand...
Click to collapse
Okay, I have good news and bad news
THe good news is that I was able to find someone with a jtag adapter and he fixed the phone for me for $50
Being more careful this time, I went through the wiki steps and installed CM 5.0.8 and gapps-ds-ERE36B-signed
Yaay!
But then I noticed that CM6 was out, and that it had flash, so why wait, right?
I flashed CM6 with no problems, rebooted the phone, logged in, everything seemed OK, except that I didn't have google apps
So I flashed gapps-mdpi-FRF91-signed.zip and... I wasn't able to log on to google!
You know the menu that asks you to sign in to your google account at the beginning
It says "touch the android to begin"... And when I touched the android, it wouldn't ask for my username and password.. Right click would go into 'Wireless Settings', and I was able to successfully define an APN and get a 3G connection, however, even after all that, and when the phone had reception,
touching the android would make the android change color, but it wouldn't let me go to the next step!
So I decided to flash the previous google apps
Now the phone does not boot in normal mode
I can access the bootloader and the fastboot menu (both Camera+Power and Home+Power work fine), but I am not sure how to fix the problem I have
I tried downgrading to Android 1.5 and starting over, but when I go into the bootloader menu, I see 3 androids with skateboards and the following options:
CAMERA_STEP2 : Hboot mode
SEND: Reset device (Doesn't reset, it just reboots when you try)
ACTION: Restart to hboot
MENU: Power down
And when you are in hboot mode, you can't click anything
How can I revert to CM 5.0.8??
Also, is it normal for the new gapps to cause this type of an error?
HEARTBREAKER123 said:
Okay, I have good news and bad news
THe good news is that I was able to find someone with a jtag adapter and he fixed the phone for me for $50
Being more careful this time, I went through the wiki steps and installed CM 5.0.8 and gapps-ds-ERE36B-signed
Yaay!
But then I noticed that CM6 was out, and that it had flash, so why wait, right?
I flashed CM6 with no problems, rebooted the phone, logged in, everything seemed OK, except that I didn't have google apps
So I flashed gapps-mdpi-FRF91-signed.zip and... I wasn't able to log on to google!
You know the menu that asks you to sign in to your google account at the beginning
It says "touch the android to begin"... And when I touched the android, it wouldn't ask for my username and password.. Right click would go into 'Wireless Settings', and I was able to successfully define an APN and get a 3G connection, however, even after all that, and when the phone had reception,
touching the android would make the android change color, but it wouldn't let me go to the next step!
So I decided to flash the previous google apps
Now the phone does not boot in normal mode
I can access the bootloader and the fastboot menu (both Camera+Power and Home+Power work fine), but I am not sure how to fix the problem I have
I tried downgrading to Android 1.5 and starting over, but when I go into the bootloader menu, I see 3 androids with skateboards and the following options:
CAMERA_STEP2 : Hboot mode
SEND: Reset device (Doesn't reset, it just reboots when you try)
ACTION: Restart to hboot
MENU: Power down
And when you are in hboot mode, you can't click anything
How can I revert to CM 5.0.8??
Also, is it normal for the new gapps to cause this type of an error?
Click to expand...
Click to collapse
*FACEPALM*
goldenarmZ said:
*FACEPALM*
Click to expand...
Click to collapse
Don't facepalm just yet
I managed to go back to 5.0.8 after doing everything from scratch
I guess I will use it like that for a while until CM6 / google apps stabilizes
HEARTBREAKER123 said:
Okay, I have good news and bad news
THe good news is that I was able to find someone with a jtag adapter and he fixed the phone for me for $50
Click to expand...
Click to collapse
I bricked my G1 as well, but I'm not in the US
Do you have an idea what the JTAG adapter looked like ?
wow you guys sound mean to the poor guy when he was just making a newbie mistake. i remember when i was making all of those mistakes...hell im still making those mistakes and even thou i have gotten my fone to freeze on the g1 logo or even just go into a constant reboot im glad iv been able to fix the problem everytime and still dont know what im doing im just learning. but hey isnt that procedure that you have up there an unrooting procedure???? and for those getting the wrong gappss try downloading the tiny mdpi on the dream that one worked for me, the mdpi didnt work at all till i tried that one got it from the cyanogenmod site. by the way i gotta say thanks to all the devs, which i had a brain like yals id love to join in on developing but im kinda an idiot here lol
spike210 said:
wow you guys sound mean to the poor guy when he was just making a newbie mistake. i remember when i was making all of those mistakes...hell im still making those mistakes and even thou i have gotten my fone to freeze on the g1 logo or even just go into a constant reboot im glad iv been able to fix the problem everytime and still dont know what im doing im just learning. but hey isnt that procedure that you have up there an unrooting procedure???? and for those getting the wrong gappss try downloading the tiny mdpi on the dream that one worked for me, the mdpi didnt work at all till i tried that one got it from the cyanogenmod site. by the way i gotta say thanks to all the devs, which i had a brain like yals id love to join in on developing but im kinda an idiot here lol
Click to expand...
Click to collapse
bigest mistake evar was probably buyng tha damn mobo ...you see i have 3 HTC's 1 HTC Dream that work's just fine , 2 T Mobile G1 that it's a piece of **** ( it got's nothing in comon with HTC dream it's just a cheap crap copy of the original ) and 3 it's a HTC with Win Mobile wich i think it's by far the most stable mobile operating sistem for now , all of you will say that it does not work like that , but think about this .... how manny win mobo's hawe ever been bricked?! and how manny android mobos are there bricking every day ? your android will brick eventualy ... oh yeah and i am selling 2 HTC dream Black and white
Thumb's upp if you are born in the rong generation )