twrp no longer unlocks / decrypts after flashing stock 8.1 Feb ota - Google Pixel 2 XL Questions & Answers

I flashed the February via fastboot last night (no wipe), unlocked phone just fine. Then fastbooted into latest twrp, but twrp does not recognize my pattern!
When I adb side loaded the latest romaur via twrp, the phone itself wouldn't recognize the pattern upon reboot.
I deleted the (only) fingerprint file in data, and that just broke login completely.
I then clean flashed Feb Ota via fastboot, set up the phone (single account), then fastbooted into latest twrp, but twrp still did not recognize my pattern!
I was able to add sideload magisk via twrp, but don't know how to decrypt in recovery.
Any ideas?

TWRP is currently broken for the February update so the only way is to completely remove your lockscreen.

Not So Pro said:
TWRP is currently broken for the February update so the only way is to completely remove your lockscreen.
Click to expand...
Click to collapse
So...disable lock screen, fastboot to TWRP again, do Kernel, do magisk, reboot and redo lockscreen?
EDIT: The above worked. I was able to see my files...however ElementalX is taking a long time to install...it says it's finished but just sitting there. No button to hit okay on, etc.
EDIT2: Kernel is fine. Something with TWRP possibly. I flashed TWRP instead of booting to it and tried again and it went fine. My phone is back to working lol.

IlyaKol said:
So...disable lock screen, fastboot to TWRP again, do Magisk/Kernel, reboot and redo lockscreen?
Click to expand...
Click to collapse
That's what I did and it worked beautifully! You can check some of the kernel topics in development and they talk about the issue. Same with the TWRP topic they talk about the issue.

IlyaKol said:
So...disable lock screen, fastboot to TWRP again, do Kernel, do magisk, reboot and redo lockscreen?
EDIT: The above worked. I was able to see my files...however ElementalX is taking a long time to install...it says it's finished but just sitting there. No button to hit okay on, etc.
EDIT2: Kernel is fine. Something with TWRP possibly. I flashed TWRP instead of booting to it and tried again and it went fine. My phone is back to working lol.
Click to expand...
Click to collapse
Do you mean disable screen lock? I don't know how to disable lock screen.

wtherrell said:
Do you mean disable screen lock? I don't know how to disable lock screen.
Click to expand...
Click to collapse
Yep, screen lock is correct. Just set it to swipe before you begin.

Related

Can't boot into recovery after cm14.1 nightly official

