Database Info

[XT1644] Stock Marshmallow to latest Nougat NPJ25.93-14

Hello!
If you have been wanting to jump on the Nougat bandwagon, but do not want to flash a soak test or risk getting off the official OTA path: fear no more! I finally caved and decided to try it out... and it worked perfectly on my Moto G4+! I have not experienced battery drain on wifi/4g/bluetooth usage. Performance is smooth and I did not lose any data. Of course we are dealing with computers so YMMV. As usual you are responsible for anything you do to your phone, all I can do is provide information.
First of all this is for those who are still on the stock MM release. So you will want to make sure that you are fully updated, bootloader locked and unrooted. Also I would consider this intermediate level, so if you do not know your way around Windows/Unix/Android, make sure to do your research before continuing. There are plenty of resources on XDA. Second, as always backup all your data, just in case. You should not lose data, but you never know.
Installing the OTAs:
Download image and extract it: https://forum.xda-developers.com/moto-g4-plus/how-to/android-7-0-install-nougat-official-t3531612
Install adb/fastboot drivers: https://forum.xda-developers.com/showthread.php?t=2317790
Put your Moto G4 into fasboot mode by (while off) holding 'power' and 'vol 'down'
Run 'flashall.bat' in Windows or 'flashall.sh' in Unix.
Make sure it connects to phone and it will flash. If it cannot find your phone, go into the device manager and make sure that the Android Device / ABD driver is correctly installed for your device.
You should now have Nougat installed! It may take a few minutes on first boot and be prepared to hear a "Hello Moto!" upon boot.
Once fully booted and cooled down from the update, continue to latest OTA.
Download the OTA file from here onto your phone: https://forum.xda-developers.com/moto-g4-plus/how-to/ota-zip-update-npj25-93-14-t3539407
Boot phone into recovery by (while off) holding 'power' and 'vol 'down' until you see the fastboot screen, then use the volume buttons to scroll and select recovery with the power button.
Once you see the android with the no command, hold 'power' and tap 'vol up' to get the menu. (May take a couple of tries)
Select the option to apply update from sdcard.
Navigate to download folder where the OTA downloaded. Scroll with 'vol up/down' select it using 'power'.
Confirm flash and allow to install and reboot!
Congratulations you are now on the newest Nougat (available for Moto G4) with the December security patch!
A few notes:
I would go into the settings and reset network settings. This means you will have to re-add your WiFi networks but its preventative to make sure that there is no network related battery drain.
If something goes wrong, the way to recover would be to unlock the bootloader and try to manually flash all partitions. If you are worried, make sure to enable OEM unlocking in the developer options to give you this out just in case
For the security minded, remember that the bootloader/recovery uses encryption keys to verify that the system upgrade was signed by Motorola. So the install will not work w/ an unlocked bootloader if the system image has been modified in any way.
All credit for the files to those who provided them on XDA. I just compiled some instructions. Enjoy!

Is there anyway to update the N firmware, i.e radio and modem, without re-locking the boot loader?

Who said anything about relocking bootloader, that's not needed.

I already flashed the base Nougat update from a different tutorial; however, I don't know how to flash the security patch so thank you! I'm good to go! I do have a question, am I going to receive any future OTA since we flashed N manually?

I may try this later so I can flash LineageOS 14.1 since it needs a stock Nougat image first.

GigaHertzzz said:
I already flashed the base Nougat update from a different tutorial; however, I don't know how to flash the security patch so thank you! I'm good to go! I do have a question, am I going to receive any future OTA since we flashed N manually?
Click to expand...
Click to collapse
Provided you don't root or modify your system or recovery, you should still be eligible for official OTA updates. Note also unlocking your bootloader will not stop you from getting/installing OTAs.

Where can I get the Unix script?

Just did this on a UK Moto G (unlocked, retgb) and it worked perfectly. Many thanks.

Would you happen to have saved the stock marshmallow for XT1644? I need it.

Soft bricked my Mate 8 - can't flash anything anymore

