Database Develop

HELP!!! G1 acting weird.

Sometimes my phone goes into like suspend mode where the screen times out, and I can not wake it up. I press every button nothing happens. If I hold the power button it does not come on. I have to take the battery out and turn the power back on. What is this? Its very annoying.

Post some spec. Are you rooted? If so, what rom are you on? Does it do it on specific roms or on all? Just need some more info to help.

Radio: 2.22.19.26I
SPL: 1.33.2005
ROM: Cyanogen 3.9.10
the phone is rooted

Well I just got this phone and I went straight to this rom, didnt try any other rom on this phone. So I can only say it happens on this rom only.

Have you tried any other roms to see if it would do it? Have you tried it on the stock facotry rom? If the problem still exist on all roms then it will be a hardware problem and need to be sent off.

I ran the stock rom for only about 15 mins lol. The problem never occurred. Im thinking its the rom, but I haven't anyone else complain about this issue. I guess I try some different roms if the issues continue.

mikesx4911 said:
I ran the stock rom for only about 15 mins lol. The problem never occurred. Im thinking its the rom, but I haven't anyone else complain about this issue. I guess I try some different roms if the issues continue.
Click to expand...
Click to collapse
There have been some people that had this issue and either it was rom related or hardware related. So I would try another rom and see if it does it, if it does then try the stock and if it still happens then you know you might need to get a new phone. But the phone is still under a year old so it will be covered under warranty.

This is a common problem referred to as a phone coma, which happens on some Cyanogen builds. Update to the latest stable build and you will be fine.

[Q] Bricked Milestone, stuck at Motorola logo

Hi,
I managed to brick my Milestone, terminally I'm afraid, but the symptoms are different than what I see around the forum so they might interest someone else.
So, I first backed up everything with GOT Nandroid and Titanium Backup then modded CyanogenMod 7 RC4 0.08-11.04.05 (Android 2.3.3) successfully, except that the SIM was locked and would not unlock, although it works in another phone. This was a bug supposedly fixed in version 6 of Cyanogen...
Browsing the forums, the only thing that made a bit of sense was that maybe the GSM frequency was set to the wrong value. There is a Nandroid mod (but not GOT) that allows you to change that so I entered GOT Nandroid again. Since it had no such option, I Rebooted. Then, the fun begun.
The phone got stuck on the Motorola logo and no button, not even Power, worked anymore. After waiting for many minutes with no progress, I took out the battery - that made a change , the phone shut down. I then put it back - the phone immediatelly, no, instantly, cause there's no delay as when you were powering it up, lights up with the same Motorola logo. Tried several times, always the same behavior.
I left it booting (but also connected to the charger) for a whole night, no change.
The phone is not seen by the PC when connected to USB. It won't reboot, normally or to recovery. Buttons won't work at all. Yeah, tried with or without the SIM and the sdcard, no change. Tried to start without battery, just the charger, doesn't work.
Useless to say, I am getting bored of that Motorola logo
I suspect that the bootloader in the internal memory got corrupted. Can this be flashed even if the device is not seen by the PC (I mean by the RDSLite installed on it)?
Cheers

When the charger is connected to the phone try at the same timeull out and pull in the battery while holding the buttons who will get you in the OR

Yup, it worked. So first I got the battery with a question mark. Then I put in the battery and I got a battery at 60%. Since I was holding Power+Camera, it continued to the Recovery mode and now I have a working Milestone with Cyanogen mod!!
Thank you a lot, Mikicishte.
I still have to see about the initial locked SIM problem... but that will be mostly fun.

