Database Develop

Trying to flash twrp recovery...getting error "target reported max download..."

Trying to flash twrp recovery...getting error "target reported max download..."
I'm trying to install twrp recovery but getting the error message: Target reported max download size of 536870912 bytes; error: cannot load 'twrp.img': unknown error
The phone was previously unlocked and rooted on lollipop....had problems and restored...took OTA update to Marshmallow 6.0.1
Any ideas? Please and thanks!

DoritoKing said:
I'm trying to install twrp recovery but getting the error message: Target reported max download size of 536870912 bytes; error: cannot load 'twrp.img': unknown error
The phone was previously unlocked and rooted on lollipop....had problems and restored...took OTA update to Marshmallow 6.0.1
Any ideas? Please and thanks!
Click to expand...
Click to collapse
1) how are you trying to install TWRP?
2) You are using the most recent version from our official TWRP maintainer?
January 12, 2017
twrp-3.0.3-0-Mod_01-quark.img
https://www.androidfilehost.com/?fid=745425885120699982
3) And you are showing known file extensions in Windows? Do you know what that means?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If you have a jpg or pdf, and you see a file name -- do you also ALWAYS, ALWAYS see the extension like jpg or pdf? Default in Windows -- for idiotic reasons -- is to "hide known file extensions".
Make sure that box is UNchecked in your Windows settings. Because otherwise you are re-naming TWRP as TWRP.img(.img). You do NOT have to type the .img part, it's ALREADY an .img file.
That may or may not be your issue, but it messed up a lot of people in the past. ADB couldn't find TWRP.img because they had unknowingly called it TWRP.IMG.img -- because they couldn't see the file extension and thought they needed to add it to the file name.

1. I had the previous version 3.0.2-0...will try your link.
2. I unchecked the extension box...
will try again and let you know...thank you!

Just tried with the changes....still getting same error messages.

DoritoKing said:
1. I had the previous version 3.0.2-0...will try your link.
2. I unchecked the extension box...
will try again and let you know...thank you!
Click to expand...
Click to collapse
When you unchecked the extension box, what is now the visible name of your TWRP file? Does it say TWRP.img.img or just TWRP.img? Besides unchecking the extension box, you also need to make sure you are typing the actual name of the file. IF you had typed "TWRP.img"(.img) before, you now need to re-name it just "TWRP".img.
If you confirm that's not the issue, then we'll get @bhb27 involved over in the Quark TWRP thread.

I changed the filename to twrp and I'm using the command: fastboot flash recovery twrp.img and I've tried every other combination of twrp.img.img, twrp, etc just to make sure I wasn't missing something!
My goal is to be able to flash a new build.prop to allow for tethering...if there is a way to do that without installing twrp, that would be great

DoritoKing said:
I changed the filename to twrp and I'm using the command: fastboot flash recovery twrp.img and I've tried every other combination of twrp.img.img, twrp, etc just to make sure I wasn't missing something!
My goal is to be able to flash a new build.prop to allow for tethering...if there is a way to do that without installing twrp, that would be great
Click to expand...
Click to collapse
OK, just as a test, do this. Forget the name TWRP. That's just a convenience. Call it something else. Rename it box or chair. I'm not joking. Then, in your PC, what file name do you see? IF you renamed it "box", you should see box.img. You do NOT type .img. It's just the extension that should already be there!
then flash: fastboot flash recovery box.img
I'm suggesting this because somehow, somewhere it seems your file name is messed up?
Also you have done all this too? Permissions and stuff?
Enable USB debugging on your device:
Open Settings on your device.
Go to About phone and tap seven times on Build number, this will enable Developer options.
Now go back to Settings and you’ll see Developer options there, open it.
Tick the USB Debugging checkbox.
Connect your device to the PC. And type the following into the command window we opened to boot your device into bootloader/fastboot mode:
adb reboot bootloader
└ If you get a permission dialogue on your device to “Allow USB debugging”, tap OK.
Click to expand...
Click to collapse
Maybe revoke those permissions and re-enable them?

Renamed it "dummy"....the name I see on my file list is "dummy"......Still getting same error message. I tried recovery dummy.img and recovery dummy....still same error.
adb reboot bootloader works....cant flash the recovery image though. Do I need to do something else on the phone side prior to flashing the image? It has the android laying on its back with the "Start" option showing on top...

DoritoKing said:
Renamed it "dummy"....the name I see on my file list is "dummy"......Still getting same error message. I tried recovery dummy.img and recovery dummy....still same error.
adb reboot bootloader works....cant flash the recovery image though. Do I need to do something else on the phone side prior to flashing the image? It has the android laying on its back with the "Start" option showing on top...
Click to expand...
Click to collapse
I was just suggesting you revoke the USB permissions and re-enable them in Developer Settings, just to make sure. That's the only thing I'm aware of you need to do on the phone side... If anyone knows something different, feel free to correct me!
@bhb27 is our TWRP maintainer for our official TWRP. So, I'm mentioning him here so he'll see this issue. Maybe he'll have some ideas?
Also, you you can post this issue over in the Quark TWRP thread. You can put a link to this thread in your post, so people can see what all we've tried.
[RECOVERY][OFFICIAL TWRP 3.0.2-0][For all Quark][Moto Maxx/Turbo and Droid Turbo]
https://forum.xda-developers.com/mo...recovery-twrp-2-8-7-0-touch-recovery-t3180308

I need print screen of what is going on in the terminal when the problem is manifested...
need a print screen of the folder were adb, fastboot and the recovery files are.
need a print screen of the content of properties of the twrp.img

bhb27 said:
I need print screen of what is going on in the terminal when the problem is manifested...
need a print screen of the folder were adb, fastboot and the recovery files are.
need a print screen of the content of properties of the twrp.img
Click to expand...
Click to collapse
Here are the screenshots...if this isn't what you were looking for, just let me know.

DoritoKing said:
Here are the screenshots...if this isn't what you were looking for, just let me know.
Click to expand...
Click to collapse
Yes it is.
can you try this fastboot?
https://www.androidfilehost.com/?fid=24052804347845784
add a m to fastboot command
Code:
mfastboot flash recovery twrp
if it fails give
Code:
mfastboot devices
and print the screen...
:good:

bhb27 said:
Yes it is.
can you try this fastboot?
https://www.androidfilehost.com/?fid=24052804347845784
add a m to fastboot command
Code:
mfastboot flash recovery twrp
if it fails give
Code:
mfastboot devices
and print the screen...
:good:
Click to expand...
Click to collapse
Didn't recognize that command...here is the screenshot

You can't just flash a file called twrp and that's it. It needs to be twrp.img. Also, in order for mfastboot (or any other .exe file) to work in a command prompt, you need to navigate to the folder that it is present in. Is mfastboot.exe located in C:\Documents and Settings\Jason? If not, that's why it isn't found.

DoritoKing said:
Didn't recognize that command...here is the screenshot
Click to expand...
Click to collapse
did you download the file I share?

TheSt33v said:
You can't just flash a file called twrp and that's it. It needs to be twrp.img. Also, in order for mfastboot (or any other .exe file) to work in a command prompt, you need to navigate to the folder that it is present in. Is mfastboot.exe located in C:\Documents and Settings\Jason? If not, that's why it isn't found.
Click to expand...
Click to collapse
I didn't know how to open my command prompt in a particular folder, but I figured that out now. I was able to try again and run the original fastboot and it worked! I've got TWRP on my phone!!
I've attached a screenshot. I was told that when I type the commands, to not include the .img for the TWRP file.....so I just typed fastboot flash recovery twrp and it worked.
Thank you everyone for all your help. I'm a newbie, so I appreciate everyone being patient when I don't know how to do certain things correctly.

