Database Develop

[STOCK][M][TMO] H811 20i Images + KDZ + Flashable Zips + OEM Unlock

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Official stock Android 6.0 Marshmallow 20i files for the T-Mobile LG G4 H811 variant only. Included below: TWRP-flashable stock rom, boot, modem and bootloader zips. Stock 20i KDZ and individual images are also included.​
20i NOTES...
1. *AntiRollback / QFuse V2* Safe to downgrade to 10N only.
2. Marshmallow bootloader requires bootloader unlock via fastboot
Requirements:
You must have TWRP 2.8.7+ installed to use these zip files. Thanks to Dees_Troy as always for that. Or you need LGUP installed to flash the KDZ in download mode.
Install Directions:
You can install stock 20i M with zip files in TWRP or flashing a KDZ in LGUP or LG Bridge. Due to the new 20i bootloader fastboot oem unlock requirements there is almost no benefit in using one method over the other.. both KDZ or ZIP upgrade methods work. If coming from Lollipop there is no way to retain TWRP or root since the new bootloader has a new unlock method.
To flash via zip in TWRP:
1. Download LG-H81120i-Flashable.COMPLETE.zip place it on internal or external sdcard (external preferred).
2. (re)Boot into TWRP if not there already.
3.* Backup current partitions: boot, system, data, efs to external sdcard if possible (optional but suggested)
4.* Up to you if you want to wipe data (TWRP > Wipe > Swipe slider) but not needed if coming from a stock rom.
5. Install LG-H81120i-Flashable.COMPLETE.zip (Install > select zip > swipe to confirm/flash)
6. After zip finishes you can reboot into M! (if TWRP asks if you want to install SU, HIT NO!!!)
7. If you want root or TWRP follow the bootloader unlock directions in the next section below.
To flash via KDZ:
1. Easiest way to flash the KDZ is just using the official LG Bridge tool. You can grab it for Windows or Mac HERE
2. Alternative to LG Bridge is downloading the 20i KDZ yourself from the Codefire directory link further below then following the LGUP thread HERE for a how-to on KDZ flashing. .
3. If you want root or TWRP follow the bootloader unlock directions in the next section below.
Bootloader OEM Unlock + Root:
Starting with the Android 6.0 20i bootloader it has to be unlocked, sorta like a Nexus, with fastboot. Previously only 'OEM Unlock' had to be toggled in Android Developer settings for TWRP or custom boot images to work.
1. Flash stock 20i using zip or KDZ. Boot into Android after upgrade to 20i.
2. Download the twrp-2.8.7.1-h811.img file HERE. This file needs to be on your computer and external sdcard*.
3. Download the latest SuperSu zip (2.67+) from HERE [Thanks to Chainfire] and stick on external sdcard*.
4. Confirm "OEM Unlock" is set to enabled in the hidden Developer Settings.
5. Enable "USB Debugging" in Developer Settings, connect USB cable PC <-> Phone... and send the following 3 commands in command prompt/terminal:
Code:
adb reboot bootloader (phone reboots to bootloader)
fastboot oem unlock (this wipes ALL data!!)
fastboot boot twrp-2.8.7.1-h811.img (phone boots TWRP)
6. For perm TWRP: In TWRP hit Install > Images... (bottom right corner) > select TWRP.img on ext sdcard > select "recovery" > swipe.
7. If you want root: Hit the Home button > Install > select SuperSU zip on external sdcard > swipe.
8. All done. Reboot into Android. (if TWRP asks if you want to install SU, HIT NO!!!)
*if you do not have an external sdcard to save SuperSU and the TWRP.img onto.. you will need to skip saving the files to sdcard until AFTER you fastboot OEM unlock and boot into TWRP. After fastboot booting TWRP you can use adb push to put SuperSU and TWRP.img onto the internal sdcard to install with TWRP. Or you can use the MTP mount option in TWRP and drag n' drop the files from the computer to the phone. You cannot store the files on the internal sdcard before the OEM unlock because OEM unlock wipes all you data.
Please do not mirror my files!
Downloads:
LG-H81120i-Flashable.COMPLETE.zip
100% stock untouched system, boot, modem and bootloader.
LG-H81120i-Flashable.Modem.zip
This is a flashable stock 20i modem.
LG-H81120i-Flashable.Boot.zip
This is a flashable stock 20i boot.img. Boot.img contains kernel + dtb + ramdisk.
LG-H81120i-Flashable.Bootloader.zip
This is a flashable stock 20i bootloader. It contains aboot, factory, hyp, laf, pmic, raw_resources, rpm, sbl1, sdi, sec and tz. If you have not already unlocked the bootloader through fastboot on 20i or higher... you will need to run stock LG M to unlock before using the M bootloader on CM or AOSP roms.
Also, KDZ + all stock images for 20i are available in the link below...
CODEFIRE DIRECTORY
MD5 Sums:
Click button below to view MD5 for each file...
MD5 (aboot.img) = 1d46ac119f89e48bb5c7d412a01eaf70
MD5 (boot.img) = 01ae6bd65523428567cbd5e012b1fef7
MD5 (factory.img) = 6e2d5a6f596befbb9b4a6852712b0c6c
MD5 (H81120i_00_0201.kdz) = 21b011e8b0410b64336c40bf6817f32a
MD5 (hyp.img) = 2c633be343054a300e4c161158762db3
MD5 (laf.img) = c7b4b2e478ce4749089d07de3a0be823
MD5 (LG-H81120i-Flashable.Boot.zip) = bfa2f1b8cbb9a55af23be7ac080c1ea4
MD5 (LG-H81120i-Flashable.Bootloader.zip) = 527bb58d7f9fcbaa383c6b4500d91424
MD5 (LG-H81120i-Flashable.COMPLETE.zip) = bf9d74bb603063e3e45549e1cfef9c4d
MD5 (LG-H81120i-Flashable.Modem.zip) = 3509dda24c85cb60c07d5818823e9524
MD5 (modem.img) = 7e67c715f70b5b6d797a2c6c71247279
MD5 (persist.img) = 451427e31a42ff055adeb7364b9b927d
MD5 (pmic.img) = 27949a20917c61f9fbb296178565b4b1
MD5 (raw_resources.img) = 43d74c6229d6e4ac851844ce8933c0c7
MD5 (rct.img) = 03e489583925004bab373b4fd71ab251
MD5 (recovery.img) = 41c1d13acd617d882e8f8ac678ce3b94
MD5 (rpm.img) = 3f1c59968b8c798fbb664cd279076deb
MD5 (sbl1.img) = a7ee1a6e3370917b6b57e927b337a83e
MD5 (sdi.img) = df16bace89164b4a8ad224fb0ca4f4c8
MD5 (sec.img) = e1d32ec012c59dd9020687ea71241d1a
MD5 (system.img) = d1f18956219cfe75d0732d1ce7be31ea
MD5 (tz.img) = 0088536b7dbf8013fb49055db5410a7f
Downgrade:
To downgrade you can use TWRP to restore your backups... and then just flash the matching bootloader zip and modem zip from my previous threads... or just check the CODEFIRE DIRECTORY link for previous stock files.
OR
Use LGUP HERE to flash a previous KDZ version. KDZ will remove TWRP but easy enough to reinstall that.
Click to expand...
Click to collapse
y u quote OP?
Follow me on twitter for future updates on LG-related things - twitter.com/@utoprime
Find this thread helpful? Like getting M ASAP? Enjoy flashable zips? Hit the Thanks button!
Feeling extra generous? Hit the Donate button under my name in post #2 or click my name at the top of this post.
Seems XDA removed the visible Donate button in OP. Thanks XDA...
Thank you to the following people for their donation:
@MickyFoley
@mark-e-mark
#TEAMCODEFIRE

I'll be using this space to respond to some questions rather than posting throughout the thread where others may not see it. Everything should be pretty standard at this point though. These are 100% stock files.. not debloated or deodexed or anything.
Feb 16 2016
I have edited the OP to suggest the 2.8.7.1 TWRP over the 3.0.0-0 version for now. I have had a few users in IRC tell me that after flashing 20i, unlocking bootloader, installing twrp then flashing CM13 causes some issues with data not mounting and some mention of "cannot find crypto footer". Will talk to dees_troy tomorrow hopefully and see what's what.... not sure if it's a TWRP issue.. or an LG issue or wat. But just in case.. using a known good working TWRP is the best bet for now.
Q & A:
Q:
DrakenFX said:
I know the answer but, updating via LG Bridge will loose Root/TWRP right?
If that the case which i know it is, is there a way to root in Marshmallow? Or is just safe to flash the files but stock recovery?
Click to expand...
Click to collapse
A:
due to the new bootloader unlock on 20i it is possible to flash stock unrooted 20i and then bootloader unlock and install TWRP/root. Directions for bootloader unlock are in the OP!

