Database Develop

Am I Bricked?

I was updating my SPL and upon reboot I got the lovely looping T-Mobile G1 screen, camer+power, back+power, and menu+power all work, but I really have no clue what to do as to fix it, I am new to this, no I did not make a recover because I had just upgraded to Cyanogen's backup, wiping didn't seem to work, I think it was possibly because my rom was out of date? I have JFv1.51_CRB43-US, so my question to you guys is, could going out and buying another SD card and dropping a newer rom and putting the new card in my phone fix my problem?

If you were upgrading to the 1.33.2005 SPL, you need to reflash with whatever rom you are using. The SPL effectively wipes the rom out, so you need to put it back.

Yeah, I just read that in the fastboot for noobs thing, thanks for the info!
Edit:
Do I have to reboot with the exact same rom as before the SPL update?

In case you missed the key point, using that hacked SPL has the effect of WIPING ALL YOUR DATA, so how, if the data is shot, could it possibly care that you write the same thing onto it as it had before? Answer is that it DOESN'T. Now go ahead and write whatever you like to it.

Thanks, was just wondering. :x

Gotta learn one way or another.

Stuck on g1 screen - can't boot recovery, no bootloader

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

Let's Do Work. Another Fix My G1 Thread!!!

Why hello there.
Thought I'd start with a nice little greeting, if you're reading this hopefully you're looking forward to a nice little task. My G1 is entered paper-weight mode rather than my fast boot setting and it's starting to get rather redundant so this is my last resort. There's the premises of my problem here's a little more detailed one for ya.
So I have a launch G1 with Cyanogen's latest 4.2.4 rom installed with the latest radio & any of the other necessary things flashes, etc. I'm honestly pretty good with these kinds of things through actual knowledge from here for just trial and error but this is something I haven't had to deal with for a LONG time. The infernal pause screen of G1 death. It won't leave the "T-Mobile G1" boot image after being flashed / wiped / all around cleaned up. I'm curious if it may just be the G1 or maybe something else caused a corrupted image for some odd reason.
Prior to getting this to happen, my keyboard wouldn't type correctly. The space bar would result in some random key being pressed and in essence, my phone typing by itself. So either my phone's possessed or.... something far worse. If you happen to know what exactly that is, please help me out! I'm open to suggestions, I've tried other builds and I'm about to just grab some old roms and see if maybe this works. If you have tips or need to know any more information please, just ask.
Thanks! Adderall will make this much easier I just need some ideas
-chatty chatt mic-chat chat.
Boom.

The fact that your keyboard was messing up is ominous. Are fastboot and recovery working ok? Can you post a startup log?

I would flash the HardSPL
the spl monitor the control input (afaik because people w/ qwertz keyboards said flashing special spl's converted them to qwerty)
before you mess with that though, make sure you followed the install directions for 4.2.4
you dont just flash it as an update.zip if your switching to cyan for the first time.
you need to flash the HTC recovery image first, then flash cyan on top of that

no see i've been around here since the beginning of the G1 mods and such I know what to do with everything it just started going wild. I'll try flashing the hardSPL and see what happens but this is just odd. I'm trying one more time to flash a new rom on my phone with a freshly formatted sd card then we'll see what happens

(SOLVED!!)Major issues!!!

Ok after countless searches on Google, and on here, with no help at all...I am making a thread. I decided a few days ago that since my phone ran terrible no matter what rom i used, that maybe the person who rooted it screwed it up. I decided to go back to stock, then back to root, then back to the rom, well somewhere i messed everything up. I had everything going good, but then flashed a bad .nbh from what i understand, got that all good now that i have a sd card adapter, now i have rc29 installed and running. When i try to use adb since i have no 3g and need wifi, it keeps saying cant find device, even tho i have used adb in the past just fine, and <enter>reboot<enter> does restart my phone. So i thought maybe its a spl error, i dled danger spl (newest from what my search found) but every time i go to recovery and try to flash update.zip i get errors. So i tried flashing the orig. just to see if it was a bad dl. Same thing. Errors. Im getting really frustrated. If someone could please help me i would greatly appreciate it. my email is [email protected] or [email protected] send me a email if you need an invite to gwave, id rather talk on that. Thanks Guys.

You can't flash a new spl with a stock rom. Did you make sure you have the right drivers installed for RC29.

shorty52732 said:
Ok after countless searches on Google, and on here, with no help at all...I am making a thread. I decided a few days ago that since my phone ran terrible no matter what rom i used, that maybe the person who rooted it screwed it up. I decided to go back to stock, then back to root, then back to the rom, well somewhere i messed everything up. I had everything going good, but then flashed a bad .nbh from what i understand, got that all good now that i have a sd card adapter, now i have rc29 installed and running. When i try to use adb since i have no 3g and need wifi, it keeps saying cant find device, even tho i have used adb in the past just fine, and <enter>reboot<enter> does restart my phone. So i thought maybe its a spl error, i dled danger spl (newest from what my search found) but every time i go to recovery and try to flash update.zip i get errors. So i tried flashing the orig. just to see if it was a bad dl. Same thing. Errors. Im getting really frustrated. If someone could please help me i would greatly appreciate it. my email is [email protected] or [email protected] send me a email if you need an invite to gwave, id rather talk on that. Thanks Guys.
Click to expand...
Click to collapse
It sounds like you're back to a "stock" phone after using the RC29 downgrade, which is a pretty good thing for you at this point because the stock recovery image just saved you from bricking your phone, by not allowing you to use update.zip to flash the danger spl with the old radio that you have from installing RC29.
That being said, now that you're back on RC29 you're gonna want to follow the rooting procedure over again to install a custom recovery image and then you can go about flashing your new rom after that.
You can follow the guide in Cyanogen's Wiki, Skip the First section called Downgrading since you've already done that, and pick up on the next section called rooting
http://wiki.cyanogenmod.com/index.php/Full_Update_Guide_-_G1/Dream_Firmware_to_CyanogenMod

Thanks.. I did end up following that wiki, but the heart n sole of the problem this whole time was a bad usb cable, tried a diff. one and it worked..I feel like a jackass,,

G1 Bricked (Not able to fastboot)

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.