[Q] Is it bricked? - G1 General

ok so i am hoping i have not bricked phone but i think i did. i booted to recovery console by holding the home+power and ran the danger spl and when i reboot it just goes to black screnn with white g1 screen and stays. cant even get back into recovery by holding home+power or holding camera+power. so am i done?

i dont see the words "battery pull" have those been done? what happens when u put battery back in? what rom or what were u running before? what radio?
theres a LOT of info i just cant glean off your post.

androidcues said:
i dont see the words "battery pull" have those been done? what happens when u put battery back in? what rom or what were u running before? what radio?
theres a LOT of info i just cant glean off your post.
Click to expand...
Click to collapse
I did pull the battery several times.
the story of how it happened:
I got my g1 unlocked via unlock code from tmobile, I the proceeded to root the phone. All of which worked fine. I then wanted to load cyanogenmod 6 so i downloaded the dangerspl and moved it to sdcard. i then powered off the phone and booted holding home+power and did an install script form sdcard. it installed and completed and i chose reboot and it went to black screen with white G1 and then just sits there. i have pulled the batt several times and just back to that screen. i have tried booting holding home+power and camera+power and both result in the same screen.

jcdeuce said:
I did pull the battery several times.
the story of how it happened:
I got my g1 unlocked via unlock code from tmobile, I the proceeded to root the phone. All of which worked fine. I then wanted to load cyanogenmod 6 so i downloaded the dangerspl and moved it to sdcard. i then powered off the phone and booted holding home+power and did an install script form sdcard. it installed and completed and i chose reboot and it went to black screen with white G1 and then just sits there. i have pulled the batt several times and just back to that screen. i have tried booting holding home+power and camera+power and both result in the same screen.
Click to expand...
Click to collapse
Yip your bricked, you'll need to jtag it im afraid or buy a new one.

Related

stuck at splash screen, have tried all the solutions.

