My G1 screen stopped backlighting and then finally stopped working/detecting its position completely, and today I just got my replacement phone from T-Mobile and now I have to ship back my old one to avoid $100-something in fees. I have my phone rooted with JF 1.5, does anyone know if will they try to use this against me in any way to say its my fault my phone broke and then charge me for the new one?
unless your returning it to ebay thens its a no go i think you can remove teh recovery image back to orig and flash the Rc29 then it should be good.
Any ideas how to go about doing that without having the screen working? It's going back to HTC/TMobile, whichever takes care of broken phones.
acanz said:
Any ideas how to go about doing that without having the screen working? It's going back to HTC/TMobile, whichever takes care of broken phones.
Click to expand...
Click to collapse
oh sorry just leave it then htc has a 2yr warranty i think, dont tell tmo you rooted it thats foolish.
you will need to plug the phone into your computer and have adb working. then just do adb push /dir/to/DREAIMG.nbh /sdcard/DREAIMG.nbh, that will put the DREAIMG.nbh on the sdcard of the phone. after that you can type adb shell reboot bootloader and it will send the phone to the bootloader, after about 2 minutes you can press the power button, wait 30 minutes and reboot the phone with the three finger salute it will be unrooted(in theory)
I'm on a Mac, does adb work with that? I never got around to setting that up. My main concern is having them find my phone is rooted, I didn't tell them it is I just told them the screen is broken.
Well the screen just started working again when I started it back up, but only with the keyboard out. I'm not sure whats wrong with this phone, but now its back to RC29 and TMobile can have fun fixing this stupid thing.
Related
I've looked all over, and I believe I already know the answer to this..
But of course while flashing ROM's and themes and whatnot, I believe I've bricked my G1. Turning it on just leaves it hanging at the T-mobile G1 screen. I cannot get into recovery or fastboot mode. (Again, nothing happens when I hold down Power + Home, or Power + Camera).
Going to say it one more time, because I've been looking things up all morning...and people seem to ask this a lot I cannot get into recover or fastboot mode. Holding down Power + Camera, Power, or Power + Home just leaves me with the same results, stuck at the T-mobile G1 screen for hours+.
Is my phone bricked? Am I screwed? is there anything I can do, or does this require replacing hardware? I've heard of some people finding a way out of this, and I've also heard others saying I'm screwed.
I received my G1 from customer care from T-mobile... So I guess I can technically return it? Should I just send it back, or will they know I've broken warranty by playing with the software?
If you can't get into bootloader, or recovery, you are bricked.
yep, prob bricked .but have you tryed just as a last resort, take out your battery, hold the camera button, and put it back in to see if it will boot into the spl. if it doesnt start right away, try holding power right after doing it again
__________________ B-man007 get's all the credit if it work worth a shot good luck
So I figured. I tried the power thing, Lucky69. No luck here.
Does anyone have a suggestion on what I do? Like I said, I've only had the phone for a couple of days now. Is it possible to return it to T-mobile? Do you thnik they'll know what happened and say no, or just flash the device and get me a fixed/new one? Can I open it up and fix it myself?
just act like when you tryed to turn it on it dont work .they should replace just don't tell them you been messing with it .but if you can't get into recovery,bootloader ect then it's done for .also if t mobile give you any trouble ,then call htc and go that route . but if you only had a fews days should be no problem good luck
Yeah, if you just got it a few days ago, it shouldn't be a problem. I'd be willing to bet tmobile will even replace it. That will save you the hassle of going through the HTC route.
That's what I was going to try. Say something about I was prompted to OTA update to 1.5, Walked awayrot he phone, came back and it was as is. I just don't know their ability to open it up and look at it/hook it in and see a ROM on there, ya know?
ya ,that would be good to say .also the tmobile store prob won't know at all just take it in .i haven't ever heard of any one getting refused unless you tell then you what you were doing .don't worry they won't come after you .just play it cool .you aren't the first one to do this .but the sooner the better then you will have your phone again .then you can go back to it just be carefull on what you flash .good luck. just say it said update and you hit ok then that's when it did it .
Recently rooted my G1 this week and installed cyanogen mod. everything's good.
I saw some cool themes and tried to install em. didn't work so just restored my back up.
Then i read that i have to be on RC30 to use the theme. I followed this guide:
http://www.intomobile.com/2008/11/1...on-your-t-mobile-g1-and-keep-root-access.html
phone gets stuck at tmobile G1 splash screen. i think hey, no prob, ill just go back to recovery and restore my back up again. take out, put in battery. home+power... uhh that's not working. even tried pressing the power+camera buttons. pressing the call+menu+end button isn't even rebooting it..
this... really sucks. is there ANYTHING i can do to fix this? maybe through adb or something? i have nandroid files backed up my computer too if that helps
bulldozamendoza said:
Recently rooted my G1 this week and installed cyanogen mod. everything's good.
I saw some cool themes and tried to install em. didn't work so just restored my back up.
Then i read that i have to be on RC30 to use the theme. I followed this guide:
http://www.intomobile.com/2008/11/1...on-your-t-mobile-g1-and-keep-root-access.html
phone gets stuck at tmobile G1 splash screen. i think hey, no prob, ill just go back to recovery and restore my back up again. take out, put in battery. home+power... uhh that's not working. even tried pressing the power+camera buttons. pressing the call+menu+end button isn't even rebooting it..
this... really sucks. is there ANYTHING i can do to fix this? maybe through adb or something? i have nandroid files backed up my computer too if that helps
Click to expand...
Click to collapse
There is something you can do 2 legal and 2 illegal
1) You could steal someone elses phone
2) You could buy a new phone
3) You could switch the motherboard out from another (non-bricked) G1 into your phone
And 4) You could breAk into HTC HQ and steal the machine they used to originally flash your phone with, connect it to your phone's JTAG' points and flash. Thisnis the most risky and most expensive because you ARE stealing, you ARE going to get sued, BUT you will have your phone back
JAguirre1231 said:
There is something you can do 2 legal and 2 illegal
1) You could steal someone elses phone
2) You could buy a new phone
3) You could switch the motherboard out from another (non-bricked) G1 into your phone
And 4) You could breAk into HTC HQ and steal the machine they used to originally flash your phone with, connect it to your phone's JTAG' points and flash. Thisnis the most risky and most expensive because you ARE stealing, you ARE going to get sued, BUT you will have your phone back
Click to expand...
Click to collapse
thanks! ill consider it. i like your thinking!
anyone else!? pff
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.
Pardon for the long post but my Nexus One has been out of comission for a few days now so I'll list everything I've tried to make it work in an attempt someone might be able to help me!
Okay, here goes.
A couple days ago I removed the battery on my phone to install an invisible shield. Prior to that I had owned the Nexus One brand new for about a week, had it rooted first thing with the HTC Desire ROM...it was running perfectly
After the installation of the shield was complete I reinserted the battery and hit the power button. The phone booted straight to the bootloader (aka white Robots on Skateboards screen). Funny thing, I was unable to navigate the bootloader (vol up/down) without fiddling with the trackball first by pressing it a couple times) Anyway if I would reboot the phone via bootloader it would return...power off the phone it wouldn't power off just reboot to bootloader.
In this mode I could still use fastboot perfectly and I could enter the restore screen. At this point I kept attempting a reboot and it actually went through at one point and did a full boot to the OS...when I powered down and booted up again however, it was back to the same issue.
On the modaco forum they suggested I flash an alpha2boot.img as the boot image replacement for r21 desire rom as a fix, I tried this method with no success. Since, I've factory reset the phone several times replacing it with various ROMs (currently running stock) none of it fixed the problem.
I also found a way to brute force the phone into safe mode via the fastboot command in prompt: fastboot-windows reboot Using this command the phone successfully reboots, albeit into SAFE MODE. In safe mode the phone works perfectly in every way. I'm just limited in that I can't install any applications and I can't reboot properly (without a computer and command prompt).
I was doing some research on the forums and read the problem could be with the trackball. It would make sense that the phone could only boot to bootloader if the phone had the key press for the trackball triggered somehow. That said, the trackball functions perfectly when operating the phone in safe mode so I doubt this is the issue.
Another idea is that the phone is stuck in some state in the SPL or bootloader...I was wondering if there was anyway to reflash the SPL or bootloader to see if I could resolve the issue that way. (how I would do this, I have no idea)
Any help, suggestions, or advice is very appreciated. As I already unlocked my phone I have a feeling I am out of luck for warranty though I would pay for HTC to repair it if they could. I would prefer to fix it in the software however and not send it in.
Reflash the stock ROM and see if that helps.
mortzz said:
Reflash the stock ROM and see if that helps.
Click to expand...
Click to collapse
He said he's running stock rom...
@ OP, if everything was absolutely perfect before putting the shield on, and everything to crap immediately after finishing the shield, then obviously something went wrong during the install.
The obvious yet unfortunate conclusion is that some solution got inside or something, most likely inside the trackball. =\
Detail exactly what you did when you installed the invisible shield.
Did you get you phone wet at all?
Got the front of the phone a little wet and I'm guessing some did get in the trackball. That said, I do invisi shields every day for my job and never had an issue with any phone...wouldn't it be ironic that mine was the one that got screwed up.
I think it's interesting to note that the trackball still works perfectly when the phone is running in safe mode, no double clicks or anything like that...possibly a sensor was tripped?
Got the front of the phone a little wet and I'm guessing some did get in the trackball. That said, I do invisi shields every day for my job and never had an issue with any phone...wouldn't it be ironic that mine was the one that got screwed up.
I think it's interesting to note that the trackball still works perfectly when the phone is running in safe mode, no double clicks or anything like that...possibly a sensor was tripped?
So I called it quits on fixing this phone and I'm sending it out to HTC does anyone know how I go about getting restore back to factory settings?
Well you can't relock the bootloader, but if you can use fastboot when your phone's on the booatloader, you can use that to wipe the phone.
Oh wow, sorry to hear it.
If your phone will not boot without the help of fastboot, I wouldn't worry to much about what state Android is in (factory, or custom rom). HTC will attempt to boot the phone, toss it in a bin, and then send you a replacement.
Or that is my assumption anyways. A friend had a similar issue; he unlocked his phone and decided after flashing the Desire rom, that he wanted to stay stock with what came on his Nexus for a while. After flashing the stock images back, his phone looped into bootloader. Off to HTC it went and within a week he had a new phone.
Best of luck!
Sorry to post in such an old thread, but I'm having the exact same issue. Even the part with the invisible shield. Didnt install it myself, the idiot at best buy used too much of the liquid I guess. Did you send yours in or what? I managed to get the phone to work for about a month then it started acting up again today. Wont boot into anything other than safe mode, or fastboot. When it boots into safe mdoe, the phone turns off within a few seconds then goes straight to the boot animation. Would love to get this issue settled, really annoying
i am having same problem. fasboot doesnt even find my phone. i got into safe mode but when i turned it off and back on it went back to fastboot
Same
I am getting the same problem! this really sucks. I think the phone might have gotten a little bit wet, just a few drops of water, and that may have caused this. Should I just call HTC and send it in?
btw, the phone was working fine, even with the very little moisture that was wiped from it. But, I took out the battery when I got home, and this happened.
so is this because on invisibleshield? cuz i just ordered mine today!!
I think its from a little bit of moisture getting into the trackball. I've been doing many "tests" trying to figure out the problem, and my almost final conclusion is the trackball not working good. Most of the time I try to start-up the phone i get into safemode, and once I have gotten into the normal way of things, but the trackball wasn't working well. I think I might have to cal htc, and that sucks because I am going out of the country in 4 days... I won't be able to take my nexus if I can't come up with a way to fix it myself.
I DID IT!
Well, I think I did.
My theory that moisture was the cause of this bootloader stuckness is quite correct. I took a towel, and rubbed the trackball to it for a good 5-10 min, then I did it for another 5-10 min wiping while pressing down on the trackball. I'm very sure that there was some moisture extracted from the device. The trackball is working now. I now do not have to call HTC or send it in.
I kept on booting into fastboot and then recovery, being unable to press buttons, but then I rebooted again into safe mode, where the trackball wasn't working either. I kept moving around the trackball, and then I figured it out, because I felt a slight bit of moisture. Now, it boots up normally, I can access the recovery, and all selection is working.
But, I have a bad feeling that this problem will come back to haunt me. It's good for now though.
Phone is working great as usual.
Can confirm the same issue.
Drop of water on the trackball.
Rebooted into an unresponsive fastboot.
Fastboot reboot command from the computer got me into safemode.
Rolling the trackball while pressed fixed it, the phone boots properly now.
so yesterday my power button decided to freak out and stop working. I had been using the phone just fine ten minutes prior. I thought I felt it vibrate in my pocket so I took it out to see and there was a notification that Amazon app store had an update. I allowed the update and saw the power menu pop up as I was putting it back in my pocket. I hit the back button and put it in my pocket without looking to make sure the power menu closed. Bout 20 minutes later I check my phone and the power button won't turn the screen on. I pull the battery and when I put it back in the phone boots automatically. I tried booting into recovery from ROM manager and it just applied update.zip (I think, cuz that's the first option on the menu iirc) and proceded to reboot. The button itself seems to work fine. It isn't stuck in and it pushes in and out like normal. I tried cleaning around it with an alcohol wipe with no results.
The phone thinks the button is pushed in but why doesn't the power menu just keep spamming? I am running miui and it had an option to use the volume rocker to turn the screen on so that's what i'm doing for now.
Is there a way to use recovery so I can see if this is a software issue? To me it seems like if it was hardware the power menu would keep poppong up, but i'm no expert.
Thanks for any advice.
EDIT: another update for Amazon app store. I applied the update and the power button worked a few times to turn the screen on and off and even a couple times to bring up the power menu. I rebooted thinking my problem was solved but nope. It does work sporadically tho. I tried uninstalling Amazon app store completely when this first happened but it didn't help anything. Might be totally unrelated and purely coincidence.
Sent.
Hopefully your warrenty isnt up! Send it in. ODIN back to stock
sent from my 2nd Samsung captivate.
sepherian said:
Hopefully your warrenty isnt up! Send it in. ODIN back to stock
sent from my 2nd Samsung captivate.
Click to expand...
Click to collapse
Yeah that would be ideal. Warranty expired bout a week before this happened. isn't that how it's supposed to work?
Sent.
nawlage said:
Yeah that would be ideal. Warranty expired bout a week before this happened. isn't that how it's supposed to work?
Sent.
Click to expand...
Click to collapse
Call Samsung, they will help. They unbricked my phone for me !! Of course, they did a complete wipe, An mine was several months out of warranty !
No kidding !
how much did it cost?
Sent.
Just had the same problem start up a few days ago. However, I bought my phone from BestBuy and pay $10 a month for the BlackTie Protection. I brought it in, said somethings wrong with the phone (he didn't even look at it) they gave me a loaner CrackBerry, and new phone will be waiting for me on Monday. Already have my ROM files waiting on my desktop...
sandrich said:
Just had the same problem start up a few days ago. However, I bought my phone from BestBuy and pay $10 a month for the BlackTie Protection. I brought it in, said somethings wrong with the phone (he didn't even look at it) they gave me a loaner CrackBerry, and new phone will be waiting for me on Monday. Already have my ROM files waiting on my desktop...
Click to expand...
Click to collapse
thats actually completely irrelevant.
update:
i figured that if it was a software problem that i could flash back to stock and my power button would be back. well, i odin 1clicked back to stock and it still dont work. now i need to flash back to miui so i can use the volume rocker to wake the phone up but i cant get into download mode. these methods ( http://samsungcaptivate.wikia.com/wiki/Putting_the_Phone_into_Download_Mode ) dont seem to work. number 3 got me into download mode to flash stock and now it just boots normally. number 4 brings me to android recovery 2e. any tips besides making a jig?
this is a bummer man, my phone takin a dump on me right after my warranty expires.
update #2: called att and it turns out i had 6 days left on my warranty. brought it back and got a refurb.
update #3: i have a new problem if you absolutely must follow my progress ( http://forum.xda-developers.com/showthread.php?p=19574329#post19574329 )