Hi guys, this is my first post here
I have a Moto G4 that I rooted recently and flashed with good ROMs for testing, but in all ROMs, Encryption doesn't work.
In all times that I tried, I go on Settings > Encrypt and start, but always remaining 00:00 for a lot or hours and when I restart phone, I enter with password and display this error.
Decryption unsuccessful. The password you entered is correct but unfortunately your data is corrupt
Click to expand...
Click to collapse
Then I have a question, encryption doesn't work on rooted Moto G4? If yes, have other option to protect my data on rooted device?
Thanks.
joubertredrat said:
Hi guys, this is my first post here
I have a Moto G4 that I rooted recently and flashed with good ROMs for testing, but in all ROMs, Encryption doesn't work.
In all times that I tried, I go on Settings > Encrypt and start, but always remaining 00:00 for a lot or hours and when I restart phone, I enter with password and display this error.
Then I have a question, encryption doesn't work on rooted Moto G4? If yes, have other option to protect my data on rooted device?
Thanks.
Click to expand...
Click to collapse
In my knowledge, encryption will not work on rooted phones. But there is a workaround for this. You can root your phone after the phone is fully encrypted. To root your phone after it is encrypted, you can click adb sideload on TWRP and through the terminal on your pc, you can sideload phh's superuser. Reboot your phone and you have a working, encrypted phone with root installed. I didn't try this, but I think, it will work.
@stkpxl thanks for the help, but I have a question.
Will be possible to make encryption with SD card as extended internal storage? Thanks
@stkpxl I'm trying to flash LineageOS after flash Magisk but response error 7. What wrong about this? Thanks.
stkpxl said:
You flash Lineage before flashing Magisk.
Click to expand...
Click to collapse
I really trying, but isn't working, look my steps.
- Flash Stock ROM like this post http://www.stechguide.com/download-stock-firmware-of-moto-g4-and-g4-plus/
- Run stock, setup first run, format sd and define as internal storage
- Flash recovery twrp-3.0.3-n4-athene_shreps.img
- Run twrp
- Install ElementalX-G4-1.04-LOS.zip
- Run stock, set password and encryption device
- Smartphone restart and stock encrypt device
- Run stock again, password working fine
- Run twrp, twrp ask for encrytion password, I put and enter on twrp normally
- Install lineage-14.1-20170313-nightly-athene-signed.zip without wipe
* Fail on this point
Code:
Installing zip file '/path/to/lineage-14.1-20170313-nightly-athene-signed.zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
Target: <a big number>
detected filesystem ext4 for /dev/block/bootdevice/by-name/system
Can't install this package on top of incompatible data. Please try another package or run a factory reset
Updata process ended with ERROR: 7
Error installing zip file /path/to/lineage-14.1-20170313-nightly-athene-signed.zip
Updating partition details...
...done
This problem display only If I encrypt device on stock ROM, when I flash without encrytion, twrp flash LineageOS normally.
Seems like full disc encryption is not working in general. Its reported https://jira.lineageos.org/browse/BUGBASH-253
I am also quite sure that this bug was already in cyanogenmod and also reported there.
tonymarschall- said:
Seems like full disc encryption is not working in general. Its reported https://jira.lineageos.org/browse/BUGBASH-253
I am also quite sure that this bug was already in cyanogenmod and also reported there.
Click to expand...
Click to collapse
Thanks for reply @tonymarschall
Are you know any custom ROM that encryption is working for me test here? Thanks
joubertredrat said:
Are you know any custom ROM that encryption is working for me test here? Thanks
Click to expand...
Click to collapse
No, I am sorry and searching by myself. I hope that one day it will be official supported. Maybe you can give the issue an upvote.
Hi guys.
A bug related about encryption fail was solved and encryption is working fine on lineage-14.1-20170501-nightly-athene-signed.zip
https://jira.lineageos.org/browse/BUGBASH-253
Related
Disclaimer: I have done these steps multiple times and haven't come across any issues
Read All Step carefully. Any issues or damage to your phone that occurs while doing this I am not responsible.
If TWRP asks you for Password to decrypt data & maybe you have important data in you device, So you can't format data.
Follow these steps:
1. Download the OxygenOS full zip file (tested on 4.0.1 & above)
2. Open TWRP.
3. When It asks for password, cancel it.
4. Click "Read Only" button.
5. Install the OxygenOS zip file.
6. Reboot.
7. The OS may misbehave.
8. Open TWRP again. & Boom! No encryption password.
9. Connect to PC and copy the Important data.
10. Flash Any ROM now.
Thanks!
Recently I had to type in the password but I didn't know that it is possible to bypass it with this...
svandasek said:
Thanks!
Recently I had to type in the password but I didn't know that it is possible to bypass it with this...
Click to expand...
Click to collapse
Glad it helped you
ah.... if i only knew :crying:
That's good from a data recovery point of view... but it just sucks from a security point of view.
Not sure if I should be happy or concerned
TWRP Encryption ByPass
maddler said:
That's good from a data recovery point of view... but it just sucks from a security point of view.
Not sure if I should be happy or concerned
Click to expand...
Click to collapse
Agree .... that seems like a gaping security vulnerability. :-/
maddler said:
That's good from a data recovery point of view... but it just sucks from a security point of view.
Not sure if I should be happy or concerned
Click to expand...
Click to collapse
There's no need to be concerned (about this, specifically).
tk8lm6 said:
Agree .... that seems like a gaping security vulnerability. :-/
Click to expand...
Click to collapse
Actually, this is a case where this device is more secure than previous devices. The encryption key for your user data is divided into two parts. First is the part you type in when booting. The other half is stored in the "secure element" (TrustZone) inside the processor, and is unique to your phone. How the OP3 improves this is that it actually stores two versions of the device-specific key. One is used when the system is trusted (the kernel is signed and dm-verity passes), and the other is used when it is untrusted. This is part of what wipes your data when you unlock the bootloader. The security benefit comes from the SoC locking down the encryption keys when verification fails. Going back to the stock ROM causes all of the verification to pass, and the keys stored in the TrustZone are allowed to unlock your data partition.
On the other hand, if this allows you to bypass manually-enabled encryption, that would be a major security problem.
What interests me is that installing OOS should replace TWRP with the stock recovery image, but this appears not to have happened. Or did you have to flash TWRP again from fastboot after booting into OOS?
smaeul said:
There's no need to be concerned (about this, specifically).
Actually, this is a case where this device is more secure than previous devices. The encryption key for your user data is divided into two parts. First is the part you type in when booting. The other half is stored in the "secure element" (TrustZone) inside the processor, and is unique to your phone. How the OP3 improves this is that it actually stores two versions of the device-specific key. One is used when the system is trusted (the kernel is signed and dm-verity passes), and the other is used when it is untrusted. This is part of what wipes your data when you unlock the bootloader. The security benefit comes from the SoC locking down the encryption keys when verification fails. Going back to the stock ROM causes all of the verification to pass, and the keys stored in the TrustZone are allowed to unlock your data partition.
On the other hand, if this allows you to bypass manually-enabled encryption, that would be a major security problem.
What interests me is that installing OOS should replace TWRP with the stock recovery image, but this appears not to have happened. Or did you have to flash TWRP again from fastboot after booting into OOS?
Click to expand...
Click to collapse
No arguing that previous versions were less secure. But, still, as long as there's a way to bypass encryption that's a security failure.
Encrypted data shouldn't be made available unless proper key(s) or passwords have been provided.
If that's the way that's meant to work, then that's flawed by design.
smaeul said:
There's no need to be concerned (about this, specifically).
Actually, this is a case where this device is more secure than previous devices. The encryption key for your user data is divided into two parts. First is the part you type in when booting. The other half is stored in the "secure element" (TrustZone) inside the processor, and is unique to your phone. How the OP3 improves this is that it actually stores two versions of the device-specific key. One is used when the system is trusted (the kernel is signed and dm-verity passes), and the other is used when it is untrusted. This is part of what wipes your data when you unlock the bootloader. The security benefit comes from the SoC locking down the encryption keys when verification fails. Going back to the stock ROM causes all of the verification to pass, and the keys stored in the TrustZone are allowed to unlock your data partition.
On the other hand, if this allows you to bypass manually-enabled encryption, that would be a major security problem.
What interests me is that installing OOS should replace TWRP with the stock recovery image, but this appears not to have happened. Or did you have to flash TWRP again from fastboot after booting into OOS?
Click to expand...
Click to collapse
I've tried many times. OOS replaces TWRP only on CLEAN Instal for me.
hey guys, i tried to flash oos 5.0 zip, before that i was on another rom. wiped data, system, cache and flashed oos 5.0. and now internal storage is encrypted. how do i flash the zip in twrp now?
manchitro said:
hey guys, i tried to flash oos 5.0 zip, before that i was on another rom. wiped data, system, cache and flashed oos 5.0. and now internal storage is encrypted. how do i flash the zip in twrp now?
Click to expand...
Click to collapse
Just flash it.
Wait, are you saying by just installing a zip, the encrypion hardware pass is gone? WTF.. Is such "hack" available on other devices? Xiaomi redmi(s) for example?
hey i am not able to see any of my files or the zip itself within? is there anything to resolve that?
i can boot into os but for whatever reason cant get to twrp. i have the backup .imgs on my pc now too can i sideload a restore?
im stuck not able to get twrp to see any of my storage and i cant get into twrp twice in a row, so if i fastboot and flash twrp thru adb and then boot into twrp, it asks me for the password, if i hit cancel it just shows 0 storage. ive tried to go to adb sideload but it just sits there. I have the backup i made thru twrp before trying to update.
SourPower said:
hey i am not able to see any of my files or the zip itself within? is there anything to resolve that?
i can boot into os but for whatever reason cant get to twrp. i have the backup .imgs on my pc now too can i sideload a restore?
im stuck not able to get twrp to see any of my storage and i cant get into twrp twice in a row, so if i fastboot and flash twrp thru adb and then boot into twrp, it asks me for the password, if i hit cancel it just shows 0 storage. ive tried to go to adb sideload but it just sits there. I have the backup i made thru twrp before trying to update.
Click to expand...
Click to collapse
Yeah same issue here, as soon as I go in twrp and can't type the password, I can't access my files which is expected behavior, so I don't understand how you can access the file to flash from twrp.
Can someone detail please?
---------- Post added at 07:06 PM ---------- Previous post was at 06:40 PM ----------
Actually I just found a way out to get to previous twrp version, and all is back to normal
From your running ROM, you can download the application twrp (root needed oc)
Then you can use it to flash recovery.
I always keep former version file so I could revert to bluspark twrp that was working before. All worked as expected!
Still not solving the encryption password issue when flashing new recent twrp..
Android 10 Encryption / Security Issue - ADB Encryption Bypass?
rahulrs0029 said:
Disclaimer: I have done these steps multiple times and haven't come across any issues
Read All Step carefully. Any issues or damage to your phone that occurs while doing this I am not responsible.
If TWRP asks you for Password to decrypt data & maybe you have important data in you device, So you can't format data.
Follow these steps:
1. Download the OxygenOS full zip file (tested on 4.0.1 & above)
2. Open TWRP.
3. When It asks for password, cancel it.
4. Click "Read Only" button.
5. Install the OxygenOS zip file.
6. Reboot.
7. The OS may misbehave.
8. Open TWRP again. & Boom! No encryption password.
9. Connect to PC and copy the Important data.
10. Flash Any ROM now.
Click to expand...
Click to collapse
Does this only affect the TWRP -encryption, because when you set your lockscreen password (for the auto-encrypted userdata partition in Android 10, for example) the data can't be decrypted without this password..?
I have discovered another security issue however on a rooted device:
On my Magisk-rooted and encrypted Note 10+/Exynos (Android 10) I just found out, that the userdata (data/data ) partition is UNENCRYPTED and fully readable when viewed with an ADB viewer from my PC although the device is in lockscreen mode / locked!
This doesn't happen after reboot before the first unlock! After the device has been unlocked, accessed via ADB and re-locked (but not rebooted) it is (still) unencrypted, even after rebooting the PC!
Here the lockscreen password would not make much sense at every screenlock - it just unlocks the screen which can be bypassed and all data can be read via ADB anyway - it would only make sense once at boot. Is there a way to have two passwords (1 at boot and an easier one at screenlock) for example?
Is this issue related to Magisk? And can it be fixed?
monicaONxda said:
Does this only affect the TWRP -encryption, because when you set your lockscreen password (for the auto-encrypted userdata partition in Android 10, for example) the data can't be decrypted without this password..?
I have discovered another security issue however on a rooted device:
On my Magisk-rooted and encrypted Note 10+/Exynos (Android 10) I just found out, that the userdata (data/data ) partition is UNENCRYPTED and fully readable when viewed with an ADB viewer from my PC although the device is in lockscreen mode / locked!
This doesn't happen after reboot before the first unlock! After the device has been unlocked, accessed via ADB and re-locked (but not rebooted) it is (still) unencrypted, even after rebooting the PC!
Here the lockscreen password would not make much sense at every screenlock - it just unlocks the screen which can be bypassed and all data can be read via ADB anyway - it would only make sense once at boot. Is there a way to have two passwords (1 at boot and an easier one at screenlock) for example?
Is this issue related to Magisk? And can it be fixed?
Click to expand...
Click to collapse
Anyone with thoughts on this...?
monicaONxda said:
Anyone with thoughts on this...?
Click to expand...
Click to collapse
There are two, separate passwords. One for the encryption and one for the lock screen. And they don't have to be the same.
If you remove the encryption by formatting /data and then boot up on stock OOS, it will encrypt /data with a default password. TWRP can decrypt /data because it knows the default password that's used.
When you set the lock screen password you have the option to set the encryption password to be the same or not.
So, you could set the lock screen and encryption password to be something and then change the lock screen password only to be something different.
ADB can only access /data after it has been decrypted, ie the phone has booted up. But only if: 1. ADB is enabled, 2. You have given permission on your phone to trust the PC connecting to the phone.
So, there's no back doors here. If you have set an encryption password, you can't access the data without having entered the password. And you can't access the phone data without entering the lock screen password. And you can't access the data via ADB unless you have given the specific PC permission from your phone.
Of course, if you use the default encryption password and have TWRP installed, you might just as well not have a password at all. But that's up too you.
Sent from my OnePlus 3T using XDA Labs
BillGoss said:
When you set the lock screen password you have the option to set the encryption password to be the same or not.
So, you could set the lock screen and encryption password to be something and then change the lock screen password only to be something different.
Click to expand...
Click to collapse
For which roms is this working? I guess this behaviour is rom spefic. E.g. for all lineageos 15.1 and 16.0 roms and all roms based on tje same code base, the above procedure (setting the lockscreen passphrase without the boot passphrase checkbox set) will reset the boot passphrase to "default_password".
The only way I know of to get a seperate passphrase for boot and lockscreen on los15, los16 and roms based on these is this:
https://forum.xda-developers.com/on...eplus-3-3t-t3866517/post80390263#post80390263
nvertigo67 said:
For which roms is this working? I guess this behaviour is rom spefic. E.g. for all lineageos 15.1 and 16.0 roms and all roms based on tje same code base, the above procedure (setting the lockscreen passphrase without the boot passphrase checkbox set) will reset the boot passphrase to "default_password".
The only way I know of to get a seperate passphrase for boot and lockscreen on los15, los16 and roms based on these is this:
https://forum.xda-developers.com/on...eplus-3-3t-t3866517/post80390263#post80390263
Click to expand...
Click to collapse
'setting the lockscreen passphrase without the boot passphrase checkbox set) will reset the boot passphrase to "default_password"' - Ah, sorry, I didn't realise that. I was saying this based on what I had done on another phone.
Sent from my OnePlus 3T using XDA Labs
BillGoss said:
'setting the lockscreen passphrase without the boot passphrase checkbox set) will reset the boot passphrase to "default_password"' - Ah, sorry, I didn't realise that. I was saying this based on what I had done on another phone.
Sent from my OnePlus 3T using XDA Labs
Click to expand...
Click to collapse
I'm pretty sure this behavior is rom dependent and not device dependent. E.g.: in los14 and early los15 builds the user was able to set lockscreen passphrase and boot passphrase seperately from rom's settings. This has been removed from aosp (officially because of "security concerns"; but I guess these "concerns" has been too many users with too less knowledge have locked up the boot process).
For me the cryptfs cli is perfectly ok, for the average user the behaviour you've expirienced may feel more comfortable. But the longer I think about, the more I like the seperate setting... YMMV.
Good evening,
I have the following situation in TWRP:
1. I have waited 7 days to release the OEM.
2. After that I installed TWRP via ODIN, and logged into Recovery.
3. As usual the DATA folder was unavailable (Encrypted) and had to do FORMAT DATA, placing yes, etc ....
4. After that I was able to access, I installed Magisk and RMM STATE.
*********I also tested using SuperSu, NO-VERITY, and RMM STATE, and the same thing happened.
5. Everything wonderful, I accessed the system, the OEM remains unlocked, in the download mode has no PRE NORMAL, I can access ROOT softwares a marvel.
6. But here comes the problem, whenever I enter the TWRP it is with the DATA folder unavailable, that is, I have to redo FORMAT DATA.
7. If you do FORMAT, it restarts the procedure from the beginning.
The version of TWRP that I use is correct, the ROM is last STOCK Brazil ZTO.
I have no idea what to do.
Link to TWRP I'm downloading
https://twrp.me/samsung/samsunggalaxys8.html
I read the link below the information below, it would have some connection with the problem:
This device uses dm-verity!
This means that if you allow the system to be modified, it will prevent you from being able to boot if you are using the kernel stock. In order to bypass dm-verity's boot prevention, you will have to install a kernel that has disabled dm-verity in the fstab.
Problem solved through link:
https://forum.xda-developers.com/ga...-twrp-oreo-t3769254/post76036701#post76036701
You are asking for help, and it just so happens that there is a forum meant specifically for that.
SirSoviet said:
You are asking for help, and it just so happens that there is a forum meant specifically for that.
Click to expand...
Click to collapse
Good afternoon.
Would you link to it?
'Cause I thought I'd go in with recovery.
I have tested everything I read in the forum and it is not right.
Problem solved through link:
https://forum.xda-developers.com/ga...-twrp-oreo-t3769254/post76036701#post76036701
Hello community!
First of all, I feel I have to apologize to you all since I know I have clogged the forum with a lot of requests of help about upgrading my smartphone... They are scattered all over the place so I have decided to gathered in a definitive one.
I have edited this post to make it a comprehensive guide for all the people who want to upgrade their HUAWEI P8 LITE ALICE from the stock Android 5.0.1 to the Resurrection Remix N v5.8.5. Before go any further I want you to read the following disclaimer:
PLEASE PLEASE PLEASE READ THIS!!
I am not a developer. I am not a programmer. I have been greatly helped by the user Botar230 so, unfortunately, I cannot help you in case of problems. I myself had problems and had to ask for help. The only thing I can say is to be always polite and try to explain, as best as you can, what's going on.
I will try to be as much clear as possible here but keep in mind that english is not my native language so it is possible that I might mistaking something. My apologize. I am not responsible for any damage you may do to your mobile and I am not responsible to any data loss it may occur. You should ALWAYS do a backup before proceeding. ALWAYS.
I've decided to flash Resurrection Remix N v5.8.5. because it is pre-rooted with Magisk.
BEFORE start to upgrade your mobile, read all this post twice and be sure to understood all the things I have written here. Check the links, check if you have the correct files, check if your mobile is fully charged, check if the bootloader is unlocked, check if you have the right ADB files and drivers downloaded and installed. Please do it BEFORE you start everything.
Done? Everything is fine? So, here we go!
GOAL: Moving from stock Android 5.0.1 to Resurrection Remix N v5.8.5.
MY MOBILE: Huawei P8 Lite ALICE (ALE-L21) unbranded single SIM - Build number: BalongC50B311 - Kernel 3.10.61-gcd3fde7 - EMUI 3.1
BOOTLOADER STATUS: unlocked, checked via ADB
The build number and the kernel number might differ. You should check them carefully and search around this forum how to proceed properly. Also, I totally don't know what to do if you have a double SIM phone. Sorry.
These are the files I have downloaded and put on the MicroSD before starting the whole process:
b895_update.zip
open_gapps-arm64-7.1-nano-20180702
RR-N-v5.8.5-20180302-alice-OpenKirin.zip
The file TWRP_3.1.1-0_ALICE_BL.img have to be put in the same directory where adb.exe is since you will flash it via adb command: fastboot flash recovery TWRP_3.1.1-0_ALICE_BL.img once you have entered in fastboot mode AND you have checked that your bootloader is unlocked.
Now, the next steps that worked for me are:
install TWRP_3.1.1-0 via ADB
Factory reset (Wipe -> Swipe to wipe)
update the device with b895_update to get Android 6.0 and EMUI 4 (by putting b895_update on the SD card and flash it via TWRP previously installed or via sideload as suggested by Botar230. I find myself comfortable to use ADB.)
install again TWRP_3.1.1-0_ALICE_BL via ADB or via sideload
Flash RR-N-v5.8.5-20180302-alice-OpenKirin) via TWRP AND at the same time...
Flash Open Gapps via TWRP. You HAVE TO USE THE ARM64 - 7.1 VERSION!!!
Reboot your device. It is done! :good:
NOTE!! Updating the phone to b895 will take really a lot of time. Seriously. It might be scary but it's ok. It will update EMUI too.
NOTE!! When you install TWRP via ADB, the TWRP_3.1.1-0_ALICE_BL.img file MUST BE in the same directory where the adb.exe file is.
At this point, everything should be fine, working and squeaky clean!
The ROM is pre-rooted with Magisk and that's pretty cool!
At this point I think my brief tutorial is over. If you find out something important missing or wrong, please point it out! It will help other people! Thank you!
Some links about ADB that I found quite useful:
How to Install TWRP Recovery via Fastboot On Any Android Device
How to Use ADB & Fastboot Commands with your Android Device
ADB Shell
Once again I have to thank the immense patience of BOTAR230 and all the people that worked so hard to make everything possible: I mean the guys (and gals? Maybe, I don't know... ) behind the Resurrection Remix ROM, behind the TWRP project and the Open Gapps and the many more I probably forgot! Thanks everyone!
DaGreatAssyr said:
Hello community!
First of all, I feel I have to apologize to you all since I know I have clogged the forum with a lot of requests of help about upgrading my smartphone... They are scattered all over the place so I have decided to gathered in a definitive one.
Next, I am quite insecure on all the steps so I will try to make a comprehensive list and keep it updated hoping it will help all the Huawei P8 Lite ALICE users that will do the same process I am about to do. Let's proceed!
GOAL: Moving from stock Android 5.0.1 to OpenKirin's MoKee
MY MOBILE: Huawei P8 Lite ALICE (ALE-L21) unbranded single SIM - Build number: BalongC50B311 - Kernel 3.10.61-gcd3fde7 - EMUI 3.1
BOOTLOADER STATUS: unlocked, checked via ADB
Now, the next steps would be to root the mobile. My wild guess are
install TWRP_3.1.1-0_ALICE_BL via ADB
install Magisk to root Android 5.0.1
At this point I am not perfectly sure if those steps are right AND if Magisk is the right choice to root Android 5.0.1 on my mobile. Are there other ways to do that?
Once the device is rooted, the next steps should be:
update the device with b895_update to get Android 6.0 and EMUI 4 (by putting b895_update on the SD card and flash it via TWRP previously installed)
install again TWRP_3.1.1-0_ALICE_BL via ADB
install again Magisk to root Android 6.0
install pa_alice-7.3.1-EOL-20180203 (or RR-N-v5.8.5-20180302-alice-OpenKirin)
That's the theory. I've used SR5-SuperSU-v2.82-SYSTEMMODE but it bricked the phone after I updated to Android 6.0 and the user Botar230 told me that it is no longer updated and used and suggested me to use Magisk instead.
The files I have are:
b895_update.zip
open_gapps-arm-7.1-stock-20180626.zip
RR-N-v5.8.5-20180302-alice-OpenKirin.zip
pa_alice-7.3.1-EOL-20180203.zip
TWRP_3.1.1-0_ALICE_BL.img
Previously, I have updated my device to Android 6.0 and installed TWRP 3.1.1-0 and everything went really good. When I tried to root the phone with SuperSU-v2.82, it bricked. Now the phone is restored to its initial conditions, brandless.
I have read THIS POST but it's pretty old and most of the link there are not working anymore.
So, if someone is kindly willingly to give me a hand (yeah, another one, I know... ) on this subject, I'd really appreciate it. Again.
Thanks in advance!
Click to expand...
Click to collapse
I didn't fully understand you, so I'll write a quick guide how to move from stock android 5.0.1 to any other custom ROM (I've read that you already unlocked your bootloader and flashed twrp so I'll skip those two)
First of all, use this version of TWRP.
1. Boot into TWRP
2. Factory reset (Wipe -> Swipe to wipe)
3. Flash B896 update (B895 is fine too)
4. Flash TWRP (Install -> Select image -> Recovery)
5. Flash a custom ROM of your choice
6. Flash Open GAPPS (I recommend flashing NANO version)
7. (Optionally) Flash Magisk if your custom ROM isn't pre-rooted (if unsure, check the root status before flashing)
Fun fact: You don't need to put every file on SD card to flash it. You can also use sideload
Botar230 said:
I didn't fully understand you, so I'll write a quick guide how to move from stock android 5.0.1 to any other custom ROM (I've read that you already unlocked your bootloader and flashed twrp
Click to expand...
Click to collapse
Hello Botar230! At the present time, I only unlocked the bootloader.
No TWRP installed so far.
Thank you for adding some steps I have missed (like the factory reset and the GApps! :good: )!!
The TWRP version I have is the same you suggested me so this is fine!
Yes, now that I think about, nearly all the custom ROM are pre-rooted and there's an option to switch the root in the setting panel but I will check it eventually.
I have make corrections in my list after your suggestion:
install TWRP_3.1.1-0_ALICE_BL via ADB
Factory reset (Wipe -> Swipe to wipe)
update the device with b895_update to get Android 6.0 and EMUI 4 (by putting b895_update on the SD card and flash it via TWRP previously installed or via sideload)
install again TWRP_3.1.1-0_ALICE_BL via ADB or via sideload
install pa_alice-7.3.1-EOL-20180203 (or RR-N-v5.8.5-20180302-alice-OpenKirin)
Flash open_gapps-arm-7.1-nano-20180630
Check whether the ROM is rootable and eventually flash Magisk
The files I have are:
b895_update.zip
open_gapps-arm-7.1-stock-20180626.zip (I will not use these)
open_gapps-arm-7.1-nano-20180630.zip (I will use these one! )
RR-N-v5.8.5-20180302-alice-OpenKirin.zip
pa_alice-7.3.1-EOL-20180203.zip
TWRP_3.1.1-0_ALICE_BL.img
Everything looks good now. Btw you don't need to flash nano gapps exclusively, it's just a matter of your personal preference which one you choose.
Sent from my LG-K220 using XDA Labs
Botar230 said:
Btw you don't need to flash nano gapps exclusively, it's just a matter of your personal preference which one you choose.
Click to expand...
Click to collapse
To be honest, I don't know what to choose between all the options I have seen on the website. Let's say that if the installation works properly it's a matter of seconds to make a backup and try another Gapp. For the moment I will follow your suggestion.
That's what I have done so far:
install TWRP_3.1.1-0_ALICE_BL via ADB DONE AND OK!
Factory reset (Wipe -> Swipe to wipe) DONE AND OK!
update the device with b895_update to get Android 6.0 and EMUI 4 (by putting b895_update on the SD card and flash it via TWRP previously installed or via sideload) DONE AND OK!
install again TWRP_3.1.1-0_ALICE_BL via ADB or via sideload DONE AND OK!
Everything is working fine so far but I am a little bit nervous about these one. I will take a deep breathe and I will proceed right now. I can flash the ROM and the Gapps with TWRP, right? I am mostly sure about but a confirm could ease my fear of bricking the phone again... :silly:
install pa_alice-7.3.1-EOL-20180203 (or RR-N-v5.8.5-20180302-alice-OpenKirin)
Flash open_gapps-arm-7.1-nano-20180630
Check whether the ROM is rootable and eventually flash Magisk
DaGreatAssyr said:
To be honest, I don't know what to choose between all the options I have seen on the website. Let's say that if the installation works properly it's a matter of seconds to make a backup and try another Gapp. For the moment I will follow your suggestion.
That's what I have done so far:
install TWRP_3.1.1-0_ALICE_BL via ADB DONE AND OK!
Factory reset (Wipe -> Swipe to wipe) DONE AND OK!
update the device with b895_update to get Android 6.0 and EMUI 4 (by putting b895_update on the SD card and flash it via TWRP previously installed or via sideload) DONE AND OK!
install again TWRP_3.1.1-0_ALICE_BL via ADB or via sideloadDONE AND OK!
Everything is working fine so far but I am a little bit nervous about these one. I will take a deep breathe and I will proceed right now. I can flash the ROM and the Gapps with TWRP, right? I am mostly sure about but a confirm could ease my fear of bricking the phone again... :silly:
install pa_alice-7.3.1-EOL-20180203 (or RR-N-v5.8.5-20180302-alice-OpenKirin)
Flash open_gapps-arm-7.1-nano-20180630
Check whether the ROM is rootable and eventually flash Magisk
Click to expand...
Click to collapse
Yes, everything is correct.
Sent from my LG-K220 using XDA Labs
Botar230 said:
Yes, everything is correct.
Click to expand...
Click to collapse
First of all, thank you for your immense patience!!
That's what happened so far:
install TWRP_3.1.1-0_ALICE_BL via ADB DONE AND OK!
Factory reset (Wipe -> Swipe to wipe) DONE AND OK!
update the device with b895_update to get Android 6.0 and EMUI 4 (by putting b895_update on the SD card and flash it via TWRP previously installed or via sideload) DONE AND OK!
install again TWRP_3.1.1-0_ALICE_BL via ADB or via sideload DONE AND OK!
install pa_alice-7.3.1-EOL-20180203 (or RR-N-v5.8.5-20180302-alice-OpenKirin) DONE AND OK!
I had to install the open_gapps-arm64 since the system required the ARM64 but apart that...
Flash open_gapps-arm64-7.1-stock-20180630.zip DONE BUT NOT OK! - I've tried to install the NANO and the STOCK Gapps but every time I got the same error message on TWRP: "failed to mount data: operation not supported on transport endpoint". Google Play and all the Google apps cannot connect: the Google error message is always the same: "couldn't sign in". I've double checked the login and they work both on my PC and on the other phones so I'm sure they are correct. Now I'm searching what kind of error it is but I'm not finding much infos about. Plus, there is the warning message saying that "Google Play services has stopped" and it keeps popping on the screen.
Check whether the ROM is rootable and eventually flash Magisk NOT DONE YET but it seems that it is not pre-rooted.
I am searching the web to understand what's going on here.
It's probably because the custom ROM that you've chosen uses f2fs file system on /data partition instead of ext4. Try to do this:
Boot to TWRP -> Wipe -> Advanced wipe -> Choose Data -> Repair or change file system. From here you can see if the file system of /data is ext4 or f2fs. If it's f2fs, then click Change file system and choose ext4.
Before doing all of this, you should flash b895 again, do a factory reset, flash twrp, flash your custom ROM, change /data file system, and finally gapps so there will be no conflicts between old and new gapps.
Hello again!
Sorry for the silence, got some busy day but here I am.
Before doing what you told me, I've tried to do a backup with TWRP and I've been flooded with error messages:
failed to mount '/data' (Operation not supported on transport endpoint)
Unable to recreate /data/media folder
Unable to mount storage
failed to mount '/data' (Operation not supported on transport endpoint)
Unable to mount /data/media/TWRP/.twrps
And, of course, the backup process failed.
At this point I cannot do anything with TWRP.
I cannot backup, cannot flash a ROM or a ZIP.
The phone works fine, it boots and I got no problems. I can boot it via ADB too.
I'm really scared it will brick or loop sooner or later. I am keeping it turned off and wait for any other advice before proceeding since it would be quite pesky to restart from scratch again....
Following your directions I've seen that the data file system is ext3.
DaGreatAssyr said:
Hello again!
Sorry for the silence, got some busy day but here I am.
Before doing what you told me, I've tried to do a backup with TWRP and I've been flooded with error messages:
failed to mount '/data' (Operation not supported on transport endpoint)
Unable to recreate /data/media folder
Unable to mount storage
failed to mount '/data' (Operation not supported on transport endpoint)
Unable to mount /data/media/TWRP/.twrps
And, of course, the backup process failed.
At this point I cannot do anything with TWRP.
I cannot backup, cannot flash a ROM or a ZIP.
The phone works fine, it boots and I got no problems. I can boot it via ADB too.
I'm really scared it will brick or loop sooner or later. I am keeping it turned off and wait for any other advice before proceeding since it would be quite pesky to restart from scratch again....
Following your directions I've seen that the data file system is ext3.
Click to expand...
Click to collapse
Don't worry, it won't brick. Maybe the internal storage is encrypted. In order to remove encryption, go to Wipe -> Format data.
Hello Botar230! Something funny (in a very positive way) happened! I did as you told me: I booted in recovery mode and went to WIPE -> FORMAT DATA.
Then I considered to install the other ROM I had, RR-N-v5.8.5-20180302-alice-OpenKirin and it has been the best idea I could have!!! :laugh:
After I formatted the data, I rebooted in recovery mode and checked that the problems where all disappeared and they actually did. Then I flashed the OpenKirin ROM and the Nano Gapps you told me.
SURPRISE SURPRISE the OpenKirin ROM is pre-rooted with Magisk 15.3 and the installation, this time, went perfectly fine without any trouble! Plus, Magisk updated to the latest version, the 16!
As I promised, I will now update my first post on how to upgrade my mobile phone hoping it will be useful for someone else but first I want to enjoy my brand new phone!
And, of course, I want to thank you for all the support you gave me in these days! You have been really patient and kind! I am really sorry I cannot help you back since (as you have noticed...) I am not much of an expert so all I can give you is my gratitude and thankfulness! THANK YOU 1000 TIMES BOTAR!! :highfive:
You're welcome. Have a nice day! :highfive:
Sent from my LG-K220 using XDA Labs
after doing this https://forum.xda-developers.com/v20/how-to/step-step-guide-lg-v20-h918-unlocking-t3808258
and finally installing a stock based rom, which is Alpha Omega Rom. I get stuck at secure startup and telling that decryption unsuccessful. I tried it with other stock based rom like a prerooted one but the result are still the same. I am never new to this problem and usually this get solved by going to twrp and wiping data(the one you have to type yes) but it did not solve this problem. Really need help badly.
noddledizzy said:
after doing this https://forum.xda-developers.com/v20/how-to/step-step-guide-lg-v20-h918-unlocking-t3808258
and finally installing a stock based rom, which is Alpha Omega Rom. I get stuck at secure startup and telling that decryption unsuccessful. I tried it with other stock based rom like a prerooted one but the result are still the same. I am never new to this problem and usually this get solved by going to twrp and wiping data(the one you have to type yes) but it did not solve this problem. Really need help badly.
Click to expand...
Click to collapse
it seems youre trying to flash a new twrp image that is higher than the allowed 3.2.3-4 in the root process,go to fastboot mode reflash twrp image 3.2.3-4 or an older one.If that's not the issue please provide more information
mikekote666 said:
it seems youre trying to flash a new twrp image that is higher than the allowed 3.2.3-4 in the root process,go to fastboot mode reflash twrp image 3.2.3-4 or an older one.If that's not the issue please provide more information
Click to expand...
Click to collapse
Where does it exactly say that I cannot flash anything higher than 3.2.3-4. All it says is to download the latest twrp from https://forum.xda-developers.com/v20/development/recovery-twrp-3-2-1-0-t3720239
Do you have a link to 3.2.3-4? It seems like 3.2.3-5 is the lowest twrp I could find in Phoenix591's android filehost https://androidfilehost.com/?w=files&flid=235271
edit: while waiting for responses, I went ahead and installed unofficial LOS15 then I was able to boot without any problem. It seem like this will only happen with stock/stock based roms.
noddledizzy said:
Where does it exactly say that I cannot flash anything higher than 3.2.3-4. All it says is to download the latest twrp from https://forum.xda-developers.com/v20/development/recovery-twrp-3-2-1-0-t3720239
Do you have a link to 3.2.3-4? It seems like 3.2.3-5 is the lowest twrp I could find in Phoenix591's android filehost https://androidfilehost.com/?w=files&flid=235271
edit: while waiting for responses, I went ahead and installed unofficial LOS15 then I was able to boot without any problem. It seem like this will only happen with stock/stock based roms.
Click to expand...
Click to collapse
You should flash latest after installing this one by installing recovery img in TWRP i am telling you cause i have tried 3.2.3-5+ with the dirty santa process for my phone and thats the message i was getting unless downgrading to 3.2.3-4
Also decryption is unsuccessful comes as a result of not formatting data on twrp after the first install of twrp but you said that you did format data so i thought you were trying to flash newer twrp via the root process of the H918
mikekote666 said:
You should flash latest after installing this one by installing recovery img in TWRP i am telling you cause i have tried 3.2.3-5+ with the dirty santa process for my phone and thats the message i was getting unless downgrading to 3.2.3-4
Also decryption is unsuccessful comes as a result of not formatting data on twrp after the first install of twrp but you said that you did format data so i thought you were trying to flash newer twrp via the root process of the H918
Click to expand...
Click to collapse
do you have 3.2.3-4? I couldn't find it anywhere unfortunately
edit:already solved it by using 3.2.3-0/1 from official twrp website. but the problem is that i get 0mb storage on internal storage on TWRP. I am not exactly new to this problem but even after flashing no verity op encryption zip. I still get it. sigh.
noddledizzy said:
do you have 3.2.3-4? I couldn't find it anywhere unfortunately
edit:already solved it by using 3.2.3-0/1 from official twrp website. but the problem is that i get 0mb storage on internal storage on TWRP. I am not exactly new to this problem but even after flashing no verity op encryption zip. I still get it. sigh.
Click to expand...
Click to collapse
you need to format data first time
noddledizzy said:
after doing this https://forum.xda-developers.com/v20/how-to/step-step-guide-lg-v20-h918-unlocking-t3808258
and finally installing a stock based rom, which is Alpha Omega Rom. I get stuck at secure startup and telling that decryption unsuccessful. I tried it with other stock based rom like a prerooted one but the result are still the same. I am never new to this problem and usually this get solved by going to twrp and wiping data(the one you have to type yes) but it did not solve this problem. Really need help badly.
Click to expand...
Click to collapse
I have this problem too for a couple days a go,
but now it have been fixed.
Flash TWRP 3.2.3 via fastboot
Boot into TWRP
format data
reboot system
done
I think Its TWRP 3.3 bug or something that not decrypt perfectly..
---------- Post added at 01:53 PM ---------- Previous post was at 01:46 PM ----------
noddledizzy said:
do you have 3.2.3-4? I couldn't find it anywhere unfortunately
edit:already solved it by using 3.2.3-0/1 from official twrp website. but the problem is that i get 0mb storage on internal storage on TWRP. I am not exactly new to this problem but even after flashing no verity op encryption zip. I still get it. sigh.
Click to expand...
Click to collapse
Format data
gandyprakoso said:
I have this problem too for a couple days a go,
but now it have been fixed.
Flash TWRP 3.2.3 via fastboot
Boot into TWRP
format data
reboot system
done
I think Its TWRP 3.3 bug or something that not decrypt perfectly..
---------- Post added at 01:53 PM ---------- Previous post was at 01:46 PM ----------
Format data
Click to expand...
Click to collapse
I did format data so many times already that it nuked my twrp(just stopped booting into it all of a sudden, still unsure if that caused it though)
noddledizzy said:
I did format data so many times already that it nuked my twrp(just stopped booting into it all of a sudden, still unsure if that caused it though)
Click to expand...
Click to collapse
Yes me too, and it almost make me crazy back in the days ?
the solution (at least for now) is downgrade TWRP it into v3.2.3-4. flash it via adb fastboot command, format data, then reboot. But sorry i dont have TWRP for H918, becoz im using F800L.. and since your TWRP has been nuked, youll have to reflash TWRP again yes? ?
Or, if youbdont want to downgrade TWRP, you can use AOSP based rom such as LOS15.1.. i already tried that rom and it dont have problem with encrypt/decrypt thing like stock based rom.
gandyprakoso said:
Yes me too, and it almost make me crazy back in the days ?
the solution (at least for now) is downgrade TWRP it into v3.2.3-4. flash it via adb fastboot command, format data, then reboot. But sorry i dont have TWRP for H918, becoz im using F800L..
Or, you can use AOSP based rom such as LOS15.1.
i already tried that rom and it dont have problem with encrypt/decrypt thing like stock based rom.
Click to expand...
Click to collapse
I am currently using v3.2.3.0/1 i couldnt find v3.2.3-4 anywhere.
I am using Resurrection Remix, everything was perfect until i stopped receiving sms once the phone goes deep sleep
noddledizzy said:
I am currently using v3.2.3.0/1 i couldnt find v3.2.3-4 anywhere.
I am using Resurrection Remix, everything was perfect until i stopped receiving sms once the phone goes deep sleep
Click to expand...
Click to collapse
Here it is, hope it helps..
TWRP: https://androidfilehost.com/?fid=11410932744536982445
H918 Prerooted Oreo 20g:
https://androidfilehost.com/?fid=11410932744536989567
H918 SIM Unlock:
https://androidfilehost.com/?fid=11410963190603886898
All credits goes to @Phoenix591
gandyprakoso said:
Here it is, hope it helps..
TWRP: https://androidfilehost.com/?fid=11410932744536982445
H918 Prerooted Oreo 20g:
https://androidfilehost.com/?fid=11410932744536989567
H918 SIM Unlock:
https://androidfilehost.com/?fid=11410963190603886898
All credits goes to @Phoenix591
Click to expand...
Click to collapse
Thank you so much, no wonder i wasn't able to find v3.2.3-4 because it's labeled as the release date. What does the sim unlock do? I mean, I can receive messages and stuff but just not get any once in awhile. Will this actually solve that?
noddledizzy said:
Thank you so much, no wonder i wasn't able to find v3.2.3-4 because it's labeled as the release date. What does the sim unlock do? I mean, I can receive messages and stuff but just not get any once in awhile. Will this actually solve that?
Click to expand...
Click to collapse
Yes i knew that. My TWRP 3.2.3-4 IMG file is labeled with same date like that.
About sim unlock, Actually I dont know for sure because in f800l we dont seeing any sim problem at all.. but in my opinion just download it, in case you seeing problem with locked sim after flashing, it will be very useful..
anyway, i found a thread that discussing about h918 sim unlock thing
https://forum.xda-developers.com/v20/how-to/discussion-t-mobile-sim-unlock-t3821051
gandyprakoso said:
Yes i knew that. My TWRP 3.2.3-4 IMG file is labeled with same date like that.
About sim unlock, Actually I dont know for sure because in f800l we dont seeing any sim problem at all.. but in my opinion just download it, in case you seeing problem with locked sim after flashing, it will be very useful..
anyway, i found a thread that discussing about h918 sim unlock thing
https://forum.xda-developers.com/v20/how-to/discussion-t-mobile-sim-unlock-t3821051
Click to expand...
Click to collapse
Thanks, I will try going back to stock roms and will report back to you.
And I forgot to mention that I already got twrp fixed after it got nuked. Sadly, I don't think fastboot flashing works on h918 so I had to do lafsploit method to flash twrp again.
noddledizzy said:
Thanks, I will try going back to stock roms and will report back to you.
And I forgot to mention that I already got twrp fixed after it got nuked. Sadly, I don't think fastboot flashing works on h918 so I had to do lafsploit method to flash twrp again.
Click to expand...
Click to collapse
Ok then and happy flashing m8 ?
noddledizzy said:
Where does it exactly say that I cannot flash anything higher than 3.2.3-4. All it says is to download the latest twrp from https://forum.xda-developers.com/v20/development/recovery-twrp-3-2-1-0-t3720239
Do you have a link to 3.2.3-4? It seems like 3.2.3-5 is the lowest twrp I could find in Phoenix591's android filehost https://androidfilehost.com/?w=files&flid=235271
edit: while waiting for responses, I went ahead and installed unofficial LOS15 then I was able to boot without any problem. It seem like this will only happen with stock/stock based roms.
Click to expand...
Click to collapse
Where? Right in the portion where it says Known Issues of the first link.
Downgrading TWRP to 3.2.3-4 will fix it. I had the same issue.
Thanks for the notes. Unfortunately this did not work for me. I ended up in this position after updating Magisk to 20.2, or trying to. My H918 went to being stuck in the fastboot mode. I was able to get to TWRP, and reinstalled H91820h.zip, but then faced with "Decryption unsuccessful" I downgraded TWRP to twrp-3.2.3-0, and deleted everything except the external microsd card, reinstalled H91820h.zip, but still stuck at the "Decryption unsuccessful". Are there other things I should try?
Thanks,
Rob
frohro said:
Thanks for the notes. Unfortunately this did not work for me. I ended up in this position after updating Magisk to 20.2, or trying to. My H918 went to being stuck in the fastboot mode. I was able to get to TWRP, and reinstalled H91820h.zip, but then faced with "Decryption unsuccessful" I downgraded TWRP to twrp-3.2.3-0, and deleted everything except the external microsd card, reinstalled H91820h.zip, but still stuck at the "Decryption unsuccessful". Are there other things I should try?
Thanks,
Rob
Click to expand...
Click to collapse
From TWRP thread:
Changed one last thing to try to fix stock Oreo decryption.
There were an upstream TWRP change that should fix the issue where formatting was still leaving /data encrypted as well (this was actually in the last build, but I didn't notice it then)
Click to expand...
Click to collapse
If you still have your non-Encryption-supporting TWRP as download mode, wipe data from there. For some reason which was documented in the TWRP thread, most versions of V20 TWRP doesn't remove the encryption flag even on a full wipe. I've gone through the pain several times, but here's roughly what I went through about a month ago. It's possible that using the latest TWRP may allow you to skip straight to step 8. As of this latest wipe, I'm finally at a point again where my phone works properly and TWRP can still see my data.
Basic process to hopefully have a working ongoing phone and TWRP:
1. Reboot to download-mode TWRP
2. Wipe dalvik/cache/data from the older download-mode TWRP
3. Factory reset with YES, still in older download-mode TWRP
4. Reboot to system; it should give you the new-system-setup past the Decryption unsuccessful screen on your wiped device
5. Setup without a Google account or fingerprint
6. Reboot back to recovery, not download TWRP; use download mode to get there if you need to
7. Flash the latest TWRP version from the thread (no older than October 25, 2019)
8. Reboot back to recovery
9. Wipe dalvik/cache/data
10. Reboot back to system
11. Setup as you like
12. Reboot back to recovery and make sure you can see your storage
If it gets a decryption error on latest TWRP at step 12 and you can't see data while in Recovery, try skipping adding a fingerprint during setup (run through steps 8-12, no fingerprint on 11) and see if that fixes it.
frohro said:
Thanks for the notes. Unfortunately this did not work for me. I ended up in this position after updating Magisk to 20.2, or trying to. My H918 went to being stuck in the fastboot mode. I was able to get to TWRP, and reinstalled H91820h.zip, but then faced with "Decryption unsuccessful" I downgraded TWRP to twrp-3.2.3-0, and deleted everything except the external microsd card, reinstalled H91820h.zip, but still stuck at the "Decryption unsuccessful". Are there other things I should try?
Thanks,
Rob
Click to expand...
Click to collapse
My solution turned out to be formatting /data. Wiping it was apparently not really wiping it clean. Formatting it got me back to a working phone, though I had to re-install everything.
Thanks everyone for the help!
Rob
anyone knows how to fix fingerprints not working? h990 oreo rom mk2000 kernel is there any fix?
do i need to return to nougat but than what? please help
edit: was able to fix that by flashing nougat modem
now wifi wont turn on tho anyone know how to fix?
Hi I need help I'm looking for a guide to root my samsung s8 SM-G950F I have done a search here on the forum but I must say that I am a little confused not all of them work.
Is there anyone who spends some of his time showing me which one to follow ?, my device mounts android 9 until the latest security update on April 1st, I tried some guide where I was told to flash twrp and immediately after dm-variety with rmm ... but every time twrp doesn't do the installation it always says it doesn't mount data or preload or other voices.
WilliamBlake said:
Hi I need help I'm looking for a guide to root my samsung s8 SM-G950F I have done a search here on the forum but I must say that I am a little confused not all of them work.
Is there anyone who spends some of his time showing me which one to follow ?, my device mounts android 9 until the latest security update on April 1st, I tried some guide where I was told to flash twrp and immediately after dm-variety with rmm ... but every time twrp doesn't do the installation it always says it doesn't mount data or preload or other voices.
Click to expand...
Click to collapse
You can still use this guide
https://forum.xda-developers.com/ga...pment/recovery-twrp-galaxy-s8-exynos-t3595102
Use latest versions of twrp,no verity and if needed rmm bypass.
Mounting data error more than likely didn't format data in twrp
Preload error can be fixed in advance wipe menu in twrp.
hello thanks for the answer I have tried more than once but it can't keep giving me errors I don't know where to start so I try to list them all:
once flashed twrp:
1) I can't reboot or bootloop
2) I can't wipe because it doesn't mount data preload partitions and now I don't remember the other voices
3) every zip that I install returns me the error of mounting partitions (obviously I try to install the dm-variety, magisk and obviously rmm ... I don't remember which version after when I access the PC I will tell you better)
4) on reboot it locks me and I can't start the phone it gives me that only the official tracks can be loaded
I hope I have been detailed but unfortunately I have some files and do what I can.
ps. I noticed on the download mode that I stuck frp and the kg in the checking state I don't know what it means
WilliamBlake said:
hello thanks for the answer I have tried more than once but it can't keep giving me errors I don't know where to start so I try to list them all:
once flashed twrp:
1) I can't reboot or bootloop
2) I can't wipe because it doesn't mount data preload partitions and now I don't remember the other voices
3) every zip that I install returns me the error of mounting partitions (obviously I try to install the dm-variety, magisk and obviously rmm ... I don't remember which version after when I access the PC I will tell you better)
4) on reboot it locks me and I can't start the phone it gives me that only the official tracks can be loaded
I hope I have been detailed but unfortunately I have some files and do what I can.
ps. I noticed on the download mode that I stuck frp and the kg in the checking state I don't know what it means
Click to expand...
Click to collapse
If you are getting the message only official binary are allowed to be flash error you will have to flash stock firmware.
KG State has to be in checking mode. If in prenormal mode you can't successfully flash non stock rom.
FRP will need to be turned off.
Also in twrp did you Format Data not wipe.
ok thankyou i'm solved a problem