I installed the Neutrino ROM (CM7) a few hours ago because I was extremely tired of dealing with the 2hr battery life I was getting from CM10.1 and kristianp's latest kernels. I'm not sure if the 38p radio was contributing to any problems or not.
I was perusing the settings; I tapped Add Account in Settings > Accounts, and my phone rebooted, after which it wouldn't go past the Moto logo and would display this message "Modem did not power up (0) Starting RSD protocol support"
I googled this, and it's a hardware problem with no way to fix it except warranty, which has expired. I can boot my phone using "Boot Android (No BP)", but this disables radio, so I cannot use my phone for communication purposes anymore. Except IM apps when I'm at home on WiFi.
Any ideas as to what I should do? I really don't think I can afford a new phone right now since I'm about to buy a laptop for school.
Ebay. $50-80.
Sent from my MB886 using xda app-developers app
txtsd said:
I installed the Neutrino ROM (CM7) a few hours ago because I was extremely tired of dealing with the 2hr battery life I was getting from CM10.1 and kristianp's latest kernels. I'm not sure if the 38p radio was contributing to any problems or not.
I was perusing the settings; I tapped Add Account in Settings > Accounts, and my phone rebooted, after which it wouldn't go past the Moto logo and would display this message "Modem did not power up (0) Starting RSD protocol support"
I googled this, and it's a hardware problem with no way to fix it except warranty, which has expired. I can boot my phone using "Boot Android (No BP)", but this disables radio, so I cannot use my phone for communication purposes anymore. Except IM apps when I'm at home on WiFi.
Any ideas as to what I should do? I really don't think I can afford a new phone right now since I'm about to buy a laptop for school.
Click to expand...
Click to collapse
I had that problem twice on my atrix and managed to boot modem again. I don't have exact solution but it was mix of booting in different modes, flashing radio, pulling battery for some time. If your modem just hang it should be possible to restart it.
krystianp said:
I had that problem twice on my atrix and managed to boot modem again. I don't have exact solution but it was mix of booting in different modes, flashing radio, pulling battery for some time. If your modem just hang it should be possible to restart it.
Click to expand...
Click to collapse
I tried flashing 38p over and over again, but it kept failing. I guess I can try booting in different modes and pulling the battery, if this has a chance of working.
txtsd said:
I tried flashing 38p over and over again, but it kept failing. I guess I can try booting in different modes and pulling the battery, if this has a chance of working.
Click to expand...
Click to collapse
I read about your storage problems. It looks like I had very similar experience. Both modem and storage started failing in the same time. To fix storage you can try flashing sbf. From what I read it rebuilds whole emmc. Another solution (that I used) was to rebuild and format partition in recovery. I have different recovery with proper support for vfat (default recovery has problems with it). If you are interested I can publish it.
I had some weird storage problems too, on two different devices, both running MROM-CM7. Both of them had a very hard time getting to 48 hours of uptime without at least one random reboot, and almost every time the reason (according to logs) was "mmcblk0: error -110 settings block erase XXX address" (XXX would be start or end) and some random sector, always different. (For what it's worth, "-110" means TIMEOUT.) After a lot of poking around, switching /data to ext3 instead of ext4 (and modifying the boot image/ramdisk accordingly) seems to have fixed it for me. No idea why ext4 would be so problematic but I'm happy for now.
krystianp said:
I read about your storage problems. It looks like I had very similar experience. Both modem and storage started failing in the same time. To fix storage you can try flashing sbf. From what I read it rebuilds whole emmc. Another solution (that I used) was to rebuild and format partition in recovery. I have different recovery with proper support for vfat (default recovery has problems with it). If you are interested I can publish it.
Click to expand...
Click to collapse
I tried booting different in different modes, pulled the battery for several minutes, and tried flashing radio to no avail. Still dead. I'm prepping to flash sbf right now. afaik vfat uses more space to store files than FAT32. Why would I want a recovery with vfat support?
EDIT: Is this the best way to flash SBF? I thought there might be a different method to go about it from CM10, but couldn't find any such methods.
ravilov said:
I had some weird storage problems too, on two different devices, both running MROM-CM7. Both of them had a very hard time getting to 48 hours of uptime without at least one random reboot, and almost every time the reason (according to logs) was "mmcblk0: error -110 settings block erase XXX address" (XXX would be start or end) and some random sector, always different. (For what it's worth, "-110" means TIMEOUT.) After a lot of poking around, switching /data to ext3 instead of ext4 (and modifying the boot image/ramdisk accordingly) seems to have fixed it for me. No idea why ext4 would be so problematic but I'm happy for now.
Click to expand...
Click to collapse
I mounted the internal SD via recovery earlier, and ran chkdsk on it in Windows. It claimed to have fixed several bad sectors, but it still didn't mount the drive after rebooting. I will try this ext3 trick too. Aren't all partitions ext3 by default anyway? Isn't that why there's an "upgrade partition to ext4" option in ROMracer's recovery?
txtsd said:
Aren't all partitions ext3 by default anyway?
Click to expand...
Click to collapse
On stock-based ROMs maybe, on CM7-based ROMs they are all ext4.
ravilov said:
On stock-based ROMs maybe, on CM7-based ROMs they are all ext4.
Click to expand...
Click to collapse
Oh. How would I go about converting them back to ext3 after flashing a CM ROM?
@KristianP @ravilov
So I flashed my phone with 1FF-olympus-user-2.3.6-4.5.1A-129_OLY-145-4-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P012.sbf
and the radio and internal storage magically started to work again. The only problem I have now, which started just now, is my screen registering touches where I'm not touching it. It's really hard to type when every 3rd or 4th tap registers above the keyboard, thereby closing it.
Going to flash a fresh CM10.1 now.
Can you share the sbf download link? I just want to have a backup on my PC, in case I ever have it, I will not panic
Related
Hello,
I downloaded the official rom from the official HTC website.
It is the WWE East Europe version - suited for my device because the SN is confirmed.
The download finished OK from the Europe 2 server.
I flashed by placing the extracted leoimg.nbh on the root of the SD Card.
I confirmed that the flash was successful - it shows the correct version number of Manilla, radio, etc. Additionally, the ROM is still only 448 MB.
However, the phone freezes all the time and/or restarts itself complely randomly - I have observed this 22 times in the past hour. Is anyone experiencing something similar?
I have redone the flash again, but the same issue occurs.
This is happening with no programs installed, no HSPL, etc. Everything is completely clean.
What can I do to stop this?
may i know why you flashed the latest stock rom using your sd card. would it not be easier to flash through your pc using a usb cable?
you might want to check the meaning of "bricking the phone"...........
then remove it from the title of the thread........
As Rurph mentioned, flash it via your pc, still following the instructions from theHTC site
I now tried flashing through PC, same freezing occurs.
To reiterate:
I have an original HTC HD2 bought from the official HTC shop in Czech republic.
I downloaded the latest official ROM for HTC HD2 from the official htc.com/cz website using my original serial number.
The download finished successfully every time (I tried it 5 times from all the different servers), and the SHA-1 hash of the files was identical every time.
I now flashed it using the normal PC method - everything appeared successful.
I also tried extracting the nbh file from the downloaded file - both by running the .exe file, and by extracting it using winrar - both methods gave me the same nbh file with the same SHA-1 hash. Then I moved the leoimg.nbh to the root of SD card and flashed using the SD-Card method. Everything appeared successful.
Both of the above methods give me a system that freezes completely at random. For example when starting the phone, it can just freeze (left it for 8 hours over night, it remained frozed), when moving from 1 tab to another (freezes in the middle of the animation), when opening the start menu, when going into settings, when making phone call, when opening SMS, and most importantly when NOT DOING ANYTHING AT ALL.
What can I do?
Try to flash an older Version.
I don't know if its possible, but maybe that solves your problem.
Did you have SPL 3.03? If no... Install HSPL and use a custom ROM like the one from NRGZ28 (EnergyROM)
If you an't flash the older version via RUU (Rom Update Utility) try to flash it from SD card. You can also perform a "task 29" with MTTY (before you flash)
But be careful, you can brick your phone...
I have always only used official ROMs from HTC, so I never needed HSPL so I never installed it. I also always prefer the official ROMs so I would rather not use a cooked one.
I think flashing an older version would solve the problem, however I would rather like to find out what the cause is...
So far, I managed to get my phone to a useable state by running Android from the SD card - it works flawlessly for all my purposes. The only problem was to start Android through Windows before windows manages to freeze...
Given that android does not freeze, I believe that the freezing problem must be a windows mobile issue.
Any suggestions for tracking down this freezing problem? Could it be a hardware issue?
hard reset. and if no better flash the rom again followed by hard reset.always hard reset straight away as soon as you see a glitch in a freshly flashed rom. don't ask me why, cos i don't know, but it does seem to help when a flash doesn't "take".
oh and you didn't leave the old application data folder on your sd card did you? or try to restore registry settings?
samsamuel said:
hard reset. and if no better flash the rom again followed by hard reset.always hard reset straight away as soon as you see a glitch in a freshly flashed rom. don't ask me why, cos i don't know, but it does seem to help when a flash doesn't "take".
Click to expand...
Click to collapse
I always hard reset before and after a flash. No change - freezing still occurs.
Even when I did multiple hard resets, the freezing persisted.
The SD card is freshly formatted, checked for no filesystem errors.
I did not restore any settings or anything else - the problem occurs on a completely fresh clean flash.
Additionally, the problem occurs even with no SIM card or SD card inserted into the phone.
Overheating?
I concur with rr5678, seems more like overheating than ROM problems, esp. that I've had the same ROM for a week with no problems whatsoever
hence kind request to OP: check overheating threads and please change the thread subject to a more accurate one so it does not spread misinformation and panic
as for the overheating - 1st thing to do is installing BattClock and monitoring correlation between freezes and battery temperature
rr5678 said:
Overheating?
Click to expand...
Click to collapse
The phone is definitely not overheating. It is very cold to touch and it runs Android without a problem.
OK I did some more testing - going back to any previous ROM fixes the freezing. Then installing the newest ROM reintroduces the freezing.
Given that it is definitely not a hardware issue (works on previous ROM, works on Android, no overheating), it looks like a Windows mobile issue.
I am surprised that nobody else is experiencing this. How come I am the only one? What is so special about my phone?
And the new firmware can "brick" the phone - a less skilled user would not be able to do anything with a frozen phone...
Anyone know why I get no ringtones or alarm sounds when using 1.8?
Deliberate?
Edit: Weird, seems first time a check a ringtone or alarm sound list it's empy. I leave then go back, it's populated again. So self-fixing issue.
Edit 2: Yeah.. tabs got mixed up, completely wrong thread, sorry!
Anyone help?
HTC Support is as always useless - their advice was to take out the battery and put it back in...
Additionally, I think this is a similar problem:
http://forum.xda-developers.com/showthread.php?t=818169
b2206015 said:
Anyone help?
HTC Support is as always useless - their advice was to take out the battery and put it back in...
Additionally, I think this is a similar problem:
http://forum.xda-developers.com/showthread.php?t=818169
Click to expand...
Click to collapse
Try another sim card if you can. I know it sounds crazy but...
wardh said:
Try another sim card if you can. I know it sounds crazy but...
Click to expand...
Click to collapse
Thanks for the advice - but given that the phone freezes even with no SIM card inserted, I do not think that it is the case...
I have however tested inserting a different SIM card anyway, and the freezing occured again...
I too faced constant freezing problems with the official ROM but then I used HSPL and flashed a different radio (2.12 in my case) and ever since never faced any freezing problems..worth a try I guess...
epic fail
not being picky, but "bricking" is, as far I know, by definition an irreversible problem? Hanging and freezing and re-booting are not bricking.
That said, sorry to hear about your troubles.
Sounds like going back to your old ROM is the only solution right now.
b2206015 said:
Hello,
I downloaded the official rom from the official HTC website.
It is the WWE East Europe version - suited for my device because the SN is confirmed.
The download finished OK from the Europe 2 server.
I flashed by placing the extracted leoimg.nbh on the root of the SD Card.
I confirmed that the flash was successful - it shows the correct version number of Manilla, radio, etc. Additionally, the ROM is still only 448 MB.
However, the phone freezes all the time and/or restarts itself complely randomly - I have observed this 22 times in the past hour. Is anyone experiencing something similar?
I have redone the flash again, but the same issue occurs.
This is happening with no programs installed, no HSPL, etc. Everything is completely clean.
What can I do to stop this?
Click to expand...
Click to collapse
Psaldorn said:
Anyone know why I get no ringtones or alarm sounds when using 1.8?
Deliberate?
Edit: Weird, seems first time a check a ringtone or alarm sound list it's empy. I leave then go back, it's populated again. So self-fixing issue.
Edit 2: Yeah.. tabs got mixed up, completely wrong thread, sorry!
Click to expand...
Click to collapse
Well, to me it seems your phone just doesn't like custom ROMs.
So I have had this issue with my phone today where I couldn't seem to get passed the Too many pattern attempts screen.
After trying all my combinations of e-mail and passwords, I was unable to access my phone. As a result, I attempted to do a hard reset (the pressing of both volume rockers and then trying to reset it in that recovery mode).
I did so, wiping all my data, but the too many pattern attempts screen remained. So as a result, I booted up Odin and downloaded the stock versions of the Samsung Fascinate's ROM and proceeded to reflash (or what I believe to be reflashing, I simply followed the directions found in the stickies).
That all said and done, my phone still remains in the too many pattern attempts lock.
I've checked the similar posts on a couple of websites, but was unable to find a situation where all of these fixes did not work.
Thank you!
No replies yet, so I am just going to throw this out there on the off chance that it *might* actually work.
The "complete voodoo lagfix removal" uninstall.zip CWM flash seems to be working as a cure-all for just about whatever may ail your phone, whether you actually *have* voodoo or not...
I would check that out in the OP of this thread.
Download the Voodoo Uninstall on your PC. Copy it to your SDcard (if you don't have a computer that you can put the card in after pulling it out of your phone, try using adb to push it to the phone)
Boot into stock recovery, and flash "update.zip" to get into CWM recovery.
Flash that voodoo uninstall zip using CWM.
I really hope this helps. (Just in case it happens to me. )
Let us know!
I work for flextronics. we see this all the time. it's a known issue that the lock screen doesn't reset with a factory wipe. just call the phone, answer and press the home screen button. it's what we do in store
Sent from my SCH-I500 using XDA App
This is more than likely living in /dbdata . You can wipe that by doing a privacy wipe in settings (requires access to the phone), or flash CWM via odin, and then when in recovery, rm -r /dbdata/ and reboot.
If the phone-call / home button thing else_where posted works, obviously go that route, then do a privacy wipe.
namebrandon said:
This is more than likely living in /dbdata . You can wipe that by doing a privacy wipe in settings (requires access to the phone), or flash CWM via odin, and then when in recovery, rm -r /dbdata/ and reboot.
If the phone-call / home button thing else_where posted works, obviously go that route, then do a privacy wipe.
Click to expand...
Click to collapse
you will more than likely need to mount the /dbdata partition r/w before you can delete the data. This is covered in the Voodoo removal thread (which I had the joy of doing).
martian21 said:
you will more than likely need to mount the /dbdata partition r/w before you can delete the data. This is covered in the Voodoo removal thread (which I had the joy of doing).
Click to expand...
Click to collapse
Good point!
mkdir /dbdata
mount -t rfs -o nosuid,nodev,check=no /dev/block/stl10 /dbdata
else_where said:
I work for flextronics. we see this all the time. it's a known issue that the lock screen doesn't reset with a factory wipe. just call the phone, answer and press the home screen button. it's what we do in store
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
You work for Flextronics ???? Didn't Verizon end their contract with them for all regions already ????
working in an A class store. allot of the philly market and north east stores still have techs. besides or sales people are helpless. like every time with a cellbrite is their first time
Sent from my SCH-I500 using XDA App
Hey guys thanks for all the help,
The calling of the phone didn't work. Tried it, but it kept giving me corrupt errors so I wasn't able to access the home screen.
The voodoo removal sort of worked in that while I was doing it, I also went ahead and did a privacy wipe. Everything would be fine and dandy however, my phone no longer connects to any network. It seems to be in a perpetual state of being unable to find a network. It's not airplane mode, but my phone does think it's January first 2005 again.
Did I miss a step?
runeliger said:
Hey guys thanks for all the help,
The calling of the phone didn't work. Tried it, but it kept giving me corrupt errors so I wasn't able to access the home screen.
The voodoo removal sort of worked in that while I was doing it, I also went ahead and did a privacy wipe. Everything would be fine and dandy however, my phone no longer connects to any network. It seems to be in a perpetual state of being unable to find a network. It's not airplane mode, but my phone does think it's January first 2005 again.
Did I miss a step?
Click to expand...
Click to collapse
You did the privacy wipe from within the settings menu ???? That fixed a similar issue where I couldn't connect to the network
mexiken said:
You did the privacy wipe from within the settings menu ???? That fixed a similar issue where I couldn't connect to the network
Click to expand...
Click to collapse
Yes indeed I did. The first thing I did was the Factory data reset.
Unfortunately, the phone seems to be in a state of perpetual ariplane mode preventing access to any network.
The phone also seems to be suffering from that com.android.phone crashes that I suppose make sense given how the Hardware version and the Baseband version are both unknown.
I'm going to try to flash it again in hopes of resetting my phone. The perpetual airplane mode is of course an issue. (but at least I got the alarm functinoality of my phone back)
Hrm, I'm concerned now. Check your settings / about phone and baseband version. Please tell me it does not say 'unknown'.
Yea, mine wasn't stuck in airplane mode, just didn't connect to google's servers to set up gmail.
If you're still rooted, maybe try the radio update ????
Any update ????
mexiken said:
maybe try the radio update ????
Click to expand...
Click to collapse
DANGER! - Don't go updating your radio unless you really know what you're doing. Yes there has been a radio update with the D01 however flashing the wrong thing to the radio will result in a shiny brick that as of right now can't be recovered!
Yeah I was seeing a bunch of unknowns in a lot of my slots.
I wasn't sure what was wrong, so I did some more research and it seemed as though that the modem aspect of my phone must have corrupted.
So I simply went to a verizon store and swapped out my phones (since I couldn't find a fixed modem).
The other fix of deleting via the privacy wipe definitely worked though.
Thanks everyone!
i500 fascinate too many patterns
what I did I turn the phone off
then turn it on ones the one verizon animation goes of it asks for the email and pass so start hitting home button as fast as you can and sometimes emergency button till it takes you to the main many do not stop till al the icons load up
then you got it but you have to go in to the menu and wipe it off or erease the email account
it worked for me after few tries it shoulg work for you too
anngiehdz said:
what I did I turn the phone off
then turn it on ones the one verizon animation goes of it asks for the email and pass so start hitting home button as fast as you can and sometimes emergency button till it takes you to the main many do not stop till al the icons load up
then you got it but you have to go in to the menu and wipe it off or erease the email account
it worked for me after few tries it shoulg work for you too
Click to expand...
Click to collapse
i think its safe to say that responding to 6+ month old threads is at best pointless..at worst stupid
nitsuj17 said:
i think its safe to say that responding to 6+ month old threads is at best pointless..at worst stupid
Click to expand...
Click to collapse
Respectfully I have to disagree. Sharing a new solution to an old problem cannot be a bad thing. maybe 6+ months from now it will save someones bacon without having to start a new thread for it
I flashed over Bionix V 1.3.1 with NextGen V2 last week by wiping data/cache/etc instead of flashing back to stock first. Everything worked really well (except for TW4 that force closes everytime) but I was just a little bugged by the 1 sec lag it takes to turn on the lock screen from sleep (the lag is absent when charging). I thought I would ODIN it back to stock and try again. Strangely, the stock has this lag now too. When I try to wipe Dalvik, I got an error "E: Can't mount /dev/block/mmcblk0p2 (File exists)". Also, my phone is still SIM unlocked after ODIN. Does this mean there are some parameters from previous flashes remaining in the system? How can I REALLY get it back to stock?
with windows plug the phone into pc then right click on the internal sd on my computer then format, should get rid of anything left from previous roms, remember to back your stuff up
dont know how to do it on mac
Thanks, will try that.
Another (silly?) question: it's always advised we leave the phone alone for ~15min before we reboot and play with it. Whenever I flash Bionix ROMS, the first thing upon reboot after flashing is a question from Google about knowing my location (or something like that). Does 15min starts the moment the phone reboots or after I've responded to the question?
donnygg said:
Thanks, will try that.
Another (silly?) question: it's always advised we leave the phone alone for ~15min before we reboot and play with it. Whenever I flash Bionix ROMS, the first thing upon reboot after flashing is a question from Google about knowing my location (or something like that). Does 15min starts the moment the phone reboots or after I've responded to the question?
Click to expand...
Click to collapse
id leave it from the moment it first comes on before
when i was flashing between 2.2 roms i always went back to simply galaxy and that had the old start up thing but i use to leave it before going through it then reboot then go through it then reboot after
1 reboot should do it though
Tried formatting but no improvement. Tried softlocker app and was able to turn on the lock screen instantly. However, I was losing about 5% battery life every hour, so that's not quite a solution. I then tried something really simple - remove the external SD. Immediately, I could see a reduction in lag when turning on the lockscreen from sleep (<0.5s vs >1s, if you call that a lag). It seems like the external SD card is the problem but I don't know what. The card seems to be lacking the ext2 partition, thus it couldn't be mounted or formatted in CWM. From what I understand, ext2 may improve I/O performance but I may be wrong. I couldn't get it to partition in my phone. The phone seems to format it back to FAT. I'll try getting a microSD adapter and partition it outside the phone and see if it helps, just out of curiosity.
Had my phone 2 years, installed ROMs without any issues before.
Was running CM10.1 daily, when yesterday I thought I'd go and encrypt the phone (using the system menu).
Phone encrypted, rebooted, but immediately I started getting 'google play store crashed' errors in an infinite loop. It was usable enough to push the latest neatrom to the phone via USB connectivity, so I did a full wipe (clear data/factory reset, clear cache, clear dalvik, format /system, install rom in CWM) and installed neatrom.
Phone reboots, looks OK at first except for a 'usb storage is blank or unsupported' message in notification center. I try to format it, no dice, just stops displays the notification again.
Of course, without what is seen by the sgs2 as usb storage I can't install any app and everything crashes to desktop (camera, etc).
I'm not sure what to do next, and could use some advice! Thank you!
Right, so now I've bricked it. Odin, GB phone, csr and pda, then black screen, then nothing. Won't reboot either. Just... great.
Ok, thanks for sharing.
Sent from the little guy
I got an iPhone now. Wondering why I spent 2 years of my life with a battery that last 1/2 day and constant issues. Problem solved for good!
Alright! Now you got so many things to do with it.
Sent from the little guy
reflash back to stock rom first, but first make a back up for your current rom. that happened to my tab before. the internal memory is not working and saying something blank/unsupported, really cannot remeber. i couldnt install apps. i contacted the support of the tab (NOMADNINE) and i was adviced to flash it back to stock since it will copy files and put the chipset to write mode and will erase everything... you can try to flash it through ODIN.
He went iOS.
Sent from the little guy
gastonw said:
He went iOS.
Sent from the little guy
Click to expand...
Click to collapse
Yup, plus the SGS2 is hard bricked: no power on, tried various ways to address that but no dice. Off to ebay for spare parts.
Hey Everyone,
I am having an issue with my screen turning on randomly on my phone. Its a Verizon Note 2 (hence me posting in this section). I'd like to think I've done some troubleshooting but I want somebody else to tell me that I am not insane.
So far what I've done:
1. Flashed Custom Rom - CM11 in this case. Screen turning on and off is persistent between stock and CM leading me to believe hardware problems.
2. Took phone apart, unplugged power button from motherboard. Booted phone back up and disconnected. With the cable disconnected it still persisted.
3. Taking a page from some other threads on XDA I have tried the key test in CWM. My screen was turning on every 1-2 minutes and right now its been sitting for 15 minutes with no key presses registered (with the cable re-connected).
So with all of that being done I'm assuming its an issue with something that Google is restoring to my phone? Does that sound like a logical conclusion? Before I factory reformat and not have anything restore I just wanted to post up and verify.
As a second question - is there a good way to clear all the internal memory before I do a fresh format of CM11 (if i go that direction tonight?) I still have folders on the internal SD card from my stock install that i would like wiped out.
Thank you all in advance: I love this site. I've been flashing every phone i've owned from the guidance here but very rarely post.
TheDigitalSlacker said:
Hey Everyone,
I am having an issue with my screen turning on randomly on my phone. Its a Verizon Note 2 (hence me posting in this section). I'd like to think I've done some troubleshooting but I want somebody else to tell me that I am not insane.
So far what I've done:
1. Flashed Custom Rom - CM11 in this case. Screen turning on and off is persistent between stock and CM leading me to believe hardware problems.
2. Took phone apart, unplugged power button from motherboard. Booted phone back up and disconnected. With the cable disconnected it still persisted.
3. Taking a page from some other threads on XDA I have tried the key test in CWM. My screen was turning on every 1-2 minutes and right now its been sitting for 15 minutes with no key presses registered (with the cable re-connected).
So with all of that being done I'm assuming its an issue with something that Google is restoring to my phone? Does that sound like a logical conclusion? Before I factory reformat and not have anything restore I just wanted to post up and verify.
As a second question - is there a good way to clear all the internal memory before I do a fresh format of CM11 (if i go that direction tonight?) I still have folders on the internal SD card from my stock install that i would like wiped out.
Thank you all in advance: I love this site. I've been flashing every phone i've owned from the guidance here but very rarely post.
Click to expand...
Click to collapse
To format the internal SD card, reboot into recovery (sounds like you use cwm), go to 'mounts and storage' and wipe 'sdcard' or 'data/media.' I havent used cwm in a while so I cant remember the exact wording.
While in mounts and storage go ahead and wipe 'system' and wipe 'data' as well before installing the new rom. Before installing a new rom you should always wipe system and data.
As far as the screen randomly turning on it does sound logical that it could be google restoring to your phone. Im guessing that you don't see new notifications in the status bar? How long did you let the phone sit after installing a new rom?
Whichever way I doubt it's hardware.
If you format and reinstall dont choose to restore from Google servers. If the problem still persists then there are ways to know what's waking up your phone.
Hälftebyte said:
To format the internal SD card, reboot into recovery (sounds like you use cwm), go to 'mounts and storage' and wipe 'sdcard' or 'data/media.' I havent used cwm in a while so I cant remember the exact wording.
While in mounts and storage go ahead and wipe 'system' and wipe 'data' as well before installing the new rom. Before installing a new rom you should always wipe system and data.
As far as the screen randomly turning on it does sound logical that it could be google restoring to your phone. Im guessing that you don't see new notifications in the status bar? How long did you let the phone sit after installing a new rom?
Whichever way I doubt it's hardware.
If you format and reinstall dont choose to restore from Google servers. If the problem still persists then there are ways to know what's waking up your phone.
Click to expand...
Click to collapse
Thanks,
I'll be doing that today. How can i tell whats waking it up? The wakelock detector i have been using isn't ready for 4.4 yet.
Turns out it was noon walk that was doing it
Sent from my SCH-I605 using xda app-developers app
Haha good. How'd you find out?
Sent from my SCH-I605 using Tapatalk