Database Develop

Cm10 - 15/09/2012 - sim pin re-entering

Hello, and first of all thank you for reading.
The issue is the following, after I boot my Note I input the PIN and all goes well, but if I left it with the screen off ( locked ), sometimes it locks the SIM again, and asks for the PIN on re-entry. It's a random event, but occurs more than a couple times a day. Any known fix? I couldn't find anything with search...
Thank you for your time,
Marco Silva.

MarcoFSilva said:
Hello, and first of all thank you for reading.
The issue is the following, after I boot my Note I input the PIN and all goes well, but if I left it with the screen off ( locked ), sometimes it locks the SIM again, and asks for the PIN on re-entry. It's a random event, but occurs more than a couple times a day. Any known fix? I couldn't find anything with search...
Thank you for your time,
Marco Silva.
Click to expand...
Click to collapse
Few Question bud:
What ROM are you using?
Did you setup SIM PIN Intentionally or you think its a bug and no PIN should be asked at all.?
There was an issue with BackCNA AOSP 1.0 ROM where it would aks for SIM PIN everytime. To fix that, go to >>>Settings>>>Security>>>Uncheck "Lock SimCard".

ruinkhan said:
Few Question bud:
What ROM are you using?
Did you setup SIM PIN Intentionally or you think its a bug and no PIN should be asked at all.?
There was an issue with BackCNA AOSP 1.0 ROM where it would aks for SIM PIN everytime. To fix that, go to >>>Settings>>>Security>>>Uncheck "Lock SimCard".
Click to expand...
Click to collapse
Hi there!
I'm using the lastest release by Cyanogen the CM10 from 15 September... It asks for the PIN the first time I turn on the phone ( ya that's how it should be ) but at some random times it asks again after the screen was locked, but it's not always... It's random that's what's pissing me off, I could just disable the PIN code, but I prefer to have it on incase someone steals my phone :/ Any ideas?
Thanks!

No Ideas what could be the cause to be honest.
If I was you, I would perform a full wipe. That could fix the issue, unless someone else would give you a clue of what that could be.

MarcoFSilva said:
Hi there!
I'm using the lastest release by Cyanogen the CM10 from 15 September... It asks for the PIN the first time I turn on the phone ( ya that's how it should be ) but at some random times it asks again after the screen was locked, but it's not always... It's random that's what's pissing me off, I could just disable the PIN code, but I prefer to have it on incase someone steals my phone :/ Any ideas?
Thanks!
Click to expand...
Click to collapse
Hey, I had exactly the same issue. Booted normally and from time to time, modem seemed to restart and asked again for PIN. That was annoying because I wasn't reachable at this time periods. I was on latest Utacka PA from 16th September with HydryCore Kernel. But it was not the Kernel's fault because I used the same Kernel with the previous build. Now I updated to latest PA from today and the problem was gone by itself.
That's what you have to expect when you are using... pre-nightly... xD.. builds of a ROM.
Consider updating your ROM to current build or change ROM if it's important.

logcats would help. I think phone reboots without you knowing. You can always go to a stabler rom. ICS or GB
Sent from my GT-N7000 using Tapatalk 2

Same problem here
ruinkhan said:
No Ideas what could be the cause to be honest.
If I was you, I would perform a full wipe. That could fix the issue, unless someone else would give you a clue of what that could be.
Click to expand...
Click to collapse
Im having the same problem with latest CM10 nightly (20121105) installing it after a full wipe on a galaxy s2. Any ideas?

[Q] i9000 screen waking itself constantly?!

Recently i put cm11 on my i9000 and now the screen is constantly turning on. As soon as the screen lock is turned on, the phone wakes again.
Sometimes this happens indefinitely and sometimes it only happens once then the screen will sleep after a second press of the lock/power button.
The only consistent thing appears to be that when the lock screen is unlocked the recent apps are always shown.
I've tried formatting/wiping and different night lies and the m4 snapshot but it all happens exactly the same.
Any help would be greatly appreciated.