TheSt33v said:
You can't just flash a file called twrp and that's it. It needs to be twrp.img. Also, in order for mfastboot (or any other .exe file) to work in a command prompt, you need to navigate to the folder that it is present in. Is mfastboot.exe located in C:\Documents and Settings\Jason? If not, that's why it isn't found.
Click to expand...
Click to collapse
Right. His screenshot is showing other extensions, like .exe, .txt, .dll -- so his TWRP extension should be .img. It's missing.
What I cautioned him about was double naming the extension -- TWRP.img.img, which can accidentally be done if you have your Windows settings to hide known file extensions. Since his file extensions are no longer hidden, his TWRP file should say TWRP.img.
But naming it TWRP is just a convenience instead of using the regular file name like "twrp-3.0.3-0-Mod_01-quark.img". It's easier to type TWRP.img in the Windows command box than that long official file name. You could easily also re-name it "chair.img" or "box.img" as long as you were re-naming the correct file. I even suggested he do that because he seemed hung up over the TWRP name.
At this point, he probably needs to also re-download the TWRP file and re-name it. Now that he can see file extensions, it should automatically have the .img extension.

Me again...the guy who probably shouldn't be messing with his phone
I got TWRP installed. Tried flashing a zip for tethering...upon reboot it was getting stuck at bootloader warning screen. Eventually tried a wipe through TWRP (data, cache, and dalvik) and a factory reset through the phone menu, but still keeps getting stuck at bootloader. I can still get into TWRP, but not sure where to go from here
Do I need to do the wipe differently? Anyway to get past the bootloader screen?

DoritoKing said:
Me again...the guy who probably shouldn't be messing with his phone
I got TWRP installed. Tried flashing a zip for tethering...upon reboot it was getting stuck at bootloader warning screen. Eventually tried a wipe through TWRP (data, cache, and dalvik) and a factory reset through the phone menu, but still keeps getting stuck at bootloader. I can still get into TWRP, but not sure where to go from here
Do I need to do the wipe differently? Anyway to get past the bootloader screen?
Click to expand...
Click to collapse
I'm going to hazard a guess here that you also flashed SuperSu in TWRP and you are running the new Marshmallow update. (Yeah, confirmed, I just checked your first post. You took Marshmallow update.) In which case, it sounds like you flashed the wrong version of SuperSu. You have to flash an older version for initial root or your phone will stick at the bootloader warning screen. This has been discussed in all the Marshmallow threads.
What version SuperSu are you using? If on stock Marshmallow or stock-based Marshmallow ROM, the one required is BETA-SuperSU-v2.62-3-20151211162651). You can boot into TWRP, plug your phone into a PC and drag it over like a flash drive. It will show up in the root folder. Flash it, wipe all caches, reboot.
I've attached it to this post.
AFTER initial root, and after you successfully boot, then you can update to newest version of SuperSu. You just need it for initial root and to successfully boot the first time.
PREDICTION: Your next question will be how to get rid of the unlocked bootloader screen. Because you will see it every time you reboot your phone. When you do, here's your answer. But first, you need to flash the correct SuperSu to get past the bootloader screen.

DoritoKing said:
I didn't know how to open my command prompt in a particular folder, but I figured that out now. I was able to try again and run the original fastboot and it worked! I've got TWRP on my phone!!
I've attached a screenshot. I was told that when I type the commands, to not include the .img for the TWRP file.....so I just typed fastboot flash recovery twrp and it worked.
Thank you everyone for all your help. I'm a newbie, so I appreciate everyone being patient when I don't know how to do certain things correctly.
Click to expand...
Click to collapse
Congratulations on installing TWRP.

P-SMR3-RC002-RZR-200226.3141 Factory Image for fastboot

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
System Image: https://drive.google.com/file/d/1cAcgP55upO6UuX-gecPIXA_xnO0IXvUO/view?usp=sharing
Flash System Image:
- Download the appropriate system image for the Razer Phone from here, then unzip it to a safe directory.
- Connect your Razer Phone to your computer over USB.
- Start the Phone in Download Mode with one of the following methods:
- Using the adb tool: With the Phone powered on, execute: adb reboot bootloader
- Enter Download Mode: Plug in a USB cable to connect your Razer Phone to your computer, Power Off the Phone, then turn it on and immediately press and hold the Volume Down button until “Download Mode” appears on screen.
- If necessary, unlock the Phone’s bootloader. See Unlocking the Bootloader and Unlocking the Bootloader Critical Partitions for instructions.
- Open a terminal on your computer and navigate to the unzipped system image directory.
- Execute the flash_all script. This script installs the necessary bootloader, baseband firmware(s), and operating system for your Razer Phone.
- Once the script finishes, your Phone will reboot.
- You should now lock the bootloader for security.

Is this the global version?
Also, is there a list regarding the detail of each img file, and that whether they're considered safe to be flashed/updated?

LSS4181 said:
Is this the global version?
Also, is there a list regarding the detail of each img file, and that whether they're considered safe to be flashed/updated?
Click to expand...
Click to collapse
Yes very much so global
#1 - I can't read his info screenshot :silly: & #2 it's the same build number
I haven't flashed it personally but I would go out on a limb and say it's safe to flash

JDBarlow said:
Yes very much so global
#1 - I can't read his info screenshot :silly: & #2 it's the same build number
I haven't flashed it personally but I would go out on a limb and say it's safe to flash
Click to expand...
Click to collapse
I mean the detail of each img file. Since I'm now on a GSI I've only flashed the updated vendor.img so far (in my case, from MR1 to MR2). I'm not sure about other non-system parts (something like bluetooth, dsp, which are probably firmware blobs), and whether these are safe to be flashed/updated (however, some of those blobs do have diffs in the OTA).

LSS4181 said:
I mean the detail of each img file. Since I'm now on a GSI I've only flashed the updated vendor.img so far (in my case, from MR1 to MR2). I'm not sure about other non-system parts (something like bluetooth, dsp, which are probably firmware blobs), and whether these are safe to be flashed/updated (however, some of those blobs do have diffs in the OTA).
Click to expand...
Click to collapse
I see what you're saying
SMS working fine on the GSI you're running? I believe I read somewhere that someone was able to get latest Havoc to work

JDBarlow said:
I see what you're saying
SMS working fine on the GSI you're running? I believe I read somewhere that someone was able to get latest Havoc to work
Click to expand...
Click to collapse
I'm on Havoc 3.2.
Actually it was thanks to Reznor7's advice (first install it as a normal app, then move the installed folder to system) that I was able to get most of the things working (SMS, VoLTE).

LSS4181 said:
I'm on Havoc 3.2.
Actually it was thanks to Reznor7's advice (first install it as a normal app, then move the installed folder to system) that I was able to get most of the things working (SMS, VoLTE).
Click to expand...
Click to collapse
Perfect.
I can confirm this image does work ?
Something odd happened after flashing Havoc 3.3 I pulled my SIM card and reinsert it in the phone and my SIM card stopped working. I had to replace it ?

