Moto G8 Play was a phone launched in October 2019 and that curiously had few (or none) mods created, and until today, February 2021, no one had managed to at least root this device, with guides that bricked the device(or made it bootloop), or at least did not work, where even with the boot.img patched, the magisk manager could not get root access on the device. Thinking about it and after losing many nights trying to do everything to root my phone, I finally got it, and decided to write this guide for you, with proof of operation and a lot of joy in having made such progress,
but enough with ceremonies, let's go to the guide in fact.
What do I need to do before read this guide?
First of all, backup all your data, you will surely lose it if you don't.
Second, keep in mind that I am not responsible for any errors or damage to the device, keep in mind that this is a mod guide that makes you lose the warranty on your device. What I did worked for me, and theoretically it works for you as long as you do everything correctly.
And lastly and most importantly, unlock the bootloader of your device, if you don't do this, it is possible to brick and transform it into a paper weight for lack of attention. Thinking about it, I wrote a quick guide to unlock bootloader, follow the steps:
1. Go to settings> System> About phone> Build Number and follow the image
{
"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"
}
2. Still in the settings, go to System> Advanced> Developer options and again follow the image:
3. On your computer, download platform-tools here and extract it to any folder you prefer. Also download and install Motorola USB drivers. After extracting and installing, open the platform-tools folder and copy the folder path, then open windows command prompt(cmd) and type the following commands:
in cmd, type cd and paste the path you copied, and hit enter. After that, type "adb devices" with your USB connected device(Remember to authorize USB debugging when connecting your device to the PC), if you did everything right, you will see something like this:
then type "adb reboot bootloader" to reboot your device for the correct mode. Once in bootloader mode, do not close cmd, it will still be useful. Access the motorola bootloader unlock site and follow the instructions provided. If you did everything right, your bootloader will appear with the status of flashing unlocked on the screen.
Ah, I talked about backup at the beginning, right? I'm glad you did the backup, because you just had your phone reset and data deleted. Now that you've installed everything right, let's start the hybridization process of your smartphone ... Let's install the Motorola One Macro ROM, which is basically the same thing as Moto G8 Play, but with more RAM, storage and 64- bit enabled, following this, download the One Macro Stock ROM here and extract it to the same folder as platform-tools:
It will look more or less like the photo above. After that, you will need a script to transform flashfile.xml into an appropriate flashfile.bat, and you can download this script here. Extract the .exe in the same folder as the platform-tools and the one macro rom, after this run and it will generate a flashfile.bat file. If your device is connected to the usb in bootloader mode you can now run the .bat and flash the rom on your device. Always remember to leave the battery with more than 50% charge to avoid problems and brick the device. If you did everything right, your device will start up normally. Configure, then go to settings and activate debugging following the steps at the beginning of the guide. You can notice that virtually your device is now a Motorola One Macro with the hardware of a Moto G8 Play, done that, let's go to the root process.
Copy the boot.img file from the platform-tools folder to any folder on your android. After that, install the magisk manager on the official website and open the app. In the magisk tab, click install and then "Select and Patch a file", select the boot.img file, after that make the selection process again, click the arrow and wait for magisk to finish the patch. After that, open google files and copy magisk_patched_XXXXX.img to your phone's root folder, and copy it to your computer again, in the platform-tools folder. Preferably rename it to an easier name, like magisk.img.
Do the process of opening cmd and pasting the folder path with the command "cd" before it. Then restart to bootloader mode as you learned above, and enter the command "fastboot flash boot_a magisk.img"
after finishing the process, type "fastboot flash boot_b magisk.img" and restart your device. If all goes well the magisk manager will detect the root and your phone will be ready.
This is the guide, I hope I have helped everyone who has gone so long without being able to root their devices. I wasted a night testing and writing this, so please consider giving feedback and if you post as a tutorial, leave the method credits to Daniel Santos (me).
Not works, when i flash the rom and the device restart, it give a message that is corrupt
CÆSAR said:
Not works, when i flash the rom and the device restart, it give a message that is corrupt
Click to expand...
Click to collapse
Did you unlock the bootloader correctly? If so, which version of Macro One did you use? If you want, I can pass the exact same version that I installed here and it works perfectly
Yes, i've already unlocked the bootloader and runned a comand in adb to check it, and used the last rom available. One question, installing the one macro firmware can damage the device? Because a 64 bit OS need more resources than the 32 bit software from the g8 play.
CÆSAR said:
Yes, i've already unlocked the bootloader and runned a comand in adb to check it, and used the last rom available. One question, installing the one macro firmware can damage the device? Because a 64 bit OS need more resources than the 32 bit software from the g8 play.
Click to expand...
Click to collapse
well, i used the version of the image i sent and it works 100% normal. As for the system, Motorola One Macro and Moto G8 Play have the exact same architecture. They differ only from some sensors, RAM and internal storage. If you want more details of the process, you can send me a dm on twitter (@danadsees) and I can give you the necessary support. I've never tested with the latest version, which uses Android 10, but versions using Android 9 work normally
ok, i will try with that version, and a last question, you tried to play games after install that version?
FInnaly i tried with your version and it works, thx
Does the G8 Play work flawlessly with the One Macro Rom?
RandoMike said:
Does the G8 Play work flawlessly with the One Macro Rom?
Click to expand...
Click to collapse
I think so. I didn't test it in depth, but in games performance looks to be better, and it worked normally in this few days that i've using it.
CÆSAR said:
I think so. I didn't test it in depth, but in games performance looks to be better, and it worked normally in this few days that i've using it.
Click to expand...
Click to collapse
That's curious. I'm gonna try to root my phone. I hope not to brick it haha.
RandoMike said:
That's curious. I'm gonna try to root my phone. I hope no to brick it haha.
Click to expand...
Click to collapse
I ended hard bricking my device . However, I managed to repair it . I dunno what could go wrong xd. I hope this tutorial would make this forum alive again xdxd.
RandoMike said:
I ended hard bricking my device . However, I managed to repair it . I dunno what could go wrong xd. I hope this tutorial would make this forum alive again xdxd.
Click to expand...
Click to collapse
This is my third update. It worked! I can't really believe it!
I would tell all the people who want to do this to be careful. You can hard brick your cellphone, specially if you flash the preloader.bin image. Being that said, thank you, Daniel. Finally I found a tutorial that works haha!
RandoMike said:
This is my third update. It worked! I can't really believe it!
I would tell all the people who want to do this to be careful. You can hard brick your cellphone, specially if you flash the preloader.bin image. Being that said, thank you, Daniel. Finally I found a tutorial that works haha!
Click to expand...
Click to collapse
thank you for your trust. I missed many nights looking for a valid method and I had to develop it myself. this also makes it possible to use custom roms and recoveries from Macro One as well
Daniel69cc said:
thank you for your trust. I missed many nights looking for a valid method and I had to develop it myself. this also makes it possible to use custom roms and recoveries from Macro One as well
Click to expand...
Click to collapse
Finally, there is some hope to revive this forum hahaha
Someone tryed with the android 10 version?
CÆSAR said:
Someone tryed with the android 10 version?
Click to expand...
Click to collapse
In my case, my cellphone just bootlooped. I think I also have to upgrade the fastboot, but I'm afraid it'll just make the phone hard brick. Or maybe I just need to try other Android 10 versions haha.
RandoMike said:
In my case, my cellphone just bootlooped. I think I also have to upgrade the fastboot, but I'm afraid it'll just make the phone hard brick. Or maybe I just need to try other Android 10 versions haha.
Click to expand...
Click to collapse
First update: I tried to restore the stock firmware of my Moto and it hard bricked (what a surprise, huh xD). I had to flash the original fastboot doing some stuff. Maybe we can upgrade to Android 10 doing that hardbrick trick (however, if you are not lucky, you can render the device unbootable), which allows you to reflash either the G8 Play's fastboot or the Macro one (it's weird that the fastboot of the One Macro also works on the G8 Play hahaha).
Second update: The One Macro Rom of Android 10 can't be flashed. It just gives me the error "sparse image size span overflow". I just proceeded to reflash the original Android 10 firmware of the G8 Play (I didn't wanna hardbrick it hahaha). It would be wonderful if anyone managed to solve or try to solve this problem.
Third update: I managed to root my G8 Play with its Stock Android 10 image! hahaha. I just flashed the "boot_a" slot with the original boot.img patched by magisk.
RandoMike said:
First update: I tried to restore the stock firmware of my Moto and it hard bricked (what a surprise, huh xD). I had to flash the original fastboot doing some stuff. Maybe we can upgrade to Android 10 doing that hardbrick trick (however, if you are not lucky, you can render the device unbootable), which allows you to reflash either the G8 Play's fastboot or the Macro one (it's weird that the fastboot of the One Macro also works on the G8 Play hahaha).
Second update: The One Macro Rom of Android 10 can't be flashed. It just gives me the error "sparse image size span overflow". I just proceeded to reflash the original Android 10 firmware of the G8 Play (I didn't wanna hardbrick it hahaha). It would be wonderful if anyone managed to solve or try to solve this problem.
Third update: I managed to root my G8 Play with its Stock Android 10 image! hahaha. I just flashed the "boot_a" slot with the original boot.img patched by magisk.
Click to expand...
Click to collapse
the root really works with the g8 play android 10 rom? i'm going to try
CÆSAR said:
the root really works with the g8 play android 10 rom? i'm going to try
Click to expand...
Click to collapse
Yep. I believed I would just get the "no bootable a/b slot" error, but it worked!
This guide is for moto g8 play or moto one macro or both ?
Related
Hello guys! At last, it is here! This tool has some distinct similarities with hasoon2000's tool (which is awesome by the way), but it also has few differences, more will be explained below.
Please note, this tool has certain requirements that you MUST follow!
This will flash a T-Mobile OTA, so if you are on ANY other carrier, you must have SuperCID, or wait for a similar tool that I may release in the future for your specific carrier. As of now, you must have SuperCID in order to run this tool (although you can try without, but results are NOT guaranteed)
As noted in the title, this tool is currently in beta, so use this as your own risk! I have tested this many times myself, but unfortunately, I haven't had enough testers respond to my request, so I am releasing this to the community as I know this would be a valuable tool.
Also, due to some people in this forum, I feel compelled to state this in big, bold, colored text.
This tool is only meant FOR S-Off users, and it does not, in ANY way, give you S-Off! NO, it will NOT work with an unlocked bootloader. To use this tool, you MUST have S-Off, plain and simple.
Click to expand...
Click to collapse
And now an explanation on what this tool does:
I've made a simple tool that will completely update your phone to the latest T-Mobile's OTA (Ice Cream Sandwich version), but without the need of reinstalling your custom recovery and reflashing SuperUser.
This is great for:
- People (especially newbies) with S-OFF that want to update to the latest OTA update, without having to find an Engineering/J-Bear hboot, without having to find a recovery to flash, without having to figure out how to flash superuser package, and without figuring out which fastboot commands to input.
- People without a SDCard, as this tool DOES NOT require a SDCard to flash the OTA!
- People who are stuck in a seemingly endless bootloop, and cannot figure out what to do in order to get the device back into a working state.
The true beauty of this tool is that it is ridiculously simple. All you really need to do is read the instructions, plug in your phone, run the program. In this program, you literally only have to touch your computer twice. The first one to accept the disclaimer, and then the 2nd to ensure that you have plugged in your USB cable.
Then this program will do the rest. It'll automatically detect which state your phone is in and then run the correct commands, check your S-Off state, flash the entire modified OTA*, detect whether the flash succeeded or failed, flash SuperUser and the free 4EXT recovery application, and does some other commands to ensure the phone works upon boot-up. This entire update should take no more than 15 minutes to complete, depending on your phone.
* The modified OTA update consists of 4Ext recovery, J-Bear Hboot (.2222), and a custom splash screen (hope you like it :laugh: )
Click to expand...
Click to collapse
Credits:
-MadMaxx82 for permission to use his awesome recovery and his free 4EXT recovery app
-Hyuh (and the entire unlimited.io team) for their work with S-Off and permission to use the J-Bear Hboot
-Hasoon2000 and Dark Nightmare for some of his suggestions and ideas
-Kgs1992 for some of his help on batch files
-Dark Nightmare, gregma, andy55, and shekki for testing this tool out
-I probably forgot some others, contact me if I did so I can credit you accordingly!
Click to expand...
Click to collapse
Before we go any further about this S-Off tool, you need to understand that there is always a risk of damaging your phone, even though I have personally tested this tool many times.
By downloading this tool, you accept all risks associated with this tool. I am not responsible if this breaks your phone, bricks it, or otherwise render your phone unusable. The standard disclaimer applies to this situation. Although I will try to help you, you are still responsible for whatever happens to your device.
Alright, moving on.
You MUST ensure that you have met the following requirements:
-The HTC Amaze 4G must have S-OFF
-The device must have SuperCID! (If it's a non T-Mobile phone)
-The device must be rooted!
-Battery must be *FULLY* charged
-A Windows computer with ADB/Fastboot drivers installed Files are included - but if it does not work, install these yourselves manually
-You must have an USB *DATA* cable. -- If you can transfer files and send adb/fastboot commands with the USB cable, it will work
-You must have USB Debugging turned on!
-Most importantly, you must have the ABILITY to follow directions
I cannot stress this enough. Make sure your battery is of decent charge. You do not want to have your phone shut down in middle of the process.
Click to expand...
Click to collapse
Instructions:
(READ THROUGH THE INSTRUCTIONS BEFORE DOING ANYTHING!)
Step 0) Ensure that your requirements are met.
Step 1) Make a nandroid backup if you want to restore your phone to the way it was before the tool. After backing up, make sure to make a backup of the nandroid backup, and both of the internal and external SDCards to your computer. I can not guarantee if the tool will wipe your external SDCard (It shouldn't, but it doesn't hurt to be safe)
Step 2) Disable any antivirus applications. This is a precautionary measure. You don't want the antivirus to remove something important in the middle of the update.
Step 3) Download the tool
Step 4) Verify the MD5 checksums to make sure they match. You do not want a corrupted tool.
The MD5 checksum is displayed on the download site, but if you need it, the MD5 checksum is:
f697211a9a49b293c4b99eee80de47d9
Step 5) After verification, use your favorite file extraction utility, put the entire ToolV2 folder (not just the files, but the entire folder) in an accessible location such as the C:\ Drive, Desktop, or whatever is the easiest for you.
Step 6) Open the folder *IMPORTANT* DO NOT change the files, move them, rename them, or anything of that nature. If you do, the tool most likely will not work.
Step 7) Open the RUN-ME.exe file (with an icon like 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"
}
) *IMPORTANT* Do not extract the file named 'UltimateUpdater', leave it alone!
Step 8) Ensure that your phone is turned on. It can be in recovery, fastboot, or even in normal mode. It will automatically detect the device state. However, if possible, it is recommended to have your phone be booted into android.
Plug in the data cable. Make sure it is set to charge only (If booted into android). Do not forget to turn on USB Debugging!!!
Step 9) Follow on screen instructions. The process may take a while. Do not touch the phone, touch your computer, close the program, and most importantly, do NOT unplug the USB cable! It should auto-detect your device state, and it will detect your S-OFF state as a precautionary measure. When you get to this point like in the screen shot:
Follow it! Do not do any of those things! Leave it alone for 10 minutes! It will then detect if the update was successful. (If it does not do anything after 10 minutes, or does not detect anything, post on this thread and we'll see what needs to be done)
Click to expand...
Click to collapse
DOWNLOAD LINK
PLEASE READ BEFORE DOWNLOADING!
http://d-h.st/r22
Click to expand...
Click to collapse
Also, if you don't like the splash screen, this is your first step in figuring out how to mod your phone. Remember, DON'T post a question on how to change the splash screen, there ARE posts in the Amaze forums complete with step-by-step instructions on how to install a different splash screen!
It's time you started using the search button, my friend
Also, don't forget to press the THANKS button if this tool helped you!
Congrats! You finally released it! lol
hasoon2000 said:
Congrats! You finally released it! lol
Click to expand...
Click to collapse
Indeed I did! You know, you should test it out too. It's pretty neat if I say so
I gave ideas too , Jk JK, congrats on your release and thanks for the creds. :good:
Dark Nightmare said:
I gave ideas too , Jk JK, congrats on your release and thanks for the creds. :good:
Click to expand...
Click to collapse
Indeed you did! Maybe you'd like to read the credits again
Keylogger_0 said:
Indeed you did! Maybe you'd like to read the credits again
Click to expand...
Click to collapse
Lol I was jk dude, thanks though, appreciate it . Now back on topic, I'll be recommending this as the restoration option for all s-off users.:good:
Edit: Don't mention it bro, you did a good job and this will be a saviour for many.
Dark Nightmare said:
Lol I was jk dude, thanks though, appreciate it . Now back on topic, I'll be recommending this as the restoration option for all s-off users.:good:
Click to expand...
Click to collapse
Thanks!
thank you!!!
As I lost hope this utility actually worked!!! Hassons utility wouldn't read my phone. I flashed nightmare sense 1.6 and my phone wouldn't boot up, then I went to recovery like you're supposed to right? Using twrp and it just crashed and it automatically boot it up to the boot loop. And this helped so much thank you for this.
HTC amaze bootloop
Keylogger_0 said:
Hello guys! At last, it is here! This tool has some distinct similarities with hasoon2000's tool (which is awesome by the way), but it also has few differences, more will be explained below.
Please note, this tool has certain requirements that you MUST follow!
This will flash a T-Mobile OTA, so if you are on ANY other carrier, you must have SuperCID, or wait for a similar tool that I may release in the future for your specific carrier. As of now, you must have SuperCID in order to run this tool (although you can try without, but results are NOT guaranteed)
As noted in the title, this tool is currently in beta, so use this as your own risk! I have tested this many times myself, but unfortunately, I haven't had enough testers respond to my request, so I am releasing this to the community as I know this would be a valuable tool.
And now an explanation on what this tool does:
I've made a simple tool that will completely update your phone to the latest T-Mobile's OTA (Ice Cream Sandwich version), but without the need of reinstalling your custom recovery and reflashing SuperUser.
This is great for:
- People (especially newbies) with S-OFF that want to update to the latest OTA update, without having to find an Engineering/J-Bear hboot, without having to find a recovery to flash, without having to figure out how to flash superuser package, and without figuring out which fastboot commands to input.
- People without a SDCard, as this tool DOES NOT require a SDCard to flash the OTA!
- People who are stuck in a seemingly endless bootloop, and cannot figure out what to do in order to get the device back into a working state.
Before we go any further about this S-Off tool, you need to understand that there is always a risk of damaging your phone, even though I have personally tested this tool many times.
By downloading this tool, you accept all risks associated with this tool. I am not responsible if this breaks your phone, bricks it, or otherwise render your phone unusable. The standard disclaimer applies to this situation. Although I will try to help you, you are still responsible for whatever happens to your device.
Instructions:
(READ THROUGH THE INSTRUCTIONS BEFORE DOING ANYTHING!)
Also, if you don't like the splash screen, this is your first step in figuring out how to mod your phone. Remember, DON'T post a question on how to change the splash screen, there ARE posts in the Amaze forums complete with step-by-step instructions on how to install a different splash screen!
It's time you started using the search button, my friend
Also, don't forget to press the THANKS button if this tool helped you!
Click to expand...
Click to collapse
Hi, i flashed this OTA but my HTC amaze still in a bootloop, could you help me with this?
Are you on tmobile? if not did you SuperCID?
This tool has helped me several times, you should not be in a bootloop if you followed the steps correctly. it installs a completely new everything, recovery included (4ext). you should at least be able to access that from bootloader and restore a backup.
Andy1886 said:
Hi, i flashed this OTA but my HTC amaze still in a bootloop, could you help me with this?
Click to expand...
Click to collapse
What carrier are you on? CID? Can you also PM me your UpdateLog.log file found in the AIO folder of this tool? Don't post it here, PM it to me.
Gonna try it now... Will update u in a while..
This is the error I get while I am on trying to run the exe file...
I am running Win 7 ultimate X86 (32 bit)
vikasraj said:
Gonna try it now... Will update u in a while..
This is the error I get while I am on trying to run the exe file...
I am running Win 7 ultimate X86 (32 bit)
Click to expand...
Click to collapse
Any help regarding the tool from the developer..
Q&A for [ROOT] Root with Locked Bootloader for SGP621 using giefroot
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROOT] Root with Locked Bootloader for SGP621 using giefroot. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Deleted
I'm at (24).
I requested the link to get an unlock code at developer.sonymobile.com. It's now been over 24 hours and i haven't get an email yet. Tried ist with a differnet email adress too.
How long does it take usally?
WiFi isssue after flashing D6603 rom
Hi,
I liked the idea of flashing D6603 rom on my SGP621 and rooting it..
I like my tablet now even more..
But the WiFi is not working for me now, only LTE/3G..
Also the camera not working, but I don't care because I'm using my mobile phone for taking pictures..
Is there any way to make WiFi working with D6603 rom?
Thanks...
russse said:
I'm at (24).
I requested the link to get an unlock code at developer.sonymobile.com. It's now been over 24 hours and i haven't get an email yet. Tried ist with a differnet email adress too.
How long does it take usally?
Click to expand...
Click to collapse
Normaly it takes not more than a few minutes. You can resend it at any time by requesting it again on sonymobile. If it still does not work you may need to get in touch with developer support on their website.
---------- Post added at 03:38 PM ---------- Previous post was at 03:33 PM ----------
kamal3383 said:
Hi,
I liked the idea of flashing D6603 rom on my SGP621 and rooting it..
I like my tablet now even more..
But the WiFi is not working for me now, only LTE/3G..
Also the camera not working, but I don't care because I'm using my mobile phone for taking pictures..
Is there any way to make WiFi working with D6603 rom?
Thanks...
Click to expand...
Click to collapse
No, you cannot. As there are other drivers used. If you want root and WiFi you need to follow the tutorial to the end and in the process unlock your bootloader and return to the SGP621 stock rom.
Hi lowtraxx
Thanks a lot for your great work!
I have the SGP611 version and have successfully followed rurie's guide to root the unit. Now i'm installing the rooted stock, but I'm stuck at your step 30. In step 28 I booted into fastboot and used Flashtool to execute the Z3TC-stock-twrp.img by pressing the button "Select system to Flash" and selecting the img-file, see pic.
I have tried to reboot by pressing "Reboot into fastboot mode (via Fastboot) to press volume down on purple light. However, the light never goes purple. It is blue, then swishes to red for an instance/glimpse. I have tried to hold down "volume down" and to press it many times but nothing works. Can you explain step 30 to 32 in detail, e.g. by using the buttons on the Flashtool - Fastboot toolbox (see pic)?
Thanks
{
"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"
}
Hi,
I hope you did not flash the SGP621_23.0.1.A.0.167_CE.ftf onto your device but the one that is for the SGP611, because from your description it sounds like you are in a bootloop. I haven't used Flashtool to flash a kernel before, I am only using the command line. But my best guess would be that you need to click on Select Kernel to flash, select the Z3TC-stock-twrp.img and click on flash. Once that is done, you should reboot the device and wait until the Xperia logo shows up and the LED goes purple. If you now press volume down you get into recovery where you need to flash the RICDefeat.zip file you downloaded. If that does not work, download flashtool binary for windows, open a cmd prompt as Administrator, boot into fastboot mode and execute 'fastboot flash boot /path/to/the/Z3TC-stock-twrp.img' and then continue as outlined above.
lowtraxx said:
Hi,
I hope you did not flash the SGP621_23.0.1.A.0.167_CE.ftf onto your device but the one that is for the SGP611, because from your description it sounds like you are in a bootloop. I haven't used Flashtool to flash a kernel before, I am only using the command line. But my best guess would be that you need to click on Select Kernel to flash, select the Z3TC-stock-twrp.img and click on flash. Once that is done, you should reboot the device and wait until the Xperia logo shows up and the LED goes purple. If you now press volume down you get into recovery where you need to flash the RICDefeat.zip file you downloaded. If that does not work, download flashtool binary for windows, open a cmd prompt as Administrator, boot into fastboot mode and execute 'fastboot flash boot /path/to/the/Z3TC-stock-twrp.img' and then continue as outlined above.
Click to expand...
Click to collapse
Thanks for your reply. I have used the SGP611 firmware, so no problem.
I have flashed Z3TC-stock-twrp.img unto the unit using the button Select Kernal, but when I reboot the LED never goes purple - only blue and for a quick glimpe (~1-3 ms) red. If I boot the unit in normal mode (without fastboot mode or flash mode) it gets stuck at the Sony logo and cannot be shut down without pressing the small force-shut-down button next to the SD card. (It booted as SPG611 just fine before I flashed Z3TC-stock-twrp.img unto it - using the button Select Kernal.)
EDIT. Tried to download Z3TC-stock-twrp.img again and flash it using CMD in windows. Now I can access Recovery.
I'm progressing, but only slowly.
I'm at step 32 in the guide but every time I try to load/install RICDefeat it fails. Nothing happens when I try to issue 'adb sideload /path/to/RICDefeat.zip', so I have put the file on my external SD card. But when I press "install" - "external_sd" - "RICDefeat.zip" in the twrp Recovery it fails and an error comes: "Error executing updater binary in zip '/external_sd/RICDefeat.zip'".
How can I progress? Why do I have to install RICDefeat?
Without RICDefeat you are not able to mount the system partition writeable, so you have no real root. The error is odd though. Have you tried downloading the RICDefeat.zip again, maybe it was corrupted too (like the TWRP img)
lowtraxx said:
Without RICDefeat you are not able to mount the system partition writeable, so you have no real root. The error is odd though. Have you tried downloading the RICDefeat.zip again, maybe it was corrupted too (like the TWRP img)
Click to expand...
Click to collapse
Yes, I have tried downloading it again by clicking "View Raw". I have copied both to the SDcard, but both fails with same error.
Trying to use ADB Sideload and writing "adb devices" in Windows CMD from the folder C:\Users\USERNAME\AppData\Local\Android\sdk\platfo rm-tools just returns an empty list, and installing from SD fails with "Error executing updater binary in zip '/external_sd/RICDefeat.zip'".
Is it possible to go back some steps and try again - without bricking the device? E.g. to step 26? Is there an other place to down the advanced stock kernel?
centric dk said:
Yes, I have tried downloading it again by clicking "View Raw". I have copied both to the SDcard, but both fails with same error.
Trying to use ADB Sideload and writing "adb devices" in Windows CMD from the folder C:\Users\USERNAME\AppData\Local\Android\sdk\platfo rm-tools just returns an empty list, and installing from SD fails with "Error executing updater binary in zip '/external_sd/RICDefeat.zip'".
Is it possible to go back some steps and try again - without bricking the device? E.g. to step 26? Is there an other place to down the advanced stock kernel?
Click to expand...
Click to collapse
It worked! I now have an rooted Z3 tablet compact with stock rom and locked bootloader. :good:
I solved it by tring to go back to step 26 and try one more time (with the same files,and same method). This time I did get the same errors about LED in twrp, but everything worked just like it was suppose to and explained in this guide. The RICDefeat flash just took 5 seconds.
Thank you for helping me!
Last questions:
Will I be able to receive Other OTA updates, e.g. for Lollipop when Sony is ready?
Can I always go back to step 35 if I want a clean/new installation, or do I have to unlock the bootloader first, going back to step 24?
centric dk said:
It worked! I now have an rooted Z3 tablet compact with stock rom and locked bootloader. :good:
I solved it by tring to go back to step 26 and try one more time (with the same files,and same method). This time I did get the same errors about LED in twrp, but everything worked just like it was suppose to and explained in this guide. The RICDefeat flash just took 5 seconds.
Thank you for helping me!
Last questions:
Will I be able to receive Other OTA updates, e.g. for Lollipop when Sony is ready?
Can I always go back to step 35 if I want a clean/new installation, or do I have to unlock the bootloader first, going back to step 24?
Click to expand...
Click to collapse
Hi,
you will most likely be notified about OTA updates, but you should not take them, because they will not apply properly and most likely remove root again. Just wait for recovery flashable updates or build your own flashable update once the ftfs for the lollipop versions get available. If you want a clean installation without unlocking the bootloader again, just build a flashable zip of a clean ftf and flash that. If you want to send it in for repairs and the like, you can always flash a clean ftf with flashtool, but if you want to root it afterwards you need to unlock the bootloader again.
centric dk said:
It worked! I now have an rooted Z3 tablet compact with stock rom and locked bootloader. :good:
I solved it by tring to go back to step 26 and try one more time (with the same files,and same method). This time I did get the same errors about LED in twrp, but everything worked just like it was suppose to and explained in this guide. The RICDefeat flash just took 5 seconds.
Thank you for helping me!
Last questions:
Will I be able to receive Other OTA updates, e.g. for Lollipop when Sony is ready?
Can I always go back to step 35 if I want a clean/new installation, or do I have to unlock the bootloader first, going back to step 24?
Click to expand...
Click to collapse
I'm currently trying to flash RICDefeat from recovery and am getting the exact same error you reported. Do you know what exactly changed that allowed you to flash it successfully? Did you use the RAW version? Where did you put it, internal memory or SD?
Thanks!
Amplifiction said:
I'm currently trying to flash RICDefeat from recovery and am getting the exact same error you reported. Do you know what exactly changed that allowed you to flash it successfully? Did you use the RAW version? Where did you put it, internal memory or SD?
Thanks!
Click to expand...
Click to collapse
I did not change anything. The second time just went a lot faster as I had tried it before. I put RICdefeat on the SD card.
I also have a Z3 Compact (phone). That it a lot simpler to root and RICdefeat is not needed in that guide. Maybe you can get inspiration there?
centric dk said:
I did not change anything. The second time just went a lot faster as I had tried it before. I put RICdefeat on the SD card.
I also have a Z3 Compact (phone). That it a lot simpler to root and RICdefeat is not needed in that guide. Maybe you can get inspiration there?
Click to expand...
Click to collapse
I actually have been following a guide in the Z3C forums but ended up with partial root. RICD should be able to solve it, but gave me an arror. When I read you've been having similar problems, I thought I'd give it a go. Thanks anyway.
Amplifiction said:
I actually have been following a guide in the Z3C forums but ended up with partial root. RICD should be able to solve it, but gave me an arror. When I read you've been having similar problems, I thought I'd give it a go. Thanks anyway.
Click to expand...
Click to collapse
I followed this guide for Z3C (phone): http://forum.xda-developers.com/showpost.php?p=59627168&postcount=120
centric dk said:
I followed this guide for Z3C (phone): http://forum.xda-developers.com/showpost.php?p=59627168&postcount=120
Click to expand...
Click to collapse
Try this one;
http://forum.xda-developers.com/z3-...to-rooted-lollipop-locked-bootloader-t3083980
All works fine.
Hey,
today I got my Xperia X3CT and I followed this Guide to Root my Tablet: http://forum.xda-developers.com/z3-t...gp621-t3013534
(I rooted my LG G2 so I thought I should be able to Root my Tablet without any problems )
At Point 6 I started my Tablet, but somehow it is Stuck in a Bootloop. I am sure I did everything the way the Guide told me to, but somehow my Tablet is still in a Bootloop. How do I get out of it? I can turn the Device of by pressing the Power Button und the Volume Up Button.
Can someone please help?
EDIT: Got out of the Bootloop by flashing back to SGP621_23.0.1.A.0.167_CE.ftf. That was quite a shocker
I think the Problem was that I was at 23.1.A.0.690. Now that I am at 23.0.1.A.0.167 it should make any problems? Or could there be another Problem? Would be thankful for help
Emildeon said:
I think the Problem was that I was at 23.1.A.0.690.
Click to expand...
Click to collapse
That was the problem , you must follow the manual from kitkat (23.0.1.A.0.167) . I advise to use http://forum.xda-developers.com/z3-...to-rooted-lollipop-locked-bootloader-t3083980 ( No need to open the bootloader ). I made a guide in Spanish
[ROOT][UNLOCKED] Wiko Ride - bootloader unlocked, mtk-su'able, & $35 at wally world
Just found this phone on the list of mtk-su'able devices and grabbed one, and to my surprise the bootloader is unlocked as well. Comes with Pie. I haven't been able to build a TWRP that runs on it, but I just dd'ed the boot partition and patched it offline with Magisk and dd'ed it back. It's only a 2GB/16GB phone but worth the price to have a real rooted phone again vs having to deal with temproots.
rlrevell said:
Just found this phone on the list of mtk-su'able devices and grabbed one, and to my surprise the bootloader is unlocked as well. Comes with Pie. I haven't been able to build a TWRP that runs on it, but I just dd'ed the boot partition and patched it offline with Magisk and dd'ed it back. It's only a 2GB/16GB phone but worth the price to have a real rooted phone again vs having to deal with temproots.
Click to expand...
Click to collapse
I was just thinking about picking one of these up today! They have them in stock at a local walmart. I found an article on getandroidtips that links to a GSI ROM.
Do you think the GSI ROM will actually work on the Wiko Ride without TWRP? Do you just flash the zip using the stock recovery?
columbustalley said:
I was just thinking about picking one of these up today! They have them in stock at a local walmart. I found an article on getandroidtips that links to a GSI ROM.
Do you think the GSI ROM will actually work on the Wiko Ride without TWRP? Do you just flash the zip using the stock recovery?
Click to expand...
Click to collapse
Yeah, I've since given the phone away but IIRC you don't even need the mtk-su, you just unlock the bootloader and flash whatever you want. I flashed with fastboot, not having a working TWRP. @tecknight managed to build a TWRP that almost worked before I kinda lost interest. You do have to sign the images using the AVB process, but IIRC it doesn't care who signed them, just that they're signed. I can look through my notes for more details. You'll definitely learn a lot about how AVB works if nothing else, and the phone seems very hard to accidentally brick.
I *think* I have dd dumps of every partition from before I changed anything saved somewhere.
rlrevell said:
Yeah, I've since given the phone away but IIRC you don't even need the mtk-su, you just unlock the bootloader and flash whatever you want. I flashed with fastboot, not having a working TWRP. @tecknight managed to build a TWRP that almost worked before I kinda lost interest. You do have to sign the images using the AVB process, but IIRC it doesn't care who signed them, just that they're signed. I can look through my notes for more details. You'll definitely learn a lot about how AVB works if nothing else, and the phone seems very hard to accidentally brick.
I *think* I have dd dumps of every partition from before I changed anything saved somewhere.
Click to expand...
Click to collapse
That's great! So I just grab the zip for the GSI ROM... sign it with AVB... then I can flash it with fastboot? I think I'll pick one up tomorrow and give it a go. I'll backup all my partitions before I do anything. If I get stuck I'll let you know thanks for the great info!
I got it working! Got root using the mtk-su then backed up all the partitions using a script on github. Enabled bootloader unlock in settings then from PC did fastboot flashing unlock. Flashed the vbmeta.img using fastboot to disable AVB checks. Wiped system then flashed the arm64 Android 10 GSI a/b ROM to system using fastboot. Everything working as expected so far!
{
"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"
}
back up all partitions with script on github
columbustalley said:
I got it working! Got root using the mtk-su then backed up all the partitions using a script on github.
Click to expand...
Click to collapse
which github script is that ? I am trying to do the same thing ! :highfive:
s4goa said:
which github script is that ? I am trying to do the same thing ! :highfive:
Click to expand...
Click to collapse
I used the project called dump-android-partitions. It worked in Cygwin on Windows 10 for me. It requires root on your device as well.
partn BAK sh script
columbustalley said:
It requires root on your device as well.
Click to expand...
Click to collapse
https://codeload.github.com/for2ando/dump-android-partitions/zip/master
looks like a good option for
adb shell
columbustalley said:
I got it working! Got root using the mtk-su then backed up all the partitions using a script on github. Enabled bootloader unlock in settings then from PC did fastboot flashing unlock. Flashed the vbmeta.img using fastboot to disable AVB checks. Wiped system then flashed the arm64 Android 10 GSI a/b ROM to system using fastboot. Everything working as expected so far!
Click to expand...
Click to collapse
So I also got lineage 17.1 up and running pretty well. Did you have any luck getting open gapps installed? No amount of searching produced a twrp for Wiko ride and I even started down the rabbit hole of maybe making my own twrp device tree and compiling from source but then I noticed the android 10 branch of twrp is still wip so that sounds like a bad idea. Maybe manual install through adb and temp root?
aroganone said:
So I also got lineage 17.1 up and running pretty well. Did you have any luck getting open gapps installed? No amount of searching produced a twrp for Wiko ride and I even started down the rabbit hole of maybe making my own twrp device tree and compiling from source but then I noticed the android 10 branch of twrp is still wip so that sounds like a bad idea. Maybe manual install through adb and temp root?
Click to expand...
Click to collapse
I actually use this phone without any google play services. I use F-Droid and Aurora for managing apps. Sorry about that mate!
There might be an easy solution though. If you use a GSI ROM that comes with gapps pre-installed everything should work fine in theory right?
Search google for this image and give it a try. It's the gapps version of the ROM that I currently use.
Havoc-OS-v3.7-20200709-Official-GApps-a64-ab.img.xz
This is absolutely incredible! Normally Pie Bootloader's are locked (as well as Android 8+). To see this is absolutely amazing! If anyone needs custom tools made I can provide a link as well as the source code to build the tools
TheExploitedOne said:
This is absolutely incredible! Normally Pie Bootloader's are licked (as well as Android 8+). To see this is absolutely amazing! If anyone needs custom tools made I can provide a link as well as the source code to build the tools
Click to expand...
Click to collapse
It is pretty great to see an "unlicked" ; ) bootloader on such a cheap device. Unfortunately they are now out of stock in all of the stores in my area and I don't see it listed on the Walmart website anymore. Hopefully they ship another batch!
Thanks for all the info. I’ll definitely check out havoc. I’m completely new to android and the custom rom scene so this has been a great learning experience. So far it’s a fantastic little retroarch emulation device for the money.
aroganone said:
Thanks for all the info. I’ll definitely check out havoc. I’m completely new to android and the custom rom scene so this has been a great learning experience. So far it’s a fantastic little retroarch emulation device for the money.
Click to expand...
Click to collapse
You'll absolutely love the journey too I started at a young age (14 and I'm 22 now) in the hacking scene. It's been absolutely incredible with what I've learned about Android as well as getting to build a custom rim from the sources with my own modifications
---------- Post added at 08:32 PM ---------- Previous post was at 08:32 PM ----------
columbustalley said:
It is pretty great to see an "unlicked" ; ) bootloader on such a cheap device. Unfortunately they are now out of stock in all of the stores in my area and I don't see it listed on the Walmart website anymore. Hopefully they ship another batch!
Click to expand...
Click to collapse
I meant locked lol
Try checking out Amazon they usually have them
columbustalley said:
I actually use this phone without any google play services. I use F-Droid and Aurora for managing apps. Sorry about that mate!
There might be an easy solution though. If you use a GSI ROM that comes with gapps pre-installed everything should work fine in theory right?
Search google for this image and give it a try. It's the gapps version of the ROM that I currently use.
Havoc-OS-v3.7-20200709-Official-GApps-a64-ab.img.xz
Click to expand...
Click to collapse
So I ended up trying (arm64 boots, a64 doesn't):
Havoc-OS-v3.7-20200709-Official-GApps-arm64-ab.img.xz
I get all the way to the every end of setting up all the google account and setting and it hangs on: All Set. "Swipe up to get started". Eventually it just goes to sleep.
Rebooting it loads for a while and then hangs on the havoc logo. Any ideas or any other images with gapps cooked in that I can try? I've wiped data and cache.
Some screen shots:
aroganone said:
So I ended up trying (arm64 boots, a64 doesn't):
Havoc-OS-v3.7-20200709-Official-GApps-arm64-ab.img.xz
I get all the way to the every end of setting up all the google account and setting and it hangs on: All Set. "Swipe up to get started". Eventually it just goes to sleep.
Rebooting it loads for a while and then hangs on the havoc logo. Any ideas or any other images with gapps cooked in that I can try? I've wiped data and cache.
Some screen shots:
Click to expand...
Click to collapse
I've actually had a similar issue but I assumed it was because of some mistake I made during the process. I got a second Wiko Ride on Ebay and ran through the steps again and discovered that you need to do a full wipe with the SP Flash Tool. Be very careful though because you could lose your MEID and MAC. Make sure to back up all partitions before using the "Format all + download" function. After I did the full format with SP Flash Tool I restored the nvram and nvdata partitions from my backup. You need to edit an XML to accomplish this there are guides on Youtube. Here are some other notes that I made during the process mind you it's not comprehensive as it doesn't even have the SP Flash Tools steps but it may help you.
Unlock bootloader in developer options
Boot into fastboot
#fastboot flashing unlock
Install mtk-easy-su and magisk
#adb install mtk-easy-su.apk
#adb install magisk.apk
Set magisk to "auto"
Backup nvram and nvdata partitions using cygwin and dump-android-partitions.sh
#./dump-android-partitions.sh -s SERIALNUMBER nvram
#./dump-android-partitions.sh -s SERIALNUMBER nvdata
Unlock SIM using Miracle Thunder
Boot into fastboot
#fastboot --disable-verification flash vbmeta vbmeta.img
#fastboot erase system
#fastboot flash system .\Havoc-OS-v3.7-20200709-Official-arm64-ab.img
#fastboot -w
#fastboot reboot
0
columbustalley said:
I've actually had a similar issue but I assumed it was because of some mistake I made during the process. I got a second Wiko Ride on Ebay and ran through the steps again and discovered that you need to do a full wipe with the SP Flash Tool. Be very careful though because you could lose your MEID and MAC. Make sure to back up all partitions before using the "Format all + download" function. After I did the full format with SP Flash Tool I restored the nvram and nvdata partitions from my backup. You need to edit an XML to accomplish this there are guides on Youtube. Here are some other notes that I made during the process mind you it's not comprehensive as it doesn't even have the SP Flash Tools steps but it may help you.
Unlock bootloader in developer options
Boot into fastboot
#fastboot flashing unlock
Install mtk-easy-su and magisk
#adb install mtk-easy-su.apk
#adb install magisk.apk
Set magisk to "auto"
Backup nvram and nvdata partitions using cygwin and dump-android-partitions.sh
#./dump-android-partitions.sh -s SERIALNUMBER nvram
#./dump-android-partitions.sh -s SERIALNUMBER nvdata
Unlock SIM using Miracle Thunder
Boot into fastboot
#fastboot --disable-verification flash vbmeta vbmeta.img
#fastboot erase system
#fastboot flash system .\Havoc-OS-v3.7-20200709-Official-arm64-ab.img
#fastboot -w
#fastboot reboot
Click to expand...
Click to collapse
So I need a nudge in the right direction. Where do I get/extract/create the scatter file? I've backed up every partition manually but I'm a bit stuck on the part where you need to load the scatter file for SP Flash Tool.
aroganone said:
So I need a nudge in the right direction. Where do I get/extract/create the scatter file? I've backed up every partition manually but I'm a bit stuck on the part where you need to load the scatter file for SP Flash Tool.
Click to expand...
Click to collapse
If you've got the MT65xx use MTK Droid Tools
TheExploitedOne said:
If you've got the MT65xx use MTK Droid Tools
Click to expand...
Click to collapse
tried it but MTK Droid Tools apparently doesn't support newer chips. It pulled the following data but didn't generate the block data.
Hardware : MT6761V/CAB
Model : W-U300
Build number : treble_arm64_bvN-userdebug 10 QQ3A.200705.002 eng.crossg.20200713.132209 test-keys
Build date UTC : 20200713-132131
Android v : 10
Baseband v: MOLY.LR12A.R3.MP.V31.3.P39
Kernel v : 4.9.117+ ([email protected]) (Android (4691093 based on r316199) clang version 6.0.2 (https://android.googlesource.com/toolchain/clang 183abd29fc496f55536e7d904e0abae47888fc7f) (https://android.googlesource.com/toolchain/llvm 34361f192e41ed6e4e8f9aca80a4ea7e9856f327) (based on LLVM 6.0.2svn)) #2 SMP Fri Nov 1 14:21:38 CST 2019
I found stock firmware with the scatter file here but not sure how much I trust it:
https://romprovider.com/wiko-u300-firmware/
I also was looking at a newer tool : Wwr MTK
but haven't tried it yet.
I know it's an old phone. The LG G5. But I bought it because my Galaxy died, the G5 was cheap, you can run Lineage OS on it! But wait! No you can't! You'll never make it past loading the custom recovery file. The guide on Lineage's website is worthless, as it's from before 8.0 Oreo. LG patched the that hole closed tighter than a... a.. <insert good simile here>. I have tried every way in the world to get into this phone. I've looked at every thread here. Dirtycow doesn't work. You can't revert back to 7.x Nougat anymore. It can't be done. LG won't let you in.
I have dreamed of escaping google's clutches. It's really important to me. But I can't afford to buy some $250+ dollar phone that may or may not have a working exploit right now.
This time I gambled and lost, so I'm asking for help. Does anyone know of any way I might salvage the situation? I'd be open to buying a phone with Lineage already on it, if it were reasonably priced. I'd also be open to paying someone else to install it on this LG G5, but I have serious doubts you'd be able to. Any help or advice to get Lineage would be greatly appreciated!
bennylava said:
I know it's an old phone. The LG G5. But I bought it because my Galaxy died, the G5 was cheap, you can run Lineage OS on it! But wait! No you can't! You'll never make it past loading the custom recovery file. The guide on Lineage's website is worthless, as it's from before 8.0 Oreo. LG patched the that hole closed tighter than a... a.. <insert good simile here>. I have tried every way in the world to get into this phone. I've looked at every thread here. Dirtycow doesn't work. You can't revert back to 7.x Nougat anymore. It can't be done. LG won't let you in.
I have dreamed of escaping google's clutches. It's really important to me. But I can't afford to buy some $250+ dollar phone that may or may not have a working exploit right now.
This time I gambled and lost, so I'm asking for help. Does anyone know of any way I might salvage the situation? I'd be open to buying a phone with Lineage already on it, if it were reasonably priced. I'd also be open to paying someone else to install it on this LG G5, but I have serious doubts you'd be able to. Any help or advice to get Lineage would be greatly appreciated!
Click to expand...
Click to collapse
Hey, easy man. There's some things you should consider before giving up on a phone. The quick search i did on Google let me know that this device can be bootloader unlocked, and rooted. At this point, I may ask: Is your device linked in someway with Verizon? Did you unlocked its bootloader? did you manage to install TWRP with no issues? Maybe you´re lucky enough to find a way out yourself. I'll try to help you in everything i can.
eduardvi995 said:
Hey, easy man. There's some things you should consider before giving up on a phone. The quick search i did on Google let me know that this device can be bootloader unlocked, and rooted. At this point, I may ask: Is your device linked in someway with Verizon? Did you unlocked its bootloader? did you manage to install TWRP with no issues? Maybe you´re lucky enough to find a way out yourself. I'll try to help you in everything i can.
Click to expand...
Click to collapse
Thanks! I could really use the help. I have unlocked the bootloader. Made it that far. But I haven't been able to root it because all the root exploits seem to have been patched out by the time I got the phone. It's running Android 8.0. It is a U.S Tmobile phone.
Here's where my progress ground to a halt: I can't get that LG program, LGup, to flash 7.0 to the phone. It gives me an error saying "Error - Invalid KDZ file". Well that's odd, I got that KDZ file from LG's official website. They have a section where they keep all the old stock ROMs.
Maybe I'm wrong here, but I think this part is absolutely necessary. You must install 7.0 Nougat in order to roll back the changes LG made when they patched up the recovery mode. Otherwise you can't install a custom recovery file, which is vital. No custom recovery file = no Lineage. Looking forward to your reply !
bennylava said:
Thanks! I could really use the help. I have unlocked the bootloader. Made it that far. But I haven't been able to root it because all the root exploits seem to have been patched out by the time I got the phone. It's running Android 8.0. It is a U.S Tmobile phone.
Here's where my progress ground to a halt: I can't that LG program, LGup, to flash 7.0 to the phone. It give me an error saying "Error - Invalid KDZ file". Well that's odd, I got that KDZ file from LG's official website. They have a section where they keep all the old stock ROMs.
Maybe I'm wrong here, but I think this part is absolutely necessary. You must install 7.0 Nougat in order to roll back the changes LG made when they patched up the recovery mode. Otherwise you can't install a custom recovery file, which is vital. No custom recovery file = no Lineage. Looking forward to your reply !
Click to expand...
Click to collapse
Here is what i found out. Considering your device is LG G5 H830, with android 8.0, it seems you cant install TWRP straight on. However, there is still something you can try. At this point I may ask: can you enter Fastboot Mode? this your only hope to actually root the phone, and then flash TWRP.
Check if you actually can enter fastboot. If you can, then try to send some basic commands like "fastboot devices" "fastboot reboot". I say this because some devices have Fastboot mode disabled on oem, rendering on useless fastboot. Hope this is not your case. Also, post here your exactly fingerprint version (your rom version). It has to be exactly the same one, otherwise it might soft-brick your phone. Maybe you can flash a patched boot image of your actual rom to then flash twrp.
eduardvi995 said:
Here is what i found out. Considering your device is LG G5 H830, with android 8.0, it seems you cant install TWRP straight on. However, there is still something you can try. At this point I may ask: can you enter Fastboot Mode? this your only hope to actually root the phone, and then flash TWRP.
Check if you actually can enter fastboot. If you can, then try to send some basic commands like "fastboot devices" "fastboot reboot". I say this because some devices have Fastboot mode disabled on oem, rendering on useless fastboot. Hope this is not your case. Also, post here your exactly fingerprint version (your rom version). It has to be exactly the same one, otherwise it might soft-brick your phone. Maybe you can flash a patched boot image of your actual rom to then flash twrp.
Click to expand...
Click to collapse
I can indeed send "fastboot devices" and "fastboot reboot", and it does work. The device will be listed in the command window on the computer, and the phone will reboot if you enter the command "Fastboot reboot".
As for the fingerprint version, here's what I was able to accomplish via a terminal in Manjaro Linux. Is this the full fingerprint?
[[email protected] ~]$ adb devices
List of devices attached
LGH8305d6bec71 device
[[email protected] ~]$ adb shell getprop ro.build.fingerprint
lge/h1_tmo_us/h1:8.0.0/OPR1.170623.032/182251913485f:user/release-keys
[[email protected] ~]$
bennylava said:
I can indeed send "fastboot devices" and "fastboot reboot", and it does work. The device will be listed in the command window on the computer, and the phone will reboot if you enter the command "Fastboot reboot".
As for the fingerprint version, here's what I was able to accomplish via a terminal in Manjaro Linux. Is this the full fingerprint?
[[email protected] ~]$ adb devices
List of devices attached
LGH8305d6bec71 device
[[email protected] ~]$ adb shell getprop ro.build.fingerprint
lge/h1_tmo_us/h1:8.0.0/OPR1.170623.032/182251913485f:user/release-keys
[[email protected] ~]$
Click to expand...
Click to collapse
Its seems you were lucky enough. I checked your rom build and compared it with the only rom on your phone that can be rolled back. It totally matchs the anti-rollback v01 firmware 8.0, so you still can roll-back to Nougat if you try the firmware version H83020c, wich you can download over here:
Fastboot-Flashable rom:
Codefire - Listing of H83020c
KDZ Format rom:
http://dl02.gdms.lge.com:5006/dn/downloader.dev?fileKey=FWAAZHZF92MNARE76685PNJ/H83020o_00_0205.kdz
Its seems the first one it's Fastboot-Flashable, so you should know what to do next if the KDZ Rom doesn't work. However, check this website and compare the rom build yourself, just to be clear about it:
Download T-mobile LG G5 H830 Stock kdz firmware H83030C
Download T-mobile LG G5 H830 Stock kdz firmware H83030C -
www.mylgphones.com
The first link has 3 flashable roms there. including KDZ and fastboot format. Make sure to try them all if one doesnt work
If both methods are useless to roll back to Nougat, dont hesitate to tell me. There's still a workaround available.
To be clear, the phone needs to be in "Firmware update" mode in order to use flashboot to flash that Fastboot rom, correct? That's where a "Firmware update" message appears on the screen, and it's encircled by two arrows. It's in the middle of the screen, and it's not small like when you're using fastboot.
I ask because iirc, KDZ files require the use of LGup, that LG official program.
bennylava said:
To be clear, the phone needs to be in "Firmware update" mode in order to use flashboot to flash that Fastboot rom, correct? That's where a "Firmware update" message appears on the screen, and it's encircled by two arrows. It's in the middle of the screen, and it's not small like when you're using fastboot.
I ask because iirc, KDZ files require the use of LGup, that LG official program.
Click to expand...
Click to collapse
It needs to be in firmware update mode only if you are flashing a kdz rom through Lg official flashtool. If you are going to flash through fastboot, you have to make sure your PC recognizes your device sending "fastboot devices". The fastboot flashable room is right in the first link (.zip file, 1,6 GB size file)
The one I'm seeing says it's 1.9 Gigabytes in size. It's #15 on that list, and it's called:
LG-H83020c-Flashable.COMPLETE-ARB01.zip
Correct?
Just wanna be clear on this, the last thing we need is a brick lol
bennylava said:
The one I'm seeing says it's 1.9 Gigabytes in size. It's #15 on that list, and it's called:
LG-H83020c-Flashable.COMPLETE-ARB01.zip
Correct?
Just wanna be clear on this, the last thing we need is a brick lol
Click to expand...
Click to collapse
That should be it. Download it and check it has all partitions (boot, system, recovery, etc...)
You are probably gonna have to flash each partition manually (for example, if you are flashing system, you should write "fastboot flash system system.img" and so on)
Below is a pic of everything that came in that zip file, just to make sure we're on the same page and I've got everything necessary.
I must admit that I'm a little intimidated by flashing each individual component in that zip file. I understand that you can just tell it "Flash this thing!" and it will do it. But how does it know where exactly to flash the new thing? How does it know not to just write it over the previous item you just flashed?
Next question: What all needs to be flashed individually? As you can see, there are a total of 28 entries shown in the pic. But the folders "bootloader" and "META.INF" both contain a lot of stuff. Do you just flash bootloader and META.INF, and it already knows to flash everything the folder contains?
{
"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"
}
bennylava said:
Below is a pic of everything that came in that zip file, just to make sure we're on the same page and I've got everything necessary.
I must admit that I'm a little intimidated by flashing each individual component in that zip file. I understand that you can just tell it "Flash this thing!" and it will do it. But how does it know where exactly to flash the new thing? How does it know not to just write it over the previous item you just flashed?
Next question: What all needs to be flashed individually? As you can see, there are a total of 28 entries shown in the pic. But the folders "bootloader" and "META.INF" both contain a lot of stuff. Do you just flash bootloader and META.INF, and it already knows to flash everything the folder contains?
Click to expand...
Click to collapse
You don't have to write "fastboot flash" 28 times. You can just write "fastboot flash all". But I'd rather flashing manually.
Ignore the META-INF folder. You can't flash any file inside there. You should only flash every file ending in "xx. Img* such as boot.img or. system.img.
This zip contains that folder because it was meant to be flashed through recovery, but if you try to do that, the recovery will not do it, or it will cancel installation, as there is a line that checks your actual fingerprint to avoid Rolling back.
So the command to flash that whole bootloader file at once is "flashboot flash all bootloader"? And it won't care that it's a folder, and not a .img file?
I see what you mean about flashing the .img files that are below the "bootloader" folder in that pic I posted. To me it makes sense that it would flash those. But as you said, you should only flash every file ending in .img and "bootloader" is actually a folder, even if it is full of those files. So I just want to be clear on how exactly to flash that bootloader file.
Sorry about all the newb questions lol. Once I see your reply here, I'm going to attempt the flash. After that, hopefully I won't need any more help.
bennylava said:
So the command to flash that whole bootloader file at once is "flashboot flash all bootloader"? And it won't care that it's a folder, and not a .img file?
I see what you mean about flashing the .img files that are below the "bootloader" folder in that pic I posted. To me it makes sense that it would flash those. But as you said, you should only flash every file ending in .img and "bootloader" is actually a folder, even if it is full of those files. So I just want to be clear on how exactly to flash that bootloader file.
Sorry about all the newb questions lol. Once I see your reply here, I'm going to attempt the flash. After that, hopefully I won't need any more help.
Click to expand...
Click to collapse
Let's try something a little bit easier first. As you say you unlocked bootloader, maybe you can flash the full rom through recovery. Copy the rom to a sdcard and try that first, maybe you will save yourself a lot of headaches doing this first.
I've bought two H830's and got both to TWRP/LOS ROM no problem. Regardless of your current official build on your phone, you can rollback to version 30c and dirtycow from there to get TWRP. You can get necessary tools/info from here.
0. (If you havn't already...) Enable OEM unlock in settings and unlock bootloader/fastboot
1. Use LGUP tool to clean flash an official 30c version (H83030c_00_0813.kdz) build to your LG H830
2. Dirtycow exploit to get TWRP
3. Use TWRP to install
Let me know how it shakes out
Also an important note, you CANNOT flash directly the recovery via fastboot to get TWRP, only the H850 can do that, NOT the H830. That's something important no one ever brings up. You must use the dirtycow exploit.
EDIT: Oh yeah, and I recommend using UPPERCUT to flash the kdz file since LGUP is such broken trash.
eduardvi995 said:
Let's try something a little bit easier first. As you say you unlocked bootloader, maybe you can flash the full rom through recovery. Copy the rom to a sdcard and try that first, maybe you will save yourself a lot of headaches doing this first.
Click to expand...
Click to collapse
So just put the zip file on my external SD card, and then tell flashboot to...? Or somehow use only the phone itself to flash the rom? Sorry I'm afraid I'm having trouble following along as I've never done this before.
But as per your instructions, the rom (the whole zip file) is now on the external storage SD Card.
Or did you mean to extract the zip file to a folder, and put that on the SD card? My next question would be thus:
What is the exact command to begin flashing, once I have everything in it's proper place? I did a little experiment where I tried to flash one of the files individually. The Linux terminal gave me the following error:
[[email protected] Desktop]$ cd bootloader
[[email protected] bootloader]$ fastboot flash aboot.img
unknown partition 'aboot.img'
fastboot: error: cannot determine image filename for 'aboot.img'
[[email protected] bootloader]$
As you can see, the bootloader folder is on the desktop, with many .img files inside it. Just as the pic in post #11 shows. Inside the bootloader folder is a .img file called "aboot.img". And for some reason fastboot "cannot determine the image filename for aboot.img"
DrowningInFreedom said:
EDIT: Oh yeah, and I recommend using UPPERCUT to flash the kdz file since LGUP is such broken trash.
Click to expand...
Click to collapse
Thank you for the reply! I've got two questions for you:
1. Do you have a link to the version of LG UP that you'd recommend using? It seems that there are many links out there in the wild, and some of them are to old versions. I'm not sure exactly which one I should use.
2. How exactly do you use Uppercut with LG Up? I got Uppercut, but it didn't seem to do anything when I double clicked on it. It just sat there. Is it like some kind of addon or modification to LG up? Or is it supposed to open as it's own program. Thanks!
Use the files provided by codefire , Launch UPPERCUT which will then hook into and launch LGUP automatically (All it does is make LGUP work without errors)
DrowningInFreedom said:
Use the files provided by codefire , Launch UPPERCUT which will then hook into and launch LGUP automatically (All it does is make LGUP work without errors)
Click to expand...
Click to collapse
Here's what happened when I tried to flash the right 80320a file (Nougat):
Any idea why it would say that?
I unfortunately decided to upgrade my Moto G Power 2020 to Android 11 when the update was available and have had many issues most of which is that it is now very slow and battery drain is much higher. Have tried the many suggestions online to help, but none have worked. I found that Android 10 was good and stable. My question is, how can I downgrade my Moto G Power back to Android 10 easily? Can it be done with Moto's Rescue and Smart Assistant? This rescue utility seems to only want to keep the device on Android 11. Please provide step by step instructions how to do this. Thanks.
Gordster said:
I unfortunately decided to upgrade my Moto G Power 2020 to Android 11 when the update was available and have had many issues most of which is that it is now very slow and battery drain is much higher. Have tried the many suggestions online to help, but none have worked. I found that Android 10 was good and stable. My question is, how can I downgrade my Moto G Power back to Android 10 easily? Can it be done with Moto's Rescue and Smart Assistant? This rescue utility seems to only want to keep the device on Android 11. Please provide step by step instructions how to do this. Thanks.
Click to expand...
Click to collapse
Downgrading the android version with Moto firmware is always a risk.
If you downgrade you need to disable updates, OTA updates could brick the device.
First Unlock the bootloader
[Guide]Un/locking Motorola Bootloader
UnLocking and ReLocking Motorola Bootloader https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a Moto Bootloader Unlocking site Re-Locking see Post #4 More about bootloader UnLocking Post #2 Can my...
forum.xda-developers.com
Once the bootloader is unlocked, find your
Software Channel, it will be like, Retail, RetUS, Verizon, MetroPCS...
You can find your firmware here
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
download. and Unzip it
Check if your device uses fastbootd
Flash option 1
Find the flashfile.xml in the firmware folder
and use the online flashfile converter to get the flash commands
add the fastboot reboot fastboot commands if you have a fasbootd device.
Flash Option 2
Install LMSA
use the rescue option to download the current firmware for your device
move the LMSA firmware to a different folder
rename the Android 10 firmware folder to the same name as LMSA firmware.
Move that folder to the LMSA download folder
Use the rescue option to flash renamed firmware.
There is no guarantee that either method will work, but it should.
On the phone
Toggle off "install updates" option in Dev Options
sd_shadow said:
Downgrading the android version with Moto firmware is always a risk.
If you downgrade you need to disable updates, OTA updates could brick the device.
First Unlock the bootloader
[Guide]Un/locking Motorola Bootloader
UnLocking and ReLocking Motorola Bootloader https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a Moto Bootloader Unlocking site Re-Locking see Post #4 More about bootloader UnLocking Post #2 Can my...
forum.xda-developers.com
Once the bootloader is unlocked, find your
Software Channel, it will be like, Retail, RetUS, Verizon, MetroPCS...
You can find your firmware here
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
download. and Unzip it
Check if your device uses fastbootd
Flash option 1
Find the flashfile.xml in the firmware folder
and use the online flashfile converter to get the flash commands
add the fastboot reboot fastboot commands if you have a fasbootd device.
Flash Option 2
Install LMSA
use the rescue option to download the current firmware for your device
move the LMSA firmware to a different folder
rename the Android 10 firmware folder to the same name as LMSA firmware.
Move that folder to the LMSA download folder
Use the rescue option to flash renamed firmware.
There is no guarantee that either method will work, but it should.
On the phone
Toggle off "install updates" option in Dev Options
Click to expand...
Click to collapse
Thank you sd_shadow. I appreciate your very detailed response and answer. I will try your methods and hopefully be able to return to Android 10. Android 11 seems to currently have a lot of bugs at least with the Moto G Power phone. Wish I had stayed on Android 10.
sd_shadow said:
Downgrading the android version with Moto firmware is always a risk.
If you downgrade you need to disable updates, OTA updates could brick the device.
First Unlock the bootloader
[Guide]Un/locking Motorola Bootloader
UnLocking and ReLocking Motorola Bootloader https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a Moto Bootloader Unlocking site Re-Locking see Post #4 More about bootloader UnLocking Post #2 Can my...
forum.xda-developers.com
Once the bootloader is unlocked, find your
Software Channel, it will be like, Retail, RetUS, Verizon, MetroPCS...
You can find your firmware here
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
download. and Unzip it
Check if your device uses fastbootd
Flash option 1
Find the flashfile.xml in the firmware folder
and use the online flashfile converter to get the flash commands
add the fastboot reboot fastboot commands if you have a fasbootd device.
Flash Option 2
Install LMSA
use the rescue option to download the current firmware for your device
move the LMSA firmware to a different folder
rename the Android 10 firmware folder to the same name as LMSA firmware.
Move that folder to the LMSA download folder
Use the rescue option to flash renamed firmware.
There is no guarantee that either method will work, but it should.
On the phone
Toggle off "install updates" option in Dev Options
Click to expand...
Click to collapse
Thanks a lot sd_shadow
I tried Flash Option 2 using LMSA. Replaced all the Android 11 ROM files in the default download directory folder with official Android 10 ROM files, and then used the rescue option to flash the Android 10 files to the Moto g Power. Everything worked perfectly. I now have Android 10 back on my phone. I keep getting the notification that there is an Android 11 update available but just have to ignore this. Thanks again for your help.
Gord
HEY im trying to flash stock rom using LMSA manually but a popup says cannot match current firmware ...
Is there somthing i can do to select and flash a downloaded firmware for lolinet?
thanks
darko454 said:
HEY im trying to flash stock rom using LMSA manually but a popup says cannot match current firmware ...
Is there somthing i can do to select and flash a downloaded firmware for lolinet?
thanks
Click to expand...
Click to collapse
Seems that lmsa doesn't work for some software channels, or if the baseband and the channel don't match.
What does getvar all say?
Code:
fastboot getvar all
Curious.
I managed to downgrade, but can't re-lock the bootloader on Android 10 or else it throws this error and will not boot:
{
"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"
}
However, when I reflashed Android 11 and re-locked the bootloader, it boots just fine, without any warnings.
Something, the bootloader itself maybe, must be stuck on 11 and won't let me relock the bootloader when 10 is flashed.
Since I need the bootloader locked so I can pass Playstore security, I guess I'm stuck on Android 11 :\
JackDHopper said:
Curious.
I managed to downgrade, but can't re-lock the bootloader on Android 10 or else it throws this error and will not boot:View attachment 5375851
However, when I reflashed Android 11 and re-locked the bootloader, it boots just fine, without any warnings.
Something, the bootloader itself maybe, must be stuck on 11 and won't let me relock the bootloader when 10 is flashed.
Since I need the bootloader locked so I can pass Playstore security, I guess I'm stuck on Android 11 :\
Click to expand...
Click to collapse
Magisk Hide should be able to hide the bootloader status
Nothing ventured, nothing gained I guess. I was afraid of doing this whole thing because I'm your typical Problem User who tends to make things worse. Might as well go for root now that I've voided my warranty (not that I cared anyway).
Flashed Android 10 and Magisk got me past playstore security. Everything's working as intended now.
I'm quite surprised at how easy it was, since I had read that Google patched MagiskHide at hardware level sometime ago.
THANK YOU VERY MUCH, sd_shadow.
JackDHopper said:
Nothing ventured, nothing gained I guess. I was afraid of doing this whole thing because I'm your typical Problem User who tends to make things worse. Might as well go for root now that I've voided my warranty (not that I cared anyway).
Flashed Android 10 and Magisk got me past playstore security. Everything's working as intended now.
I'm quite surprised at how easy it was, since I had read that Google patched MagiskHide at hardware level sometime ago.
THANK YOU VERY MUCH, sd_shadow.
Click to expand...
Click to collapse
It''s a game of cat and mouse, google introduces new security measures, magisk devs get to working a way around it... There is even a module now that lets you pass full safetynet with xposed and microg.
JackDHopper said:
Nothing ventured, nothing gained I guess. I was afraid of doing this whole thing because I'm your typical Problem User who tends to make things worse. Might as well go for root now that I've voided my warranty (not that I cared anyway).
Flashed Android 10 and Magisk got me past playstore security. Everything's working as intended now.
I'm quite surprised at how easy it was, since I had read that Google patched MagiskHide at hardware level sometime ago.
THANK YOU VERY MUCH, sd_shadow.
Click to expand...
Click to collapse
@JackDHopper. I don't want to brick my Moto G8 Power 2020 running the Havoc 4.8 Android 11 ROM by screwing up a downgrade to Android 10 so I can flash LineageOS 11. So, can you please explain how you did it?
Thanks. Much appreciated.
jhford said:
@JackDHopper. I don't want to brick my Moto G8 Power 2020 running the Havoc 4.8 Android 11 ROM by screwing up a downgrade to Android 10 so I can flash LineageOS 11. So, can you please explain how you did it?
Thanks. Much appreciated.
Click to expand...
Click to collapse
You dont need to downgrade again. You only downgrade if you flashed stock 11 again. Simply format data and flash the new rom from another custom rom.
Beetle84 said:
You dont need to downgrade again. You only downgrade if you flashed stock 11 again. Simply format data and flash the new rom from another custom rom.
Click to expand...
Click to collapse
Beetle84 said:
You dont need to downgrade again. You only downgrade if you flashed stock 11 again. Simply format data and flash the new rom from another custom rom.
Click to expand...
Click to collapse
@Bettle84 thanks for the reply. I'm running TWRP 3.5.0_10-0. I flashed the img files with fastbootd when i initially installed Havoc and when i upgraded to 4.8. So, do you mean that I can flash the LOS ROM in TWRP on top of Havoc without using fastbootd?
Thanks again
jhford said:
@Bettle84 thanks for the reply. I'm running TWRP 3.5.0_10-0. I flashed the img files with fastbootd when i initially installed Havoc and when i upgraded to 4.8. So, do you mean that I can flash the LOS ROM in TWRP on top of Havoc without using fastbootd?
Thanks again
Click to expand...
Click to collapse
Yeah you should be able to
Beetle84 said:
Yeah you should be able to
Click to expand...
Click to collapse
OK. LOS is installed, but I can't find a GAPPS that works. Suggestions?
Thanks
jhford said:
OK. LOS is installed, but I can't find a GAPPS that works. Suggestions?
Thanks
Click to expand...
Click to collapse
No idea, i havent flashed anything on my g8 in a while
does this work with moto g power 2021, android 11 aint working for me either, always get the systen ui has stopped error and certain apps stop working
this is my model number just to make sure
Hi all!! I been trying to downgrade my moto g power 2021 to Android 10 from 11 and I been reading in this thread. At first I tried the second method of flashing that sd_shadow suggested and it seems after 32% a message that says "flash single partian, flash failed" pops up.
Then I tried the first method. I tried making the flashall.bat file and put it in the sdk tools directory as the steps said in the fast boot forum. It didn't work when I double clicked so then I put my supposed firmware zip files (that I got from the lolinet website above) inside the sdk tool directory (unzipped) and Android 10 actually installed. I skipped all the steps after factory reset so I can go into devmode and turn off automatic updates. However when I tried turning on my WiFi, the phone would crash and restart and it would do that everytime it tried to connect to the WiFi. Even after I factory reset my device again the same problem persisted. I managed to use lmsa to go back to 11. What can I do to fix this downgrade issue?
After 1.5 full days of many attempts to downgrade from A11 to A10, fastbootd is the answer! I used Motorola-XML-To-Batch-Script-master with stock firmware from bootloader with nothing but boot loops. went into fastbootd just for the hell of it and ran the bat and boom! back to stock 10!
I go into further details here: https://forum.xda-developers.com/t/how-to-downgrade-android-11-to-10.4283809/post-86614163