Root on Chinese Device? [begonia] - Redmi Note 8 Pro Guides, News, & Discussion

I decided to create this thread in order that we gather all the information about rooting on the Chinese Device version of begonia. The described processes presented here are based on my personal experience with the device.
A. Begonia (Chinese Device) + Stock Stable MIUI (whichever region: Chinese/Europe/Global...).
Rooting is achievable with the following process:
0. Flash LRT TWRP and make it permanent by deleting the "recovery_fromboot.p" file.
1. Boot to LRT TWRP.
2. Flash Magisk zip via TWRP.
3. Do Wipe > Advanced Wipe > Dalvik/Art Cache, Data and Cache and proceed.
4. Do > Wipe > Format Data > yes and proceed.
5. Advanced > Close AVB2.0 (2checkmarks)
6. Advanced > RM Force encrypt (2 checkmarks)
7. Reboot to system and complete the initialisation process.
8. Find the Magisk apk that is located on the Magisk zip file and install it.
This process has 2 drawbacks:
1. Encryption is lost (as we put 2 checkamarks in steps 5 and 6).
2. All the user data are lost (as we perform steps 3 and 4).
B. Begonia (Chinese Device) + Stock Beta MIUI (Chinese Version)
Rooting is achievable with the following process:
0. Flash LRT TWRP and make it permanent by deleting the "recovery_fromboot.p" file.
1. Boot to LRT TWRP.
2. Flash Magisk zip via TWRP.
3. Advanced > Close AVB2.0 (1 checkmark, leave it as it is!)
4. Reboot to system
As we can see, rooting begonia (Chinese Device) on the Stock Beta Chinese MIUI firmware is as easy as with any other begonia, from any other region.
However, rooting it while being on a Stock Stable MIUI firmware (any region) cannot be achieved unless encryption is disabled. If we try to follow the usual rooting process by only disabling AVB2.0 (1 checkmark), the phone gets into bootloop.
And here come my questions to the community:
*Does anybody know of a way to root the begonia (Chinese Device) while being on a Stable MIUI firmware without losing encryption? Am I missing something?
*Does anybody know why there is this different behavior on the Chinese Device? What is the difference that causes it?

Can you check develop version. I cant root my device
I only want stock root. Not supersu or magic

This method worked perfectly. :good:
I started with a China ROM Redmi Note 8 Pro with Android 9, MIUI 11.0.3.0.
I did the following steps to convert to Global and install Magisk:
0) Unlock Bootloader
1) Do steps from Megathread (add factory preloader) to avoid bricks.
2) Installing LRT TWRP or Magisk at this step is optional and only needed, if you want to stay on China ROM (tutorial).
3) Convert from China to Global ROM following steps from this thread.
4) Apply immunisation again (repeat step 1 to install factory preloader).
5) Install LRT TWRP again (step 2), but don't follow the steps from there to install Magisk.
6) Follow steps from this tutorial (Method A) to acquire root (Magisk). DATA needs to be formatted and encryption will be lost.
The factory preloader from step 4 should still be present at the end. If not, repeat step 1 once again.
The entire process went smoothly without any problems. Thanks to all the tutorial authors!!

Perfect! Finally i root my device
Great!
Please follow all steps and it would work.
polfrank said:
I decided to create this thread in order that we gather all the information about rooting on the Chinese Device version of begonia. The described processes presented here are based on my personal experience with the device.
A. Begonia (Chinese Device) + Stock Stable MIUI (whichever region: Chinese/Europe/Global...).
Rooting is achievable with the following process:
0. Flash LRT TWRP and make it permanent by deleting the "recovery_fromboot.p" file.
1. Boot to LRT TWRP.
2. Flash Magisk zip via TWRP.
3. Do Wipe > Advanced Wipe > Dalvik/Art Cache, Data and Cache and proceed.
4. Do > Wipe > Format Data > yes and proceed.
5. Advanced > Close AVB2.0 (2checkmarks)
6. Advanced > RM Force encrypt (2 checkmarks)
7. Reboot to system and complete the initialisation process.
8. Find the Magisk apk that is located on the Magisk zip file and install it.
This process has 2 drawbacks:
1. Encryption is lost (as we put 2 checkamarks in steps 5 and 6).
2. All the user data are lost (as we perform steps 3 and 4).
B. Begonia (Chinese Device) + Stock Beta MIUI (Chinese Version)
Rooting is achievable with the following process:
0. Flash LRT TWRP and make it permanent by deleting the "recovery_fromboot.p" file.
1. Boot to LRT TWRP.
2. Flash Magisk zip via TWRP.
3. Advanced > Close AVB2.0 (1 checkmark, leave it as it is!)
4. Reboot to system
As we can see, rooting begonia (Chinese Device) on the Stock Beta Chinese MIUI firmware is as easy as with any other begonia, from any other region.
However, rooting it while being on a Stock Stable MIUI firmware (any region) cannot be achieved unless encryption is disabled. If we try to follow the usual rooting process by only disabling AVB2.0 (1 checkmark), the phone gets into bootloop.
And here come my questions to the community:
*Does anybody know of a way to root the begonia (Chinese Device) while being on a Stable MIUI firmware without losing encryption? Am I missing something?
*Does anybody know why there is this different behavior on the Chinese Device? What is the difference that causes it?
Click to expand...
Click to collapse

Zementblock said:
This method worked perfectly. :good:
I started with a China ROM Redmi Note 8 Pro with Android 9, MIUI 11.0.3.0.
I did the following steps to convert to Global and install Magisk:
0) Unlock Bootloader
1) Do steps from Megathread (add factory preloader) to avoid bricks.
2) Installing LRT TWRP or Magisk at this step is optional and only needed, if you want to stay on China ROM (tutorial).
3) Convert from China to Global ROM following steps from this thread.
4) Apply immunisation again (repeat step 1 to install factory preloader).
5) Install LRT TWRP again (step 2), but don't follow the steps from there to install Magisk.
6) Follow steps from this tutorial (Method A) to acquire root (Magisk). DATA needs to be formatted and encryption will be lost.
The factory preloader from step 4 should still be present at the end. If not, repeat step 1 once again.
The entire process went smoothly without any problems. Thanks to all the tutorial authors!!
Click to expand...
Click to collapse
Yes, but with the method you describe we lose encryption.
This thread is asking for a method to root stock stable miui on the Chinese device without losing encryption.

Related

Asus ZenPad 8.0 (Z380KL) Information Repository

