Search results

That's my whole point. I want to extract the current init_boot.img of the phone that's sit on WITHOUT having the Recovery or fastboot or ROM file of the phone. How can I succeed to extract the init_boot.img from my phone OR with a PC, WITHOUT having the recovery or fastboot.img?

C:\adb\platform-tools>adb shell nuwa:/ $ dd if=/dev/block/bootdevice/by-name/init_boot_a of=/sdcard/init_boot.img dd: /dev/block/bootdevice/by-name/init_boot_a: Permission denied 0+0 records in 0+0 records out 0 bytes (0 B) copied, 0.001 s, 0 B/s 1|nuwa:/ $

How to extract the init_boot.img? I use on PC CMD: ls -la /dev/block/bootdevice/by-name Result: lrwxrwxrwx 1 root root 16 1970-01-02 01:42 init_boot_a -> /dev/block/sde30 lrwxrwxrwx 1 root root 16 1970-01-02 01:42 init_boot_b -> /dev/block/sde59 Then I use: dd if=/dev/block/sde30...

Thanks, Im gonna try it and let you know. But can you tell me the difference between the init_boot.img and the Boot.img?

Ah I dindt know that.... How to extract the init_boot.img of the current OS that is being installed? This was for the Boot.img ( dd if=/dev/block/bootdevice/by-name/boot of=/sdcard/boot.img) Could you tell me where the boot.img is need it for then?

Hi, I have a Xiaomi 13 Pro EEA Version: 1.0.7.0.UMBEUXM I wanna get Root acces by the method by doing extracting the Boot.img file from the ROM and patch it by Magisk. But when I patch the original Boot.img of the ROM, I get a modified magisk_patched-2700_xxxx.img, what is correct. Now my...

Really really nice to see that the Xiomi 13 is being supported. Admin, how long is the list with supported devices? Every year comes new devices and the list is going larger.. How do you maintain so long these devices, and do you drop the support on other models after a 4 a 6 years?

Guys, I have a problem that the phone continues boot into the Recovery MUIU 5.0 after having root... What I am doing wrong? I am pulling, scratting my head.. Never saw this before on the Xiaomi mi device. Would be helpful if someone could help me with this. 1. Find or redownload the zip file...

It worked out the decryption TWRP recovery of SKKK ([BOOT]3.6.2_12-Mi11Ultra-Mi11Pro_v5.6_A12-star-skkk_016c95cb (1)) for the Mi 11 Pro (Chinese release) with EEA ROM stock flashed. But still I have that the phone still boots automatically to the TWRP (Recovery). After second reboot it boots...

@katerpanne How do I should update my phone on the propper way if there is a OTA update with Root available?

Does this also works for the Xiaomi Mi 11 Pro? Codename: "Star" Because more and more TWRP are not suitable for Android 12. Because its being encrypted.

Yeah, the modules work fine after wipe data. No, it's data, not Cache. I uploaded the pictures of it. What I did. Yeah, it's really strange that this works now... Which version of Magisk are you running? In the native settings of the orginal apps, there is under Permissions: AutoStart. The...

No Im using the official rom for this phone, instead of a China build I use the EEA (Europe) version, instead of the Global version. Why? Less adds, more updates. More capable GPS Antennas to get a fix. Im using unlocked bootloader ofcourse for this. But passing Safetynet, I need these 2...

Is it right that you dont need to wipe the phone after its being flashed with the modified_Boot.img (root)? I need these 2 modules. Passing SafetyNet , fingerprint adjust. It doesnt matter which module I install after the first module installed, and after a restart its boots into Muiu recovery...

Which Magisk version do you use then? For example, Im installing 1 of these tweaks: - Magisk Hide props config module from Github (finding on Magisk is not working anymore) - Universal Safety net Fix .2.1.1 from Github (finding on Magisk is not working anymore) It doesnt matter which one I...

I tried different Module's and on every module its gets a bootloop into the recovery of "MIUI Recovery 5.0" After a few reboots in to this recovery the phone boots finnaly up in the normale mode...

Stock flashed. Im rooted right now, but also in a bootloop/recovery. This happend after installing a different kind of module, After a restart it keeps in the MIUI Recovery 5.0, after a serveral reboots it boots into the phone. How can I fix this? Can I flash the normall boot.img? or the applied...

Fresh flashed with a stock EEA firmware. Extract the boot.img and flash it with magisk. That gives a modified boot.img. This one flashed in Fastboot. " fastboot flash boot magisk_patched-25200_ECKSt.img " If I now reboot the phone it DOESN'T automatically boots in to MIUI Recovery 5.0, it boots...

Im going to flash the phone I tried but still bootloops. Yeah I created the other post in the wrong section.. Can't delete it unfor. What im going to do is flash a new firmware EEA build. and start over. Installing Magisk 25.2 and not to hide this app. Is there some settings I need to do? Or...

I want to root my phone Mi 11 Pro without - TWRP. But by doing this with Magisk 25.1 and patching the boot.img after installing a tweak Magisk Hide props config The phone boots continuously to the MIUI Recovery 5.0, instead of starting the phone normally... After a couple reboots into to MIUI...