So I was using my G1 today, (it has never been hacked), I've never had a reason to mess with any of the files, but while I was talking the battery died. Plugged it in the charger and now all I get is this rainbow screen (screen that says DREA100 PVT 32B
HBOOT - 0.95.0000
CPLD-4
RADIO-1.22.14.11
Sep 2 2008
Serial0
. I've been messing around it for hours now and I seem to be getting no where. I tried wiping the phone. It still boots up to this. I tried over and over and over again to get to the boot loader sceen (holding the camera key + pushing the power key). It keeps bringing me back to the same screen. I am lost. Any help would be great.
I've also done ALT+L and ALT+W numerous times...nothing..Same screen.
The rainbow screen is the bootloader screen. If you reboot holding the Camera or Back button down, that's what you should see. If the phone is constantly rebooting into the bootloader screen, you might want to see if the camera button is stuck against the outer case shell?
Before it goes to the rainbow screen.
No image file found! (gray colored screen) flashes for a milisecond
Doing this with the back cover off. the camera button is not stuck. clicking just fine.
And what if you boot up holding down the home button? Does it enter the recovery screen?
jashsu said:
And what if you boot up holding down the home button? Does it enter the recovery screen?
Click to expand...
Click to collapse
Yup. I can get to the screen where I see all my "ALT+" options.
Take your microsd out of the Dream, put it in a card reader, and put a full RC33 update.zip on it (in case you've not done this before, make sure you rename the file to update.zip before putting it on the sdcard). Then plug the card back into Dream, reboot into recovery, and perform an Alt+W, Alt+S. Seems like your /system/recovery.img might have been corrupted or something.
jashsu said:
Take your microsd out of the Dream, put it in a card reader, and put a full RC33 update.zip on it (in case you've not done this before, make sure you rename the file to update.zip before putting it on the sdcard). Then plug the card back into Dream, reboot into recovery, and perform an Alt+W, Alt+S. Seems like your /system/recovery.img might have been corrupted or something.
Click to expand...
Click to collapse
Thank you for being so helpful so far. It's really kind of you! I will try that right now.
So I tried what you said, and I got further than I ever did but nothing.
So I copied the file on a newly formatted card. Renamed it update.zip like usual. Rebooted the phone with home+power. did the update. And this time, it actually went thru the whole process. Even said installation complete. said to press home+back to reboot like usual. Did that. Got the picture of the arrow and the chip. then rebooted by iteself, moved to the picture with the box and loader bar, and then reboots RIGHT BACK to the rainbow screen.
Repeated the process. Exactly the same thing again...jeez.
hpichris said:
So I tried what you said, and I got further than I ever did but nothing.
So I copied the file on a newly formatted card. Renamed it update.zip like usual. Rebooted the phone with home+power. did the update. And this time, it actually went thru the whole process. Even said installation complete. said to press home+back to reboot like usual. Did that. Got the picture of the arrow and the chip. then rebooted by iteself, moved to the picture with the box and loader bar, and then reboots RIGHT BACK to the rainbow screen.
Repeated the process. Exactly the same thing again...jeez.
Click to expand...
Click to collapse
Wow. It's pretty badly booched. Try this.
http://forum.xda-developers.com/showthread.php?t=442480
Follow steps 1-6 under "Preparing to Get Root". For step 1, use a cardreader instead of the mount option.
jashsu said:
Wow. It's pretty badly booched. Try this.
http://forum.xda-developers.com/showthread.php?t=442480
Follow steps 1-6 under "Preparing to Get Root". For step 1, use a cardreader instead of the mount option.
Click to expand...
Click to collapse
I followed that process, and even though the .nbh file is on the card, the phone won't go into bootloader mode....
holding the camera key and pressing power just brings me to the rainbow screen.
Did you name the file DREAIMG.NBH? The instructions say to name it "DREAMIMG.NBH" but I believe that is incorrect.
jashsu said:
Did you name the file DREAIMG.NBH? The instructions say to name it "DREAMIMG.NBH" but I believe that is incorrect.
Click to expand...
Click to collapse
Yup
It's saved as DREAIMG.NBH
Time to call up T-Mo and ask for an exchange I guess.
jashsu said:
Time to call up T-Mo and ask for an exchange I guess.
Click to expand...
Click to collapse
Yeah, that's the reason I am working so hard on it, I bought it in November from someone on craigslist. No way T-Mobile is going to warranty it for me.
Sounds like I am screwed big time.
hpichris said:
Sounds like I am screwed big time.
Click to expand...
Click to collapse
Are you a current T-Mo customer? If so, maybe they can cut you a break.
I am. Like I said, my g1 was completely stock, didn't unlock, didn't mess with it all. Kinda sucks what happened. It's so strange.
the only answer is that the guy that sold it to you had root access and then went back to stock g1 and did something wrong in the process.
Hi hpichris. I had this exact same problem last week with my G1: it just popped into this rainbow screen one time when I was restarting it, with the same quick "image not found" message. I called T-Mobile tech support and they didn't have much to offer. They asked me to check whether the camera button was stuck (it wasn't), and then the tech support lady told me it was "a known issue" with some of the early produced G1s (I bought mine almost immediately after it came out). And that was it, they didn't have any other fixes, so they sent me a replacement. It's seems like its a hardware issue, especially if your attempts to reflash it have failed.
I recommend calling them, telling them what's up, and maybe they'll give you a new one for a discount.
Oh, and by the way, never rooted the phone, never moded or damaged it in anyway. The phone just broke.
I agree with jashu, the RC29 image should work. (I had this happen before too) remember to use a card reader or have a ferrite core on your USB cable, the first time around my RC29 image file somehow became corrupted during transfer, and the flash failed causing more complications.
Related
So, I plugged my Kaiser (Tilt) into my computer the other day to charge it, and the next morning when I unplugged it, I noticed it was locked up. No biggie, I soft-reset it, and it came directly back to the bootloader (right before the bootloader shows is a white screen, that says "Loading image... No image found!", that flashes for a fraction of a second.
If I plug it into my computer at this point, Windows says the USB device has malfunctioned and it doesn't recognize it. I can't flash it ("connection error"), and it wouldn't hard reset.
Then it kinda came back to life, kinda. Suddenly it'll boot into WM. Windows still doesn't recognize it, but I used JumpSPL to get it into a bootloader, and tried to install a HardSPL on it so I could flash a new ROM (to this point it's been stock-only because it belongs to the company I work for). The HardSPL flash failed partway through, and then it was stuck in bootloader for real. At that point I tried flashing a stock ROM, and it kept failing at different points, never getting more than about halfway through.
Does anyone have any suggestions? Or, do you want to buy it? At this point it's mine (company doesn't want it back), so I'm willing to experiment freely with it. Right up until my Touch Pro 2 comes in and I lose interest
*** UPDATE ***
So after writing this, just for kicks, I decided to give re-flashing the original ROM one more shot (it's been off and untouched now for several days at this point) and the flash succeeded. We'll see where it goes from here
Good luck with your phone.. I hope all goes well.. If you find out what the problem was/is, let me know
Hey godefroi, im new to all of this, just bought a messed up tilt from my friend, and i want to know if you could givve me the link for the insturctions to refalsh my tilt
Just hit up AT&T's site (which redirects you to HTC's site) and download the ROM. The file you want is "_ATT Tilt_RUU_Kaiser_CINGULAR_WWE_3.57.502.2_radio_sign_25.88.40.05_1.65.21.18_Ship.exe", which was the latest update for the phone.
Seems it's not fixed. After playing around with it for a couple days, it's back into bootloader and stuck there. Taking out the battery and leaving it for a few hours brings it back for a while, but it seems there's no permanant fix. Next step will be flashing HardSPL and a custom ROM. I'll update when that happens.
awww dang, that sucks. thank you for tellin me. hopin your tilt comes out ok
Did you ever get this resolved?
Hey man did you ever get this fixed? I cant find anything on it.
I can get to a boot loader screen and it shows USB and when I plug it into my computer I hear the sound that it's recognized but my active sync wont connect.
This is what I posted earlier and a moderator killed the post because I didn't spend hours hunting for a solution first before posting. I don't think one exists but if there is I would be glad to know it. I have flashed this phone and my older HTC Wizard dozens of times with no issues so Im not a "noob"
Earlier today I was taking a picture and the screen kind of stuck so I has to soft reboot it.
It didn't come back up. I was left at the rainbow bootloader screen.
I tried holding the camera button down and rebooting but it didn't change anything.
I tried several different combo's of holding keys down and rebooting and it always came back to that bootloader screen.
So the next thing I did was to format my cd card and downloaded KaisDiagTest1.zip and then coppied the KAISDIAG.NBH image file from the zip on to the root of the sd card.
That worked fine and I was left at a screen saying SPL 1.00.OliNex.
Next thing I did is were I think I screwed up. I flashed it with _ATT Tilt_RUU_Kaiser_CINGULAR_WWE_1.62.502.0_radio_sign _22.45.88.07_1.27.14.09R2_Ship.exe which is the ROM from the HTC site and I think I was only supose to use a custom ROM and now after it finished flashing the ROM it rebooted and is stuck showing loading ... on the screen.
It goes past the boot loader and is stuck at loading...
Please advise if there is anything I can do.
Cheers,
Chris
godefroi said:
So, I plugged my Kaiser (Tilt) into my computer the other day to charge it, and the next morning when I unplugged it, I noticed it was locked up. No biggie, I soft-reset it, and it came directly back to the bootloader (right before the bootloader shows is a white screen, that says "Loading image... No image found!", that flashes for a fraction of a second.
If I plug it into my computer at this point, Windows says the USB device has malfunctioned and it doesn't recognize it. I can't flash it ("connection error"), and it wouldn't hard reset.
Then it kinda came back to life, kinda. Suddenly it'll boot into WM. Windows still doesn't recognize it, but I used JumpSPL to get it into a bootloader, and tried to install a HardSPL on it so I could flash a new ROM (to this point it's been stock-only because it belongs to the company I work for). The HardSPL flash failed partway through, and then it was stuck in bootloader for real. At that point I tried flashing a stock ROM, and it kept failing at different points, never getting more than about halfway through.
Does anyone have any suggestions? Or, do you want to buy it? At this point it's mine (company doesn't want it back), so I'm willing to experiment freely with it. Right up until my Touch Pro 2 comes in and I lose interest
*** UPDATE ***
So after writing this, just for kicks, I decided to give re-flashing the original ROM one more shot (it's been off and untouched now for several days at this point) and the flash succeeded. We'll see where it goes from here
Click to expand...
Click to collapse
I never did. Every once in a while I can get it reflashed, but inevitably it stops working. Just like yours, I'll sfot reset it and it'll be stuck in bootloader.
Best bet is when it gets stuck on the bootloader or on the "white screen" as to put it. Do the following:
1) Unplug battery, memory car and simcard. Reinsert battery ONLY after 3 seconds (cards stay out!)
2) Hold BOTH softkeys down at the same time
3) Whilst holding softkeys, turn the unit on
4) You will be prompted to press "SEND" to reset all user data (you will lose everything on the internal storage. Press the Dial (green button) to reset.
5) When it's finished, you will be prompted to press "SEND" to reboot. Press send and it will boot into WM but might take slightly longer.
6) Realign your pointer and tada. It's up and running.
n.b. This often happens when the radio version of your phone isn't correct. If you notice, when you get stuck in the "white screen" the "gsm signal sight" is frashing green!
I've got to warn you again, this procedure WILL delete all of your internal user storage, hence why I recommend taking out all of the cards before proceeding.
heyadrian said:
Best bet is when it gets stuck on the bootloader or on the "white screen" as to put it. Do the following:
1) Unplug battery, memory car and simcard. Reinsert battery ONLY after 3 seconds (cards stay out!)
2) Hold BOTH softkeys down at the same time
3) Whilst holding softkeys, turn the unit on
4) You will be prompted to press "SEND" to reset all user data (you will lose everything on the internal storage. Press the Dial (green button) to reset.
Click to expand...
Click to collapse
Nope. Stuck in bootloader is stuck in bootloader. Like, stuck. No, really, it's stuck. Hard-resetting doesn't get it out.
heyadrian said:
n.b. This often happens when the radio version of your phone isn't correct. If you notice, when you get stuck in the "white screen" the "gsm signal sight" is frashing green!
Click to expand...
Click to collapse
There's no white screen, just bootloader rainbow. Also, there's no chance that I flashed the wrong radio, because this phone has never been flashed with anything but the official ROM. It's never even had a HardSPL flashed on it.
hmmm...now that you mention it has never had a hardSPL, maybe that could be the next step?
i understand that some people may want to keep a "stock" configuration in case waranty needs to be claimed or for any other valid reasons...but if the phone is out of waranty, theres little to lose.
only reason i'm suggesting it is because cmonex has a hardSPL that aims to fix EXACTLY this problem, among others (if i understand your problem and cmonex's fix correctly):
http://forum.xda-developers.com/showthread.php?t=420683
also, this thread links to a page in the wiki about your problem (or something along the same lines):
http://forum.xda-developers.com/showthread.php?t=423486
finally, a collection of hardSPL versions can be found in this "roll up" thread:
http://forum.xda-developers.com/showthread.php?t=498320
i guess you may have already gone through the above mentioned links but if not, they may open up more avenues for troubleshooting or even a permanent resolution.
I've had my G1 for about 1 year now... about 1 month ago it just stopped working. WHEN I TURN IT ON I GET AN ERROR IMAGE (its an exclamation point inside a triangle with a g1 phone right under it)
What the heck does it mean?
The phone is pretty much useless, cant do anything to it.
I've taken out the battery put it back in and nothing....still get that image.
I have no idea what to do.
Can anyone Help me???
http://www.flickr.com/photos/[email protected]/3986746644/
see if you can get into bootloader with camera and power.
Have you been running a cooked ROM or a stock ota release?
OTA. Anything I got on the phone i got through the market place or from t-mobiles updates and stuff. i really dont know anything about "cooked roms"....
Didn't Work
david1171 said:
see if you can get into bootloader with camera and power.
Click to expand...
Click to collapse
It didn't do anything. no bootloader, no nothing. it was still on that same image.
thanks anyway.
lmvcorp said:
It didn't do anything. no bootloader, no nothing. it was still on that same image.
thanks anyway.
Click to expand...
Click to collapse
Sounds like a brick.....RIP lmvcorp's G1
I need a new screen for my spare G1 and would be willing to take it off your hands......
don't give up on it just yet, i remember reading about this somewhere and someone getting this fixed on a rooted phone, i don't now bout stock but let me look
I agree that its better not to give up, but with an unrooted phone, it seems unlikely that there is a fix. Root gives so many more options in the way of workarounds. Without those workarounds, it will be a miracle to get a somewhere on a phone that can't get into the bootloader. Would it be worth running a logcat and posting it? I can't remember if ddms will recognize a device that is on that screen or not.
Grid, any thoughts on that?
i am trying to look up the info, the screen means kernel or rom corruption, can prob still be adp push. i keep getting distracted and i am not used to being up this long
to the op, try sliding out your keyboard when on that screen and press alt + and w and report back if it does anything
i knew i knew this, duh. you are stuck on the stock recovery, try what i said then, pull the battery and reinsert it and power the phone back up by holding the camera and power buttons if you get into the tri color screen,report back and everbody here can tell you what to do next
you could put DREAIMG.NBH in the root of your sd card, camera+power and run update and go through the rooting process..Many tutorials all over the web
jndd333 said:
you could put DREAIMG.NBH in the root of your sd card, camera+power and run update and go through the rooting process..Many tutorials all over the web
Click to expand...
Click to collapse
he cant get into bootloader.....
if its only going to that one screen, just take it to tmobile and have them replace it. you didnt mod it or anything
Tried it...
The Reverend Gridlock said:
to the op, try sliding out your keyboard when on that screen and press alt + and w and report back if it does anything
i knew i knew this, duh. you are stuck on the stock recovery, try what i said then, pull the battery and reinsert it and power the phone back up by holding the camera and power buttons if you get into the tri color screen,report back and everbody here can tell you what to do next
Click to expand...
Click to collapse
OK. I did what you said. I press ALT + W and nothing happened so i pushed it a couple of time and another screen came up... it wasnt the the tri color screen. I got a screen with a "box, an arrow coming out of it....with the phone outside and a loading bar at the bottom" I'm assuming this is like a un-boxing process. but right after that the phone just restarts and the process starts all over again.... G1 screen, then the error screen. I've also tried to press CAM+POWER after that in so many ways and nothing..... taken the battery off and nothing. tried so many combinations.....
(sorry it took me a while to report back, i was on vacation, then i caught the flu.)
i wish
B-man007 said:
he cant get into bootloader.....
if its only going to that one screen, just take it to tmobile and have them replace it. you didnt mod it or anything
Click to expand...
Click to collapse
Yeah... you know what TMOBILE ppl are jerks....
i was paying for insurance but then i cancelled it because i was trying to lower my bill and that within 1 month the whole error thing happened...
and i asked them if i could get it replace or fixed....
i told them i payed all this time and u guys cant do anything for me...
they just said sorry.
i'll try another t-mobile store.
Link
jndd333 said:
you could put DREAIMG.NBH in the root of your sd card, camera+power and run update and go through the rooting process..Many tutorials all over the web
Click to expand...
Click to collapse
Can you post some LINKS????
Thanks.
If you cant get to the tricolor screen then DREAIMG.nbh wont help
You should take it to the store and tell them it happened after the update.
Are you sure your home button isnt stuck?
HELP PLZ
Ok. I've searched and searched... and I still don't know what to do. I found a method on trying a "master reset" but after it re-boots its still stuck in the "triangle, exclamation, phone" screen. Attached are photos of how the screen looks like after every step. I think the problem is that the software is damaged and that it cant be loaded correctly. Is there anything I can download into the SD CARD and load to "alt+s"???
Hi guys
Please help! Basically, I bought an item off ebay on my phone. The seller then sent me a question which I picked up through my gmail email account on my T-Mob G1 and when I clicked 'Respond Now' in the email...
My phone just died and went to a multi-colour screen saying the following:
DREA110 PVT 32B
HBOOT-0,95,0000
CPLD-4
RADIO-2.22.19.261
Sep 2 2000
I am sooo worried that I've lost everything... my pics of my little boy, contacts etc etc... is it a lost cause? Am I doomed?
Please help me fix this I can't find my user guide or a backup disc if one was supplied in my pack I've lost it!
Nat x
That's the boot loader screen, nothing to panic about. It's accessed by turning on the phone with the camera button held in.
If you pull the battery and restart the phone, does it go straight back to this screen?
Hi GoldenarmZ
Thank you sooo much for your reply!
Yes when I turn it off and back on it takes me straight to the screen... took my SIM card and memory card out too and still takes me to that screen.
N
It's possible your camera button is stuck in.. give it a wiggle and pull the battery again.
If that doesn't work, Pull the battery, hold down the [home] button, replace the battery and power on (still holding home).. see if you get a different screen.
Should I leave my SIM card and memory card out when I press the home button or does it not matter either way?
Camera button isn't in by the way
natell1983 said:
Should I leave my SIM card and memory card out when I press the home button or does it not matter either way?
Camera button isn't in by the way
Click to expand...
Click to collapse
Put the sim back in, memory card doesn't matter at this point.
You're great!! Thanks, it now has a pic of a phone with a triangle 'i' symbol?
Sorry for late reply, had to quickly bath my baby!
Well the phone is probably fine since you can get bootloader and recovery screens. There's no reason to think you've lost any data, all your photos will be stored on the memory card anyway.. but if its going straight to bootloader every time I reckon your camera button must be broken. If that's the case there isn't a great deal you can do except get it repaired by t-mobile. There's no point wiping the phone or anything like that as no matter what you do, every restart will come back to the bootloader screen.
All I can suggest at the moment is to take the back off the phone and hammer the camera button a few times.. really give it some agro.
If it were me, I'd be at it with a screwdriver and a good portion of fury by now, but if you're not a natural geek that's probably a bad play.
So the phone pic with the 'i' sign is basically telling me there's a problem with the phone not the data?
I've attacked the camera button but I really don't think it's the camera button stuck in?
Is there nothing else I can do?
in the i screen when I press home and power off the android system recovery screen comes up in front of the image with the following options:
reboot system now [home+back] - tried this and just turned off phone
apply sdcard:update.zip [Alt+S]
wipe data/factory reset [Alt+W] - will this delete everything saved to the hpone i.e. contacts etc?
wipe cache partition
Then at the bottom it says:
E:Can't open /cache/recovery/command
natell1983 said:
So the phone pic with the 'i' sign is basically telling me there's a problem with the phone not the data?
Click to expand...
Click to collapse
No, that's the recovery screen.. you can use it to reload the phone's operating system. You can give that a try, but bear in mind you will lose all downloaded apps, system settings, sms messages etc. Your contacts should be synced with your google account so you won't lose those, nor will you lose any music and photos on the memory card.
Are you a t-mobile UK or US customer?
I'm UK, what's the cache partition? Will I still lose the above things i.e. txts etc if I clear the cache partition?
I'm not insured so don't think T-Mob will fix it for me
natell1983 said:
I'm UK, what's the cache partition? Will I still lose the above things i.e. txts etc if I clear the cache partition?
I'm not insured so don't think T-Mob will fix it for me
Click to expand...
Click to collapse
Clearing the cache partition won't help.. How long have you had the phone? T-mobile replaced my first g1 under warranty.. If it's under 12 months old and its not damage you've caused yourself, they should fix it.
had it 14 months nearly
Well if you don't want to pay for repairs, you'll have to try reflashing the phone.. there's very little else you can do at the moment.
Do you have a card reader that will fit your phone's memory card?
Yes I have a card reader... I don't know how to flash it though?
natell1983 said:
Yes I have a card reader... I don't know how to flash it though?
Click to expand...
Click to collapse
I'm going to tell you
Just give me a minute to find the files you need.
How good are you with computers..? Do you understand zip files and such? and are you using windows xp/vista/7 ?
Just so I know where to pitch these instructions..
Not to but in, because the advice is sound, but it may be wroth getting everything off the memory card before performing the flash.
am sure you already thought of that, but I know whta its like to miss that one step and lose something important.
and yeah I know it shouldnt make a difference, but safety first.
Any help would be greatly appreciated.
I have a launch day Nexus One running CM5.0.5.3, the OC/UV kernel, and the EPE54B radio.
It has all been running great until today. I took it out of my pocket and it was warm (not hot) to the touch. I noticed the screen was blank but the buttons along the bottom were illuminated. I tried resetting it (power+volume down+trackball) and that didn't do anything, so I pulled the battery. When I rebooted it, it seemed to take a longer than usual time at the initial boot screen, and then went to the animated screen. It stayed on the animated screen for quite a while and then froze. It's stuck on the X mid-formation.
I then booted into the bootloader (which reacts like normal) and went into recovery. I re-flashed CM5.0.5.3, no effect. I wiped cache and system and re-flashed. Nothing. I did it again, and it finally booted up but I could only select things with the scrollball. The volume rocker worked fine, but the touchscreen is completely non responsive.
If I let it sit at the boot screen for a while it will go black eventually and time out.
I'm at a loss. I'm in the process of downloading a stock ROM and am going to flash it next. Anyone have any suggestions? My bootloader is (obviously) unlocked, so I'm worried about warranty work
Update: Just got it to boot (with the stock ROM) and I've got a warning screen saying:
Sorry!
Process system is not
responding.
[Force close] [Wait]
Any ideas?
Reflash CM 5.0.5.3 and then post back
Ok, re-downloading now.
Just flash in recovery?
Flashed in recovery (after wiping)
The phone stays on the stationary initial boot screen (four bars) for about a minute and a half and then goes to the animated cyan X. It stays there booting for probably two minutes before stopping mid-animation. If you let it sit there for a while the screen will time-out, which you can bring back with the power button. Sometimes when you hit the volume rocker you can hear the beep beep but nothing shows on the screen.
What the hell is wrong with my phone?
After an obscenely long time I got it to boot up.
Touchscreen is not responding, trackball is not responding, I have a question mark on the battery indicator, and no service.
I can't unlock the screen because of the non-functioning touchscreen. Live wallpaper is running great, it makes the sound when USB debugging is connected, it just won't react to any input.
I can, however, establish an ADB connection. It shows up on the device list and a remount succeeded.
Would reflashing the radio be of any benefit?
Dang the touch screen is unresponsive? I'm not an expert, but i'll try to give you some ideas.
I had some trouble once and I used settings-privacy then erased everything from within the OS. Then I reported to the screen just before going into recover and hit clear storage. Then went into recovery and wiped everything that I could. After that, flash the Rom that you want.
I've done a full wipe to no avail.
I'd bite the bullet and call htc, don't mention that you have rooted, it may be a hardware thing.
Scaaaary!! But hey, it happens. I would also try wiping for EXT on the SD card if you have been using apps2sd.....May not hurt, mights well try everything.....
Wiped everything, reflashed radio, flashed to stock. Nothing. This is exactly what I was worried about when I unlocked it.
Oh, well.
liam.lah said:
I'd bite the bullet and call htc, don't mention that you have rooted, it may be a hardware thing.
Click to expand...
Click to collapse
Yeah, I'll do that tomorrow. I guess I'll flash everything back to shipping and hope they don't notice.
mortzz said:
Wiped everything, reflashed radio, flashed to stock. Nothing. This is exactly what I was worried about when I unlocked it.
Oh, well.
Yeah, I'll do that tomorrow. I guess I'll flash everything back to shipping and hope they don't notice.
Click to expand...
Click to collapse
Many people have posted that they got a replacement even with an unlocked bootloader. One guy I heard said they charged him $55.
Either way, you can probably get a replacement.
Hey,
I bought a T-Mo HTC G1 on ebay and it worked pretty well. It would reboot a few times a day but oh well. I sold it on ebay (full disclosure on the problem) when I bought my Milestone.
It was working fine, I took some photos of it turned on, sold it on ebay. Shipped it off, the guy got it, and then claimed it wouldn't turn on and shipped it back.
So, I shipped away a working phone, and now when I've received it when I turn the phone on it just indefinitely hangs on the "T-Mobile G1" screen as soon as I turn it on. I never get to the "Android" loading screen or anything. Any tips on what I can do? I'd love to be able to fix it so I can try and sell it for _something_ while I still can.
Thanks for all your help in advance
If it honestly worked as you state when you sent it, then my guess is that one of two things happened to it;
1) he tried to install the deathspl using the dangerous method -- which means using RECOVERY rather than fastboot and bricked it.
2) he ALREADY HAD a bricked phone and swapped mainboards out.
Either way, if what you say is true, he's pulling a fast one on you.
You can confirm either of these with just a serial cable.
If the device is stuck in boot mode 3, then its bricked.
If the IMEI matches, it is #1 he's pulling.
If the IMEI doesn't match, it is #2 he's pulling.
Either way, I wouldn't refund his money. If he paid with paypal or something like that, then you should be able to present your case for him causing the damage, which makes HIM liable TO YOU. It also makes him liable for FRAUD, which is a CRIMINAL offence.
Make sure that you confirm bricking first though;
you need to try to start it in fastboot or recovery mode.
If it won't go into either of those modes (note: stock SPL doesn't HAVE a fastboot mode... but it its bricked, then it has some engineering spl installed -- which is how it was bricked), then start it in bluelight mode and attach a serial cable to diagnose.
Note: If it IS bricked, then you'll need a jtag to fix it.
bradass said:
Hey,
I bought a T-Mo HTC G1 on ebay and it worked pretty well. It would reboot a few times a day but oh well. I sold it on ebay (full disclosure on the problem) when I bought my Milestone.
It was working fine, I took some photos of it turned on, sold it on ebay. Shipped it off, the guy got it, and then claimed it wouldn't turn on and shipped it back.
So, I shipped away a working phone, and now when I've received it when I turn the phone on it just indefinitely hangs on the "T-Mobile G1" screen as soon as I turn it on. I never get to the "Android" loading screen or anything. Any tips on what I can do? I'd love to be able to fix it so I can try and sell it for _something_ while I still can.
Thanks for all your help in advance
Click to expand...
Click to collapse
Thanks for all that info. Too bad that when he filed his dispute with Paypal he claimed the phone didn't work when he received it, and so they automatically sided with him seeing as he's the buyer. I've been disputing it and getting them to re-open the case over and over trying to get them to listen but so far no luck. Hopefully this last time it will have a better chance of being overruled seeing as I've been speaking with managers the whole time.
Anyways, I've tried booting the phone normally, booting the phone pressing home, camera key, all different combo's and the only time it _doesn't_ hold up on the T-Mobile screen is with the "home" key, where it gets to that rainbow screen and just displays a few lines.
So are you saying the phone is more or less hooped? What's this jtag you speak of?
If you can get to the bootloader "rainbow" screen, then it's not bricked and it's quite possible your buyer was being honest. You should be able to reflash an official image and get it back in working order.
Download this:
http://android-dls.com/files/upload/DREAIMG.nbh (for a US phone)
or this:
http://android-dls.com/files/upload/uk/DREAIMG.NBH (for an EU phone)
Use a card reader to put it on the root of your sdcard (not in a folder), and power on the phone using [camera]+[power]. You should get the rainbow screen followed by a progress bar and if all goes well, a working phone.
goldenarmZ said:
If you can get to the bootloader "rainbow" screen, then it's not bricked and it's quite possible your buyer was being honest. You should be able to reflash an official image and get it back in working order.
Download this:
http://android-dls.com/files/upload/DREAIMG.nbh (for a US phone)
or this:
http://android-dls.com/files/upload/uk/DREAIMG.NBH (for an EU phone)
Use a card reader to put it on the root of your sdcard (not in a folder), and power on the phone using [camera]+[power]. You should get the rainbow screen followed by a progress bar and if all goes well, a working phone.
Click to expand...
Click to collapse
Do you roughly know how long it will then take the phone to update to latest T-Mobile release, as until then can't use a lot of the software on the market place
walkerx said:
Do you roughly know how long it will then take the phone to update to latest T-Mobile release, as until then can't use a lot of the software on the market place
Click to expand...
Click to collapse
No idea.. iirc there's an option in the settings to check for OTA updates.
Edit: There are more recent nbh files floating around the internet but I don't have links to hand. Should be easy enough to find a 1.6 image.
goldenarmZ said:
No idea.. iirc there's an option in the settings to check for OTA updates.
Edit: There are more recent nbh files floating around the internet but I don't have links to hand. Should be easy enough to find a 1.6 image.
Click to expand...
Click to collapse
Yeh, looked for the OTA check in the phone and can't find it. I tried another NBH image but that reported 'not allowed'
Correct, ability to get to rainbow screen means not bricked.
In fact rainbow screen means stock SPL 0.95.0000.
The NBH is the only option.
Doesn't matter about being able to "OTA" it -- just root the RC29 and install preferred system image.