Database Info

Vortex SYNQ Dev Thread (TWRP Image & Bootloader Unlock!!!)

During our quest to gain root on the ANS UL40, @Matthew702 and I went a bit off topic and started messing with his Vortex Synq he picked up. 'Thew was able to find a method to unlock the bootloader, which I will post here shortly, and we shortly thereafter found out that the device is "vulnerable" to using SPFT--as in the VCOM port stays open and allows us to read/write partition images directly from the emmc.
UPDATE: We now have enough people to really get the ball rolling for some development for this phone, so as we accomplish more things we'll post them here

Anything you try from here, you do so at your own risk. This may void your warranty, break your device, etc.
HOW TO UNLOCK THE BOOTLOADER
Go to Settings>About Phone>Build Number and tap this a lot really fast to enable developer mode
Go to the new developer mode option in the Settings menu, check the switch that says Allow OEM Unlock
Plug your phone into your computer, enable ADB Debugging, open up a terminal on your computer, and initiate an "adb reboot fastboot" to put the device into fastboot mode
In your computer terminal again, type in "fastboot oem unlock". If it fails, run it again. If it fails again, reboot to fastboot one more time and try a couple more times. Eventually it should work after a couple tries, it did for us
Confirm the device unlock on the phone (pressing volume up at the prompt I believe), and wait for the phone to reboot. Note that it's not stuck in a bootloop at this point, it's just factory resetting after the unlock, so give it time to work
HOW WE WANT TO ROOT IT (NOT DONE YET): METHOD 1
Pull a recovery image from the phone with SPFT using a proper mtk6739 scatter file which I can't exactly find
Port TWRP to the phone from another device's mtk6739 TWRP image with carliv image kitchen tool, and flash it back to the phone with SPFT
Flash Magisk in TWRP, reboot, profit
HOW WE WANT TO ROOT IT (NOT DONE YET): METHOD 2
Pull a boot image with SPFT
Use the Magisk APK to inject magisk into the boot image
Flash the boot image back with SPFT (or maybe fastboot), reboot, profit
HOW TO FLASH TWRP TO THE PHONE (STILL EXPERIMENTAL)
Download the TWRP image from here
Reboot to the bootloader
Assuming you unlocked the bootloader from before, just do "fastboot flash recovery [imagename]" to get it on there
If fastboot complains about it not being able to flash, try running the command one more time
CUSTOM ROMS FOR THIS PHONE
This phone came with 8.1 Oreo, so that means it has to be Treble enabled. I'm no expert with Treble stuff but I believe GSIs made for arm a-only partitions SHOULD work on here. We haven't tested this for ourselves yet though
Like mentioned before, feel free to drop by and leave a message if you're willing to help us out on our endeavors. I also want to try and get 'Thew a working recovery on his phone again if possible, since for some reason when we try to flash back the image we pulled (with our "best guess" mt6739 scatter file) it didn't work

i might have one.. i will check as soon as i get to the shop

jasonmerc said:
During our quest to gain root on the ANS UL40, @Matthew702 and I went a bit off topic and started messing with his Vortex Synq he picked up. 'Thew was able to find a method to unlock the bootloader, which I will post here shortly, and we shortly thereafter found out that the device is "vulnerable" to using SPFT--as in the VCOM port stays open and allows us to read/write partition images directly from the emmc.
Unfortunately during our testing, he seems to have messed up his recovery image and is unable to restore a stock one on there. If there's any other owners out there willing to help us out (and maybe willing to risk their device for some test builds of TWRP too) I beseech thee to make yourself known.
Click to expand...
Click to collapse
i have one .. if you need

desbloqueokings said:
i have one .. if you need
Click to expand...
Click to collapse
Check your PMs on here, just sent you something

So the other 6739 scatter files we found didn't exactly work for this phone, so we pulled our own with a tool we found on Hovatek. This isn't a "port" from another phone, this directly came from the Synq itself.
Give major thanks to @desbloqueokings for pulling this for us!

The group we had seems a bit inactive now, so I'll post my new creations up here for all you guys here to test and tell us all if it works or not. One is a patched boot image that contains Magisk, all you'd need to do for that is flash the boot image and install a Magisk APK and you should be good to go for root. The other is a dirty port of TWRP Recovery I did from another MT6739 phone. It was hard finding an image to port from, so I want to give a huge thanks to @lopestom who sent me a 6739 image he had that I could port from
PLEASE BE AWARE THAT THESE ARE TEST IMAGES. I DONT HAVE THIS PHONE MYSELF AND CANT TEST IT MYSELF, SO IM NOT SURE IF THESE WILL WORK OR NOT. PLEASE MAKE A BACKUP OF YOUR CURRENT BOOT & RECOVERY IMAGES WITH SPFT USING THE SCATTER FILE ABOVE BEFORE TRYING ANY OF THIS. WHAT YOU DO TO YOUR OWN PHONE IS YOUR OWN RESPONSIBILITY. WHILE I WILL TRY TO HELP YOU IF SOMETHING BREAKS, IM NOT RESPONSIBLE FOR WHAT YOU CHOOSE TO DO
With that being said, here's the Mega folder containing the boot and recovery images. You can either flash these through SPFT like most people do with mediatek phones, or through fastboot, whatever you can get working. I'd also recommend you unlock your bootloader using the method posted above before doing any of this
Let me know if this stuff works or not, if you choose to flash it

Our victory was bittersweet, but a victory nonetheless
We got a working recovery image from @lopestom that seems to work fine on the surface, but when we need to flash the zip that disables dm-verity (disables force encryption) it supposedly breaks the /system partition on the stock ROM. My recommendation would be to take a backup of your /system directory in recovery before trying to flash anything. But since this is a Treble-enabled device, that means GSI ROMs could also work when flashed.
Here's a link to the recovery image we were using. We flashed it in fastboot with an unlocked bootloader but I imagine it would work just fine in SPFT too. I was told by the person that made the image that it's apparently not a good idea to flash the disable-force-encryption zip on a dirty port of a TWRP image like this (and to also never wipe /data). While you should be able to use this TWRP to flash something like Magisk, don't do those other two things for now.
Here's some screenshots from @Matthew702 to show the phone booting to TWRP (we made the mistake of trying to wipe /data and trying to flash the disable-encryption zip, please do not do this):
{
"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"
}

Thank you!

You guys are amazing.
I had a SYNQ just laying around taking up space. Now it is not totally useless. Anyway i wanted to say thanks and post some proof of concept.
Sorry for the horrible quality...
So i used the recovery image named “recoverytest3.img” if im not mistaken. Once that was complete (And i figured i messed everything up because i had a dead android guy every other time....) To my surprise TWRP popped up in russian. At that point i installed magisk manager and downloaded the most recent package then rebooted to recovery and flashed the pack.
NOTES - I did use Command line WIN 10 via the platform tools package your provided for the whole process.... If you don’t know russian or whatever lang TWRP happens to be in just good. Anyway im sure im missing some data i should add but i am dog tired and having trouble reading the phone.
night all and i hope it all goes well for everyone else.
xAlimorAx

xAlimorAx said:
I had a SYNQ just laying around taking up space. Now it is not totally useless. Anyway i wanted to say thanks and post some proof of concept.
Sorry for the horrible quality...
So i used the recovery image named “recoverytest3.img” if im not mistaken. Once that was complete (And i figured i messed everything up because i had a dead android guy every other time....) To my surprise TWRP popped up in russian. At that point i installed magisk manager and downloaded the most recent package then rebooted to recovery and flashed the pack.
NOTES - I did use Command line WIN 10 via the platform tools package your provided for the whole process.... If you don’t know russian or whatever lang TWRP happens to be in just good. Anyway im sure im missing some data i should add but i am dog tired and having trouble reading the phone.
night all and i hope it all goes well for everyone else.
xAlimorAx
Click to expand...
Click to collapse
Yeah it showed up in Russian for our tester too. Not sure why it does that, but otherwise it should still work fine

Need your assistance
Season greetings to you my friend, I ended up formatting my vortex synq using Sp flash tool, after attempting to root, now I have black screen only vcom for sp flash tool works but I need preloaded files and others to unbrick, it was gonna be a Xmas gift for my aunt, but I messed it up, wont turn on just vcom when connected to PC, I have the files stckboot and recovery but sp tool needs pre-loader error, plz help me

Please back up vortex synq
Good I ask for a help to see if someone will have or could make a back up for this vortex synq cell phone since some of us have problems in the firmware when modifying it and we do not have a previous backup if someone can collaborate, it would be infinitely appreciated.

I know this post is old but if somebody can backup the firmware from this it would be awesome, because i am trying to restore my vortex snyq (its hard bricked) but i can't find the preloader for this phone anywhere, when i tried to flash the preloader with sp flash tool it gives me this: STATUS_DA_HASH_MISMATCH, the preloader has to match this phone, if anyone has a backup of the firmware feel free to post it here or dm me, but yeah just wanted to post here.

also need firmware having the same issue ages now
any help much appreciated
safe 2021-2022

use this to unlock bootloader and backup fw https://github.com/bkerler/mtkclient

Making this post to do a dump of the Vortex Synq stuff I had on Mega. XDA allows us to upload large files to here now, and my Mega account is getting pretty full, so I want to transfer everything I have that's Vortex Synq related from there to here. That means any download links pointing to my Mega will be broken, but all of that stuff previously linked by me can be found in this zip.
disclaimer
Feel free to use any of my stuff in any way you see fit. The only thing I ask is that if you do improve on something, share it with everyone else and don't just keep it for yourself. Keep it going for the good of the community/public.
Also, know that it's been a long time since I've messed with this phone, so I don't remember what mods/images/etc in my Mega repo are functional or not. Anything contained within this zip, FLASH AT YOUR OWN RISK.
/disclaimer

[TOOL] fastboot flash / info

I've made a .bat file for flashing and some other stuff. Basic stuff that I use the most.
I made it for One Vision but since Action use exactly the same flash commands, it works for Action as well.
{
"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"
}
Unzip .bat to same dir as your fastboot.exe and double click it or drag it to your cmd window and press enter.
Options:
[f] - FLASH FULL FIRMWARE.
[w] - FACTORY RESET. (erase userdata)
[g] - DEVICE INFO. (getvar all)
[p] - OEM PARTITION INFO. (oem partition)
- GET BOOTLOADER UNLOCK CODE FROM DEVICE. (oem get_unlock_data)
[r] - REBOOT TO SYSTEM, EXIT.
- REBOOT TO BOOTLOADER.
[e] - EXIT, leave the phone in fastboot mode.

Nice work! Really useful for flashing Android 9. However, couple of changes might be necessary for Android 10, in case anyone wants to use it for that. Minor changes.
Such as:
renaming bootloader.bin to bootloader.img
renaming fwbl1.nbl1.bin to fwbl1.img
renaming keystorage.bin to keystorage.img
renaming ldfw.bin to ldfw.img
Other than that, very good idea, and very useful tool!
Thank you!

