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!!
Related
Now, using my Archos 70IT machine,
After bootup, I need to run z4root (temp root) to root the machine,
then, I open up the setcpu to check the CPU frequency profiles,
repeating the steps again and again for each boot up...
Heard that it is hard to root as the system files are protected using a squashfs compressed image (with encryption?)
Cannot touch the system files make me feel sad
- I want to modify the hosts file to bypass all the advertisements
- I want to remove not-used system apps
- I want to modify the init.rc (maybe lagfix?)
- I want to apply wifi ad-hoc fix
- bla bla bla....
So, I would like to ask for the progress of rooting? Any news? Anything I can help to speedup the investigation?
Many of plenty of thanks to all those rooting gurus ~~~ !
I also have same problem. Can anyone advise how to resolve. Many thanks.
I think, though I can very easily be wrong, the problem right now is gaining write access to the partitions, the main system partition is mounted Read Only.
I'm trying to find time to look at this but I don't think I'll be able to get any time untill the weekend.
DougEdey said:
I think, though I can very easily be wrong, the problem right now is gaining write access to the partitions, the main system partition is mounted Read Only.
I'm trying to find time to look at this but I don't think I'll be able to get any time untill the weekend.
Click to expand...
Click to collapse
Yeah, from following a bit of the action over at archosfans.com forums it seems the system is mounted as a read only SquashFS image.
As soon as I get my A101 I'll dig deeper into this problem. Hopefully we'll get a working solution
chulri said:
As soon as I get my A101 I'll dig deeper into this problem. Hopefully we'll get a working solution
Click to expand...
Click to collapse
Yes, I've been holding my order for the Archos 70 to see if root would seem plausible and I just ordered it now. A section at XDA together with Archos release of the source should help us in search for enlightenment
Delivery in 2-4 days, final exam for some electronics course next week and then I've got 30 days off Uni to spend on this...hopefully
I have an A70IT 8 GB and have yet to successfully get z4root to work on it. I'm using the latest version (downloaded today).
I look forward to hearing how some people are successfully doing it, at least I get the impression on the fan site, they are doing it successfully. If anyone knows or has the time / desire to help a fellow Archos user out, please feel free to contact me.
Bert Moshier
BGMArchos said:
I have an A70IT 8 GB and have yet to successfully get z4root to work on it. I'm using the latest version (downloaded today).
I look forward to hearing how some people are successfully doing it, at least I get the impression on the fan site, they are doing it successfully. If anyone knows or has the time / desire to help a fellow Archos user out, please feel free to contact me.
Bert Moshier
Click to expand...
Click to collapse
I had the same problem with Z4Root not working. I found that powering off (complete power off, no suspending or rebooting) the device and starting it back up again did the trick. I also found that I have better success getting Z4Root to run if its the first program I run after a fresh power up. Don't run anything until you Z4Root.
Let me know if this works for you or not.
I've been having inconsistent results, but just stumbled across something that might help.
set airplane mode
turn off unknown sources
turn off usb debug
power off
power on
reset airplane mode off/on (doesn't look like it is really on on reboot)
turn on unknown sources
turn on usb debug
run z4root
wait.
seems to be working more consistently. I think these tablets don't save the state of things like unknown sources and usb debug (and airplane mode) very cleanly.
does this proxy app work with z4root ?
http://forum.xda-developers.com/showthread.php?t=766569
i really would like to use the wifi at my university with my archos.
I've been using it for some time. The only trick is that you need uncheck USB Debugging and recheck every time you run the z4Root app. Doesn't matter if its currently on, uncheck/re-check and you'll be good.
kenyu73 said:
I've been using it for some time. The only trick is that you need uncheck USB Debugging and recheck every time you run the z4Root app. Doesn't matter if its currently on, uncheck/re-check and you'll be good.
Click to expand...
Click to collapse
Shouldn't it be possible to write a simple app that does this automatically on each startup after launch?
Tasker probably can. I haven't installed it to test yet.
Edit: Scratch that. USB Debug toggle is still on Tasker's to do
hosts file is now temporary editable: http://forum.xda-developers.com/showthread.php?t=866104
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.
The multi user and guest account feature is not available on either of the two recent releases of Lollipop for the Z3v. I did some research and it appears this is the case, not only on other Verizon handsets like the Droid Turbo and the Galaxy S5 / S6, but a few other non-VZW devices as well. I'm not sure why it was removed but apparently it's just hidden. It can be enabled and I followed the instructions for doing this for the various other devices and can report that it works for our Z3v (see attached screenshots).
I've kind of cleaned up the instructions and put them below. Usual disclaimer - I'm not responsible for anything that may happen to you or your cat if you choose to do the following. You DO need root access to edit and write to the system file.
** To be safe, please make a backup of your phone and/or a copy of the build.prop file that you are going to edit.
Get ES File Explorer. Run it and enable Root Explorer setting. (You may be able to use any file explorer and editor with root access but this is used most in the instructions and works.)
With ES File Explorer, go to device/system/ and find the file: build.prop
Choose to edit it with ES Note Editor.
Scroll to the end of the file and type in the following:
fw.max_users=5
fw.show_multiuserui=1
Save the file.
I'm not sure if the next step is required but it was in half the instructions I saw, and I did it myself: Click and hold the file, go to Properties, and then change the permissions to Read, Write & Execute. [all three]
Reboot your phone.
When you're up and running, access multi user mode by pulling down your notification shade and then clicking on your user icon at the top right corner.
Notes so far:
A guest user does not have access to the original user's files on the internal drive - the guest user has their own file directory. The guest CAN access the External SD Card, though.
Therefore, an app such as Movie Creator can and will create a "highlight" movie that is composed from photos that are saved on the external SD Card. Just keep this in mind as far as privacy.
There is a per user option that lets you decide whether or not the additional users can use the phone and access the text messages. If you disable this ability, while they cannot open the phone app to make a call, the CAN receive an incoming call.
You can find out more about the nuances of additional users with your Google Fu.
Enjoy!
Wow! Great work!
AddictedToGlass said:
Wow! Great work!
Click to expand...
Click to collapse
Thanks! I really wanted this feature and it seemed like not many people care too much about it. It's my way of circumventing the awful permissions control we currently have in Android. That is, there are apps I want to use but refuse to install because of their overreaching permission requirements (contacts, etc) and so I can now create a second user with a new "dummy" Gmail account that has no sensitive information and install these apps without worrying.
By the way, something neat I figured out about this. Additional user accounts are not allowed to side load apps (the toggle to install from unknown sources is grayed out). I figured out that if the main user / owner restores an app through Titanium Backup, any other currently existing user will have it installed for some reason. I don't know why this happens but it's a neat glitch that gets you around that restriction.
Well I think most people simply don't let others touch their phones and so don't have a use for multiple user accounts. I find that my phone, as big as the screen is, is becoming more and more of a computer / tablet replacement. I like the idea of a multiuser functionality, but mostly to hide my own stuff. I'll silk never let anyone else touch my phone!
The use for multi-user that I've seen that makes the most sense is people with children. They will create a user profile for the child so they can't get into any of the parent's stuff or settings. That or the guest profile which will let them do whatever the heck they want without screwing up the phone.
Aside from that I have read that devs find the feature very useful for testing. Heck, that's not a bad idea to install and test apps, in general.
uh oh.
Well something didnt work. Maybe a certain build I have to be on or what. I followed the instructions to a t. Now stuck on endless boot loop. Only bad part is I'm on as hotel room working out of town without a laptop Or pc to fix it. I used a one click root just today and didn't install a proper recovery. Any thoughts
rpelljr said:
Well something didnt work. Maybe a certain build I have to be on or what. I followed the instructions to a t. Now stuck on endless boot loop. Only bad part is I'm on as hotel room working out of town without a laptop Or pc to fix it. I used a one click root just today and didn't install a proper recovery. Any thoughts
Click to expand...
Click to collapse
I had a problem with this also twice cause I'm always doing stupid things to my phone my guess is you didn't change the system to r/w but modified it anyway or you used a editor that would let you input the correct values I used s manager I think. As far as getting your phone working you could try safe mode or maybe a factory reset if you can hold power and the volume button down and enter recovery.
Tigerhoods said:
I had a problem with this also twice cause I'm always doing stupid things to my phone my guess is you didn't change the system to r/w but modified it anyway or you used a editor that would let you input the correct values I used s manager I think. As far as getting your phone working you could try safe mode or maybe a factory reset if you can hold power and the volume button down and enter recovery.
Click to expand...
Click to collapse
I believe the mistake was made when i changed the permissions per instructions. I finially got to my house and im using adb to freeze the loop then going to push a script over to fix the permissions. I will update when i get it done and I will post my fix. Also I used ES file explorer, which i have already used it for years now. Never had anything like this happen before. it just baffles me. I have never got any instructions off of XDA that led to any malfuntion of my phone. But oh well, sh!+ happens.
rpelljr said:
I believe the mistake was made when i changed the permissions per instructions. I finially got to my house and im using adb to freeze the loop then going to push a script over to fix the permissions. I will update when i get it done and I will post my fix. Also I used ES file explorer, which i have already used it for years now. Never had anything like this happen before. it just baffles me. I have never got any instructions off of XDA that led to any malfuntion of my phone. But oh well, sh!+ happens.
Click to expand...
Click to collapse
Hey! I'm so sorry! I got a couple of new phones (Droid Maxx 2 and LG G4) and have been using those phones so I haven't been checking these forums like I was when I just had the Z3v. Really sorry to hear that you ran into that kind of trouble . Thing is, the instructions above are culled from 4 or 5 different sets of instructions for various devices that I found across the web. I performed them step by step myself while cross referencing them to each other and combined them all to the instruction set above as I did it. Did you ever fix it with the method you mentioned? I'm curious if it was the permissions thing (odd, because it worked for me).
Jurassic Pork Fried Rice said:
Hey! I'm so sorry! I got a couple of new phones (Droid Maxx 2 and LG G4) and have been using those phones so I haven't been checking these forums like I was when I just had the Z3v. Really sorry to hear that you ran into that kind of trouble . Thing is, the instructions above are culled from 4 or 5 different sets of instructions for various devices that I found across the web. I performed them step by step myself while cross referencing them to each other and combined them all to the instruction set above as I did it. Did you ever fix it with the method you mentioned? I'm curious if it was the permissions thing (odd, because it worked for me).
Click to expand...
Click to collapse
it is guys if done right your system needs to be switched to r/w then go back to r/o after modifying the build prop if you modify in r/o you will get bootloop to a hard brick it depends.
Jurassic Pork Fried Rice said:
Hey! I'm so sorry! I got a couple of new phones (Droid Maxx 2 and LG G4) and have been using those phones so I haven't been checking these forums like I was when I just had the Z3v. Really sorry to hear that you ran into that kind of trouble . Thing is, the instructions above are culled from 4 or 5 different sets of instructions for various devices that I found across the web. I performed them step by step myself while cross referencing them to each other and combined them all to the instruction set above as I did it. Did you ever fix it with the method you mentioned? I'm curious if it was the permissions thing (odd, because it worked for me).
Click to expand...
Click to collapse
Well I kinda fixed it. I went and bought a HTC M9. Lol but not yet, I'm still working on it. I have found scripts to run, even a specific build.prop fix to push, but I have windows 10 and couldn't get adb to find the device. Plus I'm a little rusty. So I broke out my old windows 7 laptop I have used just for rooting an modding phones and tablets. I did get adb and fastboot to find it once. Then some reason lost it. I didn't have it ready to go. But I'm almost 100 percent sure I can get it. Just need to play around with it a little bit more. Having trouble with drivers etc. I will let you know when I have it.
And didn't really hurt my feelings getting the phone I truly want. I never had problems with HTC since I was flashing roms on my old window phones. I just want my pictures I cannot replace.
"Run it and enable Root Explorer setting. (You may be able to use any file explorer and editor with root access but this is used most in the instructions and works.)"
Alas- I am not rooted, and therefore can not enable "Root Explorer" option. Unless someone has some other suggestions- I think I can't do this unless I'm rooted.
Well this is probably what I did to brick my first z3v.
I don't suggest anyone do this at all. There does seem to be an issue with the permission setting on the build.prop file. If it's not reset correctly after editing, you'll get stuck in a loop or worse. I'm stuck in bootloop, but can get into recovery. I made a backup hoping to learn how to edit the build.prop (delete it and rename the copied original to set it back as it was). But I can't even run the original zip that GigaSPX made up for us. (I don't have a backup like I hought I did.)
Anytime I try to install the flashable prerooted zip it tells me it's done after 2 seconds and says;
set_perm: some changes failed
I'm typing this on my z2 tablet, which has the multi user feature enabled. I'm going to see if RootExplorer will give me some clues as to why this doesn't work.
In the mean time I'm hoping someone can help me out?
If love to get this feature to work, but it has to be safe.
Just checked the build.prop on my tablet and got no clue.
AddictedToGlass said:
Well this is probably what I did to brick my first z3v.
I don't suggest anyone do this at all. There does seem to be an issue with the permission setting on the build.prop file. If it's not reset correctly after editing, you'll get stuck in a loop or worse. I'm stuck in bootloop, but can get into recovery. I made a backup hoping to learn how to edit the build.prop (delete it and rename the copied original to set it back as it was). But I can't even run the original zip that GigaSPX made up for us. (I don't have a backup like I hought I did.)
Anytime I try to install the flashable prerooted zip it tells me it's done after 2 seconds and says;
set_perm: some changes failed
I'm typing this on my z2 tablet, which has the multi user feature enabled. I'm going to see if RootExplorer will give me some clues as to why this doesn't work.
In the mean time I'm hoping someone can help me out?
If love to get this feature to work, but it has to be safe.
Just checked the build.prop on my tablet and got no clue.
Click to expand...
Click to collapse
a backup usually means going into your twrp and hit the back up button and make a copy of your system including data and all that. This is mandatory before messing with the build prop. If you want Pm me your build prop and I will send it back to you. With multi user enabled.
Yup, I know what a back-up is and how to do it, and I know it's a must before messing with the build.prop. I just really thought I had done it recently...
-and I had! But I forgot that a few days ago I bought myself a Christmas present; a 200 Gb micro SD, and copied most of the contents to the new card from my old one. I chose not to copy the backup because I had planned to make some changes and create a more recent backup. Never happened though because I got side tracked loading music and such. Lol!
So I'm all back together, but would still like to play with this feature. So I'm going to give it another shot.
A guest user does not have access to the original user's files on the internal drive - the guest user has their own file directory. The guest CAN access the External SD Card, though.
Click to expand...
Click to collapse
Perhaps the wrong thread but: enabled multi user on a Cube T8 only to find that guest and other user can access INTERNAL sd but not external sd. I'd rather have it the other way round. So the kids (other users) can use the whole of 32 GB sd card rather than me having to share the small internal sd with them.
Any ideas how to fix this? Phablet is not rooted btw.
got bootloop..... but i'm safe as i've backup.... through recovery..
I've inserted two lines and fell in bootloop
Thanks bro.. working....!!!! but second step is not needed...
I am making this tutorial as I have had multiple versions of the LG LTE Leon and have used many firmware versions. I have created a stable method that has the least issues as I have had trouble with the latest firmware (MS34510f) disabling my root privileges. I have created a MEGA account specifically for all of the files necessary to complete this operation and have your device run smoothly. So, please follow my instructions exactly as stated and you should not have any issues. THIS PROCESS WILL REMOVE ALL DATA NOT SYNCED, DO READ BELOW NOTES IT IS VERY BENEFICIAL
Important Notes:
+This process will wipe all data that is not synced, it is important to ensure that no newer LG process are still on the device. Some might argue to leave data, to that I say good luck keeping your root and tethering without the device becoming suspiciously unstable.
+ I am not GUARANTEEING this will work on every model, but I have had an extremely high success rate with all Leon versions.
+ In this tutorial the process in which I remove Kingroot and replace it with SuperSu is for system stability. I find that most root functions I use seem to not work properly. (Wifi Tether Router and many others). So, I do recommend doing so.
+After the new OS is installed a MetroPCS splash screen will appear even if you do have T-Mobile. DO NOT BE ALARMED this firmware will not limit any functionality you had before, it will even help with tethering functionality.
Tutorial:
Let's Begin.
1. Download the link posted to obtain required files for this tutorial
Link: https://mega.nz/#F!PM4CQRqb!92kgIOnD0ZBY-8HVbtTwGQ
2. Open up LGFlashTool2014.exe
Begin by copying settings posted below, then click "normal flash"
3. Next click the "START" button
4. At this time, I recommend you verify all sync settings are to your liking and that all personal info needed is backed up
a. You have the option to throw all of your personal documents/pictures onto your SD card and removing it appropriately
(Go to: Settings - Storage - [scroll down to] Unmount SD card)
b. Next, navigate to Settings -Backup & reset [leave options default; both checked off] - Factory data reset - reset phone
c. Once reset it will most likely reboot, wipe, and then back to a OS. Now, you will Power Off entirely (make sure it is not plugged in so it will not go to charging mode)
d. Here is where we will hold down the Volume Up button with the phone unplugged from your PC. Then you must plug the USB into your phone.
e. A black screen with white text should post onto your screen, here we will continue to step 6
note: If this screen does not appear please power off and retry step d.
6. Next, follow the posted settings. Make sure to click the "Clear phone Software update Registry" button Then click "OK"
7. A new screen will arrive, and should begin the firmware download process. At this time it will take a few minute to load and should reboot to a fresh OS.
8. With the new OS in place, you can either follow the setup tutorial now or skip through for a later setup.
note: you can now insert your SD card
9. In the tools folder of the folder you downloaded copy the "mrw" folder to the Main Storage folder of your phone
10. Now copy the Kingroot apk to your downloads folder located on the main storage.
11. Go to Settings - About Phone - Software Info
At this time click the build number box a few times until it says you are a developer
12. Hit back until you are at the Setting menu, click on Developer options and check off "Stay Awake" and "Enable OEM Unlock" as well as "USB Debugging"
13. You may now run Kingroot, if it does not install root the first time it should flawlessly install the next.
14. After root is obtained, please go to your home screen and click the "Google Search" widget. Press Update Google Services and let it run. After that has been updated search for terminal emulator and install.
note: If the Play Store is acting fishy and force closing while typing in the search bar do not fret it will be fixed after reboot in further instruction
as an allternative use the jackpal.androidterm-1.0.70-71-minAPI4.apk provided in the "tools" folder
15. Open terminal and in a new window type: Su
16. Allow root usage and at this time type: sh /storage/emulated/0/mrw/root.sh
17. It will run with a few failed messages do not worry it should open SuperSu momentarily
18. Once SuperSu opens up allow it to update binaries using the "NORMAL" option but DO NOT REBOOT YET
19. At this time either download TWRP Manager from the play store or alternatively use the com.jmz.soft.twrpmanager-7.5.1.3-82-minAPI11.apk provided in the tools folder
20. Install and open TWRP Manager. Once opened click on device name and scroll until you see "LG Leon LTE (c50)"
a. Click on Recovery Version to Install and select "twrp-2.8.7.0-c50.img"
b. next click "Install Recovery" and if prompted for verification of install path and for install version select "YES" & "NORMAL"
21. After the TWRP setup is complete it may prompt you to reboot, if not click the arrow in the top left of the TWRP Manager screen and scroll down to "Reboot" and select "Reboot device"
22. After Reboot click TWRP Manager and verify a SuperSu prompt comes up if it hasn't already before the boot
At this point the device should be running smoothly. From here I prefer to do the following steps.
My Personal Setup after new install:
+Personally I like to install use a Root Uninstaller (I use 3C Toolbox Pro) and Uninstall and Backup all MetroPCS BloatWare including the Metro Browser.
+I also access the Hidden Menu by using the Dialer and Dial "2776348*#*"
- I scroll down to ApnUnlock and click to "Unlock APN"
- Then I navigate to Settings -Tethering & networks - Mobile Networks (I check off roaming data) - Access point names
--I then select the top APN and edit APN Type to: default,supl,mms,dun
---I click save from the top right selection, then turn on and off airplane mode
+If you are and Xposed user download "xposed-v79-sdk22-arm.zip","xposed-uninstaller-20150831-arm.zip", and "XposedInstaller_3.0_alpha4.apk" from: http://forum.xda-developers.com/showthread.php?t=3034811
-install the Xposed Installer, then Go to TWRP Manager, use reboot to recovery and from there click install and navigate to the "xposed-v79-sdk22-arm.zip" and install and reboot, it will reboot with a installing screen before your home screen, takes 5 minutes.
+I also use this AMAZING app "Wifi Tether Router", it is the only tethering app I use that works consistently (if you have an unlimited data plan). I get 30mbps up and down, playing many multiplayer games off my PC and PS4 averaging ping as low as 30 ! Setting I use for our device are in a post I created here: http://forum.xda-developers.com/leon/help/unlimited-metropcs-t-mobile-tether-t3290180
---------------------------------------------------------------------------------------------------------------------------------------------------------------
Special Thanks to:
MrW0lf from www.W0lfdroid.com for the Kingroot to SuperSU scrip
Numerous users on the XDA forums I pieced all of this information with
Fabio Grasso for making the amazing Wifi Tether Router
Team Win for being creating an awesome utility that has saved me from numerous bricks creating a stable method
Xposed and the creators of awesome additions such as Lolistat, Lucky Patcher, Max Lock, and SNAPPREFS
Any feedback? Did I do Okay? Questions? Let me know!
Worked for me on T-mobile H345
Worked for me on T-mobile H345 any way to install a H340 firmware on it? I GeT a Binary not authorised when trying to flash.
kodacy said:
Worked for me on T-mobile H345 any way to install a H340 firmware on it? I GeT a Binary not authorised when trying to flash.
Click to expand...
Click to collapse
Apologies for the late response, I never received a notification of your posting. I would not recommend that as I believe the H340 has a different "radio" driver or cellular chip, If I'm not mistaken the H340 isn't even LTE, the H345 is. In that case it may be possible. One thing I suggest doing before wasting your time in using any other ROM is googling H345 vs Ms345, typically the phonemore.com results will provide you with an abundance of hardware specs and let you know if they're different! Just be weary of the newest MS34510f_00.KDZ firmware I believe it has an active unroot process I've had some stability issues. I am using MS34510D_00.KDZ for months and have had no issues whatsoever! Again, I'm sorry I got back to you so late, let me know how everything goes!
brad2192 said:
Apologies for the late response, I never received a notification of your posting. I would not recommend that as I believe the H340 has a different "radio" driver or cellular chip, If I'm not mistaken the H340 isn't even LTE, the H345 is. In that case it may be possible. One thing I suggest doing before wasting your time in using any other ROM is googling H345 vs Ms345, typically the phonemore.com results will provide you with an abundance of hardware specs and let you know if they're different! Just be weary of the newest MS34510f_00.KDZ firmware I believe it has an active unroot process I've had some stability issues. I am using MS34510D_00.KDZ for months and have had no issues whatsoever! Again, I'm sorry I got back to you so late, let me know how everything goes!
Click to expand...
Click to collapse
No problem thank you for your help!
will i still have metro service?
Port(usb or serial) not found! tried on, off, update mode, changing ports and unplugging every other port. any thoughts?
kap10nuka said:
Port(usb or serial) not found! tried on, off, update mode, changing ports and unplugging every other port. any thoughts?
Click to expand...
Click to collapse
Same here (firmware update) usb not detected when using the S/W update tool
After going all the way through this guide with a T-Mobile Leon, I do indeed have a Metro PCS ROM and root, which is great! Unfortunately, it also refuses to acknowledge my T-Mobile SIM. In fairness, I did not even insert a SIM for the first time (just got the phone) until the end of the process, but it shows as carrier locked which is significantly less than useful. I'll flash back to a TMO rom and put the SIM in to double check, but it's quite a bummer. Great job on the guide otherwise, though! It definitely did what it says on the tin; I have root and apart from the SIM lock which may be my fault somehow it works great.
Hey bud those links are no longer valid know where i can get them?
I have an issue with my M20P. I got the phone 12 days ago and everything was fine with notifications up until yesterday. As of right now, I am NOT receiving notifications for whatsapp, gmail,* FB, messanger on time. They're constantly late and usually show up only when I actually go into one of the apps, then the content shows up and syncs, I guess.
I decided to manually launch important apps such as gmail, messanger, whatsapp and I checked all 3 boxes (primary, secondary and background launch). And this morning, after some 9 hours of not touching the phone, I woke up and there were some notifications (quite a few actually) and I was happy thinking the issue's gone but I was curious why there were no messanger and gmail notifications (two of my most active apps) and* I was right... as soon as I entered gmail, the mail that I did NOT receive notification for came on top of queue and messanger literally blew with how many notifications came at once. Other apps, less important, followed with some notification.
I'm worried because I actually decided to manually launch apps I use the most and still, the issue persists, even though most of users had this sorted with manual launching...
So yes, manual launching did not fix it for me
Is there anything else I should do and what?
And also, I have found out that this has only happened thus far on WiFi, my home WiFi. Mobile data doesn't seem to be affected. Will have to confirm though. I don't know if that's an important information...
Please help. I don't wanna sell the phone because other than this bs I like it very much
Go into settings/battery/more battery settings and make sure stay connected when device sleeps is toggled on.
jhs39 said:
Go into settings/battery/more battery settings and make sure stay connected when device sleeps is toggled on.
Click to expand...
Click to collapse
I already had that enabled.... anything else?
I'm still looking for any help.. please
Have you tried disabling PowerGenie.apk via adb?
https://forum.xda-developers.com/mate-20-pro/themes/remove-powergenie-to-allow-background-t3890409
Thanks to @klaus27
jhs39 said:
Go into settings/battery/more battery settings and make sure stay connected when device sleeps is toggled on.
Click to expand...
Click to collapse
kai84m said:
Have you tried disabling PowerGenie.apk via adb?
https://forum.xda-developers.com/mate-20-pro/themes/remove-powergenie-to-allow-background-t3890409
Thanks to @klaus27
Click to expand...
Click to collapse
I think this is my last resort. I really don't want to use my laptop to debug something unless completely necessary..
furiouszagreb said:
I think this is my last resort. I really don't want to use my laptop to debug something unless completely necessary..
Click to expand...
Click to collapse
That's the only fix available. You could unpack and decompile PowerGenie and see what's inside. A bunch of routines that try to identify apps that require being online, plus a bunch of hardcoded apps that are allowed to run in the background. That's Facebook and a bunch of Chinese apps. But everything else is being sent to sleep aggressively.
I tried every other setting available and still, the PowerGenie rendered any background app unusable.
You don't need to debug anything. Just turn on debugging, so you can disable PowerGenie. If you want to use your phone the way it is supposed to work, you have to get rid of PowerGenie. Using the ADB method is the only possible way I am afraid.
klaus27 said:
That's the only fix available. You could unpack and decompile PowerGenie and see what's inside. A bunch of routines that try to identify apps that require being online, plus a bunch of hardcoded apps that are allowed to run in the background. That's Facebook and a bunch of Chinese apps. But everything else is being sent to sleep aggressively.
I tried every other setting available and still, the PowerGenie rendered any background app unusable.
You don't need to debug anything. Just turn on debugging, so you can disable PowerGenie. If you want to use your phone the way it is supposed to work, you have to get rid of PowerGenie. Using the ADB method is the only possible way I am afraid.
Click to expand...
Click to collapse
I appreciate the thorough report. Before I do that, I'll run some over night tests to see if this perhaps is just due to my WiFi. For example, I'll leave the phone over night with WiFi disabled and mobile data on. If I receive all the notifications at the time they should have been received - I'll know the issue is with my WiFi and I'll update it to static and use the pre-set DNSs I found online.
I'm guessing you had the same issue... did it only work for you when you disabled powergenie? Have you tried perhaps what I will - to see if it was a WiFi issue? Or did it happen to you on mobile data too?
And what I find EXTREMELY weird - I had P20 Pro like until 15 days ago, updated to EMUI 9 and it received all the notifications on time. Is this solely M20P issue?
My issue was the Blackberry mobile device management suite, my company uses. Those apps use Android for work, so a separate encrypted partition (and a different user id), open a VPN tunnel and fetch emails in the background.
I have tried every possible solution, like turning off startup control, enabling those apps to run in the background, even checked special permissions, tried different hacks, reset my device multiple times, ... . Nothing helped. The VPN tunnel was capped after a few minutes and even if I opened it manually (by starting the app), the email app was sent to sleep hence not receiving anything.
I started digging around and found a way to disable system-apps even when you cannot disable them from the Android menus. I pulled a copy and decompiled it. This PowerGenie app has routines to identify apps that have widgets, pull a lot of power, have notifications, ... . And it has a list of package names (Android apps) that are never sent to sleep. Stuff like Facebook and Chinese apps. As I started digging around I found this to be a commonly reported issue with Huawei smartphones of all flavours. I think they built that in to mask the fact that Kirin has a higher standby drain than Qualcomm and Samsung. I am just assuming that..
For me this definitely wasn't an issue with my WLAN, DNS or the likes. Now without the PowerGenie, when I turn off the flight mode in the morning, the VPN app is connecting automatically and my Blackberry Hub is pulling all emails. WhatsApp, Gmail, even third party calendar apps now show their notifications in time. So I am happy.
Did it have any influence on my battery life? no, not at all.
I did the same for a couple of colleagues having the same phone and issues and they all are very happy now.
My company even stopped supporting Huawei phones because of these issues.
I can't comment on the P20 unfortunately as this was my first Huawei. But maybe the fact that you were upgrading from Oreo to Pie was the difference here.
furiouszagreb said:
I appreciate the thorough report. Before I do that, I'll run some over night tests to see if this perhaps is just due to my WiFi. For example, I'll leave the phone over night with WiFi disabled and mobile data on. If I receive all the notifications at the time they should have been received - I'll know the issue is with my WiFi and I'll update it to static and use the pre-set DNSs I found online.
I'm guessing you had the same issue... did it only work for you when you disabled powergenie? Have you tried perhaps what I will - to see if it was a WiFi issue? Or did it happen to you on mobile data too?
And what I find EXTREMELY weird - I had P20 Pro like until 15 days ago, updated to EMUI 9 and it received all the notifications on time. Is this solely M20P issue?
Click to expand...
Click to collapse
Thanks for explaining everything. I'll try some methods first and if they don't work I'll go with what you did.
Thank you.
@klaus27
It appears you were right. Tried everything, still some come through, some don't. This suck soooo much
furiouszagreb said:
@klaus27
It appears you were right. Tried everything, still some come through, some don't. This suck soooo much
Click to expand...
Click to collapse
Trust me, run through this short procedure and you won't regret it:
1) install Huawei ADB drivers: https://devfiles.co/download/zygGeX8N/Huawei-MediaPad-10-FHD-USB-Drivers-TeamAndroid.zip
2) install and enable ADB: https://www.xda-developers.com/install-adb-windows-macos-linux/
3) Open a CMD window, change directory to where ADB is installed. Run this:
Code:
adb shell pm uninstall --user 0 com.huawei.powergenie
4) Reboot
klaus27 said:
Trust me, run through this short procedure and you won't regret it:
1) install Huawei ADB drivers: https://devfiles.co/download/zygGeX8N/Huawei-MediaPad-10-FHD-USB-Drivers-TeamAndroid.zip
2) install and enable ADB: https://www.xda-developers.com/install-adb-windows-macos-linux/
3) Open a CMD window, change directory to where ADB is installed. Run this:
Code:
adb shell pm uninstall --user 0 com.huawei.powergenie
4) Reboot
Click to expand...
Click to collapse
I'm a total anti talent for this stuff. Do I install and do this from my phone or laptop?
furiouszagreb said:
I'm a total anti talent for this stuff. Do I install and do this from my phone or laptop?
Click to expand...
Click to collapse
1) from your laptop
2) Follow the link, perform the steps in the tutorial below "How to Setup the Android Debug Bridge (ADB)".
Then scroll down to the part titled "Microsoft Windows ADB Setup". Download the file from the link and unpack to c:\adb (you will have to create the folder).
Then you connect your phone to your laptop and will see a prompt for authenticating your laptop. This is all well documented, just follow the link
3) On your laptop, start menu, run, cmd. Now you will see a console window. Just enter the commands below
Code:
c:\adb\platform-tools
adb shell pm uninstall --user 0 com.huawei.powergenie
The reboot should obiously be done on your phone.
Sounds complicated, but is really easy.
@klaus27
Thank you for bearing with me and explaining. Just one more thing. On the second code, what do you mean by "maybe"?
furiouszagreb said:
@klaus27
Thank you for bearing with me and explaining. Just one more thing. On the second code, what do you mean by "maybe"?
Click to expand...
Click to collapse
I have checked the tutorial and adjusted my reply accordingly .
klaus27 said:
I have checked the tutorial and adjusted my reply accordingly .
Click to expand...
Click to collapse
Thank you so much for explaining everything even to a dummy like myself lol. Much appreciated.
klaus27 said:
1) from your laptop
2) Follow the link, perform the steps in the tutorial below "How to Setup the Android Debug Bridge (ADB)".
Then scroll down to the part titled "Microsoft Windows ADB Setup". Download the file from the link and unpack to c:\adb (you will have to create the folder).
Then you connect your phone to your laptop and will see a prompt for authenticating your laptop. This is all well documented, just follow the link
3) On your laptop, start menu, run, cmd. Now you will see a console window. Just enter the commands below
Code:
c:\adb\platform-tools
adb shell pm uninstall --user 0 com.huawei.powergenie
The reboot should obiously be done on your phone.
Sounds complicated, but is really easy.
Click to expand...
Click to collapse
Hey, I finally gave in and tried to do this but I am having so much trouble doing this mate. Could you please explain like you're talking to a child? My computer skills are abysmal. I downloaded these 2 links you said on my laptop. But I am stuck at step 2. Here are the screenshot to see where I got held up lol
gyazo.com/6541fa024b72309323ab6ed889e19420
gyazo.com/727b043a651185da8761ca8c72d8917a
gyazo.com/d510eef1ce22dde74362a670051b1d7d
When I right click on "platform tools" it gives me several options such as "extract to a specified folder" and I clicked on that (I dont know if thats right) and what do I do now? I am confused with the steps provided in the link. "Extract the contents of this ZIP file into an easily accessible folder (such ad C:\adb)" I dont know where and how to do that
Then it says "Open Windows explorer and browse to where you extracted the contents of this ZIP File" what does this mean?
And 3rd step dont even get me started.
Could you by any chance upload a video of going through all that and doing everything needed up until running the command to.disable power genie? Im lost man
@klaus27
As much as I would like to help you, I think it would make more sense if you ask someone physically around you for help. I don't think I can make it more simple than that and explaining that in such a detail without knowing what system you have is quite complicated.... But I am sure that if you show the instructions to someone with a little bit more experience, it would be a lot simpler...
Sorry I cannot help you further...
furiouszagreb said:
Hey, I finally gave in and tried to do this but I am having so much trouble doing this mate. Could you please explain like you're talking to a child? My computer skills are abysmal. I downloaded these 2 links you said on my laptop. But I am stuck at step 2. Here are the screenshot to see where I got held up lol
gyazo.com/6541fa024b72309323ab6ed889e19420
gyazo.com/727b043a651185da8761ca8c72d8917a
gyazo.com/d510eef1ce22dde74362a670051b1d7d
When I right click on "platform tools" it gives me several options such as "extract to a specified folder" and I clicked on that (I dont know if thats right) and what do I do now? I am confused with the steps provided in the link. "Extract the contents of this ZIP file into an easily accessible folder (such ad C:\adb)" I dont know where and how to do that
Then it says "Open Windows explorer and browse to where you extracted the contents of this ZIP File" what does this mean?
And 3rd step dont even get me started.
Could you by any chance upload a video of going through all that and doing everything needed up until running the command to.disable power genie? Im lost man
@klaus27
Click to expand...
Click to collapse
klaus27 said:
1) from your laptop
2) Follow the link, perform the steps in the tutorial below "How to Setup the Android Debug Bridge (ADB)".
Then scroll down to the part titled "Microsoft Windows ADB Setup". Download the file from the link and unpack to c:\adb (you will have to create the folder).
Then you connect your phone to your laptop and will see a prompt for authenticating your laptop. This is all well documented, just follow the link
3) On your laptop, start menu, run, cmd. Now you will see a console window. Just enter the commands below
Code:
c:\adb\platform-tools
adb shell pm uninstall --user 0 com.huawei.powergenie
The reboot should obiously be done on your phone.
Sounds complicated, but is really easy.
Click to expand...
Click to collapse
I tried following your steps, but when I put in the command, it says " 'c:\adb\platform-tools' is not recognized as internal or external command, operable program or batch file "