this has been going on for a few months now, when i try to shut the phone down completely it just reboots itself. the only way to get it to turn completely off is by pulling the battery and leaving it out. as soon as i put the battery back in the phone it autoboots up. at first i thought this was a CM7 issue but in the past 2 days ive tested leedroids rom, honeysenceHD, and a few others and the phone still acts the same. its never been an issue but i would love to be able to turn the phone completely off if i ever needed to. someone suggested that its possible my bootloader is corrupted. is there any way to fix this issue?
This is a problem with the Advanced Power Manger, search for the fix.
Sent from my Inspire 4G
ok well can someone point me in the direction to fix this problem.....search finds NOTHING for a fix
what apps do you have installed can you list them? They can sometimes cause problems...
Make sure "Fast boot" is UNchecked under Settings, Power.
i dont see a POWER sub menu in settings nor can i find Fast Boot.
apps are as follows
everything that comes stock with CM7
Battery Calibrator
Beautiful Widgets
COveroid
Dev Tools
DSPManager
FasterFix
Linpack
Quickboot- just to see if it would turn the phone off and it doesnt
setCPU but not using it currently
Spare Parts
thats about it a few of those apps i think are part of CM7 but im not sure
Look for fastboot in settings, applications.
Sent from my Desire HD using XDA Premium App
theres nothing in applications that allows me to turn on or off FASTBOOT
ok so i was told theres no FASTBOOT option in CM7 so anyone else out there have any clue as to why my phone will not turn off and stay turned off when i power it down?
Projectdwnshft said:
ok so i was told theres no FASTBOOT option in CM7 so anyone else out there have any clue as to why my phone will not turn off and stay turned off when i power it down?
Click to expand...
Click to collapse
Well at this point, if you think that continuing to try other roms other than what you've already flashed won't help, you might just try flashing a completely stock image, with the stock hboot/recovery, etc., and see if indeed something went haywire with your bootloader, as you mentioned someone had suggested to you.
Try the RUU in the stickied thread, for example. The recent OTA ROM by Attn1 has the hboot removed from it so I don't think that would be a good choice for this attempt, because you want to get the stock bootloader back.
Now, I can't speak to the validity of that suggestion about the possible corrupt bootloader... I don't know either way whether or not that could be the cause, but if you wanted to at least try it, then my suggestion above would be the way to do it, I would think.
There would be no reason for it to continue to behave like this on a completely stock ROM, other than there being something defective with the phone itself.
It's a clockworkmod issue with daylight savings time. Change your date from automatic to a date before the time change (I just go to Jan) and your phone will shut off and stay off.
"Change your date from automatic to a date before the time change (I just go to Jan) and your phone will shut off and stay off. "
i dont really understand what you mean by change it to a date/time before the time change. i turned off the auto time but dont see where your talking about with setting the date change
I wasn't going to try to help cause I didn't like yer tone. You could say please and thank you for peeps time..
http://forum.xda-developers.com/archive/index.php/t-1104835-p-2.html
Not sure if anyone has run into this yet, if so please share the fix. When selecting "power off" my Inspire 4G just reboots. I can no longer turn off my device. Thanks in advance for the help.
Download quick reboot from the market for now
Sent from my Desire HD using XDA Premium App
Click to expand...
Click to collapse
I stopped reading. But a search is easy on the thread. Google is your friend....
big ups for the useless reply but thanks anyways....CHEERS
oh and there was no tone, but whatever mr internet coolguy THUMBSUP to you. i wouldnt have made this thread if i didnt already search to see if anyone else has had this problem, and it seems noone else has. when the phone was flashed back to stock the problem stopped and as soon as i re-rooted it the problem started again
Projectdwnshft said:
big ups for the useless reply but thanks anyways....CHEERS
oh and there was no tone, but whatever mr internet coolguy THUMBSUP to you. i wouldnt have made this thread if i didnt already search to see if anyone else has had this problem, and it seems noone else has. when the phone was flashed back to stock the problem stopped and as soon as i re-rooted it the problem started again
Click to expand...
Click to collapse
I just linked a guy with the same issue .. Yes its on another rom, but its the same issue....
Download the app....does it work? Problem solved if it does? Or don't.. i could not care less, my phone works normally......
it was a rom issue but guess u didnt read the thread to see that, that app is just another way to reboot your phone, i appreciate the effort but ive tried it many times and it boots/reboots the phone in the same manor the phone boots itself
Scott_S said:
Well at this point, if you think that continuing to try other roms other than what you've already flashed won't help, you might just try flashing a completely stock image, with the stock hboot/recovery, etc., and see if indeed something went haywire with your bootloader, as you mentioned someone had suggested to you.
Try the RUU in the stickied thread, for example. The recent OTA ROM by Attn1 has the hboot removed from it so I don't think that would be a good choice for this attempt, because you want to get the stock bootloader back.
Now, I can't speak to the validity of that suggestion about the possible corrupt bootloader... I don't know either way whether or not that could be the cause, but if you wanted to at least try it, then my suggestion above would be the way to do it, I would think.
There would be no reason for it to continue to behave like this on a completely stock ROM, other than there being something defective with the phone itself.
Click to expand...
Click to collapse
so yeah you had a good point scott. i went ahead and got the phone all back to stock and problem solved, but its not what i want sadly. so i re-rooted the phone and immediately after the re-root i went to turn it off and there it goes again turning itself back on =(
Projectdwnshft said:
it was a rom issue but guess u didnt read the thread to see that, that app is just another way to reboot your phone, i appreciate the effort but ive tried it many times and it boots/reboots the phone in the same manor the phone boots itself
Click to expand...
Click to collapse
So you have re-flashed to stock and the issue went away.
What rom are you flashing after root?
Did you check the MD5sum of the rom?
Have you tried a second rom?
Try just flashing to a stock rom like TCP;
http://forum.xda-developers.com/showthread.php?t=982963
Edit, just read yer above post... None this is going to help. Lol
i havent tried flashing anything, i flashed it back to stock, rebooted worked fine. So i decided to just reroot it. its stil STOCK atm just rooted. its obvious that its a software issue id just love to know what and how to fix it.
When you're flashing to a new rom are you clearing all of your data every time? If not you might want to give it a shot when you try to flash to another rom.
I simply rebooted my phone and all my settings and customizations are gone, many things just stopped workings for no reason too.....
kolyan said:
I simply rebooted my phone and all my settings and customizations are gone, many things just stopped workings for no reason too.....
Click to expand...
Click to collapse
This doesn't belong in General. This is a question being asked, looking for an answer. Thus, it should be in Q&A.
On that note, I need more information than, "my phone reboot and stuff is gone", to help. What ROM are you using? What kernel? What MODs? What customizations? What tweaks?
Stock with Franco and Exposed. Didn't install anything and never had any problems till now
. Getting E: error opening in recovery, don't think I ever saw that either.
Hello all. Since this is a new account I guess I cannot post under the development page. So my question is this (sorry if this has been asked before I search as much as I could). I installed this Echoe Rom about four days ago and works great but when someone tries to call me I recieve nothing, sometimes a Voice-mail but doesn't ring or get a notification. Rebooted and no go. I thought it was an issue with the cache/Davilk so I wiped and rebooted but still nothing. So I researched and some android users (pm another site) said you have to switch between Auto/LTE/4g and 3g/2g and back again....finally worked. But every time it reboots I have to do this and it's rather annoying because I get a random reboot everyday. If anyone knows a work around for this would greatly appreciate it because after a day of trying to fix it I'm stumped lol. Thx
Viktor0088 said:
Hello all. Since this is a new account I guess I cannot post under the development page. So my question is this (sorry if this has been asked before I search as much as I could). I installed this Echoe Rom about four days ago and works great but when someone tries to call me I recieve nothing, sometimes a Voice-mail but doesn't ring or get a notification. Rebooted and no go. I thought it was an issue with the cache/Davilk so I wiped and rebooted but still nothing. So I researched and some android users (pm another site) said you have to switch between Auto/LTE/4g and 3g/2g and back again....finally worked. But every time it reboots I have to do this and it's rather annoying because I get a random reboot everyday. If anyone knows a work around for this would greatly appreciate it because after a day of trying to fix it I'm stumped lol. Thx
Click to expand...
Click to collapse
I has this issue ... what fixed it for me was just making a backup with TitaniumBackup and doing a clean install of stock firmware, re-rooting and and flashing the rom and then wiping data in the Aroma installer... doing this gave me zero issues .
KillerClaw321 said:
I has this issue ... what fixed it for me was just making a backup with TitaniumBackup and doing a clean install of stock firmware, re-rooting and and flashing the rom and then wiping data in the Aroma installer... doing this gave me zero issues .
Click to expand...
Click to collapse
Thanks for replying. I definetly will try this later. Appreciate it :good::good:
Viktor0088 said:
Hello all. Since this is a new account I guess I cannot post under the development page. So my question is this (sorry if this has been asked before I search as much as I could). I installed this Echoe Rom about four days ago and works great but when someone tries to call me I recieve nothing, sometimes a Voice-mail but doesn't ring or get a notification. Rebooted and no go. I thought it was an issue with the cache/Davilk so I wiped and rebooted but still nothing. So I researched and some android users (pm another site) said you have to switch between Auto/LTE/4g and 3g/2g and back again....finally worked. But every time it reboots I have to do this and it's rather annoying because I get a random reboot everyday. If anyone knows a work around for this would greatly appreciate it because after a day of trying to fix it I'm stumped lol. Thx
Click to expand...
Click to collapse
Do you have Lspeed installed by any chance? If so do you have improve call quality enabled? Disabling this fixed the issue for me so anyone who has this problem and enabled it, disable it and see if it fixes the problem.
Hi
Recently I've unlocked my Z5's bootloader and rooted it.
I installed Paranoid android from the thread in the forum, everything was working fine, even the fingerprint sensor was working quite ok.
after a day I wanted to switch the locking option. so i wouldn't use the fingerprint, and only swipe to unlock the phone.
After i changed the settings the app crashed (it changed successfully to swipe instead of using fingerprint)
Now the result is that every time I try to change this specific setting (Screen Lock) the app asks me for my pin, I type it and the settings app crash.
I tried to restart, Clean cheche and uninstalling some google apps. nothing helps
Thank you for the help! :angel:
RomSeeker said:
Hi
Recently I've unlocked my Z5's bootloader and rooted it.
I installed Paranoid android from the thread in the forum, everything was working fine, even the fingerprint sensor was working quite ok.
after a day I wanted to switch the locking option. so i wouldn't use the fingerprint, and only swipe to unlock the phone.
After i changed the settings the app crashed (it changed successfully to swipe instead of using fingerprint)
Now the result is that every time I try to change this specific setting (Screen Lock) the app asks me for my pin, I type it and the settings app crash.
I tried to restart, Clean cheche and uninstalling some google apps. nothing helps
Thank you for the help! :angel:
Click to expand...
Click to collapse
Probably its something from Rom which yoi installed and beacuse that happends.
Solution to try stock based custom rom or back to stock official.
Sent from my D6503
Allek84 said:
Probably its something from Rom which yoi installed and beacuse that happends.
Solution to try stock based custom rom or back to stock official.
Sent from my D6503
Click to expand...
Click to collapse
So obviously it happened because I am no longer stock, But as my experience goes, I know people may have stumbled upon the same problem in their past, and maybe know a solution that will work for me.
I do not want to go back to stock, Because Sony's Stock is ****, serious **** full for bloatware that you cannot remove and battery life that makes you cry.
Your message was not helpful, but thanks for trying
It most likely is a problem with the ROM installed on your device, as you already performed wipes and the problem persists. Try reporting the problem to the rom dev or if its that important, try a different rom for now
Good luck
Hi,
To begin with, before all this I already had a wifi issue:
I had to reconnect to wifi networks every 5 minutes. After 5 minutes the wifi signal icon was still showing but nothing on apps etc could refresh, simply no signal.
I searched something on Google and found a forum post about someone having the same issue. He fixed the issue by flashing and installing a 'firmware' zip, file or whatever. This was for OnePlus One devices running Nougat so I tought, all ok!
So I flashed the file and since then a new (huger) problem showed up.
When my device was on, no SIM card could be find (And yes it's in lol..) and I can't turn on WIFI (When I do, it turns off automaticely after 5 sec.)
I tried a FULL wipe via TWRP, tried to flash the rom again (TugaPower) and NOTHING worked.
HELP! Seriously, I've been searching **** for 2 days now and I really need my phone.
Twanofzo said:
Hi,
To begin with, before all this I already had a wifi issue:
I had to reconnect to wifi networks every 5 minutes. After 5 minutes the wifi signal icon was still showing but nothing on apps etc could refresh, simply no signal.
I searched something on Google and found a forum post about someone having the same issue. He fixed the issue by flashing and installing a 'firmware' zip, file or whatever. This was for OnePlus One devices running Nougat so I tought, all ok!
So I flashed the file and since then a new (huger) problem showed up.
When my device was on, no SIM card could be find (And yes it's in lol..) and I can't turn on WIFI (When I do, it turns off automaticely after 5 sec.)
I tried a FULL wipe via TWRP, tried to flash the rom again (TugaPower) and NOTHING worked.
HELP! Seriously, I've been searching **** for 2 days now and I really need my phone.
Click to expand...
Click to collapse
You likely have a corrupt EFS partition due to wrong frimware flash.Tugapower recommends flashing Tuga frimware,its already on the thread but anyways...
https://forum.xda-developers.com/oneplus-one/general/guide-efs-partitions-how-to-lost-t3307793
This thread should be able to HELP you.
Mr.Ak said:
You likely have a corrupt EFS partition due to wrong frimware flash.Tugapower recommends flashing Tuga frimware,its already on the thread but anyways...
https://forum.xda-developers.com/oneplus-one/general/guide-efs-partitions-how-to-lost-t3307793
This thread should be able to HELP you.
Click to expand...
Click to collapse
Damn, what stupid of me haha. Thanks dude!
Twanofzo said:
Damn, what stupid of me haha. Thanks dude!
Click to expand...
Click to collapse
Did that worked for you?
Mr.Ak said:
Did that worked for you?
Click to expand...
Click to collapse
Sorry for the late reply but if anyone comes out on this topic, yes, your solution worked.