For those who want to try LineageOS 17.1/18.1-UNOFFICIAL-GSI . IMO stable enough to be used as your daily driver.
LOSQ/LiR is not developed nor maintained by me!
Credits: @eremitein
Requirements: basically full stock EMUI 9.1, with stock recovery_ramdisk.
Note: I prefer to install in fastboot mode, it's quick, easy and most importantly, safe.
IMPORTANT! Before booting up the ROM, you will need to perform a factory reset in stock recovery!
Install arm64-b.. only!
1. LOSQ - LineageOS 17.1-[10]-unofficial-GSI
with the GAPPS
GAPPS
without GAPPS
Vanilla
-----------------------
LiR- LineageOS 18.1-unofficial-[11]-GSI
Download
2. Extract the ROM .img file from the compressed file.
3. Flash extracted losq/lir... .img from fastboot , use command
fastboot flash system (file_name).img
4. Run command fastboot reboot, unplug your phone, when appears on screen yellow warning, press and hold for 3 sec Volume Up . In eRecovery select 'Wipe data/factory reset'.Reboot .
NFC patch:
https://forum.xda-developers.com/t/losq-lineageos-17-1-unofficial-gsi.4219291/post-84394147
Magisk root (23.0):
(Note: If you don't plan to use TWRP, simply install patched Recovery_ramdisk in fastboot mode. Run command
fastboot flash recovery_ramdisk magisk_patched-23.img ),
- download and install Magisk manager-23.apk:
https://mega.nz/file/go0m2RiR#M5UTv6FPjWPtDaGPr-u2tpJMCwdf8uwnniZg69LiGfw
- Install TWRP-9.1
https://mega.nz/#!tkcTlATI!A8UJGPBGtxJbLcUOJoxCGJj5PFZXzCnjbb3OkwqKTP8
over eRecovery (it's necessary on EMUI 9.1):
- copy TWRP file to the SD card, and also copy to the SD card patched Recovery_ramdisk:
https://mega.nz/file/lp1kHLxJ#htCMaPjSsg_dy0w_jNOft-t_DZRAPwhOvwy_Wr2cjX8
- flash TWRP - run command
fastboot flash recovery_ramdisk (TWRP's_name).img
- boot into TWRP, select storage - SD Card, select "Install image", find TWRP-9.1.img file and mark eRecovery, swipe. Go back, find magisk_patched-23.img file, mark Recovery, swipe. Go back to the TWRP's main menu, select Reboot > Recovery. Done.
Note: you then need to boot your phone every time via Recovery. It'll boot into android as normal but with root.
( Note: for those who want keep the erecovery as a fail-safe:
https://forum.xda-developers.com/t/...-erecovery-with-twrp-installed-on-it.4357127/ )
To remove Magisk reinstall stock recovery_ramdisk via TWRP or fastboot , download Here
How to boot into TWRP:
- Turn off your phone, connect to the PC (or charger), then press and hold Power + Volume Up, device will reboot into eRecovery (= TWRP).
How to boot into patched Recovery :
- Restart your phone, when appears the yellow warning on the screen, press and hold Volume Up for ~ 2 sec,
release the button and immediately press and hold again for ~ 2 sec. Repeat it 6-7 times, the device will reboot into Stock Recovery (you can perform Wipe cache or Factory reset).
Tips:
https://forum.xda-developers.com/t/treble-gsi-favorite-gallery-camera-and-file-manager.4246019/
I have tried this rom - but without the magisk as I don't really care for root.. However.. This rom still has one big missing feature.. Fingerprint unlock. I can go to register fingerprint. Add the finger multible times to complete the circle.. however.. every time it misses just the last part - it will fail. If anyone has a fix for this I would be happy to use this as my daily driver as it works just fine.
whitetigerdk said:
This rom still has one big missing feature.. Fingerprint unlock
Click to expand...
Click to collapse
I'm afraid you're wrong... It works perfectly for me.
Can confirm that so far everything works flawless. Fingerprint sensor is working on the phone too.
Thank you Alf.
Just two additional questions:
How will updates be perform in future?
How to switch from LOS 16 to this rom - the other P20 lite we have is still on v.16?
Cheers
Horqai
horqai said:
How will updates be perform in future?
Click to expand...
Click to collapse
Hi, I don't know bro, I'm not a developer . But you can check the update here:
https://sourceforge.net/projects/treblerom/files/LOSQ/
horqai said:
How to switch from LOS 16 to this rom
Click to expand...
Click to collapse
Install Service ROM using dload method (9.1.0.132 recomm.) , then you can safely flash 17.1 GSI. Dload method will erase all your data and will lock the BL again!
-Alf- said:
Hi, I don't know bro, I'm not a developer . But you can check the update here:
https://sourceforge.net/projects/treblerom/files/LOSQ/
Install Service ROM using dload method (9.1.0.132 recomm.) , then you can safely flash 17.1 GSI. Dload method will erase all your data and will lock the BL again!
Click to expand...
Click to collapse
Ugh, is there a way to install emui 9 without it locking my bootloader? I unlocked my bootloader via the @huaweihax method.
[/QUOTE]
XRealX said:
Ugh, is there a way to install emui 9 without it locking my bootloader?
Click to expand...
Click to collapse
OTA update, via HiSuite, you can try also through eRecovery ...
make sure to have the stock recovery flash.
XRealX said:
I unlock my bootloader via the @huaweihax method.
Click to expand...
Click to collapse
Idk how huaweihax method works, but the BL unlock
code is permanent, it wont expire, you use the same bootloader code to unlock if your device is relocked.
Btw, with EMUI 8 installed with May 2018 security patch you should be able to use DC-Unlocker or hcu-client to get BL unlock code for 4euros.
Or, you can also unlock BL for free using
PotatoNV method
OTA update, via HiSuite, you can try also through eRecovery ...
make sure to have the stock recovery flash.
Idk how huaweihax method works, but the BL unlock
code is permanent, it wont expire, you use the same bootloader code to unlock if your device is relocked.
Btw, with EMUI 8 installed with May 2018 security patch you should be able to use DC-Unlocker or hcu-client to get BL unlock code for 4euros.
Or, you can also unlock BL for free using
PotatoNV method
Click to expand...
Click to collapse
There's no way I'm paying for unlocking!
The huaweihax method works this way: you give some information about your device and you flash a slock file to the ramdisk. It unlocks your phone.
To prevent EMUI 9 from re-locking your device, you can flash a zip file to have a custom bootloader unlock code.
Btw, I have hyperlinked the thread that describes this in the "thingy" word.
I guess that custom code should work even if my device is re-locked.
I do not start the phone only in loop TWRP mode, what solution do I have to revive the phone
I do not start the phone only in loop TWRP mode, what solution do I have to revive the phone
How can I repair the factory erecovery I am using the phenix program but it gives me recovery error
itrisev said:
How can I repair the factory erecovery I am using the phenix program but it gives me recovery error
Click to expand...
Click to collapse
Sorry, this is not the DC-Phoenix support chat, let's please remember to keep conversations and comments in this thread about LOSQ - LineageOS 17.1, thanks...
Thanks @-Alf-
I followed all your advice in the LOS 16 thread to get 16 installed, but couldn't get gapps to work. So I thought lemme give LOS 17 a shot since it includes gapps, and it works great! However I get the same issue with fingerprint as @whitetigerdk. During fingerprint enrolment it works up until the last time you have to finger it, after which I get popup "Enrolment was not completed: Fingerprint enrolment didn't work. Try again or use a different finger". I can provide a screenshot but it's literally just that text.
Apart from that everything seems to work fine. Haven't installed magisk yet, will do that next.
An3skmbi said:
During fingerprint enrolment it works up until the last time you have to finger it, after which I get popup "Enrolment was not completed: Fingerprint enrolment didn't work.
Click to expand...
Click to collapse
-Alf- said:
Tested on 9.1.0.132.
Click to expand...
Click to collapse
-Alf- said:
Clean OS
Click to expand...
Click to collapse
-Alf- said:
Install Service ROM using dload method (9.1.0.132 recomm.)
Click to expand...
Click to collapse
Most of custom ROMs require lower build number, on latest build number may or may not work correctly.
If you have followed this guide to the letter and it didn't work, i'm afraid I cant help you .
I've not had any major issue with this LineageOS.
P.S.:
If all this has worked on my device, it does not mean that it goes with everyone else, and vice versa (we are talking about Huawei devices ).
@-Alf- Thanks, that might be it. I'm on firmware 9.1.0.200(C185E4R1P8T8) as that was the recommended one for LOS 16. Let me give it a shot with 132, will update with results.
Edit: With "Clean OS" I assume you mean a clean install of the stock ROM? My approach is to install 132 via dload, unlock bootloader, then follow your installation steps.
An3skmbi said:
With "Clean OS" I assume you mean a clean install of the stock ROM? My approach is to install 132 via dload, unlock bootloader, then follow your installation steps.
Click to expand...
Click to collapse
Yes, but I'm afraid there's no .132 build number for region C185 on androidhost.ru
IMO you can get it via paid service only, for 17euros , hm...look here
.132
The difference between .132 and .200 is google patch - may 2019 vs. july 2019.
-Alf- said:
Yes, but I'm afraid there's no .132 build number for region C185 on androidhost.ru
Click to expand...
Click to collapse
What about this one? http://huawei-firmware.com/rom/huawei-p20-lite/ane-lx1/42056
It doesn't have a dload folder, it's just the update.zip basically, so I'm not sure how to flash it only unlocked my phone yesterday, not used to huawei roms yet.
Edit: they explain how here, you create the dload folder manually.
An3skmbi said:
they explain how here, you create the dload folder manually.
Click to expand...
Click to collapse
This guide is valid for Android 6 . Huawei-firmware is a really reliable website .
-Alf- said:
This guide is valid for Android 6 . Huawei-firmware is a really reliable website .
Click to expand...
Click to collapse
What do you mean really reliable when the guide is for Android 6? Is there a way to flash the 132 ROM from huawei-firmware?
Also, magisk installation worked perfectly by following your instructions. I can pass safety net with the universal safetynet fix module and got google play certification with the props module.
Is there a way to now boot into TWRP (erecovery)? Currently when booting it doesn't show the option to hold volume up to enter erecovery, it immediately says your phone is booting now. The only way to get into TWRP is to fastboot flash recovery twrp, do stuff there, then flash magisk_patched-ane-v21 over recovery and reboot.
Edit: I captured a logcat while getting the fingerprint enrollment error, there are some exceptions about the enrollment, not sure if that could mean something to the devs to help fix it?
An3skmbi said:
Is there a way to flash the 132 ROM from huawei-firmware?
Click to expand...
Click to collapse
Nope.
An3skmbi said:
Is there a way to now boot into TWRP (erecovery)?
Click to expand...
Click to collapse
Oops I thought I mentioned it in my post, mea culpa.
You have two options:
1. Turn off phone, connect to PC (or charger), then pres and hold Power + Volume Up, device will reboot into eRecovery (= TWRP).
2. Restart phone, when appears the yellow warning on screen, press Volume up, hold for ~ 2 sec,
release the button and immediately press and hold again for 2 sec, repeat it 6-7 times, the device will reboot into Stock Recovery , then you can do normal restart - Reboot system now.
Related
Guys i have a really really big problem with mate 9 (MHA-L29). I broke both twrp and system same time (please don't ask why.)
Now, my phone don't open, just fastboot&rescue mode, useless huawei recovery (which can't format data neither install stock rom). Besides, i can't install stock rom because i tried once, and i downloaded wrong system file, and i can't format the phone now. Because of that, stock rom that i download sd card not working too. Because there is a dload file in phone.
worst of all, i can't install twrp again, because my fastboot screen tell me that: "Phone Unloced" (with red) "FRP Lock" (with green). When i try to install twrp, adb says "Failed, remote command not allowed"
Now, if can install the twrp, all my problems will be solve. There is 1 custom rom (RomAur) and 1 system backup.
How can i install twrp with this situation?
Please someone help me i spend 2 days and still nothing! How can i open this phone? Stock rom, with/without root, custom rom whatever, just tell me how can i open this phone
up
You get that command when trying to flash the wrong recovery partition, was your room nougat or Oreo based?? If nougat it's fastboot flash recovery recovery.img and Oreo fastboot flash recovery_ramdisk recovery.img I think you are trying to flash the wrong partition
shae23 said:
You get that command when trying to flash the wrong recovery partition, was your room nougat or Oreo based?? If nougat it's fastboot flash recovery recovery.img and Oreo fastboot flash recovery_ramdisk recovery.img I think you are trying to flash the wrong partition
Click to expand...
Click to collapse
No, my twrp is not wrong, i installed before, and i used long time, till broken. I installed wrong twrp recovery over correct recovery (i was trying to chance recovery because project treble). Thats why my twrp broken. Now i try to correct one, but adb says "not allowed". My custom rom nougat based.
cannurkars said:
No, my twrp is not wrong, i installed before, and i used long time, till broken. I installed wrong twrp recovery over correct recovery (i was trying to chance recovery because project treble). Thats why my twrp broken. Now i try to correct one, but adb says "not allowed". My custom rom nougat based.
Click to expand...
Click to collapse
With FRP lock you'll have to use DC-Phoenix.
But it costs €19 (For 3 days usage).
Simply put you can bypass FRP with it by force closing DC-Phoenix when it has activated the backdoor, after this you can flash anything from fastboot (until you reboot).
So you could use it to flash back TWRP.
Or you can use it to install stock firmware
ante0 said:
With FRP lock you'll have to use DC-Phoenix.
But it costs €19 (For 3 days usage).
Simply put you can bypass FRP with it by force closing DC-Phoenix when it has activated the backdoor, after this you can flash anything from fastboot (until you reboot).
So you could use it to flash back TWRP.
Or you can use it to install stock firmware
Click to expand...
Click to collapse
I will try it. Thank you very much.
cannurkars said:
Guys i have a really really big problem with mate 9 (MHA-L29). I broke both twrp and system same time (please don't ask why.)
Now, my phone don't open, just fastboot&rescue mode, useless huawei recovery (which can't format data neither install stock rom). Besides, i can't install stock rom because i tried once, and i downloaded wrong system file, and i can't format the phone now. Because of that, stock rom that i download sd card not working too. Because there is a dload file in phone.
worst of all, i can't install twrp again, because my fastboot screen tell me that: "Phone Unloced" (with red) "FRP Lock" (with green). When i try to install twrp, adb says "Failed, remote command not allowed"
Now, if can install the twrp, all my problems will be solve. There is 1 custom rom (RomAur) and 1 system backup.
How can i install twrp with this situation?
Click to expand...
Click to collapse
During startup the menu there is a option to go in Huawei e-recovery, when you are at the start up menu hold volume up for about 5 second.
ConnerZhao929 said:
During startup the menu there is a option to go in Huawei e-recovery, when you are at the start up menu hold volume up for about 5 second.
Click to expand...
Click to collapse
No it wasn't work for me. But thank for your attention. I'm glad to find a good person to help me and my problem solved about 1-2 hour ago.
Special Request
Hey ante . Is it possible to help me ? I rooted my phone 2 days back and messed it up while downloading a framework app which ended me up in a bootloop. I have been reading and following your posts of you helping others. I don't really get the steps what I should follow.
My phone is unlocked. FRP shows Unlock.
Rooted on oreo and I tried e-recovery and fastboot steps you mentioned in other threads using kernel and ramdisk etc. ( After this I have lost access to TWRP and I am simply getting EMUI Screen with options for Factory Data Reset and Wipe Cache Partition. I don't know where it is going to lead me next :-/.
Also downloaded Huawei Extractor and tried to extracted specific files but the firmware file I have doesn't have CUST.img file.
Also the site link you mentioned for download firmware is in some other language and I am unable to search for my firmware.
I also tried the placing update file in the dload on my sd card but fails at 5%. The file was correct and I am sure I did'n download the wrong firmware.
Currently it shows this on the fastboot screen.
Andorid reboot reason
: AP_S_ABNORMAL 32
NA
Just don't know what I should be doing ? PLEASE HELP BRO?
ante0 said:
With FRP lock you'll have to use DC-Phoenix.
But it costs €19 (For 3 days usage).
Simply put you can bypass FRP with it by force closing DC-Phoenix when it has activated the backdoor, after this you can flash anything from fastboot (until you reboot).
So you could use it to flash back TWRP.
Or you can use it to install stock firmware
Click to expand...
Click to collapse
AniMaL92 said:
Hey ante . Is it possible to help me ? I rooted my phone 2 days back and messed it up while downloading a framework app which ended me up in a bootloop. I have been reading and following your posts of you helping others. I don't really get the steps what I should follow.
My phone is unlocked. FRP shows Unlock.
Rooted on oreo and I tried e-recovery and fastboot steps you mentioned in other threads using kernel and ramdisk etc. ( After this I have lost access to TWRP and I am simply getting EMUI Screen with options for Factory Data Reset and Wipe Cache Partition. I don't know where it is going to lead me next :-/.
Also downloaded Huawei Extractor and tried to extracted specific files but the firmware file I have doesn't have CUST.img file.
Also the site link you mentioned for download firmware is in some other language and I am unable to search for my firmware.
I also tried the placing update file in the dload on my sd card but fails at 5%. The file was correct and I am sure I did'n download the wrong firmware.
Currently it shows this on the fastboot screen.
Andorid reboot reason
: AP_S_ABNORMAL 32
NA
Just don't know what I should be doing ? PLEASE HELP BRO?
Click to expand...
Click to collapse
What's your firmware now?
You can get that info in Fastboot using
Code:
fastboot oem get-product-model
fastboot oem get-build-number
Since your recovery and fastboot still functions you probably will only need to use HWOTA to get back to stock.
It can be found here: https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-oreo-update-package-t3699522
But post your cust/build before proceeding.
Also cust.img is found in UPDATE.APP in the hw data zip.
Problem Solved - Somewhat
Hey ante. Thanks for the promt reply. I got it solved by using CHIMERA tool.
Would like to suggest others also stuck with same issue to use CHIMERA.
Note - It is a paid tool and 100% legit and it can help with all problems related to FRP, Bootloader Lock / Unlock & also flashes back to factory firmware.
However what I am facing now I have flashed another version of firmware which isn't my region and some features of my phone like fingerprint scanner and other things are not working but phone is back to live. So Im glad and looking forward to searching for clean Oreo Firmware for my region to flash using CHIMERA Again.
Also, the sick and stupid part of it. I went to the service center and a person non-technical told me straight that you lost your device and it's of no use now. We cannot fix such issues 99% but I'll still ask my team and let you know after 3 days.
Thank God I didn give them and wasted my time and money.
As soon as I returned, I followed up to things and got it done myself. :good:
Anybody can possibly suggest a official firmware Oreo EMUI for Middle East Region!? If not which one can be flashed instead and where to download from?
As there seems to be no such guide yet and it took me quite a while to get all this information together, I thought of giving back something by putting information together for others to start.
This guide is meant for the CLT-L29 (dual SIM). Rebranding and switching your CLT-L09 (single SIM) to dual is not subject of this guide and is not adviced.
This is for a Huawei P20 Pro CLT-L29 with factory reset. Please bear with me if there really is a step missing as I try to reproduce this for the documentation with an already bootloader unlocked and previously rooted phone (root should be gone after [factory] resetting via eRecovery).
A collection of all tools used can be found here.
As always, you are doing this on your own risk, no one else can be held responsible for this.
Cheat sheet
eRecovery
The recovery sitting in the "recovery" partition. eRecovery is Huawei's recovery that is able to fix your phone by downloading the latest OTA update via WiFi if you got stuck in a boot loop for several reasons.
To boot into eRecovery:
Power down your phone (if you are stuck in a boot loop simply continue with the next step).
Hold volume up until you end up in eRecovery.
Setup your WiFi access and let it recover your phone.
If unsure, "wipe data/factory reset" to get rid of any leftovers you messed up.
Reboot and be happy that you have not fully bricked your phone.
TWRP
The recovery typically flashed to the "recovery_ramdisk" partition. TeamWin Recovery Project is what you typically use to flash ROMs, to root the phone and to install OTA updates.
Do NOT flash TWRP into "recovery" partition or you will lose eRecovery and the ability to easily recover your semi-bricked phone via WiFi!
To boot into TWRP (once flashed):
Power down your phone (if you are stuck in a boot loop simply continue with the next step).
Hold volume up and power until you end up in TWRP.
Unlock your bootloader
Get your bootloader unlock code from here https://emui.huawei.com/en/unlock_detail (available until mid of July I think). Some report to have to wait 24/48h to get their code via mail, I got mine directly.
Register via mail and do not get confused that you can not select USA or Germany or whatever country, simply use location Hong Kong.
Make sure you select "EMUI above 5.0" when entering your phone data (P20 Pro comes with EMUI 8.x).
Connect your phone via ADB. There are tons of HowTos about this, so I will not be covering this here.
Use Tool All In One to check that you can talk to your device via ADB. It will also help you installing the correct ADB USB drivers.
Unlock your bootloader using Tool All In One.
Reboot back into system.
Flash TWRP
Make sure no lock screen or other locking is set:
"Settings > Security": Remove fingerprint, face or password locking, simply set to none.
Enter developer mode, should already been done for unlocking the bootloader.
Setting > System > Developer options: Disable the display lock.
Download latest ADB & Fastboot as I will continue with the rest on command line.
Verify connection to your phone with "adb devices", this should list your phone.
Reboot into fastboot by using "adb reboot bootloader".
Verify connection to your phone with "fastboot devices", this should list your phone.
Flash TWRP by Pretoriano80 with "fastboot flash recovery_ramdisk twrp_clt_0.1.img". This TWRP is able to access the encrypted internal storage! TWRP is flashed to "recovery_ramdisk". This ensures that you can still access eRecovery if something goes wrong.
Remove the USB cable.
Reboot into TWRP. If you do not boot directly into TWRP the Huawei eRecovery might replace TWRP again. Once you booted into TWRP you are fine for future reboots.
Use "Keep Read Only" for the system partition.
Make a backup!!!
Backup your phone to internal storage (USB stick via USB-OTG adapter failed for me):
Select "Backup".
Tick all partitions (scroll down and tick all).
Swipe to Backup.
Select "Reboot System", "Do Not Install".
Back in Android make a copy of your backup located in your internal storage "/TWRP/" to an external location like your PC. Keep the backup on your phone to be able to go back quickly to this point via TWRP.
Root the stock ROM
Place "Magisk-v16.4-Beta.zip" onto the internal storage.
Power off the phone and remove the USB cable.
Boot into TWRP.
Install root and Magisk Manager:
Select "Install".
Select "Magisk-v16.4-Beta.zip"
Tick "Reboot after installation is complete".
Swipe to confirm Flash.
Select "Do Not Install".
Back in Android start "Magisk Manager" and check that it is green and therefore rooted.
Install an OTA (Over The Air) stock update
PC method
Method involving ADB based on this guide.
First make sure no OTA update gets installed automatically as this will end up in booting into TWRP and failing with the update.
Go to "Settings > System > System Update".
Open the three dots menu on the top right and select "Update Settings".
Disable automatic update download via WiFi as once updates are downloaded the phone will bug you to update and maybe tries to update itself during the night!
Start in Android but do not download the OTA update yet.
Verify connection to your phone with "adb devices", this should list your phone.
Reboot into fastboot by using "adb reboot bootloader".
Verify connection to your phone with "fastboot devices", this should list your phone.
Flash "recovery_ramdisk_nocheckP20.img" with "fastboot flash recovery_ramdisk recovery_ramdisk_nocheckP20.img". For official OTA updates that you would regularly get, the "nocheck" feature should not be needed but does not harm. This will remove TWRP and you have to flash it again after the OTA update has finished.
Reboot into Android by using "fastboot reboot".
Remove the USB cable.
Download your OTA update via "Settings > System > System Update".
Let the phone reboot to install the OTA update and follow the update until you are back in Android with your new firmware version.
Install TWRP and root again.
Standalone method
Deprecated/wrong method based on this guide.
Read first!!!
While this method should do no harm it will only ever update to CLT-L29 8.1.0.128a(C432) [hw/eu] as this is what is inside the file "update.zip" that you can currently download and that gets installed by "HuRUpdater_0.3.zip" in the same folder. This was not clearly explained in the source thread, therefore sorry about this wrong information. If you intend to update to this stock ROM continue, otherwise use the "PC method".
I will check about the best way to install OTA updates without PC interaction in the next couple of days (currently waiting for 130+ getting rolled out for me for some investigations regarding the OTA process).
First make sure no OTA update gets installed automatically as this will end up in booting into TWRP and failing with the update.
Go to "Settings > System > System Update".
Open the three dots menu on the top right and select "Update Settings".
Disable automatic update download via WiFi as once updates are downloaded the phone will bug you to update and maybe tries to update itself during the night!
Place the following files into a folder on the internal storage (for sure not all are required but this is part of the little information not clear right now):
"HuRUpdater_0.3.zip"
"recovery.img"
"update.zip"
"update_all_hw.zip"
"update_data_public.zip"
Go to "Settings > System > System Update" and check for an update.
Download the OTA update.
Do not reboot when prompted.
Make sure no lock screen or other locking is set:
"Settings > Security": Remove fingerprint, face or password locking, simply set to none.
Enter developer mode, should already been done for unlocking the bootloader.
Setting > System > Developer options: Disable the display lock.
Power down the phone.
Boot into TWRP.
Install "HuRUpdater_0.3.zip". Do not get irritated if it tells you it is for CLT-L09 instead of CLT-L29, everything is fine.
Wipe dalvik cache before rebooting.
Reboot back into Android.
Check "Magisk Manager" to see if root got removed. TWRP might get removed as well. If TWRP or root got removed, repeat the install for one or both like before.
In my case only root got removed but TWRP was kept functional. If this is the case for you as well, simply flash "Magisk-v16.4-Beta.zip" via TWRP again.
Changelog
2018-06-21
Updated/corrected wrong information collected about installing OTA updates standalone (without PC). Until further notice use the PC method.
Great post. Thank you
Very good post!
Thank you to collect all this important info!
[emoji481]
P20 Pro & Tapatalk
can i use your step above to rebranding from L29c636 to l29c432? Thanks
Barcovn said:
can i use your step above to rebranding from L29c636 to l29c432? Thanks
Click to expand...
Click to collapse
Not sure, not tested and not topic of this thread.
For my understanding, why do you want to rebrand it to C432 which is the region code as far as I understand.
Is there a BIG benefit of getting OTA updates earlier or why do you want to mess around with it ?
Xcelsior said:
Not sure, not tested and not topic of this thread.
For my understanding, why do you want to rebrand it to C432 which is the region code as far as I understand.
Is there a BIG benefit of getting OTA updates earlier or why do you want to mess around with it ?
Click to expand...
Click to collapse
yes, i mean change the region code. as i use the p20 pro since April, newer firmware ususal fix/improve performance for phone or camera. however it seem the c636 update is much slower then C432. currently i have problem with facebook lagging which inhope newer firmware fix it
This is good! I'll sticky it when I get a chance later tonight. I'm mobile atm
Maybe I'm missing something.
https://forum.xda-developers.com/hu...de-how-to-root-debrand-remove-retail-t3788326
It's been here for some time.
Nothing wrong with your guide it's decent but the info provided is actually already here mate.
Root, twrp, de-brand, OTA, it's all there
dladz said:
Maybe I'm missing something.
https://forum.xda-developers.com/hu...de-how-to-root-debrand-remove-retail-t3788326
It's been here for some time.
Nothing wrong with your guide it's decent but the info provided is actually already here mate.
Root, twrp, de-brand, OTA, it's all there
Click to expand...
Click to collapse
They're a bit different. The debrand thread is obviously good but much more specific to debranding. This is a more generic for general How-To's
dladz said:
Maybe I'm missing something.
https://forum.xda-developers.com/hu...de-how-to-root-debrand-remove-retail-t3788326
It's been here for some time.
Nothing wrong with your guide it's decent but the info provided is actually already here mate.
Root, twrp, de-brand, OTA, it's all there
Click to expand...
Click to collapse
I was reading this one as well but like matt4321 already said, it is actually for a different purpose.
And even the "ROOT ONLY" instructions are either widespread over the whole P20 Pro forum, incomplete or even outdated:
Linking to other threads with endless, partly revised instructions (on page n of the thread).
Referring to wrong official TWRP that can not use internal storage.
Hard to understand for beginners on this device (not even talking about someone who is entirely new to all of this).
Missing steps or expecting that you have already successfully flashed your first ROM (talking about advanced things like rebranding).
Don't get me wong, I am used to read a lot when it comes to custom ROMs (if you check the old part of my signature you can see that I am not actually a newbie here and my roots actually reach back to when all of the Android stuff startet at all, back when XDAs flashed HTC HD2 WinMo to Android). However I really missed a guide that actually collects all the basic information for beginners without going off roads too early.
These are more or less the steps I'm used to when I owned my nexus phones.
I have some questions:
If I root my phone and install, let's say adaway, will I be able to receive OTA? Or I will have to flash a new image manually?
If after root I relock bootloader, will I be able to unlock it again later for further modding?
This method implies that I can return to stock anytime and relock bootloader?
Thanks for the guide and answers , great job
mangusZen said:
If I root my phone and install, let's say adaway, will I be able to receive OTA? Or I will have to flash a new image manually?
Click to expand...
Click to collapse
Yes, exactly what I am doing. I need root for some apps and besides that I am happy with the stock OTA ROM, at least for the moment. OTA updates work fine so far.
The only thing as explained in my guide is that OTA updates will fail as they boot into TWRP instead of original fastboot. Therefore you need to explicitly boot into TWRP and install the downloaded OTA update with "HuRUpdater_0.3.zip".
mangusZen said:
If after root I relock bootloader, will I be able to unlock it again later for further modding?
Click to expand...
Click to collapse
From what I have read so far re-locking your bootloader is not advised. You seem to be unable to unlock it again or at least need to request another unlock code from Huawei.
At least this is my understanding of the situation so far.
mangusZen said:
This method implies that I can return to stock anytime and relock bootloader?
Click to expand...
Click to collapse
Returning to stock is even easier if you keep eRecovery working as explained in the guide (flashing TWRP only to recovery_ramdisk partition). With eRecovery you can wipe TWRP and root and let eRecovery download and install the latest official stock ROM.
Regarding the bootloader re-locking, see my answer above.
Xcelsior said:
Yes, exactly what I am doing. I need root for some apps and besides that I am happy with the stock OTA ROM, at least for the moment. OTA updates work fine so far.
The only thing as explained in my guide is that OTA updates will fail as they boot into TWRP instead of original fastboot. Therefore you need to explicitly boot into TWRP and install the downloaded OTA update with "HuRUpdater_0.3.zip".
From what I have read so far re-locking your bootloader is not advised. You seem to be unable to unlock it again or at least need to request another unlock code from Huawei.
At least this is my understanding of the situation so far.
Returning to stock is even easier if you keep eRecovery working as explained in the guide (flashing TWRP only to recovery_ramdisk partition). With eRecovery you can wipe TWRP and root and let eRecovery download and install the latest official stock ROM.
Regarding the bootloader re-locking, see my answer above.
Click to expand...
Click to collapse
Ok, so to install OTA I have to use hurupdater method and flash the OTA package manually.
For what I read and understood, but I may be wrong, the problem with relocking bootloader is encountered by who used the funkyhuawei method, that alters bootloader in some way, especially to achive the mono sim - dual sim switch.
With this you cant for now re unlock the bootloader again.
But I could be wrong and be like that for everyone, will see if someone will come up with some clarifications.
It would be nice to have the ability to return to stock, lock bootloader and use warranty
[emoji14]
Thanks for your work and answers
mangusZen said:
Ok, so to install OTA I have to use hurupdater method and flash the OTA package manually.
Click to expand...
Click to collapse
Yes, that is basically what "HuRUpdater_0.3.zip" will do, it will flash/install an OTA update that has previously been downloaded.
Wipe cache afterwards and be happy with your new up to date stock ROM version.
Xcelsior said:
Yes, that is basically what "HuRUpdater_0.3.zip" will do, it will flash/install an OTA update that has previously been downloaded.
Wipe cache afterwards and be happy with your new up to date stock ROM version.
Click to expand...
Click to collapse
I have to rename the downloaded OTA packages for huru to work, right?
mangusZen said:
I have to rename the downloaded OTA packages for huru to work, right?
Click to expand...
Click to collapse
Not for me. Just downloaded the OTA update via the EMUI system menu in Android, rebooted into TWRP and installed (aka executed) HuRu.
HuRu did the rest for me.
Tested with 120 -> 128 OTA update.
Hi It is late at night and I am not sure if I typed fastboot flash recovery twrp_clt_0.1.img instead off fastboot flash recovery_ramdisk twrp_clt_0.1.img. How can I make sure I still have erecovery? super newbie to android rooting, please help Thank you
Amowiel said:
Hi It is late at night and I am not sure if I typed fastboot flash recovery twrp_clt_0.1.img instead off fastboot flash recovery_ramdisk twrp_clt_0.1.img. How can I make sure I still have erecovery? super newbie to android rooting, please help Thank you
Click to expand...
Click to collapse
Simplest way would be to try to boot into eRocovery:
Power off the phone.
Power on the phone until you see the "you are a baddy because you unlocked your bootloader" screen.
Hold volume up (you can already hold it when powering on the phone) until you end up in eRecovery or TWRP.
If you end up in TWRP it should still be possible to recover your eRecovery with a proper backup of the "recovery" partition from any other P20 Pro.
Xcelsior said:
Simplest way would be to try to boot into eRocovery:
Power off the phone.
Power on the phone until you see the "you are a baddy because you unlocked your bootloader" screen.
Hold volume up (you can already hold it when powering on the phone) until you end up in eRecovery or TWRP.
If you end up in TWRP it should still be possible to recover your eRecovery with a proper backup of the "recovery" partition from any other P20 Pro.
Click to expand...
Click to collapse
thank you so much for such a quick reply, can confirm that my brain was not so fried and I didn't wipe my ercovery
thank you for your amazing guide, everything worked perfectly
mangusZen said:
Ok, so to install OTA I have to use hurupdater method and flash the OTA package manually.
For what I read and understood, but I may be wrong, the problem with relocking bootloader is encountered by who used the funkyhuawei method, that alters bootloader in some way, especially to achive the mono sim - dual sim switch.
With this you cant for now re unlock the bootloader again.
But I could be wrong and be like that for everyone, will see if someone will come up with some clarifications.
It would be nice to have the ability to return to stock, lock bootloader and use warranty
[emoji14]
Thanks for your work and answers
Click to expand...
Click to collapse
Actually you don't in some cases, if your simply rooted with twrp and you want to install an OTA that's been advertised to your device. All you need to do is install the nocheck recovery IMG and then take the update, reinstall twrp and magisk after the update and you're done.
If it's an update that's not advertised to your device yet then hur updater is the way.
First of all the guide i took it from @Vedrick by searching here in XDA. I just opened this post because i found his guide with a little bit hardness and its easier now for ya.
Well lets start. FIRST Back up all your data.
I was on the latest version of CLT-L29 Huawei p20 pro 6/128 9.0.0.195(C432E5R1P9) if you try it on another version let me know
As always, if you do this it's at your own risk.
PREREQUIREMENTS:
Watch my video on youtube that made to help you guys
1) ADB, Fastboot and Drivers
2)Patched boot image
3) A pc of course.
4) Make sure your phone is not bootloop and working
5)Enable Debugging and OEM unlocking from dev options
This is how i got root on EMUI 9 without TWRP recovery
1 - I Flashed Get your phone on fastboot mode FIRST MAKE SURE YOUR PHONE HAS UNLOCKED BOOTLOADER (download it, and move it on your adb folder-default is on C: drive) (press SHIFT button and right click on the adb folder->select open here PowerShell) type the command fastboot flash recovery_ramdisk patched_boot.img
2-Reboot phone, install Magisk manager last apk from google , go into settings, and change the update channel to custom: )COPY AND PASTE THIS LINKhttps://raw.githubusercontent.com/topjohnwu/magisk_files/master/canary_builds/release.json, go back to the Magisk home screen and hit install, download the odd Magisk file.zip file.
3-Reboot phone, press and hold the volume up key if it goes to ERecovery then reboot again and keep pressing like the video.
4-Open Magisk app, install the zip, then patch, and install the downloaded Magisk.zip file if it says direct install(recommender choose this should say this)
5-Reboot phone, press and hold the volume up key and your phone should boot just fine.(like i said above and like i show the video)
6-Open Magisk, install, select direct install option. and reboot.
Note:
1 - Now your phone will reboot into the recovery every time on its own, which is a good thing, you no longer need to hold the volume up key every time you reboot, it does it for you. This means no TWRP.
2 - In order to apps root access for the first time you need to have Magisk open, or you wont get prompted for approval. Then the app will have permanent root access.
3- You can enter fastboot mode from connecting your phone to pc and open adb as i say above and type adb reboot bootloader OR by turn off your phone, press the down button volume and after 3 secs connect the cable on your pc DONT LEAVE THE DOWN BUTTON
Usefull Commands: If you cannot enter bootloader mode ( IS NEEDED ) type this command on the adb , but first connect your phone with your PC/LAPTOP adb reboot bootloader
IF you have any questions fell free to comment bellow. Also i am gonna try some things to flash twrp and have it for ever because @Vedrick i think couldnt flash twrp recovery
Hi,
thanks a lot taking time for this guide but there are 2 things that I think are confusing :
FIRST - Once you have flashed recovery_ramdisk partition with the patched_boot.img file through fastboot , and you reboot holding up volume button, the phone boots. But after installing latest magisk manager, even without changing the update channel adress, phone is already rooted and you can add modules, etc...
SECOND - when following the guide step by step, part 4 is a problem because it finds new version and asks tout update. And when you do, the guide says install then to patch the tout install the downloaded file.
That part ils not clear as you do not tell what file to patch at this state....
If you could clear that part it would be perfect.
deltaman83 said:
Hi,
thanks a lot taking time for this guide but there are 2 things that I think are confusing :
FIRST - Once you have flashed recovery_ramdisk partition with the patched_boot.img file through fastboot , and you reboot holding up volume button, the phone boots. But after installing latest magisk manager, even without changing the update channel adress, phone is already rooted and you can add modules, etc...
SECOND - when following the guide step by step, part 4 is a problem because it finds new version and asks tout update. And when you do, the guide says install then to patch the tout install the downloaded file.
That part ils not clear as you do not tell what file to patch at this state....
If you could clear that part it would be perfect.
Click to expand...
Click to collapse
i am gonna check it now because my phone was bricked and i cant root now
deltaman83 said:
Hi,
thanks a lot taking time for this guide but there are 2 things that I think are confusing :
FIRST - Once you have flashed recovery_ramdisk partition with the patched_boot.img file through fastboot , and you reboot holding up volume button, the phone boots. But after installing latest magisk manager, even without changing the update channel adress, phone is already rooted and you can add modules, etc...
SECOND - when following the guide step by step, part 4 is a problem because it finds new version and asks tout update. And when you do, the guide says install then to patch the tout install the downloaded file.
That part ils not clear as you do not tell what file to patch at this state....
If you could clear that part it would be perfect.
Click to expand...
Click to collapse
ok i did manage to root it again. you need to unlock your bl and press the volume up button. i edited the post
I did first time as just flashing fastboot recovery_ramdisk with patched_boot.img was enough when opening magisk manager.
Updating was the issue. SO i downloaded the original recovery_ramdisk 195 , and used that file to patch with the latest version downloaded. Then I flashed in fastboot the new patched_boot.img and all was good to latest version.
deltaman83 said:
I did first time as just flashing fastboot recovery_ramdisk with patched_boot.img was enough when opening magisk manager.
Updating was the issue. SO i downloaded the original recovery_ramdisk 195 , and used that file to patch with the latest version downloaded. Then I flashed in fastboot the new patched_boot.img and all was good to latest version.
Click to expand...
Click to collapse
why to download another patch i dont get it.
plus see my signature
Because with yours i was not on latest magisk. Now i can update each time there's a new version by patching the original recovery_ramdisk and flashing the patched_boot.img on fastboot.
I'm curently on 18.2-e05cdc83 (18104)
deltaman83 said:
Because with yours i was not on latest magisk. Now i can update each time there's a new version by patching the original recovery_ramdisk and flashing the patched_boot.img on fastboot.
I'm curently on 18.2-e05cdc83 (18104)
Click to expand...
Click to collapse
i have the same version as you. the problem is 1) you cant have twrp recovery 2) when you open a app that needs root you have to open magisk app first otherwise the permissions will fail
unfortunately no twrp recovery ...
You're right I noticed that
deltaman83 said:
unfortunately no twrp recovery ...
You're right I noticed that
Click to expand...
Click to collapse
do no try to flash twrp it bricked my device.,
Join my telegram group dude
Thanks a lot but i don't have enough time....see m'y number of posts by there lol...same on Facebook etc (f..k I'm already late for work....?).
Regards
Hi all, this method will work on my device? thanks!
P20 PRO
model: CLT-L09
Build: 9.0.0.163 (C432E5R1P9patch01) GPU Turbo
EMUI: 9.0.0
Android 9
Evasi0n3r said:
Hi all, this method will work on my device? thanks!
P20 PRO
model: CLT-L09
Build: 9.0.0.163 (C432E5R1P9patch01) GPU Turbo
EMUI: 9.0.0
Android 9
Click to expand...
Click to collapse
Hello yes sir.
Please check my signature and join my telegram
Watch my video on youtube that made to help you guys https://youtu.be/AB6wwBTfKEc
Hi. Thank you.
I did it in firmware 9.0.0.191 and worked fine.
gvflavio said:
Hi. Thank you.
I did it in firmware 9.0.0.191 and worked fine.
Click to expand...
Click to collapse
np if u want press the thanks button. also join my telegram group see the link in my signature bellow this post.
John
You are genius. Thanks working great p20 pro 9.0.0.191c605
Every time I flash the patched_boot.img and restart with volume up into recovery I have a bootloop. I have CLT-L09 pie 9.0.0.1.9.5 with the custom link for magisk. The only way to get out of the loop is to reflash the stock recovery_ramdis.img. But after flashing stock recovery, magisk has no root any more...
Any suggestions why I only get the bootloop after reflashing the patched_boot.img?
Thanks a lot!
mauritz1972 said:
You are genius. Thanks working great p20 pro 9.0.0.191c605
Click to expand...
Click to collapse
Do you have a problem when you try to pull down the quick setting touching the right or left corner of the screen?
That happens to me when I rooted it.
I need to unlock bootloader with some key, or can i just follow the guide?
I would like to flash custom recovery -> in order to use custom ROM -> in order to gain split screen in my 7" device (ehhh)
I have root, adb, access to bootloader (everything what I need..) but it does not work in default way.. - I mean flashing just by fastboot flash recovery TWRP.img
I have checked those TWRP builds
https://twrpbuilder.github.io/downloads/twrp/ (type px5)
Flashing worked fine (no error, success message)
But after rebooting to recovery I still have original recovery. Note: I have to reboot to system, and then to recovery by adb command. There is no reset button on my device, I can only enter bootloader by long pressing volume button while booting.
I saw `backup` partition in my device. Is it possible that system is reverting recovery partition? How to fix that so I can use TWRP
SZAMAN92 said:
I would like to flash custom recovery -> in order to use custom ROM -> in order to gain split screen in my 7" device (ehhh)
I have root, adb, access to bootloader (everything what I need..) but it does not work in default way.. - I mean flashing just by fastboot flash recovery TWRP.img
I have checked those TWRP builds
https://twrpbuilder.github.io/downloads/twrp/ (type px5)
Flashing worked fine (no error, success message)
But after rebooting to recovery I still have original recovery. Note: I have to reboot to system, and then to recovery by adb command. There is no reset button on my device, I can only enter bootloader by long pressing volume button while booting.
I saw `backup` partition in my device. Is it possible that system is reverting recovery partition? How to fix that so I can use TWRP
Click to expand...
Click to collapse
That TWRP don't work in PX5. I'm trying to get it work
Good luck!
Please inform me if you will succeed.
Have you first tried to boot TWRP without flashing? I'd most certianly want to try that before flashing something.
Did that work?
This might sound super silly, but did you also unlock the bootloader first? (Sorry, I'm not familiar with your specific device so this may or may not apply in your situation)
stokedcrf said:
Have you first tried to boot TWRP without flashing? I'd most certianly want to try that before flashing something.
Did that work?
This might sound super silly, but did you also unlock the bootloader first? (Sorry, I'm not familiar with your specific device so this may or may not apply in your situation)
Click to expand...
Click to collapse
Any advice is welcome thanks
But without unlocking bootloader I would not be able to go to bootloader and use fastboot tool right? So I concluded it is already unlocked.
I tried
fastboot boot TWRP.img
Image was downloaded and booted (success message was printed in console), I lost connection with device so it went in some other mode then bootloader, but after 30 seconds of black screen I have switch power off and back on to restart.
SZAMAN92 said:
Any advice is welcome thanks
But without unlocking bootloader I would not be able to go to bootloader and use fastboot tool right? So I concluded it is already unlocked.
I tried
fastboot boot TWRP.img
Image was downloaded and booted (success message was printed in console), I lost connection with device so it went in some other mode then bootloader, but after 30 seconds of black screen I have switch power off and back on to restart.
Click to expand...
Click to collapse
What android version you have ? 8 ?
tuga_z said:
What android version you have ? 8 ?
Click to expand...
Click to collapse
9
Build nr: rk3368-userdebug 9 PQ2A 190305
Kernel v: 4.4.167
MCU: MTCE_GS_V3.07_3
It is that build:
https://yadi.sk/d/umCvHqCDzHccr/RockChip PX5 Android 9/HA/HA_px5_9.0_ota(20190528)升级包.7z
I tried using A8 roms but I can not flash it with original recovery.. It requires device name be PX5 (I have rk3368). If I remove checking from rom updater script, signature verification fails.
I have tried recovery from Malaysk pack (extracted from update.zip), tried RecoveryInstaller from malaysk, lot of TWRP which I have found in web.
Nothing worked.
However as a last chance I used bootable SD from Malaysk - recovery (for android 8) successfully installed, Malyask rom installed. Im happy now
BTW. If you want you system to not revert recovery - you need to remove "/system/recovery-from-boot.p"
SZAMAN92 said:
I have tried recovery from Malaysk pack (extracted from update.zip), tried RecoveryInstaller from malaysk, lot of TWRP which I have found in web.
Nothing worked.
However as a last chance I used bootable SD from Malaysk - recovery (for android 8) successfully installed, Malyask rom installed. Im happy now
BTW. If you want you system to not revert recovery - you need to remove "/system/recovery-from-boot.p"
Click to expand...
Click to collapse
By this you mean that you no longer need TWRP for android 8 ?
tuga_z said:
By this you mean that you no longer need TWRP for android 8 ?
Click to expand...
Click to collapse
I mean I already have Recovery v8. So I was been able to flash custom A8 ROM.
However if you would implement TWRP please message me It is always better.
SZAMAN92 said:
I mean I already have
However if you would implement TWRP please message me It is always better.
Click to expand...
Click to collapse
Except if you ever want to update your unit or MCU, then it's pretty much useless.
marchnz said:
Except if you ever want to update your unit or MCU, then it's pretty much useless.
Click to expand...
Click to collapse
Maybe you are right. But at least it is easier to backup / restore whole device with TWRP.
My way of installing TWRP and ROOT on A20e (only tested on a202f).
Everything is working both on TWRP and MAGISK.
Versions:
-Magisk (v26.1)
-MagiskManager (v26.1)
-TWRP (3.6.1_9.0)
_________________________________________________
Download attached files:
-TWRP and ROOT(magisk) Odin is included!
_________________________________________________
#Factory reset is recommended!
#Make sure BOOTLOADER is unlocked!
#If you don't need MAGISK stop at step 6 and reboot to system
[TWRP Installation]
1. Extract required files, open ODIN (as Administrator) click on the "AP" button and choose TWRP-3.6.1_9.0.tar file.
2. In the "Options" menu untick "Auto-Reboot" .
3. On your phone boot into the "Download Mode" then in ODIN you can press the START button. (make sure you are connected to PC)
4. If everything is fine there should be green "PASS!" text in ODIN.
[ If your flashing failed make sure the bootloader is unlocked and check if cable is properly connected ]
[Don't let the phone boot into system because it will replace TWRP with stock recovery.img]
6. Boot into TWRP and FORMAT DATA (Wipe/Format Data) to remove encryption.
# If you don't need MAGISK you can reboot to system. Otherwise continue reading the guide.
[MAGISK Installation]
7. From TWRP reboot into RECOVERY again.
8. Connect your phone to PC or if you moved Magisk-v26.1.zip and Magisk-v26.1.apk to SD card then use SD card.
9. Flash the Magisk-v26.1.zip file and reboot to system.
10. When you boot into system install the Magisk apk.
11. Open it and finish the installation process.
12. Reboot
ENJOY!
[UPDATE]
-Updated versions of both TWRP and MAGISK
# TWRP 3.5.2_9-0 --> TWRP 3.6.1_9-0
# Magisk v23 --> Magisk v24.3
-Remodifed VBMETA
For ANY help contact me on Telegram: https://t.me/SerbianGeek
does encryp work on this ? dont need to backup just hide data part if fone is stole
This one flashes and boots the first time, but after a reboot there is the infamous error "only official released binaries are allowed to be flashed"
/dev/null/ said:
This one flashes and boots the first time, but after a reboot there is the infamous error "only official released binaries are allowed to be flashed"
Click to expand...
Click to collapse
No problems on my end, pal.
SerbianGeekster said:
No problems on my end, pal.
Click to expand...
Click to collapse
this phone is really a PITA. every time i try to do something it's 1 step forward and 2 steps back. never suffered so much. i flashed it like 20 times. all i want is a working twrp on stock rom and pass safetynet
/dev/null/ said:
This one flashes and boots the first time, but after a reboot there is the infamous error "only official released binaries are allowed to be flashed"
Click to expand...
Click to collapse
to bypass this error:
1. connect to wifi
2. change the date to 2 august 2019
3. boot into download mode
4. flash twrp
Thank you! It worked! No problems got me.
I kinda feel like idiot that I couldn't install it with that ease before
OH **** IT WORKED !!!
I've been at this for hours, thank you so much !!!
Hello,
I have a Samsung A20e running with the a202fxxu4cvk1 firmware (a11 version). I would like to install twrp and then to root it. I tried several tutorials (Odin, OEM unblocked, USB debugging, time change) but twrp installation fails with message 'custom recovery blocked by frp'.
Can anyone help me?
I duckduckgoed, and found this XDA thread, where the second post says the following :
Nemirtingas said:
FRP: https://www.samsung.com/us/support/frp/
FRP Just locks your phone if you alter the boot or recovery image and you had a google account registered. To unlock it you have to wipe data (factory reset) and reflash stock boot.img and recovery.img before using it again. If your cousin wants to flash my ROM (lineageos-13.0) he'd better not, its not stable and he will encouter random reboots and codecs bugs. The best thing to do is to remove FRP from his phone and flash Magisk (a root manager like SuperSU) and debloat it.
For more information, find the Grandprimevelte group on Telegram.
Click to expand...
Click to collapse
The rest of the posts mention the need for a modified boot.img, else your phone would brick after adding a Google account, but I don't know about that... I have MicroG on mine with a Google account and no problems.
Anyway, frp seems to be a related to having a Google account on your phone.
fjunk said:
Hello,
I have a Samsung A20e running with the a202fxxu4cvk1 firmware (a11 version) /.../ Custom recovery blocked by frp'.
Can anyone help me?
Click to expand...
Click to collapse
Hello..I was wrong. My issue is not related to frp but OEM. OEM is unlocked according to developper menu but is not effective. Not able to upload any custom rom or bootloader.
I read that there was issue (use of a volume up button in download mode).
Any idea?
fjunk said:
Hello..I was wrong. My issue is not related to frp but OEM. OEM is unlocked according to developper menu but is not effective. Not able to upload any custom rom or bootloader.
I read that there was issue (use of a volume up button in download mode).
Any idea?
Click to expand...
Click to collapse
Indeed, my issue is that in download mode I can only do a volume down button and power button to reboot in system mode. No option to unlock bootloader.
I think you only need to do that once, afterwards, download mode doesn't warn you.
What error message do you get exactly when trying to flash TWRP, at what point, and what gives it (phone, odin) ?
lPolarisl said:
I think you only need to do that once, afterwards, download mode doesn't warn you.
What error message do you get exactly when trying to flash TWRP, at what point, and what gives it (phone, od
Click to expand...
Click to collapse
Many thanks for your update. Attached are pictures of the mobile and the Odin result. The error is an OEM issue (red text on the top of the mobile screen). In other forums, I can see that the download mode has an option to unlock OEM bootloader. I can't see it on my phone.
Putting the camera so that it covers the error message, what an amazing idea xD
I have never encountered this error, so let's start from the beginning.
Have you enabled the developer options, and activated "allow USB debugging" on the phone ? Also, if there is an option "allow OEM unlock", activate that as well (not all Samsung phones have it).
Have you installed the proper ADB and Samsung drivers ? Which version of Odin are you using ?
lPolarisl said:
Putting the camera so that it covers the error message, what an amazing idea xD
I have never encountered this error, so let's start from the beginning.
Have you enabled the developer options, and activated "allow USB debugging" on the phone ? Also, if there is an option "allow OEM unlock", activate that as well (not all Samsung phones have it).
Have you installed the proper ADB and Samsung drivers ? Which version of Odin are you using ?
Click to expand...
Click to collapse
Thanks for your reply.
That's sure that it doesn't really help to hide the error message. Usb debugging is enabled (I am able to run adb commands) and OEM is unlocked on the preference setting. I did the test with Odin 3.13 but same results with newer version. I installed an A11 firmware (a202fxxu4cvk1).
Don't t know how to go ahead. It seems that I don't have the possibility to unlock OEM in the download mode interface....
Wait, what is that about the firmware ? What did you flash, how and why ?
also, try a patched version of Odin from this post (I have 3.13.1_3B)
lPolarisl said:
Wait, what is that about the firmware ? What did you flash, how and why ?
also, try a patched version of Odin from this post (I have 3.13.1_3B)
Click to expand...
Click to collapse
I bought a refurbished mobile phone (blackmarket). It came with a 9.0 version. I tried to update to a custom rom without success so I installed the latest 'official' version
Download Samsung Galaxy A20e SM-A202F XEF France A202FXXU4CVK1 firmware
Fast download latest Samsung Galaxy A20e firmware SM-A202F from France with A202FXXU4CVK1 and Android version 11
www.sammobile.com
I uploaded this version using Odin. I also tried the patched Odin version. I read that the patched version only works with a10 version.
Huh...
I have no idea how that behaves, but I hardly see why it would cause a problem.
What else could you try... Restore factory settings maybe ?
Pressing volume up when starting in download mode ? (Note, this supposedly relocks the bootloader if it has been unlocked, if that happens and your phone isn't 100% on stock, it will brick.)