Wooooohooooooo
Sent from my LG-H811 using Tapatalk

This was fast!! Thank you!

i love you autoprime ! <3

Holy crap outta nowhere. Thank you auto!

Thanks. Will try tonight.
Pat

@autoprime
I'm so wanna give you a hug , been waiting for this for a while
Question..
I know the answer but, updating via LG Bridge will loose Root/TWRP right?
If that the case which i know it is, is there a way to root in Marshmallow? Or is just safe to flash the files but stock recovery?

Yes!

Thank you!

Just installed all this along with the latest xposed.
Now I have secure booting error 1003.
Wtf. I followed everything to a T how do I get back into TWRP from here?
I had OEM unlock checked before I flashed.

Raptor5150 said:
Just installed all this along with the latest xposed.
Now I have secure booting error 1003.
Wtf. I followed everything to a T how do I get back into TWRP from here?
I had OEM unlock checked before I flashed.
Click to expand...
Click to collapse
Check out this post. Stated you need OEM Unlocked in Developer Options first:
http://forum.xda-developers.com/showpost.php?p=62104913&postcount=3
Also to get to TWRP: completely shut down the phone. Remove the battery if you need to. Then when it's off, hold down Power and Vol Down buttons together. Then when the LG logo appears let go of Power Button for a second (still holding down Vol Down) , then hold the Power Button and Vol Down again. The factory reset screen comes back, click yes and yes. It will reboot into TWRP. (this is if you know for a fact TWRP is still there)

aoaleman said:
Check out this post. Stated you need OEM Unlocked in Developer Options first:
http://forum.xda-developers.com/showpost.php?p=62104913&postcount=3
Click to expand...
Click to collapse
I could have sworn I had it checked. I always have it checked.
Especially on a phone that will let me.
Now what do I do? Its just bootlooping the LG screen.

Raptor5150 said:
I could have sworn I had it checked. I always have it checked.
Especially on a phone that will let me.
Now what do I do? Its just bootlooping the LG screen.
Click to expand...
Click to collapse
You wouldn't have it checked if you flashed the complete zip above. I'm guessing you would need to wipe all (except internal and/or sd card), then reflash the complete zip, boot into system. Check OEM unlocked in Dev Options. Then reboot back to recovery, flash SuperSU.
I'm thinking this would make it work, not sure though.

aoaleman said:
You wouldn't have it checked if you flashed the complete zip above. I'm guessing you would need to wipe all (except internal and/or sd card), then reflash the complete zip, boot into system. Check OEM unlocked in Dev Options. Then reboot back to recovery, flash SuperSU.
I'm thinking this would make it work, not sure though.
Click to expand...
Click to collapse
Its bootlooping though how do I get past this?
edit: Read your edit

Coming from stock 10n, Wiped, Flashed 20i zip, flashed SuperSU -
Now i get "Secure booting error - Error Code:1003" then continues to bootloop showing that error everytime
Can't even boot into recovery, damn i'm screwed all day at work only Macs here D':

Raptor5150 said:
I could have sworn I had it checked. I always have it checked.
Especially on a phone that will let me.
Now what do I do? Its just bootlooping the LG screen.
Click to expand...
Click to collapse
You can Re-check just go to DEVELOPER OPTION and check OEM ENABLE gain

Doing the factory reset still didnt work. GOD DAMN IT.
Sigh... Phone is just a brick now I guess.

Raptor5150 said:
Doing the factory reset still didnt work. GOD DAMN IT.
Sigh... Phone is just a brick now I guess.
Click to expand...
Click to collapse
Factory Reset screens don't take you to TWRP? What happens?

aoaleman said:
Factory Reset screens don't take you to TWRP? What happens?
Click to expand...
Click to collapse
Just shows the secure boot error again doesnt load into anything. Which I have no idea how that is possible. Ill keep trying. But I hit yes and yes and then nothing. Phone reboots and keeps secure booting error.

[How To Root] [EMUI 5+EMUI 8]+[KangVip Rom V.1.1] Huawei P8 lite 2017 PRA (Prague)