So as the title says, after flashing cm14. 1 can't go into recovery anymore, it just a black screen. I tried to use flashify but nothing, a couple of apps show that I have twrp 3.0.2.1 but can't get into it... Help?
Cheers
Same situation here. Neither booting the recovery via fastboot without flashing nor flashing the TWRP an then booting into it result in black screen. Flashify gives no results here. Please help.
EDIT; flashing this one via fastboot restores the access to TWRP, confirming it right now. http://forum.xda-developers.com/devdb/project/dl/?id=21065&task=get
JKMB888 said:
Same situation here. Neither booting the recovery via fastboot without flashing nor flashing the TWRP an then booting into it result in black screen. Flashify gives no results here. Please help.
EDIT; flashing this one via fastboot restores the access to TWRP, confirming it right now. http://forum.xda-developers.com/devdb/project/dl/?id=21065&task=get
Click to expand...
Click to collapse
Which thread is this from please?
JKMB888 said:
Same situation here. Neither booting the recovery via fastboot without flashing nor flashing the TWRP an then booting into it result in black screen. Flashify gives no results here. Please help.
EDIT; flashing this one via fastboot restores the access to TWRP, confirming it right now. http://forum.xda-developers.com/devdb/project/dl/?id=21065&task=get
Click to expand...
Click to collapse
Yeah man im in the same boat, if i get time ill try this twrp recovery. Where did that recovery come from?, it seems like the CM recovery for 14.1 nightly high jacks the recovery partition (i call it that,i dont know the term for it)
Sent from my ONEPLUS A3000 using Tapatalk
I believe the official 14.1 nightlies are based on the CB which requires the modified TWRP, which is what @JKMB888 has linked you to.
Hw4ng3r said:
I believe the official 14.1 nightlies are based on the CB which requires the modified TWRP, which is what @JKMB888 has linked you to.
Click to expand...
Click to collapse
I would like to truly confirm that the direct link to recovery, along with the thread in which it can be found, repair the situation. I was able to restore the backup of Freedom OS and the return to CM14.1 backup. We should keep this one somewhere near, jsut in case.
Thanks a lot guys, that did the trick, and done with flashify
JKMB888 said:
I would like to truly confirm that the direct link to recovery, along with the thread in which it can be found, repair the situation. I was able to restore the backup of Freedom OS and the return to CM14.1 backup. We should keep this one somewhere near, jsut in case.
Click to expand...
Click to collapse
@JKMB888 it does work 100% is as simple as flashing the TWRP. Actually, i installed it with CM 14.1 running just fine
Sent from my ONEPLUS A3000 using Tapatalk
Just re flash the TWRP image via Fastboot. Apps like flashify actually use TWRP or whatever recovery installed to flash image file AFAIK. I recommend using modified TWRP,Flashing some roms break the access. But the modified one can withstand almost every new rom installs.
Hope it helps.
Why i have always mount decrypt data when i boot in recovery mode which is TWRP 3.0.2-22 aand ask me to input a password?
Edit: I found the solution, i had a pattern lock screen and i removed it!
HC4Life said:
Why i have always mount decrypt data when i boot in recovery mode which is TWRP 3.0.2-22 aand ask me to input a password?
Click to expand...
Click to collapse
At some point your phone data became encrypted. While booted up if you search for encrypt in settings you'll see your phone is encrypted.
Same thing happened to me yesterday after flashing 3.2.7 and booting up for the first time before going back to TWRP to flash AICP. Only way to decrypt permanently, as far as I know, is to wipe all data including internal and completely start from scratch.
GrandMasterB said:
At some point your phone data became encrypted. While booted up if you search for encrypt in settings you'll see your phone is encrypted.
Same thing happened to me yesterday after flashing 3.2.7 and booting up for the first time before going back to TWRP to flash AICP. Only way to decrypt permanently, as far as I know, is to wipe all data including internal and completely start from scratch.
Click to expand...
Click to collapse
Look at my edited reply...
m4manusraj said:
Just re flash the TWRP image via Fastboot. Apps like flashify actually use TWRP or whatever recovery installed to flash image file AFAIK. I recommend using modified TWRP,Flashing some roms break the access. But the modified one can withstand almost every new rom installs.
Hope it helps.
Click to expand...
Click to collapse
actually flashify did the trick for me as I had no access to a pc for the time
http://forum.xda-developers.com/one...nity-build-t3461648/post68691560#post68691560
Flash this recovery. Fixed the problem for me
JKMB888 said:
I would like to truly confirm that the direct link to recovery, along with the thread in which it can be found, repair the situation. I was able to restore the backup of Freedom OS and the return to CM14.1 backup. We should keep this one somewhere near, jsut in case.
Click to expand...
Click to collapse
i am facing just the same situation with cm14.1 nightly and can't boot into recovery
i tried flashing the recovery image provided by you i.e. twrp-3.0.2-22-oneplus3.img but i face the same problem again
when i go into the recovery all i see is a black screen with a white notification light on and it remains there untill i switch off my phone manually using the power button
i tried facing the problem when i installed the cm14.1 nightly
i was unable to login snapchat as i device was rooted as said by the message on snapchat
so i decided to unroot my device via supersu FULL UNROOT option
after a reboot i successfully logged into snapchat
then i tried to root it again
i went into recovery to flash the supersu zip
and since then i have been unable to see the twrp recovey
please help me
This thread is a life save. Tried everything and it drove me nuts not getting into recovery.
THANK YOU!
gangangan2 said:
http://forum.xda-developers.com/one...nity-build-t3461648/post68691560#post68691560
Flash this recovery. Fixed the problem for me
Click to expand...
Click to collapse
Thank you so much it's work for me now..
After I got the recovery back, I flashed CM13 again and ARM64 6.0 Nano Gapps for my Oneplus 3, but I'm getting an error after the "preparing apps' screen is loaded saying that - unfortunately the process android.process.media has stopped one plus 3 boot and then the phone switches off.
Any solution to this? I've already tried flashing different versions of CM13.
Thank you!! I was looking for hours.
This link fixed the problem!
JKMB888 said:
Same situation here. Neither booting the recovery via fastboot without flashing nor flashing the TWRP an then booting into it result in black screen. Flashify gives no results here. Please help.
EDIT; flashing this one via fastboot restores the access to TWRP, confirming it right now. http://forum.xda-developers.com/devdb/project/dl/?id=21065&task=get
Click to expand...
Click to collapse
Hey, guys. I'm pretty sure I bricked my phone and there's no way to get out.
So I was on CM13 official builds on my OP3. Then, on the OTA update system they have, I got moved onto the CM14.1. I downloaded from here and went into my twrp recovery to flash. I made a clean flash and then proceeded to go back to system. I thought everything was ok until I realised I hadn't flashed a gapps package which I pretty much need to survive as all my contacts backups etc. are on there. I powered off my phone and went to go back into the recovery after downloading gapps 7.1 micro. It went past the *You're device can not be trusted'* and then went to the oneplus screen. After that, it stayed like that for about 30 secs and powered off. At first, I thought I messed something up and tried again. I repeated that for about 3 times and it didn't work. I tried going into the normal system and coming back to recovery and it didn't work still. In fact, now I can't even get into system. Now, i can only boot up to fastboot, where my computer still doesn't realise my phone is plugged in.
Anyone got any ideas on how to fix this? I wouldn't say I'm a noob at this because I have flashed many times before but I'm relatively new to the scene. I didn't see this thread before i ripped my hair out and i think wrecked my phone @JKMB888
EDIT: I sorted it out with help from Naman Bhalla's unbrick thread and this. A certain combo works and now I'm on CM14.1 enjoying life

