I'm new to this so i probably messed up something. I just got a redmi note 11 spesn and decided to root it. I unlocked the bootloader with the official xiaomi tool and downloaded what should be the official rom (https://xiaomifirmwareupdater.com/miui/spesn/stable/V13.0.2.0.SGKMIXM/). I then unpacked the payload.bin into separate img files with a python tool, patched boot.img file with magisk and then, again from the pc, flashed it to my phone. The phone takes about 3 minutes to boot up but that isn't really that big of a deal. Apps can now get root (confirmed with adaway) but I can't turn on wifi or tilt my screen. I have a suspicion it may be because i flashed a newer version of rom (noticed later), one that also ships with android 12, while the phone still displays the old version number and android 11. Do i have to flash any other image as well for it to work, or is this an unexpected result and I'm better off just flashing the default, A11 rom with the official flash tool and forget about rooting
As described, you are using boot.img from a newer version (A12) of your installed software (A11). Also, isn't it easier to install Magisk using TWRP?
There is an unofficial version for this device but it works correctly, except for the MTP
Related
The Title says it all.
Phone Xiaomi Redmi Note 4X (Snapdragon)
Do you not have TWRP? Download the uninstaller, and Magisk 17, flash the uninstaller, reboot, reboot into recovery, and flash Magisk 17.
@Lirannl: I suspect he wants to keep his stock recovery so he can take OTA updates while being rooted. The Redmi Note 4X forums in fact have a post addressing this very scenario. Where he apparently doesn't have a PC yet wants root keeping the stock recovery actually makes sense. After all, not everyone can have a Pixel 2 XL and be able to flash full OTA zips from Google's pages in TWRP.
Idk about Xiaomi but if I didn't have my laptop I could flash firmwares onto my Sony from my old phone. The newflasher flash tool is available from Android to Android. As for Xiaomi, I only ever used aosp on their devices. I would immediately unlock the bootloader and flash CM/LOS.
hello
It's been a while since I wrote anything on XDA, so please be gentle
Let's get the ball rolling.
I have been using MI9 since launch. I bought mine directly at the store in Shanghai, and brought it with me to Europe. After 2 weeks i unlocked the bootloader, and was able to flash TWRP + xiaomi.eu ROM (current beta at that time).
For a couple of months I received OTA updates (all firty flashes), up until introduction of beta android Q (miui 11).
I downloaded the ROM, and flashed, everything worked fine. after some time I had an issue with google pay, so thought of reverting to android Q. I checked, and dirty flash was not recommended option, so I prepared Android P ROM (not sure if exact version is relevant), booted to TWRP (3.3.1.42), wiped the data and tried to flash the ROM (from USB OTG).
Sadly - received error 7, some info about system partition.
I tried reflashing android Q - only to receive the same error.
Stuck at TWRP or fastboot, I used miflash and returned to a global stable.
then I reflashed twrp hoping to remove the error, but had the same error while flashing. Tried to flash from both internal memory, and usb OTG.
returned with miflash to stable, to use the phone..
bootloader is still unlocked, I can flash twrp again, but it will be wiped once I restart the system (as global roms "reflash" recoveries when they boot up).
I looked on some guides how to deal with error 7, but most of them aren't applicable (removing asses lines from config files, as there is no assess line in the ROMs).
Perhaps I am missing some files that I should flash, such as "vendor" files, or something ?
I thought that miflash restores fully to factory state, so TWRP shouldn'[t give any more errors.
There might be something wrong about either the rom, or the twrp.
> Since error 7 is the updater script checking for the phone model, it's either a bad script, or you missed an asserts file when flashing with MiFlash, as even the "factory" roms might not contain all partitions.
> Some partitions can't be seen by Mauronofrio's TWRP, but that shouldn't be a problem tho...
- Try using TWRP 3.3.1-1001 by a chinese team
- Try using the latest 10.10.2019 MIUI11 Rom from xiaomi.eu, I'm using in on an EEA phone and quite satisfied with it
After some time I got a second Axon 10 and I spend some time figuring out what was possible with this phone in terms of root, custom ROM etc.
My results are as follows.
What is working:
Android 9 + Magisk and TWRP
Android 9 + TWRP + Custom ROMs (LineageOS 16 and patched GSI)
Android 10 + Magisk and TWRP
Android 10 + Magisk and MicroG flashed via Magisk (= stock ROM without Google Services)
Android 11 + Magisk
What is not working:
Android 11 + Magisk + TWRP (TWRP logo flashes randomly but TWRP does not load).
Android 11 + Magisk + MicroG (the nanolx patching script does not work with Android 11 as of yet)
Encryption in Custom ROMs
Method to flash files via EDL
Unzip / unrar my files into the backup\full folder of the EDL tool and choose restore + full in the tool.
Unlock Bootloader:
Before you try any of the files, you MUST unlock your bootloader!
BACKUP of your data as it will be lost!
Download the EDL tool from this Thread
If your phone is not on android 9, you must go back to Android 9 first. e.g. by using my Android 9 1.9 backup.
After you restored it, restart while holding the volume + key and do a factory reset / format data.
Boot into EDL again and unlock the bootloader.
Now you are on android 9 with unlocked bootloader.
From here you can follow the other guides in the form and install TWRP or lineageos. Or flash one of my files below.
Flashing EDL files:
Unzip / unrar my files into the backup\full folder of the EDL tool and choose restore + full in the tool.
I put all my files into this MEGA account: MEGA
Android 10 version 2.9 Magisk + TWRP
Android 11 version 3.5 stock
Android 11 version 3.5 Magisk
Android 10 version 2.10 stock
Android 10 version 2.10 Magisk (TWRP can be flashed with Magisk)
Install MicroG:
Only works on Android 9 and 10.
Before you install MicroG you must patch the stock ROM to allow for signature spoofing.
The patcher script I used is on https://downloads.nanolx.org/NanoDroid/Stable/ When I write these lines the up-to-date-version is NanoDroid-patcher-23.1.2.20210117.zip
Reboot.
Install MicroG from the Magisk repository.
After a restart there will be error messages that google apps keep crashing. With each warning, disable the apps one by one.
When you reboot again, no errors should appear and MicroG should report that it is fully working.
You can add the Bromite Framework and give F-droid system rights. Both are available from the Magisk repo.
Updates will likely install the Google apps again and uninstall Magisk...
Revive phone:
Not really related, but I bricked my phone several times.
If your phones does not boot anymore or hangs in a bootloop, try accessing the EDL mode.
The easy way:
Boot while holding volume -
The hard way:
Old Volume +, volume - and power until you end up in EDL. The screen will be black, so it helps if you have the Phone connected to Windows and can hear the system sound when the USB sees a connection.
In anyway you can then use the EDL tool to restore / flash an EDL image.
On custom ROM support:
Well there is LineageOS 16 by Unjustified Dev. https://forum.xda-developers.com/t/rom-unofficial-zte-axon-10-pro-9-lineageos-16-0.3992127/ It works well. But has a patch level that is outdated by now.
On top of it you can install the GSI ROMs created by Rafyvitto. The latest one is Resurrection Remix https://forum.xda-developers.com/t/...nofficial-resurrection-remix-q-8-6-7.4172527/
with a security patch level of mid 2021. Which is recent enough to use. The stock roms are not much better.
With both Custom ROMs, encryption is not working which poses a privacy/security risk when your phone is stolen. Do not forget that your phone does not only contain your photos and data but also your passwords to your accounts.
Added Android 10 2.10 files.
Its nice to see anything new for this phone. I wish I can use these roms but I have the American version.
Hi and thanks for your work and your files.
I'm stuck on "Loading the programmer: prog_ufs_firehose_sdm855.elf >>>", if I try to recover your edl files with EDL Tool, v 3.25.
I have to choose option 2: "Restore Full EDL from backup", right?
Is there a way to check if the bootlaoder is really unlocked?
Thanks in advance
OK, I was able to solve the problem with the "programmer" and try the backups. The next step was almost clear. The device is stuck in bootloop. I've already tried all the backups I could find on Mega. After the EDL Tool has done its work and the device has restarted, the mobile phone goes into the boot loop. And now? So the starting position was: Android 9 with an open bootloader. Maybe someone has an idea?
After I couldn't get the device out of the bootloop, I flashed the A2020G_PRO_V1.6_FULL_EDL via MiFlash and then did an OTA update to 1.8.
Then I tried unlocking the bootloader again, which unfortunately didn't work. The flash is carried out without errors, but the device then apparently does not start in the desired Fastboot mode.
Thanks for your guide. However am I missing something with the Android 11+Magisk installation? I restored all the correct files and everything flashed correctly, however upon reboot there is no Magisk installed anywhere. Did a factory reset after the flash and still not there. Tried installing Magisk via his github and tried patching the boot.img again and it says success but after rebooting it says Magisk is not installed.
brian117 said:
Thanks for your guide. However am I missing something with the Android 11+Magisk installation? I restored all the correct files and everything flashed correctly, however upon reboot there is no Magisk installed anywhere. Did a factory reset after the flash and still not there. Tried installing Magisk via his github and tried patching the boot.img again and it says success but after rebooting it says Magisk is not installed.
Click to expand...
Click to collapse
Maybe you need to switch the slot in TWRP. It sounds as if you install it to the other slot (like A) an then boot B. Or vice versa.
Hi,
My S21 Ultra was rooted and I used to flash the regular updates manually by patching the AP and flashing everything with HOME_CSC.
Today I did all that with the December update (UI 4.0, Android 12). It all went smoothly, but when the phone rebooted, I have lost root access. I have no root, Safetynet doesn't pass and basically I don't know what to do now.
I guess that wiping the phone and doing a clean install with the patched version is an option, but I would really want to keep all the data I have. Is there anyway around this?
did a clean install, my phone wont really boot up with a patched boot image. have you had any luck?
Other users with unlocked devices have stated root access is blocked after updating to One UI 4.0, Android 12.
Don't know what is causing your issues, I'm using my S21U on December (actually now January) image. Patched with Magisk Alpha (23016), works like a charm here.....
Oh, I'm on DBT/998B-version with Exynos - just in case if this matters
PS: procedure is the same as outlined in OP.
On a sidenote I had numerous issues with transferring the full AP-Image between PC and phone, in the end I just extracted the boot.img.lz4 and the vbmeta.img.lz4 into a new tar, transferred that to the phone, patched it and copied the resulting tar back to the PC.
Then I copied all remaining files from the original AP into the Magisk-patched tar and flashed the result in Odin......
Hi
A few months ago I was able to flash on angelica lineage-17.1-20210326-UNOFFICIAL-angelica.zip and this worked well. Yesterday I tried to flash the s same image again and after several attempts I get a black backlit screen when lineage is meant to start. I reflash stock _V12.0.10.0.QCRMIXM then a recovery - PBRP 3.0.1. From there I was having issue
What is the flashing process for an unlocked device that has something like TWRP/Pitch Back/Orange Fox installed?
I guess once you unlock and can flash the recover you use the recover to flash the zip, then reboot and flash magisk.zip and everything should work? Or is there some step missing.
I had this problem too with the google pixel 7 pro. Can't help ya there on that one. I even tried re installing older firmware and it still didn't work. Maybe the bootloader is permanetly downgradable but the firmware of the stock is. Just a guess. Lineage os 20 is an unofficial build at the moment that receives hardly any updates.