[ASK] Rooting Redmi 6a without TWRP / using Magisk Boot Image Patching - Xiaomi Redmi 6A Questions & Answers

I was read https://topjohnwu.github.io/Magisk/install.html. That link describe how to install Magisk in our device in few ways. I was interested "Boot Image Patching" section that tell us about rooting device without TWRP.
Before this, I have 5 redmi devices and 3 of it were rooted-well via TWRP. 1 bricked (totally bricked) :laugh: and 1 still un-rooted (Redmi 6A-cactus).
My spec of Redmi 6A are:
Security Level Patch: 2019-03-01
MIUI Version: Global Stable 10.2.8.0 (oCBMIXM)
Unlocked: False (i know that i should unlocked it later, i still waiting my 360 hours )
RAM: 2GB
Storage: 16GB
Since i found that link, i still wondering and keep searching about: "is anybody succesfull root their device (especially Redmi 6A with same spec above) with "Boot Image Patching" way?
if any, please let me know. i just want to hear their review and (of course) their experience.
thanks

Yes, i got it working but i still recommend the TWRP method, but if you're still interested, be careful, don't disable the forceencrypt while patching, you can disable dm-verity but DO NOT disable the forceencrypt or you'll lose IMEI/Baseband.
Anyway, this is the patched_boot.img i've used (extracted from the latest V10.2.8.0.OCBMIXM rom).
https://www80.zippyshare.com/v/2zWEXIcM/file.html
Repeating, i still prefer the TWRP method, be careful.

jonaaa said:
Yes, i got it working but i still recommend the TWRP method, but if you're still interested, be careful, don't disable the forceencrypt while patching, you can disable dm-verity but DO NOT disable the forceencrypt or you'll lose IMEI/Baseband.
Anyway, this is the patched_boot.img i've used (extracted from the latest V10.2.8.0.OCBMIXM rom).
https://www80.zippyshare.com/v/2zWEXIcM/file.html
Repeating, i still prefer the TWRP method, be careful.
Click to expand...
Click to collapse
Nice... i'll try that soon when my 360 hours run out..
thanks.

Hi @jonaaa, its me again..
i was success root my 6a with patched_boot.img. but i've got problem when i installing systemless xposed. Xposed Zip successfully installed, but when i tried to install Xposed Manager then reboot, i got stuck in mi logo. i've been trying for 3 times and getting frustrated
now i decided to install twrp and (again) i got stuck in encryption problem. most of google result said that data partition should be formatted and that dont make any sense for me. how could i formatting data partition while that partition is untouchable.
so i wanna ask you: how you get rid from twrp encrypt-decrypt problem?

adista said:
Hi @jonaaa, its me again..
i was success root my 6a with patched_boot.img. but i've got problem when i installing systemless xposed. Xposed Zip successfully installed, but when i tried to install Xposed Manager then reboot, i got stuck in mi logo. i've been trying for 3 times and getting frustrated
now i decided to install twrp and (again) i got stuck in encryption problem. most of google result said that data partition should be formatted and that dont make any sense for me. how could i formatting data partition while that partition is untouchable.
so i wanna ask you: how you get rid from twrp encrypt-decrypt problem?
Click to expand...
Click to collapse
Forget it..
My step was wrong. i was ignoring "fastboot format userdata" command in first and install twrp directly...
thanks for your suggestion :good:

adista said:
Forget it..
My step was wrong. i was ignoring "fastboot format userdata" command in first and install twrp directly...
thanks for your suggestion :good:
Click to expand...
Click to collapse
hi
can share your steps in detail, from beginning to end
Sent from my Redmi 6A using Tapatalk

ahhl said:
hi
can share your steps in detail, from beginning to end
Sent from my Redmi 6A using Tapatalk
Click to expand...
Click to collapse
i dont recommend to use my step, because right now i even dont have twrp in my redmi 6a. In other word, im failed.
UBL
Enabling Developer Option
Entry Fastboot mode
fastboot devices (to check it's connected well with pc)
fastboot format userdata
fastboot flash recovery twrp-3.3.0.0.img
fastboot boot twrp-3.3.0.0.img
For a while, i was able to entry twrp without any password asked and installing magisk (magisk-19.0.zip) smoothly.
But, when i rebooting, i've got stuck at mi logo (i've been wait more than 40 minutes and still at mi logo). When i tried to Volume Up + Power, just nothing happened but back to mi logo and stuck again (and more 40 minutes :silly:).
and finally i did install fastboot-rom from scratch... :laugh::laugh: and since that, twrp wont installed on my redmi even i flash fastboot-rom again and again. Till now i still wondering why and not found the answer yet.

adista said:
i dont recommend to use my step, because right now i even dont have twrp in my redmi 6a. In other word, im failed.
UBL
Enabling Developer Option
Entry Fastboot mode
fastboot devices (to check it's connected well with pc)
fastboot format userdata
fastboot flash recovery twrp-3.3.0.0.img
fastboot boot twrp-3.3.0.0.img
For a while, i was able to entry twrp without any password asked and installing magisk (magisk-19.0.zip) smoothly.
But, when i rebooting, i've got stuck at mi logo (i've been wait more than 40 minutes and still at mi logo). When i tried to Volume Up + Power, just nothing happened but back to mi logo and stuck again (and more 40 minutes :silly:).
and finally i did install fastboot-rom from scratch... :laugh::laugh: and since that, twrp wont installed on my redmi even i flash fastboot-rom again and again. Till now i still wondering why and not found the answer yet.
Click to expand...
Click to collapse
Use the TWRP-1020 instead, it works much better.

