Database Develop

G1 big problems

Hay i have a rooted G1 with Jf - can't rember what version.
I've been having lots of problems with force closing of various programs but otherwise everything was going fine.
After a few force closes today i decided to restart my phone, turned it off and then back on and stuck it in my pocket.
When i went to check my texts 5 minuets later i took it out and it was just stilling on the 'Android' splash screen - it was moving then freezing for a few seconds then moving (i don't know if that's normal but it wouldnt surprise me).
I took the battery out and restated again and exactly the same thing - it would not boot.
I did a quick search on the problem and remembered how to boot in camera+red mode - which the phone did fine. I then read that pushing green+menu+red would fix it.
I did this and the phone booted, but it lost all my home screen icons and was laid out like when the phone was bought. i then cheked an app or two and they are all still there and seem to have retained their data.
However other strange things are happening - the home button dosnt work, nether does the green, when i hold the red button i only get the 'power off' option not 'power off, silent and airplane' as i used to.
They are the problems i have found so far but there may be more. Basically i want to know what pushing green, menu, red actually does and i want to know what the hell is going on - im totally lost.
Please help
P.S. i did a test on the consol and it seems i still have root assess - just encase that relative

Go to recovery, wipe and reflash. It will solve all your issues.

I can't actually remember how to do that - can you explain more or link me?
and will it have any effect on my apps or settings?

Zippokovich said:
I can't actually remember how to do that - can you explain more or link me?
and will it have any effect on my apps or settings?
Click to expand...
Click to collapse
You're going to need to go into recovery; press the home screen button, then the red (energize, end call, whatever) button. Hold both down until you get into recovery, which will be the text menu with all the selections available in green. Then scroll down to "wipe data/ factory reset" and do that- this simply wipes the phones internal memory. Then load the rom you are using, which I assume is already on the root of your sd card. If not, connect the phone, mount the card, and put the rom there before you get started with the above steps- chris

[Q] Samsung Galaxy S GT-I9000 won't work if not plugged on external power source

Hi guys,
The following problem has taken me litterally DAYS of reading XDA, trying everything I could, but still no solution. Googling and searching this forum didn't help either, and it's totally weird.
It's a Samsung Galaxy S GT-I9000, on which were installed, almost two years ago, the ClockWorkMod recovery, Darky's ROM, Froyo, and everything was fine for months. Then, one day, out of nowhere, it switched off, without notice. Impossible to switch it on again! I remembered having seen some strange battery behavior few days before, like falling from 80% to 30% with no reason, so I thought of a battery issue. I plugged it for a full night. In the morning, I was able to boot it, but not easily, and all apps were crashing: during boot, or when launched manually. Yes, all I tried were crashing! Then, the phone became fully not bootable: press the power button, the screen shows "Samsung GT-I9000", then switches off...
I ordered a new battery: same result.
A guy from a phone repair store told me to plug the phone, and keep the power button down for 2 minutes: after this, I could reboot the phone, and thus, wipe data (factory reset). But it didn't help.
After "playing" a bit with it, I realized that the problem is:
the phone won't boot if an external source of power is not connected (as said above, white text shows, then the phone "dies")
if started with power cord/usb, the phone will work fine, all the time
if started with power cord/usb, and the external power source removed once the phone is booted, the phone will work fine, UNTIL the screen goes black for power saving mode or by pressing pwoer button, after which, within seconds, you can't open the phone anymore. I mean: if you press the start/power button immediately after the screen goes black, the screen goes on again, and the phone is ok. If you wait for few seconds, it's over, you can't do anything, and have to reboot the phone. This said, the phone doesn't vibrate, so I suppose it's not really off. But then... what is this state??
I really tried my best: updated to GB2.3.6, bricked my phone trying to re-install the CWM and having a bootloop, installed and used Odin and Heimdall, reverted to stock kernel, etc, etc, etc.
I feel sorry to bother you guys, I was really convinced that with the incredibly huge amount of data, how-tos, explanations, etc. I would manage to get rid of this, but this problem, though I don't really think it's hardware (but maybe it is?) stayed across so many kernels, roms, etc. that it's killing me!
For the record:
Model number: GT-I9000
Micro-software (?): 2.3.6
Baseband: I9000XXJW4
Kernel: 2.6.35.7-I9000XWJW7-CL1125830 [email protected] #2 (problem was the same with [email protected] #2)
Version number: GINGERBREAD.XXJW4
Any help would be greatly appreciated, considering that a wireless phone that needs to be wired is a little bit of an issue... :laugh:
Thanks in advance !

