If you have TWRP installed and FRP locked and no system to boot, this is for you.
This is not my work but it was very hard to find, so many days of flashing and googling.
Flash the zip from this thread to unlock your FRP:
https://forum.xda-developers.com/huawei-p20-lite/development/huawei-solution-unlock-oem-frp-google-t3812445
Then use Pretoriano80 TWRP to restore backups or wipe the system partitions if necessary. This is the only one that worked for me.
Special thanks to:
@ KingOfMezi
@Pretoriano80
:good:
This ZIP also worked on my MediaPad T5... Amazing, thanks!
Related
Hi guys,
I'm on an outdated version of the global beta ROM and have received an OTA notification.
Unfortunately I can't run this as I'm rooted.
Please could you tell me the easiest way of updating the ROM without wiping everything and maintaining root?
Many thanks,
Andy
After flashing Rom root will be gone and if you need root just flash supersu.zip using twrp and you will get root back. That's all
sarthakwarlock said:
After flashing Rom root will be gone and if you need root just flash supersu.zip using twrp and you will get root back. That's all
Click to expand...
Click to collapse
thank you, unfortunately when I get into TWRP it asks for a password. Without a password I can't browse to the downloaded zip.
any idea?
andypa1 said:
thank you, unfortunately when I get into TWRP it asks for a password. Without a password I can't browse to the downloaded zip.
any idea?
Click to expand...
Click to collapse
Reflash Twrp from fastboot.
I've just found in a thread elsewhere:
"It's because of the dm-verity protection included in the MIUI firmwares.
To disable it, you have to:
- Format all encrypted partitions on fastboot (fastboot format system; fastboot format userdata;...)
- Boot on TWRP and flash a MIUI recovery image
- Download this patched boot file
- On fastboot flash the patched boot.img (fastboot flash boot boot-patched.img)
To manually remove the protection from a kernel you have to:
- Extract boot.img from a rom/device
- Unpack it, with this tool for example -> mkbootimg_tools
- Search the fstab file (fstab.qcom for example) and remove the "verify" mention and replace all "forceencrypt" mentions by "encryptable"
- Repack it and flash it"
I don't really understand this, or understand / remember how I managed to flash the global beta rom in the first place?!
So I've done a lot of reading and there are multiple threads with steps that aren't exactly clear or contradict each other or are outdated. I just want clarification on what I believe are the steps to flash a custom rom (7.1.2 since I can wait for 8) on a brand new Pixel XL.
Setup phone to the point of enabling adb debugging and oem unlock
Fastboot unlock
Fastboot boot twrp RC1 img
Flash twrp RC2 zip in twrp
Reboot to installed twrp
Wipe system, data, caches
Flash ROM
Flash twrp again
Reboot to twrp
Flash gapps and root method (magisk working for 7.1.2 or should I be using supersu? Also which versions?)
Flash twrp again??
Boot to ROM then setup and use like normal
Should this give me custom ROM, root and twrp that I can boot directly to without a pc again? As long as I do twrp flashing after a ROM each time it'll stick? Also, I keep seeing things for setting a pin before initial twrp boot but without spending 4 days reading I can't find the reason for it. Should I be flashing vendor, bootloader and radio for the latest Nougat release BEFORE unlocking or can I do it through fastboot prior to unlocking?
Coming from Nexus 6P and that was my first run in with the bootloader, radio and vendors so I want to avoid issues for myself. Phone should be here tomorrow and want to get down to business right away lol.
Any and all information is greatly appreciated. If all of this is answered in a centralized area please point me to it and tell me I'm stupid for missing it.
Sent from my SM-N910P using Tapatalk
Found this over in PN thread. Is it accurate? Seems similar to my process.
https://forum.xda-developers.com/showthread.php?p=73846565
wgrant said:
Fastboot boot twrp RC1 img
Flash twrp RC2 zip in twrp
Reboot to installed twrp
Wipe system, data, caches
Flash ROM
Flash twrp again
Reboot to twrp
Flash gapps and root method (magisk working for 7.1.2 or should I be using supersu? Also which versions?)
Flash twrp again??
Boot to ROM then setup and use like normal
https://forum.xda-developers.com/showthread.php?p=73846565
Click to expand...
Click to collapse
Assuming the bootloader is already unlocked and disregarding the unlocking instruction, these instructions are dead on accurate. I personally dont use magisk, but maybe another user will chime in. For 7.1.2 id use supersu 2.82.
You dont have to flash twrp again after flashing gapps and supersu, but its a good practice to have.
noidea24 said:
Assuming the bootloader is already unlocked and disregarding the unlocking instruction, these instructions are dead on accurate. I personally dont use magisk, but maybe another user will chime in. For 7.1.2 id use supersu 2.82.
You dont have to flash twrp again after flashing gapps and supersu, but its a good practice to have.
Click to expand...
Click to collapse
Thank you very much. I'm about to unlock and go nuts on my phone. New phones are so fun to fiddle with!
if you want to use magisk you'll need to flash a custom kernel before you flash magisk. Also you'll need a modified magisk zip. Search around the thread you'll find one, the latest version I found was magisk v13.3.
Edit: Just found out magisk is officially support for pixel on version 14.1 Check out the magisk beta thread.
I unlocked the bootloader on my device previously. I hadn't rooted it yet, just haven't had the time. I'm ready to do so now, and i've read that you need to boot to this modified version of TWRP and use it to flash the TWRP image to the device, in doing so it flashes it to both the A/B partition of the device. I know you are always supposed to do good backups when you are doing these types of mods, BUT is it by functionality going to clear the device when it writes TWRP to both the A/B partition? When flashing TWRP to any other device that has never been the case. I just wondered if this works differently given the dual partition setup?
Afterwards I plan on using TWRP to flash magisk beta 14.3 to my pixel xl.
Thanks in advance.
Flashing TWRP will not wipe your dsevice.
Using the unofficial modified twrp is no longer necessary. Use twrp 3.1.1.1 img and 3.1.1.1 zip.
I'm on 9.5.13 stable and i'm waiting for unlocking my bootloader, i heared that miui by default encrypt the phone, and after flashing magisk to get root, it will not boot unless i do format data from twrp to decrypt it, it that true or i'm missing something ?
I'm just want to get root on current build 9.5.13 to get some mods and enable camera2api without loosing all stock camera features.
Thanks in advance
Not true!
What your confusing things with, is when you flash TWRP, you need to flash lazyflasher to allow the device to boot. Or use a TWRP that includes a script to do so.
You can run the device encrypted if you want, but formatting data will let it run decrypted if magisk is flashed before booting rom.
Unlocking your bootloader will wipe data, so backup beforehand!
corkiejp said:
Not true!
What your confusing things with, is when you flash TWRP, you need to flash lazyflasher to allow the device to boot. Or use a TWRP that includes a script to do so.
You can run the device encrypted if you want, but formatting data will let it run decrypted if magisk is flashed before booting rom.
Unlocking your bootloader will wipe data, so backup beforehand!
Click to expand...
Click to collapse
Thanks for your help, unlocked my bootloader yesterday and flashed twrp, lazyflasher and magisk and everything is ok, no issues with booting, thanks again.
corkiejp said:
Not true!
What your confusing things with, is when you flash TWRP, you need to flash lazyflasher to allow the device to boot. Or use a TWRP that includes a script to do so.
You can run the device encrypted if you want, but formatting data will let it run decrypted if magisk is flashed before booting rom.
Unlocking your bootloader will wipe data, so backup beforehand!
Click to expand...
Click to collapse
I am new to Custom ROM installer. I had unlocked refmi note 5 pro using miui tool and flashed twrp recovery. But I could nt flash lazyflasher through twrp.
Now my mobile works fine in miui 10 . But I couldn't root it. I need to flash resurrection remix ROM .
Please help me
@sathishob you don't need root to flash a custom rom. Check the rom thread you want to flash for instructions and further assistance.
corkiejp said:
@sathishob you don't need root to flash a custom rom. Check the rom thread you want to flash for instructions and further assistance.
Click to expand...
Click to collapse
@corkiejpThank you for the support corkiejp... Successfully i flashed a custom ROM (Resurrection remix 7 ) but I couldn't use the banking apps and camera doesn't open . I tried to solve it without root. But I couldn't . So I installed magisik now everything works fine . ( I couldn't install magisik easily. It took several times to success. Most probably it says error 1 . Installed magisik uninstall then every thing went smoothly.)
Installing Aosp extended ROM I fixed camera issue and by flashing magisik banking apps are working
Thanks a lot for your valuable reply...
Hello guys
I had unlocked my whyred and flashed twrp recovery by fastboot. First time it went smoothly . after reboot phone went to stock mi recovery . I searched and found that to resolve this i have to install lazyflasher zip file . so i tried to flash that file through twrp. I could nt flash that file because it showed some error message . some how i tried two or more times to flash it with some other lazyflasher files . It did nothing . Then i installed twrp image file from twrp recovery suddenly issue was solved . properly phone booted on twrp recovery .
Then i tried to flash magisik but i couldnt flash it because it says error 1 as a reason . I tried some more ways to flash it but i can't find any solution . from the help of corkiejp i flashed the resurrection remix 7 successfully without flashing magisik. But my camera was not worked and banking apps are not worked .
So i flashed the aosp extended pie rom and the camera worked fine . but i could nt use banking apps. I searched for a way and landed on flashing magisik manager . again the error 1 prevented me to flash magisik . I flashed magisik uninstall zip and everything went smoothly.
Now my phone was properly rooted and working fine.
But my question is if until now i could nt flash lazy flashers prooerlybon my phone . is this make any harm to my phone ? Please help me
Thanks in advance ...
Hi everyone.
I had a issue and i really want help
I had unlock the OEM,and after installing the twrp and format data (to remove the forced encrypt), i had flash the Disable_Dm-Verity_ForceEncrypt zip file.
Okay, after that i have restarted the device and configure as my away to use, after that, booted on recovery again and flashed the magisk.
But i wanna encrypt my device, and when i go to configs->security and encrypt area, says that my device its not encrypted. Okay, i followed the steps and when i gonna try to encrypt the device, the process start and... some seconds after, the phone just restart and nothing has done.
The onlys changes that i have made on system is: root and flashed a splash.img(without that stupid warning of unlocked bootloader)
I really want to encrypt my device, so, if i get stolen, the thief wont get my user data.
Can anyone help me?
Flash the stock rom and and don't flash the encryption disabler next time. You don't need to install TWRP to flash Magisk either, you can just boot it and then flash Magisk. Also you don't even need TWRP, you can just follow the guide in the forum to install Magisk by booting the magisk patched boot.img for your version of the stock ROM and then install Magisk manually via Magisk Manager.
TL;DR : Flash stock ROM and do the same things except flashing dm-verity-disabler, you don't need that for Magisk or TWRP.
marstonpear said:
Flash the stock rom and and don't flash the encryption disabler next time. You don't need to install TWRP to flash Magisk either, you can just boot it and then flash Magisk. Also you don't even need TWRP, you can just follow the guide in the forum to install Magisk by booting the magisk patched boot.img for your version of the stock ROM and then install Magisk manually via Magisk Manager.
TL;DR : Flash stock ROM and do the same things except flashing dm-verity-disabler, you don't need that for Magisk or TWRP.
Click to expand...
Click to collapse
Thanks sir, i will try!
marstonpear said:
Flash the stock rom and and don't flash the encryption disabler next time. You don't need to install TWRP to flash Magisk either, you can just boot it and then flash Magisk. Also you don't even need TWRP, you can just follow the guide in the forum to install Magisk by booting the magisk patched boot.img for your version of the stock ROM and then install Magisk manually via Magisk Manager.
TL;DR : Flash stock ROM and do the same things except flashing dm-verity-disabler, you don't need that for Magisk or TWRP.
Click to expand...
Click to collapse
Sir, i really need twrp now, its there any way i can enable encrypt after rooting the device? (to sure that, if gets stolen, the data need to be wipped out or the password must be given on twrp)
Same issue, i tried to encrypt on security menu,reboot and nothing was done.
@edit
Better, without TWRP, i can flash other zips via magisk/stock recovery?
mrkeitsuke said:
Sir, i really need twrp now, its there any way i can enable encrypt after rooting the device? (to sure that, if gets stolen, the data need to be wipped out or the password must be given on twrp)
Same issue, i tried to encrypt on security menu,reboot and nothing was done.
@edit
Better, without TWRP, i can flash other zips via magisk/stock recovery?
Click to expand...
Click to collapse
I'm not sure what you're trying to do here, do you want to have TWRP + stock encryption?
If so you can just boot TWRP and flash the TWRP installer package (.zip) inside TWRP to do that. And you don't need to change anything, currently I have TWRP installed and encryption enabled on my Stock ROM.
But if you're trying to get TWRP's own encryption, sadly that doesn't work.
You can also use TWRP without flashing/installing it, just go to the directory TWRP is stored in, open a command line, connect your phone and boot it with this command :
Code:
fastboot boot twrp.img
then flash whatever you'd like.
DO NOT lock your bootloader after you flash something on TWRP, this will most probably brick the device.
marstonpear said:
I'm not sure what you're trying to do here, do you want to have TWRP + stock encryption?
If so you can just boot TWRP and flash the TWRP installer package (.zip) inside TWRP to do that. And you don't need to change anything, currently I have TWRP installed and encryption enabled on my Stock ROM.
But if you're trying to get TWRP's own encryption, sadly that doesn't work.
You can also use TWRP without flashing/installing it, just go to the directory TWRP is stored in, open a command line, connect your phone and boot it with this command :
Code:
fastboot boot twrp.img
then flash whatever you'd like.
DO NOT lock your bootloader after you flash something on TWRP, this will most probably brick the device.
Click to expand...
Click to collapse
I want to stick with the stock rom rooted, with the twrp installed and the user data encrypted
So i can flash things through TWRP even i have encrypt enabled?
@edit
dont worry about bootloader, i will keep unlocked
It's perfectly fine to have TWRP and/or Magisk and encryption using stock ROM.
Flash stock ROM (erase user data)
Install TWRP
install Magisk
Don't flash the encryption Disabler. As its name implies, it disables the automatic encryption of the userdata partition.
a1291762 said:
It's perfectly fine to have TWRP and/or Magisk and encryption using stock ROM.
Flash stock ROM (erase user data)
Install TWRP
install Magisk
Don't flash the encryption Disabler. As its name implies, it disables the automatic encryption of the userdata partition.
Click to expand...
Click to collapse
:highfive: i had done this and... i think its working!!! :crying::crying::crying:
(crying for emotion, almost thirty factory resets to get an good result :crying::crying::crying
Anyway, if anything bad occurs, i will update here, thanks a1291762 and marstonpear