Database Info

A: Having Problems Rooting the Note Pro 12.2 SM-P900/905? TRY THIS!

**NOTE** For the SM-P900! However steps should be the same for SM-P905 EXCLUDING THE FILE TYPES (THEY ARE DIFFERENT DO NOT ATTEMPT TO USE THE FILES FOR THE SM-P900 OR BYE BYE TO YOUR NOTE 12.2 Pro because now you have a problem that may or may not be repairable/reversible). You just have to make sure you have the coordinating files for the process!
If anyone else has issues try this and these steps to complete the Root/Custom ROM/TWRP Recovery installations successfully for a "First time go":
1. Remove Kies and Kies3 files, related files, folders, and everything that has anything to do with the primary installation of either the two programs on your PC and your devices. When/if prompted, select the checkable box and elect not save any type of files... if you want to keep them save them OFF your main PC on a flash or removable storage device.
2. REMOVE ALL SAMSUNG DRIVERS AND REPLACE WITH ONLY OFFICIAL SAMSUNG DRIVES!!! THIS IS A BIG MUST!
3. Using your USB 2.0 cable and ports Install the Custom Rom "P900XXUANB3-RecoveryImg.tar" FIRST and flash it via ODIN 3.07 under the PDA checkbox that is "fixed" (so you noobs don’t make any soft bricks if this is your first attempt at rooting), and only use the ODIN 3.07 THAT COMES W/ CHAINFIRES AUTO ROOT .zip file and then unzip the folder to open ODIN 3.07 ONLY! This is only because I have read that there have been issues installing the SU via Chain Fires Auto Root Process... the file is called (currently as of 25 JUNE 2014) "P900XXUANB3-RecoveryImg.tar" PDA select it and then start when in DOWNLOAD MODE on your device. Manually select DOWNLOAD MODE if you have to BEFORE PRESSING START! Otherwise, one is just going to sit there and not accomplish anything.
http://forum.xda-developers.com/attachment.php?attachmentid=2591013&d=1392923580
http://forum.xda-developers.com/attachment.php?attachmentid=2591159&d=1392930654
http://forum.xda-developers.com/attachment.php?attachmentid=2775098&d=1401644348
4 Reboot back into DOWNLOAD MODE. Flash in ODIN 3.07 with the PDA section and select this file next to install: "openrecovery-twrp-2.7.1.0-v1awifi.img.tar"
5. In DOWNLOAD MODE and flash the file under the PDA box TWRP (OR CURRENT RECOVERY OF YOUR CHOICE THAT IS AVAILABLE)
6. AGAIN... Restart your device into DOWNLOAD MODE via ODIN 3.07 and select PDA and then finally root this: "CF-Auto-Root-v1awifi-v1awifixx-smp900.tar.md5" Then you can backup, restore, flash anything, and be happy! YOU SHOULD FINALLY HAVE A SUCCESSFUL ROOT! Turn off and REBOOT into RECOVERY to see if TWRP stuck and then reboot to see if the SU stuck. IF everything stuck reboot back into TWRP to flash whatever rom is available MAKE SURE TO BACK UP EVERY FILE BEFORE YOU FLASH ANY NON-STOCK ROMS. If not successful rinse wash and repeat until it does!
http://download.chainfire.eu/384/CF-Root/CF-Auto-Root/CF-Auto-Root-v1awifi-v1awifixx-smp900.zip
7. That’s it you should have root and a custom rom and recovery if you followed these instructions for flashing via ODIN 3.07 and Chainfires AutoRoot files. If you still have an issue repeat until root/recovery/Rom sticks. If you have to update the Binary for the SU just go to the Google Play Store and install the app and then try it again till it works. GOOD LUCK it worked for me this way!
**IMPORTANT**
BACK UP BACK UP BACK UP BACK UP after every flash that is possible to back up. If you can, back up the NON-SU stock ROM BEFORE installing SU, after installing the recovery and/or back up.
***IF I HELPED YOU OUT THANK ME***
DISCLAIMER - all research was observed via comments on the thread according to issues people have been having during ROOTING the device I simply have compiled the data and made a check list!

Need a link to the files you mentioned.

Thanks. Very helpful.
I have a P900. Is there a way to unroot and bring a unit back to stock? My main concern is if Samsung sends out a software/firmware update, and a device is already rooted, can the update be applied?

sstea said:
Thanks. Very helpful.
I have a P900. Is there a way to unroot and bring a unit back to stock? My main concern is if Samsung sends out a software/firmware update, and a device is already rooted, can the update be applied?
Click to expand...
Click to collapse
Read THIS
But still one quiestion, why the heck you root your device if you are going to update it via Samsung's official ways. Ah and one more question.. why the heck would you want to update your device if it's rooted?
A new update from Samsung can patch all known security holes and make your device unrootable, and since you are rooted now, one would think that you don't want to loose it. Or where do I know if you rooted because it sounded nice and cool, without knowing what you did and most importantly WHY you did.

Spere said:
Read THIS
But still one quiestion, why the heck you root your device if you are going to update it via Samsung's official ways. Ah and one more question.. why the heck would you want to update your device if it's rooted?
A new update from Samsung can patch all known security holes and make your device unrootable, and since you are rooted now, one would think that you don't want to loose it. Or where do I know if you rooted because it sounded nice and cool, without knowing what you did and most importantly WHY you did.
Click to expand...
Click to collapse
Thanks. I appreciate the reply. I have rooted many devices before. I have to admit that it was more of following posted instructions and not fully understanding the details. What gives me pause is how extremely limited the support is for this tablet. I want to root my note if I can make it more responsive, get rid of bloatware, enable more apps for multi-window, titanium backup, etc. I want to make sure that if I root that I don't get stuck with on an old release. So will previously rooted Notes be able to get the necessary files to easily update and maintain root, or does rooting now mean that a tablet may be stuck at the current release? Thanks

