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
See by the post count, certainly a noob but I think I've done my homework here. I know this is posted in various places with long threads attached but here it is ...
Atrix 4G ATT
I was on 1.8.3 rooted, did the OTA update to 4.5.91. I think I want root back.
Is this thread the safest way to accomplish this?
http://forum.xda-developers.com/showthread.php?t=1138204 (OP)
I'm not concerned with losing any data on the phone as far as media or anything.
abuse away for being new, idiot with android at the moment.
Best and safe way is preinstall method by eval.... Why?
you dont need to unlock your unit it work with lock / unlocked units
So the method referenced in my first post?
1. Flash with RSD (2.3.4 SBF)
Then ...
Hi guys.. here is a useful little /preinstall for you (attached)
Put phone in fastboot mode, then:
Code:
fastboot flash preinstall preinstall.img
fastboot reboot
(older versions maybe need "fastboot -i 0x22b8")
after fastboot & reboot, type in adb ("adb shell") or terminal emulator, exactly:
Code:
/preinstall/dosu
/bin/mount -o remount,rw /system
cp /preinstall/su /system/bin/
chmod 6755 /system/bin/su
PATH=/system/bin:$PATH pm install /preinstall/Superuser.apk
The last step is optional (and next-to-last *should* be unnecessary), as you can install Superuser however you like. In fact, if you've installed it, simply typing "/preinstall/su" is another way to root, and you could then mount /system read-write and copy it into /system/bin.
Many thanks to Brandon & The2d for brainstorming this out in a crazy "there's no way it could be possible" rooting session. There were a lot of harder ways... who knew we'd be so lucky! And thanks to Edgan for the great "dosu" =)
You can find fastboot here: http://forum.xda-developers.com/show....php?t=1138092
Click to expand...
Click to collapse
thanks!
I used this briefmobile method
http://briefmobile.com/motorola-atrix-4g-root
same as you - OTA to 2.3 from stock locked AT&T. Above method worked first time no data loss. YMMV of course.
I specifically did NOT want to use anything related to sbf due to all the warnings about bricking etc. etc.
I'm holding off on BL unlock as right now 2.3 is a great build even with AT&T restrictions/crapware, hoping that the official unlock will drop before stable CM/AOSP builds appear, but you never know lol
I saw this one too but wasn't sure, no issues at all on this one?
EDIT: That was easier than anticipated..... What's next for a noob such as myself? Tech background: UNIX Engineer (AIX/Solaris/Linux) 15+ years *NIX experience. I don't know crap for java, I alright with c, perl, python, korn ....
Hi there everyone, i am in need of assistance.
I have follwed the guide on here for downgrading my phone usin the ADB commands and all is good up until the actual downgrading stage. After a few attempts i had managed a temp root (i think) using command line.
" adb shell " brought back the # so i know i did that right, but when it comes to pushing the rom file to my sd card it comes back adb not found in which case i cannot reboot the bootloader if that doesnt work.
Is there something i am doing wrong or is the file im uusing just not compatible, "PC10IMG.zip"
If there is another way to downgrade after temp root with maybe a different rom file i would be very grateful if someone could help me.
Any questions you have to help me, just let me know
Thanks
Sent from my HTC Vision using XDA App
Im still very new at this but i'll thrown in my two cents here.
After you've gotten temporary root status '#' and you've set your version to 1.00.000.0 following the guide, your next step is it push the stock ROM used to downgrade into your sd card.
At this point make SURE you are not in the adb shell, (aka you dont see the #)
so make sure you exit first.
Another thing is to make sure the ROM you want to push, the "...._PC10IMG.zip" file is in the correct directory, same directory as your CMD.
Lastly the push process takes time so dont be impatient, unlike the other files you pushed before which were more or less instant, this one will take at least a minute and the CMD may look idle so really just have to wait.
when the results show, you can then proceed with reboot bootloader command.
hope it helps.
i got stuck after this point, i keep getting a cid error, which is a totally differnt issue from your above question.
Hi all,
I have been through douzens of threads and forums looking for a solution to this.
I followed some instructions to modify the build.prop file on my Huawei G535-L11 to disable Huawei theme manager in order to get Xsposed working fully (changed ro.config.hwtheme: 0). I did a backup of my original build.prop before hand, and my phone was rooted and unlocked but running the stock rom.
Unfortunately, it rebooted but won't go past the first 'EE' splash screen (just turns off again).
I can inconsistently get in to both fastboot and Android recovery, so I have been trying to use adb to push the original build.prop to /system/ on the phone.
However, this fails as /system/ is apparently RO. I have now discovered that I can't get SU permissions despite my phone being rooted.
If I try:
adb shell
$ su
nothing happens and it goes back to a $ prompt.
If I try:
adb root
I get the message (paraphrased):
adb cannot run as root in production builds.
So I can't push or do any adb method of restoring the build.prop file?! I don't understand why it is acting as if it is not rooted. I had Link2sd, Gravity Box, No Frills Cpu Controller all set up and working before, so I'm fairly sure I did truly have root.
I have also tried flashing a TWRP recovery, which apparently is successful, but when I go in to recovery it is still the Android Recovery.
Does anyone have any ideas what I could do to get my phone working again please?! This is my last gasp before the phone gets filed under 'B' in the cylindrical cabinet in the corner of the room!
Any assistance greatly appreciated!
Some systems are very finicky with modded build.props, or you didn't set the file's permissions correctly. I'm afraid without being able to boot or a working custom recovery, then adb won't work, much less root enabled adb functions. adb works in some stock recoveries, but only for sideloading files directly signed by the manufacturer. In regards to TWRP, is the bootloader unlocked? If not, that would explain why it didn't work. Other than that, I don't believe you'll have any other options besides reloading the stock firmware.
Hi,
Thanks for the reply. Yes, the bootloader was / is unlocked.
Unfortunately, there isn't any stock firmware available anywhere. Unless someone out there has a backed up rom image from the EE Kestrel?
This is supposed to be a working TWRP for your device http://forum.xda-developers.com/showpost.php?p=58522448&postcount=117 - if you get it loaded, there might be a chance to push the working build.prop back to the phone. I would read that thread too and see if there isn't more useful info there or another member with your phone that could make a backup for you. Good luck.
Thanks.
Unfortunately, I'm pretty sure that is the TWRP I've tried. I'll double check when I'm on my PC.
I might try requesting a rom image on that thread, but the community for this phone seems to be pretty dead :/
I've just gone and ordered a new phone anyway, but it seems like a waste of a good phone just for the sake of one line of bad code!
Thanks for your help. I'll post again if I have any success.
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.