Hello, I am having some issues and I've tried all of the fixes on several different forums including this one.
I wanted to root my phone so I followed Amon's guide and successfully went from the Tmobile released 1.6 to the rooted 1.5 in the guide. I then wanted to update to the rooted 1.6 but was having issues with trying to install the update. While in the safe mood I asked it to extract update.zip about 3 times before it finally opened it and it extracted everything really quickly!
I then tried to reboot the phone but it stayed at the green MyTouch 3G splash screen without going anywhere. I've tried all the tricks of taking out my battery, unplugging the USB, any form of combination I could.
I'm told my phone isn't bricked, only stuck but my computer isn't picking up the phone either. It doesn't say it can't read the USB device and fastboot still says waiting for devices.
Can some one please help me with my problem?
Thank you,
Difinitus said:
Hello, I am having some issues and I've tried all of the fixes on several different forums including this one.
I wanted to root my phone so I followed Amon's guide and successfully went from the Tmobile released 1.6 to the rooted 1.5 in the guide. I then wanted to update to the rooted 1.6 but was having issues with trying to install the update. While in the safe mood I asked it to extract update.zip about 3 times before it finally opened it and it extracted everything really quickly!
I then tried to reboot the phone but it stayed at the green MyTouch 3G splash screen without going anywhere. I've tried all the tricks of taking out my battery, unplugging the USB, any form of combination I could.
I'm told my phone isn't bricked, only stuck but my computer isn't picking up the phone either. It doesn't say it can't read the USB device and fastboot still says waiting for devices.
Can some one please help me with my problem?
Thank you,
Click to expand...
Click to collapse
What do you mean by safe mode? Which donut ROM are you trying to flash? Which recovery image do you have? How long was it stuck on the splash screen. You need to give more details for us to be able to help out. What radio and spl do you have?
I meant safe mode by where you select the option to extract update.zip.
I was trying to flash Amon's 1.6 32A Rom. Even though my phone states 32B I followed his instructions on how to Root the Mytouch and he was using 32A stuff so I figured if it worked OK, I was now running on 32A instead of 32B.
I was using RAv1.2.0H.img from his original guide. I dont know what radio and spl I have. There wasn't really a guide on updating ROMs so I just tried the same basic steps.
I hope this is more helpful, I am doing my best to learn everything, I am still fairly new to modding a phone. (my last phone was a Blackberry 8100).
Difinitus said:
I meant safe mode by where you select the option to extract update.zip.
I was trying to flash Amon's 1.6 32A Rom. Even though my phone states 32B I followed his instructions on how to Root the Mytouch and he was using 32A stuff so I figured if it worked OK, I was now running on 32A instead of 32B.
I was using RAv1.2.0H.img from his original guide. I dont know what radio and spl I have. There wasn't really a guide on updating ROMs so I just tried the same basic steps.
I hope this is more helpful, I am doing my best to learn everything, I am still fairly new to modding a phone. (my last phone was a Blackberry 8100).
Click to expand...
Click to collapse
I'm not sure what you mean by extract update.zip. I think you are talking about fastboot there. Have you tried to flash the rom in the recovery image? you know, by pressing power and home to get to the recovery, then flashing it through there. go into fastboot by pressing power and back and it will tell you what radio and spl you have. once you have that, write that so we can further get a grasp as to your problem. if in fact you still have the 32A configuration, you might want to flash over the 32B radio and and try to flash a 32B rom.
That is my problem, I can't get past the "MyTouch 3G" green screen. I've tried the Home button, Back button, Vol Down button and holding them for several minutes with no result, it stays at the very first screen when it turns on.
I've tried flashbooting from adb but it says "waiting for devices" and my computer isn't picking up any kind of device.
I'm having the exact same problem except im stuck on the vodafone screen. I also tried flashboot form adb but "waiting for devices" is shown and pc wont detect the device.
Did this before.
If you can get into recovery mode, Hold Home button while powering on, you can restore a nandroid backup, if you took one, or put the sappimg.nbh file or the correct items to flash whatever rom.
I had a stock 1.5 Mytouch. I wanted to root and get the 1.6 version of cyanogen, forgot to flash the HTC_ADP_1.6_DRC83_rooted_base as part of the process and had got stuck in the neverending mytouch logo.
If you can get into recovery:
wipe, then put the update.zip files directly on the card.(use a SD adapter, ...)
Choose apply any update from SD
Choose the base files, then the rom if its a newer version
Once those two updates run, reboot the phone.
My never ending logo disappeared, and the phone booted. Newb mistake on my part.
Wait at least a minute or two once this is done.
since the phone is stuck on the original logo and isnt responding to buttons when loading up... do we manually remove and reinsert the battery while holding the home button?
I have tried getting into recovery mode, but it doesn't do anything past the splash screen. Holding the home button while trying to power on the device won't do much.
hey difinitus keep me updated if u somehow get it to work
Even when you take the battery out for a significant time it turns on immediately to the logo screen. Whats the longest you have left the phone sitting at the logo screen.
A small thought, since it was trying to load a rom you had on your memory card, try taking the battery out, and removing the memory card, and then turn it on and wait a bit and see if you get a different result. Its a thought.
If that doesnt work put the memory card back in and turn it on and once its on remove the memory card.
Perhaps the rom on your memory card is corrupt and it is unable to continue to load it, you could even try putting the rom on again using your memory card reader and your computer, thus erasing the existing one.
try plug usb in to phone
take battery out
prees and hold home button
re-insert battery while still holding button
let go after about 3-5 sec
have you tried getting into fastboot by holding back and powering on the phone once you took out the battery? cuz fastboot doesn't initialize after the splash screen, it just pops up as soon as you hit back and power
@Tech no boy; I have tried using several different update.zip and a .nbh and also tried reformatting.
@sitimber; have tried that before, the splash screen still pops up. It just vibrates once and goes to the logo, with any combination of buttons and steps.
@tazz9690; Yes, no matter what I do it still goes to the splash screen. I've been saying that for several posts now.
you might have a bricked phone then. call up t-mobile and get it returned under warranty. if you are 100% positive that you will not be able to get past your splash screen, then the return center will not be able to prove that you have modded your phone, and they will send you another phone.
you might have a bricked phone then. call up t-mobile and get it returned under warranty. if you are 100% positive that you will not be able to get past your splash screen, then the return center will not be able to prove that you have modded your phone, and they will send you another phone.

Root gone wrong

