[Tutorial]Root Oppo F1s with FlashTool for 6.0 (SafetyNet Passed/no red status bar)

[Tutorial]Root Oppo F1s with FlashTool for 6.0 (SafetyNet Passed/no red status bar) - Oppo F1s Guides, News, & Discussion

First of all, big thanks to @ngoralph sent me a link at May. It's a post looks like a working guide rooting A1601 with flash tool, however it's written in Vietnamese,none of us understand Vietnamese. I finally have some time to take a deeper look at that guide and figure it out how it works.
2017.11.04 Update
Added a stock recovery image generated with install-recovery.sh and boot.img(Generated from A1601EX_11_OTA_002_all_201704120142_wipe.zip) for those who don't have stock recovery image
Download Stock recovery of 20170412 : https://drive.google.com/open?id=0B1X00ZJdxkKyR3g5V3BuTlNYdlU
In short, It seems like the process was done by a tool from phone repair services. The tool itself did try to connect to an oppo server when it's opened. Anyway, lets start
Benefits in comparison with other known old root method:
1.No modification to system.img, no red status bar "root detected", no need to replace SystemUI.
2.Pass SafetyNet.
SOMETHING YOU HAVE TO KNOW BEFORE DOING
*NOTE:This method uses meta mode*
1.You need a clean install 6.0 stock rom(factory reset)(6.0 Stock firmware installed by stock recovery not twrp, all the twrp for F1s are buggy).
*why buggy? take a look at /cache/recovery/xxx.log, you'll find out the ported recovery was compiled with different PixelFormat and also many different specifications, that's why the twrp recovery often give you a black screen.
2.Some twrp automatically did some modifications with your system.img to prevent stock recovery being recovered at boot, that might be the reason everyone see the read status bar "root detected"(modification detected). (Edit: Now there're more version of ported TWRP available, so this issue depends on the version of your twrp)
3.The flash tool will only work when you have mtk driver installed properly on your PC.
4.The new added dm-varity in oppo 6.0 rom will cause /data become unreadable with recovery, thus a format of /data is required (systemless root needs /data readable with recovery because they put su.img in /data).
5.Until now, I think this CTR recovery is the most stable recovery for oppo F1s
Preparations : Installation & Downloads before rooting process
1.Install mtk driver:
If you haven't have mtk drivers installed, you can follow this tutorial to install it on your PC
https://tehnotone.com/windows-10-mtk-vcom-usb-drivers-for-32-64-bit-drivers-installation-tutorial/(this driver also works on win7)
To install the driver under Windows 10, the only method is entering trouble shoot menu to temporary disable Driver Signature Enforcement and install it.(after next reboot, the driver will not work again. You will need to do the same trouble shoot menu procedure again if you want to use it again)
If you want the driver works permantly , enabling test mode will does the trick. To enable test mode, open cmd.exe with administrator privilege,type following command
Code:
bcdedit /set testsigning on
Other problems cause the flash tool not working!! If you're sure you installed mtk driver correctly.....
If you have Core Quarantine enabled in Windows Defender,the flash tool will not be able to download firmware to your phone.(Tried to fix driver problem but all no luck until i found this.......I spent almost a day to figure out this)
To disable Core Quarantine, go to ( Windows Defender Security Center> Device Security> Core Quarantine)
2.Download DownloadTool_1612.8.exe here
3.Download a Flashtool flashable stock rom here(Any build number version is okay, but need to match your phone's hardware specifications. 3GB ram = mt6750, 4GB ram= mt6755. Even you just want to flash a single partition, the FlashTool still need you to load a full firmware,so you have to download it.)
4.Download newest 6.0 stock firmware zip( You can use your own or here is a 20170412 6.0 build)
5.Download newest Magisk flashable zip here
6.Download a little modified CTR here with "ro.product.device=A1601" which can open all the stock firmware package. (modified from this CTR recovery (original CTR credits @BouyaPK) )
LASTEST EDIT : The modified CTR recovery seems has no problem to handle official OTA package correctly after being tested(unlike some old twrp builds have issues), if you found any problem with this CTR recovery for installing any official OTA Package, please report...
Good! Now you are ready to root your device !
Here's the steps:
old steps was abandoned due to lastest edit: no need to revert to stock recovery
1. Copy magisk, 6.0 stock firmware zip to your external sd card( internal storage may had been encrypted sometimes)
2.Flash CTR Recovery to your phone with DownloadTool...Video Demonstration for this step:
https://youtu.be/DPRzWiAaaCY
Open DownloadTool_1612.8.exe, choose "Developement Mode", enter password "oppodeve", then uncheck all partitions, leave only recovery checked, then select CTR recovery image as target. ==>Press start ==>Hold phone's volume up(when your phone is off) and connect it to PC with usb cable ==> the PC detected it ==> release volume up button.
3.After flashing CTR recovery, boot into recovery , hold Volume down key+ power key boot into CTR recovery
4.Do a full wipe with CTR recovery(factory reset in wipe menu)
5.[optional step] If you have android 6.0 on your phone installed before, your /data partition was encrypted when you boot 6.0 rom , you need to wipe /data(you will loose your internal SD data). To wipe /data , in CTR Recovery Click "Mounts/Storage" ==> Click "Format /data" . If you have 5.1 firmware on your phone before you do these steps, just skip this step.
6.Install stock firmware zip ( in CTR recovery main menu ==> Click "Install zip" ==> select the firmware zip and install) (IMPORTANT: you must not reboot phone before you've done step 7(install magisk)!!!!! If you reboot system before installing magisk, your /data will end up being encrypted, You will have to do step 5 wipe data then you can install magisk)
7.Install magisk zip ( in CTR recovery main menu ==> Click "Install zip" ==> select magisk and install)
8.reboot ==> select no when ask fix stock recovery
9. you have root with SafetyNet passed.
ScreenShots:
Proof Of SafetyNet On A1601 Marshmallow Rooted Rom
{
"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"
}

EDIT: followed the instruction and sucessfully done it
maybe you should include that the zip file to be downloaded in preparation 3 is only used to flash the recovery and that they can flash any firmware via stock recovery

Red root detection warning is only in MM..
It doesn't matter how you root, u will get that red statud bar in MM if u root it as it is implemented in systemUI..

sagargjasani264 said:
Red root detection warning is only in MM..
It doesn't matter how you root, u will get that red statud bar in MM if u root it as it is implemented in systemUI..
Click to expand...
Click to collapse
nope, following this method i got root without the annoying status bar i think the red status bar triggers when something is edited in system ie like installing xposed since installing xposed triggers the red status bar even after doing this

sagargjasani264 said:
Red root detection warning is only in MM..
It doesn't matter how you root, u will get that red statud bar in MM if u root it as it is implemented in systemUI..
Click to expand...
Click to collapse
The old root method might have tampered something in system and it's possible related to TWRP because SafetyNet always show CTS profile mismatch.
With this method you can get SafetyNet pass, take a look at my screenshot, Safetynet passed ,no red status bar and also it's android marshmallow 6.0 Android Pay is only compatible with this root method.
I'm a player of pokemon go that's why I care SafetyNet

evilhawk00 said:
The old root method might have tampered something in system and it's possible related to TWRP because SafetyNet always show CTS profile mismatch.
With this method you can get SafetyNet pass, take a look at my screenshot, Safetynet passed ,no red status bar and also it's android marshmallow 6.0 Android Pay is only compatible with this root method.
I'm a player of pokemon go that's why I care SafetyNet
Click to expand...
Click to collapse
Thats good.. If u have flashed like this and have root access then can u try to flash twrp and check whats the results?
Bcos to flash custom rom of MM this CTR recovery wont work.. As it contains L data with L recovery..

sagargjasani264 said:
Thats good.. If u have flashed like this and have root access then can u try to flash twrp and check whats the results?
Bcos to flash custom rom of MM this CTR recovery wont work.. As it contains L data with L recovery..
Click to expand...
Click to collapse
I already tried, and failed with TWRP.
After the upgrade of Android 6.0, all the twrp stopped working on my device, all gave me a black screen, your MM twrp doesn't work on my device either. Even I reflashed twrp, still not working , the only solution for me is CTR.
I tried to figure out the reason twrp stopped working from /cache/recovery/xxx.log and found out all twrp was compiled with the different pixel format,such as RGB, which gave this black screen error. You can take a look at your recovery log.
I flashed twrp with flash tool, it gave me black screen so I couldn't do any operation to my system, but when I reboot, I got root detected status bar. I think the root detected might related to twrp itself.
That's why I chose CTR, correct pixel format and it did ask fixing stuff to prevent stock recovery being recovered(so I can choose no to keep system unmodified)

Finally, thanks so much for dedication. So after flashing and rooting, is it ok to restore all the apps and data that has been backed up before flashing?

evilhawk00 said:
I already tried, and failed with TWRP.
After the upgrade of Android 6.0, all the twrp stopped working on my device, all gave me a black screen, your MM twrp doesn't work on my device either. Even I reflashed twrp, still not working , the only solution for me is CTR.
I tried to figure out the reason twrp stopped working from /cache/recovery/xxx.log and found out all twrp was compiled with the different pixel format,such as RGB, which gave this black screen error. You can take a look at your recovery log.
I flashed twrp with flash tool, it gave me black screen so I couldn't do any operation to my system, but when I reboot, I got root detected status bar. I think the root detected might related to twrp itself.
That's why I chose CTR, correct pixel format and it did ask fixing stuff to prevent stock recovery being recovered(so I can choose no to keep system unmodified)
Click to expand...
Click to collapse
Have you tried my new twrp or old one?
Bcos blank screen is different in both..
Previously it tooks 1-2min
But now after some modifications in some xml it boots after 10-15 sec..
I will try to make CTR recovery for M

sagargjasani264 said:
Have you tried my new twrp or old one?
Bcos blank screen is different in both..
Previously it tooks 1-2min
But now after some modifications in some xml it boots after 10-15 sec..
I will try to make CTR recovery for M
Click to expand...
Click to collapse
I tried both new and old. Both black screen, and~ it's not just few minutes only........ it showed black screen forever~~
The most weird part was that if I press power+ volume down , I can take a screenshot of twrp,the file was stored in dcim/screenshot , and the screenshot taken was white background and purple title bar(the title bar should be blue though)

evilhawk00 said:
I tried both new and old. Both black screen, and~ it's not just few minutes only........ it showed black screen forever~~
The most weird part was that if I press power+ volume down , I can take a screenshot of twrp,the file was stored in dcim/screenshot , and the screenshot taken was white background and purple title bar(the title bar should be blue though)
Click to expand...
Click to collapse
Strange.. Bcos i have tested it personally on my 3/32 version.. Still i will try to improve twrp... But right now I am behind bug in my custom rom...

betongsky said:
Finally, thanks so much for dedication. So after flashing and rooting, is it ok to restore all the apps and data that has been backed up before flashing?
Click to expand...
Click to collapse
of course yes! why not?

Thank you so much bro evilhawk. Followed your tutorial, works flawlessly. Im on marsmallow now, with no annoying rooting detected on top. Thanks again and more power.

Oops, after installing xposed framework via ctr, after boot there goes again the rooting has been detected on top. What have i done wrong? Anybody here pls enlighten me how to flash the signature file along with xposed framework via ctr? All I know is that the verification signature is enabled when i flashed the framework. Unlike twrp that i could flash signature, i cant see the signature file for my framework. Thnks in advance

betongsky said:
Oops, after installing xposed framework via ctr, after boot there goes again the rooting has been detected on top. What have i done wrong? Anybody here pls enlighten me how to flash the signature file along with xposed framework via ctr? All I know is that the verification signature is enabled when i flashed the framework. Unlike twrp that i could flash signature, i cant see the signature file for my framework. Thnks in advance
Click to expand...
Click to collapse
You can't install normal xposed because it it might modify your /system which will trigger "ROOT DETECTED". You have to use systemless xposed. Just a reminding that sometimes the newest systemless xposed has bootloop bug, the newest version of systemless xposed often have compatibility issue with updated magisk, always check the replies of the systemless xposed thread before installing any systemless xposed. If the newest version seems to cause bootloop, install an older version of systemless xposed. A buggy systemless xposed will definitely softbrick your phone,so a backup is necessary.
btw, what is "signature file" you mentioned????? what did you mean by " i cant see the signature file for my framework" , why kind of error did you encountered?
How did you flash signature with twrp, what's that????

When installing xposed framework, the zip file i mean, is it a must that we flash along with it the .asc file? If so, how?
I mentioned twrp bec couple of years ago i remember flashing xposed framework, along with the .asc file, flashed together at once. And that .asc file i cant seem to find via bouyaks ctr.
However, no error occured after flashing xposed framework. Just like you said, the change in the system triggerd that annoying notice on top. I'll head to the systemless xposed thanks bro.
And one last, when restoring from backup(in ctr), system wont restore. Forgot the error msg, but it cause me to bootloop in recovery. Is it compatibility issue, or bug in ctr, or might be something ive done wrong? Anyway thanks replying to my inquiries bro

betongxda said:
When installing xposed framework, the zip file i mean, is it a must that we flash along with it the .asc file? If so, how?
I mentioned twrp bec couple of years ago i remember flashing xposed framework, along with the .asc file, flashed together at once. And that .asc file i cant seem to find via bouyaks ctr.
However, no error occured after flashing xposed framework. Just like you said, the change in the system triggerd that annoying notice on top. I'll head to the systemless xposed thanks bro.
And one last, when restoring from backup(in ctr), system wont restore. Forgot the error msg, but it cause me to bootloop in recovery. Is it compatibility issue, or bug in ctr, or might be something ive done wrong? Anyway thanks replying to my inquiries bro
Click to expand...
Click to collapse
ah....okay, after reading xposed thread, yeah there did exist an .asc thing which I never noticed before(I've seen that but didn't take that seriously), okay so the .asc thing is just a verification thing that verify the zip you downloaded was not corrupted, that's it! you can verify the signed zip with any GPG tools or something on PC.......I actually don't care about .asc because it seems useless to verify a zip before flashing unless your network is "extremely" unstable. I've never verify any zip with recovery and also never flashed a corrupted zip file(well, my network is very stable). Just flash the zip, the .asc is nothing related to xposed itself.
You know that when you install magisk, it patched your boot.img and also disable dm-varity? anyway there're so many possiblity to cause bootloop. I have no idea what did the zip file of xposed modify, but if dm-varity is enabled again that will cause recovery can not mount /data correctly and make the installation or restoration failed. Better check if there's an mount error of your /data. Anyway, that's just my prediction , only the error msg can give the correct information. The error log can be read from /cache/recovery/last_xxx.log, you can use "carliv menu" ==> aroma file manager ==> select aromafm.zip from external sdcard ==> use aroma file manager to copy that log to your external sd card so we can read the log and figure out what happened.

evilhawk00 said:
ah....okay, after reading xposed thread, yeah there did exist an .asc thing which I never noticed before(I've seen that but didn't take that seriously), okay so the .asc thing is just a verification thing that verify the zip you downloaded was not corrupted, that's it! you can verify the signed zip with any GPG tools or something on PC.......I actually don't care about .asc because it seems useless to verify a zip before flashing unless your network is "extremely" unstable. I've never verify any zip with recovery and also never flashed a corrupted zip file(well, my network is very stable). Just flash the zip, the .asc is nothing related to xposed itself.
You know that when you install magisk, it patched your boot.img and also disable dm-varity? anyway there're so many possiblity to cause bootloop. I have no idea what did the zip file of xposed modify, but if dm-varity is enabled again that will cause recovery can not mount /data correctly and make the installation or restoration failed. Better check if there's an mount error of your /data. Anyway, that's just my prediction , only the error msg can give the correct information. The error log can be read from /cache/recovery/last_xxx.log, you can use "carliv menu" ==> aroma file manager ==> select aromafm.zip from external sdcard ==> use aroma file manager to copy that log to your external sd card so we can read the log and figure out what happened.
Click to expand...
Click to collapse
I see, might be the trials ive done after the detection appears, i mean not going tru the whole process. but its negative, we have to start from the very beginning(your tutorial). i could get used to the flashing process but its backing up and restoring that consumes time.
attached here are the last_logxx files, i zip them using xplore as i cannot see them tru carlivs...
oh oh... how to send files here? lol

Attached are the lastlogxxs bro, zipped tru xplore.

betongsky said:
Attached are the lastlogxxs bro, zipped tru xplore.
Click to expand...
Click to collapse
I took a look at your log files, however I don't think there's any error when you tried to restore /system.
It's at log 5.
According to the log, all files in /system were restored successfully.

Related

[Guide][Tutorial] Root TWRP LG G5 using Autorecowvery[H830 & V20A only][Noobfriendly]

[Guide][Tutorial] Root TWRP LG G5 using Autorecowvery[H830 & V20A only][Noobfriendly]
This is guide to root and install twrp on lg g5 T-Mobile using recowvery method.
Read 4th post before proceedingThis method is to root & install TWRP on only T-Mobile LG G5 running Nougat 20a software. If your phone isn't on 20a then first downgrade/upgrade to 20a software.
Before asking a question, first, see FAQ in 3rd post. In that way you can save a lot of time.
For Video Guide refer to 5th Post
You need to disable antivirus before extracting files. Because we are using DirtyCow vulnerability here. Which is technically a virus (It's not dangerous for pc but for exploiting android to get root access). If you can't disable AV then don't proceed because process will not work
Download:1: Recowvery (2nd post)
2: Minimal adb (2nd post)
3: TWRP
A: H830 | For H850 (Refer to this Post and read carefully)
[Download TWRP 3.0.2 as 3.1.0 is having some little issues with flashing with autorecowvery] Always download latest TWRP available for your device to avoid most issues.
(rename it to recovery.img)
{
"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"
}
Procedure:Drivers should be installed. Also install minimal ADB and fastboot.
1: Make sure to unlock bootloader. Backup internal data because it will be erased.
A: First enable developer options and toggle “Enable OEM unlock” to ON. Also enable “USB Debugging”.
B: Run Minimal ADB and Fastboot. Enter Command
Code:
adb devices
C: You will see permission dialogue on phone. Tick “Always allow” and ok.
D: Now enter.
Code:
adb reboot bootloader
E: Now phone be in fastboot mode. Enter
Code:
fastboot oem unlock
F: This will wipe all data on internal storage. Now Enter
Code:
fastboot reboot
G: Now OS will get booted. Bootloader will be unlocked but phone should be in factory reset condition. So again enable “USB Debugging”.
THEN
2: Connect phone with pc in MTP mode and copy recovery.img to phone’s internal storage (Make sure to select MTP as always to avoid problem during procedure). Extract recowvery software. (If it causes permission problems extract it to USB device and perform process from there)
3: Run “EasyRecowvery.cmd”. Press “5” -->Enter then press “7” -->Enter to disable integrity check. Then enter “0” to go back. Skip it if you are using Recowvery G5 modified.
4: Now press “2” and wait until it says warning. Press “y” -->Enter. (It won't say warning in Recowvery G5 modified)
5: It will do rest process. After Flashing TWRP it will flash “no-opt-encrypt” (This is most important to save twrp from being removed by OS)
6: Phone will boot into TWRP. Here on phone it will ask for decrypt code. Cancel it. Swipe to allow modification.
7: On pc press any key, the flashing process on phone will automatically get started. Then it will reboot into OS.
8: To flash supersu, select option 3 from recowvery windows and phone will boot into twrp. Same as step 5-6 it will automatically flash supersu.
Now Your rooted and have twrp install.
Note: For removing Encryption.
To flash a custom rom and remove encryption in twrp, you need to once format data in twrp else you won’t be able to wipe and install any custom rom in your phone.

Attachments
Recowvery G5 modified is fully working, so you can try it.
I'm still keeping easyrecowvery 1.3 in this thread as a backup plan.
Read Read Read Before using This
Test Version --> Ricksy-Recowvery | Mirror
(Ricksy Recowvery is streamlined, checks free version of EasyRecowvery. It has no unlock checks, no model verification so use it only if you're fully sured about what you're doing. It includes but isn't limited to unlocked bootloader, USB Debugging Enabled, Being on V20a firmware, LG Drivers installed, PC allowed as Trusted in USB Debugging as always)
Remember to copy latest TWRP to root of internal storage as recovery.img before proceeding.
Old Test
There is also Addition of Recowvery G5 modified 2.0 Test version as well (This script has some additional features)
(I have also turned off most security checks, so you should have an more easy rooting experience. However, this increase risk of bricking device if you do not read things properly). If you can provide your experience of using this script please share your knowledge.
Download Test version either from here or here or through attachments

FAQ
Recowvery tool is causing permission errors when I run it through computer's internal HDD storage. What shall I do?
Ans: There are possibly 2 workarounds for that.
A: Extract the zip to external USB storage and Run the tool.
B: Change the name of folder, in which recowvery tool is, to "1" and copy to root of storage e.g. "Computer:\D:\1".
Can I re-lock my bootloader after rooting and TWRP flashing?
Ans: No, as recovery partition modified now, this will brick your device.
Can I use V20C or later on my phone after rooting and flashing TWRP?
And: You can't take OTA after rooting as this might create a brick but fortunately @autoprime created TWRP flashable zips of firmwares e.g 20c,20f,20i and he might create newer builds too. Anyways here's the Auto Prime's thread, Go to "LG G5 Files" link and download file as per your variant and choice.
I bricked my phone after following this guide and now I can access only download mode, what shall I do now?
I'm on other version than 20a, What shall I do?
Ans: Really? It seems like you're kidding because this guide can never harm your device, It can either do it's work or not but there is no way for it to brick a device (Unless you don't read carefully).
Ans: You can take your phone back to v20a by using the following guide.
AnywaysYou can always bring your phone back to life by following this Back to Life thread.
How to remove encryption in TWRP? or I'm unable to access my phone's internal storage from TWRP, What shall I do?
Ans: So for this process.
a: Boot into twrp.
(you can boot to TWRP by any app or by vol- and power button combination or from option “5” --> “5” in recowvery toolkit (command window).
b: In TWRP, cancel code Windows, Swipe to allow modification then
Click -->Wipe-->Format Data-->type “yes”-->enter.
You need to do this only once. After that you can flash roms and zips unlimited times.
Will this root method work on 20c/d/e/f or others?
Well, it shouldn't. Because I tried this on 20c and it never worked, so I believe it will not work on any software other than 20a because LG removed that exploit to root after 20a. But you can try your luck and tell me if you succeed.
a: Thanks a lot i have one lg g5 h830 and i have some fear to lose the unlocking and i want to modify the phone.
b: Same i have anyone please answer it will i lost the UNLOCKING (Modified by shopkeeper) if i FLASH another ROM?
What are you people trying to ask here?
Bootloader Unlock:
Bootloader can be locked and unlocked anytime you can to do so just by typing commands in fastboot mode. In T-Mobile G5 the fastboot mode do not accept flash command that's why we can only lock and unlock bootloader.
TWRP:
As commands are limited in fastboot mode of T-Mobile G5, we are unable to flash twrp through fastboot mode. So, for this process we rely vulnerability found in G5 firmware. The only currently found method for doing so is by using dirtycow exploit to flash TWRP on H830. Only V20a contains this vulnerability to do so.
Summary:
So to flash TWRP and enjoy freedom of using custom rom (Which I suppose you refer as Unlock to) you need to be on V20a. Which can be flashed easily through LGUP with Uppercut or use my LG FlashTool method (Link in FAQ section). When on V20a firmware simply use this or your preferred method for flashing TWRP.
If you want to go back to stock, simply flash any stock KDZ and lock bootloader. If you want to get TWRP again, simply unlock bootloader and flash V20a kdz (or flash V20a kdz and unlock bootloader) then instal TWRP by using the process.
Important:
Currently our stock firmwares are running Anti-Rollback (ARB 01), LG can increment this whenever they want, whenever LG increase ARB to 02 or upper then you won't be able to get back to ARB 01 firmwares (e.g V20a ) again. Which means you can unlock bootloader but won't be able to flash TWRP as dirtycow is patched after 20a. So you will lose the ability to flash TWRP which means unlocked bootloader is useless unless someone finds another method of flashing TWRP.
So, if you want to stay unlocked, then make sure to install TWRP as described above and flash latest TWRP flashable stock base zips or use other roms like Fulmics or AOSP based. It's very simple and easy .

First of All:
After Flashing let me know about your experience by answering the poll, this will help me in updating this post.
POLL is ended, so let me know about your experience with toolkit and thread readability in comments.
Disclaimer:
Before proceeding, remember I’m not responsible for anything bad happened to your device by following this or any of my guide. I’m just trying to help. So always do it on your own risk…
Don’t blame me or Any other developer.
All tools here are developed by different personalities. I’m just providing a guide on using these tool. Always say thanks to me and them. And If possible, donate them. They really deserve it.
Thanks be to:
@jcadduono For Recowvery tool
Source thread [V20 originated]

Due to some issue YouTube video aren't being played directly on XDA. So, you need to watch it here (Maybe some resistance on XDA side because things are good on my blog)
https://www.youtube.com/watch?v=F5PdTW8QHcA&t
Video Tutorial:
<iframe allowfullscreen="" frameborder="0" height="270" src="https://www.youtube.com/embed/F5PdTW8QHcA" width="480"></iframe>
https://youtu.be/G_4ayiZbSkM<br />
<br />
<br />
<br />
<br />
<div class="separator" style="clear: both; text-align: center;">
<iframe width="320" height="266" class="YOUTUBE-iframe-video" data-thumbnail-src="https://i.ytimg.com/vi/G_4ayiZbSkM/0.jpg" src="https://www.youtube.com/embed/G_4ayiZbSkM?feature=player_embedded" frameborder="0" allowfullscreen></iframe></div>
<br />
[YOUTUBE]<object width="445" height="364"><param name="movie"
value="http://www.youtube.com/v/AK9aZyJJNIo&hl=en_US&fs=1&rel=0&color1=0x234900&color2=0x4e9e00&border=1"></param><param name="allowFullScreen" value="true"></param><param name="allowscriptaccess" value="always"></param><embed src="http://www.youtube.com/v/AK9aZyJJNIo&hl=en_US&fs=1&rel=0&color1=0x234900&color2=0x4e9e00&border=1" type="application/x-shockwave-flash" allowscriptaccess="always" allowfullscreen="true" width="445" height="364"></embed></object>[/YOUTUBE]

For which software version is this applicable?

arjunking said:
For which software version is this applicable?
Click to expand...
Click to collapse
Nougat v20a only as the thread title says.

I had to extract to a USB device to get recowvery to work but it went smoothly from there, until I got to TWRP to flash the no verity zip. It hung on hit any key to continue, it didn't dawn on me till later I should have mounted USB storage (derp), but I already had the no verity zip and SuperSU on my external SD so I just flashed them manually, booted, and had root. Then I formatted data, lost root, and flashed SuperSU again to get it back. I later flashed @autoprime 20c zip with SuperSU and now I'm rooted with TWRP on 20c, tyvm for the tutorial

Char_G said:
I had to extract to a USB device to get recowvery to work but it went smoothly from there, until I got to TWRP to flash the no verity zip. It hung on hit any key to continue, it didn't dawn on me till later I should have mounted USB storage (derp), but I already had the no verity zip and SuperSU on my external SD so I just flashed them manually, booted, and had root. Then I formatted data, lost root, and flashed SuperSU again to get it back. I later flashed @autoprime 20c zip with SuperSU and now I'm rooted with TWRP on 20c, tyvm for the tutorial
Click to expand...
Click to collapse
First of all you welcome, 2nd thanks for writing about your experience.
I am not completely assured but to make recowvery work in internal hard drive you need to change the name of recowvery folder to "1". Next time whenever you root try this method and let me know wether it worked...
And as you mentioned about having difficulty in flashing no verity. I think this issue is happening only on TWRP 3.1.0, on TWRP 3.0.1 it works fine, i think .

Does this method work with the latest update to 20f? Can I just try it without bricking my phone?
Sent from my LG-H830 using Tapatalk

dksoni411 said:
First of all you welcome, 2nd thanks for writing about your experience.
I am not completely assured but to make recowvery work in internal hard drive you need to change the name of recowvery folder to "1". Next time whenevee you root try this method and let me know wether it worked...
And as you mentioned about having difficulty in flashing no verity. I think this issue is happening only on TWRP 3.1.0, on TWRP 3.0.1 it works fine, i think .
Click to expand...
Click to collapse
Thanks, I'll try that next time. I did use TWRP 3.0.1 though, but I'm thinking that without mounting USB storage, perhaps the verity zip couldn't be found to be flashed.

This worked perfectly!! Thank you so much again! I had to extract the recowvery to a usb stick and run it from there (it wouldn't run properly from the computer hd) and at first I got an error as I had put the recovery.img on the external phone sd. My bad. Anyway... I just copied it over to the phone sd and started over, and it worked exactly as explained in the OP.
AWESOME effort by everyone involved. XDA rules!
Btw... can I relock the bootloader now? And one more thing... I turned off "automatic system updates" in developer mode. I assume if I update to v20c or newer I will lose root? And I guess I should not update the supersu either?
Thanks again! You rock!!

d3th.m0nk3y said:
This worked perfectly!! Thank you so much again! I had to extract the recowvery to a usb stick and run it from there (it wouldn't run properly from the computer hd) and at first I got an error as I had put the recovery.img on the external phone sd. My bad. Anyway... I just copied it over to the phone sd and started over, and it worked exactly as explained in the OP.
AWESOME effort by everyone involved. XDA rules!
Btw... can I relock the bootloader now? And one more thing... I turned off "automatic system updates" in developer mode. I assume if I update to v20c or newer I will lose root? And I guess I should not update the supersu either?
Thanks again! You rock!!
Click to expand...
Click to collapse
As you installed TWRP, so recovery partition is modified which means if you relock bootloader, you will brick your device.
Also if you want to use V20c check @autoprime's thread for the TWRP flashable zip of V20c or later (if there any).
And if you want to update supersu you can do it either by newest supersu zip to flash it through TWRP or by updating it through playstore then update binary through supersu it self, but I think updating supersu mostly changes nothing.

dksoni411 said:
As you installed TWRP, so recovery partition is modified which means if you relock bootloader, you will brick your device.
Also if you want to use V20c check @autoprime's thread for the TWRP flashable zip of V20c or later (if there any).
And if you want to update supersu you can do it either by newest supersu zip to flash it through TWRP or by updating it through playstore then update binary through supersu it self, but I think updating supersu mostly changes nothing.
Click to expand...
Click to collapse
Ok. Thanks for all the info. I think I will keep the v20a with the current supersu. It works perfectly! Hopefully it will not "automatically update between 23:00 and 04:00" as it says in "about phone/update center/system updates". From what I understand, it shouldn't as long as I have the "automatic system updates" set to OFF in developer options.
How can I boot into TWRP? When I reboot and try to enter TWRP I always end up in the hard reset menu where it asks if I want to wipe the phone... Do I have to boot into TWRP through ADB fastboot?

d3th.m0nk3y said:
Ok. Thanks for all the info. I think I will keep the v20a with the current supersu. It works perfectly! Hopefully it will not "automatically update between 23:00 and 04:00" as it says in "about phone/update center/system updates". From what I understand, it shouldn't as long as I have the "automatic system updates" set to OFF in developer options.
How can I boot into TWRP? When I reboot and try to enter TWRP I always end up in the hard reset menu where it asks if I want to wipe the phone... Do I have to boot into TWRP through ADB fastboot?
Click to expand...
Click to collapse
When you boot to recovery through hardware key combination, say yes through hardware keys twice (as you want to reset), it will take you to TWRP, thats the logic from lg g2

dksoni411 said:
When you boot to recovery through hardware key combination, say yes through hardware keys twice (as you want to reset), it will take you to TWRP, thats the logic from lg g2
Click to expand...
Click to collapse
He is absolutely correct. That's exactly what I did on my H830 yesterday.
Keep up the great work people......

Got it after a few attempts
Thanks for the step by step. It is a good walkthrough for a tough device. With all the previous complicated, and sometimes confusing/conflicting, instructions in other (older) threads for the H830 I was nervous to try.
I struggled a little getting it to work; 1) .cmd returned "don't have permission to create log or backup files..." when running from my "documents" directory, had to run it in a root folder. 2) I got the wrong TWRP version at first and the process said success, but never made it to TWRP.
It was the most challenging of any device I have owned to get root, but happy to crack it. Thanks!

root 20f?
does this root method work on 20f?

hp786 said:
does this root method work on 20f?
Click to expand...
Click to collapse
Well, it shouldn't. Because I tried this on 20c and it never worked, so I believe it will not work on any software other than 20a. But you can try your luck and tell me if you succeed.

Salam bro,I followed your method and rooted the phone,after rooting I wiped system, data and cache so I could flash fulmics 2(based on v20c) which I had already downloaded,it flashed successfully but after booting on startup screen there's this popup error"settings keep closing " because of which I can't do anything so can u please tell me where did I go wrong,should I have wiped the system or not?

[HOW-TO] HUAWEI NOVA-PLUS root with MAGISK

Yes,its working...
REMOVE ALL OTHER ROOT...working or not befor installing magisk....may end with....something you dont want...
Maybe it would be best to start with a freshly factory resetted phone.... (anyway,to erase all errors in TWRP,youll format/data so... )
you need bootloader unlock... followed instructions HERE don't forget to OEM UNLOCK in /settings/Developer section on phone..(enable it while pressing repeatedly on Phone version (in ''about phone also in settings)
You need MINIMAL ADB on pc...HERE
You need TWRP recovery installed...HERE
but before doing all that...BE SHURE to have the original UPDATE.APP (firmware from huawei) somewhere on your pc
you will need the BOOT.img from your original firmware... (extract it from the update.app (update.zip for huawei firmware)
HERE
extract the boot.img somewhere on your pc... like on your desktop...
then,youll need 2 magisk things...
the LATEST magisk ZIP file...
and the LATEST MAGISK APK...
FOLLOW THESE INSTRUCTIONS (from Magisk post...i did it and its working :silly: )
Installation Instructions
If you already have Magisk installed, you can directly upgrade through Magisk Manager
For installing Magisk the first time
Make sure to remove any other root, best to restore your boot image back to stock
Via custom recovery:
Download the latest Magisk zip file
Reboot to a custom recovery and flash the flashable zip
Via Magisk Manager (Only support v14.0+):
This method does not need root, and also does not require a custom recovery.
However, you MUST have a stock boot image dump beforehand, and also be able to flash the patched boot image, either through fastboot/download mode or ODIN
Install the latest Magisk Manager
If you're planning to flash the patched boot image through ODIN, go to Settings > Update Settings > Patched Boot Output Format, and select .img.tar. For normal users leave it as the default .img
Press Install > Install > Patch Boot Image File, and select your stock boot image file
Magisk Manager will now patch your boot image, and store it in [Internal Storage]/MagiskManager/patched_boot.img[.tar]
Flash the patched boot image to your device and reboot. Voilà!
Check whether Magisk Manager is installed and the version matches the latest one in the OP
If for some reason Magisk Manager isn't installed/upgraded automatically, please install it manually
the ADB method is the best...
after reboot,in magisk app,youre supposed to be GREEN checked....
after that,if all green,you can FIX that DATA problem in TWRP...saying cant mount or blablabla...
DO a backup cuz yess,youll loose everything... Hisuite for your apps
in twrp, FORMAT DATA... ...wipe data factory reset...re install your things then,youll be able to do recoverys ect. in twrp
dont forget to RE INSTALL magisk APK after formatting and factory reset
IT WILL take some time TO BOOT... so let it do its thing...
Now about magisk modules...all of them ive tried ended in (blablabla not a magisk module)...
no big deal....just dload the zip and look for the app or file in it... and apply to where it belongs... like new Oreo Emojis...ive dloaded the zip,found the file, then paste the file in /system/fonts...then reboot
now...if i made a mistake somewhere in my explanations well... sorry....
WARNING
IF youre device is bricked or what so ever... its not MY fault....you do that on your own......Ive done it,followed MAGISK instructions and its working....
Not shure about it...DONT DO IT....
DON'T DO TWRP backups with fingerprints/nip/code unlock methods activated on your phone... i had to factory reset phone cuz code was not working.
YES there's a way to recover anyway... THANKS HENKATE
Regarding fingerprint, boot in recovery and go to advanced > file manager and delete data/system/locksettings.db
Then advanced > terminal and type:
cd data/system
rm -rf *.key
Then reboot and you won't have secured lockscreen

MAGISK modules are HERE
Magisk MANAGER is available on PLAYSTORE

BEFORE making a twrp backup... (after data format ect.)...
you may want to FIX the huawei theme manager not working problem for some of us... the FIX is HERE
Thanks to Henkate
Youll need a good file system manager...i'm using ROOT EXPLORER and theres that new FX file explorer

does it work with android 7?

tanlikar1 said:
does it work with android 7?
Click to expand...
Click to collapse
Yes. In fact, this was meant for Android 7, but it should work on Android 6 too.

Absolutely...Im on Nougat emui5

does anyone have stock rom for MLA-L12C636B340 ?

Do you mean original firmware ?
Maybe you can still get it via firmware finder...

virusdunil said:
Do you mean original firmware ?
Maybe you can still get it via firmware finder...
Click to expand...
Click to collapse
ya

Working on Nova?
Does it work in the non plus Nova as well? Any experiences?

Worked on Can-L11. Tested. No need format data, in twrp tree, i add img, that work with encrypted data.

I can't get this to work on my MLA-03, i have TWRP installed and unlocked b/l. I tried to flash RR and Lineage but getting "can't mount" errors up the ying yang. Anyone with MLA-03 got any tips? Is there a certain recovery that is recommended?

Cooks_08 said:
I can't get this to work on my MLA-03, i have TWRP installed and unlocked b/l. I tried to flash RR and Lineage but getting "can't mount" errors up the ying yang. Anyone with MLA-03 got any tips? Is there a certain recovery that is recommended?
Click to expand...
Click to collapse
hi...yes and its a bit confusing...but,just follow instructions for LOS install...forget about /mount data and after flashing ,just reboot

virusdunil said:
hi...yes and its a bit confusing...but,just follow instructions for LOS install...forget about /mount data and after flashing ,just reboot
Click to expand...
Click to collapse
Got the flash working. Used Garak's Twrp and now i got. Thanks.

Does it work for android 8.0 or Huawei nova 2s in particular? I did make unlock the bootloader, but i could not find reliable root method. Please help with advice. Thank you.

Mezo21 said:
Does it work for android 8.0 or Huawei nova 2s in particular? I did make unlock the bootloader, but i could not find reliable root method. Please help with advice. Thank you.
Click to expand...
Click to collapse
Hi there,
I have Nova 2s, carefully follow this thread's instructions, it will 100% works : https://forum.xda-developers.com/ho...agisk-root-honor-view-10-mate-10-pro-t3749280

Thanks for the guidance, Magisk is doing very well.
Only TWRP is missing, but later.
Huawei Nova
CAN-L01C432B382

Magisk modules not working even if i rooted. Cant install modules from magisk app and twrp .zip

meskafonas said:
Magisk modules not working even if i rooted. Cant install modules from magisk app and twrp .zip
Click to expand...
Click to collapse
did you format data as f2fs? If yes, magisk doesn't go well along with it. If no, then you would get better support at magisk thread

virusdunil said:
Yes,its working...
REMOVE ALL OTHER ROOT...working or not befor installing magisk....may end with....something you dont want...
Maybe it would be best to start with a freshly factory resetted phone.... (anyway,to erase all errors in TWRP,youll format/data so... )
you need bootloader unlock... followed instructions HERE don't forget to OEM UNLOCK in /settings/Developer section on phone..(enable it while pressing repeatedly on Phone version (in ''about phone also in settings)
You need MINIMAL ADB on pc...HERE
You need TWRP recovery installed...HERE
but before doing all that...BE SHURE to have the original UPDATE.APP (firmware from huawei) somewhere on your pc
you will need the BOOT.img from your original firmware... (extract it from the update.app (update.zip for huawei firmware)
HERE
extract the boot.img somewhere on your pc... like on your desktop...
then,youll need 2 magisk things...
the LATEST magisk ZIP file...
and the LATEST MAGISK APK...
FOLLOW THESE INSTRUCTIONS (from Magisk post...i did it and its working :silly: )
Installation Instructions
If you already have Magisk installed, you can directly upgrade through Magisk Manager
For installing Magisk the first time
Make sure to remove any other root, best to restore your boot image back to stock
Via custom recovery:
Download the latest Magisk zip file
Reboot to a custom recovery and flash the flashable zip
Via Magisk Manager (Only support v14.0+):
This method does not need root, and also does not require a custom recovery.
However, you MUST have a stock boot image dump beforehand, and also be able to flash the patched boot image, either through fastboot/download mode or ODIN
Install the latest Magisk Manager
If you're planning to flash the patched boot image through ODIN, go to Settings > Update Settings > Patched Boot Output Format, and select .img.tar. For normal users leave it as the default .img
Press Install > Install > Patch Boot Image File, and select your stock boot image file
Magisk Manager will now patch your boot image, and store it in [Internal Storage]/MagiskManager/patched_boot.img[.tar]
Flash the patched boot image to your device and reboot. Voilà!
Check whether Magisk Manager is installed and the version matches the latest one in the OP
If for some reason Magisk Manager isn't installed/upgraded automatically, please install it manually
the ADB method is the best...
after reboot,in magisk app,youre supposed to be GREEN checked....
after that,if all green,you can FIX that DATA problem in TWRP...saying cant mount or blablabla...
DO a backup cuz yess,youll loose everything... Hisuite for your apps
in twrp, FORMAT DATA... ...wipe data factory reset...re install your things then,youll be able to do recoverys ect. in twrp
dont forget to RE INSTALL magisk APK after formatting and factory reset
IT WILL take some time TO BOOT... so let it do its thing...
Now about magisk modules...all of them ive tried ended in (blablabla not a magisk module)...
no big deal....just dload the zip and look for the app or file in it... and apply to where it belongs... like new Oreo Emojis...ive dloaded the zip,found the file, then paste the file in /system/fonts...then reboot
now...if i made a mistake somewhere in my explanations well... sorry....
WARNING
IF youre device is bricked or what so ever... its not MY fault....you do that on your own......Ive done it,followed MAGISK instructions and its working....
Not shure about it...DONT DO IT....
DON'T DO TWRP backups with fingerprints/nip/code unlock methods activated on your phone... i had to factory reset phone cuz code was not working.
YES there's a way to recover anyway... THANKS HENKATE
Regarding fingerprint, boot in recovery and go to advanced > file manager and delete data/system/locksettings.db
Then advanced > terminal and type:
cd data/system
rm -rf *.key
Then reboot and you won't have secured lockscreen
Click to expand...
Click to collapse
Do you have this problem with fingerprint? [emoji853] https://r.tapatalk.com/shareLink?ur...share_tid=3907398&share_fid=3793&share_type=t
Enviado desde mi HUAWEI CAN-L11 mediante Tapatalk

[FRP Lock] Need help to unbrick honor 7X (SOLVED)

Hi
After updating to EMUI 8.0 from this tutorial everything went well. Got Oreo working fine, so started to root with magisk = Ok; Xposed=Nok... Bootloop.
First - clean Data and Cache+Dalvik, still Bootloop
Entered to fastboot and tried to flash this file to rollback to 8.0, but...
I nottest that it said on the screen:
Bootloader UNLOCKED (in RED) and FRP Locked (In Green)
Confusing colors, cause it seems that i can't flash anything with unlocking the FRP... but i don´t have access the the system....
Also cant format System partition cause its read only, unable to flash other recovery files thought fastboot....
It s a f*cking MESS....
Can anyone please advice on this?
What can i do to recover this piece of sh*t??
Please........
Thank you, people
==============================
Well, got it figured out... But had to pay for it....
First of all:
{
"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"
}
You SUCK. Thanks for NOTHING
Lastly:
Thank YOU!!!
Long story short, i've solved it but have to pay for it.
Went to HUAWEI Service Center here in Portugal, and they told me that they couldn't do anything since the phone was not marketed for Europe (??????) [ASS Os]
I've discovered this service, and as with any other service online, i get suspicious for a while, asked a lot of questions and decided:
Bought a Month Pass for 50 EUD (45 Euros), and voila, in the first try unbricked the phone
Now i have the rest of the month to play with it...
Thanks for the people of FunkyHuawei for the kind attention (mostly pacience) they had with me.
I recommend it :good::good::good::good::good:

RSGI said:
Hi
After updating to EMUI 8.0 from this tutorial everything went well. Got Oreo working fine, so started to root with magisk = Ok; Xposed=Nok... Bootloop.
First - clean Data and Cache+Dalvik, still Bootloop
Entered to fastboot and tried to flash this file to rollback to 8.0, but...
I nottest that it said on the screen:
Bootloader UNLOCKED (in RED) and FRP Locked (In Green)
Confusing colors, cause it seems that i can't flash anything with unlocking the FRP... but i don´t have access the the system....
Also cant format System partition cause its read only, unable to flash other recovery files thought fastboot....
It s a f*cking MESS....
Can anyone please advice on this?
What can i do to recover this piece of sh*t??
Please........
Thank you, people
Click to expand...
Click to collapse
Do you still have access to twrp?
It could be only hope.
I had frp lock problem after unlocking bootloader. I had hit reset to default setting while inside developer options menu. That flipped the oem unlock switch.
I had to use twrp to flash back the stock boot.img and stock recovery.img then i was able to oem relock (my code).
And boot into room and reflip oem unlock toggle

thanks for replying
Not sure that i can access TWRP cause every time i force the recovery it appears the EMUI recovery (probably the NoCheck version that i used to update to Oreo)
Isn't it possible to reverte back to EMUI 5.1? Maybe with the 'dload' methode??
Is there any way to reset/unlock FRP from fastboot? I tried to relock bootloader with my own key but got an error (can't remember now what...)
I can't access the ROM itself...
This was because i installed Xposed....
If i could access TWRP again, perhaps i could delete the xposed files (in a recovery with the system as read-only)...
But i just dont know what to look for....
In older systems i knew that was the app_process file... Now i just dont know....
Thanks again for your reply!

help
download multi tool in pc and flash oreo beta via bootloader
i phase the same problem and it fixed my problem

RSGI said:
thanks for replying
Not sure that i can access TWRP cause every time i force the recovery it appears the EMUI recovery (probably the NoCheck version that i used to update to Oreo)
Isn't it possible to reverte back to EMUI 5.1? Maybe with the 'dload' methode??
Is there any way to reset/unlock FRP from fastboot? I tried to relock bootloader with my own key but got an error (can't remember now what...)
I can't access the ROM itself...
This was because i installed Xposed....
If i could access TWRP again, perhaps i could delete the xposed files (in a recovery with the system as read-only)...
But i just dont know what to look for....
In older systems i knew that was the app_process file... Now i just dont know....
Thanks again for your reply!
Click to expand...
Click to collapse
If you tried to install exposed from twrp, it should still be there

try dload method with emui 5 rom package, it may downgrade, no harm in trying.

Sudeep Duhoon said:
try dload method with emui 5 rom package, it may downgrade, no harm in trying.
Click to expand...
Click to collapse
Please can you explain that in detail?
Cause that might be the only way to save this (#"))&%&(/)&....
So, here is my situation:
- No TWRP access (recovery_ramdisk might be empty or damage... hopefully just empty)
- Bootloader Unlocked but FRP Locked
- eRecovery only presents 3 choices: Shutdown, Reboot and "Download latest version and recovery"*
- The System it self it's messed up after trying to install xposed.... just when its about to start, it reboots...
So.......
Still 3 ways that i can resolv this:
1 - the dload method (already tried, it updates until 5%, then error:" Install update failed" (Use the update.app file from the OTA, FullOTA, just the app file, all files in the update.zip... ) Not sure if i'm missing the right app file or if the eRecovery (maybe the NoCkeck version used to update initially) is screwed-up...
2 - Unlocking the FRP (Factory Reset Protection) this means that the "Allow OEM unlocking" is Off
Hopping to find a way to unlock it via fastboot
3 - The *Download latest version and recovery method allows to connect to wifi and download the firmware...
Not much sucess, but i know that i'm missing something (just dont know what it is...)
It seems that the router requires a certain configuration which i have no idea....
Suggestions are always welcome!
Thanks

RSGI said:
Please can you explain that in detail?
Cause that might be the only way to save this (#"))&%&(/)&....
So, here is my situation:
- No TWRP access (recovery_ramdisk might be empty or damage... hopefully just empty)
- Bootloader Unlocked but FRP Locked
- eRecovery only presents 3 choices: Shutdown, Reboot and "Download latest version and recovery"*
- The System it self it's messed up after trying to install xposed.... just when its about to start, it reboots...
So.......
Still 3 ways that i can resolv this:
1 - the dload method (already tried, it updates until 5%, then error:" Install update failed" (Use the update.app file from the OTA, FullOTA, just the app file, all files in the update.zip... ) Not sure if i'm missing the right app file or if the eRecovery (maybe the NoCkeck version used to update initially) is screwed-up...
2 - Unlocking the FRP (Factory Reset Protection) this means that the "Allow OEM unlocking" is Off
Hopping to find a way to unlock it via fastboot
3 - The *Download latest version and recovery method allows to connect to wifi and download the firmware...
Not much sucess, but i know that i'm missing something (just dont know what it is...)
It seems that the router requires a certain configuration which i have no idea....
Suggestions are always welcome!
Thanks
Click to expand...
Click to collapse
What I'm trying to understand , is how were you trying to install exposed.
I assume it was with twrp, no.

mrmazak said:
What I'm trying to understand , is how were you trying to install exposed.
I assume it was with twrp, no.
Click to expand...
Click to collapse
theres not much to understand there....
i flashed it with twrp and the phone never booted again...
yes, had access to the twrp for a while, but then, trying to run again the update process to flash the wrong recovery to recovery_ramdisk partition.... (another shot in the foot)
now i dont have twrp anymore and i'm unable to flash it cause th frp lock keeps telling thats not allowed...
the most clean way to solve this is to erase/unlock the FRP without accessing the ROM...
I'm already thinking about buy some credits with one of those online services that might unlock it...
Can you suggest to me some serious and honest services?
I'm desperate....

RSGI said:
theres not much to understand there....
i flashed it with twrp and the phone never booted again...
yes, had access to the twrp for a while, but then, trying to run again the update process to flash the wrong recovery to recovery_ramdisk partition.... (another shot in the foot)
now i dont have twrp anymore and i'm unable to flash it cause th frp lock keeps telling thats not allowed...
the most clean way to solve this is to erase/unlock the FRP without accessing the ROM...
I'm already thinking about buy some credits with one of those online services that might unlock it...
Can you suggest to me some serious and honest services?
I'm desperate....
Click to expand...
Click to collapse
Ok, I see
Didn't know you where 2 or 3 miss- steps past a failed exposed install.
I have no idea which service to recommend.

Hi,
Hope OP got his solution.
@matt4321
Honorable mod, I guess this thread belongs to Honor 7X Q&A forum. Please relocate.
Cheers

you cant downgrade from emui 8 you need to extract update.app of emui 8 an flash the ramdisk boot img so it will boot for that you need to download indian firmware mannual update given in other forum and extract the zip file update22 and data file extract both zip files and download the multi tool version 8 install all drivers boot your phone into bootloader now go to multi tool and click on unbreak and open huawie update extractor and extract update.app of data or update 22 make sure to check the mark on top emui 8 and when you click on update make sure to uncheck the verify the headder for that you go to settings in extracting update and follow the procedure of flashing for that you can google how to use multi tool i cant explain more i am not a developer but i phase the same problem and i got fixed hope i helped you

RSGI said:
Hi
After updating to EMUI 8.0 from this tutorial everything went well. Got Oreo working fine, so started to root with magisk = Ok; Xposed=Nok... Bootloop.
First - clean Data and Cache+Dalvik, still Bootloop
Entered to fastboot and tried to flash this file to rollback to 8.0, but...
I nottest that it said on the screen:
Bootloader UNLOCKED (in RED) and FRP Locked (In Green)
Confusing colors, cause it seems that i can't flash anything with unlocking the FRP... but i don´t have access the the system....
Also cant format System partition cause its read only, unable to flash other recovery files thought fastboot....
It s a f*cking MESS....
Can anyone please advice on this?
What can i do to recover this piece of sh*t??
Please........
Thank you, people
Click to expand...
Click to collapse
can't you install image from fastboot, if so try to flash rr or aosp system.img or extract from update.app

11122314 said:
download multi tool in pc and flash oreo beta via bootloader
i phase the same problem and it fixed my problem
Click to expand...
Click to collapse
Tried that but the only response that fastboot gives me is "Command not allowed" .
I just can´t flash anything in fastboot. I think i can thought adb shell dd (at least that how i manage to screw twrp partition), but i just can´t get ADB connection.
Just got fastboot connection with HiSuite drivers...
How can i get ADB access? It just installs an USB Storage Device...
Also i can try update via fastboot but it saying that it misses android-info.txt file.... whatever that means...
If i could boot once into the ROM, i would enable "Allow OEM Unlocking" and do exactly that.... btut i junt can´t... not yet...

11122314 said:
you cant downgrade from emui 8 you need to extract update.app of emui 8 an flash the ramdisk boot img so it will boot for that you need to download indian firmware mannual update given in other forum and extract the zip file update22 and data file extract both zip files and download the multi tool version 8 install all drivers boot your phone into bootloader now go to multi tool and click on unbreak and open huawie update extractor and extract update.app of data or update 22 make sure to check the mark on top emui 8 and when you click on update make sure to uncheck the verify the headder for that you go to settings in extracting update and follow the procedure of flashing for that you can google how to use multi tool i cant explain more i am not a developer but i phase the same problem and i got fixed hope i helped you
Click to expand...
Click to collapse
That was my plan... but even that is screwed-up.....
Here is my Recovery Status, without the possibility to flash any img via fastboot:
recovery_ramdisk (empty or in-error)
erecovery_ramdisk ( BND-RECOVERY-NoCheck.img flashed to update into EMUI 8.0)
With the software now, whats failling me is the ****ing recovery, that flash only 5% before it shows this error : "Install update failed!"
Dont have ADB support, maybe because i dont have the "USB Debbuging" option enable...
It seems that i will spend 15 euros to unlock this &%/())(/&%$######()/=?(/%&$#

Just thought I'd post here in case you are still in need. I believe that there are two different recovery modes - one that is triggered by holding power, up vol, and down vol, and another that is triggered by holding just power and up vol. Are you sure twrp is gone? I thought I had lost twrp when in fact it was in the other recovery.

RSGI said:
Please can you explain that in detail?
Cause that might be the only way to save this (#"))&%&(/)&....
So, here is my situation:
- No TWRP access (recovery_ramdisk might be empty or damage... hopefully just empty)
- Bootloader Unlocked but FRP Locked
- eRecovery only presents 3 choices: Shutdown, Reboot and "Download latest version and recovery"*
- The System it self it's messed up after trying to install xposed.... just when its about to start, it reboots...
So.......
Still 3 ways that i can resolv this:
1 - the dload method (already tried, it updates until 5%, then error:" Install update failed" (Use the update.app file from the OTA, FullOTA, just the app file, all files in the update.zip... ) Not sure if i'm missing the right app file or if the eRecovery (maybe the NoCkeck version used to update initially) is screwed-up...
2 - Unlocking the FRP (Factory Reset Protection) this means that the "Allow OEM unlocking" is Off
Hopping to find a way to unlock it via fastboot
3 - The *Download latest version and recovery method allows to connect to wifi and download the firmware...
Not much sucess, but i know that i'm missing something (just dont know what it is...)
It seems that the router requires a certain configuration which i have no idea....
Suggestions are always welcome!
Thanks
Click to expand...
Click to collapse
[BND-L22 / BND-AL10C675] Back to Stock / Unbrick your Honor 7X Indian Variants

Sudeep Duhoon said:
[BND-L22 / BND-AL10C675] Back to Stock / Unbrick your Honor 7X Indian Variants
Click to expand...
Click to collapse
Not even that i can do....
Let's update:
State
OS: Bootloop
System: No "recovery_ramdisk" partition (no stock / no twrp)
Bootloader: Unlocked
*FRP: Locked
So can't flash in fastboot, *Already got the unlock code for the FRP but without the "recovery_ramdisk" recovery the system wont reset....
(Weird!) No adb access in recovery mode (which would help A LOT....)
The dload method, whatever the update.app only updates until 5% , then error updating...
The eRecovery Wireless method might work, but i just dont know how to do it.
Tried with a usb pen inserted on the router with all the ROMs all together, in separated folders, whatever, no rom detected... there must be a way to do it right... i just dont know how...
Just need one of two things to happend:
Flash the stock recovery - still dont know how to do it...
Fix the bootloop and access the SO Rom - also, without adb access just dont know how...
Out of the box thinking required...
About UPDATE.APP
Can't we make a update.app much like o do it for zip files?
Would it be possible to make um UPDATE.APP just to flash/restore recovery partition?
The updates with zip files must also be inside a dload folder?
About Bootloop and SD Card
Is there a way, using the sd card, to stop the reboot, maybe enable the Safe Mode...
Something that would allowed me to access the Settings...
Any apk, any script that could be loaded from the SD card....
Not an easy plan... i know...
Maybe something very basic and easy is escaping me....

RSGI said:
Not even that i can do....
Let's update:
State
OS: Bootloop
System: No "recovery_ramdisk" partition (no stock / no twrp)
Bootloader: Unlocked
*FRP: Locked
So can't flash in fastboot, *Already got the unlock code for the FRP but without the "recovery_ramdisk" recovery the system wont reset....
(Weird!) No adb access in recovery mode (which would help A LOT....)
The dload method, whatever the update.app only updates until 5% , then error updating...
The eRecovery Wireless method might work, but i just dont know how to do it.
Tried with a usb pen inserted on the router with all the ROMs all together, in separated folders, whatever, no rom detected... there must be a way to do it right... i just dont know how...
Just need one of two things to happend:
Flash the stock recovery - still dont know how to do it...
Fix the bootloop and access the SO Rom - also, without adb access just dont know how...
Out of the box thinking required...
About UPDATE.APP
Can't we make a update.app much like o do it for zip files?
Would it be possible to make um UPDATE.APP just to flash/restore recovery partition?
The updates with zip files must also be inside a dload folder?
About Bootloop and SD Card
Is there a way, using the sd card, to stop the reboot, maybe enable the Safe Mode...
Something that would allowed me to access the Settings...
Any apk, any script that could be loaded from the SD card....
Not an easy plan... i know...
Maybe something very basic and easy is escaping me....
Click to expand...
Click to collapse
I just read through the fastboot partition from my backup using "strings" to find the available "oem" commands.
I think i found possible solution for you.
careful useing these commands as I do not know for sure if they work and what they do.
Code:
fastboot oem frp-unlock
also not sure about the dashes or underscores.

mrmazak said:
I just read through the fastboot partition from my backup using "strings" to find the available "oem" commands.
I think i found possible solution for you.
careful useing these commands as I do not know for sure if they work and what they do.
Code:
fastboot oem frp-unlock
also not sure about the dashes or underscores.
Click to expand...
Click to collapse
Hi
Thank you for replying.
Already tried that.... Actually the command should be:
Code:
fastboot oem frp-unlock (unlock frp key)
Bought the unlock code from an online unlock store.
Spent 10 euros. The code is correct cause i got the message that the device will reboot and do a factory reset.
Than it reboots into an error screen, cause i screwed up the "recovery_ramdisk" partition earlier and its not working now. So, no factory reset, no changing the Frp status... Still locked.
Still no flashing img files from recovery... Still got the reply oficial Command Not Allowed...
But:
I'm trying to gain adb access while on eRecovery.
Than i could try to flash the stock recovery with the code dd command. From there i would unlock the Frp with the code and the Factory Reset might be enought to fix the bootloop.
Also the bootloop it self...
I wonder if there's a way to force the boot even with FC errors....
Access to the ROM software would allow me to flash the stock recovery and then make a factory reset, by changing the OEM Unlocking status
Thanks for your reply, maybe you can give me some tips on this 2 ways that i'm exploring right now.
Or some other ways that i haven't consider yet... please....
:cyclops::cyclops:

ERROR MODE Attention! Please update system again.

Hi
I have a problem with my Honor 7X L21.
Because online update dose not work for this model I decided to updated my smartphone offline.
I downloaded Oreo update file
Unlock my phone
install twrp
update phone
every thing is going well until here
then I decided to root my phone but I saw there is no twrp on my phone
I search and I found a thread here that show how install twrp with adb use recovery ramdisk.
I install twrp on recovery ramdisk and try to root my phone. its OK but when my phone want to start its stuck on google page "just a sec..."
I boot my device on twrp and I did factory reset but the problem was still exist.
then I decided to flash update again.
I copy update file on SD card and wright code on twrp
but at the end when I reboot the recovery, twrp except stock recovery came up and my stock recovery was gone.
I reboot the system but Its loop on this page that says:
ERROR MODE
Attention!
Please update system again.
Error!
Func NO : 11 (recovery image)
Error NO : 2 (load failed!)
Please help me!!!
I try to install stock recovery and twrp with adb and huawei multi tools but it didn't work.
it shows:
"FAILED (remote: partition length get error)"
I try to unbrick my phone too but it shows same message that "FAILED (remote: partition length get error)"
Helllllp lpeaeaeaeaeaseeee!!!

Mohammadreza76646 said:
Hi
I have a problem with my Honor 7X L21.
Because online update dose not work for this model I decided to updated my smartphone offline.
I downloaded Oreo update file
Unlock my phone
install twrp
update phone
every thing is going well until here
then I decided to root my phone but I saw there is no twrp on my phone
I search and I found a thread here that show how install twrp with adb use recovery ramdisk.
I install twrp on recovery ramdisk and try to root my phone. its OK but when my phone want to start its stuck on google page "just a sec..."
I boot my device on twrp and I did factory reset but the problem was still exist.
then I decided to flash update again.
I copy update file on SD card and wright code on twrp
but at the end when I reboot the recovery, twrp except stock recovery came up and my stock recovery was gone.
I reboot the system but Its loop on this page that says:
ERROR MODE
Attention!
Please update system again.
Error!
Func NO : 11 (recovery image)
Error NO : 2 (load failed!)
Please help me!!!
I try to install stock recovery and twrp with adb and huawei multi tools but it didn't work.
it shows:
"FAILED (remote: partition length get error)"
I try to unbrick my phone too but it shows same message that "FAILED (remote: partition length get error)"
Helllllp lpeaeaeaeaeaseeee!!!
Click to expand...
Click to collapse
Doing the update second time is fine, and best way to restore full stock. But you needed to use Oreo version of no-check recovery and the Oreo partition to flash it to.
So if still able to get into twrp, can try with correct no-check recovery and correct partition it's flashed to.
Also
With multi tool , make sure you put check mark on emui 8. Up in upper right corner. That way it uses Oreo partition names and file not nougat.
The partition length over message usually means nougat file or partition name used on Oreo system

mrmazak said:
Doing the update second time is fine, and best way to restore full stock. But you needed to use Oreo version of no-check recovery and the Oreo partition to flash it to.
So if still able to get into twrp, can try with correct no-check recovery and correct partition it's flashed to.
Also
With multi tool , make sure you put check mark on emui 8. Up in upper right corner. That way it uses Oreo partition names and file not nougat.
The partition length over message usually means nougat file or partition name used on Oreo system
Click to expand...
Click to collapse
Thank you for your answer.
But I try to extract update.app (oreo version) but its failed! huawei update extractor cant open it and 7zip cant extract it with (unexpected error...)!
And unfortunately my TWRP dos not work anymore

Mohammadreza76646 said:
Thank you for your answer.
But I try to extract update.app (oreo version) but its failed! huawei update extractor cant open it and 7zip cant extract it with (unexpected error...)!
And unfortunately my TWRP dos not work anymore
Click to expand...
Click to collapse
I give my phone to a friend to work on it. If he can't fix it I try new multi tools version to flash phone.

Mohammadreza76646 said:
Thank you for your answer.
But I try to extract update.app (oreo version) but its failed! huawei update extractor cant open it and 7zip cant extract it with (unexpected error...)!
And unfortunately my TWRP dos not work anymore
Click to expand...
Click to collapse
On the extractor app. On options tab uncheck the verify header option, it should extract then.
Then perhaps first do these three partitions.
Kernel.img
Ramdisk.img
Then
twrp_ramdisk or for stock use recovery_ramdisk

Mohammadreza76646 said:
Hi
I have a problem with my Honor 7X L21.
Because online update dose not work for this model I decided to updated my smartphone offline.
I downloaded Oreo update file
Unlock my phone
install twrp
update phone
every thing is going well until here
then I decided to root my phone but I saw there is no twrp on my phone
I search and I found a thread here that show how install twrp with adb use recovery ramdisk.
I install twrp on recovery ramdisk and try to root my phone. its OK but when my phone want to start its stuck on google page "just a sec..."
I boot my device on twrp and I did factory reset but the problem was still exist.
then I decided to flash update again.
I copy update file on SD card and wright code on twrp
but at the end when I reboot the recovery, twrp except stock recovery came up and my stock recovery was gone.
I reboot the system but Its loop on this page that says:
ERROR MODE
Attention!
Please update system again.
Error!
Func NO : 11 (recovery image)
Error NO : 2 (load failed!)
Please help me!!!
I try to install stock recovery and twrp with adb and huawei multi tools but it didn't work.
it shows:
"FAILED (remote: partition length get error)"
I try to unbrick my phone too but it shows same message that "FAILED (remote: partition length get error)"
Helllllp lpeaeaeaeaeaseeee!!!
Click to expand...
Click to collapse
I ever have similiar problem with you dude, but it's solved now, if you always stuck on " its OK but when my phone want to start its stuck on google page "just a sec...", its call google accont verification, i'll by bypass with this script, save as to .bat and put on adb folder
adb devices
adb shell content insert --uri content://settings/secure --bind name:s:user_setup_complete --bind value:s:1
adb shell am start -n com.google.android.gsf.login/
adb shell am start -n com.google.android.gsf.login.LoginActivity
pause
in fastboot type:
fastboot -w
after all it's works to me to bypass google account verification
and if now your problem is
ERROR MODE
Attention!
Please update system again.
Error!
Func NO : 11 (recovery image)
Error NO : 2 (load failed!)
i solve with re-flash system from this
https://androidfilehost.com/?fid=673956719939830152
fastboot flash system system.img
and doing TWRP Flashing
https://forum.xda-developers.com/devdb/project/?id=25826#downloads
fastboot flash recovery_ramdisk complete_twrp_ramdisk.img
and voila my problem solved..

mrmazak said:
On the extractor app. On options tab uncheck the verify header option, it should extract then.
Then perhaps first do these three partitions.
Kernel.img
Ramdisk.img
Then
twrp_ramdisk or for stock use recovery_ramdisk
Click to expand...
Click to collapse
Hello again dude.
Finally I flashed my phone and I got the system installed.
But now my phones IMEI is lost. and I cant put sim on it!!!
what should I do now???
FRP is locked! (

Mohammadreza76646 said:
Hello again dude.
Finally I flashed my phone and I got the system installed.
But now my phones IMEI is lost. and I cant put sim on it!!!
what should I do now???
FRP is locked! (
Click to expand...
Click to collapse
So now is locked frp. Does phone have twrp or stock now.?
I think when you tried to install the oreo update for second time, you followed same tutorial as the first time. And that made you problem worse. The tutorial has you flash no-check recovery to 2 partition by block number. 22 & 29. On nougat that is "recovery" and "recovery2". On Oreo partion table it is "reserved2" & "erecovery_vendor"
I don't know how to fix imei. Have hope that if to ucan have a full ota install , maybe can be fixed.
There is available a "service rom" (used to fix most all problem) for Europe region with l21.
I can share link to site with service rom if you want , but I have not used it myself so not gonna be much help with it.
Link is to rusian language page. Google should translate for you.
https://4pda.ru/forum/index.php?showtopic=879524&view=findpost&p=73818595

mrmazak said:
So now is locked frp. Does phone have twrp or stock now.?
I think when you tried to install the oreo update for second time, you followed same tutorial as the first time. And that made you problem worse. The tutorial has you flash no-check recovery to 2 partition by block number. 22 & 29. On nougat that is "recovery" and "recovery2". On Oreo partion table it is "reserved2" & "erecovery_vendor"
I don't know how to fix imei. Have hope that if to ucan have a full ota install , maybe can be fixed.
There is available a "service rom" (used to fix most all problem) for Europe region with l21.
I can share link to site with service rom if you want , but I have not used it myself so not gonna be much help with it.
Link is to rusian language page. Google should translate for you.
https://4pda.ru/forum/index.php?showtopic=879524&view=findpost&p=73818595
Click to expand...
Click to collapse
It have stock recovery.

Mohammadreza76646 said:
It have stock recovery.
Click to expand...
Click to collapse
in summery. because i have been going back and forth in multiple different groups, multiple problem, i cant remember it all.
you have broken system, from failed root attempt, followed by failed update.
device condition is as follows.
--system not booting
--stock recovery loads
--fastboot/bootloader loads, but is in frp lock status
options are limited, at best.
I think "dload" method with service rom is best.
other option is maybe paid service like dc-unlock. But I can recall some note on there service about frp-unlock, that can only be used on device with working system. (of course if was working system, wouldn't need dc-unlock)

mrmazak said:
in summery. because i have been going back and forth in multiple different groups, multiple problem, i cant remember it all.
you have broken system, from failed root attempt, followed by failed update.
device condition is as follows.
--system not booting
--stock recovery loads
--fastboot/bootloader loads, but is in frp lock status
options are limited, at best.
I think "dload" method with service rom is best.
other option is maybe paid service like dc-unlock. But I can recall some note on there service about frp-unlock, that can only be used on device with working system. (of course if was working system, wouldn't need dc-unlock)
Click to expand...
Click to collapse
No. System boot successfully!
I will send you screenshot:

Mohammadreza76646 said:
No. System boot successfully!
I will send you screenshot:
Click to expand...
Click to collapse
here you are

Mohammadreza76646 said:
here you are
Click to expand...
Click to collapse
what about the "about phone" screen
what does it show for version?
If is all stock you should be able to go into deveolper options and enable "oem unlock". If it is greyed out and cannot switch it. Try First to remove google account (all accounts ). and reboot. See if can change then. If not, try Second to do "fastboot oem relock [enter your bootloader code here]
after relock and rebooted oem switch should be enabled again.
****RELOCK IS ONLY ADVISED IF 100% STOCK ROM****
otherwise relock could make more trouble.
Still not sure how to get IMEI back even if unlocked frp though.
**And please stop posting in other threads , the same problem , because you are getting help here.
your post in recovery thread is off topic to that thread and just makes the forum harder to maintain.

mrmazak said:
what about the "about phone" screen
what does it show for version?
If is all stock you should be able to go into deveolper options and enable "oem unlock". If it is greyed out and cannot switch it. Try First to remove google account (all accounts ). and reboot. See if can change then. If not, try Second to do "fastboot oem relock [enter your bootloader code here]
after relock and rebooted oem switch should be enabled again.
****RELOCK IS ONLY ADVISED IF 100% STOCK ROM****
otherwise relock could make more trouble.
Still not sure how to get IMEI back even if unlocked frp though.
**And please stop posting in other threads , the same problem , because you are getting help here.
your post in recovery thread is off topic to that thread and just makes the forum harder to maintain.
Click to expand...
Click to collapse
Thanks )
I'm so sorry for my posts, it's because I don't have a stable connection and I can't see notification of my thread.
I gave my phone to friend an he fix IMEI (I don't know how)
But OEM is steel lock.
I think he did it with using special box.

Mohammadreza76646 said:
Hi
I have a problem with my Honor 7X L21.
Because online update dose not work for this model I decided to updated my smartphone offline.
I downloaded Oreo update file
Unlock my phone
install twrp
update phone
every thing is going well until here
then I decided to root my phone but I saw there is no twrp on my phone
I search and I found a thread here that show how install twrp with adb use recovery ramdisk.
I install twrp on recovery ramdisk and try to root my phone. its OK but when my phone want to start its stuck on google page "just a sec..."
I boot my device on twrp and I did factory reset but the problem was still exist.
then I decided to flash update again.
I copy update file on SD card and wright code on twrp
but at the end when I reboot the recovery, twrp except stock recovery came up and my stock recovery was gone.
I reboot the system but Its loop on this page that says:
ERROR MODE
Attention!
Please update system again.
Error!
Func NO : 11 (recovery image)
Error NO : 2 (load failed!)
Please help me!!!
I try to install stock recovery and twrp with adb and huawei multi tools but it didn't work.
it shows:
"FAILED (remote: partition length get error)"
I try to unbrick my phone too but it shows same message that "FAILED (remote: partition length get error)"
Helllllp lpeaeaeaeaeaseeee!!![/QUOTE
Are u able.to boot into twrp ?
Click to expand...
Click to collapse

Hello I have a Huawei Mate-SE (with bootloader unlocked and rooted with magisk v16). I have been using the android custom rom RRO v6 (RR-O-v6.0.0-20180401-bnd-OpenKirin) for around a month now. I got this exact same problem about the White Screen saying "ERROR MODE Attention...." since I updated the Magisk to latest version (from the installed application) and rebooted my phone. SInce I rebooted I am getting that same error which makes the phone loops into it for a few times and then it loads the Huawei eRecovery that offers me some options that I am not sure what would do to my phone.
I have been trying to connect to adb tools/fastboot but it doesn't detect the phone and im pretty sure I have the device drivers installed on my computer since nothing have changed in my pc for a month now since I flashed RRO on it.
Is there any other mode besides recovery that would allow me to connect adb/fastboot to it? Or does anyone knows how should I proceed?

IonDEfeso said:
Hello I have a Huawei Mate-SE (with bootloader unlocked and rooted with magisk v16). I have been using the android custom rom RRO v6 (RR-O-v6.0.0-20180401-bnd-OpenKirin) for around a month now. I got this exact same problem about the White Screen saying "ERROR MODE Attention...." since I updated the Magisk to latest version (from the installed application) and rebooted my phone. SInce I rebooted I am getting that same error which makes the phone loops into it for a few times and then it loads the Huawei eRecovery that offers me some options that I am not sure what would do to my phone.
I have been trying to connect to adb tools/fastboot but it doesn't detect the phone and im pretty sure I have the device drivers installed on my computer since nothing have changed in my pc for a month now since I flashed RRO on it.
Is there any other mode besides recovery that would allow me to connect adb/fastboot to it? Or does anyone knows how should I proceed?
Click to expand...
Click to collapse
I have seen where the magisk update screwed up and patches the kernel intead of the ramdisk.
Power off , long press power button.
Hold volume down and plug in USB from PC.
This should cause it to boot into fastboot mode.
Then flash the stock kernel. And the stock or first patched ramdisk. (From earlier root)

mrmazak said:
I have seen where the magisk update screwed up and patches the kernel intead of the ramdisk.
Power off , long press power button.
Hold volume down and plug in USB from PC.
This should cause it to boot into fastboot mode.
Then flash the stock kernel. And the stock or first patched ramdisk. (From earlier root)
Click to expand...
Click to collapse
Hi thank you I was able to finally detect the device now. I am unsure about the kernel is that the recovery.img or system.img files I downloaded (i saved every file i used when I installed the rom) or do I need to look for the kernel somewhere else? I do have the complete_twrp_ramdisk.img file though.
Edit, I did more research and found the stock kernel is withing the boot.img file which I dont have so I looked up for the official BND-L34 oreo update and im currently downloading to extract the stock boot.img from the update.zip and flash it. Since that download was going to take me a while anyway i tried flashing the twrp recovery file without success (didn't changed anything) so i guess I should follow the instructions you gave me by flashing the kernel first then the twrp recovery.

mrmazak said:
I have seen where the magisk update screwed up and patches the kernel intead of the ramdisk.
Power off , long press power button.
Hold volume down and plug in USB from PC.
This should cause it to boot into fastboot mode.
Then flash the stock kernel. And the stock or first patched ramdisk. (From earlier root)
Click to expand...
Click to collapse
Do you know what the boot.img files name is after extraction?
I have extracted all 3 update zips and cannot find anything called boot.img
By the way, thank you.. After updating magisk I have been dealing with failed recovery and failed boot for over a week and this is the first reply anywhere that looks promising

IonDEfeso said:
Hi thank you I was able to finally detect the device now. I am unsure about the kernel is that the recovery.img or system.img files I downloaded (i saved every file i used when I installed the rom) or do I need to look for the kernel somewhere else? I do have the complete_twrp_ramdisk.img file though.
Edit, I did more research and found the stock kernel is withing the boot.img file which I dont have so I looked up for the official BND-L34 oreo update and im currently downloading to extract the stock boot.img from the update.zip and flash it. Since that download was going to take me a while anyway i tried flashing the twrp recovery file without success (didn't changed anything) so i guess I should follow the instructions you gave me by flashing the kernel first then the twrp recovery.
Click to expand...
Click to collapse
if you were on oreo. then there is not a boot.img, instaed there is seperate ramdisk.img and kernel.img.
i have all the files already extracted for oreo and a backup from nougat as well.
https://androidfilehost.com/?w=files&flid=265998
make sure you know what you are doing before flashing.
for example. on oreo the boot and recovery share one kernel image. SO if kernel is messed up you will not be able to boot "boot" or "recovery"

Update BLN-L22C675 from EMUI 5.X.X to EMUI 8.0 (with VOLTE)- Noob Friendly

Hi Guys,
Note- if you are on BLN-L22C675 Nougat you can do this easily but if you are on other variants, you need to debrand first as per this guide- https://forum.xda-developers.com/honor-6x/how-to/guide-debranding-to-india-variant-bln-t3679402
Some background-
So what I heard earlier that post China Oreo beta, other regions may not get it (via various unofficial channels and on XDA) its finally here, even though via firmware finder but it gives us a glimpse that beta or stable would be coming soon.
I had given my Honor 6X to my brother 6 months back and was using V10 since then but he came yesterday and I tried to enable VOLTE on that phone but was not working. Even though I debranded my Honor 6X from AL10 to BLN-L22 Indian version very easily (guide in my signature) but somehow I was not able to get VOLTE working. Yesterday I tried all the known methods till 2.30 AM My time but VOLTE was not working and I gave up but today morning again I tried and updated my phone to EMUI 8.0 (already kept one phone for my brother so that if something goes wrong, I will give a new one to him so that he can use atleast as he is leaving today)
As VOLTE was not working and I decided to update to Android 8.0 Indian version, I saw a screenshot in my Honor 6X Oreo update discussion thread and downloaded and flashed via HuRUpdater but failed last night and I recovered back to B340 and then updated to B365.
Click to expand...
Click to collapse
In this guide, I will provide detailed instruction on how to update your Nougat BLN-L22C675 Indian version of Honor 6X to Oreo. Process is simple and you just need patience while updating and post updating I verified, Jio, Vodafone VOLTE working (seems iDEA would work but no 4G in Delhi/NCR).
Prerequisites-
Unlocked bootloader.
HiSuite backup/TWRP backup.
Downloads-
TWRP for BLN - https://mega.nz/#!bY9hRazT!I9kqA3a9i1tAc3tQSnDGpqMPc_cEKR4JAYe6rDQqvdE
All the Oreo files (downloaded from Firmware finder or below URLs)- you need to put your device as BLN-L22HNC675 and it will show these files under B510 firmware version.
Main zip- http://update.hicloud.com:8180/TDS/data/files/p3/s15/G3196/g1699/v154301/f1/full/update.zip
Data File- http://update.hicloud.com:8180/TDS/...channel_in/update_full_BLN-L22_channel_in.zip
Public Zip- http://update.hicloud.com:8180/TDS/...01/f1/full/public/update_data_full_public.zip
HwOTA zip from https://mega.nz/#!CXRnEaAb!XYodFoS9CDqJkHx0Uv2fdFmzycCvTrexcvYzrwnjfGI given in thread Thanks to @vovan1982
If you have not unlocked your your bootloader, please do so. You can refer this guide if not aware of the method-
Unlocking the bootloader-
Backup all your data as unlocking the bootloader will reset the device and all your data will be erased.
On windows machine, go to folder C:\adb or wherever you installed the adb drivers.
Press shift+right click together and select Open command prompt here (it will be open PowerShell here on Windows 8 and Windows 10 machine)
Run - adb reboot bootloader (this command may prompt for acceptance of RSA key if not already accepted)
This will boot the phone into bootloader mode.
Run - fastboot oem unlock <16 digit unlock code- Put your actual code you obtained from Huawei site > (This step will unlock the bootloader and will erase all your data)
Phone will restart automatically.
Installing TWRP
Once on the system, open the PowerShell or command prompt again in ADB folder (can use the previous instance as well)
Run -
Code:
adb reboot bootloader
Once in bootloader, Run
Code:
fastboot flash recovery twrp-3.1.1-0-berlin.img
(This will install the TWRP recovery for EMUI 5.0 on your phone)
Once done with the flashing the TWRP, Run
Code:
fastboot reboot
Actual Oreo update procedure
Once you have unlocked the bootloader, and installed TWRP recovery via command
Download the Oreo firmware given above in download link.
Download the HWOTA_BLN_Eng.zip from the link given above.
Unzip the HWOTA_BLN_Eng.zip file and move the extracted content (HWOTA_BLN_Eng folder) to adb folder of your PC.
Copy the downloaded Oreo firmware to C:\adb\HWOTA_BLN_Eng\HWOTA8_BLN\update\ folder.
Rename update_data_full_public.zip file to update_data_public.zip and update_full_BLN-L22_channel_in.zip to update_all_hw.zip, do not rename the update.zip.
{
"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"
}
Boot to bootloader or fastboot mode. Keep your phone connected with PC.
Go to C:\adb\HWOTA_BLN_Eng\HWOTA8_BLN folder and run the update_eng.bat file and follow the on screen instructions.
The update_eng.bat will install the TWRP recovery and boot to TWRP (if not, you can remove USB and press power and volume up key and it will boot to TWRP, connect the USB again)
You will get prompt for update via SD card or script, select via script
You will get prompt for change region or change firmware, select change firmware.
It will automatically copy the content of C:\adb\HWOTA_BLN_Eng\HWOTA8_BLN\update, mainly those 3 zips and it will flash automatically.
You may see the update.zip file flashed as successful with no error but may see Error result [] for other 2 zips, dont worry that is expected.
Once flashed, it will automatically boot to Oreo without any issue and also it will ask if you want to relock your bootloader or keep this unlocked, this is your wish, I kept it unlocked and will be locked in future updates.
Your Nougat data may remain the same as it was in my case but I would advise to go with Hisuite backup and TWRP backup.
If phone unable to boot, flash the stock recovery and make factory reset and boot normally, it should boot fine. (haven't encountered this issue though)
I did factory reset after booting and verifying to system. Everything was working fine but still I did just to avoid any issue or lag (even though no lags were seen)
About Phone info and VOLTE for Jio and Vodafone. iDEA VOLTE would work as well but there is no 4G in NCR.
Enjoy Oreo.
Update- anyone having issues with call recorder, turn off Google voice typing and recording will work fine.

Changelog for - BLN-L22HN 8.0.0.510(C675CUSTC675D1)
Code:
[PHP][PHP]ANDROID 8.0[Oreo] upgrade with EMUI 8.0 is available for your device. This will upgrade your system BLN-L22HN 8.0.0.510(C675CUSTC675D1).
● VOLTE calls enabled for Vodafone,Idea and JIO.
● Call Recording feature has been added, and it has an ability to Records all your phone calls.
● EMUI 8.0 not only brings you the latest version of Android (8.0), it's also boosted with a lot of great features and improvements to make your device more intuitive, faster and safer. We highly recommend updating now.
● A new floating Navigation dock lets you perform frequently-used operations from anywhere on the screen. Newly added home screen shortcuts let you quickly access the app features you use most frequently. Simply touch and hold an app icon to display a shortcut menu.
● You can drag your navigation to any where of screen once you enabled this brand-new feature.
● How to set:Go to Setting > System > System navigation > Navigation dock Or drop down status bar > Navigation dock.
● Long-tap on parts of apps launcher icons, a shortcut menu will display.
● You can Tap and drag a shortcut to pin it to the device's launcher.
● Play Store, Settings, Gallery, Dialler, Contacts, Messaging, Camera, Email, Themes, Clock, Calendar, Notepad, Sound Recorder, Downloads etc. support the feature.
● Improved false touch protection functionality reduces unintended operations on the touch screen in a wider range of scenarios.
● Smart tips recommend you faster and smarter ways to operate your phone, appearing in specific usage scenarios and responding to your usage habits.
● Contacts and Email now let you sync the career details of your LinkedIn contacts.
● Settings has been redesigned for clearer and more intuitive organization.
● Gallery new features a recycle bin that retains deleted photos for up to 30 days. Accidentally deleted photos can be restored with a single touch.
● Phone Manager has been simplified to make managing your device easier. Standard cleanups are faster and deep cleanups more thorough.
● Google security patches are merged to make your device more secure.
● Downloading over WiFi is recommended. and make sure that the remaining power is greater than 50%.
● This update will not erase your personal data, but it's recommended to backup all of your personal data, including phone book, text messages, emails etc. before updating.
● Some third-party apps that are not compatible with Android 8.0 may function incorrectly after the update. It is recommended that you update these apps to their latest versions in the Google Play Store.
● Before upgrading, please ensure there is sufficient storage space for the update package on either the microSD card or the internal storage prior to proceeding with the update. Free storage space can be checked under system settings -> storage.
● During downloading upgrade package, the operation of the device will not be impacted. Please note, upgrade procedure need have some minutes to let device reboot and flashing. During flashing, the device is not available to be used.
● If you encounter any problems during the update, please contact the customer service hotline or visit an authorized Huawei service center for assistance which you can find.
● Your home screen layout may be rearranged slightly.
● This system version can be rolled back to the official version of EMUI 5.0 in Phone Manager. Rolling back the system version will erase your personal data. For more information, please contact the customer service hotline.

Stock Boot file for BLN-L22C675 OREO.

Bro which oreo recovery that support mtp and access to OTG

rojanjoy01 said:
Bro which oreo recovery that support mtp and access to OTG
Click to expand...
Click to collapse
did you mean during TWRP or in general. Mine supports OTG by default all the time.

Which TWRP ar you using on oreo ?

sreekantt said:
Which TWRP ar you using on oreo ?
Click to expand...
Click to collapse
None. I flashed without it. same as given in guide. you may use this post update-
https://mega.nz/#!a81EDZAR!2-9yPFh3reghkGcfSl3nRIJhHGkP8fqDsgUG66ewjkk

amazing work Shashank...

shashank1320 said:
None. I flashed without it. same as given in guide. you may use this post update-
https://mega.nz/#!a81EDZAR!2-9yPFh3reghkGcfSl3nRIJhHGkP8fqDsgUG66ewjkk
Click to expand...
Click to collapse
Internal storage shows as 0Mb. If I format data, Rom won't boot. I had to flash back stock recovery to factory reset and make it boot.
Flashing TWRP again shows 0Mb. Looks like a decryption issue.

sreekantt said:
Internal storage shows as 0Mb. If I format data, Rom won't boot. I had to flash back stock recovery to factory reset and make it boot.
Flashing TWRP again shows 0Mb. Looks like a decryption issue.
Click to expand...
Click to collapse
May be TWRP is not compatible with Oreo yet. Have seen similar issues on V10. BTW given back the phone to bro and he left for Mumbai so I couldnt test and explore much but somehow I updated his phone to Oreo and then got VOLTE working as was struggling since long and even yesterday for around 8-10 hours.
Which stock recovery you used (extracted from update.zip or else)?

shashank1320 said:
did you mean during TWRP or in general. Mine supports OTG by default all the time.
Click to expand...
Click to collapse
which twrp u use ,plz give the link
bro viper4fx not working on oreo emui 8,plz help me for solving this

rojanjoy01 said:
which twrp u use ,plz give the link
bro viper4fx not working on oreo emui 8,plz help me for solving this
Click to expand...
Click to collapse
hwota will take care of twrp if you want twrp for oreo then flash twrp from elemental rom on development section.
don't flash viper or dolbyatmos they will corrupt system files and you have to install stock again via hwota8

rojanjoy01 said:
which twrp u use ,plz give the link
bro viper4fx not working on oreo emui 8,plz help me for solving this
Click to expand...
Click to collapse
These will evolve with time. we just got Oreo. may be some developer can port these. for TWRP, Ramesh answered your query above. I have not flash any TWRP or stock recovery. HWOTA Will do the needful and install TWRP during the process and flash the update.zips one by one without issue. Once all done, your phone will boot and you will have stock recovery.

Ramesh006 said:
hwota will take care of twrp if you want twrp for oreo then flash twrp from elemental rom on development section.
don't flash viper or dolbyatmos they will corrupt system files and you have to install stock again via hwota8
Click to expand...
Click to collapse
bro now i use elemental twrp which will not support mtp and tpg
---------- Post added at 02:12 PM ---------- Previous post was at 02:12 PM ----------
Ramesh006 said:
hwota will take care of twrp if you want twrp for oreo then flash twrp from elemental rom on development section.
don't flash viper or dolbyatmos they will corrupt system files and you have to install stock again via hwota8
Click to expand...
Click to collapse
bro now i use elemental twrp which will not support mtp and otg

shashank1320 said:
Hi Guys,
Some background-
In this guide, I will provide detailed instruction on how to update your Nougat BLN-L22C675 Indian version of Honor 6X to Oreo. Process is simple and you just need patience while updating and post updating I verified, Jio, Vodafone VOLTE working (seems iDEA would work but no 4G in Delhi/NCR).
Prerequisites-
Unlocked bootloader.
HiSuite backup/TWRP backup.
Downloads-
All the Oreo files (downloaded from Firmware finder or below URLs)- you need to put your device as BLN-L22HNC675 and it will show these files under B510 firmware version.
Main zip- http://update.hicloud.com:8180/TDS/data/files/p3/s15/G3196/g1699/v154301/f1/full/update.zip
Data File- http://update.hicloud.com:8180/TDS/...channel_in/update_full_BLN-L22_channel_in.zip
Public Zip- http://update.hicloud.com:8180/TDS/...01/f1/full/public/update_data_full_public.zip
HwOTA zip from https://mega.nz/#!CXRnEaAb!XYodFoS9CDqJkHx0Uv2fdFmzycCvTrexcvYzrwnjfGI given in thread Thanks to @vovan1982
If you have not unlocked your your bootloader, please do so. You can refer this guide if not aware of the method-
Unlocking the bootloader-
Backup all your data as unlocking the bootloader will reset the device and all your data will be erased.
On windows machine, go to folder C:\adb or wherever you installed the adb drivers.
Press shift+right click together and select Open command prompt here (it will be open PowerShell here on Windows 8 and Windows 10 machine)
Run - adb reboot bootloader (this command may prompt for acceptance of RSA key if not already accepted)
This will boot the phone into bootloader mode.
Run - fastboot oem unlock <16 digit unlock code- Put your actual code you obtained from Huawei site > (This step will unlock the bootloader and will erase all your data)
Phone will restart automatically.
Once you have unlocked the bootloader, download the Oreo firmware given above in download link.
Download the HWOTA_BLN_Eng.zip from the link given above.
Unzip the HWOTA_BLN_Eng.zip file and move the extracted content (HWOTA_BLN_Eng folder) to adb folder of your PC.
Copy the downloaded Oreo firmware to C:\adb\HWOTA_BLN_Eng\HWOTA8_BLN\update\ folder.
Rename update_data_full_public.zip file to update_data_public.zip and update_full_BLN-L22_channel_in.zip to update_all_hw.zip, do not rename the update.zip.
Boot to bootloader or fastboot mode. Keep your phone connected with PC.
Go to C:\adb\HWOTA_BLN_Eng\HWOTA8_BLN folder and run the update_eng.bat file and follow the on screen instructions.
The update_eng.bat will install the TWRP recovery and boot to TWRP (if not, you can remove USB and press power and volume up key and it will boot to TWRP, connect the USB again)
You will get prompt for update via SD card or script, select via script
You will get prompt for change region or change firmware, select change firmware.
It will automatically copy the content of C:\adb\HWOTA_BLN_Eng\HWOTA8_BLN\update, mainly those 3 zips and it will flash automatically.
You may see the update.zip file flashed as successful with no error but may see Error result [] for other 2 zips, dont worry that is expected.
Once flashed, it will automatically boot to Oreo without any issue and also it will ask if you want to relock your bootloader or keep this unlocked, this is your wish, I kept it unlocked and will be locked in future updates.
Your Nougat data may remain the same as it was in my case but I would advise to go with Hisuite backup and TWRP backup.
If phone unable to boot, flash the stock recovery and make factory reset and boot normally, it should boot fine. (haven't encountered this issue though)
I did factory reset after booting and verifying to system. Everything was working fine but still I did just to avoid any issue or lag (even though no lags were seen)
About Phone info and VOLTE for Jio and Vodafone. iDEA VOLTE would work as well but there is no 4G in NCR.
Enjoy Oreo.
Click to expand...
Click to collapse
Do not need to renam the firmware files. HwOTA will renam firmware files automatically.

vovan1982 said:
Do not need to renam the firmware files. HwOTA will renam firmware files automatically.
Click to expand...
Click to collapse
Cool. Was not aware of this. Coz with HurUpdate, got error that file doesn't exist so rename them their and thought that is applicable here as well. Thanks for correcting this.

@shashank1320
While unlocking bootloader I took the complete backup with Hisuite but after restoring it everything's there except my safe files.
I am unable to find any of those files(safe box) in file manager too.
Is there any way to recover those files?

Mr. Ajay said:
@shashank1320
While unlocking bootloader I took the complete backup with Hisuite but after restoring it everything's there except my safe files.
I am unable to find any of those files(safe box) in file manager too.
Is there any way to recover those files?
Click to expand...
Click to collapse
not sure how did you backup so cant comment bro. backup doesnt copy any folder.

rojanjoy01 said:
bro now i use elemental twrp which will not support mtp and tpg
---------- Post added at 02:12 PM ---------- Previous post was at 02:12 PM ----------
bro now i use elemental twrp which will not support mtp and otg
Click to expand...
Click to collapse
currently twrp not supporting mtp or otg only way is via sd card.
I saw a TWRP thread for another honor varient that supports mtp and adb push files.

Thank you very much for such a detailed guide.. successfully installed Oreo on my Device ?
Just wanted to mention that faced issue with existing process when it ask to boot in TWRP recovery... It was booting to stock recovery only. So disconnected mobile, switched on , flash TWRP seperately, directly booted to TWRP and connected again to the computer and continued process.
Thak you very much for detailed guide.
Cheers:good:

Develop Bugs

welcome