Database Develop

need help fellas... i made a mistake n cant fix it?

i was rooting a friends g1, i missed a step n tried flashing a rom without having the danger spl installed first, i cant get into my spl menu by holding camera and power nor can i get into my recovery nor can i get into adb... my phone turns on and stays at the g1 logo... any advice?

bricked.. look in the development section for un-bricking guides... although it'll cost some money i think.. i'll look for one myself and post back with a link
edit: http://forum.xda-developers.com/showthread.php?t=576628&highlight=brick
or
http://forum.xda-developers.com/showthread.php?t=591048
maybe those could help... Good luck!

madunix said:
i was rooting a friends g1, i missed a step n tried flashing a rom without having the danger spl installed first, i cant get into my spl menu by holding camera and power nor can i get into my recovery nor can i get into adb... my phone turns on and stays at the g1 logo... any advice?
Click to expand...
Click to collapse
that is why i dont screw around with other peoples phones LOL

i just checked my sdcard that was in the phone, the update.zip file is the danger spl. im guessing i flashed that? but i dont get why that would brick anything.. the phone was rooted... but i had the factory recovery where u see that pic in the middle, i hit alt w? or alt s i forget what the instructions were i was following. soo its a brick huh? no way of getting through this one?

madunix said:
i just checked my sdcard that was in the phone, the update.zip file is the danger spl. im guessing i flashed that? but i dont get why that would brick anything.. the phone was rooted... but i had the factory recovery where u see that pic in the middle, i hit alt w? or alt s i forget what the instructions were i was following. soo its a brick huh? no way of getting through this one?
Click to expand...
Click to collapse
Just because the phone is rooted doesn't mean it is magical and can't be bricked. You have to have the latest radio before you can flash the danger SPL. Depending on which method you used(likely RC29 method) that radio would not be anywhere close to what is needed. And, yes, once you flash the danger SPL without the newest radio, you have a brick and no way getting back from it.
Hopefully your friend is understanding and it isn't a major disaster getting a replacement G1 for him.

Flash Danger SPL without Latest Radio = Bricked.
I hope that your friend can get a replacement without much complications, because that one is screwed.

You could give him your phone...

the phone already had the newest radio installed... it was a brand new G1.. =X did i still have to flash it with the radio on this forums?

madunix said:
the phone already had the newest radio installed... it was a brand new G1.. =X did i still have to flash it with the radio on this forums?
Click to expand...
Click to collapse
Most likely yes usually when something is brand new it was manufactured months ago. Its unlikely that it included the proper radio. try blaming your friend lol good luck!

madunix said:
the phone already had the newest radio installed... it was a brand new G1.. =X did i still have to flash it with the radio on this forums?
Click to expand...
Click to collapse
Brand new or not, most every root method has you downgrade to RC29, which takes you back to a radio that is about a year old now.

G1 stuck at G1 screen

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.

my brick ?

no adb and no fastboot on pc
i can go into recovery but when phone boots it goes straight to tri color screen a.k.a bootloader with serial0
i tried downgrading it shows down grade on bootloader but not booting to rom what am i not doing

any suggestions

mods close thread solved by reflashing org.spl

ok it happen again and this time flashing stock spl is not working any help any one

Well it's very probable that by flashing your stock spl that youre now running a perfected spl which won't let you get any further, If you do manage to get back into the rom adb erase and flash a new recovery and spl because it sounds as if your recovery is fried. If you want help from others it would be a good idea to include rom, spl, radio, recovery that you're running so we can better assist you. every combination is different and often it's something as simple as a radio/rom mismatch or an overclocking issue

ok im at complete stock everything

rooted or unrooted?
one second thought.. try downgrading and re-rooting your phone via old school rc29 rom versions..
something has obviously gone awry. lets see if flashing an older rom will get you into the phone and then you can flash a new recovery, spl and radio from there.
http://forum.xda-developers.com/showthread.php?t=442480&page=35
Sometimes you just gotta redo everything because of software mismatches and extra crap in your phone that isn't supposed to be there.

i had bought the phone like that stuck on bootloader i fixed it after i tried to flash the org. spl it didnt flash but after reset it booted fine after rooting and using the danger spl and cannon complete eclair my carmera went bugging so i decide to downgrade and reroot i flashed the rc29 but it went back to the first problem again

all eclair roms have problems with cameras.. but this sounds more like there's just something not right.. could be anything from your radio to your recovery.. Full wipe and restart the process I no longer have a g1 but im pretty sure if i downgraded from 2.1 to rc29 my phone would act screwy too.

i did the full wipe formated sd cards i am at a brick wall with out a brick

