I'm using a Rogers Infuse 4G and seem to be having difficulties with my lock screen to prompt for a password/pin.
I had previously rooted my phone, and used MIUI, Infused, and a few other ROM's. the issue started on my last install of Infused. If I set a password, or pin it prompts, prompts for confirmation then goes back to the password options screen.
When I lock my device, or reboot, it does not prompt for the PIN/Password. Strangely enough, Pattern works, but, because I use my phone on an exchange email system, I'm forced to use a password/pin.
So I decided that maybe the ROM was bad, so I redownloaded and flashed the device, clearing cache, user data and dalvik cache. Same issue. Failing that, I used ODIN to reload a stock rooted Rogers PDA and Phone image back on to the device.
Rebooted, ran SuperOneClick to Unroot the device, and I have the same issue. Are the infuses like iPhones, where the PIN is stored in a hardware chip? Is it possible that, if this is the case, that chip is somehow not functioning?
I'm having difficulties figuring out why a Rogers Infuse Gingerbread ROM can't update the security settings
Any help is appreciated
Bump.
Anyone have any ideas as to why this is happening? I've tried re-flashing using ODIN and a PIT file + PDA_UXKG3_rooted_no_bootloaders_v2.tar.md5 and PHONE_UXKG3.tar.md5
For whatever reason, my phone still refuses to save whatever password I put in for the lock screen.
Related
I'm at a loss here. I was using my phone as normal today, no issues all day. When I tried loading Facebook to respond to a comment I suddenly started getting a lot of stopped process errors. Pretty much all were GAPPS processes. Then my phone rebooted. After it booted back up (no issues, no subsequent reboots, saw the HTC screen and the ViperXL screen), my phone loads to an empty lock screen with the default ViperXL background and just the ring. The phone is also now in Airplane mode and showing the time to be 5 hours ahead. When I unlock the phone, I am met with a screen that tells me to "Type password to decrypt". I have never created a password. Nothing works. I can only make emergency calls. No amount of rebooting or wiping cache or dalvik in TWRP works. I have not updated this phone recently and when I try to restore from backup none of my backups show up in the TWRP folder. I cannot do a factory reset as I receive errors when attempting to mount the SD card. I've read several other forum posts for similar issues for different devices but none of what they try works. My computer recognizes when the phone is connected, but it does not mount the SD Card and I cannot put the ROM .zip file back onto it to reinstall from recovery. I cannot adb as it doesn't recognize the device as being connected. I can initiate fastboot and it does see my device, but when I try to erase the userdata partition or anything else I receive an error that states "failed (remote: not allowed)". All instincts would lead me to believe it's a locked bootloader, but the bootloader screen still shows as UNLOCKED. I am S-Off on HBOOT 1.14.0002. Currently ViperXL 3.2.6 is installed with ElementalXL 5.4 for the kernel and the AT&T 3.18 Radio. Again, I have not TOUCHED my setup in over 3 weeks, with the last update being the updated radio. I am freaking out without any means to communicate with my family and just want an operational phone again. Any ideas/thoughts/suggestions would be greatly appreciated.
Pdj7969 said:
I'm at a loss here. I was using my phone as normal today, no issues all day. When I tried loading Facebook to respond to a comment I suddenly started getting a lot of stopped process errors. Pretty much all were GAPPS processes. Then my phone rebooted. After it booted back up (no issues, no subsequent reboots, saw the HTC screen and the ViperXL screen), my phone loads to an empty lock screen with the default ViperXL background and just the ring. The phone is also now in Airplane mode and showing the time to be 5 hours ahead. When I unlock the phone, I am met with a screen that tells me to "Type password to decrypt". I have never created a password. Nothing works. I can only make emergency calls. No amount of rebooting or wiping cache or dalvik in TWRP works. I have not updated this phone recently and when I try to restore from backup none of my backups show up in the TWRP folder. I cannot do a factory reset as I receive errors when attempting to mount the SD card. I've read several other forum posts for similar issues for different devices but none of what they try works. My computer recognizes when the phone is connected, but it does not mount the SD Card and I cannot put the ROM .zip file back onto it to reinstall from recovery. I cannot adb as it doesn't recognize the device as being connected. I can initiate fastboot and it does see my device, but when I try to erase the userdata partition or anything else I receive an error that states "failed (remote: not allowed)". All instincts would lead me to believe it's a locked bootloader, but the bootloader screen still shows as UNLOCKED. I am S-Off on HBOOT 1.14.0002. Currently ViperXL 3.2.6 is installed with ElementalXL 5.4 for the kernel and the AT&T 3.18 Radio. Again, I have not TOUCHED my setup in over 3 weeks, with the last update being the updated radio. I am freaking out without any means to communicate with my family and just want an operational phone again. Any ideas/thoughts/suggestions would be greatly appreciated.
Click to expand...
Click to collapse
You're s-off. Boot bootloader/fast boot and ruu
Sent from my One X using xda app-developers app
We're you connected to an exchange server? It is the only thing that I know of that could wipe or encrypt your phone.
Sent from the HOXL dimension of S-OFF
Well this is a new one on me. Not sure what happened or how I did it, but as you can see below, I managed to get my phone working again. I left it alone for a bit while I had dinner. Once done, I tried once again to do a factory reset in TWRP and all indications led me to believe that it had failed once again (received a failed notification). I then rebooted the phone and this time it brought me to the HTC setup screens where I was to enter all my info. I got past that and connected to my wifi. I then noticed my phone wouldn't get a network connection with AT&T so I downloaded and refreshed the 3.18 radio and after reboot it connected to LTE without issue. Since I lost all my data I am now in the process of reinstalling my apps. I had been meaning to do a full wipe eventually as things were getting a little sluggish, so I guess this just kicked me in the pants a bit. Bummed I lost my photos I took today, but what can you do?
To answer your question, no, I do not have it setup with Exchange. My company does not allow Android devices to connect to Exchange, only iPhones via ActiveSend so that wasn't it. This has happened to several others, but they were always in the act of flashing something or making changes when it happens, never just normal use and a magical reboot kills everything. This of course makes me nervous that it'll happen again, but seeing as I am in the market for the One, I might not have to worry much longer. Thanks for the suggestions.
Sent from my HTC One X using xda app-developers app
As long as you can get into bootloader you can always run the ATT 3.18 RUU.
Sent from the HOXL dimension of S-OFF
Hi,
I'm using an unlocked Nexus 5, and flashed as soon as the factory image was released. I used CF-Autoroot to gain root access.
The problem that I'm having is that the lock screen does not work. This means that when I lock the phone (power button), it just fades to black, but when I hit the button again (either immediately, or after a wait), I go straight to where I was, the lock screen does not activate no matter what I do. I've tried letting it time out, still no luck.
When I restart the phone, it shows the lock screen, but sounds like something is trying to unlock the phone, and the phone then unlocks and doesn't lock again. I've tried disabling all Device Administrators, with no luck. I tried a factory reset and then a re-flash followed by another factory reset, and the problem still persists. I've also tried toggling Smart Lock on and off, still no change.
If I go to the security settings and re-select a Screen Lock mode, then the lock screen shows up again, but after I unlock, it goes away never to return.
This has been extremely frustrating, since Smart Lock was one of the features I was most looking forward to. Does anyone know what could be causing this?
The current Root apps that I use are:
1. SuperSU (obviously) 2.23 BETA
2. BusyBox Free
3. AutomateIt Pro
4. Greenify
5. Power Toggles
6. AdAway
7. Titanium Backup
Another note: After the factory-reset, wipe, flash, factory-reset that I did, I restored all non-system Apps and data with Titanium Backup. Just putting this here in case you guys know of any app that causes this problem.
Ekitrak said:
Hi,
I'm using an unlocked Nexus 5, and flashed as soon as the factory image was released. I used CF-Autoroot to gain root access.
The problem that I'm having is that the lock screen does not work. This means that when I lock the phone (power button), it just fades to black, but when I hit the button again (either immediately, or after a wait), I go straight to where I was, the lock screen does not activate no matter what I do. I've tried letting it time out, still no luck.
When I restart the phone, it shows the lock screen, but sounds like something is trying to unlock the phone, and the phone then unlocks and doesn't lock again. I've tried disabling all Device Administrators, with no luck. I tried a factory reset and then a re-flash followed by another factory reset, and the problem still persists. I've also tried toggling Smart Lock on and off, still no change.
If I go to the security settings and re-select a Screen Lock mode, then the lock screen shows up again, but after I unlock, it goes away never to return.
This has been extremely frustrating, since Smart Lock was one of the features I was most looking forward to. Does anyone know what could be causing this?
The current Root apps that I use are:
1. SuperSU (obviously) 2.23 BETA
2. BusyBox Free
3. AutomateIt Pro
4. Greenify
5. Power Toggles
6. AdAway
7. Titanium Backup
Another note: After the factory-reset, wipe, flash, factory-reset that I did, I restored all non-system Apps and data with Titanium Backup. Just putting this here in case you guys know of any app that causes this problem.
Click to expand...
Click to collapse
I'm facing the same issue with my NON-rooted Nexus 4.
Anybody having any ideas?
Arijit
arijitmaniac said:
I'm facing the same issue with my NON-rooted Nexus 4.
Anybody having any ideas?
Arijit
Click to expand...
Click to collapse
Mine fixed itself after I manually installed the latest Google Play Services apk. Maybe try that and see if it works for you...
Cant flash Cyanogen, recovery faulty & weird crashes in stock on refurbished Nexus 5
Hey guys,
so I recently got a "refurbished" replacement for my Nexus 5 and I decided since im starting out fresh (can't access the data on the old one), I'll try out Cyanogen mod.
I can assure you that I followed all the instructions exactly. At some point I checked every download for his checksums and all were ok.
Each time I started the process by flashing a factory image (flash-all.bat), to have a clean start.
I also tried to wipe cache/dalvik cache/data afterwards, but not always. This didn't change the behavior.
These things happened to me while trying to accomplish the task, and working around the issues as they arised:
Flashing TWRP: High (3 of 4) chance that TWRP wouldn't even start up, the phone would hang and just flash the TWRP background picture on screen.
When I did get through to TWRP, applying the Cyanogenmod .zip got stuck at "patching system image unconditionally". Let it go on for hours.
I figured that TWRP was broken and tried Clockworkmod instead. CWM at least always started after flashing it. But same as TWRP, it failed in installing the Cyanogenmod .zip. I tried putting it onto the phone by going into the stock android and then through adb push command, but also through sideloading directly into CWM.
What I noticed when going into the stock ROM was, that a lot of Google processes were failing during the initial setup (where it wants to know ur WiFi, date, Google acc, etc), like Maps, Settings, Play Services, and some others. Sometimes they were failing so hard it was impossible to type in the WiFi passphrase because the notifications of different "xxx has stopped working" were coming to fast, sometimes not a single one was failing. I could not find any pattern to this. When they were failing so hard I couldn't get through the initial setup I would just flash the stock again, until I got only some of them failing, or none at all.
Back to CWM and installing the Cyanogenmod .zip:
It failed with different errors. I got status 0, status 1, I think I once got status 6 or 7, but half of the time it hanged exactly where TWRP was hanging. The errors were random. After getting status X, I would sideload it right again, to get other status Y, sideload again, to get the hang. Could not recognize a pattern.
During this I switched USB ports, and cables, and even tried using my laptop instead of the desktop. One of the cables was faulty, it didn't even allow a connection, but any other setup showed the same behaviour.
Is there anything else I can/should try? Is it my fault, or is the phone bad?
Assuming the phone is bad, I suppose I still could get a stock running without the crashes, so it would _feel_ like the phone is alright (which is what Google probably did before sending it out again as "refurbished"), but I think there would be errors in the future, also I don't want a phone with such an uncertainty. Would they swap it? Also, it is a LG-D820, which means it might have issues with european LTE, haven't gotten to trying that out since I don't use LTE right now, nor will I in the near future.
Best regards,
napster
napstr said:
Hey guys,
so I recently got a "refurbished" replacement for my Nexus 5 and I decided since im starting out fresh (can't access the data on the old one), I'll try out Cyanogen mod.
I can assure you that I followed all the instructions exactly. At some point I checked every download for his checksums and all were ok.
Each time I started the process by flashing a factory image (flash-all.bat), to have a clean start.
I also tried to wipe cache/dalvik cache/data afterwards, but not always. This didn't change the behavior.
These things happened to me while trying to accomplish the task, and working around the issues as they arised:
Flashing TWRP: High (3 of 4) chance that TWRP wouldn't even start up, the phone would hang and just flash the TWRP background picture on screen.
When I did get through to TWRP, applying the Cyanogenmod .zip got stuck at "patching system image unconditionally". Let it go on for hours.
I figured that TWRP was broken and tried Clockworkmod instead. CWM at least always started after flashing it. But same as TWRP, it failed in installing the Cyanogenmod .zip. I tried putting it onto the phone by going into the stock android and then through adb push command, but also through sideloading directly into CWM.
What I noticed when going into the stock ROM was, that a lot of Google processes were failing during the initial setup (where it wants to know ur WiFi, date, Google acc, etc), like Maps, Settings, Play Services, and some others. Sometimes they were failing so hard it was impossible to type in the WiFi passphrase because the notifications of different "xxx has stopped working" were coming to fast, sometimes not a single one was failing. I could not find any pattern to this. When they were failing so hard I couldn't get through the initial setup I would just flash the stock again, until I got only some of them failing, or none at all.
Back to CWM and installing the Cyanogenmod .zip:
It failed with different errors. I got status 0, status 1, I think I once got status 6 or 7, but half of the time it hanged exactly where TWRP was hanging. The errors were random. After getting status X, I would sideload it right again, to get other status Y, sideload again, to get the hang. Could not recognize a pattern.
During this I switched USB ports, and cables, and even tried using my laptop instead of the desktop. One of the cables was faulty, it didn't even allow a connection, but any other setup showed the same behaviour.
Is there anything else I can/should try? Is it my fault, or is the phone bad?
Assuming the phone is bad, I suppose I still could get a stock running without the crashes, so it would _feel_ like the phone is alright (which is what Google probably did before sending it out again as "refurbished"), but I think there would be errors in the future, also I don't want a phone with such an uncertainty. Would they swap it? Also, it is a LG-D820, which means it might have issues with european LTE, haven't gotten to trying that out since I don't use LTE right now, nor will I in the near future.
Best regards,
napster
Click to expand...
Click to collapse
Hi.
According to what you say, it seems an hardware problem of you phone. Don't know if it may help but you can try installing an older factory image (for example kitkat) and seeing if the "force closing" problems are still there. If your phone is ok it should be able to run a factory image at least.
Download the nexus root toolkit, create a nandroid backup, then when either in CWM or TWRP wipe everything off the phone then try to flash a ASOP rom like Cataclysm if nothing else works then I don't know how to help sorry-.-
So I tried to get the stock ROM up and running again, and it seems even that is not possible. Several processes keep crashing during various tasks, even when idling. After having a short chat with Google Support about the issues I got an RMA offered, so things are cool. I locked the phone again, set the tamper-bit to false and wiped everything.
Stock Galaxy S7, no root, no dubious apps, only AirWatch Agent: play.google.com/store/apps/details?id=com.airwatch.androidagent required for installing a corporate email client on the personal phone.
Everything worked fine for months, until yesterday, when the app AirWatch crashed, and would not start.
The user decided to reboot the phone. On the reboot, the phone got stuck on the second Samsung logo animation.
Wipe cache, force restart, reboot, reboot bootloader were tried, hoping to fix this boot issue, but without success. The phone still stays stuck at the Samsung logo animation.
What I'm looking for: to avoid phone ROM reflashing, because it has no backup and the data on the microSD card is encrypted.
I want to recover the personal data, by any means.
Any suggestions on how to achieve this?
Thank you.
If you can't flash stock, and have already wiped cache, and the guy doesn't have a backup (dumb), then there's not much else you can do really
I'm not sure which part of the phone the encryption key is stored, but you could try flashing just the Bootloader part of the ROM with ODIN
Also not sure if flashing the same stock ROM over the top, but using HOME_CSC instead of CSC to avoid the factory reset, would mess up the encryption, but as a last resort it would be what I would do
Backups are good, if the data is so important to encrypt I can't see why it would not also be backed up
I understand your point and I agree with it.
As a sidenote, that encryption was required by the app AirWatch, not by the phone's owner.
We'll try those steps as a last resort, but for the moment, we're gathering information, since most of the options are a "no way back" process.
For example, I'm thinking about a way to inspect the boot process, and alter it if there's something there that hangs.
Could this be possible? Is there any documentation about this?
germanino said:
I understand your point and I agree with it.
As a sidenote, that encryption was required by the app AirWatch, not by the phone's owner.
We'll try those steps as a last resort, but for the moment, we're gathering information, since most of the options are a "no way back" process.
For example, I'm thinking about a way to inspect the boot process, and alter it if there's something there that hangs.
Could this be possible? Is there any documentation about this?
Click to expand...
Click to collapse
You could trying running a logcat with the phone connected to USB during boot, not sure if it will connect to adb though, worth a shot
https://www.xda-developers.com/install-adb-windows-macos-linux/
If it works it should show you what it's hanging on, no idea how you would fix it though without a custom recovery
Ok Masters, so I am having the same issue that this guy here:
https://forum.xda-developers.com/ga...mand-error-samsung-galaxy-j7-prime-s-t3929850
I can install any rom. However, the pin to register either face or fingerprint, does not work. So I cannot even get to the fingerprint screen because it returns me to enter pin, and when I re-enter it, it says is wrong. I guess it has something to do, the fingerprint so far, had just worked on Cerberus AOSP rom, but neither on one UI nor 8.1 based roms work. on 8.1 I get setting had stopped.
So, flash stock over odin was already tried and it gets stuck there. Already flashed no verity, no luck, flashed, bbos, godness, venom, no luck.
Any other advice? Seems that somehow I messed up with the encryption and that is making not registering the pin or pattern.
I managed to pass the screen with Magisk, but as soon as system boots and I try to set fingerprint, it says settings stopped. I am really frustrated now.
Thanks,
This was already solved. If anyone is interested in getting more details he they are:
The no command was because someway somehow, the system partition was "busy " or non-writteable, at least that was the message that I was able to read. I don't know how it got to that state, but my solution was the following:
- Select system partition in twrp and tapped on repair file system. I got an error immediately that twrp could not read system block. I changed file system to ext2 and rebooted twrp.
- once again I clicked on repair file system. No errors this time. Rebooted twrp. Changed file system to ext4. Rebooted twrp. Repaired file system again and rebooted twrp once again. Downloaded an aosp 8.1 rom and setted screen lock after the set up, it worked. Then, installed apollo v1. Screen got frozen for a second when setting pin, but it let me pass to set my fingerprints.
Then I knew that it was already working. Installed a One Ui rom to try and it worked again my screen lock with finger print.
Hopefully this helps someone as I found no solution whatsoever in any part of forums or internet, this was pure trial an error over 4 days.