JDBarlow said:
Perfect.
I can confirm this image does work ?
Something odd happened after flashing Havoc 3.3 I pulled my SIM card and reinsert it in the phone and my SIM card stopped working. I had to replace it ?
Click to expand...
Click to collapse
Where did you get Havoc 3.3? Even ExpressLuke hasn't any Havoc 3.3 GSI build for ARM64/AB from what I could see (the SourceForge page still lists the 3.2 one as the latest).

LSS4181 said:
Where did you get Havoc 3.3? Even ExpressLuke hasn't any Havoc 3.3 GSI build for ARM64/AB from what I could see (the SourceForge page still lists the 3.2 one as the latest).
Click to expand...
Click to collapse
/HavocOS/Ten/20200402-vanilla/Havoc-OS-v3.3-20200402-arm64-ab-vanilla-nosu.img.xz

If anyone can get havoc 3.3 to work on Verizon without the sim card issue please let me know. No gsi rom will work on Verizon. Its frustrating. Thanks.

Finally got the MR3 update extracted
I worked all night extracting/converting the stock img and got beat by minutes posting Lol... anyway I also have the stock ota for global variant of MR3 if anyone needs it. You can easily patch the boot img with magisk and fastboot flash boot_a with the patched boot img and you have root again on MR3 Update. Works flawless

i Take a copy Thank You

Flashed some stuffs from MR3: modem (both), bluetooth (both), dsp (both), vendor (both), boot (inactive B slot only), system (inactive B slot only). These seem to work.
However, when flashing system and vendor I saw it mentioned something about "invalid sparse file format at header magic", but the flashed stuffs (at least vendor) looks fine.
Also, not sure if it's because of my Linux distro's (Manjaro/Arch) fastboot version or some other reasons (the cables are fine), I could only properly issue a fastboot command right after the phone restarted to bootloader. After that, the commands would stuck at Sending. Ctrl-C won't work at this point. I could only get out by unplugging the cable, and after that the phone won't be detected until I restart the bootloader again (if I issue a fastboot command here, it'll show <waiting for device>, but when the phone restarted, the command would begin and succeed).
Havoc 3.3 GSI works fine here (the SELinux fix may still be needed for it to boot). However, for some reasons (either due to recent Magisk canary update, or something else), I lost access to VoLTE and that after updating to the new GSI version, all my app's permissions were lost and I need to reassign them (maybe it's time I back things up and start over again, as the permission reset issue can indeed happen when dirty-flashing newer GSI versions).