​​​​​[How To Root]
[2017 Family] Huawei/ Honor series PRA (Prague)
-Android 7.0 -EMUI 5.0
P8 Lite 2017 - PRA-LX1, LX2, LX3, LA-1
P9 Lite 20176
NovaLite
Honor 8 Youth
Rooting has been developed and tested on this device:
Huawei P8 lite 2017 [PRAGUE]
Model number: PRA-LX1
Build number: PRA-LX1C432B170
Free device
You need:
- PC or Windows tablet
- USB cable
- Windows 7 / 8.1 / 10
- Minimal Adb and Fastboot
- OEM unlocking in the developer options active
- Huawei HiSuite (installs all necessary drivers)
OEM and FRP unlocked
Bootloader unlocking:
- Go to this page: Homepage - EMUI - on UNLOCK (Currently offline.),
- then on Account login - and log in with the Huawei ID.
- Then confirm the terms and conditions.
- On the next page, fill in the form. This page is self-explanatory.
- Confirm your entries with "Commit". The unlock code is now displayed immediately.
- Please note down immediately.
- Now start the PRA in fastboot mode and enter fastboot oem unlock in the Adb command window (PC)
- followed by your unlock code. (like this: fastboot oem unlock 123456787890987654)
- Now comes a hint screen, in which the unlocking is pointed out.
- You now have the option to cancel this action. If you confirm with yes, it will be unlocked and a
- Factoryreset will be performed.
FRP - Unlocking:
- After the reboot has just been executed, the device starts the new setup.
- Reject or skip anything related to security and Google. Can be made up later.
- After setup, turn on OEM unlock and USB debugging in the developer settings and boot back into Fastboot mode.
- It should be there now: FRP Unlock
Rooting:
The following is required:
TWRP recovery (prague311.img)
-in the ADB directory
SuperSU2.82-EMUI5-dm-verityPermissive.zip
(By @Tecalote)
-to the Ext Sd
Backup your data using Huawei Backup.
Please enter only flash commands by using Adb.
Reboots only by keyboard combination.
Installing TWRP:
Connect the device via USB to the PC and start into the boot loader
(Fastboot Mode):
Now start adb on the PC and enter it in the terminal:
fastboot flash recovery prague311.img
Disconnect device from PC and start TWRP: Press Vol + and Power and hold both.
When signs or logo appears on the screen, release the buttons.
After a few seconds TWRP starts.
There the SuperSU2.82-EMUI5-dm-verityPermissive.zip flash
and reboot.
The device starts twice before it finally boots.
Then load from the Playstore the Busybox.apk from Stericson
and thus install Busybox into this path:
/ Su / Xbin
In the future:
All actions in TWRP must be executed wisely.
Learn about the features of this custom recovery.
Note:
The data partition is mountable in TWRP,
but is not reliably secured or restored.
Therefore, never delete the internal memory and data partition,
or perform a factory reset. I have had the experience that too.
Other partition backups will never be restored as they are
were created. A perfect restoring is not possible.
Please do not use TWRP for backup and restore operations.
If a backup or restore should be done, please always without the data partition.
Apply a factory reset only in stock recovery.
This can be done with a regular backup per Huawei data backup.
Button combinations:
Fastboot Mode: Vol.- and Power with PC connection
Recovery: Vol. + and Power without PC connection
eRecovery: Vol. + and Power with PC connection
All system reboots always without PC connection.
Without PC connection means that the cable from the PRA
is separated, only from the PC is not sufficient.
I wish you success!
Root the PRA is now also available with the Magisk-v13./16.
Requirement:
- Firmware from the B164
- not root
Who has already rooted with SuperSu, lets
everything as it is.
Magisk Rooting:
- Install MagiskManager-v5.3.0.apk
- flash Magisk-v14.0.zip by TWRP
- flash BusyBox-Magisk-1.25.zip by TWRP
- reboot and update the MagiskManager.
For this we thank the Magisk developer
@topjohnwu.
[How to unbrick]
The procedure of rescue is risky.
Without appropriate knowledge, I advise.
It is only successful if the instructions are executed exactly.
This TWRP backup rom is not suitable for normal use. It was created for the following purpose:
- Rescue of bricked phones.
- Force an OTA update.
Do not root this rom!
Unzip the download 2017-08-11-RESCUE.ROM.PRA.OTA.B164.to.170.rar (1.05 GB).
This creates the TWRP backup:
2017-08-11-RESCUE.ROM.PRA.OTA.B164.to.170
installation:​
copy my backup to the TWRP backup path to the Ext Sd.
(see screenshot)
Boot into the Bootloader.
Stock Recovery flash by adb.
In the recovery start and
perform a factory reset.
Boot into the Bootloader.
TWRP flash by adb.
To start TWRP.
There data wipe
and restore my backup.
In the Bootloader start and
flash by adb the Stock Recovery.
There then again a factory reset.
Reboot
When the boot process is finished,
Go to Settings> Update program> New version> Update.
Will not be offered, in the Stock Recovery again perform a factory reset.
The upgrade to the B170 succeeds only with sim-card.
You have now done an official update and a new, clean and up-to-date firmware.
Congratulation!
Thread Update: 2017-11-10
There is also an alternative method. This can work, but it doesn't have to.
Starts the device into eRecovery and tries to recover and download the firmware.
If you had the B170, this one will also be sent to you here offered.
If it works, then immediately starts the download and installation.
Thread update: 2017-12-09
[Rooting B182]
With SuperUser:
After the update to the B182
surely TWRP already flashed
and created a backup.
Now installed in TWRP, on the Stock Kernel,
the "SuperSU-v2.82. PRA. B182. zip"
from the appendix.
Reboot and ready.
You can use the Busybox from the App
suggested path.
With Magisk:
As described above.
Nothing's changed.
Threadupdate: 2017-12-30
Here's the new rescue rom:
https://forum.xda-developers.com/p8...ck-rom-huawei-prague-pra-xxxc432b182-t3727816
Threadupdate: 2018-01-04
Here I have a new possibility to restore a bricked device:
It's an original Huawei UPDATE.APP.
It is designed for emergencies to repair damaged firmware.
However, some functions are limited until the next OTA Update.
The Magazine-Unlocking does not work and other themes cannot be activated.
TWRP backup and restore are faulty and can lead to a brick.
Don't use dual recovery here. eRecovery is mandatory.
After downloading the UPDATE. ZIP you unpack the archive.
Now create the folder dload on the ExtSd
and copies the resulting UPDATE.APP there.
Now in the dialer with the input of *#*#2846579#*#*
call up the secret menu and perform the update. If you can't boot anymore, you start
the update as follows, without USB connection:
Vol. + and vol. - and power and press together and hold on tight. The device goes off and on again.
As soon as text appears on the display, release all keys. Now start after the update process within a few seconds.
After this update the firmware should be repaired.
TWRP and root do not need to be removed as they are overwritten during the update.
The FRP is then locked again.
After the first reboot go to recovery and make a factoryreset and reboot again.
Now disable in the developer options the oem unlocking und your device is full stock wihout the bootscreen: "your device has been unlocked and can't be trusted". If you need twrp and root again, unlock with the huawei unlockcode.
Good luck.
And now we install the OREO-Beta:
Download:
LX1C432B321-PRA log (8.0.0.321)
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G2312/g1699/v130567/f1/full/update.zip
Instructions:
The UPDATE.ZIP from the download, nocheck.img and Magisk-v16.0.zip copy to the extSd card.
Perform a HW backup
Sync your Google Account.
Write down Google Login data.
Enable OEM unlocking and USB debugging.
Perform a factoryreset. (Stock Recovery)
Now carry out a short new setup.
Reject everything for security and google, or skip it.
Can be made up later.
Reactivate OEM unlock and USB debugging.
Now flash TWRP. (prague311.img)
Then install nocheck.img into the recovery partition with TWRP.
This is a stock recovery that bypasses the UPDATE.ZIP check and makes it
so that it can be installed.
Now enter the following command in the TWRP terminal:
echo -update_package=/sdcard/update.zip > /cache/recovery/command
Please follow the exact spelling!
Then enter in the terminal: reboot recovery.
The device now boots into the recovery and installs the UPDATE.ZIP.
That'll take a while. Afterwards you boot directly to OREO.
Congratulations!
I've been using OREO for a few hours now and haven't found any bugs yet. They are of course
as it is probably a beta version.
The settings still contain the same firmware entry,
as before installation. I don't know why that is. But it is
actually the EMUI 8 firmware with Google patch from 01.04.2018.
A test of the eRecovery recovery revealed that there the rollback of
EMUI 8 on 5 is offered. I promptly tested it successfully.
Rooting:
Install the OREO TWRP via ADB. (FIGO4.img)
fastboot flash recovery_ramdisk figo4.img
Install the Magisk-v16.zip there.
After rebooting the Magisk Manager app and check the root.
To what extent an update capability to the following firmware exists,
is unfortunately beyond my knowledge and remains to be seen.
Have fun with OREO.
One more comment on the new TWRP:
The TWRP comes from my P smart and is compatible.
More partitions can be backed up there than used to be the case.
However, restoring carries unpredictable risks/results.
Please select only the following partitions for backups in the future:
kernel
Boot Ramdisk
Recovery Ramdisk
System
The data partition can only be backed up after a previous formatting.
You will to get back to EMUI 5:
Starts the eRecovery. There will be a rollback for EMUI 5, at the latest after a Factoryreset.
And now for the final:
[OREO-Custom Rom] Huawei P8 lite 2017 - PRA-LX1 -
K-Rom V.1.1 - EMUI 8, Android 8
On TWRP backup basis:
Developed and tested on this device:
Huawei P8 lite 2017 (Prague)
Model Number: Huawei PRA-LX1
Build Number: FIG-LX1 8.0.0.0.046(C432)
free device, without branding, with root and
TWRP recovery
The OREO beta from this thread is required:
Huawei P8 lite 2017 - PRA-LX1C432B321(8.0.0.321) - EMUI 8/ Android 8 - OREO
Mods:
Call Recorder and KangVip Advanced Settings
It is based on the official Asia-B046 and KangVip version for the Honor V10 (BKL)
Quick guide for experienced users:
Please make a TWRP backup of these partitions,
separately: Kernel, Boot Ramdisk, Recovery Ramdisk and System.
It serves to restore the old system, if you don't like this Rom.
The Rom will be installed as if you were restoring a TWRP backup.
wanted to. All your apps will be preserved.
Further requirements:
TWRP Recovery,
Root is not necessary,
OEM and FRP unlocked,
USB debugging on.
You are familiar with the subject? Then let's go!
A Unroot is not necessary.
Preparation:
Your device must be fully equipped. Including all accounts and apps.
Synchronize the accounts as usual. Especially the Google Account.
Perform a backup with the Huawei data backup.
Remove the device pin, Sim Pin, Face Unlock and the fingerprint.
Installation:
Download: 2018-04-22-PRA-OREO-K-ROM-V1.1.exe
Run this self-extracting archive on the PC.
This creates a TWRP backup folder.
Copy to the TWRP backup directory on extSd.
Restore the backup completely and reboot it into the system.
Do not wipe before and after restoring.
The installation is now complete.
Xposed is not perfectly compatible yet and I will send it later. The system has root
with Magisk. Therefore the existing SuperSu app has to be deleted.
Do not use "hide NavBar" in the Kangvip Advanced Settings, as it only works in China Roms.
Hiding the NavBar is integrated in the EMUI 8.
In the K-Advanced Settings / tune cpu, some changes of the Cpu power are possible. Anyone who
Power needed, can do that. Testing the "Save" options is useless. I tested it extensively.
The in-house Huawei energy saving settings are unbeatable. The Advanced Settings
I will not describe in more detail here, as these are very extensive. Most settings can be set to
the screenshots. On these it can also be seen that I have already been
I've made some design changes. See Notification Bar, Desktop and Appdrawer.
Good luck!
Downloads:*
https://mega.nz/#F!3SwSFIgK!VvtbxPWV2PssIxoHQf556g
[Team HRC]
The Rom I offer is original Huawei firmware. Modified by Kangvip and reworked by me.
If you like this work, you can make a donation to Kangvip: 志康 黄 Send money with PayPal.Me
Not for me, because I don't take money for it. I made this Rom for my purposes.
I love it when these things work. And it does. Now I share it with you.
Here is the link to the original and the developer: 微博正文 - 版版
Many thanks to:
KangVIP - Rom
topjohnwu - Magisk
@Tecalote - SuperSU
Chainfire - SuperSu
Stephen (Stericson) - Busybox
TeamWinRecoveryProject - TWRP
Huawei Technologies Co, Ltd. 华为技术有限公司
WARNING !
If all this has worked on my device, it does not mean that it goes with everyone else. Follow exactly the instructions to prevent damage. The execution is your risk.
Never make a factory reset in TWRP. Brick !!! Wipes only in stock recovery.
Tipp:
The current bricks were mostly caused by TWRP. The Data Partition is missing or corrupted. This is done by TWRP, which still generates errors. There is still no TWRP that works properly. Directly after a new update usually goes everything. But at the latest after the rooting come the problems. Then you can not edit the data partition anymore. No backup and no restoration of data partition.
NOTE: Despite careful preparation I can not guarantee that through the implementation of this Guidance does not create damage to the device or operating system, and therefore assume no liability for ensuing damage and malfunction of hardware and software! If you are still unsure, follow these steps: Only perform the procedure if any mentioned conditions (model number, Android version, etc.) apply to you or your device. Read the instructions carefully and completely, check unfamiliar terminology by google or xda. Downloaded files check for viruses. A backup of important settings and data make. The instructions do not perform, if you do not know what you're doing.
These warnings must be, that is logical. In the end, I have experienced this: For testing, I have seven times a complete backup and can also restore. TWRP worked wonderfully now. When I then restored an older backup, the old error came back.
TWRP works correctly: Before the first restoring first in the stock recovery make a factoryreset. Then also in TWRP and there data wipe. Then restore the backup. All goes well. All older backups I have deleted.
This project is finished. There are no more downloads available.

