Hey guys: My phone froze randomly while i was listening to music, so naturally i restarted holding the home+power+menu buttons. Ive restarted my phone several times using this method without any problems. this time around it loads to a screen that im not too familiar with: it has three little android guys skateboarding on the bottom and a solid yellow line in the middle that says "Serial0", up top it says:
DREA100 PVT 32B
HSPL10.95.3000
CPLD-4
RADIO-2.22.19.26I
Oct 20 2008
it loads to that screen and then from a brief second a gray screen pops up and says "No Image File!"
it wont let me load into recovery to wipe, ive tried just pulling out the battery, sim, and SD card and it still goes straight to this screen.
I am/ was running Cyanogen's latest rom and my sd card had ext3/linux swap.
i tried researching this and no luck...im pretty desperate for help..
so please and thank you for any advice/ways to fix this!
ive managed to get into the recovery, but after several wipes it still goes into the same screen (the screen where you hold the camera and power button). so i decided to throw in the DEAIMG-RC29 and it asked me if to install it so i did. but it still keeps going back to that screen...
anyone.please. any advice...This phone is my life! so could really really use some help..id be so grateful
did you get any errors when you flashed RC29? because if your still seeing skateboards after flashing RC29....something went wrong
no, i got the screen with the blue green and red bars. i just tried draining the battery but still no luck, it still keeps going back to this screen
well if everything is stock and its still doing that.....make sure your camera key isnt stuck.
See if you can boot into recovery with
adb shell reboot recovery
Click to expand...
Click to collapse
and if all else fails, just call tmo and tell them to replace the phone
Related
Hi Guys,
Little help here. Phone is stuck on TRICOLOR screen. I was down grading to RC29. Update goes 100% and failed.
Now everytime phone reboots goes straight to TRICOLOR screen.
I have downloaded 10 Different DREAMIMG.nbh files but none of them are working.
Also try to Extract it NBHextractor and it tells me that file is not valid.
Any help will be appreciated.
what part of the world are you living in?
Is that really answer to my question?
Yes so we can tell you which SPL verson you need to flash.
I have a T-Mobile G1 (US).
depending on where you live there are different DREAIMG.nbh that you have to use. did you get the RC-29 file from this thread.
also it has to be named DREAIMG.nbh not DREAMIMG.nbh, and since it keeps booting into that screen is your camera button stuck
I have tried that already and as i mentioned that i have tried 10 Different files from 10 different threads and locations but same thing.
Update goes 100% and then it came up DREAIMG.nbh --- failed in red.
and it says Update failed.
Everytime i turn on the phone and it goes straight to TRICOLOR screen.
I was hoping someone can help to get out os this TRICOLOR screen.
I have tried all combinations Camera+POWER. HOME+POWER no matter what it goes to the same damn screen.
2 other things i can think of.
1. check the md5sum of the download
2. try booting without the sdcard in. also you could take off the battery cover and see if the camera is really stuck or not
I can check md5sum on the files which i have not tried it yet.
As far as the camera button concerned i have checked it couple of times and it's working fine.
One other i noticed the Board Revision is EVT. would that makes any difference ?
Not unless you are trying the danger spl, but you didn't brick it because you can get into bootloader. But you still need a flashboot spl to push the update as a last resort. You say 10 different spl files, but you never said where you got it so we can verify they are the correct files.
This all will go a lot smoother if you you would calm down and explain everything.
Most of the NBH files i have downloaded the link posted in the forums.
How can you push spl while the phone is not going into recovery mode?
did you get it wet?
my 8 month old had my phone in his mouth for about 30 seconds. It was long enough till fill the back with slobber and short out the phone. It took over an hour for the phone to even turn back on. And after it did I would keep getting stuck at the SPL screen. BUT, 1 out of say 30 or so tries to restart the phone it actually boots. So my guess is that there is something shorting out the contacts under the camera button unless you can't get into recovery either. I can get into recovery which is why I know there is a short of some sort.
Hello!
First real problem EVER with this phone. Am running Cyanogen's latest 4.1.999 build which has been running fine for the last 2 weeks. Nothing moved or changed recently besides un-installing the iMusic App earlier today. At any rate I had it plugged into my PC via USB, pulled cord out (never had an issue doing this before)... knew I had a couple txts waiting so tried to wake screen... lights came on but black screen (has delayed like this before... wasn't worried yet). Waited, tried pressing menu again then opening keyboard and pressing menu... nuthin. Suddenly a quick buzz and it reboots and I see the T-Mobile G1 screen (STILL not worried at this point since I know Cyanogen 4.1.999 is experimental and to not begrudge a random reboot here and there... HOWEVER... after sitting at G1 screen for a bit it simply fades out and SITS.... doing NOTHING. Black screen... no android logo... but button lights are on. Hit power button I get G1 screen again. What I've tried so far:
1. Removed/replaced battery and reboot - No change.
2. Removed/replaced SIM Card and reboot - No change.
3. Removed SD card and reboot - No change.
4. Wasnt able to at first, but now after leaving battery out for a bit I can boot into Recovery, did a wipe, tried rebooting... it just shuts off and doesnt reboot. Recovery again, tried restoring latest nandroid backup... it said it did, reboot, same thing. Finally tried recovery, then flashing latest HTC recovery build needed for Cyanogen's latest... it started, then screen went dark during the process. Almost like a bum power supply! RANDOM!!
Don't have ADB installed unfortunately... was going to but then I realized since I can't even boot into the OS to enable USB debugging what's the point?
Reasonably saavy here but by no means a coder... ideas?? Help?? Sympathy?? LOL
since you have tried a lot of things already, you may need to flash the rc29 image in bootloader and re-root your phone, if it still will not work after the rc29 flash, then it is hardware related altogether.
RC29?? Couldn'ty I just flash to 1.5 if it came to that?
themoebius said:
RC29?? Couldn'ty I just flash to 1.5 if it came to that?
Click to expand...
Click to collapse
to unroot you flash the DREAIMG.nbh file because it will overwrite everything.
themoebius said:
Hello!
First real problem EVER with this phone. Am running Cyanogen's latest 4.1.999 build which has been running fine for the last 2 weeks. Nothing moved or changed recently besides un-installing the iMusic App earlier today. At any rate I had it plugged into my PC via USB, pulled cord out (never had an issue doing this before)... knew I had a couple txts waiting so tried to wake screen... lights came on but black screen (has delayed like this before... wasn't worried yet). Waited, tried pressing menu again then opening keyboard and pressing menu... nuthin. Suddenly a quick buzz and it reboots and I see the T-Mobile G1 screen (STILL not worried at this point since I know Cyanogen 4.1.999 is experimental and to not begrudge a random reboot here and there... HOWEVER... after sitting at G1 screen for a bit it simply fades out and SITS.... doing NOTHING. Black screen... no android logo... but button lights are on. Hit power button I get G1 screen again. What I've tried so far:
1. Removed/replaced battery and reboot - No change.
2. Removed/replaced SIM Card and reboot - No change.
3. Removed SD card and reboot - No change.
4. Wasnt able to at first, but now after leaving battery out for a bit I can boot into Recovery, did a wipe, tried rebooting... it just shuts off and doesnt reboot. Recovery again, tried restoring latest nandroid backup... it said it did, reboot, same thing. Finally tried recovery, then flashing latest HTC recovery build needed for Cyanogen's latest... it started, then screen went dark during the process. Almost like a bum power supply! RANDOM!!
Don't have ADB installed unfortunately... was going to but then I realized since I can't even boot into the OS to enable USB debugging what's the point?
Reasonably saavy here but by no means a coder... ideas?? Help?? Sympathy?? LOL
Click to expand...
Click to collapse
Try adb, USB debugging is usually on with these modded ROMs. See if you can get a logcat to someone who is much more knowledgeable.
Hold on...not to call you out, but im pretty sure cm 4.1.999 HAS NOT been out for 2 weeks...please clarify...did you flash the newest update THEN had problems?
themoebius said:
Hello!
First real problem EVER with this phone. Am running Cyanogen's latest 4.1.999 build which has been running fine for the last 2 weeks. Nothing moved or changed recently besides un-installing the iMusic App earlier today. At any rate I had it plugged into my PC via USB, pulled cord out (never had an issue doing this before)... knew I had a couple txts waiting so tried to wake screen... lights came on but black screen (has delayed like this before... wasn't worried yet). Waited, tried pressing menu again then opening keyboard and pressing menu... nuthin. Suddenly a quick buzz and it reboots and I see the T-Mobile G1 screen (STILL not worried at this point since I know Cyanogen 4.1.999 is experimental and to not begrudge a random reboot here and there... HOWEVER... after sitting at G1 screen for a bit it simply fades out and SITS.... doing NOTHING. Black screen... no android logo... but button lights are on. Hit power button I get G1 screen again. What I've tried so far:
1. Removed/replaced battery and reboot - No change.
2. Removed/replaced SIM Card and reboot - No change.
3. Removed SD card and reboot - No change.
4. Wasnt able to at first, but now after leaving battery out for a bit I can boot into Recovery, did a wipe, tried rebooting... it just shuts off and doesnt reboot. Recovery again, tried restoring latest nandroid backup... it said it did, reboot, same thing. Finally tried recovery, then flashing latest HTC recovery build needed for Cyanogen's latest... it started, then screen went dark during the process. Almost like a bum power supply! RANDOM!!
Don't have ADB installed unfortunately... was going to but then I realized since I can't even boot into the OS to enable USB debugging what's the point?
Reasonably saavy here but by no means a coder... ideas?? Help?? Sympathy?? LOL
Click to expand...
Click to collapse
I am having the EXACT same problem with CM4.2.4. I certainly hope its not hardware, but it sure "feels" like it. Especially when my G1 is even shutting down from the Recovery Menu. I'll try to unroot and see if that resuscitates it.
Another one....
Have a look at my current issue on this thread: http://forum.xda-developers.com/showthread.php?t=582576. Check to see in bootloader mode what your board type is (it states it at the top for those who don't know).
Mine is currently showing an EVT board, which doesn't exist. I've pulled the battery out and am leaving it for a while. It could be a hardware issue, but I'm not sure. I was having the "fading screen" issue and eventually got back to RC7 (when I could get into recovery).
Which recovery are you using?
So I have this g1 sitting here for a few months- great looking phone, not a scratch on it...total virgin- no water damage or anything... a true spectacle compared to me daily driver (water damaged g1 with cm 5.07 on it... broken camera, broken wifi module <or so i am guessing since its been that way through all of the different roms ive tried... just shuts off> )
Back to the point-
This spectacle of a g1 - has but one issue... the digitizer doesn't work. No clue why- just wont respond... the g1 has been wiped so I have been stuck @ a "touch the android in its naught spot to continue" screen for a while...
Just decided today that I would try and get cm 5.07 on it... I was remembering (correct me if I am wrong) that android 2.1 didnt bother you with that "touch me" screen when you first booted it up.
So I began with a wipe through recovery- ... formated my sd to fat 32, and threw my DREAIMG.NBH (RC29) on it.
hit the boot loader (camera + power) - boots up as normal- grey screen for the update, and continued with it. Got an OK on each item down the list...looking good.
Update done- hit the power button to finish it- goes back to boot loader displaying the rainbow screen with:
DREAM100 PVT 32B
HBOOT-0.95.0000
CPLD-4
RADIO-1.22.12.29
Sep 2 2008
Serial 0
--
So at this point its all looking great to me- I hit call + menu + power and phone begins to reboot.
But gets stuck @ the freaking tMobile G1 Screen...
I can still access the boot loader... but Ive tried 6 different downloads, re formatted the sd card 3 times, tried a second sd card... tried a copy of RC30 ... nothing works... I get stuck at the G1 screen every time.
I cannot access recovery! Just sticks at G1 screen.
What now? Is this G1 a paper weight?
THANKS!
I don't know if this works with a stock rom, but did you try to get a logcat while it hangs at the g1 screen? Might be useful...
Logcat
I cant do anything :/ Only ability I currently have is to boot the phone via fast boot with a DREAIMG.NBH or sit at a boot screen.
Is there a modified DREAIMG.NBH I should try and run?
Thread moved to Q&A.
pcguru000 said:
This spectacle of a g1 - has but one issue... the digitizer doesn't work. No clue why- just wont respond... the g1 has been wiped so I have been stuck @ a "touch the android in its naught spot to continue" screen for a while...
Click to expand...
Click to collapse
I had a G1 refurb from HTC on which the digitizer did not work properly. No matter what ROM I installed, same problem, no accurate touch response. It was a hardware issue with the phone. I know it doesnt help with the phone hanging on boot. As far as that, it's a tough one. If you only have the stock SPL (rainbow screen) and no modded recovery, you can't do much other than use a .nbh (release key signed ROM/stock ROM) to flash a ROM. Unless there another backdoor I'm unaware of. Good luck!
CM roms need danger SPL, if you're on the "rainbow" screen - you don't have it. You shou've not run NBH because that takes away the root and brings you back to RC29. Sound's like you're out of luck on this one. However, now would be a good time to swap out that digitizer for the one out of "mother-of-all-problems" phone.
Good luck.
danger
I know CM roms need Danger- but at the point I was at I had no way of flashing danger, I needed to first root the phone... the way I have rooted all my G1's was using RC29 first (DREAIMG.NBH) and then using the "type anywhere" exploit to give the phone root administrative rights.
After that i load up a good recovery image, do a nandroid back up etc etc...
Im just not sure why it just died half way through the process- its strange that I can still access the stock boot loader and flash an image but yet nothing happens.
Is it possible for me to flash an image OTHER than RC29- and where could I access that image download?
pcguru000 said:
I know CM roms need Danger- but at the point I was at I had no way of flashing danger, I needed to first root the phone... the way I have rooted all my G1's was using RC29 first (DREAIMG.NBH) and then using the "type anywhere" exploit to give the phone root administrative rights.
After that i load up a good recovery image, do a nandroid back up etc etc...
Im just not sure why it just died half way through the process- its strange that I can still access the stock boot loader and flash an image but yet nothing happens.
Is it possible for me to flash an image OTHER than RC29- and where could I access that image download?
Click to expand...
Click to collapse
That all sounds like it should be working but I would try one more thing. You say you have a second G1. I would try formating the sd card in that phone. It may make a difference. If that does not work you may want to search this forum for "gold card" instructions.
Good luck.
Hello. I am new to the Android scene, just came over from the iPhone scene. Sooo. i got my Android G1 today and it came with Super D firmware, if i remember correctly it was 1.6. I wanted to go back to stock, so i downloaded the stock firmware and placed it in the root of a freshly formatted 4gb SDHC card. It installed and then prompted for reboot. I rebooted and i have left the phone on trying to get it to boot into OS but to no avail. I tried booting to recovery screen but i didnt get any menu and had to key alt+l in my keyboard. I did a wipe and rebooted. Still couldn't boot up. Holding the Camera and power button gives me this :
DREA110 PVT 32B
HBOOT-0.95.0000
CPLD-4
RADIO-1.22.12.29
Sep 2 2008
Serial0
Any ideas?
EDIT: Just realized for god's sake, i flashed the RC29 firmware when i was supposed to flash the RC7 one. F***. Now i need to find a way to flash back. Any ideas?
First thing to do is read everything two times... including the FAQs... too many noobs have bricked their devices... Thus dettering them and anyone they talk to from committing to Android... Take your time research and watch a vid first...
Nah, i just screwed up. Didnt know why i went to flash RC29 anyway. Gonna get a goldcard tomorrow with the help of someone. Then i can get pass the error of flashing another firmware.
Okay, so i got a gold card and reflashed the RC7 image and it booted. Done everything including rooting but i cant install the radio as i cant get into recovery. If i hold home + power button i will boot into fastboot mode. Why.
Apparently telnet wasnt flashing the img file properly.
EDIT: Now getting stuck at the Nexus One X Android Screen in a loop.
EDIT 2: Did a reboot. Now all is good. ^_^
Hello, and welcome myself to this wonderful forum.
Let me introduce myself:
My name is Mish , im a 100% dumbass
Also BIG! thanks for sh1tty cyan's wiki about flashing with dangerspl.
Let me tell you my story:
In a cold night, a boy tried to update his G1 to android 2.2 , updated dreaimg.nbh , rooted the device, installed recovery image . that boy was so excited his 1st android, his 1st up mod.
but that boy was upset, didnt wanted to get his update.zip installed because of the status 7 error. well done , he just looked into the cyan's bloody wiki and he found the magic archive called Danger SPL.
flashed it , rebooted it and stucked into G1 T-mobile Splash screen .. he was like . ah , allrite, i'l reboot and enter to recovery mode . but he cannot do that.
He was so anger . he kissed his keyboard with 2 gently strikes. and searched for hours for solutions but nothing found.
I dont have pages to write the whole story. Aka the end.
in other words, can i get my device working or should i give him wings to fly straight on the garbage can ?
Can you get into fastboot mode? Also i think in the instructions it tells you to flash the radio first. I could be wrong but several people have successfully rooted their device with the instructions given here on xda. Welcome to xda btw.
John
Hello John, i can't enter to fastboot mode or i dont know , it shows me just the T-mobile G1 Splash screen and nothing more, tried with Camera + Power, Volume + Power, Home + Power and still nothing . if you have any hints please share, regards.
Can you reboot holding back and power and get into fastboot?
nope , is stucked in G1 splash screen
I did the same thing and had the same problem - had to replace the motherboard. There is NO WAY to fix it except to replace the mainboard. Good Luck
Is my phone a goner?
I wasn't trying to root or modify my phone in any way. It started flickering and then went black. Now...
Phone does not power on. Not with power button or any combo (camera+power; home+power; etc).
No LED notification. Not even orange when charging.
Eventually starts in tri-color/rainbow/RGB Bootloader ON ITS OWN (no keystrokes). Sometimes after 1 min, sometimes after 20+. Once in Bootloader, it stays there. If it's plugged in and charging, the Bootloader stays on even after battery pull.
Bootloader says:
DREA100 PVT 32B
HBOOT-0.95.0000
CPLID-4
RADIO-2.22.23.02
Sep 2 2008
Serial0
Reformatted SD card and installed original SPL (renamed install.zip) and DREAIMG.nbh to the SD's root. When my phone eventually started in Bootloader (on its own), it went into the install phase, completed, and asked for reboot. I pressed the trackball (action button), it rebooted, and hasn't done a thing since.
mish12 said:
Also BIG! thanks for sh1tty cyan's wiki about flashing with dangerspl.
Click to expand...
Click to collapse
Cyan's wiki is one of the most well written, organized and constanly updated around. Don't blame wiki for something that you did.
Take a look at http://wiki.cyanogenmod.com/index.php?title=DreamangerSPL#Flashing_DangerSPL, how can anyone miss this?
Congrats on your new paperweight.
DUBsays said:
I wasn't trying to root or modify my phone in any way. It started flickering and then went black. Now...
Phone does not power on. Not with power button or any combo (camera+power; home+power; etc).
No LED notification. Not even orange when charging.
Eventually starts in tri-color/rainbow/RGB Bootloader ON ITS OWN (no keystrokes). Sometimes after 1 min, sometimes after 20+. Once in Bootloader, it stays there. If it's plugged in and charging, the Bootloader stays on even after battery pull.
Bootloader says:
DREA100 PVT 32B
HBOOT-0.95.0000
CPLID-4
RADIO-2.22.23.02
Sep 2 2008
Serial0
Reformatted SD card and installed original SPL (renamed install.zip) and DREAIMG.nbh to the SD's root. When my phone eventually started in Bootloader (on its own), it went into the install phase, completed, and asked for reboot. I pressed the trackball (action button), it rebooted, and hasn't done a thing since.
Click to expand...
Click to collapse
Do you have access to another battery? I would try that first. This is not a software issue, if new battery doesn't fix it... you may be better off getting another G1 of CL or Ebay (I hear of folks picking them up for less then $50 nowadays)