Database Info

SM-T235 / SM-T235Y Tab 4 7" - ROOTED - TWRP Recovery 2.8.7 for SM-T235/235Y (LTE)

SM-T235 / SM-T235Y Tab 4 7" - ROOTED - TWRP Recovery 2.8.7 for SM-T235/235Y (LTE)
UPDATED 7/30/2015 with OFFICIAL TWRP 2.8.7 for Galaxy Tab 4.7.0 SM-T235(Y) DEVICES​As with other TWRP's for newer Samsung devices, you need to uncheck auto-reboot and F.Reset time in Odin so you can manually shut down the device and boot into recovery the first time after flashing the custom recovery. If you don't boot into the custom recovery immediately after flashing it to the device, then the OS will overwrite it with the factory recovery and you'll need to start over.
DISCLAIMER :
While we all love to flash new things, You and You alone can choose or choose not to flash this custom recovery.
I am not liable for any of the following : Bricks, Soft Bricks, Meltdowns, loss of data, or damage to your device.
DISCLAIMER #2:
THIS RECOVERY WILL TRIP YOUR KNOX COUNTER - YOUR WARRANTY WILL BE VOID.
THIS RECOVERY IS ONLY FOR SM-T235 and SM-T235Y Tab 4 7" LTE Devices
INSTRUCTIONS​1). Download Odin3v1.85.zip, recovery.tar.md5.zip, and UPDATE-SuperSU-v2.46.zip - all attached
2). Unzip Odin3v1.85.zip placing the extracted folder somewhere on your PC you can find and execute Odin3 from later.
3). Store UPDATE-SuperSU-v2.46.zip somewhere on your SM-T235's external SD storage where you can find it from TWRP later.
4). Unzip recovery.tar.md5.zip placing the extracted file recovery.tar.md5 somewhere on your PC you can find it from Odin3 later.
5). Put SM-T235 tablet in Download Mode (Power Button+Volume Down+Home Button)
6). Flash recovery.tar.md5 using Odin3 v1.85 - use PDA/AP button in Odin - UNCHECK Auto-Reboot and F.Reset Time
7). When flashing is completed you will see RESET displayed in Odin3.
8). Unplug your SM-T235/SM-T235Y from the PC and press (Power Button+Volume Down+Home Button) to initiate a restart/reboot - Don't release your fingers from the buttons.
9). IMPORTANT: AS SOON AS THE DEVICE POWERS DOWN (screen goes blank) MOVE YOUR FINGER FROM THE VOLUME DOWN BUTTON TO THE VOLUME UP BUTTON WHILE STILL PRESSING THE POWER BUTTON+HOME BUTTON.
10). IMPORTANT: AS SOON AS THE SAMSUNG SM-T235 LOGO APPEARS (White Letters) RELEASE YOUR FINGER FROM THE POWER BUTTON WHILE CONTINUING TO PRESS VOLUME UP+HOME BUTTON (If the animated Samsung Logo appears, then you missed Recovery mode and will need to start the entire process over from the beginning.
11). IMPORTANT: If you timed your finger pressing and releasing properly, you should now SEE the blue TEAMWIN splash screen which means you are entering TWRP recovery.
12). Once in TWRP Recovery, you will see a button that says Install. Tap on it.
13). Find UPDATE-SuperSU-v2.46.zip where you previously stored it on your external SD card and install/flash it to your SM-T235/235Y using TWRP.
14). Once installation of UPDATE-SuperSU-v2.46.zip is completed, you can proceed to reboot your SM-T235/T235Y from the TWRP main menu.
15). After the device finishes booting up, your Galaxy Tab 4 7.0" SM-T235/T235Y will be rooted.
16.) Download and run RootChecker to verify root.
CREDITS:
hennymcc - [T235][ROM][5.1.1][LMY48G] CyanogenMod 12.1 for T235(Y) [Alpha 12/07/2015]
RVR - TWRP 2.8.1 for the Galaxy S5 Mini (G800F)
Chainfire - UPDATE-SuperSU-v2.46
A.S._id - Odin3 ROM Editor
A.S._Dev - android_img_repack_tools​

My friends,
I still could use some radio help. ...
TTB
SM-T235 Tab 4 7" LTE ROOTED - TWRP 2.8.1 for the SM-T235/T235Y Tab 4 7" LTE
{
"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"
}

Reserved