I appreciate the work of @G.Man. He tested every possible situation with this Phone to find the best way how to Root it despite the limitations of EMUI 5.0!
He wasn't afraid to bring his phone three or more times nearly to a brick just in the hope to find a possible Root Solution for us, which works pretty much good
Many thanks at this point. Without his testing and work we would not be able to get Root Rights on this Phone with newest SuperSU

I bought this phone (pra-lx1) yesterday and i check at the settings that my build number is NRD90M test-keys and i don't have the system update option available and some other stuff(like file manager).
How is this possible on a brand new device??? Is there something i can do without losing warranty?

alimentas said:
I bought this phone (pra-lx1) yesterday and i check at the settings that my build number is NRD90M test-keys and i don't have the system update option available and some other stuff(like file manager).
How is this possible on a brand new device??? Is there something i can do without losing warranty?
Click to expand...
Click to collapse
Seriously ? You got a model test then can you show a screen shot ?, I think it would be better to change it

Test model??? Really??
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Hello, i'm trying to unlock my bootlader, i have my unlocking password from huawei and when i type adb devices i get my device, then i boot into fastmode but when i type fastbbot oem unlock followed by my unlocking code it replies FAILED (remote: Command not allowed)
on the lower part on the fastboot mode it's written phone locked and frp lock : what does FRP Lock mean ?

alimentas said:
Test model??? Really??
Click to expand...
Click to collapse
That's not a test model, your oeminfo partition doesn't match the installed firmware. Is yours an operator bought one? or did you buy it unlocked?

randhackr said:
That's not a test model, your oeminfo partition doesn't match the installed firmware. Is yours an operator bought one? or did you buy it unlocked?
Click to expand...
Click to collapse
Οperator bought one.I just bought it ''factory sealed''.I am fron Greece and this was supposed to be by the place i bought it,αn unbranded EU device.
Is there is something i can do or i change it with a new one????

alimentas said:
Οperator bought one.I just bought it ''factory sealed''.I am fron Greece and this was supposed to be by the place i bought it,αn unbranded EU device.
Is there is something i can do or i change it with a new one????
Click to expand...
Click to collapse
Dial *#*#2846579#*#* (this opens project menu), select Network information Query and vendor country info a report back what you've got there.

i've succeeded unlocking my bootloader, i had to go to developer mode enable oem unlock then retry fastboot mode then it worked.

harlock59 said:
i've succeeded unlocking my bootloader, i had to go to developer mode enable oem unlock then retry fastboot mode then it worked.
Click to expand...
Click to collapse
Yes you need to enable the oem unlock option to disable the frp lock.
Is your phone not branded to any operator? If it is not could you use the twrp that is used for the rooting process to dump the oeminfo partition of your phone?

randhackr said:
Dial *#*#2846579#*#* (this opens project menu), select Network information Query and vendor country info a report back what you've got there.
Click to expand...
Click to collapse
That 's what i got.
Vendor:hw
Country:eu

alimentas said:
That 's what i got.
Vendor:hw
Country:eu
Click to expand...
Click to collapse
That's strange. You seem to have a stock oeminfo. You could try o use the firmware finder in the playstore to try to update your phone to the b118 firmware. You should have something like the screenshot that I uploaded.

i didn't understand what i had to do after unlocking bootloader, i have RootBoxLX1.rar but i don't know how to use it, i've unrared it but what should i do to make them work ?

harlock59 said:
i didn't understand what i had to do after unlocking bootloader, i have RootBoxLX1.rar but i don't know how to use it, i've unrared it but what should i do to make them work ?
Click to expand...
Click to collapse
I only installed twrp, but as far as I understand you must use fastboot to flash the modified boot.img provided in the rar file.

randhackr said:
I only installed twrp, but as far as I understand you must use fastboot to flash the modified boot.img provided in the rar file.
Click to expand...
Click to collapse
how can i install twrp and where can i find twrp for huawei pra-lx1or what is the command line to flash the modified boot.img ?
---------- Post added at 05:36 PM ---------- Previous post was at 05:32 PM ----------
isn't there a mistype (mis spelling) fastboot flash boat boot_root.img shouldn't it be fastboot flash boot boot_root.img ???

harlock59 said:
how can i install twrp and where can i find twrp for huawei pra-lx1or what is the command line to flash the modified boot.img ?
---------- Post added at 05:36 PM ---------- Previous post was at 05:32 PM ----------
isn't there a mistype (mis spelling) fastboot flash boat boot_root.img shouldn't it be fastboot flash boot boot_root.img ???
Click to expand...
Click to collapse
Check this post https://forum.xda-developers.com/showpost.php?p=71601405&postcount=62
Edit: Yes there is a misspelling it should be boot

harlock59 said:
i didn't understand what i had to do after unlocking bootloader, i have RootBoxLX1.rar but i don't know how to use it, i've unrared it but what should i do to make them work ?
Click to expand...
Click to collapse
Extract RootBoxLX1.rar, gets so all necessary files. Then work the Root instructions. TWRP may not be on the device separate the original Recovery.

I have changed the write errors boat to boot.
Sorry

randhackr said:
Check this post https://forum.xda-developers.com/showpost.php?p=71601405&postcount=62
Edit: Yes there is a misspelling it should be boot
Click to expand...
Click to collapse
thanks, that helped !

Unbrick tool for OnePlus 5

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Some china OP5 user got it from OnePlus staff, and uploaded it to china cloud drive.
[Driver]
Mega:
https://mega.nz/#!l2oXjD6Q!pT6OQjtmikWX7Q_OjTJndo3Hy1miJ3KvdE7ghe3QfPQ
AFH mirror (Thanks to @Titokhan):
https://www.androidfilehost.com/?fid=889764386195921378
[Oxygen Version Download]
After you use this tool, your OP5 will be restore into stock Oxygen OS.
Mega 1:
https://mega.nz/#!MPBXkJjK!O2uDD7Xx04KPT_cx9coMHnGtaeSK06t9gwNpUR4KDXE
Mega 2:
https://mega.nz/#!gjRFmB4C!-HN00YSS2tUy5ZQTbJbzwEmZ8VU_iv5lLaTlbXin7Ec
AFH mirror (Thanks to @Titokhan):
https://www.androidfilehost.com/?fid=745425885120760474
[Hydrogen Version Download]
After you use this tool, your OP5 will be restore into stock Hydrogen OS.
Source :
http://www.oneplusbbs.com/thread-3587805-1-1.html
Baidu pan:
http://pan.baidu.com/s/1qYz7hZu
pwd: 0fb4
Mega (corrupted):
https://mega.nz/#!kyJ1XJ7D!ghgEuR2sb1XkyGM4n5KDjOiID4KS6cFL5cIQqjSRAkc
Mega 2:
https://mega.nz/#!RmQnQKTB!ghgEuR2sb1XkyGM4n5KDjOiID4KS6cFL5cIQqjSRAkc
Google Drive:
https://drive.google.com/file/d/0B9vxnq7dlG4pYVJGaGZOYWNuZzA/view?usp=sharing
AFH mirror (Thanks to @Titokhan):
https://www.androidfilehost.com/?w=files&flid=204903
[Tutorial]
The steps is the same as 1+3T.
Ref:
https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306

