Related
I just pushed the new 4.2 update via adb,
I then tried re-rooting as I lost root in the project.
I used WugFreshs at first, which said successful. I tried root check and titanium backup which both said no root access.
I then tried mikes toolkit and chose root and install busybox, all that wen through great and said successful, so I retried Tibackup and rootchecker again, both were denied root access.
This time round, rootcheck said "System Running Slow" whilst checking for root access.
What should I do?
Re-boot into recovery and clear cache etc?
Factory reset?
Both?
For some reason superuser is installed not supersu if that makes a difference?
Any help appreciated.
Wilks3y said:
I just pushed the new 4.2 update via adb,
I then tried re-rooting as I lost root in the project.
I used WugFreshs at first, which said successful. I tried root check and titanium backup which both said no root access.
I then tried mikes toolkit and chose root and install busybox, all that wen through great and said successful, so I retried Tibackup and rootchecker again, both were denied root access.
This time round, rootcheck said "System Running Slow" whilst checking for root access.
What should I do?
Re-boot into recovery and clear cache etc?
Factory reset?
Both?
For some reason superuser is installed not supersu if that makes a difference?
Any help appreciated.
Click to expand...
Click to collapse
I apply the update by doing fresh install:
-always backup your data
Then I use wug's nexus root toolkit:
-flash stock + unroot 4.1.2 jzo54k
-flash zip stock + unroot 4.2 jop40c
-change the model type to "NAKASI: Android *.*.* Any build"
-apply root
gesitkumara said:
I apply the update by doing fresh install:
-always backup your data
Then I use wug's nexus root toolkit:
-flash stock + unroot 4.1.2 jzo54k
-flash zip stock + unroot 4.2 jop40c
-change the model type to "NAKASI: Android *.*.* Any build"
-apply root
Click to expand...
Click to collapse
I applied the update over the top of 4.1.2, wiped cache and then restarted.
I then used Wug's toolkit to root, which didn't work.
So I tried Mikes, which also didnt work.
Both report the Root as being succesful, but they arent.
If I change the model to all types on Wug's, would that make a difference?
Is it worth trying a manual root?
I use the Google Nexus 7 Toolkit which was great in fixing the problems after upgrade. Flashing the previous version bootloader (I think that is what it was) solved the root problem. The hints and guidance in this application are great and have always solved my problems. No offence meant to Wug here, I just find the other application suits me better.
Sent using Tapatalk 2
Waxwrong said:
I use the Google Nexus 7 Toolkit which was great in fixing the problems after upgrade. Flashing the previous version bootloader (I think that is what it was) solved the root problem. The hints and guidance in this application are great and have always solved my problems. No offence meant to Wug here, I just find the other application suits me better.
Sent using Tapatalk 2
Click to expand...
Click to collapse
As already said, both Toolkits have been attempted and both report that its rooted, but my device tells me otherwize, as do Titanium Backup.
Can someone just give me a step by step for what I should do to gain Root again?!
Wilks3y said:
As already said, both Toolkits have been attempted and both report that its rooted, but my device tells me otherwize, as do Titanium Backup.
Can someone just give me a step by step for what I should do to gain Root again?!
Click to expand...
Click to collapse
Hi, are you using the fully updated version of Toolkit (updated to include the 4.2 stuff. When I did mine I was told to go ahead but if it didn't work the next step was to flash the 4.1 bootloader? as it was compatible with 4.2
The root with the 4.2 bootloader didn't give me root so I flashed the 4.1 bootloader and rooted again. This was successful for me. The Toolkit application gives you step by step instructions as you request as long as it is updated to do 4.2 and follow the advice you should have no problem.
I don't think you can do the full updates in the application unless you are a donater. If I remember correctly you cannot update the application unless you use the donater version. The update for 4.2 came out at almost the same time as 4.2 was being pushed to devices.
You sound cluey enough to know you must use USB debugging but many users don't realise this or the tapping on the build trick to get the developer options available so you can select USB debugging.
Sent using Tapatalk 2
Waxwrong said:
Hi, are you using the fully updated version of Toolkit (updated to include the 4.2 stuff. When I did mine I was told to go ahead but if it didn't work the next step was to flash the 4.1 bootloader? as it was compatible with 4.2
The root with the 4.2 bootloader didn't give me root so I flashed the 4.1 bootloader and rooted again. This was successful for me. The Toolkit application gives you step by step instructions as you request as long as it is updated to do 4.2 and follow the advice you should have no problem.
I don't think you can do the full updates in the application unless you are a donater. If I remember correctly you cannot update the application donate version. The update for 4.2 came out at almost the same time as 4.2 was being pushed to devices.
You sound cluey enough to know you must use USB debugging but many users don't realise this or the tapping on the build trick to get the developer options available so you can select USB debugging.
Sent using Tapatalk 2
Click to expand...
Click to collapse
Hey mate, thanks for your reply !
I downloaded both ToolKits yesterday, so I'm guessing they are the newly updated ones?
Yes my tablet has usb debugging enabled, and is put into the Camera Mode.
I will have another go tonight, and try a different way, including using the "All Models" choice you mentioned.
If this doens't work, whereabouts in the ToolKit(Wug's) if the option to downgrade HBOOT in order to try the Root method you attempted which was successful.
Again, thanks mate !
Wilks3y said:
Hey mate, thanks for your reply !
I downloaded both ToolKits yesterday, so I'm guessing they are the newly updated ones?
Yes my tablet has usb debugging enabled, and is put into the Camera Mode.
I will have another go tonight, and try a different way, including using the "All Models" choice you mentioned.
If this doens't work, whereabouts in the ToolKit(Wug's) if the option to downgrade HBOOT in order to try the Root method you attempted which was successful.
Again, thanks mate !
Click to expand...
Click to collapse
I don't use Rug's Toolkit but Mike's Toolkit (only because it is easier to follow and use because it tells you what to do at all stages). You can see if it is updated by checking whether it has functions for 4.2 - I always use it for flashing the latest roms as well as the unlocking, root, recovery, etc, all of which the Toolkit guides you through. It even downloads the roms for you.
My only question is why did you put it in camera mode, change it back.
Sent using Tapatalk 2
Just install the 4.2 that is already Stock rooted, de-odexed apps.
Install the ROM as already Stock rooted, de-odexed apps.
Here is the link for the download: http://www.scottsroms.com/downloads.php?do=file&id=288
Thanks to Scott's post http://forum.xda-developers.com/showthread.php?t=1991157
Okay well, I have a GS4 GT-I 9500 on android 4.2.2 KitKat.
I updated it from 4.3 to this version when I was in Russia.
And lately, I heard of rooting and stuff so I'm a total newbie!
So, I jumped for some tutorials on the web and I learned about Pc Odin, chainfire root, and CWM recovery.
I used first a method wich involved using odin to push the CF auto-root with PDA into the phone while on download mode. I got only 'reset' but no 'pass' would show. And no supersu icon will appear in my app drawer. After lots of tires and multiple Odin version changes I succeeded in having 'pass', but nope, "no proper root access"(via root checker).
So then I used Odin to put CWM recovery in the phone and enter it to "install zip from sd card" and installed the CF auto-root . zip. Lines start to flow and ends with a "Done". Then I go back to reboot and it says something like do you want to fix root located in... before root? I tried "yes - fix root" and "no - just reboot" And both didn't fix it for me.
Finally, I tried motochopper.zip that have some files wich needed developer mode to be enabled and USB debugging. I only had to hit enter in run.bat and it starts the rooting process. But immediately says failure and gives an error like "failure supersu already available"...
I would really appreciate any help. I need my device rooted soon, please. Thanks in advance.
P.S: While on download mode, it shows that my phone status is modified. I won't mind having to force a factory reset if it'll fix something.
Thanks a lot!
I wonder if my post is visible to others, I really need my phone rooted
nicolaz_i said:
I wonder if my post is visible to others, I really need my phone rooted
Click to expand...
Click to collapse
there is an app called framaroot, available by searching xda or google, usually works for rooting samsung phones.
there is also a pc app called Vroot that works almost like magic, every device i plug in is rooted within 2 minutes, even without drivers!
Nope...
Kobro said:
there is an app called framaroot, available by searching xda or google, usually works for rooting samsung phones.
there is also a pc app called Vroot that works almost like magic, every device i plug in is rooted within 2 minutes, even without drivers!
Click to expand...
Click to collapse
Framaroot doesn't support the GT-i9500 model. I also tried Vroot and it didn't work. I'm really sure it's something from the phone...
Sorry bro, that didn't help
nicolaz_i said:
Okay well, I have a GS4 GT-I 9500 on android 4.2.2 KitKat.
I updated it from 4.3 to this version when I was in Russia.
And lately, I heard of rooting and stuff so I'm a total newbie!
So, I jumped for some tutorials on the web and I learned about Pc Odin, chainfire root, and CWM recovery.
I used first a method wich involved using odin to push the CF auto-root with PDA into the phone while on download mode. I got only 'reset' but no 'pass' would show. And no supersu icon will appear in my app drawer. After lots of tires and multiple Odin version changes I succeeded in having 'pass', but nope, "no proper root access"(via root checker).
So then I used Odin to put CWM recovery in the phone and enter it to "install zip from sd card" and installed the CF auto-root . zip. Lines start to flow and ends with a "Done". Then I go back to reboot and it says something like do you want to fix root located in... before root? I tried "yes - fix root" and "no - just reboot" And both didn't fix it for me.
Finally, I tried motochopper.zip that have some files wich needed developer mode to be enabled and USB debugging. I only had to hit enter in run.bat and it starts the rooting process. But immediately says failure and gives an error like "failure supersu already available"...
I would really appreciate any help. I need my device rooted soon, please. Thanks in advance.
P.S: While on download mode, it shows that my phone status is modified. I won't mind having to force a factory reset if it'll fix something.
Thanks a lot!
Click to expand...
Click to collapse
If you have Clockwork Mod Recovery on your phone now, find a Superuse.zip install package and flash that in recovery. It will work like a charm.
easy steps !
download & flash touch philz Recovery via Odin
then go to recovery and select re-root system > > yes apply ( Supersu )
Then download supersu from google play and he will ask you how do you want to update binary ,just click normal
YEAH!! Finally rooted
RubbaBand said:
easy steps !
download & flash touch philz Recovery via Odin
then go to recovery and select re-root system > > yes apply ( Supersu )
Then download supersu from google play and he will ask you how do you want to update binary ,just click normal
Click to expand...
Click to collapse
You sir, is the best person I ever known. Thanks a lot for saving my life. I swear I almost tried everything on the internet to root my phone, but none really worked. Please stay awesome. Bye.
nicolaz_i said:
You sir, is the best person I ever known. Thanks a lot for saving my life. I swear I almost tried everything on the internet to root my phone, but none really worked. Please stay awesome. Bye.
Click to expand...
Click to collapse
anytime bro, if you have any questions or any problems send me PM
RubbaBand said:
easy steps !
download & flash touch philz Recovery via Odin
then go to recovery and select re-root system > > yes apply ( Supersu )
Then download supersu from google play and he will ask you how do you want to update binary ,just click normal
Click to expand...
Click to collapse
dont you have to find the root pakage, or does philz do root without a root package?
Kobro said:
dont you have to find the root pakage, or does philz do root without a root package?
Click to expand...
Click to collapse
No he doesnt need
RubbaBand said:
No he doesnt need
Click to expand...
Click to collapse
so philz can root without any other downloads???
i didnt know that.
@Kobro
you need just to download SuperSu from google play
thats all
RubbaBand said:
@Kobro
you need just to download SuperSu from google play
thats all
Click to expand...
Click to collapse
nice, now , just gotta find philz for my phone...
Kobro said:
nice, now , just gotta find philz for my phone...
Click to expand...
Click to collapse
k bro
This is merely a guide, I do not take credit for any methods or apps listed below. I am not a developer. The great people working on these apps and methods deserve all the credit and your donations, so please disparse accordingly.
BIG THANKS to @iKrYpToNiTe, @jcase, @geohot who worked on these apps. Also thanks to @mschumacher69 for some constructive discussions.
YOU AGREE BY PERFORMING ANY OF THE ACTIONS BELOW THAT I AM NOT RESPONSIBLE IF YOU BRICK YOUR PHONE. EVERY DISCLAIMER STATED ON THE LINKS PROVIDED IS STILL 100% VALID.
A RECAP OF THOSE DISCLAIMERS IS THAT YOU WILL VOID YOUR PHONE'S WARRANTY AND NOONE ELSE BUT YOURSELF ARE RESPONSIBLE IF YOU DAMAGE YOUR PHONE!!!
I decided to compile a root guide for the Cricket variant of the Moto G falcon xt1032 running 4.4.2 (may work on other variants as well, not sure). I obtained full, permanent root with philz touch recovery (but it would work for any other recovery you may choose to use).
THIS METHOD DOES NOT REQUIRE A COMPUTER/PC/MAC/LINUX USB CONNECTION
1. Enable USB debugging
2. From the setting tab "security". Check the " unknown sources" box, so you can install apk outside of play store
3. In addition to all things below, you will need a file explorer. I find es file explorer to be the golden standard, but your preferred file manager will do
4. This Link below is for you to install towelpieroot.apk
http://forum.xda-developers.com/moto-x/themes-apps/root-towelpieroot-motorola-devices-t2825059.
The version 1.2 supports the xt1032 falcon. Big thanks to @iKrYpToNiTe for adding support for the Moto G! You will need this temporary or "tethered" root before you go to the next step, which is unlocking the bootloader with this app called Sunshine (link to thread given below). Towelpieroot is buggy at times, but if it doesn't work the first time, try a few more. It WILL work.
5. http://theroot.ninja/
Note that running Sunshine is not free, but the $25 is well spent! Just so you know, Sunshine will NOT charge you if the process fails.
6. After the bootloader is unlocked, UNINSTALL towelpieroot. This is important in order for you to proceed to the next step.
7. Once you unlock the bootloader, you need to run towelroot (link below)
https://towelroot.com/
This step will grant you full, permanent root. Tap on the "welcome to towel root V3" three times, then you should see a box where you can modify the modstring. By experimentation and trial, I found the modstring 1337 0 0 0 4 0 to be the one. Click "Make it ra1n" and you should have permanent, full root privileges!!!
8. Download your favorite root checker to verify root access!
9. Go to play store and install SuperSU, and do any necessary updates.
10. Go to play store and install busybox and do all necessary binary updates.
11. Go to play store and download a terminal emulator. This will aid you in flashing your recovery.
12. My personal preference is Philz Touch recovery, but I think it it fair to assume that any compatible recovery of your choice is appropriate to flash with this method (link below)
http://forum.xda-developers.com/showthread.php?t=2639583
Download the latest .IMG from the OP
13. Before you flash you may want to back up your stock recovery.
Open the terminal emulator.
(do not include quote marks, only what's inside them, including spaces)
Type "su" and hit the ENTER key
This will get you superuser access
Type "dd=if/dev/block/mmcblk0p32 of=/sdcard/stock-recovery-backup.img"
This will create a backup of your current STOCK recovery.
14. Now ,using your file manager, go to the philz touch recovery .img file you just downloaded and rename it into "recovery.img", then move it to the sdcard folder (storage root folder)
Note: there you should also see the backup recovery file "stock-recovery-backup.img" you just created
15. Open the terminal emulator
Type "su" to gain superuser access
Type "dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p32
16. THAT'S IT!!!
Verify by powering off your phone, hold volume down and power button for 5 seconds, select recovery and you should have Philz touch recovery in your phone.
NEXT LOGICAL STEP WOULD BE TO BACKUP YOUR STOCK FIRMWARE IMMEDIATELY!
BE MINDFUL WHEN YOU HOP BETWEEN ROMS THIS PHONE HAS ONLY AN INTERNAL STORAGE, SO BE CAREFUL WHAT YOU FORMAT
Other than that, whoohoo!!!!
NOTE: ACCORDING TO SOME DEVS I HAVE COME ACROSS ARE TELLING ME STEP 7 IS NOT NECESSARY. YOU CAN TRY SKIPPING IT. UNFORTUNATELY MY BOOTLOADER AND ROOT ARE IN EFFECT, THEREFORE I CANNOT VERIFY THIS. YOU COULD TRY[emoji3]
Please, when you need app-specific support, you may get better answers in the respective forums, but don't be discouraged posting questions here. It took me great effort finding a way to root without a PC, and although i am not a developer, I have stumbled in enough obstacles to be of some assistance
XT 1032 Falcon from Cricket GSM 4.4.2 stock
Once you unlock ur bootloader, u don't need exploit apps such as towelroot to gain root, all you need is a custom recovery such as twrp. Once you flash it and reboot from it, it will tell you that you're not rooted, do u want to flash supersu to gain root access? Swipe to intall supersu and u're rooted...
mschumacher69 said:
Once you unlock ur bootloader, u don't need exploit apps such as towelroot to gain root, all you need is a custom recovery such as twrp. Once you flash it and reboot from it, it will tell you that you're not rooted, do u want to flash supersu to gain root access? Swipe to intall supersu and u're rooted...
Click to expand...
Click to collapse
Yes that is true if you wanna fastboot via USB, which means connecting the phone to a PC. I was under the impression that I could not flash a custom recovery from the stock one. I have been struggling to gain root because of non-access to a computer. It is a little more lengthy but I find this to be the only no PC guide around, since I've been looking for one for 4 months now. And most certainly I would not be able to flash a recovery from the terminal emulator if I did not have su.
Towelpieroot only gives a tethered, temp root with no r/w privileges to system. It would make it impossible to flash a recovery from the terminal without gaining full root. This is why you need to run the original towelroot with the modified modstring.
REMINDER: THIS METHOD DOES NOT REQUIRE A USB CONNECTION WITH A COMPUTET. ITS ALL DONE ON THE PHONE.
XT 1032 Falcon from Cricket GSM 4.4.2 stock
Thanks for the guide. I ran towelroot 1.2 and it crashes my phone ;( and v3 says it's not compatible
lmf said:
Thanks for the guide. I ran towelroot 1.2 and it crashes my phone ;( and v3 says it's not compatible
Click to expand...
Click to collapse
Towelpieroot is buggy (the dev states in his post). I had to try the process numerous times. What i think may work (or may have worked). Is you have to make sure that before running towelpieroot again youbhave to clear it from the recents. What i have done was clear it from recents, uninstall. Reboot phone. Install and run again. Once you get temp root you can continue the process.
On towelroot v3. It will say your device is not supported. Tap on "welcome to towelroot v3" twxt three times and a modstring modification box will appear showing numbers. Input the modstring posted above in the OP "1337 0 0 0 4 0" (with the spaces). Then it will give you root
Note: According to some devs i have come across are telling me step 7 is not necessary. You can try skipping it. Unfortunately my bootloader and root are in effect, therefore i cannot verify this. You could try. [emoji3]
THIS NOTE ADDED TO THE OP AS WELL
BBobby said:
Note: According to some devs i have come across are telling me step 7 is not necessary. You can try skipping it. Unfortunately my bootloader and root are in effect, therefore i cannot verify this. You could try. [emoji3]
THIS NOTE ADDED TO THE OP AS WELL
Click to expand...
Click to collapse
It is definitely unnecessary. Once you unlock ur bootloader, all you need to do is flash custom recovery and it would flash supersu for u which would give u root...
Towelroot uses an exploit to root, exploits are only needed on a locked bootloader. Unlocked bootloaders don't need exploits to be rooted...
mschumacher69 said:
It is definitely unnecessary. Once you unlock ur bootloader, all you need to do is flash custom recovery and it would flash supersu for u which would give u root...
Towelroot uses an exploit to root, exploits are only needed on a locked bootloader. Unlocked bootloaders don't need exploits to be rooted...
Click to expand...
Click to collapse
Would it be OK to download super su from play store directly?
BBobby said:
Would it be OK to download super su from play store directly?
Click to expand...
Click to collapse
You wouldn't be able to download it directly. Once you unlock the bootloader, you flash custom recovery such as twrp, then when u reboot from twrp (or any other custom recovery), it would tell you that you're not rooted, would you like to install supersu? Swipe to install it and you're rooted. Then you can update supersu from the play store.
mschumacher69 said:
You wouldn't be able to download it directly. Once you unlock the bootloader, you flash custom recovery such as twrp, then when u reboot from twrp (or any other custom recovery), it would tell you that you're not rooted, would you like to install supersu? Swipe to install it and you're rooted. Then you can update supersu from the play store.
Click to expand...
Click to collapse
But my questions continue to be:
1. How do I flash a custom recovery from the stock one?. Will the terminal commands still be effective? Or an .IMG file flasher app like rashr will be effective without initial root?
2. Is it bad to just run towelroot V3 and gain permanent root in less than a minute, then just download super su and continue?
I just posted what has worked for me. I am thankful for your input and persistent suggestions. But like I said it has worked for me the way it is described in the OP. I just don't think it is necessary to fix what is not broken.
BBobby said:
But my questions continue to be:
1. How do I flash a custom recovery from the stock one?. Will the terminal commands still be effective? Or an .IMG file flasher app like rashr will be effective without initial root?
2. Is it bad to just run towelroot V3 and gain permanent root in less than a minute, then just download super su and continue?
I just posted what has worked for me. I am thankful for your input and persistent suggestions. But like I said it has worked for me the way it is described in the OP. I just don't think it is necessary to fix what is not broken.
Click to expand...
Click to collapse
1. Yes you can flash a custom recovery via a terminal emulator, but you would need root to be able to do it without using a PC.
2. I wouldn't say bad, it's rather unnecessary especially that it uses an exploit to gain root. You wouldn't know what unnecessary changes it makes to your system in order to be able to gain root.
mschumacher69 said:
1. Yes you can flash a custom recovery via a terminal emulator, but you would need root to be able to do it without using a PC.
2. I wouldn't say bad, it's rather unnecessary especially that it uses an exploit to gain root. You wouldn't know what unnecessary changes it makes to your system in order to be able to gain root.
Click to expand...
Click to collapse
The guide is about NOT using a PC. Its in the topic, in the OP, in my posts... Then yes, its necessary to gain some sort of root (permanent, in the towelroot case) to run the terminal emulator.
Two birds with one shot.
Moto G (XT 1032) from Cricket. Unlocked Bootloader, Rooted, Stock ROM (4.4.2) with Xposed tweaks
BBobby said:
The guide is about NOT using a PC. Its in the topic, in the OP, in my posts... Then yes, its necessary to gain some sort of root (permanent, in the towelroot case) to run the terminal emulator.
Two birds with one shot.
Moto G (XT 1032) from Cricket. Unlocked Bootloader, Rooted, Stock ROM (4.4.2) with Xposed tweaks
Click to expand...
Click to collapse
Fair enough, but I don't see why you wouldn't want to use a PC. It's safer if u use a PC because u wouldn't be using any exploits...
mschumacher69 said:
Fair enough, but I don't see why you wouldn't want to use a PC. It's safer if u use a PC because u wouldn't be using any exploits...
Click to expand...
Click to collapse
Do you even read the posts? I have not had a PC or access to one (yes, people like me exist). I have looked for months on end and once I came across towelpieroot it all became possible. Then jcase released sunshine and that all put it together in a working method. This is the collection of hour of searching. If anyone like me does not have PC access it is still possible. But I wouldn't want others to have to go through that frustration
Moto G (XT 1032) from Cricket. Unlocked Bootloader, Rooted, Stock ROM (4.4.2) with Xposed tweaks
Thanks for the useful guide.
Once you do all of this what can be done . Does this mean the device is carrier free or just allows to install any variant of android on it.
Also even after doing all of these things how one can activate it on a different network than it is bought to be used on.
Sorry i am newbie to flashing software.
Thanks
Mars
This is a guide to root this device. That means you have access to the operating system files. By getting this access it allows you to modify the system in many ways. It also allows you to install custom ROMs. Gaining root has so many uses I cannot list here.
But no, this is not a carrier/SIM unlock.
How about the 4.4.4 cricket XT1046 seems to be impossible at this point?
When I get to the step on gaining temporary root it just keeps loading and loading and it never gives me root.. Like I went on and off multiple times and it still won't work
BBobby said:
But my questions continue to be:
1. How do I flash a custom recovery from the stock one?. Will the terminal commands still be effective? Or an .IMG file flasher app like rashr will be effective without initial root?
Click to expand...
Click to collapse
Rashr needs root to flash images and zips
Edit: I didn't saw that you already have been answered
Hello everyone. I have successfully rooted Lollipop 5.0.2 for VERIZON LG PAD 8.3 VK810 without downgrading.
PREREQUISITES
-Updated drivers installed
-turned on usb debugging
- Supersu installed from playstore
STEPS
More specifically HERE
Now the English version stands at 2.2.1 while Chinese is still at 1.85
2.Run iRoot app from PC. Wait till it is complete. You will have root with some system cleaner app with King user.
IF ABOVE FAILS
1.Install KingoRoot as well
http://www.kingoapp.com/
2.After running iRoot, run KingoRoot. Wait about 5-8 minutes as it would go on forever. Close it afterwards.
3. Run Iroot and Kingoroot together. Wait till it is restarted and you acquire root with KingUser
3. Download supersu from here and install its apk. Upgrade binaries and uninstall kinguser.SUPERSU BETA 2.49
The apk file is located in the zip
If binary upgrade fails, try2.48 version. Link given below.
You should be rooted with Supersu.
If it fails to upgrade binaries.
.Flash aboot 4.2.2 to flash twrp 2.7.0.1. Instructions given Here on my guide
.Update Twrp to 2.7.1.0. FROM HERE
.Reboot into recovery via twrp menu
. Flashed SuperSu 2.48beta via twrp.
https://download.chainfire.eu/735/SuperSU
. Flash aboot 5.0.2 via twrp from HERE
Clear cache and wipe dalvik via recovery (twrp)
Reboot.
Done!
CHECK HERE FOR OTHER INSTRUCTIONS AND PROOF
UPDATE
LATELY I HAVE SUCCESS WITH KINGROOT APK for rooting devices.
Download apk from here and report back
http://www.kingroot.net/
XDA LINK TO KING ROOT
@imilleson
KingoRoot 4.62 worked on my Verizon LG GPad 8.3 (vk810) with sim card running Android 5.02 - at first it said failed but proceed after that point and it succeeds.
Click to expand...
Click to collapse
Credits
@roirraW "edor" ehT for his aboot 5.0.2 and innumerous suggestions
@rant for giving a link to the official Verizon PDF detailing this release.
@Chainfire for SuperSu! [MENTION=2282431]
twrp team
@Drgravy for bringing tarp to this device
@KyPbP for providing the kdz file in a jiffy.
@DeanGibson for his valuable feedback and testing my guide @imilleson for confirmation that kingroot works on lollipop!
Anyone else I forgot?
FAQs
1.I flashed 2.48beta via twrp. Did not try version 2.48 or 2.49 apk to update supersu binaries.
2. Supersu 2.46 from play store failed. Even flashing 2.46 failed via twrp
Hnk1 said:
Credits
@roirraW "edor" ehT for his aboot 5.0.2 and innumerous suggestions
@rant for giving a link to the official Verizon PDF detailing this release.
@Chainfire for SuperSu! [MENTION=2282431]
twrp team
@Drgravy for bringing tarp to this device
Anyone else I forgot?
Click to expand...
Click to collapse
Maybe the guy who made us aware the KDZ was available. Without that I couldn't have gotten the ROM out so quickly.
RE: Step 12 - Does TWRP survive the updated aboot flash?
w0rdie said:
RE: Step 12 - Does TWRP survive the updated aboot flash?
Click to expand...
Click to collapse
No it doesnot survive it as TWRP is not compatible with aboot 5.0.2. I am sure developers are looking into it
roirraW "edor" ehT said:
Maybe the guy who made us aware the KDZ was available. Without that I couldn't have gotten the ROM out so quickly.
Click to expand...
Click to collapse
Added him as well to credits post
Even simpler!
Hnk1 said:
Hello everyone. I have successfully rooted Lollipop 5.0.2 for VERIZON LG PAD 8.3 VK810 without downgrading.
PREREQUISITES
-Updated drivers installed
-turned on usb debugging
STEPS
1.Install iRoot (also called Vroot) (in chinese). The Chinese version is on 1.83 while the english translated is still on 1.78. Use the Chinese one.
http://www.mgyun.com/
2. [Install KingoRoot -- not needed]
3.Run iRoot app from PC. Wait till it is complete. You will have partial root but some system cleaner app with King user. Do not do anything
4. [Run KingoRoot -- not needed]
5. Run Iroot and Kingoroot together. Wait till it is restarted and you acquire root with KingUser.
...
Click to expand...
Click to collapse
The above is all I needed to do, to root my two VK810 tablets. I had SuperSU already installed on both tablets, but it didn't want to successfully update its binary ("su"), so I uninstalled SuperSU and kept "KingUser", the equivalent tool that comes with iRoot.
w0rdie said:
RE: Step 12 - Does TWRP survive the updated aboot flash?
Click to expand...
Click to collapse
Just to be clear, TWRP itself is still there when you have the 35A_08 aboot flashed, the new bootloader just won't let you boot into recovery. To get back into it temporarily you just have to flash the 4.2.2 aboot, then when you're done in TWRP and want to boot the ROM again, you can flash the 35A_08 aboot that I provide in zip flashable format in my ROM thread in Development. I also provide a mirror of the 4.2.2 aboot and instructions for everything.
If you forget to re-flash the 35A_08 aboot before leaving TWRP, the only symptom is the ROM won't boot. Just use the hardware keys (volume down and power buttons held in) long enough (about 10 seconds) to manually boot back into recovery (choose Factory Reset from the regular recovery menu, which takes you into TWRP).
Hnk1 said:
No it doesnot survive it as TWRP is not compatible with aboot 5.0.2. I am sure developers are looking into it
Click to expand...
Click to collapse
DeanGibson said:
The above is all I needed to do, to root my two VK810 tablets. I had SuperSU already installed on both tablets, but it didn't want to successfully update its binary ("su"), so I uninstalled SuperSU and kept "KingUser", the equivalent tool that comes with iRoot.
Click to expand...
Click to collapse
Well, the only concern I had on my mind was if King User is safe enough and could be trusted with privacy. That's the reason I had to do all the effort to bring back Supersu. ELSE, King User was doing everything too, it's just I don't trust it that much. I'll update the guide , thanks for your feedback. If you wish to try, uninstall supersu from Google play, install supersu from links I provided (not available in market yet)using apk and then try upgrading your binaries. See what happens.
@roirraW "edor" ehT
Many thanks for clarification.
Hnk1 said:
Well, the only concern I had on my mind was if King User is safe enough and could be trusted with privacy. That's the reason I had to do all the effort to bring back Supersu. ELSE, King User was doing everything too, it's just I don't trust it that much. I'll update the guide , thanks for your feedback. If you wish to try, uninstall supersu from Google play, install supersu from links I provided (not available in market yet)using apk and then try upgrading your binaries. See what happens.
@roirraW "edor" ehT
Many thanks for clarification.
Click to expand...
Click to collapse
You're welcome!
Re: SuperUser, I agree with you. Hesitant to trust anything but SuperSU until I do more research.
roirraW "edor" ehT said:
Just to be clear, TWRP itself is still there when you have the 35A_08 aboot flashed, the new bootloader just won't let you boot into recovery. To get back into it temporarily you just have to flash the 4.2.2 aboot, then when you're done in TWRP and want to boot the ROM again, you can flash the 35A_08 aboot that I provide in zip flashable format in my ROM thread in Development. I also provide a mirror of the 4.2.2 aboot and instructions for everything.
If you forget to re-flash the 35A_08 aboot before leaving TWRP, the only symptom is the ROM won't boot. Just use the hardware keys (volume down and power buttons held in) long enough (about 10 seconds) to manually boot back into recovery (choose Factory Reset from the regular recovery menu, which takes you into TWRP).
Click to expand...
Click to collapse
I appreciate the clarity. :good:
I agree with the sentiment
roirraW "edor" ehT said:
...
Re: SuperUser, I agree with you. Hesitant to trust anything but SuperSU until I do more research.
Click to expand...
Click to collapse
I agree with the sentiment. I did uninstall SuperSU 2.46 and then sideload SuperSU 2.49, and it still had problems updating its binary. SuperSU even detected that there was another "root management" (my term) app installed, and offered to uninstall it. I let it try, and that failed as well. So, I will wait for a report of a successful conversion to SuperSU.
I did originally try Kingo Root (per the OP's instructions) on the 1st tablet, and that got me another "root management" app installed, so now I had three (before I uninstalled SuperSU)! It also installed something on the 1st tablet that Google warned me was a security risk, so after the 2nd tablet rooted with just iRoot, I did a factory reset on the 1st tablet and just used iRoot.
Both iRoot and its "root management" app KingUser seem well-written, surprising (at least to me) from a region not known for well-written, easy to use software.
---------- Post added at 09:42 AM ---------- Previous post was at 09:25 AM ----------
Hnk1 said:
Well, the only concern I had on my mind was if King User is safe enough and could be trusted with privacy. That's the reason I had to do all the effort to bring back Supersu. ELSE, King User was doing everything too, it's just I don't trust it that much....
Click to expand...
Click to collapse
Unfortunately, once you install anything with root privileges, who knows what it left behind. KingoRoot in particular left around several apps with no app icon, that KingUser listed and I was able to uninstall. However, that left me with an uneasy feeling, which is why I did a factory reset on the 1st tablet and started over.
I'd rather trust what one Chinese/Korean app left around (which I have to, if I use iRoot), rather than two.
iRoot does install two other apps, one is the "Cleaner", and another is part of the download process, but I very promptly uninstalled them.
w0rdie said:
I appreciate the clarity. :good:
Click to expand...
Click to collapse
You're welcome!
DeanGibson said:
I did originally try Kingo Root (per the OP's instructions) on the 1st tablet, and that got me another "root management" app installed, so now I had three (before I uninstalled SuperSU)! It also installed something on the 1st tablet that Google warned me was a security risk, so after the 2nd tablet rooted with just iRoot, I did a factory reset on the 1st tablet and just used iRoot.
Both iRoot and its "root management" app KingUser seem well-written, surprising (at least to me) from a region not known for well-written, easy to use software.
Unfortunately, once you install anything with root privileges, who knows what it left behind. KingoRoot in particular left around several apps with no app icon, that KingUser listed and I was able to uninstall. However, that left me with an uneasy feeling, which is why I did a factory reset on the 1st tablet and started over.
I'd rather trust what one Chinese/Korean app left around (which I have to, if I use iRoot), rather than two.
iRoot does install two other apps, one is the "Cleaner", and another is part of the download process, but I very promptly uninstalled them.
Click to expand...
Click to collapse
I thought the same thing, once something has root it could already have done whatever hidden "damage" it wanted to. I had the same experience regarding what iRoot left behind, the one time early during @Hnk1 's experimenting that I tried it.
Hnk1 said:
STEPS
1.Install iRoot (also called Vroot) (in chinese). The Chinese version is on 1.83 while the english translated is still on 1.78. Use the Chinese one.
http://www.mgyun.com/
2.Run iRoot app from PC. Wait till it is complete. You will have root with some system cleaner app with King user.
Click to expand...
Click to collapse
Well I sort of achieved root with this method.
The vroot program said I had root and root checker did too.
However adaway and titanium backup could not perform their functions. They are allowed in the king user app and tibu even said it had root access.
Anyone else run into this issue?
_Boondock_ said:
Well I sort of achieved root with this method.
The vroot program said I had root and root checker did too.
However adaway and titanium backup could not perform their functions. They are allowed in the king user app and tibu even said it had root access.
Anyone else run into this issue?
Click to expand...
Click to collapse
I was also partially rooted with the above method and thus I performed IF ABOVE FAILS in my guide, that is using another app and then running both apps simultaneously. However, another user said, he only needed to use IROOT so I edited it a bit.
Try restarting your device, and then try IF ABOVE FAILS.
See if that helps ?
@Hnk1 I really appreciate all your work but I have tried this method 100 ways and can not get it to work. Iroot says yea but root check says na and Kingo root never takes. If you have any ideas I will try again. Does it matter if I am on the ota or kdz?
mopartonyg said:
@Hnk1 I really appreciate all your work but I have tried this method 100 ways and can not get it to work. Iroot says yea but root check says na and Kingo root never takes. If you have any ideas I will try again. Does it matter if I am on the ota or kdz?
Click to expand...
Click to collapse
Although it shouldn't matter, I would try with a fresh CSE mode flash of the 35A KDZ.
roirraW "edor" ehT said:
Although it shouldn't matter, I would try with a fresh CSE mode flash of the 35A KDZ.
Click to expand...
Click to collapse
Yep tried that also, I will keep playing til I get it
mopartonyg said:
Yep tried that also, I will keep playing til I get it
Click to expand...
Click to collapse
It's tedious work, but satisfying once we figure it out. I had to reflash so many times in order to find out what two things I was debloating was causing the initial setup to FC. Google Webview and Google TTS.
Good luck!
Has anybody managed to get Android Pay working yet on our device with custom rom?
Tried the new SuHide by Chainfire but still get the unable to verify device is Android compatible message
TheATHEiST said:
Has anybody managed to get Android Pay working yet on our device with custom rom?
Tried the new SuHide by Chainfire but still get the unable to verify device is Android compatible message
Click to expand...
Click to collapse
requirements :
- SuperSU installed in systemless mode
So does not work on our device
xander33 said:
requirements :
- SuperSU installed in systemless mode
So does not work on our device
Click to expand...
Click to collapse
Can you clarify why not with our device?
When you install supersu it lists in output that it's being installed as systemless?
TheATHEiST said:
Can you clarify why not with our device?
When you install supersu it lists in output that it's being installed as systemless?
Click to expand...
Click to collapse
As i know the method for root our phone is system mode, the systemless zip not work
Here the procedure that i followed for rooting my phone and is system mode
What you need:
Unlocked bootloader (see chapter 2).
TWRP installed (see chapter 7).
1.Zip .
2.Zip .
How:
Put 1.zip and 2.zip into your sd card/internal storage.
Boot into TWRP.
Ignore the message from TWRP.
Choose the "install" button.
Locate 1.zip (if on sd card go "up a level" and then "external sdcard" there you should find it).
Install it.
Reboot your phone.
Boot into TWRP again.
Locate 2.zip .
Install it.
Reboot
That's just the initial bootloader unlock and root method.
I used same method but later flashed custom rom witch also comes rooted. I have also unrooted and then rerooted systemless mode with SuperSU zip.
TheATHEiST said:
That's just the initial bootloader unlock and root method.
I used same method but later flashed custom rom witch also comes rooted. I have also unrooted and then rerooted systemless mode with SuperSU zip.
Click to expand...
Click to collapse
You need to use Magisk.
It works for me.
Have a look here...
http://pecholite.blogspot.co.ke/2016/08/magisk-la-interfaz-systemless.html?m=1
http://forum.xda-developers.com/android/software/mod-magisk-v1-universal-systemless-t3432382
Greetings
Sent from my ALE-L21 using XDA-Developers mobile app
Fedroid said:
You need to use Magisk.
It works for me.
Have a look here...
http://pecholite.blogspot.co.ke/2016/08/magisk-la-interfaz-systemless.html?m=1
http://forum.xda-developers.com/android/software/mod-magisk-v1-universal-systemless-t3432382
Greetings
Sent from my ALE-L21 using XDA-Developers mobile app
Click to expand...
Click to collapse
Doesn't seem to work for me. Just keep getting the unable to verify device message in Android Pay app.
TheATHEiST said:
Doesn't seem to work for me. Just keep getting the unable to verify device message in Android Pay app.
Click to expand...
Click to collapse
3 months since your last contact....
Things have changed a lot and android pay is working hard for avoid us pay with rooted phones.
Nowadays magisk is on v9 version and facing v10.
Want a clue?
If your mobile is compatible with multirom go this way. One rom rooted and modified as you want and another stock for doing payments.
Luck!