Hats off to several Xda-Developers - Verizon LG G3

Well that was an adventure. I inadvertently ended up with an upgrade to VS9854CA over-the-air which predictably killed my root and wiped my setup. Life sucked, but livable until the screen started doing the flashy fade to back lockup. Now I've got to do something - I really don't want a new phone, I like my LG G3 even if the carrier is basically Evil Corp.
First things first: I had to fix the screen. I noted that the newer ROM was making the phone hotter. That's a side effect of what is truly an improvement in responsiveness from my old old version. I also noted that it seemed to get better if I manipulated the covers. Loose part somewhere? Quick search on the forums turned up this thread: "[GUIDE] Fix Display Flickering, Overheat and Constant Rebooting" with thanks to @IngJulian_RVLX. Reading it showed a basic problem to be sure but wasn't an entire fix. It did give me the idea what was needed though. So I disassembled the phone and re-flowed the main chips with a heat gun (NOT a hair dryer - not hot enough, focused enough, and way too much airflow, and DEFINITELY NOT a toaster oven - this will fry other components), then cleaned the board. Using silicon pad I placed one on the top of the main chip on the "front" (faces the display when assembled and has the big shield on it), then another piece over that one the length of the metal shield. Then I put another piece of silicon pad on the chip on the back side under the smaller metal shield. Reassemble the phone. Power up. Okay, we're working again without the annoying flashy fading screen.
So now the problem is getting root and TWRP back. Again the search: "Root for LG G3 VS985 Android 6.0 47A". Thanks to @annoyingduck and @roirraW "edor" ehT. I found a 10B .tot file and flashed that successfully. Only one big problem - adb would not find the phone! Turns out the identifier pulled in a G3 device and not the VS985 device for which I had a debug stack. Not to worry, stump is an apk so I should be able to upload right? Nope, it's offline. Well the suggested alternative, kingroot.net, exists try that. Yup that worked - I'm now rooted and victimized by all the bloatware kingroot brings with it.
Rather than debloat the kingroot I figured it does no harm in the moment. So let's get TWRP back so I at least have a recovery. Of course the CodeFire team has what I need and TWRP is installable as an app now. The first time I rooted it was a manual load with dd - progress! Just search the Play Store for TWRP, load and go. Nice work guys!!!
Okay so how to get up to the latest version possible and still keep root? Because, hey as long as I'm in here why not? Searching I find this: "[Guide] [VS985] Flash Back To Stock - KDZ Method". Yup, once more @annoyingduck to the rescue - a repository of .KDZ files along with more helpful experience. I managed to find this thread as well: "[TOOL] KDZ and TOT Extractor" with thanks to @bullghost. Still not quite what I need yet. I found "VS985 47A - Stock Flashable Firmware" with thanks to @xdabbeb. That's the ticket! So flashed that (and the bootstack) and now I'm at least a marshmallow 6.0 version. Lost root, but kingroot was able to root (and bloat).
Now to get rid of kingroot and put on superSU instead. Search found this: "How to Remove/Replace Kingroot (KingUser) with SuperSu". There, that's better! After a reboot I have to manually remove the last vestiges of kingroot but SuperSU is happily running and the bloatware is gone. Now I can restore the phone to it's prior level of function. Play Store restored my apps, I did have to reconfigure my home screens, but I'm now back in business. What's more I've got an upgrade that I like.
Whoops! An OTA update flashes on my screen!!! NO!!!!! Okay, calm down. This took several searches to find so basically here's what I needed to do:
1. Delete the files in the /cache/fota directory - this allowed the OTA to fail without updating my phone.
2. Find the "System updates" in the application manager - there are two of them and you have to select 'system' in the drop down to see them. One of them can be disabled the other cannot.
3. Find /system/app/FOTA and rename the LGFOTA.apk file to LGFOTA.apk.bak
No, using hiddenmenu.apk or the ##PROGRAM985 or any other method does not work. Apparently Evil Corp. doesn't pay attention to this anymore and that's why I got the original update that killed me. Thanks to this post for the tips: "[PSA] NO OTAs!! | Keep Root/Unlock | How-To: Block OTA, DL SW/FW, Update Manually" and h/t to @autoprime.
So now I've got some work to do, because there's some fun to be had. I've managed to get the VS985CA .KDZ and extracted it. I've got the .img files ready. Now I just have to add su and busybox to the system image under linux and then I can flash these files to the phone using FlashFire (again CodeFire team - what can I say, you guys rock). Time to make the chimichungas!
Moral of the story here is this:
I've been playing around with android phones and root since my HTC Incredible. Xda-Developers has always been a source of good information but it only works if you use it. I found the original hiddenmenu.apk and it was the forums that gave me the invocation command to bring it up - somewhere in the original VS985 root thread I'm there contributing that information. Do the searches and you can find the answers you need without being annoying. Also give it time - these people I've mentioned throughout this post (along with many more) are working as fast AND as carefully as they can to bring the best solutions possible to problems. But you do have to do your part, if you aren't going to put the time in to learn at least the basics by reading the forums than this isn't your rodeo. I'm no expert but I do know how to think, experiment, and I have some background in linux and have some familiarity with android application development so I could understand something of what this device is doing and how it's built. If you lack that and you're going to play here my best advice is to have a backup phone - 'cause you're going to brick yours a few times before you learn that these basics are required, even if you're not going to be a "cool ROM" developer. That's the dues you pay to play. The experienced folks will realize my mistakes made, as I do, in this post. That's because they are the experts and I am not. Did I get where I wanted to get? Yes. Was it elegant? No. But having paid the dues I never needed to ask. Just admit to myself that I needed to get smarter and dug in. Besides, it was kinda nice not to be bugged by the phone for a day.

