[VK810][ROOT][Lollipop][5.02] No downgrade required - G Pad 8.3 General

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!

Related

[Q] Lost Root after OTA update. How to properly re-root without messing the system?

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

[ROOT] 23.0.1.A.0.167 [LOCKED BL] No recovery needed

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

M8 Eye Recovery and Root

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

Root for at&t note 3 on android 5.0

Is there anybody that has been able to root their at&t note 3 on android 5.0. I bought an at&t note 3 the other day and have been looking for a way to root it but have not found one yet. Please help me.
Absolutely. I just arrived at work or I would post a full detailed guide, but here's the run down.
You have to downgrade from 5.0 (OC1) to 4.2.2 (NC2).
Once you've done that, root with towelroot.apk, install SuperSU (I prefer chainfire), then install Busybox, (I prefer Stephan Erickson) and then finally, install Safestrap Recovery V3.75.
Then boot into Safestrap recovery, wipe/factory reset, and then flash the ROM you want.
I would gladly post links to everything but as I said, I'm at work. If nobody else does before I clock out. I'll definitely help you out.
im not the poster, but I would like the info if you dont mind. Thank you.
phlashb4k said:
Absolutely. I just arrived at work or I would post a full detailed guide, but here's the run down.
You have to downgrade from 5.0 (OC1) to 4.2.2 (NC2).
Once you've done that, root with towelroot.apk, install SuperSU (I prefer chainfire), then install Busybox, (I prefer Stephan Erickson) and then finally, install Safestrap Recovery V3.75.
Then boot into Safestrap recovery, wipe/factory reset, and then flash the ROM you want.
I would gladly post links to everything but as I said, I'm at work. If nobody else does before I clock out. I'll definitely help you out.
Click to expand...
Click to collapse
im not the poster, but I would like the info if you dont mind. Thank you.
Did anyone ever figure out how to root this phone yet
Read above...
Sorry guys work got the best of me. I just got permission from a couple of developers to re-do a thread that elaborates more into how to root, flash etc. So that will be up by the end of the week (hopefully). My method I will be posting is completely different than what I'm telling you here. Because my guide will let you flash an a single file using flashfire that will already have root, xposed, viper audio, + extras already installed and configured. What I'm posting below is the main method being used.
In the mean time:
Download and install Samsung Mobile Drivers http://developer.samsung.com/technical-doc/view.do?v=T000000117, Reboot before connecting your phone.
Download https://www.androidfilehost.com/?fid=95784891001615211 - This is a stock NC2 (Android 4.4.2) image you will flash to down grade from 5.0. (Temporarily).
Download Towelroot https://towelroot.com/tr.apk - This is towelroot, it exploits a vulnerability in android 4.4.2 that allows you to gain root without even rebooting your phone.
Download SuperSU https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip?retrieve_file=1 - You can of course user any superuser app. I am personally a big supporter of Chainfire and his applications.
Download Safestrap Safestrap-KLTEVZW-NCG-3.75-B03.apk http://forum.xda-developers.com/devdb/project/?id=4718#downloads - This will be your recovery.
Download Odin http://forum.xda-developers.com/showthread.php?t=2711451 Make sure it's version 3.10.0 and only download odin from that post please. There are obnoxious amounts of fake odin downloads that come up in a google search that may contain malicious code.
Don't forget Busybox https://play.google.com/store/apps/details?id=stericson.busybox&hl=en
Also download any ROM you want to flash, BEFORE doing this. Unless of course you want to stay on rooted 4.2.2
----
0. Backup. Back up everything.
1. Place Towelroot, SuperSU, Safestrap, and Busybox on your SD card.
2. Bring your phone into download mode. (Power Button+Volume Down+Home Button)
3. Connect your phone to your computer using usb. (Back of the computer usb is always better)
-Make sure you installed the Samsung Drivers
4. Bring up odin and place N900AUCUCNC2_Full_Odin_Tar.tar.md5 file in the AP slot. (Odin might hangup and freeze for a minute. It's normal, don't click or do anything, just wait.)
5. Auto Reboot and F. Reset Time on odin should already be checked. Just make sure.
6. Under ID:COM on odin, it should read 0:[COM4] in light-ish blue color.
7. Odins message should read <ID:0/004> Added!!
--Numbers might be different for each person.
8. Click Start and wait a while. After 15-20 minutes your phone will eventually boot into Android 4.4.2
And in this exact order:
9. Install Towelroot and click 'make it rain'
10. Install SuperSU, Be sure to disable knox when it asks. If it hangs at all just force close SuperSU and try again.
11. Install Busybox
12. Install Safestrap
Done.
When you want to flash a ROM simply place it on your SD card and flash it using Safestrap. Make sure when flashing that the ROM comes with the OC1 kernel. If it doesn't you'll need to flash it after flashing the ROM.
As I said above I'm going to be posting an entire thread this week dedicated to rooting, flashing, and working with this phone. It's going to have the most updated information that I have and an easier and quicker method that doesn't require Safestrap. I'm going to ask mods and hopefully it will get a sticky.
Thank you!! I`m going to try this tonight. I`ll let you if I can pull it off. Looking forward to your new thread too. Thanks again!!
Quick question phlashb4k, the first step in your guide ( 1. Place Towelroot, SuperSU, Safestrap, and Busybox on your SD card.), the link you posted for busybox is for the play store app. Is there a zip file for it elsewhere. I can`t download the app to my sd card.. Could I install it from the play store after I`ve downgraded from 5.0 to 4.4.2? I`ve searched this site and googled for a while and I still cant do it. Everything else is ready ready to go. Thanks in advance.
I am new to the root process and must also down grade to 4.4.2, can i re-upgrade to 5.0 after the root some how while maintaining my root?
Safestrap
Without question Safestrap is the biggest problem for me
The newer version B03 would not boot to recovery
I had to go back to B01
---------- Post added at 08:01 AM ---------- Previous post was at 07:37 AM ----------
Upon boot it installs 262 "updates" fro AT&T
Using the rooted file from
http://forum.xda-developers.com/showpost.php?p=59666958&postcount=2
Last time it sent me into a boot loop after the updates.
I did get it to run for a while.
Trying the complete stagefright fix also
Which I can't seem to find the link to right this instant.
Constantly get
Unfortunately, the process
com.google.process.gaaps has stopped errors
Thought I had it fixed at one pint but it is a problem again.
this seems to help
http://www.teamandroid.com/2013/04/...ogle-process-gapps-has-stopped-error-message/
working on it.
ddamm07 said:
Quick question phlashb4k, the first step in your guide ( 1. Place Towelroot, SuperSU, Safestrap, and Busybox on your SD card.), the link you posted for busybox is for the play store app. Is there a zip file for it elsewhere. I can`t download the app to my sd card.. Could I install it from the play store after I`ve downgraded from 5.0 to 4.4.2? I`ve searched this site and googled for a while and I still cant do it. Everything else is ready ready to go. Thanks in advance.
Click to expand...
Click to collapse
Yes you can install directly from the Playstore or flash a zip file. Either works just fine as long as everything is installed in the correct order you'll be good to go. Allow me a bit and I can upload the .apk directly to my google drive account and provide a link. You could really download SuperSU and Busybox from the Playstore if you wanted to. It just takes a bit longer.
Gonobn said:
I am new to the root process and must also down grade to 4.4.2, can i re-upgrade to 5.0 after the root some how while maintaining my root?
Click to expand...
Click to collapse
Of course. After you downgrade you then have access to Safestrap, which is a custom recovery environment you use to flash ROMs with. (Almost) every ROM for our phones already have SuperSU installed, if it doesn't it will specify in the thread that you need to flash SuperSU using Safestrap. But there's only a few that require it. Most of them already include the OC1 kernel inside the ROM as well. (OC1 is the only kernel that will run 5.0 on our phones).
rlj4214 said:
Without question Safestrap is the biggest problem for me
The newer version B03 would not boot to recovery
I had to go back to B01
---------- Post added at 08:01 AM ---------- Previous post was at 07:37 AM ----------
Upon boot it installs 262 "updates" fro AT&T
Using the rooted file from
http://forum.xda-developers.com/showpost.php?p=59666958&postcount=2
Last time it sent me into a boot loop after the updates.
I did get it to run for a while.
Trying the complete stagefright fix also
Which I can't seem to find the link to right this instant.
Constantly get
Unfortunately, the process
com.google.process.gaaps has stopped errors
Thought I had it fixed at one pint but it is a problem again.
this seems to help
http://www.teamandroid.com/2013/04/...ogle-process-gapps-has-stopped-error-message/
working on it.
Click to expand...
Click to collapse
If the following doesn't help please explain your problem in a little more detail for me, write out each step you are doing and I will try to see which might be causing the issue.
Safestrap is very touchy and actually isn't compatible with 5.0 (OC1). To boot into Safestrap after flashing 5.0, if you want to do a backup (which I wouldn't recommend with safestrap, I've personally only had bad luck) you need to either flash the NC2 kernel with odin, or download and install http://forum.xda-developers.com/note-3-att/development/nc2-flasher-app-unsafe-t2989141. I suggest downloading the .apk. All you do is flash the NC2 kernel with the flasher app and it will automatically boot you into safestrap. After you do whatever it is you need to do, (flash patches, etc) you then flash the OC1 kernel and reboot. OC1 kernel can be found here: https://mega.co.nz/#!fAcA3JhL!-hK_TU6NamIJdvgwWdZ90VmOwBdRBxSL70VgC4sILwc
To fix your Playstore issue, remove any Playstore updates you have, then download and install the latest version from here: https://www.apkmirror.com/apk/google-inc/google-play-store/
Well I was was able to down grade with out a hitch. If I knew it was so simple, I would have done it a long time ago. I finally was able find all the info I needed about ROMs available and how to`s but before I start flashing, I`m going to have do a lot more reading on this awesome site. Now since my note 3 is no longer in service and out of warranty, I`m assuming I don`t have to settle for a at&t rom. I`m just going to use as a little tablet with just wifi and bluetooth. That is after have used it as a guinea pig, then I`ll start on rooting my note 4. Thanks again for your help in getting me going, phlashb4k.:good:
phlashb4k said:
Yes you can install directly from the Playstore or flash a zip file. Either works just fine as long as everything is installed in the correct order you'll be good to go. Allow me a bit and I can upload the .apk directly to my google drive account and provide a link. You could really download SuperSU and Busybox from the Playstore if you wanted to. It just takes a bit longer.
Of course. After you downgrade you then have access to Safestrap, which is a custom recovery environment you use to flash ROMs with. (Almost) every ROM for our phones already have SuperSU installed, if it doesn't it will specify in the thread that you need to flash SuperSU using Safestrap. But there's only a few that require it. Most of them already include the OC1 kernel inside the ROM as well. (OC1 is the only kernel that will run 5.0 on our phones).
If the following doesn't help please explain your problem in a little more detail for me, write out each step you are doing and I will try to see which might be causing the issue.
Safestrap is very touchy and actually isn't compatible with 5.0 (OC1). To boot into Safestrap after flashing 5.0, if you want to do a backup (which I wouldn't recommend with safestrap, I've personally only had bad luck) you need to either flash the NC2 kernel with odin, or download and install http://forum.xda-developers.com/note-3-att/development/nc2-flasher-app-unsafe-t2989141. I suggest downloading the .apk. All you do is flash the NC2 kernel with the flasher app and it will automatically boot you into safestrap. After you do whatever it is you need to do, (flash patches, etc) you then flash the OC1 kernel and reboot. OC1 kernel can be found here: https://mega.co.nz/#!fAcA3JhL!-hK_TU6NamIJdvgwWdZ90VmOwBdRBxSL70VgC4sILwc
To fix your Playstore issue, remove any Playstore updates you have, then download and install the latest version from here: https://www.apkmirror.com/apk/google-inc/google-play-store/
Click to expand...
Click to collapse
Playstore is fixed. Got that done last night.
Now I have another issue that I am about to butt heads with.
"Emergency calls only"
BS My bill is paid what is with these jackasses at AT&T
Attacking it now.
---------- Post added at 02:04 AM ---------- Previous post was at 01:23 AM ----------
rlj4214 said:
Playstore is fixed. Got that done last night.
Now I have another issue that I am about to butt heads with.
"Emergency calls only"
BS My bill is paid what is with these jackasses at AT&T
Attacking it now.
Click to expand...
Click to collapse
It was like talking to Time Warner.
Reboot it.
I understand sir, just reboot it.
Something in their network failed.
So now that I'm off the roof.
The safestrap that you had a link to wouldn't run at all.
I mean it loads and looks like it works tells me that it is installed and that the recovery is installed but won't boot to recovery. That is with mine Safestrap-HLTE-3.72-kk-B01.apk
That is the same thing that happened with your version Safestrap-KLTEVZW-NCG-3.75-B03.apk
I finally unloaded everything and started over from 4.4.2 factory stock
order that I got to work was
towelroot
su
busybox pro
safestrap B03
uninstall safestrap B03
uinstall busybox and install it again
install safestrap B01
uninstall B01
restart busybox pro
install B01
And finally I got it to show up correctly and boot properly, recovery and all.
Everything installed but now........
It wants to "update again"
Every time it updates, it crashes the system and I start over.
Gonna try it one more time and then go back to rooted 4.4.2 probably if it doesn't work.
I wonder if Verizon is this bad.
It's like when I had Time Warner's all in one router modem. Crash o matic every time they "updated" something
Now with an Asus RT-68U and Motorola modem I'm fine.
Incorporated the stagefright fix I mentioned earlier and it got all but one file.
Shows good in Lookout but CCVE-2051-6602 shows up in Ziperium.
Just turned off auto mms for this second and see what AT&T screws up with their update her when it finishes.
It's been a long ugly day and has nothing to do with this but I'm tired.
Thank you very much for your post and your help.
Take Care
Could you upload a screen shot(s) of your modem and kernel version .
Verizons Note 3 doesn't have a locked bootloader. Just AT&Ts. Which is why we have to jump to get root and such
phlashb4k said:
Sorry guys work got the best of me. I just got permission from a couple of developers to re-do a thread that elaborates more into how to root, flash etc. So that will be up by the end of the week (hopefully). My method I will be posting is completely different than what I'm telling you here. Because my guide will let you flash an a single file using flashfire that will already have root, xposed, viper audio, + extras already installed and configured. What I'm posting below is the main method being used.
In the mean time:
Download and install Samsung Mobile Drivers http://developer.samsung.com/technical-doc/view.do?v=T000000117, Reboot before connecting your phone.
Download https://www.androidfilehost.com/?fid=95784891001615211 - This is a stock NC2 (Android 4.4.2) image you will flash to down grade from 5.0. (Temporarily).
Download Towelroot https://towelroot.com/tr.apk - This is towelroot, it exploits a vulnerability in android 4.4.2 that allows you to gain root without even rebooting your phone.
Download SuperSU https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip?retrieve_file=1 - You can of course user any superuser app. I am personally a big supporter of Chainfire and his applications.
Download Safestrap Safestrap-KLTEVZW-NCG-3.75-B03.apk http://forum.xda-developers.com/devdb/project/?id=4718#downloads - This will be your recovery.
Download Odin http://forum.xda-developers.com/showthread.php?t=2711451 Make sure it's version 3.10.0 and only download odin from that post please. There are obnoxious amounts of fake odin downloads that come up in a google search that may contain malicious code.
Don't forget Busybox https://play.google.com/store/apps/details?id=stericson.busybox&hl=en
Also download any ROM you want to flash, BEFORE doing this. Unless of course you want to stay on rooted 4.2.2
----
0. Backup. Back up everything.
1. Place Towelroot, SuperSU, Safestrap, and Busybox on your SD card.
2. Bring your phone into download mode. (Power Button+Volume Down+Home Button)
3. Connect your phone to your computer using usb. (Back of the computer usb is always better)
-Make sure you installed the Samsung Drivers
4. Bring up odin and place N900AUCUCNC2_Full_Odin_Tar.tar.md5 file in the AP slot. (Odin might hangup and freeze for a minute. It's normal, don't click or do anything, just wait.)
5. Auto Reboot and F. Reset Time on odin should already be checked. Just make sure.
6. Under ID:COM on odin, it should read 0:[COM4] in light-ish blue color.
7. Odins message should read <ID:0/004> Added!!
--Numbers might be different for each person.
8. Click Start and wait a while. After 15-20 minutes your phone will eventually boot into Android 4.4.2
And in this exact order:
9. Install Towelroot and click 'make it rain'
10. Install SuperSU, Be sure to disable knox when it asks. If it hangs at all just force close SuperSU and try again.
11. Install Busybox
12. Install Safestrap
Done.
When you want to flash a ROM simply place it on your SD card and flash it using Safestrap. Make sure when flashing that the ROM comes with the OC1 kernel. If it doesn't you'll need to flash it after flashing the ROM.
As I said above I'm going to be posting an entire thread this week dedicated to rooting, flashing, and working with this phone. It's going to have the most updated information that I have and an easier and quicker method that doesn't require Safestrap. I'm going to ask mods and hopefully it will get a sticky.
Click to expand...
Click to collapse
Yea!!!
It updated and just said it failed but didn't crash the phone.
I'll have a beer now.
It looked like it was a KNOX update which is disabled.
Score one for the good guys. me me me me me
Thank you so very much for your help and putting up with me.
Have a great evening,,, and a beer.
screenshot you requested
phlashb4k said:
Could you upload a screen shot(s) of your modem and kernel version .
Verizons Note 3 doesn't have a locked bootloader. Just AT&Ts. Which is why we have to jump to get root and such
Click to expand...
Click to collapse
So the Verizon is easier to deal with? I just was looking at the BOUNTY for a Verizon note 4 and thought it might have been more of a pain
Sorry for the Delay I have 3 Great Pyrenees a Catahoula and 2 domestic short hair cats the were rioting to be fed.
SM-N900A
Hi, are my ROM choices pretty limited because the ATT phone has to run on OC1 kernel? Will most of the popular ROMs from the other Note 3 threads run on OC1?
Thanks, Mike
phlashb4k said:
Absolutely. I just arrived at work or I would post a full detailed guide, but here's the run down.
You have to downgrade from 5.0 (OC1) to 4.2.2 (NC2).
Once you've done that, root with towelroot.apk, install SuperSU (I prefer chainfire), then install Busybox, (I prefer Stephan Erickson) and then finally, install Safestrap Recovery V3.75.
Then boot into Safestrap recovery, wipe/factory reset, and then flash the ROM you want.
I would gladly post links to everything but as I said, I'm at work. If nobody else does before I clock out. I'll definitely help you out.
Click to expand...
Click to collapse
Supernoob question. I plan on doing this soon with my new note. However, I was wondering if the hotspot is automatically unlocked in 4.2.2. or do I need to download a special rom for that? thanks
Anybody know how to insall Xposed on Android 5.0? or have the link of the working one?
Thanks plashb4k, did this last night and it worked out great! I have a couple of questions though. (i'm completely new to this.) First, how can I disable Device Management from the phone? Now it is always in the Notification panel saying there is a new update. Secondly, are there any roms you recommend that work with android 4.4.2 really well? Thanks.

moto x pure 6.0 mm ( root )

Tried everything flashing every supersu via twrp and just gets stuck at the moto logo. Tried systemless root and did the same thing. So thinking it was my kernel and flashed elementalx moto kernel ( frankenclark ) then tried to flash supersu once again with the same fail and noticed with that kernel I lost my wifi connection but ran it anyways but failed. After much forum browsing and that supersu just isn't for the MXPE I even went as far as kingroot to achieve root then slap supersu to keep root like I did with my kindle fire. I'm pretty lost for words here. I'm previously running resurection remix and works flawless but I do really like the original setup. Ps tried the stock rooted roms and they was a lil off and kept trying to ota update but failed because my bootloader is unlocked so I had to uninstall it. Just looking to root the original rom so I can keep all the moto apps. Looking forward to hearing the ideas. Thanks in advance.
Wow... So I assume you flashed back to pure stock?
Rooting is not difficult, there is only 2 ways to do it, either flash SuperSU 2.62-3 beta or the latest stable version with the "echo" command for systemless installations. Look at this thread (note the pictures in the OP are of my XT1575, I fudged a little) but the method is identical. If it doesn't work, no offense, but your not doing something right.
I have both pure stock in a restore and resurection remix in a restore which is pretty much my daily because the active display drives me nuts. And supersu 2.6.2 I haven't tried yet but the SR supersu I've flashed via twrp with the stock kernel and ( frankenclark ) kernel and it responded the same stuck at moto. I've flashed it via windroid toolkit also it shows it's installing without any failure but on boot up she says no way. And I've updated the toolkit to it's newest version and still ends up stuck at moto. I'm sure I'll figure it out and get it. And no offense on doing something wrong it's been known to happen. Some lg double tap to wake the screen would be nice over the active display.
fastjohnson said:
I have both pure stock in a restore and resurection remix in a restore which is pretty much my daily because the active display drives me nuts. And supersu 2.6.2 I haven't tried yet but the SR supersu I've flashed via twrp with the stock kernel and ( frankenclark ) kernel and it responded the same stuck at moto. I've flashed it via windroid toolkit also it shows it's installing without any failure but on boot up she says no way. And I've updated the toolkit to it's newest version and still ends up stuck at moto. I'm sure I'll figure it out and get it. And no offense on doing something wrong it's been known to happen. Some lg double tap to wake the screen would be nice over the active display.
Click to expand...
Click to collapse
It sounds like the install script for SuperSU is not doing a systemless install...
So you are flashing stock, booting at least once (this is required), the open TWRP and allow changes to system (In mounts make sure Mount System Read-Only is NOT checked), go to Advanced - Terminal and enter "echo SYSTEMLESS=true>>/data/.supersu" and press enter, then go to Install and select the SuperSU zip file and install it. It should clearly say it is doing a system-less install, patching boot image, etc. as shown in the first post of the link I shared a couple posts previous.
OK I tried this info word for word and tried multiple times and its still gets stuck on the moto logo, I don't get it.
I don't know... it's a puzzler.
2.62-3 and stop using toolkits.
lafester said:
2.62-3 and stop using toolkits.
Click to expand...
Click to collapse
I'm using twrp to obtain the root like specified. But I'll try adb commands and see if the version you mentioned will do it. I appreciate the help.
fastjohnson said:
I'm using twrp to obtain the root like specified. But I'll try adb commands and see if the version you mentioned will do it. I appreciate the help.
Click to expand...
Click to collapse
Well that worked perfectly the first try I used those terminal commands with that version SuperSU it rooted and booted right up like normal and started asking the SuperSU adb shell permission banners. Perfect guys maybe this thread will help some other poor soul to get root. Awesome advice that works. Thank you.
fastjohnson said:
Well that worked perfectly the first try I used those terminal commands with that version SuperSU it rooted and booted right up like normal and started asking the SuperSU adb shell permission banners. Perfect guys maybe this thread will help some other poor soul to get root. Awesome advice that works. Thank you.
Click to expand...
Click to collapse
Yeah, glad it's working... Did you read through the link I posted earlier? The 2.62-3 method was clearly described in the second post under Alternative Methods.
acejavelin said:
Yeah, glad it's working... Did you read through the link I posted earlier? The 2.62-3 method was clearly described in the second post under Alternative Methods.
Click to expand...
Click to collapse
No actually I didn't see it, lol probably would have helped made me not look dumb. Buy who am I kidding you guys love flexing you rooting muscles..
Deleted.

Categories

Resources