yashsingh1/xdaforums huggingface dataset:
[Red Magic 8 pro] Anegorami:
Since we're in the off-topic territory already...

Nailed it. Seems like the hardware manufacturers are going the most profitable way possible (capitalism, duh) and restricting the user to the preinstalled jail, devoted of ways to modify anything at will, because (sure enough) such modification is a threat to their adware, spyware and sheer clutter nobody asked for (see Mora).

As a bonus, it also protects a lot of services from being hacked/abused (G**e G****ian my beloved) - still waiting for the moment when another Android update will completely remove the ability to install the apps from anywhere but Play Store and voila - nobody will be able to play anything from their local storage. No offline games, music collections or that 100TB of pirated anime porn every one of you are keeping. Additional points for constant internet connection being mandatory (because those apps should spam you with ad pushes constantly) and constant GPS tracing (as if Goggle doesn't do that already).

And, suddenly, we're in a world where everything is forbidden, PCs are bootloader-locked just like smartphones and Google and Microsoft are fighting for total domination over the market. What a bright future, greet the new day.
[Red Magic 8 pro] Admiral_Face:
Unfortunately, the case is final, the 8S pro will likely be the last rootable flagship from ZTE. If you get yourself approved by Xiaomi, they might let you unlock the bootloader on some of their phones, but their underscreen camera line is now gone, so until the industry changes, this will be the last rootable phone with an underscreen camera. Thankfully, turnip drivers are actually working somewhat on this thing, so in 2 years we will merely lose Camera support, but still be able to upgrade the OS for years to come, with gradually improving open source GPU/QC 5G+Wifi7 drivers.
[Red Magic 8 pro] Admiral_Face:
They 100% do already, it's a manditory regulation via prism. Our elected officials and the powers that be wanted it this way forever. Your ISP does it too, AT&T, T-Mobile, Verizon, US Cellular, ect all have constant GPS tracking, with backup triangulation incase it fails. You can bulk buy burners if you're worried about it, but they are tracked too, so it would only work if you use it somewhere not near home for privacy.

Idk if this would stick, people would start buying IBM power / RISC V, or custom ICs for sure if this were to happen. The market for x86 machines is too heavily reliant on non-microsoft software, as huge portions of the market run some *nix and there are no next to no Windows supercomputers on the 500 list.
[Red Magic 8 pro] Anegorami:
Fair point for mainframes and the like, but there are still average users who can barely comprehend on Windows dead-simple permission system and try to exorcise anyone showing them "chmod 666" on *nix. Hell, average user wouldn't even bother with root access, it's the power users who do, and there is still a possibility that M$ will try to lockdown those average Joe within a golden cage. And in this case such power users who would like to get rid of annoying "EDGE IS MORE SECURE THAN FIREFOX, CLICK HERE TO DELET MOZILLA!!!!1111" will become a minority that will be against the mainstream - forced to buy small subset of hardware, tinker with the available software to make something work and in the end living with half-baked solutions like MicroG (no offense, but it's the sole alternative to GApps that can at least run the bare minimum) because all the money going another way.

Time to start funding a foundation that will make a lineup of phones following a standard and encouraging custom ROM devs to make an open source Google-less OS that will go straight into the same niche Debian and Ubuntu are currently in - user-friendly alternative to monopoly holder.
[Red Magic 8 pro] Admiral_Face:
The thing about monopolies is that there are no other supported platforms but their's. Of course in a court a totally different market (the apple users) looks like a competitor, even though it shouldn't even be in the same category of device. (they both connect to cellular infrastructure, so it must be the same durr) I don't think anyone has a shot at making a full new platform at this point, Ubuntu Touch and Plasma Mobile were horrendous atrocities, and major failures for Canonicle and Crunchbase respectively. We can't even get Netflix with L1 Widevine on GNU at all without GPU Passthrough and a Windows VM, hooked to a HDCP 2.2 compliant capture device that also supports GNU streamed via v4l to mpv with lowlatency flags. The simple truth is, if you want to use anything legal at all to do anything or watch anything, you are forced to use Wingdings, Goggle, or Crapple operating systems with an untouched canned user environment, any slight settings change could spell demise for your ability to legally use the services you pay for.

On the other side of things, all the DRM was broken years ago, or doesn't need to be broken in the case that almost every capture device on the market is HDCP compliant, so piracy is often the only road for any users that changed too many settings, or have root access or sideload capability. No wonder piracy is at an all time high, this business has gone on for too long. If businesses really want more users on their platforms, they should consider canning this broken DRM crap all together, it's clearly affecting their bottom line, and is probably only still there to make themselves look viable to licensees and shareholders, as petabytes get stolen in 4k/atmos each quarter.

I guess we just have to stick to our guns with things like the 8s pro, which has this nuts ABL from the 8 pro flashed through EDL for partial Fastboot support workaround, and pray the next update doesn't wipe EDL off the device entirely, or "upgrade the device security" in such a way that makes the old firehose bork itself.
[Red Magic 8 pro] Timmy Turner10:
How can an update wipe EDL entirely? It is baked into the memory. Nothing a software update can change. Qualcomm made this as an emergency rescue sort of thing. It's permanent. If you remove it, boom. Brick.
[Red Magic 8 pro] alecxs:
I don't think EDL mode can removed, but maybe the method to enter it can be changed?
[Red Magic 8 pro] aaa.bbb111222:
Firehose loaders need to be signed, so it's theoretically possible that some vendor will only allow in-house signed (not generic Qualcomm) ones and will never leak them. This doesn't not technically remove EDL, but makes it unusable.
[Red Magic 8 pro] niveZz:
xiaomi devices already require authenticated accounts for edl flashing
[Red Magic 8 pro] limalvin1203:
i tried this now i stuck on the redmagic boot sreen
[Red Magic 8 pro] Anegorami:
Tried what, exactly? If you tried to enter EDL mode (somehow) and ended up on the boot screen then you've done something wrong, as EDL mode has zero interaction aside from providing a USB connection - the phone should look like it's turned off entirely.

Anyway, please, provide more data.
[Red Magic 8 pro] limalvin1203:
In the step with the partition manager, I mass up and accidentally clicked on init_boot_b instead of init_boot_a a second time do it properly now i stuck
[Red Magic 8 pro] Pixelramp:
Does anybody know if there is a difference in the EU version? Or can this method be applied to this as well?
[Red Magic 8 pro] Anegorami:
Have you unlocked the bootloader? What's currently in init_boot_a and init_boot_b partitions? Do you have a backup? Have you patched init_boot image with Magisk before flashing? Did you even flash anything so far? Sorry, I can't even begin to help with this little information, tell us your EXACT actions, from the beginning, step by step.

Well, given that the method uses quite agnostic tools and components this method "should" apply to any firmware version. Of course, you could upload your original init_boot partition (or its checksum) for the community to check against theirs. Also, be sure to make a backup, just in case.
[Red Magic 8 pro] Pixelramp:
Okay, good, thanks! I was a bit unsure because I read something about the Chinese version being different (?).

And sure, I'll upload the boot partitions as soon as I get my device. Sadly, we have a 3-week delivery time on the Aurora version, so hopefully, I'll upload it in the next two weeks.
[Red Magic 8 pro] limalvin1203:
I followed all the steps I read data load image of both init_boot_b and init_boot_a and no I do not have a backup I'm just stuck on Redmagic Lego can't even go into fastboot only into recovery
[Red Magic 8 pro] Anegorami:
>I followed all the steps I read data load image of both init_boot_b and init_boot_a

You did what?

Seriously, just to clarify all this mess I can't even comprehend to (believe me, I'm trying), all you had to do is to make A FULL BACKUP (by pressing Read Data button on every visible partition, get them tasty stock images, store them somewhere safe and, optionally, filter out the empty ones to free space) and then overwrite abl partition with the one provided in the very first post (by pressing Load Image button and selecting the downloaded abl image on abl_a or abl_b partition, depending on your currently active slot, or both for an overkill). AND THAT'S IT. All subsequent operations including flashing Magisk-patched init_boot were supposed to be done from the unlocked bootloader (not that you can't flash init_boot from EDL but there is zero point in going there for the second time just to flex).