TopTongueBarry said:
Also reserved
IT IS SO NEARLY IMPOSSIBLE TO WORK ON ANY THREAD OR POSTING ON THIS SITE. I LOST EVERYTHING I I WAS TRYINGTO UPDATE THIS THREAD WITH D/L LINKS, BUT THE VIDEO ADVERTISEMENTS JUST KILL IE. REPEATEDLY. WHY SO MANY VIDEO ADS, IMPOSSIBLE TO ENJOY AN XDA EXPERIENCE BECAUSE THE HUGE VIDEO ADS JUST CRAWL MY SYSTEM.
THERE WOULD HAVE BEEN A T235 RECOVERY ROOT HERE TODAY BUT THE ADS KILLED MY SESSIONS. I WROTE INSTRUCTIONS AND HAD EVERYTHING READY. THE LONGER IT TAKES TO POST A TOPIC AND INSTRUCTIONS THE MORE BEFUDDLED UP IE GETS UNTIL IT CRASHES.
OH WELL I CANNOT SPEND ANY MORE TIME TODAY HERE. HAVE TO GET BACK TO WORK. SO MUCH FOR GIVING YOU THE D/L's DURING LUNCH BREAK, BUT MAYBE TONIGHT, MAYBE NOT. IM TOO FRUSTRATED AND UPSET THAT I LOST ALL THAT WRITING AND WORK HERE TODAY. WE'LL SEE HOW QUICKLY I GET OVER IT , THEN YOU'LL GET YOUR RECOVERY ROOT.
Click to expand...
Click to collapse
That really blows, I feel your pain. I use chrome on my desktop with the adblock extension (I think it's even available for IE now) and I find the -- XDA 2013 theme for the website is much more aesthetically appealing and easier to navigate

It works! Changing of buttons is kinda tricky though, but its all good.. Thanks alot! :good:

thisisapoorusernamechoice said:
That really blows, I feel your pain. I use chrome on my desktop with the adblock extension (I think it's even available for IE now) and I find the -- XDA 2013 theme for the website is much more aesthetically appealing and easier to navigate
Click to expand...
Click to collapse
Thanks for the tip. I added the adblock plug in. My XDA experience is much improved. Thanks!
TTB

Jay018 said:
It works! Changing of buttons is kinda tricky though, but its all good.. Thanks alot! :good:
Click to expand...
Click to collapse
Confirming what you posted in the old thread, that your device is a SM-T235Y ?
Glad it works.
The T235Y has different factory ROMS on sammobile than the T235. Differences include CSC groupings, and configured radio bands, but the kernel and the partitions are the same as the T235. I suspect that's why this recovery works for the T235Y too.
- Speaking of which, can anybody point me in the direction of a way to get past the hurdles Samsung has added to block the ability to reconfigure LTE radio bands
- If we need to change the CSC's or CSC group to be able to enable LTE Bands 4 and 17, well, Sammy's making that tough to do too.
- Wondering if I can flash the modem firmware from the S5 Mini on the Tab 4 7" LTE using TWRP?
- Then wondering if bands 4 and 17 would be available after flashing since the CSC's play such a role in which radio band's get configured on each device.
Any help with the radio would be greatly appreciated.
TTB

TopTongueBarry said:
Confirming what you posted in the old thread, that your device is a SM-T235Y ?
Glad it works.
The T235Y has different factory ROMS on sammobile than the T235. Differences include CSC groupings, and configured radio bands, but the kernel and the partitions are the same as the T235. I suspect that's why this recovery works for the T235Y too.
Click to expand...
Click to collapse
Yes it's T235Y.. You can add T235Y in your title so other users will know.. Yes it has different ROM so I hesitated at first. Just need a couple of beer to do it, lol. Thanks a lot for this recovery. :good:

My friend....Congratulations...I have tried any method known to Google to root this tablet. Yours was the only one that worked. I have been waiting for this moment from November so thank you for making my day.

Success!!
I played fingers just like over my guitar fingerboard, haha! Then, suddenly, I was in face of TWRP face!:laugh:
First of all: install SD fix!
Infinity thanks to TopTongueBarry and his brilliant idea!:good:

aftnoon2 said:
Success!!
I played fingers just like over my guitar fingerboard, haha! Then, suddenly, I was in face of TWRP face!:laugh:
First of all: install SD fix!
Infinity thanks to TopTongueBarry and his brilliant idea!:good:
Click to expand...
Click to collapse
SD gets fixed if you flash a newer factory ROM than the 5/22 NE8 version. You will need to reinstall TWRP and re root.
TWRP installation and root tested and found to be working no matter which ROM you are running, including the latest version, NJ3
TTB
P.S. After rooting, KNOX can be disabled using ES Task Manager and it doesn't respawn, remains disabled. I'm toying with this in an attempt to get service mode changes to the available LTE bands to stick.
P.S.S ... I'll be releasing either ALPHA 2 or BETA 1 with the Slide to install SuperSU fixed and the missing advanced menu items added later this week.

TopTongueBarry said:
SD gets fixed if you flash a newer factory ROM than the 5/22 NE8 version. You will need to reinstall TWRP and re root.
TWRP installation and root tested and found to be working no matter which ROM you are running, including the latest version, NJ3
TTB
P.S. After rooting, KNOX can be disabled using ES Task Manager and it doesn't respawn, remains disabled. I'm toying with this in an attempt to get service mode changes to the available LTE bands to stick.
P.S.S ... I'll be releasing either ALPHA 2 or BETA 1 with the Slide to install SuperSU fixed and the missing advanced menu items added later this week.
Click to expand...
Click to collapse
Just don't care, TTB! I was ALREADY on NJ3!
Thanks for the Es explorer Knox idea, but, do you mean freezing Knox? I don't understand, sorry ...
And many thanks for keep the job over TWRP :good:

this is awesome i bought a couple 235y of my step dads friend for 100 bucks a pop thinking i got a great deal and and I was gonna put vanilla on it and blah blah came to xda to see there was no support..... decided to come on today see if there was anything and see this...
so amped..
---------- Post added at 10:51 PM ---------- Previous post was at 10:11 PM ----------
any custom rome we can flash or am i assuming no because deltas, I'm gonna try a couple things.

David111jr said:
this is awesome i bought a couple 235y of my step dads friend for 100 bucks a pop thinking i got a great deal and and I was gonna put vanilla on it and blah blah came to xda to see there was no support..... decided to come on today see if there was anything and see this...
so amped..
---------- Post added at 10:51 PM ---------- Previous post was at 10:11 PM ----------
any custom rome we can flash or am i assuming no because deltas, I'm gonna try a couple things.
Click to expand...
Click to collapse
No Custom ROMS yet, but since we now have a working recovery and root, there will hopefully be some soon..
I'm beating my head against the wall trying to get LTE bands 4 and 17 added. The factory firmware is quite unforgiving. A custom ROM would sure make the effort easier. Someone PLEEZE ......
Regarding freezing Knox, yes that's what I meant, and it works, but I've managed to wipe the CSC during my efforts to add LTE bands. Don't know if that's a good or bad thing at this point.
Apparently the Samsung USB drivers do have a diagnostic mode driver for Marvel chipsets. After much effort, I have it installed on my Win 8 machine, and the driver switches dynamically when switching from PDA to MODEM in the Service Mode menus. Problem is, its not a serial driver it is a USB/QC driver and QPST version 2.7.411 still doesn't recognize it. Need to find a way to get QPST to recognize it.
Can't do the NV ram edit needed to add LTE bands without diagnostics mode.
TTB

It works. SM-T235 LTE
Thanks!

I think my t235y will never be rooted, you are awesome bro

Thanks for your efforts, TTB!
Now a question : can we make a Nandroid bckp on the External SD?
I would to make one, but, apparently, the bckp goes to Internal, where I have no place ...
Is this intrinsic of TWRP or a later version can change this?

aftnoon2 said:
Thanks for your efforts, TTB!
Now a question : can we make a Nandroid bckp on the External SD?
I would to make one, but, apparently, the bckp goes to Internal, where I have no place ...
Is this intrinsic of TWRP or a later version can change this?
Click to expand...
Click to collapse
Check the T230 recovery/root threads. I believe (not 100% certain though) I saw that someone has created a fix/work-around to allow switching internal SD and external SD for this.

thienlong0193 said:
I think my t235y will never be rooted, you are awesome bro
Click to expand...
Click to collapse
What do you mean you think it will never be rooted? This works on the T235 and the T235Y.

TopTongueBarry said:
What do you mean you think it will never be rooted? This works on the T235 and the T235Y.
Click to expand...
Click to collapse
sorry my bad english, i mean i've been waiting for so long to root my tab :laugh: thank you a lot :x

Safestrap for galaxy s5 active g870w telus

G870W Recovery
Hello there!
I've successfully rooted my (Telus) S5 Active / G870WVLU1ANH3 / kltevlactive using CF Auto Root, blowing my knox and all that, works great.
However, I'm now trying to flash either TWRP or CWM Philz for klte (which may have not been to smart come to think about that, but I recall reading it should work just fine) using Odin, and I can't get into recovery. Whenever I attempt to boot into recovery, I end up with "cannot do normal boot".
I recall reading a SafeStrap for G900 works for the G870, but I can't find the thread again, and don't want to just try and see what happens.
I've also tried flashing a recovery using either TWRP app and RomManager, I have yet to try Rashr, but since all the recoveries I've found are for klte, instead of kltevlactive, I'm slightly worried.
I'm not all that new to rooting, but I'm quite new (and upset ) at the Samsung realm, any chance you guys would know what could get me going with a custom recovery?
I also have a Xposed Framework installed, I read it could cause issues with SafeStrap, but I don't suppose it would affect flashing a rom from Odin/whatever else?
My SELinux on the phone claims to be "Enforcing", if that matters, perhaps.
Thanks!

Am I allowed to bump? I have seen the exact same question before and it never was replied. . And I believe it is a good question. Worth an answer.
Thanks
Sent from my SM-G870W using XDA Free mobile app

marcil802 said:
Am I allowed to bump? I have seen the exact same question before and it never was replied. . And I believe it is a good question. Worth an answer.
Thanks
Sent from my SM-G870W using XDA Free mobile app
Click to expand...
Click to collapse
For installing safestrap you must remove XPOSED. Once installed SS you can reinstall xposed. BUT the only SafeStrap I found is for G900V (Verizon s5) and it has been abbonded in September 2015 as it has a heavy bug. If I was you, i won't look for adventures and flash other phone model's software to my own. And it could be usefull to check if the phone you are going to buy has a permanent locked bootloader when you're interested in modding.

Hey thanks man. Now I'm sure this is gonna a weird question to you but. As for safestrap I've read about out dated versions. But are there different versions for different devices? Could you help me get the right one for my phone or tell me where to download it.
Active g870w. Telus
Thanks alot.
Québec Canada
Sent from my SM-G870W using XDA Free mobile app

marcil802 said:
Hey thanks man. Now I'm sure this is gonna a weird question to you but. As for safestrap I've read about out dated versions. But are there different versions for different devices? Could you help me get the right one for my phone or tell me where to download it.
Active g870w. Telus
Thanks alot.
Québec Canada
Sent from my SM-G870W using XDA Free mobile app
Click to expand...
Click to collapse
Just like normal custom recoveries the safestrap recoveries also must be fitted for every single Phone. As comparison you can think about a custom recovery that works on every phone with unlocked bootlader. That was great but can never be made real. I already tried to find a matching recovery for your S5 active but haven't found anything suitable yet.

I'm still looking like crazy...
I have seen the at&t version got one also they
Now got a stock firmware and safestrap for them... Have you find anything that can suit our G870W
Im so desperate .
Sent from my SM-G870W using XDA Free mobile app
Here is the link of what I'm talking about
http://forum.xda-developers.com/showpost.php?p=56009811&postcount=1974
Sorry for my bad English.
Thanks and when ever I hear from another guy talking about the G870W it makes me feel like a baby with he's teddy bear... Lol
So left alone... Hard start for first time rooting

Dammit i guess i screwed i need help
IM , now stuck between power off and android system recovery
i try to do as i did before
-wipe data
-wipe cache
-apply update from extrnal storage/
-unity 2.1.0/
-Unity_ROM_V2.1.0_Signed.zip
it says
Install /sdcard/Unity 2.1.0...
then i reboot and it keep brigning me back to first step !
i guess thats a boot loop what now:crying:

BTW i forgot to say thanks for your time i apppreciate. in 18 month ill start enjoying my phone again

s5 active canadian
figured out how to flash custom roms to the g870w find a rom for an s5 variant that is snapdragon download it use 7zip to open the archive dont extract it (must get the telus ol1 firmware from android file host first ) once you have the ol1 telus firmware extract it with 7zip to a folder that you can remember now go back to the s5 rom you downloaded earlier look for the boot.img in 7zip and delete it then drag and drop the boot.img from the telus firmware that you downloaded........ On the phone make sure to root with cf auto root and install flashfire from the playstore as its vital for this to work as there is no custom recovery for the g870w now once you edit the custom rom you downloaded to include the telus boot.img drag and drop it to your phone open flash fire on the phone click the little plus button select the wipe fucntion then click the plus button again click the flash zip or ota option and select the modified custom rom you just transfered go back to where it shows the rom name and the wipe option hold on the wipe option and drag it to the spot above the rom name then click flash it will reboot and wipe then start flashing the modified custom rom.......if you want xposed download the sdk21 xposed and put it on your phone once it boots then go to flashfire again select just the flash option and select the xposed file click flash then phone will reboot flash xposed then boot up again...... i know its quiet a few steps but its the easiest way to get a custom rom on the canadian s5 active
link to the telus 5.0 https://www.androidfilehost.com/?w=search&s=g870w
xposed link http://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3113463 choose the snapdragon one
currently using g900f phoenix rom 11.0 with no problems at all tested with popwiz and scorpion rom as well also now the tgp g900x rom

Thanks for the detailed information man. I wish I'd find as detailed information about my S6
I'm far from geek and I'm. Totally lost into this forum. And from being Canadian I feel like everything is a little more complicated. I never find anything for Canadian version. Same when I had my s3 any s5 active. Luckily someone pointed me step by step.
So take it as a help call ?.
Cheers

I've been look for a way to use diff ROM on my S5 Active. Mine is from Bell, will your procedure work on my phone?
Thanks.

S5 Active Bell
Hello jayandcourt2,
I followed your instructions but instead of using boot.img from Telus' stock ROM I used the ones from Bell (G870WVLU1BOL1_G870WOYA1BOL1_BMC.zip)
I tired using "PopWiz Edge Plus 5.1.1 for the Galaxy S5 SM-G900X Snapdragon" discussed on XDA Forum
I deleted boot.img on the Pop Wiz ROM and copied the boot.img I extracted from the stock Bell ROM as per your instruction. Ran Flashfire and added
'Wipe' and 'Flash ZIP or OTA' actions (Wipe the first action). After flashing it booted up OK. I went through the initial setup of the Phone, account name, wifi connection... etc.
I don't know if I actually installed the Pop Wiz ROM. It is still using Touch Wiz, and when I flashed the Xposed framework my phone just went into a boot loop.
Just like it would if the ROM is not deodexed. Would you mind giving me the URL's to some of the custom ROM's you have successfully use using the procedures you described?
Update: I re-did the procedure and I noticed during the flashing that I got a message, something like the ROM is for klte device and I have klteactive.
So I guess the custom ROM I have won't work with my G870W.
Thanks mate.
jayandcourt2 said:
figured out how to flash custom roms to the g870w find a rom for an s5 variant that is snapdragon download it use 7zip to open the archive dont extract it (must get the telus ol1 firmware from android file host first ) once you have the ol1 telus firmware extract it with 7zip to a folder that you can remember now go back to the s5 rom you downloaded earlier look for the boot.img in 7zip and delete it then drag and drop the boot.img from the telus firmware that you downloaded........ On the phone make sure to root with cf auto root and install flashfire from the playstore as its vital for this to work as there is no custom recovery for the g870w now once you edit the custom rom you downloaded to include the telus boot.img drag and drop it to your phone open flash fire on the phone click the little plus button select the wipe fucntion then click the plus button again click the flash zip or ota option and select the modified custom rom you just transfered go back to where it shows the rom name and the wipe option hold on the wipe option and drag it to the spot above the rom name then click flash it will reboot and wipe then start flashing the modified custom rom.......if you want xposed download the sdk21 xposed and put it on your phone once it boots then go to flashfire again select just the flash option and select the xposed file click flash then phone will reboot flash xposed then boot up again...... i know its quiet a few steps but its the easiest way to get a custom rom on the canadian s5 active
link to the telus 5.0 https://www.androidfilehost.com/?w=search&s=g870w
xposed link http://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3113463 choose the snapdragon one
currently using g900f phoenix rom 11.0 with no problems at all tested with popwiz and scorpion rom as well also now the tgp g900x rom
Click to expand...
Click to collapse

m3tatr0n84 said:
Hello jayandcourt2,
I followed your instructions but instead of using boot.img from Telus' stock ROM I used the ones from Bell (G870WVLU1BOL1_G870WOYA1BOL1_BMC.zip)
I tired using "PopWiz Edge Plus 5.1.1 for the Galaxy S5 SM-G900X Snapdragon" discussed on XDA Forum
I deleted boot.img on the Pop Wiz ROM and copied the boot.img I extracted from the stock Bell ROM as per your instruction. Ran Flashfire and added
'Wipe' and 'Flash ZIP or OTA' actions (Wipe the first action). After flashing it booted up OK. I went through the initial setup of the Phone, account name, wifi connection... etc.
I don't know if I actually installed the Pop Wiz ROM. It is still using Touch Wiz, and when I flashed the Xposed framework my phone just went into a boot loop.
Just like it would if the ROM is not deodexed. Would you mind giving me the URL's to some of the custom ROM's you have successfully use using the procedures you described?
Update: I re-did the procedure and I noticed during the flashing that I got a message, something like the ROM is for klte device and I have klteactive.
So I guess the custom ROM I have won't work with my G870W.
Thanks mate.
Click to expand...
Click to collapse
Safestrap has been DEAD for years now. The SM-G870A and V versions have a locked boot-loader, W and T versions are luckier, but not to be used with Bootstrap. All we can do on A & V is to root it via Towelroot and Debloat it. Anything else will just brick it. I have tried everything and since Safestrap isn't developed any more, there is no newer Safestrap that would fit version 4 builds.

Thanks ChingghisKhan,
I don't know if owners of G870W are luckier, I tried to install both Clock Work and TWRP recovery and wasn't successful.
I believe it, like the A & V has a locked bootloader. I recently updated my Android OS to Marshmallow and lost
my root. Apparently rooting Marshmallow requires Systemless root and I haven't found any solution yet. Right now I'd
be happy just to get my root back on Android 6. I might have to just go back to Lollipop until someone find out
a way for a Systemless root on G870W.
Cheers.
ChingghisKhan said:
Safestrap has been DEAD for years now. The SM-G870A and V versions have a locked boot-loader, W and T versions are luckier, but not to be used with Bootstrap. All we can do on A & V is to root it via Towelroot and Debloat it. Anything else will just brick it. I have tried everything and since Safestrap isn't developed any more, there is no newer Safestrap that would fit version 4 builds.
Click to expand...
Click to collapse

m3tatr0n84 said:
Thanks ChingghisKhan,
I don't know if owners of G870W are luckier, I tried to install both Clock Work and TWRP recovery and wasn't successful.
I believe it, like the A & V has a locked bootloader. I recently updated my Android OS to Marshmallow and lost
my root. Apparently rooting Marshmallow requires Systemless root and I haven't found any solution yet. Right now I'd
be happy just to get my root back on Android 6. I might have to just go back to Lollipop until someone find out
a way for a Systemless root on G870W.
Cheers.
Click to expand...
Click to collapse
Hi m3tatr0n84,
Sorry to hear about your troubles.
I think the following will get you back to 5.1.1 and root: http://www.droidviews.com/update-att-galaxy-s5-active-to-lollipop-root-it-and-enable-wifi-tethering/
Install Rooted Lollipop ROM on AT&T Galaxy S5 Active
Note:
You can the following instruction of want to update to Lollipop and enjoy root access. Besides, you can install the rooted Lollipop firmware regardless of what firmware or build version your phone currently has.
Preparations
Rooted AT&T Galaxy S5 Active. If you don’t have root access, do as directed below:
Download the following firmware and extract it: G870AUCU1ANE4_Full_Odin.rar
Follow our tutorial to flash the firmware: Link
Then root your Galaxy S5 Active using Towelroot.
Enable USB Debugging on your Galaxy S5 Active. This step has nothing to do with the method given below but it could be a lifesaver if anything goes wrong.
Install Chainfire’s FireFlash app on your AT&T Galaxy S5 Active. Since this new app is only available for beta-testers currently, go to the Google+ page and join the Android-FlashFire community. You must be signed into Google+ using the same Gmail ID that you use on the Google Play Store. Having joined the community, click the Play Store link to download FireFlash.
Download the stock rooted Lollipop firmware for the AT&T Galaxy S5 Active:
G870A_OF3_Stock_Rooted_ROM.zip
G870A_OF2_Stock_Rooted_ROM.zip (older)
Also download the Odin (v3.10.6) OC5 bootloader file: G870A_OC5_Bootloader.tar.md5
Instructions
Copy the G870A_OF3_Stock_Rooted_ROM.zip to your device.
Before you do anything, open SuperSU app on your phone, tap the Settings tab, scroll to Enable su during boot option and enable it.enable-su-during-boot
Open the FlashFire app and “Agree” to the Terms and Conditions prompted by the app.
Press the rounded “+” button twice to bring up the Actions menu.fireflash-app-android
Now tap Flash Zip or OTA option and select the G870A_OF3_Stock_Rooted_ROM.zip.
Make sure that Auto-mount is unchecked under the Options menu and press the check-mark to continue.
From the main menu uncheck all options under EverRoot.
Set the Reboot settings to Download.
When all’s done, tap the Lightning bolt icon followed by OK to begin the installation.
When the installation is finished, your device will reboot automatically into the Download Mode.
Now connect your phone to the PC via USB cable and launch Odin.
Click the PDA/AP button in Odin and select the G870A_OC5_Bootloader.tar.md5 file.
Then hit the Start button to begin the installation.
Your AT&T Galaxy S5 Active will reboot automatically. Just wait patiently for a while. Done!
Enable WiFi Tethering on AT&T Galaxy S5 Active
Note: You must have root access to flash the WiFi Hotspot mod on your phone.
Install FireFlash app by Chainfire (see Method 1 for how to).
Download the Mobile Hotspot mod file and copy the zip to your phone: G870A_OC5_TetherAddOn.zip
Now launch FireFlash and tap the “+” icon twice to bring up the menu and then select Flash Zip or OTA option.
Navigate to G870A_OC5_TetherAddOn.zip file and select it.
Make sure that the Auto-mount option is not selected under Options.
Leave the default settings under EverRoot and Reboot options untouched.
Finally, tap the Lightning bolt icon and then tap OK.
Your phone’ screen will turn black for sometime so do not panic. When it turns up, install the Tether add-on zip file and reboot your device. When your phone boots up, you’ll be able to enjoy free WiFi hotspot on your AT&T Galaxy S5 Active (SM-G870A) running the new OC5 Lollipop firmware.

Thanks., but my carrier is Bell Canada. Will the AT&T ROM work on my S5 Active?
I was able to root the stock Lollipop using CF-Auto-Root-kltecanactive-kltevlactive-smg870w.zip
Cheers.
ChingghisKhan said:
Safestrap has been DEAD for years now. The SM-G870A and V versions have a locked boot-loader, W and T versions are luckier, but not to be used with Bootstrap. All we can do on A & V is to root it via Towelroot and Debloat it. Anything else will just brick it. I have tried everything and since Safestrap isn't developed any more, there is no newer Safestrap that would fit version 4 builds.
Click to expand...
Click to collapse
ChingghisKhan said:
Hi m3tatr0n84,
Sorry to hear about your troubles.
I think the following will get you back to 5.1.1 and root: http://www.droidviews.com/update-att-galaxy-s5-active-to-lollipop-root-it-and-enable-wifi-tethering/
Install Rooted Lollipop ROM on AT&T Galaxy S5 Active
Note:
You can the following instruction of want to update to Lollipop and enjoy root access. Besides, you can install the rooted Lollipop firmware regardless of what firmware or build version your phone currently has.
Preparations
Rooted AT&T Galaxy S5 Active. If you don’t have root access, do as directed below:
Download the following firmware and extract it: G870AUCU1ANE4_Full_Odin.rar
Follow our tutorial to flash the firmware: Link
Then root your Galaxy S5 Active using Towelroot.
Enable USB Debugging on your Galaxy S5 Active. This step has nothing to do with the method given below but it could be a lifesaver if anything goes wrong.
Install Chainfire’s FireFlash app on your AT&T Galaxy S5 Active. Since this new app is only available for beta-testers currently, go to the Google+ page and join the Android-FlashFire community. You must be signed into Google+ using the same Gmail ID that you use on the Google Play Store. Having joined the community, click the Play Store link to download FireFlash.
Download the stock rooted Lollipop firmware for the AT&T Galaxy S5 Active:
G870A_OF3_Stock_Rooted_ROM.zip
G870A_OF2_Stock_Rooted_ROM.zip (older)
Also download the Odin (v3.10.6) OC5 bootloader file: G870A_OC5_Bootloader.tar.md5
Instructions
Copy the G870A_OF3_Stock_Rooted_ROM.zip to your device.
Before you do anything, open SuperSU app on your phone, tap the Settings tab, scroll to Enable su during boot option and enable it.enable-su-during-boot
Open the FlashFire app and “Agree” to the Terms and Conditions prompted by the app.
Press the rounded “+” button twice to bring up the Actions menu.fireflash-app-android
Now tap Flash Zip or OTA option and select the G870A_OF3_Stock_Rooted_ROM.zip.
Make sure that Auto-mount is unchecked under the Options menu and press the check-mark to continue.
From the main menu uncheck all options under EverRoot.
Set the Reboot settings to Download.
When all’s done, tap the Lightning bolt icon followed by OK to begin the installation.
When the installation is finished, your device will reboot automatically into the Download Mode.
Now connect your phone to the PC via USB cable and launch Odin.
Click the PDA/AP button in Odin and select the G870A_OC5_Bootloader.tar.md5 file.
Then hit the Start button to begin the installation.
Your AT&T Galaxy S5 Active will reboot automatically. Just wait patiently for a while. Done!
Enable WiFi Tethering on AT&T Galaxy S5 Active
Note: You must have root access to flash the WiFi Hotspot mod on your phone.
Install FireFlash app by Chainfire (see Method 1 for how to).
Download the Mobile Hotspot mod file and copy the zip to your phone: G870A_OC5_TetherAddOn.zip
Now launch FireFlash and tap the “+” icon twice to bring up the menu and then select Flash Zip or OTA option.
Navigate to G870A_OC5_TetherAddOn.zip file and select it.
Make sure that the Auto-mount option is not selected under Options.
Leave the default settings under EverRoot and Reboot options untouched.
Finally, tap the Lightning bolt icon and then tap OK.
Your phone’ screen will turn black for sometime so do not panic. When it turns up, install the Tether add-on zip file and reboot your device. When your phone boots up, you’ll be able to enjoy free WiFi hotspot on your AT&T Galaxy S5 Active (SM-G870A) running the new OC5 Lollipop firmware.
Click to expand...
Click to collapse

m3tatr0n84 said:
Thanks., but my carrier is Bell Canada. Will the AT&T ROM work on my S5 Active?
I was able to root the stock Lollipop using CF-Auto-Root-kltecanactive-kltevlactive-smg870w.zip
Cheers.
Click to expand...
Click to collapse
Hi m3tatr0n84,
You need to substitute the version that fits your phone, i.e. "W" or which ever you have. http://www.sammobile.com/firmwares/
I am using "A" here in Mongolia with any carrier, also works in Germany, India, etc...

Root Kitkat/Lollipop KNOX 0X0

​I searched but couldn't find a proper guide to do what the title says..
Whatever is mentioned in pieces here and there aren't detailed enough for a starter..
Thanks to
@geohot for TowelRoot
@Chainfire for Mobile Odin Lite/Pro and SuperSU
@joeykrim for Root Checker
@Wrathlon for the pit file (I registered on XDA just to Thank him - he helped me overcome Boot Loop with that pit file when I installed the 1st Poland Kitkat firmware) :highfive:
Please let me know if I am missing crediting someone else.. :angel:
TowelRoot won't function on recent Kitkat firmwares because geohot has been hired by Google and therefore, the loophole was fixed (t​​his is what I've read on XDA-not very sure about it though it makes sense)..
Mobile Odin Lite/Pro won't function on latest Kitkat firmwares & any of the Lollipop firmwares.
Now, moving on..
I own the 32 GB International variant of Samsung Galaxy Note (from UK), Model : SM-N9005 to be precise, I am not sure if this works on other models of Note 3 or not
I am gonna mention here the steps that I followed, in a manner as precise as I can enlist..
I'll also gonna try to do so in a manner that's as elaborate as I can make it.. Therefore, some steps might seem obvious and/or extra
If you still find yourself in any doubt-do let me know..
Strong Personal Advice -
Please read the steps twice before you actually start following them
Because these are all Official Firmwares that we're gonna be using, you don't need to turn on ADB (Android Debugging) in Developer Options.
Requirements
Install latest Samsung USB Driver for Mobile Phones (current latest can be downloaded from here).
Download and extract N9005XXUEND3_BTU
Download and extract N9005XXUGNG1_BTU
(only if you want to your device to be finally on Lollipop), download and extract N9005XEOGBOA4_XEO (you can find all of these here at Sammobile.com or Samsung-Updates.com
Download the archive from the attachment & extract it. It contains a pit file, Odin v3.09 (newer versions are available too, I provided with this version so that snapshots don't differ), SuperSU v2.46, Root Checker (so you won't need to visit Play Store when your phone would be lagging after downgrading) SuperSU v2.46.zip & TowelRoot (so you won't need to visit their respective websites when your phone would be lagging after downgrading)
I request you guys to visit these websites before & or after this process to donate to their creators.
Guys! Please do so.
You'll also need Mobile ODIN Pro which can be bought from here.
Back up your data & ensure that your phone is charged 80% or more
Downgrade to N9005XXUEND3_BTU
Use Odin v3.09 & flash your phone with the N9005XXUEND3_BTU tar.md5 file & use the pit file that I provided in the attachments
Make sure that before you hit the Start button, it matches this snapshot-
{
"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"
}
The actual name & path of files will differ, just ensure that the same options are Ticked/Unticked
Let the device boot normally, a seeming Boot Loop might be encountered (I encountered it), don't worry, let it Boot Loop several times, finally, it'll Start
It'll lag (mine lagged badly ), will not have any Network signal/IMEI
Don't panic & be patient with your phone, you might need to pull out the battery if it goes totally unresponsive (mine did), but it'll manage to get the work done & be better with the operations after some time.
Connect it to the same PC as before (if you removed it after flashing it)
Copy the extracted tar.md5 from N9005XXUGNG1_BTU archive, SuperSU v2.46.apk & TowelRoot.apk into the phone's internal memory
Install TowelRoot.apk & Root using the app (reboot won't be required-I didn't need to)
Install SuperSU v2.46.apk & let it update SU binaries
Tick on Enable Pro in SuperSU, it'll restart itself
Tick on Survival Mode in SuperSU
Restart your phone now.
Use Root Checker, grant it SuperSU access & you should have Root access now.
Upgrade to N9005XXUGNG1_BTU
Purchase Mobile ODIN Pro & run it (grant it Root access)
In Mobile ODIN Pro, use the Open file option & choose the extracted tar.md5 from N9005XXUGNG1_BTU archive (it should be in the Internal SD-card if you've followed the steps precisely
choose Enable Ever Root
choose Inject Superuser
choose Wipe data and cache
choose Wipe Dalvik cache
Tap on the Flash Firmware option & then tap on Continue to go ahead with the flashing process
You might wanna plug in your phone's AC charger to avoid any power shortage during this critical phase.
Let the phone boot up, use Root Checker.
Phewwwww..... :victory:
Your phone should now have the Stock Firmware which is Rooted & KNOX 0x0
:laugh:
You can remove your phone from charging now.
But, if Lollipop is what you desire to have rooted on your phone, you'll have to follow these steps too..
Upgrade to Lollipop N9005XEOGBOA4_XEO
Put SuperSU zip in a folder in your SD Card (external SD recommended)
Put Lollipop ROM (N9005XEOGBOA4_XEO.TAR.MD5) in your SD Card (external SD recommended)
On Mobile Odin Pro, touch on "Open file ..." load the TAR.MD5 file and confirm
Then touch on "OTA / Update ZIP" and select the SuperSU v2.46.zip
Untick the Enable Ever Root box.
Tick the Wipe data and cache box.
Tick the Wipe Dalvik cache box.
Tap on the Flash Firmware option & then tap on Continue to go ahead with the flashing process
You might wanna plug in your phone's AC charger to avoid any power shortage during this critical phase.
Let the phone boot up, use Root Checker.
:victory:
Your phone should now have the Lollipop Stock Firmware which is Rooted & KNOX 0x0
:laugh:
You can remove your phone from charging now.
Note : The bootloader won't upgrade in this method.
DOWNGRADE POSSIBILITY TO KITKAT AFTER GOING TO LOLLIPOP?
Please read this.. :highfive:
Click on the following line for
LOLLIPOP 5.0 STOCK ROM MODS
Note : I take no responsibility for any damage that you bring to your phone, I just gathered information from XDA & some other websites (I don't remember which all) & used them myself - use them at your own risk.
Skip typing - hit
instead..

Waiting for the first tested users))) And why using PIT file? If I'm already use 4.4.2 with root and KNOX 0x0, that I not need firmware with PIT?

alex3n said:
Waiting for the first tested users))) And why using PIT file? If I'm already use 4.4.2 with root and KNOX 0x0, that I not need firmware with PIT?
Click to expand...
Click to collapse
4/5 current Thanks for the OP are there because it works for them..
1/5 current Thanks is from one of the developers whose app has been mentioned here, Root Checker's developer to be precise..