TWRP 3.2 on android 8.1

Does TWRP 3.2.0-0 work on 8.1?
kingbri said:
Does TWRP 3.2.0-0 work on 8.1?
Click to expand...
Click to collapse
Sure does. I'm on the latest Dev preview with twrp 3.2 and magisk 14.5 beta. Flash everything and surprisingly, everything stuck on the first try.
Pain-N-Panic said:
Sure does. I'm on the latest Dev preview with twrp 3.2 and magisk 14.5 beta. Flash everything and surprisingly, everything stuck on the first try.
Click to expand...
Click to collapse
Can you use a password with this?
Pain-N-Panic said:
Sure does. I'm on the latest Dev preview with twrp 3.2 and magisk 14.5 beta. Flash everything and surprisingly, everything stuck on the first try.
Click to expand...
Click to collapse
How did you do it. I'm on Pixel , 128 GB, Oreo 8.1 (nov) but TWRP doesn't allow to attain the disk
I booted the 3.2.0-0.img, flashed the zip file but no way.
henk-jan said:
How did you do it. I'm on Pixel , 128 GB, Oreo 8.1 (nov) but TWRP doesn't allow to attain the disk
I booted the 3.2.0-0.img, flashed the zip file but no way.
Click to expand...
Click to collapse
I know that you have to factory reset and then install TWRP to work on swipe unlock every time. I'm asking if 3.2 fixed this problem so that I can log in using my password instead of removing my screen lock every single time
How did you get elementalx on 8.1, it keeps failing for me
kingbri said:
Can you use a password with this?
Click to expand...
Click to collapse
Not sure. I intentionally did not set a password prior to using it just in case twrp wasn't compatible with a password like the previous version.
---------- Post added at 09:00 PM ---------- Previous post was at 08:52 PM ----------
These are the steps I took to get twrp 3.2 working (without using a pin/password):
Clean flash 8.1 image
Boot into phone, setup device withOUT pin
Boot to bootloader
Fastboot boot twrp 3.2
Flash 3.2 installer zip
Reboot recovery
Flash 14.5 magisk beta
Flash 14.5 magisk a 2nd time
Reboot system.
kingbri said:
I know that you have to factory reset and then install TWRP to work on swipe unlock every time. I'm asking if 3.2 fixed this problem so that I can log in using my password instead of removing my screen lock every single time
How did you get elementalx on 8.1, it keeps failing for me
Click to expand...
Click to collapse
Thanks. I don't like a factory reset (till now I managed a dirty flash) because of the many apps I use
I don't have ElementalX at the moment installed, that's why I used ( ). I'm waiting for a update, probably when 8.1 is no longer beta.
henk-jan said:
Thanks. I don't like a factory reset (till now I managed a dirty flash) because of the many apps I use
I don't have ElementalX at the moment installed, that's why I used ( ). I'm waiting for a update, probably when 8.1 is no longer beta.
Click to expand...
Click to collapse
You'll only get away with dirty flashing for so long. I did the same as you for a while and ended up with a corrupted data partition. I was forced to do a factory reset and lost all data on my phone. Literally had to start from scratch.
Now, I clean flash (full wipe) every time. I make a backup of all of my apps with titanium backup. I adb pull my titanium folder, DCIM folder (photos) and my twrp folder (nandroid backup) to my PC. After I clean flash I use adb to push them back to my SD card. Reinstall titanium from the play store and restore all apps from my backup folder.
Pain-N-Panic said:
You'll only get away with dirty flashing for so long. I did the same as you for a while and ended up with a corrupted data partition. I was forced to do a factory reset and lost all data on my phone. Literally had to start from scratch.
Now, I clean flash (full wipe) every time. I make a backup of all of my apps with titanium backup. I adb pull my titanium folder, DCIM folder (photos) and my twrp folder (nandroid backup) to my PC. After I clean flash I use adb to push them back to my SD card. Reinstall titanium from the play store and restore all apps from my backup folder.
Click to expand...
Click to collapse
Twrp would probably update it once 8.1 releases
kingbri said:
I know that you have to factory reset and then install TWRP to work on swipe unlock every time. I'm asking if 3.2 fixed this problem so that I can log in using my password instead of removing my screen lock every single time
How did you get elementalx on 8.1, it keeps failing for me
Click to expand...
Click to collapse
No it didnt fix the encryption...
Hi,
just flashed the 8.1 Factory Image (without -w option) and TWRP fails to decrypt.
Tried setting a password instead of PIN but no success.
Wipe is no option for me.
Any chance to get the decryption working?
no, I don't think so, wait for twrp to update
Doenerbude said:
Hi,
just flashed the 8.1 Factory Image (without -w option) and TWRP fails to decrypt.
Tried setting a password instead of PIN but no success.
Wipe is no option for me.
Any chance to get the decryption working?
Click to expand...
Click to collapse
I am assuming you have things to flash, like root? Put the files on a USB and use the adapter to plug it into the phone. Hit cancel interpretation at the password screen and then you can select storage for the USB and flash the zips from there.
kingbri said:
Can you use a password with this?
Click to expand...
Click to collapse
No its still encrypted
before dirty flash 8.1, remove all patten/fingerprint, then flash 8.1, install twrp
flash all zips you need
re-enable your patten/fingerprint, just leave twrp there, till next update.
Doenerbude said:
Hi,
just flashed the 8.1 Factory Image (without -w option) and TWRP fails to decrypt.
Tried setting a password instead of PIN but no success.
Wipe is no option for me.
Any chance to get the decryption working?
Click to expand...
Click to collapse
The key is to NOT set a password at all...
Can we not use twrp 3.1.1-1 on Android 8.1?
It worked with both -removing any pin/passwort/pattern or in case you don't want to do this putting the files on an USB-C Stick, fastboot boot twrp.img and mount the USB-OTG
Just got everything working on 8.1, but TWRP does ask for a password instead of a pattern unlock. I got around this by the following method:
in fastboot:
fastboot boot twrp-3.2.0-0-marlin.img
since my phone is encrypted with a pattern, I had to "cancel" out of the prompt and sideload install everything, starting with TWRP 3.2:
adb sideload twrp-pixel-installer-marlin-3.2.0-0.zip
then rebooted into recovery:
adb reboot recovery
since unlocking encryption still didn't work, I sideloaded Magisk first:
adb sideload Magisk-v14.5(1456).zip
and then SuperSU:
SR5-SuperSU-v2.82-SR5-20171001224502.zip
rebooted to system, everything works as it should. passes safetynet check.
cowrecked said:
since unlocking encryption still didn't work, I sideloaded Magisk first:
adb sideload Magisk-v14.5(1456).zip
and then SuperSU:
SR5-SuperSU-v2.82-SR5-20171001224502.zip
Click to expand...
Click to collapse
Why are you flashing both? New to Magisk so perhaps I am missing something.