Now, let me try to understand your current situation. Seems like you, somehow, flashed wrong init_boot into the wrong partition - you see, initially one (active) slot contains actual init_boot partition and another one (inactive slot) contains empty space (you'll get a zero-filled file of partition length if you try to dump it). By flashing inactive (empty) init_boot into the active slot you've broken the loading chain and now stuck in bootloop. Seems logical to me, correct me if I'm wrong.

Now, don't panic, you've nowhere near a hardbrick, so breath out and do the following:

- Dump (Read Data) both init_boot partitions. Check them carefully and tell me if there are any data present or just zeros. For that, use any hex editor around, HxD, for example. DO NOT FLASH ANYTHING ANYWHERE, FOR THE TIME BEING FORGET THAT LOAD IMAGE BUTTON EXISTS.

- Boot into recovery and try to get to bootloader from there (since you've managed to get into EDL software way I suppose ADB commands are working on your side. Use them.).

Once you do, the next steps will be restoring init_boot partition (not having a backup is a serious issue here but there are some options left) and booting back into the system. If successful, you'll get another chance to proceed with gaining root user access. Good luck.
[Red Magic 8 pro] Timmy Turner10:
If you're on US Redmagic 8S Pro model, here: my init_boot_a and init_boot_b images. Rename them from .bin to .img and flash via fastboot, or EDL if you can't boot. If you need more images, let me know, I'll see if I have them if needed.

Another issue is that even after locking/unlocking screen lock hasn't came back yet, but I'll keep trying.
[Red Magic 8 pro] babyplex:
Hi guys! New owner of Redmagic 8S Pro (US version) here. I've tried to follow the steps by Timmy Turner in rooting my phone but am having issues understanding the jargon going around.

For instance: What is EDL and how do I access it? Is it Factory Test Mode (Power + Vol Down) or is it Recovery Mode (Power + Vol Up)?

I also purchase QLMFlasherPro, but am having a hard time using it, as it doesn't seem to recognize my phone. Here's a screenshot from the program.

Any assistance on this would be much appreciated!
[Red Magic 8 pro] guus1612:
Is there any way to get the lock screen working after rooting?
[Red Magic 8 pro] alecxs:
No, it's a secret mode one can't reach with buttons. also called QDL mode. try fastboot oem enter-dload or fastboot oem edl or something. adb reboot edl should also work.
[Red Magic 8 pro] DarkestSpawn:
Its currently a long and annoying process to fix after triggering the issue. Backup everything you need because the device has to be factory reset and relocking/unlocking will also reset the device.

- Relock bootloader (Critical and Non-Critical).

- Fastboot erase userdata or Format Data thru stock recovery

- Setup device without setting any pattern or pin security setup on first boot.

- Follow standard bootloader unlock steps (Enable OEM unlock from Developer Settings, reboot to fastboot, fastboot unlock and unlock critical) *Note*: if this doesnt boot to recovery and perform the factory resets automatically after unlocking before booting to system, I suggest interrupting the boot and boot to recovery to manually do this, then boot to system.

- Setup device without setting any pattern or pinsecurity setup on first boot after bootloader unlocking

- Magisk patch init_boot and flash to init_boot slot.

- Boot to system, finish setting up Magisk which includes a reboot.

- Once everything is done, go to Settings-> Security -> Screen Lock and setup your desired screenlock.

I have seen people say this did not work for them and others it did. I am one of the lucky folks that it did work for.
[Red Magic 8 pro] Timmy Turner10:
I've entered EDL mode by pressing vol-down and power after having the cable plugged via USB. The phone was turned completely off though beforehand. Though maybe it was thanks to TWRP.

And about the lockscreen issue, it'd be great if there were a TWRP flashable zip to fix it. TWRP for Redmagic 8 Pro worked on 8S Pro. Seems the same issues between both devices are present. Thought I saw a fix before for the lockscreen you could flash in TWRP but can't seem to find the forum anymore.
[Red Magic 8 pro] Anegorami:
>What is EDL..?

In short: Emergency DownLoad mode, used in cases of hardbrick when the loader chain is broken so much that even bootloader cannot be accessed. In our particular case its usage is narrowed down to flashing the 8Pro bootloader (ABL) which, unlike the 8S Pro one, still has the unlocking commands. If you want to learn more about both loading chain, EDL and bootloader commands, Google is your friend.

>..and how do I access it?

To append to the answers above: adb reboot edl and fastboot reboot edl both work, depending on where are you, currently. Also, a word of caution - recently I've gotten a message noting that the phone should be charged enough before entering EDL mode else it may stop responding to the USB connection. While this particular case doesn't occured to me I'll leave it here just in case - free for everyone to confirm or bust.

>it doesn't seem to recognize my phone

Check the connected devices and, if necessary, install the required drivers. Haven't used QLMFlasherPro so, unfortunately, cannot provide any further help.
[Red Magic 8 pro] babyplex:
Thank you all for all the helpful advice! I've managed to get myself to actually going into EDL mode. I thought @alecxs was joking when he said it was hidden. No display and all really makes it super hidden...

I tried reading the partition table with the firehose file @Timmy Turner10 provided, but ran into some errors on the way. I've tried the following in QLMFlasherPro but still ran into the same exact error code. Does anyone have any idea what is going on here?

1) changing the model of the phone to '8sPro-8sPro-Pro' instead of '8Pro-8Pro-Plus'

2) changing from 'custom firehose' to 'auto firehose'