florinadrian said:
I still have to see about the initial locked SIM problem... but that will be mostly fun.
Click to expand...
Click to collapse
Have you tried to factory reset the Milestone, to see if after that the SIM is accessible again ?
http://forum.cyanogenmod.com/topic/14099-sim-card-not-detected-after-factory-reset/
You could try also to install a logger application catlog for example (https://market.android.com/details?id=com.nolanlawson.logcat&feature=search_result ) to see in the logs if you can find out more details to help you with the investigations...

I did the factory reset as part of installing the mod.
Even if the post quoted reports the wipe as the source of the problem and not as a solution, I just wiped again with no good result.
Will try catlog.

florinadrian said:
I did the factory reset as part of installing the mod.
Even if the post quoted reports the wipe as the source of the problem and not as a solution, I just wiped again with no good result.
Will try catlog.
Click to expand...
Click to collapse
or maybe you could try to use an unlock tool to see what error is reporting
https://market.android.com/details?id=com.droidgram.bladeunlock&feature=search_result

Boot loop after CM7 & Baseband 15

Hi Guys,
I had a reboot loop problem in my X8 after installing Viber from a Wifi connection and decided to mod it. I successfully unlocked the boot loader & rooted my Xperia X8. Flashed it with CM7 RC1 V4. I rebooted the phone to see the Cyanogen Mod screen with the skate board and it proceeded to ask me a question about the setup wizard or market option, I made a selection and the phone went dead. It rebooted and started hanging on the SE logo. I thought it was due to Baseband 15 and flashed it but no luck.
I have Clockwork Mod on it and can randomly enter it also. I would appreciate any help and pointers, is this an issue due to using the wifi and is the hardware at fault. Once the boot loop starts the battery drains pretty fast I can see the Cyanogen battery status icon and try to wait for it to charge completely
Many thanks & regards

bytecodeboy said:
Hi Guys,
I had a reboot loop problem in my X8 after installing Viber from a Wifi connection and decided to mod it. I successfully unlocked the boot loader & rooted my Xperia X8. Flashed it with CM7 RC1 V4. I rebooted the phone to see the Cyanogen Mod screen with the skate board and it proceeded to ask me a question about the setup wizard or market option, I made a selection and the phone went dead. It rebooted and started hanging on the SE logo. I thought it was due to Baseband 15 and flashed it but no luck.
I have Clockwork Mod on it and can randomly enter it also. I would appreciate any help and pointers, is this an issue due to using the wifi and is the hardware at fault. Once the boot loop starts the battery drains pretty fast I can see the Cyanogen battery status icon and try to wait for it to charge completely
Many thanks & regards
Click to expand...
Click to collapse
* Did you factory reset it from CWM before installing the ROM? Boot loops are common when one doesn't, particularly if you're coming from another ROM (from what you say, I guess you're coming from stock 2.1)
* It seems that you flashed baseband 015 AFTER flashing the new ROM. AFAIK it should be done BEFORE flashing a new ROM, while still on stock 2.1. If that's the case, you'd have to go back to 2.1 using SEUS (or Flashtool; there are stock ROM images here on XDA), THEN flash baseband 015, THEN root, THEN flash CM7 again.
---
As a side note, you unlocked your bootloader but didn't install a new kernel, which is what one normally unlocks the bootloader for. Unlocking the bootloader isn't needed to flash a ROM as long as it works with the stock kernel (most don't, but yours should.)

Mod issue or battery or hardware fault
Cheshire-Cat said:
* Did you factory reset it from CWM before installing the ROM? Boot loops are common when one doesn't, particularly if you're coming from another ROM (from what you say, I guess you're coming from stock 2.1)
* It seems that you flashed baseband 015 AFTER flashing the new ROM. AFAIK it should be done BEFORE flashing a new ROM, while still on stock 2.1. If that's the case, you'd have to go back to 2.1 using SEUS (or Flashtool; there are stock ROM images here on XDA), THEN flash baseband 015, THEN root, THEN flash CM7 again.
---
As a side note, you unlocked your bootloader but didn't install a new kernel, which is what one normally unlocks the bootloader for. Unlocking the bootloader isn't needed to flash a ROM as long as it works with the stock kernel (most don't, but yours should.)
Click to expand...
Click to collapse
Many thnks for the reply mate, what you said is right. I might have missed a few things. But I reflashed Baseband 15 yesterday before your reply to my post and now it seems to be booting into cyanogen mod happily but each time it takes only a few seconds and through a few setup screens before it reboots again.This is exactly what was happening even on the stock ROM before doing any Mod procedure and the battery gets drained too. Could this be a hardware fault.

bytecodeboy said:
Many thnks for the reply mate, what you said is right. I might have missed a few things. But I reflashed Baseband 15 yesterday before your reply to my post and now it seems to be booting into cyanogen mod happily but each time it takes only a few seconds and through a few setup screens before it reboots again.This is exactly what was happening even on the stock ROM before doing any Mod procedure and the battery gets drained too. Could this be a hardware fault.
Click to expand...
Click to collapse
i didnt get it, when on setup screen you mean when it tells to add your email.....and when you are finished it reboots?!
if i understood well,there is no hardware problem, go to cwm, full wipe-factory reset,advanced>wipe dalvik, reinstall your rom(install custom zip) and it should work:fingers-crossed:

stamatis16 said:
i didnt get it, when on setup screen you mean when it tells to add your email.....and when you are finished it reboots?!
if i understood well,there is no hardware problem, go to cwm, full wipe-factory reset,advanced>wipe dalvik, reinstall your rom(install custom zip) and it should work:fingers-crossed:
Click to expand...
Click to collapse
Thanks for the reply stamatis, basically its just shutting down because there is no battery left to power it, it seems. At times it reaches upto the setup wizard (shown when booting for the first time), the next time it could go up to adding a gmail account or language selection screen. I have even seen it load the home screen before it shuts off. This all started happening after downloading some apps from a wifi connection. I have done that before wiping and re installing but will try again. My presumption is that since it was happening on stock ROM and now on CM7 too then it's probably a hardware issue
Regards

bytecodeboy said:
Thanks for the reply stamatis, basically its just shutting down because there is no battery left to power it, it seems. At times it reaches upto the setup wizard (shown when booting for the first time), the next time it could go up to adding a gmail account or language selection screen. I have even seen it load the home screen before it shuts off. This all started happening after downloading some apps from a wifi connection. I have done that before wiping and re installing but will try again. My presumption is that since it was happening on stock ROM and now on CM7 too then it's probably a hardware issue
Regards
Click to expand...
Click to collapse
ok i see now,your problem is battery drain,
is it that extream? i mean, you charge to full and when you open it up it shut down by low battery?
have you try to opening while charging?is it the same?
are you sure its charging?
that way too xtream to be software problem so its more likely that its hardware...

stamatis16 said:
ok i see now,your problem is battery drain,
is it that extream? i mean, you charge to full and when you open it up it shut down by low battery?
have you try to opening while charging?is it the same?
are you sure its charging?
that way too xtream to be software problem so its more likely that its hardware...
Click to expand...
Click to collapse
yes you got it right. I do charge it fully and when it boots the CM7 UI for a few seconds the battery goes down half or even less or nearly empty. I have tried opening it while charging and thats when the above happens, yes I can see the Cyanogen charging icon. So you think its a hardware issue and I should not pursue it further

bytecodeboy said:
yes you got it right. I do charge it fully and when it boots the CM7 UI for a few seconds the battery goes down half or even less or nearly empty. I have tried opening it while charging and thats when the above happens, yes I can see the Cyanogen charging icon. So you think its a hardware issue and I should not pursue it further
Click to expand...
Click to collapse
yea, i guess your battery almost dead.....and i dont think its a good idea to by new battery, you better buy new phone,as the batteries are quite expensive if you think that the worth of the x8 right now would be 50 euros....

Try ebay bro
Sent from my E15i using Tapatalk 2

Flash rom with xrecovery not cwm
Sent from my X8 using xda premium

[Q] Captivate power issue download mode unless charging.

Hello. I have been reading on these forums for a while now. I always go here to find out information about smartphones. I have had this captivate for quite some time now. Probably about 2 years. When I was first given the phone it wouldn't do anything but go into download mode and my friend just gave me the phone because he actually had 2 broken ones and i was able to make a completely working captivate from the pieces from the 2. but the other would go straight to download mode if i hit the power button. the guy gave me the one that was constantly in download mode for fixing his other phone. This phone also had an lcd problem untill i came across a captivate that someone had torn the power connectors off so i used the lcd from that phone and put it on the captivate that was constantly in download mode. i plugged it into the charger and it shows a loading screen alot like what an iphone shows when it is loading. and after long enough it would show a battery partially charged. at this point i can push the power button and it powered on and went into safe mode. so I factory reset it and it still has the same problem. i have even formated the internal storage and tried many different roms. the first i tried was serendipity VII it was a great gingerbread rom but it also had the problem. i later flashed cm9 and icyglitch kernel. icy glitch is amazing however ics is old now. in ics the download mode problem still exists. Now the real problem to all of this that makes me think it is a hardware problem is i have recently tried about every jellybean rom with the combination of demon and semaphore and semaphore unofficial kernel and they also have this problem. however there is another problem with any of the jellybean roms i try. they will all work perfectly. i just have to install them 2 times. first install installs semaphore kernel andsays it needs to repartition. i guess cause its coming from icy glitch kernel. then it restarts into the semaphore cwm and then i reinstall jellybean rom and reboot and the phone just laggs unbelievable unless plugged into the charger. i mean the booot animation will move like 1 frame every 10 seconds. i have tried changing the voltage and overclocking it once it starts up. everything works perfectly until the second i unlug the charger then it does the extreeeeem lagg. From my experiences with this phone i would have to say that it is the power management ic on the logicboard. My question is what do you guys think i should do. i am back on icyglitch kernel and the outdated slim ics. i would really like to get jelly bean working and i would also like to be able to boot my phone with out a charger and an electric outlet.
sorry for such a long post i just thought that some of this information could give someone on here an idea of what is wrong with my phone.
Thanks for any help you guys can give.

anarchybob6 said:
Hello. I have been reading on these forums for a while now. I always go here to find out information about smartphones. I have had this captivate for quite some time now. Probably about 2 years. When I was first given the phone it wouldn't do anything but go into download mode and my friend just gave me the phone because he actually had 2 broken ones and i was able to make a completely working captivate from the pieces from the 2. but the other would go straight to download mode if i hit the power button. the guy gave me the one that was constantly in download mode for fixing his other phone. This phone also had an lcd problem untill i came across a captivate that someone had torn the power connectors off so i used the lcd from that phone and put it on the captivate that was constantly in download mode. i plugged it into the charger and it shows a loading screen alot like what an iphone shows when it is loading. and after long enough it would show a battery partially charged. at this point i can push the power button and it powered on and went into safe mode. so I factory reset it and it still has the same problem. i have even formated the internal storage and tried many different roms. the first i tried was serendipity VII it was a great gingerbread rom but it also had the problem. i later flashed cm9 and icyglitch kernel. icy glitch is amazing however ics is old now. in ics the download mode problem still exists. Now the real problem to all of this that makes me think it is a hardware problem is i have recently tried about every jellybean rom with the combination of demon and semaphore and semaphore unofficial kernel and they also have this problem. however there is another problem with any of the jellybean roms i try. they will all work perfectly. i just have to install them 2 times. first install installs semaphore kernel andsays it needs to repartition. i guess cause its coming from icy glitch kernel. then it restarts into the semaphore cwm and then i reinstall jellybean rom and reboot and the phone just laggs unbelievable unless plugged into the charger. i mean the booot animation will move like 1 frame every 10 seconds. i have tried changing the voltage and overclocking it once it starts up. everything works perfectly until the second i unlug the charger then it does the extreeeeem lagg. From my experiences with this phone i would have to say that it is the power management ic on the logicboard. My question is what do you guys think i should do. i am back on icyglitch kernel and the outdated slim ics. i would really like to get jelly bean working and i would also like to be able to boot my phone with out a charger and an electric outlet.
sorry for such a long post i just thought that some of this information could give someone on here an idea of what is wrong with my phone.
Thanks for any help you guys can give.
Click to expand...
Click to collapse
2 things, probably needs a new mobo and/or battery (thinking mobo though) and your volume down is probably stuck or dirty, making your phone go in download mode all the time.
Did you try flashing Odin KK4 with bootloaders and start fresh from there?

BWolf56 said:
2 things, probably needs a new mobo and/or battery (thinking mobo though) and your volume down is probably stuck or dirty, making your phone go in download mode all the time.
Did you try flashing Odin KK4 with bootloaders and start fresh from there?
Click to expand...
Click to collapse
What is odin kk4?if its the korn kernel i have tried it and semaphore kernel and they both installed but semaphore had the extreme lagg problem and korn kernel worked but the power issue was still there i installed the cwm .zip version tho would this make a difference? I have used odin one click to restore it to factory defaults. I think that should have ruled out any firmware issues, but im not sure. maybe i need to do the master clear thing that it shows on odin. It does seem like it could be a bootloader issue becuase the phone was originally on some half working rom when i got it and i know the guy i got it from said he was always flashing new roms on it. when i got it it already had this problem. then i flashed all kinds of roms and kernels trying to c if it was a firmware issue. I dont think the volume button is stuck because I use my phone daily even with this very annoying defect. It never turns the volume down on its own. the power button does stick sometimes but thats not too often. i have actually tried another battery in the phone too with the same results.
Do you think that having the wrong bootloader would cause something like this? I know from experiences installing linux and hackintosh that the bootloader is crucial to how the system runs. I did the one click restore and i would think that would also restore the original eclair bootloader but it still had the issue. then from there i flashed a GB rom then an ICS rom and a JB rom. I think these would each have their own different bootloaders and maybe they are conflicting. i always clear cache and dalvic cache before installing a new rom.
Is there anymore software i could try troubleshooting on my phone or is this seeming like a hardware problem?

anarchybob6 said:
What is odin kk4?if its the korn kernel i have tried it and semaphore kernel and they both installed but semaphore had the extreme lagg problem and korn kernel worked but the power issue was still there i installed the cwm .zip version tho would this make a difference? I have used odin one click to restore it to factory defaults. I think that should have ruled out any firmware issues, but im not sure. maybe i need to do the master clear thing that it shows on odin. It does seem like it could be a bootloader issue becuase the phone was originally on some half working rom when i got it and i know the guy i got it from said he was always flashing new roms on it. when i got it it already had this problem. then i flashed all kinds of roms and kernels trying to c if it was a firmware issue. I dont think the volume button is stuck because I use my phone daily even with this very annoying defect. It never turns the volume down on its own. the power button does stick sometimes but thats not too often. i have actually tried another battery in the phone too with the same results.
Do you think that having the wrong bootloader would cause something like this? I know from experiences installing linux and hackintosh that the bootloader is crucial to how the system runs. I did the one click restore and i would think that would also restore the original eclair bootloader but it still had the issue. then from there i flashed a GB rom then an ICS rom and a JB rom. I think these would each have their own different bootloaders and maybe they are conflicting. i always clear cache and dalvic cache before installing a new rom.
Is there anymore software i could try troubleshooting on my phone or is this seeming like a hardware problem?
Click to expand...
Click to collapse
Start by flashing Odin KK4 from this post: http://forum.xda-developers.com/showpost.php?p=18370912&postcount=3 - That will clean your phone of w/e was on it before.
From there, you can flash Corn Kernel to get back to a JB ROM. Although, know that if you had the wrong bootloaders, your phone wouldn't boot and it would show color stripes.
Also, before flashing a ROM, you should wipe system and factory reset to make sure everything is clean (Backup your stuff first).

BWolf56 said:
...your volume down is probably stuck or dirty, making your phone go in download mode all the time...
Click to expand...
Click to collapse
I had a similar problem with my Sprint Galaxy S2 D710 (Epic 4G Touch) - my phone would randomly reboot every few days, and it kept getting more frequent. I thought it was the ROM, the overclock, etc. I flashed back to a stock ROM, and stock clock speeds. Eventually, I noticed that even brushing the power button would wake the screen, and about 10 seconds later the phone would reboot. I cleaned the button with some 95% isopropyl (rubbing) alcohol, and it worked better for a few weeks. It started acting up again, so I bought and installed a replacement power button.
Long story short, I got a new power switch, soldered it in place, and have had zero problems since!
The i897 Captivate uses the same switches for power and volume up/down. These switches are notorious for failing, so that's probably the issue with your phone. Try cleaning them, or you can buy a new switch for about ten bucks on ebay.
YouTube has numerous "teardown" or "disassemble" videos and several eBay sellers offer the switch you'll need.
(They don't include the skills needed to replace it. It's a tiny switch - about 4mm long, and you'll need a good soldering iron and a steady hand. Do you have a friend who's pretty good at soldering stuff?)

Xperia T completely dead, no charging, no booting

Hello,
I have a problem, tried searching for a solution but couldn't find anything. I have an Xperia T with NEO's rom with CM 12.1. I put the rom last week and it has been working very nicely.
Last night I went to bed with its battery being around 20%. This morning when I woke up it was completely dead:
1. Won't turn on using power button
2. Won't charge at all, not with usb, not with wall charger
3. Won't fastboot/recovery
4. PC doesn't recognize it.
5. Tried power + vol up to reset, nothing happens
6. Whatever I try, the LED stays completely off, no blinking, no colors, nothing.
Any ideas? Could this be a hardware (battery) problem? Never thought it could break instantly

While I did manage to fix it but removing the battery and connecting it again, I am still not sure what cause this. Could it be a software issue? I`m using CM 12.1

digital29 said:
While I did manage to fix it but removing the battery and connecting it again, I am still not sure what cause this. Could it be a software issue? I`m using CM 12.1
Click to expand...
Click to collapse
It's called Sleep of Death (SOD). It can be caused by ROM issue, kernel issue or installed app issue.
Look into the Developer thread for your ROM if there is some advise.

balonik said:
It's called Sleep of Death (SOD). It can be caused by ROM issue, kernel issue or installed app issue.
Look into the Developer thread for your ROM if there is some advise.
Click to expand...
Click to collapse
Thank you very much for your reply. In the meantime I restored it to stock and seems to be working ok.

I had issues with WhiteNeo's CM12/12.1 as well.
If stock rom is slow for you, you can try one of the custom 4.3 ROMs. PureXT or Omega worked fine for me and they are based on stock ROM, just lighter/faster and customized.