hi, i followed this video and i succes for install twrp https://www.youtube.com/watch?v=522RzZ7_uRM&t=254s

jonaaa said:
Yes, i got it working but i still recommend the TWRP method, but if you're still interested, be careful, don't disable the forceencrypt while patching, you can disable dm-verity but DO NOT disable the forceencrypt or you'll lose IMEI/Baseband.
Anyway, this is the patched_boot.img i've used (extracted from the latest V10.2.8.0.OCBMIXM rom).
https://www80.zippyshare.com/v/2zWEXIcM/file.html
Repeating, i still prefer the TWRP method, be careful.
Click to expand...
Click to collapse
My IMEI/Baseband are gone, when I install xposed framework and reboot it's stuck in MI logo, and I tried factory reset from my original MI recovery, it's fix the bootloop but my IMEI/Baseband are gone.... Do you know how to fix it? I spend my time searching to fix it and no result. And I tried flash stock ROM too and no result. Hope you know how fix my issue, thanks!!

whothehellami said:
My IMEI/Baseband are gone, when I install xposed framework and reboot it's stuck in MI logo, and I tried factory reset from my original MI recovery, it's fix the bootloop but my IMEI/Baseband are gone.... Do you know how to fix it? I spend my time searching to fix it and no result. And I tried flash stock ROM too and no result. Hope you know how fix my issue, thanks!!
Click to expand...
Click to collapse
Someone said to encrypt the data on settings, i don't know how though, if you fix it, next time, don't disable the forceencrypt.

Can you post questions in the questions and answers section next time?

i was looking around on how to flash twrp but theres no clear guide on how to do it. i keep noticing people said dont disable verity, they didn't mentioned where and when not to disable it.
because after we flash twrp, we boot to twrp. then what?
Sent from my vivo 1723 using Tapatalk

ahhl said:
i was looking around on how to flash twrp but theres no clear guide on how to do it. i keep noticing people said dont disable verity, they didn't mentioned where and when not to disable it.
because after we flash twrp, we boot to twrp. then what?
Sent from my vivo 1723 using Tapatalk
Click to expand...
Click to collapse
Uhh... just flash the TWRP and you're done.
The dm-verity removal is necessary if you want to install any GSI.

jonaaa said:
Uhh... just flash the TWRP and you're done.
The dm-verity removal is necessary if you want to install any GSI.
Click to expand...
Click to collapse
well i got this issue after flash twrp. after boot and reboot
i got this annyoing android system error, contact manufacturer for detail.

I have a similar problem
I was rooting my redmi 6a and now its bricked
First i intall the twrp, then i flash the Magisk with DisableEncryption, the first boot work fine, i update the magisk app and the new version isnt compatible with the magisk installed
Well i repeat the steps and then i lost the signal, in that moment i didnt know it is the IMEI lost, then i try to install Lineage OS 15.1 GSI for Redmi6a cause i think that is the solution
but the system dont boot, only boot the Xiaomi Tittle with "unlocked" (I unlock the phone before) and then get me to TWRP
Im only one with this problem?
I try use the MiFlashTool for flash the stock rom but not work, now im trying with MiFlashTool flash the MIUI9 and MIUI10.2 and other versions
I think, the problem maybe is the Boot.img
(Sorry for my bad English)
Edit-
I dont have any backup lol
---------- Post added at 02:23 AM ---------- Previous post was at 02:01 AM ----------
jonaaa said:
Uhh... just flash the TWRP and you're done.
The dm-verity removal is necessary if you want to install any GSI.
Click to expand...
Click to collapse
¿Can you share your correct steps to have the Lineage OS 15.1 in Redmi6A Please?

ahhl said:
well i got this issue after flash twrp. after boot and reboot
i got this annyoing android system error, contact manufacturer for detail.
Click to expand...
Click to collapse
This "contact manufacturer" error happens when you disable dm-verity, you can install Magisk without disabling it.

whothehellami said:
My IMEI/Baseband are gone, when I install xposed framework and reboot it's stuck in MI logo, and I tried factory reset from my original MI recovery, it's fix the bootloop but my IMEI/Baseband are gone.... Do you know how to fix it? I spend my time searching to fix it and no result. And I tried flash stock ROM too and no result. Hope you know how fix my issue, thanks!!
Click to expand...
Click to collapse
Sorry for late post
Just make sure that you flash Fastboot ROM, not just STOCK ROM. I did that last time when my IMEI/Baseband are gone. Of course it will wipe all of your data. Just be prepare for it.. :laugh:

davidhozic said:
Can you post questions in the questions and answers section next time?
Click to expand...
Click to collapse
Ups sorry.. i didnt notice that is exists :silly:
No, it wasnt like that :laugh:,, actually i did confused where should i put this question, because in Question & Answers (for me) the topic just too general and i was thinking that my question (maybe) still in development because i didnt found that in Question & Answer...
All my fault, Sorry again,

jonaaa said:
Use the TWRP-1020 instead, it works much better.
Click to expand...
Click to collapse
that just un-official TWRP, right??
i will try that in this weekend. Last time i remember that i can not boot into twrp. Till now, my devices still unrooted. I flash it back to stock ROM. But, when OTA update notification comes and reboot for installing, it give me bootloop into twrp (not to system), and that's mean my TWRP still inside i just cannot boot into.
so, i'll try that TWRP-1020 this weekend. Thanks.

Related

[Solved!] Blu Life One X2 problem with flashing ROM (Failed to read command: Success)

