Related
since the phone maintains the 2 pushed files on the phone after reboot, is it possible to make an app that can be run from the phone itself to run the two adb commands of Pie root that do the rooting?
Well Google now doesn't work worth an iPhone. .I've spoken those last two lines ADB shell commands out loud for the past 15 minutes and I don't get root
You cannot do it from the phone. That method lacks sufficient permissions
Sent from my XT1058 using XDA Free mobile app
Neighbor808 said:
You cannot do it from the phone. That method lacks sufficient permissions
Sent from my XT1058 using XDA Free mobile app
Click to expand...
Click to collapse
I'm starting to believe you....
doitinthedirt said:
I'm starting to believe you....
Click to expand...
Click to collapse
We KNOW that the commands MUST be run from ADB (and not from a SHELL, as your screenshot shows you have tried).....
But before we discount the idea completely, perhaps an experienced DEV could commend on this possibility:
Guys, have a look at this thread regarding running adb commands (through adb wireless) from another android device:
http://androidforums.com/android-applications/783226-run-adb-shell-another-android-phone.html
See the last 2 posts. This user successfully connected one android device to another via WiFi and was able to run adb commands.
Now first, I know that "ADB Wireless" requires root access, however there are 2 non-root variants aptly called "ADB Wireless (No Root)" -- see the play store.
Having read up on those specific apps, I've found that they require you to first connect the USB cable to the PC, and run an adb command to activate ADB over WiFi. What I'm not sure about is if you must do this each time the phone is rebooted. If not, then we have the possibility to actually run adb commands through TCP/IP possibly from the phone itself.
Consider the possibility of using the loop-back address...for instance: adb connect 127.0.0.1 in order to achieve a connection to the device itself.
If the adb command to activate adbwireless on non-rooted devices must be run each time the phone is rebooted, then this solution is probably going to go nowhere....but its worth checking out nonetheless....
We would definitely need a working adb binary for the Moto X in order for this to be possible at all.
See this link: http://forums.androidcentral.com/be...ol-native-adb-fastboot-your-phone-tablet.html
This user has repacked the adb and fastboot binaries (called "kadb" and "kfastboot") so they can be run on an android device itself. The intention is to use USB-OTG to connect another android device and run adb commands on the connected device.
^^ This definitely shows that it is possible to at least run adb commands from another android device connected via USB-OTG.
I know that many users are looking for a way to use PIE without having to connect to the PC after each reboot, hence the reason the "TowelRoot" app has had so much interest...
Unfortunately, TowelRoot has inherent limitations, because of the SU context (Non--Trusted App) as I understand. Several of us (myself included) have attempted to reach out to the developer for comment as to why this SU context is being used, and whether or not it can be modified to use the "Kernel" SU context that jcase is using with PIE, but none of us have received a response....
Do any experienced DEVS care to comment on the possibility of using the methods I have described, or something similar?
EDIT: Also, @doitinthedirt : have you tried to unlock your bootloader via the middleman? Or do you have a 2013 variant that he can not access the code for? The BL unlock solution is far superior to any of these temp-root methods, and it is permanent. (disregard if you already know this and are unable to obtain a code...)
I was running those commands from the same phone.. it was on a wifi network only to access internet. i used an app https://play.google.com/store/apps/details?id=com.spartacusrex.spartacuside
Only had about 10 minutes to mess around with it.. going to experiment more tonight.. and another app https://play.google.com/store/apps/details?id=jackpal.androidterm
The wireless from my nexus 7 was going to be my next try if i I couldnt get anywhere running from phone itself. And no I have not tried the middleman.. phone is july 3 2014 make so going to send a paypal to him and see if i get a code to unlock.
Getting nowhere..
doitinthedirt said:
Getting nowhere..
Click to expand...
Click to collapse
I appreciate your enthusiasm, but you are still trying to run the commands from a terminal SHELL. We -know- that this won't work. I'm not sure you understand what I was trying to express in my earlier post. I will attempt to experiment with the kadb binary, but you shouldn't continue trying to do this from ANY terminal emulator - it simply won't work, as @Neighbor808 has correctly advised...
Both of the apps you have linked ARE terminal emulators (hence running from SHELL).
If an experienced DEV could read my post, they might be able to comment further.
EDIT: I believe this is a lost cause:
From the dev who compiled the kadb binary: "Note : You do not need to be rooted, you do however need a custom recovery or temp boot a custom recovery."
This means that it should -absolutely- work for those of us who are unlocked, but definitely not temp-rooted.
Additionally, the AdbWireless method seems to fall short as well. It will probably work, but only if you connect to your PC first to run an ADB command to activate adb over WiFi, which defeats the whole idea of not having to use a PC.
The only method that IS viable for those of you using PIE, is the USB-OTG method. If you have ANOTHER android device (NOT your X) that:
1. has custom recovery
and
2. supports USB-OTG
Then you could purchase a USB-OTG cable, install the flashable zip containing the kadb and kfastboot binaries from the post I linked earlier, and run the ADB commands FROM the 2nd device.
This may be an option for you. Assuming you have installed custom recovery on your Nexus 7 (it definitely supports USB-OTG), you should be able to install the flashable zip, and run the commands from your Nexus 7 (just like you would from a PC, except using the command "kadb" instead of "adb".....i.e.:
kadb shell chmod 755 /data/local/atvc/root.sh
kadb shell /data/local/atvc/root.sh
I see no reason that this would not work....all the other methods I suggested have been eliminated as possibilities during my research/testing.
I don't, however, see how this is any better than simply connecting to your pc and running the adb commands the traditional way.
Good Luck
---------- Post added at 02:48 AM ---------- Previous post was at 02:19 AM ----------
doitinthedirt said:
Well Google now doesn't work worth an iPhone. .I've spoken those last two lines ADB shell commands out loud for the past 15 minutes and I don't get root
Click to expand...
Click to collapse
Oh wow! I missed this post. You are joking, right? You've --spoken-- the commands to Google Now?!?! LMFAO + ROFL + LOL....I just can't find a way to express just how humorous this post is
Good One :silly:
Use towel root if your trying to root from your phone.
Sent from my XT1058 using XDA Premium 4 mobile app
Thanks Sir, towelroot does not root my moto X
[email protected] said:
Use towel root if your trying to root from your phone.
Sent from my XT1058 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
This:
samwathegreat said:
I know that many users are looking for a way to use PIE without having to connect to the PC after each reboot, hence the reason the "TowelRoot" app has had so much interest...
Unfortunately, TowelRoot has inherent limitations, because of the SU context (Non--Trusted App) as I understand. Several of us (myself included) have attempted to reach out to the developer for comment as to why this SU context is being used, and whether or not it can be modified to use the "Kernel" SU context that jcase is using with PIE, but none of us have received a response....
Click to expand...
Click to collapse
samwathegreat said:
This:
Click to expand...
Click to collapse
Oh yeah? What about this?
Sent from my XT1058 using XDA Premium 4 mobile app
[email protected] said:
Oh yeah? What about this?
Sent from my XT1058 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Um... Pointing out the inherent limitations of the towel root and why it doesn't work for many and causes issues for others. I'm going to assume that because you are using the XDA app, you didn't see the quote attached to my post, but if you view it in a browser you should understand the point I was making...
I'm glad that towel root is actually working for you. Are you experiencing the random reboots?
[email protected] said:
Use towel root if your trying to root from your phone.
Sent from my XT1058 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
towel root will not work on the motoX
it doesn't work for Him I get that same screen saying you should have root but if he would bother checking with file explorer root access he will find out he doesn't have root
yamaha83 said:
towel root will not work on the motoX
Click to expand...
Click to collapse
Not entirely accurate. Some have managed to use after rooting with PIE, but it does cause issues for many and (once again) has inherent limitations due to the SU context being used.
---------- Post added at 02:26 PM ---------- Previous post was at 02:22 PM ----------
doitinthedirt said:
it doesn't work for Him I get that same screen saying you should have root but if he would bother checking with file explorer root access he will find out he doesn't have root
Click to expand...
Click to collapse
I don't think hovax is foolish enough to mistakenly believe he has root when he does not lol. He has obviously managed to get it to work for him, as have many others. I am curious if he is experiencing the problems that many others are with towel root, however.
a simple screenshot showing root access in system folder like this one from my other moto x running ios 4.4 rooted with slap, that will convince me
doitinthedirt said:
is it possible to make an app that can be run from the phone itself to run the two adb commands of Pie root that do the rooting?
Click to expand...
Click to collapse
If it was possible, I would have thought JCASE would have released it that way, instead of having to do the process while connected to the PC.
doitinthedirt said:
a simple screenshot showing root access in system folder like this one from my other moto x running ios 4.4 rooted with slap, that will convince me
Click to expand...
Click to collapse
You have to realize that many users including hovax are much more experienced than you seem to be. All the proof you should need is located in the towel root discussion thread.
Remember: you were trying to -speak- adb commands using Google now in order to root your phone...
Some of your comments are likely being taken as insults...
EDIT: I won't be posting any further in this thread. This idea is going nowhere and (obviously) does not belong in the original android development sub-forum.
EDIT2: Mods moved the thread to the appropriate location, so I will continue posting here.
I dont believe anyone has ever rooted an x with tr. all you get is the page pictured in the post above by the guy saying tr says you should have root... ive got it on two moto xs a broken one and a replacement one both on 4.4.2 and fx explorer and root checker confirm no root. one is 15 april 2014 build and the other is 03 july 2014 build. both fail under tr.
Hey guys,
Recently, I have been trying to re-root my LG G2 VS980 that was returned to lollipop stock (LG Firmware). However, all the tools I knew that previously worked, (Ioroot, Towelroot, Stumproot, Kingoroot, etc..) did not work. After months of testing, I finally found one app that currently works called KingRoot.
As far as I know, it is the only root method that acutally still works after LG patched most of the exploits so I thought I would share the info with you guys in case some of you are still interested in rooting your G2.
Instructions:
1. Install Kingroot: http://kingroot.net/ (the APK doesn't work for the G2)
2. Go to settings in your phone and click the build number 7-10 times to enable Developer Options
3. Go to Developer Options and enable USB Debugging
4. plug the phone into your computer and launch the program. Make sure you see the USB Debugging card that will pop up on your phone.
Launch the program and allow the program to root your phone.
Sidenote: The only downside to the app is it is all in Korean but it is very easy to tell what it is asking due to excellent pictures
After you receive root, download the app RootChecker just to make sure.
To Install TWRP:
1. Instructions: Go to Play Store and type in the search window, "AUTOREC".
2. Select the correct variant: ex. VS980=Verizon etc...
3. Install the app.
4. Watch TWRP Install on your phone.
5. Reward yourself on your hard work with a pat on the back.
So that's it; A fast easy, and trouble free method on getting root and installing TWRP
Thanks for this. I recently acquired a G2, and will be trying this out tonight.
tribalartgod said:
Thanks for this. I recently acquired a G2, and will be trying this out tonight.
Click to expand...
Click to collapse
No problem. Have fun with your custom ROM of choice.
Can you share the setup files? I also need to re-root my Verizon phone. The kingroot ownload links looks dead
i downlaoded it from here. I have usb dev enabled. now what? http://kingroot-pc.en.uptodown.com/download
Stuck on that step. I know its telling me to enable USB debuggin which I have, it doens' do anythong when I click Go in Korean
I managed to enable debugging mode which was by setting the 'USB Type" on the phone to "Internet -> Ethernet"
But Kingroot isn't managing to root the phone. It goes 100 percent and nothing.
Ioroot managed to get the phone into the reboot phase but the phone no longer processed the splash screen of the recover/bootloader. The splash screen which has the android mascot on its back with abdomen open.
"LG G2 One lick Tool" makes the phone go to "download mode" but its stuck at 0 percent. I disconnect and replug in hope of kickstarting it, doesn't work.
What can I do now?
y300owner said:
I managed to enable debugging mode which was by setting the 'USB Type" on the phone to "Internet -> Ethernet"
But Kingroot isn't managing to root the phone. It goes 100 percent and nothing.
Ioroot managed to get the phone into the reboot phase but the phone no longer processed the splash screen of the recover/bootloader. The splash screen which has the android mascot on its back with abdomen open.
"LG G2 One lick Tool" makes the phone go to "download mode" but its stuck at 0 percent. I disconnect and replug in hope of kickstarting it, doesn't work.
What can I do now?
Click to expand...
Click to collapse
Where you able to get it to work? I am running into the same problems.
Sent from my SM-N920V using Tapatalk
y300owner said:
Can you share the setup files? I also need to re-root my Verizon phone. The kingroot ownload links looks dead
i downlaoded it from here. I have usb dev enabled. now what? http://kingroot-pc.en.uptodown.com/download
Stuck on that step. I know its telling me to enable USB debuggin which I have, it doens' do anythong when I click Go in Korean
Click to expand...
Click to collapse
Hmm... Sorry for the late response. Try this link and see if it works: http://www.kingroot.org/
mach01 said:
Hmm... Sorry for the late response. Try this link and see if it works: http://www.kingroot.org/
Click to expand...
Click to collapse
Thanks I tried almost almost everything.
Stumbled upon Stump root last night and it brute forced it way in.
---------- Post added at 12:46 PM ---------- Previous post was at 12:44 PM ----------
Jshokamp said:
Where you able to get it to work? I am running into the same problems.
Sent from my SM-N920V using Tapatalk
Click to expand...
Click to collapse
What problem? Check one of the thread I started. Posted everything on it.
y300owner said:
Thanks I tried almost almost everything.
Stumbled upon Stump root last night and it brute forced it way in.
---------- Post added at 12:46 PM ---------- Previous post was at 12:44 PM ----------
What problem? Check one of the thread I started. Posted everything on it.
Click to expand...
Click to collapse
You on 39aa or just 39a?
Lawlrus said:
You on 39aa or just 39a?
Click to expand...
Click to collapse
No idea. I was on a downgraded stock ROM, VS980_27A or was it VS980_24A. Can't remember; 4.4.2
Whatever it was, none of the popular rooting method was working. They were managing to do 'semi root' as in root message was displayed in "hard reset mode" and in 'download mode' but there was no root when the OS fully booted. The 'stock recovery' was also corrupted as in it showed a dead android with red exclamation mark. From the searching I did, people were saying there was no recovery installed so I needed one but I could not install. No stock recovery means no 'adb'.
Stump root gave 'complete' root. I hope you understand what I'm trying to say.
Will this work if I am on the 39aa update from Verizon? I am skeptical about this because this is my only phone and don't need to mess it up.
UserofAndroid1813 said:
Will this work if I am on the 39aa update from Verizon? I am skeptical about this because this is my only phone and don't need to mess it up.
Click to expand...
Click to collapse
I don't think I've seen a way to root 39aa as of yet. One of our developers was asking about it as well, if you do find a way, please @ me so I can hook him up
I'm still looking around for a way.
Lawlrus said:
I don't think I've seen a way to root 39aa as of yet. One of our developers was asking about it as well, if you do find a way, please @ me so I can hook him up
I'm still looking around for a way.
Click to expand...
Click to collapse
I tried and failed at it. I am downgrading to VS98039A_05 and going from there. it seems VS9803AA was meant to patch root and also SF security patches.
This XML file does not appear to have any style information associated with it.
The document tree is shown below.
<Error><Code>AccountProblem</Code><Message>
Your Google account is not currently enabled for this operation. Please check https://code.google.com/apis/console/#:billing to see if you have a past due balance or if the credit card (or other payment mechanism) on your account is expired. You can find additional information at https://developers.google.com/storage/docs/signup</Message></Error>
Thanks for this. For people who don't want to mess with Korean, or if Kingroot doesn't work, LG One Click Root still works on VS9803AA, although you may have to run it 3 or 4 times. Here's the original post: http://forum.xda-developers.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951
And here's a good guide: http://webtrickz.com/how-to-root-lg-g2-running-lollipop-with-lg-one-click-root/
Interesting... I've tried that method four times and it never worked for me. Good to hear it works for other people though. I agree not to many people want to use
Korean deciphering skills just to root their phone but its just an option.
marathonjon said:
Thanks for this. For people who don't want to mess with Korean, or if Kingroot doesn't work, LG One Click Root still works on VS9803AA, although you may have to run it 3 or 4 times. Here's the original post: http://forum.xda-developers.com/lg-g...lipop-t3056951
And here's a good guide: http://webtrickz.com/how-to-root-lg-...ne-click-root/
Click to expand...
Click to collapse
Both of these links are dead.
CruelSun said:
Both of these links are dead.
Click to expand...
Click to collapse
Links are fixed. The whole URLs don't show in the post, but if you click on them, they should work.
those with the issue of kingroot not reading your phone plugged in. put your usb option on phone to PTP camera mode and it will work now.
Even doing all, i m still unable to get my phone recognized. Switched many times befween ptp
Sent from my VS980 4G using Tapatalk
---------- Post added at 05:55 AM ---------- Previous post was at 05:54 AM ----------
Furqan Ullah said:
Even doing all, i m still unable to get my phone recognized. Switched many times befween ptp
Sent from my VS980 4G using Tapatalk
Click to expand...
Click to collapse
And other file transfer option. USB picture is displaying sometimes or sometimes circle
Sent from my VS980 4G using Tapatalk
Hi, I've been trying to unlock bootloader since yesterday. Everything was good until 'booting tablet in fastboot mode'. I have typed 'adb reboot bootloader' in Minimal ADB and fastboot but no result. Tablet have just rebooted normally. Same in recovery mode. After choosing 'reboot to bootloader' option, nothing happens. Just simply reboot nothing else. Does anyone know what's wrong?
Krystiannnnnn said:
Hi, I've been trying to unlock bootloader since yesterday. Everything was good until 'booting tablet in fastboot mode'. I have typed 'adb reboot bootloader' in Minimal ADB and fastboot but no result. Tablet have just rebooted normally. Same in recovery mode. After choosing 'reboot to bootloader' option, nothing happens. Just simply reboot nothing else. Does anyone know what's wrong?
Click to expand...
Click to collapse
http://forum.xda-developers.com/galaxy-tab-s/help/looking-to-direction-root-galaxy-tab-a6-t3390941
you may want to ask ashyx or see his posts in the above link
(am trying to modify the system image for debloat and smaller changes mentioned in one of the posts in the above thread - but its tar.md5 fails on flash in odin..did all changes in windows using various tools-have the system folder...have the 285M)
also see page 14 here
http://forum.xda-developers.com/and...ng-tab-e-sm-sm-smnu-smp-t3302935/post66585078
mac231us said:
http://forum.xda-developers.com/galaxy-tab-s/help/looking-to-direction-root-galaxy-tab-a6-t3390941
you may want to ask ashyx or see his posts in the above link
(am trying to modify the system image for debloat and smaller changes mentioned in one of the posts in the above thread - but its tar.md5 fails on flash in odin..did all changes in windows using various tools-have the system folder...have the 285M)
also see page 14 here
http://forum.xda-developers.com/and...ng-tab-e-sm-sm-smnu-smp-t3302935/post66585078
Click to expand...
Click to collapse
That's really helpfull, thanks.
Galaxy tab A6 FRP
Hi all!!
someone know how to remove FRP from this device?
i have tired OTG but file maneger not appear, and several bug but nothing works...
sorry for my bad english!
thank to all!!!
MarcoKrT said:
Hi all!!
someone know how to remove FRP from this device?
i have tired OTG but file maneger not appear, and several bug but nothing works...
sorry for my bad english!
thank to all!!!
Click to expand...
Click to collapse
I think that you can't unlock FRP without OTG, but this may help: http://forum.xda-developers.com/nexus-6/general/guide-frp-bypass-solution-usb-otg-t3261846
Krystiannnnnn said:
I think that you can't unlock FRP without OTG, but this may help: http://forum.xda-developers.com/nexus-6/general/guide-frp-bypass-solution-usb-otg-t3261846
Click to expand...
Click to collapse
Thank you for reply but i can't do it because on phone USB debug is off
MarcoKrT said:
Thank you for reply but i can't do it because on phone USB debug is off
Click to expand...
Click to collapse
Why do you want to disable FRP lock, it basically has no effect on this device.
If you still want to do it enable OEM UNLOCK in developer settings.
---------- Post added at 12:59 AM ---------- Previous post was at 12:56 AM ----------
Krystiannnnnn said:
Hi, I've been trying to unlock bootloader since yesterday. Everything was good until 'booting tablet in fastboot mode'. I have typed 'adb reboot bootloader' in Minimal ADB and fastboot but no result. Tablet have just rebooted normally. Same in recovery mode. After choosing 'reboot to bootloader' option, nothing happens. Just simply reboot nothing else. Does anyone know what's wrong?
Click to expand...
Click to collapse
This device does not have FASTBOOT mode. Neither do most other Samsung devices. Your wasting your time. Samsung bootloaders are almost impossible to unlock unless they provide you with it officially.
ashyx said:
Why do you want to disable FRP lock, it basically has no effect on this device.
If you still want to do it enable OEM UNLOCK in developer settings.
---------- Post added at 12:59 AM ---------- Previous post was at 12:56 AM ----------
This device does not have FASTBOOT mode. Neither do most other Samsung devices. Your wasting your time. Samsung bootloaders are almost impossible to unlock unless they provide you with it officially.
Click to expand...
Click to collapse
srsroot claims to root this device (saw a tweet about it), has anyone tried it?
ozkaya said:
srsroot claims to root this device (saw a tweet about it), has anyone tried it?
Click to expand...
Click to collapse
It doesn't nothing does.
I purchased this and it just arrives. Is this model too new?
If samsung doesn't provide the bootloader unlock, then we will never figure it out?
nekmiyev said:
I purchased this and it just arrives. Is this model too new?
If samsung doesn't provide the bootloader unlock, then we will never figure it out?
Click to expand...
Click to collapse
Highly unlikely the bootloader can be unlocked unless Samsung provides it or an unlocked bootloader or engineering kernel is leaked.
As for root it's still possible with the right exploit.
ashyx said:
Why do you want to disable FRP lock, it basically has no effect on this device.
If you still want to do it enable OEM UNLOCK in developer settings.
---------- Post added at 12:59 AM ---------- Previous post was at 12:56 AM ----------
This device does not have FASTBOOT mode. Neither do most other Samsung devices. Your wasting your time. Samsung bootloaders are almost impossible to unlock unless they provide you with it officially.
Click to expand...
Click to collapse
Well, this sucks. I'm probably gonna change device because of this :/ One more question.... Do you know if Samsung Galaxy Tab E have locked bootloader? (and if it's locked, is there any way to unlock it?) I'm just asking because I'm probably gonna buy this device next.
Krystiannnnnn said:
Well, this sucks. I'm probably gonna change device because of this :/ One more question.... Do you know if Samsung Galaxy Tab E have locked bootloader? (and if it's locked, is there any way to unlock it?) I'm just asking because I'm probably gonna buy this device next.
Click to expand...
Click to collapse
Sm-t560/560nu does not have a locked bootloader.
Sent from my SM-T280 using XDA-Developers mobile app
ashyx said:
Sm-t560/560nu does not have a locked bootloader.
Sent from my SM-T280 using XDA-Developers mobile app
Click to expand...
Click to collapse
What about SM-T377 ? (This smaller one, 8')
Krystiannnnnn said:
What about SM-T377 ? (This smaller one, 8')
Click to expand...
Click to collapse
As far as I know T377P/R4/W doesn't have a locked bootloader.
Stay away from verizon and ATT models.
Sent from my SM-T280 using XDA-Developers mobile app
thx all for help
Hi Im just wondering if this phone is actually rootable? If so can someone help? Thank you
zipl0cc said:
Hi Im just wondering if this phone is actually rootable? If so can someone help? Thank you
Click to expand...
Click to collapse
Took me less than a minute to locate the following thread that answers your question.
http://forum.xda-developers.com/showthread.php?t=3587174
Good Luck!
***Please Note: As always, I welcome any member to help with further valuable information/clarification for any of my posts.
Sent via Communicator [D2VZW] from the Bridge of the U.S.S. Enterprise...
If you use the method described in the thread DON'T flash the SuperSu zip mentioned until you delete Kingoroot s 'superuser'.
I did this and bricked my phone for about 10 days until I could manage to keep the system running long enough to get rid of all the KingCrap from it.
Better yet NEVER USE KINGOROOT FOR ANYTHING EXCEPT AS A LAST RESORT
I've spent many hours fixing the damage it can do to a system.
Recommendation?
equitube said:
If you use the method described in the thread DON'T flash the SuperSu zip mentioned until you delete Kingoroot s 'superuser'.
I did this and bricked my phone for about 10 days until I could manage to keep the system running long enough to get rid of all the KingCrap from it.
Better yet NEVER USE KINGOROOT FOR ANYTHING EXCEPT AS A LAST RESORT
I've spent many hours fixing the damage it can do to a system.
Click to expand...
Click to collapse
Hi, Steven
As a new forum user, what do you recommend to use to root my phone instead? I have just done this and am having a terrible time with it! I can't move any of the bloatware or anything yet.
Thanks in advance,
Dr Cheryl
DrCheryl said:
Hi, Steven
As a new forum user, what do you recommend to use to root my phone instead? I have just done this and am having a terrible time with it! I can't move any of the bloatware or anything yet.
Thanks in advance,
Dr Cheryl
Click to expand...
Click to collapse
Did you replace the Kinguser (it might be called something a bit different like Superuser) with SuperSu or another SU? That is the first step to get out of the Kingroot trap.
DrCheryl said:
Hi, Steven
As a new forum user, what do you recommend to use to root my phone instead? I have just done this and am having a terrible time with it! I can't move any of the bloatware or anything yet.
Thanks in advance,
Dr Cheryl
Click to expand...
Click to collapse
Welcome Dr Cheryl
If you've rooted your n817 using this method and managed to replace KU congratulations. This one is not an easy root. Id be xurious what you're using to remove bloatware. 3c works good, Titanium backup, theres a lot
You can pm me iff you need help.
---------- Post added at 03:00 PM ---------- Previous post was at 02:57 PM ----------
equitube said:
Welcome Dr Cheryl
If you've rooted your n817 using this method and managed to replace KU congratulations. This one is not an easy root. Id be xurious what you're using to remove bloatware. 3c works good, Titanium backup, theres a lot
You can pm me iff you need help.
Click to expand...
Click to collapse
Rereading your question/ i guess you don't have root. I'm not aware of any other rooting methods for this phone. I've got one in my hands right now I'll be rooting soon, so Ill knpw if the new twrp is working
---------- Post added at 03:01 PM ---------- Previous post was at 03:00 PM ----------
equitube said:
Welcome Dr Cheryl
If you've rooted your n817 using this method and managed to replace KU congratulations. This one is not an easy root. Id be xurious what you're using to remove bloatware. 3c works good, Titanium backup, theres a lot
You can pm me iff you need help.
Click to expand...
Click to collapse
Rereading your question/ i guess you don't have root. I'm not aware of any other rooting methods for this phone. I've got one in my hands right now I'll be rooting soon, so Ill knpw if the new twrp is working
Doesnt work said:
As probably to be expected with this website, yet another complete failure.
Absolutely NOTHING will ever root an N817. Why are people still pushing the obvious lie??
15 attempts. ALL resulted in "root failed".
If you do not know what you are talking about, try NOT posting suggestions because they all lead to the exact same non-functional outcome.
Tried literally everything. All steps posted throughout the internet. NONE of them actually function as advertised.
I am sick of the lies. It is clear that no one on this site actually knows what they are talking about.
The "apps" suggested on this site, along with dr.fone, and even the debloater apps are ALL non-functional.
What is it going to take to stop the lies????
Face it. The N817 can not be rooted nor cleaned up. It is the sole intention of ZTE.
When you call ZTE and navigate past their red tape, you find out the truth.
The device will never allow ANY user access over the device.
STOP the lies and remove this entire topic already.
---------- Post added at 06:13 PM ---------- Previous post was at 06:07 PM ----------
Well, you asked for it. NONE of these suggestions, and NONE of the other suggestions this site has offered works in any way what so ever.
"root failed" is the only outcome for everything this site has claimed.
The N817 can NOT be rooted, nor debloated. ALL N817's are blocked. Meaning that there is no possible way to clean up nor root them. ZTE will tell everyone the same if they bother to investigate the claims made by users of this site.
I have tried everything this site has stated numerous times. The only result possible is "root failed" or device not recognized.
Click to expand...
Click to collapse
Actually, I just obtained ROOT with 360Root that chinese app on android. Then I flashed TWRP, then SuperSU, boom fully rooted
I did some thread cleanup. Please stop the ranting and be respectful to other users.
BIatu said:
Actually, I just obtained ROOT with 360Root that chinese app on android. Then I flashed TWRP, then SuperSU, boom fully rooted
Click to expand...
Click to collapse
Well, some people, like the poster above can't seem to do any critical thinking for themselves. If it doesn't go 'just like the video' heaven forbid they would have to synthesize their own methods.
Hey guys I've tried everything and it's just not happening I have Qlink ZTE 818 with a 7.1.1 OS and it's just not working. I guess I'm not smart enough to do this.
zipl0cc said:
Hi Im just wondering if this phone is actually rootable? If so can someone help? Thank you
Click to expand...
Click to collapse
360root works, but you will lose root if you restart/reboot your system.
Similar result but still not the same.
texas4la said:
360root works, but you will lose root if you restart/reboot your system.
Click to expand...
Click to collapse
I also ran 360root but I tried to run Root Checker and System App Safe Remover and neither worked. Root Checker didn't even pull up the prompt, yet SASR brought the prompt up but still wouldn't remove system apps. Any thoughts from anyone? When I ran kingoroot it brought the menu up at 70% and restarted and nothing changed. I'd like to remove the bloatware not just disable it.
I have searched countless forums and have tried kingroot, kingoroot, 360, the PC version of kingo, I have tried adb root exploits. I have tried fastboot (I have never been able to type "fastboot devices" and receive recognition) I have downloaded Qualcomm drivers, adb drivers, zte drivers. I have used the software for flashing zte devices which failed when I tried to flash. I have enabled developer options and ticked OEM unlocking and USB debugging. The device I am referencing is the ZTE sapphire from qlink. MODEL# Z3001S. If anyone knows a method I'm all ears and would greatly appreciate some help here
Ive got root before on this device. Helped me girlfriends mom out.
Since there are some request from other fellow users, i decide to create a dedicated guide thread to show the process of UNLOCKING BOOTLOADER & ROOTING the Huawei Mate 10 (FOR MATE 10 LITE, CHECK BOTTOM OF THE POST)
Warning : Unlocking bootloader and rooting your phone come with a risk of bricked devices, bootlooping, loss of data, etc. I am not responsible for any harm that can happen during the process , ALWAYS MAKE BACKUP FIRST - use Huawei Backup App to backup your data to MicroSD, or get HiSuite ready to reflash your phone in case of brick situation happen
Pre-requisites :
1. "Enable OEM unlock" & "USB Debugging" option turned on from developer options
2. ADB & Fastboot installed on your WINDOWS 7 (YES, Win 10 has problem with Mate 10 Fastboot driver. except you know how to properly install the driver manually i would suggest you do this on Windows 7) - if you havent, search "Minimal ADB & fastboot" on XDA.
UPDATE : Windows 10 driver fix can be found HERE
3. Download FunkyHuawei Tool from : HERE - ALL CREDIT GOES TO FUNKYHUAWEI for PROVIDING THE TOOL
4. Valid Huawei Account logged in on your Mate 10
UNLOCKING BOOTLOADER
1. Go to : emui.huawei.com/en/plugin/unlock/index
2. Log in using your Huawei Account, make one if you dont have it yet
3. "Agree" to Huawei unlocking agreement presented
4. Input all neccessary values related to your device (the one you want to unlock) - IMEI, Model Number etc
5. Click "Commit"
6. You will get a pop up dialog, containing your unlock KEY. Save this key or screenshot the screen, you gonna need it to unlock your phone
7. Now, plug your phone to your PC. Assumed that you got USB debugging enabled, pop up will appear on your phone screen, asking whether you want to allow the PC to access your phone or not. Authorize the request
8. Fire up ADB on your CMD/Terminal. and type
Code:
adb devices
9. Your devices should listed on your adb window, if it isn't, either you didnt install the adb driver properly, or your usb port has problem
10. Now type
Code:
adb reboot bootloader
to reboot your phone to fastboot mode
11. Once the phone is booted up to the fastboot mode screen, type this in your CMD windows :
Code:
fastboot oem unlock [your UNLOCK KEY here]
- without the brackets
12. Confirmation dialog should appear on your phone screen, give you a warning about unlocking bootloader, just go with proceeding the process (YOU WILL LOSS YOUR USER DATA]
13. Once the unlocking process is finished, your phone will boot up to initial set up stage
14. Set up everything up until you can re-enable USB Debugging option in Developer Options (you can skip all account stuff, security and elses, you gonna do it again anyay after ROOTING)
15. Plug back your phone, and from your CMD Windows, retype this code :
Code:
adb reboot bootloader
16. Your phone will rebooted to FASTBOOT MODE again - now close your CMD Windows
ROOTING
1. Now launch "FHMate10Tool.exe" which you have downloaded from the prerequisites step
2. 5 Options will be presented, and the 1st is "Root your Mate 10"
3. Type "1" and hit ENTER
4. few more dialog and instructions will be given, and Rooting process will started
5. Once the process finished, your phone will booted back to initial set up screen with all USERDATA ERASED, but with SuperSU INSTALLED
CONGRATULATION, YOU HAVE ROOTED YOUR MATE 10
Addendum :
FOR MATE 10 LITE ONLY
Use same step to unlock bootloader.
Download TWRP from HERE and SuperSU from attached.
Place SuperSU to MicroSD and place TWRP img file to your directory in PC where fastboot and adb installed
Reboot to fastboot mode,
Execute this command :
Code:
fastboot boot twrp-mate10-lite.img
Your device will boot into temporary TWRP,
Go to Terminal in TWRP and type this :
Code:
echo "systemless = true" /data/.supersu
(Tick the bottom right corner)
go back to TWRP main menu and choose "Install"
Choose external storage and choose the Supersu.zip file and flash it,
Reboot System
Your device should be rooted.
Note : this method wont install TWRP to your device. You can install it using fastboot flash recovery twrp-mate10-lite.img command, but since the TWRP is still in beta stage, i do not recommend it.
Credit to Aonja for Mate 10 Lite TWRP img
Thanks for the info, I'm having difficulty getting a Windows 7 machine going, anyone know how to install the fastboot drivers manually on Windows 10?
Hello. I request that you don’t link directly to the google drive download page of the FunkyHuawei tool but rather if you want to link, link to the Reddit page that explains how to use it.
duraaraa said:
Hello. I request that you don’t link directly to the google drive download page of the FunkyHuawei tool but rather if you want to link, link to the Reddit page that explains how to use it.
Click to expand...
Click to collapse
Noted, can you give me latest link ?
I was using link that given to me by customer support after purchasing credit
otonieru said:
Noted, can you give me latest link ?
I was using link that given to me by customer support after purchasing credit
Click to expand...
Click to collapse
Check your PM for more info.
Basically the idea is, I might update it if a bug is found/fixed, so it should point to the latest version to avoid issues. If we have a direct link, that makes it difficult. Thanks
ballistykx said:
Thanks for the info, I'm having difficulty getting a Windows 7 machine going, anyone know how to install the fastboot drivers manually on Windows 10?
Click to expand...
Click to collapse
You need to disable driver signature verification on windows 10. And install the huawei driver afterward
duraaraa said:
Check your PM for more info.
Basically the idea is, I might update it if a bug is found/fixed, so it should point to the latest version to avoid issues. If we have a direct link, that makes it difficult. Thanks
Click to expand...
Click to collapse
Done
@otonieru , i have mate 10 standard,
- If i rooted the phone would i still receive OTA ? and if i received and installed them, would that brick my phone or just remove the root?
and if my phone ended up being bricked, is it easy to just flash back the rom of huawei using Hisuite ?
- is it easy to unroot the phone back to original, if i needed to use back the warranty? or maybe just flash the huawei rom.
- can the root be hidden ? like magisk ?
Thank you very much for this thread, it is a must ! <3
Two questions (sorry, I'm new to Huawei world...):
1. UNLOCKING BOOTLOADER does not void my warranty, right?
2. Will I loose root when install OTA update?
taddzio said:
Two questions (sorry, I'm new to Huawei world...):
1. UNLOCKING BOOTLOADER does not void my warranty, right?
2. Will I loose root when install OTA update?
Click to expand...
Click to collapse
1. Yes, it voids it in most cases, but might depend on your local Huawei region.
2. Yes, you lose root.
---------- Post added at 09:00 PM ---------- Previous post was at 08:58 PM ----------
Shady282 said:
@otonieru , i have mate 10 standard,
- If i rooted the phone would i still receive OTA ? and if i received and installed them, would that brick my phone or just remove the root?
and if my phone ended up being bricked, is it easy to just flash back the rom of huawei using Hisuite ?
- is it easy to unroot the phone back to original, if i needed to use back the warranty? or maybe just flash the huawei rom.
- can the root be hidden ? like magisk ?
Thank you very much for this thread, it is a must ! <3
Click to expand...
Click to collapse
If you root you will apparently still receive OTA. Receiving an OTA will unroot your phone, but should not brick it.
You can't unroot the phone back to original. Even if you relock the bootloader, it will show relocked, not locked. There are tools which you'd need to pay for which can help in that case.
The root cannot be hidden.
Anyone who roots, I urge you, be VERY VERY careful. Huawei phones are very finnicky, brick easily (the Mate 10 even more easily than previous versions), and there is no free way to restore them if they do brick. Even with paid methods,
it's not easy.
duraaraa said:
1. Yes, it voids it in most cases, but might depend on your local Huawei region.
2. Yes, you lose root.
---------- Post added at 09:00 PM ---------- Previous post was at 08:58 PM ----------
If you root you will apparently still receive OTA. Receiving an OTA will unroot your phone, but should not brick it.
You can't unroot the phone back to original. Even if you relock the bootloader, it will show relocked, not locked. There are tools which you'd need to pay for which can help in that case.
The root cannot be hidden.
Anyone who roots, I urge you, be VERY VERY careful. Huawei phones are very finnicky, brick easily (the Mate 10 even more easily than previous versions), and there is no free way to restore them if they do brick. Even with paid methods,
it's not easy.
Click to expand...
Click to collapse
Dunno but you people are scaring me of rooting huawei tho i have rooted and flashed so many roms on my LG and other phones...
I mean if i follow the procedures and use your tool wouldn't that just work ? or there are factors that may affect it
Shady282 said:
Dunno but you people are scaring me of rooting huawei tho i have rooted and flashed so many roms on my LG and other phones...
I mean if i follow the procedures and use your tool wouldn't that just work ? or there are factors that may affect it
Click to expand...
Click to collapse
The procedure is safe, but it's what you do with the root powers that could cause a brick. If you touch the wrong file on the phone, caput. In the worst case, the phone won't turn on, won't be recognized with USB, and can't be unbricked.
Obviously you're protected from doing that when you don't have root.
I've already lost two test devices to the symptoms described above.
So my opinion is, as the developer of the tool, root only if it's absolutely essential to you. And if you do root, only use the root privilege for things you absolutely must do, or things that have been tested on the phone and proven to be safe. Hopefully you won't brick it, but I need to put out this warning so I'm not blamed if someone does.
Any other down sides to unlocking bootloader and or rooting on this device eg apps auto removed, loss of camera functionality or codecs disabled etc as seen with other devices?
somemadcaaant said:
Any other down sides to unlocking bootloader and or rooting on this device eg apps auto removed, loss of camera functionality or codecs disabled etc as seen with other devices?
Click to expand...
Click to collapse
None as i may concern. Android pay wont work though, and some banking app as well. Since those app wont allow rooted phone.
But if you didnt use such an app. Or like me, have another phone for that, then its perfectly fine.
For me, there's more benefit / advantage come from rooting
Example :
1. Effective adblocking (not VPN solution)
2. Removing unneccessary stuff and app
3. Youtube without ads + background play
4. Better battery life (with appops, greenify, and my own GMSDoze)
5. Enabling VoLTE option
6. Audio MOD (gain, and better dual speaker)
7. etc
Fastboot driver fix
Use the fix from DC Unlocker for the fastboot driver under Windows 10
https://www.dc-unlocker.com/huawei-mate-10-fastboot-usb-device-not-recognised-fix
ElMartinoAT said:
Use the fix from DC Unlocker for the fastboot driver under Windows 10
https://www.dc-unlocker.com/huawei-mate-10-fastboot-usb-device-not-recognised-fix
Click to expand...
Click to collapse
Thx for heads up,
I'll include it in main post soon
otonieru said:
None as i may concern. Android pay wont work though, and some banking app as well. Since those app wont allow rooted phone.
But if you didnt use such an app. Or like me, have another phone for that, then its perfectly fine.
For me, there's more benefit / advantage come from rooting...
Click to expand...
Click to collapse
Good point about NFC pay methods, I do use those a lot.
I read a few people here having issues with their devices eg here, Lg devices has a similar issue with camera and missing appps, Samsung devices would lose the IR blaster after bootloader unlock.
somemadcaaant said:
Good point about NFC pay methods, I do use those a lot.
I read a few people here having issues with their devices eg here, Lg devices has a similar issue with camera and missing appps, Samsung devices would lose the IR blaster after bootloader unlock.
Click to expand...
Click to collapse
Am still using nfc payment, but not android pay.
Android pay is not even working in my country after all.
Nothing is lose after UBL, this UBL method is official from huawei anyway
It may be that after unlocking the bootloader the theme manager does not correctly apply the themes in emui?
Thanks in advance
sonice21 said:
It may be that after unlocking the bootloader the theme manager does not correctly apply the themes in emui?
Thanks in advance
Click to expand...
Click to collapse
Working just fine on mine. But experience might be vary.