Database Develop

Nvidia SHIELD Portable Root

Hi everyone!
This morning I woke up to find my SHIELD with the so waited notification of Lollipop update. I'm really happy to finally have lollipop running on my device, but sadly I found a problem after the update. I was trying to re-root my device, but neither the SHIELD RAM tool or Root Genius could do the trick. But I didn't gave up, I searched in Google any way to root my SHIELD with the still fresh update, and found that the Kinguser app can root it without trouble.
You just need to download the apk, install it on your SHIELD and open it.
Btw, the old recovery isn't working anymore, you can flash it with the RAM tool, but the device will reflash the stock recovery.

twrp works, but SU binary still wont flash :/
edit - the combination of this APK and TWRP gave me all I need for root + rebooting and keeping root

Yeah, I was about to say that. The TWRP recovery works like a charm, but Supersu binary won't install. But well, the KingRoot app is pretty good.

I can confirm some problem with supersu and update 103. I flashed 2.46 and my portable wouldn't boot. Like, something broke so bad I had to reflash 101 and update again. The later might indicate backups are broke in my twrp, I'll have to look into that. For now, I'm going try kingroot as suggested here and continue other development.

Steel01 said:
I can confirm some problem with supersu and update 103. I flashed 2.46 and my portable wouldn't boot. Like, something broke so bad I had to reflash 101 and update again. The later might indicate backups are broke in my twrp, I'll have to look into that. For now, I'm going try kingroot as suggested here and continue other development.
Click to expand...
Click to collapse
So you were successful in getting TWRP installed, SuperSU installed and removing KingRoot clean - leaving only SuperSU on the system, surviving a reboot?

Ink Rampant Wolf said:
Yeah, I was about to say that. The TWRP recovery works like a charm, but Supersu binary won't install. But well, the KingRoot app is pretty good.
Click to expand...
Click to collapse
hey wolf, what is the easiest way to flash twrp with the 103 upgrade? thanks

You might wanna include the instructions as shown here,
http://forum.xda-developers.com/xpe...how-to-root-lollipop-xperia-tablet-z-t3115107
It basically tells you how to install SuperSU and remove the entire KingRoot library after that. It worked on my Z and on my SHIELD as well.

This was essentially what I did:
http://greenrobotgamer.com/shieldzone/root-shield-portable-lollipop-5-1/

Mine seems to be working just fine, after obtaining root and installing SuperSU. I didn't bother with installing TWRP, I just hotboot the recovery. I'm rebooting my SHIELD as we speak, see if there's any issue
EDIT: Scractch that, it's not booting. How do I flash the latest image back in?

JCESAR2 said:
hey wolf, what is the easiest way to flash twrp with the 103 upgrade? thanks
Click to expand...
Click to collapse
Boot the SHIELD in fastboot and connect it to your pc, then open a command window in a folder with the adb files and the recovery image and type: fastboot flash recovery -the name of the recover-.img, and it will flash the recovery. You can do that with the stock too.
Sent from my HUAWEI P7-L12 using My-RoM V3.3.
Ask if you have doubts or problems, we're here to help.

Ink Rampant Wolf said:
Boot the SHIELD in fastboot and connect it to your pc, then open a command window in a folder with the adb files and the recovery image and type: fastboot flash recovery -the name of the recover-.img, and it will flash the recovery. You can do that with the stock too.
Sent from my HUAWEI P7-L12 using My-RoM V3.3.
Ask if you have doubts or problems, we're here to help.
Click to expand...
Click to collapse
thanks for the reply, also, when i boot the shield into fastboot it says in the first line : boot loader version ..../ device locked, does that matter? i rooted the shield already with kingroot.

JCESAR2 said:
thanks for the reply, also, when i boot the shield into fastboot it says in the first line : boot loader version ..../ device locked, does that matter? i rooted the shield already with kingroot.
Click to expand...
Click to collapse
You need to unlock your bootloader first.

ok long story short: since i had the shield drivers installed and tha adb drivers installed i did the oem unlock and after a confirmation screen on the shield i did it, then i immediately flashed the twrp image from the same command line. now the shield is stuck in nvidia android boot logo. any suggestions? thanks

I am in fact stuck in the boot as well. Anyone's got stock image we can flash?

nevermind, after like 10 minutes the thing just booted fine, these are the perks of being a newb.

341464 said:
I am in fact stuck in the boot as well. Anyone's got stock image we can flash?
Click to expand...
Click to collapse
JCESAR2 said:
nevermind, after like 10 minutes the thing just booted fine, these are the perks of being a newb.
Click to expand...
Click to collapse
Search for the SHIELD RAM Tool, it have everything that you all need to flash recovery or old firmware to unbrick the device. It also comes with the necessary files and drivers to work ADB Fastboot.
Sent from my HUAWEI P7-L12 using My-RoM V3.3.
Ask if you have doubts or problems, we're here to help.

Ink Rampant Wolf said:
Search for the SHIELD RAM Tool, it have everything that you all need to flash recovery or old firmware to unbrick the device. It also comes with the necessary files and drivers to work ADB Fastboot.
Sent from my HUAWEI P7-L12 using My-RoM V3.3.
Ask if you have doubts or problems, we're here to help.
Click to expand...
Click to collapse
Guess I'll have to flash the old firmware then, it's been sitting there forever.

341464 said:
I am in fact stuck in the boot as well. Anyone's got stock image we can flash?
Click to expand...
Click to collapse
try this shield thread
http://forum.xda-developers.com/showthread.php?t=2388870