"Fingerprint Hardware Not Available" and missing WiFi

Yesterday I updated my Magisk to 15.3 and also decided that I wanted to flash a new Kernel too, so I did with The Flash. Once everything booted back up, when I try to unlock my phone I get the message at the bottom of my screen saying "Fingerprint Hardware Not Available" and then once I just unlock with my pattern, WiFi won't turn on, I can click and click and it just stays greyed out. I read somewhere that flashing to the Stock+Safetynet Kernel that it could fix those problem, but it didn't for me. Would anyone know of any other solutions other than Factory reset? Thanks in advance.
absoluthamm said:
Yesterday I updated my Magisk to 15.3 and also decided that I wanted to flash a new Kernel too, so I did with The Flash. Once everything booted back up, when I try to unlock my phone I get the message at the bottom of my screen saying "Fingerprint Hardware Not Available" and then once I just unlock with my pattern, WiFi won't turn on, I can click and click and it just stays greyed out. I read somewhere that flashing to the Stock+Safetynet Kernel that it could fix those problem, but it didn't for me. Would anyone know of any other solutions other than Factory reset? Thanks in advance.
Click to expand...
Click to collapse
Fastboot the stock boot.img and see if it boots up normally without the warning. That's pretty strange behavior after flashing the Flash kernel. Kindly post your installation method when you can :good:
Badger50 said:
Fastboot the stock boot.img and see if it boots up normally without the warning. That's pretty strange behavior after flashing the Flash kernel. Kindly post your installation method when you can :good:
Click to expand...
Click to collapse
When I get a chance I'll download the stock image and try fastbooting it.
As far as my install method, I flashed the kernel via TWRP, then flashed Magisk, then rebooted.
Thanks!
absoluthamm said:
When I get a chance I'll download the stock image and try fastbooting it.
As far as my install method, I flashed the kernel via TWRP, then flashed Magisk, then rebooted.
Thanks!
Click to expand...
Click to collapse
Just for the heck of it, if you want to try, go back to TWRP and flash...
Flash kernel
The twrp.zip
Then reboot back into TWRP and flash the magisk zip. Then we'll see if that fixes it.
Badger50 said:
Just for the heck of it, if you want to try, go back to TWRP and flash...
Flash kernel
The twrp.zip
Then reboot back into TWRP and flash the magisk zip. Then we'll see if that fixes it.
Click to expand...
Click to collapse
Haven't had a chance to download the stock boot.img yet, but I did try your suggestion here and the same result happens, no fingerprint, no wifi.
absoluthamm said:
Haven't had a chance to download the stock boot.img yet, but I did try your suggestion here and the same result happens, no fingerprint, no wifi.
Click to expand...
Click to collapse
Darn! Oh well, if your still having trouble after you fastboot the stock boot.img, you may have to dirty flash the factory image. If that doesn't work, then a factory reset or a clean flash of the factory image might be needed. If that doesn't work, then you may have to run it in safe mode for a while. Finally, if that doesn't work, your hardware/software may be hosed and RMA here you come. Lets hope it's not that serious
This happened to me on the Pixel 2 when updating to the January image, I had do a full image wipe in order to fix it.
bro i am worried i wiped data cache vendor and flashed RR rom now the sim is not inserting and wifi bluetooth fingerprint music everything is not working ..what should i do

