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.
Related
Unfortunately my OnePlus is no longer able to function and would like some assistance/suggestion from the community.
OnePlus has TWRP installed
- installed Paranoid Android rom = no issues
- enabled encryption
Now here is where the issue occurs.
When I start the phone I am able to see the PA bootup screen, it prompts me to enter the password. Once the password is entered "bugdroid" appears on the screen for a quick flash and then disappears. The screen continue to stay blank/black with no further progress, I have left the phone in this state for at least 20mins but it still doesn't proceed further. It should also be noted the the soft keys STAYS lit once the password has been entered for decryption.
I am still able to boot into recovery, enter my password to decrypt and use the standard TWRP functions. It should be noted that unfortunately I haven't done a backup on the phone at all {something that I totally regret right now), plus there is no rom left on the phone for me to attempt a install.
Any help is appreciated
note: the phone as able to complete its bootup process when I initially activated encryption but has failed ever since the first reboot
There are multiple threads discussing this in the very section you posted this thread in. Have a look, you'll find what you need.
Transmitted via Bacon
I have a Samsung Galaxy S5 mini on stock rom, rooted. I was looking through Xposed for new possibly interesting modules. I installed one which said you can set volumes to have more than 15 points. So I installed it but I did not reboot yet figuring that I would do that later. I made all new backups of my apps and data using Titanium backup and then tried to reboot my phone but the reboot menu button would not work and the screenshot button at the top was blank yet functional. So I loaded up, or attempted to load up Wanam Xposed to check what was going on since that is what configures my rom and it said the app was not installed when I pressed on the shortcut.
So I rebooted the phone, entered the encryption password, it came up to the lock screen and from that point it would say my password did not match. I tried every password I have ever used, varying case and everything. No password worked. I had not manually changed it either. I had no choice but to factory reset the phone and format the SD card. Also I should mention that when I found out that wanam xposed was not seemingly installed any more, I attempted to install it and it would just say "App was not installed" or something. Then I installed Wanam Toolbox or something, I forget exactly now, but that installed and I rebooted and that's when I noticed my lock screen password was not working.
Any ideas on what the cause may have been and what things I could attempt to do if it ever happens again? I thought there was a thing where you can use your google account to unlock the phone but I could not get that thing to come up.
I am running stock ROM and have bootloader unlocked and TWRP already installed. The phone was rooted without problems. I was getting an error from Super SU, so I looked up how to fix it online and the suggestion was to install an older version and then try to upgrade it. It was hard to find a zip from a legitimate source but once I found it, TWRP did not show the directory I was looking for (this was previously available when I rooted it). This is where I did something stupid and looked around in the settings and found the Slot A / Slot B option. I switched from B to A and the phone got stuck on the boot animation for several minutes after rebooting. I decided to reboot into TWRP and switched the slot back to B. This brought the phone back but WiFi is off by default and whenever I try to turn it on, it doesn't change.
I have seen a couple of other people mention similar issues about losing wifi after a root or changing the slot. What's the fix? I am wondering if there is anything else "broken" after the slot change and if I should do a factory reset (I would hate to do that as I was almost finished setting up this device). I have also received the error message saying "Process System isn't responding" in the settings menu a few times. It also seems like the finger print scanner isn't recognizing fingerprints any more and face unlock isn't working
One possibility is, that SuperSU isn't that compatible anymore. Magisk does a wonderful job and no problems so far. Maybe you should give it a try and switch from using SuperSU to Magisk.
shagexpert said:
I am running stock ROM and have bootloader unlocked and TWRP already installed. The phone was rooted without problems. I was getting an error from Super SU, so I looked up how to fix it online and the suggestion was to install an older version and then try to upgrade it. It was hard to find a zip from a legitimate source but once I found it, TWRP did not show the directory I was looking for (this was previously available when I rooted it). This is where I did something stupid and looked around in the settings and found the Slot A / Slot B option. I switched from B to A and the phone got stuck on the boot animation for several minutes after rebooting. I decided to reboot into TWRP and switched the slot back to B. This brought the phone back but WiFi is off by default and whenever I try to turn it on, it doesn't change.
I have seen a couple of other people mention similar issues about losing wifi after a root or changing the slot. What's the fix? I am wondering if there is anything else "broken" after the slot change and if I should do a factory reset (I would hate to do that as I was almost finished setting up this device). I have also received the error message saying "Process System isn't responding" in the settings menu a few times. It also seems like the finger print scanner isn't recognizing fingerprints any more and face unlock isn't working
Click to expand...
Click to collapse
I had the same issue when I first got my 6 when I was playing around with the slots. Also my original TWRP install for some reason would crash and reboot whenever I plugged in the data cable while in TWRP. I ended up flashing back to stock OOS 5.1.5 through fastboot (used the flash-all command) and then reinstalled TWRP and everything has been working great since then.
MickyFoley said:
One possibility is, that SuperSU isn't that compatible anymore. Magisk does a wonderful job and no problems so far. Maybe you should give it a try and switch from using SuperSU to Magisk.
Click to expand...
Click to collapse
The instructions I followed already installed Magisk to the phone. I wanted Super SU because some of the other chainfire apps like Liveboot and rooted apps like Titanium backup said Super SU is needed (Titanium said Magisk will work but may not be reliable for some newer versions of the ROM). I can live without liveboot but really need Titanium to reliably transfer data from my older phone.
To be honest I didn't know they did the same thing (magisk and Super SU). I am curious now, what if I factory reset my phone and attempted to install Super SU instead of Magisk this time?
If I do a factory reset (let's say I want it just like it was out of the box and I format the data partition as well), will I need to root the phone again? I am asking because I don't know which part of the instructions I should ignore. I am sure TWRP will already be installed after the reset so I would only need to install the extra apps...
You don't have to format data. Just factory reset it. Then use "fastboot boot twrp.img", don't allow modifications, flash a kernel you want (if you want one - I really recommend ElementalX) and then the latest version of Magisk (16.4 BETA currently). Did so - all fine. And yes: Even Titanium Backup works without any issue with Magisk.
We had similar problems with TWRP on the Razer Phone when it was new. We solved the problem by using the TWRP boot image to flash the stock boot image and then flashing a TWRP zip. I just got the OnePlus 6 yesterday and haven't really messed with it yet but everything sounds the same to me so far.
I read more about TWRP and realized what I was doing wrong when the directory with zip files wasn't showing up. When TWRP showed up I was supposed type in my regular unlock password to decrypt storage. When I did that the folder I was looking for showed up. I made a backup through recovery (which took like an hour, may be because the external flash drive I attached was really slow - and the size of the backup was about 12GB). After that I installed the zip file for Super SU, just to see if it worked - it showed the installation was successful but the app was still missing from the app drawer. Now I wanted to factory reset the device and start over.
I went into wipe and there was nothing listed under the wipe screen. I went into Advanced wipe and wiped whatever was selected by default. The selected items were Dalvik / ART Cache, System, Data. There was also "Internal Storage and USB Storage" that wasn't selected.
I swiped to wipe, it wiped everything. Then asked reboot, I rebooted, got a blank screen with white LED for a long time. When I plugged it into the computer it recognized the device as Qualcomm HS-USB Diagnostics 900E (COM4). I rebooted it by holding Power + Volume Up + Volume Down. I tried to boot into boot loader next. This brought me to another blank screen. The computer still makes a noise when it reboots but screen stays black. The only message that shows up is the one saying boot loader is unlocked. Did I brick my phone? This keeps getting progressively worse.
shagexpert said:
I read more about TWRP and realized what I was doing wrong when the directory with zip files wasn't showing up. When TWRP showed up I was supposed type in my regular unlock password to decrypt storage. When I did that the folder I was looking for showed up. I made a backup through recovery (which took like an hour, may be because the external flash drive I attached was really slow - and the size of the backup was about 12GB). After that I installed the zip file for Super SU, just to see if it worked - it showed the installation was successful but the app was still missing from the app drawer. Now I wanted to factory reset the device and start over.
I went into wipe and there was nothing listed under the wipe screen. I went into Advanced wipe and wiped whatever was selected by default. The selected items were Dalvik / ART Cache, System, Data. There was also "Internal Storage and USB Storage" that wasn't selected.
I swiped to wipe, it wiped everything. Then asked reboot, I rebooted, got a blank screen with white LED for a long time. When I plugged it into the computer it recognized the device as Qualcomm HS-USB Diagnostics 900E (COM4). I rebooted it by holding Power + Volume Up + Volume Down. I tried to boot into boot loader next. This brought me to another blank screen. The computer still makes a noise when it reboots but screen stays black. The only message that shows up is the one saying boot loader is unlocked. Did I brick my phone? This keeps getting progressively worse.
Click to expand...
Click to collapse
OK good news! I tried one more time and fast boot showed up. I was able to get into recovery. I have the backup so I will try to restore that. I don't know what to do after that. I am thinking wiping without getting into advanced mode.
shagexpert said:
OK good news! I tried one more time and fast boot showed up. I was able to get into recovery. I have the backup so I will try to restore that. I don't know what to do after that. I am thinking wiping without getting into advanced mode.
Click to expand...
Click to collapse
When your phone booted straight into that mode with black screen and the led, then you bricked it. Same happened to me 2 days ago. The solution was to use the Msmtool from another thread and it worked great. Just follow the guide. But it will wipe your device. And you have to install oxygenos manually via "local upgrade". If you have a question, just ask
What I ended up doing was restoring from the backup I had. This was the "bad backup" without WiFi and broken finger print and facial recognition. After the restore, I did a normal wipe (not advanced). This reset the phone to factory settings. Once I configured WiFi and signed into my Google account, Google offered to recover from a cloud backup of my One Plus - I didn't know Google made these backups. It downloaded all the apps automatically. I don't know yet if I have sign into all of them all over again.
The bad back up saved my ass, I wasn't even planning on making it. I was just testing the backup feature. That's why you should always do a backup, even if the device isn't in ideal configuration.
shagexpert said:
The instructions I followed already installed Magisk to the phone. I wanted Super SU because some of the other chainfire apps like Liveboot and rooted apps like Titanium backup said Super SU is needed (Titanium said Magisk will work but may not be reliable for some newer versions of the ROM). I can live without liveboot but really need Titanium to reliably transfer data from my older phone.
Click to expand...
Click to collapse
I rooted my phone with Magisk and installed the 5.1.6 via OTA (and reroot via installed Magisk Manager). So no need to install TWRP so far.
Titanium Backup runs flawlessly with Magisk (already on my OP 3T and my OP 5).
So give Magisk a try, I never had such an easy and reliable update as the one from 5.1.5 to 5.1.6
Helium is a great alternative to titanium.
Has anyone else had this happen to them? Phone stopped responding, so I tried to force a reboot; it wouldn't recognize my pattern anymore, so I booted into TWRP and deleted locksettings.db, whereupon system hung up on "Android is Starting". So, went back to TWRP to attempt to wipe data, and phone would not let me set up; just stayed on "Just a sec" progress bar.
I'm at the point where I'm about to install a factory image and start fresh. Ideas?
Mine told me that the pattern wasn't correct, so my first move was to boot to twrp. Since that took my pattern, I knew that it wasn't incorrect, so I just booted straight without altering anything. It ended up accepting my pattern that time. I've had it happen a few times that it didn't recognize my pattern, then after a reboot, it was fine.
lightningdude said:
Mine told me that the pattern wasn't correct, so my first move was to boot to twrp. Since that took my pattern, I knew that it wasn't incorrect, so I just booted straight without altering anything. It ended up accepting my pattern that time. I've had it happen a few times that it didn't recognize my pattern, then after a reboot, it was fine.
Click to expand...
Click to collapse
I unfortunately didn't get it that easy...had to do a factory reset.
Oddly, this happened right after I got locked out of my Facebook account...
this morning, my gps wasn’t working and i did a reboot, since then my phone won’t start anymore. originally: bootloader unlocked, twrp installed, magisk as well.
after typing in the security pin, it was stuck. i assumed there was some problem with that, so i went into twrp and deleted those lock settings files, reboot, now i’m at "phone is starting" after each reboot now and i can access settings and basic stuff, but no home or anything, and tapping on system update tells me that the app is not responding ("settings keeps stopping"). booting into twrp asks for a pin which does NOT work anymore (neither my original one, nor 0000 or default_password).
i used magisk uninstaller (sideloaded), and reflashed what i assumed was an OTA-zip from the oneplus website, so i’ve got stock recovery installed now (bootloader still open), but otherwise not much changed - after booting i can basically only access settings (from the quick settings bar), nothing else works.
i ASSUME it has got something to do with not being able to decrypt data anymore. i also assumed i can just reflash the 2gb-zip from oneplus and that would include a fresh system/boot img and deleting those lock files from twrp would remove decryption, but i guess i was wrong.
other that formatting data now .. any recommandations/suggestions? any help would be greatly appreciated. :/
could be stock launcher is frozen or disabled?
it did this to me, even if I had another launcher.
virtyx said:
could be stock launcher is frozen or disabled?
Click to expand...
Click to collapse
thanks for your guess - but, no, not disabled, i can see it in the list of apps. the only app "disabled" was the oneplus gallery, switched that back on, no effect ..
frank93 said:
thanks for your guess - but, no, not disabled, i can see it in the list of apps. the only app "disabled" was the oneplus gallery, switched that back on, no effect ..
Click to expand...
Click to collapse
wipe cache in recovery
virtyx said:
wipe cache in recovery
Click to expand...
Click to collapse
tried that, didn’t work. and even after a "factory reset", starting from the "hello!"-page from scratch, everything stopped on the next page ("just a sec ..") - so i guess there was something seriously wrong with my data partition. not sure why though.
after formatting data (and crying during those few seconds) it "worked" again, now, and fortunately i had some kind of app backup at least, but ..
yeahwell.
frank93 said:
tried that, didn’t work. and even after a "factory reset", starting from the "hello!"-page from scratch, everything stopped on the next page ("just a sec ..") - so i guess there was something seriously wrong with my data partition. not sure why though.
after formatting data (and crying during those few seconds) it "worked" again, now, and fortunately i had some kind of app backup at least, but ..
yeahwell.
Click to expand...
Click to collapse
very strange
maybe the restricted. XML file was stuck
no point trying since you formatted
four hours later, fresh setup - it’s starting to happen again, sudden "hangs" and "phone is starting .." out of nowhere, then "system ui is not responding", force reboot, .. working right now, but there’s something really fishy and i’m starting to assume it’s a hardware thing.
I'm having the same issue after rebooting to fix gps/mobile data issues. Any other solutions?