Updated Fastboot command batch file for Android 10
This is the updated fastboot command batch file for Android 10. Just move to the platform-tools folder and execute it (obviously the stock firmware should be there as well )
Haven't added the fastboot reboot command at the end. You will have to execute that command manually after the flashing is done (in case the device doesn't automatically boots up).
PS: Can't upload the .bat file directly so had to compress it.

Attached the updated version for Android 10, including the rest of the tool, for anyone interested.

arsradu said:
Attached the updated version for Android 10, including the rest of the tool, for anyone interested.
Click to expand...
Click to collapse
Thanks for your contribution. I actually updated the .bat it a few weeks ago to include both pie and A10 flash commands, since not everyone is updated yet.
Then I realized it would be stupid to share it cause someone would probably try to downgrade, which may result in i brick, and then blame me for it although it's common knowledge not to downgrade android version on new devices.
I'll probably have to add a warning about it in the .bat at least.

tys0n said:
Thanks for your contribution. I actually updated the .bat it a few weeks ago to include both pie and A10 flash commands, since not everyone is updated yet.
Then I realized it would be stupid to share it cause someone would probably try to downgrade, which may result in i brick, and then blame me for it although it's common knowledge not to downgrade android version on new devices.
I'll probably have to add a warning about it in the .bat at least.
Click to expand...
Click to collapse
Heey! Welcome back!
It is common knowledge indeed. And I always wondered why is that. Why does it result in a brick? I'm guessing there are some conflicts or something, right? If you have more info (which it sounds like you do) could you share it? I would love to know more about it.
I mean, you could do that pretty easily with older (Android 6 for example) devices. I mean, it's not advisable. But...if the update sucks or it brings some really nasty bugs and you cannot use your phone cause the modem part of it is broken, for example, there should be a way to safely go back to the previous version, right...? At least until the bug is fixed. Shouldn't it be possible to simply flash Android 9 the same way you do Android 10 (I'm guessing the answer is no, but just wondering why...)? You can even do that on iOS, for God's sake! Which is like the definition of no downgrades! But Apple still allows it. Not permanently, but for a while, yeah, if you have an issue with the new version, you can go back to the old one.
But, yeah, you're definitely not the first one advising against going back to, in this case, Android 9.
By the way, nice job with this script. I was working on a version for Mac, since I'm a Mac guy. And...I got pretty far. But one thing I can't figure out how to do: goto (especially for the "Back to Menu" option which is used pretty often). There is no such thing in Bash. So...you have to improvise. And so far, everything I tried failed, for one reason or the other. So..for now, I just boot into Windows if I need to flash anything. Then return to Mac. )
It's' good to see you around. And once again, thank you!
Update:
So...downgrading to Android 9 is definitely possible. You just need to make sure OEM Unlock is checked in Developer Options (allowing bootloader to be unlocked) and that you actually are bootloader unlocked. Everything else is the same.
Update 2:
There seems to be a typo in your script when flashing vbmeta.
It should be "fastboot flash vbmeta_a vbmeta.img" according to the flashfile.xml for Android 9.

arsradu said:
Heey! Welcome back!
It is common knowledge indeed. And I always wondered why is that. Why does it result in a brick? I'm guessing there are some conflicts or something, right? If you have more info (which it sounds like you do) could you share it? I would love to know more about it.
I mean, you could do that pretty easily with older (Android 6 for example) devices. I mean, it's not advisable. But...if the update sucks or it brings some really nasty bugs and you cannot use your phone cause the modem part of it is broken, for example, there should be a way to safely go back to the previous version, right...? At least until the bug is fixed. Shouldn't it be possible to simply flash Android 9 the same way you do Android 10 (I'm guessing the answer is no, but just wondering why...)? You can even do that on iOS, for God's sake! Which is like the definition of no downgrades! But Apple still allows it. Not permanently, but for a while, yeah, if you have an issue with the new version, you can go back to the old one.
But, yeah, you're definitely not the first one advising against going back to, in this case, Android 9.
By the way, nice job with this script. I was working on a version for Mac, since I'm a Mac guy. And...I got pretty far. But one thing I can't figure out how to do: goto (especially for the "Back to Menu" option which is used pretty often). There is no such thing in Bash. So...you have to improvise. And so far, everything I tried failed, for one reason or the other. So..for now, I just boot into Windows if I need to flash anything. Then return to Mac. )
It's' good to see you around. And once again, thank you!
Update:
So...downgrading to Android 9 is definitely possible. You just need to make sure OEM Unlock is checked in Developer Options (allowing bootloader to be unlocked) and that you actually are bootloader unlocked. Everything else is the same.
Update 2:
There seems to be a typo in your script when flashing vbmeta.
It should be "fastboot flash vbmeta_a vbmeta.img" according to the flashfile.xml for Android 9.
Click to expand...
Click to collapse
Sorry, I don't know what it is that can cause bricks when downloading android version, but you're right, everything was easier with older android versions
Did you try to downgrade from 10 to 9, and it worked? It would be great if that was the case.
Thank you..again! Didn't notice that typo and I've had no problems or errors while testing/flashing with it.
I guess that's why I missed it. You don't look for errors if it's working
I'm attaching an updated tool with pie and android 10 flashing, and typo corrected. Also added you to "credits".
For now I've added a warning about downgrade since I don't have any confirmation on if it's possible or not.

tys0n said:
Sorry, I don't know what it is that can cause bricks when downloading android version, but you're right, everything was easier with older android versions
Did you try to downgrade from 10 to 9, and it worked? It would be great if that was the case.
Thank you..again! Didn't notice that typo and I've had no problems or errors while testing/flashing with it.
I guess that's why I missed it. You don't look for errors if it's working
I'm attaching an updated tool with pie and android 10 flashing, and typo corrected. Also added you to "credits".
For now I've added a warning about downgrade since I don't have any confirmation on if it's possible or not.
Click to expand...
Click to collapse
It is possible. I'm back on Android 9 right now.
BUT, a few notes:
1. the problem causing boot failure (and flash failure, with error "(bootloader) validation image failed") is not so much the ROM itself, as it is the Security Patch. It seems that it HAS TO be at least the same version. Which makes me think that it should be possible (at least in theory) to downgrade to Android 9, even without unlocking the bootloader, IF the Security Patch you're coming from is the same as the one of the ROM you're trying to flash. In other words, if your Security Patch is not being downgraded. It has to be at least the same version, or newer, in order to work without any issues.
2. IF you already upgraded to something, anything, with a newer Security Patch, downgrading is no longer possible with a locked bootloader. It IS, however, possible after unlocking the bootloader (which will void the warranty).
3. once in this state (unlocked and downgraded to Android 9), you cannot relock the bootloader anymore (again, IF you're coming from a newer Security Patch). No errors when locking, but upon boot, you'll get the "your device has failed verification and may not work properly" warning, and, despite the message underneath that says "your device will boot in 5 seconds", it won't boot.
I'm guessing...it should be possible to relock the bootloader IF:
1. you're upgrading again to the ROM with the Security Patch you had before (January 2020 for example), but then you won't be able to downgrade again (unless you unlock the bootloader).
2. you're waiting for a security patch for the current Android version to match the one you had before (again, January 2020 for example).
So, in other words, you can either flash a January 2020 Security Patch included with a ROM, or wait to receive it via OTA.
Also, thank you very much for the update. Indeed, it doesn't show any errors. When upgrading to Android 10, I already corrected that line. But I forgot to do the same in the original script. No errors indeed (not sure if it makes any difference....) but it's probably better to be corrected nonetheless.
Soo...thank you!

Hey, first off thanks to both of you arsradu and tys0n for sharing some wonderful insights. What I failed to understand is the fact that how the initial tool was still able to flash the vbmeta file if you failed to mention which slot should it be flashed to? Is explicitly mentioning slot isn't compulsory for all the files?
Another thing which seems to intrigue me is the fact that how come we have fixed the slots in these fastboot commands. Because in dual slots, the active/inactive slots keep on changing every time we flash an OTA and REBOOT the device. So in those cases, why don't we have to modify these fastboot commands according to the changing slots?
For example, if we use fastboot flash vbmeta_a vbmeta.img, then we always use this command only and not vbmeta_b vbmeta.img. It seems we are explicitly assuming that every device should be having 'A' partition as the inactive slot (before REBOOT), but that can't be universally applicable, right? But we all know it works like a charm! So what is it that is actually happening ??
Any update on this by you guys will be highly appreciated

binary**# said:
Hey, first off thanks to both of you arsradu and tys0n for sharing some wonderful insights. What I failed to understand is the fact that how the initial tool was still able to flash the vbmeta file if you failed to mention which slot should it be flashed to? Is explicitly mentioning slot isn't compulsory for all the files?
Another thing which seems to intrigue me is the fact that how come we have fixed the slots in these fastboot commands. Because in dual slots, the active/inactive slots keep on changing every time we flash an OTA and REBOOT the device. So in those cases, why don't we have to modify these fastboot commands according to the changing slots?
For example, if we use fastboot flash vbmeta_a vbmeta.img, then we always use this command only and not vbmeta_b vbmeta.img. It seems we are explicitly assuming that every device should be having 'A' partition as the inactive slot (before REBOOT), but that can't be universally applicable, right? But we all know it works like a charm! So what is it that is actually happening ??
Any update on this by you guys will be highly appreciated
Click to expand...
Click to collapse
Your guess is a s good as mine. ) Maybe tys0n has some better knowledge about it. I was also wondering why only vbmeta_a.... And how does it work though, without specifying which slot to write to? There is no vbmeta_b in the xml. Why? I have no idea.
I mean, it's clear that, for other components, you need to specify it. At least, the flashfile.xml is specifying it. So you would assume it is important. Aaand I don't think anyone is assuming this is a universal tool for every device. Though it can definitely be adapted for other phones.... ) So I'm not assuming every phone is gonna write to the same partition. But these two (the Vision and the Action) seem to have this thing in common.
I'm not sure what you mean by switching slots. I honestly don't have enough experience with that. Also, I don't think the tool is for flashing the OTA updates... I think it's only for flashing the full images. Again, I could be wrong here. This is a new phone for me, and I haven't checked any OTAs for it yet. If you have one, we can analyse that. But...again, I'm not sure if this tool was meant for flashing OTAs.