Marc_B_ said:
Hi guys,
The following problem has taken me litterally DAYS of reading XDA, trying everything I could, but still no solution. Googling and searching this forum didn't help either, and it's totally weird.
It's a Samsung Galaxy S GT-I9000, on which were installed, almost two years ago, the ClockWorkMod recovery, Darky's ROM, Froyo, and everything was fine for months. Then, one day, out of nowhere, it switched off, without notice. Impossible to switch it on again! I remembered having seen some strange battery behavior few days before, like falling from 80% to 30% with no reason, so I thought of a battery issue. I plugged it for a full night. In the morning, I was able to boot it, but not easily, and all apps were crashing: during boot, or when launched manually. Yes, all I tried were crashing! Then, the phone became fully not bootable: press the power button, the screen shows "Samsung GT-I9000", then switches off...
I ordered a new battery: same result.
A guy from a phone repair store told me to plug the phone, and keep the power button down for 2 minutes: after this, I could reboot the phone, and thus, wipe data (factory reset). But it didn't help.
After "playing" a bit with it, I realized that the problem is:
the phone won't boot if an external source of power is not connected (as said above, white text shows, then the phone "dies")
if started with power cord/usb, the phone will work fine, all the time
if started with power cord/usb, and the external power source removed once the phone is booted, the phone will work fine, UNTIL the screen goes black for power saving mode or by pressing pwoer button, after which, within seconds, you can't open the phone anymore. I mean: if you press the start/power button immediately after the screen goes black, the screen goes on again, and the phone is ok. If you wait for few seconds, it's over, you can't do anything, and have to reboot the phone. This said, the phone doesn't vibrate, so I suppose it's not really off. But then... what is this state??
I really tried my best: updated to GB2.3.6, bricked my phone trying to re-install the CWM and having a bootloop, installed and used Odin and Heimdall, reverted to stock kernel, etc, etc, etc.
I feel sorry to bother you guys, I was really convinced that with the incredibly huge amount of data, how-tos, explanations, etc. I would manage to get rid of this, but this problem, though I don't really think it's hardware (but maybe it is?) stayed across so many kernels, roms, etc. that it's killing me!
For the record:
Model number: GT-I9000
Micro-software (?): 2.3.6
Baseband: I9000XXJW4
Kernel: 2.6.35.7-I9000XWJW7-CL1125830 [email protected] #2 (problem was the same with [email protected] #2)
Version number: GINGERBREAD.XXJW4
Any help would be greatly appreciated, considering that a wireless phone that needs to be wired is a little bit of an issue... :laugh:
Thanks in advance !
Click to expand...
Click to collapse
That's a very strange problem... let's try something, remove the battery, sim card and sd card and hold the power button for 1-2 minutes, btw when the screen is off, is really the phone off or just the screen? did you try to make a call to your phone when the screen is off?

timberman4444 said:
That's a very strange problem... let's try something, remove the battery, sim card and sd card and hold the power button for 1-2 minutes, btw when the screen is off, is really the phone off or just the screen? did you try to make a call to your phone when the screen is off?
Click to expand...
Click to collapse
Hi timberman thanks for the answer!
You're very right: I totally forgot to say that what initially allowed me to restart my phone "regularly" was this procedure of pressing the power button for 2 minutes (hint given by a man from a repair shop). Before this, I couldn't (kind of a bootloop).
It's a very good question! I don't think the phone is really off in fact, because there isn't this vibration saying the phone turned off... Let me try to call it!
F..k! I was redirected right away to the voicemail... so... phone was off
I'm starting to think it's an harware issue... I reinstalled lots of ROMs, kernel, etc. Same ****...
Any idea?

Marc_B_ said:
Hi timberman thanks for the answer!
You're very right: I totally forgot to say that what initially allowed me to restart my phone "regularly" was this procedure of pressing the power button for 2 minutes (hint given by a man from a repair shop). Before this, I couldn't (kind of a bootloop).
It's a very good question! I don't think the phone is really off in fact, because there isn't this vibration saying the phone turned off... Let me try to call it!
F..k! I was redirected right away to the voicemail... so... phone was off
I'm starting to think it's an harware issue... I reinstalled lots of ROMs, kernel, etc. Same ****...
Any idea?
Click to expand...
Click to collapse
Hi mark, i'm totally out of ideas for your problem... anyway, maybe you read mi answer wrong, in your post you say that the guy in the repair shop tell yo to press the power button with THE PHONE PLUGGED IN, but what i say is press the power button 2 minutes WITHOUT BATTERY, btw i keep thinking about this.. if any idea comes to my mind i tell you.