JCESAR2 said:
try this shield thread
http://forum.xda-developers.com/showthread.php?t=2388870
Click to expand...
Click to collapse
I just re-flashed the system using RAM, should be fine now. I'll just have wait for the OTA all over again. UGH.
I wish someone could provide a KitKat version tho.
EDIT: Annnd battery's at 15% so the system won't let me OTA yet.

SuperSU will work fine with my latest TWRP builds posted here. The older 2.8.5.0 builds will not work, neither will any build in the linked thread before yesterday. I used SuperSU 2.49 Beta and it worked as expected.
Side Note: The older builds will have the problem where boot will just hang. That seems to be because the older builds didn't have selinux policies built in, so some things never get set up right and the boot panics.

LMY48I update error

Hey.
My N6 got an error after I tried to update. I saw somewhere that installing the update on a rooted device (stock everything, just root) would be successful but it would remove root. Tried and got the error message with the android guy and a warning sign or something like that just with the "error" text, no more. I unrooted and rebooted, after some time the update prompted again and tried, same result.
I did some searches and just a few people have commented this issue, no answers yet.
Any ideas?

OscarBrito said:
Hey.
My N6 got an error after I tried to update. I saw somewhere that installing the update on a rooted device (stock everything, just root) would be successful but it would remove root. Tried and got the error message with the android guy and a warning sign or something like that just with the "error" text, no more. I unrooted and rebooted, after some time the update prompted again and tried, same result.
I did some searches and just a few people have commented this issue, no answers yet.
Any ideas?
Click to expand...
Click to collapse
Has to be completely stock. No root, custom kernel or recovery. How did you unroot. Have to flash factory image to remove root. Can't just remove the app. Forget OTAs if you are gonna root. Have to reflash factory image anyway so might as well just flash the updated image.

KingRoot
prdog1 said:
Has to be completely stock. No root, custom kernel or recovery. How did you unroot. Have to flash factory image to remove root. Can't just remove the app. Forget OTAs if you are gonna root. Have to reflash factory image anyway so might as well just flash the updated image.
Click to expand...
Click to collapse
I did with King Root, that thing works like a charm, Here's the thread. It has an option to remove root, the root manager disappeared, I rebooted and checked with a root checker and it says that I'm not rooted, still I get the error message when trying to update.

OscarBrito said:
I did with King Root, that thing works like a charm, Here's the thread. It has an option to remove root, the root manager disappeared, I rebooted and checked with a root checker and it says that I'm not rooted, still I get the error message when trying to update.
Click to expand...
Click to collapse
Your system is still modified. Even if remove the files the partition has been modified. If you have custom recovery or kernel it also won't flash. Have to flash back to stock so might as well just fastboot the updated factory image.

OscarBrito said:
I did with King Root, that thing works like a charm, Here's the thread. It has an option to remove root, the root manager disappeared, I rebooted and checked with a root checker and it says that I'm not rooted, still I get the error message when trying to update.
Click to expand...
Click to collapse
None of the unroot options put things back to 100% stock. They just remove root. The only way to remove all traces is to fastboot flash the system.img
If you're going to run rooted, forget about OTA and learn about fastboot.
General > sticky roll-up > adb and fastboot

Reset
prdog1 said:
Your system is still modified. Even if remove the files the partition has been modified. If you have custom recovery or kernel it also won't flash. Have to flash back to stock so might as well just fastboot the updated factory image.
Click to expand...
Click to collapse
Can I backup, do a factory data reset and then do the update? Then root again and restore my stuff.

OscarBrito said:
Can I backup, do a factory data reset and then do the update? Then root again and restore my stuff.
Click to expand...
Click to collapse
Nope. Have to flash stock image as posted above.

prdog1 said:
Nope. Have to flash stock image as posted above.
Click to expand...
Click to collapse
Dang. I don't like to mess with flashing and custom recoveries but I guess now I most.
I'm looking at Flashify. Download the stock image with the patch already on it and flash it that way. Do you recommend doing it that way?
Another thing, Any good and simple backup tool? I just want to skip the part where I need to configure everything again.

OscarBrito said:
Dang. I don't like to mess with flashing and custom recoveries but I guess now I most.
I'm looking at Flashify. Download the stock image with the patch already on it and flash it that way. Do you recommend doing it that way?
Another thing, Any good and simple backup tool? I just want to skip the part where I need to configure everything again.
Click to expand...
Click to collapse
You can't flash the stock image with flashify. Use fastboot as I have already advised.
Titanium backup is a great backup app, but you won't wipe the device if you only flash the system.img, boot.img and radio.img

danarama said:
You can't flash the stock image with flashify. Use fastboot as I have already advised.
Titanium backup is a great backup app, but you won't wipe the device if you only flash the system.img, boot.img and radio.img
Click to expand...
Click to collapse
Sorry for so many questions mate, but I run linux and for reasons I try to avoid getting into my W8 partition.

OscarBrito said:
Sorry for so many questions mate, but I run linux and for reasons I try to avoid getting into my W8 partition.
Click to expand...
Click to collapse
Fastboot works with Linux also.

OscarBrito said:
Sorry for so many questions mate, but I run linux and for reasons I try to avoid getting into my W8 partition.
Click to expand...
Click to collapse
No worries. Linux is even easier. You just stick the fastboot binaries in /usr/bin
Note, you'll probably need to use sudo / su to call fastboot.