Hey guys,
I've backed myself into a corner here a little and I hope you can guide me to get a working phone again.
I was on Ephemeral Mate 8 for a while now and decided it was time to upgrade. The new ROM I wanted to try mentioned I should have at least firmware version B3XX to flash it, so I thought the easiest way to get there would be to flash a stock ROM again and let the system update function do it's work. I updated from NXT-L29C432B180 to B192 to B560 to B581 (no B3XX offered in between) and somehow managed to get the phone rooted again. Yet I noticed some things (like Bluetooth) not working quite properly anymore (for whatever reason) and so wanted to downgrade again.
Tried to restore one of my old backups from Ephemeral Mate 8: it failed. The backup from stock B581 I made before: no idea where it was stored, but I can't find it anymore and may have accidentally deleted it by now. Currently it seems I don't have any OS installed anymore.
I still have an unlocked bootloader and can access it by pressing power + volume down and can flash a custom recovery via Fastboot (the one I'm currently trying with is this one). However, no ROM I try to flash or backup I want to restore will work anymore, they just fail with varying errors like error 7 or invalid zip file. At some point I tried to wipe almost anything I could before every new try to flash anything (probably a very bad idea), because I thought a clean start would somehow resolve some of the various errors TWRP was throwing at me - obviously it hasn't. I also tried installing the same stock ROM like the first time via dload method, but it always says there is an incompatibility with my current version (probably that I don't have one anymore by now) and fails.
Sadly, I can't remember anymore what everything I tried to flash in between to try and get it working again or where I found it, because it simply is too much. But I'm willing to provide any information I'm able to achieve and try any steps you tell me to get it working again. I'd be very grateful for any help on this and already thank you in advance for any advice.

Sooo... in the meantime I followed this guide and got my phone working again. However, I'm facing another problem now:
When I try to flash TWRP I always get this error and can't find out what it means and how to fix it:
Code:
target reported max download size of 471859200 bytes
sending 'recovery' (17280 KB)...
OKAY [ 0.437s]
writing 'recovery'...
FAILED (remote: image verification error)
finished. total time: 0.454s
Maybe it's related to that somehow the Serial Number of my device has changed in the process? It's now just '0123456789ABCDEF'. I read about fixing it with HCU Client tool, but when trying to repair the Serial Number it just gives me this error:
Code:
2017-06-23 13:11:36.503 Autodetect COM port and phone type start!
2017-06-23 13:11:36.509 Compatible COM ports not found!
2017-06-23 13:11:36.513 ERROR!
Phone not found !
I don't know how to proceed, but don't want to be stuck with stock rom. Any suggestions?

Okay, image verification error obviously had something to do with the B320 rom I flashed. Tried B192 now and recovery flash with fastboot goes through with OKAY... Just that the phone doesn't boot into recovery - it just sits there stuck on boot screen.
Would still be thankful for any hints.

Patneu said:
Okay, image verification error obviously had something to do with the B320 rom I flashed. Tried B192 now and recovery flash with fastboot goes through with OKAY... Just that the phone doesn't boot into recovery - it just sits there stuck on boot screen.
Would still be thankful for any hints.
Click to expand...
Click to collapse
I read somewhere that once you are on EMUI 5 you can't go back to 4. The rollback works to 4.1 which is where I am now with C636B330 but that's it. No further. I was advised to use the DC Phoenix tool and go to 330 which thankfully worked! Do the same and you should be ok I guess.. 4.1 or 5.
I think I'm just going to have to wait for someone like kang to do a Rom based on one of those before I try custom. Unless there already is one? Next time I flash a phone I should really research the pitfalls. That would avoid a week of using a different device!

Bearded_1 said:
I read somewhere that once you are on EMUI 5 you can't go back to 4. The rollback works to 4.1 which is where I am now with C636B330 but that's it. No further. I was advised to use the DC Phoenix tool and go to 330 which thankfully worked! Do the same and you should be ok I guess.. 4.1 or 5.
Click to expand...
Click to collapse
Thanks for the reply! I'm now back on C432B180 with EMUI 4.0 flashed with DC Phoenix and finally managed to flash a TWRP using SRK Tool.
Anything with B3XX or B5XX still just gives me the 'image verification error' mentioned above for any custom recovery and I doubt it would be any different with SRK Tool since it also just makes use of fastboot as it seems to me. So I'm staying with B180 for the moment unless someone has a suggestion on how to get rid of this error.
I'll now try to flash Ephemeral Mate 8 again, since it was the first (and last) custom ROM that worked for me before. I know it's discontinued, but it's the only one I can currently find that doesn't mention to go to B3XX first - which wouldn't work for me.
What worked and didn't work so far:
Tried flashing EM8_41816_SIGNED.zip, which failed without warning and rebooted to fastboot mode mid-process which showed some error involving the word 'panic'.
Managed to root the stock B180 again with SRK Tool, but will continue to try earlier versions of Ephemeral 'cause I really need the Kang Tools. Will update on how that worked out.
Suggestions still welcome on:
How to get rid of 'image verification error' on B3XX and B5XX' so I can try flashing a non-outdated ROM.
Other still available pre-B3XX ROMs I could try.
Any root apps to achieve navbar and status bar modifications similar to Kang Tools, so I could do without a custom ROM and stay with currently achieved rooted stock ROM.
One little edit concerning the 'image verification error': My phone mentions the FRP to be unlocked in fastboot mode, when on B3XX or B5XX which it doesn't on B1XX, so maybe that's related to it? But I don't know exactly what an FRP is or what it means to unlock it.

YEEESSS!!! :victory:
Tried flashing EM8_40416_SIGNED.zip now and went through without errors. Took a few seconds to reboot and it works! Just B170 now it seems, but hey...
My quest to upgrade may have failed graciously, but at least I got a working rooted phone again with Kang Tools - what more can I ask for? And unless someone, somehow, somewhen has a hint for me about this damned 'image verification error' (at least I now know a foolproof way to fix it if I mess anything up again) I'm taking this cautionary tail to heart and won't touch this damned phone's firmware again 'til it turns to dust under my fingers.
And now, as common courtesy commands, my exact steps - from having completely messed up with nothing save stock recovery and fastboot mode working anymore to functioning phone again with root, cutom ROM and Kang Tools - for the sake of the poor souls of the future who may (hopefully not) follow in my footsteps facing the same problems (no guarantees or responsibility whatsoever on my part, just what worked for me):
1. Reboot your phone into fastboot mode (bootloader) by pressing and holding power + volume down together (don't forget to connect the phone to a PC before!). As always, make sure you have enough battery power left before each step! If you don't at this point, try booting into stock recovery by holding power + volume up and charge your phone, then continue.
2. Download:
2.1: DC Phoenix from here. Found here via here.
2.2: File with partition rework and factory firmware from here. Found here.
2.3: NXT-L29C432B180 stock ROM from here (you may need a different version depending on your device!). Found here. (Stock ROMs B3XX or higher may work too, but didn't for me - see above).
3. Buy 15 credits here to use DC Phoenix (it's worth it!), unpack and start DC Phoenix and login with your DC-unlocker credentials. (Edit: If you want to try the new guide mentioned below from step 5 onward, you should consider buying the 'DC-Phoenix + HCU timed license' option for 19 bucks instead.)
4. Follow this guide. You find the mentioned 'UPDATE.APP' file in the stock ROM ('update.zip') file you downloaded before.
5. You should have unbricked your phone and have a working stock ROM again by now. :fingers-crossed: Now on to getting a custom ROM again:
(Edit: I fiddled around with my phone a bit more in the meantime, so if you prefer flashing a TWRP on a B5XX-based stock ROM and finding your way from there, you may want to follow this new guide instead.)
6. In the settings of your phone enable 'Developer options' -> 'USB debugging' if you haven't already (and 'Enable OEM unlock' too just to be sure, don't know if it's necessary, but I did it). If you don't see 'Developer options', tap on 'About phone' -> 'Build number' a few times. Connect phone to your PC.
7. Downloads:
7.1: SRK Tool from here. Found here via here.
7.2: Ephemeral Mate 8 from here. Found here via here. (Later version or other ROMs may work for you, but didn't for me.)
8. Move 'EM8_40416_SIGNED.zip' file (or the one you want to flash) to the external sdcard of your phone.
9. Unpack and start SRK Tool.
10. Select '3. Install Recovery 6.0' -> '2. Huawei Mate 8' -> '2. Install Mate 8 TWRP for Marshmallow (EMUI 4.0)' (may depend on the stock ROM version you flashed before). Confirm requests and follow the instructions.
11. Your phone now reboots. Remove the USB cable connecting it to the PC and press and hold power + volume up to boot into the newly flashed custom recovery.
12. Select your language (it was chinese later on for me, when I didn't!) and press 'Cancel' if asked for a password. When asked to allow changes to system, do it (don't know if necessary, but I did).
13. Select 'Wipe' -> Swipe to Factory Reset'.
14. Go back and 'Format Data' -> type 'yes' and confirm. Reboot the phone and enter custom recovery like before. Factory Reset again. (Don't know if this step is necessary, but I did it.)
15. Go back and select 'Install' -> select and flash the zip file you moved to sdcard before. If no errors occured, reboot your phone. Let it reboot, it may take a few seconds. If you get errors, try starting with step 1 or 11 again (depending on how badly you messed up...) and try a different custom ROM (Follow the instructions there and be aware of prequisites and warnings!). If that doesn't work either, note your errors and ask for help - good luck!
16. Congratulations, you should have a working phone again with Ephemeral Mate 8 custom ROM with Kang Tools, it should be rooted already. :good:
17. Maybe buy the guys, who developed and wrote the mentioned tools and guides to help you on your way, a coffee - they surely deserve it.
Hint: If you only want a rooted stock ROM, reboot your phone after step 12, start SRK Tool again, select option '4. Root' and follow instructions.

Patneu said:
Thanks for the reply! I'm now back on C432B180 with EMUI 4.0 flashed with DC Phoenix and finally managed to flash a TWRP using SRK Tool.
Anything with B3XX or B5XX still just gives me the 'image verification error' mentioned above for any custom recovery and I doubt it would be any different with SRK Tool since it also just makes use of fastboot as it seems to me. So I'm staying with B180 for the moment unless someone has a suggestion on how to get rid of this error.
I'll now try to flash Ephemeral Mate 8 again, since it was the first (and last) custom ROM that worked for me before. I know it's discontinued, but it's the only one I can currently find that doesn't mention to go to B3XX first - which wouldn't work for me.
What worked and didn't work so far:
Tried flashing EM8_41816_SIGNED.zip, which failed without warning and rebooted to fastboot mode mid-process which showed some error involving the word 'panic'.
How to get rid of 'image verification error' on B3XX and B5XX' so I can try flashing a non-outdated ROM.
Any root apps to achieve navbar and status bar modifications similar to Kang Tools, so I could do without a custom ROM and stay with currently achieved rooted stock ROM.
One little edit concerning the 'image verification error': My phone mentions the FRP to be unlocked in fastboot mode, when on B3XX or B5XX which it doesn't on B1XX, so maybe that's related to it? But I don't know exactly what an FRP is or what it means to unlock it.
Click to expand...
Click to collapse
Isn't the FRP related to the 'enable oem lock' option? Glad it's sorted! I might follow this thread in the future to go back to pre EMUI 4.1, but I like the camera options so willing to stick with it for a while!

Hey, I didn't realized, I have the 0123456789ABCDEF serial number too, I'm on B330, after unbricking it with DC phoenix (flashed directly from the "Factory_firmware.." for unbrick it, to B330). Did you solve that?
I think I cannot do much now because I'm waiting for the 14 days using my HW account to request de bootloader unlock code. Altough, my phone says I have the bootloader unlocked (that's because the DC phoenix tool did something). But I've never formerly unlocked my phone.

Don Kronos said:
Did you solve that?
Click to expand...
Click to collapse
Well, sort of... I'm still on this fake ABC... Serial Number, but as you can read above, I at least managed to flash a TWRP again and also to install a custom ROM, if only a B1XX based. Better than nothing, though. Didn't encounter any other downsides of the changed Serial Number 'til now.
If you have a hint concerning the 'image verification error' I'd still be glad to hear, but otherwise I'm fine now.

Patneu said:
If you have a hint concerning the 'image verification error' I'd still be glad to hear, but otherwise I'm fine now.
Click to expand...
Click to collapse
Patneu said:
One little edit concerning the 'image verification error': My phone mentions the FRP to be unlocked in fastboot mode, when on B3XX or B5XX which it doesn't on B1XX, so maybe that's related to it? But I don't know exactly what an FRP is or what it means to unlock it.
Click to expand...
Click to collapse
The FRP (Factory Reset Protection) prevents some "writing" commands of ADB to be executed, thats the reason of the "image verification error". It is the homologue to an iCloud protection of iPhone, but using Google Account. I don't know why it gets locked.. but the DC phoenix can crack that protection.

Don Kronos said:
The FRP (Factory Reset Protection) prevents some "writing" commands of ADB to be executed, thats the reason of the "image verification error".
Click to expand...
Click to collapse
Sounds right, aside from the fact that my FRP doesn't seem to be locked. When I flashed B320 via DC Phoenix or flashed B1XX and updated to B560 via OTA and booted into fastboot mode, it said there "Phone unlocked" and "FRP unlocked". I shouldn't get the 'image verification error' then, right? But I do. If I flash B1XX via DC Phoenix, it says nothing about FRP, whether locked or unlocked, just "Phone unlocked" and I don't get 'image verification error'.
I remember getting a TWRP to flash when I updated from B180 (flashed with the TWRP I had before) to B581 OTA before I used DC Phoenix (even if it threw errors like nothing good), but I don't remember if it said anything about FRP then.
Don Kronos said:
I don't know why it gets locked.. but the DC phoenix can crack that protection.
Click to expand...
Click to collapse
Yeah, it seems so, but it can't flash a custom ROM, can it? Only 'UPDATE.APP' of stock ROMS as far as I can see.

Patneu said:
YEEESSS!!! :victory:
And now, as common courtesy commands, my exact steps - from having completely messed up with nothing save stock recovery and fastboot mode working anymore to functioning phone again with root, cutom ROM and Kang Tools - for the sake of the poor souls of the future who may (hopefully not) follow in my footsteps facing the same problems (no guarantees or responsibility whatsoever on my part, just what worked for me):
Click to expand...
Click to collapse
You just saved my fuc**ing ass bro. Thanks a lot for such detailed steps. I was another prick who got his device bricked. I also fhashed a buch of things and lost track on the number of solutions tried until I came across your post:fingers-crossed: Now i feel solid again and want to continue flashing and messing up with my device. That´s the beauty of android, you can recover your device from almost any state. Thanks a lot. You made my day!
The process really work and it's really easy. Those 15 bucks are worth every penny!

juanq214 said:
The process really work and it's really easy. Those 15 bucks are worth every penny!
Click to expand...
Click to collapse
Glad, I could help you and yeah, they surely are.
Just a few remarks I discovered in the meantime:
- If you want to further mess with your phone after that, be sure to not mess up so badly as to having to use DC Phoenix again, unless within the next 72 hours or you'll have to pay the 15 bucks again (as mentioned here). Other claims made there about "lifetime" are not legit.
- Tried EM8_41816_SIGNED version of Ephemeral Mate 8 (based on B180) again and it works, too. The failure and mid-process 'panic' reboot at first try was caused by unrelated battery (hardware) problems of my device (which I think already started before messing with the firmware), which caused me to think I had more power left than I actually did. :silly:
I solved the battery problems by replacing the battery using this guide, ruining some cheap repair kit, made of too much plastic, in the process and paying altogether around 40 bucks for it and for now, everything runs fine again. :good:

Patneu said:
Glad, I could help you and yeah, they surely are.
Just a few remarks I discovered in the meantime:
- If you want to further mess with your phone after that, be sure to not mess up so badly as to having to use DC Phoenix again, unless within the next 72 hours or you'll have to pay the 15 bucks again (as mentioned here). Other claims made there about "lifetime" are not legit.
- Tried EM8_41816_SIGNED version of Ephemeral Mate 8 (based on B180) again and it works, too. The failure and mid-process 'panic' reboot at first try was caused by unrelated battery (hardware) problems of my device (which I think already started before messing with the firmware), which caused me to think I had more power left than I actually did. :silly:
I solved the battery problems by replacing the battery using this guide, ruining some cheap repair kit, made of too much plastic, in the process and paying altogether around 40 bucks for it and for now, everything runs fine again. :good:
Click to expand...
Click to collapse
I successfully got OTA for L29C432B581. I don't really care much about xposed or magic, all I needed was Nougat update. The only downside is that fast charging is gone, but that is not because of the brick but rather a bug related to the update.

Everything fixed.
Ok, so I'm a little late on this, but because some recent circumstances forced me to mess with my phones firmware again - despite my former new-found resolutions :angel: - I dug into this mess again and finally found the solution for the last unsolved problem I encountered: the dreaded 'image verification error'. So I thought, I'd share it with anyone else out there, who may still be struggling:
If you followed my original instuctions, maybe you got stuck at the same point I did: I originally wanted to install a more recent custom ROM based on Android Nougat, but couldn't for the hell of it flash a working TWRP, because of 'image verification error', when I was on a stock Nougat ROM (B5XX-based) and finally settled for my old B1XX-based Ephemeral Mate 8 ROM once more.
So here's what I did to get a working TWRP flashed with a B5XX-based stock ROM (again, no guarantees, just what worked for me):
1. Depending on how badly you messed up before or at what point you currently are, first you may want to follow some of my original instructions 'til step 5. (All links are still working, as far as I can see.) You then should be good to go with a working B1XX-based stock ROM as a basis for what where going to do now. :fingers-crossed: If you already are, great. :good:
1.1: Attention! If you don't already have a working B1XX-based stock ROM, you may want to slightly differ from my original instructions: instead of buying the 15 credits for DC Phoenix in step 3, you could directly choose the "DC-Phoenix + HCU timed license" option for 19 bucks, so you're already set for everything we're doing later and can mess with your phone as much as you want for the next 72 hours - it may come cheaper in the end and it's easier in any case.
1.2: You may notice afterwards, that if you start adb and type 'adb devices', that the serial number of your device changed to something generic like '0123456789ABCDEF'. We'll fix that later on, along with the 'image verification error', but be sure to note your devices original S/N! You can find it on a sticker at the side of the box your phone came in or in the phones 'Settings' -> 'About phone' -> 'Status' -> 'Serial number'. I don't know where else to recover it, if you lost it.
2. Once you have a working B1XX-based stock ROM as a basis, update it to the latest B5XX-based one (was B582 for me) via 'Settings' -> 'System update'.
2.1: Attention again! You may want to check 'Developer options' -> 'Enable OEM unlock' first, since it was greyed out (while still checked) for me once I updated to B5XX. Don't know if it's necessary to have it enabled, but better safe than sorry so you don't have to start over. (If you don't see 'Developer options', tap 'About phone' -> 'Build number' a few times.)
3. Download:
3.1: HCU Client from here. (Thanks Petr S. for putting me on the right track!)
3.2: Unofficial TWRP for EMUI 5.X from here. Found here. (Official TWRP versions may work for you, but didn't for me.)
4. If you didn't already, buy a sufficient number of credits (don't know how much it will be) to use HCU Client from here or directly choose the "DC-Phoenix + HCU timed license" option for 19 bucks to get the all-round carefree package.
5. Unpack and start HCU Client and login with your DC-Unlocker credentials.
6. Connect your phone to your PC and enable 'Developer options' -> 'USB debugging' (don't know if necessary, but I did).
7. As instructed by HCU Client, type '*#*#2846579#*#*' (minus the quotes) into your phones dialer and select '1. Background Settings' -> '2. USB Port Settings' -> 'Manufacture Mode'. If your phone should be rebooting somewhere in the process, you may need to do this again.
8. Now click 'Read phone info' in HCU Client ('Autodetect' should be checked already) and wait for it to complete. (If you didn't buy a sufficient number of credits or the mentioned license before, HCU Client will simply get stuck instead of just telling you - which I found a little odd. )
9. Click 'Repair UMTS' (acknowledge the warning) and type the original serial number of your device (not the '0123456789ABCDEF' one!) into the 'SN' textfield, check it and hit 'Repair'. (I also retyped the 'IMEI' and 'IMEI 2' numbers, but I guess that was unnecessary.)
10. If now you hit 'Read phone info' again, all the textfields under 'Repair UMTS' (except 'WiFi MAC' and 'Bluetooth MAC') should be filled with the right values. Then click 'Unlock' -> 'Read Bootloader code', note the bootloader code. Your phone will shutdown.
11. Power up your phone again, make sure 'Settings' -> 'Developer options' -> 'USB Debugging' and 'Enable OEM unlock' are still checked and bring it into fastboot mode, then open a command prompt and cd to where your 'Minimal ADB and Fastboot' (or whatever you're using) is installed, if you didn't already, and type 'fastboot devices'. You should see your device with the original serial number again.
12. Unlock your device again with the command 'fastboot oem unlock ' followed by the bootloader code you noted before. Now you should be able to flash the unofficial TWRP you downloaded with 'fastboot flash recovery twrp-3.1.1-1-next.img' (assuming you copied the TWRP image file to your 'Minimal ADB and Fastboot' directory for convenience and didn't rename it).
13. Type 'fastboot reboot' and immediately bring your phone into recovery mode. You should now have a working TWRP with a B5XX-based stock ROM and should be able to flash anything you'd like. :fingers-crossed::good:
You should also be able to flash a Nougat-based custom ROM now, though I didn't try that and settled for the stock ROM rooted with Magisk for personal reasons.
A last word of warning: Be sure to frequently make backups in TWRP before you flash or change anything important like installing or updating Magisk or Xposed modules, because I noticed my system to be a little... wonky at this point.
Don't know if that's related to the way I unbricked my phone with all these DC-unlocker tools or just using Magisk or whatever, but several times after changing something important and rebooting, my phone kind of crashed into fastboot mode with some warning about 'native_boot_fail' and wouldn't boot again until I made a factory reset in recovery and started all over (the first time while writing this guide :silly. Not so bad, as it doesn't happen randomly as long as I don't make any major changes to the system, but you wouldn't want to retype your Google password and setup your system again everytime like I had to do, would you? So, yeah, just make a backup in TWRP before you change anything root-related - and tread a little lightly, as in: don't make to many changes at once - and you should be fine.

[RECOVERY][OFFICIAL] TWRP 3.3.1-0 for Galaxy A8+ 2018

Team Win Recovery Project
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about doing this to your device
* YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
{
"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"
}
Disclaimer:
- I am not responsible about any damage of any kind that this custom binary may cause.
- Please read the whole main post & related ones before proceed and follow the guide as it is wrote. I will not offer support for any issues that have been already stated.
- Your Knox Warranty Bit will be blown once you flash this or others custom binaries, preventing you to use Knox TZ Features. It can't be resetted in any way, so think twice before flashing this.
- Bugs can be reported here in XDA or via our Telegram Group. Please be more clear as possible and make sure you provide detailed info when reporting bugs (device variant and logcat).
- If you like my work please hit the "Thanks" button to support me. You're also free to donate me via my donation link here in XDA.
What is TWRP?
Oh come on, you know what it is - don't try to fool me!
In case you're serious, though...
Team Win Recovery Project is a custom recovery for Android devices.
It allows you to back up and restore your data, flash custom ROMs to your device, repair broken file systems, root your device and more.
Read more about TWRP here: https://twrp.me/about/
How to flash and setup it completely?
- First, make sure your phone isn't RMM Locked.
- Download Odin3 v3.13.1, Samsung USB Drivers, latest TWRP's tar for your variant, latest no-verity-opt-encrypt zip and RMM Bypass v3 zip.
- Go to Settings App, Developer Options and enable OEM Unlock (If you don't see Developer Setings, go into About phone>Software info and tap "Build number" 10 times to show Developer Options menu).
- Do a backup of all your important data and files in your phone.
- Shutdown the phone. Once it's off, Power it On in Download Mode (Press and hold Power, Vol + and Vol - buttons together)
- Connect your phone in your PC, open Odin3, go in Option section and untick "Auto-reboot". Once that click the "AP" button and select the TWRP tar you downloaded before, then press the "Start" button.
- Once Odin3 finished to flash the recovery (you should see a "PASS" message), force reboot your phone (Press and hold Power and Vol - buttons together) and once the screen is off, press and hold Power and Vol + buttons together to boot in TWRP.
- Once TWRP is booted you first need to decrypt your /data partition. To do so touch Wipe>Format Data and follow the instructions in screen.
- Once it finished go back at the home screen and touch Reboot>Recovery. TWRP should be able to mount your data partition. Now copy the no-verity-opt-encrypt and RMM Bypass zip you downloaded before and flash them (touch Install and select each zip to flash it)
- You're now able to reboot to your OS without re-encrypting /data partition and without RMM Prenormal lock.
Download:
Galaxy A8 2018 (jackpotlte):
https://twrp.me/samsung/samsunggalaxya82018.html
Galaxy A8+ 2018 (jackpot2lte):
https://twrp.me/samsung/samsunggalaxya8plus2018.html
Sources:
Kernel Source Code: https://github.com/devkingsteam/android_kernel_samsung_universal7885/
Device Tree (jackpotlte): https://github.com/TeamWin/android_device_samsung_jackpotlte
Device Tree (jackpot2lte): https://github.com/TeamWin/android_device_samsung_jackpot2lte
Changelog:
Check Post #2.
A8 2018 Community Telegram Group:
Invite Link
Credits:
- Samsung for kernel source code
- TeamWin for their awesome recovery
- @ananjaser1211 and @McFy for their help and support
- @SaboorTheCool for testing out the recovery
XDA:DevDB Information
TWRP for Galaxy A8+ 2018, Tool/Utility for the Samsung Galaxy A8+ (2018)
Contributors
BlackMesa123
Source Code: https://github.com/TeamWin
Version Information
Status: Stable
Current Stable Version: 3.3.1-0
Stable Release Date: 2019-05-20
Created 2018-07-18
Last Updated 2019-06-17

Changelog:
Note that this page only includes device-specific changes. For global TWRP changes, go to twrp.me.
20180921 (3.2.3-0)
- Updated kernel source code
- Fixed USB OTG
- Enabled FBE support (general AOSP only, Samsung method is still not supported)
20180730 (3.2.3-0)
- Removed /preload from partitions table
- Added /system_image (raw system partition backup)
- Enabled software encryption support (general AOSP only, Samsung method is still not supported)
20180718 (3.2.2-0)
- First release

Reserved

Plan to do nightlies for TWRP?

SRIHARI_GUY said:
Plan to do nightlies for TWRP?
Click to expand...
Click to collapse
Nope, gonna update it just if omni/A8 sources gets updated

TWRP 3.2.3 released. Enjoy!

Will this work with A8+ oreo?

Bad.Server said:
Will this work with A8+ oreo?
Click to expand...
Click to collapse
TWRP isn't built for a specific OS since it's totally separated from OS, so it works on all of them if there aren't significately changes in bootloader/kernel. Even if it was, mine is compiled with latest Oreo kernel source code and based on omniROM 8.1, so...

I lost mobile network?
Hi all. I have an unlocked A8+. I rooted when I had Nougat. I installed the oreo firmware from Columbia and the phone works great. I like the enhancements. I followed the instructions to install the new twrp. Took a bit but got magisk working and root explorer but had issues with busy box and titanium bkup. No biggie. The issue I had is the when I went to send a text I got an error and then I noticed I had no signal. So I checked and low and behold I had no mobile networks in the connections list. Does anyone have a clue as to why it disappeared? Did I miss something? I tried it 2 times with the same result. And help would be greatly appreciated.
P.S. OEM unlock is enabled as well as USB debugging enabled also.

Really proud to announce my request to became the official TWRP Maintainer for Galaxy A8/A8+ 2018 has been accepted! You can download the new build of TWRP directly from twrp.me now.

BlackMesa123 said:
Really proud to announce my request to became the official TWRP Maintainer for Galaxy A8/A8+ 2018 has been accepted! You can download the new build of TWRP directly from twrp.me now.
Click to expand...
Click to collapse
Good work

Help Flash odin erro
Flash odin file twrp 3.2.3 erro “only official released binaries are allowed to be flashed” help me..

vantanvu0804 said:
Flash odin file twrp 3.2.3 erro “only official released binaries are allowed to be flashed” help me..
Click to expand...
Click to collapse
Please read and follow the RMM State guide linked in OP.

Congrats on getting Official xD

vantanvu0804 said:
Flash odin file twrp 3.2.3 erro “only official released binaries are allowed to be flashed” help me..
Click to expand...
Click to collapse
Same thing happened to me.
had to download and install the whole firmware.
downloaded from this
https://forum.xda-developers.com/galaxy-a8-plus/how-to/pie-a8-pie-a730fxxu4csb9-t3908703
probably happened because I still have RMM lock (can't do anything to unlock) in oreo. Bootloader got unlocked in Pie so I thought i can now flash custom binaries. Turns out, you still can't

Its been a long time since I had this phone, June 2018 when I had my first "A" series phone. Since then, I'm planning to root it right away but reading a bunch of forum saying new security patch that samsung did some tells its worst than frp locked something about rmm locked and they say if it happens, theres no way to fix the device unless you have to wait for 7 days without turning off the phone and stay connected and after a week of waiting the "OEM Unlock" option will now be available. There after, with that option now ticked you can now proceed to the common thing here in xda usually do, which is "FLASHING" after that is "CUSTOMIZING" for us to have a unique device amongst others and also enhancing anything to the very limit can handle, system app we only need without those useless bloatwares...
Flashing, rooting and customizing sure is fun and satisfies our needs but it comes with risk. Even we have same device model flashing custom rom in other but same device can experience bugs and some are not, some will experience less issue and some even worst so that caution about the disclaimer always there and proceeding means you take the risk and if something went wrong you're the one responsible and no one but your self will be the only person to blame so if you have no idea what you're doing just stop for a while.
If you really want to start rooting your phone just like me, all you need to do is read, study and understand every aspect, because in some complicated proceedure, there's no room for error and you'll end up crying with a dead phone...
Few months ago from time to time of visiting xda, I have a positive feeling and also I'm completely aware that I can now flash my A8+ 2018 without a doubt, just a piece of cake!
While reviewing step by step, downloaded everything, preparing for every "what if" then the problem came up...
Well, just a little problem, but that small little problem thing suddenly stop me to proceed.
(Read more)
To fully understand the procedure, it took me time, very long waiting time. Passing almost a year now and I'm still stock with the same phone running also in stock os.
Although it's in the "mid-end" phone, having such as this device for almost a year was long enough to love it, enough to get used to it.
Until now, this mid-end phone with stock Android 8.0.0 official operating system runs impressively very smooth and not a single issue ever experienced and to be honest, it exceeds my expectations but still, there's a limitation and that's the customization. To make it possible, I need privilege access to these "four letters" R O O T.
We all know that with a stock os, accessing root surely not possible, it need the superuser (su) to grant permission to access the root and installing su ofcourse is not just like the ordinary apk that can easily be installed, it needs to be flash manually but not in odin. It will be flash in recovery mode but flashing it there still be impossible because that su.zip file cannot be flashed with the stock recovery, you need to modify the recovery mode... Do you how to mdofy it? Well, if you can, that's good and you will have a unique version of it, but me? No way I can modified it...
So, to those people like me who cannot make a customized recovery, NO WORRIES! good news for us because xda geniuses made us for free, custom recovery like twrp, hurray!
It must be flashed via odin, after flashing twrp you can now flash su and congrats, your done rooting...
How I wish rooting todays device was that easy do...
BUT IT'S NOT!
IT'S GETTING MUCH COMPLICATED NOW...
THANKS TO THE GENIUSES HERE IN THE XDA!
Like what I said, it took me too long to fully understand, long enough to like it a lot that putting lots of apps, games, gig to gig files in my secured folder, dozen of duplicated media apps and multiple accounts, in short "LOTS OF THINGS" and for me all those are important and I can't afford to lose a single file...
In the step by step procedure, when everything was already correct settings and before to click and start the flashing of twrp recovery via odin there's instructed or warning that must not be ignored, something like this:
BE SURE "AUTO-REBOOT" IS NOT CHECKED and then after the successful flashing and see the PASS message, force reboot your phone (Press and hold Power and Vol -+ buttons together) and once the screen is off, press and hold Power and Vol + buttons together to boot in TWRP.
Not following the "EXCACT" instruction? Well, it still boot hopefully to normal but then if you try to check if the custom recovery is there... SURPRISE! Nothing's new! Just the same old samsung recovery and you just made your newly flashed recovery useless because it will revert back to stock recovery, instantly replace the twrp recovery you've flashed. That's the reason it have to force reboot to recovery mode.
But there's more, if you start the procedure without enabling the OEM Unlocked somehow kick-in the device "enhanced" security and trip the RMM "TO LOCKED" (not locked yet but it will as soon as the device reboot) if that happens, your'e in some kind of trouble now because at that moment the OEM automatically locked meaning the bootloader will also locked and also means NO FLASHING CAN BE MADE and there's no way the OEM to unlocked because the "OEM Unlocked" option in the developer setting will removed and "UNABLE" to access it for exactly 7 days and forcing odin to flash it again without waiting the said time not an option because doing so while OEM is locked will trip next the Factory Reset Protection aka FRP Locked and it's very hassle. Doing it again and again will not help, the 7 days period will only reset 0 so if it happen, just be patient.
Now back to:
BE SURE "AUTO-REBOOT" IS NOT CHECKED
after successfully flashing your custom recovery it will manage to reboot to your new recovery which is twrp (preferably latest)
Next step to do is yet very simple and easy up to the last step of the procedure...
Its been a long time since I had this phone, June 2018 when I had my first "A" series phone. Since then, I'm planning to root it right away but reading a bunch of forum saying new security patch that samsung did some tells its wosrt than frp lovked something about rmm locked and they say if it happens, theres no way to fix the device unless you have to wait for 7 days without turning off the phone and stay connected and after a week of waiting the "OEM Unlock" option will now be available. There after, with that option now ticked you can now proceed to the common thing here in xda usually do, our only and always be our favorite to do... which is "FLASHING" after that is "CUSTOMIZING" for us to have a unique device amongst others and also enhancing anything to the very limit can handle, having an app that we need and removes those useless bloatwares...
Flashing, rooting and customizing sure is fun and satisfies your needs but it comes with risk. Even we have same device model flashing custom rom some device can face bugs some is not, some will experience less issue and some even worst so that caution about the disclaimer always there and proceeding means you take the risk and no one but your self will be the only person to blame so if you have no idea what you're doing just stop for a while.
Like me, if you really want to make it happen, all you need to do is read, study and understand, because in some complicated proceedure, there's no room for error and you'll end up crying with a dead phone...
Few months ago from time to time visiting xda, I have a positive feeling and completely aware that I can now flash my A8+ 2018 without a doubt, just a piece of cake!
While reviewing step by step, downloaded everything, preparing for every "what if" then the problem came up...
Well, just a little problem, but that small little problem thing stops me to proceed.
(Read more)
To fully understand the procedure and , it took me time, very long waiting time. Passing almost a year now and I'm still stock with the same phone running also in stock os.
Although it's in the "mid-end" phone, having such as this device for almost a year was long enough to love it, enough to get used to it.
Until now, this mid-end phone with stock Android 8.0.0 official operating system runs impressively very smooth and not a single issue ever experienced and to be honest, it exceeds my expectations but still, there's a limitation and that's the customization. To make it possible, I need access to these "four letters" R O O T.
Accessing it is not possible, I need the superuser to grant me permission to access the root and su ofcourse is not just like the ordinary apk that can easily be installed, it will be flash, not in odin but recovery but flashing it will not be possible because that su.zip file cannot be flashed with the stock recovery, but custom recovery can like twrp.
It must be flashed via odin, after flashing twrp you can now flash su and congrats, your done rooting...
How I wish rooting todays device was that easy do...
BUT IT'S NOT!
IT'S GETTING MUCH COMPLICATED NOW...
THANKS TO THE GENIUSES HERE IN THE XDA!
Like what I said, it took me too long to fully understand, long enough to like it a lot that putting lots of apps, games, gig to gig files in my secured folder, dozen of duplicated media apps and multiple accounts, in short "LOTS OF THINGS" and for me all those are important and I can't afford to lose a single file...
In the step by step procedure, when everything was already correct settings and before to click and start the flashing of twrp recovery via odin there's instructed or warning that must not be ignored, something like this:
BE SURE "AUTO-REBOOT" IS NOT CHECKED and then after the successful flashing and see the PASS message, force reboot your phone (Press and hold Power and Vol -+ buttons together) and once the screen is off, press and hold Power and Vol + buttons together to boot in TWRP.
Not following the "EXCACT" instruction? Well, it still boot hopefully to normal but then if you try to check if the custom recovery is there... SURPRISE! Nothing's new! Just the same old samsung recovery and you just made your newly flashed recovery useless because it will revert back to stock recovery, instantly replace the twrp recovery you've flashed. That's the reason it have to force reboot to recovery mode.
But there's more, if you start the procedure without enabling the OEM Unlocked somehow kick-in the device "enhanced" security and trip the RMM "TO LOCKED" (not locked yet but it will as soon as the device reboot) if that happens, your'e in some kind of trouble now because at that moment the OEM automatically locked meaning the bootloader will also locked and also means NO FLASHING CAN BE MADE and there's no way the OEM to unlocked because the "OEM Unlocked" option in the developer setting will removed and "UNABLE" to access it for exactly 7 days and forcing odin to flash it again without waiting the said time not an option because doing so while OEM is locked will trip next the Factory Reset Protection aka FRP Locked and it's very hassle. Doing it again and again will not help, the 7 days period will only reset 0 so if it happen, just be patient.
Now back to:
BE SURE "AUTO-REBOOT" IS NOT CHECKED
after successfully flashing your custom recovery it will manage to reboot to your new recovery which is twrp (preferably latest)
***Next step to do is very simple and easy up to the last step of the procedure...
Once TWRP is booted you first need to decrypt your /data partition. To do so touch Wipe>Format Data and follow the instructions in screen.
Can do it with a couple of swipes to wipe (format data), reboot to recovery again flash su, flash no-verity and also RMM bypass zip just for sure... after that fun stuff can now be available, flash custom roms, blah.. blah.. etc. Boot normally without worries.
About the:
" ***Next step to do is very simple and easy "(above)
Yet very simple and very easy, that's the actual problem dive-in...
As I've mentioned above about having this device from such time and putting lots of apps, games, gig to gig files in my secured folder, dozen of duplicated media apps and multiple accounts, in short "LOTS OF THINGS"
The next step was about formatting and it's a must thing to do to make it work and using unrooted device is impossible to make NANdroid backup, the 64Gb internal storage were almost full and because of that it makes much harder backing-up...
Any advise?
Please help...

@BlackMesa123, please build latest twrp for A8 star, source https://github.com/sabpprook/android_device_samsung_astarqlte

mark0021 said:
bla bla bla...
Click to expand...
Click to collapse
Well the answer is no of course, if you don't wipe your /data partition it will be unreadable from TWRP, equals you can't flash anything that needs to write data in that partition, like Magisk itself. Was it necessary to write that whole post when all you're asking is just a way to avoid /data partition wiping? You basically blamed the "master XDA devs" (which I feel like I'm part of it, sort-of) because "they made the steps for root so hard". I imagine you know "we" aren't the "bad guys that wanna make you lose your precious time" and if I wrote all those steps to follow in the main post (that you copy-pasted twice in your post, without any sense I'd add since users can read the steps from there instead of reading a 1500 lines post) are there because... they are needed? You even noticed and wrote yourself that if you miss one you break something in the way and you get no TWRP if you don't follow all the steps correctly... Wanna blame someone? Then blame the OEMs that add all those security features instead of blaming people that dedicated their time to bypass those and bring you custom softwares for your phone.

inunxelex said:
@BlackMesa123, please build latest twrp for A8 star, source https://github.com/sabpprook/android_device_samsung_astarqlte
Click to expand...
Click to collapse
Sorry but I'm not interested on that phone (since I don't even own it), ask the device tree maintainer to do that.

pls someone help me. Everytime I install TWRP through odin my entire system wipes, and in TWRP it recognizes as 0mb. How can I install TWRP without wiping the entire phone?

[Huawei P20] getting root on AOSP 10 Preview 2

After several days reading into topic, many tries, (including bricking and unbricking my P20 two times down to fastboot access only..), I still not at my goal: Taking full ownership aka. get root of slick & clean device.
Thanks to @OldDroid and his crew (THX!) now I have a working AOSP 10 Preview 2. It was flashed over a fully working EML-L29 9.0.0.293 (C432E7R1P11), bootloader & FRP unlocked, installed from eRecovery internal download(after second brick..) Thankfully I refused to update to 9.1 before due to /system read-only problems i red about. So everything, including recovery should be genuine. I will try to keep all the Google inside an Island and restrict it as far as possible with firewall.
Now I question myself how I can obtain root without bricking this wonderful machine again. I guess I will need Canary Magisk Manager from this link:
https://forum.xda-developers.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337
Switching channel to canary too, going the recovery_ramdisk patching route. (TWRP I already miss you!!)
I already downloaded EML-LGRP2-OVS 9.0.0.293 (FullOTA-MF) via Firmwarefinder to extract recovery_ramdisk from it. As I only flashed system I guess this should be the version I need to patch with Magisk?
I know, this is pretty unknown territory, but on OmniROM 5 beta I the non working touchscreen bug. Would give it a second try if there is no other way, maybe starting from a lower EMUI 9 version? If anybody could confirm my plan, or tell me its rubbish, I would be thankful.
@mods: This whole Treble thing makes it quite confusing, if you believe this post would get more attention in another place, feel free to move it. thx!

[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!