TWRP Unresponsive

So, I have AOISP on my phone, and TWRP was on it and it worked flawlessly. I performed an update to AOISP, which it installs like an OEM update, not simply flash in TWRP, but installs behind the scenes. Of course I knew TWRP would go away after updating this way. Now anytime I do the usual method to get TWRP again, you know, fastboot boot twrp.... you know the drill, my phone boots into TWRP, but twrp just doesn't respond. I'm used to the whole first couple of touches will say wrong password because of the touch issue, but it eventually works. Right now, it just doesn't respond at all. Anyone else face this and have a fix for it. I'd rather not have to use the flash-all.bat file and wipe everything. I'm sure considering I'm on AOSIP I can't just simply remove the -w and everything work just fine. Oh and I've tried multiple twrps as well. 3.2.3-3 and I've tried 3.2.3-5.
I don't have a solution, unfortunately, but I am experiencing the same issue.
godraistlin said:
So, I have AOISP on my phone, and TWRP was on it and it worked flawlessly. I performed an update to AOISP, which it installs like an OEM update, not simply flash in TWRP, but installs behind the scenes. Of course I knew TWRP would go away after updating this way. Now anytime I do the usual method to get TWRP again, you know, fastboot flash boot twrp.... you know the drill, my phone boots into TWRP, but twrp just doesn't respond. I'm used to the whole first couple of touches will say wrong password because of the touch issue, but it eventually works. Right now, it just doesn't respond at all. Anyone else face this and have a fix for it. I'd rather not have to use the flash-all.bat file and wipe everything. I'm sure considering I'm on AOSIP I can't just simply remove the -w and everything work just fine. Oh and I've tried multiple twrps as well. 3.2.3-3 and I've tried 3.2.3-5.
Click to expand...
Click to collapse
You said you were using "fastboot flash boot" twrp. If that is the command you used, it should be "fastboot boot" twrp
Sent from my Pixel 3 XL using XDA Labs
I had this too. The fix that worked for me. Haven't tried the time to reproduce is. When you fastboot boot twrp.img and it loads. Touch will stop.
Then reboot via buttons and get to fastboot again by buttons (power and vol down). Select recovery and wait for recovery to boot again. Once that happened touch worked again for me.
I tried various other versions of twrp and none work. But this did.
Again not sure if I can reproduce this as I have not had the time.
Also have not had the chance to try rebooting into twrp from system after flashing it to see if the issue continues.
godraistlin said:
So, I have AOISP on my phone, and TWRP was on it and it worked flawlessly. I performed an update to AOISP, which it installs like an OEM update, not simply flash in TWRP, but installs behind the scenes. Of course I knew TWRP would go away after updating this way. Now anytime I do the usual method to get TWRP again, you know, fastboot flash boot twrp.... you know the drill, my phone boots into TWRP, but twrp just doesn't respond. I'm used to the whole first couple of touches will say wrong password because of the touch issue, but it eventually works. Right now, it just doesn't respond at all. Anyone else face this and have a fix for it. I'd rather not have to use the flash-all.bat file and wipe everything. I'm sure considering I'm on AOSIP I can't just simply remove the -w and everything work just fine. Oh and I've tried multiple twrps as well. 3.2.3-3 and I've tried 3.2.3-5.
Click to expand...
Click to collapse
Don't fastboot flash the image. Put the twrp.zip file on your phone. Then boot the twrp.img. Once in twrp install the zip.
c_86 said:
I had this too. The fix that worked for me. Haven't tried the time to reproduce is. When you fastboot boot twrp.img and it loads. Touch will stop.
Then reboot via buttons and get to fastboot again by buttons (power and vol down). Select recovery and wait for recovery to boot again. Once that happened touch worked again for me.
I tried various other versions of twrp and none work. But this did.
Again not sure if I can reproduce this as I have not had the time.
Also have not had the chance to try rebooting into twrp from system after flashing it to see if the issue continues.
Click to expand...
Click to collapse
I could not get this method to work for me. I keep booting back into the stock recovery. It seems that my installation of TWRP is gone.
godraistlin said:
So, I have AOISP on my phone, and TWRP was on it and it worked flawlessly. I performed an update to AOISP, which it installs like an OEM update, not simply flash in TWRP, but installs behind the scenes. Of course I knew TWRP would go away after updating this way. Now anytime I do the usual method to get TWRP again, you know, fastboot flash boot twrp.... you know the drill, my phone boots into TWRP, but twrp just doesn't respond. I'm used to the whole first couple of touches will say wrong password because of the touch issue, but it eventually works. Right now, it just doesn't respond at all. Anyone else face this and have a fix for it. I'd rather not have to use the flash-all.bat file and wipe everything. I'm sure considering I'm on AOSIP I can't just simply remove the -w and everything work just fine. Oh and I've tried multiple twrps as well. 3.2.3-3 and I've tried 3.2.3-5.
Click to expand...
Click to collapse
What are you using for your screen lock security? If something other than PIN, try either setting it to PIN or None. There is a dedicated TWRP thread where you may find your answer or at least get more visibility.
lollyjay said:
You said you were using "fastboot flash boot" twrp. If that is the command you used, it should be "fastboot boot" twrp
Sent from my Pixel 3 XL using XDA Labs
Click to expand...
Click to collapse
That's what I meant. I was running on no sleep when I typed this. I was typing in the right command. Lol I just mixed up the old command with the new one when typing my problem out because the old one was fastboot flash recovery twrp...
jd1639 said:
Don't fastboot flash the image. Put the twrp.zip file on your phone. Then boot the twrp.img. Once in twrp install the zip.
Click to expand...
Click to collapse
Yeah. I accidentally said I typed in that command. I don't type in flash. I do use fastboot boot twrp.... I was just sleep deprived when typing out my issue. I do it the way you're supposed to, but it just doesn't work.
godraistlin said:
That's what I meant. I was running on no sleep when I typed this. I was typing in the right command. Lol I just mixed up the old command with the new one when typing my problem out because the old one was fastboot flash recovery twrp...
Click to expand...
Click to collapse
OK np :good:
Sent from my Pixel 3 XL using XDA Labs
v12xke said:
What are you using for your screen lock security? If something other than PIN, try either setting it to PIN or None. There is a dedicated TWRP thread where you may find your answer or at least get more visibility.
Click to expand...
Click to collapse
I use a pattern, but I tried it with no pin at all, and it's still unresponsive.
godraistlin said:
I use a pattern, but I tried it with no pin at all, and it's still unresponsive.
Click to expand...
Click to collapse
Ok, well I have always used a PIN for the screen lock and have never had a problem. I use the same PIN in TWRP. Worth a shot.
v12xke said:
Ok, well I have always used a PIN for the screen lock and have never had a problem. I use the same PIN in TWRP. Worth a shot.
Click to expand...
Click to collapse
I flash new ROMs almost weekly and have never had this issue. My last resort is to use the flash-all.bat putting the phone back to factory, and seeing if the issue continues.
gordopa1 said:
I could not get this method to work for me. I keep booting back into the stock recovery. It seems that my installation of TWRP is gone.
Click to expand...
Click to collapse
Ya I don't know then. That's what I did and got touch back. Might have been a 1 off
godraistlin said:
I flash new ROMs almost weekly and have never had this issue. My last resort is to use the flash-all.bat putting the phone back to factory, and seeing if the issue continues.
Click to expand...
Click to collapse
I flashed back to the latest stock image and TWRP was able to boot normally.
gordopa1 said:
I flashed back to the latest stock image and TWRP was able to boot normally.
Click to expand...
Click to collapse
Yeah, that's what I just did as well, and twrp is functioning normal again. I bet it had something to do with the way AOISP updates install. That's the only thing I can think of.
godraistlin said:
Yeah, that's what I just did as well, and twrp is functioning normal again. I bet it had something to do with the way AOISP updates install. That's the only thing I can think of.
Click to expand...
Click to collapse
That's the odd thing. I didn't do the ota I direct down loaded the zip and flashed it manually. And still had the issue but corrected it with my previous method.
I experienced the same TWRP gone after the update, but I flashed it again with Fk manager. It then booted perfectly into TWRP version 3.5. From there, I reflashed Magisk. Now all is working perfectly.
Sent from my Pixel 3 XL
Eudeferrer said:
I experienced the same TWRP gone after the update, but I flashed it again with Fk manager. It then booted perfectly into TWRP version 3.5. From there, I reflashed Magisk. Now all is working perfectly.
Click to expand...
Click to collapse
Fk manager?
FK Kernel Manager from Francisco Franco on the Google app store. It lets you flash any zip file, as well as tweak your kernel.
Sent from my Pixel 3 XL

