Database Develop

I think I bricked him :(

Something screwed up today after installing that ApptoSD application from the market and I had to downgrade to RC29 again. That was all fine.
Now I was in the process of upgrading to CM 4.0.4. I already installed the old HardSPL, and realized I needed to install the 'new' one. I did this, and upon reboot my phone is stuck at the G1 screen.
Home+Power and Camera+Power do absolutely nothing.
Am I ****ed? This sucks.

jackaz said:
Something screwed up today after installing that ApptoSD application from the market and I had to downgrade to RC29 again. That was all fine.
Now I was in the process of upgrading to CM 4.0.4. I already installed the old HardSPL, and realized I needed to install the 'new' one. I did this, and upon reboot my phone is stuck at the G1 screen.
Home+Power and Camera+Power do absolutely nothing.
Am I ****ed? This sucks.
Click to expand...
Click to collapse
Yes, its gone. You need to install the radio update before the SPL update. Don't know why you would install the update that kills so many phones without reading up on it...

for the record: cm4.0.4 and all cyanogen mods do not require the DangerSPL, hardspl works fine.

Wow you get a big ol' F for not doing your homework and thinking that you needed the newest thing, good job screwing yourself

Just like everyone else said your toast. I was first thinking why would you need to go back to rc29 because of an apps2sd issue or really any issue, you should have just reflashed a rom. Second (like the others said) you didn't need the new spl.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

WTB - spare batt and batt cover!

Whoa, didn't need to jump down my throat - I already flashed the new radio after HardSPL, but I suppose it doesn't matter anyway.
The phone bricked after installing that app, and upon restart it was stuck at the G1 screen, I had to leave the office so I reflashed to RC29 (as it was the only ROM I had on my laptop) while I was on the road (so no internet access) because I desperately needed my phone for a job I was attending. When I got back to the office I must have mixed up my update.zip files somewhere in the process.
Thanks for the help from the people that weren't dicks about it, at the end of the day it's only a phone. Time for a shiny new one.

It is pretty common knowledge that the DangerSPL will not work with older radio versions BUT I believe flashing RC29 downgrades your radio to an earlier version, therefore bricking your phone. If you decide to use DangerSPL or Haykuro's SPL (the same I think) in the future, make sure you flash HardSPL BEFORE restoring to RC29.
I would play the stupid card with TMO and see if they will send you a new one.
And if you don't already, use Cyanogen's 1.4 Recovery. You can backup and restore via Nandroid from the recovery image so you can have a working version on your SD card at all times and not need a computer to access it.

Just for my own knowledge,
A phone with the hard spl can be safely downgraded back to rc29 (if you needed to send it back to tmo for instance) correct?
It's the danger spl that can brick your system if you downgrade to earlier radio right?

dcorrea said:
Just for my own knowledge,
A phone with the hard spl can be safely downgraded back to rc29 (if you needed to send it back to tmo for instance) correct?
It's the danger spl that can brick your system if you downgrade to earlier radio right?
Click to expand...
Click to collapse
Correct......

downgrading by using rc also downgrades the radio and spl, does not matter what spl you are using. it takes it back. you will not brick by using the rc dreaimg.nbh

r4d14n7 said:
It is pretty common knowledge that the DangerSPL will not work with older radio versions BUT I believe flashing RC29 downgrades your radio to an earlier version, therefore bricking your phone. If you decide to use DangerSPL or Haykuro's SPL (the same I think) in the future, make sure you flash HardSPL BEFORE restoring to RC29.
I would play the stupid card with TMO and see if they will send you a new one.
And if you don't already, use Cyanogen's 1.4 Recovery. You can backup and restore via Nandroid from the recovery image so you can have a working version on your SD card at all times and not need a computer to access it.
Click to expand...
Click to collapse
Thanks for that information.
I'd play the stupid card but I'm guessing that being in Australia makes that pretty difficult eh?

hey you guys have an awesome prime minister

He gave use all $900 just for the fun of it. Great guy.
I guess I can try contacting HTC and see if they'll repair it, I'm expecting to pay for it but i guess it's better than paying for a new phone.

i was talking about his policies, like telling everyone that this is our country and that we will not bend over backwards to appese you and if you don't like it then get the **** out. we need someone like that guy here instead of ass kissing obama
sorry small rant
yeah you could call htc

Haha I know you were
I've got in contact with the repair center in my area and they're going to 'get back to me'.

I bricked my phone.

I mixed up my update files trying to update my radio and spl and installed the spl before the radio. And now it is stuck on the "t-mobile G1" screen. recovery won't work, fastboot won't work. Is there anything that I can do or is it gone for good?

Babyche43 said:
I mixed up my update files trying to update my radio and spl and installed the spl before the radio. And now it is stuck on the "t-mobile G1" screen. recovery won't work, fastboot won't work. Is there anything that I can do or is it gone for good?
Click to expand...
Click to collapse
lol......its gone....call tmobile and tell them your phone said it had an update and you said to update it and that you left it there for a while and when you came back it wouldn't get past that.

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Just another brick in the wall.

How did you mix up the ordering of the files? Sounds like you know which should come first...

Oh well. Thanks for the advice. I just call T-mobile and they are going to send me a new phone and give me a loaner phone until the new one arrives. Great.

I did know but I'm new to this rooting thing I just started Monday. I had my phone rooted but I messed up when i was switching roms. I didn't know I had to wipe everything when you switch to a hero rom. So I started over and picked the wrong spl from all the different files that I downloaded on my computer to do the root. Then combine that with all the different guides that I have been reading I was doomed. The funny thing is that as soon as I hit update I knew I messed up.

Babyche43 said:
I did know but I'm new to this rooting thing I just started Monday. I had my phone rooted but I messed up when i was switching roms. I didn't know I had to wipe everything when you switch to a hero rom. So I started over and picked the wrong spl from all the different files that I downloaded on my computer to do the root. Then combine that with all the different guides that I have been reading I was doomed. The funny thing is that as soon as I hit update I knew I messed up.
Click to expand...
Click to collapse
You don't need to reroot the phone to go to a hero ROM from another modded rom. You only need to flash the newest radio and then the special SPL (in that order)

Babyche43 said:
I did know but I'm new to this rooting thing I just started Monday. I had my phone rooted but I messed up when i was switching roms. I didn't know I had to wipe everything when you switch to a hero rom. So I started over and picked the wrong spl from all the different files that I downloaded on my computer to do the root. Then combine that with all the different guides that I have been reading I was doomed. The funny thing is that as soon as I hit update I knew I messed up.
Click to expand...
Click to collapse
Yessir the ol gut feeling.

that's the worst when you ****ed up and there is nothing that you can do to stop it. well unless you are like me and don't care and just do it anyway

Diceman4 said:
You don't need to reroot the phone to go to a hero ROM from another modded rom. You only need to flash the newest radio and then the special SPL (in that order)
Click to expand...
Click to collapse
I know but something happen when I went from a Cyanogen mod too a Drizzy hero rom to were it would work and kept boot looping (if that is a word) so since I don't know that much about flashing roms and all that I figured I would just start over and just install the hero rom from the beginning and that's were I installed the wrong update.

Babyche43 said:
I mixed up my update files trying to update my radio and spl and installed the spl before the radio. And now it is stuck on the "t-mobile G1" screen. recovery won't work, fastboot won't work. Is there anything that I can do or is it gone for good?
Click to expand...
Click to collapse
How would you know if you bricked your G1?will it be stuck in a certain logo it'll be stuck at?

will it be stuck in a certain logo it'll be stuck at?
hahahahahahaha yes. The very first one.

you will know your phone is bricked by the fact that it no longer wants to cuddle with you when your press power, or when it no longer gets in the mood when you press home and power, and you know all hope is lost and you will never get to the g-spot on your g1 when camera and power no longer does anything.
yes all the answers are in there lol

desperate plea for help

if anyone here who lives in Toronto ON that can fix my HTC rogers dream , please let me know im willing to pay in beer or straight cash, long story short
i get htc dream with 1.5 , i want to update to 1.6, my friend makes recovery image and puts on nandroid v2.2 and at bottom it says " build: cyanogenMod V1.4 + JF", console doesnt work, and he tried flashing via the update.zip , and since then its never gotten past the rogers splash screen. on the camera+power menu it shows the following
DREAM PVT 32B SHIP S-ON d
HBOOT -1.33.0009 (DREA21000)
CPLD-4
RADIO -3.22.20.17
May 12 2009 , 17:05:58
HBOOT
<SEND> fastboot mode
me and Ace 42 spent the last 2 days trying to fix this problem, we tried updating the "dreaimg.nbh " or w.e its called file and then we tried loading rogers htc dream roms found on this website, and it still wouldnt boot... im fearing the worst , as i cant get into console, the screen goes from
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
to just the black background with the android logo and the writing " build cyanogenMod v1.4 + JF" and its unresponsive, only way is to pull battery,
also now the fastboot menu says
DREAM PVT 32B ENG S-OFF
HBOOT -1.33.2005 (DREA21000)
CPLD-4
RADIO-3.22.20.17
APR 20, 2009 15:30:43
HBOOT
<SEND> fastboot mode
also the icons on the bottom are skateboards with the little green android guys ( before and after hboot changed)...
ok so now ace42 told me he thinks the only option left is to flash the radio, but he said theres a 50/50 chance it might permanently brick the phone since its downgrading ( i think i dont exactly remember what he said) ill get him to chime in here and say his side of this whole situation.
honestly i just want android 1.5 back, no fancy custom stuff, OR android 1.6 and as long as it works normally ill be quite happy and never touch this updating fiasco every again....

Looks to me like you flashed the danger SPL without updating to the 26I radio. I am pretty sure you own a paperweight.

please.. i dont want to hear that

ummm
you are gunna have to do this
http://forum.xda-developers.com/showthread.php?t=491350&highlight=stock+firmware
then after you do that, just either go to your settings and search for updates or root and get a CM rom

After re-reading you post, I am really not positive. I didn't notice you were using a rogers phone. The radio might be different. Hopefully someone with a rogers phone can confirm their radio with yours.

do you have another nandroid backup? if so... when you press camera+power, go into fastboot mode and fastboot flash system.img...etc, if not use fastboot to flash another update.zip

So after checking out some sigs from other Rogers users...they have the 26I radio with the 1.33.2005 SPL...so yea...I fear the worst for you. Good luck tho.

nandroid backup of the OS when the phone was working?? no i accidentally pressed the backup choice and it overwrote the original recovery with a nonworking rom

sockpuppet4 said:
So after checking out some sigs from other Rogers users...they have the 26I radio with the 1.33.2005 SPL...so yea...I fear the worst for you. Good luck tho.
Click to expand...
Click to collapse
, this is a ******* nightmare.. i dont have money for a new phone and i needed this phone for work...
cant i update or change SPL then change radio?
wait, my radio didnt change at all from the beginning to right now???
just the SPL... :|

32adream said:
, this is a ******* nightmare.. i dont have money for a new phone and i needed this phone for work...
cant i update or change SPL then change radio?
wait, my radio didnt change at all from the beginning to right now???
just the SPL... :|
Click to expand...
Click to collapse
Sorry man, it happens. Good luck to you. Maybe try and brick it all the way and get your warranty fix.

cant.. bought it second hand...

*checked spl & radio versions
*attempted to flash cyan mod
*tried micro hero
*tried regular rogers build by enomther
*console but was unable to acess
*was gonna try to flash dreaimg-rc29 but it contains older radio

ok so you can get into recovery and fastboot?

yes i can get into recovery and fastboot.

lol... chill.. this is NOT an spl brick. Sounds like your recovery image could be corrupt from a bad flash, but that's perfectly fixable. You know how to use fastboot from your pc, right? If not there are plenty of guides around here.. use fastboot to flash either cyanogen's recovery or amon_ra's.. from there, follow instructions to install CM 4.2 here: http://wiki.cyanogenmod.com/index.php/Upgrading_From_Older_CyanogenMod_Versions
Just don't flash that old radio.. thats not a 50/50 chance of brick, that's 100% cast-iron brick.
ITT: n00bs scaring n00bs.

ace42 helped me alot, i dont think he is a noob
ok from what you said, im gonna need step by step instructions on how to access fastboot from my pc. :| goldenarmz do you have gmail chat or msn??

I can't do a live chat atm, but I'm feeling helpful so I'll try to talk you through it here.. I'm just reading up on the rogers dream rooting process to try and see where you're at.
While you wait, download and indstall the android 1.6 sdk from here:
http://developer.android.com/sdk/index.html
http://developer.android.com/sdk/installing.html
You don't need to download eclipse or set up the adt, just get the SDK installed with the tools path defined.
I'm assuming you're on windows btw?

yep, windows xp

OK I think I can see where you've gone wrong. You need to have the rom you want to flash on your sdcard (im assuming its still there from your earlier tries), and you need to download givemeroot.zip to your pc:
http://www.stevebirstok.com/android/givemeroot.zip
Let me know when you've got the SDK installed and we can proceed..

i was on the other computer, im doing all this from my laptop since the usb ports are right in front of me, i actually do have the sdk, and i dont think i have the rom i want . i just want a plain android 1.6 thats optimized for the htc dream. and now its updating the sdk

Absolutely bricked?

Story, in key point format:
-Just moved, no internet at home yet (in fact I've been using tether since I only check e-mail and use FB anyway)
-At cafe... Already closed, but they agreed to let me stay about 5 minutes past closing time, no time to search. NO N00B/"SEARCH FIRST" COMMENTS PLEASE.
-Don't have any old phones
-Just got a new girlfriend and didn't think much about emergency expenses and spent most of my $ on wine n' dine with her (but at least I got some worthy "dessert", but that's another story).
-Just lost my job a week after meeting her (I stayed up all night, eventually gave into a "food coma" [see above] and came into work late) LOLOL... Woulda had a new phone budget if I was around for another 2 weeks, but noooo....
Anyway:
-Tried to install CM5 onto G1
-Installed it with the CM bootloader (or something like that, it had an orange font)
-Downgraded to RC29, successfully loaded AMON_RA
-Installed DangerSPL, rebooted per the instructions
-Stuck on the boot screen for almost exactly half an hour (5 mins after 8PM until 8:30PM), said "WTF" and pulled battery out
-According to the first few search results, my phone is "fully bricked", as in end+back/home/camera/whatever doesn't work (although when you push end+trackball the blue light turns on, whatever that means)
With that in mind, what should I do? Any hope?

Hmm well Im not an expert like most of these other guys by ANY means, but in my experience I've learned that removing the battery during a percieved "hangup" is a sure fire way to brick a G1. Trust me Ive done it, not fun.
If you can make it to the recovery screen somehow, theres still hope. On the Cyanogen Wiki, I believe theres a type of method for reflashing a rom, by booting while holding the camera button. I would recommend researching that.

Pulling the battery had nothing to do with it. The combination of 1.33.2005 SPL + 1.x radio is incapable of booting any known kernel. The misc partition was configured to boot-recovery, which overrides any key presses. So when it starts up, it figures it should launch recovery, which boots far enough for the SPL to think that its booted (otherwise it would force you into fastboot).
Your only hope right now is to jtag the thing and either wipe your misc partition or load a compatible SPL that allows fastboot.

You forgot to flash a compatible radio!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

BoomBoomPOW said:
You forgot to flash a compatible radio!
Click to expand...
Click to collapse
The funny thing is that if he had done the first sensible steps of installing an engineering bootloader (one with fastboot) and wiping the recovery partition (to force it into fastboot when recovery failed due to being wiped), he'd be fine.

DAMNITS!! I only read the "steps" portion of the instructions on the Cyanogen Wiki, which didn't even include the "radio" portion of the equation (I edited it just to avoid other people having the same problems).
lbcoder said:
Pulling the battery had nothing to do with it. The combination of 1.33.2005 SPL + 1.x radio is incapable of booting any known kernel. The misc partition was configured to boot-recovery, which overrides any key presses. So when it starts up, it figures it should launch recovery, which boots far enough for the SPL to think that its booted (otherwise it would force you into fastboot).
Your only hope right now is to jtag the thing and either wipe your misc partition or load a compatible SPL that allows fastboot.
Click to expand...
Click to collapse
Jtag? Sounds horribly hard; baking it and taking out a ROM chip? Wow.
Acecalibur said:
...by booting while holding the camera button. I would recommend researching that.
Click to expand...
Click to collapse
"-According to the first few search results, my phone is "fully bricked", as in end+back/home/camera/whatever doesn't work"
lbcoder said:
The funny thing is that if he had done the first sensible steps of installing an engineering bootloader (one with fastboot) and wiping the recovery partition (to force it into fastboot when recovery failed due to being wiped), he'd be fine.
Click to expand...
Click to collapse
Well, I was (somewhat) following the steps of the Cyanogen wiki.

EdWaRdW818 said:
Jtag? Sounds horribly hard; baking it and taking out a ROM chip? Wow.
Click to expand...
Click to collapse
Your information is wrong. There's no baking, there's no removing chips. There is just interfacing with the board. If you're handy with a soldering iron, its a cakewalk.
Well, I was (somewhat) following the steps of the Cyanogen wiki.
Click to expand...
Click to collapse
Finding all your information in one location? What makes you think that your SINGLE SOURCE of information was accurate or correct? For all you know, it was written with the INTENTION of screwing you up.

[Q] Possibly bricked Rogers HTC Dream (G1) - tried several NBH's

I've searched Google quite a bit, and found others that had a similar issue, but I notice that they experienced slightly different outcomes (mostly not fixing the problem for them). I'm going into this assuming that the phone may just have to be jtag'd to be fixed... but as a last ditch effort I'd like to lay out my issue in as much detail as possible to see if anything can be done to salvage this thing.
How I broke it: I recall about a year ago, I tried flashing an SPL (was it DangerSPL? Maybe...). The phone was already rooted, but I think I was trying to gain S-OFF with it. Whatever it was, it was stupid to do.
How it behaved after that (and as of right now): Turning on the phone shows the Rogers logo, and it does nothing. For a very long time.
Power key combinations and their results: I notice that 3 work. Here they are:
1st) Hold wheelbutton+POWER - it illuminates the led (Blue colour).
2nd) Hold BACK+POWER: Takes me to a rainbow screen that has HBOOT text. The text is:
DREA210 PVT 32B
HBOOT-0.95.0000
CPLD-4
RADIO-2.22.19.26I
Sep 2 2008
Also, inside the green part is a white line that says "Serial0"
Screenshot:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
3rd) Hold CAMERA+POWER: Takes me to the same rainbow screen mentioned above, BUT - it turns into a grey screen that tries to load something. Research toldme that this is where it tries to load an NBH file (it's like a system image... like a rom I assume). I found 3 different NBH files.
First NBH file I tried was a "Rogers" one - which I thought would be perfect for me, since it's a Rogers phone. I made sure to rename it to DREAIMG.nbh, put it on a freshly-formatted MicroSD card, popped it in, and turned the phone on by holding CAMERA+POWER. It got to the grey screen, "loading..." and then "checking..." and then it said "00028002 not allow". It then returned me to the rainbow screen.
I then tried 2 other NBH's (the standard US one - RC29? and then the UK one - RC7?) with no luck - still got the "not allow" message.
So I think that's it. I'm glad that I can actually get SOME kind of screen up... as that is a sign of hope...
If anyone can contribute to this, it would be greatly appreciated. Thanks for reading.

a) you need to make a goldcard to flash any nbh other than the rogers ones.
b) 0.95.0000 will not net you flash the rogers firmware (I think an issue with the ebi1radio)
This means you must make a goldcard, borowing someone elses phone if needed to get the CID of a micro sdcard.
After you have a gold card I recommend you flash the orange nbh from my 2708+ thread http://forum.xda-developers.com/showthread.php?t=831139
(rename to DREAIMG.nbh and place on the root of the gold card)
Once the orange nbh is flashed you can flash and slash screen you want if any (only reason for a full s=off spl) then use the fastboot instructions to install the 2708+ radio and a rom. also on that thread)
_--

Ezterry to the rescue! Lots of info there. Thanks a lot - i will let u know of the results!
Sent from my XT860 using XDA App

ezterry thank you thank you thank you!!! Dream is up and running!!!!
Sent from my XT860 using XDA App