Database Info

[Q] Rooting T-Mobile SG3

I installed the OTA for 4.1.2 and have not rooted my T-mobile T999 at all. I've watched videos that said it was for this firmware and model, but when I go into recovery mode and try to install the zip file, I get a message saying "E: Signature Verification Failed." SuperSU is on my phone, but when I try to launch it, it says "There is no SU binary installed and SuperSU cannot install it. This is a problem!"
I've never rooted a phone before, but the videos I watched seemed really easy, but it's not working for me.
Can somebody post how to do it with the most updated G3rootsprint.zip file. Maybe I'm using one that's too old, or maybe since the update is only days old, it's not possible with the processes that are online already.

gstoliby said:
I installed the OTA for 4.1.2 and have not rooted my T-mobile T999 at all. I've watched videos that said it was for this firmware and model, but when I go into recovery mode and try to install the zip file, I get a message saying "E: Signature Verification Failed." SuperSU is on my phone, but when I try to launch it, it says "There is no SU binary installed and SuperSU cannot install it. This is a problem!"
I've never rooted a phone before, but the videos I watched seemed really easy, but it's not working for me.
Can somebody post how to do it with the most updated G3rootsprint.zip file. Maybe I'm using one that's too old, or maybe since the update is only days old, it's not possible with the processes that are online already.
Click to expand...
Click to collapse
try disabling signature verification in your recovery

chromium96 said:
try disabling signature verification in your recovery
Click to expand...
Click to collapse
I can't even figure out how to do that!

gstoliby said:
I can't even figure out how to do that!
Click to expand...
Click to collapse
Which recovery are you using? In clockwordmod the option is located in the advacned menu

chromium96 said:
Which recovery are you using? In clockwordmod the option is located in the advacned menu
Click to expand...
Click to collapse
I'm attempting to root with clockworkmod, but since I can't get that far, it's the android recovery.

gstoliby said:
I'm attempting to root with clockworkmod, but since I can't get that far, it's the android recovery.
Click to expand...
Click to collapse
Use this guide to root the t999v. I used it a couple months ago and it works fine, and as a bonus it wont trip your flash counter.

chromium96 said:
Use this guide to root the t999v. I used it a couple months ago and it works fine, and as a bonus it wont trip your flash counter.
Click to expand...
Click to collapse
I'll have to give it a try when I get to my personal computer.

Wiped for new ROM, Weaksauce says rooted, SuperSU says no root.

So Weaksauce won't do anything since it says I'm already rooted... Rootchecker and SuperSU say I am NOT rooted. Not sure where to go from here since SuperSU doesn't seem to have access to install new binaries..
I was on CleanROM and had an issue with something so I tried to reinstall it, but installed a Sense rom over it by accident and realized root was messed up. Did "Wipe For New ROM" or whatever the option in TWRP is, installed CleanROM which is pre-rooted, then ran into this seemingly uncorrectable root issue.

TheCheeks said:
So Weaksauce won't do anything since it says I'm already rooted... Rootchecker and SuperSU say I am NOT rooted. Not sure where to go from here since SuperSU doesn't seem to have access to install new binaries..
I was on CleanROM and had an issue with something so I tried to reinstall it, but installed a Sense rom over it by accident and realized root was messed up. Did "Wipe For New ROM" or whatever the option in TWRP is, installed CleanROM which is pre-rooted, then ran into this seemingly uncorrectable root issue.
Click to expand...
Click to collapse
Have you tried flashing SU in recovery?

...
droidkevlar said:
Have you tried flashing SU in recovery?
Click to expand...
Click to collapse
I flashed Superuser-3.1.3-arm-signed.zip in recovery, still no root.

RUU that bad boy.
TheCheeks said:
I flashed Superuser-3.1.3-arm-signed.zip in recovery, still no root.
Click to expand...
Click to collapse

.
godhamba said:
RUU that bad boy.
Click to expand...
Click to collapse
Never heard of RUU before but this sound like a solid fix. Will attempt this right now. Here is where I'm at though if you've got any other ideas:
S-Off (bootloader says UNLOCKED in fastboot)
I wiped /system, /data /cache and dalvik before installing a GPE ROM.
Weaksauce says already rooted, SuperSU says it can't update binaries.

Read this thread and follow the instructions. This will get your phone completely back to stock except that it will be pre-rooted. You should know what to do from there.
TheCheeks said:
Never heard of RUU before but this sound like a solid fix. Will attempt this right now. Here is where I'm at though if you've got any other ideas:
S-Off (bootloader says UNLOCKED in fastboot)
I wiped /system, /data /cache and dalvik before installing a GPE ROM.
Weaksauce says already rooted, SuperSU says it can't update binaries.
Click to expand...
Click to collapse