Hi again, try to play a song and turn the screen off to see what happens.
Sent from my GT-I9000 using xda app-developers app

timberman4444 said:
Hi mark, i'm totally out of ideas for your problem... anyway, maybe you read mi answer wrong, in your post you say that the guy in the repair shop tell yo to press the power button with THE PHONE PLUGGED IN, but what i say is press the power button 2 minutes WITHOUT BATTERY, btw i keep thinking about this.. if any idea comes to my mind i tell you.
Click to expand...
Click to collapse
Hi! Answering is already nice
I tried the button pressed for 2 minutes without battery: didn't change anything.
I tried playing a sound: MAN, YOU'RE A GENIUS!!! Launching the music, then forcing the screen off with power button lets the music play, and OF COURSE, I can reactivate the screen by pressing the home button. The screen goes off normally again after few seconds, but the music is still playing, etc. So, as long as the music goes, the bug doesn't happen!
Other hints:
For some time already, when I was removing the phone from my ear after a call, quite often, the screen was staying off, and I had to press a lot of buttons to have it on again, and be able to close the call
The moment where it crashes when booting without power is the very INSTANT where the initial white text (Samsung Galaxy S) goes brighter. So, if you unplug the power cord just after this, the boot ends normally. In summary, something happens at boot just after screen brightness changes which is the same thing happening when the screen goes off for power saving. All this, only when no external power is plugged.
Hehe, we (you) are making progress

Marc_B_ said:
Hi! Answering is already nice
I tried the button pressed for 2 minutes without battery: didn't change anything.
I tried playing a sound: MAN, YOU'RE A GENIUS!!! Launching the music, then forcing the screen off with power button lets the music play, and OF COURSE, I can reactivate the screen by pressing the home button. The screen goes off normally again after few seconds, but the music is still playing, etc. So, as long as the music goes, the bug doesn't happen!
Other hints:
For some time already, when I was removing the phone from my ear after a call, quite often, the screen was staying off, and I had to press a lot of buttons to have it on again, and be able to close the call
The moment where it crashes when booting without power is the very INSTANT where the initial white text (Samsung Galaxy S) goes brighter. So, if you unplug the power cord just after this, the boot ends normally. In summary, something happens at boot just after screen brightness changes which is the same thing happening when the screen goes off for power saving. All this, only when no external power is plugged.
Hehe, we (you) are making progress
Click to expand...
Click to collapse
Hi again, it seems like your phone is unable to exit the deep sleep mode or something like that so, let`s try another thing, in ICS or JB there´s an option in the developer option settings that unfortunately is not present in gingerbread roms, so, you can try to switch to a ICS/JB rom and go to settings-developer options and disable the "PM sleep mode" let`s see what happens then

timberman4444 said:
Hi again, it seems like your phone is unable to exit the deep sleep mode or something like that so, let`s try another thing, in ICS or JB there´s an option in the developer option settings that unfortunately is not present in gingerbread roms, so, you can try to switch to a ICS/JB rom and go to settings-developer options and disable the "PM sleep mode" let`s see what happens then
Click to expand...
Click to collapse
I tried to install ICS, with a GREAT tutorial found here: http://forum.xda-developers.com/showthread.php?t=1494493 Sadly, the phone reboots after installing the ICS kernel, and then doesn't work anymore, I had to reinstall the Gingerbread (I tried twice).
Last news: I let the phone play music (sound muted!!) for about 12 or 18h: all was fine! So I decided to pause the music, and see what happens. Boom ((c) Steve Jobs)!! The screen went black, and phone was "dead". I was expecting this, so no panick, I put back my SIM card, my SD card, and tried to reboot, with power cord plugged: it boots until the screen shows the small loader animation, then the empty battery image, but then goes black again, instead of showing the charging battery!! Download mode is still available, so I'll try to reflash the kernel, say.
It's like if each time screen was put black, phone was dying.
I can't stress enough how I appreciate your help: even if we can't save my phone, it's very pleasant to be able to TRY things. Thanks man!! :good:
Update: I reinstalled all... and it's not, even with power cord in, going further than the "Samsung Galaxy S" white text. The moment this picture disappears from screen, phone is dead. For good this time ?

