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.
Related
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
Hi Guys
I'm trying to root this phone so after a bit of looking around I have vroot and all the drivers for the phone.
I have the English version of the software but half way through the root, it ask for something to be done in Chinese which I'm not sure what it needs.
On screen I get the options to hit next and on the phone its enable restore or not.
Anyone have any clues as to what needs to be done to stop the root failing ?
Thanks
Richie
No one else ever root this device?
richie1888 said:
No one else ever root this device?
Click to expand...
Click to collapse
I Did, just install Vroot or RootGenius they should do the trick.
i went for RootGenius
i suggest u to install CWM recovery after rooting and keeping a copy of the original rom
Sorry i cannot post link since i registered only to answer
Thanks, Trabacchin.luigi - most helpful Just got my S208 today and XDA first place to come for helpful info
RootGenius did not work, but then again, I am running it in Paralells desktop on MAC which may be the issue. Awaiting for a Windows machine to be free to try it on that.
Thanks again,
Jeff
---------- Post added at 12:55 PM ---------- Previous post was at 12:40 PM ----------
Update - Vroot worked first time.
Couple of pointers for others:
RootGenius loads LOTS of junk stuff to your PC unless you custom install and be VERY CAREFUL to deny loading of "apps". Lots of double-negative options, looks like you are saying "no" but you are really saying "yes". Be careful.
Vroot worked straight away - BUT loads some Chinese options on your phone and all of a sudden your call logs, contacts, SMS etc are being accessed. All text in Chinese characters so do not know what exactly the apps are. Deleted.
Jeff
Well, I had LOTS of problems subsequently with Vroot (now iRoot). In the end, I unrooted and used KINGO ROOT and it worked first time, with no extra odd apps loaded, doing who-knows-what (iRoot add-ons!).
Anyway, have now rooted the S208 and I hope to be able to update the firmware, resizing the partitions at the same time.
Look here http://www.android-hilfe.de/8390125-post4.html
Install mentioned recovery using flash tool, boot into recovery, leave recovery and answer question to install SU by swiping slider. After reboot into ROM, let SU do update (it will ask you) and voilá phone is rooted
root Cubot S208 using KingRoot (I installed also Purify)
trabacchin.luigi said:
I Did, just install Vroot or RootGenius ...
Click to expand...
Click to collapse
tested RootGenius and Vroot (now iRoot) *installed lot of spam*.
I rooted my firmware CUBOT_4041C_V12 original buil using KingRoot (I installed also Purify) using this xda download link:
http://forum.xda-developers.com/android/apps-games/one-click-root-tool-android-2-x-5-0-t3107461
and next
http://forum.xda-developers.com/devdb/project/dl/?id=13663&task=get
Hello! I've upgraded to 5.1 and have lost my root. I have tried using kingo and towelroot but neither have worked. I have tried downgrading to 4.3 re-rooting and then upgrading to 5.1 only to lose root again. Any help as to fix this would be awesome and highly appreciated!
Use TWRP
Milkteabubbles said:
Hello! I've upgraded to 5.1 and have lost my root. I have tried using kingo and towelroot but neither have worked. I have tried downgrading to 4.3 re-rooting and then upgrading to 5.1 only to lose root again. Any help as to fix this would be awesome and highly appreciated!
Click to expand...
Click to collapse
You can flash twrp to root, then install superusersu. There's a zip file that's been posted in the forums recently by ArkAngel 06 that has everything you should need and a step by step guide to do it. Hope this helps
This question has been asked and answered. Do you guys read the other threads at all?
To get root and TWRP.
Credit to Foltz61.
1. Boot to bootloader.
2. Fastboot boot TWRP-L.img
3. Install supersu-2.49.zip (even though I didn't lose root)
4. Reboot back to system.
5. Reboot back to bootloader.
6. fastboot flash recovery TWRP-L.img.
7. fastboot reboot.
8. Boot to recovery and had TWRP
Thanks
Thank you both for your help! I saw this posted in the other threads but there's been a lot of activity since the release of 5.1 and it was all getting confusing
to get su 2.49 .zip do a Google search u will find it after twrp just flash su 2.49.zip and ur all set .
I tried n its working fine
Would be best at this time to not flash twrp. Instead fastboot boot twrp.img then install the beta.SuperSU v2.49.
Sent from my MT2L03 using XDA Free mobile app
Re-rooting your LOLLIPOP HAM2
Milkteabubbles said:
Hello! I've upgraded to 5.1 and have lost my root. I have tried using kingo and towelroot but neither have worked. I have tried downgrading to 4.3 re-rooting and then upgrading to 5.1 only to lose root again. Any help as to fix this would be awesome and highly appreciated!
Click to expand...
Click to collapse
If your Bootloader is still unlocked, skip to step 5
UNLOCKING YOUR BOOTLOADER
1) Request your 16 digit Bootloader Unlock Code from [email protected] (you'll need to give them your phone's IMEI and SERIAL numbers)
2) Download the HW-QmOneKeyTool to your PC from here: http://www.mediafire.com/download/um5sqbwp094r2x4/HW-QmOneKeyTool.rar
3) Connect your phone to your PC, open the HW-QmOneKeyTool and enter your 16 digit unlock code into the text box in the first tab of that tool, then click 'ROOT' {This button should actually read 'UNLOCK'}
4) Now that your phone's Bootloader is unlocked, flash TWRP as follows:
INSTALLING TWRP
4a) Download TWRP Recovery from the following site: http://forum.xda-developers.com/asc.../2014-09-22-teamwin-recovery-project-t2885144
4b) Rename TWRP_MT2-L03_RECOVERY.img to TWRP.img
4c) Move TWRP.img to hard drive C, folder: adb
4d) Connect you phone to your PC, open Command Prompt and type: cd C:\adb
4e) After the adb prompt, type: adb devices
4f) With your device serial showing in the Command Prompt, type: fastboot flash recovery c:\adb\TWRP.img
4g) The Command Prompt should now say "waiting for device"
4h) Unplug your phone and reboot into bootloader (power + volume down)
4i) Once in the bootloader make sure it says unlocked then plug your phone in.
4j) The command prompt should say done after 2 seconds and your phone will stay the same.
4k) Unplug your phone and reboot.
INSTALLING SUPERUSER
5) Download BETA-SuperSU-v2.49 to your root: http://download.chainfire.eu/740/SuperSU/BETA-SuperSU-v2.49.zip
6) Boot into TWRP and Flash BETA-SuperSU-v2.49
7) download the TWRP App from Google Play, and let it install BusyBox, then run the SD fix if needed
7) Now you can grant Superuser status to Apps that need root
Is there a backup of the mt02 emui 3.1 boot loader before I go to the twrp?
omnithesis said:
5) Download BETA-SuperSU-v2.49 to your root: http://download.chainfire.eu/740/SuperSU/BETA-SuperSU-v2.49.zip
6) Boot into TWRP and Flash BETA-SuperSU-v2.49
7) download the TWRP App from Google Play, and let it install BusyBox, then run the SD fix if needed
7) Now you can grant Superuser status to Apps that need root
Click to expand...
Click to collapse
Step 7 is required if you don't have an SD card issue?
For anyone that knows, if you root your device, will this cause issues getting OTA updates from Huawei? I registered my IMEI after converting to OEM and loading Lollipop so I would like to ensure I get these updates and can install without issue.
No one?
No
Moody66 said:
No
Click to expand...
Click to collapse
What sort of response is this on a community forum where people try to help each other? Or I thought people helped each other?
I don't get a couple of you members here on the Huawei forums.
Trying to figure out if root causes an issue with OTA updates I believe is a valid question. Thanks for nothing though Moody. You're awesome. :good:
What phone because only a few phones are rooted on lollipop and they have to have unlocked bootloaders.
Sent from my SM-N910V using XDA Free mobile app
TheIgster said:
What sort of response is this on a community forum where people try to help each other? Or I thought people helped each other?
I don't get a couple of you members here on the Huawei forums.
Trying to figure out if root causes an issue with OTA updates I believe is a valid question. Thanks for nothing though Moody. You're awesome. :good:
Click to expand...
Click to collapse
The question was did root affect OTA. The answer is NO. What more do you want.
Moody66 said:
The question was did root affect OTA. The answer is NO. What more do you want.
Click to expand...
Click to collapse
Well, your simple one worded response was misinterpreted. How about that...
And yes, it does effect OTA. I just received B20 and it clearly said to make sure your phone was NOT rooted before upgrading, so obviously it causes an issue with the OTA updates.
Root does not affect OTA. Only if you change system files. Stock recovery and stock system files will not. At worst you will loose root and have to reroot.
---------- Post added at 02:19 PM ---------- Previous post was at 02:14 PM ----------
does root affect OTA....type that into Google. Thousands of posts will tell you the same thing.
Was simply reporting what the update to B20 said. It stated ensure your device is NOT rooted before updating. Perhaps it is just them being careful and ensuring that bugs that may appear on a rooted device would be tougher to diagnose.
Personally I don't see a big need for root with no ROM's available for the HAM.
Because you can't make some changes without root. LCD etc.
Moody66 said:
Because you can't make some changes without root. LCD etc.
Click to expand...
Click to collapse
Yeah, that's true, but to date, I have been pretty happy with the HAM stock. The LP update made this phone a whole new phone. The UI is very nice for an older phone with older specs. Coming from and LG G3 (yes, some would think the HAM is a downgrade), I love the HAM over the G3. The colors are amazing, the screen size is awesome and the new UI for LP is way better than stock LG.
Have a look at a G4. Shame they are expensive
Worth it. But expensive.
rooted alcatel ideal 4060a trying to find out if there is anyway to unlock bootloader and install custom recovery
Developer options
Sent from my Alcatel_4060A using XDA-Developers mobile app
r00t.l3gg3r said:
Developer options
Sent from my Alcatel_4060A using XDA-Developers mobile app
Click to expand...
Click to collapse
i am aware of allow oem unlock, this does not however help me in the process of unlocking and installing custom recovery.
TWRP doesn't appear to be available for the 4060A Ideal yet, if anyone notices they made one in the future please post in this thread.
Did you try the very latest version of KingRoot from Nov 23, 2016: http://forum.xda-developers.com/devdb/project/dl/?id=21707
Please post if you did and if it worked.
EDIT: Yes. KingRoot5 does work but DO NOT USE King-O-Root. King-O-Root will permanently BRICK this phone. But KingRoot5 works.
EDIT2: See this post
I rooted this phone yesterday with the latest KingRoot. I I installed my backup from an LG K7 which I had fully rooted by using an older version of Super su me. Unfortunately I lost that phone. I found this phone on closeout at Kmart and Im trying to get something going on it. It's strange that busybox will install with the new version of KingRoot still installed. Everytime I run super su me (I have tried several different versions) it either crashes or just doesn't do anything. I'm working on it now. Any of you funny guys been able to remove KingRoot and keep root.
Screenshot from this phone. I once rooted an elevate and it came back as a pixi.
The reason why your post is important is people don't want to run KingRoot and find out the hard way it doesn't work, so thanks for posting that.
Yes, removing KingRoot and keeping root would be the golden grail, I'll post here as soon as I come across anyone who's done that. I can't find anyone yet with TWRP or FlashFire-equivalent, let alone root with KingRoot removed...
I read on another thread for this device that they successfully did it with the PC version of KingRoot. I'm leary about putting it on my laptop. I'm hard on phone's and have been messing with them for about a year now so far I haven't bricked a device. I've unlocked a couple of bootloader's. Seems I have the best luck with metro/lg. But I like a challenge and couldn't pass up this phone for the price. First time I got an at&t phone to achieve any kind of root.
I rooted this phone using kingroot then used this post http://forum.xda-developers.com/a310/general/how-to-remove-replace-kingroot-kinguser-t3308989 to switch out kingroot for SuperSU. But you should read the comments in the thread as well for helpful hints, I used link2sd to fully remove kingroot after the script finished.
Bottom line is root and supersu can be achieved fairly easily.
I will give it a try. Ty
arolust said:
I rooted this phone using kingroot then used this post http://forum.xda-developers.com/a310/general/how-to-remove-replace-kingroot-kinguser-t3308989 to switch out kingroot for SuperSU. But you should read the comments in the thread as well for helpful hints, I used link2sd to fully remove kingroot after the script finished.
Bottom line is root and supersu can be achieved fairly easily.
Click to expand...
Click to collapse
Did you remove KingRoot 5?
Would you please post how exactly you removed KingRoot on Alcatel Ideal 4060a..
Thank you.
Dingolo said:
I will give it a try. Ty
Click to expand...
Click to collapse
Did it work for you? I don't see Alcatel mentioned in that thread. I'm curious.
He says it worked for him using link2sd. The original method without link2sd used in the linked thread does not work on Alcatel Ideal 4060a, I tried it.
But his method of using link2sd may work - he says it does.
But how do you exactly do that method? What lines of code do you use, what exactly is the process with link2sd?
That's what we are after, how do you use link2sd with Alcatel Ideal 4060a. I hope he comes back and posts. Otherwise one of us will hopefully figure it out eventually on here...
arolust said:
I rooted this phone using kingroot then used this post http://forum.xda-developers.com/a310/general/how-to-remove-replace-kingroot-kinguser-t3308989 to switch out kingroot for SuperSU. But you should read the comments in the thread as well for helpful hints, I used link2sd to fully remove kingroot after the script finished.
Bottom line is root and supersu can be achieved fairly easily.
Click to expand...
Click to collapse
In the post I linked theres a person who (on the first page) added a code to the script for link2sd.
However, im a bit to lazy to do the research into editing the script, so I think I just ran the script then used link2sd to remove kingroot, then reboot.
Though I had to do this while enduring a constant popup requiring me to press ok over and over.
To be honest though Im a bit fuzzy on the full process because I to had trouble getting the script to work. I might have run the script then rebooted then tried removing kingroot.
I will do this then post full instructions.
I actually know exactly what you are talking about.
But what exactly did you do inside link2sd, can you just post that?
c627627 said:
I will do this then post full instructions.
I actually know exactly what you are talking about.
But what exactly did you do inside link2sd, can you just post that?
Click to expand...
Click to collapse
Thank you for your leadership/initiative :good:
Heyyyyyy, picked up this phone on black friday for $10, well 2 of them. Cant find the device thread tho....im sure its just that im blind...anyone link me up? AND this is the first ATT phone I have read that root can be achieved, I mean by running kingo root, Gonna try it as soon as I find some time...
forgottenhacker said:
Heyyyyyy, picked up this phone on black friday for $10, well 2 of them. Cant find the device thread tho....im sure its just that im blind...anyone link me up? AND this is the first ATT phone I have read that root can be achieved, I mean by running kingo root, Gonna try it as soon as I find some time...
Click to expand...
Click to collapse
Low-end phones don't have their own sections in xda. I doubt there is one for this phone.
goldentequila said:
Low-end phones don't have their own sections in xda. I doubt there is one for this phone.
Click to expand...
Click to collapse
Right, I have attempted to use Kingo root and I was able to remove att crap but I can't grant any other su permissions as I don't get that pop-up box with allow root permissions. I'm not sure how Kingo works but I'm pretty sure there should be some way to grant permissions.
forgottenhacker said:
Right, I have attempted to use Kingo root and I was able to remove att crap but I can't grant any other su permissions as I don't get that pop-up box with allow root permissions. I'm not sure how Kingo works but I'm pretty sure there should be some way to grant permissions.
Click to expand...
Click to collapse
We should wait for c627627 to post an instruction. He was going to try it and report back.
If you are not an H918, H830, or US996 (Unlocked, NOT US Cellular) user, kindly leave this thread, this will not do anything for your device, exchange it if you're so desperate. Thank you.
Note for US996: It's probably easier for you guys just to flash TWRP the normal way and pull your battery then do the factory reset dance to get in!
Team Win Recovery Project 3.0.2-1
Alright, so you guys have probably heard about me working on this project for a week now. Sorry it's been taking so long, there's been so many variables and hurdles to go through!
I don't own the device myself, so it was all done over TeamViewer thanks to @slayerh4x and @Darriousx who stayed around in the #twrp channel on freenode to assist with their devices.
This will allow you to install TWRP and flash SuperSU!
Step 1: Unlocking your bootloader
You will need to unlock your bootloader first. For this you'll probably need LG's drivers.
Windows: http://tool.lime.gdms.lge.com/dn/downloader.dev?fileKey=UW00120120425
Mac: http://tool.lime.gdms.lge.com/dn/downloader.dev?fileKey=UW00320110909
You will also need adb and fastboot. You can download them in a portable small form factor here:
http://forum.xda-developers.com/android/software/host-tools-t3402497
Start by turning on developer options in Settings -> About device -> Software info -> Build number. (tap 7 times until it's enabled)
Now navigate to Settings -> Developer options -> OEM unlock. (turn it on)
Don't ever turn OEM unlock or Developer options off when using a custom ROM or recovery. This could lose to loss of all your data.
For your computer to see ADB, you will need to put the phone in PTP mode (for transferring images). I don't know why this is, a misconfiguration in LG's kernel gadget drivers maybe?
Extract adb and fastboot to a folder on your PC.
Type adb start-server and make sure to check the notification on your phone to accept debugging authorization.
You can reboot into fastboot mode with adb reboot bootloader once authorized.
If it fails to authorize or show the notification on your phone, you may need to try other USB ports.
H918/H830 users only:
To unlock your bootloader, use fastboot oem unlock once the phone boots into fastboot mode.
Warning: This step will wipe all your data and factory reset your phone!
You can check the status of your bootloader lock with the fastboot getvar all command.
ex. (bootloader) unlocked:yes
You should now boot back into your phone (fastboot reboot).
You will probably need to complete the Android setup wizard at this point to get access to ADB again.
US996 users only:
To unlock your bootloader, follow the unlock instructions on LG's site (I can't really help you there):
https://developer.lge.com/resource/mobile/RetrieveBootloader.dev?categoryTypeCode=ANRS
Once you're finished with unlocking your bootloader, continue on to step 2.
Step 2: Running recowvery
You can find the recowvery binaries (you need to download all of these) at:
https://build.nethunter.com/android-tools/dirtycow/arm64/
You're now ready to follow the recowvery installation instructions.
See here: https://github.com/jcadduono/android_external_dirtycow#running (running section)
Bonus: There's also a full write up on that page on how recowvery works if you're into that kind of stuff.
Step 3: Flashing TWRP & Rooting
Notice: There is currently no decryption support, just the same as the LG G5, I'm running into the exact same scenario (unable to start rpmb device).
Due to this, I have disabled hardware decryption in this build to keep it stable. If you wish to have your data work in TWRP, you will need to disable decryption.
If you're coming from the Note 7 or S7, this will be a familiar scenario for you.
Once you've got your permissive shell in adb, you will have access to your partitions via dd.
You should transfer TWRP to your internal storage (name in twrp.img) using MTP, you can also just use adb push. (mentioned here)
Download TWRP: (official builds, V20 is waiting for TWRP 3.1.0 for twrp.me download)
H918: https://build.nethunter.com/test-builds/twrp/lge/twrp-3.0.2-1-h918.img
US996: https://build.nethunter.com/test-builds/twrp/lge/twrp-3.0.2-1-us996.img
H830: https://twrp.me/devices/lgg5h830.html
This step requires that you've used dirtycow to replace /system/bin/run-as with recowvery-run-as. If you've rebooted since doing that, you will need to go back and do that again.
Code:
adb push twrp-3.0.2-x-xxxx.img /sdcard/twrp.img
adb shell
$ run-as exec dd if=/sdcard/twrp.img of=/dev/block/bootdevice/by-name/recovery
"<wait for it to complete>"
$ reboot recovery
You should be inside TWRP now. It will ask you if you want to enable system modifications. You should swipe yes, otherwise your OS will replace TWRP on next boot.
Flash the latest zip from https://build.nethunter.com/android-tools/no-verity-opt-encrypt/ to turn off forced encryption at boot and allow you to boot a modified system. If you're flashing SuperSU.zip, it will also do this for you so this won't be necessary.
Warning: If you don't flash either no-verity-opt-encrypt or SuperSU, you will probably end up in a horrifying never-ending boot loop of "corruption"!
Latest SuperSU: https://download.chainfire.eu/supersu
To disable encryption after flashing SuperSU or the no-verity-opt-encrypt zip, you must use the [Format Data] button on the Wipe page in TWRP. No other options will work.
Back up all your internal storage and apps data that you can to your PC. You can use Titanium Backup with SuperSU before doing this step if you like.
Warning: Using [Format Data] will wipe all your apps and data (including internal storage) off the phone, giving you the out-of-the-box experience of a new phone!
Once this is done, you should be able to backup/restore/use any function of TWRP without any issues.
Flashed SuperSU? You're done! Boot up (it will reboot a few times) and set up your SuperSU Manager to your liking and give this post a thanks!
Step 4: Have fun!
I know a few people have mentioned donating, there is a button right on this post under my username.
Sorry, I don't keep a list as I prefer to keep people's information confidential, but if you do send any money my way, you can request that I mention you at the bottom of this post with any details.
I ask that people please not attach files in this thread, everything required is mentioned in this post, and should be stable in its present state. Thank you.
Thanks for testing on my phone! =]
Does This wipe data on the phone?
justthefacts said:
Does This wipe data on the phone?
Click to expand...
Click to collapse
Unlocking the bootloader does.
jcadduono said:
Alright, so you guys have probably heard about me working on this project for a week now. Sorry it's been taking so long, there's been so many variables and hurdles to go through!
I don't own the device myself, so it was all done over TeamViewer thanks to @slayerh4x and @Darriousx who stayed around in the #twrp channel on freenode to assist with their devices.
Understand that I'm still working on getting TWRP to boot, there seems to be something about the stock kernel sources that doesn't want TWRP to be a part of it.
This will not get you SuperSU or app root access, this is only a root shell allowing you to flash TWRP when it's ready and do other things.
This does however open up some methods of installing SuperSU without TWRP. @Chainfire might have some ideas if he wishes to show up here and stir up some noise.
We do have the ability to do a full ramdisk unpack, edit, repack, and flash within the confines of /data/local while booted into the permissive system using recowvery-applypatch.
This should bring some opportunities, but it's still more sane to just wait for TWRP.
For the instructions on using recowvery, you should read the README.md on the GitHub page:
https://github.com/jcadduono/android_external_dirtycow
You can find the recowvery binaries prebuilt at:
https://build.nethunter.com/android-tools/dirtycow/arm64/
You will need to unlock your bootloader first. For this you'll probably need LG's drivers.
Windows: http://tool.lime.gdms.lge.com/dn/downloader.dev?fileKey=UW00120120425
Mac: http://tool.lime.gdms.lge.com/dn/downloader.dev?fileKey=UW00320110909
You will also need adb and fastboot. You can download them in a portable small form factor here:
http://forum.xda-developers.com/android/software/host-tools-t3402497
Start by turning on developer options in Settings -> About device -> Software info -> Build number. (tap 7 times until it's enabled)
Now navigate to Settings -> Developer options -> OEM unlock. (turn it on)
Don't ever turn OEM unlock or Developer options off when using a custom ROM or recovery. This could lose to loss of all your data.
For your computer to see ADB, you will need to put the phone in PTP mode (for transferring images). I don't know why this is, a misconfiguration in LG's kernel gadget drivers maybe?
Extract adb and fastboot to a folder on your PC.
Type adb start-server and make sure to check the notification on your phone to accept debugging authorization.
You can reboot into fastboot mode with adb reboot bootloader once authorized.
If it fails to authorize or show the notification on your phone, you may need to try other USB ports.
To unlock your bootloader, use fastboot oem unlock once the phone boots into fastboot mode.
Warning: This step will wipe all your data and factory reset your phone!
You can check the status of your bootloader lock with the fastboot getvar all command.
ex. (bootloader) unlocked:yes
You should now boot back into your phone (fastboot reboot).
You're now ready to follow the recowvery installation instructions.
See here: https://github.com/jcadduono/android_external_dirtycow
There's also a full write up on that page on how recowvery works if you're into that kind of stuff.
I probably need to proof read it though, I'm really tired.
Click to expand...
Click to collapse
Thank you for taking the time to begin with the first step to develop on this device! (although i will have to do a replacement tomorrow for 2 defects that emerged on my phone) I always had in mind that this device had only a 50% of chances to get rooted, and that it might actually never get rooted . But now chances have increased even more thanks to your hard work. and also thanks to the others you previously mentioned. Let us see if Chainfire takes an interest on adding the final details :good:
I've got ADB working fine, but get nothing with fastboot. Just a blank line when I type 'fastboot devices'. Tried 3 different USB ports also. Windows 10 x64.
I did grab the ADB/fastboot files linked in the first post, but the older files I had don't work either, and they have no issues with my Nexus 7 2013 and HTC 10.
Promising stuff ,I just upgraded to this phone yesterday ,and was hoping to eventually get custom roms on it
Sent from my VS995 using Tapatalk
---------- Post added at 03:24 PM ---------- Previous post was at 03:21 PM ----------
Quick question should I wait or take the ota updates?
Sent from my VS995 using Tapatalk
So Idk what to do or how to get the file to flash it.. Any help?
mrtruckincowboy said:
Promising stuff ,I just upgraded to this phone yesterday ,and was hoping to eventually get custom roms on it
Sent from my VS995 using Tapatalk
---------- Post added at 03:24 PM ---------- Previous post was at 03:21 PM ----------
Quick question should I wait or take the ota updates?
Sent from my VS995 using Tapatalk
Click to expand...
Click to collapse
My advice? Never, ever take an update until the developers say that they are sure they can exploit it. From what I can see, this process uses the "dirty cow" exploit which will assuredly be fixed on the next security update.
---------- Post added at 05:11 PM ---------- Previous post was at 05:10 PM ----------
bambam126 said:
So Idk what to do or how to get the file to flash it.. Any help?
Click to expand...
Click to collapse
Why not wait until they can get full root and TWRP? As I see it, this process is to help other developers and people that know what they're doing refine and advance the move to full root. I don't think it's quite ready for prime time yet. It does nothing but get the foot in the door for rooting.
---------- Post added at 05:17 PM ---------- Previous post was at 05:11 PM ----------
And, we're off to the races. Let the "I bricked my phone" threads begin!
douger1957 said:
[/COLOR]And, we're off to the races. Let the "I bricked my phone" threads begin!
Click to expand...
Click to collapse
LOL! YASSSSSS i can imagine that already. There will be some who will get it hard bricked .
---------- Post added at 05:39 PM ---------- Previous post was at 05:34 PM ----------
mrtruckincowboy said:
Promising stuff ,I just upgraded to this phone yesterday ,and was hoping to eventually get custom roms on it
Sent from my VS995 using Tapatalk
---------- Post added at 03:24 PM ---------- Previous post was at 03:21 PM ----------
Quick question should I wait or take the ota updates?
Sent from my VS995 using Tapatalk
Click to expand...
Click to collapse
Isn't your model the verizon model? If it is... I havent heard any Verizon user to have unlocked the bootloader for their LG V20's. Not to be a downer, but the methods on this thread are only possible for the H918 (Tmobile variant). unless someone found a way to unlock Verizon's bootloader.
joseguillen1994 said:
LOL! YASSSSSS i can imagine that already. There will be some who will get it hard bricked .
---------- Post added at 05:39 PM ---------- Previous post was at 05:34 PM ----------
Isn't your model the verizon model? If it is... I havent heard any Verizon user to have unlocked the bootloader for their LG V20's. Not to be a downer, but the methods on this thread are only possible for the H918 (Tmobile variant). unless someone found a way to unlock Verizon's bootloader.
Click to expand...
Click to collapse
They discuss unlocking in the first post so I'm optimistic. Even if not there has been custom stuff done around locked bootloader.I came from s4 and that was possible with the loki method so im optimistic
Sent from my VS995 using Tapatalk
mrtruckincowboy said:
They discuss unlocking in the first post so I'm optimistic. Even if not there has been custom stuff done around locked bootloader.I came from s4 and that was possible with the loki method so im optimistic
Sent from my VS995 using Tapatalk
Click to expand...
Click to collapse
Oh. Great to know. I hope they manage to do something with the verizon variants, in fact, with all the variants . Maybe after that they will have more interest on the device
jcadduono said:
alright, so you guys have probably heard about me working on this project for a week now. Sorry it's been taking so long, there's been so many variables and hurdles to go through!
I don't own the device myself, so it was all done over teamviewer thanks to @slayerh4x and @darriousx who stayed around in the #twrp channel on freenode to assist with their devices.
Understand that i'm still working on getting twrp to boot, there seems to be something about the stock kernel sources that doesn't want twrp to be a part of it.
this will not get you supersu or app root access, this is only a root shell allowing you to flash twrp when it's ready and do other things.
this does however open up some methods of installing supersu without twrp. @chainfire might have some ideas if he wishes to show up here and stir up some noise.
we do have the ability to do a full ramdisk unpack, edit, repack, and flash within the confines of /data/local while booted into the permissive system using recowvery-applypatch.
This should bring some opportunities, but it's still more sane to just wait for twrp.
For the instructions on using recowvery, you should read the readme.md on the github page:
https://github.com/jcadduono/android_external_dirtycow
you can find the recowvery binaries prebuilt at:
https://build.nethunter.com/android-tools/dirtycow/arm64/
you will need to unlock your bootloader first. For this you'll probably need lg's drivers.
Windows: http://tool.lime.gdms.lge.com/dn/downloader.dev?filekey=uw00120120425
mac: http://tool.lime.gdms.lge.com/dn/downloader.dev?filekey=uw00320110909
you will also need adb and fastboot. You can download them in a portable small form factor here:
http://forum.xda-developers.com/android/software/host-tools-t3402497
start by turning on developer options in settings -> about device -> software info -> build number. (tap 7 times until it's enabled)
now navigate to settings -> developer options -> oem unlock. (turn it on)
don't ever turn oem unlock or developer options off when using a custom rom or recovery. This could lose to loss of all your data.
For your computer to see adb, you will need to put the phone in ptp mode (for transferring images). I don't know why this is, a misconfiguration in lg's kernel gadget drivers maybe?
Extract adb and fastboot to a folder on your pc.
Type adb start-server and make sure to check the notification on your phone to accept debugging authorization.
You can reboot into fastboot mode with adb reboot bootloader once authorized.
If it fails to authorize or show the notification on your phone, you may need to try other usb ports.
To unlock your bootloader, use fastboot oem unlock once the phone boots into fastboot mode.
warning: This step will wipe all your data and factory reset your phone!
you can check the status of your bootloader lock with the fastboot getvar all command.
Ex. (bootloader) unlocked:yes
you should now boot back into your phone (fastboot reboot).
You're now ready to follow the recowvery installation instructions.
See here: https://github.com/jcadduono/android_external_dirtycow
there's also a full write up on that page on how recowvery works if you're into that kind of stuff.
I probably need to proof read it though, i'm really tired.
Click to expand...
Click to collapse
you are the man !!!!!!!!!!!!!!!!!!!!!!!
joseguillen1994 said:
LOL! YASSSSSS i can imagine that already. There will be some who will get it hard bricked .
---------- Post added at 05:39 PM ---------- Previous post was at 05:34 PM ----------
Isn't your model the verizon model? If it is... I havent heard any Verizon user to have unlocked the bootloader for their LG V20's. Not to be a downer, but the methods on this thread are only possible for the H918 (Tmobile variant). unless someone found a way to unlock Verizon's bootloader.
Click to expand...
Click to collapse
For me, there's a certain amount of education that needs to be tackled before you start messing with a phone. I have never had a LG smartphone before, but rather quickly discovered that LGUP is not ODIN, and that yes, you can hard brick a LG doing stuff that a Samsung will shrug off.
Too many people are impatient and won't let the developers come out with a product that is relatively easy to use. Too many people won't take the time to learn what they're doing and how to fix their mistakes. Too many people won't bother to read and follow simple instructions, and too many people think their experience on other phones will play out here. The only thing this phone has in common with others is the basic Android. It's what LG has put on top that has given the developers a hard time. That, and Nougat seems to be a new beast to be slain.
douger1957 said:
For me, there's a certain amount of education that needs to be tackled before you start messing with a phone. I have never had a LG smartphone before, but rather quickly discovered that LGUP is not ODIN, and that yes, you can hard brick a LG doing stuff that a Samsung will shrug off.
Too many people are impatient and won't let the developers come out with a product that is relatively easy to use. Too many people won't take the time to learn what they're doing and how to fix their mistakes. Too many people won't bother to read and follow simple instructions, and too many people think their experience on other phones will play out here. The only thing this phone has in common with others is the basic Android. It's what LG has put on top that has given the developers a hard time. That, and Nougat seems to be a new beast to be slain.
Click to expand...
Click to collapse
yup! i couldn't have written it better hahaha. But it is bound to happen for some people that will not pay careful attention. I mena, im not an expert, im maybe a little more than a noob now since i have been dealing with this for quite some time, and that is why i just started my C++ class in order to reach at least a good-to-go level of understanding.
As this method does not ever mount your system r/w, it won't brick your system. Since it also can't provide you with real root access until you reboot recovery into a permissive system, you risk no chances of bricking your device if this is not for it, because if your device is locked, the recovery will refuse to boot and be replaced with stock again 2 seconds later.
Unfortunately I have not yet disabled verity in the fstab, so if a H918 user uses their new root shell to remount system as r/w then they will be bricked. I'll see if I can find a decent way to do this...probably with sed.
But yeah. You're safe if your bootloader is locked.
jcadduono said:
As this method does not ever mount your system r/w, it won't brick your system. Since it also can't provide you with real root access until you reboot recovery into a permissive system, you risk no chances of bricking your device if this is not for it, because if your device is locked, the recovery will refuse to boot and be replaced with stock again 2 seconds later.
Unfortunately I have not yet disabled verity in the fstab, so if a V20 user uses their new root shell to remount system as r/w then they will be bricked. I'll see if I can find a decent way to do this...probably with sed.
But yeah. You're safe if your bootloader is locked.
Click to expand...
Click to collapse
Locked or unlock
jcadduono said:
As this method does not ever mount your system r/w, it won't brick your system. Since it also can't provide you with real root access until you reboot recovery into a permissive system, you risk no chances of bricking your device if this is not for it, because if your device is locked, the recovery will refuse to boot and be replaced with stock again 2 seconds later.
Unfortunately I have not yet disabled verity in the fstab, so if a V20 user uses their new root shell to remount system as r/w then they will be bricked. I'll see if I can find a decent way to do this...probably with sed.
But yeah. You're safe if your bootloader is locked.
Click to expand...
Click to collapse
Oh, ye of little faith. Where there's a will, there's a way.
Chainfire just tweeted:
Just installed SuperSU on a V20, based on @jcadduono 's initial work. Good times.
Can this method be used on other devices?
Sent from my R1HD(ZenUI) via Tapatalk