danarama said:
No worries. Linux is even easier. You just stick the fastboot binaries in /usr/bin
Note, you'll probably need to use sudo / su to call fastboot.
Click to expand...
Click to collapse
If all this stuff is needed I better go all in and get AOSiP.
Gonna do it with Nexus Root Toolkit, get TWRP and flash the ROM.
I'm kinda new to this kind of stuff, I use ArchLinux and mess with my computer like there's no tomorrow but doing stuff with a phone can brick it. So, any last advice?
Thanks both in advance.

OscarBrito said:
If all this stuff is needed I better go all in and get AOSiP.
Gonna do it with Nexus Root Toolkit, get TWRP and flash the ROM.
I'm kinda new to this kind of stuff, I use ArchLinux and mess with my computer like there's no tomorrow but doing stuff with a phone can brick it. So, any last advice?
Thanks both in advance.
Click to expand...
Click to collapse
Better chance of bricking it with ToolKit than with manual fastboot. I run stock rooted with TWRP also. Takes 2-3 minutes to update with fastboot. If toolkit fails will most likely need fastboot to fix it anyway.

OscarBrito said:
If all this stuff is needed I better go all in and get AOSiP.
Gonna do it with Nexus Root Toolkit, get TWRP and flash the ROM.
I'm kinda new to this kind of stuff, I use ArchLinux and mess with my computer like there's no tomorrow but doing stuff with a phone can brick it. So, any last advice?
Thanks both in advance.
Click to expand...
Click to collapse
Don't use toolkits unless you can use fastboot..so just use fastboot. I'm not saying this for fun you know...if anything, its quite boring having to say this to everyone on a daily basis
Use fastboot please. Read my fastboot thread. You understand that fastboot is Googles method for flashing Google android on the google nexus? It should be pretty clear that this is the best tool for the job.

danarama said:
Don't use toolkits unless you can use fastboot..so just use fastboot. I'm not saying this for fun you know...if anything, its quite boring having to say this to everyone on a daily basis
Use fastboot please. Read my fastboot thread. You understand that fastboot is Googles method for flashing Google android on the google nexus? It should be pretty clear that this is the best tool for the job.
Click to expand...
Click to collapse
Don't get me wrong, I'm not afraid of a terminal, but well, you are right going with a terminal rather than a tool.
I'm finishing my backup and then doing all this manually, thanks a lot, both.

OscarBrito said:
Don't get me wrong, I'm not afraid of a terminal, but well, you are right going with a terminal rather than a tool.
I'm finishing my backup and then doing all this manually, thanks a lot, both.
Click to expand...
Click to collapse
I can't see how any Linux user would be afraid of terminals

Yeap, just tried to Flash my Super Awesome Nexus 5 with the LMY48I Update Zip file (10mb), via TWRP, while Rooted and I got the Nice Red Error... So I guess I have to download the Factory image LMY48I and via fastboot just flash the system.img if nothing else has been modified since LMY48B... In case I loose Root Access I might just reflash the script via TWRP... I will post update if anyone interested...

imor said:
Yeap, just tried to Flash my Super Awesome Nexus 5 with the LMY48I Update Zip file (10mb), via TWRP, while Rooted and I got the Nice Red Error... So I guess I have to download the Factory image LMY48I and via fastboot just flash the system.img if nothing else has been modified since LMY48B... In case I loose Root Access I might just reflash the script via TWRP... I will post update if anyone interested...
Click to expand...
Click to collapse
You will lose root. Flash supersu from recovery before first boot

Ok, just confirming here before I mess up. I have an international N6 rooted with stock recovery running LMY47Z. I can't update OTA. So I should flash the full stock image and then run cf-auto-root before rebooting.
Is this correct? Will I lose my user data when I do this? If so, what's the easiest way to backup and restore? Can't I flash the 25MB update .zip instead?
Thanks!

I got TWRP and root on magisk here's how.

I have ABSOLUTELY no clue why this works, BUT. Giving credit where credit is due and also a discovery of my own.
@3DSammy listed 3 different ways to get TWRP on the 5. One of them was VERY VERY CLOSE. They suggested a seperate usb port which was close. What I did was i tried to install TWRP on my surface pro 3 where i originally unlocked my bootloader, but for some reason it refused to let me add TWRP on top. So I grabbed a secondary PC and tried every single USB port on it since the Surface pro 3 only has 1 usb. None of them worked. Tried restarting the pc. Nothing. Tried updating fastboot drivers and uninstalling and reinstalling fastboot drivers. STILL NOTHING
At this point I just got really pissed and force shut my laptop down by holding the power button. Tried it again on my surface to no avail. But once i went back to my other computer i forced down it worked for some reason.... O,o really spooky. So i guess if you want twrp then force shut down a windows PC and try again after it boots. Its just how i got it to work i REALLY hope this works for others because i was steamin. I got my 3t rooted in 2 seconds but this thing. MAAAAN a whole afternoon wasted on such an odd solution. I think it has something to do with the usb ports losing all power then resetting once they receive power again.
Take all this with a grain of salt, i dont know if this will work for you but lots of folks seem to be having issues with getting TWRP running.
Also yes, magisk does work normally and passes safetynet.

hey man, i'm wodering which version of magisk did you choose for oneplus 5?