use this and see if it's the rom or an app that's keeping the phone awake http://forum.xda-developers.com/showthread.php?t=2179651

pryerlee said:
use this and see if it's the rom or an app that's keeping the phone awake http://forum.xda-developers.com/showthread.php?t=2179651
Click to expand...
Click to collapse
Thanks, I've installed this earlier today and I don't quote understand it.
According to wake lock detector, under screen wake lock, running and usage, phone - system (radio) is number one.
Does this mean it's the rom keeping the phone awake?

Not sure how wakelock works to be honest but I don't think it's the rom that's the problem, it sounds like its the radio (modem) try flashing a different baseband for your region and see if that fixes the problem? http://forum.xda-developers.com/showthread.php?t=1870460 http://forum.xda-developers.com/showthread.php?t=1158783

pryerlee said:
Not sure how wakelock works to be honest but I don't think it's the rom that's the problem, it sounds like its the radio (modem) try flashing a different baseband for your region and see if that fixes the problem? http://forum.xda-developers.com/showthread.php?t=1870460 http://forum.xda-developers.com/showthread.php?t=1158783
Click to expand...
Click to collapse
Tried several different radios without any success I'm afraid.
Just tried flashing stock JVU rom and then back to CM11 without any success. Exactly the same issue.
Oddly, if you hold the home key whilst pressing the lock key, the screen turns off and stays off for a while, then wakes after a minute or so again.

New Method
Try going into settings>Applications (or Apps)> Running and check which application(s) is taking up the most memory, it may be that a application from an unknown source is waking up the device, like a virus or your phone is consuming too much RAM. If this is the case try and delete it or run a security scan from the play store such as BitDefender.
Another option is to run a more stable version of CyanogenMod instead of a Nightly, I had problems with Nightly builds and changed back to a stable build. Try the new 4.4 snapshot of CyanogenMod, it is more stable. DOWNLOAD from the official cyanogenmod website, don't update using the option in settings as it always sends my phone into a boot loop. Hope it helps

Try another ROM
Let me know if switching to another ROM helps. I'd suggest Paranoid Android or OmniROM.
The thanks button is right there! just saying...

Gokulbalram said:
Let me know if switching to another ROM helps. I'd suggest Paranoid Android or OmniROM.
The thanks button is right there! just saying...
Click to expand...
Click to collapse
No luck unfortunately, I think I've narrowed it down, and the menu button keeps activating itself.

kcajjones said:
No luck unfortunately, I think I've narrowed it down, and the menu button keeps activating itself.
Click to expand...
Click to collapse
Try Flashing Stock.

Gokulbalram said:
Try Flashing Stock.
Click to expand...
Click to collapse
Stock is doing exactly the same thing

kcajjones said:
Stock is doing exactly the same thing
Click to expand...
Click to collapse
Have you erased each and everything? /data and stuff? also, just see if Touchwake is enabled by any chance

I don't mean to drag this old thread back up, but I've come to use my i9000 again as a backup device and it still has this same problem.
Is there anyway I can prove that it's a button that's faulty (for instance)?
I thought maybe a logger that would show if it detected/logged the home button being pressed when I notice the screen turning itself on, but I can't find such an app.

Non-responsive touchscreen post 5.1 update