thatruth132 said:
i did the full wipe formated sd cards i am at a brick wall with out a brick
Click to expand...
Click to collapse
set up sdk/adb and see if your phone is being found or not with the command
Code:
/cd
cd AndroidSDK/tools/
adb devices

i have adb installed correct its not picking up in adb at all no fastboot of course

I don't know i maybe wrong but think you should start all over again
downgrading to v1.0
although i am not that experience
please wait for someone how know

nothing i try is catching

still needing help

And we still don't know what you have installed..
1) make sure your phone is off: boot into the spl by turning on the phone while holding down camera.. tell us all the text on that screen
2) power off your phone again and enter recovery (power on holding home) if it loads do you see any version info? Or just an icon in the center of the screen.. if it dosent load tell us that
3) can you boot into a system (in your case I assume not but if others are reading) tell us the build number and rom if possible in about phone. If it wont boot tell us that.
4) Last what carrier and country is the phone originally from. (This changes what "stock" is)
With all of this information we can find the correct path to solve any issues.. usually without resorting to jtag.

DREA 100 PVT 32B
HBOOT 0.95.0000
CPLD 4
Rado 2.22.19.26I
Sep 2 2008
At this point, I searched around again for 30 minutes or so, and saw the stuck camera button problem and took off the back battery case and performed a restart and still went straight to the SPL with almost no delay. The camera button depresses properly and doesnt seem to be stuck.
After all this, I figured I should just start off fresh, so I flashed the DREAM.nbh for RC29 that is listed everywhere in order to get root. On restart, I held down the camera button, and the white screen comes up to ask if I want to boot image.
I do, and everything goes off without a hitch, I press action key to restart and end up at the SPL screen again, this time, my radio is down to v1.2 instead of v2.2 so I know I changed something. I have done this update twice just to make sure everything is going right but I am still stuck at SPL.
Sorry for the extensive post, but as you can see, I did a bit of trouble shooting before I posted this.
1 did that
2 did that regular recovery
3 can not boot into system on 1.5 cupcake signed-kila-ota-148830.de6a94ca.zip
4 tmobile usa

anything i know its not bricked

OK you have rc29 installed. That is the original android with 1x radio. So software wise you are fine. (Ie not bricked)
The problem is you need to enter normal boot and are always entering the spl instead?
My guess is the camera button is stuck..
The real button is surface mounted on the main board what you press is a user friendly piece of plastic on top of that, attatched to the phone's cover.
If you have any warranty get T-Mobile to take a look.. Otherwise you can try opening it and cleaning it out.

i tired that and i actually switched the mother boards and check the buttons and nothing is stuck when i update to rc29 it lets me when i update to cupcake it lets me the text even changes on bootloader but not actual boot

G1 stuck on bootloader screen (G1 screen) PLEASE HELP!!!

hi,
my friend tried to root his g1 and somehow he got it stuck on the bootloader screen. It just stays there and does nothing.
I have no clue what to do and he let me have the phone.
I was just wondering if someone can tell me what to put onto my sd card to get it up and running. thanks so much!

hi there hope this helps follow this guide and it will help. hope all goes well.
http://forum.xda-developers.com/showthread.php?t=463779

Thank you, i will check it out.

your welcome. anymore help just ask. there's a lot of people here on XDA that would be gladly to help out. Some of them have great experience with the G1 and many others android phones. if that file don't work for you, this one will truly work its the one i use if i get into any trouble like your self, i been there. sometimes its stays on booting and this don't work i use this one.
http://www.megaupload.com/?d=EMY1HIVU and just follow the same direction as the last site i gave you.

For some reason i cant get into boot loader mode... any ideas?

did you press camera button and power button just like that. fist step camera button second step power button at same time. but before you do this phone needs to be off to get into boot loader mode. you need to place the image on the root of the sdcard thats in no folder at all, in the root of the sdcard.

What i did is i pulled out the battery, put the sd card in and then put the battery back in. Next I held down the camera key and then I pushed the power button. I have not let go.

sould i let go next time?

this is what you suppost to follow http://www.youtube.com/watch?v=ckbsFRnVciE . tell me something can your phone power on the g1 boot screen. can you tried for me power and home and tell me what you see. thanks.

It will not do anything. it is just stuck on the g1 screen.

I asked my friend what he used and he said Anon recovery rom and hard spl

probably the phone is bricked. write every single step you remember you took on trying to root your phone maybe i can get something out from there. its hard to brick one of this phones. to use amon recovery and hard spl your phone need to be downgraded with rc29 by using the file in the website i posted.