ihead said:
hey man, i'm wodering which version of magisk did you choose for oneplus 5?
Click to expand...
Click to collapse
I recommend using the latest beta (v13)
---------- Post added at 07:22 AM ---------- Previous post was at 07:21 AM ----------
OcazPrime said:
I have ABSOLUTELY no clue why this works, BUT. Giving credit where credit is due and also a discovery of my own.
@3DSammy listed 3 different ways to get TWRP on the 5. One of them was VERY VERY CLOSE. They suggested a seperate usb port which was close. What I did was i tried to install TWRP on my surface pro 3 where i originally unlocked my bootloader, but for some reason it refused to let me add TWRP on top. So I grabbed a secondary PC and tried every single USB port on it since the Surface pro 3 only has 1 usb. None of them worked. Tried restarting the pc. Nothing. Tried updating fastboot drivers and uninstalling and reinstalling fastboot drivers. STILL NOTHING
At this point I just got really pissed and force shut my laptop down by holding the power button. Tried it again on my surface to no avail. But once i went back to my other computer i forced down it worked for some reason.... O,o really spooky. So i guess if you want twrp then force shut down a windows PC and try again after it boots. Its just how i got it to work i REALLY hope this works for others because i was steamin. I got my 3t rooted in 2 seconds but this thing. MAAAAN a whole afternoon wasted on such an odd solution. I think it has something to do with the usb ports losing all power then resetting once they receive power again.
Take all this with a grain of salt, i dont know if this will work for you but lots of folks seem to be having issues with getting TWRP running.
Also yes, magisk does work normally and passes safetynet.
Click to expand...
Click to collapse
Did you decrypt before installing Magisk?

Im using beta 13 and i dont know anything about the decryption so im guessing no im not. But i think i know wjat you mean. When i went into twrp the first time it asked for my pattern. So i drew that and it worked perfectly. I think maybe that decrypted it. Twrp and magisk work 100%

OcazPrime said:
Im using beta 13 and i dont know anything about the decryption so im guessing no im not. But i think i know wjat you mean. When i went into twrp the first time it asked for my pattern. So i drew that and it worked perfectly. I think maybe that decrypted it. Twrp and magisk work 100%
Click to expand...
Click to collapse
I just asked because it seems that Magisk can't work if your device is decrypted

Didn't know that. But, no it's working perfectly fine. I used the test twrp build on the stable twrp 3.1.1 thread. Everything went great, no reason to flash anything else. Stock is king.

i have tried to used magisk v12 and it didn't work perfectly, specificialy 3C System Tuner doesn't get the root permission correctly then i have to use supersu 2.8.2
so if you want to root you OP5 , magisk v13 or supersu is recommended

If I'm already rooted with SuperSU, would it be pretty easy to unroot and then root using the latest beta of Magisk?
It looks like this modified the boot image, would this cause problem when taking updates or would we simply just need to reflash Magisk after?

geoff5093 said:
If I'm already rooted with SuperSU, would it be pretty easy to unroot and then root using the latest beta of Magisk?
It looks like this modified the boot image, would this cause problem when taking updates or would we simply just need to reflash Magisk after?
Click to expand...
Click to collapse
You won't be able to update OTA because your stock recovery is gone. You'll need to download the full ROM and flash it in TWRP every time an update comes. You can uninstall SuperSU and put Magisk v13. I currently have it, works perfect and safety net passes.

geoff5093 said:
If I'm already rooted with SuperSU, would it be pretty easy to unroot and then root using the latest beta of Magisk?
It looks like this modified the boot image, would this cause problem when taking updates or would we simply just need to reflash Magisk after?
Click to expand...
Click to collapse
If you do the OTA through the official update method in the settings, it will say that you have a rooted device and the entire package will need to be flashed. Then TWRP will flash it and the phone will update correctly. However, you lose root, as well as TWRP. So then you have to fastboot flash recovery and then flash Magisk to get back to where you were.
I did it last night.

ArkAngel06 said:
If you do the OTA through the official update method in the settings, it will say that you have a rooted device and the entire package will need to be flashed. Then TWRP will flash it and the phone will update correctly. However, you lose root, as well as TWRP. So then you have to fastboot flash recovery and then flash Magisk to get back to where you were.
I did it last night.
Click to expand...
Click to collapse
Once you flash the full zip, flash magisk BEFORE you got into the phone, you will keep root and that also keeps the stock recovery from overwriting TWRP. So you keep root and TWRP. After flashing full zip.
This is for future reference so you do go through that again.

Eric214 said:
Once you flash the full zip, flash magisk BEFORE you got into the phone, you will keep root and that also keeps the stock recovery from overwriting TWRP. So you keep root and TWRP. After flashing full zip.
This is for future reference so you do go through that again.
Click to expand...
Click to collapse
Hmm, I can't remember if it auto rebooted or not now, but thanks for the tip.

[Q][HELP] OP3T Soft bricked after installing TWRP Recovery

Today, after i installed the latest OOS 5.0.1 with Android O 8.0, i decided to root my device.
After successfully unlocking the bootloader, i flashed the TWRP Recovery and flashed the SuperSU zip, i was stuck on the 1+ Boot logo. I tried fixing the contents through advanced options of TWRP recovery and still no luck. I also tried wiping my cache, data, dalvik etc...
So far i tried:
Installed stock recovery via fastboot, then adb sideload. My device was recognized when typing ADB Devices but when i tried to adb sideload ota.zip i got the cannot read *...zip* error. Then i tried everything i could find, my devices are installed correctly, i also tried the Large Address Awarness program and still no luck.
Then i flashed TWRP again through fastboot and try to do the same through TWRP's sideload. Still no luck
Then i tried to adb push the ota.zip so i can install it manually through TWRP recovery.. still no luck
I ran out of ideas.... What can i do?
Thanks in advance