3) switching USB cables as well

Here's how it looks:

C
[Red Magic 8 pro] Pixelramp:
Im trying to use QFIL. But i always get a " Download Fail:Sahara Fail:QSaharaServer Fail: Process fail" error when trying to open the partition manager.

EU 8s Pro.

I've added the logfile to the attachments.
[Red Magic 8 pro] Pixelramp:
Fixed it by using a different PC.
[Red Magic 8 pro] babyplex:
Here's me trying out the QFIL way. No luck as well! :(

It fails during before partition table loads.
[Red Magic 8 pro] Pixelramp:
Looks like the same problem i had.. Well i fixed it by using a diffrent System. So maybe driver issues?

So maybe try to uninstall everything including the drivers. Download this exact version https://qpsttool.com/qpst-tool-v2-7-496

Then first install the driver in the driver folder and then reinstall QPST.

Maybe this works, if not try using a fresh install on maybe a different system.
[Red Magic 8 pro] Pixelramp:
As promised, here are the backups of the init_boot_a and init_boot_b EU versions. (I don't think there is a difference, but it's better to be safe.)
[Red Magic 8 pro] babyplex:
Tried 3 different PCs (2 Ryzen and 1 Intel) and nothing works. I think I might just return this phone as its too hard to root.
[Red Magic 8 pro] mark332:
you still don't know how to use, if you select a model in drop down meaning it's fully supported by program and no need to use your own firehose file the custom and auto checkbox must be unchecked, if you select custom firehose then Model section must be empty. to fix the above problem move the tool in c & it works
[Red Magic 8 pro] mark332:
Unable to read packet header. Only read 0 bytes