rhonal89 said:
probably the phone is bricked. write every single step you remember you took on trying to root your phone maybe i can get something out from there. its hard to brick one of this phones. to use amon recovery and hard spl your phone need to be downgraded with rc29 by using the file in the website i posted.
Click to expand...
Click to collapse
He said he did not downgrade it. he went straight to the spl and this is what happened.

he needed to downgrade the phone from stock before doing those steps. it aint that easy. probably he bricked the phone somehow.

enferrari said:
He said he did not downgrade it. he went straight to the spl and this is what happened.
Click to expand...
Click to collapse
He could not have flashed the spl straight onto a stock phone.. He's leaving something out, probably in the full knowledge that he did something stupid.
Anyway, if you can't get into bootloader with cam+power of recovery with home+power, it's a brick. JTAG it if you're comfortable with that or if not, sell it to someone who is.

then mines possibly bricked! maaan this is such BS. i accidentally installed the wrong recovery image, then figured I redo everything again. I got it working again, downgraded to RC29 and flashed Amon Ra 1.7.0 image. After that I got too excited, I went straight ahead and flashed hard spl and complete Eclair rom right away. Then poof, stuck on g1 screen. Still is now, possibly brick right?

iLOSER said:
then mines possibly bricked! maaan this is such BS. i accidentally installed the wrong recovery image, then figured I redo everything again. I got it working again, downgraded to RC29 and flashed Amon Ra 1.7.0 image. After that I got too excited, I went straight ahead and flashed hard spl and complete Eclair rom right away. Then poof, stuck on g1 screen. Still is now, possibly brick right?
Click to expand...
Click to collapse
HardSPL should not cause a brick with the RC29 radio, unless you are mistaking HardSPL 10.95.3000 for DeathSPL 1.33.2005.. which did you flash?

goldenarmZ said:
HardSPL should not cause a brick with the RC29 radio, unless you are mistaking HardSPL 10.95.3000 for DeathSPL 1.33.2005.. which did you flash?
Click to expand...
Click to collapse
I flashed with hardSPL. but isnt the steps i did correct? or did i skipped something? i haven't root my phone since last summer. so my brain was kinda fuzzy when i reroot my phone.

iLOSER said:
I flashed with hardSPL. but isnt the steps i did correct? or did i skipped something? i haven't root my phone since last summer. so my brain was kinda fuzzy when i reroot my phone.
Click to expand...
Click to collapse
You should've updated the radio before trying to run eclair, but that wouldn't cause a brick. Can't you get to recovery or bootloader?

goldenarmZ said:
You should've updated the radio before trying to run eclair, but that wouldn't cause a brick. Can't you get to recovery or bootloader?
Click to expand...
Click to collapse
Before this happen I can, but now I'm stuck on the g1 screen. I left it on all night and nothing. I still can't get into recovery nor bootloader. Any other suggestions? So tired too of staying up all night reading trying to figure this out

Trying to Root HTC DREAM: nightmare

Hello all. This isn't your usual noob rooting thread. I'm having some serious problems trying to root my phone, I need some professional help here. I literally have scoured every tutorial trying to figure this out, my phone has been down for two weeks. PLEASE help me out, I looked everywhere trying to fix this thing.
Here is my problem: Downgraded from 1.5 to RC29, but when I try and update from RC29 A) Rainbow/Serial0 B) When I try to go into the OS it hangs at the T-Mobile G-1 Screen (I have a Rogers Dream).
Here is where my phone is at now:
DREAM210 PVT 32B
HBOOT 0.95.0000
CPLD-4
RADIO-2.22.23.02
Sept 2 2008
I can access the recovery options, but I can't update. When I tried to access sqlite_stmt_journals it told me it couldn't cd there even though when I ls'ed it told me the directory existed.
Even when I thought I used update.zip and flashed to the newest version it still had the old T-Mobile on there. Please help, I'm desperate guys! Anything!
You guys are great, thanks in advance. I'll check this thread constantly. Regards.

I'm not sure how you are where you are.. (you must have been rooted at some point to install RC29; rogers phones won't install it without doing so.. however for many it boots into android more successfully)
It also sounds like you have a custom recovery as stock dream recoveries don't have ADB or console applications. In addition having 2.22.23.02 indicates you changed the radio after flashing RC29 (that may be the issue with boot.. but as Android 1.0 isn't that interesting we can leave the radio in question)
So here is some questions
1) is it stock recovery (has a /!\ image and you must use ALT+L to see the options) or a custom recovery; if a custom recovery can you give more info like is it RA or clockwork recovery
2) Where are you seeing sqlite_stmt_journals in adb with recovery booted or while stuck on the G1 screen? If the G1 screen maybe a 'adb logcat > out.log' will help attach said out.log to your post.
With this info I can try to help you find a way out of this mess.

