Related
First, props to TeamWin, joel.bourquard, theintelligent, and maybe a few others I'm not aware of...
Second, these are Windows instructions. If you have another OS, you can open the batch files and type the commands inside (or paste them) one by one.
Third, keep in mind that the current temp root is NOT a full root even WHEN it is in place... so don't expect too much! This method has also been modified (by others) so that it does not "randomly" reset and it sticks until the next restart. As a result of how that works, however, even fewer apps recognize root with this method but some do!
Most of this is just other people's work: stuff from several different posts repackaged in a way that I found very easy to use. So I don't take credit for most of the contents, although I did modify the batch files to take care of a timing issue that was causing a fail on most machines. In the end, you should be able to use the attached prepare.bat file to prepare your phone once and then you can use root.bat after each reboot to restore temp root. Create a shortcut to root.bat on your desktop and you can just plug your phone in, click the icon, and you're (re)rooted in about 8 seconds.
The instructions are simple but I elaborate below to try to hit all the stumbling blocks. Basically you just run prepare.bat the first time you do this and from that point forward, you only need to run root.bat after every restart.
Here are the specific instructions:
THE FIRST TIME ONLY:
(1) Unzip contents of the attached ZIP to a folder you'll remember on your hard drive.
(2) Plug your phone in via USB and set it to "charge only" with "USB debugging" under "Settings", "Applications", "Development" turned on. It's best to do this after a fresh (full, not fast) boot. Your phone should be in this mode each time you connect it to root it. Trust me, if you've been using your phone for a while, reboot it first, then wait a few minutes for it to stabilize, THEN do this routine... saves a lot of headaches.
(3) Go to the folder where you unzipped the files in (1) and run prepare.bat. I prefer to do it in a DOS box but you should be able to just use Explorer and double click on the prepare.bat file.
(4) The first thing these batch files do is a check to make sure your computer can see the phone. If your phone isn't in the list, Ctrl-C and break out of the batch file. You'll have to correct the problem which will most likely be an issue with the HTC drivers. If your phone is not found, try these x64 drivers... or these if you're running a 32 bit OS. To install these, go to Control Panel and click on your Android device and do "Update Drivers" and browse to the location of the drivers you downloaded.
(5) Assuming your phone is on the list, everything should be ready to go. Press enter and the batch file will proceed and it will root your phone.
AFTER DOING THE ABOVE ONCE, AFTER EACH REBOOT:
(1) Attach phone and double click the root.bat file.
(2) Again, verify that your phone is on the list (proves your PC can see the phone). If so, press enter and the phone will be RErooted.
That's it! Works for me. Keep in mind that temp root is NOT a full root! Many apps will not run (won't see root) but that's just the nature of the current temp root. But some apps do work. Barnacle WiFi does for example: although sometimes it take two "start" presses to get it to connect as the first one sometimes produces errors. People say Titanium Backup and some other apps work: I haven't personally tested them. As temp root is really for dev and testing, test what you want and see if it works.
Hope this helps some of us to get a quick and easy temp root. If any issues are found, I'd be glad to modify this initial post and/or modify the batch files if any errors are found.
Mike
I can't get to the site to download the 64-bit drivers for windows. Anybody has an alternate links? Thanks.
Does this really work? How is this thread not blowing up??
vWvSTATICvWv said:
Does this really work? How is this thread not blowing up??
Click to expand...
Click to collapse
Really! Anyone out there? I expected to come back from lunch to find questions I needed to answer or maybe a suggested modification or two. This has been working for me for over 12 hours now. No restarts. No reverting to non-root. Barnacle Wifi Tether is still working. And the best thing is, if I have to restart the phone for some reason, I connect it to my computer, click, and 8 seconds later it is rooted again and I unplug it and go on my way.
Mike
can you run a wireless tethering app after temp root?
edit: see mikeyxda's post above this
I was hoping to be able to help some people with the Barnacle WiFi Tether app because a lot of people complain that they didn't get it to work and I suspect I got it to work with some combination of settings. Only problem is: I don't know how my Barnacle settings differ from those other people are using so I wanted to compare with others. Short on time right now but later I'll try to post my entire list of Barnacle settings. They work for me.
Edit: Oh Hell... I have a few minutes, here are my settings:
SSID: Evo 3D Tether
BSSID: <blank>
Wireless Encryption: not enabled (open)
Channel: mine is 6, probably doesn't matter
Custom Wifi Ad-hoc: none
Skip wpa_supplicant: NOT checked
Auto Associate: NOT checked
Access Control: NOT checked
New Client Actions: Notify Checked, nothing else checked
Local Mode: NOT checked
DHCP: Didn't mess with these
NAT: Didn't mess with that either
WAN: rmnet0 (whatever that means)
LAN: Blank
Mike
it seems like the link for the 32bit drivers is down also....
i ran batch files as OP directed, they run successfully, but when i go to start barnacle tether it doesn't have root. same for the "wifi tether for root" app. tried full reboots several times, no help.
os10 said:
i ran batch files as OP directed, they run successfully, but when i go to start barnacle tether it doesn't have root. same for the "wifi tether for root" app. tried full reboots several times, no help.
Click to expand...
Click to collapse
Try making sure fast boot is turned off and then power the phone down and power it back up. Then use the root.bat to reroot. Might not work the first time.
For those having trouble with the driver links, try this link. It's kind of a convoluted mess with countdowns, etc. but seems like the files are there. I haven't verified them yet though.
Mike
Gave it a shot, doesn't quite seem to be working for me.
johnsmusicbox said:
Gave it a shot, doesn't quite seem to be working for me.
Click to expand...
Click to collapse
What is it that isn't working: the rooting process itself or Barnacle? I was hoping to give enough feedback in this thread to get things working for the people who say "it doesn't work" because I've been watching other threads and most of these methods seem to be very inconsistent, meaning, they don't work for a lot of people. My intention was to find the kinks and get it working for the vast majority. If you can give me details like what you see during the process, whether any error messages display, and so on, we might be able to get a more reliable temp root.
Mike
Titanium backup is definitely not working with this.
So what's going on with this? Anyone got it to work?
OK, let's try this. This is a "cleaned up" version of a different method posted in another thread. Comes with 2 batch files. Run root-init the first time and then root-redo each time you restart after that. Let's see if this works better.
Mike
Ok...My guess is that people are scared and don't know exactly what they're flashing. Would you mind sharing the source of your find, Mike? If this does indeed work, I can't see people not using this method. HmMm
*EDIT* I found the source is from XHAUSX
*EDIT 2* IT WORKS!!
EDIT: DEAD. Unlock you bootloader and get perm root.
It still uses zergrush and absolutely does not provide any other capability than other temp roots. (Although some people have reported root apps see root better so it might actually be better). The only difference is I have the things relating to root (ie su,busybox, etc) stored in a ramdisk that lasts alot longer than things "written" or linked to /system. This is because we still have /system write locked so when we write things to it (like the original zergrush implementation) it gets forgotten after while.
Your mileage may vary. I am obviously not responsible for bricks, data loss, etc if you use this. I and others have used it for about a week and it has been fine.
To use:
0) Make sure superuser isn't installed
1) Reboot phone (full reboot), make sure usb debugging is on.
2) Plug in phone in charge only mode to PC.
3) Kill everything in the built in task manager, then go back to the rosie home screen.
4) Extract zip and doubleclick temproot.bat
5) There is a 20 second time out at the beginning just in case you forgot to plug in your phone, etc so you have time to cancel the process before it starts. To skip it just hit enter on the keyboard or wait the 20 seconds.
6) Hit the thanks button (bottom left of this post) if you like it!
Let me know if you like it better or if something bad happens so I can take it down. Lets hope we get S-Off soon and don't have to deal with this temp root **** anymore.
Troubleshooting:
1) Bootlooping? Pull the battery. If you still are boot looping, an RUU restore may be necessary. I believe this has only happened to one user and it was likely a result of something that was done AFTER root and not directly caused by this program.
2) Just not working? Reboot both your PC and Phone. If ADB cannot see your phone, it is not a fault of the program. If you haven't gotten other temp root methods to work, it is likely this one won't either.
3) If you want bluetooth to work while you are rooted, turn it on before running this app. It won't toggle on for some reason after the program is run.
Finally, if you want to contribute, thank the Revolutionary team for their work on the zergRush exploit!
ok so let me be the first to ask.... what's "better" about it?
It should stick longer.
has anyone figured out exactly why we lose root within minutes?
So every time we want to use this root again we'll have to uninstall SU first?
You can probably run without but I have always removed it first
ya it worked perfectly thanxs
You have to have drivers installers and such before you do this method? Thing is ny computer broke so I would be using a school computer which restricts me from downloading htc drivers
Sent from my ADR6425LVW using xda premium
The root access is definitely better. I have root access apps that would force reboot my phone before that actually run now. Nice work! It definitely sticks longer.
bast525 said:
has anyone figured out exactly why we lose root within minutes?
Click to expand...
Click to collapse
Since we don't have write access to /system. When the superuser stuff gets "written" to /system it really isn't so it goes away randomly after awhile. This helps to prolong the life of superuser.
NoNotReally said:
So every time we want to use this root again we'll have to uninstall SU first?
Click to expand...
Click to collapse
I am not sure... Try it. If you do I can have the script uninstall before it runs perhaps.
bokechukwu1 said:
You have to have drivers installers and such before you do this method? Thing is ny computer broke so I would be using a school computer which restricts me from downloading htc drivers
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
Yes this just is what I think is a better root method. It is the same exploit, it is just stored on the device a bit differently.
mohkg said:
ya it worked perfectly thanxs
Click to expand...
Click to collapse
Good to hear.
flexor224 said:
The root access is definitely better. I have root access apps that would force reboot my phone before that actually run now. Nice work! It definitely sticks longer.
Click to expand...
Click to collapse
Also good to hear.
It has worked to control setcpu profiles for me very well over the past few days so it has stuck for about 72 hours+ for me before I rebooted to retest this script before release.
confirmed, this root is definitely working better. not only lasting longer, but some apps that require root that wouldn't work or wouldn't work fully before are now working. for instance, I have an sql database editor app that was not recognizing root before and wouldn't let me edit databases. works perfectly now. I want to try WiFi tether but do we know if Verizon can detect this now?
also, I'm guessing you're setting some low clock speed with setcpu when asleep/idle... noticing better battery?
Thank you! This works amazingly well. My root actually sticks this time. It doesnt give me a single issue.
Thank you once again!
I have run this script several times now and no worky.
- Installed drivers (no old drivers to conflict)
- fresh reboot, charge only, USB debug, tasks are terminated
- adb sees my device
SU does push to the phone, but apps like TB cannot get root access. Any thoughts folks? I have tried ever one of these temp root methods without success.
plug in your phone for me. Then shift+click on the folder that you extracted the stuff to and do open command prompt here or whatever. Then in there type adb shell and see if you get a shell.
It is likely if you haven't gotten success before this won't help. This is just and improved root, but not an improved way to get it on the device.
con247 said:
plug in your phone for me. Then shift+click on the folder that you extracted the stuff to and do open command prompt here or whatever. Then in there type adb shell and see if you get a shell.
It is likely if you haven't gotten success before this won't help. This is just and improved root, but not an improved way to get it on the device.
Click to expand...
Click to collapse
I have shell con.
My root held overnight. I was able to clear battery stats using Battery Monitor Widget (other temp roots could not), and using CPU Boost to underclock and run a screen off profile.... unfortunately I'm not really noticing any better battery.
Irieone said:
I have run this script several times now and no worky.
- Installed drivers (no old drivers to conflict)
- fresh reboot, charge only, USB debug, tasks are terminated
- adb sees my device
SU does push to the phone, but apps like TB cannot get root access. Any thoughts folks? I have tried ever one of these temp root methods without success.
Click to expand...
Click to collapse
Adb can see your device but still doesn't work..... Post the output from an adb command and maybe we can help.
Sent from my HTC Rezound via the XDA app
Definitely the best temp root method so far!
Already past 24hrs! Past methods would last an hour or so. This is awesome. How did you figure this out? Maybe it'll help those trying to get S-Off? Thanks!
It won't help with perma-root/s-off. I figured a ramdisk wouldn't get killed nearly as fast as the fake /system write does.
I am able to get it to run through now. At the end it tells me it needs to reboot my phone, enjoy root, etc... When the phone reboots. It boot-loops. I have to pull battery.
my method here will give you a permanent rooted shell and will give you read-only system root which is useful for using root apps to backup data or freeze system apps--works just like real root without being able to delete system contents--freezing apps however works like a charm and should reduce the need for rw root anyway
FOLLOW DIRECTIONS EXACTLY--I WILL NOT RESPOND TO STUPID QUESTIONS--PROBABLY WON'T RESPOND TO ANY QUESTIONS BECAUSE MY DIRECTIONS ARE PERFECT, WORK PERFECTLY WHEN FOLLOWED, AND ARE EASY TO READ. FOLLOW ALL STEPS EXACTLY. IF IT DIDN'T WORK, IT IS BECAUSE OF YOUR ERROR
This works best from a factory reset device, but will work from a already used device but all other root apps and superuser apps must have their data deleted and be uninstalled first
1) make sure device is at least 50% charged--doesn't matter most of the time; better safe than sorry
install latest superuser apk
http://www.mediafire.com/file/dx854fsys5pvxjh/SuperSU.apk
install dirty cow root apk (croowt) [comes from this post https://forum.xda-developers.com/android/software-hacking/root-tool-dirtycow-apk-adb-t3525120
http://www.mediafire.com/file/1hbey829hc7676a/CRooWt.apk
make sure usb debugging is activated in developer settings and make sure you have accepted the debugging access prompt on the phone for the computer you will use
make sure you have an external sdcard installed--the smaller the better for this first time
2) open dirty cow root apk
choose "get root"
choose "method 1"
hit "ok"
choose "ok"
app will direct you to unmount and remount sdcard, choose "ok" and it will take you to storage settings
unmount sdcard
remount sdcard
when finished proceed to step 3
3) open superuser
do not update su binary
go to settings and make the default action "grant"
remove any and all apps from superuser log including the croowt app
3) THIS MUST BE DONE FROM A REAL TERMINAL ON A PC--TERMINAL EMULATORS WILL NOT WORK FOR THIS STEP
from a working pc with adb setup, preferrably linux, input commands exactly as listed
adb shell
su
setprop persist.sys.k P816A06
reboot
5) once rebooted, open dirty cow root apk again
choose get root
choose "method 2"
hit "ok"
choose "ok"
if app asks you to open with a browser, choose one, and choose "always"
screen will go black, systemui will crash and then reboot
6) once systemui is back up and running
you now have read-only root
you can now freeze system apps or backup your data using apps that require root
Your shell will be permanently rooted when accessed from a computer using adb--this will last forever unless you undo the setprop
Your system however will only be temp, read-only rooted until the phone is rebooted.
If you wish to have your temp, read-only root reactivated, all you have to do is repeat step 5 and that is it.
You can do this over and over again.
GIVE STAYBOOGY SOME PROPS FOR MAKING YOUR LIFE WITH THIS PHONE BETTER
Does this only work to back up or freeze applications?
poseidon207 said:
Does this only work to back up or freeze applications?
Click to expand...
Click to collapse
ACTUALLY READ the first sentence of OP
I don't see how freezing system apps would negate the need for a real root method? Is this "Read-Only" root method working with lucky patcher or Kernel Auditor?
Can this be used to bypass the subscription check for tethering? I assume not since system isn't writeable.
Does this method work in the ZTE Maven 3 (Z835)?
I'm doing it wrong, probably
First of all, thank you so much for doing this. I've been following that other thread since it was new, and you've put far more effort into this than the phone or most of us deserve.
I've gotten stuck trying to run Dirty Cow. I have USB Debugging enabled, adb installed on my Linux computer which recognizes my Maven (i.e. I've allowed access on the phone), etc. It eventually goes from "Checking vulnerability" to "Your device is not vulnerable" and I'm unable to proceed to the "Get root" step. What am I doing wrong? Might be some recent system update? Probably less effort to just buy a Galaxy.
Please be gentle. I know I'm a noob.
z812 root
I previously rooted my maven with kingroot and the dirtycow exploit.sh file and today I was overwhelming the device by running multible windows and apps and the phone rebooted and root was still intact....haven't rebooted it again yet but I shall.
Following the instructions from this post (except don't rebook at the end) https://forum.xda-developers.com/showpost.php?p=61736387&postcount=15 I was able to successfully tether on the LG G6 h871. The data flows from phone to whatever wifi device smoothly.
The thing I'm still working on is that the changes don't persist if the phone turns off. The settings reset when the phone is restarted. Anyone know how to make the changes stick?
Thanks!
Here's a brief update.
You can actually make these settings from within your phone, instead of through the ADB command, which is useful in case you suffer an inadvertant reboot while in the field. Still haven't been able to make the settings persist through reboot however.
Taken from here https://forum.xda-developers.com/att-lg-v10/help/activate-hotspot-unlocked-lg-v10-t3585697
You use the Settings Database Editor and find these entries in there (you have to find the one in both the System and Global tables).
The setting in Global table "tether_dun_required 0" is protected and won't let you edit it.
You can change this using ADB, and fortunately granting these permissions is a one time process that does persist through normal reboots. https://forum.xda-developers.com/tm...settings-database-editor-tweaks-t3609876/amp/
"adb shell"
"pm grant by4a.setedit22 android.permission.WRITE_SECURE_SETTINGS" (check this command against the text the app pops up when you try to change the protected setting)
"reboot"
Now you are able to go into the Settings Database Editor app and modify these two settings
Global table "tether_dun_required 0"
System table "tether_entitlement_check_state 0"
And viola you will have a working wifi hotspot on your unrooted stock phone. Hopefully I can figure out a way to make these changes stick through reboots though, because it is a bit of a hassle to click through the app anytime it reboots, but at least it works, and it's certainly better than the popping out your sim card trick and trying to time shoving it back in just at the right moment during the wifi hotspot creation trick.
I used to use this trick but tried the other day and while I was able to connect to the hotspot I could not get internet on any device. Anyone else notice this.
Is this issue specific to the h871 / AT&T? On h870 (carrier free) you can just enable it in settings...
Worked very well for me, thanks! Did you get around these settings stick after reboot?
First of all, Obi is a Chinese OEM. So the support for their products is very bad. Unlike renowned Chinese OEMs like Xiaomi and OnePlus. They never bother to release their kernel map. So most rooting apps won't work. Then they have implemented Bootloader lock, Signature Verification at boot, Secure Boot and A/B authentication and secure Ramdisk. All these are good from a security perspective. Would've been one of the most secure devices had they continued to support it by regularly patching security updates.
This was a bit of hit or miss on my part, I admit. But I'm proud and happy with the results. So let's get right to it. Follow the steps in the sequence otherwise can't guarantee whether it will work or not. There'll be video link posted. Showing the process or part of it at least. So you can use it for reference. I'm working on a custom ROM for this device as well. I'll also be porting a CWM/TWRP recovery for this device, unofficial as it's my personal project. The file lists and maps will also be uploaded for anyone who wants to help. This process also works on Obi Worldphone SF1.
Here's the video tutorial:
youtu.be/MmkaCb2C8wY
Step 1: Download Kingo ROOT 4.5.8 from the official website. Make sure your phone is charged. Close all apps running in the background using recents. This is done as the phone is very slow and underpowered. This is to help prevent it from crashing due to it's underwhelming performance.
Step 2: Click on One-Click Root in Kingo ROOT app. Wait for it. It'll be slow at 30% and 80%. Leave it as it is. Don't disturb and touch it. You'll see Rooted Successfully.
WAIT. DON'T START REJOICING NOW.
Step 3: Since the phone is Bootloader locked, what we have achieved here is a temporary root. The moment you reboot it, the root will be lost. If you want to make Payments, use apps which won't work on Root. You can leave the phone as it is. And root everytime you reboot. Following the same process. That way you'll always be able to retain that system intergrity and never lose your Bootloader locked status. The phone will be as secure as possible after a reboot. But in case, you want to keep the root after reboot and permanently root it. Follow the steps below.
Step 4: Since the Bootloader is locked, the SuperUser app can't be moved to /system/app directory. The temporary root won't allow such /system/ modifications. So to completely breach the system protection against rooting. We'll need BusyBox, Magisk Manager and XposedInstaller. Download from the official sources.
Step 5: Install BusyBox, Magisk Manager and XposedInstaller.
Step 6: Open BusyBox app and press Install. Wait for it to complete. You may notice that you were not asked to give it root/su permission. This is because of Temporary Root. It'll continue to grant all apps which require root permissions. So always be careful that you don't have harmful/malicious apps installed.
Step 7: Open XposedInstaller and install Xposed Framework. It'll reboot automatically. Once done, proceed.
Step 8: Now open Magisk Installer. There'll be two Install options one for Magisk and the other for Manager. If an update is available for the Magisk Manager from within the app, install it. It'll download to your Internal storage/Download/ directory. Install it directly or manually by going to that folder. Now install Magisk. You can choose to preserve AVB 2.0/dm-verity and force encryption if you still want to retain SafetyNet features. I'd recommend you to uncheck both else you may suddenly lose root access with no way to root it again. Hit next. In method, select Direct Install(recommended). Hit Let's go. Wait for it to complete. It'll download it from the internet then flash it. In case, you encounter, Signature Verification failed, reinstall XposedInstaller and retry.
Step 9: Will all that done, if you're greeted with Installed in Magisk. Then reboot your phone.
Step 10: Make Magisk Manager using Lucky Patcher as System App. It'll automatically do it for you. Otherwise you can use RootExplorer/ES File Explorer(first turn on Root Explorer and grant SU permission to ES File Explorer; yes this time due to successful install of Magisk it'll show a toast for 10 sec. to ask for root permissions) then go to system/app/MagiskManager (create this folder) then drag and drop the apk. Rename the apk to MagiskManager.apk and set permissions as rw_r__r__ using properties of either explorer. Then uninstall the app. Then reboot. You may need to repeat step 8 after re-rooting using Kingo ROOT app.
Step 10: After all this is done, just uninstall Kingo ROOT or leave it(In case, you choose to preserve the AVB2.0/dm-verity and force encryption, as you'll suddenly lose the root some day randomly). And you're done.
Things to keep in mind: In case, Root Unsuccessful using Kingo ROOT app. It'll ask to try using the PC Version. There's no need for it. The PC version won't work and no other ADB or Fastboot method work to unlock the bootloader of this device. Just go to app info and clear data. Then try again. This should fix the issue. You must have developer tools unlocked and ADB Debugging turned on. OEM Unlocking should be turned on as well.