sstea said:
Thanks. I appreciate the reply. I have rooted many devices before. I have to admit that it was more of following posted instructions and not fully understanding the details. What gives me pause is how extremely limited the support is for this tablet. I want to root my note if I can make it more responsive, get rid of bloatware, enable more apps for multi-window, titanium backup, etc. I want to make sure that if I root that I don't get stuck with on an old release. So will previously rooted Notes be able to get the necessary files to easily update and maintain root, or does rooting now mean that a tablet may be stuck at the current release? Thanks
Click to expand...
Click to collapse
You can always flash stock firmware via odin

I was just wondering if everyone was having a much easier time with achieving root now? Kies caused me to "Hang" a lot during the Root and custom rom to stick w root... as of right now i can not get the only ONE custom ROM that looks promising, i have found by GWatts (correct me if i am wrong and i apologize if i have typed the wrong screen name handle) i believe his handle is... at this point im not sure what i am doing wrong as of yet but im sure i am missing a step or i just need to start back at unroot back to stock firmware and try and try again lol. not saying anything is wrong with his work at all by any means because people other than me with the same device have gotten it to stick and im just wishing i could as well because its sweet looking ROM! NOT TO MENTION THE ONLY ONE THAT IS OUT (that is which i know about. i haven't been on in a few months idk), SO KUDOS TO WATTS i just haven't been successful at installing his custom rom just yet... Im hoping that its just going to need to be erased again and then reformatted after a factory reset and what not, i pray it sticks because his incorporation of the aroma installer was a nice touch and his ROM really looks good... Now if i can just get it not to stick at samsung boot logo and freeze id be good lol!

sanvara said:
Need a link to the files you mentioned.
Click to expand...
Click to collapse
ok

I followed your instructions but while flashing the cf-auto-root file my screen got all distorted (speckled grains of color), and nothing else happened for about 15 minutes, until I just unplugged it and shut it off.
Now when I power it on it gives me the error "Firmware upgrade uncountered an issue. Please select recovery mode in Kies & try again."
I wonder what I did wrong.

pnuker said:
I followed your instructions but while flashing the cf-auto-root file my screen got all distorted (speckled grains of color), and nothing else happened for about 15 minutes, until I just unplugged it and shut it off.
Now when I power it on it gives me the error "Firmware upgrade uncountered an issue. Please select recovery mode in Kies & try again."
I wonder what I did wrong.
Click to expand...
Click to collapse
**Edit**
I went back and reflashed the twrp file and it got me out of the error screen. I installed supersu, and then re-flashed the cf-auto-root file, and it worked like a charm. I'm not sure if it was the installation of supersu, or just repeating the process that fixed it, but I'm happy either way...

Thank you! I succesfully rooted my SM-P900 after all mentioned problems ( hanging in the cache.img and after a while a disturbed screen etc.) with your guide. I am a very happy rooter now.

Thanks,
Thanks to the poster. I tried rooting with the instructions from a few other sites and thought I bricked it,
Followed your instructions, and presto.. Rooted! :good:

Rooted!
Thanks for your post. This is my first time ever rooting a device. Your method worked perfectly!

your welcome!
frankiecxyz said:
Thanks for your post. This is my first time ever rooting a device. Your method worked perfectly!
Click to expand...
Click to collapse
your very welcome! it took me a bit to get it down but i eventually figured it out and at the time information on rooting the device was hard to find with this specific model. then i discovered what the issues where and felt the need to post it! im glad i could help!:laugh:

Flash SU with TWRP not ODIN
Here's my story...
Received my new UK spec SM-P900 Note Pro 12.2, ran through the initial setup, performed two OTA upgrades to KOT49H.P900XXUANI1, then attempted to flash SU using Odin 3.07 using the various instructions on this forum. Result: failed cache flash and soft brick!
Used Keis 3 to recover the tablet which took two hours! After more reading I discovered the quick boot recovery flash method, so re-attempted on a different PC, with exactly the same result. Re-flashed the boot, tried again, fail, again, fail, etc, etc. Various permutations of PCs, Odin versions and USB ports were tried.
Concluded that the Odin method was NEVER going to work, so had a rethink. Used Odin to flash TWRP v2.8. Downloaded the latest SU-BETA v2.7 flash for TWRP (not Odin), copied it to the root of the tablet SD and then flashed it with TWRP. Worked first time with no messing about!!!
Booted, ran SU and upgraded to Premium, disabled KNOX from within SU. Tablet locked up. Booted, re-ran SU, disabled KNOX again, this time successfully. Ran Titanium, filtered with KNOX and froze all occurrences, then de-installed KNOX completely. :good:
Lesson learnt... DO NOT use Odin to flash SU on a P900 !

soft bricked
Hello!
First of all let me say that I'm a complete newbie, this is my first android device. I tried to root my SM-P900 (P900XXUANI1) using an online guide (image with URL attached, as I am not allowed to paste URLs)
Unfortunately at Step 10 (flashing with Odin) the operation failed and now I ended up with a soft bricked device (I assume this is the correct definition). It will only show the message asking me to connect it to KIES to recover it.
I know i can try to use KIES 3 and restore it, but before that i would like to ask if there is any alternative which will allow me to unbrick the device without losing all my data... (yeah i know...).
If i follow this guide will this help? I'm not sure if I can even put the device in download mode again as it shows the error message about connecting it to KIES...
At this point I don't care about rooting, I just want to unbrick the device.... I understand the guide up to (and including) step 3. But for the rest of the steps I'm lost Could anyone please explain them in a bit more detail? I don't want to install any custom firmware, just to unbrick it...
Any help would be very appreciated!
Thank you

Yemble said:
Here's my story...
Received my new UK spec SM-P900 Note Pro 12.2, ran through the initial setup, performed two OTA upgrades to KOT49H.P900XXUANI1, then attempted to flash SU using Odin 3.07 using the various instructions on this forum. Result: failed cache flash and soft brick!
Used Keis 3 to recover the tablet which took two hours! After more reading I discovered the quick boot recovery flash method, so re-attempted on a different PC, with exactly the same result. Re-flashed the boot, tried again, fail, again, fail, etc, etc. Various permutations of PCs, Odin versions and USB ports were tried.
Concluded that the Odin method was NEVER going to work, so had a rethink. Used Odin to flash TWRP v2.8. Downloaded the latest SU-BETA v2.7 flash for TWRP (not Odin), copied it to the root of the tablet SD and then flashed it with TWRP. Worked first time with no messing about!!!
Booted, ran SU and upgraded to Premium, disabled KNOX from within SU. Tablet locked up. Booted, re-ran SU, disabled KNOX again, this time successfully. Ran Titanium, filtered with KNOX and froze all occurrences, then de-installed KNOX completely. :good:
Lesson learnt... DO NOT use Odin to flash SU on a P900 !
Click to expand...
Click to collapse
Have you got a link to the odin rwrp 2.7 you used and the su 2.7 flash for twrp please?

VenomousViper said:
**NOTE** For the SM-P900! However steps should be the same for SM-P905 EXCLUDING THE FILE TYPES (THEY ARE DIFFERENT DO NOT ATTEMPT TO USE THE FILES FOR THE SM-P900 OR BYE BYE TO YOUR NOTE 12.2 Pro because now you have a problem that may or may not be repairable/reversible). You just have to make sure you have the coordinating files for the process!
If anyone else has issues try this and these steps to complete the Root/Custom ROM/TWRP Recovery installations successfully for a "First time go":
1. Remove Kies and Kies3 files, related files, folders, and everything that has anything to do with the primary installation of either the two programs on your PC and your devices. When/if prompted, select the checkable box and elect not save any type of files... if you want to keep them save them OFF your main PC on a flash or removable storage device.
2. REMOVE ALL SAMSUNG DRIVERS AND REPLACE WITH ONLY OFFICIAL SAMSUNG DRIVES!!! THIS IS A BIG MUST!.......
Click to expand...
Click to collapse
When i trying root, my SGN freeze in "cache". Odin show error and tablet goes to Emergency Firmware Recovery. Аnd it does not matter what program I use and how I do it.

Mine Reboots Constantly
I rooted my SM-900 about two weeks ago.
It worked great for a week until the device started rebooting by itself.
The first time a couple times a day, now it does it whenever as often as twice in 5 minutes.
Is there a way to see which app is causing this or does anyone know why this might be happening?
Though I rooted I haven't been poking around. I figured it'd be like using Linux but now I see it's not quite like that.
Thanks in advance.

sunnykhs said:
I rooted my SM-900 about two weeks ago.
It worked great for a week until the device started rebooting by itself.
The first time a couple times a day, now it does it whenever as often as twice in 5 minutes.
Is there a way to see which app is causing this or does anyone know why this might be happening?
Though I rooted I haven't been poking around. I figured it'd be like using Linux but now I see it's not quite like that.
Thanks in advance.
Click to expand...
Click to collapse
Have you cleared dalvic cache and cache in TWRP recovery? Be forewarned the process takes a while for cache wipe.
Sent from my SM-P900 using Tapatalk

Removing retail mode from S7 live demo unit?

Hello,
I bought a cheap used live demo unit S7 that I want to use just for the GearVR.
It works great so far but the retail services are annoying, I've found articles that mention how to remove the software on S6 units...
I was wondering if the same instructions apply to the S7? Model is "SM-G930x"
I've also read a couple of posts about someone successfully flashing the stock rom using odin, but when going to sammmobile to download the firmware I don't know which country to choose. I bought it in the US but I don't know if there are different firmwares for Snapdragon versions or Exynos versions.
Any help would be appreciated.
Thanks!

In case someone stumbles upon my thread, I have successfully flashed a stock rom into my live demo S7.
I just used Odin and had to delete the same files that needed to be deleted for the S6 demo units using cygwin... cm.bin, sboot.bin and modem.bin. The difference here though is that with the S7 firmware, those files are spread between files, since the firmware zip contains 5 md5 files instead of 1... one is inside the CP file and the other two inside the BL file.
I deleted them all and then flashed with Odin by selecting the main AP file and the 2 modified BL/CP files.
Hope it helps someone in case they are looking to flash an S7 LDU, I'm guessing the same rules apply to the S7 edge though I have not tried that myself.
Everything works perfectly except cellphone calls/internet obviously, and the fingerprint sensor...which appears to commonly not work on live demo units.
Cheers

andrewe1 said:
In case someone stumbles upon my thread, I have successfully flashed a stock rom into my live demo S7.
I just used Odin and had to delete the same files that needed to be deleted for the S6 demo units using cygwin... cm.bin, sboot.bin and modem.bin. The difference here though is that with the S7 firmware, those files are spread between files, since the firmware zip contains 5 md5 files instead of 1... one is inside the CP file and the other two inside the BL file.
I deleted them all and then flashed with Odin by selecting the main AP file and the 2 modified BL/CP files.
Hope it helps someone in case they are looking to flash an S7 LDU, I'm guessing the same rules apply to the S7 edge though I have not tried that myself.
Everything works perfectly except cellphone calls/internet obviously, and the fingerprint sensor...which appears to commonly not work on live demo units.
Cheers
Click to expand...
Click to collapse
Any idea if this same method applies to Verizon demo phones that are actually consumer models running retail software?

I don't know...probably? If the model is the same I don't see why not. Don't take my word for it though... This was my first experience flashing an LDU model.

andrewe1 said:
I don't know...probably? If the model is the same I don't see why not. Don't take my word for it though... This was my first experience flashing an LDU model.
Click to expand...
Click to collapse
Well, since you managed to do it with an X variant, I have pretty high hopes that it will work with an actual consumer model(SM-G935V).
How did you manage to power off the device and go into Download mode?

KillTheSprint said:
Well, since you managed to do it with an X variant, I have pretty high hopes that it will work with an actual consumer model(SM-G935V).
How did you manage to power off the device and go into Download mode?
Click to expand...
Click to collapse
Follow the same instructions here up to the part where you delete the files with cygwin... in that step do what I did:
http://forum.xda-developers.com/galaxy-s6/general/g920x-master-thread-guides-firmwares-t3267738
Same passwords and everything.
Hope that helps

andrewe1 said:
Follow the same instructions here up to the part where you delete the files with cygwin... in that step do what I did:
http://forum.xda-developers.com/galaxy-s6/general/g920x-master-thread-guides-firmwares-t3267738
Same passwords and everything.
Hope that helps
Click to expand...
Click to collapse
Thanks!
I am not sure deleting files from the firmware is needed since you needed to delete them since you were flashing a different model firmware on to the demo model. In my case it is just a verizon stock firmware to a regular consumer phone so hopefully after removing the Retail software, Odin successfully flashes the stock firmware.

Hi, Is it possible to give a step by step process taken and the files used to flash with.
thanks in advance.

try to flash stock rom to your s7
---------- Post added at 04:12 AM ---------- Previous post was at 04:11 AM ----------
or try to reset the phone from recovery

Please help guys, I have a Samsung galaxy s7 demo version SM-G930X and stuck in boot loop error. I am trying to install SM-G930F stock rom on this by following this method but don't know how to delete those files from the firmware .tar file. Please can anyone provide a stepwise instruction

flutenpsyte said:
Please help guys, I have a Samsung galaxy s7 demo version SM-G930X and stuck in boot loop error. I am trying to install SM-G930F stock rom on this by following this method but don't know how to delete those files from the firmware .tar file. Please can anyone provide a stepwise instruction
Click to expand...
Click to collapse
here you go: basicly just the same but remember to flash s7 roms/firmware not s6.
Edit: /u/servili007 posted this thread on XDA developers forum which is probably a better guide. I'm not an expert so defer to that if it makes sense. /edit
In case you saw this thread a couple of weeks ago and thought you can get a GearVR capable Samsung S6 for cheap by buying a Live Demo Unit (LDU) here's some warnings:
It's a store display unit meaning it's likely used and abused.
There's no phone capabilities as the cellular antenna and SIM slot are removed.
The screen probably has burn in of some sort and has been on a lot.
It's not covered by warranty so you're getting it as is, and likely no return to the Ebay seller
The stock ROM automatically loads "Retail Mode" that's not simple to remove and it resets the phone
GearVR software likely will not load on it without effort.
If you understand the above, read what might be required before making the plunge.
First, watch this and write down the information he says to get: https://www.youtube.com/watch?v=n8LMyRqBViM
Basically you need to disable "Retail Mode" by installing a ROM that's not retail. Again, this probably won't work and will BRICK your phone, but you've been warned. This works for S6 and not the Note 4 which needs different passwords.
Go to the app drawer and open an app called Samsung Retail (not the Retail Mode program).
Go to Configuration Settings and enter the password 5444 to unlock it.
Then uncheck “Disable the factory reset” and enter the following password M729Q16K8546.
Decline the "Factory Reset" and instead turn your Samsung Galaxy S6 off
Boot into Recovery mode by holding down Volume Up, Power and Home button all at the same time.
Go to Wipe data & factory reset and press OK.
Now comes the fun part: Flash a stock firmware with ODIN. These steps I've got from here, here and here.
Go to sammobile and download the fimware you think it is the right one. This firmware which is a 5.0.2 version from New Zealand worked for more than one person
Extract the firmware file which is a 1.5gb tar.md5 file.
You will now have something like this G920IDVU1AOC6_G920INZC1AOC6_G920IDVU1AOC6_HOME.tar.md5
Rename it to something shorter like G920IDVU1AOC6.tar and be sure to delete the .md5 at the end.
Download the pseudo-Linux emulator Cygwin from it's home site here and install it
Move the tar file (G920IDVU1AOC6.tar) to C:\cygwin\home\''username''
Open cygwin and delete all the ''.bin'' files by typing the following commands (use up arrow to reload last command and edit for next command). Takes a few moments per command.
tar --delete --file=G920IDVU1AOC6.tar modem.bin
tar --delete --file=G920IDVU1AOC6.tar cm.bin
tar --delete --file=G920IDVU1AOC6.tar sboot.bin
Close cygwin. You can check if cygwin really deleted the bin files by opening the .tar file with winRAR.
Make sure the Samsung drivers are installed on your computer. Something you should verify ahead of time (before any of this) by seeing if you can access it from "My Computer" when it's connected.
Download the latest Odin3 v3.10.6 from here and unzip it (the link is in the signature block of the comment). Odin is a program for service stores to reload stock roms into units in maintenance.
Open Odin
Click on AP button and choose modified .tar file from step 7.
Connect your Samsung phone to the pc. Turn it on using Down Volume (not Up), Power and Home buttons. When you get the warning screen about loading up roms can be dangerous, press Up volume to accept.
On Odin screen, you should see the phone connect. Click "Start" and hope it works .... your s6 should boot a few times, and then start up like new, if not, try another fimware from another country from sammobile.
Again, the firmware that seems to work is a 5.0.1 and only if you remove the .bin files. The above worked for myself and I was finally able to load up GearVR. However, as it was a LDU there is burn in easy to make out. In addition it was an S6 with older firmware meaning it's missing out on some improvements.
Please note I don't make a habit of rooting smartphones or messing around installing images into hardware. As such, I probably spent way to much time searching around for the above, downloading a few roms and trying to get it to work before finding the correct path. Hopefully the above saves you some headache if you take the unadvised route of using an LDU for your GearVR.

I found this somewhere on this website:
Free simple factory reset - how to
Okay this is how you do it, super easy
Download: https://apkpure.com/free-simple-fact....android?hl=en
1. Connect phone to PC
2. Place Simple Factory Reset.apk in the phone's storage
3. Install Simple Factory Reset.apk
4. Open Simple Factory Reset
5. Click reset
5. Wait untill you see a message that says something like "not allowed to shut down"
6. Once you see that restart the phone (hold: volume down, volume up, power and home button)
7. As soon as phone goes black, boot into recovery (hold power, volume up, and home button)
8. Let phone reset
Done, phone will restart and retail mode is no more.
This works on all samsung, ive tested it myself on s4, s5, s6, and s7 as well

Donnavarro said:
here you go: basicly just the same but remember to flash s7 roms/firmware not s6.
Edit: /u/servili007 posted this thread on XDA developers forum which is probably a better guide. I'm not an expert so defer to that if it makes sense. /edit
In case you saw this thread a couple of weeks ago and thought you can get a GearVR capable Samsung S6 for cheap by buying a Live Demo Unit (LDU) here's some warnings:
It's a store display unit meaning it's likely used and abused.
There's no phone capabilities as the cellular antenna and SIM slot are removed.
The screen probably has burn in of some sort and has been on a lot.
It's not covered by warranty so you're getting it as is, and likely no return to the Ebay seller
The stock ROM automatically loads "Retail Mode" that's not simple to remove and it resets the phone
GearVR software likely will not load on it without effort.
If you understand the above, read what might be required before making the plunge.
First, watch this and write down the information he says to get: https://www.youtube.com/watch?v=n8LMyRqBViM
Basically you need to disable "Retail Mode" by installing a ROM that's not retail. Again, this probably won't work and will BRICK your phone, but you've been warned. This works for S6 and not the Note 4 which needs different passwords.
Go to the app drawer and open an app called Samsung Retail (not the Retail Mode program).
Go to Configuration Settings and enter the password 5444 to unlock it.
Then uncheck “Disable the factory reset” and enter the following password M729Q16K8546.
Decline the "Factory Reset" and instead turn your Samsung Galaxy S6 off
Boot into Recovery mode by holding down Volume Up, Power and Home button all at the same time.
Go to Wipe data & factory reset and press OK.
Now comes the fun part: Flash a stock firmware with ODIN. These steps I've got from here, here and here.
Go to sammobile and download the fimware you think it is the right one. This firmware which is a 5.0.2 version from New Zealand worked for more than one person
Extract the firmware file which is a 1.5gb tar.md5 file.
You will now have something like this G920IDVU1AOC6_G920INZC1AOC6_G920IDVU1AOC6_HOME.tar.md5
Rename it to something shorter like G920IDVU1AOC6.tar and be sure to delete the .md5 at the end.
Download the pseudo-Linux emulator Cygwin from it's home site here and install it
Move the tar file (G920IDVU1AOC6.tar) to C:\cygwin\home\''username''
Open cygwin and delete all the ''.bin'' files by typing the following commands (use up arrow to reload last command and edit for next command). Takes a few moments per command.
tar --delete --file=G920IDVU1AOC6.tar modem.bin
tar --delete --file=G920IDVU1AOC6.tar cm.bin
tar --delete --file=G920IDVU1AOC6.tar sboot.bin
Close cygwin. You can check if cygwin really deleted the bin files by opening the .tar file with winRAR.
Make sure the Samsung drivers are installed on your computer. Something you should verify ahead of time (before any of this) by seeing if you can access it from "My Computer" when it's connected.
Download the latest Odin3 v3.10.6 from here and unzip it (the link is in the signature block of the comment). Odin is a program for service stores to reload stock roms into units in maintenance.
Open Odin
Click on AP button and choose modified .tar file from step 7.
Connect your Samsung phone to the pc. Turn it on using Down Volume (not Up), Power and Home buttons. When you get the warning screen about loading up roms can be dangerous, press Up volume to accept.
On Odin screen, you should see the phone connect. Click "Start" and hope it works .... your s6 should boot a few times, and then start up like new, if not, try another fimware from another country from sammobile.
Again, the firmware that seems to work is a 5.0.1 and only if you remove the .bin files. The above worked for myself and I was finally able to load up GearVR. However, as it was a LDU there is burn in easy to make out. In addition it was an S6 with older firmware meaning it's missing out on some improvements.
Please note I don't make a habit of rooting smartphones or messing around installing images into hardware. As such, I probably spent way to much time searching around for the above, downloading a few roms and trying to get it to work before finding the correct path. Hopefully the above saves you some headache if you take the unadvised route of using an LDU for your GearVR.
Click to expand...
Click to collapse
Thanks for the Info, I got my s7 LDU working, I just flashed a normal G930F stock room via Odin and it was stuck in bootloop, then flashed a twrp and later went to recovery mode where it showed "dm varity check failed, need to check drk first". I learned that it happens when you are not rooted, so I flashed cf auto root via Odin and after that it booted correctly. The retail softwares all gone. But there's only a problem that it hangs for 2-3seconds every now and then unfortunately.
https://www.s7fanclub.com/2016/04/flash-stock-rom-galaxy-s7-galaxy-s7-edge.html
https://www.s7fanclub.com/2016/03/download-flash-twrp-recovery-root-galaxy-s7-sm-g930f.html
https://www.s7fanclub.com/2016/02/how-to-root-samsung-galaxy-s7.html

I finally removed the Retail Mode from my Verizon Demo Phone.
https://www.youtube.com/watch?v=MXrHmD-mee8

KillTheSprint said:
I finally removed the Retail Mode from my Verizon Demo Phone.
https://www.youtube.com/watch?v=MXrHmD-mee8
Click to expand...
Click to collapse
Why don't you post the method you used.. the video, is not only useless it doesn't work anymore....

All I did was flash it with the stock rom. The Verizon demos seem to have a different bootloader/recovery compared to regular demos. What model do you have?

vo_danh said:
Why don't you post the method you used.. the video, is not only useless it doesn't work anymore....
Click to expand...
Click to collapse
Not surprising considering the post you just replied to is 9 months old....

*Detection* said:
Not surprising considering the post you just replied to is 9 months old....
Click to expand...
Click to collapse
Just wanted to confirm, you got full retail S7 functionality, calls, text, fingerprint reader everything?

KillTheSprint said:
Thanks!
I am not sure deleting files from the firmware is needed since you needed to delete them since you were flashing a different model firmware on to the demo model. In my case it is just a verizon stock firmware to a regular consumer phone so hopefully after removing the Retail software, Odin successfully flashes the stock firmware.
Click to expand...
Click to collapse
bump
---------- Post added at 02:08 PM ---------- Previous post was at 02:07 PM ----------
flutenpsyte said:
Thanks for the Info, I got my s7 LDU working, I just flashed a normal G930F stock room via Odin and it was stuck in bootloop, then flashed a twrp and later went to recovery mode where it showed "dm varity check failed, need to check drk first". I learned that it happens when you are not rooted, so I flashed cf auto root via Odin and after that it booted correctly. The retail softwares all gone. But there's only a problem that it hangs for 2-3seconds every now and then unfortunately.
https://www.s7fanclub.com/2016/04/flash-stock-rom-galaxy-s7-galaxy-s7-edge.html
https://www.s7fanclub.com/2016/03/download-flash-twrp-recovery-root-galaxy-s7-sm-g930f.html
https://www.s7fanclub.com/2016/02/how-to-root-samsung-galaxy-s7.html
Click to expand...
Click to collapse
bump

m.jordan89 said:
Just wanted to confirm, you got full retail S7 functionality, calls, text, fingerprint reader everything?
Click to expand...
Click to collapse
I don't have a demo unit, and no, you won't get all that because there is no modem or fingerprint reader in demo units, so you can't call or text or use fingerprint security

[j701f] Boot Logo Changer for J7 nxt/core

Boot logo changer for j7 nxt / core.
Not made by me.
Extracted from Revolution os [link]
How to install / use
Download the file from the link below.
Open the file through 7zip.
Make a new folder.
Extract the zip file in the folder.
Replace the logo.jpg with your own logo.
Select all the contents of the file and compress them into a zip file.
Copy the zip into your phone and flash it through twrp.
This only works on j7 nxt/core. Also make sure that your logo is 720 x 1280.
The logo in the zip is note 8s logo. So if you want note 8s logo , then flash the zip file withought making any changes.
Download
Click here
Be sure to hit the thanks button

Simrat singh said:
Boot logo changer for j7 nxt / core.
Not made by me.
Extracted from Revolution os [link]
How to install / use
Download the file from the link below.
Open the file through 7zip.
Make a new folder.
Extract the zip file in the folder.
Replace the logo.jpg with your own logo.
Select all the contents of the file and compress them into a zip file.
Copy the zip into your phone and flash it through twrp.
This only works on j7 nxt/core. Also make sure that your logo is 720 x 1280.
The logo in the zip is note 8s logo. So if you want note 8s logo , then flash the zip file withought making any changes.
Download
Click here
Be sure to hit the thanks button
Click to expand...
Click to collapse
can you please give me the stock boot logo

maybe because you put a wrong resolution of the photo

No. Its pretty difficult to make a mistake like that at all, let alone after being reminded in the instructions and triple checking when I did it.
The output at TWRP said exactly what the script said it should, no errors running it, and it was the right size for the image. Flashing the PDA which included a boot.img didn't fix it either btw, I had to flash a boot.tar.md5 through odin to finish it off as bootable again which has more than just a boot.img in it, I'm thinking that this is working specific to files flashed to the partitions of the ROM it was pulled from and isn't fit for general use.

PantsDownJedi said:
No. Its pretty difficult to make a mistake like that at all, let alone after being reminded in the instructions and triple checking when I did it.
The output at TWRP said exactly what the script said it should, no errors running it, and it was the right size for the image. Flashing the PDA which included a boot.img didn't fix it either btw, I had to flash a boot.tar.md5 through odin to finish it off as bootable again which has more than just a boot.img in it, I'm thinking that this is working specific to files flashed to the partitions of the ROM it was pulled from and isn't fit for general use.
Click to expand...
Click to collapse
this logo works for me

Okay. And?
Have you looked at how the script works? Do you know a little about where its injecting it? Is there room in that functionality for it to fail on differing firmwares? Yes? Okay so then why are you making an issue of my phone reacting different to yours then?
It didn't work for me and it failed in a way that isn't okay for it to be remain published for people to come along and be trying it out.
I feel annoyed that you're persisting and that the implication is that because it worked on yours, that mine should therefore also work and I don't understand why you want to pursue this angle to begin with especially when you didn't post the injection in the first place, so I don't care about a logo that worked for you, it obviously is not the logo I would choose anyway given the possibility of any image in the world I feel like.

I've tested and confirmed it not working for me and indeed the phone won't boot or go into recovery after flashing, on my firmware. I put the image used for the original poster to verify that after trying the commands in the script at the adb shell, and using an image both of the correct size and less than the filesize of the one in Samsung stock, I couldn't inject it with a "No room on storage device" error. Unfortunately, I can't upload the image for inspection without it being taken down and given a warning, whatever the hell that's supposed to mean.
Blurry charcoal images almost entirely obscured and pulled from art gallery sites are forbidden I suppose and get pulled within minutes while phone bricking scripts stay up for a long time.
I tried again using the zip, I got the same result. It doesn't boot nor go into recovery afterwards, zip or adb. It vibrates but the display doesn't appear to come on so its not easy to tell whats happening. I didn't think to try recovery and plug in for adb to see if I ever got it or not.
What's relevant, is that it wasn't necessary to flash the PDA, just the Boot.img.md5 to recover, and that I've confirmed the issue on my firmware.
Apologies for being brash with the previous post, I was still a bit panicked from the initial idea that I had a hard brick when it first happened. I knew I was being a hard head by carrying on when I wrote it.

please we j7 pro users need this too

NICE WORK BRO Keep It UP

PantsDownJedi said:
I've tested and confirmed it not working for me and indeed the phone won't boot or go into recovery after flashing, on my firmware. I put the image used for the original poster to verify that after trying the commands in the script at the adb shell, and using an image both of the correct size and less than the filesize of the one in Samsung stock, I couldn't inject it with a "No room on storage device" error. Unfortunately, I can't upload the image for inspection without it being taken down and given a warning, whatever the hell that's supposed to mean.
Blurry charcoal images almost entirely obscured and pulled from art gallery sites are forbidden I suppose and get pulled within minutes while phone bricking scripts stay up for a long time.
I tried again using the zip, I got the same result. It doesn't boot nor go into recovery afterwards, zip or adb. It vibrates but the display doesn't appear to come on so its not easy to tell whats happening. I didn't think to try recovery and plug in for adb to see if I ever got it or not.
What's relevant, is that it wasn't necessary to flash the PDA, just the Boot.img.md5 to recover, and that I've confirmed the issue on my firmware.
Apologies for being brash with the previous post, I was still a bit panicked from the initial idea that I had a hard brick when it first happened. I knew I was being a hard head by carrying on when I wrote it.
Click to expand...
Click to collapse
Hey, I got the same problem and i can neither boot into system nor into recovery. Can you tell me what boot.tar.md5 should i use ?

aditya9991 said:
Hey, I got the same problem and i can neither boot into system nor into recovery. Can you tell me what boot.tar.md5 should i use ?
Click to expand...
Click to collapse
Do not use this tool. you'll hard brick ur device.***** ass tool.**** u ***** ass nigga.

aditya9991 said:
Hey, I got the same problem and i can neither boot into system nor into recovery. Can you tell me what boot.tar.md5 should i use ?
Click to expand...
Click to collapse
You want to flash one with Odin that is for your phone and ROM version. If you have a full firmware you can extract it, and look for a boot.tar.md5 file.
I don't remember very well now where it flashes to; I think it may be the bootloader file, in fact since its the logo when starting the phone I very much assume it is, so you wouldn't select AP in Odin but BL or whatever the latest version offers for that.
The benefit of doing it this way is that you don't wipe your entire phone in the process, but that it just boots back to how it was. If you have a custom kernel installed then its possible you'll want to reinstall that, though I'm not entirely sure if its necessary or not.

Rooting with Magisk?

So... I unlocked the bootloader, but I haven't found a way to get root yet. There's no TWRP available, and I can't find a useable boot image. I tried to copy boot_a and boot_b using dd in an ADB shell, but all I got was "permission denied". There don't seem to be any stock images available, so I'm not sure where to get a boot image until there's an OTA update, but even then I might not be able to pull it from the data partition without root. Argh.

Also, Motorola has kernel source at https://github.com/MotorolaMobilityLLC/kernel-msm, but the last commit was over 2 months ago, and I can't find a default config for racer.

https://mirrors.lolinet.com/firmware/moto/racer/official/
Firmware for device

Thanks for that. I also found Lenovo's support app at https://support.lenovo.com/us/en/downloads/ds101291 (Lenovo owns Motorola.) Too tired to mess with this now. I'll try it later.

You can retrieve full ROM and boot.img from LMSA using rescue mode.
You can run rescue to update the ROM, observe the download process, copy the .zip once it reached 100% as well as retrieve boot
Copy boot.img to phone and patch with Magisk Manager, and copy back to host computer
Flash the patched boot
Make sure ADB is up to date
adb reboot fastboot
fastboot flash boot patched_boot.img

Yup, it's working now. Thanks all.

I have successfully rooted mine and having adaway installed

Can you install stock android 10 or even android 11 now?

ROM updated
Since Motorola/Lenovo updated the Edge since this was first posted, I would like to add that coming across the boot image file is a bit more scarce than the original release version for the Edge. However, using Rescue and Smart Assistant, you can downoad the latest ROM version. You may now use the boot image file in the downloaded folder [ProgramData\Lenovo\Downloads\Roms] and use that for Magisk patching to attain root. However, since I am not sure how that EXACTLY works, I am worried about the resulting file size. Original file size is 101MB. Patched file size is 36MB. I am afraid to flash due to this. Another however, I use fastboot to boot the patched file directly and it DOES work, just unsure if there would be any problems with it if I FLASH it, instead. I believe I read in a related thread to Magisk and rooting, that it reduces the file size to remove unnecessary space now that it is patched? Can someone confirm how that works and if it is safe to flash? I really don't want to flash it, then come across a problem and have to flash stock boot image and end up running into some other problems all because I wanted to flash the patched file instead of using fastboot to boot every time I reboot. Thanks for any and all help, guys.

mingkee said:
I have successfully rooted mine and having adaway installed
Click to expand...
Click to collapse
How did you get root?

zrex said:
How did you get root?
Click to expand...
Click to collapse
Magisk patched boot flashing method

TOOLBOYNIN39 said:
Since Motorola/Lenovo updated the Edge since this was first posted, I would like to add that coming across the boot image file is a bit more scarce than the original release version for the Edge. However, using Rescue and Smart Assistant, you can downoad the latest ROM version. You may now use the boot image file in the downloaded folder [ProgramData\Lenovo\Downloads\Roms] and use that for Magisk patching to attain root. However, since I am not sure how that EXACTLY works, I am worried about the resulting file size. Original file size is 101MB. Patched file size is 36MB. I am afraid to flash due to this. Another however, I use fastboot to boot the patched file directly and it DOES work, just unsure if there would be any problems with it if I FLASH it, instead. I believe I read in a related thread to Magisk and rooting, that it reduces the file size to remove unnecessary space now that it is patched? Can someone confirm how that works and if it is safe to flash? I really don't want to flash it, then come across a problem and have to flash stock boot image and end up running into some other problems all because I wanted to flash the patched file instead of using fastboot to boot every time I reboot. Thanks for any and all help, guys.
Click to expand...
Click to collapse
Yes, my patched boot image is smaller too, but it works. I'm guessing the patched image is either sparse or truncated.

Mogster2K said:
Yes, my patched boot image is smaller too, but it works. I'm guessing the patched image is either sparse or truncated.
Click to expand...
Click to collapse
That makes all the sense in the world to me. I flashed it and have been running it for a few days now without issue. Have my usual setup with Magisk, Riru-core, Riru EdXposed, and then GravityBox in EdXposed for the free customization. Only thing I couldn't get was Xblast module. Not compatible at all with Android Q. Only thing I need now is make the nav bar black all the time. Can't do it with GB since it doesn't have an option for that. Xblast had one but... oh well. Phone works nice aside from the occasional app that isn't compatible with edge enable/disable.

minidude2012 said:
https://mirrors.lolinet.com/firmware/moto/racer/official/
Firmware for device
Click to expand...
Click to collapse
WOW! You're a life savor, thank you!

I unlocked my bootloader through moto and downloaded the rom through lmsa and patched the boot img with magisk, then tried to flash it using adb but it put my phone into a boot loop.. can anyone help me out? this phone seems like a pain the ass to root* compared to the last one ive done (about 2 years ago)
edit: i think i found out what i did wrong, not renaming the patch file back to how it should be. and i patch the boot.img correct? or patch the recovery.img? getting conflicting guides

Make sure you flash boot.img in fastbootd

I'm curious of people's opinions of rooting this phone?
I just got mine yesterday, and I don't think I've ever not used rooted android all the way back to my first Android Eclair device over a decade ago now.
But here I find myself worried I'll have some of the display issues so I'm hesitant to root my device or request an unlock code while I'm in the 2 week return window because of the wording of the agreement once the code is used. It very explicitly absolves Moto of every possible responsibility for hardware faults under a blanket accusation that by unlocking the phone I must have broken it. And while I have no doubt the wording would crumple in court or whatever, I don't really want to go to court over a cell phone.

I rooted both my "send-ins". I am on my third and just going to accept the light green haze at low light. I rooted my first two and sent them in within a total of a month. First phone was on day 17. 2nd was about 6 or 7 days. That one was a turn around since it displayed the haze during setup. This third one shows it as well but I don't feel like doing the return and setup all over again. You shouldn't have to worry about the agreement since Lenovo/Motorola is not looking into that as this is a known hardware/software issue from factory.

Does this forum include the edge 5G? I have the US model(6/ram, 256GB). Does twrp still have that builder? There used to be something, to that, don't know if that's continued.

reggjoo said:
Does this forum include the edge 5G? I have the US model(6/ram, 256GB). Does twrp still have that builder? There used to be something, to that, don't know if that's continued.
Click to expand...
Click to collapse
Sorry to be a little late, but I am unsure of your question. This forum IS "Motorola Edge 5G". There is a separate forum under the name of "Motorola Edge+ 5G" for the more expensive version. If you are looking for TWRP for this phone, there never was a release. At least none that I had ever seen around here. I was always on the lookout for one and never came across one. The "plus" version of the phone does have a TWRP, however. Maybe that is the phone you have or at least the one you are confusing the TWRP with?

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