Thanks - I appreciate the reply. It's been a strange path for sure. But I managed to escape the one I was in and into another one.
I managed to put AMON RA's 1.7.0 recovery on my phone, and upgrade to Android 1.6 (Cyanogen 4.2.15.1). My radio at that point was 2.22.19.26i (obvious mistake). But regardless it worked for whatever reason. Regardless.
I pumped straight through that (as in the instructions after flashing DangerSPL) to putting Cyanogen 6.0.0DS on, then the EB11 kernal (even though I wasn't sure if I needed it, but it said it you had a Rogers phone you should) and the tiny GAPPS. It said welcome to Cyanogen 6.0.0 in the recovery screen, but when I rebooted it still went to the T-Mobile G1 screen.
So i sasw my error with the radio, and went to switch it from the one I had to the correct one: 3.22.26.17 (as per the site). So I thought I should reflash the Danger SPL just to make sure I was clean to reapply the Cyanogen update after.
However, when I applied the 3.22.26.17.zip, and rebooted and held camera it just held at the t-mobile G1 screen. I waited for 10 minutes then had to pull the battery.
Now I can't boot into the phone, into recovery, or fastboot. What. a. mess.
Thanks in advance for the help, this really is a nightmare for me.

nudasveritas said:
Thanks - I appreciate the reply. It's been a strange path for sure. But I managed to escape the one I was in and into another one.
I managed to put AMON RA's 1.7.0 recovery on my phone, and upgrade to Android 1.6 (Cyanogen 4.2.15.1). My radio at that point was 2.22.19.26i (obvious mistake).
Click to expand...
Click to collapse
NOT a mistake at all! There is NOTHING wrong with a 2.x radio!!!!
But regardless it worked for whatever reason. Regardless.
Click to expand...
Click to collapse
Probably worked because it was a perfectly valid thing to do!
I pumped straight through that (as in the instructions after flashing DangerSPL) to putting Cyanogen 6.0.0DS on, then the EB11 kernal (even though I wasn't sure if I needed it, but it said it you had a Rogers phone you should) and the tiny GAPPS.
Click to expand...
Click to collapse
Your mistake was the EBI1 kernel -- you had an EBI0 radio, that means that you needed to use the (default) EBI0 kernel.
It said welcome to Cyanogen 6.0.0 in the recovery screen, but when I rebooted it still went to the T-Mobile G1 screen.
Click to expand...
Click to collapse
This is because CM doesn't change that image. It came with the NBH file you installed. Nothing to worry about. The reason it didn't boot is because you had the wrong kernel installed.
So i sasw my error with the radio, and went to switch it from the one I had to the correct one: 3.22.26.17 (as per the site). So I thought I should reflash the Danger SPL just to make sure I was clean to reapply the Cyanogen update after.
Click to expand...
Click to collapse
I'm trying hard to understand what you did... at this point, you had... 1.33.2005 SPL and 3.22.26.17 radio?
This is a valid pair, BUT, you had an EBI0 recovery installed and just switched to an EBI1 radio... and have the thing set to boot-recovery. This is an awkward spot to be in..... basically, since you had a 1.33.2xxx SPL installed, you should NOT have tried flashing radio through recovery -- you had a perfectly good FASTBOOT, and should have used THAT.
However, when I applied the 3.22.26.17.zip, and rebooted and held camera it just held at the t-mobile G1 screen. I waited for 10 minutes then had to pull the battery.
Now I can't boot into the phone, into recovery, or fastboot. What. a. mess.
Thanks in advance for the help, this really is a nightmare for me.
Click to expand...
Click to collapse
This is an interesting spot you're in, I'm not sure how to resolve it. You appear to have an SPL and RADIO that are compatible, but are, nevertheless, bricked in a boot-recovery mode.
Following the update-radio cycle, the command field of the misc partition gets set to boot-recovery, with the parameter set to format the cache partition. Well, you have an EBI1 radio and an EBI0 recovery kernel, so recovery won't boot to finish its cleanup.

The reason I went from the 2.x radio to the 3.x radio is because on the walkthrough it said that the 2.x radio was for non-US whereas the 3.x radio was for Rogers dream customers. But something that might help:
If I plug in my phone via USB, it won't acknowledge it as either a Fastboot or Recovery/ADB device, but the computer does acknowedge it as an "Unknown USB device," while under Android Devices there is the Android Composite ADB Device... which says it cannot start because of Code 10. Windows 7 Pro, 64-Bit is my OS.
Would repartitioning or formatting the SD card do anything? Also, start+menu+end won't do anything either.
Thanks again folks for the help, I am in a situation here.

I'm stuck in 1.0 with some keys not responding like "s" and am stuck. Any chance this could be what I did?