Can Android 10 beta be rooted?

If it can, how? I'm having bootloop issues trying to do that. Thank you.
Bootloop in logo S9
RpRAUC said:
Bootloop in logo S9
Click to expand...
Click to collapse
follow up
Piereligio said:
If it can, how? I'm having bootloop issues trying to do that. Thank you.
Click to expand...
Click to collapse
http://forum.xda-developers.com/galaxy-s9/how-to/one-ui-2-beta-rooting-installing-twrp-t4012961
https://forum.xda-developers.com/ga...rooting-installing-twrp-t4012961/post81084623
The patched kernel contained here was the solution for me
S9 ROOT
I did it.I flashed twrp format data and and installed SoldierR9312 mod. lock screen,samsung account and magisk root all work
http://www.renovate-ice.com/soldier9312/#stable_g96x-q
viktorvlahov11 said:
I did it.I flashed twrp format data and and installed SoldierR9312 mod. lock screen,samsung account and magisk root all work
http://www.renovate-ice.com/soldier9312/#stable_g96x-q
Click to expand...
Click to collapse
This worked great, thanks. Only issue I met was that I couldn't see the OEM unlock switch, so it didn't let me to flash TWRP from Odin (even though it was already unlocked), giving me "only official released binaries are allowed to be flashed(recovery)" error.
The solution for that was following these steps: https://www.xda-developers.com/fix-...y-s9-samsung-galaxy-s8-samsung-galaxy-note-8/
EDIT: no wait, maybe it's bootlooping.
EDIT2: yes it is. I'm using italian carrier, you?
EDIT3: at the end I created a custom boot.img by using Magisk and I flashed it. In this way I kept encryption and stock recovery, but this doesn't give me write permissions in /system. But I do have root.
it stucks for me on the samsung logo
aidenpearce296 said:
it stucks for me on the samsung logo
Click to expand...
Click to collapse
Try flashing the twrp flashable firmware it may fix your problem
---------- Post added at 08:41 AM ---------- Previous post was at 08:37 AM ----------
viktorvlahov11 said:
Try flashing the twrp flashable firmware it may fix your problem
Click to expand...
Click to collapse
Piereligio said:
This worked great, thanks. Only issue I met was that I couldn't see the OEM unlock switch, so it didn't let me to flash TWRP from Odin (even though it was already unlocked), giving me "only official released binaries are allowed to be flashed(recovery)" error.
The solution for that was following these steps: https://www.xda-developers.com/fix-...y-s9-samsung-galaxy-s8-samsung-galaxy-note-8/
EDIT: no wait, maybe it's bootlooping.
EDIT2: yes it is. I'm using italian carrier, you?
EDIT3: at the end I created a custom boot.img by using Magisk and I flashed it. In this way I kept encryption and stock recovery, but this doesn't give me write permissions in /system. But I do have root.
Click to expand...
Click to collapse
I got it to work on a Bulgarian unlocked model
Maybe try flashing the twrp flashable firmware after the mod
omg it was so easy!
after you flashed twrp and formated data you just have to flash magisk and that's it
viktorvlahov11 said:
omg it was so easy!
after you flashed twrp and formated data you just have to flash magisk and that's it
Click to expand...
Click to collapse
I done that, but still stuck on SAMSUNG logo, no boot loop or what. I was waiting 10min, nothing happened.
Any advice?
Hi there,
after having tried different methods to root my S9, which has updated to Android 10 One UI 2.0 this morning, maybe the solution that finally worked for me will help you too.
First I tried to root just like in Pie, as found on the net: flashed TWRP 3.2.3 via Odin, then flashed Magisk with TWRP plus this no-verity-opt-encrypt. Got stuck in bootloop, tried different no-verity/dm-verity versions, Magisk 18.x and Magisk 20.1. Nothing worked, got stuck again every time i rebootet the system again.
Then, after realising that I CANT get back to Android 9 (old rom wasnt Odin flashable anymore, phone didnt boot, BSoD), I first downloaded the new stock rom and bootloader as zip, got it from here:
https://forum.xda-developers.com/showpost.php?p=81615561&postcount=1830.
You have to check if that fits with your version / phone. Once downloaded, I copied both onto my SD card. So now I was able to install at least the new clean stock rom. Oh, and now I used the TWRP version 3.3.1.
Then I found this:
https://forum.xda-developers.com/galaxy-s9/development/root-s9plus-exynos-android10-t4065343
At first I tried to root without the SoLdieR9312's mod, only with MAGISK 20.3 and no-verity. Stuck again, it only bootet to download mode, nothing else. So flashed again the clean stock rom, and after first not keeping the right order (I suppose) I finally followed EXACTLY the instructions 1 - 4 in above manual including SoLdieR9312's mod (I highly recommend first a complete Wipe, format data, and then flash the clean new Rom with Android 10 and bootloader from above link).
Now, to save you the time I spent today: once your phone is bootet (and succesfully rooted via Magisk 20.3, which will happen automatically due to the SoLdieR9312's mod), DONT LET MAGISK UPDATE TO VERSION 20.4!!!! Magisk Manager asks you to update, but when I did update to 20.4, everything fell apart again, it only bootet to download mode.
Now I seem to have it stable and running with 20.3 and the [email protected]. I rebootet 5 times so far just for the sake of it, and it works fine and rootet.
If I can be of further help, please let me know. I spent the last 12 hours on this matter, so dont hesitate.
Greetz from me minus a bunch of nerves
PS: After I wrote the above, I deleted the Knox family in the rootet system, and then it collapsed again and, after BSoD, it only rebootet into download mode. I can not exclude the possibility, that this might have been the reason for some system breakdowns before, as I had to re-do the wipe-clean-install-then-root-then-customize worksteps aroung 8 times yesterday before it was stable as it is now. Now I´ll leave Knox on it, though that itches me a bit. But I´m exhausted for now
PPS: IMPORTANT when I try to create a PIN or a pattern for the lock screen, phone reboots to SIM card PIN screen and then keeps rebooting and rebooting. It looks like there are some interferences with root and PIN / security. I did NOT create a Samsung account, only a google one, cause in the beginning i suspected it might have been a Sam acct problem (I constantly couldnt log into it on the phone). Turns out that might not have been the case, rather a prob between root and setting a lock screen security.

Categories

Resources