arsradu said:
Your guess is a s good as mine. ) Maybe tys0n has some better knowledge about it. I was also wondering why only vbmeta_a.... And how does it work though, without specifying which slot to write to? There is no vbmeta_b in the xml. Why? I have no idea.
I mean, it's clear that, for other components, you need to specify it. At least, the flashfile.xml is specifying it. So you would assume it is important. Aaand I don't think anyone is assuming this is a universal tool for every device. Though it can definitely be adapted for other phones.... ) So I'm not assuming every phone is gonna write to the same partition. But these two (the Vision and the Action) seem to have this thing in common.
I'm not sure what you mean by switching slots. I honestly don't have enough experience with that. Also, I don't think the tool is for flashing the OTA updates... I think it's only for flashing the full images. Again, I could be wrong here. This is a new phone for me, and I haven't checked any OTAs for it yet. If you have one, we can analyse that. But...again, I'm not sure if this tool was meant for flashing OTAs.
Click to expand...
Click to collapse
First off I should have been more specific regarding the term "every device", what I actually meant was "every Moto one action device".... An error on my part [emoji2960]....
Regarding the OTA I didn't meant to say that this tool could be/couldn't be used to flash OTAs[emoji85]
Coming back to the point, while executing the fastboot command to flash vbmeta, we always keep the slot A attached to it, rather than checking for the inactive slot beforehand and then flashing. I guess the reason could be the fact that since we are using these fastboot commands to install the stock firmware from scratch...so whatever slot we install the system to, vbmeta needs to be flashed to that slot...
As we are installing system to slot A (fastboot flash system_a system.img), so it's 'vbmeta_a' vbmeta.img.
Now I'll try flashing all these sparsechunk files to slot b and then check whether vbmeta gets flashed to that slot without actually mentioning that slot (B) in its fastboot command [emoji14]
And yes, thanks for your prompt response
Sent from my motorola one action using Tapatalk

binary**# said:
First off I should have been more specific regarding the term "every device", what I actually meant was "every Moto one action device".... An error on my part [emoji2960]....
Regarding the OTA I didn't meant to say that this tool could be/couldn't be used to flash OTAs[emoji85]
Coming back to the point, while executing the fastboot command to flash vbmeta, we always keep the slot A attached to it, rather than checking for the inactive slot beforehand and then flashing. I guess the reason could be the fact that since we are using these fastboot commands to install the stock firmware from scratch...so whatever slot we install the system to, vbmeta needs to be flashed to that slot...
As we are installing system to slot A (fastboot flash system_a system.img), so it's 'vbmeta_a' vbmeta.img.
Now I'll try flashing all these sparsechunk files to slot b and then check whether vbmeta gets flashed to that slot without actually mentioning that slot (B) in its fastboot command [emoji14]
And yes, thanks for your prompt response
Sent from my motorola one action using Tapatalk
Click to expand...
Click to collapse
You know why I love this community? Cause we can share interesting ideas and experiences like this. We can learn from each other. And at least for what I'm concerned, I do have a LOT to learn. And I'm glad I have nice people I can learn from.
As for your experiment, I'm also curious to know the outcome. I never wondered what would happen in that particular case. But then again, I'm very much a noob when it comes to this phone. It's a new phone, never done this on another Moto phone, and I know each manufacturer (and sometimes each phone) has its own particularities. So I'm happy to learn from you guys.

arsradu said:
You know why I love this community? Cause we can share interesting ideas and experiences like this. We can learn from each other. And at least for what I'm concerned, I do have a LOT to learn. And I'm glad I have nice people I can learn from.
As for your experiment, I'm also curious to know the outcome. I never wondered what would happen in that particular case. But then again, I'm very much a noob when it comes to this phone. It's a new phone, never done this on another Moto phone, and I know each manufacturer (and sometimes each phone) has its own particularities. So I'm happy to learn from you guys.
Click to expand...
Click to collapse
Exactly! There are tons of new things to learn from everyone out there. And this being my first Exynos device, I'm just loving the challenges here. Till now I only had Snapdragon devices in which everything was a cakewalk. Furthermore, my recent devices were all Redmi/Xiaomi and it had a pretty neat escape even from hard-brick situations via EDL Mode. But with One Action, everything is so different, thanks to its processor

binary**# said:
Exactly! There are tons of new things to learn from everyone out there. And this being my first Exynos device, I'm just loving the challenges here. Till now I only had Snapdragon devices in which everything was a cakewalk. Furthermore, my recent devices were all Redmi/Xiaomi and it had a pretty neat escape even from hard-brick situations via EDL Mode. But with One Action, everything is so different, thanks to its processor
Click to expand...
Click to collapse
Yeah, I was actually surprised (pleasantly surprised, I might say) it had a Samsung SOC. My previous Moto had a Mediatek and I did not enjoy that one bit. New versions are better though. But that one...not really. And before that I had a SONY Z3 Compact. Cool phone, plenty powerful for its time, but apparently SONY had some troubles with their glue...cause the display kept getting unstuck. )) Looks like this was its "thing".
Anyway, back to Moto Action, I'm liking it so far. The only thing I don't particularly like about it is the update. Kinda slow for an Android One device. But hey, it could be worse. ) I'm not expecting too much from a mid-range device. It's perfect for the price. And for my use case, it gets the job done.

arsradu said:
Yeah, I was actually surprised (pleasantly surprised, I might say) it had a Samsung SOC. My previous Moto had a Mediatek and I did not enjoy that one bit. New versions are better though. But that one...not really. And before that I had a SONY Z3 Compact. Cool phone, plenty powerful for its time, but apparently SONY had some troubles with their glue...cause the display kept getting unstuck. )) Looks like this was its "thing".
Anyway, back to Moto Action, I'm liking it so far. The only thing I don't particularly like about it is the update. Kinda slow for an Android One device. But hey, it could be worse. ) I'm not expecting too much from a mid-range device. It's perfect for the price. And for my use case, it gets the job done.
Click to expand...
Click to collapse
You pretty much summed it up: "kinda slow, but could have been worse". I was confused between Mi A3 and One Action, but I ultimately decided to go with the latter (because of 720p display of Mi A3, there was really no point in going after that). And now I'm quite satisfied with my choice, even more so considering Mi A3 is yet to receive the Android 10 update.

binary**# said:
You pretty much summed it up: "kinda slow, but could have been worse". I was confused between Mi A3 and One Action, but I ultimately decided to go with the latter (because of 720p display of Mi A3, there was really no point in going after that). And now I'm quite satisfied with my choice, even more so considering Mi A3 is yet to receive the Android 10 update.
Click to expand...
Click to collapse
Lucky dawg, you already got it. You got it first, didn’t you? ))
Well, you know, I’m happy for you, man. This way you have more time to experiment with it so you can help others when they get theirs. So, if you think about it, it’s really a win-win. ))

i ****ed up
guys i ****ed up and bricked my moto one action xt2013-4 and now it wont boot and i cant flash stock firmware back to it

achmed420 said:
guys i ****ed up and bricked my moto one action xt2013-4 and now it wont boot and i cant flash stock firmware back to it
Click to expand...
Click to collapse
What did you do? What error do you get on boot? What error do you get when flashing?

i ****ed up
i unlocked boot loader and attempted to flash TROIKA_QSB30.62-17_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml some items failed other flashed some had verification image errors and now it won let me boot anything except recovery and fastboot ... i was on psbs29. 105-27-2 before this with january 2020 security patch

achmed420 said:
i unlocked boot loader and attempted to flash TROIKA_QSB30.62-17_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml some items failed other flashed some had verification image errors and now it won let me boot anything except recovery and fastboot ... i was on psbs29. 105-27-2 before this with january 2020 security patch
Click to expand...
Click to collapse
Where did you get the ROM from? Can you post a link? I'm trying to understand which exact variant (for which region) did you flash.
You still didn't tell me which error do you get upon boot.
Also, did you use the correct commands for Android 10? Which script did you use?
By the looks of it, you tried to flash a ROM with December security patch over one with January security patch. Which, with a locked bootloader is not gonna be possible, but...should be possible with an unlocked bootloader. But since you didn't tell me which error do you get upon boot, I'm not sure how to help you.

Temp root on 7.0 N920VVRS3CRH1

I mean its with SuperSU and of course doesn't survive a reboot and still can't figure out anyway to write to /system..
{
"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"
}

How did you manage this? Was it with just installing SuperSU?

https://github.com/gfunkmonk/N920V_7_TMPROOT

Hey man @gfunkmonk, thank you so much for continuing development on this phone because I lost all hope recently. I saw your link to github.com and downloaded the files. Flashed the first folder using Odin but couldn't figure out what to do with the second folder. I would love if you could assist me in getting it done. I know it's tempting root but at least I could remove bloatware and run certain software. Looking forward to a reply and hopefully full root could actually be a possibility. I'll also volunteer to test anything you come up with if you continue development.

Oh yeah, the second folder is a linux script.. i'll add something for windows. Unfortunately you aren't going to be able to do that anyways. If you try to remount /system read/write the phone will lock up and reboot. I believe this is due to dm-verity which would require patching the kernel. Not possible since the bootloader is locked.

gfunkmonk said:
Oh yeah, the second folder is a linux script.. i'll add something for windows. Unfortunately you aren't going to be able to do that anyways. If you try to remount /system read/write the phone will lock up and reboot. I believe this is due to dm-verity which would require patching the kernel. Not possible since the bootloader is locked.
Click to expand...
Click to collapse
I saw different options on different threads, Would something like this be possible on marshmallow 6.0.1? Or maybe flashing a different firmware such as one for the N920T beacause they use the same processor after flashing a combination file? Full root is possible on 5.1.1 for the N920V but because we cant downgrade if you didn't have an old device without updates it's impossible. So I think the best bet is working with marshmallow for now. I've seen people say they get temp root without crashing using mobilego so maybe applying what you have here would have better luck on MM. Maybe dm-verity could be bypassed and maybe we can use safestrap to flash files that could help.

You most certainly can downgrade to 5.1.1. I did it a couple days ago myself. But yes you do have to flash a combination firmware and use safestrap, Now, I'm not much of a dev but I did make some pretty cool roms for my Moto Droid and later my Droid 3... Now, I remeber we had a safestrap on it, I almost swear it had some nifty was to boot other kernels... but that was just 2012 and I can't remeber.
As far as MM if you had a engboot kernel that gives root in adb, it would work exactly the same. Sorry I don't know much about the N920V, I have a N920T.. I got the Verizon one as a cheap whim on ebay. Plus it was gold lol.
I've got a way to get perm root but its so complicated and still can't touch /system or it reboots so not even worth it,
Either way, I found MM firmware that should flash, I might mess with it later.
Oh, and I certainly wouldn't flash another models anything. Like with Note8s they literally are all the same... I *think* I read something about the N920P being close enough it could boot our kernel or the other way around... something like that. But I think any of that stuff would just end badly.