rooted phone. went well Installed rom
not so well.
Holding home and power brings me to a "Android System recovery Utility"
I think what i did wrong was i installed two different types of roms on to my G1 unwittingly. So now all that happens is it stays on the G1 screen and doesn't change. Left it charging overnight and stayed on that screen
Is there a way to access and rectify via console option.
Please help
If you have recovery, you should be fine. Just flash your favorite image and wipe your userdata.
DOD1 said:
rooted phone. went well Installed rom
not so well.
Holding home and power brings me to a "Android System recovery Utility"
I think what i did wrong was i installed two different types of roms on to my G1 unwittingly. So now all that happens is it stays on the G1 screen and doesn't change. Left it charging overnight and stayed on that screen
Is there a way to access and rectify via console option.
Please help
Click to expand...
Click to collapse
Holding Home + Power is supposed to take you into the recovery image.
At the bottom of your recovery image does it say Amon Ra 1.5.2 or 1.6.2 or something like that?
If your phones rooted then just wipe and reinstall you rom.
Like lets say your doing the new cyanmod
you apply zip
DR83
With out rebooting apply zip
Cyanmod-rom 1.4xxxx
If it boots back into Android System recovery Utility just hold home and back again.
Give it time to write its radio and its first time rebooting it says on the boot screen for a awhile some longer then others.
This site has always helped me its better to see the instructions rather then read them.
http://www.google.com/search?q=the+...s=org.mozilla:en-US:official&client=firefox-a

Stuck in bootloader

so ive been flashing roms and have never had a problem till today.
i went to flash the new ava-froyo rom and it went fine and booted right up, and then i tried flashing the new radio and that when everything froze.. it was stuck at the white evo 4g screen...
so i rebooted and it did the same freezein at the white screen..
i rebooted again into hboot, and tried going into recovery and it goes to the white screen again and freezes.
so i only have control in hboot and fastboot. yet i cant get a shell connection. the device is recognized, so im just lost at what to do. been reading for hours and cant figure it out.
thanks for any help.
rdkustom said:
so ive been flashing roms and have never had a problem till today.
i went to flash the new ava-froyo rom and it went fine and booted right up, and then i tried flashing the new radio and that when everything froze.. it was stuck at the white evo 4g screen...
so i rebooted and it did the same freezein at the white screen..
i rebooted again into hboot, and tried going into recovery and it goes to the white screen again and freezes.
so i only have control in hboot and fastboot. yet i cant get a shell connection. the device is recognized, so im just lost at what to do. been reading for hours and cant figure it out.
thanks for any help.
Click to expand...
Click to collapse
Wipe three times wipe wipe wipe if that don't work do whitslack startover method
Sent from my PC36100 using Tapatalk
i cant get into recovery to wipe. do u mean clear storage?
and also, ive been trying to load pc16img off my sdcard, but its not reading. i didnt the sdcard fix and still nothing.. thanks for your help
I kinda had the same issue, try the unrevoked recovery reflash
that's what I did and it worked for me
mine was stuck on the red exclamation point... I tried 5 times by pressing power and +vol buttons, but it was just sitting there for ever...
baiatul said:
mine was stuck on the red exclamation point... I tried 5 times by pressing power and +vol buttons, but it was just sitting there for ever...
Click to expand...
Click to collapse
Are you rooted if not then take battery out put back in hold power and vol down once it goes into hboot pull battery back out then put back in boot up regular way. Happen to me was trying something on non rooted phone went into recovery and got that red! Was like oh man so I did that it v came up hope it works for u
Sent from my PC36100 using Tapatalk
rdkustom said:
so ive been flashing roms and have never had a problem till today.
i went to flash the new ava-froyo rom and it went fine and booted right up, and then i tried flashing the new radio and that when everything froze.. it was stuck at the white evo 4g screen...
so i rebooted and it did the same freezein at the white screen..
i rebooted again into hboot, and tried going into recovery and it goes to the white screen again and freezes.
so i only have control in hboot and fastboot. yet i cant get a shell connection. the device is recognized, so im just lost at what to do. been reading for hours and cant figure it out.
thanks for any help.
Click to expand...
Click to collapse
If all fells do power and vol up hook to CPU HTC sync and try load stock ruu on there
Sent from my PC36100 using Tapatalk
so i can only communicate with the phone thru fastboot..
adb isnt seeing the phone, ive also put a pc36img on my memcard and reboot to get it to load, but it wont load it.. so then i did the sdcard fix and still nothing.. thanks again
ewilson said:
Are you rooted if not then take battery out put back in hold power and vol down once it goes into hboot pull battery back out then put back in boot up regular way. Happen to me was trying something on non rooted phone went into recovery and got that red! Was like oh man so I did that it v came up hope it works for u
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
Thanks, that's correct. Not rooted. Thanks.
baiatul said:
Thanks, that's correct. Not rooted. Thanks.
Click to expand...
Click to collapse
Ok yes that's what happen to my friend phone I was just seeing what happen. Man I was like oh my lord got scared thought I brick phone what I did was pulled battery put battery back in holding vol down and power once in hboot pull battery wait a min or so put battery back and boot up normal way it came on I was like whew. If that doesn't work pull battery put back in vol. Up and power while phone hooked to CPU do HTC sync and reload stock ruu let me know if it works
Sent from my PC36100 using Tapatalk