First of all, why didn't you make a TWRP backup of the stock ROM before trying to root? This is best practice before trying any mods (root, flashing ROMs) for reasons which are probably now obvious. I'm always surprised at how many folks skip this step.
Maybe you planned ahead of time to use the stock recovery image, if you had to. But since it wasn't on the phone when you need it, you're running into the problem of getting it on there now.
Yiannis75 said:
i flashed the TWRP Recovery and flashed the SuperSU zip
Click to expand...
Click to collapse
What version TWRP, and what version SuperSU?
Honestly, I would recommend Magisk for root, over SuperSU. I've seen a number of folks have problems with recent version SuperSU on this device. And Magisk has a lot of really cool, useful features. I'm normally not one to recommend one method over another. Especially since SuperSU was so tried and true for so long. But at this point, I see no benefit of using SuperSU, but many benefits to Magisk. And seemingly less problems rooting with Magisk. My recommendation would be current version Magisk, which is v16.0.
Yiannis75 said:
Then i tried to adb push the ota.zip so i can install it manually through TWRP recovery.. still
Click to expand...
Click to collapse
First of all, make sure you are using the "full" update zip (which will be >1 GB) and not the partial OTA "patch". You can get the full zip from here (Post #2): https://forum.xda-developers.com/oneplus-3t/how-to/official-oxygenos-5-0-1-android-8-0-t3728119
Since you have TWRP installed, boot into TWRP. You should be able to see your internal storage on your computer, just like it's a thumb drive. Just drag/copy and drop the full OTA zip onto the phone's internal storage. Then just flash the zip in TWRP.
The internal storage should be selected to "Mount" in TWRP by default. But if you can't see internal storage on your computer, make sure it's selected in the TWRP "Mount" section.

Yiannis75 said:
Today, after i installed the latest OOS 5.0.1 with Android O 8.0, i decided to root my device.
After successfully unlocking the bootloader, i flashed the TWRP Recovery and flashed the SuperSU zip, i was stuck on the 1+ Boot logo. I tried fixing the contents through advanced options of TWRP recovery and still no luck. I also tried wiping my cache, data, dalvik etc...
So far i tried:
Installed stock recovery via fastboot, then adb sideload. My device was recognized when typing ADB Devices but when i tried to adb sideload ota.zip i got the cannot read *...zip* error. Then i tried everything i could find, my devices are installed correctly, i also tried the Large Address Awarness program and still no luck.
Then i flashed TWRP again through fastboot and try to do the same through TWRP's sideload. Still no luck
Then i tried to adb push the ota.zip so i can install it manually through TWRP recovery.. still no luck
I ran out of ideas.... What can i do?
Thanks in advance
Click to expand...
Click to collapse
Which exact version of TWRP did you install?
Are you Greek btw?
Unleashed by my rooted OP3T on 8.0

RASTAVIPER said:
Which exact version of TWRP did you install?
Are you Greek btw?
Unleashed by my rooted OP3T on 8.0
Click to expand...
Click to collapse
I believe i used TWRP 3.2.1-0... the very latest
And yeah am cypriot

Yiannis75 said:
I believe i used TWRP 3.2.1-0... the very latest
Click to expand...
Click to collapse
You can verify by booting to TWRP. It says version number on the splash screen.
Did you look at, or try my recommendations in my last response?

redpoint73 said:
First of all, why didn't you make a TWRP backup of the stock ROM before trying to root? This is best practice before trying any mods (root, flashing ROMs) for reasons which are probably now obvious. I'm always surprised at how many folks skip this step.
Maybe you planned ahead of time to use the stock recovery image, if you had to. But since it wasn't on the phone when you need it, you're running into the problem of getting it on there now.
What version TWRP, and what version SuperSU?
Honestly, I would recommend Magisk for root, over SuperSU. I've seen a number of folks have problems with recent version SuperSU on this device. And Magisk has a lot of really cool, useful features. I'm normally not one to recommend one method over another. Especially since SuperSU was so tried and true for so long. But at this point, I see no benefit of using SuperSU, but many benefits to Magisk. And seemingly less problems rooting with Magisk. My recommendation would be current version Magisk, which is v16.0.
First of all, make sure you are using the "full" update zip (which will be >1 GB) and not the partial OTA "patch". You can get the full zip from here (Post #2): https://forum.xda-developers.com/oneplus-3t/how-to/official-oxygenos-5-0-1-android-8-0-t3728119
Since you have TWRP installed, boot into TWRP. You should be able to see your internal storage on your computer, just like it's a thumb drive. Just drag/copy and drop the full OTA zip onto the phone's internal storage. Then just flash the zip in TWRP.
The internal storage should be selected to "Mount" in TWRP by default. But if you can't see internal storage on your computer, make sure it's selected in the TWRP "Mount" section.
Click to expand...
Click to collapse
I did make a nandroid backup from TWRP i just didnt restore it because i thought it was TWRP’s issue due to dm-variety... my bad but whatever
Yeah i have read about Magisk i just didnt investigate enough to know exactly what it is was so i thought it would be better to go for SuperSU because thats what i used on every android device i has... my bad aswell here
About the full update zip.. i’ll try that because i think i was trying to sidelod the ota patch which was 1.6gb...(but still, is the “cannot read xxx.zip” related with what zip file do i sideload? Whatever ill try it when i get home
And also i have already tried the mount feature of twrp recovery but my device just wouldnt show up on my computer.... I will try again later when i have the time and i will contact you if i need any help(if thats ok ofcourse) ...thanks in advance

Yiannis75 said:
I did make a nandroid backup from TWRP i just didnt restore it because i thought it was TWRP’s issue due to dm-variety... my bad but whatever
Click to expand...
Click to collapse
TWRP and root shouldn't normally trip DM-verity (make the phone not boot).
I don't think it will hurt anything at this point to restore the backup you made. You're already trying to flash stock recovery, anyway (which is not that different).
If the restore is successful (phone boots to OS), then just flash Magisk and be done with it!
Yiannis75 said:
Yeah i have read about Magisk i just didnt investigate enough to know exactly what it is was so i thought it would be better to go for SuperSU because thats what i used on every android device i has... my bad aswell here
Click to expand...
Click to collapse
I wouldn't say it's "your bad". Magisk is just a suggestion or recommendation. Some folks have had success with SuperSU. But also seems like a lot more folks than usual, having problems (like no boot) with SuperSU than I'm used to seeing. And as I mentioned, I don't see any benefit of SuperSU (over Magisk) at this point. I was slow to change as well. But after trying Magisk, there has been no going back for me since. So therefore, the suggestion.
You didn't mention what version SuperSU, but 2.82 SR5 is recommended. It's in beta now, so if you used the "stable" 2.82 version, that might be the problem right there.
Yiannis75 said:
About the full update zip.. i’ll try that because i think i was trying to sidelod the ota patch which was 1.6gb...(but still, is the “cannot read xxx.zip” related with what zip file do i sideload? Whatever ill try it when i get home
Click to expand...
Click to collapse
If it was 1.6GB, than it was the full update (at least one of them). I typed ">1 GB" so any OTA zip for this device greater than 1 GB should be okay. It's the OTA zips that are less than 1 GB that you need to watch out for, as it is not a full update, just a partial "patch" (don't flash on a modded device with TWRP or you will soft brick!).
I don't personally use sideload. While I see the convenience, I find it a bit messy. I've seen folks have problems with sideload, when simply putting the ROM on the phone and flashing with TWRP works fine (so in those cases sideload itself was the point of failure).
Now of course, getting the ROM on the phone is the problem, in your case.
Yiannis75 said:
And also i have already tried the mount feature of twrp recovery but my device just wouldnt show up on my computer.... I will try again later when i have the time and i will contact you if i need any help(if thats ok ofcourse)
Click to expand...
Click to collapse
Just post to this thread, and I'll see it. That is the best way to contact me. Good luck!

Yiannis75 said:
I believe i used TWRP 3.2.1-0... the very latest
And yeah am cypriot
Click to expand...
Click to collapse
Inta mou laleis??
Coming to Cyprus soon bro!
About your issue, use TWRP bluespark 8.61, just to be sure.
Never had issues with this version.
Unleashed by my rooted OP3T on 8.0

redpoint73 said:
TWRP and root shouldn't normally trip DM-verity (make the phone not boot).
I don't think it will hurt anything at this point to restore the backup you made. You're already trying to flash stock recovery, anyway (which is not that different).
If the restore is successful (phone boots to OS), then just flash Magisk and be done with it!
I wouldn't say it's "your bad". Magisk is just a suggestion or recommendation. Some folks have had success with SuperSU. But also seems like a lot more folks than usual, having problems (like no boot) with SuperSU than I'm used to seeing. And as I mentioned, I don't see any benefit of SuperSU (over Magisk) at this point. I was slow to change as well. But after trying Magisk, there has been no going back for me since. So therefore, the suggestion.
You didn't mention what version SuperSU, but 2.82 SR5 is recommended. It's in beta now, so if you used the "stable" 2.82 version, that might be the problem right there.
If it was 1.6GB, than it was the full update (at least one of them). I typed ">1 GB" so any OTA zip for this device greater than 1 GB should be okay. It's the OTA zips that are less than 1 GB that you need to watch out for, as it is not a full update, just a partial "patch" (don't flash on a modded device with TWRP or you will soft brick!).
I don't personally use sideload. While I see the convenience, I find it a bit messy. I've seen folks have problems with sideload, when simply putting the ROM on the phone and flashing with TWRP works fine (so in those cases sideload itself was the point of failure).
Now of course, getting the ROM on the phone is the problem, in your case.
Just post to this thread, and I'll see it. That is the best way to contact me. Good luck!
Click to expand...
Click to collapse
So, got home fixed the drivers so that my pc could recognize my device while on TWRP recovery, flashed the zip file through TWRP and it worked like a charm
Thanks for all the help bro

Help pls
Hi my oneplus 3t is on Oreo 5.0.2. I flashed twrp recovery(3.2.1-0) nd super su root (v.2.82) but when I restarted the phone it's stuck on black screen with white oneplus logo.what should I do now?my phone is going into twrp recovery
Should I flash stock oos 5.0.2 from twrp recovery? Pls guide

mannulko said:
Help pls
Hi my oneplus 3t is on Oreo 5.0.2. I flashed twrp recovery(3.2.1-0) nd super su root (v.2.82) but when I restarted the phone it's stuck on black screen with white oneplus logo.what should I do now?my phone is going into twrp recovery
Should I flash stock oos 5.0.2 from twrp recovery? Pls guide
Click to expand...
Click to collapse
just like me, if u flash oos 5.0.2 from twrp u will be just fine. Just flash magisk instead of supersu like i did and all will be working just fine

mannulko said:
Hi my oneplus 3t is on Oreo 5.0.2. I flashed twrp recovery(3.2.1-0) nd super su root (v.2.82) but when I restarted the phone it's stuck on black screen with white oneplus logo.what should I do now?my phone is going into twrp recovery
Should I flash stock oos 5.0.2 from twrp recovery? Pls guide
Click to expand...
Click to collapse
If posting on a thread, related to your issue; it would make sense to actually read the responses in the thread. Since your question is already answered.
In short, you need to use SuperSU 2.82 SR5. The "stable" version 2.82 won't work, and will result in no boot. Or use Magisk 16.0.
If the phone still won't boot after (only) flashing the proper version SuperSU or Magisk; then flash the full stock update file using TWRP. Then flash the right version SuperSU or Magisk.

Trouble rooting my g6

I'm coming to the g6 from an older Samsung. I figured that rooting this one would be just as simple, but was I ever wrong. I've gone through the guides available here, as well as guides on other sites, but no joy. I've probably restored my phone to the original system now 5 or 6 times. I'm hoping that someone can point me in the correct direction here.
The last couple of times I tried, here's what I did and what went wrong. I found a guide over at https://www.androidinfotech.com/root-moto-g6-and-g6-plus-pie/ that was fairly straight forward.
The first time I followed the instructions, booting to twrp failed but I figured that was because it never included flashing twrp to the phone. So I flashed it and used fastboot to boot the phone to the image. I then wiped the phone, flashed magisk and then did the same thing with no-verity-opt and rebooted.
On the reboot, the phone cycled through a couple of attempts and then was successful on the third try. But some things were broken. The battery indicator said I had 0% charge, and the phone refused to connect to wi fi. It also didn't recognize my network. And best of all, I've never achieved root. When I boot back into the bootloader, it comes up with the standard motorola file; not twrp.
Just FYI, I'm running pie.
Can anyone point me in the correct direction here? any help will be very much appreciated.

jmalmberg said:
I'm coming to the g6 from an older Samsung. I figured that rooting this one would be just as simple, but was I ever wrong. I've gone through the guides available here, as well as guides on other sites, but no joy. I've probably restored my phone to the original system now 5 or 6 times. I'm hoping that someone can point me in the correct direction here.
The last couple of times I tried, here's what I did and what went wrong. I found a guide over at https://www.androidinfotech.com/root-moto-g6-and-g6-plus-pie/ that was fairly straight forward.
The first time I followed the instructions, booting to twrp failed but I figured that was because it never included flashing twrp to the phone. So I flashed it and used fastboot to boot the phone to the image. I then wiped the phone, flashed magisk and then did the same thing with no-verity-opt and rebooted.
On the reboot, the phone cycled through a couple of attempts and then was successful on the third try. But some things were broken. The battery indicator said I had 0% charge, and the phone refused to connect to wi fi. It also didn't recognize my network. And best of all, I've never achieved root. When I boot back into the bootloader, it comes up with the standard motorola file; not twrp.
Just FYI, I'm running pie.
Can anyone point me in the correct direction here? any help will be very much appreciated.
Click to expand...
Click to collapse
Need a bit more info
What model G6 ? Software channel?
What build number of Pie are you trying to root?
You say "restored my phone to the original system now 5 or 6 times" what version and build number is that and how are you restoring it?

kc6wke said:
Need a bit more info
What model G6 ? Software channel?
What build number of Pie are you trying to root?
You say "restored my phone to the original system now 5 or 6 times" what version and build number is that and how are you restoring it?
Click to expand...
Click to collapse
Model is xt1925-6
Android version is ALI_RETAIL_9.0_PPS29.118-11-1_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip.
I'm restoring it using Minimal ADB and Fastboot, and flashing the files over.
A couple of other things I should probably say too.
1. The phone was originally running Oreo. About two weeks ago, Motorola pushed out PIE to me and I installed it. That caused a tone of problems... the biggest one was that you couldn't hear the phone anymore. Couldn't hear callers, ringing, notifications, etc... It might has well have been a doorstop. I tried to roll the phone back to Oreo doing a factory reset, but that didn't work either. Wiped out my IMEI and carrier. So I did a little research and found out that some other people had the same issue. They couldn't roll back so I figured I was stuck with Pie.
2. At that point, I unlocked the bootloader and downloaded the version above from a link in one of the forums and flashed it to the phone. For whatever reason, that cured the IMEI, carrier and sound issues. Since I've come this far and the phone doesn't have anything on it, I'd like to root what I have and get some of the capability that I had on the Samsung.
Thanks for your assistance on this.

jmalmberg said:
Model is xt1925-6
Android version is ALI_RETAIL_9.0_PPS29.118-11-1_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip.
I'm restoring it using Minimal ADB and Fastboot, and flashing the files over.
A couple of other things I should probably say too.
1. The phone was originally running Oreo. About two weeks ago, Motorola pushed out PIE to me and I installed it. That caused a tone of problems... the biggest one was that you couldn't hear the phone anymore. Couldn't hear callers, ringing, notifications, etc... It might has well have been a doorstop. I tried to roll the phone back to Oreo doing a factory reset, but that didn't work either. Wiped out my IMEI and carrier. So I did a little research and found out that some other people had the same issue. They couldn't roll back so I figured I was stuck with Pie.
2. At that point, I unlocked the bootloader and downloaded the version above from a link in one of the forums and flashed it to the phone. For whatever reason, that cured the IMEI, carrier and sound issues. Since I've come this far and the phone doesn't have anything on it, I'd like to root what I have and get some of the capability that I had on the Samsung.
Thanks for your assistance on this.
Click to expand...
Click to collapse
PPS29.118-11-1 has a lot of issues. downgrading doesn't seem possible. I thought we had it solved today but ran into the same issue with calls
Follow This thread for rooting

kc6wke said:
PPS29.118-11-1 has a lot of issues. downgrading doesn't seem possible. I thought we had it solved today but ran into the same issue with calls
Follow This thread for rooting
Click to expand...
Click to collapse
Oh, interesting, That's the thread I started with but couldn't get to work for me. That's when I went out and found the guide that I linked to in my original posting. Let me walk through the steps I used here to see if you can tell me where I went wrong.
1. Unlocked my bootloader.
2. Installed Minimal ADB & Fastboot.
3. Placed TWRP, in the Minimal ADB director on my PC and loaded Magisk, DM Verity, Magisk Manager apk to the SD card on my phone. (NOTE: the SD card isn't installed in the phone yet. I'll do that after doing the wipe. Just putting the software on it.)
4. Flashed TWRP to the phone and used Fastboot to load it.
5. Wiped the phone. Used advanced wipe and deleted the cache and data then rebooted to TWRP and did it again. At this point, I installed the SD card.
6. Rebooted the phone into TWRP and then selected install for DM Verity and again for Magisk.
7. Reboot and check for root using Rootcheck. I'm being told that I don't have root access.
What am I missing here?
Again, thank you for the assistance.

jmalmberg said:
Oh, interesting, That's the thread I started with but couldn't get to work for me. That's when I went out and found the guide that I linked to in my original posting. Let me walk through the steps I used here to see if you can tell me where I went wrong.
1. Unlocked my bootloader.
2. Installed Minimal ADB & Fastboot.
3. Placed TWRP, in the Minimal ADB director on my PC and loaded Magisk, DM Verity, Magisk Manager apk to the SD card on my phone. (NOTE: the SD card isn't installed in the phone yet. I'll do that after doing the wipe. Just putting the software on it.)
4. Flashed TWRP to the phone and used Fastboot to load it.
5. Wiped the phone. Used advanced wipe and deleted the cache and data then rebooted to TWRP and did it again. At this point, I installed the SD card.
6. Rebooted the phone into TWRP and then selected install for DM Verity and again for Magisk.
7. Reboot and check for root using Rootcheck. I'm being told that I don't have root access.
What am I missing here?
Again, thank you for the assistance.
Click to expand...
Click to collapse
You need to format data (type yes) In twrp

kc6wke said:
You need to format data (type yes) In twrp
Click to expand...
Click to collapse
That worked! Thank you very much!!! I really appreciate it!!!!

jmalmberg said:
3. Placed TWRP, in the Minimal ADB director on my PC and loaded Magisk, DM Verity, Magisk Manager apk to the SD card on my phone. (NOTE: the SD card isn't installed in the phone yet. I'll do that after doing the wipe. Just putting the software on it.)
.
Click to expand...
Click to collapse
What ver TWRP did you use?
Apparently there is an official version and a modified version to mount vendor-specific mount points?
Thanks,

Tigger31337 said:
What ver TWRP did you use?
Apparently there is an official version and a modified version to mount vendor-specific mount points?
Thanks,
Click to expand...
Click to collapse
I renamed the TWRP file I flashed "recovery.img" and I don't remember the original file name. When I boot to recovery mode it says 3.3.0-0. Hope that helps

jmalmberg said:
I renamed the TWRP file I flashed "recovery.img" and I don't remember the original file name. When I boot to recovery mode it says 3.3.0-0. Hope that helps
Click to expand...
Click to collapse
Yup, I solved it. Thanks. I ended up using 3.2.3.official.

Rooting; ending in bootloop help
Sorry if I am hijacking this thread; thought to discuss here as the title "Trouble rooting my g6" still applies.
I have:
XT1925-13 (Moto G6 ALI) running stock Android Pie with build ppss29.55-34.
I have issues when I tried to root. I followed these steps:
I downloaded the factory image “ALI_RETAIL_9.0_PPS29.55-34_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip” and flashed it first. The mobile restarted and went to the first screen to select a language.
I rebooted it into bootloader, ran the TWRP as a temp by command “fastboot boot twrp-3.3.0-0-Ali.img,” which asked for the password.
I pressed cancel, and then I wiped cache and data.
Via ADB I transferred “adb push Magisk-v20.0.zip /sdcard” and “adb push no-verity-opt-encrypt-6.1.zip /sdcard”.
Then from TWRP, I installed Magisk. Then when installing no-verity, it gave an error “updater process ended with an error: 1 error installing zip file ‘no-verity-opt-encrypt-6.1.zip’.
Rebooted the device with hope and ended in a boot loop.
I also tried to use Magisk-v19.4.zip in the above steps and also tried to skip no-verity-opt-encrypt-6.1.zip. All ended in boot loop.
Any idea why? Are there any guides for the combination XT1925-13 (Moto G6 ALI) running ppss29.55-34?
Many thanks for your time.

Here is a solution
Flash original boot in fastboot followed by TWRP and reboot in recovery.
Install Magisk 19.4 in TWRP (3.3.x Android 9 OK) and reboot
You can update to 20 in Magisk Manager later