Great ! I always prefer a fastboot / edl flash.
Sent from my ONEPLUS A5000 using Tapatalk

Isn't it Oxygen OS?

gonsa said:
Isn't it Oxygen OS?
Click to expand...
Click to collapse
Yes,it isn't.
However you can easily install Oxygen OS by yourself.:laugh:
Ref:
https://forum.xda-developers.com/oneplus-5/how-to/guide-installing-oxygenos-chinese-t3647409

Someone should be able to tweak this to fetch OOS files instead of H2OS. Both the firmwares are the same except userdata
Sent from my ONEPLUS A5000 using Tapatalk

Someone should upload this to androidfilehost so there are other places to download incase the original is taken down.

file in mega is corrupted.
please upload in any uploading site

@snowwolf725 ,since I already "came back" from fastboot-ed github/OOS/MSM8998 build, I like to clarify few tips:
-Unbrick via Qualcomm QFIL tools were well documented here and there (Oneplus 1/2/3/3T) ; but Qualcomm never granted free distribution of QualcommQDLoader9008 DRV or QFIL, AND your WindowsPC has to be disabled with integrity checks or antivirus. So it should be considered as the last extreme ultimate rescue.
-For cleaned & original OOS4.5.x back, with certified Playstore (and Magisk SafetyNet), full official Oneplus tools work fine : you need fastboot + original op5recovery with adb_sideload ok ; the main process is to recovery wipe allx3 + fastboot toggle OEM Lock / Unlock + fastboot erase [boot / cache / system / userdata]. The concealed trick is to recovery wipe allx3 once more (official OP5 recovery is re-branded CM/Lineage "re-signed" recovery); these 3x wipes will re-initiate "correct" user partitions from 4x fastboot/erase, with "somewhere" a kind of signature or cert (?), before adb sideloading official OOSzip.
-Then, only use official twrp for limited Magisk SafetyNet.
-IMHO, crucial persist (img /dev/block/sda2) should also be backup(, like modemst1&2 ), for advanced testers only.
(I'm not here begging for thx), but if you succeed back to "pure certified" OOS, give your thx (for others user attention) here : https://forum.xda-developers.com/oneplus-5/help/oos-darkware-fullvendor-building-t3637344 ; AND take time to check the attached Oneplus5 full "sparted" partitions txt: you "must" have identical partitioning.

@oF2pks if I get your process correctly, for a clean flash, Flash all needs to be done 3 times with the stock recovery followed by OEM lock and post that the last step is to fastboot erase boot/system/user data/cache followed by adb sideload of the stock firmware?
Sent from my ONEPLUS A5000 using Tapatalk

On this subject, we need a return to stock guide for the OP5 :good: Fine writeup oF2pks! :highfive:

oF2pks said:
-For cleaned & original OOS4.5.x back, with certified Playstore (and Magisk SafetyNet), full official Oneplus tools work fine : you need fastboot + original op5recovery with adb_sideload ok ; the main process is to recovery wipe allx3 + fastboot toggle OEM Lock / Unlock + fastboot erase [boot / cache / system / userdata]. The concealed trick is to recovery wipe allx3 once more (official OP5 recovery is re-branded CM/Lineage "re-signed" recovery); these 3x wipes will re-initiate "correct" user partitions from 4x fastboot/erase, with "somewhere" a kind of signature or cert (?), before adb sideloading official OOSzip.
-Then, only use official twrp for limited Magisk SafetyNet.
-IMHO, crucial persist (img /dev/block/sda2) should also be backup(, like modemst1&2 ), for advanced testers only.
(I'm not here begging for thx), but if you succeed back to "pure certified" OOS, give your thx (for others user attention) here : https://forum.xda-developers.com/oneplus-5/help/oos-darkware-fullvendor-building-t3637344 ; AND take time to check the attached Oneplus5 full "sparted" partitions txt: you "must" have identical partitioning.
Click to expand...
Click to collapse
Okay - my writeup of the above quick instructions:
The end goal of this process
To return your One Plus 5 (codename Cheeseburger) back to 100% STOCK condition - both recovery and ROM. OEM status will be unlocked, but this is not an issue for OTA etc. This status will be suitable to you if you wish to "start over" with the phone, sell it, or similair.
Steps
Preparation:
1. Make sure you have a WORKING ADB and Fastboot setup on your computer. I recommend the ADB tool found here:
https://forums.oneplus.net/threads/cannot-read-ota-zip.457965/#post-15957941
I had the problem "* cannot read 'D:\OP5.zip' *", but the ADB tools from the above link solved this :good:
Notice the revision difference here: https://i.imgur.com/JurOcUf.png (green = Good, working version, red = the version that failed)
2. Download the ORIGINAL OnePlus5 recovery image, AND the FULL ZIP for the stock OOS ROM - NOT an OTA image ([OFFICIAL] OxygenOS 4.5.6 (7.1.1) OTA for OnePlus 5, posted by @Funk Wizard in the 2nd post - thanks dude :highfive: )
The process:
3. Flash the stock recovery -- Command: fastboot flash recovery recovery.img
4. Boot stock recovery by rebooting the phone and press VOL+UP within 5 seconds to interrupt the process.
4a. Select Recovery with VOL buttons. Confirm with power button
4b. Choose your language in the recovery and select wipe data and cache and then Erase everything
4c. Select DONE, not reboot. Select erase everything 2 times more (so you have erased it all three times in total).
5. Reboot the phone into fastboot again, and type fastboot oem lock - confirm and let it reboot.
6. Reboot the phone into fastboot again, and type fastboot oem unlock - confirm and let it reboot.
(if you wish to have a unlocked bootloader, this allows you to flash a custom recovery and thus install custom roms).
7. Boot into fastboot mode. Now we will manually wipe and format cache, system and userdata. paste this command into the commandprompt:
fastboot erase cache & fastboot erase system & fastboot erase userdata
- This will run the 3 commands after each other.
8. Repeat step 4, 4a, 4b and 4c again. In 4c only a single "erase everything" is needed.
9. Reboot into recovery again, select Install from ADB - this will enter the sideload mode, allowing you to install ZIP (flash it) from the PC.
10. Yay. 10 step Anniversary - dont we love it?!:good::highfive:
11. Enter adb sideload C:\path\to\full\OOS\stock\rom.zip
12. The CMD window will say "serving (1%)", etc... After a good while, the phone will say Install success - reboot the phone.
Thats it! :good: 100% STOCK!

TwinAdk said:
Okay - my writeup of the above quick instructions:
The end goal of this process
To return your One Plus 5 (codename Cheeseburger) back to 100% STOCK condition - both recovery and ROM. OEM status will be unlocked, but this is not an issue for OTA etc. This status will be suitable to you if you wish to "start over" with the phone, sell it, or similair.
Steps
Preparation:
1. Make sure you have a WORKING ADB and Fastboot setup on your computer. I recommend the ADB tool found here:
https://forums.oneplus.net/threads/cannot-read-ota-zip.457965/#post-15957941
I had the problem "* cannot read 'D:\OP5.zip' *", but the ADB tools from the above link solved this :good:
Notice the revision difference here: https://i.imgur.com/JurOcUf.png (green = Good, working version, red = the version that failed)
2. Download the ORIGINAL OnePlus5 recovery image, AND the FULL ZIP for the stock OOS ROM - NOT an OTA image ([OFFICIAL] OxygenOS 4.5.6 (7.1.1) OTA for OnePlus 5, posted by @Funk Wizard in the 2nd post - thanks dude :highfive: )
The process:
3. Flash the stock recovery -- Command: fastboot flash recovery recovery.img
4. Boot stock recovery by rebooting the phone and press VOL+UP within 5 seconds to interrupt the process.
4a. Select Recovery with VOL buttons. Confirm with power button
4b. Choose your language in the recovery and select wipe data and cache and then Erase everything
4c. Select DONE, not reboot. Select erase everything 2 times more (so you have erased it all three times in total).
5. Reboot the phone into fastboot again, and type fastboot oem lock - confirm and let it reboot.
6. Reboot the phone into fastboot again, and type fastboot oem unlock - confirm and let it reboot.
(if you wish to have a unlocked bootloader, this allows you to flash a custom recovery and thus install custom roms).
7. Boot into fastboot mode. Now we will manually wipe and format cache, system and userdata. paste this command into the commandprompt:
fastboot erase cache & fastboot erase system & fastboot erase userdata
- This will run the 3 commands after each other.
8. Repeat step 4, 4a, 4b and 4c again. In 4c only a single "erase everything" is needed.
9. Reboot into recovery again, select Install from ADB - this will enter the sideload mode, allowing you to install ZIP (flash it) from the PC.
10. Yay. 10 step Anniversary - dont we love it?!:good::highfive:
11. Enter adb sideload C:\path\to\full\OOS\stock\rom.zip
12. The CMD window will say "serving (1%)", etc... After a good while, the phone will say Install success - reboot the phone.
Thats it! :good: 100% STOCK!
Click to expand...
Click to collapse
I don't know, this seems way too complicated to do.
If you are on official OnePlus firmware, just place the full zip or OxygenOS and flash using local update in settings. It's as simple as that. If you are on TWRP or custom recovery, also flash the stock recovery image.
If you are custom firmware, use TWRP to flash OxygenOS zip and then flash stock recovery. Then wipe data and cache.
Assuming that your phone is functioning properly, why would you need to use ADB sideload commands for any of these? And why on earth are you unlocking the bootloader? You do know that "fastboot oem unlock" unlocks the bootloader right?
Also check out my guide for a more in-depth but easier way of doing things.
If your phone cannot boot up, use the unbrick tool posted by OP. You will end up with a working phone but with HydrogenOS. Then flash OxygenOS on top of HydrogenOS. Wipe data and cache if needed.

File in mega is corrupt please re upload

hi guy's. dont download from mega. this file is corrupted.
only download from baidu link.
http://pan.baidu.com/s/1qYz7hZu

Sir link is not visible

Link is not visible

hsareminia said:
file in mega is corrupted.
please upload in any uploading site
Click to expand...
Click to collapse
sanjeevattre said:
File in mega is corrupt please re upload
Click to expand...
Click to collapse
hsareminia said:
hi guy's. dont download from mega. this file is corrupted.
only download from baidu link.
http://pan.baidu.com/s/1qYz7hZu
Click to expand...
Click to collapse
I add new mirror links and dirver download link.
Driver:
https://mega.nz/#!l2oXjD6Q!pT6OQjtmikWX7Q_OjTJndo3Hy1miJ3KvdE7ghe3QfPQ

jasonwsc said:
I don't know, this seems way too complicated to do.
If you are on official OnePlus firmware, just place the full zip or OxygenOS and flash using local update in settings. It's as simple as that. If you are on TWRP or custom recovery, also flash the stock recovery image.
If you are custom firmware, use TWRP to flash OxygenOS zip and then flash stock recovery. Then wipe data and cache.
Assuming that your phone is functioning properly, why would you need to use ADB sideload commands for any of these? And why on earth are you unlocking the bootloader? You do know that "fastboot oem unlock" unlocks the bootloader right?
Also check out my guide for a more in-depth but easier way of doing things.
If your phone cannot boot up, use the unbrick tool posted by OP. You will end up with a working phone but with HydrogenOS. Then flash OxygenOS on top of HydrogenOS. Wipe data and cache if needed.
Click to expand...
Click to collapse
I am aware that the process above is HIGHLY complicated - and is often not necessary.
At the time of my post, my phone was in a state where I had been doing crazy things with it (decrypted data, multiple custom ROMs and TWRP versions, including multiboot variants and the chinese one. On top of that I had flashed the am-verity and force decryption patch zip). This is as such not unusual, but my attempts to return to stock had failed (stock ROM zip failed to flash, stock recovery were wierd as well).
Therefore, when the quick layout for COMPLETE STOCK were outlined above, I grabbed them and did the process, while documenting it for future reference for others. Also, I choose to include the oem unlock and lock part - though I am fully and completely aware that it's unnecessary to 99% of the readers, after all this is One Plus phones
I had not been able to find any other sources of the steps outlined, though they may be simple, so I took all the steps how ever overkill they might be, because then there would be a documented process
The steps above would recover a One Plus 5 from a state where only adb works, pretty serious condition indeed....
I'm staying on OOS based custom ROMs as long as the blobs for the camera is undisclosed by One Plus. I haven't had time to reply to this sooner, have a great weekend, and @asonwsc, I agree with you :highfive:
Kind Regards
TwinAdk

jasonwsc said:
...If you are on official OnePlus firmware, just place the full zip or OxygenOS and flash using local update in settings. It's as simple as that. If you are on TWRP or custom recovery, also flash the stock recovery image.
If you are custom firmware, use TWRP to flash OxygenOS zip and then flash stock recovery. Then wipe data and cache.... flash OxygenOS on top of HydrogenOS. Wipe data and cache if needed.
Click to expand...
Click to collapse
Even with a locked bootloader and a certified Playstore on unrooted device , you can miss security checks : try MagiskApp for SafetyNet test + https://play.google.com/store/apps/details?id=com.cigital.safetynetplayground WITHOUT active su (root).
The only way to recover "factory"-like OP5 device is to follow fastboot/erase4 by recovery/wipes3, and thus you need to unlock. Then sideload original OOS/H2O
You can relock before entering Oneplus' Wizard settings (reboot physical power button long press) and sale OP5 like effective brand NEW.
( @TwinAdk don't get why you "missed" [fastboot erase boot.img] ; still prefer my R&B "style": https://forum.xda-developers.com/oneplus-5/help/oos-darkware-fullvendor-building-t3637344 )

oF2pks said:
Even with a locked bootloader and a certified Playstore on unrooted device , you can miss security checks : try MagiskApp for SafetyNet test + https://play.google.com/store/apps/details?id=com.cigital.safetynetplayground WITHOUT active su (root).
The only way to recover "factory"-like OP5 device is to follow fastboot/erase4 by recovery/wipes3, and thus you need to unlock. Then sideload original OOS/H2O
You can relock before entering Oneplus' Wizard settings (reboot physical power button long press) and sale OP5 like effective brand NEW.
( @TwinAdk don't get why you "missed" [fastboot erase boot.img] ; still prefer my R&B "style": https://forum.xda-developers.com/oneplus-5/help/oos-darkware-fullvendor-building-t3637344 )
Click to expand...
Click to collapse
But if the device is considered certified on the play store, then it passed SafetyNet without an issue.
Correct me if I'm wrong, but shouldn't SafetyNet pass under the following conditions?
1. Locked bootloader with no root (stock)
2. Unlocked bootloader with Magisk root.
Is it actually possible for a locked bootloader and unrooted phone to fail SafetyNet? You can't root without the unlocking the bootloader, so how would that trigger SafetyNet?

[ROM][SOFIAR][11][UNOFFICIAL][GAPPS][VANILLA] ArrowOS

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ArrowOS​
ArrowOS is an AOSP/CAF based project started with the aim of keeping things simple, clean and neat.
Website: https://arrowos.net
Telegram: Channel | TG Portal/Links
Github: https://github.com/ArrowOS
Code Review: review.arrowos.net
E-mail: arrowos.contact
PayPal: Donate to us
Blog: blog.arrowos.net
WHAT WORKS?
Almost everything
WHAT DOESN'T WORK?
You tell me
Be sure to include a log : via the Matlog app included or check how to
DOWNLOADS
Here!
INSTALLATION - TWRP
Unlocked Bootloader Required: google "unlock motorola bootloader"
Download the ArrowOS zip and copy to your external sd card
Download/Install firmware with the latest version of Moto Flash Tool
(this tool also prepares the b slot for custom rom installation)
Boot to the start/welcome screen
Power off and reboot to the bootloader/fastboot interface (power and volume down)
Install TWRP to slot a and slot b
Code:
fastboot flash recovery TWRP.img
fastboot flash recovery_b TWRP.img
Boot to TWRP (navigate with the volume buttons, select recovery, press power)
FORMAT DATA!!
Flash the ArrowOS zip
REBOOT TO RECOVERY!!
Reboot to system
Profit
INSTALLATION - FASTBOOTD
Unlocked Bootloader Required: google "unlock motorola bootloader"
Download the ArrowOS zip and extract it to your adb/fastboot folder
Download/Install firmware with the latest version of Moto Flash Tool
(this tool also prepares the b slot for custom rom installation)
Boot to the start/welcome screen
Power off and reboot to the bootloader/fastboot interface (power and volume down)
Install TWRP to slot a and slot b
Code:
fastboot flash recovery TWRP.img
fastboot flash recovery_b TWRP.img
Boot to TWRP (navigate with the volume buttons, select recovery, press power)
FORMAT DATA!!
In TWRP reboot menu, select fastboot, wait for it to reboot
Open a cmd window where you extracted the files to earlier and flash the ROM with the below commands
Code:
fastboot flash boot boot.img
fastboot flash vbmeta vbmeta.img
fastboot flash product product.img
fastboot flash system system.img
Reboot to system
Profit
*** Dont install Magisk until you have booted the ROM once
ROM Source: https://github.com/ArrowOS
Kernel Source: https://github.com/Odin1101/Project-Sofia/tree/Upstream-plus
Device Source: https://github.com/whatthef84/android_device_motorola_sofiar-1
Vendor Source: https://github.com/whatthef84/android_vendor_motorola_sofiar-1/tree/android-11
Many thanks to @vache for the above device/vendor trees, the flash tool, and building TWRP. The guy's a legend!

View attachment 5273685View attachment 5273649View attachment 5273651View attachment 5273653View attachment 5273655
View attachment 5273657View attachment 5273659View attachment 5273661View attachment 5273669View attachment 5273671View attachment 5273673View attachment 5273675View attachment 5273677View attachment 5273679

Agh, plain AOSP. I miss Havoc already.

Testing it out and everything thing seems smooth. I did find one minor issue for the people that like their temperatures in imperial units. You can change the lockscreen temp to imperial and it displays an F for farenheit but the temperature value is still Cecius.

Flashed twrp using minimal adb to recovery and recovery_b. Flashed arrow after formatting. Now I have no mobile data connection. Also getting: access point name settings are not available for this user, under apn. Tried fastboot erase modemst2, resetting, installing other roms doesn't work either. I'm on XT2041DL. Thoughts?

jonshmorg said:
Flashed twrp using minimal adb to recovery and recovery_b. Flashed arrow after formatting. Now I have no mobile data connection. Also getting: access point name settings are not available for this user, under apn. Tried fastboot erase modemst2, resetting, installing other roms doesn't work either. I'm on XT2041DL. Thoughts?
Click to expand...
Click to collapse
You will need to go back to rooted stock, and copy your apn_conf.xml file from product/etc to your sd card, amd replace it on arrow (or another rom)

Quantumstate said:
Agh, plain AOSP. I miss Havoc already.
Click to expand...
Click to collapse
Closest thing to havoc is crDroid ATM mate, it's on the forums here

This ROM is marked as only being compatible with sofiar, but I can confirm that everything seems to work on my sofia device.

Also, I had a problem when installing and I thought I should warn others. When I tried to install with TWRP, it failed and always booted back to TWRP when I tried to boot to system. When I tried the fastbootd method, it also failed because fastbootd is not available when TWRP is installed. Instead, I did this:
1. Skip the step of installing TWRP. It messes things up. You may be able to install it later, but I don't want to take my chances.
2. For the "format data" part in TWRP, run
Code:
fastboot -w
instead.
3. Instead of rebooting to fastboot from TWRP, run
Code:
fastboot reboot fastboot
.
4. Continue with the steps of installing boot, vbmeta, product, and system with fastboot.
Edit: It turns out I was using the wrong build of TWRP. Use the one linked in the original post, not the one elsewhere on the forums.

RaspberryPiBen said:
Also, I had a problem when installing and I thought I should warn others. When I tried to install with TWRP, it failed and always booted back to TWRP when I tried to boot to system. When I tried the fastbootd method, it also failed because fastbootd is not available when TWRP is installed. Instead, I did this:
1. Skip the step of installing TWRP. It messes things up. You may be able to install it later, but I don't want to take my chances.
2. For the "format data" part in TWRP, run
Code:
fastboot -w
instead.
3. Instead of rebooting to fastboot from TWRP, run
Code:
fastboot reboot fastboot
.
4. Continue with the steps of installing boot, vbmeta, product, and system with fastboot.
Click to expand...
Click to collapse
While in twrp, if you select reboot to fastboot, that is fastboot d

Beetle84 said:
While in twrp, if you select reboot to fastboot, that is fastboot d
Click to expand...
Click to collapse
I did not have an option for that. There was system, bootloader, "edl," recovery, slot A, and slot B, but no fastboot.

RaspberryPiBen said:
I did not have an option for that. There was system, bootloader, "edl," recovery, slot A, and slot B, but no fastboot.
Click to expand...
Click to collapse
Using the twrp linked here or another?

Beetle84 said:
Using the twrp linked here or another?
Click to expand...
Click to collapse
I just noticed that. I was using the TWRP build from https://forum.xda-developers.com/t/sofia-p-r-recovery-wip-twrp-3-4-0-0.4128353/ because I assumed that was what the link was for. Thank you.

Apps aren't able to see registered fingerprints. Fingerprint auth is grayed out and the apps complain "register fingerprints on the device settings".
I have tried:
Deleting and redoing fingerprints (just one and multiple) with and without rebooting.
Confirmed the fingerprints work for screen unlock and gestures.
Re-installed 08-04-21 Vanilla build with full format, issue persists.
Anything I missed to check? I do not have my phone rooted, so cannot see system logs using the logging app.
Using sofiar (moto g8 power). Tested the apps themselves on my second phone klte (Samsung S5 Lineageos 16) and fingerprints work just fine there.

Ok so I am so frustrated with this Moto G power , If anyone can please tell me what I am doing wrong...I have rooted and ran mutliple custome roms since back in the Jelly bean days but I have always been able to do all the fundamentals of owning root and making the most of my phone.. You guys have always been helpful . SO when i attempt flash a custom rom through adb folder ( because I think you cannot flash custom roms with twrp at all) attemtp to follow your instructions to the T
but every time after install of custom , and thats any custom rom i try to boot it up for first time , prior to re-twrping, adding gapps, or magisk rooting and it literally just stays on the new rom animation for hours until i give up and I have to rescue it with lenovo'S rescue tool . Any help would be awesome ?

jdude520 said:
Ok so I am so frustrated with this Moto G power , If anyone can please tell me what I am doing wrong...I have rooted and ran mutliple custome roms since back in the Jelly bean days but I have always been able to do all the fundamentals of owning root and making the most of my phone.. You guys have always been helpful . SO when i attempt flash a custom rom through adb folder ( because I think you cannot flash custom roms with twrp at all) attemtp to follow your instructions to the T
but every time after install of custom , and thats any custom rom i try to boot it up for first time , prior to re-twrping, adding gapps, or magisk rooting and it literally just stays on the new rom animation for hours until i give up and I have to rescue it with lenovo'S rescue tool . Any help would be awesome ?
Click to expand...
Click to collapse
You need to install the official android 10 rom to your phone using the moto flash tool linked in the first post. After that you can install custom roms from fastbootd with the first page instructions.
Android 11 official rom has some changed encryption stuff which I think is responsible for the infinite boot on custom roms when flashed over it. That's why you need to downgrade to android 10 first.

ok because I am on android 11 when it is back to stock flashed. I am using the lenovo tool and it is installing rpms31.q1.54-13-2_subsidy . So to clarify I need to roll back to android 10 to be able to flash any custom roms ? Or is there 11s that will work with a different method to flash them?

Carl-Robert said:
You need to install the official android 10 rom to your phone using the moto flash tool linked in the first post. After that you can install custom roms from fastbootd with the first page instructions.
Android 11 official rom has some changed encryption stuff which I think is responsible for the infinite boot on custom roms when flashed over it. That's why you need to downgrade to android 10 first.
Click to expand...
Click to collapse
I'm not the person with the problem, but thank you for the explanation. I installed my ROMs before Android 11 came out for this phone and I was planning to test the stock Android 11 ROM, so this information will be very useful.

jdude520 said:
ok because I am on android 11 when it is back to stock flashed. I am using the lenovo tool and it is installing rpms31.q1.54-13-2_subsidy . So to clarify I need to roll back to android 10 to be able to flash any custom roms ? Or is there 11s that will work with a different method to flash them?
Click to expand...
Click to collapse
I believe you have to roll back to Android 10. Custom Android 11 ROMs may work, but you can't install custom ROMs so that doesn't help.

actually it is rescuing me to android 11 no matter what i do

[RECOVERY][UNOFFICIAL][3.5.2] TWRP for Galaxy M21 [CWB1 and Above]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Disclaimer:
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed.
Please do some research if you have any concerns about features included in this recovery before flashing it!
YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
I am not the developer.
Developer: @naz664
Changelog:
Spoiler: View
Changelog :-
- Souls recovery with latest A12 support (Jan 2023)
- Updated kernel
- This recovery won't work on older stock version
So don't flash this unless you are running latest jan 2023 stock rom
How to install?
Spoiler: ODIN (Windows)
Prerequisites: Samsung USB drivers, Odin v3.14.1
Make sure OEM Unlock is ON in developer settings;
Turn off the phone;
Press the volume down + volume up button whilst the phone is connected to a pc to boot in download mode;;
Long press vol up then confirm you want to unlock bootloader (this is needed one time only);
* Please be aware all your data will be erased including internal storage and phone will reboot!!
Let the phone boot normally, pass the setup and connect to internet (wireless or mobile data) in order to unlock RMM;
Make sure OEM Unlock is ON in developer settings;
Turn off the phone;
Use vol down + Bixby key + USB cable plugged to a pc to start the phone in download mode, short press vol up to confirm you want to go to download mode;
* If by any chance you see RMM state=Prenormal or KG state=Prenormal, factory reset data and redo from step 5!
Download TWRP.tar from download link below;
Open odin and place the TWRP.tar file in AP slot and press start. Once you press start, keep holding power and volume up button and the device will reboot to recovery mode.
* If you're coming from stock, go to "Wipe" > ""Format Data" > type "yes" to format data. If you skip this, Internal storage won't work in TWRP
Flash the encryption_disabler.zip from the link below to disable internal storage encryption and patch stock recovery restoration.
Additionally, flash TWRP_Bootlogo_patcher to patch warning screens when booting the device.
If you want to root, flash Magisk.
Spoiler: TWRP
If you're coming from other TWRP versions, download TWRP.img, reboot to recovery, tap Install > Install Image > Navigate to downloads folder > select TWRP.img > Select Recovery and swipe to confirm flash. Go to reboot and reboot to recovery and the changes will have taken place.
TWRP Source: GitHub
Credits:
Soul reaper
Nazim
Lmao
Max B
Darshana & Encrypted for testing
Important:
This version only works on the latest update of stock rom (M215FXXU3CWB1) and above. If you are running an older version, use the previous build of TWRP.
Download: Link

И что делать ?

w1nk1 said:
И что делать ?
Click to expand...
Click to collapse
Different device?

Hi Fredin friend,
I Recently upgraded SM-M215G device to OneUi5.1 (M215GDDS3CWD1-20230522142126) Binary 3 and TWRP (twrp-3-5-2-m21-v3-1-a12-tar)but anything I am flashing is either bootlooping or stuck on Rom Logo, I flashed (Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip) still only Rom Logo showing, how to boot the GSIs? Any help appreciated.

OldNoobOne said:
Hi Fredin friend,
I Recently upgraded SM-M215G device to OneUi5.1 (M215GDDS3CWD1-20230522142126) Binary 3 and TWRP (twrp-3-5-2-m21-v3-1-a12-tar)but anything I am flashing is either bootlooping or stuck on Rom Logo, I flashed (Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip) still only Rom Logo showing, how to boot the GSIs? Any help appreciated.
Click to expand...
Click to collapse
Hi
If you had unencrypted data (if you could see files in internal storage) and flashed the latest stock rom, but you didn't flash encryption/multi disabler before the first boot into OneUI, it will probably cause problems.
So try formatting data and flash encryption/multi disabler (although I believe dm verity disabler also disables encryption by default, but it won't hurt flashing them). Or you can format data and not flash anything to let data stay encrypted, but then you won't be able to use the internal storage in TWRP.

Fredin_ said:
Hi
If you had unencrypted data (if you could see files in internal storage) and flashed the latest stock rom, but you didn't flash encryption/multi disabler before the first boot into OneUI, it will probably cause problems.
So try formatting data and flash encryption/multi disabler (although I believe dm verity disabler also disables encryption by default, but it won't hurt flashing them). Or you can format data and not flash anything to let data stay encrypted, but then you won't be able to use the internal storage in TWRP.
Click to expand...
Click to collapse
Hi friend Fredin,
Thanks for the reply.
I used (twrp-3-5-2-m21-v3-1-a12-tar) and it is smooth (just like previous Soulr-A11 twrp) but sideload did not work while the other recovery (TWRP.3.7.0_11.-.M215FXXU3CWB1.tar) by Dev Ravindu Deshan works great too but Reboot to Recovery does not work properly all the time, so sometimes instead of Reboot to Recovery the changes happen when manually reboot to recovery using usb cable also sometimes it does not recognise pen drive. Till now I only managed to boot Tuki1.2 and the other Lineage 20 zip had Oplist error 1 issue. Hoping for GSI boot too later. Thanks for recovery

OldNoobOne said:
Hi friend Fredin,
Thanks for the reply.
I used (twrp-3-5-2-m21-v3-1-a12-tar) and it is smooth (just like previous Soulr-A11 twrp) but sideload did not work while the other recovery (TWRP.3.7.0_11.-.M215FXXU3CWB1.tar) by Dev Ravindu Deshan works great too but Reboot to Recovery does not work properly all the time, so sometimes instead of Reboot to Recovery the changes happen when manually reboot to recovery using usb cable also sometimes it does not recognise pen drive. Till now I only managed to boot Tuki1.2 and the other Lineage 20 zip had Oplist error 1 issue. Hoping for GSI boot too later. Thanks for recovery
Click to expand...
Click to collapse
I'm not the dev btw, @naz664 is

Fredin_ said:
I'm not the dev btw, @naz664 is
Click to expand...
Click to collapse
Hi Friend,
Naz Roms great also
sidetalk: Do you know how to unlock CWD1 Stock Rom bootloader? my bootloader isnt unlocked fully? And in Shaomi phones which model would you recommend, it has fastboot so.

OldNoobOne said:
Hi Friend,
Naz Roms great also
sidetalk: Do you know how to unlock CWD1 Stock Rom bootloader? my bootloader isnt unlocked fully? And in Shaomi phones which model would you recommend, it has fastboot so.
Click to expand...
Click to collapse
What do you mean by it's not fully unlocked? iirc the toggle stays like that once the bootloader is unlocked.

Fredin_ said:
What do you mean by it's not fully unlocked? iirc the toggle stays like that once the bootloader is unlocked.
Click to expand...
Click to collapse
Hi Friend,
When I had unlocked the bootloader of the same device while it had A11 loaded in it, the oem unlock button was TOTALLY GREYED OUT (I swear I'm not lying), I mean even the toggle button was greyed out but in above picture you can see toggle buttons are Blue color and oem-unlock toggle button is light-blue but not fully greyed out, I didnt relock my bootloader before flashing A13 Stock CWD1 update
Now I cant flash GSI they refuse to boot always stuck on bootlogo.

OldNoobOne said:
Hi Friend,
When I had unlocked the bootloader of the same device while it had A11 loaded in it, the oem unlock button was TOTALLY GREYED OUT (I swear I'm not lying), I mean even the toggle button was greyed out but in above picture you can see toggle buttons are Blue color and oem-unlock toggle button is light-blue but not fully greyed out, I didnt relock my bootloader before flashing A13 Stock CWD1 update
Now I cant flash GSI they refuse to boot always stuck on bootlogo.
Click to expand...
Click to collapse
Don't think there is any in between state. If you can flash stuff, your bootloader is unlocked. If the GSI is not booting, that's some other issue. Try the new AOSP ROMs instead.
A51 Builds by Royna - Browse Files at SourceForge.net
sourceforge.net

Fredin_ said:
Don't think there is any in between state. If you can flash stuff, your bootloader is unlocked. If the GSI is not booting, that's some other issue. Try the new AOSP ROMs instead.
A51 Builds by Royna - Browse Files at SourceForge.net
sourceforge.net
Click to expand...
Click to collapse
Thanks Friend,
It looks like Royna's ROM zips (Lineage 20 & evolution_m21-ota-tq2b.230505.005.a1-06050648-community-unsigned.zip & crDroidAndroid-13.0-20230427-m21-v9.4.zip) not flashing, reason - TWRP error : 1 Assert failed : update_dynamic_partitions(package_extract_file("dynamic_partitions_op_list") and repartition issue even while sideloading. The only one that boots is TukiRom1.2, I havent tried Tuki1.3 yet. I tried Roynas' TWRP files too but after boot to recovery they get stuck, the other TWRP files (TWRP-3.5.2-m21-v3.1-A12.tar & TWRP.3.7.0_11.-.M215FXXU3CWB1.tar) boot and work with some issues though.