Related
Hello,
This is my first android tablet and i love it, but i have bricked it, i was messing around with it and i think i wiped it all, at this moment the device is stuck at the mediapad logo, fastboot mode is working but i can not get into recovery.
I have downloaded the two official stock roms mentioned in this post http://forum.xda-developers.com/hua...rom-official-huawei-mediapad-x1-b007-t2811863 but when i try to do
Code:
fastboot update update.zip
i get the below error:
Code:
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt]
The zip file contain the dload folder and the update.app file, no .txt files in mention. Any solution to this ?
I have also tried to flash a cwm/twrp recovery (tried many variants) into the device but i can not boot into them (nothing happens, still stuck at the mediapad screen).
Code:
fastboot flash recovery recovery.img
At this moment i have only fastboot available, what can i do to unbrick the device ?
Thanks alot
zertux said:
Hello,
This is my first android tablet and i love it, but i have bricked it, i was messing around with it and i think i wiped it all, at this moment the device is stuck at the mediapad logo, fastboot mode is working but i can not get into recovery.
I have downloaded the two official stock roms mentioned in this post http://forum.xda-developers.com/hua...rom-official-huawei-mediapad-x1-b007-t2811863 but when i try to do
Code:
fastboot update update.zip
i get the below error:
Code:
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt]
The zip file contain the dload folder and the update.app file, no .txt files in mention. Any solution to this ?
I have also tried to flash a cwm/twrp recovery (tried many variants) into the device but i can not boot into them (nothing happens, still stuck at the mediapad screen).
Code:
fastboot flash recovery recovery.img
At this moment i have only fastboot available, what can i do to unbrick the device ?
Thanks alot
Click to expand...
Click to collapse
Use the standard ROM flashing method by copying the update.app into dload folder onto an external sdcard and reboot your device. This ought to work. If it doesn't you've truly bricked your device by screwing up the bootloader.
The only other way if you've screwed up the bootloader is to perform a bootloader unlock using the tool on 4PDA.ru. Google Translate is rather spotty though.
joytest said:
Use the standard ROM flashing method by copying the update.app into dload folder onto an external sdcard and reboot your device. This ought to work. If it doesn't you've truly bricked your device by screwing up the bootloader.
The only other way if you've screwed up the bootloader is to perform a bootloader unlock using the tool on 4PDA.ru. Google Translate is rather spotty though.
Click to expand...
Click to collapse
Will the sdcard method work if i can not boot into recovery ? also, can you point me to that tool ? i can not find it there
zertux said:
Will the sdcard method work if i can not boot into recovery ? also, can you point me to that tool ? i can not find it there
Click to expand...
Click to collapse
Sdcard method is the default update method for Huawei. There is no need to mess with any 3-button combo or hardware.
It is the easiest update method I've seen among the major phone companies.
I will post link to the 4pda tool link later as I am at work now.
Sent from my SM-N9005 using Tapatalk
joytest said:
Sdcard method is the default update method for Huawei. There is no need to mess with any 3-button combo or hardware.
It is the easiest update method I've seen among the major phone companies.
I will post link to the 4pda tool link later as I am at work now.
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
I have made a little progress i think, using your post https://forum.lowyat.net/index.php?showtopic=3280093&st=840&p=70452069&#entry70452069 i have flashed the CWM recovery and i am able to boot into it (Chinese XD) and i am using the menu you translated to navigate around, i have put the stock zip that i downloaded and tried to flash the zip file but i got some erros that i did not understand (see attached screenshot)
I have noticed that when i plug the device now into the pc it shows the battery charging (something did not appear before). Also, the sdcard update method is not working (nothing happens, stays at the mediapad logo)
What should i do now ?
screenshot:
http://i59.tinypic.com/29xue0p.jpg
It says cannot open the file.
Just use the normal method of the dload folder.
You have taken a very complex route to solve a simple issue.
Sent from my Mediapad X1 7D-501L using Tapatalk HD
joytest said:
It says cannot open the file.
Just use the normal method of the dload folder.
You have taken a very complex route to solve a simple issue.
Sent from my Mediapad X1 7D-501L using Tapatalk HD
Click to expand...
Click to collapse
I have tried the dload method, i have extracted the contents of the zip file "dloadl/update.app" and put them in a 2GB memory, inserted the momeory inside the device and turned it on but nothing happens, it stays on the logo of "mediapad"
zertux said:
I have tried the dload method, i have extracted the contents of the zip file "dloadl/update.app" and put them in a 2GB memory, inserted the momeory inside the device and turned it on but nothing happens, it stays on the logo of "mediapad"
Click to expand...
Click to collapse
Then it is quite possible your download is corrupted. Try downloading again. And I think the recommendation was to use a 4Gb card.
joytest said:
Then it is quite possible your download is corrupted. Try downloading again. And I think the recommendation was to use a 4Gb card.
Click to expand...
Click to collapse
Ok, will re download and try with a 4GB memory stick, what about the bootloader unlocker that you mentioned ? do we still need that ?
zertux said:
Ok, will re download and try with a 4GB memory stick, what about the bootloader unlocker that you mentioned ? do we still need that ?
Click to expand...
Click to collapse
Just to clarify, my device is 7d-501u so i will have to download this http://www.emui.com/nsp/geturl.php?path=7D-501u_EMUI_2.0_V100R001C233B019.zip&rid=560 right ?
zertux said:
Just to clarify, my device is 7d-501u so i will have to download this http://www.emui.com/nsp/geturl.php?path=7D-501u_EMUI_2.0_V100R001C233B019.zip&rid=560 right ?
Click to expand...
Click to collapse
Yes you have to download the correct ROM for your device. 501u is the 3G version.
joytest said:
Yes you have to download the correct ROM for your device. 501u is the 3G version.
Click to expand...
Click to collapse
so i have downloaded http://www.emui.com/nsp/geturl.php?path=7D-501u_EMUI_2.0_V100R001C233B019.zip&rid=560 and it still gives me the same error in the screenshot, how can i get the correct firmware for my device ? (on the back of the device its written 7D-501u )
zertux said:
so i have downloaded http://www.emui.com/nsp/geturl.php?path=7D-501u_EMUI_2.0_V100R001C233B019.zip&rid=560 and it still gives me the same error in the screenshot, how can i get the correct firmware for my device ? (on the back of the device its written 7D-501u )
Click to expand...
Click to collapse
As far as I know, you downloaded the 501u version. Perhaps the last resort is to enable the CWM to allow ABD sideloading?
Or, you can try this "unlock bootloader" from 4PDA
http://4pda.ru/forum/index.php?showtopic=564429&view=findpost&p=34341371
It seems you just need to run the exe file. You can try this since nothing else works for you.
Appreciate if you report on the success.
joytest said:
As far as I know, you downloaded the 501u version. Perhaps the last resort is to enable the CWM to allow ABD sideloading?
Or, you can try this "unlock bootloader" from 4PDA
http://4pda.ru/forum/index.php?showtopic=564429&view=findpost&p=34341371
It seems you just need to run the exe file. You can try this since nothing else works for you.
Appreciate if you report on the success.
Click to expand...
Click to collapse
I will try the bootloader unlocker when i get home, i have tried 4 official roms for the 3G and 4G and i get this error
http://tinypic.com/usermedia.php?uo=adkBqYNLlttp9d8/5vW/a4h4l5k2TGxc
Can you tell me what does it say ? Also hoq can i re install the stock recovery of the device ? Maybe it will work ? I flashed it and installed wcm.
Update: i have downloaded the bootloader unlocker but its all in Chinese! any help is appreciated.
Update2: The bootloader is already unlocked, when i run
Code:
fastboot oem get-bootinfo
it says unlocked. however the device is not taking any rom that i try to install to it (errors in Chinese). i have extracted the system.img, boot.img and recovery.img from the update.app package, i will try to flash them into the device one by one with fastboot.
FIXED!
So for anyone who ran into the same problem, here is how i fixed it:
1. Downloaded the 7D-501u official stock ROM mentioned in this post http://forum.xda-developers.com/hua...rom-official-huawei-mediapad-x1-b007-t2811863
2. Used Huawei update.app extractor tool from http://forum.xda-developers.com/attachment.php?attachmentid=2822142&d=1403960391
3. Flashed boot.img, recovery.img and system.img
Code:
fastboot flash recovery RECOVERY.img
fastboot flash system SYSTEM.img
fastboot flash boot BOOT.img
Rebooted and it worked! the bootloader comes unlocked by default (at least for my model). Special thanks for joytest for his help.
Hello. I'm crazy. I deleted stock recovery original for my 7D-503L 4.2.2 (B008). The problem was install the stock recovery 4.4 kit Kat for error. I installed again the rom B008 and anything. Is impossible to find the stock recovery original and one CWM for my device. Somebody can I help me please? Somebody know where lies the stock recovery? I know is independently of the Rom.
Regards
Soft Brick: Stuck at Huawei logo and unbale to Boot/access Recovery.
=> Install the Universal Android USB Driver from the link below:
http://adbdriver.com/upload/AdbDriverInstaller.exe
=> Download and install ADB and Fast Boot from thebelow link.
http://fs1.d-h.st/download/00103/KIP/adb-setup-1.2.exe
=> Extract the Stock ROM using the Tool "Huawei Update Extractor" in the computer.
=>"HuaweiUpdateExtractor download link:
http://dl.xda-developers.com/attachd....7.9_Setup.zip
=> Copy and paste the Stock/TWRP Recovery and BOOT.img in the "ADB and Fast Boot" folder.
=> Connect the HAM to the computer using the supplied USB cable.
=> Press and hold the Power and Volume Down button.
=> HAM will be recognized as ABD device.
=> Leave the Power and Volume Down button.
=> Double click to open the installed "ADB and Fast Boot" from the Desktop or open the computer prompt to access the "ADB and Fast Boot" folder.
=> In the ADB and Fast Boot prompt:
=> Type: fastboot reboot-bootloader.
=> Type: fastboot flash BOOT BOOT.img
=> Type fastboot flash RECOVERY RECOVERY.img
Fastboot will flash the image and give you a success/failure notification. If successful, you're all set.
Finally, press and hold the Power button. HAM will boot now
fastboot: that's the executable tool
flash: that's the function we want the fastboot tool to perform
recovery: this is the name of the partition we want to flash into. since we are flashing a recovery image, it needs to go to the recovery partition.
recovery.img: this is the name of the actual file to flash. Your file name may be different. Just make sure it matches the actual file name.
@eennap. Ok tomorrow I will to try.
Thanks and Regards
I have a bricked (7D-501L).
1 .
I download a ROM «Huawei_MediaPad_X1_7D-501L_V100R001C170B001_Android_4.2_Russia».
I unzip ROM into root sdcard.
I use Huawei update.app extractor tool, and extract from ROM «boot» and «recovery» partitions.
I flashed a «boot» and «recovery» partitions via fastboot (from it ROM).
After, I use the standard ROM flashing method. The device start flashing, but after a few minutes the device reboot.
ROM not installed, the device not start.
2.
I download a ROM OTA_7D-503LV100R002C208B002.
I extracted this ROM, and flashed a BOOT.img, CACHE.img, CUST.img, RECOVERY.img, SYSTEM.img, USERDATA.img partitions via fastboot.
The device started, but after a few minuts my device reboot to black screen FASTBOOT.
What can i do to unbrick the device ?
P.S.: sorry for bad English
how can i make update.zip from update.app?
my device not flashing standard method.
I can flash it from recovery. I need update.zip
Please, help me
Problem already solved. Thanks!
Hi everyone, this is Sarry. I got my new huawei mate 9 pro on Wednesday this week, the version is LON-L29C636, I was trying to flash a custom ROM into the phone, but unfortunately I was too careless, flashed a different version ROM into it and cause immediate start up loop. As I finally boot into fastboot and twrp rec mode, I noticed that the computer won't recognize the USB portal of the device. So I went in eRecovery mode and tried to download an updated version but it failed to find any useful version.
Since mate 9 pro doesn't support SD card, I brought a USB-OTG cable and also usb type-c microSD adapter, when I connected the sd card to the phone, twrp reads the information, but when I tried to flash the update.zip file, it failed. I tried to copy the dload folder with update.app by twrp into phone storage, even if I got successful, the file just disappeared when i refresh the page. So now I don't have any idea on how to unbrick the phone, felt really bad.
Feel free to ask me any question or information needed, I really hope to unbrick the phone, I've been using huawei cellphone for more then 2 years and love it very much. Thanks for the help!!
Hello,
well the situation isn't that hard actually, you may just get the stock image and flash it from fastboot then start the custom rom installation from scratch.
what is the error number or statement?
EDIT: you will need huawei update extractor to pull out the img files and flash them through fastboot
Another Edit:
in the file path choose the update.app
you will need the following partitions:
Boot
System
Recovery
^select these then right click and press `extract selected` and flash them using the following commands:
1- fastboot devices > to check the device
2- fastboot flash boot boot.img
3- fastboot flash recovery recovery.img
4- fastboot flash system system.img
hope this helps you
good luck!
TheShadowMC said:
Hello,
well the situation isn't that hard actually, you may just get the stock image and flash it from fastboot then start the custom rom installation from scratch.
what is the error number or statement?
EDIT: you will need huawei update extractor to pull out the img files and flash them through fastboot
Another Edit:
in the file path choose the update.app
you will need the following partitions:
Boot
System
Recovery
^select these then right click and press `extract selected` and flash them using the following commands:
1- fastboot devices > to check the device
2- fastboot flash boot boot.img
3- fastboot flash recovery recovery.img
4- fastboot flash system system.img
hope this helps you
good luck!
Click to expand...
Click to collapse
Thank you so much for the help! The fastboot script isn't really working because when I tried to run it in cmd, it shows 'error can't find device', so I tried to flash the img files with twrp, the boot.img and recovery.img works well, but the system.img cannot be flashed, and the error message shows 'E:\cannot flash system.img'. I also tried to download the full version firmware and created dload folder in my SD card, copied UPDATE.APP into the folder, tried the 3 button force update, still nothing worked. Now the seller send me an Email said I can return the product, they are going to charge me for some ROM re installation fee.
However what error does it give during flashing system.IMG I would like to know, also as well as twrp custom ROM flashing?
Aquarius_2333 said:
Thank you so much for the help! The fastboot script isn't really working because when I tried to run it in cmd, it shows 'error can't find device', so I tried to flash the img files with twrp, the boot.img and recovery.img works well, but the system.img cannot be flashed, and the error message shows 'E:\cannot flash system.img'. I also tried to download the full version firmware and created dload folder in my SD card, copied UPDATE.APP into the folder, tried the 3 button force update, still nothing worked. Now the seller send me an Email said I can return the product, they are going to charge me for some ROM re installation fee.
Click to expand...
Click to collapse
well brother about the driver issue, sorry about being late, you must have downloaded the fastboot drivers and installed them.
Hi. I've been rooted with Magisk ever since I got this phone but now I got tired of having to wipe everything, every time I tried to take OTA.
I've tried unroot and flash stock boot.img, but that wasn't enough to take OTA. I've tried factory reset from within settings and not even that worked.
OTA still failed at step 3.
So this is what I finally did, and it worked.
DISCLAIMER
I AM NOT RESPONSIBLE FOR ANY LOSS OF DATA. IT SHOULD WORK FINE, BUT
IF YOU HAVE INVALUABLE PICS OF YOUR KITTEN, PLEASE MAKE A BACKUP TO BE SAFE
Uninstall any substratum overlays you have installed and unroot from within Magisk Manager.
Reboot your phone.
Unpack your current firmware in the same location where you have adb/fastboot and unzip the "XT-1941-flash_No-wipe.bat" to same directory.
Boot your phone to fastboot mode, plug the cable in, open cmd and drag the "XT-1941-flash_No-wipe.bat" in to the cmd window.
It will automaticly flash all files in the firmware, without wipe. Just wait for it to finish.
Reboot and take the OTA.
After that I booted TWRP and made a backup of boot.
Booted to system, installed Magisk Manager, renamed the backup to boot.img and patched it with Magisk Manager, then flashed it in TWRP. (fastboot works too)
Now I'm updated to PPKS29.68-16-21-3 without having to go through the painfull process of backing up and restoring all data.
Been waiting for something like this. Thanks.
Tested on XT1941-4 DEEN RETEU PPKS29.68-16-21-2, update to PPKS29.68-16-21-3
Used script and update gone past step 3 and rebooted successfully.
Thanks for your guide. Just two questions
1. What's the right fastboot command?
fastboot flash boot_a patched_boot.img
or
fastboot flash boot_b patched_boot.img
2. There is an extra file named "system.img_sparsechunk.9" in the stock firmware PPKS29.68-16-21-2, but there is no command for flashing this file in your .bat file. Is this not important?
vrezaei said:
Thanks for your guide. Just two questions
1. What's the right fastboot command?
fastboot flash boot_a patched_boot.img
or
fastboot flash boot_b patched_boot.img
2. There is an extra file named "system.img_sparsechunk.9" in the stock firmware PPKS29.68-16-21-2, but there is no command for flashing this file in your .bat file. Is this not important?
Click to expand...
Click to collapse
Hmm that's strange. I just had a look at the PPKS29.68-16-21-2 but I don't have any.
View attachment 4782745
For the boot you can just use fastboot flash boot patched_boot.img
It will flash the active slot if you don't specify.
tys0n said:
Hmm that's strange. I just had a look at the PPKS29.68-16-21-2 but I don't have any.
View attachment 4782745
For the boot you can just use fastboot flash boot patched_boot.img
It will flash the active slot if you don't specify.
Click to expand...
Click to collapse
Sorry about my mistake
My current and planing to update build numbers are PPKS29.68-16-36-2 & 3, respectively and the first one (my current stock firmware) contains system.img_sparsechunk.9 file. So, I think I must edit your .bat file and add the appropriate command for flashing this file.
vrezaei said:
Sorry about my mistake
My current and planing to update build numbers are PPKS29.68-16-36-2 & 3, respectively and the first one (my current stock firmware) contains system.img_sparsechunk.9 file. So, I think I must edit your .bat file and add the appropriate command for flashing this file.
Click to expand...
Click to collapse
Oh ok. I'll take another look when I get home, but yeah, you'll have to add the additional file if there is any.
Sent from motorola one.
If I understand correctly, after that step:
tys0n said:
Reboot and take the OTA.
Click to expand...
Click to collapse
Do I just need reinstall Magisk?
damiann69 said:
If I understand correctly, after that step:
Do I just need reinstall Magisk?
Click to expand...
Click to collapse
Ya
tys0n said:
Hi. I've been rooted with Magisk ever since I got this phone but now I got tired of having to wipe everything, every time I tried to take OTA.
I've tried unroot and flash stock boot.img, but that wasn't enough to take OTA. I've tried factory reset from within settings and not even that worked.
OTA still failed at step 3.
So this is what I finally did, and it worked.
DISCLAIMER
I AM NOT RESPONSIBLE FOR ANY LOSS OF DATA. IT SHOULD WORK FINE, BUT
IF YOU HAVE INVALUABLE PICS OF YOUR KITTEN, PLEASE MAKE A BACKUP TO BE SAFE
Uninstall any substratum overlays you have installed and unroot from within Magisk Manager.
Reboot your phone.
Unpack your current firmware in the same location where you have adb/fastboot and unzip the "XT-1941-flash_No-wipe.bat" to same directory.
Boot your phone to fastboot mode, plug the cable in, open cmd and drag the "XT-1941-flash_No-wipe.bat" in to the cmd window.
It will automaticly flash all files in the firmware, without wipe. Just wait for it to finish.
Reboot and take the OTA.
After that I booted TWRP and made a backup of boot.
Booted to system, installed Magisk Manager, renamed the backup to boot.img and patched it with Magisk Manager, then flashed it in TWRP. (fastboot works too)
Now I'm updated to PPKS29.68-16-21-3 without having to go through the painfull process of backing up and restoring all data.
Click to expand...
Click to collapse
I am new to this, could you please give us step by step process or a video will help, Thanks for the efforts
Thanks tys0n for sharing this! I've updated a few times using this way.
But from time to time Motorola is changing files or commands and I had allways to check, if the commands in the bat file match those of the servicefile.xml and to adapt it accordingly.
First I thought about to write a small 'servicefile2bat' converter tool - but since almost everything already exists, I did a search and found this one:
https://sourceforge.net/projects/flashfile2batchfile/
I've tested it with today's update to DEEN_QPKS30.54_22_7 and it works perfectly.
Devices that started to be received today have Oxygen OS 10.5 out of the box.
No flashable zip for that software release is publicly available, meaning its stock boot.img cannot be extracted.
You then need to update to a newer build first. You can do so from my OxygenOS builds repo thread.
Once done, enable developers options and enable OEM unlock.
Reboot to fastboot (enable USB debugging in dev options and use adb reboot bootloader)
Type fastboot oem unlock and accept to unlock bootloader (warning: as a safety measure Android will wipe your userdata)
Go through OxygenOS setup
Install Magisk Manager from https://github.com/topjohnwu/Magisk/releases/download/manager-v7.5.1/MagiskManager-v7.5.1.apk
Move stock boot.img to your phone internal storage (please open spoiler)
For your convenience, 10.5.2 stock boot.img for EU and India have been extracted
EU download: https://drive.google.com/file/d/18aPqErEMbRqmN4BpdvHE4OKgizDcEbou/view?usp=sharing
India download: https://drive.google.com/file/d/1ZIEYWH2PYkKyojq_S_i_onBstejHKDTJ/view?usp=sharing
For future builds, you can use payload dumper (Windows) , (Linux ) to extract stock boot.img
Click on Install
Choose "Select and patch a file"
Select your stock boot.img
Wait until Magisk patches your boot.img, and once patched it can be found in the Downloads folder
Copy that patched boot.img (which should be named magisk_patched.img) to your computer
Boot into fastboot again
Type fastboot getvar current-slot into your terminal window and press Enter.
If the output is a , type fastboot flash boot_a magisk_patched.img into your terminal window and press Enter.
If the output is b , type fastboot flash boot_b magisk_patched.img into your terminal window and press Enter.
Reboot to OxygenOS
Open Magisk Manager and your device should now be rooted.
TIPS:
- Ensure you got latest platform tools installed from https://developer.android.com/studio/releases/platform-tools
- Backup your /persist once rooted (dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/persist.img) and save it somewhere on your cloud/computer, this might save you from a broken fingerprint sensor and an RMA in the future if it turns out this device has same issue as 8-series when it comes to crossflash regional builds of OOS.
Credits:
@topjohnwu for making Magisk
/u/Jisifus for testing on his device and for screenshots
Some_Random_Username said:
TIPS:
- Ensure you got latest platform tools installed from https://developer.android.com/studio/releases/platform-tools
- Backup your /persist once rooted (dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/persist.img) and save it somewhere on your cloud/computer, this might save you from a broken fingerprint sensor and an RMA in the future if it turns out this device has same issue as 8-series when it comes to crossflash regional builds of OOS.
Click to expand...
Click to collapse
Great to see it works this way and thanks for the tip.:good:
do u lose all data while rooting?
#edit1
nevermind, cannot read right
OK, will give this a try asap,have the device here now...
I gave it a try, works like a charm! Thanks for this! Small tip, unlock bootload before u copy your files
now my phone is a bit laggy. with magisk on it.. i will test it later if its getting better
Some_Random_Username said:
Type fastboot getvar current-slot into your terminal window and press Enter.
If the output is a , type fastboot flash boot_a magisk_patched.img into your terminal window and press Enter.
If the output is b , type fastboot flash boot_b magisk_patched.img into your terminal window and press Enter.
Click to expand...
Click to collapse
You can simply type "fastboot flash boot magisk_patched.img" - it flash boot to current active slot. Just for note.
Can confirm that it works, just tried it myself
If WiFi/data does not work (usually happens when you flash wrong version, but can also happen if you flash correct one), fastboot boot the image, then do a direct install in Magisk Manager.
Also, big thumbs up for adding tips for persist backup, I see too many people needing to send their device back because they messed it up somehow.
Failed for me
Hi and thanks for the tips.
Running 10.5.2 (latest build) and Bootloader is unlocked.
1: Downloaded EU BootImage File suggested (10.5.2.AC01BA.boot.img - 101MB)
2: Went to Magisk Manager, Advanced Settings, Recovery Mode Ticked, Install Magisk, Install, Select and Patch a File - Browse to 10.5.2.AC01BA.boot.img in Downloads and select.
3: Command Window appears detailing successful patching of ramdisk and also location of the newly created magisk_patched.img (37.52MB???????????????)
4: Size of new boot image looks suspiciously small.
5: Copied magisk_patched.img to PC and rebooted phone into fastboot.
6: Issued the fastboot getvar current-slot command - mine is reported as b
7: Issued the fastboot flash boot_b magisk_patched.img - File flashed OK - Reboot (Start) Phone.
8: 30 seconds of unlocked bootloader warning screen followed by 10 secs black screen followed by Qualcom Crash Dump. Rebooted phone three times - same result.
9: Rebooted phone into fastboot mode, reflashed the stock boot image and all now OK (but obviously not rooted).
Would be grateful if anyone could advise - the magisk_patched.img looks suspiciously small to me at 37.52MB compared to 101MB for the original boot image.
Thanks
10: Double checked the patching process again in Magisk and again, patched bootimage filesize is on 37.52MB.
11: I have saved log from patching process and on reading, all looks OK.
jmwengineering said:
Hi and thanks for the tips.
Running 10.5.2 (latest build) and Bootloader is unlocked.
1: Downloaded EU BootImage File suggested (10.5.2.AC01BA.boot.img - 101MB)
2: Went to Magisk Manager, Advanced Settings, Recovery Mode Ticked, Install Magisk, Install, Select and Patch a File - Browse to 10.5.2.AC01BA.boot.img in Downloads and select.
3: Command Window appears detailing successful patching of ramdisk and also location of the newly created magisk_patched.img (37.52MB???????????????)
4: Size of new boot image looks suspiciously small.
5: Copied magisk_patched.img to PC and rebooted phone into fastboot.
6: Issued the fastboot getvar current-slot command - mine is reported as b
7: Issued the fastboot flash boot_b magisk_patched.img - File flashed OK - Reboot (Start) Phone.
8: 30 seconds of unlocked bootloader warning screen followed by 10 secs black screen followed by Qualcom Crash Dump. Rebooted phone three times - same result.
9: Rebooted phone into fastboot mode, reflashed the stock boot image and all now OK (but obviously not rooted).
Would be grateful if anyone could advise - the magisk_patched.img looks suspiciously small to me at 37.52MB compared to 101MB for the original boot image.
Thanks
10: Double checked the patching process again in Magisk and again, patched bootimage filesize is on 37.52MB.
11: I have saved log from patching process and on reading, all looks OK.
Click to expand...
Click to collapse
The size is normal.
When patching your image you have to select "Preserve Force Encryption" and "Preserve AVB 2.0/dm-verity" under advanced settings in the main screen where you patch the image.
jmwengineering said:
Hi and thanks for the tips.
Running 10.5.2 (latest build) and Bootloader is unlocked.
1: Downloaded EU BootImage File suggested (10.5.2.AC01BA.boot.img - 101MB)
2: Went to Magisk Manager, Advanced Settings, Recovery Mode Ticked, Install Magisk, Install, Select and Patch a File - Browse to 10.5.2.AC01BA.boot.img in Downloads and select.
3: Command Window appears detailing successful patching of ramdisk and also location of the newly created magisk_patched.img (37.52MB???????????????)
4: Size of new boot image looks suspiciously small.
5: Copied magisk_patched.img to PC and rebooted phone into fastboot.
6: Issued the fastboot getvar current-slot command - mine is reported as b
7: Issued the fastboot flash boot_b magisk_patched.img - File flashed OK - Reboot (Start) Phone.
8: 30 seconds of unlocked bootloader warning screen followed by 10 secs black screen followed by Qualcom Crash Dump. Rebooted phone three times - same result.
9: Rebooted phone into fastboot mode, reflashed the stock boot image and all now OK (but obviously not rooted).
Would be grateful if anyone could advise - the magisk_patched.img looks suspiciously small to me at 37.52MB compared to 101MB for the original boot image.
Thanks
10: Double checked the patching process again in Magisk and again, patched bootimage filesize is on 37.52MB.
11: I have saved log from patching process and on reading, all looks OK.
Click to expand...
Click to collapse
And that's why it's recommended to boot the patched image first.
Thanks
Lossyx said:
The size is normal.
When patching your image you have to select "Preserve Force Encryption" and "Preserve AVB 2.0/dm-verity" under advanced settings in the main screen where you patch the image.
Click to expand...
Click to collapse
Thanks for confirming file size - Preserve Force Encryption and Preserve AVB 2.0/dm-verity were ticked during the patching process. Guess I'll have to wait until TWRP is verified as Nord compatible.
---------- Post added at 07:06 PM ---------- Previous post was at 06:59 PM ----------
Kollachi said:
And that's why it's recommended to boot the patched image first.
Click to expand...
Click to collapse
Thanks for the reply. Not sure what you mean by booting the patched image first. You have to create the patched image on the phone first before you can flash and then boot it. Step 7 in my post above details the flashing of the patched image and subsequent attempt to reboot Oxygen OS. I can't boot the patched image until I've created and flashed it!
jmwengineering said:
Thanks for the reply. Not sure what you mean by booting the patched image first. You have to create the patched image on the phone first before you can flash and then boot it. Step 7 in my post above details the flashing of the patched image and subsequent attempt to reboot Oxygen OS. I can't boot the patched image until I've created and flashed it!
Click to expand...
Click to collapse
Nah, instead of flash the patched boot image you can boot it only. Not sure why it's not working for you. But usually it should work.
Command: fastboot boot "patched boot image"
Edit: that's also what lossyx said. Boot image and than install it with magisk manager.
And if you boot the image and something went wrong you aren't bricked or anything. It's a safe way to test something.
Thanks for the advice - will boot the image file on my PC rather than flashing first.
Sent from my AC2003 using Tapatalk
Does unlocking the bootloader break widewine L1 on this device like it did with 7/7T/7P/7TP/8/8P
..
CryllicBuster273 said:
Does unlocking the bootloader break widewine L1 on this device like it did with 7/7T/7P/7TP/8/8P
Click to expand...
Click to collapse
Yeah I guess when you unlock your phone it will break L1 as always.
---------- Post added at 12:17 PM ---------- Previous post was at 12:15 PM ----------
DIR49DNOR0N said:
I will try this unless twrp is cooked on release. Where did you get the OTA zips from actually?
I want to, extract boot.img, save it, patch boot.img, boot it, use some apps that require root and remove some packages, uninstall magisk, power down, use normal image, relock bootloader. Does this work how i expect it to work ?
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-nord/how-to/oneplus-nord-repo-oxygen-os-builds-t4138085
DIR49DNOR0N said:
I will try this unless twrp is cooked on release. Where did you get the OTA zips from actually?
I want to, extract boot.img, save it, patch boot.img, boot it, use some apps that require root and remove some packages, uninstall magisk, power down, use normal image, relock bootloader. Does this work how i expect it to work ?
Click to expand...
Click to collapse
No, keep the bootloader unlocked if your phone is modified, else it can cause some issues.
Btw when you lock/unlock the bootloader, data will be wiped. apps will be reinstated again so that's useless
The guide worked perfectly and I'm up and running with Root!
One thing I have noticed is that the Google Play store is no longer Play Protect Certified.
I've tried registering my device with Google using this XDA guide but I haven't found any change to the Play Store certification.
I should probably wait for a while to see if the registration takes some time. I also couldn't use the adb commands that Google recommends and I had to use the Device ID app to get the Google Service Framework (GSF).
I've read in a few places that it may be because the Bootloader is unlocked and I'm wondering if I should re-lock it now that I have root. Not sure how/if that will affect my ability to keep root when future updates come out though.
Anyone have any thoughts/experience with this?
Possible TWRP without waiting?
Can anyone use this and try? Might be used as an alternate Method for Rooting via TWRP
https://forum.xda-developers.com/an...g/guide-how-to-port-twrp-to-qualcomm-t3420013
Rooting the POCO M4 Pro 4G (fleur) turned out to be quite straightforward. Note, I have a 2201117PG (EEA), you may have a different experience, it's not my fault if you brick your phone etc. Backup before you start as this will wipe your phone.
The process can be broken down into 4 steps:
Unlock Bootloader
Source boot.img
Patch boot.img (using Magisk)
Flash patched boot.img (using adb)
1. Unlock BootloaderNote: This step will wipe your phone.
This can be done using the official tool from MIUI, using MediatekBootloaderUnlock (Windows 10/11, which reportedly does not wipe your user data), or using mtkclient (Any OS but requires Python). I will explain the mtkclient option as I'm on Linux and don't trust MIUI with more personal data than I have to.
Step-by-step (adapted from this How to Guide):
Install mtkclient and its dependencies (easier if familiar with installing python packages etc., straightforward for me on Linux)
On your phone activate developer mode and turn on USB debugging and OEM unlocking
Turn off phone and disconnect from computer
In the directory where you installed mtkclient run:
python mtk e metadata,userdata,md_udc
This erases your data
At this point plug your phone in (still turned off)
python mtk da seccfg unlock
This unlocks the bootloader
python mtk reset
This reboots the phone
Disconnect USB cable and reboot phone
When it boots a message is displayed warning that dm-verity is corrupted. Click the power button to dismiss and continue booting.
2. Source boot.img
Find your MIUI version in Settings -> About phone -> MIUI Version and look for the version number (e.g. 13.0.6.0(RKEEUXM))
Visit the MIUI Updates Tracker and download the matching Stable Fastboot update (if you can't find it scroll down to Extracting boot.img from Payload)
Unzip the TGZ and the TAR that it contains then navigate to the images directory and find the boot.img file
3. Patch boot.imgWe need to patch the boot.img to give it root powers. We do this on the phone using Magisk.
Step-by-step (adapted from the Magisk installation instructions):
On your phone, download Magisk and install it
Connect your phone to your computer and put the boot.img you extracted on your phone somewhere
Open Magisk and in "Magisk" section tap "Install"
Choose the "Select and Patch a File" option and select your boot.img in the file browser and let Magisk patch it
Find the patched boot image in Downloads (called magisk_patched_*.img) and copy it to your computer in the same directory as the vbmeta.img we extracted earlier
4. Flash patched boot.imgFinally we need to replace the current boot.img on the phone with our patched one that has root powers. This is called flashing and is done using adb.
Step-by-step:
Install the Android SDK platform tools which contains adb and fastboot
Install a USB driver that supports fastboot mode (you cannot use fastbootd for this or you'll bootloop)
Ensure your phone is connected, USB debugging is enabled and working, and OEM Unlocking is enabled
In the directory you copied the magisk_patched_*.img to run:
adb reboot bootloader
This reboots your phone into fastboot mode. Wait until "FASTBOOT" is displayed on the screen
fastboot flash boot magisk_patched_*.img
This flashes the patched boot.img to give you root
fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
This flashes the vbmeta.img, disabling the dm-verity corruption message at startup
Once it's done reboot your phone by pressing and holding the power button
That's all there is to it! This took me about an hour as I was working out all the steps as I've not rooted in a phone in nearly a decade - I reckon with a fast internet connection you could get it done in about 15 minutes.
Extract boot.img from PayloadIf you can't find a fastboot image (boot.img) for your version then you might be able to extract it from the full firmware package. This will require the use of a third party tool such as payload-dumper (python) or payload-dumper-go. Note that you may be better off just waiting for the fastboot image to be released to the public.
Tidying upYou can delete all the stuff you downloaded onto your computer and the boot.img and magisk_patched_*.img from your phone.
It's a good idea to disable automatic OTA updates (Settings -> Additional settings -> Developer options -> Automatic sytem updates) so that you can update through Magisk.
Some apps will be able to tell that you have rooted your phone, and may stop you from using them. You can check this by downloading YASNAC onto your phone and seeing if it passes. If not (which it won't) the most straightforward solution is to add the Universal SafetyNet Fix module to Magisk, then enable Zygisk in Magisk settings and restart your phone, which will be enough to pass SafetyNet Attestation. If they're clever and still detect the root then in Magisk toggle Enforce DenyList and add the problematic apps to the DenyList.
Updating Magisk
You cannot update Magisk via the Magisk app, as this device does not allow writing to the boot partition at runtime.
Instead, update the Magisk app, then use it to patch your stock boot.img and flash it manually using fastboot, as if you were installing it from scratch (as above). This will not wipe your user data, but be sure to backup first in case something goes wrong.
aricooperdavis said:
Rooting the POCO M4 Pro 4G (fleur) turned out to be quite straightforward. Note, I have a 2201117PG (EEA), you may have a different experience, it's not my fault if you brick your phone etc.
The process can be broken down into 4 steps:
Unlock Bootloader
Source boot.img (using payload_dumper)
Patch boot.img (using Magisk)
Flash patched boot.img (using adb)
1. Unlock BootloaderThis can be done using the official tool from MIUI or using mtkclient. I went for the mtkclient option as I don't want to send more of my personal data to MIUI than I have to.
Step-by-step (adapted from this How to Guide):
Install mtkclient and its dependencies (easier if familiar with installing python packages etc., straightforward for me on Linux)
On your phone activate developer mode and turn on USB debugging and OEM unlocking
Turn off phone and disconnect from computer
In the directory where you installed mtkclient run:
python mtk e metadata,userdata,md_udc
At this point plug your phone in (still turned off)
python mtk da seccfg unlock
python mtk reset
Disconnect USB cable and reboot phone
When it boots a message is displayed saying it is corrupted. Click the power button to dismiss and continue booting.
2. Source boot.imgThe boot.img needs to be extracted from the official MIUI firmware package using payload_dumper.
Step-by-step:
Download the firmware package for your device (you can check what version you need in Settings -> About phone -> MIUI version (For POCO)
Extract the .zip and find the payload.bin file
Download the payload dumper, extract the zip, and place the payload.bin file in the payload_dumper folder
In the payload_dumper directory run:
python payload_dumper.py payload.bin
This will extract lots of files from the firmware package. You only need to keep boot.img and vbmeta.img
3. Patch boot.imgWe need to patch the boot.img to give it root powers. We do this on the phone using Magisk.
Step-by-step (adapted from the Magisk installation instructions):
On your phone, download Magisk and install it
Connect your phone to your computer and put the boot.img you extracted on your phone somewhere
Open Magisk and in "Magisk" section tap "Install"
Choose the "Select and Patch a File" option and select your boot.img in the file browser and let Magisk patch it
Find the patched boot image in Downloads (called magisk_patched_*.img) and copy it to your computer in the same directory as the vbmeta.img we extracted earlier
4. Flash patched boot.imgFinally we need to replace the current boot.img on the phone with our patched one that has root powers. This is called flashing and is done using adb.
Step-by-step:
Install the Android SDK platform tools which contains adb and fastboot
Install a USB driver that supports fastboot mode
Ensure your phone is connected, USB debugging is enabled and working, and OEM Unlocking is enabled
In the directory you copied the magisk_patched_*.img to run:
adb reboot bootloader
This reboots your phone into fastboot mode. Wait until "FASTBOOT" is displayed on the screen
fastboot flash boot magisk_patched_*.img
fastboot flash vbmeta --disable-verity --dsable-verification vbmeta.img
Once it's done reboot your phone by pressing and holding the power button
That's all there is to it! This took me about an hour as I was working out all the steps as I've not rooted in a phone in nearly a decade - I reckon with a fast internet connection you could get it done in about 15 minutes.
Tidying upYou can delete all the stuff you downloaded onto your computer and the boot.img and magisk_patched_*.img from your phone.
It's a good idea to disable automatic OTA updates (Settings -> Additional settings -> Developer options -> Automatic sytem updates) so that you can update through Magisk.
Some apps will be able to tell that you have rooted your phone, and may stop you from using them. You can check this by downloading YASNAC onto your phone and seeing if it passes. If not (which it won't) the most straightforward solution is to add the Universal SafetyNet Fix module to Magisk, then enable Zygisk in Magisk settings and restart your phone, which will be enough to pass SafetyNet Attestation. If they're clever and still detect the root then in Magisk toggle Enforce DenyList and add the problematic apps to the DenyList.
Click to expand...
Click to collapse
Wow, Thank you very much!
Very details!
Will try it in my spare time.
MarkLev said:
Wow, Thank you very much!
Very details!
Will try it in my spare time.
Click to expand...
Click to collapse
Good luck, let us know how it goes and what you do with your root! So far I've installed AdAway and De-Bloater
aricooperdavis. hi!I buy phone Poco M4 Pro (4G) (fleur). Please help me get ROOT rights for this phone.
I do not have PYTHON, but I have mtkclient - the bootloader is unlocked, and there is an Android SDK for fastboot firmware.
Global 13.0.7.0 RKEMIXM now. You have 2 file 1.magisk_patched_*.img and 2. vbmeta.img for Global 13.0.7.0 ? Can I save them for download?
After unlocking the bootloader, using the mtkclient method, a new notification appeared
- dm-verity coruption
You device is corrupt/
It can't be trusted and may not work properly
Press power button to contime
Or, device will power off in 5 sec. Always need PRESS POWER for contime again How to fix it?
It sounds like you've done everything right so far.
Lark5 said:
Global 13.0.7.0 RKEMIXM now. You have 2 file 1.magisk_patched_*.img and 2. vbmeta.img for Global 13.0.7.0 ? Can I save them for download?
Click to expand...
Click to collapse
Sorry, I have the EEA firmware; RKEEUXM.
If you want to extract the boot.img and vbmeta.img from your firmware package you will have to install python. This is worth doing as installing updates in the future may require you to do this extraction process again.
Alternatively you may be able to use mtk to dump these images directly from the phone, but I don't have any experience with this. To perform updates this way you would have to completely unroot and relock the bootloader, update the firmware, then re-dump the new boot and vbmeta images and root again. I think just installing python is probably easier...
The error message you're seeing is dm-verity, and we disable this when flashing the vbmeta.img in step 4, which I've edited to clarify. You can see that we disable it in the final fastboot command:
aricooperdavis said:
fastboot flash vbmeta --disable-verity --dsable-verification vbmeta.img
This flashes the vbmeta.img, disabling the dm-verity corruption message at startup
Click to expand...
Click to collapse
Good luck with your rooting!
Unlock Bootloade and Root and RECOVERY for Poco M4 Pro (4G) with out Pyton (on Windows 10\11):
Unlock Bootloader:
1.Download the MediatekBootloaderUnlock archive. Unpack the archive ZIP.
2. Open the Driver folder and right-click the cdc-acm.inf file, select "Install"
3.Now go back to the main folder and install the USBDK (x64 for 64-bit OS, x86 for 32-bit OS) on your PC (also right click - install).
4. Reboot the PC.
5.Turn off the phone.
6.Run the UnlockBootloader.bat file to start the bootloader unlock process. We keep it on, it is in a state of response from the phone, if the firewood, the cable is connected, then everything is ok, I’ll tell you right away that it turned out 3 times.
7.Now connect the phone to the computer with a cable by holding down the volume up + down + power button. (If the volume up button doesn't work, try using volume up or volume up + volume down or all three hardware buttons) while the UnlockBootloader.bat file is open.
8.Once the phone is detected, some commands will be run in the UnlockBootloader.bat file. Let the commands finish and as soon as the window closes. Your bootloader will be unlocked.
BY THE WAY! - You can lock the bootloader again by following the same steps without clearing. Just use LockBootloader.bat with the same steps.
Root:
Downloading the official firmware for the phone, I took fleur_global_images_V13.0.7.0.RKEMIXM_20220419.0000.00_11.0_global (approximately 5.6GB in weight)
Unpacked it ZIP, pulled out 2 files from there fleur_global_images_V13.0.7.0.RKEMIXM_20220419.0000.00_11.0_global\images
boot.img and vbmeta.img
Downloaded Magisk STABLE Version: 24.3 - download on telephone, setup APP
Launch Magisk Manager. When a pop-up window appears asking you to install Magisk, select INSTALL and select install again.
Click on "Fix Boot Image File".
Connect your device to PC via USB cable. Make sure USB debugging is enabled.
Download ADB \ fastoot (I took tools_r29.0.6-windows)
Run CMD as Administrator
We write -
adb devices - the phone must be determined (QX ********* device - so all drivers are correct)
adb reboot bootloader - The phone reboots into fastboot mode - an inscription on the screen if dm-verity corruption messages appear - press POWER to continue
fastboot flash boot boot_PATCH.img (file name how to change)
fastboot flash vbmeta --disable-verity --dsable-verification vbmeta.img - will remove the inscription dm-verity corruption
OrangeFox-R11 RECOVERY:
Downloads for : -Android- Generic Device/Other | AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Download, and Run CMD as Administrator
We write -
fastboot flash boot XXXXNAMEXXXX.img
Flash !boot! not fastboot flash recovery XXXXNAMEXXXX.img
Well done, glad you've got it sorted!
To clarify, this essentially follows the same 4 steps outlined in my post but using different tools that don't require python:
Unlock Bootloader
- Used MediatekBootloaderUnlock rather than mtkclient
Source boot.img
- Managed to find the images online without having to extract them from a ROM. @Lark5, where?
Patch boot.img (using Magisk)
- Same
Flash patched boot.img (using adb)
- Same
I think there's also a custom recovery install too (OrangeFox [not yet officially supported]) at the end. I tend not to bother with custom recoveries as I stick with the stock MIUI ROM and a custom recovery would complicate applying OTA updates. However, if you wish to install a custom ROM (anything other than a stock MIUI signed boot.img) then a custom recovery would be necessary, and they can also facilitate taking device backups etc.
aricooperdavis said:
Well done, glad you've got it sorted!
To clarify, this essentially follows the same 4 steps outlined in my post but using different tools that don't require python:
Unlock Bootloader
- Used MediatekBootloaderUnlock rather than mtkclient
Source boot.img
- Managed to find the images online without having to extract them from a ROM. @Lark5, where?
Patch boot.img (using Magisk)
- Same
Flash patched boot.img (using adb)
- Same
I think there's also a custom recovery install too (OrangeFox). I tend not to bother, but it can be convenient.
Click to expand...
Click to collapse
2. Find ROM on this link: https://mirom.ezbox.idv.tw/en/phone/fleur/roms-global-stable/
Fastboot Download V13.0.7.0.RKEMIXM
Explanations:
For fastboot (~5.6Gb) - firmware version, just unzip the ZIP, inside there is boot.img and vbmeta
For recovery (-2.5Gb) needed to extract boot.img Through Pyton for example
thanks for the help aricooperdavis
Lark5 said:
Find ROM on this link: https://mirom.ezbox.idv.tw/en/phone/fleur/roms-global-stable/
Click to expand...
Click to collapse
That's a great resource - the files it links to seem to be hosted on MIUIs servers too, so they're verifiably official
The more general link for all regions (not just global) for this phone would be: https://mirom.ezbox.idv.tw/en/phone/fleur/
I've updated the instructions to reflect your experience, thanks @Lark5!
aricooperdavis said:
Rooting the POCO M4 Pro 4G (fleur) turned out to be quite straightforward. Note, I have a 2201117PG (EEA), you may have a different experience, it's not my fault if you brick your phone etc. Backup before you start as this will wipe your phone.
The process can be broken down into 4 steps:
Unlock Bootloader
Source boot.img
Patch boot.img (using Magisk)
Flash patched boot.img (using adb)
1. Unlock BootloaderNote: This step will wipe your phone.
This can be done using the official tool from MIUI, using MediatekBootloaderUnlock (Windows 10/11), or using mtkclient (Any OS but requires Python). I will explain the mtkclient option as I'm on Linux and don't trust MIUI with more personal data than I have to.
Step-by-step (adapted from this How to Guide):
Install mtkclient and its dependencies (easier if familiar with installing python packages etc., straightforward for me on Linux)
On your phone activate developer mode and turn on USB debugging and OEM unlocking
Turn off phone and disconnect from computer
In the directory where you installed mtkclient run:
python mtk e metadata,userdata,md_udc
This erases your data
At this point plug your phone in (still turned off)
python mtk da seccfg unlock
This unlocks the bootloader
python mtk reset
This reboots the phone
Disconnect USB cable and reboot phone
When it boots a message is displayed warning that dm-verity is corrupted. Click the power button to dismiss and continue booting.
2. Source boot.imgNote: if your MIUI version (Available at: Settings -> About phone -> MIUI version) has a "Fastboot" file listed here then you can download that file and unzip it to find the boot.img and vbmeta.img, then skip to step 3.
Otherwise you'll have to extract them from the official MIUI firmware package using payload_dumper as follows.
Step-by-step:
Download the firmware package for your device (you can check what version you need in Settings -> About phone -> MIUI version (For POCO))
Extract the .zip and find the payload.bin file
Download the payload dumper, extract the zip, and place the payload.bin file in the payload_dumper folder
In the payload_dumper directory run:
python payload_dumper.py payload.bin
This will extract lots of files from the firmware package. You only need to keep boot.img and vbmeta.img
3. Patch boot.imgWe need to patch the boot.img to give it root powers. We do this on the phone using Magisk.
Step-by-step (adapted from the Magisk installation instructions):
On your phone, download Magisk and install it
Connect your phone to your computer and put the boot.img you extracted on your phone somewhere
Open Magisk and in "Magisk" section tap "Install"
Choose the "Select and Patch a File" option and select your boot.img in the file browser and let Magisk patch it
Find the patched boot image in Downloads (called magisk_patched_*.img) and copy it to your computer in the same directory as the vbmeta.img we extracted earlier
4. Flash patched boot.imgFinally we need to replace the current boot.img on the phone with our patched one that has root powers. This is called flashing and is done using adb.
Step-by-step:
Install the Android SDK platform tools which contains adb and fastboot
Install a USB driver that supports fastboot mode
Ensure your phone is connected, USB debugging is enabled and working, and OEM Unlocking is enabled
In the directory you copied the magisk_patched_*.img to run:
adb reboot bootloader
This reboots your phone into fastboot mode. Wait until "FASTBOOT" is displayed on the screen
fastboot flash boot magisk_patched_*.img
This flashes the patched boot.img to give you root
fastboot flash vbmeta --disable-verity --dsable-verification vbmeta.img
This flashes the vbmeta.img, disabling the dm-verity corruption message at startup
Once it's done reboot your phone by pressing and holding the power button
That's all there is to it! This took me about an hour as I was working out all the steps as I've not rooted in a phone in nearly a decade - I reckon with a fast internet connection you could get it done in about 15 minutes.
Tidying upYou can delete all the stuff you downloaded onto your computer and the boot.img and magisk_patched_*.img from your phone.
It's a good idea to disable automatic OTA updates (Settings -> Additional settings -> Developer options -> Automatic sytem updates) so that you can update through Magisk.
Some apps will be able to tell that you have rooted your phone, and may stop you from using them. You can check this by downloading YASNAC onto your phone and seeing if it passes. If not (which it won't) the most straightforward solution is to add the Universal SafetyNet Fix module to Magisk, then enable Zygisk in Magisk settings and restart your phone, which will be enough to pass SafetyNet Attestation. If they're clever and still detect the root then in Magisk toggle Enforce DenyList and add the problematic apps to the DenyList.
Click to expand...
Click to collapse
When I gave this command fast boot flash dm verify it always unknown option in my cmd any solution ? can anybody help me??
Daafafagsgsgs said:
When I gave this command fast boot flash dm verify it always unknown option in my cmd any solution ? can anybody help me??
Click to expand...
Click to collapse
Make sure you're copying the command exactly - it's fastboot rather than fast boot and verity not verify. Did you install the Android SDK platform tools that contain fastboot? You may need to restart after this install to make the command available in your command prompt/shell.
aricooperdavis said:
Make sure you're copying the command exactly - it's fastboot rather than fast boot and verity not verify. Did you install the Android SDK platform tools that contain fastboot? You may need to restart after this install to make the command available in your command prompt/shell.
Click to expand...
Click to collapse
Yeah i copied the same command but how to install Android sdk tools can you suggest me a video?
Daafafagsgsgs said:
Yeah i copied the same command but how to install Android sdk tools can you suggest me a video?
Click to expand...
Click to collapse
Go to this link, scroll to the downloads section, and select the right download for your OS, then follow the instructions.
This video shows the process, but has very annoying music!
aricooperdavis said:
Make sure you're copying the command exactly - it's fastboot rather than fast boot and verity not verify. Did you install the Android SDK platform tools that contain fastboot? You may need to restart after this install to make the command available in your command prompt/shell.
Click to expand...
Click to collapse
I installed and tried everything this error comes
Interesting, that sounds like you've got an outdated version of fastbook. What does fastboot --version give you?
Can i flash it with my phone ??
Adb otg app??
I don't know, I can't help you with that.
aricooperdavis said:
Interesting, that sounds like you've got an outdated version of fastbook. What does fastboot --version give you?
Click to expand...
Click to collapse
Fastboot version
That's not an official version of fastboot, so it looks like it's missing the command you need. Download the proper Android SDK tools from Android (the same as the original link) and replace your "Minimal" version with it.
aricooperdavis said:
That's not an official version of fastboot, so it looks like it's missing the command you need. Download the proper Android SDK tools from Android (the same as the original link) and replace your "Minimal" version with it.
Click to expand...
Click to collapse
After many tries i found that the command given is wrong
fastboot flash vbmeta --disable-verity --dsable-verification vbmeta.img
This is given
It will be
fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
I is Missing Now i have flashed vb meta and problem is solved with the fastboot version i have
By the way thanks