Just going to dump all the info I've found about this device into this thread. All the threads pertaining to this thread are in Russian and I can't read Russian, so this might be helpful to any English speaking owners of this tablet.
Special thanks to Telegram user @SSDD_1744 (don't know your XDA/Reddit user, I'm sorry) for basically spoonfeeding me all these instructions!
WARNING: If you need to flash to stock for whatever reason, be sure to download a image file specific to your country. If you don't, you'll hard brick your device that can only be fixed QPST (supposedly).
Rooting:
(Tested on 5.0.2)
Install KingRoot. Let it root your device.
Install Super-SU Me, to get rid of the bloatware that comes with KingRoot.
Installing Xposed:
I used Flashify to flash TWRP. Be sure to flash the right version though (2.8.7.7 v2) or else you won't be able to mount cache.
Then download Xposed (version sdk21 ARM) and flash it.
WARNING: Flash v1 of the modded TWRP and you won't be able install any apps after flashing Xposed.
Unbricking:
Still working on it. Downloaded QPST but have not been able to get QPST 2.7 to read the tablet.
Links:
Discussion:
https://translate.googleusercontent...690491&usg=ALkJrhiWSlkbZ-tUofZx68NPSGIv8pjIPA
Root:
https://translate.googleusercontent...JrhhQszcRvUo8HILThvz57JmsLj4L9g#entry44556703
https://translate.googleusercontent...JrhiCt__6apcRhk-gtcBExYJCnC9nGQ#entry41676452
Instructions for obtaining the rights to Ruth phones / tablets.
Tested on Android 4.4+
perhaps this algorithm works on Android 5+, I have no way to verify
All transactions with their phones / tablets are performing at your own risk !!!
To get started, read this post from start to finish and only then proceed to action!
Introduction
This instruction is written based on my own experience obtaining root on their plates, and then on the Xperia M2, bought plemyashki. For instructions attached versions of applications that were relevant at the time, the new version can download the relevant topics on the forum, there will find all information on how to work with the proposed programs and algorithms for their actions (links to topics added).
For all the action with your phone / tablet you are responsible for yourself!
Download all the necessary tools to obtain Root (of instructions / topics on the forum), obespechte for phone / tablet access to the Internet (Wi-F / mobile data) and let the phone settings / tablet installation from unknown sources.
Needed Downloads
KingRoot_V4.5.0B202.apk (6.76 MB)
Me_5.9.apk-SuperSU (9.07 MB)
V2.49 Beta.apk SuperSU (5.63 MB)
eu.chainfire.supersu.pro.205.apk (52,88 KB)
Next in series:
1. Install KingRoot .
Get Ruth's right, in the device may reboot.
2. Set SuperSU-Me, .
Run the grantor, the program deletes KingRoot and Chinese KingUser with replacement SuperSu.
Remove the longer SuperSu-Me the desired program.
3. Obnovyaem SuperSu to the latest version. Then set PRO-key .
Installing Pro-key Optionally !!! Use Cases SuperSu without installing key .
4. Open SuperSu and on-demand update binary SU normal way. After a successful update, confirm the request to restart.
5. To make sure that everything is done correctly, check the correct installation and operation of Ruth (mount the system partition on the record), I used the Root Checker Pro and Root Explorer , respectively.
The output is a complete rut without kitayschiny with SuperSu Pro. We use and enjoy
Click to expand...
Click to collapse
Unlocking bootloader (haven't tried this):
https://translate.googleusercontent...Jrhh6g4wI-8Hb_LzAcPnIUxYvWNzZ0A#entry46711087
Stock firmware:
https://translate.googleusercontent...?s=&showtopic=703414&view=findpost&p=45272695
Damn, development has really boomed on this little tablet! Finally got it back after a few months (I sent it into Asus to repair it for me).
Stock ROM:
https://www.asus.com/ru/Tablets/ASUS_ZenPad_80_Z380KL/HelpDesk_Download/ (I can't get the English version to load, delete the /ru/ and you'll be redirected to the English site)
https://www.asus.com.cn/Tablets/ASUS_ZenPad_80_Z380KL/HelpDesk_Download/ (Chinese site)
==== REMEMBER TO DOWNLOAD THE CORRECT COUNTRY OR YOU'LL BE BRICKED) ====
https://yadi.sk/d/b1NMLXHBsNV8C (latest software for the worldwide model)
[http://4pda.ru/forum/index.php?showtopic=703414&st=320#entry50270292]
http://4pda.ru/forum/index.php?showtopic=703414&st=200#entry49389176 (Asus Flash Tool and stock ROM v4.8.2 WW [WorldWide])
Unlocking bootloader:
http://4pda.ru/forum/index.php?showtopic=690491&st=1280#entry48200665 (use fastboot oem device-info to check if it's unlocked)
Root:
http://4pda.ru/forum/index.php?showtopic=690491&st=580#entry44778545 (KingRoot - you'll need a 4PDA.ru account to download this)
http://4pda.ru/forum/index.php?showtopic=690491&st=1280#entry48185323 (last section of the post)
CM13:
http://get.cm/?device=P024&type=nightly
https://vasy.ru/CM13/
http://forum.xda-developers.com/android/help/asus-zenpad-8-z380kl-custom-rom-t3370277
http://forum.xda-developers.com/android/development/kernel-asus-z380kl-p024-kcal2-t3405595 (Kernel)
Recovery:
https://vasy.ru/TWRP/P024/
http://4pda.ru/forum/index.php?showtopic=690491&st=1220#entry48094504 (TWRP 2.8.7.0)
http://forum.xda-developers.com/android/help/asus-zenpad-8-0-z380kl-bootloop-t3373051
Guides:
http://4pda.ru/forum/index.php?showtopic=690491&st=1280#entry48185323 (this has a lot of instructions: root, recovery, boot partition restore, adb drivers etc.)
http://forum.xda-developers.com/android/help/asus-zenpad-8-0-z380kl-bootloop-t3373051 (this has a bunch of files, Resurrection Remix [I haven't tested it yet tho], and instructions on getting out a bootloop)
http://4pda.ru/forum/index.php?showtopic=690491&st=1640#entry49724823 (flashing stock software)
If you want to open the engineering menu, type " * # * # 4636 # * # * "
To boot into fastboot, restart/turn on the device and hold volume up. It'll pop you into a menu with three options.
To boot into recovery, from the fastboot screen (three options), use the volume buttons and navigate to the second option "factory reset" and hit power to confirm. It'll boot into recovery.
=====================================================================================
Recommended way to flash ROMs:
1) Download TWRP. Use adb to boot (NOT flash) into TWRP. Flash ROM there.
2) use KingRoot to root. Use Flashify to flash the ROM.
======================================================================================
If you want to go look up some more info or guides, go here:
http://4pda.ru/forum/index.php?act=...=rel&subforums=0&query=z380kl&forums=570&st=0
and use GTranslate to translate the page. The first page is the earliest posts with the keyword, the last page are the latest post.
please add these ROM's for this Device:
Ressurection Remix:
https://www.androidfilehost.com/?w=files&flid=121811
AICP 12.1:
https://www.androidfilehost.com/?w=files&flid=136181
The latest Official ROM P024 model:
http://dlcdnet.asus.com/pub/ASUS/Ee...ser.zip?_ga=1.109506565.1670552787.1483182775
ZenPad 8 Z380KL Firmware: V5.9.0.0 (WW SKU version only)
Improved Item:
1. Update Google security patch
2. Support unlock tool
9008 brick info:
https://4pda.ru/forum/index.php?showtopic=643084
Pertaining to p024:
https://4pda.ru/forum/index.php?showtopic=643084&st=5740
https://4pda.ru/forum/index.php?showtopic=643084&st=3660 (page 179 - 180, 183 - 185 discusses the files needed to unbrick and how you would - CTRL + F Russ and read the people who quote him)
How I bricked: https://4pda.ru/forum/index.php?showtopic=703414&st=180#entry49329798
https://4pda.ru/forum/index.php?showtopic=690491&st=1420#entry48527044 (unbricking files - dead link though)
https://4pda.ru/forum/index.php?showtopic=703414&st=140 (discussing how to fix using the images from the dump)
I see that Lineage OS is supported on Z380KL. However, I found the wiki spec showing Snapdragon 410, but I found Z380KL in Asia with Snapdragon 615. Before I commit, I'd like to know if anyone knows whether LineageOS is fully compatible with Z380KL with Snapdragon 615 chipsets? Thanks.
Special thanks to @a350tv for helping me comb through 4PDA - this process would've been a lot slower or just wouldn't have happened if he hadn't offered to translate guides and download links to me. So most of the credit goes to him.
Flashing TWRP on 6.0.1 (Sept 1, 2016 patch):
1) grab your drivers (W10: boot into "no driver signature verification mode" to install the drivers needed for fastboot)
https://drive.google.com/open?id=1cGcoDCvmTxfXWNTG0iOXHw1WScmYBrKS
2) turn on debugging
3) type in "adb devices", verify that your computer sees your tablet (if you don't have ADB/Fastboot, get https://forum.xda-developers.com/showthread.php?t=2317790)
4) type in "adb reboot bootloader"
5) you'll see three options: 1. Enter SD DL mode, 2. Factory Reset, 3. Exit update mode
6) type in "fastboot devices", verify that your computer sees your tablet
7) grab your TWRP file (http://vasy.ru/TWRP/P024/) and type in "fastboot flash recovery [replace w/ location of the TWRP file].img"
8) once it says "finished", click factory reset mode (use volume buttons to navigate, power button to enter)
9) it should reboot into TWRP, slide to allow modifications
10) Boom, TWRP is installed.
OPTIONAL, BUT HELPS TO KEEP TWRP INSTALLED: Flash Magisk.
That way, stock recovery won't overwrite TWRP when you reboot.
IF YOU WANT TO KEEP TWRP BUT DON'T WANT Magisk:
1) After first boot into TWRP, turn off tablet.
2) Then turn on and hold Volume Up + Power. That will boot you into Bootloader Mode.
3) Go into factory reset and it should boot you into TWRP.
Now, it's safe to boot into the OS.
(TL;DR: Boot into TWRP twice before booting into the OS or else stock recovery will overwrite TWRP.)
Flashing LineageOS:
1) DL LOS from https://download.lineageos.org/P024
2) DL GApps from http://opengapps.org/ (choose 7.1)
3) boot into TWRP
4) go into Wipe, slide to wipe
5) go to Install, click on LOS file > add to queue, click on Open GApps file > add to queue, flash
6) wait til it's done, click "reboot"
7) wait a while (took mine 3 or so minutes to boot)
8) enjoy!
My GDrive folder with all files needed (except ROM and GApps)
https://drive.google.com/open?id=0BzJ-WWaQYXttTkttdHNELVBEc2M
To do:
Use this tutorial to backup all my partitions, just in case I get bricked yet again.
https://forum.xda-developers.com/showthread.php?t=2450045
Links to unbrick device via Asus FlashTool
Links to service ROMs (for use with AFT)
Add original links from 4PDA
ROMs
LineageOS: https://download.lineageos.org/P024
AICP: https://saki-sss.blogspot.com.by/2016/12/z380k-aicp-121.html
Resurrection Remix: https://androidfilehost.com/?w=files&flid=121811
(made by https://androidfilehost.com/?w=profile&uid=457095661767100043, found from http://andmem.blogspot.jp/2016/05/asus-zenpad-8-z380kl-root-rom.html#chapter-19) - abandoned?
seities said:
I see that Lineage OS is supported on Z380KL. However, I found the wiki spec showing Snapdragon 410, but I found Z380KL in Asia with Snapdragon 615. Before I commit, I'd like to know if anyone knows whether LineageOS is fully compatible with Z380KL with Snapdragon 615 chipsets? Thanks.
Click to expand...
Click to collapse
probably not. I think it's only compatible with the SD 410.
xDark_ said:
Special thanks to @a350tv for helping me comb through 4PDA - this process would've been a lot slower or just wouldn't have happened if he hadn't offered to translate guides and download links to me. So most of the credit goes to him.
Flashing TWRP on 6.0.1 (Sept 1, 2016 patch):
1) grab your drivers (W10: boot into "no driver signature verification mode" to install the drivers needed for fastboot)
https://drive.google.com/open?id=1cGcoDCvmTxfXWNTG0iOXHw1WScmYBrKS
2) turn on debugging
3) type in "adb devices", verify that your computer sees your tablet (if you don't have ADB/Fastboot, get https://forum.xda-developers.com/showthread.php?t=2317790)
4) type in "adb reboot bootloader"
5) you'll see three options: 1. Enter SD DL mode, 2. Factory Reset, 3. Exit update mode
6) type in "fastboot devices", verify that your computer sees your tablet
7) grab your TWRP file (http://vasy.ru/TWRP/P024/) and type in "fastboot flash recovery [replace w/ location of the TWRP file].img"
8) once it says "finished", click factory reset mode (use volume buttons to navigate, power button to enter)
9) it should reboot into TWRP, slide to allow modifications
10) Boom, TWRP is installed.
OPTIONAL, BUT HELPS TO KEEP TWRP INSTALLED: Flash Magisk.
That way, stock recovery won't overwrite TWRP when you reboot.
IF YOU WANT TO KEEP TWRP BUT DON'T WANT Magisk:
1) After first boot into TWRP, turn off tablet.
2) Then turn on and hold Volume Up + Power. That will boot you into Bootloader Mode.
3) Go into factory reset and it should boot you into TWRP.
Now, it's safe to boot into the OS.
(TL;DR: Boot into TWRP twice before booting into the OS or else stock recovery will overwrite TWRP.)
Flashing LineageOS:
1) DL LOS from https://download.lineageos.org/P024
2) DL GApps from http://opengapps.org/ (choose 7.1)
3) boot into TWRP
4) go into Wipe, slide to wipe
5) go to Install, click on LOS file > add to queue, click on Open GApps file > add to queue, flash
6) wait til it's done, click "reboot"
7) wait a while (took mine 3 or so minutes to boot)
8) enjoy!
My GDrive folder with all files needed (except ROM and GApps)
https://drive.google.com/open?id=0BzJ-WWaQYXttTkttdHNELVBEc2M
To do:
Use this tutorial to backup all my partitions, just in case I get bricked yet again.
https://forum.xda-developers.com/showthread.php?t=2450045
Links to unbrick device via Asus FlashTool
Links to service ROMs (for use with AFT)
Add original links from 4PDA
Click to expand...
Click to collapse
Thanks for the tutorial, I had already dared to flash twrp recovery before you wrote this tutorial...
I believe my bootloader is still locked. And I could not reproduce/ write exactly what I did. But, in my case, just for information, when I want to go back into twrp, I can boot into bootloader (power volume up) and then option 2 reset the device gives me the twrp... I am not sure if that is how you get it, but for me, I still had twrp.
I think i will install magisk after reading your post.
jutphaas said:
Thanks for the tutorial, I had already dared to flash twrp recovery before you wrote this tutorial...
I believe my bootloader is still locked. And I could not reproduce/ write exactly what I did. But, in my case, just for information, when I want to go back into twrp, I can boot into bootloader (power volume up) and then option 2 reset the device gives me the twrp... I am not sure if that is how you get it, but for me, I still had twrp.
I think i will install magisk after reading your post.
Click to expand...
Click to collapse
I don't think unlocking the BL is necessary for flashing LOS. But yes, that's how I get into TWRP as well.
Hello I'm new in the forum and I write from Italy, yesterday unfortunately I had the brilliant idea to downgrade my Asus z380kl through ADB, Fastboot and TWRP from pc so far so good, I go to flash the new rom and gives me error, I try to restore the backup here too error result? Tablet locked the only way to make it recognize to the PC is with ASUS FLASH TOOL ROM problem in format.raw unobtainable not even on the Russian site. Any good soul has the possibility to let me download it? Thanks, Sorry English but it is a translation of the very useful Google translate.
pucci2 said:
Hello I'm new in the forum and I write from Italy, yesterday unfortunately I had the brilliant idea to downgrade my Asus z380kl through ADB, Fastboot and TWRP from pc so far so good, I go to flash the new rom and gives me error, I try to restore the backup here too error result? Tablet locked the only way to make it recognize to the PC is with ASUS FLASH TOOL ROM problem in format.raw unobtainable not even on the Russian site. Any good soul has the possibility to let me download it? Thanks, Sorry English but it is a translation of the very useful Google translate.
Click to expand...
Click to collapse
Can you still access fastboot, then at least you can flash twrp as described before in this thread and install from twrp lineageos p024 (lineage-14.1-20180105-nightly-P024-signed.zip) and Open gapps to get google playstore etc , select Arm, (not 64) then version 7.1, then Pico would work.
If you have twrp, you at least can still use your asus... I have found no way to flash original stock... stock must not be flashed from twrp.
Since you mention twrp already used, you can try: turn your device off, then press volume up then the bootloader menu comes, select 2: reset to enter twrp(where it says reset. if you had flashed twrp, that is how you can get into twrp) from there, install lineage os and gapps from micro sd card
My rom is MMB29M.WW_P024-V5.9.4-20170613
xDark_ said:
OPTIONAL, BUT HELPS TO KEEP TWRP INSTALLED: Flash Magisk.
That way, stock recovery won't overwrite TWRP when you reboot.
Click to expand...
Click to collapse
I assume this is on stock rom ? What version of magisk would work? I found I can be back at stock with my twrp backup so ..
But magisk 15.3 zip failed to install on stock-
I also used supersu v82 working on stock, or lineageos.
Would you know what magisk works on lineageos?
I like the exsd extension of magisk so I would like to try it on this device, either stock or lineageos
jutphaas said:
I assume this is on stock rom ? What version of magisk would work? I found I can be back at stock with my twrp backup so ..
But magisk 15.3 zip failed to install on stock-
I also used supersu v82 working on stock, or lineageos.
Would you know what magisk works on lineageos?
I like the exsd extension of magisk so I would like to try it on this device, either stock or lineageos
Click to expand...
Click to collapse
Yes it was. I flashed 15.2 on both stock and LOS. I've heard of some issues with 15.x so you can try .2 or 14.x.
pucci2 said:
Hello I'm new in the forum and I write from Italy, yesterday unfortunately I had the brilliant idea to downgrade my Asus z380kl through ADB, Fastboot and TWRP from pc so far so good, I go to flash the new rom and gives me error, I try to restore the backup here too error result? Tablet locked the only way to make it recognize to the PC is with ASUS FLASH TOOL ROM problem in format.raw unobtainable not even on the Russian site. Any good soul has the possibility to let me download it? Thanks, Sorry English but it is a translation of the very useful Google translate.
Click to expand...
Click to collapse
What error was given? What do you see when you connect it to a computer? What does "tablet locked" mean? Would help if you gave some pictures too.
I'm currently in the process of getting the RAW files/service ROMs for AFT but I don't have an ETA on when I'll be able to get that.
No on the tablet I have not installed TWRP and no other recovery.When I go into the original recovery of the tablet there is always the screen with the lock closed at the bottom right and there is no way to show it to the PC even with adb sideload, l 'only program that recognizes me the tablet is Asus flash tool, however, as I have already written the damn ROM in RAW format is untraceable.
pucci2 said:
No on the tablet I have not installed TWRP and no other recovery.When I go into the original recovery of the tablet there is always the screen with the lock closed at the bottom right and there is no way to show it to the PC even with adb sideload, l 'only program that recognizes me the tablet is Asus flash tool, however, as I have already written the damn ROM in RAW format is untraceable.
Click to expand...
Click to collapse
Does it respons to adb devices of fastboot devices in this stage?
no, it is not recognized

