Related
Does anybody know how I can flash a custom recovery to this device? I have already gotten it rooted with the method for the Optimus. However any attempt to flash a recovery sets it back to default, it retains root, after the reset, but will not allow for a custom recovery. I know this isn't an awesome phone and I have a D1 that I use, but have been given this as a work phone and would love the same freedom with this device.
bump! I've had the phone for a month now, and am looking to try some custom roms now. doesn't appear as though cyanogen or clockworkmod support the lg, or do they?? It looks like the first stumbling block is the recovery image. Anybody know a way to backup the ROM on this phone??
what did you do to get you LG VORTEX rooted? i have tried several different ways to no avail. also my phone updated to android 2.2.1 is there any way to roll it back to 2.2 so that rooting may be easier?
mike9064 said:
what did you do to get you LG VORTEX rooted? i have tried several different ways to no avail. also my phone updated to android 2.2.1 is there any way to roll it back to 2.2 so that rooting may be easier?
Click to expand...
Click to collapse
Rooting hasn't really happened for 2.2.1 on the LG Vortex. You have to roll back to 2.2 to root (use the z4root, search the forums on how to use it). To roll back, check out the downgrading tutorial on breakneckmod dot co dot cc (I can't post links yet, but I feel like this one is necessary and doesn't constitute spam). If that seems a little hard to follow, or if you don't feel as advanced a user, there's an updated, more step-by-step, hold-your-hand kinda thing (which will take longer if you already know what you're doing), check the latest post on technoheads dot org.
You don't need to roll back to 2.2 to root this phone. I rooted it with no problems using Super One Click with rageagainstthecage. You may need to turn the usb debug mode on and off a couple times to get it to take during the process. After you see the message that you have succeeded you need to reboot your phone. Then you're good to go.
I just rooted with the latest update.
Unzip the SuperOneClick archive
Put the phone in debug mode (I had it in modem mode and enabled debugging)
using adb push psneuter to /data/local/tmp
then do
Code:
adb shell
cd /data/local/tmp
chmod 0777 ./psneuter
./psneuter
adb shell
id
if the last command says uid=0(root) then you are temp rooted
close out of the shell and do
Code:
adb remount
adb push su-v3 /system/bin
adb push Superuser.apk /system/app
adb shell sync
And you are rooted
Looking for a rom for the lg vortex
i need a stock ROM that i can use ROM Manager to install that will let me use the wifi hotspot i have it rooted
I used ARoot
Just rooted my Vortex running 2.2.2bFRG83G, using SOC. Apparently LG made it easy with their modem drivers available on their website. The only "trick" that i did (and was not documented in rooting procedures) is to enable modem mode in the USB connection chooser menu (with USB debugging of course).
I rooted my LG Vortex using Gingerbreak, but I had issues flashing the recovery. However, I did it using ADB and it worked wonders for me. I even have a custom ROM on the device now. I tried CM7 on it, but I kept getting random force closes, especially when going into the settings to try to change some things. I did find another one (Lightning) and it seems to be pretty stable right now.
seejay1120 said:
Just rooted my Vortex running 2.2.2bFRG83G, using SOC. Apparently LG made it easy with their modem drivers available on their website. The only "trick" that i did (and was not documented in rooting procedures) is to enable modem mode in the USB connection chooser menu (with USB debugging of course).
Click to expand...
Click to collapse
Thank you Thank you Thank you! I have been pulling my hair out trying to get this to work, and that was all that was needed!
i rooted my vortex
i rooted my vortex but thats about as far as i got.
is there any way to do this that works?
LG Vortex root
I root my phone using SuperOneClick and then using something else (I forgot) to automatically install SU. I did have problems to start with using ADB but by reading and RE-reading the forums, I learned how to use it correctly. I then started deleting unwanted apps using this thread (http://forum.xda-developers.com/showthread.php?t=617026). Now some of you may have noticed that I didn't say anything about doing a backup.... that's because in my hurry to kill those few apps, I didn't do a backup. Well, now I want to start over from scratch because my home screen freezes and force-closes way too often. Where can I get a backup from?
tia...
Winston
check out the GNM recovery on android forums
My apologies for taking so long, life is hectic. This is a "root path" for the 4.4 update, and in this case you will retain your stock recovery so features like remote wipe will continue to work. It requires you downgrading to 4.2.2 or already be on 4.2.2 before updating to 4.4. Unlike hte MotoX, you can not downgrade. This Must be preformed while on 4.2.2 before updating to 4.4
First you must use MotoWPNoMo, if you haven't then you will need to. Use RockMyMoto to gain root, then use MotoWPNoMo, and then restore to the 4.2.2 Camera update.
Step1)
Unzip SlapMyMoto-1,0.zip and push the jar file to your internal storage
Code:
adb push SlapMyMoto.jar /sdcard/SlapMyMoto.jar
Step2)
Use http://www.cydiaimpactor.com/ to open up a telnet session as system user on port 2222. We covered how to use Impactor and telnet in the RockMyMoto root, I won't be covering it again since this post is going to be long enough already, see here -> http://forum.xda-developers.com/showthread.php?t=2509590 or http://rootzwiki.com/topic/107098-root-rockmymoto-yes-even-the-first-ota/
Connecting over telnet, and run Stage1 with this command:
Code:
dalvikvm -cp /sdcard/SlapMyMoto.jar SlapMyMoto
When the device tells you to reboot, do this manually with "adb reboot" or your power button. It will not auto reboot on this step
Step3)
Once the device has rebooted, run Impactor again and connect over telnet just like in the previous step, then run the same command
Code:
dalvikvm -cp /sdcard/SlapMyMoto.jar SlapMyMoto
Once the device has rebooted, please take the 4.4 OTA.
Step4)
Now that we are on 4.4, we can finish the process with adb shell:
Code:
adb shell
cp /sdcard/install.sh /data/local/tmp/install.sh
chmod 755 /data/local/tmp/install.sh
echo "/data/local/tmp/install.sh" > /sys/kernel/uevent_helper
Then either wait, or toggle your bluetooth. Once the device reboots, you will have root.
So, if I have a root that I've gained with RockMyMoto I just need to take an OTA and start from the step 4 ?)
Sent from my XT1080 using Tapatalk
I was going to say what if we used voodoo un root then take the update when it comes hopefully restore with it? I know voodoo doesn't support 4.3+ but what if we achieved root on 4.2.2?
Sent from my XT1080 using Tapatalk
No....make sure you have write protection off with the MotoWPNoMo procedure jcase linked, then start at step 1. It's my understanding that if you start from step 4 nothing will work because 4.4 can't currently be rooted, so you go through all these other steps to maintain a root via 4.2.2. Besides that, with the 4.2.2 root, there's no recovery so if you tried to take it right away you'd just boot loop your phone. Someone correct me if I'm wrong.
Has this been verified? I saw people in another thread getting a "security version downgraded" error but could not figure out exactly what they did
Sent from my XT1080 using XDA Premium 4 mobile app
Another question I got root through rockmynoto. When I got my maxx I took the update to 12.15.15 do I still have to do all the steps?
Sent from my XT1080 using Tapatalk
Well, upon flashing back to 4.2.2, my phone says I don't need the update. It can't be polled, so I have no idea when it'll prompt me to do it again.
With my luck I'll have to wait until after the push window closes and it becomes a freeforall.
jcase said:
God-like abilities
Click to expand...
Click to collapse
Does anyone have the update.zip?
EDIT:
MAXX Camera Update: http://sbf.droid-developers.org/download.php?device=4&file=1
Mini Camera Update: http://sbf.droid-developers.org/download.php?device=2&file=6
Ultra Camera Update: http://sbf.droid-developers.org/download.php?device=1&file=8
i really dont feel like going back to 4.2.2 to root lol.. battery life is great.. think ill stick with 4.4 /4.1/.2 until there's an exploit for it.
shouldnt there be an "adb push su /sdcard/" somewhere
TheWhiteChallenger said:
shouldnt there be an "adb push su /sdcard/" somewhere
Click to expand...
Click to collapse
Nope
Sent from my HTC Two
digitaloutsider said:
Well, upon flashing back to 4.2.2, my phone says I don't need the update. It can't be polled, so I have no idea when it'll prompt me to do it again.
With my luck I'll have to wait until after the push window closes and it becomes a freeforall.
Click to expand...
Click to collapse
That's what I'm afraid of..I'm going to wait.
ok so im having major issues, idk if its the root method or the fact that i push the ota via adb, so ima keep that conversation here: http://forum.xda-developers.com/showthread.php?p=48656238&posted=1#post48656238 for now in an effort not to clutter this thread needlessly
but i would really appreciate any help, especially if jcase would like to take a peek and see if he know wtf i did wrong.
on the lighter side can someone whos done this tell me if we were suposed to get the new dialer or did our kitkat get shorted out of that?
Just verifying for everyone that I run a Droid Maxx and I am part of the soak test and This did work I am on 4.4 with Root and Hotspot active used another mod on here for that and Also google wallet working with touch 2 pay !!!
Thanks Jcase As you know I think you are the best !!!!
jcase said:
My apologies for taking so long, life is hectic. This is a "root path" for the 4.4 update, and in this case you will retain your stock recovery so features like remote wipe will continue to work. It requires you downgrading to 4.2.2 or already be on 4.2.2 before updating to 4.4.
First you must use MotoWPNoMo, if you haven't then you will need to. Use RockMyMoto to gain root, then use MotoWPNoMo, and then restore to the 4.2.2 Camera update.
SlapMyMoto requires you to be on the 4.2.2 Camera update, you can find the firmware for your device below:
<someone please post the appropriate firmware links below, I dont have the droid devices here>
Step1)
Unzip SlapMyMoto-1,0.zip and push the jar file to your internal storage
Code:
adb push SlapMyMoto.jar /sdcard/SlapMyMoto.jar
Step2)
Use http://www.cydiaimpactor.com/ to open up a telnet session as system user on port 2222. We covered how to use Impactor and telnet in the RockMyMoto root, I won't be covering it again since this post is going to be long enough already, see here -> http://forum.xda-developers.com/showthread.php?t=2509590 or http://rootzwiki.com/topic/107098-root-rockmymoto-yes-even-the-first-ota/
Connecting over telnet, and run Stage1 with this command:
Code:
dalvikvm -cp /sdcard/SlapMyMoto.jar SlapMyMoto
When the device tells you to reboot, do this manually with "adb reboot" or your power button. It will not auto reboot on this step
Step3)
Once the device has rebooted, run Impactor again and connect over telnet just like in the previous step, then run the same command
Code:
dalvikvm -cp /sdcard/SlapMyMoto.jar SlapMyMoto
Once the device has rebooted, please take the 4.4 OTA.
Step4)
Now that we are on 4.4, we can finish the process with adb shell:
Code:
adb shell
cp /sdcard/install.sh /data/local/tmp/install.sh
chmod 755 /data/local/tmp/install.sh
echo "/data/local/tmp/install.sh" > /sys/kernel/uevent_helper
Then either wait, or toggle your bluetooth. Once the device reboots, you will have root.
Click to expand...
Click to collapse
---------- Post added at 11:14 PM ---------- Previous post was at 11:09 PM ----------
My Dialer looks the same !!
TheWhiteChallenger said:
ok so im having major issues, idk if its the root method or the fact that i push the ota via adb, so ima keep that conversation here: http://forum.xda-developers.com/showthread.php?p=48656238&posted=1#post48656238 for now in an effort not to clutter this thread needlessly
but i would really appreciate any help, especially if jcase would like to take a peek and see if he know wtf i did wrong.
on the lighter side can someone whos done this tell me if we were suposed to get the new dialer or did our kitkat get shorted out of that?
Click to expand...
Click to collapse
jcase said:
Nope
Sent from my HTC Two
Click to expand...
Click to collapse
I cannot downgrade. I get an error that the bootloader noticed it was a downgrade....
Oh well, I guess I'll wait for something else.
dtreth said:
I cannot downgrade. I get an error that the bootloader noticed it was a downgrade....
Oh well, I guess I'll wait for something else.
Click to expand...
Click to collapse
What was the exact erro, what were you downgrading to, and what specific device?
I did not confirm downgrade was possible, so it may only apply to those that already were on 4.2.2
jcase said:
What was the exact erro, what were you downgrading to, and what specific device?
I did not confirm downgrade was possible, so it may only apply to those that already were on 4.2.2
Click to expand...
Click to collapse
I took the OTA 4.4, tried to downgrade to the link I provided earlier in the thread, I have a Droid MAXX. I don't remember exactly what it said but it was the same error I got when I tried to FXZ my Razr MAXX HD to 4.1.2 unlockable after I took 4.1.2 locked forever. I don't really want to do it again but I will for exact text.
EDIT:
I did it again, it said
"downgraded security version
update gpt_main version failed
preflash validation failed for GPT"
I DID do MotoWpNoMo and it survived the OTA even without root or anything, so I'd be willing to test any methods you cook up to remedy this, if you do indeed attempt anything (and I'd also probably try to hug you through the computer somehow)
jcase said:
It requires you downgrading to 4.2.2 or already be on 4.2.2 before updating to 4.4.
Click to expand...
Click to collapse
Correct me if if I'm wrong, but this looks like I need to be on STOCK 4.2.2, correct?
I'm currently rooted with WP off on 4.2.2 (XT1080M, MAXX). When I run SlapMyMoto, it says rooted devices are not supported. If I'm understanding these steps correctly, I need only go back to stock 4.2.2 and then complete all of these steps. Can anyone that has completed these steps confirm this?
j.bruha said:
Correct me if if I'm wrong, but this looks like I need to be on STOCK 4.2.2, correct?
I'm currently rooted with WP off on 4.2.2 (XT1080M, MAXX). When I run SlapMyMoto, it says rooted devices are not supported. If I'm understanding these steps correctly, I need only go back to stock 4.2.2 and then complete all of these steps. Can anyone that has completed these steps confirm this?
Click to expand...
Click to collapse
I suggest doing a FXZ (w/ Keep Data) with House of Moto to get back to 4.2.2 stock without root. Be sure to flash the 12.15.15 firmware. You will not lose "WP off". Then proceed with the SlapMyMoto steps.
UPDATE: Success! Followed jcase's steps exactly and had no issues. One exception is that I installed the update from internal storage instead of an OTA.
A few other things I've noticed:
1. Recovery is now true recovery and is no longer the normal boot with "write protection off" (like it was with RockMyMoto). Now you see the Android with the red exclamation point like stock recovery.
2. MotoWpNoMo survives the 4.4 OTA!!!
3. Google hotword detection ("OK Google") in the GEL and GoogleNow isn't working. Moto X users on KitKat are seeing the same thing, so hopefully a fix is coming soon. Of course, Moto's Touchless Controls ("OK Google Now") still works like a charm.
Question...
Currently I'm on 4.2.2 no root, no WP off...fresh from the box...
I am not yet able to pull the update from the servers...should I wait till I get notification that there is an update to take? Or can I preemptively do steps 1-3 and then take the OTA whenever it comes and finish the process?
Sent from my XT1080 using Tapatalk
Here's my situation. I rooted MJ7 using rootjunky via vroot and then flashed to get rid of the chinese. I then installed safestrap and created a new romslot and put Hyperdrive on my device. Then... my usb port on my device quit working. Verizon is sending me a replacement. So I read somewhere to take the MK2 update to lose root and factory reset which supposedly was going to get me back to a point where I can send it to Verizon. I did this and unfortunately the SuperSu icon is still there and the Custom padlock boot animation is still there. I never did unroot through the terminal nor uninstall safestrap. SO..... what are my options here? USB still doesn't work so I cant reroot via USB and try to gracefully unroot and uninstall SuperSu. Is there a way to root directly on the device? Thanks.
G
rolltide78 said:
Here's my situation. I rooted MJ7 using rootjunky via vroot and then flashed to get rid of the chinese. I then installed safestrap and created a new romslot and put Hyperdrive on my device. Then... my usb port on my device quit working. Verizon is sending me a replacement. So I read somewhere to take the MK2 update to lose root and factory reset which supposedly was going to get me back to a point where I can send it to Verizon. I did this and unfortunately the SuperSu icon is still there and the Custom padlock boot animation is still there. I never did unroot through the terminal nor uninstall safestrap. SO..... what are my options here? USB still doesn't work so I cant reroot via USB and try to gracefully unroot and uninstall SuperSu. Is there a way to root directly on the device? Thanks.
G
Click to expand...
Click to collapse
The saferoot method might be able to be done via terminal emulator, the install.sh seems to be all shells commands. Don't see why you couldn't modify it to run from the phone, or enter the commands manually. Someone correct me if I'm wrong...
Edit:
Nvm. It states it cannot be ran from terminal emulator.
rolltide78 said:
Here's my situation. I rooted MJ7 using rootjunky via vroot and then flashed to get rid of the chinese. I then installed safestrap and created a new romslot and put Hyperdrive on my device. Then... my usb port on my device quit working. Verizon is sending me a replacement. So I read somewhere to take the MK2 update to lose root and factory reset which supposedly was going to get me back to a point where I can send it to Verizon. I did this and unfortunately the SuperSu icon is still there and the Custom padlock boot animation is still there. I never did unroot through the terminal nor uninstall safestrap. SO..... what are my options here? USB still doesn't work so I cant reroot via USB and try to gracefully unroot and uninstall SuperSu. Is there a way to root directly on the device? Thanks.
G
Click to expand...
Click to collapse
Perhaps post this in saferoot thread in dev forum. Smart guys hangout there
safestrap enabled, Hyperdrive driven
decaturbob said:
Perhaps post this in saferoot thread in dev forum. Smart guys hangout there
safestrap enabled, Hyperdrive driven
Click to expand...
Click to collapse
Unfortunately I haven't had 10 posts yet so it won't let me post anything there.
rolltide78 said:
Unfortunately I haven't had 10 posts yet so it won't let me post anything there.
Click to expand...
Click to collapse
Would obtaining a stock rom and flashing with Odin get me through this or will that flag the counter?
rolltide78 said:
Would obtaining a stock rom and flashing with Odin get me through this or will that flag the counter?
Click to expand...
Click to collapse
A full-wipe stock ROM will clear the custom flag. However, if you can't get USB to work, I'm not sure what you can do.
k1mu said:
A full-wipe stock ROM will clear the custom flag. However, if you can't get USB to work, I'm not sure what you can do.
Click to expand...
Click to collapse
Dang. We'll can you provide me with a link to the stock? The ones I've found lead me not too confident.
rolltide78 said:
Dang. We'll can you provide me with a link to the stock? The ones I've found lead me not too confident.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2578209
gnubian said:
http://forum.xda-developers.com/showthread.php?t=2578209
Click to expand...
Click to collapse
So this will keep Knox/etc alone? It still baffles me why we can't root without using a PC.
gnubian said:
http://forum.xda-developers.com/showthread.php?t=2578209
Click to expand...
Click to collapse
Also, one other thing to add... it does charge verrrrrryyy slowly when its powered off and connected. It loops and vibrates the charging icon with a grey spinning icon. It does charge though (about a 1/4 over a 4 hour span). So its not completely not working..whichi is odd.
rolltide78 said:
Also, one other thing to add... it does charge verrrrrryyy slowly when its powered off and connected. It loops and vibrates the charging icon with a grey spinning icon. It does charge though (about a 1/4 over a 4 hour span). So its not completely not working..whichi is odd.
Click to expand...
Click to collapse
Are you using the USB cable that came with the phone? Some other USB cables will charge, but won't transfer data. So, it may be the cable and not the USB port. Just a thought!
rolltide78 said:
So this will keep Knox/etc alone? It still baffles me why we can't root without using a PC.
Click to expand...
Click to collapse
You can root using a Mac, or a Linux system. But I don't think that's what you're asking I think what you mean is "why do you need another computer to do this?"
The reason that you need a separate computer is that the security policy on the Verizon device doesn't allow you to push a file to the phone and make it executable. i.e. you can't get it to run.
Specifically, to root you need to run the supplied "getroot" program. ADB can be used to push that to the phone and make it executable:
adb push getroot /data/local/tmp/
adb shell chmod 755 /data/local/tmp/getroot
Click to expand...
Click to collapse
So you now have a getroot program that can be executed to root the phone. The "chmod" command sets the "executable" bits so the program can run. You've got to do that to allow it to get started and root the phone.
So, let's get rid of the PC. Copy the getroot program to the external SD card. OK, so it's now on the phone.
You can't run programs from that external card, and can't set it to be executable. But the rooting scripts writes it to another place and marks it executable, so why not just do that from a terminal emulator prompt? So, it shoudl be easy - copy /mnt/extSdCard/getroot to /data/local/tmp/getroot.
Cool, that works. So now change it to be executable so you can run it:
[email protected]: / $ chmod 755 /data/local/tmp/getroot
unable to chmod /data/local/tmp/getroot: Operation not permitted
Click to expand...
Click to collapse
Oops. You can't do that. Without that, you can't run it. Game over.
I'm not using adb to force use of a separate computer to run the root. I'm doing it because the policy on the i545 doesn't allow you to push a program onto the phone and run it unless you do it via ADB.
Some phones/tablets aren't so locked down, and so may be able to use a terminal emulator to do this. I'm going to be posting info this weekend on how to do that, which may help to get rid of the PC, kind of.
Any other questions?
As far as the "Custom" status goes, this is a FAQ. Short answer:
Do you want root? OK, then you will be running a non-standard system, i.e. customized.
Do you want to avoid seeing the Custom flag? If so, either run stock, unrooted, or use the Wanam hack to fake the status.
If you don't want to be running custom software, then don't. Go stock.
Finally, "Knox" is not a thing, it's a series of protective mechanisms, some of which we can disable on rooted phones. We can't override the Knox bootloader flag ("Knox warranty void") flag, however. Apparently the Knox container software uses that to disable the ability to use a container.
k1mu said:
You can root using a Mac, or a Linux system. But I don't think that's what you're asking I think what you mean is "why do you need another computer to do this?"
The reason that you need a separate computer is that the security policy on the Verizon device doesn't allow you to push a file to the phone and make it executable. i.e. you can't get it to run.
Specifically, to root you need to run the supplied "getroot" program. ADB can be used to push that to the phone and make it executable:
So you now have a getroot program that can be executed to root the phone. The "chmod" command sets the "executable" bits so the program can run. You've got to do that to allow it to get started and root the phone.
So, let's get rid of the PC. Copy the getroot program to the external SD card. OK, so it's now on the phone.
You can't run programs from that external card, and can't set it to be executable. But the rooting scripts writes it to another place and marks it executable, so why not just do that from a terminal emulator prompt? So, it shoudl be easy - copy /mnt/extSdCard/getroot to /data/local/tmp/getroot.
Cool, that works. So now change it to be executable so you can run it:
Oops. You can't do that. Without that, you can't run it. Game over.
I'm not using adb to force use of a separate computer to run the root. I'm doing it because the policy on the i545 doesn't allow you to push a program onto the phone and run it unless you do it via ADB.
Some phones/tablets aren't so locked down, and so may be able to use a terminal emulator to do this. I'm going to be posting info this weekend on how to do that, which may help to get rid of the PC, kind of.
Any other questions?
As far as the "Custom" status goes, this is a FAQ. Short answer:
Do you want root? OK, then you will be running a non-standard system, i.e. customized.
Do you want to avoid seeing the Custom flag? If so, either run stock, unrooted, or use the Wanam hack to fake the status.
If you don't want to be running custom software, then don't. Go stock.
Finally, "Knox" is not a thing, it's a series of protective mechanisms, some of which we can disable on rooted phones. We can't override the Knox bootloader flag ("Knox warranty void") flag, however. Apparently the Knox container software uses that to disable the ability to use a container.
Click to expand...
Click to collapse
Thank you very much for the explanations. I love it! First...I've tried using multiple USB cables and no go (except for the slooowww charge using the vibrate behavior loop). Any microusb cable used to work fine. I want root but just not on this device as I'm sending it in to Verizon. If I could get rid of the custom boot animation and the SuperSu app I wouldn't be wary but I just feel awkward sending a device back with these two items still visible ont he device. I'll root and load hypervisor on the new device when it arrives. Now, I'm just trying to get it to a state to send back and am trying to figure out my options.
rolltide78 said:
Thank you very much for the explanations. I love it! First...I've tried using multiple USB cables and no go (except for the slooowww charge using the vibrate behavior loop). Any microusb cable used to work fine. I want root but just not on this device as I'm sending it in to Verizon. If I could get rid of the custom boot animation and the SuperSu app I wouldn't be wary but I just feel awkward sending a device back with these two items still visible ont he device. I'll root and load hypervisor on the new device when it arrives. Now, I'm just trying to get it to a state to send back and am trying to figure out my options.
Click to expand...
Click to collapse
Have you used the SuperSU "full unroot" setting to remove it? That'll get rid of SuperSU at the very least;
My Saferoot thread has unrooting info in post 2 - worth trying, especially before killing SuperSU.
k1mu said:
Have you used the SuperSU "full unroot" setting to remove it? That'll get rid of SuperSU at the very least;
My Saferoot thread has unrooting info in post 2 - worth trying, especially before killing SuperSU.
Click to expand...
Click to collapse
See that's just it....I took the MK2 OTA update from MJ7 thinking that is how to unroot and now I no longer have root. I get the binary not found issue when I try to launch supersu. Root checker confirms I no longer have root.
k1mu said:
You can root using a Mac, or a Linux system. But I don't think that's what you're asking I think what you mean is "why do you need another computer to do this?"
The reason that you need a separate computer is that the security policy on the Verizon device doesn't allow you to push a file to the phone and make it executable. i.e. you can't get it to run.
Specifically, to root you need to run the supplied "getroot" program. ADB can be used to push that to the phone and make it executable:
So you now have a getroot program that can be executed to root the phone. The "chmod" command sets the "executable" bits so the program can run. You've got to do that to allow it to get started and root the phone.
So, let's get rid of the PC. Copy the getroot program to the external SD card. OK, so it's now on the phone.
You can't run programs from that external card, and can't set it to be executable. But the rooting scripts writes it to another place and marks it executable, so why not just do that from a terminal emulator prompt? So, it shoudl be easy - copy /mnt/extSdCard/getroot to /data/local/tmp/getroot.
Cool, that works. So now change it to be executable so you can run it:
Oops. You can't do that. Without that, you can't run it. Game over.
I'm not using adb to force use of a separate computer to run the root. I'm doing it because the policy on the i545 doesn't allow you to push a program onto the phone and run it unless you do it via ADB.
Some phones/tablets aren't so locked down, and so may be able to use a terminal emulator to do this. I'm going to be posting info this weekend on how to do that, which may help to get rid of the PC, kind of.
Any other questions?
As far as the "Custom" status goes, this is a FAQ. Short answer:
Do you want root? OK, then you will be running a non-standard system, i.e. customized.
Do you want to avoid seeing the Custom flag? If so, either run stock, unrooted, or use the Wanam hack to fake the status.
If you don't want to be running custom software, then don't. Go stock.
Finally, "Knox" is not a thing, it's a series of protective mechanisms, some of which we can disable on rooted phones. We can't override the Knox bootloader flag ("Knox warranty void") flag, however. Apparently the Knox container software uses that to disable the ability to use a container.
Click to expand...
Click to collapse
I wish the moderators were more helpful so we could have a number of stickies in these forums. We could save so many from screwing their phones up as well as saving us a lot of time in constantly explaining the same stuff over and over again because some new comers don't want to take the necessary time to research the process. As you can tell, I'm getting a bit testy with new posters in some of my replies because its so obvious they put in so little research into what their phones are capable of taking for mods. This explains the background and how and why ADB needs to be understood as well as the ODIN process before you take the plunge. Three thumbs up to you!
rolltide78 said:
See that's just it....I took the MK2 OTA update from MJ7 thinking that is how to unroot and now I no longer have root. I get the binary not found issue when I try to launch supersu. Root checker confirms I no longer have root.
Click to expand...
Click to collapse
I apologize for my lack of experience with rooted with the Android platform. I think my downfall was relying too much on youtube videos by folks like rootjunky and galaxys4root. They are excellent at obtaining root but not so much on removing root and getting rid of the Custom screens, etc. When I tried to come here it was a bit overwhelming with all the variants, versions, and options. I thought I was doing the correct methods. I'm going to look into adb and understand more of the inter-workings now. Hopefully it won't be an issue with Verizon but I just wanted to do as much as I could to get it back to stock given the issues I have with my device and USB.
Am I completely out of luck removing the padlock custom?
rolltide78 said:
Am I completely out of luck removing the padlock custom?
Click to expand...
Click to collapse
If you can't get your device to be recognized over USB, you're kind of stuck.
Typically, you'll at least see the "Verizon Mobile" disk drive show up when you plug it in. If you see that, try running the VZW_Software_upgrade_assistant.exe that appears - that will flash stock and clear the "Custom" flag.
rolltide78 said:
I think my downfall was relying too much on youtube videos...
Click to expand...
Click to collapse
Bingo! Your modifying a $700 device based on YouTube videos. At bare minimum one should take the time to read and understand the complete process. Yes it can be very overwhelming because of all the different information contained here. Stick with reading the most popular threads in the topic you want to learn about. They are generally up to date and contain answers to most questions.
Sent from my SM-T310 using Tapatalk
How do i root my zte z831/chapel? if there is one will somebody please explain it to me?:crying:
ZTE MAVEN 2 Z831 - Android 6.0.1 - Messaging App .3
I just got this new AT&T phone and need to root it to delete this bloatware!! Also need to fix Messaging App .3 - I just got this phone and the Messaging App is crashing constantly!
I've searching all around, tried everything recommended, Kingo desktop and one-click as well as SRS... tried all recommended fixes for Messaging App and NOTHING ...
Experts please reply?!?
To start off. If the ZTE maven 2 was bought from a carrier your phone is boot loader locked. Until your phone's boot loader is unlocked by some soft ware or a source available rooting the ZTE maven 2 will be impossible. Even I the bootloader was unlocked there is still no custom Roms made for this phone yet. Definitely the first thing needed will be the TWRP program. So far no new methods of rooting or unlocking the boot loader yet.
Ok... So are we saying it's not possible? Or it is possible with a difficult process?
Lookingforinfo said:
To start off. If the ZTE maven 2 was bought from a carrier your phone is boot loader locked. Until your phone's boot loader is unlocked by some soft ware or a source available rooting the ZTE maven 2 will be impossible. Even I the bootloader was unlocked there is still no custom Roms made for this phone yet. Definitely the first thing needed will be the TWRP program. So far no new methods of rooting or unlocking the boot loader yet.
Click to expand...
Click to collapse
Mine has an OEM unlocking option under Developer options ...
Sent from my LG-V410 using XDA-Developers mobile app
Has anyone made progress with the Z831
errata
i have gotten kingroot apk to successfully rooted my maven z831.
Only the apk worked, the windows version did not.
However, its not persistent between reboots.
But, i only need to root the phone and remove bloatware, so that work fine for me.
one more thing to note: the first 2 times after reboot, kingroot was able to smoothly root the phone again.
by the third time, it took a bit longer to root and went thru 2 reboots, between the same rooting process, which is normal.
So, if you want to remove bloatware, i would suggest: install titianium backup root (TI), root the phone, use TI to remove bloat
Tested kingroot 5.0.5, achieved partial root and it doesn't persist. cannot grant SU privilege to some apps. cannot remount partition as R/W, so you are not really "deleting" the bloatware, it will come back after reboot. Also very unstable, will have frequent random power offs which resets root. Tried to replace with Super SU and make changes via terminal but nothing worked yet.
How did you get it to work? I have tried to run it multiple times and it won't root with Kingoroot on my Maven 2 ZTE z831.
smith.ks1028 said:
How did you get it to work? I have tried to run it multiple times and it won't root with Kingoroot on my Maven 2 ZTE z831.
Click to expand...
Click to collapse
Make sure you are running the latest version of kingroot.
is there a forum for this phone?
cfli1688c1 said:
i have gotten kingroot apk to successfully rooted my maven z831.
Only the apk worked, the windows version did not.
However, its not persistent between reboots.
But, i only need to root the phone and remove bloatware, so that work fine for me.
one more thing to note: the first 2 times after reboot, kingroot was able to smoothly root the phone again.
by the third time, it took a bit longer to root and went thru 2 reboots, between the same rooting process, which is normal.
So, if you want to remove bloatware, i would suggest: install titianium backup root (TI), root the phone, use TI to remove bloat
Click to expand...
Click to collapse
I'm starting to get mad. Has anyone made any progress on rooting this damn phone since it is such low memory?
JDeschaine1985 said:
I'm starting to get mad. Has anyone made any progress on rooting this damn phone since it is such low memory?
Click to expand...
Click to collapse
I got perm root did u miss my last post where it shows it? We don't have a forum to my knowledge for the maven 2 for me to post a guide if we get one I will post a guide on how to root it perm with kingroot
Nope,
I didn't see that post. Would you mind sending it to me?
JDeschaine1985 said:
I'm starting to get mad. Has anyone made any progress on rooting this damn phone since it is such low memory?
Click to expand...
Click to collapse
Here's how I got my zte maven 2 (ATT) rooted.
Disclaimer: This method worked for me but may not work for others, I am not responsible if your device is bricked as a result of this. Also, this method does seem to be a bit finicky and inconsistent.
Credit to @madvane20 his post here helped me get root for this phone. He also got his phone rooted before I did, be sure to give him thanks.
Credit to @ZTE Girl for finding a way to remove ads from King root and keeping perm root.
With KingRoot you can get perm root, but personally I hate KingRoot, so at the end there is a method to replace KingRoot with SuperSu. Unfortunately SuperSu root resets on reboot, but a quick, 10 second adb command will reroot your phone with SuperSu
Edit: @ZTE Girl found that using lucky patcher to remove ads from King root worked for her and kept permroot.
Step 1: Enable USB debugging on your phone, and download adb and ZTE drivers to your PC.
2: Download KingRoot from KingRoot.net (download the apk for android)
3: Connect your phone to ADB, and run this command in terminal adb shell make sure you get no errors and accept any USB debugging requests.
4: Now type reboot disemmcwp This will reboot your phone without write protection.
5: When your phone reboots, run adb shell again, and install the kingroot APK. Google will give you a warning about this app being unsafe, install it anyways.
6: Now, here's the finicky part, sometimes KingRoot works, sometimes it doesn't, you just have to keep trying. Make sure your phone is still connected to the computer through adb shell, and then click try root in KingRoot. While KingRoot is attempting to get root: in adb shell keep typing su and pressing enter. Just spam this, It will keep giving errors, but eventually it (should) work. Make sure to accept any prompts on your device while you do this.
7: When you are able to successfully get into su, wait a bit, just to make sure your device doesn't restart
8: Now type getprop ro.product.name, the response should be Z831
9: Now type setprop persist.sys.k Z831, then type getprop persist.sys.k It should say Z831
10: Now type cd /dev/block/platform/soc.0/7824900.sdhci/by-name/
11: Then type dd if=recovery of=/sdcard/recovery.img This will backup your recovery, I highly recommend that you copy the backup to your computer in case something goes wrong.
12: Now type dd if=boot of=recovery, this will write boot to recovery. This part can be risky, it worked for me, but if it bricks your device, you can't say I didn't warn you with that said, don't let that scare you away from finally rooting this device and getting all the advantages that come with it
13: Now type this reboot recovery Your device my blackscreen and not boot after this, personally mine did, and I fixed it by removing the battery, and after puttting it back in, it booted normally.
14: When your phone boots up, type adb shell again, and then type su
15: Type id response should be "uid=0(root) gid=0(root) context=u:r:shell:s0" Note: I don't think my uid showed when I did this, if yours doesn't show, don't worry, it should work fine.
16: Now type setenforce 0
17: After that, type getenforce, it should respond back with "permissive"
18: To test if system is writable, type mount -o remount,rw /system, if you get no errors, everything is working , if you get an error, type reboot disemmcwp, and then try to mount system RW again.
19: I would recommend removing the update service now, so an update doesn't come and screw up your root.
20: Read this: Now you should have permroot with kingroot, however, as you will soon find, kingroot has a ton of ads, and can get very annoying. So, if you want SuperSu and no kingroot, keep reading. If you want to keep KingRoot, then you are done, have fun with your rooted Maven 2
Edit: @ZTE Girl found that you can use lucky patcher to remove ads from Kingroot while still keeping permroot.
21: Download the KingToSuperSu zip in attachments, I have modified it slightly from the original zip so it works better. You will see a folder inside the zip named "mrw" copy this folder to the root of your /sdcard (must be copied to the root of /sdcard)
22: Now go into adb shell again, and then type su
23: Type mount -o remount,rw /system
24: If you get no errors, simply type sh /sdcard/mrw/root.sh, you will see a lot of errors in the script, no need to worry, now you should have SuperSu. Note: sometimes you get a notification saying "com.eu.chainfireSuperSu has stopped" or something like that, run the command again, and it should work.
25: SuperSu will say binary needs to be updated, but the update always fails, however you can click no thanks, and it will work fine.
26: SuperSu root will go away after you reboot, however, to get root back, simply type adb shell (while connected to your computer of course) then su and then sh /sdcard/mrw/root.sh and just like that, you're rooted again. Note: I couldn't get this to work in a terminal emulator, and it would only work in adb shell for me.
Edit: If you want stock recovery back, run this command in adb shell with su dd of=recovery if=/sdcard/recovery.img. I haven't tested this, and it might unroot/brick your device. This is at your own risk.
This guide was long and complicated, sorry for that, if you need any help, just ask me and I will try to help the best I can.
If this guide helped, please clicks thanks, it means a lot to me
Proof: http://imgur.com/a/zecyU
Also: if any mods/admins read this, could you please make a forum for ZTE Maven 2? I would love to get this guide out more so more people can root their phone.
Ur guide is pretty much what I did I asked for a forum but never got one I have a guide for warp 7 very similar just not as much words wrote out however I didn't try to replace king root does it work without risk of brick to replace king oh SuperSU u have to keep enabling I guess. U can disable all the annoying stuff kingroot has
---------- Post added at 02:47 PM ---------- Previous post was at 02:41 PM ----------
Also u didn't list at the end once u have root u can reflash reg recovery back unless I mean the SuperSU part needs it still the same
madvane20 said:
Ur guide is pretty much what I did I asked for a forum but never got one I have a guide for warp 7 very similar just not as much words wrote out however I didn't try to replace king root does it work without risk of brick to replace king
Click to expand...
Click to collapse
Yup, your post for the warp 7 helped me a lot, I gave you credit in my post too.
You can replace KingRoot without any risk of brick, only problem is SuperSu is only temproot. To get root back after reboot you just have to run a quick command in adb shell, it's inconvenient, but I think it's much better than the alternative of having KingRoot.
Edit:
I haven't tried putting recovery back, so i'm not sure if that would work or not. I'll put that in the post though.
Ok I'll give a shot at making SuperSU perm once I get home not home for weekend
---------- Post added at 02:51 PM ---------- Previous post was at 02:50 PM ----------
I have a guide ready for the phone but never posted due to no forum for it lol
---------- Post added at 02:52 PM ---------- Previous post was at 02:51 PM ----------
So since u have one posted already we can use that and if I get SuperSU to be perm then I will add to the guide.
madvane20 said:
Ok I'll give a shot at making SuperSU perm once I get home not home for weekend
---------- Post added at 02:51 PM ---------- Previous post was at 02:50 PM ----------
I have a guide ready for the phone but never posted due to no forum for it lol
---------- Post added at 02:52 PM ---------- Previous post was at 02:51 PM ----------
So since u have one posted already we can use that and if I get SuperSU to be perm then I will add to the guide.
Click to expand...
Click to collapse
Yeah SuperSu perm would be nice, I think we just need to add a startup script or something? Also, I feel bad since I kinda stole your guide, I can delete my post if you want.
My first post, please be gentle. So I bought a pretty sweet tablet on sale for $60. I know with these no name tablets, there is no expectation of software updates or support really. thats ok. Stock marshmallow is stable and does most of what I need. gravity box and root would be tha shiznit. Framaroot, towelroot, kingroot all failed (not enirely unexpected).
ABD and fastboot worked great like they should. I used Terminal app on my mac for control. After seeing bootloader unlock in developer options, I was able to unlock bootloader in like 4 min (no surprises there).
I tried to mount system as -RW using several different ADB and ADB shell commands, all were denied. I tried to remount system but got the not uncommon "adbd cannot run as root in production builds".
I'm at the end of my skill. I was able to get the flashtool and stock firmware from the manufacturer. I was hoping having the firmware and bootloader unlocked, rooting would be somewhat easier for someone with mroe skill. Any ideas? thanks in advance.
Firmware
https://drive.google.com/file/d/0Bz90gDBcVbcCdk5rZWtOdTdiejA/view?usp=drive_web
Ps if it goes,on sale again for $60, its a great buy.
2gb/16gb/10.1/micro hdmi/gps/bluetooth/microsd. Purchased 2 to Upgrade the kids' sero 7 pros.
Product
https://www.amazon.com/dp/B074W8R6H3?tag=slickdeals&ascsubtag=e1b4d5c0bf4311e7becf7a1b1e43ba390INT
If anyone is able to root this tablet, please share. Thanks.
---------- Post added at 08:07 AM ---------- Previous post was at 08:02 AM ----------
DarkPhazon said:
My first post, please be gentle. So I bought a pretty sweet tablet on sale for $60. I know with these no name tablets, there is no expectation of software updates or support really. thats ok. Stock marshmallow is stable and does most of what I need. gravity box and root would be tha shiznit. Framaroot, towelroot, kingroot all failed (not enirely unexpected).
ABD and fastboot worked great like they should. I used Terminal app on my mac for control. After seeing bootloader unlock in developer options, I was able to unlock bootloader in like 4 min (no surprises there).
I tried to mount system as -RW using several different ADB and ADB shell commands, all were denied. I tried to remount system but got the not uncommon "adbd cannot run as root in production builds".
I'm at the end of my skill. I was able to get the flashtool and stock firmware from the manufacturer. I was hoping having the firmware and bootloader unlocked, rooting would be somewhat easier for someone with mroe skill. Any ideas? thanks in advance.
Firmware
https://drive.google.com/file/d/0Bz90gDBcVbcCdk5rZWtOdTdiejA/view?usp=drive_web
Ps if it goes,on sale again for $60, its a great buy.
2gb/16gb/10.1/micro hdmi/gps/bluetooth/microsd. Purchased 2 to Upgrade the kids' sero 7 pros.
Product
https://www.amazon.com/dp/B074W8R6H3?tag=slickdeals&ascsubtag=e1b4d5c0bf4311e7becf7a1b1e43ba390INT
Click to expand...
Click to collapse
Thanks very much for sharing the firmware. I also like this tablet for the price.
played around with the flash tool included with the firmware sent by the manufacturer. After a little trial and error I got the program into english. I'm running into some problems though. I run windows 7 via Bootcamp on my mac. Windows does not recognize either of my tablets unders ADB. Unfortunately the driver installation package won't install for me so i'm guess thats my problem. It seems the scatter file for the tablet (needed to create custom recovery as I understand) is included with the stock firmware. so 2 questions
1. Anyone able to get the driver package to install?
2. anyone know how to compile CWM or twrp if I provide the stock scatter file?
If some can provide the recovery I'll borrow a friend's laptop to try to flash (assuming i can get drivers to install!!!!). scatter attached.
ok. Still trying on this one. I reinstalled windows 7 clean. I still am unable to access ADB through windows. Adb still fine when booted into mac. Pretty sure its a driver thing. according to their "tutorial", the signed drivers install fine but the unsigned drivers (including ADB of course) do not install.
I'm not a windows guy but could use some help. I have turned off UAC and have pressed F8 during reboot to allow unsigned drivers.
Yet, nothing like what they describe is happening. Appreciate any help. This is HUGE because since no one has stepped forward yet, I'm just gonna keep trying things. BUt I cannot do a factory restore if/when i break something without full windows 7 drivers installed as the flash tool will not work. please help. the "tutorial is attatched, and is part of the firmware posted earlier.
Thanks for working on this. I have the Npole NT103 tablet also, and would appreciate being able to root it.