I recently acquired a Nexus 6 last month. Everything was fine until I got the new 5.1 update notification. I decided to let it download overnight.
The next morning I unlocked my device to find that I couldn't even do that, because pressing the numbers for the pin code did nothing!
Turning it off by holding the power button (the power off option on screen didn't work) only restarted the device. Restarting didn't fix the issue.
Please help! :crying:

cerealtendencies said:
I recently acquired a Nexus 6 last month. Everything was fine until I got the new 5.1 update notification. I decided to let it download overnight.
The next morning I unlocked my device to find that I couldn't even do that, because pressing the numbers for the pin code did nothing!
Turning it off by holding the power button (the power off option on screen didn't work) only restarted the device. Restarting didn't fix the issue.
Please help! :crying:
Click to expand...
Click to collapse
Flash factory using wug's toolkit
http://forum.xda-developers.com/showthread.php?t=2947452

jiv101 said:
Flash factory using wug's toolkit
http://forum.xda-developers.com/showthread.php?t=2947452
Click to expand...
Click to collapse
USB debugging isn't on, so the toolkit wasn't able to identify my device.
How do I turn on usb debugging from a computer? The screen is completely unresponsive so I can't get past my lockscreen

cerealtendencies said:
I recently acquired a Nexus 6 last month. Everything was fine until I got the new 5.1 update notification. I decided to let it download overnight.
The next morning I unlocked my device to find that I couldn't even do that, because pressing the numbers for the pin code did nothing!
Turning it off by holding the power button (the power off option on screen didn't work) only restarted the device. Restarting didn't fix the issue.
Please help! :crying:
Click to expand...
Click to collapse
I had a similar issues with my first Nexus 6 I bought. It worked find for a whole day and then one morning I wasn't able to unlock it and my touch screen wasn't working anymore. Did not flash anything on it-it was 100% stock. I have the feeling you may have the same problem. I am not sure 100% but you may need to contact Motorola for replacement.

jiv101 said:
Flash factory using wug's toolkit
http://forum.xda-developers.com/showthread.php?t=2947452
Click to expand...
Click to collapse
So I managed to unlock bootloader and flash stock via fastboot mode and the device booted up after erasing was done.
The welcome screen appeared and the screen was still unresponsive, I couldn't press anything
I'm worried Motorola's warranty won't cover my device since I bought it from Saudi and I'm currently living in Sudan.
I have an upcoming trip to Malaysia, I'm wondering if I should take it with me there and try to fix the issue.

Weird Error

So lately I'm getting this weird error wherein after the battery drops below 30% and if I try to call or if I receive a call, the phone restarts itself. And after restarting, it completes boot animation, loads "Starting Apps" screen and after that screen just goes blank(ie. Pressing any button is futile at this point of time). This keeps on repeating itself. The only workaround I have found to it is to connect a charger while restarting. After connecting charger the phone boots itself (instead of screen going blank) and works normally.
I'm currently on Cataclysm 6.0.1
Kernel : Elite Kernel
Multi ROM : Installed.
Xposed : Installed
I've tried various kernels and various ROMS combinations (except the stock ones) but the error keeps on repeating itself.
Any help appreciated.

x0nar said:
So lately I'm getting this weird error wherein after the battery drops below 30% and if I try to call or if I receive a call, the phone restarts itself. And after restarting, it completes boot animation, loads "Starting Apps" screen and after that screen just goes blank(ie. Pressing any button is futile at this point of time). This keeps on repeating itself. The only workaround I have found to it is to connect a charger while restarting. After connecting charger the phone boots itself (instead of screen going blank) and works normally.
I'm currently on Cataclysm 6.0.1
Kernel : Elite Kernel
Multi ROM : Installed.
Xposed : Installed
I've tried various kernels and various ROMS combinations (except the stock ones) but the error keeps on repeating itself.
Any help appreciated.
Click to expand...
Click to collapse
an error is when an error screen appears, you arent having an error. first thing first though, completely get xposed off your phone, completely, reflash if need be. i bet this will fix your issue. whenever weird issues appear, and xposed is installed, most likely its xposed.

simms22 said:
an error is when an error screen appears, you arent having an error. first thing first though, completely get xposed off your phone, completely, reflash if need be. i bet this will fix your issue. whenever weird issues appear, and xposed is installed, most likely its xposed.
Click to expand...
Click to collapse
Hi thanks for replying. I've followed your instructions, however the issue still persists.
So this is my current combination
Benzo ROM : 6.0.1
Kernel : Default
Multi ROM : Uninstalled
Xposed : Uninstalled.
The only change that is left to make is to change the recovery from Multi ROM to TWRP.
The most weird part of this problem is that as soon as I make a call or receive a call it restarts and enters into a black screen. However as soon as I connect charger it works normally. That is what bugs me the most. Also my bootloader and Radio are the updated ones. And I checked if there was a log in /sys/fs/pstore but there isn't any.
Please suggest.

x0nar said:
Hi thanks for replying. I've followed your instructions, however the issue still persists.
So this is my current combination
Benzo ROM : 6.0.1
Kernel : Default
Multi ROM : Uninstalled
Xposed : Uninstalled.
The only change that is left to make is to change the recovery from Multi ROM to TWRP.
The most weird part of this problem is that as soon as I make a call or receive a call it restarts and enters into a black screen. However as soon as I connect charger it works normally. That is what bugs me the most. Also my bootloader and Radio are the updated ones. And I checked if there was a log in /sys/fs/pstore but there isn't any.
Please suggest.
Click to expand...
Click to collapse
You're probably not going to like this suggestion, but here goes. In order to confirm or deny a potential hardware defect, you probably should go back to 100% stock. Fastboot flash the factory image for MMB29K. IMHO

Your issue is most likely multi. It has been known to cause random issues.
Your best bet is to make it do it again and grab a logcat or kmsg

zelendel said:
Your issue is most likely multi. It has been known to cause random issues.
Your best bet is to make it do it again and grab a logcat or kmsg
Click to expand...
Click to collapse
I'm willing to do that, but the problem is as soon as I connect it to the charger or USB on my laptop to take out log via ADB it acts normally. So, I believe the log will come out normal. Now the only option left here for me is to Factory Reset, and see how it goes.
To be honest, I never faced this issue while on 5.1.1. This just started out recently. Anyways, thank you.

cam30era said:
You're probably not going to like this suggestion, but here goes. In order to confirm or deny a potential hardware defect, you probably should go back to 100% stock. Fastboot flash the factory image for MMB29K. IMHO
Click to expand...
Click to collapse
Unfortunately that is what I believe I'll have to do.

x0nar said:
I'm willing to do that, but the problem is as soon as I connect it to the charger or USB on my laptop to take out log via ADB it acts normally. So, I believe the log will come out normal. Now the only option left here for me is to Factory Reset, and see how it goes.
To be honest, I never faced this issue while on 5.1.1. This just started out recently. Anyways, thank you.
Click to expand...
Click to collapse
There are apps out there that will do it without being connected to the pc. Try one of those. If it was me I would just drop multi rom all together. It has never been completely stable and most likely never will be.

zelendel said:
There are apps out there that will do it without being connected to the pc. Try one of those. If it was me I would just drop multi rom all together. It has never been completely stable and most likely never will be.
Click to expand...
Click to collapse
I've dropped Multi ROM completely. The issue sad-fully still persists. I have even deleted Kernel Control Apps and any apps that revolve around Root. I really am not aware of what I should be doing next other than formatting and just hoping nothing worse happens. Also could you name a few apps that could take out logcat even while booting. In a surprising twist of events, now as soon as I hit reboot on the phone, it enters into bootloop and does not return back to normalcy, until connected to a charger or PC via USB. So I guess, I could take a logcat. Thank You again.

Redstate and caught in a bootloop

Hi,
So i thought i knew what i was doing and tried to root my 6gb Alpha but apparently i didn't know what i was doing and now i'm stuck in a bootloop with the phone complaining it is in redstate and insecure. I have tried the stock recovery and both cleared cache and factory reset and still nothing. The phone isn't rooted(obviously) anyone one with more knowledge on this have any ideas? I'm about to tear my hair out.

Would advise you flash the old stock ROM. You can find instruction on how to do that in one of many threads in Maze Alpha section of this forum.

Thanks, I tried that with flashtool,now when the phone powers on the backlight comes on and that's it oh I can adjust the volume and it clicks as if the phone is locking when I hit the power button but that's it no images on screen.

Azurewraith said:
Thanks, I tried that with flashtool,now when the phone powers on the backlight comes on and that's it oh I can adjust the volume and it clicks as if the phone is locking when I hit the power button but that's it no images on screen.
Click to expand...
Click to collapse
Sure you flashed the 6GB rom and not the 4GB one?
Maybe try it again and check if there are no errors visible during the flash.
Just found this on the Gearbest blog, which is worth trying first if you flashed the correct rom : https://www.gearbest.com/blog/how-to/solutions-to-maze-alpha-4g-phablet-problems-2018
If the problem still exists, try resetting your phone in the following steps (Note: back up all your important data on the phone, or the data will be wiped after the factory reset):
a. Power off your phone. Then press the Volume up key and Power key at the same time until it navigates to Recovery Mode.
b. Use Volume up/down key to select "Wipe data/Factory reset".
c. Use Power key to confirm.
d. Use Volume key to select "Yes - Delete Alluser".
e. Once the resetting is finished, your phone will reboot automatically. It will take a few minutes to recover. Please wait patiently.

Unfortunately I can't factory reset without a screen. I'll double check the Rom pretty sure it was the correct one, I think it may be a return and play dumb job.

Azurewraith said:
Unfortunately I can't factory reset without a screen. I'll double check the Rom pretty sure it was the correct one, I think it may be a return and play dumb job.
Click to expand...
Click to collapse
So screen doesn't come on at all? Ouch. then I would double check the rom and try to flash again.
I was planning to root my 6GB this weekend but these stories are no good.

Azurewraith said:
Thanks, I tried that with flashtool,now when the phone powers on the backlight comes on and that's it oh I can adjust the volume and it clicks as if the phone is locking when I hit the power button but that's it no images on screen.
Click to expand...
Click to collapse
Please, can you post information on where you downloaded your ROM from and got the instruction? The ROM posted in this thread link below seems to be for Maze Alpha 6GB.
https://forum.xda-developers.com/ma...rom-mazealphabv0420171018-maze-alpha-t3717082

pja1985430 said:
Please, can you post information on where you downloaded your ROM from and got the instruction? The ROM posted in this thread link below seems to be for Maze Alpha 6GB.
https://forum.xda-developers.com/ma...rom-mazealphabv0420171018-maze-alpha-t3717082
Click to expand...
Click to collapse
From the maze gdrive I couldn't get their app to work even following all of the instructions for some strange reason. When trying to root my phone I hit the bootloop then flashing the stock rom from the gdrive with flashtool got me the black screen issue.

Azurewraith said:
From the maze gdrive I couldn't get their app to work even following all of the instructions for some strange reason. When trying to root my phone I hit the bootloop then flashing the stock rom from the gdrive with flashtool got me the black screen issue.
Click to expand...
Click to collapse
So have you been able to flash it again?

lukesan said:
So have you been able to flash it again?
Click to expand...
Click to collapse
No change im afraid I think it's died a death. Its like the phone is fully functional except it just won't display anything.

Azurewraith said:
No change im afraid I think it's died a death. Its like the phone is fully functional except it just won't display anything.
Click to expand...
Click to collapse
Try to use the instruction on the link I posted earlier. It is not dead.

pja1985430 said:
Try to use the instruction on the link I posted earlier. It is not dead.
Click to expand...
Click to collapse
That's what I tried to do initially but their flash tool would never work out never once scanned but my comps where allways different numbers to the ones shown in the screen shots.

Azurewraith said:
That's what I tried to do initially but their flash tool would never work out never once scanned but my comps where allways different numbers to the ones shown in the screen shots.
Click to expand...
Click to collapse
Maybe try to take screenshots of what it is showing on the screen as what you write is very unclear.
Does it detect the phone.
What numbers ....
etc etc

lukesan said:
Maybe try to take screenshots of what it is showing on the screen as what you write is very unclear.
Does it detect the phone.
What numbers ....
etc etc
Click to expand...
Click to collapse
I'll see what I can do tomorrow when I get off work.