gfunkmonk said:
You most certainly can downgrade to 5.1.1. I did it a couple days ago myself. But yes you do have to flash a combination firmware and use safestrap, Now, I'm not much of a dev but I did make some pretty cool roms for my Moto Droid and later my Droid 3... Now, I remeber we had a safestrap on it, I almost swear it had some nifty was to boot other kernels... but that was just 2012 and I can't remeber.
As far as MM if you had a engboot kernel that gives root in adb, it would work exactly the same. Sorry I don't know much about the N920V, I have a N920T.. I got the Verizon one as a cheap whim on ebay. Plus it was gold lol.
I've got a way to get perm root but its so complicated and still can't touch /system or it reboots so not even worth it,
Either way, I found MM firmware that should flash, I might mess with it later.
Oh, and I certainly wouldn't flash another models anything. Like with Note8s they literally are all the same... I *think* I read something about the N920P being close enough it could boot our kernel or the other way around... something like that. But I think any of that stuff would just end badly.
Click to expand...
Click to collapse
Hey man could you maybe give me a link to the combination file and safestrap as well as instructions on how to downgrade? There's permanent root on 5.1.1 and I'd rather have a rooted phone on lollipop than a stock one on nougat.
Hopefully you can mess around the MM firmware and figure something out. I think we're about the only two persons still interested in root on the version note 5 so we gotta stick together lol.
I'm definitely no dev or anything but I can contribute with info as I've searched every thread on XDA and other sides and I will help you test etc. Thanks again for everything you're doing man, you've stopped me from giving up on this device XD .

Yeah, so this is the combonation file I used: https://drive.google.com/file/d/1FEU3Msz3MQTCv5DnMe6zc8PlZERa2y6x/edit
So flash it in Odin and let it boot up all the way and whatnot.
use wondershare/mobilego to root from your computer or kingoroot or Kingroot 5.3.7, but you'll want to switch their junk for SuperSU. There's a script for that. Search "replace kingroot with supersu" the file is usually called mrw.zip
Go to the play store and install 'flashfire' If you have trouble with it crashing when you start it manually change the date on the phone to 2012, it'll work then, just believe me.
get safestrap 4.08 here https://forum.xda-developers.com/verizon-galaxy-note5/recovery-locked-safestrap-recovery-v4-t3915714
in flashfire click install zip, select the safestrap and when it asks hit mount system rw. Then hit flash, screen will go dark stuff will scroll by it'll reboot. when it does you'll have an option to enter recovery.
NOBLEROM is pre-rooted 5.1.1 it's here https://forum.xda-developers.com/verizon-galaxy-note5/rom-noble-rom-aoj3-v1-0-t3940543
flash that into recovery and then reflash safestrap before you leave, cause it'll be overwritten by that rom
and uhhh that's it. when you reboot you should be greeted with rooted 5.1.1

gfunkmonk said:
Yeah, so this is the combonation file I used: https://drive.google.com/file/d/1FEU3Msz3MQTCv5DnMe6zc8PlZERa2y6x/edit
So flash it in Odin and let it boot up all the way and whatnot.
use wondershare/mobilego to root from your computer or kingoroot or Kingroot 5.3.7, but you'll want to switch their junk for SuperSU. There's a script for that. Search "replace kingroot with supersu" the file is usually called mrw.zip
Go to the play store and install 'flashfire' If you have trouble with it crashing when you start it manually change the date on the phone to 2012, it'll work then, just believe me.
get safestrap 4.08 here https://forum.xda-developers.com/verizon-galaxy-note5/recovery-locked-safestrap-recovery-v4-t3915714
in flashfire click install zip, select the safestrap and when it asks hit mount system rw. Then hit flash, screen will go dark stuff will scroll by it'll reboot. when it does you'll have an option to enter recovery.
NOBLEROM is pre-rooted 5.1.1 it's here https://forum.xda-developers.com/verizon-galaxy-note5/rom-noble-rom-aoj3-v1-0-t3940543
flash that into recovery and then reflash safestrap before you leave, cause it'll be overwritten by that rom
and uhhh that's it. when you reboot you should be greeted with rooted 5.1.1
Click to expand...
Click to collapse
Hey man I got it to work and i just want to say thank you so much! My error before was that flashify wasn't flashing the zip properly. Flashfire did the trick and the ROM works now and everything. However I'm noticing a few bugs such as the WiFi password is forgotten after a reboot and the fingerprint sensor option no longer works. I know you weren't on development of Noble ROM but any idea on how to fix this?
Also I saw this customn rom - : Samsung OneUI Running Full Android 9.0 For the Exynos7420 Family! . Here's the link if you have time to have a look [ https://forum.xda-developers.com/note5/development/rom-floyd-n7fe-port-v1-0-t3882804 ] Do you think I would be able to flash it now that I have safestrap installed?
Also if there are any updates regarding getting permanent root on Marshmallow or ultimately Nougat think we could be kept in the loop on this thread? I'll probably just check in every few days. Once again thanks for everything you've helped me with.

Jherane said:
Hey man I got it to work and i just want to say thank you so much! My error before was that flashify wasn't flashing the zip properly. Flashfire did the trick and the ROM works now and everything. However I'm noticing a few bugs such as the WiFi password is forgotten after a reboot and the fingerprint sensor option no longer works. I know you weren't on development of Noble ROM but any idea on how to fix this?
Also I saw this customn rom - : Samsung OneUI Running Full Android 9.0 For the Exynos7420 Family! . Here's the link if you have time to have a look [ https://forum.xda-developers.com/note5/development/rom-floyd-n7fe-port-v1-0-t3882804 ] Do you think I would be able to flash it now that I have safestrap installed?
Also if there are any updates regarding getting permanent root on Marshmallow or ultimately Nougat think we could be kept in the loop on this thread? I'll probably just check in every few days. Once again thanks for everything you've helped me with.
Click to expand...
Click to collapse
Again the only kernels we can use are flashed through odin and have to pass secure boot check, So stock or engboot. Now I used to run that rom on my t-mobile version, till it bugged me so much that the camera is broken in the S8/N8 ports past Nougat. As for the wifi pass and biometrics, never checked it. Now, same thing happens when you root a Note8 (which is a similar process) and I believed it's fixed by flashing a Nougat bootloader. Unfortunatley, we don't have one, so basically both will be forever broken.
As for MM, you gotta remember I'm one guy and I'm simply doing this for fun. I don't always know what I'm doing exactly 100%, some of its straight trial and error. I'll probably try flashing stock MM and playing around a bit tomorrow maybe, but I wouldn't have high hopes for anything there either tbh.

I got a little excited because I found an engboot kernel for MM, but unfortunately, it's exactly like nougat. root is temp and trying to modify or remount /system leaves phone unresponsive and eventually reboots. However, I haven't noticed any random reboots like nougat.

gfunkmonk said:
I got a little excited because I found an engboot kernel for MM, but unfortunately, it's exactly like nougat. root is temp and trying to modify or remount /system leaves phone unresponsive and eventually reboots. However, I haven't noticed any random reboots like nougat.
Click to expand...
Click to collapse
Haha the journey continues, I figured it would be a huge task since most people said it was impossible XD. It's a little more stable than Nougat I guess because it's closer to 5.1.1 I think the issue is always gonna lie with getting system to mount r/w without freezing. Whatever code they inserted as soon as the system is altered the kernel panics unfortunately.
Btw Completely get you regarding the development. I didn't mean any disrespect, just meant in the event you had a breakthrough, wasn't so much out of expectation ?
I see you mentioned a S8/N8 port, I'm not the most advanced in the custom rom section so are you saying that the the noble rom you mentioned to me earlier today is an s8 or n8 port or is that another rom? If I can ask you to clarify?
Lastly about the Wi-Fi and Fingerprint, it sucks but I can live with that with everything that root offers. I'm gonna do a complete wipe and repeat the process to see if it goes away or search the noble rom thread to see if anyone had the same error.

Jherane said:
Haha the journey continues, I figured it would be a huge task since most people said it was impossible XD. It's a little more stable than Nougat I guess because it's closer to 5.1.1 I think the issue is always gonna lie with getting system to mount r/w without freezing. Whatever code they inserted as soon as the system is altered the kernel panics unfortunately.
Btw Completely get you regarding the development. I didn't mean any disrespect, just meant in the event you had a breakthrough, wasn't so much out of expectation
I see you mentioned a S8/N8 port, I'm not the most advanced in the custom rom section so are you saying that the the noble rom you mentioned to me earlier today is an s8 or n8 port or is that another rom? If I can ask you to clarify?
Lastly about the Wi-Fi and Fingerprint, it sucks but I can live with that with everything that root offers. I'm gonna do a complete wipe and repeat the process to see if it goes away or search the noble rom thread to see if anyone had the same error.
Click to expand...
Click to collapse
No, the Floyd rom you linked me is an N8 port. The Note8 came up because they way you root it is similar. Flash combination, flashfire, all that.
Now interestingly, 6.0.1 let me make a backup of /system without rebooting, 7.0 would not. So I got one idea here that could work, but it's going to take me a minute to test it.

gfunkmonk said:
No, the Floyd rom you linked me is an N8 port. The Note8 came up because they way you root it is similar. Flash combination, flashfire, all that.
Now interestingly, 6.0.1 let me make a backup of /system without rebooting, 7.0 would not. So I got one idea here that could work, but it's going to take me a minute to test it.
Click to expand...
Click to collapse
Well that actually sounds like progress. There was another thread on here about rooting the N920V, Idk if you've seen it for maybe situations where you get stuck. All the best.

Can you send me/post a link? I have learned a couple things today, its progress but I don't know how much.

gfunkmonk said:
Can you send me/post a link? I have learned a couple things today, its progress but I don't know how much.
Click to expand...
Click to collapse
Long story short: can we flash normal system.img over ENG bootloaders? I got "SYSTEM REV. CHECK FAIL DEVICE:1, BINARY:0" after reboot, so instead we can flash it as flashable zip. yes this work but we end up with bootloop. so what to do to pass this situation.
digging in ENG boot.img ramdisk I can see "export LD_PRELOAD libsigchain.so:liblptcp.so" and system/lib/liblptcp.so nor system/lib64/liblptcp.so is not there in stock 5.1.1, So take them from ENG firmware you will get fully working system over combo bootloader.
Attached Files
File Type: zip LD_PRELOAD-NOBLELTEVZW-SS-FF-flashable.zip
@gfunkmonk I'm trying to post the links here but it won't allow me. I'm gonna private message them to you. Also what do you get from this? I'm seeing on another thread where a DEV said this could fix the Wi-Fi and fingerprint issue because it would be a stock system image but the binary would be bootloader would be unlocked. Any help please. I know this maybe not your area of expertise but I asked on the thread and it seems to be dead. Thanks in advance.
---------- Post added at 03:59 AM ---------- Previous post was at 03:58 AM ----------
gfunkmonk said:
Can you send me/post a link? I have learned a couple things today, its progress but I don't know how much.
Click to expand...
Click to collapse
Long story short: can we flash normal system.img over ENG bootloaders? I got "SYSTEM REV. CHECK FAIL DEVICE:1, BINARY:0" after reboot, so instead we can flash it as flashable zip. yes this work but we end up with bootloop. so what to do to pass this situation.
digging in ENG boot.img ramdisk I can see "export LD_PRELOAD libsigchain.so:liblptcp.so" and system/lib/liblptcp.so nor system/lib64/liblptcp.so is not there in stock 5.1.1, So take them from ENG firmware you will get fully working system over combo bootloader.
Attached Files
File Type: zip LD_PRELOAD-NOBLELTEVZW-SS-FF-flashable.zip
@gfunkmonk I'm trying to post the links here but it won't allow me. I'm gonna private message them to you. Also what do you get from this? I'm seeing on another thread where a DEV said this could fix the Wi-Fi and fingerprint issue because it would be a stock system image but the bootloader would be changed. Any help please. I know this maybe not your area of expertise but I asked on the thread and it seems to be dead. Thanks in advance.