Hello everyone. I started this thread because I don't think I've seen anything with this issue on my specific phone on this forum. Apologies if this has been discussed before.
Anyway, I'm having issues installing a ROM with adb sideload on TWRP recovery.
I got the ROM and the recovery image from blox2.com (I would post the links but apparently the forum doesn't allow me to...)
Everything works fine, I'm able to boot into TWRP recovery and inititiate the adb sideload, but the process gets stuck when it reaches 28% and throws the error message:
serving: 'BLOX2core-v1.1.1-31217.zip' (~28%) * failed to read command: Success
Click to expand...
Click to collapse
In case this has anything to do with ADB version, I'm using Debian and my adb version is 1:7.0.0+r1-4
If you need any more info, please ask.
Thanks in advance.
Ok, an update.
I now tried installing the ROM through TWRP's own installing option, but TWRP crashes and reboots a couple of seconds after the install is initiated.
max_157 said:
Ok, an update.
I now tried installing the ROM through TWRP's own installing option, but TWRP crashes and reboots a couple of seconds after the install is initiated.
Click to expand...
Click to collapse
Make sure you have MTP turned off. Also DM verity and force encryption needs to be disabled
ieatgravity said:
Make sure you have MTP turned off. Also DM verity and force encryption needs to be disabled
Click to expand...
Click to collapse
How do I disable MTP? I can't get android to boot. Can you disable it from TWRP or is it done from a fastboot/adb command?
I figured it out. I disabled MTP from the mount menu and disabled DM-Verify and encryption from the Advanced menu... same results
max_157 said:
How do I disable MTP? I can't get android to boot. Can you disable it from TWRP or is it done from a fastboot/adb command?
Click to expand...
Click to collapse
Flash supersu then flash the ROM
ieatgravity said:
Flash supersu then flash the ROM
Click to expand...
Click to collapse
OK. I tried
1. Booting into TWRP
2. Selected Install
3. Selected UPDATE-SuperSU-v2.65-20151226141550.zip
It crashed after a couple of seconds.
Tried with MTP disabled and DM-verity and encryption disabled.
max_157 said:
OK. I tried
1. Booting into TWRP
2. Selected Install
3. Selected UPDATE-SuperSU-v2.65-20151226141550.zip
It crashed after a couple of seconds.
Tried with MTP disabled and DM-verity and encryption disabled.
Click to expand...
Click to collapse
I'm would assume the bootloader was unlocked? Are you able to make a nandroid backup? And have you tried flashing twrp to the phone ?
Where do you have the files located at? Is it on the SDcard or on the flash drive?
does this work?
fastboot oem unlock
or
fastboot flashing unlock
Should also erase/wipe everything except system/recovery/boot...
Also hope you made a nandroid backup first with the fastboot boot recovery.img, then booting into TWRP and backup. to flash drive. Need MTP disabled for some to not reboot.
Also try with the new TWRP where the reboot has been fixed.. and which version 16/2 or 64/4 BLU X2 or mini?
ieatgravity said:
I'm would assume the bootloader was unlocked? Are you able to make a nandroid backup? And have you tried flashing twrp to the phone ?
Click to expand...
Click to collapse
The bootloader was indeed unlocked.
I haven't tried flashing TWRP to the phone. Would this make it work? I'm kind of scared of having a recovery image that crashes whenever I try stuff. Can I restore the stock recovery in case anything happens?
AlienTeck said:
Where do you have the files located at? Is it on the SDcard or on the flash
drive?
Click to expand...
Click to collapse
Internal flash drive.
AlienTeck said:
does this work?
fastboot oem unlock
or
fastboot flashing unlock
Click to expand...
Click to collapse
Yup! It works. It says it's already unlocked.
AlienTeck said:
Should also erase/wipe everything except system/recovery/boot...
Also hope you made a nandroid backup first with the fastboot boot recovery.img, then booting into TWRP and backup. to flash drive. Need MTP disabled for some to not reboot.
Click to expand...
Click to collapse
I did wipe cache and everything else, and had MTP disabled.
AlienTeck said:
Also try with the new TWRP where the reboot has been fixed.. and which version 16/2 or 64/4 BLU X2 or mini?
Click to expand...
Click to collapse
64/4 BLU X2 version.
I can't find BLU Life One X2 on the official TWRP website, the only version I tried was on blox2.com, which I think is a modified version of 3.0.2-0.
Problem fixed!
I flashed the stock firmware using QFIL 1.0.2. Thanks so much to everyone who helped!
QFIL
I got the QFIL rom from blox2.com
When you say fixed, do you mean TWRP is now working? Or that you were able to flash the stock back? Did you already take the BLOX2 OTA update?
Trying to figure out if the update had anything to do with this default rebooting on /system being made writable.. Also did you make a nandroid backup?
QFIL is now on 1.0.0.3
AlienTeck said:
When you say fixed, do you mean TWRP is now working? Or that you were able to flash the stock back? Did you already take the BLOX2 OTA update?
Trying to figure out if the update had anything to do with this default rebooting on /system being made writable.. Also did you make a nandroid backup?
QFIL is now on 1.0.0.3
Click to expand...
Click to collapse
I was able to flash the stock back, but via QFIL, not TWRP. The rebooting issue still persists.
I didn't make a nandroip backup, will get to it now.
Oh, I'm actually now trying to fix the rebooting issue. I think it might be a write protection, like the one HTC has. Example: https://www.youtube.com/watch?v=KV3YaMBnEYI
I really really need to be able to modify the system partition because the phone comes with a lot of crawpare and even some malware (https://www.cyberscoop.com/android-malware-china-huawei-zte-kryptowire-blu-products/)
FotaProvider installs some apps without your consent like Uber and some games and supposedly sends some info, too.
When I try to remove it with root uninstallers, the phone reboots. I though I had gotten rid of this issue by reflashing the ROM but apparently not...
I only flashed TWRP to cache and booted to it and flashed super SU, then used root essentials to remove some of the bloatware. But noticed supersu was gone now. It was able to remove or disable some of the stuff without rebooting and then later manually rebooting it. I disabled the apps and then removed it, so I think even the update now has the stuff but still disabled. The update also supposedly removes one of the apps that sent data back.
It rebooted at first until I saw that I had to disable MTP in TWRP options. I have not tried the recent TWRP, I was still using the one under development in the beginning.
AlienTeck said:
I only flashed TWRP to cache and booted to it and flashed super SU, then used root essentials to remove some of the bloatware. But noticed supersu was gone now. It was able to remove or disable some of the stuff without rebooting and then later manually rebooting it. I disabled the apps and then removed it, so I think even the update now has the stuff but still disabled. The update also supposedly removes one of the apps that sent data back.
It rebooted at first until I saw that I had to disable MTP in TWRP options. I have not tried the recent TWRP, I was still using the one under development in the beginning.
Click to expand...
Click to collapse
How do I install this update?
Also, I tried removing some system apps with Root Essentials but it still rebooted.
max_157 said:
How do I install this update?
Also, I tried removing some system apps with Root Essentials but it still rebooted.
Click to expand...
Click to collapse
For the time being you need to boot into TWRP and manually remove apps using ADB. We are currently working on patching the kernel to allow /system to be mounted RW sAo that you can use apps to remove system apps. In the mean time use Blox2core as it has been fully debloated.
ieatgravity said:
For the time being you need to boot into TWRP and manually remove apps using ADB. We are currently working on patching the kernel to allow /system to be mounted RW sAo that you can use apps to remove system apps. In the mean time use Blox2core as it has been fully debloated.
Click to expand...
Click to collapse
Sounds great! Looking forward to it.
I can't install Blox2core since TWRP reboots when I try to install it or even wipe the /system partition though. Some people mentioned TWRP 3.0.3 fixed this issue.
max_157 said:
Sounds great! Looking forward to it.
I can't install Blox2core since TWRP reboots when I try to install it or even wipe the /system partition though. Some people mentioned TWRP 3.0.3 fixed this issue.
Click to expand...
Click to collapse
We have a new tool that you can use to flash TWRP and root. All auto matic. Give it a try and let me know if it works for you.
[TOOL]Draco’s Blox2Autoroot - http://wp.me/p8gYUZ-5x
Afterwards you'll be able to flash Blox2core
Also I was unaware of this TWRP 3.0.3 for the blox2. The only one that has been ported has been 3.0.2 last I checked.
I would say disable MTP in TWRP options and developer options as well. dirst disabled it in developer options before I found out that did not stop the kernel rebooting the phone when /system became writable. I had not installed the oct update BLU sent out and maybe that makes a difference? Although the QFIL should also have the original boot/kernal image? so not sure what is going on..
If that dont stop it we need a new kernal.. I think I have the original kernal/boot saved. If anyone wants to see if that fixed the reboot.
twrp gave a MD5 of it..
152479bd51790d374885cc1a847e4c31 boot.emmc.win
Seems I need a faster course in android.. A few months ago I thought an android was some guy in dr who.
---------- Post added at 12:08 PM ---------- Previous post was at 11:46 AM ----------
The OTA update showed up one day and it installed it.. For the longest time I ignored it but I suppose someone hit ok on it.. But SuperSU seemed to have vanished before that I think. Spending time on 2 other problem phones so this one is not a priority since it works very well comparatively. I love it though it is heavy as a brick. Even my N5x case fits with a little coaxing. Although the DPI setting is set much higher like for a HD screen and not FHD. Maybe we can change it in build.prop to fix it. The N5x has much smaller icons and letters and actually fit 5 icons to a row although they both have the same density screen.. BLU has much better touch though and is far brighter and richer.
---------- Post added at 12:30 PM ---------- Previous post was at 12:08 PM ----------
The 2 boot images ARE different.. But you should first try to write a backup back to itself and see if there are problems and guess I dont have the previlage of attaching files just yet on here.
max_157 said:
Problem fixed!
I flashed the stock firmware using QFIL 1.0.2. Thanks so much to everyone who helped!
I got the QFIL rom from blox2.com
Click to expand...
Click to collapse
Could you share the link to the stock ROM you used with QFIL?
Thanks!

Again on recovery, root, etc.

Hi to all. I'm new in Honor world and I've stopped my Android experience with KitKat so I'm a little bit confused ...
I've read several guides (on XDA too) that that three steps to obtain root are unlock bootloader, flash TWRP via ADB and then install Magisk or SuperSU via TWRP. But in the thread on TWRP is clearly written that to install Magisk decryption is needed and to have decryption we must flash a kernel with encryption disabled in fstab. But no guide says anything about this step. Can someone explain me how encryption/decryption work doing a standard installation of TWRP ? Is needed a flash of a modified kernel ? And where find it ?
And another question (if it's not too much ). Since I don't need to install custom rom (I want root only to use some apps like Titanium) how can I make a backup of stock rom, boot.img, efs partition and all that can be useful to restore phone to the starting point if, by chance, I need Huawei warranty ?
Thanks a lot
Hi, apparently there's a way to get root on an encrypted system. Follow the rebrand guide and then flash supersu in TWRP via ADB sideload. It worked for me and a few others, there is no comment from the developers as of right now.
So basically in short follow this guide until you are finished with the TWRP section:
https://forum.xda-developers.com/honor-9/how-to/one-guide-recovery-os-roms-t3661829
Then
- enter twrp
- adb sideload supersu
Afterwards follow the "rooting!" section with point 2
Thank for your answer... I'd like to try to install Magisk instead of SuperSU. In several places is written that this should be right. I'll try....
unvisigoth said:
Thank for your answer... I'd like to try to install Magisk instead of SuperSU. In several places is written that this should be right. I'll try....
Click to expand...
Click to collapse
The method is also working fine with Magisk. Let me know if you need help
zxz0O0 said:
The method is also working fine with Magisk. Let me know if you need help
Click to expand...
Click to collapse
Finally done with a couple of hours of panic. This is the story if can be useful to someone...
Unlock bootloader....done TWRP install... done. Copy magisk (apk and zip) on phone than install apk without opening it. Reboot to recovery wipe all, factory reset. Trying to boot.....BOOTLOOP But I don't have installed Magisk zip. Only apk without opening it.
Nothing to do. Bootloop and then erecovery. I try to restore the backups previously done with TWRP. I restore boot and system partition. All wipes ...no luck. I don't know what has happened. While downloading full firmware to try to reinstall it I try to install magisk.zip. Install via TWRP. All wipes and then magically (it's such a case ) phone boots. Powered off and on several times no problem. Root (verified with root checker) ok.
I habe b100 release but I don't think to update to b130. I wait for Oreo...
The only two things that I can say are these: first TWRP even after flashing magisk gave an error (unable to mount system). Two while installing magisk it seems that magisk itself has patched something.
If someone has an explanation is welcome...
unvisigoth said:
Finally done with a couple of hours of panic. This is the story if can be useful to someone...
Unlock bootloader....done TWRP install... done. Copy magisk (apk and zip) on phone than install apk without opening it. Reboot to recovery wipe all, factory reset. Trying to boot.....BOOTLOOP But I don't have installed Magisk zip. Only apk without opening it.
Nothing to do. Bootloop and then erecovery. I try to restore the backups previously done with TWRP. I restore boot and system partition. All wipes ...no luck. I don't know what has happened. While downloading full firmware to try to reinstall it I try to install magisk.zip. Install via TWRP. All wipes and then magically (it's such a case ) phone boots. Powered off and on several times no problem. Root (verified with root checker) ok.
I habe b100 release but I don't think to update to b130. I wait for Oreo...
The only two things that I can say are these: first TWRP even after flashing magisk gave an error (unable to mount system). Two while installing magisk it seems that magisk itself has patched something.
If someone has an explanation is welcome...
Click to expand...
Click to collapse
So do you have some step-by-step instructions for someone who wants to unlock and root the phone with magisk?
shiboby said:
So do you have some step-by-step instructions for someone who wants to unlock and root the phone with magisk?
Click to expand...
Click to collapse
Here what I have done:
Unlock bootloader
install adb drivers (find something that is right for your PC. For example minimal ADB found on XDA weren't suitable for me. Google adb drivers...). Open a command windows (shift+right click). If typing "adb devices" your phone is found that's ok
Enable usb debugging and oem unlock (or in other words disable FRP, factory reset protection)
Put the phone in fastboot mode ("adb reboot bootloader"). If all ok typing "fastboot devices" your phone is found
Type "fastboot oem unlock xxxxxxxx" (xxxxxxxx is the code provided by Huawey)
Bootloader unlocked
Flash TWRP
Download TWRP recovery for Honor 9 (link found on other thread on this forum)
Put the phone in fastboot mode
Type "fastboot flash recovery xxxxx.img" (where xxxx.img is the recovery downloaded)
Reboot phone directly in Recovery to avoid erecovery overwrite TWRP. Booting on TWRP let TWRP patch to avoid erecovery booting
Now here I've had some issues as said (read previous post). My tip is the following:
after rebooting in TWRP make all wipes then reboot again in TWRP
Install Magisk.zip (for me download here https://geekaxe.com/root-honor-9-twrp-bootloader-unlocking/)
Reboot recovery
All wipes
Reboot to system
If it's all OK you can install magisk.apk and you are rooted
I suggest after flashing TWRP to make backup of all partitions on external SD (for some reasons, maybe encryption, backup on internal storage gives error). Again I suggest to copy all files that you need (i.e. magisk files) on external sd before starting all.
Pay attention that if you update firmware after this procedure I think that you must repeat all. For me I remain on original firmware found on phone (B100). B130 seems to have some bugs, B120 doesn't seem improve much. Moreover all releases are 7.0 based. I wait for Oreo, hopefully in some custom rom!
To add to this, a bootloop or two might be normal. Let it sit for a few minutes before considering re-flashing everything.
Thanks for your guide!
Zuzler said:
To add to this, a bootloop or two might be normal. Let it sit for a few minutes before considering re-flashing everything.
Thanks for your guide!
Click to expand...
Click to collapse
You're right. But after 20 minutes of bootlops I've chosen another way....:laugh::laugh:
unvisigoth said:
You're right. But after 20 minutes of bootlops I've chosen another way....:laugh::laugh:
Click to expand...
Click to collapse
So is it fixed?
Sent from my Honor 8 Pro using XDA Labs
adriansticoid said:
So is it fixed?
Sent from my Honor 8 Pro using XDA Labs
Click to expand...
Click to collapse
Yes sure. As said previously installation of magisk.zip fixed the bootloop problem. I think (but I could be wrong) that installation of TWRP corrupted the boot partition and magisk fixed it. But it's only an hypothesis...
unvisigoth said:
Yes sure. As said previously installation of magisk.zip fixed the bootloop problem. I think (but I could be wrong) that installation of TWRP corrupted the boot partition and magisk fixed it. But it's only an hypothesis...
Click to expand...
Click to collapse
Observe and be careful man.
Sent from my Honor 8 Pro using XDA Labs
unvisigoth said:
Yes sure. As said previously installation of magisk.zip fixed the bootloop problem. I think (but I could be wrong) that installation of TWRP corrupted the boot partition and magisk fixed it. But it's only an hypothesis...
Click to expand...
Click to collapse
Which TWRP version did you use?
I had a similar problem after formatting all data with the OpenKirin TWRP 3.1.1 Perhaps its an issue with this TWRP release?
I was able to recover in similar circumstances by flashing a stock boot.img over fastboot. Based on this, it's looking like Magisk is really the way to go for rooting atm. Making sure to pull my twrp backup with adb this time though.
If I'm lucky enough to install magisk and not get a bootloop the safetynet always fails. Anyone got a valid method of actually getting magisk working fully?

How to fix device stuck at boot screen?

So recently I unlocked the bootloader of my Redmi Note 5 and flashed TWRP to it. When I boot to TWRP, they asked me for a decryption password, but I don't think I encrypted my device. I started to feel something's wrong. I pressed cancel then rebooted my phone, but it is stuck on the MI logo. What should I do?
Flash lazyflasher or magisk. It should boot normally again.
jes0411 said:
Flash lazyflasher or magisk. It should boot normally again.
Click to expand...
Click to collapse
Thank you so much, it worked! I was nothing but hopeless before you replied
nabilmuafa said:
Thank you so much, it worked! I was nothing but hopeless before you replied
Click to expand...
Click to collapse
How to flash the lazyflasher. could you please tell me the detailed steps on how to resolve this issue
manojsv19 said:
How to flash the lazyflasher. could you please tell me the detailed steps on how to resolve this issue
Click to expand...
Click to collapse
It's a zip posted in several threads in the forum.
Just install it with recovery.
manojsv19 said:
How to flash the lazyflasher. could you please tell me the detailed steps on how to resolve this issue
Click to expand...
Click to collapse
You could find the file needed in https://github.com/jcadduono/lazyflasher/ . If you have the exact same issue as me, download and flash the no-verity-opt-encrypt branch (this branch will only patch the dm-verity and TWRP encryption, so if you have another issue, download another branch). The files in the zip was contained in a folder, so if you want to make the flashing work, make sure you move the files directly inside the zip file (not in a folder in a zip file). You could put the zip file in an OTG USB or in a MicroSD.
Sorry if you don't understand something, my English is still bad and I'm still learning.
Device stuck at mi logo screen
PLEASE HELP
My redmi note 5 (vince) was earlier on havoc os rom . Then i decided to install miui again through fastboot. I started installing using fastboot method but it said mismatching of image and device ....so i searched for this issue on xda
Someone already suggested to omit two lines that included“getvar” and try flashing again. I did the same. It flashed but didn't rebooted. Not even started. I took it to service center ....they opened it and when they came back with the phone....it was showing it's mi logo and was not going further..
So for now my phone is showing mi logo and is not going further ...please suggest something.

[AIO] Guide to Unlock bootloader , Flash TWRP and a Custom rom.

Unlocking Bootloader​1. Make sure you have a sim and active mobile data. Then go to about phone tap build number 7-8 times. After that go to advanced settings > developer options > turn on OEM unlocking and then check if this device is secure and click add account and device.
2. Download Mi unlock tool from here. Extract it and paste it in C:/unlock. or else your device won't be recognized for unlocking.
3. Open Mi unlock tool and then enter the Mi account which was on your device. Put your device in fastboot mode by pressing vol- and power and then connect to PC. Press unlock and if it tells you to wait you have no other option but to wait. If your mi flash tool shows connect your device even after you have connected it. Follow this guide here.
4. After you have unlocked your bootloader reboot your phone.
Flashing TWRP and Rooting via magisk​
1. Download this TWRP image here. Thanks to the original developer mauronofrio.
2. Download adb and fastboot tools here and install it.
3. Now put your phone in fastboot mode and connect it with your pc. Now where you have downloaded the TWRP file rename it to TWRP.img and open a CMD window there if you don't know how just google.
4. Type the following commands
1. fastboot devices
2. fastboot flash recovery TWRP.img
3. fastboot reboot recovery.
Click to expand...
Click to collapse
5. Your phone will boot into TWRP now. But TWRP will be overwritten by stock miui recovery to stop that you need to flash Magisk. Download this zip move it to internal storage then flash by tapping on install and swipe to flash. Reboot your device. Reboot to recovery again to check if TWRP is present.
Now your device is rooted
OR
Flash latest OrangeFox Recovery if you don't want magisk.
Flashing A rom
1. Download.
2. Flash.
3 Format Data.
Done
Feel free to ask any questions. And don't point a finger at me for messing your device.
My mi unlock tool says can't get info. I using Indian version miui 12
Thanks for the useful guide. I have a quick question, does this works with MIUI 12?
igeekyayush said:
My mi unlock tool says can't get info. I using Indian version miui 12
Click to expand...
Click to collapse
Sorry for late reply. Have you installed the drivers correctly? Try using another port in your pc or use this mi unlock tool version zip
Doombuggie85 said:
Thanks for the useful guide. I have a quick question, does this works with MIUI 12?
Click to expand...
Click to collapse
Yes, it does.
hello,
thanks for the reply sir. yes i've tired changing port, pc everything. today i've factory reset my phone and added mi account and now i'm getting 7 days wait time. let's see now
LoadOP2 said:
Sorry for late reply. Have you installed the drivers correctly? Try using another port in your pc or use this mi unlock tool version zip
Click to expand...
Click to collapse
igeekyayush said:
hello,
thanks for the reply sir. yes i've tired changing port, pc everything. today i've factory reset my phone and added mi account and now i'm getting 7 days wait time. let's see now
Click to expand...
Click to collapse
Okay keep the sim inserted and use the device for 7 days. And if it doesn't work try using older version of unlock tool.
Hi there!
Silly question: is it possible to install TWRP but keep the official ROM? (phone is unlocked)
_benedict_ said:
Hi there!
Silly question: is it possible to install TWRP but keep the official ROM? (phone is unlocked)
Click to expand...
Click to collapse
Flashing a custom rom is optional. You don't NEED to flash a rom to get TWRP...
---------- Post added at 06:48 PM ---------- Previous post was at 06:46 PM ----------
I've unlocked the bootloader using the unlock tool and waited for 7 days,
But i rooted the device using a different method where i patched a boot.img and flashed that to the device.
Will this method still work for me as I'm already rooted but just want TWRP so i can flash other ROMs.. The post says you have to flash magisk from the (temporary) TWRP for the TWRP to stay as the recovery..
Will the magisk on my phone and the magisk installed here collide?
I just want TWRP so i can switch to a custom rom, so any input is appreciated!!
_benedict_ said:
Hi there!
Silly question: is it possible to install TWRP but keep the official ROM? (phone is unlocked)
Click to expand...
Click to collapse
Skip the flashing a rom part and you will be good to go.
But i rooted the device using a different method where i patched a boot.img and flashed that to the device.
Will this method still work for me as I'm already rooted but just want TWRP so i can flash other ROMs.. The post says you have to flash magisk from the (temporary) TWRP for the TWRP to stay as the recovery..
Will the magisk on my phone and the magisk installed here collide?
I just want TWRP so i can switch to a custom rom, so any input is appreciated!!
Click to expand...
Click to collapse
You can flash twrp and then check if it persists. If not flash magisk again their is no thing as magisk colliding lol. Just make sure you flash a newer version. And if nothing works flash stock rom and then twrp.
If you have the stock boot IMG flash it and then intsall twrp and magisk.
smsry said:
Flashing a custom rom is optional. You don't NEED to flash a rom to get TWRP...
Click to expand...
Click to collapse
LoadOP2 said:
Skip the flashing a rom part and you will be good to go.
Click to expand...
Click to collapse
Haha, makes sense! Thank you for your answers
Nevermind.. i got it to work pretty easily..
I have twrp on this device and Pixel Experience ROM and it's working all fine..
But there's this one thing where when booting to recovery, it asks me to input a password for User(0) when i try to input anything it says password failed..
From reading the log, it says it's for decrypting data(8f I'm not mistaken)
Is this important? Do i need to decrypt it?
Currently the ROM works fine with no errors, so I'm not gonna bother, but would still like to know what this "decrypting" thing is..
smsry said:
Nevermind.. i got it to work pretty easily..
I have twrp on this device and Pixel Experience ROM and it's working all fine..
But there's this one thing where when booting to recovery, it asks me to input a password for User(0) when i try to input anything it says password failed..
From reading the log, it says it's for decrypting data(8f I'm not mistaken)
Is this important? Do i need to decrypt it?
Currently the ROM works fine with no errors, so I'm not gonna bother, but would still like to know what this "decrypting" thing is..
Click to expand...
Click to collapse
Yes, If you use a lock screen enter that password it will be decrypted. You will have to format data if you decide to flash any other rom anyway.
flashed twrp but not able to boot into recovery.
igeekyayush said:
flashed twrp but not able to boot into recovery.
Click to expand...
Click to collapse
There can be many reasons for that. Please tell me the error or what's actually happening. Then only I can be of help.
Sir ive used xiaomi flashtool v2 after that and it worked. Thanks sir. After that i updated to latest twrp from that chinese one.
​
LoadOP2 said:
There can be many reasons for that. Please tell me the error or what's actually happening. Then only I can be of help.
Click to expand...
Click to collapse
Joyeuse
Hello, Does it work for Joyeuse (European version)?
The name of TWRP says Curtana -Unified
rfguy said:
Hello, Does it work for Joyeuse (European version)?
The name of TWRP says Curtana -Unified
Click to expand...
Click to collapse
Yes Unified means all Snapdragon 720g Devices which include Joyeuse, Curtana, Gram, Excalibur.
Hey buddy, thank you for this quick step-by-step guide. I flash ROMs since 2012 and you know what? It helped me the same. Having all stuff needed for go from stock to custom concentrated in one place (plus some useful tip like the Magisk flash at the end) it's always useful and time-saving. Thank you
2 Micro-notes about fastboot btw:
- write 'fastboot (with lowered 'f'): it may confuse some newbie
- it's 'reboot' instead of 'boot'

Question What is the easiest and safest way to root Redmi Note 10?

I want to access /data/system/users//settings_ssaid.xml to know what my game unique id is.
But after some research i learned that i have to root to able to get there but i have almost zero knowledge about it.
Are there any guide to root Redmi Note 10 from the scratch? Thanks.
1- Boot into Custom Recovery
2- Flash Magisk ZIP
3- Install Magisk APK
Done
if you want detailed steps , please tell me on wich ROM you are and if you have your bootloader unlocked
alonsoj636 said:
1- Boot into Custom Recovery
2- Flash Magisk ZIP
3- Install Magisk APK
Done
if you want detailed steps , please tell me on wich ROM you are and if you have your bootloader unlocked
Click to expand...
Click to collapse
Hi, I'm on official global ROM 12.5.3.0 RKGMIXM
And i turned on OEM Unlocking in developer mode yesterday (Which is confuse me a little a guide said i have to wait for 7 days for this but mine is nothing it's just switched to on)
OEM Unlocking is only one of the steps, but it does not unlock the bootloader. File a request with Xiaomi.
unlock bootloader
i recommend only booting to twrp, not flashing it
flash magisk 23
hide magisk
inn0ichi said:
...
i recommend only booting to twrp, not flashing it
...
Click to expand...
Click to collapse
Why do you recommend to only booting to TWRP instead of flashing it?
Pasarireng said:
Why do you recommend to only booting to TWRP instead of flashing it?
Click to expand...
Click to collapse
because the twrp developer instruction is to booting , not flashing
alonsoj636 said:
because the twrp developer instruction is to booting , not flashing
Click to expand...
Click to collapse
Aside of that instruction, actually is it 'dangerous' if we install the TWRP? What 'bad things' would/may happen if we install it? (Because I see some guides about installing it on RN10, like this one for example, and I was almost followed that guide).
Risk of bootloop
Pasarireng said:
Aside of that instruction, actually is it 'dangerous' if we install the TWRP? What 'bad things' would/may happen if we install it? (Because I see some guides about installing it on RN10, like this one for example, and I was almost followed that guide).
Click to expand...
Click to collapse
Risk of bootloop and fastboot loop... because this twrp is modded to be booted and then flashed (you can found the option in advanced)
One time i faced a fastboot loop once i flashed directly the twrp , that's why i recommend booting it first and then , flashing
Y
alonsoj636 said:
Risk of bootloop
Risk of bootloop and fastboot loop... because this twrp is modded to be booted and then flashed (you can found the option in advanced)
One time i faced a fastboot loop once i flashed directly the twrp , that's why i recommend booting it first and then , flashing
Click to expand...
Click to collapse
Yes, I mean that, (booting it first then flashing,.. (the TWRP right?).. I think the guide (which the youtube link I attached above) is also told to do that, right? (Or do I misunderstand this?)
Pasarireng said:
Y
Yes, I mean that, (booting it first then flashing,.. (the TWRP right?).. I think the guide (which the youtube link I attached above) is also told to do that, right? (Or do I misunderstand this?)
Click to expand...
Click to collapse
Yes , is the correct way
inn0ichi said:
unlock bootloader
i recommend only booting to twrp, not flashing it
flash magisk 23
hide magisk
Click to expand...
Click to collapse
Please confirm these;
*So we can:
Use TWRP only temporarily, only to root the phone (by flashing Magisk v23),
and then,
back to using the stock recovery on our RN10 afterward,
even if the RN10 is already rooted?
**If the answer for my question above is yes, then (in RN10 condition of Unlocked Boot Loader, Rooted, Stock MIUI & Stock Recovery) ;
Would we still get official OTA Update from Xiaomi (and can download and install the update- as how it's like before rooting the phone)?
Thank you in advance
It's an unnecessarily complicated procedure. Just flash a modified boot.img for your Miui using fastboot from your PC. If you don't have the ability to modify the boot.img on another rooted phone yourself, request a modified boot.img with the exact update version of your Miui here.
StaryMuz said:
It's an unnecessarily complicated procedure. Just flash a modified boot.img for your Miui using fastboot from your PC. If you don't have the ability to modify the boot.img on another rooted phone yourself, request a modified boot.img with the exact update version of your Miui here.
Click to expand...
Click to collapse
Thanks again, (and maybe I will try your suggestion later).. but (sorry)... your reply doesn't answer my questions.
(I think my questions are very clear and probably very easy to be answered by someone who has experience/knowledge about it (like you?).. no?)
Forgive my nooby questions.
But I really want to know as much as I can (especially about the answer for some questions I have inside my head about the matter, like I asked above),.. before executing doing something about my phone.
oops... I'm sorry for double send
In the past I rooted Miui and then continued to get OTA updates. However, this cannot be confirmed for all versions of Miui. Each new update changes the phone software and so what worked before may not work today.
alonsoj636 said:
1- Boot into Custom Recovery
2- Flash Magisk ZIP
3- Install Magisk APK
Done
if you want detailed steps , please tell me on wich ROM you are and if you have your bootloader unlocked
Click to expand...
Click to collapse
Hi, I'm unlocked my phone and installed the orange fox it's the custom recovery right? Because it say so.
If yes, By Flash Magisk ZIP how to do that? Please explain the detailed steps, Thanks.
First of all, I would like to point out that Magisk (root) is a security risk. Without understanding the issues, the phone is more easily exploitable.
To install, just download the magisk file with the ZIP extension. In recovery, select the install option and select this file. Once installed, exit recovery and boot the system. Once the system boots, use magisk and complete the installation it requests.
Lolitary said:
Hi, I'm unlocked my phone and installed the orange fox it's the custom recovery right? Because it say so.
If yes, By Flash Magisk ZIP how to do that? Please explain the detailed steps, Thanks.
Click to expand...
Click to collapse
the answer above is right ... but i would suggest to flash Orange Fox zip and then Magisk zip... to avoid problems
isn't there decrypt.zip for RN10?
How to decrypt this phone?
I usually did that along with rooting with my android phones before this.
Edit:
Update:
It's ok now I understand how, after watching this video.

Categories

Resources