.
godhamba said:
Read this thread and follow the instructions. This will get your phone completely back to stock except that it will be pre-rooted. You should know what to do from there.
Click to expand...
Click to collapse
Thanks, that's the thread I found too. Attempted to get adb/fastboot working on my computer here at work but I'm tired of driver after driver. I know my MBP at home has a properly working adb/fastboot folder and boy is using Terminal better than CMD
The only question I have is what file(s) do I push? They have a tiny <10MB stickerfix.zip at the top of the post, but I feel like I should probably do the full RUU at the bottom, followed by the TWRP ruu/zip?|
Edit: NVM, I should read better. stickersfix is the last thing to flash to make sure any needed HTC stuff is put on the device.

[q] OTA 5.0.1 on rooted shield

I am rooted on locked bootloader. My tablet just downloaded the 5.0.1 update. Has anyone flashed this yet and kept root? Not sure where the download is stored on the file system in case of sideloading or flashing from CWM. Thanks.

Hi. Inside the update ZIP there are some hash checks of the system partition, so what is needed is rebuilding ota update ZIP, which I can't do atm.

didn't work for me
Im 5.0 rooted with unlocked bootloader, using CWM.
After downloading, it restarted to cwm and installation failed. Didn't take a picture or write down the details; making a second attempt now, will report back. Did not lose root during install attempt.

Mine is failing because CWM seems to be telling it I'm still on Android 4.4.2.

same here
johndough247 said:
Im 5.0 rooted with unlocked bootloader, using CWM.
After downloading, it restarted to cwm and installation failed. Didn't take a picture or write down the details; making a second attempt now, will report back. Did not lose root during install attempt.
Click to expand...
Click to collapse
The same happend to me did you manage to fix it?!

wibimaster said:
The same happend to me did you manage to fix it?!
Click to expand...
Click to collapse
Until someone rebuilds the update to remove the checks you will keep getting an error.

Ok. Here is what I did on my locked bootloader shield:
1. Download the full 5.0.1 US LTE zip and SuperSU 2.40.
2. Entered CWM, flashed 5.0.1, then SuperSU, wipe cache partition, and reboot. Done.
Nothing to it. Only thing now, how do I remove the OTA notice I keep getting to update? It seems that the incremental update had downloaded and now it keeps prompting me to flash even though I manually updated with the full version. Anyone know how to get around this? Thanks.
EDIT: I used the command 'pm disable com.nvidia.ota' and so far seems to have fixed it.

bigcletus said:
Ok. Here is what I did on my locked bootloader shield:
1. Download the full 5.0.1 US LTE zip and SuperSU 2.40.
2. Entered CWM, flashed 5.0.1, then SuperSU, wipe cache partition, and reboot. Done.
Nothing to it. Only thing now, how do I remove the OTA notice I keep getting to update? It seems that the incremental update had downloaded and now it keeps prompting me to flash even though I manually updated with the full version. Anyone know how to get around this? Thanks.
EDIT: I used the command 'pm disable com.nvidia.ota' and so far seems to have fixed it.
Click to expand...
Click to collapse
Oh, this is interesting! so this way you keep both the root and CWM?

which shield you have got?
bigcletus said:
Ok. Here is what I did on my locked bootloader shield:
1. Download the full 5.0.1 US LTE zip and SuperSU 2.40.
2. Entered CWM, flashed 5.0.1, then SuperSU, wipe cache partition, and reboot. Done.
Nothing to it. Only thing now, how do I remove the OTA notice I keep getting to update? It seems that the incremental update had downloaded and now it keeps prompting me to flash even though I manually updated with the full version. Anyone know how to get around this? Thanks.
EDIT: I used the command 'pm disable com.nvidia.ota' and so far seems to have fixed it.
Click to expand...
Click to collapse
Do you have the wifi 16 us or the 32 LTE us?

Accidently updated SuperSU

So I accidentally updated SuperSu. My brain was operating on auto and I tried to update the binary as well, it failed. Now I've lost root and can't seem to get it back. I tried uninstalling SuperSu then re flashing it via ADB like I did when I first rooted, but it just won't work. Any thoughts?
Running a tmobile s7 on the MMB29M.G930TUVU3APG1 build.
Thanks!

