Hello,
I just wanted to share how I have rooted my device today, and it was way easier than the methods I have been reading about so far.
My device: Xperia Z2 , C6543.
How I did it:
1- I updated my flashtool to the latest version, downloaded the 7.1.2.A.0.314 ftf for my region and flashed like instructed in the post. (Note that If you don't have flashtool installed, you have to go inside it's drivers folder and install the Z2 driver so it can communicate to the phone).
http://forum.xda-developers.com/showthread.php?t=2759934
2- After the downgrade to the 7.1.2.A.0.314 version mentioned above, I went to the flashtool menu (My 65XX -> Root -> Force towelroot)
When prompted to, I have choosen the SuperSU option.
Then the towelroot app showed in the phone's screen, I've tapped on "make it rain" and let it run.
After that the phone restarted and it was rooted.
3. Okay, now that the 7.1.2.A.0.314 is rooted, an OTA update notification showed up to update to the same version (lol). Well, I just let it update, and the root was there (I confirmed by restoring some data in titanium backup).
4. After that, another OTA update showed up to update to 23.0.1.A.0.167. Again, I let it download and install.
Well, that's what it took for me to root my z2 in it's latest version with only one downgrade and no manual adb commands, no manual rootkit downloads, pretty similar to the way I've always rooted my ZQ (R.I.P - it drowned lol).
The credits are due to the hard-working people who made all the mentioned tools, I am only doing my part by sharing an easier method than what i've seen around. Feel free to share your toughts.
Laters!
Sorry to be noob! Will it break anything like camera x reality or anything? And for warranty, can I claim it by just unrooting it(it's in the su) ?
Did not break anything for me. Now I can use foldermount and transfer heavy apps to the external sd. Wonderful. As for the warranty, since there is no recovery installed and no bootloader unlocked, it is as easy as doing the step 1 in the procedure described. It will flash the unrooted system back.
But ist same method, if u use this or this tool.
This post doesnt deserve an original development section!
thanks. I will follow this guide as i had root, upgraded and lost it. But i've have been itching to flash stuff lol.
But ist same method, if u use this or this tool.
Click to expand...
Click to collapse
I am not sure I understand what you mean, but if you are talking about the xperiarootkit compared to the "force towelroot" from flashtool, I checked the scripts in advance and they seem to be the same thing yes. The only shortcut to what I did was not having to flash recovery, and creating customized ftf, etc.
This post doesnt deserve an original development section!
Click to expand...
Click to collapse
I am sorry you feel that way man, that comment was a great way to add value to the conversation, thank you.
remydlc said:
thanks. I will follow this guide as i had root, upgraded and lost it. But i've have been itching to flash stuff lol.
Click to expand...
Click to collapse
Did you tried ota survival in Supersu?
rjshrjndrn said:
Did you tried ota survival in Supersu?
Click to expand...
Click to collapse
not before applying the OTA. Perhaps that would have helped. I have the app installed, but it says the binaries are not installed, to consult the forums for re-rooting
remydlc said:
not before applying the OTA. Perhaps that would have helped. I have the app installed, but it says the binaries are not installed, to consult the forums for re-rooting
Click to expand...
Click to collapse
I think you have to do all the stuff one again and root device. Then check the option for its root survival and do ota updates. I think you'll be fine with the updates.
Question, /System RW? (don't confuse it with a TA Restore, as it could only be restoring to the /Data partition).
Moscow Desire said:
Question, /System RW? (don't confuse it with a TA Restore, as it could only be restoring to the /Data partition).
Click to expand...
Click to collapse
I doubt you'll have system RW access as sony ric should still be running, but if root is working fine flashing nut's recovery should fix this easily.
root achieved and kept
Nice one thanks for the info worked well and updated to .167 ota and kept root.
Going to give this a try. Thanks
Thanks for the info, OP.
I used flashtool to downgrade my D6503 to .55, tried to use towelroot, no luck. used the CVE root exploit and got root, but after that update center failed the verification to .314.
Your method works, so cheers!
Will the Phone be wiped during this root method
ecolupo said:
Will the Phone be wiped during this root method
Click to expand...
Click to collapse
flashtool will wipe your phone unless you unselect data partition (not recommended). The rooting part is non-destructive so no that part won't your phone.
ptmaniac said:
I doubt you'll have system RW access as sony ric should still be running, but if root is working fine flashing nut's recovery should fix this easily.
Click to expand...
Click to collapse
Tried to install nut's recovery with supersu option but all the apks in the script could not be written into system folder. Also could not install xposed installer. May have to downgrade again and avoid this method
update: no need to downgrade again. sony_ric prevents r/w to system folder even with root, so I just used ric killer by forty two: http://forum.xda-developers.com/xperia-z2/general/4-4-4-sony-ric-killer-t2953141
afterward I was able to install xposed installer via normal method.
Thank you for the tutorial. It worked fine for me.
What will happen if I do a factory reset via settings-menu? Will root be gone? Do I have to downgrade again or can I install SuperSU to get root back?
Sent from my D6503 using XDA Free mobile app
Related
Hello everyone,
I noticed that this is a common problem and I realize just not that I shouldn't have just updated without informing myself.
Anyway, I checked and the root seems to be gone (checked with Root Checker, although the SU app is still there [but not working]).
I checked the fastbook and it says 'unlocked', which is good, I don't have to lose data.
How do I re-root properly?
I am using OS X at the moment and I have access to adb but, if needed, I can access a Windows computer again and use Nexus Root Toolkit again (that's what I used the first time I rooted).
I have CWM-SuperSU-v0.98.zip and recovery-clockwork-6.0.1.9-manta.img.
I checked the bootloader and it says 'no command' but it still has:
- reboot system now
- apply update from ADB
- wipe data...
- wipe cache...
Thanks in advance for any help
First thing - Nearly always you will lose root after applying an OTA - at least lately so that's not really a big deal.
Second - Get and always use the Latest version of root zip from chainfire: http://download.chainfire.eu/370/SuperSU/UPDATE-SuperSU-v1.80.zip
Or you can also just apply SuperSU from google play and you will prompted to reboot to update binaries etc. after you apply the OTA.
His blog on latest version: https://plus.google.com/+Chainfire/posts/QhrEdeJ3nqQ
I got the same problem.
I solved it by just by downgrading and upgrading back to the latest version of Cyanogenmod.
lg Darcade
I have the same problem...
I have the same problem, I have installed the 4.4.3 OTA and now SuperSU stopped working.
Any advice?
Easily got my root back using Wugfresh toolkit.
Only the paid for version of SuperSU - "Pro" will attempt to keep root after an OTA update. It worked perfectly for me on a 5, 7 and 10.
[Lemmy] said:
I have the same problem, I have installed the 4.4.3 OTA and now SuperSU stopped working.
Any advice?
Click to expand...
Click to collapse
Don`t use toolkits, just boot into TWRP in fastboot and reflash the latest superSU.zip and you`re rooted.
gee2012 said:
Don`t use toolkits, just boot into TWRP in fastboot and reflash the latest superSU.zip and you`re rooted.
Click to expand...
Click to collapse
thats what I did by now, just with CWM instead of TWRP.
[Lemmy] said:
thats what I did by now, just with CWM instead of TWRP.
Click to expand...
Click to collapse
Well done mate , toolkits suck and you have no control over them. Flashing with adb gives you full control and you learn something
gee2012 said:
Well done mate , toolkits suck and you have no control over them. Flashing with adb gives you full control and you learn something
Click to expand...
Click to collapse
...after having to go through this over and over again with every single update I'm starting to think that having root is definitely not worth the pain.
If you switch to TWRP using its built in SuperSU install makes re-rooting a breeze.
Sent from my SM-T800 using XDA Premium HD app
There are quite a few threads that have all the information but for new Z3TC owners, it can be challenging to know where to start and to understand the process.
How I started here is recently purchasing a Rogers Z3TC and to my surprise, the bootloader cannot be unlocked. I shouldn't have been surprised since carriers do tend to lock the bootloaders and if I did my research, I would have found out that Sony offers unlockable and non-unlockable versions of the same hardware. I have never had to worry about having a recovery to root the device or install custom ROMs with root. For anyone new to Android, the recovery is probably the single most important mode to setting up your device the way you want. A prerequisite for that is of course an unlocked bootloader so you can install the recovery of your choice - ClockworkMod (CWM) or TeamWin Recovery Project (TWRP).
So what makes the process confusing for some new Z3TC owners, such as myself, is that the process is somewhat backward. For most of my previous devices, it is:
1. Unlock bootloader
2. Install recovery
3. Gain root through flashing SuperSU or a rooted custom ROM
Because for my Rogers Z3TC cannot be bootloader unlocked, the process now looks like this:
1. Obtain root
2. Install recovery
3. Flash a pre-rooted Lollipop ROM
The only way we can get root on Lollipop is on a pre-rooted ROM because there is no exploit yet to do it directly. The only way we can install a pre-rooted ROM is through a custom recovery. The only way we can get a custom recovery is to be rooted. For unlocked bootloaders, they can get recovery through flashing the img of the recovery. The only way we can obtain root is through an exploit on a Z3 ROM, which thankfully works on the Z3TC due to the similar hardware.
So without quoting all the instructions of each step, I will provide the links and you just have to follow the instructions for each part.
Before you begin, you will need Flashtool and install the drivers for Flashmode and your device. You will not need Fastboot because unfortunately, you wont be doing anything with it on a locked bootloader. You may install it if you want.
If you are on Windows 8.1/10, you will need to to disable driver signature.
1. Obtain root by first flashing SGP621_23.0.1.A.0.167_CE.ftf and the system partition of D6603_23.0.A.2.93_Generic_20GLOBAL.ftf. Then use giefroot to root.
2. Prepare prerooted flashable zip of 23.1.A.0.690 NOBA on your internal storage or external SD.
3. Install XZDualRecovery and now you will have TWRP to install 23.1.A.0.690 NOBA on your SD card.
I would finish off by running SGP621-RICDefeat.zip to get R/W system access.
This is the simple template that I would imagine be the way those of us with locked bootloaders will install custom ROMs, obtain root or upgrade Android.
Thank you @lowtraxx for the root instructions and @[NUT] for the XZDualRecovery.
I am running stock Lollipop now.
If I take above mentioned steps,
do I lose the data with apps and settings I am using now?
ux50jp said:
I am running stock Lollipop now.
If I take above mentioned steps,
do I lose the data with apps and settings I am using now?
Click to expand...
Click to collapse
I have tried downgrading from Lollipop back to step one without wipe in Flashtool but I think the system data are incompatible and caused bootloop.
Once I flashed a fresh SGP621_23.0.1.A.0.167_CE.ftf, I did not bother setting up any apps until I did a fresh install of the pre-rooted Lollipop ROM. If you can back up everything first, that would be best. If you cannot, try Flashtool without wipe and worst case scenario if you bootloop, there is a shut off button beside the SIM card tray and you can still get back into Flashmode.
hellocng said:
I have tried downgrading from Lollipop back to step one without wipe in Flashtool but I think the system data are incompatible and caused bootloop.
Once I flashed a fresh SGP621_23.0.1.A.0.167_CE.ftf, I did not bother setting up any apps until I did a fresh install of the pre-rooted Lollipop ROM. If you can back up everything first, that would be best. If you cannot, try Flashtool without wipe and worst case scenario if you bootloop, there is a shut off button beside the SIM card tray and you can still get back into Flashmode.
Click to expand...
Click to collapse
If someone could do a tutorial video, I think a lot of people along with myself would highly appreciate it. I tried doing root on locked bootloader prior to Lollipop, but it just wasn't happening for me. So I decided to give up and just update it since it was too much of a hassle.
Thanks for the post.
Has anyone else tried this?
I am wondering why the root method previously need to unlock the bootloader to get the 621 firmware back on an rooted.
What has changed for this to work without unlocking the bootloader?
Thanks in advance
hellocng said:
1. Obtain root by first flashing SGP621_23.0.1.A.0.167_CE.ftf and the system partition of D6603_23.0.A.2.93_Generic_20GLOBAL.ftf. Then use giefroot to root.
2. Prepare prerooted flashable zip of 23.1.A.0.690 NOBA on your internal storage or external SD.
3. Install XZDualRecovery and now you will have TWRP to install 23.1.A.0.690 NOBA on your SD card.
I would finish off by running SGP621-RICDefeat.zip to get R/W system access.
This is the simple template that I would imagine be the way those of us with locked bootloaders will install custom ROMs, obtain root or upgrade Android.
Thank you @lowtraxx for the root instructions and @[NUT] for the XZDualRecovery.
Click to expand...
Click to collapse
Will I lose my drm keys by doing this? I want to get root but dont wanna unlock my bootloader
Jiyeon90 said:
Will I lose my drm keys by doing this? I want to get root but dont wanna unlock my bootloader
Click to expand...
Click to collapse
yes if you don't follow this steps
1- flash stock 4.4.4 with flashtool
2-flash the 4.4.4 Z3 system only" with flastool
3-factory reset in settings enable usb debuging etc,etc
4-obtain root with giefroot
5-backup TA partition
6-unlock boot loader
7-install dual recovery
8-flash prerooted 5.0.2 with custom recovery
9- gain get system R/W access with ricdefeat
10-relock boot loader restoring TA
good luck
Jiyeon90 said:
Will I lose my drm keys by doing this? I want to get root but dont wanna unlock my bootloader
Click to expand...
Click to collapse
No, we cannot unlock our bootloader so we will not lose DRM.
Speedy Gonzalez said:
yes if you don't follow this steps
1- flash stock 4.4.4 with flashtool
2-flash the 4.4.4 Z3 system only" with flastool
3-factory reset in settings enable usb debuging etc,etc
4-obtain root with giefroot
5-backup TA partition
6-unlock boot loader
7-install dual recovery
8-flash prerooted 5.0.2 with custom recovery
9- gain get system R/W access with ricdefeat
10-relock boot loader restoring TA
good luck
Click to expand...
Click to collapse
Step 3 and 5 is not necessary because we cant do step 6.
hellocng said:
No, we cannot unlock our bootloader so we will not lose DRM.
Step 3 and 5 is not necessary because we cant do step 6.
Click to expand...
Click to collapse
what do you mean with we can't ? you don't want to ?
Never mind I didn't knew you CAN'T unlock the bootloader at all
1. Obtain root by first flashing SGP621_23.0.1.A.0.167_CE.ftf and the system partition of D6603_23.0.A.2.93_Generic_20GLOBAL.ftf. Then use giefroot to root.
2. Prepare prerooted flashable zip of 23.1.A.0.690 NOBA on your internal storage or external SD.
3. Install XZDualRecovery and now you will have TWRP to install 23.1.A.0.690 NOBA on your SD card.
I would finish off by running SGP621-RICDefeat.zip to get R/W system access.
Click to expand...
Click to collapse
These steps don't unlock bootloader. So DRM stays intact. No need to backup/restore TA!!!
hellocng said:
No, we cannot unlock our bootloader so we will not lose DRM.
Step 3 and 5 is not necessary because we cant do step 6.
Click to expand...
Click to collapse
So I can get root even if I skip step 3, 5, and 6?
Jiyeon90 said:
So I can get root even if I skip step 3, 5, and 6?
Click to expand...
Click to collapse
Yes.
Thank you, its working now, yeah no need to backup TA, unlock bootloader, etc.
It was a bit tricky but not as hard as in the other threads.
I did one mistake, I flashed the SGP621 pre-rooted zip on my SGP611, it wouldnt turn on obviously, so I created a pre-rooted file for the SGP611 and now I'm on lollipop with root and dual recovery
Flashing the ricdefeat file fails everytime though but thats a very minor issue.
Here's the pre-rooted file for the SGP611 users
https://drive.google.com/file/d/0Bz4ANHmLVuVTR2FqWHEzemxORjg/view?usp=sharing
It seems really hard to brick the device too, I ran out of space on my pc while flashing 4.4.4 with flashtool so the processes was aborted at about 50% but I was still able to get into flash mode again.
Jiyeon90 said:
Thank you, its working now, yeah no need to backup TA, unlock bootloader, etc.
It was a bit tricky but not as hard as in the other threads.
I did one mistake, I flashed the SGP621 pre-rooted zip on my SGP611, it wouldnt turn on obviously, so I created a pre-rooted file for the SGP611 and now I'm on lollipop with root and dual recovery
Flashing the ricdefeat file fails everytime though but thats a very minor issue.
Here's the pre-rooted file for the SGP611 users
https://drive.google.com/file/d/0Bz4ANHmLVuVTR2FqWHEzemxORjg/view?usp=sharing
It seems really hard to brick the device too, I ran out of space on my pc while flashing 4.4.4 with flashtool so the processes was aborted at about 50% but I was still able to get into flash mode again.
Click to expand...
Click to collapse
Could that prerooted 611 file work on my lollipop 612? Or would it need 612 specifically to work?
Thanks
GigaSPX said:
Could that prerooted 611 file work on my lollipop 612? Or would it need 612 specifically to work?
Thanks
Click to expand...
Click to collapse
I'm not sure, you could give it a try.
Or just make a pre-rooted file yourself, it's quite easy, just remember to use the right lollipop .FTF file for your 612 device.
Jiyeon90 said:
I'm not sure, you could give it a try.
Or just make a pre-rooted file yourself, it's quite easy, just remember to use the right lollipop .FTF file for your 612 device.
Click to expand...
Click to collapse
Just follow the same instructions from the first post?
GigaSPX said:
Just follow the same instructions from the first post?
Click to expand...
Click to collapse
Yes, what I did was.
Downgrade to 4.4.4 using flashtool, if you are on 611 or 612 dont use the ftf file in the first post as your device wont turn on, use the correct ftf file for your device.
Flash z3 compact system using flashtool (dont wipe anything and exclude everything but system, you will end up with with the z3 system and you will get error messages when you turn it on, thats fine)
Root using giefrrot (it took me 3 tries to get it rooted)
Install double recovery.
Put the pre-rooted file in your phone memory or sd card.
Flash the pre-rooted lollipop file and reboot, thats all.
But as you have the 612 device I would recommend you to make your own pre-rooted file, just follow these instructions
http://forum.xda-developers.com/crossdevice-dev/sony/tool-prfcreator-easily-create-pre-t2859904
Jiyeon90 said:
Flashing the ricdefeat file fails everytime though but thats a very minor issue.
It seems really hard to brick the device too, I ran out of space on my pc while flashing 4.4.4 with flashtool so the processes was aborted at about 50% but I was still able to get into flash mode again.
Click to expand...
Click to collapse
The RICDefeat is quite important if you want to remove bloatware or alter the system in anyway, which is one of my prime reasons for rooting. What was the error or message?
Flash mode is intact as long as the bootloader is locked as we cannot modify any of the kernel or boot partitions.
Jiyeon90 said:
Yes, what I did was.
Downgrade to 4.4.4 using flashtool, if you are on 611 or 612 dont use the ftf file in the first post as your device wont turn on, use the correct ftf file for your device.
Flash z3 compact system using flashtool (dont wipe anything and exclude everything but system, you will end up with with the z3 system and you will get error messages when you turn it on, thats fine)
Root using giefrrot (it took me 3 tries to get it rooted)
Install double recovery.
Put the pre-rooted file in your phone memory or sd card.
Flash the pre-rooted lollipop file and reboot, thats all.
But as you have the 612 device I would recommend you to make your own pre-rooted file, just follow these instructions
http://forum.xda-developers.com/crossdevice-dev/sony/tool-prfcreator-easily-create-pre-t2859904
Click to expand...
Click to collapse
I want to personally thank you for the instructions. I'm now running perfectly as is prerooted Lollipop SGP612. It took me several tries too with the rooting with giefroot because each time I run it, I can't get it connected to USB anymore, which I had to constantly restart to get.
hellocng said:
The RICDefeat is quite important if you want to remove bloatware or alter the system in anyway, which is one of my prime reasons for rooting. What was the error or message?
Flash mode is intact as long as the bootloader is locked as we cannot modify any of the kernel or boot partitions.
Click to expand...
Click to collapse
I don't remember what error message I got, all I remember is seeing the word 'aborted' with the green Android guy laying down.
I have removed several apps that came pre-installed using titanium backup, I also installed the SD card fix so I can use the SD card freely. I haven't had a single issue so far.
---------- Post added at 12:03 AM ---------- Previous post was at 12:03 AM ----------
GigaSPX said:
I want to personally thank you for the instructions. I'm now running perfectly as is prerooted Lollipop SGP612. It took me several tries too with the rooting with giefroot because each time I run it, I can't get it connected to USB anymore, which I had to constantly restart to get.
Click to expand...
Click to collapse
No problem, glad I could help [emoji2]
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!
Hello everyone. Finally i found it. I want to help everyone who search along time this recovery.
This is twrp recovery for One M8 Eye. First please unlock bootloader via HTC DEV. Than ( fastboot flash recovery twrp-m8eye-2.8.0.3.img ) After that flash UPDATE-SuperSU-v2.46.zip ( http://download.chainfire.eu/supersu). Now you have root :good::good:
Thanks Iman Mark and Chainfire
Link: https://drive.google.com/file/d/0B71KxMi9guCSN0V5bU1DSUNaX2c/view?usp=sharing
Please don't forget thanks
This update supersu no longer works. I installed that twrp and did the process for that version of supersu and it said successful. Upon checking supersu, it says the binary files are missing. Then I installed the newer supersu verison through twrp, without deleting the old supersu and now the phone is stuck on htc boot screen. This may work for some, but DO NOT install another supersu over an old one without deleting it first. You WILL get stuck on boot.
Weisheit7 said:
Then I installed the newer supersu verison through twrp
Click to expand...
Click to collapse
"Newer" meaning what? Always be specific, otherwise we can only guess. For all we know, you flashed 2.47, which is "newer" than 2.46.
You should be using the latest stable version, which is currently 2.78, which you can obtain the zip from here: http://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703
Try flashing this, and hopefully that works. I'm not certain, but as far as I know, you don't need to delete an old SuperSU app, in order for the proper updated one to work.
Also, a word of basic good practice when modding any Android device: Always make sure you are using the current updated methods according to your OS version.
The files in the OP are from July 15, 2015. That is well before Marshmallow existing. Root methods almost always need to be updated with each major OS version update. There is really no reason to have thought SuperSU from over a year ago would work on a current OS version device.
redpoint73 said:
"Newer" meaning what? Always be specific, otherwise we can only guess. For all we know, you flashed 2.47, which is "newer" than 2.46.
You should be using the latest stable version, which is currently 2.78, which you can obtain the zip from here: http://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703
Try flashing this, and hopefully that works. I'm not certain, but as far as I know, you don't need to delete an old SuperSU app, in order for the proper updated one to work.
Also, a word of basic good practice when modding any Android device: Always make sure you are using the current updated methods according to your OS version.
The files in the OP are from July 15, 2015. That is well before Marshmallow existing. Root methods almost always need to be updated with each major OS version update. There is really no reason to have thought SuperSU from over a year ago would work on a current OS version device.
Click to expand...
Click to collapse
You're right, and as of right now I have a different issue. I found a link for the Chinese ROM of the htc m8 eye and I successfully installed it. Now the device is on 4.4.4 rooted. I've tried to do the OTA update but each time in stock recovery it fails after about 20-25% and says "system/bin/reboot has unexpected contents" and fails every time. I have uninstalled supersu from the app itself, deleted all of the residual files and checked the phone for root. Root checker says it's not rooted.
How can I fix the OTA problem through stock recovery? I checked the /system/bin/reboot file and there's nothing there specifically that I can see is corrupted or changed. Is there any possibility that supersu has system permissions and is causing this error? If so, how do I fix the /reboot has unexpected contents problem? How can I delete supersu (su) from having system permissions over everything?
I cannot find a stock Chinese ROM for this device, only the rooted one. I'm at a loss here..
Weisheit7 said:
I've tried to do the OTA update but each time in stock recovery it fails after about 20-25% and says "system/bin/reboot has unexpected contents" and fails every time. I have uninstalled supersu from the app itself, deleted all of the residual files and checked the phone for root. Root checker says it's not rooted.
Click to expand...
Click to collapse
Unrooting in order to OTA doesn't work, you need the stock never rooted ROM.
redpoint73 said:
Unrooting in order to OTA doesn't work, you need the stock never rooted ROM.
Click to expand...
Click to collapse
I've read online that if you unroot it the OTA update should go through. It depends on how the root was done, correct? If root has (owner) permissions over system files, how can I put it back to stock? Are you aware of any HTC One M8 eye mels_tuhl stock rom China region? I've scoured the internet forever and cannot find one. If you need my getvar info I'll post it here and I appreciate any help you can potentially give me.
Weisheit7 said:
I've read online that if you unroot it the OTA update should go through.
Click to expand...
Click to collapse
I can't speak to what you read, if you are vague and don't reference any specific website.
What you read is not correct. Its been verified in the M8 forums many times (at least on the "regular" M8). The fact you unrooted, and the OTA doesn't work, also proved it.
Weisheit7 said:
It depends on how the root was done, correct?
Click to expand...
Click to collapse
Incorrect. I haven't seen any root method on the M8, which allows OTA updates after unrooting.
Weisheit7 said:
Are you aware of any HTC One M8 eye mels_tuhl stock rom China region?
Click to expand...
Click to collapse
Unfortunately, no.
redpoint73 said:
I can't speak to what you read, if you are vague and don't reference any specific website.
What you read is not correct. Its been verified in the M8 forums many times (at least on the "regular" M8). The fact you unrooted, and the OTA doesn't work, also proved it.
Incorrect. I haven't seen any root method on the M8, which allows OTA updates after unrooting.
Unfortunately, no.
Click to expand...
Click to collapse
Thanks for taking the time to reply. Since then I have corrected the problem. I downloaded a TWRP backup of Marshmallow from another user on here in a different thread, placed it into my TWRP backup folder, wiped system, internal storage, cache etc and then flashed the backup. Everything went well...marshmallow is on the phone and root is gone.
necaticetinkaya said:
Hello everyone. Finally i found it. I want to help everyone who search along time this recovery.
This is twrp recovery for One M8 Eye. First please unlock bootloader via HTC DEV. Than ( fastboot flash recovery twrp-m8eye-2.8.0.3.img ) After that flash UPDATE-SuperSU-v2.46.zip ( http://download.chainfire.eu/supersu). Now you have root :good::good:
Thanks Iman Mark and Chainfire
Link: https://drive.google.com/file/d/0B71KxMi9guCSN0V5bU1DSUNaX2c/view?usp=sharing
Please don't forget thanks
Click to expand...
Click to collapse
Can you provide another share of the file? The previous link has expired
Hi guys,
I'm trying to understand if this (thread title) is possible and which is the right way.
I would like use OTA for this, but if not possible also manual update is good for me (but how? MiFlash?).
Issue: I have to install a Tasker plugin as system app: Nougat+ Tasker Tethering Control and this should change my system partition and not allow me to update by OTA, is it right? ...or my misunderstanding?
I would like also use app like AdAway that need read/write access to system partition to change hosts file.
Question: So what is the best way for keep phone rooted, allow system modification ant at the same time preserving OTA or stock rom update?
Thanks a lot for all suggestions and answer!
someone? any suggestions?
Install that tasker app as Magisk module and allow systemless hosts modification in Magisk settings. This way you won't have to modify system partition directly.
Two ways to update,
1. OTA
2. Miflash - which you have to download the rom. normally you have wait few days or week after OTA release.
No matter how you update, it will restore stock system. Thats mean you have to reinstall above apps everytime you update.
ltf_195 said:
Two ways to update,
1. OTA
2. Miflash - which you have to download the rom. normally you have wait few days or week after OTA release.
No matter how you update, it will restore stock system. Thats mean you have to reinstall above apps everytime you update, unless you root with Magisk.
Click to expand...
Click to collapse
Reading this page: https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md
NOTE: In order to apply OTAs, you HAVE to make sure you haven't modified /system (and /vendor if available) in anyway, even remounting the partition to rw will tamper block verification!!
Click to expand...
Click to collapse
So if I write my system partition, I think OTA don't running anymore.
note: for install system app (write sytem partition) as I need, of course I'll root my phone...there isn't other way, isn't it?
kam1kazze said:
So if I write my system partition, I think OTA don't running anymore.
Click to expand...
Click to collapse
Correct
kam1kazze said:
note: for install system app (write sytem partition) as I need, of course I'll root my phone...there isn't other way, isn't it?
Click to expand...
Click to collapse
If you already modified your system partition, follow this step:
1. download and flash stock rom from here.You can keep your data if you want.
2. Follow this guide to root using magisk https://forum.xda-developers.com/mi-a1/how-to/root-mi-a1-oreo-8-0-disabling-ota-magisk-t3728654
Magisk will root your phone without modified /system partition.
Good luck
So if I well understood I have to follow the posted guide https://forum.xda-developers.com/mi-a1/how-to/root-mi-a1-oreo-8-0-disabling-ota-magisk-t3728654 each time I flash the rom...
kam1kazze said:
So if I well understood I have to follow the posted guide https://forum.xda-developers.com/mi-a1/how-to/root-mi-a1-oreo-8-0-disabling-ota-magisk-t3728654 each time I flash the rom...
Click to expand...
Click to collapse
Correct. But if you follow the guide, your OTA will work again, so you dont need to download and flash every update.
When you successfully follow the guide, make sure you disable automatic update in developer option. When update arrive, follow this step https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md
ltf_195 said:
Correct. But if you follow the guide, your OTA will work again, so you dont need to download and flash every update.
When you successfully follow the guide, make sure you disable automatic update in developer option. When update arrive, follow this step https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md
Click to expand...
Click to collapse
Don't work OTA beacause I have write the system partition...this was my question
kam1kazze said:
I have to install a Tasker plugin as system app: Nougat+ Tasker Tethering Control
Click to expand...
Click to collapse
In the description on the play store it says it only requires root, do you really need to install it as a system app?
If you really need to install it to the system partition, do it as a magisk module (as was said before). That way you don't need to touch your system partition and you can still do OTAs (if you follow the magisk ota guide)
hacker1 said:
In the description on the play store it only says it requires root, do you really need to install it as a system app?
If you really need to install it to the system partition, do it as a magisk module (as was said before). That way you don't need to touch your system partition and you can still do OTAs (if you follow the magisk ota guide)
Click to expand...
Click to collapse
It need the root permission to install the app in system partition...this allow tasker plugin to enable/disable wi-fi tethering. Since nougat, tasker cannot do this without this plugin
I don't know how to transform it to a magisk module.
Thanks for all information
ltf_195 said:
Two ways to update,
1. OTA
2. Miflash - which you have to download the rom. normally you have wait few days or week after OTA release.
No matter how you update, it will restore stock system. Thats mean you have to reinstall above apps everytime you update.
Click to expand...
Click to collapse
With two, do you lose data as long you don't check the clear data?