Help me please my cellular isn't working

Hey you guys i just flashed the open 8 beta and now my sim card won't configure itself and it's really stressing
jamesblunt1 said:
Hey you guys i just flashed the open 8 beta and now my sim card won't configure itself and it's really stressing
Click to expand...
Click to collapse
how did you flash it and what was your previous setup? you need to tell people what exactly you have done, otherwise there's literally no way anyone can help you.
bombaglad said:
how did you flash it and what was your previous setup? you need to tell people what exactly you have done, otherwise there's literally no way anyone can help you.
Click to expand...
Click to collapse
I had the latest freedom OS CB build and the modified twrp
> Method 2 with Modified Script using Official TWRP Credits @ahmediftikhar
If you come from a Custom Rom Factory Reset and Clean Flash or If you come from OOS based rom Dirty Flash as below:
This guide allows you to install OOS Open Beta 8 (N) / 7 (MM) without having to switch to modified TWRP
All credits to the respective developers
Downloads : MEGA
Download Contains the following:
1- Modded OOS Open Beta 8 (No F2FS , Downgradable to any OOS version)
2- Modded OOS Open Beta 7
3 - Debloater / Pixel Laucher (Black) and H2OS Icon Packs , Google Assistant (Unified Flashable Zip)
4- Super SU 2.78-SR5
5- Official TWRP
6 - Modified TWRP Recovery 3.0.2-1.28 Credits @eng.stk
7- Latest Xposed Installer (Beta 7 Only) (It will give you the option to download / install the latest version of framework automatically)
8- Open Beta 8 Full flash able (F2FS support with Modified Recovery)
Instructions for Clean / Dirty Flash (Over any Open Beta after 3.5.1) :
1. Boot into TWRP (modified or official which ever you are on)
2. Wipe Dalvik / ART cache & cache OR Factory Reset ( If you are coming from another ROM)
3. Flash Modded OOS Open Beta 8 (Dont Switch /system and /data to F2FS if you want to root) or Beta 7
4. Wipe Dalvik and Cache
5 . Flash official twrp as image (even if you are already on it)
6. Reboot to into recovery directly (this will prevent recovery from being overwrite by the stock)
7. Flash SuperSu (Optional)
8. Flash Debloater / Pixel Laucher (Black) and H2OS Icon Packs , Google Assistant (Clear Google App Data after Booting) (Unified Flashable Zip) (Optional)
9. Reboot System & Profit
PS: System will reboot twice if you flashed SuperSU, Dont Panic !!
Never Settle
http://forum.xda-developers.com/oneplus-3/how-to/rom-community-build-3-5-5-t3490939
ok. a simple search in the thread showed that several people were having issues with the sim, and no solution has been posted. i suggest you try the following:
- put your sim in the other slot
- wipe dalvik and cache
- go back to stock completely and flash the beta 7 the official way (i know you'll loose the data but clean flashes are always better)
you need to root the phone install Super SU (SR5) as given in the instructions above.

[How-to]: OTA updates with (Magisk) rooted devices

Hi,
I present here my last guide for OTA upgrades with rooted devices, in this case with Magisk.
Previous similar work:
http://forum.xda-developers.com/g5-plus/how-to/guide-simple-ota-update-rooted-unlocked-t3610895
http://forum.xda-developers.com/moto-g4/how-to/guide-simple-ota-update-rooted-unlocked-t3510126
This guide is tested by me for an upgrade from NPNS25.137-33-5 to NPNS25.137-33-11 using the incremental OTA (the official upgrade you get in the smartphone). Please, note that this guide is for advanced users!
Starting point:
- STOCK ROM with an untouched SYSTEM partition.
- Flashed custom TWRP as recovery.
- Flashed custom kernel with disabled Data encryption enforcement.
- MagiskSU installed, and any other changes that you like (i.e. Xposed) but all Systemless.
- USB Debug mode enabled in Developer Options and access granted from your PC.
- One SD card with almost 16GB of size.
Warning: If you use PIN or any other lock procedure, I recommend to disable it before backups and enable after restore!
PROCEDURE:
Step 1:
Backup your SD-Internal (to PC or SD-CARD). This is required because the TWRP backup doesn't backup this data.
Step 2:
Reboot to TWRP, Make backup of "Data", "Logo" & "Boot" (you will restore them after the upgrade).
Step 3:
Reboot to Bootloader and flash ORIGINAL partitions "Recovery", "Logo" & "Boot" using a PC:
Code:
# fastboot flash logo logo.bin
# fastboot flash boot boot.img
# fastboot flash recovery recovery.img
Or if you have a TWRP backup of these patitions, then you could restore them from TWRP (instead of using a PC).
Note: If you have modified SYSTEM and/or OEM partitions, then also flash them (or restore them from a TWRP backup):
Code:
# fastboot flash system system.img
# fastboot flash oem oem.img
Step 4:
Reboot.
Note: from this point your "Data" partition is now fully encrypted, so not execute any relevant command as you will lose any update when restore the "Data" after the OTA update. At this point you have the smartphone in "pure" Stock mode.
Step 5:
Go to check "System Updates", download the update & install the OTA (the device reboots).
Step 6:
After rebooting the OTA file is executed. If it ends with an "ERROR" message, then something is erroneous (check your partitions!).
If the device reboots without an error check your new firmware. The upgrade is completed!
Step 7:
From this point you would like to restore your previous state: data, root, Magisk, etc.
If you like to save a TWRP backup of current partitions (for the next OTA upgrade) then do this:
- Reboot to bootloader mode and boot a non-flashable TWRP (like then Multi-ROM version: "fastboot boot mr-twrp-3.1.1-potter-20170521.img") and complete a backup of the new "Recovery", "Boot", "Logo", "System" & "Oem" partitions to the SDCard.
NOTE: The Multi-ROM TWRP can't backup/mount the OEM partition! Use another method or complete the backup after (you can backup SYSTEM and OEM after).
ALTERNATIVE: Open Terminal and do a manual dump of "Recovery", "Boot", "Logo" and/or "System", "OEM":
Code:
# dd if=/dev/block/bootdevice/by-name/recovery of=/external_sd/recovery.img
# dd if=/dev/block/bootdevice/by-name/boot of=/external_sd/boot.img
# dd if=/dev/block/bootdevice/by-name/logo of=/external_sd/logo.img
Code:
# dd if=/dev/block/bootdevice/by-name/system of=/external_sd/system.img
# dd if=/dev/block/bootdevice/by-name/oem of=/external_sd/oem.img
Step 8:
a) Restore or Flash a recent version of TWRP: "fastboot flash recovery twrp-3.1.1-4-GtrCraft.img" (this version has support for backup/restore OEM!)
b) Reboot to the TWRP recovery and inside it...
c) I recommend first to make now a backup of SYSTEM and OEM paritions (for the next OTA).
d) Format your "Data" partion with "f2fs".
e) Restore your "Data" (and "Logo" & "Cache") from the backup at step #2.
f) Install the ZIP of your custom kernel (or as alternative apply "disable dm-verity").
g) Install the ZIP of Magisk for root.
Step 9:
Re-boot an enjoy your upgraded system!
Remeber to restore your Internal SD card data (from the step #1).
Enable your preferable security option.
:victory:
Nice guide!
One question: How do we flash original items (e.g. OEM, system, boot) if we are on a version with no official firmware? For example, I'm on NPN25.137-83. As far as I know, there is no full firmware for that version; it's only offered as an OTA. If I'm offered an OTA, how can I restore an unmodified system, boot, recovery, etc?
Jrhotrod said:
Nice guide!
One question: How do we flash original items (e.g. OEM, system, boot) if we are on a version with no official firmware? For example, I'm on NPN25.137-83. As far as I know, there is no full firmware for that version; it's only offered as an OTA. If I'm offered an OTA, how can I restore an unmodified system, boot, recovery, etc?
Click to expand...
Click to collapse
If you lost your original SYSTEM, OEM and BOOT partitions, then you need to flash from another place.
For example, you can use download from this post
http://forum.xda-developers.com/g5-plus/how-to/firmwares-moto-g5-plus-t3593160
In any case, I recommend to:
- Use OTAs for upgrading, as it's safe for update your modem and other device stuff (IMEI, etc.) in sync.
- If you like to go from Custom ROM to Stock ROM then restore the last Stock version in your device and apply OTAs from this point.
Regards!
Hi,
More than a week with this GUIDE and only one user puts feedback?
Which TWRP?
manos78 said:
Hi,
More than a week with this GUIDE and only one user puts feedback?
Click to expand...
Click to collapse
This is because we are all still stunned by this cool guide!
However, before I give it a try: in Step 7, why does it have to be
"fastboot boot mr-twrp-3.1.1-potter-20170521.img"?
Can't I use
"fastboot boot twrp-3.1.1-4-GtrCraft.img" here, already? What is it, the craft TWRP cannot do? At least I am able to boot it that way.
Thanks in advance,
Nick.
G5 Plus Mate said:
This is because we are all still stunned by this cool guide!
However, before I give it a try: in Step 7, why does it have to be
"fastboot boot mr-twrp-3.1.1-potter-20170521.img"?
Can't I use
"fastboot boot twrp-3.1.1-4-GtrCraft.img" here, already? What is it, the craft TWRP cannot do? At least I am able to boot it that way.
Thanks in advance,
Nick.
Click to expand...
Click to collapse
Yes, the Fastboot boot command will work for any TWRP image for this phone.
Jrhotrod said:
Yes, the Fastboot boot command will work for any TWRP image for this phone.
Click to expand...
Click to collapse
Cool, so as it seems, we now only need two tools for rooting, unrooting and OTA updates. The Craft TWRP and Magisk v14.0 (or higher). Well, or SuperSU. Booth seem to remove "force encryption" and the "dm-verify-test".
So, we also do not need any further custom kernel or anything else anymore(?)
Well, my XT1687 (which will replace my XT1685, I need a compass!) is supposed to arrive tomorrow. :fingers-crossed:
I'll give it all a try and some comments, too...
G5 Plus Mate said:
Cool, so as it seems, we now only need two tools for rooting, unrooting and OTA updates. The Craft TWRP and Magisk v14.0 (or higher). Well, or SuperSU. Booth seem to remove "force encryption" and the "dm-verify-test".
So, we also do not need any further custom kernel or anything else anymore(?)
Well, my XT1687 (which will replace my XT1685, I need a compass!) is supposed to arrive tomorrow. :fingers-crossed:
I'll give it all a try and some comments, too...
Click to expand...
Click to collapse
Most people with this phone use custom kernels in order to be able to use magisk modules. The stock kernel does not allow for neither passing safetynet nor installing modules. If you would like to use something like systemless Xposed Framework, I'd recommend flashing ElementalX.
Jrhotrod said:
Yes, the Fastboot boot command will work for any TWRP image for this phone.
Click to expand...
Click to collapse
OK, thank you for confirm it!
G5 Plus Mate said:
Cool, so as it seems, we now only need two tools for rooting, unrooting and OTA updates. The Craft TWRP and Magisk v14.0 (or higher). Well, or SuperSU. Booth seem to remove "force encryption" and the "dm-verify-test".
So, we also do not need any further custom kernel or anything else anymore(?)
Click to expand...
Click to collapse
Hi,
If you save a full dump of the SYSTEM partition, then you can use "dm-verity" disable. However, I don't recomment it. Use MagiskSU with a custom kernel (like ElementalX). A custom kernel que provide: Magisk loop mount, non forced encryption, and SafetyNet pass with Magisk running.
Summarizing, you need: custom kernel, Magisk and TWRP.
Slightly modified
Hi.
first of all, thanks again, Manos 78, for the wonderful guide. Playing around with it for several days, I have come up with a slightly modified solution that might be easier to handle. However, it's based on your guide.
So, this guide is for people who (like me) want
- a rooted Moto G5 Plus (might work on other phones, too)
- an unencrypted data partition (e.g. to be able to backup it)
- a relatively easy way to do a system upgrade.
Also, this guide goes for categories of people who start from here with a phone
Cat-1
- with an unencrypted data partition (rooted)
Cat-2
- which is a blank new phone
Cat-3
- with an encrypted data partition
Instead of Magisk, you can probably use SuperSU as well. Also, it doesn't matter if you flash or load TWRP with fastboot. I would recommend flashing it like described below. I have tested it once with XT1687 only, and then with transferring images from my XT1685. Both worked.
So, first you should find yourself a stock-rom suitable for your phone. As for now (let's hope that this won't change) you need to download it once and then use it again for all upcoming future updates as we do the OTA-update.
I used for
XT1687 : POTTER_NPNS25.137-35-5_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC
XT1685: POTTER_NPN25.137-35_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC
After transferring from XT1685 to XT1687, the Dual-SIM handling app froze automatically and I am now on software channel reteu. However, as we update as described below, it doesn't matter.
Let's start with
Cat-1:
01. Disable PIN or any other lock procedure and TWRP-Backup of all partitions (precaution, but you will definitely need data, boot and logo!). Also backup all data of your internal SD-card as it will be wiped. External SD-card will stay untouched.
02. Flash latest elementalX Kernel (optional) and Magisk (14.0 or later) to be on the same version before and after the update (precaution).
Either
03a. Flash any valid old(er) Stock-Rom, fitting to the update channel of your phone. If one works, use it again each time you update.
03b. Perform OTA update (after reboot wait for the message saying it's done!)
or
04. Download and install latest Stock-Rom and install
05. Flash TWRP "twrp-3.1.1-4-GtrCraft.img"
06. Flash latest elementalX Kernel(optional, but recommended) and then MAGISK (14.0 or later)
07. Reboot to TWRP
08. Format data
09. Reboot to TWRP
10. Restore data, boot und logo
11. Reboot
12. In Developer Options disable automatic update
13. Install / upgrade Magisk Manager app
14. Flash logo.bin (optional to get rid of the ugly initial warning screen)
done.
Cat-2
Perform steps 03a/b, 5,6,7,8,9,12,13,14. Boot-loader needs to be unlocked, of course.
Cat-3
As you cannot backup an unencrypted partition (for now) you will have to backup your data conventionally. Titanium Backup and app's own functionalities might help. However, this needs to be done only once as you will be unencrypted afterwards.
After this, re-flash Stock-Rom and proceed like for Cat-2.
Note:
Once again: this is a system-less variant, so it doesn't touch the system partition. If you want to keep it that way, then in TWRP never swipe to allow modifications! Choose system partition read only.
The following might need to be confirmed, but I believe, that if you do it once, the device will recognize it and when you go into boot loader the device will from now on display the system to be modified. I haven't found a way to get rid of that again.
If you leave it untouched, then this message will not come up and after locking the boot loader again you will have a device like new again. I think you will not get into any warranty trouble once something is broken.
Maybe some one can comment on this to be right or wrong…
And, just in case you have similar problems:
On windows I was not able to unlock my boot-loader.. I got the message that the boot-loader cannot be unlocked. On Mint Linux it just worked fine. Also flashing logo.bin did not work on windows but on Linux.
On Linux again flashing the stock-rom does not work, but on windows. I am not sure if I want a comment on that.
Stuck in Your device will boot in 5 seconds screen
Hi,
At step 3, I didnt have the original partitions. So I used the partitions from the firmware POTTER_AMZ_7.0_NPNS25.137-35-5_cid18_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip.
After rebooting it, my phone is stuck in the screen. At one point it showed error.
What should I do??
Help
Why data partition format to f2fs
Is it important to format data partition to f2fs? Can I just wipe data partition and restore from the backup without formatting?
manos78 said:
Hi,
I present here my last guide for OTA upgrades with rooted devices, in this case with Magisk.
Previous similar work:
http://forum.xda-developers.com/g5-plus/how-to/guide-simple-ota-update-rooted-unlocked-t3610895
http://forum.xda-developers.com/moto-g4/how-to/guide-simple-ota-update-rooted-unlocked-t3510126
This guide is tested by me for an upgrade from NPNS25.137-33-5 to NPNS25.137-33-11 using the incremental OTA (the official upgrade you get in the smartphone). Please, note that this guide is for advanced users!
Starting point:
- STOCK ROM with an untouched SYSTEM partition.
- Flashed custom TWRP as recovery.
- Flashed custom kernel with disabled Data encryption enforcement.
- MagiskSU installed, and any other changes that you like (i.e. Xposed) but all Systemless.
- USB Debug mode enabled in Developer Options and access granted from your PC.
- One SD card with almost 16GB of size.
Warning: If you use PIN or any other lock procedure, I recommend to disable it before backups and enable after restore!
PROCEDURE:
Step 1:
Backup your SD-Internal (to PC or SD-CARD). This is required because the TWRP backup doesn't backup this data.
Step 2:
Reboot to TWRP, Make backup of "Data", "Logo" & "Boot" (you will restore them after the upgrade).
Step 3:
Reboot to Bootloader and flash ORIGINAL partitions "Recovery", "Logo" & "Boot" using a PC:
Code:
# fastboot flash logo logo.bin
# fastboot flash boot boot.img
# fastboot flash recovery recovery.img
Or if you have a TWRP backup of these patitions, then you could restore them from TWRP (instead of using a PC).
Note: If you have modified SYSTEM and/or OEM partitions, then also flash them (or restore them from a TWRP backup):
Code:
# fastboot flash system system.img
# fastboot flash oem oem.img
Step 4:
Reboot.
Note: from this point your "Data" partition is now fully encrypted, so not execute any relevant command as you will lose any update when restore the "Data" after the OTA update. At this point you have the smartphone in "pure" Stock mode.
Step 5:
Go to check "System Updates", download the update & install the OTA (the device reboots).
Step 6:
After rebooting the OTA file is executed. If it ends with an "ERROR" message, then something is erroneous (check your partitions!).
If the device reboots without an error check your new firmware. The upgrade is completed!
Step 7:
From this point you would like to restore your previous state: data, root, Magisk, etc.
If you like to save a TWRP backup of current partitions (for the next OTA upgrade) then do this:
- Reboot to bootloader mode and boot a non-flashable TWRP (like then Multi-ROM version: "fastboot boot mr-twrp-3.1.1-potter-20170521.img") and complete a backup of the new "Recovery", "Boot", "Logo", "System" & "Oem" partitions to the SDCard.
NOTE: The Multi-ROM TWRP can't backup/mount the OEM partition! Use another method or complete the backup after (you can backup SYSTEM and OEM after).
ALTERNATIVE: Open Terminal and do a manual dump of "Recovery", "Boot", "Logo" and/or "System", "OEM":
Code:
# dd if=/dev/block/bootdevice/by-name/recovery of=/external_sd/recovery.img
# dd if=/dev/block/bootdevice/by-name/boot of=/external_sd/boot.img
# dd if=/dev/block/bootdevice/by-name/logo of=/external_sd/logo.img
Code:
# dd if=/dev/block/bootdevice/by-name/system of=/external_sd/system.img
# dd if=/dev/block/bootdevice/by-name/oem of=/external_sd/oem.img
Step 8:
a) Restore or Flash a recent version of TWRP: "fastboot flash recovery twrp-3.1.1-4-GtrCraft.img" (this version has support for backup/restore OEM!)
b) Reboot to the TWRP recovery and inside it...
c) I recommend first to make now a backup of SYSTEM and OEM paritions (for the next OTA).
d) Format your "Data" partion with "f2fs".
e) Restore your "Data" (and "Logo" & "Cache") from the backup at step #2.
f) Install the ZIP of your custom kernel (or as alternative apply "disable dm-verity").
g) Install the ZIP of Magisk for root.
Step 9:
Re-boot an enjoy your upgraded system!
Remeber to restore your Internal SD card data (from the step #1).
Enable your preferable security option.
:victory:
Click to expand...
Click to collapse
androidgeek121 said:
Is it important to format data partition to f2fs? Can I just wipe data partition and restore from the backup without formatting?
Click to expand...
Click to collapse
Hi,
- The "f2fs" is the default format in Stock ROM. If you don't select it in TWRP it will be formated as "ext4".
- The "f2fs" filesystem it's better than "ext4" for the internal eMMC storage (faster writes and more robust).
- If you format as "ext4" it will continue working. So, if you restore without forcing the format perhaps you don't care that the filesystem it's changed.
Regards!
Are OTA updates possible 1. without TWRP and 2. with preserved encryption?
I have a Samsung Galaxy S7 edge, international version, Android 6, unlocked bootloader, first rooted with CF-auto-root, now installed Magisk via modified boot.img, pure stock rom.
Forgive me for sounding dense but this method could work on a Moto G4 Plus (athene) correct? ?
G5 Plus Mate said:
Hi.
first of all, thanks again, Manos 78, for the wonderful guide. Playing around with it for several days, I have come up with a slightly modified solution that might be easier to handle. However, it's based on your guide.
So, this guide is for people who (like me) want
- a rooted Moto G5 Plus (might work on other phones, too)
- an unencrypted data partition (e.g. to be able to backup it)
- a relatively easy way to do a system upgrade.
Also, this guide goes for categories of people who start from here with a phone
Cat-1
- with an unencrypted data partition (rooted)
Cat-2
- which is a blank new phone
Cat-3
- with an encrypted data partition
Instead of Magisk, you can probably use SuperSU as well. Also, it doesn't matter if you flash or load TWRP with fastboot. I would recommend flashing it like described below. I have tested it once with XT1687 only, and then with transferring images from my XT1685. Both worked.
So, first you should find yourself a stock-rom suitable for your phone. As for now (let's hope that this won't change) you need to download it once and then use it again for all upcoming future updates as we do the OTA-update.
I used for
XT1687 : POTTER_NPNS25.137-35-5_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC
XT1685: POTTER_NPN25.137-35_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC
After transferring from XT1685 to XT1687, the Dual-SIM handling app froze automatically and I am now on software channel reteu. However, as we update as described below, it doesn't matter.
Let's start with
Cat-1:
01. Disable PIN or any other lock procedure and TWRP-Backup of all partitions (precaution, but you will definitely need data, boot and logo!). Also backup all data of your internal SD-card as it will be wiped. External SD-card will stay untouched.
02. Flash latest elementalX Kernel (optional) and Magisk (14.0 or later) to be on the same version before and after the update (precaution).
Either
03a. Flash any valid old(er) Stock-Rom, fitting to the update channel of your phone. If one works, use it again each time you update.
03b. Perform OTA update (after reboot wait for the message saying it's done!)
or
04. Download and install latest Stock-Rom and install
05. Flash TWRP "twrp-3.1.1-4-GtrCraft.img"
06. Flash latest elementalX Kernel(optional, but recommended) and then MAGISK (14.0 or later)
07. Reboot to TWRP
08. Format data
09. Reboot to TWRP
10. Restore data, boot und logo
11. Reboot
12. In Developer Options disable automatic update
13. Install / upgrade Magisk Manager app
14. Flash logo.bin (optional to get rid of the ugly initial warning screen)
done.
Cat-2
Perform steps 03a/b, 5,6,7,8,9,12,13,14. Boot-loader needs to be unlocked, of course.
Cat-3
As you cannot backup an unencrypted partition (for now) you will have to backup your data conventionally. Titanium Backup and app's own functionalities might help. However, this needs to be done only once as you will be unencrypted afterwards.
After this, re-flash Stock-Rom and proceed like for Cat-2.
Note:
Once again: this is a system-less variant, so it doesn't touch the system partition. If you want to keep it that way, then in TWRP never swipe to allow modifications! Choose system partition read only.
The following might need to be confirmed, but I believe, that if you do it once, the device will recognize it and when you go into boot loader the device will from now on display the system to be modified. I haven't found a way to get rid of that again.
If you leave it untouched, then this message will not come up and after locking the boot loader again you will have a device like new again. I think you will not get into any warranty trouble once something is broken.
Maybe some one can comment on this to be right or wrong…
And, just in case you have similar problems:
On windows I was not able to unlock my boot-loader.. I got the message that the boot-loader cannot be unlocked. On Mint Linux it just worked fine. Also flashing logo.bin did not work on windows but on Linux.
On Linux again flashing the stock-rom does not work, but on windows. I am not sure if I want a comment on that.
Click to expand...
Click to collapse
Many thanks for this method. I used Cat -1 today and ran into a little problem with repeated com.android.phone has stopped working errors after just flashing the partitions listed here. So I just did a complete Stock reflash and that resolved that error. Then was able to proceed with the rest of the steps without any issues!
I am on RETUS and applied the November 1st update. Surprised on how well it worked!
manos78 said:
Hi,
I present here my last guide for OTA upgrades with rooted devices, in this case with Magisk.
Previous similar work:
http://forum.xda-developers.com/g5-plus/how-to/guide-simple-ota-update-rooted-unlocked-t3610895
http://forum.xda-developers.com/moto-g4/how-to/guide-simple-ota-update-rooted-unlocked-t3510126
This guide is tested by me for an upgrade from NPNS25.137-33-5 to NPNS25.137-33-11 using the incremental OTA (the official upgrade you get in the smartphone). Please, note that this guide is for advanced users!
Starting point:
- STOCK ROM with an untouched SYSTEM partition.
- Flashed custom TWRP as recovery.
- Flashed custom kernel with disabled Data encryption enforcement.
- MagiskSU installed, and any other changes that you like (i.e. Xposed) but all Systemless.
- USB Debug mode enabled in Developer Options and access granted from your PC.
- One SD card with almost 16GB of size.
Warning: If you use PIN or any other lock procedure, I recommend to disable it before backups and enable after restore!
PROCEDURE:
Step 1:
Backup your SD-Internal (to PC or SD-CARD). This is required because the TWRP backup doesn't backup this data.
Step 2:
Reboot to TWRP, Make backup of "Data", "Logo" & "Boot" (you will restore them after the upgrade).
Step 3:
Reboot to Bootloader and flash ORIGINAL partitions "Recovery", "Logo" & "Boot" using a PC:
Code:
# fastboot flash logo logo.bin
# fastboot flash boot boot.img
# fastboot flash recovery recovery.img
Or if you have a TWRP backup of these patitions, then you could restore them from TWRP (instead of using a PC).
Note: If you have modified SYSTEM and/or OEM partitions, then also flash them (or restore them from a TWRP backup):
Code:
# fastboot flash system system.img
# fastboot flash oem oem.img
Step 4:
Reboot.
Note: from this point your "Data" partition is now fully encrypted, so not execute any relevant command as you will lose any update when restore the "Data" after the OTA update. At this point you have the smartphone in "pure" Stock mode.
Step 5:
Go to check "System Updates", download the update & install the OTA (the device reboots).
Step 6:
After rebooting the OTA file is executed. If it ends with an "ERROR" message, then something is erroneous (check your partitions!).
If the device reboots without an error check your new firmware. The upgrade is completed!
Step 7:
From this point you would like to restore your previous state: data, root, Magisk, etc.
If you like to save a TWRP backup of current partitions (for the next OTA upgrade) then do this:
- Reboot to bootloader mode and boot a non-flashable TWRP (like then Multi-ROM version: "fastboot boot mr-twrp-3.1.1-potter-20170521.img") and complete a backup of the new "Recovery", "Boot", "Logo", "System" & "Oem" partitions to the SDCard.
NOTE: The Multi-ROM TWRP can't backup/mount the OEM partition! Use another method or complete the backup after (you can backup SYSTEM and OEM after).
ALTERNATIVE: Open Terminal and do a manual dump of "Recovery", "Boot", "Logo" and/or "System", "OEM":
Code:
# dd if=/dev/block/bootdevice/by-name/recovery of=/external_sd/recovery.img
# dd if=/dev/block/bootdevice/by-name/boot of=/external_sd/boot.img
# dd if=/dev/block/bootdevice/by-name/logo of=/external_sd/logo.img
Code:
# dd if=/dev/block/bootdevice/by-name/system of=/external_sd/system.img
# dd if=/dev/block/bootdevice/by-name/oem of=/external_sd/oem.img
Step 8:
a) Restore or Flash a recent version of TWRP: "fastboot flash recovery twrp-3.1.1-4-GtrCraft.img" (this version has support for backup/restore OEM!)
b) Reboot to the TWRP recovery and inside it...
c) I recommend first to make now a backup of SYSTEM and OEM paritions (for the next OTA).
d) Format your "Data" partion with "f2fs".
e) Restore your "Data" (and "Logo" & "Cache") from the backup at step #2.
f) Install the ZIP of your custom kernel (or as alternative apply "disable dm-verity").
g) Install the ZIP of Magisk for root.
Step 9:
Re-boot an enjoy your upgraded system!
Remeber to restore your Internal SD card data (from the step #1).
Enable your preferable security option.
:victory:
Click to expand...
Click to collapse
Thank you so much you wonderful person. Successfully upgraded to NPNS25. 137-93-4 and security patch January, 1 2018 with an unlocked bootloader. I had to flash recovery, logo, boot, system.parts & oem for it succeed. I won't forget this anytime soon.
Just a little hint:
In step 8 you say
e) Restore your "Data" (and "Logo" & "Cache") from the backup at step #2.
Click to expand...
Click to collapse
It should be "Boot" instead of "Cache" as we made a backup of "Data", "Logo" & "Boot" in step 2.
manos78 said:
Hi,
I present here my last guide for OTA upgrades with rooted devices, in this case with Magisk.
Previous similar work:
http://forum.xda-developers.com/g5-plus/how-to/guide-simple-ota-update-rooted-unlocked-t3610895
http://forum.xda-developers.com/moto-g4/how-to/guide-simple-ota-update-rooted-unlocked-t3510126
This guide is tested by me for an upgrade from NPNS25.137-33-5 to NPNS25.137-33-11 using the incremental OTA (the official upgrade you get in the smartphone). Please, note that this guide is for advanced users!
Starting point:
- STOCK ROM with an untouched SYSTEM partition.
- Flashed custom TWRP as recovery.
- Flashed custom kernel with disabled Data encryption enforcement.
- MagiskSU installed, and any other changes that you like (i.e. Xposed) but all Systemless.
- USB Debug mode enabled in Developer Options and access granted from your PC.
- One SD card with almost 16GB of size.
Warning: If you use PIN or any other lock procedure, I recommend to disable it before backups and enable after restore!
PROCEDURE:
Step 1:
Backup your SD-Internal (to PC or SD-CARD). This is required because the TWRP backup doesn't backup this data.
Step 2:
Reboot to TWRP, Make backup of "Data", "Logo" & "Boot" (you will restore them after the upgrade).
Step 3:
Reboot to Bootloader and flash ORIGINAL partitions "Recovery", "Logo" & "Boot" using a PC:
Code:
# fastboot flash logo logo.bin
# fastboot flash boot boot.img
# fastboot flash recovery recovery.img
Or if you have a TWRP backup of these patitions, then you could restore them from TWRP (instead of using a PC).
Note: If you have modified SYSTEM and/or OEM partitions, then also flash them (or restore them from a TWRP backup):
Code:
# fastboot flash system system.img
# fastboot flash oem oem.img
Step 4:
Reboot.
Note: from this point your "Data" partition is now fully encrypted, so not execute any relevant command as you will lose any update when restore the "Data" after the OTA update. At this point you have the smartphone in "pure" Stock mode.
Step 5:
Go to check "System Updates", download the update & install the OTA (the device reboots).
Step 6:
After rebooting the OTA file is executed. If it ends with an "ERROR" message, then something is erroneous (check your partitions!).
If the device reboots without an error check your new firmware. The upgrade is completed!
Step 7:
From this point you would like to restore your previous state: data, root, Magisk, etc.
If you like to save a TWRP backup of current partitions (for the next OTA upgrade) then do this:
- Reboot to bootloader mode and boot a non-flashable TWRP (like then Multi-ROM version: "fastboot boot mr-twrp-3.1.1-potter-20170521.img") and complete a backup of the new "Recovery", "Boot", "Logo", "System" & "Oem" partitions to the SDCard.
NOTE: The Multi-ROM TWRP can't backup/mount the OEM partition! Use another method or complete the backup after (you can backup SYSTEM and OEM after).
ALTERNATIVE: Open Terminal and do a manual dump of "Recovery", "Boot", "Logo" and/or "System", "OEM":
Code:
# dd if=/dev/block/bootdevice/by-name/recovery of=/external_sd/recovery.img
# dd if=/dev/block/bootdevice/by-name/boot of=/external_sd/boot.img
# dd if=/dev/block/bootdevice/by-name/logo of=/external_sd/logo.img
Code:
# dd if=/dev/block/bootdevice/by-name/system of=/external_sd/system.img
# dd if=/dev/block/bootdevice/by-name/oem of=/external_sd/oem.img
Step 8:
a) Restore or Flash a recent version of TWRP: "fastboot flash recovery twrp-3.1.1-4-GtrCraft.img" (this version has support for backup/restore OEM!)
b) Reboot to the TWRP recovery and inside it...
c) I recommend first to make now a backup of SYSTEM and OEM paritions (for the next OTA).
d) Format your "Data" partion with "f2fs".
e) Restore your "Data" (and "Logo" & "Cache") from the backup at step #2.
f) Install the ZIP of your custom kernel (or as alternative apply "disable dm-verity").
g) Install the ZIP of Magisk for root.
Step 9:
Re-boot an enjoy your upgraded system!
Remember to restore your Internal SD card data (from the step #1).
Enable your preferable security option.
:victory:
Click to expand...
Click to collapse
I am kind'a novice at this - also it's my first time installing the latest RETUS OTA update 93-10. Would someone please clarify the questions below?
I do not recall if I modified SYSTEM and/or OEM partitions when I rooted the phone, is it OK to go ahead and flash? :
Code:
# fastboot flash system system.img
# fastboot flash oem oem.img
In Step 7 - do I restore "Data", "Logo" & "Boot" with TWRP from back-up in Step 2?
Everything else from Step 8 down is optional?

Installing Magisk on Redmi Note 8T (Willow) with Lineage OS and recovery

I am trying to get Magisk to work on my Xiaomi Redmi Note 8T with Lineage OS, but the step where I am patching the boot.img is failing. I am using LOS recovery, and I followed the instructions provided by topjohnwu [1]: because the 8T doesn't appear to have ramdisk (I don't know what that means btw), I need to patch an image (my recovery image?) with the magisk app - this is what I did:
1. Install Magisk App and check status: "Ramdisk: No"
2. Download Lineage recovery image [2] and patch in Magisk
3. Install patched recovery image using fastbook [3]
4. Wipe device and Install LOS + GApps
5. Reboot to system => still says "Ramdisk: No"
What am I doing wrong? How did everyone else root their Note 8T?
[1] https://topjohnwu.github.io/Magisk/install.html
[2] https://download.lineageos.org/ginkgo
[3] https://wiki.lineageos.org/devices/ginkgo/install#installing-a-custom-recovery-using-fastboot
---
EDIT: I just found this: https://github.com/topjohnwu/Magisk/issues/3239 - does that mean it worked? Doesn't look it did...I don't think I have root
lueromat said:
I am trying to get Magisk to work on my Xiaomi Redmi Note 8T with Lineage OS, but the step where I am patching the boot.img is failing. I am using LOS recovery, and I followed the instructions provided by topjohnwu [1]: because the 8T doesn't appear to have ramdisk (I don't know what that means btw), I need to patch an image (my recovery image?) with the magisk app - this is what I did:
1. Install Magisk App and check status: "Ramdisk: No"
2. Download Lineage recovery image [2] and patch in Magisk
3. Install patched recovery image using fastbook [3]
4. Wipe device and Install LOS + GApps
5. Reboot to system => still says "Ramdisk: No"
What am I doing wrong? How did everyone else root their Note 8T?
[1] https://topjohnwu.github.io/Magisk/install.html
[2] https://download.lineageos.org/ginkgo
[3] https://wiki.lineageos.org/devices/ginkgo/install#installing-a-custom-recovery-using-fastboot
---
EDIT: I just found this: https://github.com/topjohnwu/Magisk/issues/3239 - does that mean it worked? Doesn't look it did...I don't think I have root
Click to expand...
Click to collapse
install OrangeFox recovery
rename Magisk22.APK to Magisk22.ZIP
install it like any zip in recovery
reboot
(i suggest you do a clean flash to avoid problems)
(yess, RN8 have ramdisk but that's not required for root to work)
After clean flashing the official LOS 17.1, I re-tried to install Magisk giving it every request permission and following steps detailed above by loopypalm but (as before) I'm still seeing "Requires Additional Setup" followed by a "Setup failed" message...
I unlocked the phone recently, set up the latest OrangeFox recovery and flashed new RN8 global firmware v12.0.4.0, Lineage v17.1 nightly 20210405 and pico OpenGapps 20210406. The phone isn't even encrypted (i.e., I've set no fingerprint, pin or pattern).
I tried removing Magisk v22 with the official uninstaller and downgrading to v21.4 with the same result. Then I used the Manager facilities to upgrade both Manager and the underlying Magisk, but still no dice.
I'm scratching my head here about what else to try. Something I noticed that may or may not be related is, while it was working alright before I started setting up Magisk, advanced reboot became really sluggish and failed to reboot to recovery after this (only buttons work).
I'll keep searching and will maybe try a different ROM but this is a real bummer.
loopypalm said:
install OrangeFox recovery
rename Magisk22.APK to Magisk22.ZIP
install it like any zip in recovery
reboot
(i suggest you do a clean flash to avoid problems)
(yess, RN8 have ramdisk but that's not required for root to work)
Click to expand...
Click to collapse
after installing LOS, GApps and Magisk in OrangeFox, and then booting to system, the phone is stuck at the sim PIN entry - I can enter it, but it doesn't advance afterwards. this is what I did:
1. Install TWRP
2. Use TWRP to install OF
3. in OF, wipe everything except usbstorage and sdcard
4. create installation queue with latest LOS, GApps, and Magisk, and install
5. boot to system => stuck at sim PIN entry
any suggestions?
i have the same with the latest LOS 17.1 tried also 21.4 both not working, I flashed again without Magisk so far
cali.s said:
i have the same with the latest LOS 17.1 tried also 21.4 both not working, I flashed again without Magisk so far
Click to expand...
Click to collapse
I hit "Emergency", went back to the PIN mask, and then it would accept my SIM pin. So far so good...
pnin said:
After ...
Click to expand...
Click to collapse
please follow instruction and do not add/remove a step
-flash OFox (if you already have it = no need)
-reboot to recovery
-flash latest A10 stable FW RN8 Ginkgo / RN8T Willow
-format data (not wipe) (this will erase internal storage!)
-reboot to recovery
-wipe 5 (cache/dalvik/system/vendor/data)
-flash the rom you want
-flash kernel (if you have any)
-flash DFE
-format data again
-reboot to recovery
-reboot to system
-reboot to recovery and flash magisk
done
lueromat said:
after installing LOS, GApps and Magisk in OrangeFox, and then booting to system, the phone is stuck at the sim PIN entry - I can enter it, but it doesn't advance afterwards. this is what I did:
1. Install TWRP
2. Use TWRP to install OF
3. in OF, wipe everything except usbstorage and sdcard
4. create installation queue with latest LOS, GApps, and Magisk, and install
5. boot to system => stuck at sim PIN entry
any suggestions?
Click to expand...
Click to collapse
i heard about that bug
remove the pin from the sim in another phone
loopypalm said:
-flash the rom you want
-flash kernel
-flash DFE
Click to expand...
Click to collapse
The ROM I want is the official Lineage -- I'm no hardcore flasher, just want to take it easy with a tried and tested custom ROM. But the kernel and DFE got me stumped: do I really need them? Which ones?
pnin said:
The ROM I want is the official Lineage -- I'm no hardcore flasher, just want to take it easy with a tried and tested custom ROM. But the kernel and DFE got me stumped: do I really need them? Which ones?
Click to expand...
Click to collapse
i think you should try RRos (it's based on LOS and updated)
i said kernel, so if you have one in mind, that's the step (correct order) you flash it in
(people use "sixteen" for battery,or default "quicksilver" ,or ryzen or ...)
DFE is "Disables dm-verity, forced encryption"
lueromat said:
after installing LOS, GApps and Magisk in OrangeFox, and then booting to system, the phone is stuck at the sim PIN entry - I can enter it, but it doesn't advance afterwards. this is what I did:
1. Install TWRP
2. Use TWRP to install OF
3. in OF, wipe everything except usbstorage and sdcard
4. create installation queue with latest LOS, GApps, and Magisk, and install
5. boot to system => stuck at sim PIN entry
Click to expand...
Click to collapse
lueromat said:
I hit "Emergency", went back to the PIN mask, and then it would accept my SIM pin. So far so good...
Click to expand...
Click to collapse
so in the end this worked, LOS + root, and no complaints so far.
other users were also successful with not sticking to the official magisk installation instruction, but just flashing the zip in recovery: https://github.com/topjohnwu/Magisk/issues/3239#issuecomment-816164610
guess this is the way to go for willow
loopypalm said:
please follow instruction and do not add/remove a step
-flash OFox (if you already have it = no need)
-reboot to recovery
-flash latest A10 stable FW RN8 Ginkgo RN8T Willow
-format data (not wipe) (this will erase internal storage!)
-reboot to recovery
-wipe 5 (cache/dalvik/system/vendor/data)
-flash the rom you want
-flash kernel (if you have any)
-flash DFE
-format data again
-reboot to recovery
-reboot to system
-reboot to recovery and flash magisk
done
Click to expand...
Click to collapse
Hi loopypalm, only for curiosity: is there a reason why to wipe /data "again" in step 6 after having formatted /data already in step 4? And furthermore why to format /data for a second time in step 10? What happens to /data after the first formatting that makes these steps recommendable? Thx if you find a minute to explain...
HI , this is what devs been recommending since the beginning (on ginkgo)
Uluru25 said:
is there a reason why to wipe /data "again" in step 6 after having formatted /data already in step 4?
Click to expand...
Click to collapse
no
Uluru25 said:
And furthermore why to format /data for a second time in step 10? What happens to /data after the first formatting that makes these steps recommendable?
Click to expand...
Click to collapse
me personally i don't think formatting data a 2nd time is necessary
but as for what i think could be the reason is after formatting data you will get a "raw" file system , so the OS will choose the situable file system for it "EXT2" or "EXT4" or ...
that's why sometimes the system wont boot even if you flash DFE
(which (i think) is the case on all ports like ONEUI or OOS ...)
loopypalm said:
please follow instruction and do not add/remove a step
-flash OFox (if you already have it = no need)
-reboot to recovery
-flash latest A10 stable FW RN8 Ginkgo / RN8T Willow
-format data (not wipe) (this will erase internal storage!)
-reboot to recovery
-wipe 5 (cache/dalvik/system/vendor/data)
-flash the rom you want
-flash kernel (if you have any)
-flash DFE
-format data again
-reboot to recovery
-reboot to system
-reboot to recovery and flash magisk
done
Click to expand...
Click to collapse
loopypalm,
- Orange Fox, should "Allow modifications" be enabled OR "keep read-only"?
- will latest A11 (anrdoid 11) stable FW (Firmware) also be ok, or is this guide specifically for A10?
Other notes of mine:
- OrangeFox requires device to be unlocked with MiFlash unlocking software first. (It's a type A device it seems, NOT a/b)
jddcef said:
- Orange Fox, should "Allow modifications" be enabled OR "keep read-only"?
Click to expand...
Click to collapse
allow Read & write
jddcef said:
- will latest A11 (anrdoid 11) stable FW (Firmware) also be ok, or is this guide specifically for A10?
Click to expand...
Click to collapse
this guide is for all rom, if you are using A11 then use A11 FW
jddcef said:
- OrangeFox requires device to be unlocked with MiFlash unlocking software first. (It's a type A device it seems, NOT a/b)
Click to expand...
Click to collapse
The Ofox i linked is for Ginkgo/Willow if you have this device + unlocked BL = just flash

How To Guide [GUIDE] [HOW TO INSTALL MIUI MOD OG IN Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40]

This post is on how to install MIUI MOD OG
Features -
1. BGMI / PUBG 90fps available
2. 90hz is there in refresh rate
3. cool animations
4. Totally debloated
Note -
1. Take backup of all your files because this process will wipe your data
2. follow the steps properly
Required -
1. unlocked boot loader
2. twrp vasis/nebrassy(offical)/commando
Steps
1. Download the rom from below
2. boot into twrp
3. go to install and select the rom and flash it ( 3 to 4 minutes to flash )
4. go to wipe > format data > yes
that's all your done with the installation first boot may take longer
Optional
1. flash magisk apk in twrp for root access
Download links
1 . TWRP -
https://twrp.me/xiaomi/xiaomipocof3.html
2. MIUI MOD -
Search in Google you will get

Categories

Resources