Hi all. had an issue while trying to load up LinageOS last night. Was having trouble with keeping root. Seem to have solved that by using Magisk 11.6 and the SUaddon rather than any superuser version.
Anyhow as part of this i went back to a TWRP backup of which i had 3 different versions (stock and lineage) available being a bit ocd with backups. They all flashed ok, but for ALL of them, when the phone booted it kept telling me had wrong pattern when i tried to unlock. Not good. Thought only way back was to factory reset and do all the app loading and setup again.
After a bit of searching found this thread and this post.
https://forum.xda-developers.com/showpost.php?p=69189392&postcount=65
Worked a treat.
The other methods didn't and i suspect are obsolete.
Anyow, posted for info if anyone else runs into this problem. Success dependent on having working TWRP and being able to boot to that as you need to use the File Manager capability in TWRP.
Seeyahs!
Same thing happened to me last week, when I tried lineage, found the answer on HTC forum,.
So avoid that from happening , before you make a backup, unlock all securities( pin, password, fingerprint) then make a backup, next time you restore your backup, it will boot without any issues.
ta for that. will try.
Related
I apologize if this is already covered in another thread. I wasn't able to find anything.
I am having an issue with restoring a backup I created in TWRP. I backed up only System and Data. I was able to restore one backup but then realized I forgot to remove my lock screen security (I have since found a way to fix this issue in another thread). Then when I tried restoring a different one, backed up the same way, I got a bootloop. I got the bootloop with two different backups.
I let it sit for about 10 minutes on the boot animation. Do I need to wait longer?
bretrick30 said:
I apologize if this is already covered in another thread. I wasn't able to find anything.
I am having an issue with restoring a backup I created in TWRP. I backed up only System and Data. I was able to restore one backup but then realized I forgot to remove my lock screen security (I have since found a way to fix this issue in another thread). Then when I tried restoring a different one, backed up the same way, I got a bootloop. I got the bootloop with two different backups.
Also, when starting the restore it gave me the option to restore Data, System, and EFS. I only checked Data and System. Is that correct?
I let it sit for about 10 minutes on the boot animation. Do I need to wait longer?
Click to expand...
Click to collapse
I feel your pain. Many people have the same restore problem, and it is unclear to me ( from reading) how to get the recovery working well so one can go back and forth between several roms, including a stock rom. Dees Troys' instructions, for first time Omnirom installers, states that once TWRP is installed, you not only do the TWRP factory reset, but you must format the data partition if you previously had a stock encrypted rom on your device. You will lose all data if you do this, but I think this is the only way to have a fully functional TWRP recovery. I haven't tried this yet, but probably will when I have hours of spare time.
bretrick30 said:
I apologize if this is already covered in another thread. I wasn't able to find anything.
I am having an issue with restoring a backup I created in TWRP. I backed up only System and Data. I was able to restore one backup but then realized I forgot to remove my lock screen security (I have since found a way to fix this issue in another thread). Then when I tried restoring a different one, backed up the same way, I got a bootloop. I got the bootloop with two different backups.
I let it sit for about 10 minutes on the boot animation. Do I need to wait longer?
Click to expand...
Click to collapse
Sent from my Nexus 6P using Tapatalk
Hello all
I am having a little bit of trouble with my TWRP recovery after flashing an updated version of a custom ROM, i have been using for a while.
I am using the latest version of the Pure Nexus ROM, and am currently un-rooted. I earlier want to try and clear my davlik cache as i was having a few little issues with some things, and wiping this has previously fixed the issue, i rebooted into the TWRP, and was asked for a password, which i thought would have been the PIN i use to unlock my phone. This then failed, and it proceeded to try and decrypt the partition. I left it doing this for about 20 mins, but nothing happened.
After reading up a little more, and trying a few different potential passwords to no avail, i read up that the password that TWRP was asking me for was related to the fact i had my phone set to ask for password on boot.
I removed this, and tried again. This time, TWRP just got stuck on the splash screen when trying to boot. Nothing happened for a good 10 minutes.
After putting the PIN settings back on, it goes back to asking for a password, that it wont take.
Whats my next option here, im kinda stuck. I really dont want to have to wipe the phone as i have just spent the best part of a week after flashing my new ROM getting it all back to how it was after flashing the new custom ROM i am using..
All help, much appreciated, thanks in advance
What version of TWRP are you using ?
No issues on TWRP 3.2.0.3
Sent from my Nexus 6P using Tapatalk
I'm on version 30.20
I got a notification for system update. When I rebooted, my tablet started up in TWRP. The update finished (I don't Know if it was successful or not). After I rebooted into system, my usual PIN is not working, do I can't get access. I'm away from home and away from my PC for a couple of weeks, so I'm limited in what I can do.
Does anybody know how to get a PIN to work? Looks like TWRP has been replaced with regular recovery on partition 1, but I have TWRP on partition 2 also. Is there a way to get into TWRP on partition 2 without a desktop PC?
I have the same problem, after the system update yesterday my old pin does not work anymore. What could I do?
So, before you updated, was your tablet rooted? Did the update use TWRP or the stock recovery? Did you have a pin set before the update?
before the update I use PIN and fingerprint reader, device was not rooted.
The update was offered by the device and ran normally.
Now my PIN does not work anymore. I do not have an "ok" button
when entering the PIN and I do not remember if there was one before?
My pin was reset after I updated, but I thought it was because I had replaced the stock recovery with TWRP. I've heard that there's a bug in TWRP that can mess up your pin. Now it looks like the pin problem is happening with stock updates, too. I'm surprised that other people haven't reported it.
If you had TWRP installed and you were able to boot into it, there's a way that you can use the TWRP file manager to delete the pin lock files. In your case, you will probably have to do what I ended up doing. I copied into Huawei eRecover and reset the tablet. That means it was wiped and I had to restore my apps and settings. You could try to get in touch with Huawei support first and see if they have a solution, since it appears that a stock update caused the problem. Please post back again if you find a solution.
I haven't followed development of the 6T since November so please forgive me if this has been answered 100 times.
The steps to flashing custom non-OOS ROM's is to; flash ROM/flash TWRP installer/reboot recovery/flash gapps/flash magisk
The weird issue for me is when I reboot recovery after flashing the ROM and TWRP when I go to install gapps all my files are encrypted. My way around this was to sideload gapps and magisk and everything booted up fine. When I go back to recovery after the first boot all the files are normal again.
This has happened both times I've flashed a ROM.
I'm sure this has an easy answer and it's most likely due to a step I didn't execute properly -- or at all. I did a lot of reading and making sure I understood the process before rooting my device but as far as flashing ROM's I was noticing a lot of conflicting info which I've never seen before on any other device. Anyway, other than this I haven't had any issue.
Thanks for any feedback.
Security issue. Best way around it is to either format data before flashing and/or remove your lockscreen security pin before flashing.
Deleted
ogkillergreen said:
Security issue. Best way around it is to either format data before flashing and/or remove your lockscreen security pin before flashing.
Click to expand...
Click to collapse
I never use any lock. Always just use Swype to unlock. I'm aware of the issue with using a lock though. I read that people had problems. I just haven't seen where any one brought up my exact issue. It doesn't seem to effect anything so I'm not stressing it too bad. Eventually I'll get around to troubleshooting it.
I've flashed almost every ROM for 6T till now and every time I flash a ROM I'm having exactly the same issue as you. I've also tried formatting data several times, but the issue with unreadable data in TWRP after flashing a ROM returns every single time. I've tried multiple combinations of flashing, wiping etc. and it's always the same. However, what I'm doing in such case is flashing gapps + magisk from USB-C pendrive, no need to sideload, just mount USB and flash files from that as usual. After doing that I can boot to ROM and the data is readable again. I just need to remember to have this pendrive close to me when I'm flashing a new ROM.
BreathingWounds said:
I've flashed almost every ROM for 6T till now and every time I flash a ROM I'm having exactly the same issue as you. I've also tried formatting data several times, but the issue with unreadable data in TWRP after flashing a ROM returns every single time. I've tried multiple combinations of flashing, wiping etc. and it's always the same. However, what I'm doing in such case is flashing gapps + magisk from USB-C pendrive, no need to sideload, just mount USB and flash files from that as usual. After doing that I can boot to ROM and the data is readable again. I just need to remember to have this pendrive close to me when I'm flashing a new ROM.
Click to expand...
Click to collapse
Thanks for the tip and info. I don't mind sideloading because it's fast and anytime I mess with my phone it's when I'm at my PC. I've been using adb for so many years it's my go-to whenever my phone is acting stupid.
The second time I flashed a ROM I didn't even worry about flashing gapps, just magisk. And I stacked them. So ROM, TWRP, Magisk. Then rebooted system. I actually prefer this anyway because then you boot straight to the launcher with no setup process. Then I go back and flash GAPPS. I actually have used this flashing process for years because I hate the setup after a first time boot.
I had attempted to install Evolution X, and after installing Magisk I had an issue with WiFi not working.
After reading another thread where a user had success installing PQ1A.190105.090 from fastboot, I decided to do the same myself.
After installing PQ1A.190105.090 it does not go through the setup process, and instead asks for PIN. Entering the PIN causes the phone to crash right back to the lockscreen.
I even tried wiping Data from TWRP (Which also asks for PIN and says it is incorrect)
I think I managed to mess up my phone, can someone be of assistance? Thanks!
but2002 said:
I had attempted to install Evolution X, and after installing Magisk I had an issue with WiFi not working.
After reading another thread where a user had success installing PQ1A.190105.090 from fastboot, I decided to do the same myself.
After installing PQ1A.190105.090 it does not go through the setup process, and instead asks for PIN. Entering the PIN causes the phone to crash right back to the lockscreen.
I even tried wiping Data from TWRP (Which also asks for PIN and says it is incorrect)
I think I managed to mess up my phone, can someone be of assistance? Thanks!
Click to expand...
Click to collapse
No expert here but I am pretty sure I read on here of others having had issues and thus advise to disable PIN lock on the phone before attempting. Might want to try a search on here for that and it should point you to how to fix it.
Hopefully others that have rooted already will chime in for you. I am still stock 10 due to the whole A-B slot thing that has me scared.
https://forum.xda-developers.com/showpost.php?p=83458899&postcount=5