I would be very very wary of using PIT as many brick the phone .
I flashed using the original posts that this thread expands upon but at the boot loop just flashed Modem NF2 and rebooted .

JJEgan said:
I would be very very wary of using PIT as many brick the phone .
I flashed using the original posts that this thread expands upon but at the boot loop just flashed Modem NF2 and rebooted .
Click to expand...
Click to collapse
I did the "almost same steps" twice because sometimes (with these 2 Kitkat firmwares) the Bootloader won't update..

I used this instruction to root KitKat.
http://forum.xda-developers.com/galaxy-note-3/general/root-root-xxufnf4-stock-firmware-knox-t2840150
Apparently, you don't need to downgrade. Flashing old kernel is enough to use towelroot.

I'm already on N9005XXUEND3, rooted with TowelRoot with Knox 0x0.
Can I directly upgrade to Lollipop or I have to upgrade to N9005XXUGNG1 before?

cinciopillo said:
I'm already on N9005XXUEND3, rooted with TowelRoot with Knox 0x0.
Can I directly upgrade to Lollipop or I have to upgrade to N9005XXUGNG1 before?
Click to expand...
Click to collapse
Great.. :good:
You can directly jump to Lollipop.. :highfive:
Skip typing - hit
instead..

Still on Jelly Bean
I am still on JB - MJ3 (see in my signature). Rooted with Towelroot
Can I use this method but skipping the UEND3 ?
Also does this do the modem etc or is it just kernel?