Jherane said:
Long story short: can we flash normal system.img over ENG bootloaders? I got "SYSTEM REV. CHECK FAIL DEVICE:1, BINARY:0" after reboot, so instead we can flash it as flashable zip. yes this work but we end up with bootloop. so what to do to pass this situation.
digging in ENG boot.img ramdisk I can see "export LD_PRELOAD libsigchain.so:liblptcp.so" and system/lib/liblptcp.so nor system/lib64/liblptcp.so is not there in stock 5.1.1, So take them from ENG firmware you will get fully working system over combo bootloader.
Attached Files
File Type: zip LD_PRELOAD-NOBLELTEVZW-SS-FF-flashable.zip
@gfunkmonk I'm trying to post the links here but it won't allow me. I'm gonna private message them to you. Also what do you get from this? I'm seeing on another thread where a DEV said this could fix the Wi-Fi and fingerprint issue because it would be a stock system image but the binary would be bootloader would be unlocked. Any help please. I know this maybe not your area of expertise but I asked on the thread and it seems to be dead. Thanks in advance.
---------- Post added at 03:59 AM ---------- Previous post was at 03:58 AM ----------
Long story short: can we flash normal system.img over ENG bootloaders? I got "SYSTEM REV. CHECK FAIL DEVICE:1, BINARY:0" after reboot, so instead we can flash it as flashable zip. yes this work but we end up with bootloop. so what to do to pass this situation.
digging in ENG boot.img ramdisk I can see "export LD_PRELOAD libsigchain.so:liblptcp.so" and system/lib/liblptcp.so nor system/lib64/liblptcp.so is not there in stock 5.1.1, So take them from ENG firmware you will get fully working system over combo bootloader.
Attached Files
File Type: zip LD_PRELOAD-NOBLELTEVZW-SS-FF-flashable.zip
@gfunkmonk I'm trying to post the links here but it won't allow me. I'm gonna private message them to you. Also what do you get from this? I'm seeing on another thread where a DEV said this could fix the Wi-Fi and fingerprint issue because it would be a stock system image but the bootloader would be changed. Any help please. I know this maybe not your area of expertise but I asked on the thread and it seems to be dead. Thanks in advance.
Click to expand...
Click to collapse
Ahhh, I get it but no. That's what we did. used the ENG bootloader and kernel (combination files) then re-wrote the system image. Which speaking of, I've got to test out the new nougat image I made earlier.

Okay so what I'm asking is, the issue with the Wi-Fi and biometrics seems to be with the Kernel that's included in noble rom. I read somewhere where you can flash a system image from an earlier 5.1.1 firmware. Say AOJ3 and it should still work since it's close enough to stock and that should fix the Wi-Fi issue. My problem is I have the system image extracted but I don't know how to create a flashible Zip from the system.img so I can use flashify or safetrap to flash it. I saw the kitchen stuff but it's a little complicated for me.
The Dev for noble rom also created a script that would remove the parts of the system that wouldn't allow the normal system image to boot over the ENG bootloader so I'm wondering if this would work. I'm really just desperately searching for a fix to the wifi password being forgotten after reboot so if you have any ideas or workaround it would be greatly appreciated. I can live without the fingerprint scanner.
I saw something about maybe using Tasker to move the file containing the saved password to somewhere safe at shutdown and restoring it on reboot but I'm not sure of proof of concept so I thought I'd ask here first if it sounds feasible.

either flashfire or the safestrap twrp lets you flash an 'img' file... But remeber if it doesn't work you have to redo the entire process and flash & root the combo again

[CLOSED]LG Stylo 6 root development! ANY HELP APPRECIATED. DISCORD LINK AVAILABLE

Moderator Announcement:
Thread closed and content removed on request of OP.
- Oswald Boelcke

I SERIOUSLY would like to know how you get that bug report so I can get any files for the stylo 6 boost mobile
Where did you find the zip or link to the site hosting the zip in the big report? I can get that far but I really want any help on getting similar files from this specific device model/variant
I am not gonna lie your post is an oasis in a desert and I hope this does find its way into the right hands to push root dev

Me to I have the lg stylo 6 from my cable company

I'm currently browsing through the root directory to see if I can pull the boot.img.. there's a method of rooting it with magisk manager.. the bigger issue is how to reinstall the modified boot.img.. I think we will need the bootloader unlocked
Spoiler
{
"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"
}

I just checked on firmware download and the kdz for lgup is available to download.. in theory because I don't have a pc to verify.. a possible root method might be as simple as, extracting the kdz file, modifying the boot.img with magisk manager, rebuild the kdz file with a kdz tool.. then flashing the modified kdz with lgup.. then install magisk manager after 1st boot and hope we have root.. feel free to test or share any other ideas..
Spoiler

It seems like very few working on this project.. I've come across a dual mode lgup made by one of our developers capable of crossflash.. probably the best version of lgup to flash firmware with modified boot.img.. I'm also buying a laptop for experiments on this device.. I now have 2 versions of the stylo 6 to play with.. hopefully I don't go overboard and turn them to paperweight .. the only thing I need is the method or tool to rezip kdz to try achieving root myself.. if anyone find such a tool, please share ..

The boot image wouldn't work. In theory, you would use kdzTools and it will turn the KDZ into a DZ file and then you extract the DZ file. You would have to use Qfil or fastboot to flash a modified boot image, and have an unlocked bootloader. LGUP is an amazing tool to crossflash different firmware from different Stylo variants, but with AVB 2.0, this doesn't work on many of the LG devices that came out of the box with Android 10, and repacking the KDZ with a modified boot image would fail because of the boot image being signed inncorrectly. Your best bet is to see if there is an exploit like what was found on the V50, and to hope that someone makes gets Firehose working for the Stylo.