Is my HTC Magic totally bricked?

I bought a Rogers HTC Magic for a pretty cheap price. It had The Rogers 1.5 Sense UI update on it. I decided I wanted to root it and load other ROMs, etc. So I read that the easiest method was to use Universal Androot to root it, and ROM Manager (from the Market) to flash the appropriate recovery image.
So, I installed both apps. I first ran Universal Androot and rooted. I confirmed root through ADB and also Super User permissions. I then restarted the phone just for peace of mind. After the restart, I ran ROM Manager. It automatically popped up and asked me if I was running an Ion/My Touch or an HTC Magic. I selected HTC Magic, because that's what this is. So then it flashed the recovery image and restarted the phone. When it restarted it went to the Rogers boot screen for a few seconds, and then started a loop of restarts. That's all it does now. It shows the Rogers screen for a few seconds, goes black and reboots over and over. I have tried booting into HBOOT, Fastboot, and into recovery. I cannot boot into any of them. One thing I did notice is that when I'm pressing any of the combinations (volume down + power, home + power, menu + power) for a very brief half a second right before the phone restarts, the bottom of the screen says "ClockwordMod ..." where ... is the version of the image (I'm at work without the phone, so I don't recall the exact number there).
So, is this thing officially a paperweight now, or is there some sort of hope?
Thanks.
Paul
Well, I don't know if you are full-bricked but here is what went wrong. The HTC Magic recovery is incorrect for the mytouch3g (at least the 32b). There was a top option for "saphire/mytouch 3g" which is what you should have chosen. So, you can't load the incompatible recovery. Can't you boot back into the rom you were using? The recovery flash shouldn't have messed with it. If you can, boot back in and flash the correct mytouch3g recovery in rom manager.
adrift02 said:
Well, I don't know if you are full-bricked but here is what went wrong. The HTC Magic recovery is incorrect for the mytouch3g (at least the 32b). There was a top option for "saphire/mytouch 3g" which is what you should have chosen. So, you can't load the incompatible recovery. Can't you boot back into the rom you were using? The recovery flash shouldn't have messed with it. If you can, boot back in and flash the correct mytouch3g recovery in rom manager.
Click to expand...
Click to collapse
Okay. That's weird. I mean, my phone is a Magic so choosing the option for the Magic instead of the Ion/MyTouch seemed to make sense.
Anyway, I cannot get anywhere. Holding vol+ and power does nothing, neither does home and power or back and power. Are there any other tricks to getting anywhere beyond this endless restart loop?
Thanks.
Starting to think I'm screwed.
PaulieORF said:
Starting to think I'm screwed.
Click to expand...
Click to collapse
You may be, I'm not sure exactly what state you are in but the recovery you installed was for a magic 32a (that you have) with a 3.x radio (that you don't have)
The rogers sense rom uses the 6.x hero radio and needs a hero recovery.
The mt3g uses a 2.x radio thus yet another recovery.
Try booting with volume down to see if you can get into the hboot/fastboot screen, but I think you tried this already.. you may also try letting it loop unplugged until the battery drains it may error out giving you access again..
Besides that there is the option of jtag and fixing the software stack that way.
ezterry said:
You may be, I'm not sure exactly what state you are in but the recovery you installed was for a magic 32a (that you have) with a 3.x radio (that you don't have)
The rogers sense rom uses the 6.x hero radio and needs a hero recovery.
The mt3g uses a 2.x radio thus yet another recovery.
Try booting with volume down to see if you can get into the hboot/fastboot screen, but I think you tried this already.. you may also try letting it loop unplugged until the battery drains it may error out giving you access again..
Besides that there is the option of jtag and fixing the software stack that way.
Click to expand...
Click to collapse
Thanks for the reply!
Right, I cannot get into fastboot or hboot. I'll try running the battery down when I get home today. Interesting idea.
Unfortunately running the battery dead with restarts didn't do the trick.
Any idea if there's any place I can send it to who has the smarts to jtag recover this thing?
Thanks.
me too
I did the same thing on a 32B. Rooted. loaded ROM Manager. Ran the recovery, I choose the Ion/MT3G option. tried to load CM6-FroyoRedux-v1.7-32b-blk.zip. Now it's stuck in the boot screen.
tmokeith said:
I did the same thing on a 32B. Rooted. loaded ROM Manager. Ran the recovery, I choose the Ion/MT3G option. tried to load CM6-FroyoRedux-v1.7-32b-blk.zip. Now it's stuck in the boot screen.
Click to expand...
Click to collapse
I don't think it's the same thing.
I rooted, loaded ROM Manager and installed the recovery. I was never even able to get into recovery in order to try to load any ROMs.
I have a Rogers magic, and its a 32a. One way to fix it is to go to the HTC website and punch in your serial number and download the rogers update. Only problem is that will make it a pain to root again. But should fix that reboot loop. But do that as a last resort to get the phone running again.
Sent from my HTC Magic using XDA App
nate_benji said:
I have a Rogers magic, and its a 32a. One way to fix it is to go to the HTC website and punch in your serial number and download the rogers update. Only problem is that will make it a pain to root again. But should fix that reboot loop. But do that as a last resort to get the phone running again.
Sent from my HTC Magic using XDA App
Click to expand...
Click to collapse
The phone does not identify itself to the computer, so this doesn't work.
The program should try to put the phone into fastboot mode, and install the upgrade. Have you tried pulling the battery and pressing the power button + back, once the battery is installed again?
Sent from my HTC Magic using XDA App
nate_benji said:
The program should try to put the phone into fastboot mode, and install the upgrade. Have you tried pulling the battery and pressing the power button + back, once the battery is installed again?
Sent from my HTC Magic using XDA App
Click to expand...
Click to collapse
Oh yes. I've gone crazy trying every key combination with every combination of taking battery out, plugging it in, USB cable attached, detached, etc.
The phone never identifies itself as a piece of hardware to the computer in the 5 seconds between reboots.
I had the same problem yesterday, and i was doing the same rooting with Universal Androot and flashing recovery witch Rom Manager (choose the same options). I tried to go into recovery and then it started to bootlooping the whole time.
I was pretty scared when that happens, can't open fastboot menu and the only thing that my phone was showing was HTC logo and a quick blink of clockwork sign over and over.
I don't know exactly how i managed to fix it, but it started to work when i quickly plug off baterry and i immiediatly plug it in (I was doing it at the exactly time when the phone reboots) while holding the power button.
Now my magic turns on, but recovery won't work (just flash for a moment, and reboots) and it always say at the beginning of booting system that SD card was removed which means i can't use any SD card.
I hope it somehow helped you.
naparstekk said:
I had the same problem yesterday, and i was doing the same rooting with Universal Androot and flashing recovery witch Rom Manager (choose the same options). I tried to go into recovery and then it started to bootlooping the whole time.
I was pretty scared when that happens, can't open fastboot menu and the only thing that my phone was showing was HTC logo and a quick blink of clockwork sign over and over.
I don't know exactly how i managed to fix it, but it started to work when i quickly plug off baterry and i immiediatly plug it in (I was doing it at the exactly time when the phone reboots) while holding the power button.
Now my magic turns on, but recovery won't work (just flash for a moment, and reboots) and it always say at the beginning of booting system that SD card was removed which means i can't use any SD card.
I hope it somehow helped you.
Click to expand...
Click to collapse
I tried doing this quickly for about 5 minutes this morning but didn't get it to go anyway. I can try some more after work today.
When you say it booted after this battery pull thing, do you mean the phone booted right into Android, or you were able to get to hboot or fastboot?
Thanks.
PaulieORF said:
I tried doing this quickly for about 5 minutes this morning but didn't get it to go anyway. I can try some more after work today.
When you say it booted after this battery pull thing, do you mean the phone booted right into Android, or you were able to get to hboot or fastboot?
Thanks.
Click to expand...
Click to collapse
I wasn't able to get hboot or fastboot. I pluged off and on the battery in the exact moment when the Logo came out after restarting. The logo was on the screen for the whole time, even while battery plugged off. I guess, i've done it so quickly that phone didn't switched off.
I think i was holding the power+home or power+back buttons all the time.
Can't really rember the exact way, sorry.
PaulieORF said:
I tried doing this quickly for about 5 minutes this morning but didn't get it to go anyway. I can try some more after work today.
When you say it booted after this battery pull thing, do you mean the phone booted right into Android, or you were able to get to hboot or fastboot?
Thanks.
Click to expand...
Click to collapse
Try removing the SD card and booting if its not restarting due to the wrong radio too soon that may help.. if you get into android restore the SD card and run the exploid process I posted a bit back for rogers magics, or the older goldcard method.
I've played around with taking the battery out and putting it right back in at all different times during the booting and can't get the phone to behave any differently. Iv'e tried it with SD card in and SD card out, USB cable in and USB cable out. I can't get anywhere.
I did notice that the phone does show up as an Android device for a second when it's booting. Tried to catch it in adb but no luck.
Starting to think this thing is shot. Any other ideas?
Just so everyone can see what's happening, I recorded a video and uploaded it. Linked below:
http://www.youtube.com/watch?v=hPoxMzm0MVU&hd=1
try to hold and KEEP holding the back + power... Not volume down!
Don't push and release like you did in the video.

