Hi!
Not to long ago my g1 was acting up so I did a hard reset. I was taken back to the start, but had to use JesusFreke's guide to register it without a data plan. I had to get it back down to RC29 I believe that is what it is, to get it to work. (The starting android screen went from the word "Android" in blue to I think a white one with the little android guy standing next to it. So I assume there was a change.)
After all that the problems still persisted. Then my g1 updated itself. It now has trouble turning on. I got it to turn on and noticed that it went back to the original android starting screen. So I'm assuming it went back to what it was before. But it still has trouble turning on after it has been turned off.
So, I believe I am under warranty still with T-mobile. I know that messing with your phone could void the warranty. I just want to know if they will notice, seeing as it went back to it's original state, yet still messed up. It's not rooted or anything. I had just set it back to RC29, but then it updated and took it back to what it used to be. Will they notice? If there is even anything to notice? Or am I just being paranoid? Thanks in advance!
if its not rooted, and it went back to orginal shipping rom your fine, as there is still some ppl that didnt update and still running it,
Related
Hello all,
I have recently upgraded from my g1 to an HD2. HD2 is a great phone but still miss android . Anyways, today I wanted to get my g1 to work without a sim or data plan and was about to start working on it when my g1 screen dimmed to just the blacklight with a black screen. I turned it off and tried turning it back on but it just comes up with the backlight on a black screen. It does not even get to the G1 screen. I cannot get to recovery mode or any other mode for that matter. I have searched around but not found any real solution to this problem (if there is one). I am thinking my phone is bricked but have heard possibilities using ADB. I have never used ADB before and if anyone knows if this is a possible fix to my problem that would be great. It would be nice to know if it actually could fix my problem before looking into it and learning it all while finding out it has no chance of fixing my problem. I have tried using my sim card and a different sd card so those are not causing the problems.
So the background of what I am running on my g1. Right before I got my HD2 I was using Cyanogen version 4.2.14.1 with and ext 3. I had no problems with it until now. I got my HD2 a week ago and my g1 has been on about twice in that time without a sim card just for comparing purposes to the HD2. Then just today (about 2-3 days since I last turned it on) the screen just went black and I had my problems. I cannot return my phone because it has been over a year and I dont have insurance on the phone so these are not possibilities for me unfortunately. I also don't really want to get parts from other g1's and take apart and put my g1 back together. I am just looking for something with ADB or any other possible solution to the problem (if one exists).
Any help would be greatly appreciated!
I had this happen to me before. Apparently, it was a hardware GPU problem that would cause a boot loop because it couldn't draw anything on the screen. This happened on SuperD, AOSP, Cyanogen, and stock Donut.
If your problem is the same, you should be able to get into recovery, regardless of your ability to see what you're doing. Easy way of telling is to hit Camera+End on boot. If it doesn't vibrate, you're able to flash still. You may be able to get the screen back temporarily by either pulling the battery or letting the battery die and recharging.
Anyways, I ended up flashing the DREAIMG.nbh, and trying to upgrade back to 1.6 to remove traces of hacking. (Be careful if you have DangerSPL, you want to restore the default before flashing DREAIMG.nbh) I eventually got the screen working on 1.6, but it died again, so I sent it in to T-Mobile and got a replacement. I'm now using AOSP with no problems.
One small note, however, I did start having my problems using Cyanogen's mod. May want to bring it up with him?
Sorry if this sounds scatterbrained, it's a bit late and I should be asleep right now.
e:Just realized you said the warranty was void. You may be able to get something out of what I did, though? Good luck, in any case.
Thanks very much for the help even though it was really late. I did understand pretty much everything you said and I tried the camera plus power button and it didn't vibrate so it should mean I probably can flash things still. I have drained the battery and am charging it back up to see if that helped.
I have a friend who knows ADB so I am going to have him look at it to see if we can't get it working through there. Also the G1 screen has been popping up but then fading right when its about to change to the boot animation. So we will see how things go and I'll try a couple different things and report back if anything seems to work or open up more possibilities.
Thanks again for your information.
Ok, so my friend and I were going to flash a rom through fastboot. It was responding and such so we knew we were able to get it in there.
Anyone know what the command to flash a rom in fastboot is and if there are specific instructions to follow?
Any help would be greatly appreciated!
coolookoo said:
Ok, so my friend and I were going to flash a rom through fastboot. It was responding and such so we knew we were able to get it in there.
Anyone know what the command to flash a rom in fastboot is and if there are specific instructions to follow?
Any help would be greatly appreciated!
Click to expand...
Click to collapse
google it. i did and got about 100 links telling me how to do it. "unroot g1 with fastboot."
sorry i have the same problem, but my g1 is not rooted nor has it been flashed before, my friend messed it up somehow? wen i turn it on all there is is a blank highlighted black screen. What do yall suggest i should do
r3s-rt said:
google it. i did and got about 100 links telling me how to do it. "unroot g1 with fastboot."
Click to expand...
Click to collapse
First of all we are not trying to unroot the phone just flash another rom
Secondly we already tried your "fantastic" method of using google before coming to the forums
Ok I think I just bricked my G1
I was following the steps on theunlockr.com and was following the steps to the T like I always do.
The problem incurred after flashing the spl. I flashed the correct radio then ir rebooted and went back into recovery mode. Then I flashed the spl all seemed well home+back and never rebooted. It stayed on a black screen for over 30 mins. So I took out the battery and waited a few mins and put battery back in and same thing. Just a black screen nothing I can do. I have tried holding home+power and camera+power and back+power nothing. I am stuck have looked it up and this is the best forum I have found to post in.
Any input would be great.
thanks
nate
the subject says it all. I have had fresh 2.1 since May and worked well until this weekend when I was outside with the phone in my pocket for a couple of hours. I think a mixture of the heat/humidity has bugged the phone out, because randomly the phone has a dead spot in the same spot and the screens just start scrolling through back and forth..... so I need to take this into the sprint store to get serviced but need to go back to an original state.
I tried the "unlockers" all in 1 method but got Error [140]: Bootloader version error so I'm stuck trying to get it back to a "sprint" authorized version.
any help would be great so I can use my phone.
tonyy1 said:
the subject says it all. I have had fresh 2.1 since May and worked well until this weekend when I was outside with the phone in my pocket for a couple of hours. I think a mixture of the heat/humidity has bugged the phone out, because randomly the phone has a dead spot in the same spot and the screens just start scrolling through back and forth..... so I need to take this into the sprint store to get serviced but need to go back to an original state.
I tried the "unlockers" all in 1 method but got Error [140]: Bootloader version error so I'm stuck trying to get it back to a "sprint" authorized version.
any help would be great so I can use my phone.
Click to expand...
Click to collapse
There is a CDMA forum for this kind of thing
I have a Galaxy S as shipped by Bell Canada. It doesn't have the 3 button download mode so I'm staying away from 3rd party roms for now.
It is unlocked and rooted. All has been well until today. I had it off for a while to use the SIM in another phone. When I turned it back on it asked for the SIM unlock code. I Dismissed that and checked the phone, all seemed well other than no SIM activation. I turned it off and removed the SIM and now it won't boot. I get the usual logo, the song, and for a long time the S logo. If I wait long enough it then appears to be off. If I press the back or menu key they will light up but that's it. I can't do anything else other than pull the battery.
I tried the hard reset with holding volume down and tap the power button. That only turns it back on with the same problem. The actual SIM is fine and working in another phone.
Is there anything I can do? If I could hard reset it I'd take it back to the store but I hesitate for now while it still contains my data.
this is a problem i have just posted about a couple of mins ago
but i can get it recovery mode and fatory reset with the vol up, home and power
then it will boot but obviously i have to then reset everything from scratch which is really annoying so anyone got any idea re this
lucky for you that you can get into recovery. Right now I'd be happy with a hard reset, it doesn't take long to rebuild the setup. I'd like to know who decided to remove the recovery mode, that's evil and keeps me from simply resetting the device.
its all the apps re downloading and installing them and resetting up accounts and swype and all that lot need a fix asap
do you know what version of andoid you are running
yes but at least you can get a working phone again, I can't without being able to get into any boot menus. Honestly it only takes 30 minutes to setup again from scratch. I'm on 2.1 and what I find at least on my HTC when it had 2.1 is that I setup the google account, let it sync contacts etc, then from Market Downloads I'll see listed all my apps that were previously installed. As long as I don't leave that screen I can install each app one after the other. Or a proper backup....
Any other magic key combos to reset this thing???
did you try hooking up to kies?
Yes but that does nothing since it never fully boots.
3rdcoast said:
I have a Galaxy S as shipped by Bell Canada. It doesn't have the 3 button download mode so I'm staying away from 3rd party roms for now.
It is unlocked and rooted. All has been well until today. I had it off for a while to use the SIM in another phone. When I turned it back on it asked for the SIM unlock code. I Dismissed that and checked the phone, all seemed well other than no SIM activation. I turned it off and removed the SIM and now it won't boot. I get the usual logo, the song, and for a long time the S logo. If I wait long enough it then appears to be off. If I press the back or menu key they will light up but that's it. I can't do anything else other than pull the battery.
I tried the hard reset with holding volume down and tap the power button. That only turns it back on with the same problem. The actual SIM is fine and working in another phone.
Is there anything I can do? If I could hard reset it I'd take it back to the store but I hesitate for now while it still contains my data.
Click to expand...
Click to collapse
Same thing happened to my phone, but a factory reset did nothing. The internal SD card gave out. Phone is now sent away for 3 - 6 weeks awaiting repair.
my phone did this to me today too, I was just about to post about this when I saw this thread.
So its an SD Card problem? theres no hope of getting it fixed without sending it in?
Yes I think it is the internal card meaning there isn't anything good enough to reset to. I walked the phone over to the store and I'll have to wait for new stock next week. Actually I'm lucky they will exchange it since I bought it outright which apparently is "against policy" even though they list a no contract full price. We'll see how it goes next week but overall I despise the telco industry in this country.
3rdcoast said:
Yes I think it is the internal card meaning there isn't anything good enough to reset to. I walked the phone over to the store and I'll have to wait for new stock next week. Actually I'm lucky they will exchange it since I bought it outright which apparently is "against policy" even though they list a no contract full price. We'll see how it goes next week but overall I despise the telco industry in this country.
Click to expand...
Click to collapse
i went to best buy today to try and exchange it, and apparently they only have a 14 day exchange policy with phones despite it saying 30 day on the receipt, anyhow i phoned samsung and they said i have to go through bell, even though im using the phone on telus, so that should be interesting.
So all the people that are having this problem have the Bell model?
Today i got mine off eBay, as soon a i turned it on, i get exactly the same thing.
It wont load into Android, i see that galaxy S logo and then black screen.
If i go into recovery i see "cant mount SD Card".
The more is search this forum the more i see that all the people with this problem are owners of the Bell i9000M model.
I seriously think they have some defect with the manufacturing line of the phone.
Have you guys installed any firmware on your phone before this happened?
mine is like that out of the box.
Mine is the same Bell model. There seems to be some issues with them which makes the lack of download mode even more dangerous. Right now it doesn't feel like the warranty is going to cover us for problems not our fault. I hope they replace it next week but if it still lacks download mode I'll remain nervous.
Seems like everyone is with the Bell model but my questions is:
Have you guys installed another firmware than the factory one which caused this to happen?
Are you running Stock?
We need to try and narrow this down as i am seeing too many posts about this issue, and they are with the Bell model.
clubtech said:
Seems like everyone is with the Bell model but my questions is:
Have you guys installed another firmware than the factory one which caused this to happen?
Are you running Stock?
We need to try and narrow this down as i am seeing too many posts about this issue, and they are with the Bell model.
Click to expand...
Click to collapse
i put new firmware on it last week, can't remember what it was but it was upgraded through kies so it's one samsung pushed to me, not a froyo unstable one.
bigc_13 said:
i put new firmware on it last week, can't remember what it was but it was upgraded through kies so it's one samsung pushed to me, not a froyo unstable one.
Click to expand...
Click to collapse
Thanks. if it was pushed to you via Kies i assume you were running stock JH2.
So it just stopped booting out of the blue?
To the OP: have you install any firmware on your device before this happened?
clubtech said:
Seems like everyone is with the Bell model but my questions is:
Have you guys installed another firmware than the factory one which caused this to happen?
Are you running Stock?
We need to try and narrow this down as i am seeing too many posts about this issue, and they are with the Bell model.
Click to expand...
Click to collapse
I haven't flashed any 3rd party roms. I did do the official update via Keis which even at the store today they reminded me that I should do the update.. That update seemed to go well and has been working for over a week until I turned it off for an hour. It still isn't clear if the disabled 3 button mode is hardware or software related but we all seem to have that in common too. So before they dismiss the whole thing and we get hosed over technicalities such as unlocking it should be clear that there are clear defects in these phones as far as I can tell.
I want to be comfortable that I'm not left out of hundred of dollars just because I choose to buy it outright and not be tied to contracts. Samsung has to play nicely because it is their phone. Bell has to play nicely because they are bringing them in and distributing to retail. What carrier I use should be irrelevant because the problems are not related to usage.
FYI, the clerks went off for conference to decide if I somehow got the phone against policy. Either they trust my story or I got mine moments before they got the memo about not selling outright.
clubtech said:
Thanks. if it was pushed to you via Kies i assume you were running stock JH2.
So it just stopped booting out of the blue?
To the OP: have you install any firmware on your device before this happened?
Click to expand...
Click to collapse
Same here, stock JH2 from Kies. Not rooted. Boots to Galaxy S logo, then black screen. Mine is sent in for repair... Almost two weeks now.
Seeing more and more of this being posted. There is obviously some issues with this phone.
clubtech said:
Thanks. if it was pushed to you via Kies i assume you were running stock JH2.
So it just stopped booting out of the blue?
To the OP: have you install any firmware on your device before this happened?
Click to expand...
Click to collapse
Our posts crossed..
Yes I believe mine had the JH2, the official keis offered firmware. I was looking forward to the biggie update at the end of the month so wasn't about to risk bricking before then. Irony stepped in anyway.
I'm a bit nervous until I get a new one. At that point if the 3 button mode still doesn't work I'll remain nervous that I'll get another potential brick.
edit-> yes, I simply shut it down for an hour or two to use the SIM in another phone to test that phone. At next boot it died. I knew something was wrong when the logo stayed up for much longer.
I have the 3 buttons enabled so it is not related to the 3buttons being disabled, however when i boot into recovery it clearly displays an error that it can not find the internal SD.
There is definitely something wrong with the Bell Galaxy S corrupting itself.
I bought mine from an eBay seller, he is saying the phone booted fine when he shipped it but when i opened the box today i only got this black screen after logo.
Gladly the seller will take it back.
Maybe this is why there are shortages everywhere in Canada. I hope the caught this up and are fixing it with the new batch.
Hey everyone, I have been trying to diagnose my HD2 alone for quite some time now, and thought maybe someone on XDA can help. So when i first got the phone, it ran just fine, about a month in i decided it was time to load it with a cooked rom. I used Energy rom because i loved the look. Before i had huge problems flashing it in the first place, after i got the flash to stay stable, the phone ran just fine. A while back (2010) i dropped the phone and cracked my glass. After replacing that, i had problems with the boot all over again.
When my phone boots it will boot 50% of the time, it will either freeze on the boot image (no red text) or just start up like normal. after 12-24 hours of general use, the phone will just freeze up and i will need to pop the battery out. Once i put it in, it will not boot unless i let it sit for a while. the longer i let it sit, the longer the phone stays working before it freezes. it seems that the longer it sits past a day doesnt matter, but it does increase the odds of booting in the first place. only a few times has it posted the rom number and not booted.
Im wondering if this could be a mainboard problem, or something im overlooking. I also had android problems back when 2.1 was ran from the exe. i also ran many other roms, and just recently the Nand 2.2 droid.
My biggest problem is ive spent over $100 USD trying to fix the glass/lcd.
Any imput would be greatly appreciated. so what do you think?
mdnelson09 said:
Hey everyone, I have been trying to diagnose my HD2 alone for quite some time now, and thought maybe someone on XDA can help. So when i first got the phone, it ran just fine, about a month in i decided it was time to load it with a cooked rom. I used Energy rom because i loved the look. Before i had huge problems flashing it in the first place, after i got the flash to stay stable, the phone ran just fine. A while back (2010) i dropped the phone and cracked my glass. After replacing that, i had problems with the boot all over again.
When my phone boots it will boot 50% of the time, it will either freeze on the boot image (no red text) or just start up like normal. after 12-24 hours of general use, the phone will just freeze up and i will need to pop the battery out. Once i put it in, it will not boot unless i let it sit for a while. the longer i let it sit, the longer the phone stays working before it freezes. it seems that the longer it sits past a day doesnt matter, but it does increase the odds of booting in the first place. only a few times has it posted the rom number and not booted.
Im wondering if this could be a mainboard problem, or something im overlooking. I also had android problems back when 2.1 was ran from the exe. i also ran many other roms, and just recently the Nand 2.2 droid.
My biggest problem is ive spent over $100 USD trying to fix the glass/lcd.
Any imput would be greatly appreciated. so what do you think?
Click to expand...
Click to collapse
Mate, I think it's rather hardware related problem. You better go back to the repair center before your warranty expires
silverwind said:
Mate, I think it's rather hardware related problem. You better go back to the repair center before your warranty expires
Click to expand...
Click to collapse
I went back right after i cracked the glass, and they said my insurance never covered it, even tho i pay extra on my bill for it. i voided the warranty when i replaced the lcd too
Does anyone know where i can get it fixed say under the counter or anything?
Verizon Galaxy S5 which I've had almost a year.
Sometimes when I turn on the screen, the screen flashes and then goes black. The buttons stay lit and I can enter the unlock pattern but not see anything.
Does anyone know if this could be a loose cable or ribbon inside the phone that needs to be tightened or might it be the screen itself? The weird thing is that when the screen does light up, it works perfectly.
If I knew which ribbon could be loose, I'd take the phone apart and tighten it. I'd hate to pay a fix-it shop for something I can do myself.
Mike
Warranty Replace
I spoke to a friend who used to work for Verizon and she reminded me that since the phone is less than a year old, I can go into the store and get it replaced under manufacturer's warranty. Yay me.
I will back up the phone's apps and data with titanium backup. Is there a different program that does not require root? I'm asking because I have rooted KitKat on the phone and might want to try going to Lollypop, but am not sure if there's root for that. I guess it's time to dive in, get my hands wet and see just how far one can get with rooting. Also, I will have to return the phone to unrooted status before going in. Such a pain.
Got replacement
I got a warranty replacement and have rooted android Lollypop on it. So happy.
I oden'd back to stock NCG and took all the OTA updates, did a factory reset and added a few apps.
It took the VZW employee less than 5 minutes to determine the phone was defective and in need of a replacement under warranty. The cool thing is that I didn't have to do any factory resets or anything else. The employee tried the test app on the phone and since the flicker is not something that can be tested for, sent me a new phone.