Yeedatoy said:
The boot image wouldn't work. In theory, you would use kdzTools and it will turn the KDZ into a DZ file and then you extract the DZ file. You would have to use Qfil or fastboot to flash a modified boot image, and have an unlocked bootloader. LGUP is an amazing tool to crossflash different firmware from different Stylo variants, but with AVB 2.0, this doesn't work on many of the LG devices that came out of the box with Android 10, and repacking the KDZ with a modified boot image would fail because of the boot image being signed inncorrectly. Your best bet is to see if there is an exploit like what was found on the V50, and to hope that someone makes gets Firehose working for the Stylo.
Click to expand...
Click to collapse
I just found all the information necessary to root our Stylo.. I'm not experienced enough to do the final step but I'm willing to pay our more experienced developers to do it.. we can simply use an all in one tool I'll share the link to, that will let us extract the kdz, modify the system.img and reconstruct the kdz.. in the extracted system.img we can hopefully find the boot.img and modify it for root using magisk manager.. dual mode lgup should flash the modified kdz.. I plan to try.. then on 1st boot we can manually install magisk manager and enjoy root.. the downside is with a locked bootloader all we get is root.. no custom recovery or custom rom until we unlock the bootloader.. but it's a start.. again.. bounty for dev that can use this handy tool.. Happy New Year
GitHub - ehem/kdztools: Tools for working with KDZ files (LG's Android device upgrade format)
Tools for working with KDZ files (LG's Android device upgrade format) - GitHub - ehem/kdztools: Tools for working with KDZ files (LG's Android device upgrade format)
github.com
Spoiler

lowkeyst4tus said:
I just found all the information necessary to root our Stylo.. I'm not experienced enough to do the final step but I'm willing to pay our more experienced developers to do it.. we can simply use an all in one tool I'll share the link to, that will let us extract the kdz, modify the system.img and reconstruct the kdz.. in the extracted system.img we can hopefully find the boot.img and modify it for root using magisk manager.. dual mode lgup should flash the modified kdz.. I plan to try.. then on 1st boot we can manually install magisk manager and enjoy root.. the downside is with a locked bootloader all we get is root.. no custom recovery or custom rom until we unlock the bootloader.. but it's a start.. again.. bounty for dev that can use this handy tool.. Happy New Year
GitHub - ehem/kdztools: Tools for working with KDZ files (LG's Android device upgrade format)
Tools for working with KDZ files (LG's Android device upgrade format) - GitHub - ehem/kdztools: Tools for working with KDZ files (LG's Android device upgrade format)
github.com
View attachment 5179601
Click to expand...
Click to collapse
Give it a shot, it's not as confusing as it may look at first glance. Just put everything in the same folder on you computer. Open the tool and select your KDZ file. Extract it, and it turns it from a KDZ file into DZ file. Select extract DZ in KDZ tools next, and it will fully extract the file. You'll see a bunch of bin files. You can simply rename bin, to img for boot, and then copy it to your phone and patch it with magisk. Then copy the patched boot image back to your PC and change the img extension back to bin and rezip the KDZ.

Do you have fastboot access on the Stylo 6?

Not sure yet but I don't think I'll need it.. I don't want to start by diving deep and overlook a simpler solution than accessing fastboot.. I just need a developer that can modify a kdz.. if I can simply achieve root via the new magisk method, it's a start.. I'm picking up another stylo 6 today, then a real computer cause my chromebook useless.. I'll update if I get a modified kdz and what happens when I try to flash

lowkeyst4tus said:
Not sure yet but I don't think I'll need it.. I don't want to start by diving deep and overlook a simpler solution than accessing fastboot.. I just need a developer that can modify a kdz.. if I can simply achieve root via the new magisk method, it's a start.. I'm picking up another stylo 6 today, then a real computer cause my chromebook useless.. I'll update if I get a modified kdz and what happens when I try to flash
Click to expand...
Click to collapse
I myself have just finally found this thread and am super more than willing to put in some work!
so i've gotta:
- `adb reboot recovery`
- boot into fastboot from recovery
- unlock the bootloader with `fastboot oem_unlock`
- let the phone factory reset with an unlocked bootloader
_____________________
and:
- download the .kdz firmware file for the unlocked version on pc
- locate and extract the boot.bin with kdzTools and convert it to boot.img
- send extracted file to my personal phone
- patch boot.img in magisk manager app on my phone
- send it back to pc with `adb pull /sdcard/boot.img C:/users/myname/`
_____________________
then:
- load patched boot.img into the stylo 6 through `fastboot flash boot boot.img`
- `fastboot reboot` and let it reboot hopefully with root AND with carrier unlock
- download magisk manager to verify
I guess I'll give this a shot and get back to you guys.

haise.zero said:
I myself have just finally found this thread and am super more than willing to put in some work!
so i've gotta:
- `adb reboot recovery`
- boot into fastboot from recovery
- unlock the bootloader with `fastboot oem_unlock`
- let the phone factory reset with an unlocked bootloader
_____________________
and:
- download the .kdz firmware file for the unlocked version on pc
- locate and extract the boot.bin with kdzTools and convert it to boot.img
- send extracted file to my personal phone
- patch boot.img in magisk manager app on my phone
- send it back to pc with `adb pull /sdcard/boot.img C:/users/myname/`
_____________________
then:
- load patched boot.img into the stylo 6 through `fastboot flash boot boot.img`
- `fastboot reboot` and let it reboot hopefully with root AND with carrier unlock
- download magisk manager to verify
I guess I'll give this a shot and get back to you guys.
Click to expand...
Click to collapse
If you do manage to get into fastboot, there's 2 commands to try.. the new command is " fastboot flashing unlock".. you can also try getting unlock.bin even though there's no mention of availability.. it might be required for fastboot unlock.. the unlocked firmware is what I was going to experiment with also.. if you do manage to successfully extract the boot.img from the kdz, skip fastboot flashing.. just install magisk manager on your phone and follow the instructions on other threads to modify the boot.img.. then rezip the kdz with the modified boot.img.. flash with dual mode lgup for better chance of success.. it should install and boot normal.. on the surface you should not notice any change like errors with boot.. after 1st boot, install magisk manager and it should say root is working .. good luck and I look forward to your results
Spoiler

lowkeyst4tus said:
If you do manage to get into fastboot, there's 2 commands to try.. the new command is " fastboot flashing unlock".. you can also try getting unlock.bin even though there's no mention of availability.. it might be required for fastboot unlock.. the unlocked firmware is what I was going to experiment with also.. if you do manage to successfully extract the boot.img from the kdz, skip fastboot flashing.. just install magisk manager on your phone and follow the instructions on other threads to modify the boot.img.. then rezip the kdz with the modified boot.img.. flash with dual mode lgup for better chance of success.. it should install and boot normal.. on the surface you should not notice any change like errors with boot.. after 1st boot, install magisk manager and it should say root is working .. good luck and I look forward to your results View attachment 5181357
Click to expand...
Click to collapse
Sounds good, thanks for the advice! It's super helpful.
I'll be taking a crack at it here soon, or maybe tomorrow since it's 1:30am and I'm having a drink (depends on my mood ). I'll probably go with fastboot flashing unlock_critical just to be on the safe side of things and have everything unlocked from the get go for development purposes. I did run into an issue when I ran that command already -
C:\Users\myname>fastboot flashing unlock_critical
...
FAILED (remote: Unrecognized command flashing unlock_critical)
finished. total time: 0.006s
I can get into fastbootd on the device, and need to read up on it a bit since nearly every fastboot command I send in is unrecognized (see above) or gets a response like FAILED (remote: Unable to open fastboot HAL)
I'll enable test signing mode on my windows machine and get the right drivers installed, and get fastbootd working and then try again. I'll likely run into a roadblock though, since Boost doesn't exactly want us unlocking the bootloader - nor does LG, apparently...
For now, here's a few resources that might help catch you up on things and possibly give me some more room to wiggle around:
- Android documentation on fastbootd and fastboot being moved to userspace (contains information about the HAL)
- A mildly helpful and more easy-on-the-eyes article that can help explain the above documentation
I'll try and get past this issue. There's gotta be something, somewhere... I first just need to communicate with the phone correctly and get it to do what I need it to do in fastboot mode.
I also have downloaded two different .kdz files and have indeed extracted both of them into .dz files. I didn't get past that last night, so I'll have to get in there soon or maybe tomorrow and see if I can't find the system.img and/or the boot.img contained within. If I can, I'll be sure to get it patched and try to pass it to the phone.
For anyone trying to use the kdztools, it's outdated and you'll get some error about the headers when you try to extract the Stylo 6's .kdz files. Below are links to a couple of repositories that will be helpful:
- An updated fork of the original kdztools from somebody else that I've forked for laziness (fixes the headers issue)
- A fork of KDZZ, an up-to-date-enough tool for zipping .kdz files into TWRP-able zip files (again, personally forked for laziness)
There's only one problem... Boost Mobile.
I bought this phone from a third party and it is still registered to someone else on the Boost network. Since it's gone through a factory reset and my google account has been added to it, the phone isn't activated on their network and they seem to have disabled my ability to use wifi as they constantly send me screens and notifications trying to get me to activate the device, which I don't have the money to do. So, no internet access; I'll have to adb push and pull files and apks in order to get things working. I could factory reset and not ping their networks or put the other person's SIM in, but for the sake of longevity, I'd love if anybody had a solution to carrier unlocking this thing - or even an idea of what to do for that? Could I flash stock firmware? Is there any process to read the code I need from logcat? Any ideas at all? New ideas, hypothetical ideas, or even old ideas I could shine up and make new? Even just a thought? This is a pain.
I will keep everyone posted! I'd ask you all do the same - about this, and about carrier unlocking just as a possible favor.
PS: Bounty, huh? I could really use the reward. I might just have to take you up on that if we can get this working haha, exciting!

haise.zero said:
Sounds good, thanks for the advice! It's super helpful.
I'll be taking a crack at it here soon, or maybe tomorrow since it's 1:30am and I'm having a drink (depends on my mood ). I'll probably go with fastboot flashing unlock_critical just to be on the safe side of things and have everything unlocked from the get go for development purposes. I did run into an issue when I ran that command already -
C:\Users\myname>fastboot flashing unlock_critical
...
FAILED (remote: Unrecognized command flashing unlock_critical)
finished. total time: 0.006s
I can get into fastbootd on the device, and need to read up on it a bit since nearly every fastboot command I send in is unrecognized (see above) or gets a response like FAILED (remote: Unable to open fastboot HAL)
I'll enable test signing mode on my windows machine and get the right drivers installed, and get fastbootd working and then try again. I'll likely run into a roadblock though, since Boost doesn't exactly want us unlocking the bootloader - nor does LG, apparently...
For now, here's a few resources that might help catch you up on things and possibly give me some more room to wiggle around:
- Android documentation on fastbootd and fastboot being moved to userspace (contains information about the HAL)
- A mildly helpful and more easy-on-the-eyes article that can help explain the above documentation
I'll try and get past this issue. There's gotta be something, somewhere... I first just need to communicate with the phone correctly and get it to do what I need it to do in fastboot mode.
I also have downloaded two different .kdz files and have indeed extracted both of them into .dz files. I didn't get past that last night, so I'll have to get in there soon or maybe tomorrow and see if I can't find the system.img and/or the boot.img contained within. If I can, I'll be sure to get it patched and try to pass it to the phone.
For anyone trying to use the kdztools, it's outdated and you'll get some error about the headers when you try to extract the Stylo 6's .kdz files. Below are links to a couple of repositories that will be helpful:
- An updated fork of the original kdztools from somebody else that I've forked for laziness (fixes the headers issue)
- A fork of KDZZ, an up-to-date-enough tool for zipping .kdz files into TWRP-able zip files (again, personally forked for laziness)
There's only one problem... Boost Mobile.
I bought this phone from a third party and it is still registered to someone else on the Boost network. Since it's gone through a factory reset and my google account has been added to it, the phone isn't activated on their network and they seem to have disabled my ability to use wifi as they constantly send me screens and notifications trying to get me to activate the device, which I don't have the money to do. So, no internet access; I'll have to adb push and pull files and apks in order to get things working. I could factory reset and not ping their networks or put the other person's SIM in, but for the sake of longevity, I'd love if anybody had a solution to carrier unlocking this thing - or even an idea of what to do for that? Could I flash stock firmware? Is there any process to read the code I need from logcat? Any ideas at all? New ideas, hypothetical ideas, or even old ideas I could shine up and make new? Even just a thought? This is a pain.
I will keep everyone posted! I'd ask you all do the same - about this, and about carrier unlocking just as a possible favor.
PS: Bounty, huh? I could really use the reward. I might just have to take you up on that if we can get this working haha, exciting!
Click to expand...
Click to collapse
I have the boost mobile version and I got the cricket wireless version yesterday just for gradient blue.. according to Gsmarena, all versions of the Stylo 6 are identical.. I'm going to try flashing the unlock firmware on the boost mobile version.. it should unlock the sim and no longer ask for activation .. then I'm going to sell it before I drop it .. I'll use my blue one for development

lowkeyst4tus said:
I have the boost mobile version and I got the cricket wireless version yesterday just for gradient blue.. according to Gsmarena, all versions of the Stylo 6 are identical.. I'm going to try flashing the unlock firmware on the boost mobile version.. it should unlock the sim and no longer ask for activation .. then I'm going to sell it before I drop it .. I'll use my blue one for development
Click to expand...
Click to collapse
Could you link me to the unlocked firmware? Is it the Q730M10l? Or another one?
I would love to flash the unlock firmware and factory reset this thing to get some internet and functionality back. It would greatly help with my development
Thank you!

haise.zero said:
Could you link me to the unlocked firmware? Is it the Q730M10l? Or another one?
I would love to flash the unlock firmware and factory reset this thing to get some internet and functionality back. It would greatly help with my development
Thank you!
Click to expand...
Click to collapse
The unlocked model according to Best Buy is LMQ730QM.. I can't find a download source yet but I'm still looking

Weird, my Stylo 6 says its software version is Q730TM... Q730TM10P to be specific There shouldn't be any issues if they're all identical though, right? I can safely flash a Q730QM image on a Q730TM device?
And I'm looking as well - I'll edit this post if/when I find a source
Edit:
Found this, and this, but I'm unsure if Q730QM10c or Q730QM10d is the genuinely unlocked version, (the C variant is USA and the D variant is USL) and I'm also unsure what carrier, if any, NAO stands for (Q730QM10c_00_NAO_US_OP_0908.kdz for example)
I suppose I'll download the kdz and flash it to try it out. I can always revert back to stock if something goes wrong. I'll let you know how that goes
Hmm... I'm having some trouble. kdzdownloader downloads 0kb. I tried switching my useragent but it didn't work out, either. You having any better luck? Able to attach the file?
Woohoo! I got it.
Use this to install the XDM download manager, and then paste this link into a new job (just hit the + button). It just worked for me.
We officially have the .kdz for Q730QM10C! Time to flash it as soon as it's done downloading.

haise.zero said:
Weird, my Stylo 6 says its software version is Q730TM... Q730TM10P to be specific There shouldn't be any issues if they're all identical though, right? I can safely flash a Q730QM image on a Q730TM device?
And I'm looking as well - I'll edit this post if/when I find a source
Edit:
Found this, and this, but I'm unsure if Q730QM10c or Q730QM10d is the genuinely unlocked version, (the C variant is USA and the D variant is USL) and I'm also unsure what carrier, if any, NAO stands for (Q730QM10c_00_NAO_US_OP_0908.kdz for example)
I suppose I'll download the kdz and flash it to try it out. I can always revert back to stock if something goes wrong. I'll let you know how that goes
Hmm... I'm having some trouble. kdzdownloader downloads 0kb. I tried switching my useragent but it didn't work out, either. You having any better luck? Able to attach the file?
Woohoo! I got it.
Use this to install the XDM download manager, and then paste this link into a new job (just hit the + button). It just worked for me.
We officially have the .kdz for Q730QM10C! Time to flash it as soon as it's done downloading.
Click to expand...
Click to collapse
Great job bro.. use dual mode lgup from XDA as it's designed for crossflashing and supposed to have more features than regular lgup.. let me know if you sim unlock with Q730QM firmware.. Q730TM is the Boost Mobile model.. I have that and the Q730AM in gradient blue from cricket wireless.. I want to crossflash both to Q730QM

Alrighty, well I've been halted. Before I could get to flash, I installed the LG drivers because LGUP wasn't detecting my device (or maybe I was just being dumb).
After that... the phone stopped being recognized. In device manager it says Unknown USB (Device Descriptor Failed)
I've looked online, no solutions have helped. I've installed the Google USB drivers through Android Studio, I've uninstalled the device and reconnected the phone, tried reinstalling the LG drivers, I've factory reset the phone, tried a different USB port, a different cable, and nothing. After I factory reset, it showed up for a bit, but upon a reconnection it crapped itself again and refuses to show up.
Any ideas? I can't continue development if I can't communicate with the phone.
Never mind, possibly? It works after uninstalling the device and replugging again... for the 20th time. But ADB still won't recognize the phone even as unauthorized; it just doesn't show up. Weird... I guess I'll tinker and get back to the post here in a while.
It's back to the error... so damn weird. I'll look into it. If and when I find a solution I'll let you know.
Development has been paused for the time being.

[CLOSED] Delete Thread.

Due to the disrespect of certain members I will no longer share the tutorials.

Wait does this mean you finally got my script to work?

lebigmac said:
Wait does this mean you finally got my script to work?
How about a little feedback in my project thread? Is that too much to ask for?
Did the latest fix work for you or not? Hello?
Click to expand...
Click to collapse
I said you were working on it. LOL. If it worked I'd be writing a Guide for that!

Make sure boot.img matched with the phone build number, or the phone may get bootloop.
Moto One Ace is one of the easiest phone to root

mingkee said:
Make sure boot.img matched with the phone build number, or the phone may get bootloop.
Moto One Ace is one of the easiest phone to root
Click to expand...
Click to collapse
Exactly. Definitely made a note of that in the guide since that is why the frozen touchscreen issue happens.

Articul8Madness said:
.This tutorial is for people like me than ran into problems rooting the Moto One 5G Ace XT2113 (MetroPCS Qualcomm Variant) running on stock Android 10. I got this phone literally last week brand new in the box. This is a hand holding guide for the Noobs that really are intimidated by rooting their device.
Follow the following at your own risk! I am not responsible for any mishaps with your devices.
I want to thank @mingkee and @sd_shadow for pointing me in the right direction. And for the rest of the contributors that I took bits and pieces from that helped me figure out rooting this; I did achieve root out the starting gate but initially lost touchscreen functionality. The issue was that you have to use the boot.img of your firmware to patch into Magisk; if you do this with your phone out the box you really don't know which firmware was used and that is where the bungle happens. This will clear up all those potential freakout moments.
Thanks to Android 10 being System As Root with all these new super partitions running amuck, you cannot get Write access in the actual system files. So even when you achieve root, you can't do much. @lebigmac is working on that as we speak. Drop by his thread on R/W access and beta test his script so he can get more knowledge about how our phone works.
Introduction/Preparation
First, go and prepare by READING EVERYTHING. Very important. This is the Qualcomm variant and NOT the Mediatek variant. Flashing does make a difference between the two. Last thing you want to do is brick the device because you flashed the wrong firmware to the wrong processor, or you flashed other software for the other similiar Moto One 5G and it bricked.
Second, unlock the bootloader. All T-Mobile and their subsidiary variants can be unlocked by Motorola as well as International and Motorola factory variants; go to their bootloader official unlock site and follow their instructions, it's easy peasy. If you do it in firefox it may not go to the third step page and hang on the page where you put the long code in (follow instructions on page to get the unlock code you'll see what I'm talking about). It is HIGHLY ADVISABLE to do this in Waterfox or Chrome (I used Waterfox). And yes, you may have to request the code 3x to get it to send to your email depending on their server traffic. When you get it, follow Motorola's instructions for unlocking the bootloader in fastboot. It will show you that the bootloader is unlocked.
Verizon and ATT Variants CANNOT BE BOOTLOADER UNLOADER UNLOCKED.
***NOTES SO YOU DON'T FREAK OUT***
1. I did NOT see the motorola post screen telling me it was unlocked. I had to find this in fastboot's menu.
2. The only way to restore the phone if something goes wrong is by flashing it via fastboot. The way to get to fastboot is turn the phone off and press Volume Down and Power. The Motorola tool will NOT work. That's normal.
3. You will see a cute message that you've unlocked the bootloader and that the phone software integrity is compromised when you boot the phone up every single time after the bootloader unlock. It will also say press the power button to pause. This is normal. Give it a minute, you havent broke it.
4. OEM Unlocking should already be activated and greyed out in the Developer Options once the bootloader is unlocked; you can't access it anymore.
Files
You will need an SD card for root. You will also need other apks to successfully help you pull off root ready to install. Pull ALL the necessary files you will need.
1. Get Minimal ADB and Fastboot (it's easier).
2. Download the Motorola Drivers from their site if yo don't already have them (if you run into problems you will have to uninstall and reinstall them through their utility which is found on PC here: C:\Program Files\Common Files\Motorola Shared\Mobile Drivers
3. Cpu-Z.apk (Very important, its hard to know your hardware without this).
4. Magisk v22.0.apk (They no longer have a separate Magisk Manager)
5. Root Explorer.apk (This software helps navigation better but you can use any Explorer of your choice).
6. Root Checker.apk
7. Stock Firmware XT2113-3_KIEV_RETEU_10_QZK30.Q4-40-62_subsidy-DEFAULT_regulatory-XT2113-3-EU-SAR_CFC.xml (This is important if you mess up the boot image trying to root). You can get the firmware of your choice at Motorola Official Firmware For Kiev.
8. Patience (and a good movie keeping you going).
As of now this device as no TWRP, so you have to do this the old fashioned way to root. And just so you know, I used Windows 7 for all of this.
Pre-Rooting
1. Make sure the phone is fully charged.
2. Make sure your sim card is REMOVED from the phone. Everytime you wipe the phone or do anything messing with the boot image the phone resets itself to factory settings, and tries to push an update. Just take the silver key thing and pop it out. You will have to push it back in and out in a second, but start with it out.
3. Make sure your wifi is OFF.
4. Make sure your SD is in and mountable and all files you need are on the card.
5. Make sure you Save boot.img to your SD Card from your firmware files. This is very important for root.
6. Make sure your developer options are activated.
7. Make sure your USB debugging is enabled AND you've given permissions for your computer to have administrative access with it enabled (more on this below).
8. Make sure to check CPU-Z for your hardware specs so you download the right files for the phone and avoid potential problems.
9. Make sure you manually set USB to Transfer files (no other option will work and by default its set to Charge this Device).
10. Make sure you have the STOCK CABLE that comes with the phone. Like most Motorolas this model is funky about using other cables.
11. Make sure you back up all your calls, texts, pics, etc. Flashing the firmware is the ultimate factory reset and you will lose all your files on the phone. SMS Restore is a good software to backup Calls and Text logs and it supports keeping MMS.
12. Make sure you have the internet. It is necessary for some steps.
Rooting
1. Make sure all the firmware files are extracted into your Minimal ADB and Fastboot folder (or whatever ADB folder you're using for this).
2. Open FlashFile.xml in Notepad. This is located among the firmware files you put in the Minimal ADB and Fastboot folder.
3. Cut, copy, and paste everything from the FlashFile that is shown and then paste it in an online Flash file Converter. I used Online Flash File Converter here.
4. Convert the text by pressing the bar below where you pasted the text. It may be in Spanish or Portuguese but is should say something like Cerar Commandos.
5. Copy the text by hitting the two pieces of paper icon in the corner after it's converted. Or just cut copy and paste manually.
6. Turn the phone completely OFF.
7. Plug your phone via USB cable into the computer.
8. Press Volume Down and Power to boot into fastboot mode. Do not use "adb reboot bootloader" as that command may or may not work and hang at "waiting for device" (it was iffy for me and it knocked off USB permissions BADLY).
9. Open up Minimal ADB and Fastboot (Make sure you don't have it set to open this as an administrator, it messes with permissions) Make sure your firmware files are in the Minimal ADB directory or it won't work.
10. Paste the contents of the flashfile converter into Minimal ADB and Fastboot. This should start the process of the flashing.
11. When the entire flash is complete, boot the phone and disconnect phone from the computer. Ignore the bootloader unlock error.
12. Wait. Sometimes this takes up to 3-5 minutes on a new flash. You should see the boot animation of Motorola.
13. Push your Sim Card back into the phone.
14. Start setting up your device on the screen. Sim Card must be in or it will give you a message your phone is Network Locked.
15. Once you make it to the Wifi Setup screen take the Sim back OUT the phone. Do not connect to Wifi.
16. Once you are done with setup, go to Settings>About phone.
17. Go all the way down to Build Number and press it until you unlock Developer Options.
18. Go to Settings>System>Advanced>Developer Options. Advanced is a pull down tab that will reveal Developer Options.
19. Disable Automatic System Updates. I know this is hard for some people, but a forced OTA update may cause problems and prohibit root.
20. Enable USB Debugging. Disable Verify bytecode of debuggable apps. Disable Verify apps over USB if it is highlighted. Exit.
21. Put your SD/Sim card back into the phone.
22. Go to the Files folder and install Magisk first, then Root Explorer and Root Checker.
23. Open Magisk. You will see Magisk and App. Hit Install by Magisk (a fingerprint looking icon is to its left).
24. Allow Magisk to access photos, media, and files if it asks.
25. Select option "Select and Patch A File."
26. It will take you to a screen where you can select your explorer to navigate to your SD card where you saved the boot.img. Go there and select it.
27. Magisk will save it as magisk_patched.img. Once you get it patched, find where it saved, make sure it's on your SD card and then turn off the phone.
28. Plug your phone via USB cable into the computer.
29. Press Volume Down and Power to boot into fastboot mode.
30. Open up a fresh Minimal ADB and Fastboot (Make sure you don't have it set to open this as an administrator, it messes with permissions) Make sure you transfer the magisk_patched.img that Magisk patched off your SD card into this folder.
31. Rename your original boot.img to "boot.img original" or whatever distinct name you want to give it in your Minimal ADB and Fastboot folder.
32. Rename your magisk_patched.img to boot.img.
33. In Minimal ADB and Fastboot type "fastboot flash boot boot.img" and hit enter.
34. If all goes well it should flash to the partition before it says done and in how many seconds.
35. When it is done, reboot phone by selecting START (keep pressing volume rockers until you see it, then press the power button).
36. Wait for the bootloader cannot be trusted screen to pass (may take a minute) and wait for the Hello Moto opening.
37. Open Root Checker and confirm root. You can uninstall it after confirmation if you like.
38. Open Root Explorer. A prompt asking you to grant permission should pop up.
Congrats. You should be rooted now.
***NOTES SO YOU DON'T FREAK OUT***
1. Do NOT flash someone else's patched boot image. It WILL NOT WORK. Do the work, find your firmware, and patch the boot image yourself. You're asking for bootloop hell if you do as your boot.img that Magisk patches needs to match that particular firmware you used.
2. While it hasn't happened to me, You may have followed everything perfect and it still bootlooped. Save yourself the frustration and just flash it over. See the next section on the proper way to flash so you don't lose your baseband, IMEI, or any other important stuff.
3. While you won't lose anything just flashing boot.img, you will lose everything having to flash ALL the firmware over. Keep backups of all your important stuff.
****Notes on Flashing The Stock Firmware if you have to****
In the event you bootloop and have to start from scratch, follow my guide on restoring the firmware on the phone. And don't worry - it won't relock the bootloader. You can find my guide here: The Complete Noob Guide to Flashing via Fastboot MetroPCS Moto One 5G Ace XT2113 [Qualcomm Version]
Hope this helps my fellow TMobile and subdiary acolytes and othoers. I have flashed and reflashed my phone with different variant roms trying to force Write status and beta testing scripts for @lebigmac on our device so it's pretty straightforward now.
I will try and answer questions if I can or point you in the right direction.
Click to expand...
Click to collapse
Question I keep seeing you have to use adb to fix if messed up, sorry not a question yet but that's wrong. When I did it I think I mixed up my moto g stylus boot.img and got a boot loop. I flashed stock boot.img and it came up with a screen saying Android os was corrupted try to reboot if didn't work factory reset is needed. Rebooted popped up again hit factory reset and the phone did it for me. Not sure if you knew that, question tho lol sorry, can I patch boot img with magisk and flash to a phone that's not fresh from a factory reset

bobbyp1086 said:
Question I keep seeing you have to use adb to fix if messed up, sorry not a question yet but that's wrong. When I did it I think I mixed up my moto g stylus boot.img and got a boot loop. I flashed stock boot.img and it came up with a screen saying Android os was corrupted try to reboot if didn't work factory reset is needed. Rebooted popped up again hit factory reset and the phone did it for me. Not sure if you knew that, question tho lol sorry, can I patch boot img with magisk and flash to a phone that's not fresh from a factory reset
Click to expand...
Click to collapse
Well, when I rooted the 1st time I got a frozen touchscreen as I didn't have the correct Firmware (as the phone's firmware out of the box auto updated and the firmware that was available did not match its peripherals). So my phone lost ALL TOUCH ability. The way I explain in this guide is what worked for me, as the LHSA tool doesn't help at that stage. And honestly, I think adb is better and more familiar to most Moto folks that have had several devices and got root on them.
If you mixed up your Moto G Stylus boot.img, all you have to do is try and reflash your firmware boot.img and flash it (or if you have root your patched boot.img). I've flashed this phone almost 70 times in 9 days and I normally do not reflash my boot.img as its already patched to the firmware and I'm just starting from scratch. However, I wouldn't advise that on recovery.img that went wrong, just saying. The phone will force a factory reset.
I don't recommend a factory reset for flashing if you're trying to get root. It's best to compile all the files in ADB to make sure they're taking together, and not going after the fact. There is no shutting off DM-Verity at this time, especially without TWRP and a patch for it, and this model is a bit funky about added flashing with this new Dynamic Partition crap.

Articul8Madness said:
Well, when I rooted the 1st time I got a frozen touchscreen as I didn't have the correct Firmware (as the phone's firmware out of the box auto updated and the firmware that was available did not match its peripherals). So my phone lost ALL TOUCH ability. The way I explain in this guide is what worked for me, as the LHSA tool doesn't help at that stage. And honestly, I think adb is better and more familiar to most Moto folks that have had several devices and got root on them.
If you mixed up your Moto G Stylus boot.img, all you have to do is try and reflash your firmware boot.img and flash it (or if you have root your patched boot.img). I've flashed this phone almost 70 times in 9 days and I normally do not reflash my boot.img as its already patched to the firmware and I'm just starting from scratch. However, I wouldn't advise that on recovery.img that went wrong, just saying. The phone will force a factory reset.
I don't recommend a factory reset for flashing if you're trying to get root. It's best to compile all the files in ADB to make sure they're taking together, and not going after the fact. There is no shutting off DM-Verity at this time, especially without TWRP and a patch for it, and this model is a bit funky about added flashing with this new Dynamic Partition crap.
Click to expand...
Click to collapse
That's what mine did, I flashed stock boot, is corrupted my phone says and forced reset, I'm newish to moto, Samsung for many years, had to ditch them tho lol.
I appreciate the help and hope I didn't come across as arguing, more like clarifying. I too prefer adb over anything, only get the rom from tool. Again thanks for info.

bobbyp1086 said:
That's what mine did, I flashed stock boot, is corrupted my phone says and forced reset, I'm newish to moto, Samsung for many years, had to ditch them tho lol.
I appreciate the help and hope I didn't come across as arguing, more like clarifying. I too prefer adb over anything, only get the rom from tool. Again thanks for info.
Click to expand...
Click to collapse
If your bootloader is unlocked the only way you should have gotten the corruption is if you flashed an incompatible firmware. Mine came with MetroPCS but I've flashed RETUS and RETEU well. I'd stray from any VZW or ATT software just because you can't trust their firmware won't lock down the bootloader.
Or maybe the software just didn't download well. Try re-downloading it . I've had a bad download mess up a flash before.

I think it's cause 1 magisk wasn't installed and 2i used a different phone to patch

bobbyp1086 said:
I think it's cause 1 magisk wasn't installed and 2i used a different phone to patch
Click to expand...
Click to collapse
You have to install Magisk and patch on the phone in question since it's looking for that firmware and that phone's peripherals. You can't use another phone - that's a no no. This ain't Gingerbread, lol.

Articul8Madness said:
You have to install Magisk and patch on the phone in question since it's looking for that firmware and that phone's peripherals. You can't use another phone - that's a no no. This ain't Gingerbread, lol.
Click to expand...
Click to collapse
I'm fairly new to magisk, just recently in past year or so stopped using supersu. Not by choice lol but upgraded my note 4 lmao. So as far as the script for read and write, never flashed and after I got magisk, no modules only su permissions, fx did mount /
{
"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"
}
and fix file permissions, it's in settings

bobbyp1086 said:
I'm fairly new to magisk, just recently in past year or so stopped using supersu. Not by choice lol but upgraded my note 4 lmao. So as far as the script for read and write, never flashed and after I got magisk, no modules only su permissions, fx did mount /View attachment 5279427View attachment 5279429View attachment 5279431View attachment 5279433 and fix file permissions, it's in settings
Click to expand...
Click to collapse
Having Root on this device is not going to magically fix the fact that Android 10 on ALL DEVICES is READ ONLY. You will have to go to @lebigmac or @munjeni and try their R/W mount scripts to get true root access. Munjeni's V2 worked for me. He's on V7 now. LeBigMac has been hard at work trying to get us up and running with his script, but we have Super partitions AND A/B. So it's taking some time.

Articul8Madness said:
Having Root on this device is not going to magically fix the fact that Android 10 on ALL DEVICES is READ ONLY. You will have to go to @lebigmac or @munjeni and try their R/W mount scripts to get true root access. Munjeni's V2 worked for me. He's on V7 now. LeBigMac has been hard at work trying to get us up and running with his script, but we have Super partitions AND A/B. So it's taking some time.
Click to expand...
Click to collapse
I am not familiar with either but take it that's it's not an easy task. Should I run v2 or v7 then? Moto one g ace metro.
I was fooled by the trickery, I thought something seemed off with the root on modern phone's.

I just bought a new Moto One 5G ace and was wondering where I can find the stock T-Mobile Firmware variants to prevent bricking?

I successfully rooted it with Magisk patched and ready to go. Unfortunately for the time being the phone won't bypass safety net even with MagiskHide. It just won't work but I'm really happy this phone can be unlocked

bobbyp1086 said:
I am not familiar with either but take it that's it's not an easy task. Should I run v2 or v7 then? Moto one g ace metro.
I was fooled by the trickery, I thought something seemed off with the root on modern phone's.
Click to expand...
Click to collapse
Android 10 is very challenging. It is easy to root but it is a trickable root with a false sense of root since Google locked all Android 10 and newer as Read Only on the System with this super partition crap trying to be Apple.

Skel40 said:
I just bought a new Moto One 5G ace and was wondering where I can find the stock T-Mobile Firmware variants to prevent bricking?
Click to expand...
Click to collapse
Check my guide. I posted link to where the repository is.

Skel40 said:
I successfully rooted it with Magisk patched and ready to go. Unfortunately for the time being the phone won't bypass safety net even with MagiskHide. It just won't work but I'm really happy this phone can be unlocked
Click to expand...
Click to collapse
You will not pass safety net because you've rooted it and Android 10 will block it. It isn't necessary, especially if you delete all Google stuff and their tracking Covid crap.

Articul8Madness said:
Having Root on this device is not going to magically fix the fact that Android 10 on ALL DEVICES is READ ONLY. You will have to go to @lebigmac or @munjeni and try their R/W mount scripts to get true root access. Munjeni's V2 worked for me. He's on V7 now. LeBigMac has been hard at work trying to get us up and running with his script, but we have Super partitions AND A/B. So it's taking some time.
Click to expand...
Click to collapse
Hi @Articul8Madness. Thanks for mentioning me
There's a Motorola user who recently got my script to work using the troubleshooting repair script that I posted here
It turns out the lpmake arguments that are auto-generated by the original script were flawless and were not the root cause of the unidentified lpmake error that some Motorola users were experiencing at the end of the original script. According to @Xiaoleng the error was most likely caused by some kind of new Motorola security feature that prevents the terminal command from executing if the arguments are too long. Go figure.
And he was even able to fastboot flash the super_fixed.bin in one piece without having to first split it up into chunks. That's a huge surprise to me. I always thought Motorola users can only fastboot flash super sparsechunks?!
Please feel free to give it a try and report back your results. Thanks. Good luck!