Still no luck
Does anyone have any ideas? I used the removal tool in the super su app, then uninstalled it, then reinstalled via adb, butI still can't fix what I've done.
Teeklee said:
So I accidentally updated SuperSu. My brain was operating on auto and I tried to update the binary as well, it failed. Now I've lost root and can't seem to get it back. I tried uninstalling SuperSu then re flashing it via ADB like I did when I first rooted, but it just won't work. Any thoughts?
Running a tmobile s7 on the MMB29M.G930TUVU3APG1 build.
Thanks!
Click to expand...
Click to collapse

Teeklee said:
Does anyone have any ideas? I used the removal tool in the super su app, then uninstalled it, then reinstalled via adb, butI still can't fix what I've done.
Click to expand...
Click to collapse
Yes. Save anything. Factory reset and reroot your phone with this superuser. Do not update the binary. It's included with the fastboot. Just run the root.bat file after you flashed your AP file in download mode.

Is it safe to do system updates while rooted?

Hello everyone!
Today I got my Mate9 toyed around and then decided to root it. All went smooth as butter and everything is working perfectly.
Just about 1 hour ago, I see a notification saying that there is a system update available: later or restart now?
I am wondering, will this system update mess up my phone, since it is rooted, or not? I'd like to avoid any possible mess up for the time being

N3sh said:
Hello everyone!
Today I got my Mate9 toyed around and then decided to root it. All went smooth as butter and everything is working perfectly.
Just about 1 hour ago, I see a notification saying that there is a system update available: later or restart now?
I am wondering, will this system update mess up my phone, since it is rooted, or not? I'd like to avoid any possible mess up for the time being
Click to expand...
Click to collapse
Depends on how you rooted.
For a successful OTA install your device probably must meet the following criteria
HUAWEI stock recovery installed
unaltered /system, /product and /vendor partitions
So if you rooted with a "systemless" method (e.g. Magisk, recent SuperSU) and haven't done other installs/modifications that typically change /system you could try it. And you have to flash stock recovery (i.e. get rid of TWRP temporarily for the OTA install).

st_voss said:
Depends on how you rooted.
For a successful OTA install your device probably must meet the following criteria
HUAWEI stock recovery installed
unaltered /system, /product and /vendor partitions
So if you rooted with a "systemless" method (e.g. Magisk, recent SuperSU) and haven't done other installs/modifications that typically change /system you could try it. And you have to flash stock recovery (i.e. get rid of TWRP temporarily for the OTA install).
Click to expand...
Click to collapse
Here is what I did:
- Unlocked bootloader with Huawei code
- Installed new TWRP recovery
- Flashed supersu via adb (no SD card atm)
- Installed supersu apk
- Ta-da!
I actually checked the changelog of the new "update" and it is basically to restore the system back to before the change. Does it mean I am stuck with this version forever now?

N3sh said:
Here is what I did:
- Unlocked bootloader with Huawei code
- Installed new TWRP recovery
- Flashed supersu via adb (no SD card atm)
- Installed supersu apk
- Ta-da!
I actually checked the changelog of the new "update" and it is basically to restore the system back to before the change. Does it mean I am stuck with this version forever now?
Click to expand...
Click to collapse
What supersu zip did you use?
And no you are not stuck with your version forever. But updating will probably require more than simply applying an OTA update.

st_voss said:
What supersu zip did you use?
And no you are not stuck with your version forever. But updating will probably require more than simply applying an OTA update.
Click to expand...
Click to collapse
Followed this: https://forum.xda-developers.com/mate-9/development/recovery-unofficial-twrp-huawei-mate-9-t3515617

N3sh said:
Followed this: https://forum.xda-developers.com/mate-9/development/recovery-unofficial-twrp-huawei-mate-9-t3515617
Click to expand...
Click to collapse
So you are using Phh's superuser? I don't think that it's "systemless".
I would recommend a complete reinstall/update using https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108 and using the lastest Magisk for rooting.

Mmm, I might just keep this until I have the need to reinstall. Thanks

It doesn't seem a system update allows you to skip it.
If the phone is rebooted, will it enter a loop or just fail the installation and carry on as normally?

I removed auto-download and rebooted, nothing different. Great

4thfloorcaveman said:
It doesn't seem a system update allows you to skip it.
If the phone is rebooted, will it enter a loop or just fail the installation and carry on as normally?
Click to expand...
Click to collapse
I think it's (stock) recovery that installs an OTA. I don't know the mechanism that allows the recovery to find the OTA file (maybe the OTA file is copied to a directory where recovery is lookup for update files or some boot parameter is modified) but a normal reboot should not trigger an OTA install attempt.