change USB port, use original cable
[Red Magic 8 pro] babyplex:
Thanks @mark332! I corrected the issue but am stuck at 'Preparing config'. Tried without model in drop down and with model in drop down and both get stuck there. Do you have any idea what's happening?
[Red Magic 8 pro] Timmy Turner10:
Must be a driver issue. On my PC, the USB device at the top right like your screenshot wasn't waiting on the device. Btw you may need to install 9008 drivers. Make sure in COMS and PORTS section actually has a device listed in device manager.
[Red Magic 8 pro] babyplex:
Could this be the problem?
[Red Magic 8 pro] Timmy Turner10:
Yes. Disable driver signature verification. It can be done via command prompt on the PC. It will restart and should work afterwards.
[Red Magic 8 pro] Pixelramp:
Due to some hardware issues with the device, I may need to return it. What is the safest way to remove root and lock the bootloader, essentially restoring it to its original shipping state? Additionally, can I remove the warranty void in the bootloader? (It shouldn't be a problem under EU law, but it looks better.)

Should I simply remove root with Magisk and lock the bootloader via ADB?
[Red Magic 8 pro] Pixelramp:
Okay, I think I did it! I'll share how I accomplished it; maybe it could help someone else.

I uninstalled Magisk/root via Magisk -> Uninstall -> Complete uninstall.

Then, I performed a factory reset just to ensure that there were no residual lockscreen or password settings left. (I was concerned about the lockscreen not functioning properly afterward.)

Next, I rebooted into the bootloader and flashed the following:

fastboot flash init_boot_a (Original init_boot_a as .img)

fastboot flash init_boot_b (Original init_boot_b as .img)

fastboot flash abl_a (Original abl_a as .img)

fastboot flash abl_b (Original abl_b as .img)

Finally, I locked the bootloader with:

fastboot flashing unlock

Done. The device restarted with a factory reset, and the bootloader no longer displays "Void."
[Red Magic 8 pro] Timmy Turner10:
After many issues still remaining, e.g., lockscreen still won't work even after 3 lock/relock cycles and magisk modules won't install in any way, I am going to go back to stock. The issues are simply too much to be a good root experience. Hopefully someone finds a better way to achieve root.

Edit: It's bricked. Restoring literally everything I backed up via EDL did not fix it, simply won't boot. Even worse, redmagic still hasn't uploaded the rom for the 8S Pro. It enters EDL and trying to reboot it only says device descriptor failed, screen blank the whole time, constantly reboots because I can hear the chime in windows.
[Red Magic 8 pro] Timmy Turner10:
Okay so bootloader is now locked, won't boot into system. Tried using edl to reflash. Turns out it's set to the a slot but the OS is on slot b. Any ideas?
[Red Magic 8 pro] Anegorami:
Welcome to the club.

Unless there is some command in EDL mode that will let you change the active slot the only way to set it is to do so from the bootloader (fastboot set_active %slot%). And if you can't get there you'll have to mirror all the partitions, did that myself (see https://xdaforums.com/t/solved-fastboot-bootloop-after-flashing-magisk-patched-init_boot.4618971).

Ninja edit: OK, set_active command requires the bootloader to be unlocked, duh. Well, sorry for the useless comment and good luck.
[Red Magic 8 pro] Timmy Turner10:
And to mirror, I would have to do what exactly? Wow I seriously messed up, impatience is getting to me. Literally just deleted every partition so now it's just blank. Hmm...

An edit: Fixed that, but it doesn't power off anymore, just reboots to bootloader, with no way to enter edl anymore. The key combinations don't work now :/

The cable and drivers are exact same. Literally just used it, had blank partition manager, reflashed everything back and no more edl.
[Red Magic 8 pro] Timmy Turner10:
So back to square one. It's set to slot a. Still locked bootloader of course. Tried everything to change the slot and putting the files from b slot to the a slot, still no boot on a. So, I read somewhere that the misc partition holds bootloader information. How about the current boot slot? How can I edit it and change slot this way, if possible?
[Red Magic 8 pro] Anegorami:
>And to mirror, I would have to do what exactly?

Copy all the data from the active slot to inactive slot so the both _a and _b partitions were the same - this trick saved me when I changed the slot, rebooted and found myself in the world where every inactive slot partition contained nothing.

Now that you're back to bootloader you could try to reboot to EDL with fastboot reboot edl command and see if it works. If it does, you can always return to bootloader by rebooting the phone.

There is also another tool (https://github.com/bkerler/edl/blob/master/edl) that claims to have the commands you need (see edl setactiveslot <slot> and edl setbootablestoragedrive <lun> commands). If the commands work as intended, you should be able to unbrick by evoking:

edl setactiveslot b
edl setbootablestoragedrive 1

Next. There is a Chinese tool linked in the thread I've mentioned, be sure to study it and see if it will be of use to you. Google Translation engine is your friend.
[Red Magic 8 pro] C4RP3 N0CT3M:
I'm doing this now. Kinda lame that I have to contact them just to get the app I paid for to work.
[Red Magic 8 pro] Timmy Turner10:
I restored it before the comment, I appreciate it. I made silly mistakes of unplugging when it said done in qlmflasherpro but it clearly wasn't done. After leaving it plugged on done, it eventually rebooted into system. Flashed Chinese rom twice this way, oem unlocked, flashed the abl in first post to both slots, unlocked, changed the slot to b, and finally flashed NA rom. Got into system, lock screen works again. A perfect device returned.
[Red Magic 8 pro] C4RP3 N0CT3M:
I still just can't get into QLMFlasherPro. It just crashes as soon as I open it (once getting past the login screen after contacting them). Did you have any issues like this @Timmy Turner10?

Edit: I got it! I had to add "https://romprovider(dot)com" to my url exceptions in ESET as well as the install folder. I also had to turn off ESET protection while extracting since it goes to the temp folder momentarily and ESET kept deleting the "fix.bat" file.
[Red Magic 8 pro] takinda10:
I hope you have a video on step by step tutorial 😭 I can't understand I'm newbie