Related
So I am on stock GPE 5.1 the device has never been encrypted. I installed TWRP 2.8.6.0 and rooted. I then encrypted the phone this afternoon and everything is going just fine....However I tried to access TWRP after encrypting and it would not take my pattern unlock code that decrypts the device on boot.
I then changed to PIN unlock. TWRP recognized I was using PIN lock now and put the code in and it still won't decrypt the data partition.
Anyone have a suggestion on how to solve this decryption conundrum?
metaphz said:
So I am on stock GPE 5.1 the device has never been encrypted. I installed TWRP 2.8.6.0 and rooted. I then encrypted the phone this afternoon and everything is going just fine....However I tried to access TWRP after encrypting and it would not take my pattern unlock code that decrypts the device on boot.
I then changed to PIN unlock. TWRP recognized I was using PIN lock now and put the code in and it still won't decrypt the data partition.
Anyone have a suggestion on how to solve this decryption conundrum?
Click to expand...
Click to collapse
hi, have u tried updating to the latest twrp 2.8.7.0. my phone is encrypted too n i m able to use password in twrp. pattern is also working. just sharing tho....
So, long story short, I followed this tutorial: www . htcmania. com/showthread.php?t=1024045 (remove the spaces in w.h and .com) and it didn't go very well.
I flashed TWRP and SuperSU as told, using both download links (TWRP 2.8.7 & SuperSU 2.46), and my phone got stuck in a bootloop at LG bootloader unlocked logo. I recovered my phone by using LG Bridge and after that, when i tried to enter TWRP using the phone keys, it resulted in a factory data reset (no TWRP after recovery, didn't know that). I then followed the exact same steps but using what I thought was the lastest SuperSU archive (SR5-SuperSU-v2.82), flashed the archive and when finished, TWRP asked me to flash it again (so I did), then rebooted, passed LG bootloader unlocked logo, got into LG animation and... Bootloop again, so I recovered again with LG Bridge but I din't attempted to enter TWRP because this time i knew it wouldn't work and I ended it there, reinstalling all apps and configuring my phone as I had it before my unsuccessfull attempt. I continued using my phone as usual but sometimes, when I enter Pokemon Go, it says that it couldn't log in and that my phone's OS is not supported. As I said, the app does this sometimes whenever it wants, so I researched a bit and turns out it doesn't work with rooted android devices (I didn't know that). I knew my root attempt failed so I downloaded and app called Root Checker and checked: Root status-Not rooted; SafetyNet Status-Failed. I don't know what should I do know, last time I rooted my phone was a Sony Xperia XL and it wasn't so tricky.
I asked for advice in the forum and got no answer, so here I am, hoping for a solution. What I want is to have a permanent custom recovery, a rooted device and to have SafetyNet status passed. Any ideas, hints or whatever? Please, help
Hello members of XDA,
The issue I'm having is pretty rare and found few or non threads about it, so I will try to be the most precise possible.
Yesterday I decided to change the ROM of my LG G4 H815, I was previously on LineageOS, since LineageOS on H815 wasn't developped anymore. So I asked myself why not trying Android Oreo with CypherOS. Before any changes I was with the latest version of LineageOS for H815 and I had TWRP with the version 3.0.2.1. Bootloader was obviously unlocked.
So I starded to download all the required material to switch to CypherOS 5.3.1, while the download I've made a backup of my actual lineageOS installation on my internal storage. Once every thing was downloaded I tried to install CypherOS I had an error 7 in TWRP install box, so I was pretty worried, scouted XDA threads about the error but i was redirected to the solution where you modify the update binary with txt but still didnt worked. I've found a thread talking about updating firmware of the H815 ( https://forum.xda-developers.com/g4/development/v5-8-5-n7-1-2-resurrection-remix-t3704450) While panicking I've done a wipe of everything (dalvik, data,cache and system) .I applied thge firmware update but I also re-read the thread of CypherOS and figured that I needed a newer version of TWRP, installed it so. THen magically CypherOS installed without any issue.
After installing the Gapps (Arm64 8.1 Nano) I rebooted and the first weird thing appears, after seeing the LG screen while the boot I have another screen telling me that the bootloader has been locked and that i should visit g.co/ABH for more information, then CypherOS initialise, CypherOS worked like a charm. So I wanted to go to my TWRP and make a backup in case. I launched ADB and use the command adb reboot recovery, the phone restarted and had the following events : LG logo, warning message about the bootloader, LG logo again and then a black screen. However I was in recovery mode since adb found me with the command fastboot devices. I had no TWRP logo or anything linked to it. Few minutes later, I had the basic recovery mode where you move yourself with the volume buttons and select with power where the functions are pretty limited.
Then I rebooted the phone with adb (fastboot reboot), CypherOS still working perfectly. Thaught that it was the bootloader which back to scratch when he was blocked, I figured out that he was still unlocked, I used the command "fastboot getvar unlocked" through ADB. THen I thaught i had to install back TWRP, tried through the fastboot mode but I had an error
Code:
FAILED (remote: unkown command)
since i tried everything i could even in the basic recovery mode, the only working command in the recovery is "fastboot flash recovery twrp.img" but still does nothing.
I mean it's not that terrible since I can use my phone and i'm about to change phone in 2 months for a Oneplus but i would really like to be able to install magisk on the phone to grant root access and be able to use TWRP on it like I used to. By the way the backup of lineageOS has been deleted while performing unecessary wipes.
Bennou said:
Hello members of XDA,
The issue I'm having is pretty rare and found few or non threads about it, so I will try to be the most precise possible.
Yesterday I decided to change the ROM of my LG G4 H815, I was previously on LineageOS, since LineageOS on H815 wasn't developped anymore. So I asked myself why not trying Android Oreo with CypherOS. Before any changes I was with the latest version of LineageOS for H815 and I had TWRP with the version 3.0.2.1. Bootloader was obviously unlocked.
So I starded to download all the required material to switch to CypherOS 5.3.1, while the download I've made a backup of my actual lineageOS installation on my internal storage. Once every thing was downloaded I tried to install CypherOS I had an error 7 in TWRP install box, so I was pretty worried, scouted XDA threads about the error but i was redirected to the solution where you modify the update binary with txt but still didnt worked. I've found a thread talking about updating firmware of the H815 ( https://forum.xda-developers.com/g4/development/v5-8-5-n7-1-2-resurrection-remix-t3704450) While panicking I've done a wipe of everything (dalvik, data,cache and system) .I applied thge firmware update but I also re-read the thread of CypherOS and figured that I needed a newer version of TWRP, installed it so. THen magically CypherOS installed without any issue.
After installing the Gapps (Arm64 8.1 Nano) I rebooted and the first weird thing appears, after seeing the LG screen while the boot I have another screen telling me that the bootloader has been locked and that i should visit g.co/ABH for more information, then CypherOS initialise, CypherOS worked like a charm. So I wanted to go to my TWRP and make a backup in case. I launched ADB and use the command adb reboot recovery, the phone restarted and had the following events : LG logo, warning message about the bootloader, LG logo again and then a black screen. However I was in recovery mode since adb found me with the command fastboot devices. I had no TWRP logo or anything linked to it. Few minutes later, I had the basic recovery mode where you move yourself with the volume buttons and select with power where the functions are pretty limited.
Then I rebooted the phone with adb (fastboot reboot), CypherOS still working perfectly. Thaught that it was the bootloader which back to scratch when he was blocked, I figured out that he was still unlocked, I used the command "fastboot getvar unlocked" through ADB. THen I thaught i had to install back TWRP, tried through the fastboot mode but I had an error since i tried everything i could even in the basic recovery mode, the only working command in the recovery is "fastboot flash recovery twrp.img" but still does nothing.
I mean it's not that terrible since I can use my phone and i'm about to change phone in 2 months for a Oneplus but i would really like to be able to install magisk on the phone to grant root access and be able to use TWRP on it like I used to. By the way the backup of lineageOS has been deleted while performing unecessary wipes.
Click to expand...
Click to collapse
It's clearly written on the official website and in the official TWRP support thread for the g4 what you have to do when on Nougat bootloader and want to flash TWRP... and keeping it.
Sent from my LG-H815 using XDA Labs
Yet, this still doesnt help me to solve my issue. Do you think there is a way to fix it or no ? If not, I'll just deal with it for the few months lasting.
Bennou said:
Yet, this still doesnt help me to solve my issue. Do you think there is a way to fix it or no ? If not, I'll just deal with it for the few months lasting.
Click to expand...
Click to collapse
Okay if it doesn't work for you you must do something wrong. It works 100%. If you really want help you should explain in detail exactly which steps you took as otherwise it's all just guessing what you're doing.
Sent from my LG-H815 using XDA Labs
Indeed, I didn't followed the procedure exactly, didn't do the step after flashing TWRP (removing battery and boot manually to recovery). Well thank you, was my bad on that.
Should I do a clean new install of cypheros or should I keep it like that, what would be your advice ? Knowing that at the moment CypherOS works like a charm. I also plan to install Magisk on it to root it.
To help others newbie like me, solution can be found here : https://forum.xda-developers.com/g4/development/recovery-twrp-3-touch-recovery-t3442424
So, being the stupid person I am I broke my Mate SE one day after purchase ._. I'm posting my entire process just in case anything helps.
I started off by updating to the latest ROM and then unlocking the bootloader, which went fairly well, then flashed TWRP. A lot of versions I found didn't work(Bootloader says Func NO: 11 (recovery image) and Error NO: 2 (load failed!)), but I got a working version here: https://forum.xda-developers.com/honor-7x/development/oreo-twrp-complete-backup-t3764500 .
After that, I installed Magisk, which went well, then Xposed framework inside Magisk, which put my phone in a bootloop. I didn't know what to do, so I went with a factory reset[terrible idea]. Now, my phone has the FRP lock on, and the android setup is stuck on a "just a sec" page, right after selecting language and wifi, so I can't login to my google account to disable the FRP lock.
I tried flashing, but apparently the FRP lock stops me from being able to flash anything inside the bootloader. I do still have my TWRP recovery and a backup of the kernel and ramdisk(sadly nothing else useful, although I do also have dts, dfx, vendor_image, oeminfo and secure_storage) but restoring them or wiping the system again has no effect(still stuck on "just a sec").
After some google searching someone in a thread said that I should use stock recovery to wipe factory data(by restoring the stock recovery in TWRP), and I would be able to get past the "just a sec" problem, but I am reluctant because if it doesn't work, I would permanently lose my TWRP recovery with no way to flash it back(because of that FRP lock). I also tried installing update.app and other stock ROMs from various sources using TWRP, but all of them had a "check_write_data_to_partition, write data error" error. I'm not sure if it's related to FRP.
I think my next course of action is to either a) disable FRP in recovery, b) bypass the setup screen or c) install some ROM on it and somehow bypassing the check_write_data_to_partition error, but I'm not sure how to do any of these. Any ideas or suggestions? Thanks.
rkevin_arch said:
So, being the stupid person I am I broke my Mate SE one day after purchase ._. I'm posting my entire process just in case anything helps.
I started off by updating to the latest ROM and then unlocking the bootloader, which went fairly well, then flashed TWRP. A lot of versions I found didn't work(Bootloader says Func NO: 11 (recovery image) and Error NO: 2 (load failed!)), but I got a working version here: https://forum.xda-developers.com/honor-7x/development/oreo-twrp-complete-backup-t3764500 .
After that, I installed Magisk, which went well, then Xposed framework inside Magisk, which put my phone in a bootloop. I didn't know what to do, so I went with a factory reset[terrible idea]. Now, my phone has the FRP lock on, and the android setup is stuck on a "just a sec" page, right after selecting language and wifi, so I can't login to my google account to disable the FRP lock.
I tried flashing, but apparently the FRP lock stops me from being able to flash anything inside the bootloader. I do still have my TWRP recovery and a backup of the kernel and ramdisk(sadly nothing else useful, although I do also have dts, dfx, vendor_image, oeminfo and secure_storage) but restoring them or wiping the system again has no effect(still stuck on "just a sec").
After some google searching someone in a thread said that I should use stock recovery to wipe factory data(by restoring the stock recovery in TWRP), and I would be able to get past the "just a sec" problem, but I am reluctant because if it doesn't work, I would permanently lose my TWRP recovery with no way to flash it back(because of that FRP lock). I also tried installing update.app and other stock ROMs from various sources using TWRP, but all of them had a "check_write_data_to_partition, write data error" error. I'm not sure if it's related to FRP.
I think my next course of action is to either a) disable FRP in recovery, b) bypass the setup screen or c) install some ROM on it and somehow bypassing the check_write_data_to_partition error, but I'm not sure how to do any of these. Any ideas or suggestions? Thanks.
Click to expand...
Click to collapse
There is an unlock frp patch by a dev in another that works with the 7x. It should work for you too.
I will find link when I get off the road
mrmazak said:
There is an unlock frp patch by a dev in another that works with the 7x. It should work for you too.
I will find link when I get off the road
Click to expand...
Click to collapse
Link to frp unlock
https://mega.nz/#!nw0wAYoA!hYtf78s0AjwRCpPo_NQ2F4LYclngNBNurJNETypSNKQ
Posted many places. But I found it on the bottom of post 2.
Here.
https://forum.xda-developers.com/showpost.php?p=76398556&postcount=2
mrmazak said:
Link to frp unlock
https://mega.nz/#!nw0wAYoA!hYtf78s0AjwRCpPo_NQ2F4LYclngNBNurJNETypSNKQ
Posted many places. But I found it on the bottom of post 2.
Here.
https://forum.xda-developers.com/showpost.php?p=76398556&postcount=2
Click to expand...
Click to collapse
Thanks for the help! It worked, and the bootloader says FRP unlocked. It didn't help the "just a sec" issue, but since I can use fastboot flash, I might be able to flash a new rom in it and just ditch EMUI[probably]. I'll play around with it a bit. Again, thanks a lot for your help!
I got everything working now! Just in case anyone had the same "just a sec" issue: it was fixed by flashing stock recovery then doing a factory reset there(I'm not sure how that's different from wiping dalvik/cache/data/internal storage in twrp, but it makes a difference apparantly). Just flashing custom ROMs didn't solve the problem. After that I installed magisk, and then installed this version of xposed: https://forum.xda-developers.com/showpost.php?p=76582399&postcount=11 . I installed the v90-beta3 version before which caused the bootloop, but it is fixed in the next version. Magisk has some issues so the magisk manager can't start with internet(adb logcat says there's a NullPointerException in com.topjohnwu.magisk.database.RepoDatabaseHelper.removeRepo) but frankly I don't need to open it with internet anyways. Now I have everything I need on my new phone! Thanks to mrmazak for pointing me to the right direction.
My girlfriend has a OnePlus 3T and is stuck on Oxygen OS 5.0.4, and it doesn't matter if I download the update via the update settings or install it locally or via adb, or use twrp to flash it, I tried all those ways.
Regardless, the update fails every time. I also tried deleting the ota folder, and rebooting her phone to recovery and deleting cache... that doesn't work either. I also tried using adb and typing in - adb reboot "dm-verity enforcing" - still nothing.
I also used the toolkit from here:
https://forum.xda-developers.com/oneplus-3/development/toolkit-oneplus-3-toolkit-unlock-t3398799
and I tried to lock the bootloader. It took me hours to figure out how to get the bootloader unlocked again, cause I had to enter a password to get in, and at the time my girlfriend had no password on her phone at all.
After I figured out about unlocking the bootloader again, I made a password in the security setting, re locked bootloader, still nothing. The password works while phone's bootloader is unlocked, but not while it's locked.
I made a video to further explain and show the situation.
https://www.youtube.com/watch?v=YBtQW00JsNU
Still nothing?
DranzerX13 said:
My girlfriend has a OnePlus 3T and is stuck on Oxygen OS 5.0.4, and it doesn't matter if I download the update via the update settings or install it locally or via adb, or use twrp to flash it, I tried all those ways.
Regardless, the update fails every time. I also tried deleting the ota folder, and rebooting her phone to recovery and deleting cache... that doesn't work either. I also tried using adb and typing in - adb reboot "dm-verity enforcing" - still nothing.
I also used the toolkit from here:
https://forum.xda-developers.com/oneplus-3/development/toolkit-oneplus-3-toolkit-unlock-t3398799
and I tried to lock the bootloader. It took me hours to figure out how to get the bootloader unlocked again, cause I had to enter a password to get in, and at the time my girlfriend had no password on her phone at all.
After I figured out about unlocking the bootloader again, I made a password in the security setting, re locked bootloader, still nothing. The password works while phone's bootloader is unlocked, but not while it's locked.
I made a video to further explain and show the situation.
https://www.youtube.com/watch?v=YBtQW00JsNU
Click to expand...
Click to collapse
I watched your video,
Before you relock the bootloader you must install the stock recovery for your device, you can't relock while TWRP is installed, use this guide, (read the guide once completely before you start).
https://forums.oneplus.com/threads/...-3-3t-and-go-back-completely-to-stock.456232/
Also make shure you use the latest ADB drivers Inside (SDK Platform-Tools) from google:
https://developer.android.com/studio/releases/platform-tools
Good Luck!
It worked like a charm. Thank you!