Marc_B_ said:
I tried to install ICS, with a GREAT tutorial found here: http://forum.xda-developers.com/showthread.php?t=1494493 Sadly, the phone reboots after installing the ICS kernel, and then doesn't work anymore, I had to reinstall the Gingerbread (I tried twice).
Last news: I let the phone play music (sound muted!!) for about 12 or 18h: all was fine! So I decided to pause the music, and see what happens. Boom ((c) Steve Jobs)!! The screen went black, and phone was "dead". I was expecting this, so no panick, I put back my SIM card, my SD card, and tried to reboot, with power cord plugged: it boots until the screen shows the small loader animation, then the empty battery image, but then goes black again, instead of showing the charging battery!! Download mode is still available, so I'll try to reflash the kernel, say.
It's like if each time screen was put black, phone was dying.
I can't stress enough how I appreciate your help: even if we can't save my phone, it's very pleasant to be able to TRY things. Thanks man!! :good:
Update: I reinstalled all... and it's not, even with power cord in, going further than the "Samsung Galaxy S" white text. The moment this picture disappears from screen, phone is dead. For good this time ?
Click to expand...
Click to collapse
you tried to install the rom on the recovery instead of odin?

timberman4444 said:
you tried to install the rom on the recovery instead of odin?
Click to expand...
Click to collapse
Hi! No, I didn't, I used Odin. But now, I can't try anything anymore The only "results" I can get from this phone are:
- enter download mode and update from Odin (maybe from Heimdall, too, but I didn't check)
- reboot until the first moment the screen goes black, after which, the phone becomes fully unresponsive

Marc_B_ said:
Hi! No, I didn't, I used Odin. But now, I can't try anything anymore The only "results" I can get from this phone are:
- enter download mode and update from Odin (maybe from Heimdall, too, but I didn't check)
- reboot until the first moment the screen goes black, after which, the phone becomes fully unresponsive
Click to expand...
Click to collapse
so, you can`t install any rom at the moment?

timberman4444 said:
so, you can`t install any rom at the moment?
Click to expand...
Click to collapse
I can! I can install any kernel, or ROM, trhough Odin, but I can't boot at all... Except if someone has a magical trick, I would say it smells like coffin...

Marc_B_ said:
I can! I can install any kernel, or ROM, trhough Odin, but I can't boot at all... Except if someone has a magical trick, I would say it smells like coffin...
Click to expand...
Click to collapse
Pretty bad signals there.. i think you should go to a repair shop or buy another device

timberman4444 said:
Pretty bad signals there.. i think you should go to a repair shop or buy another device
Click to expand...
Click to collapse
Sadly, yes... thanks for helping however !

Pure 5.1: Boots, has moto display, but black screen when I unlock

So currently I can boot my phone and it displays the boot screen fine. Once its done loading though I just have black screen. Moto display still works and shows new notifications but if I try to unlock the phone its still just the black screen. I can hold down the power button and the power menu shows up fine. I tried clearing the cache but that didn't help. Before I do a factory reset I thought I might see if any one here had some ideas on solutions.
I have the latest 5.1 OTA update. My phone us unlocked, but not rooted. I tried to hook it up to my computer to see if I could at least grab my files off of it, but while it shows up on my computer I can't access any actual files or directories.
I've tried searching around, but I can't find anyone else with a similar issue. Last night my phone battery ran down to zero (and rather quickly compared to normal usage). I may have ****ed it up by trying to get it to boot and be usable while charging but with the battery only at 1% (I guess with the standard charger an in-use Moto X uses power faster than it can take it from the charger). I tried letting it charge for a few minutes and then letting it boot, but after a couple of minutes of use it would shut down again. I finally gave up and let it charge. I didn't really pay attention to its status, but in the middle of the night when I woke up I booted it before falling back to sleep. Not sure there's a connection to my issue and this or not.
Any ideas on what the cause might be or what I can try to do to remedy the issue without data loss?
Edit: I ended up just doing a factory reset and that worked. Admin can feel free to delete this thread if they want.

This sounds similar to the issue here:
http://forum.xda-developers.com/mot...-screen-to-recover-data-t3168103#post62117413
http://forum.xda-developers.com/moto-x-2014/help/black-screen-boot-t3161110
https://www.reddit.com/r/MotoX/comments/3cf4gr/51_black_screen_after_turning_on/
https://www.reddit.com/r/MotoX/comments/3aqr95/moto_x_2nd_gen_black_screen_after_update/
https://www.reddit.com/r/MotoX/comments/383ej6/black_screen_on_startup/
This is a bug that needs to be reported to Motorola.

I am that guy from the second post, and I wasn't able to recover the phone. Connecting to PC did not do anything. I would like to ask: is it booting with the new boot animation? Or old one? Because mine showed old animation long after the update was sent out, so I'm thinking the update may have tried to apply and failed, thus breaking the phone. Should all efforts fail, your only bet is to boot into recovery (power + volume up when off, volume down, volume up in the option menu (to select recovery), then hold power when Android robot appears, and while holding it down, press the vol up button once to make the list of recovery options appear. Scroll down to wipe data/factory reset, press power to select, then find Yes to confirm. Good luck!

so this just happened
i came back from a trip and took a whoooole lot of photos. when i came back my battery went to zero and device switched off. i charged the phone to 10-20% and switched it on and all i see is blank screen only moto display is working and power off option is showing itself when i hold the power button which is the same problem as yours
havent done any factory reset yet. is there any way to retreive the photos since i dont want to lose them. there are around 600 and all of them are of the trip.
im on 5.1
there are other people too who faced the same problem and all of them are on 5.1 but there is no solution
link :-
https://www.reddit.com/r/MotoX/comme..._after_update/

Mine did this yesterday, although I'm not entirely certain that the battery hit zero percent. The best I could tell from looking through the logs in recovery was that something was trying to update and failed. I suspect that it was a push from Motorola that hosed it. The only way to fix it is to do a factory reset. Once I did that and restored all my apps the battery was draining at a rate of 40% per hour or so. I found that the package access helper was the culprit and rebooted the phone. Post reboot, I immediately noticed that the boot animation and Moto logo had changed from what they had been on 5.0/5.1 (prior to yesterday). I also noticed that some of the widgets I hadn't reconfigured after the reset were now back. Weird indeed.
Anyway, I have to agree with the others that this is a very bad bug, that needs to be fixed. I am cautiously optimistic that the factory reset has cured it but we'll see. Based on my experience with this phone so far and the sale of Moto to Lenovo, this will be my last Moto phone.

I am having the exact same issue. Has anybody had a luck resolving it short of a factory reset?
My phone battery died last night. I plugged my phone in, let it get about 15% charge, then tried to turn it back on. The phone boots like normal, but after the boot animation goes away, the screen is black. Active notifications still seem to work, and I can hold the power button to get the Power Down option. I can boot into the bootloader & access recovery just fine. However, my phone is fully stock (no root, no bootloader unlock, no anything). I can't seem to access ADB when the phone is powered normally (ie, when I'm at this mysterious black screen), but it's possible that USB debugging isn't even enabled.
So far, I've found a bunch people who've said a full factory reset will fix the problem, but I'm looking for another solution, or at least a way to grab my data before I reset. Since my bootloader's still locked, I can't seem to use fastboot boot to boot into TWRP, and I can't find any other way to access my data to copy it off the phone. I've tried wiping the cache using the stock recovery to no avail. Any suggestions?

Spontaneously soft restarting

Today, my phone has been soft restarting without warning. It'll be going along happily, and then the Sprint splash screen will pop up, and ten it'll load the OS and all that nonsense. It's annoying. How do I begin to troubleshoot this? Full disclosure: I've got the systemless root and the Xposed framework. And I've got charging issues. It charges very slowly and doesn't like its original HTC charger anymore. I tried the recallibrate trick — hold down power, vol+, and vol- for 2 minutes — and it reset a bunch of my programs and settings, and created this soft reboot problem. So it's a mess. But can I fix this one thing at least?
It did it super frequently earlier. It's doing it less and less now, but has not stopped all together to my knowledge. Will it go away on its own? I'd feel better if I knew what to do if and when it comes back.

My Motorola Droid Turbo is ****ting itself and I'm not sure why...

I originally posted this on I don't get to post links, so I can't link you to the reddit post. You can search my username on reddit if you're super-curious.
Since that posting, I let my phone sit, off, for the entire night. Turned it back on, and continue to experience similar issues.
In summary, the issue is as follows: After booting up the phone, I have roughly 2-4 minutes of "uptime" before Apps start freezing, failing to respond. This includes the SysUI app. If I jam the "home" or "tab" button on the bottom of the phone enough times, I am sometimes given an "x app is failing to respond, kill it?: Wait; OK"
If I choose to wait, it doesn't get better. If I choose to kill any of the apps, not just SysUI, the screen goes black, but the phone is still on. Sometimes I can power cycle it with the "Power Off" screen button, sometimes I have to do a hard reboot.
I tried installing Phone Doctor as one reddit user had recommended. It froze before I could see much, but I did notice the CPU was running at 97% which seems abnormally high.

Have you factory reset?
My kids HTC corrupts some system app data randomly every few months and I have to either painfully start cleaning the multiple offending apps cache or just factory reset.
No idea if this is a sign of failing as card or if it is just some app citing multiple apps data.