Quick update to the above...
The task to kill is com.lge.lgdmsclient. It took ES Task manager to find it. I moved the offending apps off to quarantine on my SD card after setting them to disable in the ES Task manager and no more OTA updates.

Related

[Q] Eris Rooting track ball challenge

I have spent days looking for threads so this neewb is about to break something. Well maybe not. I have my daughters Eris 2.1 and am trying to root it for her. I have tried several times with different methods. The issue is that I can get into recovery mode after every 1 click app but nothing I try will let me toggle to unzip to SD, or toggle to anything for that matter, volume wont do it and all track ball will do is let me select reboot. Man my DX was easy compared to the one click method.
HELP PLEASE,
If the trackball is having trouble scrolling, I'd install the trackball-optional custom recovery so you can use other buttons to scroll. There are instructions for doing this here:
http://androidforums.com/eris-all-things-root/214240-amon_ra-1-6-2-custom-recovery-trackball-not-required.html
It sounds like you fall into "Scenario 2" which says you should follow the same method as "Scenario 1" to get rooted using the trackball-optional recovery.
I'll give it a shot, The help is much appreciated,
I am been trying to help him to get this thing to add the Custom Recovery, but every root format has not worked at all. Most are outdated or there are files missing. Specially on the link provided above. The download for the scripts no longer has Root_1 or Root_2, it has a bunch of other stuff there for gscript. Found an link on Droidforums for gscript for rooting and the scripts don't work.
Any complete instructions anywhere?
popfan said:
I am been trying to help him to get this thing to add the Custom Recovery, but every root format has not worked at all. Most are outdated or there are files missing. Specially on the link provided above. The download for the scripts no longer has Root_1 or Root_2, it has a bunch of other stuff there for gscript. Found an link on Droidforums for gscript for rooting and the scripts don't work.
Any complete instructions anywhere?
Click to expand...
Click to collapse
popfan,
I am not aware that any of the above links or files are missing... Can you point-out / tell me specifically which files you cannot access / download / link-to?
The root_part1 and root_part2 files are part of erisuser1's (bftb0's) Universal Root for Dummies! thread that I do reference in my AF thread, but these should still be up, active, and available.
So, I'm not sure if you are speaking about becoming rooted or installing a my trackball-optional custom recovery.
Let us know.
Cheers!
Im sure my kid has shuned me for leaving her Eris with someone so thanks to everyone for the help. Pop is helping me out and after moving file at the point where it says to open and look to see root 1 and root2 they are not there and there are a ton of other stuff. Also the pick look different than on the thread like the app has been updated. Also when doing the ball recovery there is no tools folder to be found. I'm sure pop wont touch it again till tomorrow so any other help / advice is more than welcome or it may cost me my Dx
malloneem said:
Im sure my kid has shuned me for leaving her Eris with someone so thanks to everyone for the help. Pop is helping me out and after moving file at the point where it says to open and look to see root 1 and root2 they are not there and there are a ton of other stuff. Also the pick look different than on the thread like the app has been updated. Also when doing the ball recovery there is no tools folder to be found. I'm sure pop wont touch it again till tomorrow so any other help / advice is more than welcome or it may cost me my Dx
Click to expand...
Click to collapse
LOL, sorry, didn't make/see the connection between your two posts .
Okay, let's try something new here...
Just a week or so ago, I re-packed jcase's 1-click rooting app to include my trackball-optional recovery image in lieu of the original recovery that his app includes.
So, let's have you re-root using the new 1-click app (all credit to jcase, both for his app and his threads both here http://forum.xda-developers.com/showthread.php?t=742228 and over at AF http://androidforums.com/eris-all-things-root/139178-universal-1-click-eris-app-apk-no-pcs-no-scripts-needed-easy.html).
Since you've already used the 1-click app before, then all you'll have to do is grab my new "trackball-optional" version:
https://sites.google.com/site/scaryalienware/downloads/one-click-tbo.apk
MD5 sum: 15763b51cf707c027cc73bc117e1fc39
(the "tbo" in the name stands for "trackball optional" ).
Just follow the same process you did before while running the 1-click app and you should end-up with my trackball-optional recovery installed.
Let me know how it goes (you'll be the first besides me that I know of that has tried it; the user that I created it for to test has not yet responded, LOL).
Cheers!
I tried this link below. It no longer has the root_1 and root_2 in it.
http://www.megaupload.com/?d=774XYFRA
I did use your "updated" 1-click app with tbo and it worked great.
Thanks!!
Too bad this phone was not as easy as my captivate.
popfan said:
I tried this link below. It no longer has the root_1 and root_2 in it.
http://www.megaupload.com/?d=774XYFRA
I did use your "updated" 1-click app with tbo and it worked great.
Thanks!!
Too bad this phone was not as easy as my captivate.
Click to expand...
Click to collapse
Glad that jcase's repackaged app worked for you. I'll update my documentation to make this available to others.
Also, re. the above Megaupload link...it works just fine for me (from my PC and from my Droid X) and includes all of the aforementioned root_part1/2 files.
I think you've fallen prey to a truncated download, which is not uncommon with Megaupload in my experience. This is also why is important to double-check the file sizes and MD5 checksums of files that you download so that you know you got the whole-shebang; notice that erisuser1 did include the MD5 in his thread for this file:
- Download gscript.zip (MD5 92796a8c6e61e8f1ee36e315c0acae7d)
I've often found it helpful to use a different browser other than the stock browser (like Opera Mini) when doing downloads via my Eris since the stock browser does seem to have more issues (timeouts perhaps) than it should.
Cheers!
Thanks to all this tuff till you hooked us up but now on to nightmare 2
I downloaded CyanogenMod7.1.0 RC1 [2.3.5 GingerBread NIGHTLY]
from this thread http://forum.xda-developers.com/showthread.php?t=944430&highlight=ROM
Got it up but it has no market so I can not get to titanium, boot loader or anything... It says to flash google apps after the rom but now Im back to the trackball / volume key issue because it's all in titanium. ??? I did a factory reset and it came back up as the new ROM, ???
EDIT UPDATE!!!!
Sorry for the hassle all, the "green" start call button works as the down after the download.. All is well.. I think..
Again thanks to you all, If I hear of any good deals on an Eris I will know why.
You need to download GAPPS to your sdcard. That is why you don't have market.
http://forum.xda-developers.com/showthread.php?t=944430&highlight=ROM
Its just below link for the rom and save it to your sdcard. Go ahead boot into recovery and wipe data, daliv-cache, cache; Flash Rom again, then flash gapps and reboot.

[Q] Rooting procedure technical details - checklist

Hello everybody.
This is my first post, and while I am noob at XDA-Developers, I have spent more than 10 years writing and reading in forums, and I know what has to be done before writing on them. And I did. I have a couple of questions that I think they are not easy to answer. Indeed, I spent 8 hours yesterday searching through the interwebs and this forum to try to figure out the most thorough answer. And I think I figured out mine, but I don't know any people that can reinforce my toughts and tell me "Hey Gabriel: you are right, you did well, you are the man: go out for a beer, keep calm and carry on". I will ask the questions first, and later I will explain why I ask such questions, and finally what are the steps I did.
The questions are: How can I remove root from a custom rom, and how can I be sure that I properly did? I know that many of us think that "This is stupid / Why do you want to do such a thing / the power of your phone will... / go to stock / etc". But, any way, I have a deep concern on expanding concepts and knowledge, and I thing that root process, root means and rooted phone securing checklist are not as clear as I would like to find them. And more important: I *have* to remain in a custom rom but I *must not* be root.
So the why's are not the question but, just to add some reasonable context: I have a phone that does not fit my needs with the stock rom, because a hardware component is falling apart and I need a software workaround (YEAH, right LOL: a Nexus One with the power button falling apart and I need to be able to unlock / wake with the trackball; but this thread is Android-wide because it tries to find a deep insight into rooting itself). This software workaround does not work in stock rom when I configure the password / PIN / pattern. And the problem with custom roms is that they run into trouble with certain data-protection aware environments, which do not allow rooted terminals. And more important than all: I have no need at all to be root, at least by now.
So, I spent hours searching, and I figured out that I should remove "su" command and related APK's (ROM Manager, Superuser, ... and some others that I won't need). All by myself and with some posts (I don't remember if they were here or in "HTCMania", a good spanish smartphones board, either) that suggested it.
The exact process I did was to download CyanogenMod 7.2 RC1, check signature & md5 to make sure the zip was what it claimed to be (because later I found that I needed to shut down recovery signature check) open the .zip, remove "/system/xbin/su", install the rom, remove su-related ".apk" with adb, and try to check if it still had any sort of superuser permission scalation. It aparently does not have. I checked /data directory with Root Explorer, I downloaded and ran Root Checker Basic.
The results seem what I expected (and that's the question: they seem, and I don't know if they are): I am running on CyanogenMod, the workaround (wake on trackball) works, the PIN/password works fine with it, and it seems I am not able to gain root access.
But my question are deeper than that: is there any remaining technical mean that could be used to gain root access on my phone? Do I have to get rid of more su-companion tools to be sure and to be "non-root"-compliant? Is there any checklist we should follow to check both if our custom ROM is rooted-but-secure and if our ROM is properly un-rooted? And most important: did I miss / failed to find the correct resource in these forums?
Thanks to every body and congrats for this outrageous boards.

[Q] Azpen A701 Tablet

Does anyone have any information on rooting the AZPEN A701 Tablet (ICS OS)?
All my searches keep popping up for the Acer Iconia A701.
drivers
I found the correct address for the drivers for this tablet, and 2 others from Azpen.
www.mediafire.com/azpensupport
The links on their webpage incorrectly spell mediafire and also include .com in the last part of the link.
Note: I recently got an email from Azpen telling me the exact same url that I had already figured out. Their email is about week to a week and a half after I sent them a request for the proper address. Also, as of the time I am posting this update, they have not corrected the address on their website.
Tried methods
I have tried SuperOneClick which reports that the system is rooted, but ADB Wireless says it is not.
I have tried Bin4ry's Root Many Android! (options 1, 3, and G) and briefly got temp root on option 3 but I lose wireless functionality (I get one or the other message from ADB Wireless (no root or no wireless), verified that Wireless connection has been turned off and won't turn back on until reboot which loses me the root again).
Retries
Ok, finally rooted the Azpen A701.
What I did:
First, I went back to SuperOneClick, and choose Unroot to reverse anything it did.
Retried Bin4ry's Root Many Android! v31, option 1 (new standard method), test, failed, unroot, 3 (old method), test, failed, unroot, then G (Google Glass method), test, WORKED this time.
Verified by using a root browser (can see files/folders(subdirectories) in /data after giving permission), a root checker (note: do not turn on SuperUser's Autoanswer, gives false information from some checkers), and ADB Wireless works while in range of a wireless router/source.
I am guessing that somehow the leftovers from SuperOneClick were affecting my results with Bin4ry's collected scripts.
Props to all that developed each of those programs and scripts.
I don't know if anyone will be seeing this but I hope it helps anyone needing the info.
Just curious to know if there is a rom available in case this method bricks the tablet? I bought this tablet a couple of weeks ago because I wanted to mess with one and I didn't have a lot of cash to spend. I use it daily and my kids play games on it. I can't afford to get another anytime soon, however I'd like to have it rooted so that I can remove factory installed apps that I don't want or need.
no idea
BizarreMan said:
Just curious to know if there is a rom available in case this method bricks the tablet? I bought this tablet a couple of weeks ago because I wanted to mess with one and I didn't have a lot of cash to spend. I use it daily and my kids play games on it. I can't afford to get another anytime soon, however I'd like to have it rooted so that I can remove factory installed apps that I don't want or need.
Click to expand...
Click to collapse
I have absolutely no idea. The only additional rom I have seen ANYWHERE is the Jellybean update for it (see driver link above). This seems to not be a very popular tablet to work with, going by the fact I received no help from anyone here. All research on this so far has been done by me. I stumbled on to Bin4ry's rooting method by accident. I'm not a ROMer, I don't know how to build one. Also I don't know which ROM backup method to use on it/will work with it.
Alright
I'll give it a shot during the weekend, I've grabbed the jelly bean update (thanks for the link). Hopefully all goes well. I figured there would be little to no support for this device, however due to a tight budget I chose to get this tablet.
I don't really mind the lack of support, however I'd like to have root because like on my old phone I had a few programs I used that required root.
Thanks again.
*Edit*
I attempted last night as I had free time to do the root method and unfortunately it did not work on my device. Not sure why it did not work. I'll try it again at a later time when I can. I also attempted to upgrade to 4.2 but it seems as though I am having issues with it as well.
Maybe I'm just stuck with the tablet as is
trying again...
BizarreMan said:
I'll give it a shot during the weekend, I've grabbed the jelly bean update (thanks for the link). Hopefully all goes well. I figured there would be little to no support for this device, however due to a tight budget I chose to get this tablet.
I don't really mind the lack of support, however I'd like to have root because like on my old phone I had a few programs I used that required root.
Thanks again.
*Edit*
I attempted last night as I had free time to do the root method and unfortunately it did not work on my device. Not sure why it did not work. I'll try it again at a later time when I can. I also attempted to upgrade to 4.2 but it seems as though I am having issues with it as well.
Maybe I'm just stuck with the tablet as is
Click to expand...
Click to collapse
It may have been the sequence I used. Tried SuperOneClick several times (as above it said tablet was rooted but several apps said it wasn't) which installed su, busybox, and superuser. Then found Bin4ry's method, got temp root (tryied 1, 3, and Glass). Then went back to SuperOneClick and unrooted, returned to Bin4ry's and finally got it with Glass method.
Don't know if that helps
Well
After several attempts via Bin4ry and SuperOneClick I have obtained root on this tablet.
Not quite sure which actually did it though as with super one click it froze on me during both times I used it and each time I tried Bin4ry's method I kept getting messages about connecting my device (which was connected fro the get go).
After several tries with these programs yesterday and finally saying screw it I decided to add some apps that required root. I don't know why I did it I just figured it was worth a shot. I added Super User which told me I was rooted, then I added Titanium Backup and was able to use it as it is intended. For added measure I also installed and ran root checker which as well as super user verified that the tablet had been rooted.
Good to see that your were able to root.
BizarreMan said:
After several attempts via Bin4ry and SuperOneClick I have obtained root on this tablet.
Not quite sure which actually did it though as with super one click it froze on me during both times I used it and each time I tried Bin4ry's method I kept getting messages about connecting my device (which was connected fro the get go).
After several tries with these programs yesterday and finally saying screw it I decided to add some apps that required root. I don't know why I did it I just figured it was worth a shot. I added Super User which told me I was rooted, then I added Titanium Backup and was able to use it as it is intended. For added measure I also installed and ran root checker which as well as super user verified that the tablet had been rooted.
Click to expand...
Click to collapse
So I think we can safely say that using both methods together + patience will root this tablet (don't know why one or the other wouldn't do it).
Not having any luck
CyberSpiderPrime said:
Does anyone have any information on rooting the AZPEN A701 Tablet (ICS OS)?
All my searches keep popping up for the Acer Iconia A701.
Click to expand...
Click to collapse
I have been trying to root AZPEN A701 for the past week, I have tried everything written on this forum. Any help PLEASE!
clean slate
Are you willing to do a full restart on the tablet (factory reset)? I had to do that before my root took, as I found on other systems that I have rooted some programs you load can interfer with rooting. Save any personal data before you do this, programs can be reinstalled from Google Play or (hopefully you saved them if you downloaded them) your computer
Factory reset:
Press and hold up volume button then press and hold power button. The screen will remain black (no backlight)
Wait 4 seconds then release both buttons (backlight will come on). Shortly the android on it's back with the open torso (the sick android) will be displayed.
Press the down volume button. You should see 5 options available- You are now in the System Recovery program.
Using the up or down volume button to highlight an option then press power to select the option.
1) select Wipe Cache Partition
let the unit reboot, then turn it completely off
reenter System Recovery again.
2) select Wipe data/factory reset
let the unit reboot, then turn it completely off
The system is as clean as it is going to get now.
On your pc (don't know for MAC's) download the drivers, Android programs needed (Android Debug Bridge -ADB- is part of the Android Development kit and some Java Development Kits), and both SuperOneClick and Bin4ry's root software. Install all software and drivers as per their instructions. Run SuperOneClick and Bin4ry's root programs. Busybox and SuperUser will be added automatically by these root programs.
While having wifi and internet access (McDonalds anyone?), re-sign up for Google Play (sorry, but the settings got wiped earler). Go to Google Play and let all the programs update. Update Busybox and SuperUser if needed/possible.
Download any root enabled file system browser (FSB) (permission will have to be granted in program to use root functions) - I used Ghost Commander for mine. It may take a bit to find it in the directory structure for the FSB you downloaded but you need to get to the root system folder.
Ghost Commander has a Local Storage option press it and an new list of folders/files will be displayed, move to the previous folder level (double dots at the top) and give permission to move to a system folder, move to the previous folder again to get to root directory, "/mnt" is the directory you just came out of and is highlighted but you will be at the root of the file system.
Enter the "/data" directory. If you can see files listed there, you have root; if not rooting attempt failed.
Once rooted, doing a system cleaning and Factory reset will not remove root but will remove SuperUser and Busybox (re-run one of the root programs to re-install then update the next time you are on the internet/web). Updating/upgrading the rom will remove root if the rom does not have root activated - I don't know of any custom roms for this tablet (there is a Jellybean upgrade in the Azpen website, if they haven't updated to the correct web address then use the one I listed on the front page, mediafire is spelled wrong in the address). Nandroid level system backup is not available yet for this tablet to my knowledge.
For several reasons, do not turn on SuperUser's automatically give permission option (the one that affects all programs), except on a one for one basis: 1) some root testing programs will fail if this option is turned on, 2) security: turning this on will allow ALL programs - including some malicious ones - to have super-user rights, 3) you will get to know which programs are asking for root permissions beforehand not after, you may want some to have automatic access (like DroidWall in my case, a firewall) and not others.
Also other information that can be useful:
/sdcard does not refer to the removeable SDCard but to the internal user data area. All programs that can be moved to a SDCard (like by Apps2SD) will be moved to this directory by default (some may allow re-assignment of the destination location) instead of the removeable SDCard (blame Azpen, it was their decision to use the directory and name that way). On most other systems /sdcard is the removeable SDCard.
/extsd is the removeable SDCard, when installed, maximum size is 32Gb.
/usbhost1 is for any usb flashdrive connected by a USB-OTG cable (OTG means On-The-Go, special usb cable that puts the tablet into host mode, similar to connecting a flashdrive to a computer, the cable is not a standard Data Connect/transfer cable, one USB-OTG comes with this tablet). Note about USB-OTG cables: if one is connected you can connect either a flashdrive, usb keyboard, usb mouse, combo keyboard/mouse unit, or a powered usb 2.0 hub. Only one flashdrive can be connected at a time (anyone know of downloadable software that would allow 2 or more? I know some modified kernels can allow more than one) so with a hub you can connect a flashdrive + keyboard + mouse (I use the RII wireless combo keyboard and mouse with mine). Maximum size appears to be 8GB, format must be FAT32; will be testing with a 16GB key shortly.
Azpen A701 and Jelly Bean
Shortly after I wrote the above I had to re-flash my tablet, but Azpen had deleted the ICS image (after a request it was restored to the site, get it while you can) and had to flash Jelly Bean. I found there were troubles with this image.
First: I could not write to either the external SDCard (called extsd) nor an attached USB flash key; reading was unaffected. I found this out when I attempted to reassign my backup location to the external sdcard and it was unable to create the directories.
Second: I couldn't find a rooting program.
After a little research, I found that the external media had not been given R/W permission in the platform.xml file - I could actually navigate the FS and read the file even without root.
Also I finally found after 2 days of searching a root program, VROOT, http://forum.xda-developers.com/showthread.php?t=2434453, that would work. Be prepared to deal with Chinese for a little bit and follow the instructions on that page (press the buttons to see screenshots). The superuser app needed to fix/replace the Chinese app is SuperSU (Google Play) which supposedly fixes problems found with other superuser apps. Once you have downloaded SuperSU, had it download/update its binaries and have rebooted, you will have to disable the Chinese Superuser app as you are unable to uninstall it using the app manager: I located it by its icon (shield with cog) in /system/app and appened '.old' to the name: "Superuser.apk" => "Superuser.apk.old'. I didn't use Titanium Backup as suggested because I am not a fan of the program .
platform.xml is located in /system/ext/permissions. After you have root, open platform.xml in what ever text processor you want locally or transfer it to your computer and work with it. You will have to add '<group gid="media_rw">' to the 'WRITE_EXTERNAL_STORAGE' group, on the line after '<group gid="sdcard_rw">' (don't type the single quotes but the double quotes are needed) and write the file back to its location (need root for that, adb pull/push may be possible to fix this). Remember on this tablet, sdcard refers to the internal user storage, media_rw will give permissions to the extsd (external sdcard) and USBHost1 (using included USB-OTG cable and a flash drive). I rebooted the tablet and tested the RW state of extsd, and voila, it now is write capable.
I wish there was more aid on this tablet but since it is not mainstream (not made by a big manufacturer like LG, Motorola, Samsung, etc.) I doubt that it is coming (I am not a ROMmer but have been using computers since the 80's, so I know a few tricks and am always learning). I will keep adding info as I find or fix it.
I will probably go back to ICS as some of my programs are not working right, and JB is sluggish.
I just picked up the A700 from Microcenter, and this is the ONLY reference to rooting the device I could find. The Azpen website doesn't even acknowledge the device's existence. I just came across this yesterday: Azpen A700 - Cyanogenmod forums. I used the Kingo method without a hitch.
Hopefully, all the other folks who get that tablet for the pre-Black Friday sale who found this link will benefit.
johncro13 said:
I just picked up the A700 from Microcenter, and this is the ONLY reference to rooting the device I could find. The Azpen website doesn't even acknowledge the device's existence. I just came across this yesterday: Azpen A700 - Cyanogenmod forums. I used the Kingo method without a hitch.
Hopefully, all the other folks who get that tablet for the pre-Black Friday sale who found this link will benefit.
Click to expand...
Click to collapse
I picked up this tablet also. Not bad for $40. I used this method to root http://www.cydiaimpactor.com/ It worked the first time. I just had to do it on an old XP machine. Windows 8 would not load the right android drivers. Now I'm working on getting Titanium backup to see my external SD card.
comstar said:
I picked up this tablet also. Not bad for $40. I used this method to root http://www.cydiaimpactor.com/ It worked the first time. I just had to do it on an old XP machine. Windows 8 would not load the right android drivers. Now I'm working on getting Titanium backup to see my external SD card.
Click to expand...
Click to collapse
I was going to return it as no rooting procedure would work....(I only bought it so I could have a android tab to fool with...i'm windows tablet all the way)...and once I tried out that rooter it worked...thanks alot for the info!
cheeb said:
I was going to return it as no rooting procedure would work....(I only bought it so I could have a android tab to fool with...i'm windows tablet all the way)...and once I tried out that rooter it worked...thanks alot for the info!
Click to expand...
Click to collapse
Glad it worked for you! I started this thread for the A700 http://forum.xda-developers.com/showthread.php?t=2532464 - No activity in it yet. But if you come across anything good post it over there.
Sent from my Transformer TF101 using XDA Premium HD app
Update
I am glad to see that others are taking an interest in this tablet.
I found 2 methods that worked and am glad that others are finding more.
Now if I can get the boot loader cracked I could finally make a nandroid copy and save myself 4+ hours restoring everything when it goes wonky. This has happened twice- OS partition fills up (and don't know why) and the device resets to near factory reset level (even some of the factory apps are missing) and won't install anything but the smallest of apps which are deleted on the next reboot; the only solution is to re-flash the tablet. Note that I have gone back to using ICS as JB has other problems (external media including its own sdcard partition is not rw enabled for one).

Enable multi user / guest account feature on Lollipop

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...

Kingroot to SuperSU (Root Issue)

Hey, new user here. Sorry if this is miscategorised.
I have a very simple issue. I have a GT-I9305, recently rooted with some weird Android Terminal commands and a .zip file I found online. No issue with rooting. I did a root check and used root to uninstall Knox.
Issue is that beforehand I tried to root with KingRoot and I didn't know it would automatically download its own SU (probably should have been more cautious). I want to use Super SU instead but I can't because after some research, there'll be so conflict between these two. So further research suggests I need to do some deep replacement between these two.
I've tried several methods already.
An app called SuperSu Me required higher Android version, so that was a strike for me. The one with the commands with the mrw file did not work (just threw up a whole list of failures and errors), and another appears to be working with Kit Kat only (I'm on 4.3). Another limitation I have is that my computer is garbage and probably won't run Odin or whatever flashing thing, so that rules out another horde of solutions.
Further, Super SU did not update binary, which most websites suggested it will do. It tries to do it, then regurgitates an error message after five minutes.
So I was just wondering if there is some obscure way beyond the second Google search page which might help me out here, to replace King SU with SuperSU. After all, the root method I used in the first place wasn't exactly conventional.
Just wanted to ask around here before I simply unroot and forget about the whole business. Been lurking around here unregistered and you guys have been very helpful, so now I guess I'm starting a topic of my own.

Categories

Resources