Related
Hello,
I upgraded to Froyo last week, and hadn't had any problems until now. Yesterday when I had my bluetooth hooked up to the phone, it all of a sudden disconnected, which has happened many times before when the phones battery goes dead. So, last night I plugged into the wall to charge it, and this morning I wake up to the screen constantly flashing on and off (showing the black startup screen that says "Galaxy S I9000 Samsung".
I've tried plugging it into my computer, plugging it back into the wall charger, and booting into recovery mode, but all it does is show the battery charging screen momentarily (batteries shows to have no charge it whatsoever), and then switches back to flashing the startup screen.
Can someone please help me out, it would be greatly appreciated.
Thank you very much,
Cam
Hi Cam,
I have the same issue as you have and I'm trying to find the way to reload my device with the stock OS Android 2.1 Eclair that includes the bootloader that seems defective for some reason.
I was bounced by from Bell support to Samsung support, then to Best Buy where I got it and back to Bell.
I'll keep you in the loop if I find a solution.
Good luck
Maxx
maxximux2000 said:
Hi Cam,
I have the same issue as you have and I'm trying to find the way to reload my device with the stock OS Android 2.1 Eclair that includes the bootloader that seems defective for some reason.
I was bounced by from Bell support to Samsung support, then to Best Buy where I got it and back to Bell.
I'll keep you in the loop if I find a solution.
Good luck
Maxx
Click to expand...
Click to collapse
Hey Maxx,
I called Samsung this morning and they told me to take it to the Bell store where I purchased it from, and they may need to flash it or send it in for repairs.
Definitely keep me in the loop, it's much appreciated. This is extremely frustrating.
Thanks,
Cam
Hi Cam,
I will try the instruction found in the post http://forum.xda-developers.com/showthread.php?t=870058 after work.
Let's hope this will do the trick.
Maxx
Hi Maxx,
Did you get a chance to try it out? If so, did you have any luck?
Thanks,
Cam
Hi Cam,
No success with any firmware combination I tried, I think the only thing left is to send it back for repair. There is many others that have the same issues. All seems to be related to an internal SD card that is defective.
Maxx
Thanks, dude. Unfortunately it looks like I'll be sending it back today. You know whether or not I should take the two SD cards out before sending it back? I presume I should at least take out the card that I purchased separately?
Very late reply but this happened for me today (i was trying to install cwm through program Heimdall). So i put phone to download mode and using odin i was able to push in android 2.3.6 and everything works fine (except root permision gone).
This morning I woke up and my phone was working fine. I had 2 updates in the market and I hit update all. After that my phone rebooted and it does the Verizon LTE animation and the LG splash screen but it goes into a black screen. While it's in the black screen the phone vibrates and the battery heats up. I tried going into recovery but it did nothing.
Pull the battery fo a few and wait before a reboot?
http://www.youtube.com/watch?v=TGjBRAVZKW4&feature=youtube_gdata_player this is the issue that's happening.
Sent from my MB860 using XDA App
so you said you went in to recovery and it did nothing? So you couldn't even get recovery to load? and are you stock or rooted with clockworkmod recovery?
I can't even get it into recovery. I hold the volume keys and power buttons and it just does the boot up then black screens.
Sent from my MB860 using XDA App
Just hold down the volume down button, then hold down the power button also. Continue to hold both through the lg splash, then it should be into recovery.
Sent from my VS910 4G using XDA Premium App
isoutsider said:
This morning I woke up and my phone was working fine. I had 2 updates in the market and I hit update all. After that my phone rebooted and it does the Verizon LTE animation and the LG splash screen but it goes into a black screen. While it's in the black screen the phone vibrates and the battery heats up. I tried going into recovery but it did nothing.
Click to expand...
Click to collapse
I had the same thing happen to mine 20 days after I got it. I had to have it replaced under the warranty, which means they had to ship it next day air.
I've heard of a few other people with the same problem.
Finally able to get into recovery and wipe data but now phone starts up and its black screen with the status bar across the top. It's acting like it has no home launcher.
Unfortunately you are going to have to get a replacement from VZW. If you are within the 14 day period you can just swap it at the store. otherwise you have to go through the Warranty folks and make sure you have them ship it to you overnight.
isoutsider said:
Finally able to get into recovery and wipe data but now phone starts up and its black screen with the status bar across the top. It's acting like it has no home launcher.
Click to expand...
Click to collapse
Do you have Clockwork installed?
If so, this is an easy fix.
If not, well, it's a little tougher.
The gist of what's happening is easy to find by connecting your phone while it's booting to USB and running "adb logcat" on your desktop.
That will give you the boot logs and the exact reason for what's happening.
If you're running my decrapified ROM, you may want to switch back to the stock ROM. Go to my stock NANDROID thread, download that, put it in the right folder on your SD card, then boot into clockwork and follow the instructions in the stock nandroid thread.
Make sure you clear data also!
No need to call verizon
I tried connecting the phone to the pc and got nothing. computer couldn't even detect it. I called verizon and got the phone swapped under the warranty. First thing I'm doing when I get the phone is putting the recovery on it. Would have made this process much easier.
Sent from my DROIDX using XDA App
isoutsider said:
I tried connecting the phone to the pc and got nothing. computer couldn't even detect it. I called verizon and got the phone swapped under the warranty. First thing I'm doing when I get the phone is putting the recovery on it. Would have made this process much easier.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
Yep, having ADB access is a surefire way to get your phone up and running again.
But, just for future reference, LG has a failsafe firmware updater that will always work, no matter what state the phone is in.
It's not super easy to set up, but it will fix a phone no matter how broken the software may be.
There's a thread in the Dev subforum with the files and instructions, but the gist is that it's accessed by holding VOLUP+POWER with usb plugged in, then plugging in the battery.
It's successfully recovered 3 phones so far.
It may not be the easiest way to get the phone back, but it has a 100% success rate
I'm having no luck with my new replacement I got from vzw. I've tried rooting it with S1C using both exploits, I've tried rootwiki's manual method and none of them work for me. Anyone got any tips?
isoutsider said:
I'm having no luck with my new replacement I got from vzw. I've tried rooting it with S1C using both exploits, I've tried rootwiki's manual method and none of them work for me. Anyone got any tips?
Click to expand...
Click to collapse
Well... you could always try my "toggle ADB" trick.
Turn usb debugging on, then back off, then on again.
Then follow the rest of the rooting instructions, but skip the whole exploit section.
(Basically, remount /system as rw, push su, chmod su, and push superuser, and install busybox)
Ironically, the phone doesn't actually NEED any exploits at all-- it's pretty unlocked to begin with!
Hey Everyone,
Just seeing if anyone might have a solution to my problem that I'm facing. I had rooted my phone when the root originally came out, and everything seemed to be working fine. I had been texting on my phone when it suddenly froze, I waited to see if it would come back, but it never did so I pulled the battery.
The phone originally booted to the M logo, but froze, after another battery pull the phone now won't turn on at all. As in it's not responding to the power button press at all. It's not being recognized by a computer, and there doesn't seem like much I can do.
Any suggestions out there? If my phone is bricked and can't even turn on, will a Verizon store know this? How could they?
thanks.
If u froze something like a system app that may have bricked it. Theres something u can flash which was a cracked version of an ota update that should fix it but u may not be able to receive official updates if u do that. Other option is to wait for an official sbf file
Sent from my DROID3 using XDA App
How can I flash something? There doesn't appear to be a way for me to access my phone. I can't get into restore or the bootloader.
What happens when you plug the phone into your charger(using the stock charger and cable)?
Nothing, no light, no anything
I actually haven't tried it in a situation like that so I can't give instructions :/
Sent from my DROID3 using XDA
Just take the phone into Verizon and tell them it has stopped working. You don't have to go into any detail at all.
g3m1n1 said:
Just take the phone into Verizon and tell them it has stopped working. You don't have to go into any detail at all.
Click to expand...
Click to collapse
I think that might be what I do, I can't imagine they would have a way of knowing it's rooted if the phone won't even turn on, charge, or anything.
Thank you, btw.
Try taking out the battery and plugging it in to the wall without it in it. If it starts to boot, let it. Then replace the batter and plug it into the wall again and let it charge up. Happened to my Droid X before and I was able to get it working by doing this.
Tried this, but couldn't get it to work.
Took it to a Verizon store and they said they would send me a new one tomorrow, and then all I do is send mine in afterwards.
Is there a chance that after I send them my phone they could find out I rooted it? I'm worried they would charge me full price for the phone they sent me if they discover it.
Niviac said:
Tried this, but couldn't get it to work.
Took it to a Verizon store and they said they would send me a new one tomorrow, and then all I do is send mine in afterwards.
Is there a chance that after I send them my phone they could find out I rooted it? I'm worried they would charge me full price for the phone they sent me if they discover it.
Click to expand...
Click to collapse
Honestly the Magnuson-Moss act protects you in that VZW has to prove that rooting caused the phone to fail. However in practice you end up having to take them to court which is too costly and time consuming. But to answer your question yes they could pretty easily figure it out.
But to put it differently no one else that I've read about has had a failure like yours. People have bootlooped and such, but no one has just had nothing happen on power-up. It doesn't sound like you did anything other than root, which couldn't possible cause this. Freezing apps and deleting system apps only causes force closes and bootlooping, you had neither.
Actually, Towelroot may not be related, but oddly enough my phone did a couple of app updates and then Tmobile could tell my phone was rooted. Then it started acting really weird. I got a green LED notification but had none in any apps. The stock keyboard gets really laggy. (1 press per 4 seconds), if you try to long press to move a widget/button or anything, the phone hangs up.
I am almost convinced it is something Tmo is doing. The phone shows in Tmo My Accounts that the phone is rooted.
I tried to unroot (SuperUser is a no-go), I tried downgrading using downgrade methods but I get an error and it shuts down. I don't know where to start now. My phone will be kicked back from Tmo if I try to send it in. I knew one day Root Exploits would catch up with me.
If anyone has a bright idea other than wait till there is a fix, I am all ears.
Brutal-Force said:
Actually, Towelroot may not be related, but oddly enough my phone did a couple of app updates and then Tmobile could tell my phone was rooted. Then it started acting really weird. I got a green LED notification but had none in any apps. The stock keyboard gets really laggy. (1 press per 4 seconds), if you try to long press to move a widget/button or anything, the phone hangs up.
I am almost convinced it is something Tmo is doing. The phone shows in Tmo My Accounts that the phone is rooted.
I tried to unroot (SuperUser is a no-go), I tried downgrading using downgrade methods but I get an error and it shuts down. I don't know where to start now. My phone will be kicked back from Tmo if I try to send it in. I knew one day Root Exploits would catch up with me.
If anyone has a bright idea other than wait till there is a fix, I am all ears.
Click to expand...
Click to collapse
Has nothing to do with rooting your phone. I wasn't rooted for 2 months and it was doing that switch to the g3 keyboard in the g2 thread use the apk installer
D-FUSE said:
Has nothing to do with rooting your phone. I wasn't rooted for 2 months and it was doing that switch to the g3 keyboard in the g2 thread use the apk installer
Click to expand...
Click to collapse
The new android L keyboard in the playstore is really smooth too. No lag, good feel, has emojis if that matters to you. There's a thread in the apps section for the 5.0 keyboard you can manually install and it'll have more skins but the easiest way is to install from the playstore.
Edit: T-mobile keeps track of rooting somehow? How have I never heard that!? Seems like something a Dev or someone would have figured out how to block or what app they're using to spy. That sucks especially in regards to warranty etcetera being denied.
Its not just the Keyboard. I too switched the thumb keyboard which resolves the lagging key-input, but there is also a blinking green led notification that won't go out and I can't answer the phone because touch input (drags and long presses) are buggered.
I have installed TWRP, gonna Try to install a rom and fix it
Hi there!
I was wondering if anyone around here had some ideas on what to do.
My LG G4 had been working fine until today. I unlocked the screen to check my e-mail and it completely froze. It was plugged in at the time, so I unplugged it to see if I could restart it. The charging light was still blinking, the power button didn't respond, absolutely nothing.
I took the battery out, left it for a minute or so and rebooted. It loaded, unlocked, but I could only get to the app menu before it completely froze again. Afterwards, screen went black.
On the third try, it booted up to the LG logo and that's it. It popped up about 3 times and screen went black. No other response whatsoever. I can only try to reboot again only after taking out the battery, but it does the same thing.
I switched the battery with another one of the same model, nothing changed. Computer doesn't recognize it either.
I've looked around for a bit and I can't find anything like my case. The closest thing described is the boot loop. I'm not exactly sure that's my case, but it seems similar to a certain degree.
I got it to boot to recovery mode, but it doesn't do anything. It asks me if I'm sure I want to run it, and in the second 'yes' it freezes up completely again. Screen goes black and does absolutely nothing else.
Added note, phone upgraded to 6.0 yesterday morning. I had no issues with it until now. No app updates were running at freezing time.
I'm considering taking it to the store before I try anything myself, just in case there is still some warranty active.... But any ideas would be greatly appreciated.
sinajei said:
Hi there!
I was wondering if anyone around here had some ideas on what to do.
My LG G4 had been working fine until today. I unlocked the screen to check my e-mail and it completely froze. It was plugged in at the time, so I unplugged it to see if I could restart it. The charging light was still blinking, the power button didn't respond, absolutely nothing.
I took the battery out, left it for a minute or so and rebooted. It loaded, unlocked, but I could only get to the app menu before it completely froze again. Afterwards, screen went black.
On the third try, it booted up to the LG logo and that's it. It popped up about 3 times and screen went black. No other response whatsoever. I can only try to reboot again only after taking out the battery, but it does the same thing.
I switched the battery with another one of the same model, nothing changed. Computer doesn't recognize it either.
I've looked around for a bit and I can't find anything like my case. The closest thing described is the boot loop. I'm not exactly sure that's my case, but it seems similar to a certain degree.
I got it to boot to recovery mode, but it doesn't do anything. It asks me if I'm sure I want to run it, and in the second 'yes' it freezes up completely again. Screen goes black and does absolutely nothing else.
Added note, phone upgraded to 6.0 yesterday morning. I had no issues with it until now. No app updates were running at freezing time.
I'm considering taking it to the store before I try anything myself, just in case there is still some warranty active.... But any ideas would be greatly appreciated.
Click to expand...
Click to collapse
seems like infamous bootloop... harware issue. send it to tmobile or LG.
raptorddd said:
seems like infamous bootloop... harware issue. send it to tmobile or LG.
Click to expand...
Click to collapse
I was afraid so... Went directly to the T-Mobile store where I bought it and, since the warranty was still active, they exchanged it on the spot.
I just hope this one lasts longer than the other one did...
Thanks!
sinajei said:
I was afraid so... Went directly to the T-Mobile store where I bought it and, since the warranty was still active, they exchanged it on the spot.
I just hope this one lasts longer than the other one did...
Thanks!
Click to expand...
Click to collapse
yeah.. did you know manufacture date on the one affected by bootloop or first 3 serial number.?
raptorddd said:
yeah.. did you know manufacture date on the one affected by bootloop or first 3 serial number.?
Click to expand...
Click to collapse
Yup. Actually still have the box.... the date was 05/2015.
New one's date is 03/2016.
sinajei said:
Yup. Actually still have the box.... the date was 05/2015.
New one's date is 03/2016.
Click to expand...
Click to collapse
it was a 505.. most will bootloop... new one is. 603. theres hw 1,0 and 1.1.. this you look at software info ... in hidden menu.. in dialer..
raptorddd said:
it was a 505.. most will bootloop... new one is. 603. theres hw 1,0 and 1.1.. this you look at software info ... in hidden menu.. in dialer..
Click to expand...
Click to collapse
This one (603) is a HW Version 1.0 ...
sinajei said:
This one (603) is a HW Version 1.0 ...
Click to expand...
Click to collapse
mines its 601 and same HW 1.0 if they knew they revised 1.0 to 1.1 why not use the 1.1 if they knew this back in october 2015.. theres older phone from 2015 with HW 1.1
raptorddd said:
mines its 601 and same HW 1.0 if they knew they revised 1.0 to 1.1 why not use the 1.1 if they knew this back in october 2015.. theres older phone from 2015 with HW 1.1
Click to expand...
Click to collapse
That is an excellent question...
Btw, does your screen freeze up sometimes? 'Cause mine sometimes goes unresponsive right after I unlock it... I just lock and unlock it again and keeps working just fine, but it's kind of annoying... old one did it and it, now this one does it sometimes too...
sinajei said:
That is an excellent question...
Btw, does your screen freeze up sometimes? 'Cause mine sometimes goes unresponsive right after I unlock it... I just lock and unlock it again and keeps working just fine, but it's kind of annoying... old one did it and it, now this one does it sometimes too...
Click to expand...
Click to collapse
yes it does.. but very rare... not to often... but mines does using phone and it freezes then turn off screen and when back it all works... i used power button.. not sure why but it does..but liek i said not to often. its once in a while..
raptorddd said:
yes it does.. but very rare... not to often... but mines does using phone and it freezes then turn off screen and when back it all works... i used power button.. not sure why but it does..but liek i said not to often. its once in a while..
Click to expand...
Click to collapse
Good to know it's not just me then. Guess it's a common screen glitch then.
Thank you for the info!
Well another 505 g4 bites the dust. Playing a game, backed out of it, phone froze, pulled battery, turned on to endless bootloop, pulled battery again, now nothing and I mean nothing, no boot loop, no nothing
Definitely a brick. Computer doesn't recognize or even try to charge it. Hopefully still under warranty.
Sent from my LG-VS980 using Tapatalk