louiscar said:
I am still on JB - MJ3 (see in my signature). Rooted with Towelroot
Can I use this method but skipping the UEND3 ?
Also does this do the modem etc or is it just kernel?
Click to expand...
Click to collapse
Yes, you can..
It'll upgrade everything.. Though, if you choose to move to Lollipop in the end-the bootloader will not upgrade and it'll stay to that version of Kitkat upon which you'll install it (Lollipop).. :good:

TheTAMAS said:
Yes, you can..
It'll upgrade everything.. Though, if you choose to move to Lollipop in the end-the bootloader will not upgrade and it'll stay to that version of Kitkat upon which you'll install it (Lollipop).. :good:
Click to expand...
Click to collapse
Is that a bad thing or is it ok to have the KK bootloader?
So to be clear, I just go from "Upgrade to N9005XXUGNG1_BTU" with mobile Odin?
My region is UK which is a non-branded phone. I think BTU is the correct version for this (supports 4G)?

im on 4g updated to lollipop polish version using mobile odin i then installed lollipop bootloader seperate using odin knox will stay 0x0 too

louiscar said:
Is that a bad thing or is it ok to have the KK bootloader?
So to be clear, I just go from "Upgrade to N9005XXUGNG1_BTU" with mobile Odin?
My region is UK which is a non-branded phone. I think BTU is the correct version for this (supports 4G)?
Click to expand...
Click to collapse
There might be some bugs..
I was personally facing bad battery performance but others reported that they didn't feel that way..
EDIT:Yes, BTU is correct.. I've the same device..
stesteste said:
im on 4g updated to lollipop polish version using mobile odin i then installed lollipop bootloader seperate using odin knox will stay 0x0 too
Click to expand...
Click to collapse
That's great..
Could you please share with us the link to the bootloader, I'll update the OP with it and give credit to you.. :highfive:

TheTAMAS said:
There might be some bugs..
I was personally facing bad battery performance but others reported that they didn't feel that way..
EDIT:Yes, BTU is correct.. I've the same device..
That's great..
Could you please share with us the link to the bootloader, I'll update the OP with it and give credit to you.. :highfive:
Click to expand...
Click to collapse
Thanks, I'll probably go in stages. KK first.
 @stesteste I also second that request for details of bootloader information and can you tell us the exact steps you took and from what firmware you updated?

yeah ill just find it guys i might have it on phone otherwise its on my pc ...be back soon
---------- Post added at 02:08 PM ---------- Previous post was at 01:42 PM ----------
havent got the bootloar tar at hand but its in this post somewhere if you want to go through them ..sry not at home for now so no pc
followed these instructions
http://forum.xda-developers.com/showthread.php?t=3029557

Does this method of obtaining a Knox 0x0 root on Lollipop extend to other Lollipop ROM's, or only the one listed in the OP?
For example would it work with a newer ROM, or with the UKO2 latest release?
I literally only want root to be able to use Titanium Backup, having just had the pain of losing everything following an unintentional factory reset (don't ask!)

SilverHelmut said:
Does this method of obtaining a Knox 0x0 root on Lollipop extend to other Lollipop ROM's, or only the one listed in the OP?
For example would it work with a newer ROM, or with the UKO2 latest release?
I literally only want root to be able to use Titanium Backup, having just had the pain of losing everything following an unintentional factory reset (don't ask!)
Click to expand...
Click to collapse
It'll work on others too.. :highfive:

TheTAMAS said:
It'll work on others too.. :highfive:
Click to expand...
Click to collapse
That's awesome!
Now... please excuse my ignorance, I'm such a 'casual' user, it's almost pathetic how unadventurous I am and how intimidated by 'warranty status' I am...
But...
Could you possibly explain to me whether there is any inherent disadvantage in me using this method over, say, simply having a stock unrooted Lollipop?
Does it create any inherent instability or issues that I should be aware of?
And do you by any chance know of a better stock unbranded Lollipop ROM which will work better or with greater stability than the current UK O2 offering?

SilverHelmut said:
That's awesome!
Now... please excuse my ignorance, I'm such a 'casual' user, it's almost pathetic how unadventurous I am and how intimidated by 'warranty status' I am...
But...
Could you possibly explain to me whether there is any inherent disadvantage in me using this method over, say, simply having a stock unrooted Lollipop?
Does it create any inherent instability or issues that I should be aware of?
And do you by any chance know of a better stock unbranded Lollipop ROM which will work better or with greater stability than the current UK O2 offering?
Click to expand...
Click to collapse
None that I'm aware of..
EDIT:I mentioned in my previous replies that, the bootloader will not be upgraded to the one that comes with Lollipop if you upgrade to Lollipop with this method..
The difference is that in unbranded roms, bloatware is less than those found in a carrier rom..
On the contrary, a carrier can choose not to include some feature or pre loaded app from the manufacturer.. For eg-in the US, a carrier removed Microsoft Apps from it's version of S6 rom (you can say that the carrier removed some bloatware this time).. :laugh:

Oh, I forgot to add... does it work with other 'KK' firmwares as the 'starting place'? Are there newer KK's that this method will also accommodate as the baseline to root and then install Lollipop and keep root and 0x0?

Temp root on 7.0 N920VVRS3CRH1

I mean its with SuperSU and of course doesn't survive a reboot and still can't figure out anyway to write to /system..
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

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

https://github.com/gfunkmonk/N920V_7_TMPROOT

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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