LSS4181 said:
Also, not sure if it's because of my Linux distro's (Manjaro/Arch) fastboot version or some other reasons (the cables are fine), I could only properly issue a fastboot command right after the phone restarted to bootloader. After that, the commands would stuck at Sending. Ctrl-C won't work at this point. I could only get out by unplugging the cable, and after that the phone won't be detected until I restart the bootloader again (if I issue a fastboot command here, it'll show <waiting for device>, but when the phone restarted, the command would begin and succeed).
Click to expand...
Click to collapse
Running Manjaro Linux here too and experience the same behaviour.
Peace.

Can you dirty flash the mentioned images? Don't really feel like reinstalling all my apps and data.

is there a new root method
i have this factory image on my phone but i cant find any root guide for this version. i have my bootloader unlocked already and patched this factory image with Magisk. i copied the patched boot file to my platform-tools folder where the adb.exe is.
after running the commands adb devices it shows me my phone and serial number fine. (yes usb debugging is on)
so i continue and restart my phone into fastboot mode and type into the console astboot flash boot magisk_patched.img (thats the name of the file created by magisk)
after that the consol just responds waiting for device and nothing happens.
i already installed the adp usb drivers and the google usb drivers. but the consol only finds my phone when it is turned on and not while in fastboot mode
edit : btw one thing im not clear about, how should i format the SD card ? mobil or intern for more space
any solutions?
Cheers Mystix

MystixBlack said:
i have this factory image on my phone but i cant find any root guide for this version. i have my bootloader unlocked already and patched this factory image with Magisk. i copied the patched boot file to my platform-tools folder where the adb.exe is.
after running the commands adb devices it shows me my phone and serial number fine. (yes usb debugging is on)
so i continue and restart my phone into fastboot mode and type into the console astboot flash boot magisk_patched.img (thats the name of the file created by magisk)
after that the consol just responds waiting for device and nothing happens.
i already installed the adp usb drivers and the google usb drivers. but the consol only finds my phone when it is turned on and not while in fastboot mode
edit : btw one thing im not clear about, how should i format the SD card ? mobil or intern for more space
any solutions?
Those usb drivers didn't work for me. What did work however was the samsung usb drivers so I downloaded them and installed, however that wasn't enough. While in fastboot mode under device manager, I can't recall how I installed it but I forced the driver either from android device in list or added new legacy hardware and installed samsung android adb interface. After that when I typed fastboot devices in console from tools folder it reported back for me. I hope this helps.
Click to expand...
Click to collapse

I have 2 questions.
1. Can you flash this on other builds?
2. can any one link to P-SMR3-RC002-CKH-200226.3132 Build
Very much appriciated :good:

MystixBlack said:
i have this factory image on my phone but i cant find any root guide for this version. i have my bootloader unlocked already and patched this factory image with Magisk. i copied the patched boot file to my platform-tools folder where the adb.exe is.
after running the commands adb devices it shows me my phone and serial number fine. (yes usb debugging is on)
so i continue and restart my phone into fastboot mode and type into the console astboot flash boot magisk_patched.img (thats the name of the file created by magisk)
after that the consol just responds waiting for device and nothing happens.
i already installed the adp usb drivers and the google usb drivers. but the consol only finds my phone when it is turned on and not while in fastboot mode
edit : btw one thing im not clear about, how should i format the SD card ? mobil or intern for more space
any solutions?
Cheers Mystix
Click to expand...
Click to collapse
I u forgot something....
Fastboot flash boot_a magisk_patched.img
Fastboot flash boot_b magisk_patched.img

Xinfuzemodz said:
I have 2 questions.
1. Can you flash this on other builds?
2. can any one link to P-SMR3-RC002-CKH-200226.3132 Build
Very much appriciated :good:
Click to expand...
Click to collapse
Are you serious? The link of the OP is the link to MR3. If you click the flash_all.bat file it will wipe your phone and you get a fresh copy of MR3 installed so yes it can be installed on other builds

Question How to flash twrp recovery and root redmi note 10s?

I can't install a twrp recovery if I tried
A message appears (remote : this partition doesn't exist)

You wont be able to find rosemary's twrps yet... But you can root this model unlocking bootloader and flashing a modified boot.img from magisk APK, you can follow this instructions to do that; (you'll need the redmi note 10 s original rom firmware to extract the boot img and you can get it from here: https://c.mi.com/es/miuidownload/detail?device=1900397)
First, extract the boot.img file from Redmi Note 10 firmware. You can use 7Zip or WinRAR.​
Now install the Magisk Manager app on your phone.​
Open the Magisk Manager app and click on the Install.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
In the next step choose ‘Select and Patch a File’ from the option.
Browse and select the boot.img file, and it will start patching the boot image.​
The output file will be stored in the download folder with the name magisk_patched.img.​
Copy the patched boot image file to your computer in folder C:\adb. Also, rename the patched file to boot.img.​
Reboot your Redmi Note 10 to Fastboot mode and connect it to your computer.​
In the C:\adb folder (or platform-tools folder) press Shift + Right click on an empty area and select ‘Open Command window here’ or ‘Open PowerShell window here.’
You can check if the device is connected or not by entering the below command that should return some device id.​
fastboot devices​
Now enter the below command to flash Magisk and root Redmi Note 10.​
fastboot flash boot boot.img​
After flashing the patched boot image. reboot your device to the system.​
Install Magisk Manager if it’s not already installed.​
Complete the in-app instructions, and the device will automatically reboot into the system.​
That’s all, now your phone is rooted. You can check for root access using any root checker app. And once you have root access on your Redmi Note 10, you can enjoy all the apps and features that require root access. As you know Xiaomi phones show ads on some system apps that you can disable with root access. You can use different Xposed Modules to customize your phone. Also, you can install Xposed Framework on your phone to use modules.
Or if your system has an a/b partition you'll have to type this on your command window:
fastboot flash boot_a patched_boot.img
fastboot flash boot_b patched_boot.img

Or follow this page... https://mytechgyangadgets.com/how-to-root-redmi-note-10s-via-magisk-and-supersu/

Ali mohamed 96 said:
I can't install a twrp recovery if I tried
A message appears (remote : this partition doesn't exist)
Click to expand...
Click to collapse
Theres 2 ways to do It explained up but i prefer first one

This is a questionable part I think:
1. If your phone doesn’t have A/B partition system:
fastboot flash boot boot.img
2. If your phone has A/B partition system:
fastboot flash boot_a patched_boot.img
fastboot flash boot_b patched_boot.img
Based on the Treble Check app, at least my phone, supported Seamless System Updates and is detected to have an A/B system partition => should be used 2?
This might be a reason of : "this partition doesn't exist" with 1.
Source: https://www.naldotech.com/root-xiaomi-redmi-note-10s-magisk/

#bosr you have to follow the second step pf your post yo success, It seems that note's 10 has an a/b system partition...

!! Success !!
The process I´ve rooted my Redmi Note 10s with V12.5.8.0.RKLEUXM ROM:
(besides all needed drivers, adbs, proper fasboot ROM version, unlocked bootloader, little bit of a fear that the phone could be hard bricked and a few more) :
- patched boot.img via magisk manager v23
- flashed empty vbmeta.img as decribed here https://forum.xda-developers.com/t/root-gained.4290689/
- flashed patched_boot.img (the latest platform-tools flashed it directly to boot_a)
- reboot
Voila, Redmi Note 10s is rooted and Magisk v23 installed

Ricardo 182 said:
You wont be able to find rosemary's twrps yet... But you can root this model unlocking bootloader and flashing a modified boot.img from magisk APK, you can follow this instructions to do that; (you'll need the redmi note 10 s original rom firmware to extract the boot img and you can get it from here: https://c.mi.com/es/miuidownload/detail?device=1900397)
First, extract the boot.img file from Redmi Note 10 firmware. You can use 7Zip or WinRAR.​
Now install the Magisk Manager app on your phone.​
Open the Magisk Manager app and click on the Install.
In the next step choose ‘Select and Patch a File’ from the option.
Browse and select the boot.img file, and it will start patching the boot image.​
The output file will be stored in the download folder with the name magisk_patched.img.​
Copy the patched boot image file to your computer in folder C:\adb. Also, rename the patched file to boot.img.​
Reboot your Redmi Note 10 to Fastboot mode and connect it to your computer.​
In the C:\adb folder (or platform-tools folder) press Shift + Right click on an empty area and select ‘Open Command window here’ or ‘Open PowerShell window here.’
You can check if the device is connected or not by entering the below command that should return some device id.​
fastboot devices​
Now enter the below command to flash Magisk and root Redmi Note 10.​
fastboot flash boot boot.img​
After flashing the patched boot image. reboot your device to the system.​
Install Magisk Manager if it’s not already installed.​
Complete the in-app instructions, and the device will automatically reboot into the system.​
That’s all, now your phone is rooted. You can check for root access using any root checker app. And once you have root access on your Redmi Note 10, you can enjoy all the apps and features that require root access. As you know Xiaomi phones show ads on some system apps that you can disable with root access. You can use different Xposed Modules to customize your phone. Also, you can install Xposed Framework on your phone to use modules.
Or if your system has an a/b partition you'll have to type this on your command window:
fastboot flash boot_a patched_boot.img
fastboot flash boot_b patched_boot.img
Click to expand...
Click to collapse
"
First, extract the boot.img file from Redmi Note 10 firmware. You can use 7Zip or WinRAR."
I am not able to see boot.img file in the extracted rom. I used the same link that you had shared to download the rom. This is the file name - miui_ROSEMARYINGlobal_V12.5.5.0.RKLINXM_ab4be8a721_11.0.zip.
What is the mistake I am making?

GildroY said:
"
First, extract the boot.img file from Redmi Note 10 firmware. You can use 7Zip or WinRAR."
I am not able to see boot.img file in the extracted rom. I used the same link that you had shared to download the rom. This is the file name - miui_ROSEMARYINGlobal_V12.5.5.0.RKLINXM_ab4be8a721_11.0.zip.
What is the mistake I am making?
Click to expand...
Click to collapse
Also checked the global rom from here https://xiaomifirmwareupdater.com/miui/rosemary/stable beta/V12.5.12.0.RKLMIXM/
Same thing - cant find the boot.img

GildroY said:
Also checked the global rom from here https://xiaomifirmwareupdater.com/miui/rosemary/stable beta/V12.5.12.0.RKLMIXM/
Same thing - cant find the boot.img
Click to expand...
Click to collapse
You are searching in the wrong type of ROM. It must be the fastboot type.
for example: rosemary_global_images_V12.5.11.0.RKLMIXM_20210618.0000.00_11.0_global_06239807c1.tgz
Unpack (winrar, winzip, 7-zip ...) it, there is a folder images and boot.img in it
Do not forget to flash empty vbmeta.img first, see here

bosr said:
You are searching in the wrong type of ROM. It must be the fastboot type.
Unzip it, there is a folder images and boot.img in it
Click to expand...
Click to collapse
Yeah. Apologies. Just realized it.

I was able to successfully get root access using the additional step mentioned by @bosr (Thanks a lot for that). However post that I literally bricked my device trying to debloat the device by using debloater. Post removing few of the mi bloatware apps, when I rebooted and the device kept on going into default mi recovery (even with power + vol-). I was not able to access the fastboot mode at all, no matter what I do.
Then I did the ultimate blunder ... reset the device from mi recovery. Post that I lost adb privileges as well. Besides the phone would still not boot - MIUI logo flashed with sound, then a white setup screen for a sec and again reboot.
Searching online could not fetch anything. Then I tried moving the phone to mi assistance mode from mi recovery (which is nothing but sideload mode), connect to PC and used 'adb sideload'.
Voila, the phone was detected, from sideload mode, I was able to reboot to fastboot mode, and then flash the stock rom using miflashtool. Whole 4 hours of tussle.
Sharing here, just in case someone else, gets into the same situation.
!! BADLY WAITING FOR A CLEAN ROM FOR THIS DEVICE .... <Prayers>!!

It is strange.
I did it on two "10s" devices with EAA roms w/o problems.
Did you flash flash empty vbmeta.img first and boot.img than?
Did you use the latest platform-tools as previous ones are not able to flash directly to boot_a) automatically and you must use fastboot flash boot_a command instead.

bosr said:
It is strange.
I did it on two "10s" devices with EAA roms w/o problems.
Did you flash flash empty vbmeta.img first and boot.img than?
Did you use the latest platform-tools as previous ones are not able to flash directly to boot_a) automatically and you must use fastboot flash boot_a command instead.
Click to expand...
Click to collapse
Apologies for incorrect use of language. What I meant was that your instructions were 100% correct and accurate. However, post getting root access successfully and magisk installed, I tried to debloat the device using 'debloater' module under Magisk and ended up deleting some rogue apps which Mi wants us to keep. All the issues happened after that.
I have updated my original comment as well.

OK. Apology accepted

Hi Y'all,
I just got a new Note 10s and I'm willing to root device.
I'm still in the phase of waiting for the unlocked bootloader, but already trying to get all the necessary data for root.
While searching for the fastbbot Rom to extract the boot.img I discovered the follwing problem:
I can only find the fastboot Rom for the following SW: V12.5.8.0.RKLEUXM
But my Note 10s is already on V12.5.10.0.RKLEUXM. For this SW only the recovery ROM is available.
How long will it take for Xiaomi to upload the latest fastboot ROM? Or am I doing something wrong,
Any help really appreciated
Andreas

I also got a new Note 10s. I updated it to the latest available version (12.5.8.0 RKLEUXM, EEA).
Downloaded these ROMs (recovery and fastboot):
miui_ROSEMARYEEAGlobal_V12.5.8.0.RKLEUXM_b29e7c6a8a_11.0.zip
rosemary_eea_global_images_V12.5.8.0.RKLEUXM_20210617.0000.00_11.0_eea_6ec37534bb.tgz
But I didn't found any boot.img in the last fastboot one.
Finally I extracted boot.img from the first one (recovery) using payload_dumper - but what's wrong with the easier and usual way to extract it from the fastboot ROM? Isn't it available anymore inside this ROM?
@Agzyx
You could try the payload_dumper method to extract boot.img from recovery ROM.

@Mac23
payload_dumper may be a solution. I need to wait another 5 days for bootloader unlock anyway, so I have some more time before trying to gain root access.
@All
Is there a way to "downgrade" to V12.5.8.0.RKLEUXM?
Loss of data is no problem, as the phone will be rooted anyway in the future.
Andreas

Agzyx said:
@Mac23
payload_dumper may be a solution. I need to wait another 5 days for bootloader unlock anyway, so I have some more time before trying to gain root access.
@All
Is there a way to "downgrade" to V12.5.8.0.RKLEUXM?
Loss of data is no problem, as the phone will be rooted anyway in the future.
Andreas
Click to expand...
Click to collapse
It should be possible with XiaoMiTool

Mac23 said:
I also got a new Note 10s. I updated it to the latest available version (12.5.8.0 RKLEUXM, EEA).
Downloaded these ROMs (recovery and fastboot):
miui_ROSEMARYEEAGlobal_V12.5.8.0.RKLEUXM_b29e7c6a8a_11.0.zip
rosemary_eea_global_images_V12.5.8.0.RKLEUXM_20210617.0000.00_11.0_eea_6ec37534bb.tgz
But I didn't found any boot.img in the last fastboot one.
Finally I extracted boot.img from the first one (recovery) using payload_dumper - but what's wrong with the easier and usual way to extract it from the fastboot ROM? Isn't it available anymore inside this ROM?
@Agzyx
You could try the payload_dumper method to extract boot.img from recovery ROM.
Click to expand...
Click to collapse
Not sure, what you are looking for, but boot.img is in the fastboot rom:

How To Guide [GUIDE] Beginner's guide on how to root Redmi Note 10 Pro (sweet) without TWRP

I decided to make this guide since I didn't see a guide thread which explains how to root the phone.
DISCLAIMER: I am not responsible for ANY damage that occurs to the phone, you getting fired because the alarm app failed or the world getting nuked, etc...
Requirements:
-A unlocked bootloader (if you don't know how to unlock it, search "How to unlock bootloader Xiaomi"
-boot.img extracted from your phone's fastboot rom (MAKE SURE YOU DOWNLOADED THE EXACT SAME ROM THAT YOUR PHONE HAS (Check "About phone" in settings. Make sure that the version AND the code (RK(something)XM) match, if you have MIUI).
xiaomifirmwareupdater site contains unmodified MIUI roms for your device.
-If you have a custom rom, extract the rom's zip and get the boot.img from there.
-ADB and Fastboot drivers installed on phone and PC
-SDK Platform tools downloaded from official android website. Extract the downloaded zip to desktop and rename it to platform_tools
-A Computer
-Basic understanding of CMD, ADB and Fastboot commands.
-The phone
If you see an error, scroll down to the troubleshooting section.
Steps:
(on the pc)
-Copy the boot.img file to the phone's downloads folder
(in the phone)
-Download the magisk app from the official github site
-Install the app, then open it.
-In the app, select install on the magisk card
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
-Select patch a file, then find and select boot.img.
-Tap "let's go".
(on the pc)
-Connect your phone to your PC and copy magisk_patched.img from the phone (should be in downloads folder) back to the pc.
-Rename the file to magisk.img, then move it to the platform_tools folder which contains fastboot.exe.
-Now reboot the phone and when the screen goes fully black, hold volume down button until you see "fastboot".
-Your phone should now be in fastboot mode. Connect the phone to the pc.
-Press win+r, then type cmd
-Type cd desktop
-Type cd platform_tools
-Type fastboot devices (if you see nothing, make sure you have adb and fastboot drivers, that the phone is connected and is in fastboot mode.)
-Type this carefully: fastboot flash boot magisk.img
-Done! Now reboot the phone by typing: fastboot reboot
-If you did everything correctly, the magisk app should say that it is installed.
TROUBLESHOOTING:
Q:Fastboot says it couldn't find "magisk.img" or CMD says fastboot doesn't exist
A: Make sure that cmd says that its in C:\Users\(name)\Desktop\platform_tools and that magisk.img is also in there.
Q: Phone is in bootloop
A: Hold volume down button until phone is in fastboot and flash stock boot.img with fastboot flash boot.img. (You will not have root access) If the phone is still somehow in a bootloop, execute the flash_all_except_storage.bat script by double clicking it (found in the sweet_(region)_images folder you extracted from the full fastboot rom .tgz file).

usernamenotrequired said:
I decided to make this guide since I didn't see a guide thread which explains how to root the phone.
DISCLAIMER: I am not responsible for ANY damage that occurs to the phone, you getting fired because the alarm app failed or the world getting nuked, etc...
Requirements:
-A unlocked bootloader
-boot.img extracted from your phone's fastboot rom (MAKE SURE YOU DOWNLOADED THE EXACT SAME ROM THAT YOUR PHONE HAS (Check "About phone" in settings. Make sure that the version AND the code (RK(something)XM) match, if you have MIUI).
xiaomifirmwareupdater site contains unmodified MIUI roms for your device.
-If you have a custom rom, extract the rom's zip and get the boot.img from there.
-ADB and Fastboot drivers installed on phone and PC
-SDK Platform tools downloaded from official android website. Extract the downloaded zip to desktop and rename it to platform_tools
-A Computer
-Basic understanding of CMD, ADB and Fastboot commands.
-The phone
If you see an error, scroll down to the troubleshooting section.
Steps:
(on the pc)
-Copy the boot.img file to the phone's downloads folder
(in the phone)
-Download the magisk app from the official github site
-Install the app, then open it.
-In the app, select install on the magisk card
View attachment 5474787
-Select patch a file, then find and select boot.img.
-Tap "let's go".
View attachment 5474793
(on the pc)
-Connect your phone to your PC and copy magisk_patched.img from the phone (should be in downloads folder) back to the pc.
-Rename the file to magisk.img, then move it to the platform_tools folder which contains fastboot.exe.
-Now reboot the phone and when the screen goes fully black, hold volume down button until you see "fastboot".
View attachment 5474801
-Your phone should now be in fastboot mode. Connect the phone to the pc.
-Press win+r, then type cmd
-Type cd desktop
-Type cd platform_tools
-Type fastboot devices (if you see nothing, make sure you have adb and fastboot drivers, that the phone is connected and is in fastboot mode.)
-Type this carefully: fastboot flash boot magisk.img
-Done! Now reboot the phone by typing: fastboot reboot
-If you did everything correctly, the magisk app should say that it is installed.
TROUBLESHOOTING:
Q:Fastboot says it couldn't find "magisk.img" or CMD says fastboot doesn't exist
A: Make sure that cmd says that its in C:\Users\(name)\Desktop\platform_tools and that magisk.img is also in there.
Qhone is in bootloop
A: Hold volume down button until phone is in fastboot and flash stock boot.img with fastboot flash boot.img. (You will not have root access) If the phone is still somehow in a bootloop, execute the flash_all_except_storage.bat script by double clicking it (found in the sweet_(region)_images folder you extracted from the full fastboot rom .tgz file).
Click to expand...
Click to collapse
Very good but easier with unlocked bootloader and flashing twrp via adb flash recovery "name of twrp file". Afterwards you can flash directly magisk (I prefer 23 canary debug apk) to root.

if i may add to the troubleshooting: if it says magisk.img isn't found, just type this (after confirming connection with fastboot devices command:
fastboot flash boot
then drag and drop the patched magisk file onto the cmd window/line where you typed the command above. worked for me.

Tanks you

For beginners, "assuming bootloader is unlocked if not click here" should be mentioned.

hello, I've been trying to login to my account since this morning. after half a day I was able to get in via facebook. problem is when i want to root my phone it shows error 1004. what did I do wrong?

Bastio001 said:
hello, I've been trying to login to my account since this morning. after half a day I was able to get in via facebook. problem is when i want to root my phone it shows error 1004. what did I do wrong?
Click to expand...
Click to collapse
I've searched around, and it seems to be caused by a VPN. If you use a VPN, turn it off and try again. If not, it could be that the Xiaomi unlocking API is down temporarily.

When I root my Redmi Note 10 Pro (sweet) by using twrp to flash magisk 25.2 and lazyflasher-no-verify-opt-encrypt.zip, I receive following message
.
Nevertheless, I reboot my phone which is effectively rooted.
I can then install Magisk manager.
Has someone an idea about the meaning of this error message ?
Thanks in advance.

cocopipou said:
When I root my Redmi Note 10 Pro (sweet) by using twrp to flash magisk 25.2 and lazyflasher-no-verify-opt-encrypt.zip, I receive following message
View attachment 5704507.
Nevertheless, I reboot my phone which is effectively rooted.
I can then install Magisk manager.
Has someone an idea about the meaning of this error message ?
Thanks in advance.
Click to expand...
Click to collapse
No need to flash lazy flasher since you already flashed Magisk. They both do the same which is to disable dm verity. Also, lazy flasher is an old zip intended for old devices so maybe that's why it failed.

BigChungus321 said:
No need to flash lazy flasher since you already flashed Magisk. They both do the same which is to disable dm verity. Also, lazy flasher is an old zip intended for old devices so maybe that's why it failed.
Click to expand...
Click to collapse
I thank You very much.

BigChungus321 said:
No need to flash lazy flasher since you already flashed Magisk. They both do the same which is to disable dm verity. Also, lazy flasher is an old zip intended for old devices so maybe that's why it failed.
Click to expand...
Click to collapse
then what is the solution bro...still i cant install some custom roms showing error 1...please help me.

cocopipou said:
When I root my Redmi Note 10 Pro (sweet) by using twrp to flash magisk 25.2 and lazyflasher-no-verify-opt-encrypt.zip, I receive following message
View attachment 5704507.
Nevertheless, I reboot my phone which is effectively rooted.
I can then install Magisk manager.
Has someone an idea about the meaning of this error message ?
Thanks in advance.
Click to expand...
Click to collapse
bro am facing this erros 1. will u pls help me.

THis is the stupidest guide for beginners, this article assumes you have unlocked your phone in the first place. All the important steps are just skipped and is stuffed in the requirements. And just shows simple screenshots that even a child would know where to click.
No external links to find the sources.

While unlocking the bootloader I'm having the issue linked below, thanks in advance for all and any responses. https://forum.xda-developers.com/t/mi-unlock-country-code-broken.4572339/

r4nchy said:
THis is the stupidest guide for beginners, this article assumes you have unlocked your phone in the first place. All the important steps are just skipped and is stuffed in the requirements. And just shows simple screenshots that even a child would know where to click.
No external links to find the sources.
Click to expand...
Click to collapse
AGREE 100%!!!

[UPDATING UPGRADE METHOD] [WORK IN PROGRESS] UPGRADE TO PIE / HARMONY 2.0 / W09 - W19 - L09

Spoiler: UPDATING UPGRADE METHOD
Hello to everyone!
Following this guide, you'll be able to rebrand your T5 to Chinese version (W09-C00 or AL00-C00), so you can upgrade to EMUI 9.1/HARMONY 2.0
(IF YOU HAVE THE HONOR PAD 5 AND YOU WANT TO UPDATE, TALK ME)
I have a T5, W19 / 3gb ram / 32 internal.
It worked for me, should work for you too, but I'm not responsible if something goes wrong (well...maybe a little).
PROCESS:
1- You need to UNLOCK the BOOTLOADER with POTATONV and you MUST CHECK "Disable FBLOCK" or you'll have problems flashing the IMGs.
(fastboot oem lock-state info - to check if FBLOCK is unlocked)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
1.1- Check that FRP is UNLOCKED
1.2- CHECK that HISUITE is installed (for drivers) >>> CLICK HERE TO DOWNLOAD
1.3- BACKUP YOUR OEMINFO USING TWRP, IF SOMETHING GOES WRONG, YOU'LL NEED IT.
Follow this amazing guides to UNLOCK your BOOTLOADER:
SOFTWARE >>> CLICK HERE TO DOWNLOAD
UNLOCK BOOTLOADER T5 process >>> CLICK HERE FOR THE GUIDE
SAVE YOUR BOOTLOADER CODE, YOU'LL NEED IT.
2- Download fastboot and oeminfo, extract it and flash it:
FASTBOOT FILES (USE IT):
WINDOWS: CLICK HERE TO DOWNLOAD
LINUX: CLICK HERE TO DOWNLOAD
MAC: CLICK HERE TO DOWNLOAD
OEMINFO AGS2 / C00:
W09 - W19 WIFI ONLY:
fastboot flash oeminfo oeminfoW09C00.img
https://www.androidfilehost.com/?fid=14655340768118449368
L09 LTE (don't know if it will work on L03):
fastboot flash oeminfo oeminfoags2al00c00.img
https://androidfilehost.com/?fid=14655340768118450716
YOU CAN ALSO USE TWRP TO FLASH OEMINFO, IF YOU DO THAT, FLASH IT AND REBOOT INTO BOOTLOADER TO CONTINUE THE PROCESS
3- Now, download and extract the zip, flash the IMGs inside and wait for the best:
FILES FOR AGS2-W09 & W19
https://www.androidfilehost.com/?fid=14655340768118449355
FILES FOR AGS2-L09
https://www.androidfilehost.com/?fid=14655340768118459545
Flash this files in FASTBOOT
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash fastboot fastboot.img
fastboot flash kernel kernel.img
fastboot flash ramdisk ramdisk.img
fastboot flash recovery_ramdisk recovery_ramdisk.img
fastboot flash cust cust.img
fastboot flash version version.img
***Reboot into STOCK recovery and format data***
*If the above files doesn't work, try flashing the firmware with DLOAD method.
Download the zip and extract the DLOAD folder into the root of your SDCARD, reboot the tablet pressing VOL + and VOL - and wait...*
DOWNLOAD DLOAD W09-C00
DOWNLOAD DLOAD AL00-C00
4- Now, the phone should boot normally, rebranded and with the chinese firmware.
Now, go to settings and check for update, you'll see an update to PIE available.
You'll need to install all the PIE updates before the server sends Harmony, or... you can send the Harmony update directly with this:
https://professorjtj.github.io/ (AGS2-W09 - C00) (AGS2-AL00 - C00)
https://github.com/ProfessorJTJ/HISuite-Proxy/wiki/Complete-Guide (follow instructions, very easy to use)
Upgrading to Pie/Harmony locked my bootloader, but if you saved your code, write it again and unlock it again ^.^
Thanks to @Fosanz for its help.
Thanks to @Rockel for the detailed guide to unlock the bootloader. Go to the post
Thanks to @iceows for the script and steps to edit the oeminfo: Go to the link
Thanks to @oslo83 for helping me to fix the mess that I caused to my tablet.
IF YOU HAVE DOUBTS OR ANY PROBLEM, SEND ME A PM
TELEGRAM: sfoot13
Nc
The shadow proves the sunshine.
t.me
After the rebrand, I didn't lost Widevine L1
That's all folks!
Have a good day, cheers.

Spoiler: REBRAND TO HONOR PAD 5 TABLET AND GET A NICE NAVBAR
After upgrading to PIE/HARMONY, IF YOU WANT TO... FLASH ONLY OEMINFO!!!
W09 - W19 DOWNLOAD LINK
L09 DOWNLOAD LINK
Flash it, reboot, and done, don't do nothing else.
ROOT WITH MAGISK
Download latest magisk apk and patch your recovery ramdisk img, after that, flash with fastboot and reboot into recovery to have root working.
fastboot flash recovery_ramdisk yourimg.img
fastboot reboot-recovery (keep usb cable connected)
Here's my recovery rooted, if you want to flash it
https://www.androidfilehost.com/?fid=14655340768118462757
TWRP: System and Vendor can't be mounted, Huawei changed file system, now is EROFS, so system can't be modify.
Go to the post.

Go to data > hw_init - You'll see many folders, you can delete almost all the apps inside the folders, unless you use one of them. (you'll see the chinese apps)
Script to delete/disable some apps (if you know other apps that can be disable, tell us)
adb shell
sh deletebloatware.sh
Click here to go to the download link
PLAY STORE - MAGISK MODULE
Download the module and go to magisk and install it
Releases · nift4/microg_installer_revived
Install microG GmsCore, GsfProxy, FakeStore (or Play Store if you want so) and MapsV1 to /system/ - nift4/microg_installer_revived
github.com
Download the Playstore apk
Google Play Store 29.9.16-19 [0] [PR] 438372530 (nodpi) (Android 4.4+) APK Download by Google LLC - APKMirror
Google Play Store 29.9.16-19 [0] [PR] 438372530 (nodpi) (Android 4.4+) APK Download by Google LLC - APKMirror Free and safe Android APK downloads
www.apkmirror.com
Download latest playstore apk, use a root explorer, copy the playstore apk, go to SBIN > MAGISK > MODULES > MICROG_INSTALLER > SYSTEM > PRIV-APP > PHONESKY and delete fakestore.apk and paste the latest playstore apk and reboot.

SCREENSHOTS!!!

Hmm, tried to do this but fastboot flash oeminfo oeminfoags2al00c00.img failed. No big deal I did it through TWRP.
Next fastboot flash system system.img but also failed
Sending sparse 'system' 1/6 (412324 KB) OKAY [ 12.720s]
Writing 'system' FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
Bootloader shows PHONE Unlocked and FRP Unlocked both in red.
What am I missing?

@Sleeepy2 Hello, I'm talking with a guy that has the same problem, can't flash oeminfo and system with fastboot.
Same as your tabket, FPR and bootloader unlocked.
I was thinking that maybe in one of the latest huawei updates, they (huawei) changed something (security patches), because I never had that problems and I haven't updated to the latest security patch that huawei released...
You can try sending the firmware with EMUI Flasher https://www.androidfilehost.com/?fid=14655340768118451775
But should download the firmware from this page https://professorjtj.github.io/ look for
AGS2-AL00 - C00AGS2-AL00 8.0.0.215(C00)

@sfoot13 Can't use the EMUI flash yet, as I tried flashing system through TWRP and it failed now can't boot. lol
I've found the firmware on that page but I don't know how to down load it. Clicking the 3 dot menu opens the Downlad ROM window but it doesn't work, says to use the HISuite.Proxy. If I run that and click the link, it shows 3 zips but clicking on any of them doesn't download.
Clicking the Add Rom shows up in HISuite.Proxy but I still don't see a way to download it.
I think I figured out how I am supposed to use the ROM but it doesn't work. Run the Proxy, go to website and click add and it shows up in the proxy. Then open HiSuite connect tablet and click Update. It shows a new version is available however clicking update it instantly goes to Failed to update.
Well if I read the op closer it actually has a link explaining how to use the proxy.
I have flashed the oem file through TWRP, used the proxy to download the 8.0.0.215 rom but wile HiSuite is "installing" Proxy said it's probably not going to work. When the tablet reboots to install it says software update failed

@Sleeepy2 if you flashed the oeminfo, you can flash the system with Emui Flasher, even if you're using linage os or any gsi, because you just need to download the oreo firmware, copy it to internal memory, open emui flasher and select the firmware zip.
To download the firmware directly from the page, you need to click in the box with the three dots ... and you'll see the option to download (always with hisuite proxy open)

ugh, well I think I pooched it now.
I started over and got linage os flashed and rooted. EMUI Flasher couldn't find any files in any folder to flash.
Rebooted back into TWRP and flashed the oeminfo now it only boots into eRecovery or stock recovery, no sign of TWRP.
Booted back into fastboot to try and just flash TWRP again.
fastboot flash recovery_ramdisk TWRP_3.5.2-prague_DarkJoker360_20210508.img
Sending 'recovery_ramdisk' (14894 KB) OKAY [ 0.398s]
Writing 'recovery_ramdisk' FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
eRecovery wont download and install stock anymore. I am going to give up for today.

Ugh, well I guess my tablet is done. Fastboot wont flash recovery and eRecovery
Getting package info failed"
If any one has any suggestions, that would be great.
I just did the oem unlock again from fastboot even though it said it was unlocked. After I did that it automatically rebooted into TWRP and I was able to flash my oeminfo back and it was good to go again.

I've gone through all the the steps successfully, however when I check for updates I don't see any?
What could be wrong?

scabs said:
I've gone through all the the steps successfully, however when I check for updates I don't see any?
What could be wrong?
Click to expand...
Click to collapse
Successfully? Really? Great.
Well, if you installed oeminfo and the IMGs and you formatted data and it booted, go to settings and tell me the version it says.

Not working for me. flashing oeminfo failed using fastboot. Same problem than Sleeepy2
Any clear explanation will be appreciated. I'm not a specialist.
In fact, I'm a little bit a specialist because I've unlocked bootloader and FRP. I've also installed LineOS 18.1

@bedelaitre I'll rewrite it, maybe it will work for everyone.
One thing, you're not able to flash some imgs, because you need to unlock again your bootloader with PotatoNV and CHECK THE BOX "DISABLE FBLOCK", after that you'll be able to flash system and others img, but that means, you'll need to open again the tablet...

sfoot13 said:
Successfully? Really? Great.
Well, if you installed oeminfo and the IMGs and you formatted data and it booted, go to settings and tell me the version it says.
Click to expand...
Click to collapse

scabs said:
Click to expand...
Click to collapse
You need to format data bro.

sfoot13 said:
SCREENSHOTS!!!
Click to expand...
Click to collapse
sfoot13 said:
Hello to everyone!
Following this guide, you'll be able to rebrand your T5 to Chinese version (W09-C00 or AL00-C00), so you can upgrade to EMUI 9.1/HARMONY 2.0
(IF YOU HAVE THE HONOR PAD 5 AND YOU WANT TO UPDATE, TALK ME)
I have a T5, W19 / 3gb ram / 32 internal.
It worked for me, should work for you too, but I'm not responsible if something goes wrong (well...maybe a little).
PROCESS:
1- You need to UNLOCK the BOOTLOADER with POTATONV and you MUST CHECK "Disable FBLOCK" or you'll have problems flashing the IMGs.
(fastboot oem lock-state info - to check if FBLOCK is unlocked)
View attachment 5597429
1.1- Check that FRP is UNLOCKED
1.2- CHECK that HISUITE is installed (for drivers) >>> CLICK HERE TO DOWNLOAD
1.3- BACKUP YOUR OEMINFO USING TWRP, IF SOMETHING GOES WRONG, YOU'LL NEED IT.
Follow this amazing guides to UNLOCK your BOOTLOADER:
SOFTWARE >>> CLICK HERE TO DOWNLOAD
UNLOCK BOOTLOADER T5 process >>> CLICK HERE FOR THE GUIDE
SAVE YOUR BOOTLOADER CODE, YOU'LL NEED IT.
2- Download fastboot and oeminfo, extract it and flash it:
FASTBOOT FILES (USE IT):
WINDOWS: CLICK HERE TO DOWNLOAD
LINUX: CLICK HERE TO DOWNLOAD
MAC: CLICK HERE TO DOWNLOAD
OEMINFO AGS2 / C00:
W09 - W19 WIFI ONLY:
fastboot flash oeminfo oeminfoW09C00.img
https://www.androidfilehost.com/?fid=14655340768118449368
L09 LTE (don't know if it will work on L03):
fastboot flash oeminfo oeminfoags2al00c00.img
https://androidfilehost.com/?fid=14655340768118450716
YOU CAN ALSO USE TWRP TO FLASH OEMINFO, IF YOU DO THAT, FLASH IT AND REBOOT INTO BOOTLOADER TO CONTINUE THE PROCESS
3- Now, download and extract the zip, flash the IMGs inside and wait for the best:
FILES FOR AGS2-W09 & W19
https://www.androidfilehost.com/?fid=14655340768118449355
FILES FOR AGS2-L09
https://www.androidfilehost.com/?fid=14655340768118459545
Flash this files in FASTBOOT
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash fastboot fastboot.img
fastboot flash kernel kernel.img
fastboot flash ramdisk ramdisk.img
fastboot flash recovery_ramdisk recovery_ramdisk.img
fastboot flash cust cust.img
fastboot flash version version.img
***Reboot into STOCK recovery and format data***
*If the above files doesn't work, try flashing the firmware with DLOAD method.
Download the zip and extract the DLOAD folder into the root of your SDCARD, reboot the tablet pressing VOL + and VOL - and wait...*
DOWNLOAD DLOAD W09-C00
DOWNLOAD DLOAD AL00-C00
4- Now, the phone should boot normally, rebranded and with the chinese firmware.
Now, go to settings and check for update, you'll see an update to PIE available.
You'll need to install all the PIE updates before the server sends Harmony, or... you can send the Harmony update directly with this:
https://professorjtj.github.io/ (AGS2-W09 - C00) (AGS2-AL00 - C00)
https://github.com/ProfessorJTJ/HISuite-Proxy/wiki/Complete-Guide (follow instructions, very easy to use)
Upgrading to Pie/Harmony locked my bootloader, but if you saved your code, write it again and unlock it again ^.^
Thanks to @Fosanz for its help.
Thanks to @Rockel for the detailed guide to unlock the bootloader. Go to the post
Thanks to @iceows for the script and steps to edit the oeminfo: Go to the link
Thanks to @oslo83 for helping me to fix the mess that I caused to my tablet.
IF YOU HAVE DOUBTS OR ANY PROBLEM, SEND ME A PM
TELEGRAM: sfoot13
Nc
The shadow proves the sunshine.
t.me
After the rebrand, I didn't lost Widevine L1
That's all folks!
Have a good day, cheers.
Click to expand...
Click to collapse
Good morning !
Sorry for my broken english, i have a huawei mediapad t5 tablet with 3 giga ram exactly like yours.
I would like to know where did you make the contact point on the motherboard so that I can also do it on mine to unlock the bootloader.
I thank you in advance.

@TONYFR-1984
Follow this steps , there's a photo of the motherboard, the exact place that you need to touch (it is marked with a red line and circle)
Trying to unlock the bootloader with PotatoNV on Mediapad T5 not working (video explanation)
Hi there, So After seen many tutorials I wanted to proceed to unlock the bootloader of my Huawei Mediapad T5 , here are the specs ``` Model: AGS2-W09 Build No: AGS2-W09 8.0.0.360(OCEC431) CPU : Hisilicon Kirin...
forum.xda-developers.com

What would be the process of going back to LineageOS?

sfoot13 said:
@bedelaitre I'll rewrite it, maybe it will work for everyone.
One thing, you're not able to flash some imgs, because you need to unlock again your bootloader with PotatoNV and CHECK THE BOX "DISABLE FBLOCK", after that you'll be able to flash system and others img, but that means, you'll need to open again the tablet...
Click to expand...
Click to collapse
Hi, sorry for delay. I don't understand why I need to unlock the bootloader. When booting, the tablet says that the bootloader is unlocked. Are you sure I need to unlock it again ?