G1 Reverted to RC29 stuck at "Android system recovery utility"

I have a (formerly) rooted G1 that I've attempted to revert to stock RC29 by following the "Full Downgrade Guide" at the CyanogenMod wiki.
My device had HBOOT-1.33.2005, so I used the suggested fastboot command to roll it back to HBOOT-1.33.2003 from the g1boot.zip file linked on that page. This seemed to go well, after which I rebooted into the fastboot (which was still the skateboarding androids screen) again and saw the new (old) HBOOT in the information.
Powered off the phone, inserted the SD card loaded with the DREAIMG.nbh linked in the page, and reflashed the phone. Rebooted with Send+Menu+End, and the phone kept rebooting at the T-Mobile G1 logo screen.
So, I attempted the flash again from the bootloader menu, which is now the "rainbow" style, and shows HBOOT-0.95.(something). It immediately picked up the DREAIMG.nbh file on the SD card and asked if I wanted to flash, chose yes. Same result again: a boot loop at the G1 logo.
I redownloaded the DREAIMG.nbh file without the download accelerator I'd used before, placed it on the SD card, and booted into the bootloader again, flashed, and still the same looping.
So, I attempted to access the "recovery mode" by pressing and holding menu while powering on. I got the G1 logo, then a black screen... pressing Alt-L showed "Android system recovery utility", and nothing else.
Now, the phone will do nothing BUT Android system recovery utility, regardless of what buttons I press or do not press, and I have to remove the battery to turn the damn thing off. Pressing Alt-S, Alt-W, Alt-X, or anything else does nothing.
Where should I look to try to figure out how to recover this thing?
Is a simcard in the phone? Can you get into recovery and wipe incase the partitions are confused?
(Edit, the hint was the sim card)
There's no SIM in the phone at the moment. I can't do anything at the system recovery, except turn the log on or off with Alt-L (which I guess means it's not frozen).
It isn't recognized by ADB anymore, since it has some bastardized version of the stock T-Mobile image that has USB turned off (right? I'm new at this. ).
A bit more info:
I can get into "blue light" mode, and the light is amber/green when plugged into a charger. Sometimes, when I plug the charger in the phone will turn on immediately; but not always.
When I start the phone up and it boots into the broken recovery console, Windows does see an "HTC Dream" device, but ADB doesn't see it.
ezterry said:
(Edit, the hint was the sim card)
Click to expand...
Click to collapse
Should I, or should I not have the SIM in? For what its worth, the phone behaves exactly the same either way.
Thanks for the help.
I just had this exact experience; have you made any progress, goatlordbob?
same happened to me.
cant fastboot, loop at G1 screen, and all i can see in recovery is: Android system recovery utility
some1 find some solution?
why doesnt there seem to b any help for this matter, smh
bull.. s**t
I'm in the exact same boat now. I followed those directions *to the letter* and it put my G1 in this state. Thanks to the wiki maintainer for such wonderful attention to detail. /s
Is there NO way to recover from this?
try to flash this nbh file.... http://www.4shared.com/file/9izdCbvo/DREAIMG.html
ldrifta said:
try to flash this nbh file.... http://www.4shared.com/file/9izdCbvo/DREAIMG.html
Click to expand...
Click to collapse
How? None of the key commands work. Like the OP I can hit Alt+L and it shows ""Android system recovery utility" but that's as far as it goes.
Anyone bothered booting using home + power?
shadowch31 said:
Anyone bothered booting using home + power?
Click to expand...
Click to collapse
Yes - T-Mobile G1 logo, then blank screen forever.

Categories

Resources