Database Users

[ROOT][XT1069][Lollipop] SuperSU v2.39 Roots Lollipop'd XT1069

Hey there guys,
I know there's been a lot of fuss about Rooting Lollipop on XT1069 (BR), so I just wanted you guys to know that I just flashed the latest BETA of SuperSu using TWRP on my XT1068 running XT1069(BR) Lollipop firmware (using the TWRP Backup by droidjbc) and there was no bootloop caused.
So if you are like me and you've been holding back cause of a buggy root process, I just tried it and I didn't get any boot loop. (The first boot was long though, ~around 6-7 mins)
DISCLAIMER: This post is based on my experience with the latest beta, I can assure no guarantee that it'll be the same for you...
After reading the above disclaimer if you're going for it... Here's the links to latest SuperSu Beta v2.39.
[BETA][2014.12.10]SuperSU v2.39 Thread | [BETA][2014.12.10]SuperSU v2.39 Download Page
INSTRUCTIONS:
-Download BETA-SuperSU-v2.39.zip file from above
-Copy to Internal Storage of your Device
-Restart Device in Recovery Mode (Preferably TWRP)
-Select Install and choose the BETA-SuperSU-v2.39.zip
-Swipe to Install
-Done
Click to expand...
Click to collapse
Hope this helps...
UPDATE: Users have tested this version and have posted that it is working successfully. Proof: Link

Now everyone is going to test this and get bootloops! sorry Im friend this does not work! Please Delete before everyone tries and has to restore! you maybe trying to help but you are causing more problems than helping. Everyone seems to want to be first without having any real experience which leads to even more problems for the forums

TamatiG said:
Now everyone is going to test this and get bootloops! sorry Im friend this does not work! Please Delete before everyone tries and has to restore! you maybe trying to help but you are causing more problems than helping. Everyone seems to want to be first without having any real experience which leads to even more problems for the forums
Click to expand...
Click to collapse
You do have a valid point, but I did clearly mention a DISCLAIMER! If thats the case, then most tutorials and guides in the forum have a potential for Bootloops, Even then users are excited by the little chance that they might get lucky. For e.g., the Lollipoping method using TWRP, the method is working, even then users get boot loop.
Besides, THIS IS XDA!!!

Thanks

KrishnaSagar said:
You do have a valid point, but I did clearly mention a DISCLAIMER! If thats the case, then most tutorials and guides in the forum have a potential for Bootloops, Even then users are excited by the little chance that they might get lucky. For e.g., the Lollipoping method using TWRP, the method is working, even then users get boot loop.
Besides, THIS IS XDA!!!
Click to expand...
Click to collapse
This was tested and it has bootloops! So it would help more people removing this post then keeping it open for more people to test and get bootloops

TamatiG said:
This was tested and it has bootloops! So it would help more people removing this post then keeping it open for more people to test and get bootloops
Click to expand...
Click to collapse
I TESTED IT BEFORE POSTING! But as you said, this could be a Hit or Miss. Anyways since you pointed this out, I have Reported my Thread for Removal. I don't want any User to get Bootloops (I myself got Bootloop from v2.38) because of my Thread.
Anyways Thanks!

Sorry to say but I also got bootloop with v2.39.
In case anyone didn't realize the easy way to get out of bootloop caused by SuperSU on the BR xt1069 firmware is to boot into recovery, clear dalvik and cache. Then it will boot up (although it can take 6 or 7 minutes).

This version has been confirmed to be working for many users. Please check this link:
Proof:
http://forum.xda-developers.com/showpost.php?p=57505261&postcount=287
Click to expand...
Click to collapse
Also, Everything posted in XDA forums has a hidden potential for causing bootloops, I have added the necessary disclaimer. It is upto you to flash your device. I FLASHED THIS, IT WORKS. MANY OTHERS HAVE ALSO FLASHED THIS AND GOT IT WORKING! SO DON"T WHINE!

Closed by OP request.

Root Asus Memo Pad 176 on lollipop .36 newest firmware plus Xposed

***DISCLAIMER***
If done incorrectly, this can soft brick your device. I take no responsibility for this, and if you're unfamiliar with rooting android I suggest reading up before attempting. There are threads to fix your tablet if this goes sideways, but if this doesn't work I personally can't promise I can help you.
I used this method two days ago, and would like to thank jerbear294 for providing me with the information. I didn't come up with this, I just want to help others looking for root.
Hello guys
First, apologies if this is a redundant thread. All the root methods I've seen in individual topics seem outdated, and I just wanted to make this quick guide to help people from having to scan through pages of information to learn how to root these things. This method works on firmware WW_V12.10.1.33_20150917, which is the current release as of this post.
Lets get to it!
Download
http://forum.xda-developers.com/android/development/intel-android-devices-root-temp-cwm-t2975096
(Navigate to page 1, for some reason it links to the last page)
Place it on your computer and unzip.
And the latest supersu .zip 2.46
https://download.chainfire.eu/696/supersu/
Which will be on your tablet.
Install the temp recovery to your computer, connect the tablet, make sure you enable adb (USB Debugging) on it in developer mode (Settings → about → software version → tap build number 7 times for developer mode). Once connected, run the exe in the .zip from the temp recovery.
Choose: TWRP HDPI portrait, T4.
Your device will boot into twrp recovery. Now navigate to the supersu.zip on your tablet, and install, and you should be good to go . Good luck, and happy rooting!
Thanks to everyone who developed these tools (especially Social_Design_Concepts), and XDA for providing a medium to relate them.
To run Xposed, go to http://forum.xda-developers.com/showthread.php?t=3034811
Choose 'xposed-v80-sdk21-x86', this is currently the only version I've had success with. Happy hunting folks!

404 page not found on the first link?

ThunderThighs said:
404 page not found on the first link?
Click to expand...
Click to collapse
Link fixed, thanks and my apologies

thank you a lot! you saved me a lot of browsing! :good:

I updated my me176cx directly from v17 to v33. No matter what I do, the rooting method you outline here doesn't work for me anymore. On v17 it worked first time, now it's a fail every time. No superuser app, no su binary. Any suggestions? I've reinstalled the v33 firmware (it was actually a nandroid backup posted by jerbear on androidfilehost).
Anyway, when I installed temp TWRP this time it asked me did I want to keep system read only - I answered no. Was that a mistake? Also, I went straight from v17 to v33, bypassing the v24 update completely. Was that the wrong thing to do?
Your help would be hugely appreciated, a life with an unrooted device is not one I care to contemplate.

seamo123 said:
I updated my me176cx directly from v17 to v33. No matter what I do, the rooting method you outline here doesn't work for me anymore. On v17 it worked first time, now it's a fail every time. No superuser app, no su binary. Any suggestions? I've reinstalled the v33 firmware (it was actually a nandroid backup posted by jerbear on androidfilehost).
Anyway, when I installed temp TWRP this time it asked me did I want to keep system read only - I answered no. Was that a mistake? Also, I went straight from v17 to v33, bypassing the v24 update completely. Was that the wrong thing to do?
Your help would be hugely appreciated, a life with an unrooted device is not one I care to contemplate.
Click to expand...
Click to collapse
I hear you. I'll be honest - I didn't so much Pioneer this method so much as succeed with it and then repost it to save people some time going through the threads on here :/
That said, I would ask jerbear if he has had this problem reported via his nandroid backup. Answering "no" in twrp was fine, if you said yes it would have been gimped and probably useless, so I doubt that's the problem. I would say it's the nandroid, but I've read people using it and nobody I remember mentioned a problem. In the meantime, try re downloading the backup and flashing it again, and then trying temp twrp and see if it works. I personally haven't tried jerbear's nandroid, so I can't speak on it's behalf
Sorry I don't have something more concrete, let me know what jerbear says and how things play out, and good luck

Opensystem said:
I hear you. I'll be honest - I didn't so much Pioneer this method so much as succeed with it and then repost it to save people some time going through the threads on here :/
That said, I would ask jerbear if he has had this problem reported via his nandroid backup. Answering "no" in twrp was fine, if you said yes it would have been gimped and probably useless, so I doubt that's the problem. I would say it's the nandroid, but I've read people using it and nobody I remember mentioned a problem. In the meantime, try re downloading the backup and flashing it again, and then trying temp twrp and see if it works. I personally haven't tried jerbear's nandroid, so I can't speak on it's behalf
Sorry I don't have something more concrete, let me know what jerbear says and how things play out, and good luck
Click to expand...
Click to collapse
Hey, thanks for the reply. Just to clarify, is this the file you downloaded and restored? https://www.androidfilehost.com/?fid=24052804347832070
Here's what I had to do: I had to create a folder (this folder I named with my device's serial no) as well as creating a folder inside that folder that I named after a nandroid backup that I'd done earlier. Then I placed all the files from the nandroid zip inside that (second) folder. Only then did the TWRP 'see' the backup. I did the usual system/cache/dalvik cache wipe and restored the nandroid without any hitch. You did that or something similar to get TWRP to restore the nandroid, right?
I wonder should I have taken the recovery log from my own nandroid and replaced jerbear's recovery log with it? I'm starting to confuse myself at this point I think..

seamo123 said:
Hey, thanks for the reply. Just to clarify, is this the file you downloaded and restored? https://www.androidfilehost.com/?fid=24052804347832070
Here's what I had to do: I had to unzip the file into a folder (this folder I named with my device's serial no) as well as creating a folder inside that folder that I named after a nandroid backup that I'd done earlier. Only then did the TWRP 'see' the backup. I did the usual system/cache/dalvik cache wipe and restored the nandroid without any hitch. You did that or something similar to get TWRP to restore the nandroid, right?
Click to expand...
Click to collapse
No sorry you misread: I never had to use that nandroid (or any on this tablet yet, all my updates .33 were in order and via ota) - I'm aware of it though and I've only heard good things so I'm not sure where the process might have broken down, outside maybe a corrupted download. That's why I recommended asking jerbear if he's heard of that problem from anyone, because it's a stock backup and I know tons of people have used it and supposedly rooted successfully using temp twrp. From what I can tell, you shouldn't have any problems...it sounds like you know what you're doing and did everything properly.
Can you revert to a previous version, and manually download .33 from https://www.asus.com/support/Download/28/6/0/23/3HzHuNmdcAgeMhJ1/32/ ? I assume there are no backups readily available, but the major xda thread on the 176 might have a couple older ones you can try.
I haven't done as much as a lot of pioneers with my tab, just update, root and install xposed. As such I can't really answer myself what the problem you're having is, just offer general advice I would try. Jerbear hopefully knows about what might be causing the root to fail

Opensystem said:
No sorry you misread: I never had to use that nandroid (or any on this tablet yet, all my updates .33 were in order and via ota) - I'm aware of it though and I've only heard good things so I'm not sure where the process might have broken down, outside maybe a corrupted download. That's why I recommended asking jerbear if he's heard of that problem from anyone, because it's a stock backup and I know tons of people have used it and supposedly rooted successfully using temp twrp. From what I can tell, you shouldn't have any problems...it sounds like you know what you're doing and did everything properly.
Can you revert to a previous version, and manually download .33 from https://www.asus.com/support/Download/28/6/0/23/3HzHuNmdcAgeMhJ1/32/ ? I assume there are no backups readily available, but the major xda thread on the 176 might have a couple older ones you can try.
I haven't done as much as a lot of pioneers with my tab, just update, root and install xposed. As such I can't really answer myself what the problem you're having is, just offer general advice I would try. Jerbear hopefully knows about what might be causing the root to fail
Click to expand...
Click to collapse
Hope I haven't misunderstood you here, but I'd tried installing the v33 from that thread when I was running v17 and didn't get anywhere with it - jerbear told me that restoring a v33 android backup was the only way to go. So even if I can revert back to v17 I'm kind of back to square one, really. I wonder if skipping the v24 update (which I couldn't flash anyway) is the reason behind my current woes though..
P.S. You got Xposed framework running on v33? I'm impressed, I couldn't even get it installed on v17, how did you do it?

Just chiming in to say this method worked for me and thanks a lot!
I was on firmware WW_V12.10.1.33_20150917, followed the instructions, and used root checker to confirm. Yep, rooted!
I did tap the keep read only button, more so on accident. Not sure what that does/did but I did find the restore defaults button. I don't know if that "fixed" anything or what but I didn't want to accidentally break something. Anyway, after that, I flashed SuperSU and was rooted.
Thanks again! :good:

seamo123 said:
Hope I haven't misunderstood you here, but I'd tried installing the v33 from that thread when I was running v17 and didn't get anywhere with it - jerbear told me that restoring a v33 android backup was the only way to go. So even if I can revert back to v17 I'm kind of back to square one, really. I wonder if skipping the v24 update (which I couldn't flash anyway) is the reason behind my current woes though..
P.S. You got Xposed framework running on v33? I'm impressed, I couldn't even get it installed on v17, how did you do it?
Click to expand...
Click to collapse
Yes the general for the memo 176 has a special working xposed, make sure you use that one. I'm a bit busy, but I'll link when I can glad you got it rooted

Joe_Bangles said:
Just chiming in to say this method worked for me and thanks a lot!
I was on firmware WW_V12.10.1.33_20150917, followed the instructions, and used root checker to confirm. Yep, rooted!
I did tap the keep read only button, more so on accident. Not sure what that does/did but I did find the restore defaults button. I don't know if that "fixed" anything or what but I didn't want to accidentally break something. Anyway, after that, I flashed SuperSU and was rooted.
Thanks again! :good:
Click to expand...
Click to collapse
Glad to help, xda is where it's at for community

OMG!!!!!!!! Finally!!! I'm so glad to read this post.... thank you!!! I've been searching a good method for months!
And yes, it works!!! xD

Delichi said:
OMG!!!!!!!! Finally!!! I'm so glad to read this post.... thank you!!! I've been searching a good method for months!
And yes, it works!!! xD
Click to expand...
Click to collapse
Hurray! Glad it worked out for you

seamo123 said:
Hope I haven't misunderstood you here, but I'd tried installing the v33 from that thread when I was running v17 and didn't get anywhere with it - jerbear told me that restoring a v33 android backup was the only way to go. So even if I can revert back to v17 I'm kind of back to square one, really. I wonder if skipping the v24 update (which I couldn't flash anyway) is the reason behind my current woes though..
P.S. You got Xposed framework running on v33? I'm impressed, I couldn't even get it installed on v17, how did you do it?
Click to expand...
Click to collapse
Hey sorry for the late response, work got crazy on me. I edited the original post to now include how to set up Xposed, for you or anyone else interested. Confirmed working on both .33 and .36

Hey guys!
Sorry for the off-topic but how is the new .36 firmware compared to .33? For me .33 sucked,all memory leaks , crashing apps, slow as hell,fortunately I got motherboard replacement and now I'm on KK again. Should I update to .36? What do you think?

dareas said:
Hey guys!
Sorry for the off-topic but how is the new .36 firmware compared to .33? For me .33 sucked,all memory leaks , crashing apps, slow as hell,fortunately I got motherboard replacement and now I'm on KK again. Should I update to .36? What do you think?
Click to expand...
Click to collapse
It's got less battery drain here, performance seems better too but that could just be a placebo

Opensystem said:
It's got less battery drain here, performance seems better too but that could just be a placebo
Click to expand...
Click to collapse
Thank you. Does upgrading to LP unlock 64 bit capability of the processor (Z3745)? I'd really appreciate it if you could answer me.

dareas said:
Thank you. Does upgrading to LP unlock 64 bit capability of the processor (Z3745)? I'd really appreciate it if you could answer me.
Click to expand...
Click to collapse
I'm not sure, we should be because of art runtime but I feel like our version is bootlegged to a degree

unable to mount /data, internal storage 0MB. How can I load the zip file?
It's probably because FDE. I used a external SD card instead

What LS997-compatible ROM contains *all* working LG Stock Apps?

So the whole reason I rooted this damn phone was to be able to install working stock apps. Not just the Music and Gallery apps either--ALL THE LG APPS. Which LS997-compatible 100%-working ROM can I flash and get them all, if any? I keep hearing one exists, but no one bothers sharing that info and when I search I find nothing.

Really? No one?

bgibson72 said:
Really? No one?
Click to expand...
Click to collapse
Look in the development section it's like the 5th one down has ls997 in the title

@bgibson72
Im the only person developing a STOCK LS997 rom currently.. It contains the LG base apps and all the removed ones that we didnt get shipped with out model . Includes a ton of extras as well, alternatively we have 3 or 4 aosp roms you can use, but make sure you use twrp and backup your efs before flashing as it tends to jumble your programming up and cause issues. Otherwise you can flash the stock rom the Dev who provided the dirty santa unlock method.
Theres a good bit of info here to locate everything you need to have a awesome experience with the LG V20!
My link
https://forum.xda-developers.com/v20/development/rom-ls997-stock-debloated-su-goodies-t3531923
READ THE ENTIRE FIRST 3 POSTS!!! A LOT OF TIME WENT INTO THIS TO CLEAR UP ANY CONFUSION!
I also itemized a list of 15 or so mods and add-ons that we can use to increase our enjoyment with perspective links to their home locations and the devs that built and maintain them.

jerrycoffman45 said:
Look in the development section it's like the 5th one down has ls997 in the title
Click to expand...
Click to collapse
This one?
{ROMS}[LS997] Stock-ish Magisk+3minit+ModControl 3/10/17
Other than DirtySanta, this is the only other one with LS997 in the title on that page. I'll give it a shot, and thanks for answering.

Team DevDigitel said:
@bgibson72
Im the only person developing a STOCK LS997 rom currently.. It contains the LG base apps and all the removed ones that we didnt get shipped with out model . Includes a ton of extras as well, alternatively we have 3 or 4 aosp roms you can use, but make sure you use twrp and backup your efs before flashing as it tends to jumble your programming up and cause issues. Otherwise you can flash the stock rom the Dev who provided the dirty santa unlock method.
Theres a good bit of info here to locate everything you need to have a awesome experience with the LG V20!
My link
https://forum.xda-developers.com/v20/development/rom-ls997-stock-debloated-su-goodies-t3531923
READ THE ENTIRE FIRST 3 POSTS!!! A LOT OF TIME WENT INTO THIS TO CLEAR UP ANY CONFUSION!
I also itemized a list of 15 or so mods and add-ons that we can use to increase our enjoyment with perspective links to their home locations and the devs that built and maintain them.
Click to expand...
Click to collapse
Hey thanks--I was fairly sure this was the ROM in question. Thank you for providing this! I was hesitant to flash because I'm always a little skeptical about the amount of help I'll get should I get stuck. I'm not exactly a noob at this, but I have plenty to learn. It looks like you've done a lot of work to provide a positive experience, so I'll give it a shot and see how it goes. I promise to read and re-read the instructions on the first 3 posts, and to NOT bother you with questions that have already been addressed in the thread. . Thanks!!

bgibson72 said:
Hey thanks--I was fairly sure this was the ROM in question. Thank you for providing this! I was hesitant to flash because I'm always a little skeptical about the amount of help I'll get should I get stuck. I'm not exactly a noob at this, but I have plenty to learn. It looks like you've done a lot of work to provide a positive experience, so I'll give it a shot and see how it goes. I promise to read and re-read the instructions on the first 3 posts, and to NOT bother you with questions that have already been addressed in the thread. . Thanks!!
Click to expand...
Click to collapse
if you made it through dirty santa the rest should be cake. 99% of the issues i covered for people were
after going to AOSP and not having a backup of their programing info in their efs and having to find a way to
manually go in and fix each fd up piece.
The other is being on older software and downloading a OTA and rebooting with it in your internal storage.
This one causes a endless boot loop into twrp, so be advised to delete the update if your on older software or be prepared to
hit my post # 3 for fixes and be near a pc as you need to fastboot erase the fota and misc directories to resolve the boot loop. A twrp wipe will not fix it and restores etc wont either lol.
Otherwise theres now a lil over 100 pages of chatting and troubleshooting, fixes and things that have gone on, and mostly its all outdated as ive provided the fixes for 99% of everything in the latest version 7.5
Just be prepared to take 15-20 minutes for the phone to boot up the 1st time. My rom is deodexed, and the 1st boot is doing 298 things before you get to the optimization part. There is not boot animations as the phone will always have the static screen issue on reboots so i went ahead a placed a disabled command there to just save time/batt life. The setup wizard is stripped and only there to give you the notice its done booting and time to get to playing around.
Magisk is kinda finicy being its systemless design. It takes some time to get used to it, and be aware that some older apps that dont support exotic root or systemless root may not request root and not fully work. Titanium backup is one i know is getting attacked by googles app scanning and needs to have that turned off before it will work, most of my apps have a option to set "force root" so it asks for a root request regardless if it understands MagiskSu's root methods.
just some food for thought. Hope everything goes well, and there is a ton of people on the forum here that have great knowlege and can help with troubleshooting issues you may have

Team DevDigitel said:
if you made it through dirty santa the rest should be cake. 99% of the issues i covered for people were
after going to AOSP and not having a backup of their programing info in their efs and having to find a way to
manually go in and fix each fd up piece.
Click to expand...
Click to collapse
Yeah, I didn't have many problems there, although I did get stuck in the TWRP loop once.
The other is being on older software and downloading a OTA and rebooting with it in your internal storage.
This one causes a endless boot loop into twrp, so be advised to delete the update if your on older software or be prepared to
hit my post # 3 for fixes and be near a pc as you need to fastboot erase the fota and misc directories to resolve the boot loop. A twrp wipe will not fix it and restores etc wont either lol.
Click to expand...
Click to collapse
I am on the ZV3 version of the software. I do have the ZV5 update in my cache folder--are you saying it's a good idea to delete the update.zip file?
Otherwise theres now a lil over 100 pages of chatting and troubleshooting, fixes and things that have gone on, and mostly its all outdated as ive provided the fixes for 99% of everything in the latest version 7.5
Click to expand...
Click to collapse
That's what I like to hear! :good:
Just be prepared to take 15-20 minutes for the phone to boot up the 1st time. My rom is deodexed, and the 1st boot is doing 298 things before you get to the optimization part. There is not boot animations as the phone will always have the static screen issue on reboots so i went ahead a placed a disabled command there to just save time/batt life. The setup wizard is stripped and only there to give you the notice its done booting and time to get to playing around.
Click to expand...
Click to collapse
Appreciate the heads up. Familiar with the long boot process from DS, lol.
Magisk is kinda finicy being its systemless design. It takes some time to get used to it, and be aware that some older apps that dont support exotic root or systemless root may not request root and not fully work. Titanium backup is one i know is getting attacked by googles app scanning and needs to have that turned off before it will work, most of my apps have a option to set "force root" so it asks for a root request regardless if it understands MagiskSu's root methods.
Click to expand...
Click to collapse
Magisk is a new animal for me, as I've had zero experience with it. I do have Titanium Backup installed, so I'll make a mental note on that.
just some food for thought. Hope everything goes well, and there is a ton of people on the forum here that have great knowlege and can help with troubleshooting issues you may have
Click to expand...
Click to collapse
Thanks again--I appreciate your hard work and dedication to this!

bgibson72 said:
Yeah, I didn't have many problems there, although I did get stuck in the TWRP loop once.
I am on the ZV3 version of the software. I do have the ZV5 update in my cache folder--are you saying it's a good idea to delete the update.zip file?
YES, dont boot into twrp until you remove it, or its back into the twrp loop you go hehe
Click to expand...
Click to collapse

Team DevDigitel said:
bgibson72 said:
Yeah, I didn't have many problems there, although I did get stuck in the TWRP loop once.
I am on the ZV3 version of the software. I do have the ZV5 update in my cache folder--are you saying it's a good idea to delete the update.zip file?
YES, dont boot into twrp until you remove it, or its back into the twrp loop you go hehe
Click to expand...
Click to collapse
Weeeeeeeeeeeeee!!!
Will do!
Click to expand...
Click to collapse

Just received insurance replacement H91810j, root strategy?

So I had to get a warranty replacement phone about 3 weeks ago and got stuck on 10r with no chance of root (was following the LAF thread but I guess that hit a pretty hard wall; little above my technical knowledge but I think that's the current end result) and for the second time in my life I broke a screen (before I'd even sent back the original phone from the warranty swap). I was all kinda pissed at myself for trashing a brand new to me phone, but the silver lining may be that the insurance replacement phone came with H91810j so root may be back on the table.
I apologize for asking something I could probably find from RTFF but I've been out for a while and it's a little complex to find info on root/upgrade path for such an older build. So the question is, what do I do now? Root immediately? Upgrade to a newer build but pre-10p then root?
Any help is much appreciated (including "hey dumbass, here's the thread that answers this exact question, why didn't you RTFF?!?!").

Hey erikk,
I believe you can still root it using recowvery, but there might be a few extra steps as per this post: https://forum.xda-developers.com/v20/how-to/instruction-to-root-h918-10i-t3536472
As long as your Anti-rollback version still shows 0 you'll be okay to go ahead and root.
If you don't mind - can you share with me the files in your data/ipsec/wo folder? I'm trying to figure out T-Mobile VoLTE/WifiCalling on an H990DS.
Thanks!

So I got impatient and RTFF and was able to find what I thought was the best way through, so I thought I'd help anyone else who gets into the same situation in the future.
I first rooted on H91810j following this:
https://forum.xda-developers.com/v20/development/h918-recowvery-unlock-v20-root-shell-t3490594
This thread (https://forum.xda-developers.com/v20/development/lg-h918-t-mobile-one-click-recowvery-t3491969) has a bundled, do it for you version of the above, but the above was updated after the all-in-one thread and personally I felt more comfortable using the non-simplified method. But if you don't understand ADB or the stuff in the manual version, the do it for you version is probably better for you.
I then upgraded to 10r using the following:
https://forum.xda-developers.com/v20/development/rom-h91810q-stock-rom-twrp-flashable-zip-t3681312
I will mention one thing that was a tad bit unclear in the guide that freaked me out at the time. You need to put the latest SuperSU or no-verity-opt-encrypt and the H91810r img on your microsd card and in the phone BEFORE starting. Step 3 has a step:
Flash the latest zip from https://build.nethunter.com/android-tools/no-verity-opt-encrypt/ to turn off forced encryption at boot and allow you to boot a modified system. If you're flashing SuperSU.zip, it will also do this for you so this won't be necessary.
Warning: If you don't flash either no-verity-opt-encrypt or SuperSU, you will probably end up in a horrifying never-ending boot loop of "corruption"!
Click to expand...
Click to collapse
Well I got there and I hadn't put the files on my SD card and I flipped out thinking I was screwed; the sd card wasn't even inserted in the phone. I was able to put the files on and hot insert the sd card but I was terrified I'd just bricked my second brand new replacement.

Boxy52 said:
Hey erikk,
I believe you can still root it using recowvery, but there might be a few extra steps as per this post: https://forum.xda-developers.com/v20/how-to/instruction-to-root-h918-10i-t3536472
As long as your Anti-rollback version still shows 0 you'll be okay to go ahead and root.
If you don't mind - can you share with me the files in your data/ipsec/wo folder? I'm trying to figure out T-Mobile VoLTE/WifiCalling on an H990DS.
Thanks!
Click to expand...
Click to collapse
Hey Boxy, thanks for the reply. I actually had my just previous reply almost completely written and hadn't submitted it but your reply jogged me to finish it.
I'm happy to share the files with you if they'll help now that they're the 10r versions?

erikk said:
Hey Boxy, thanks for the reply. I actually had my just previous reply almost completely written and hadn't submitted it but your reply jogged me to finish it.
I'm happy to share the files with you if they'll help now that they're the 10r versions?
Click to expand...
Click to collapse
Hey, glad it worked out!! Sorry I didn't get to your thread sooner... looks like you found better info than I did anyway I actually bricked an H918 that was on 10q before I got this H990DS as a replacement... so I was certain you'd be okay if you weren't on 10p or 10q, haha.
Yes, please! I'd love if you could dump the files for me. Can you also check what the permissions are in that folder? Thanks! Also, if you could show me your APNs.

SM-S727VL Root and Recovery

I cannot for the life of me get this phone rooted or a recovery installed. Odin always fails and ADB doesn't recognize the device. Does anyone have any info on rooting this device? I really just want to at least be able to update this thing to nougat.

Nobody knows much about this device since it's not that popular. Some team named TWRP builder built a twrp for the SM-S727VL but it cannot be flashed even when converting to .tar.md5 or .tar.
Also I believe the bootloader on this phone is locked and CROM service does not function (if I am correct) on this device. CROM service will show it being unlocked but it seems to be lying to you.

djared704 said:
Nobody knows much about this device since it's not that popular. Some team named TWRP builder built a twrp for the SM-S727VL but it cannot be flashed even when converting to .tar.md5 or .tar.
Also I believe the bootloader on this phone is locked and CROM service does not function (if I am correct) on this device. CROM service will show it being unlocked but it seems to be lying to you.
Click to expand...
Click to collapse
Well that figures, im willing to use my device to work at it if anyone knows where to start.

I have 3 of these... not a noob but not an expert...say Pre-elite lol. I'm wanting to learn how to go further than use everybody else's solutions to root my phone's if somebody can give me some advice as to where to start as in I know how to root put it that way I was one of the people back in the day with the Evo when it was actually difficult no worries most of them were fine but these files we keep flashing these ROMs these kernels these firmwares where does one start when a phone like this 727 VL is obscure supposedly and nobody is doing anything to be able to root them I have everything that I need I'm sure and if I don't get it. It's somebody point me to a person or in the right direction to get started on what I need to due to learn how to write for I mean what where's the first step on these I've always just use everybody else's files. If that even makes any sense to anybody and anybody can give me a hand or show me the right way I'd be willing to do the work from there on I just need somebody to stick up a finger and say go there.... I mean if we have a twrp written, and we have OEM unlock, then why can't one of us do this I've been around long enough I've read long enough I've never once posted in these forms but I've read them daily... I know I got the skills I just need to know which ones to use. Odin fails like he said, fastboot for some reason still won't recognize, I actually made it one step with one of mine but it has to be a little incorrect because the only thing noticeable is it pops up with vo LTE at the top instead of just regular LTE like this one I'm on now. I was able to flash it with Odin believe it or not with what seems to be possibly just stock S727VLUDU2AQG1_ENG_boot_boxwares.tar
BUT the point is I was able to flash it with Odin and also it did change something because my phone now says there's been unauthorized changes and it wants me to restart it all the time so it can correct itself however it does not, it stays whatever it is, yes I know this is pretty vague however I got to the point where I just started trying anything on one of these phones to see if I could get any kind of anything to work and it did.. kind of.
I will say the USB drivers that's you find every where now do not work you have to go back to looks like version 1.5.5 1.0 SAMSUNG-USB-Driver-for-Mobile-Phones-15510.
With these drivers fast boots if I remember correctly will recognize it when you do fastboot devices however it still hangs on waiting on device. I'm sure I got more information my brains just a little foggy at the moment it is like 3 in the morning and I hope I didn't break any rules posting.
I did try flashing from SD card with no success yet nothing at all just error after error. I have tried twrp however it's supposed to be for this 727 VL I'm sure it's the same one everybody's got because it's only in one place that I've found but it comes up twrp-3.2.1-j7popqltefnvzw-201 and it will not flash.
I realize I have been pretty obscure however there's no reason why if all 5 of us with this VL stick together we can't get it rooted because I'm not going to give up LOL

Keep up the good work
I to have a j7 sky Pro, we need to figure out how to get this bootloader unlocked I would love the links to any from builds or twerp builds you have for this j7POPQLTEFNVZW

twrp
[email protected] said:
I to have a j7 sky Pro, we need to figure out how to get this bootloader unlocked I would love the links to any from builds or twerp builds you have for this j7POPQLTEFNVZW
Click to expand...
Click to collapse
I have a twrp that I managed to find on the internet but i have heard that it was for an older version of the phone. meaning it has to be updated somehow. I do know that the phone had a security patch update on June 1, 2018. I am currently trying to figure out if how to update the twrp or something, but I think I might need a little assistance. Because I am no expert ROM developer or anything of the sort but I am trying to learn, so I can eventually build a custom ROM for this phone.

Masterx4020 said:
I have a twrp that I managed to find on the internet but i have heard that it was for an older version of the phone. meaning it has to be updated somehow. I do know that the phone had a security patch update on June 1, 2018. I am currently trying to figure out if how to update the twrp or something, but I think I might need a little assistance. Because I am no expert ROM developer or anything of the sort but I am trying to learn, so I can eventually build a custom ROM for this phone.
Click to expand...
Click to collapse
Like I said in another thread about this issue, We are not to that bridge yet. The bootloader is locked and we cannot flash it yet.

Justin1198 said:
Like I said in another thread about this issue, We are not to that bridge yet. The bootloader is locked and we cannot flash it yet.
Click to expand...
Click to collapse
Okay, have you tried anything to unlock it. If so can you tell me what you have tried so I can see what doesn't work.

Masterx4020 said:
Okay, have you tried anything to unlock it. If so can you tell me what you have tried so I can see what doesn't work.
Click to expand...
Click to collapse
See post #11 on thread https://forum.xda-developers.com/galaxy-j7/how-to/sm-s727vl-analysis-partition-table-t3858632

Justin1198 said:
See post #11 on thread https://forum.xda-developers.com/galaxy-j7/how-to/sm-s727vl-analysis-partition-table-t3858632
Click to expand...
Click to collapse
Is there a way to tell if the bootloader is locked? (Sorry if I am asking noobish questions. I am just trying to learn.)

You can tell the Bootloader is locked because you get “Secure Check Failed” if you try to flash anything that has been modified. For example; The TWRP recovery file. We need root to bypass the Bootloader.

Allow

allow what
I feel like you're telling me to do something that's way over my head cuz I do not understand what do you mean by allow

I have read write access to root files now !!
I can now access all files on my 2nd of 3 J7s. I am attaching pics. When I try to duplicate and copy on my other J7 ,the factory ones, I get check file permissions access denied. However I've passed it on this one particularly. It also now gives me a security notice on the lock screen of unauthorised actions have been detected please restart phone to correct them. However even when you restart the phone it stays so it isnt temporary. I have actually even going to factory reset to see believe it or not it stays. So the next step would be one in which I need some input to know which files I need to modify to be able to install BusyBox Superuser and from their custom recovery excetra and we're in I believe correct me if I'm wrong.
Can't post pics yet so someone get at me here and I will send them to you to post. Or on my FB at Mighty.Whity.Titan

You can send them to me if you like.

No problem how do I not familiar with these forms
josh0426 said:
You can send them to me if you like.
Click to expand...
Click to collapse
One b a d d a d d i e i o and that said the old Google Mail you know if you want to send me an email I can forward them all to you cuz I can't post them and that's about the best I can do

Pre-Elite said:
One b a d d a d d i e i o and that said the old Google Mail you know if you want to send me an email I can forward them all to you cuz I can't post them and that's about the best I can do
Click to expand...
Click to collapse
[email protected]

Pre-Elite said:
I can now access all files on my 2nd of 3 J7s. I am attaching pics. When I try to duplicate and copy on my other J7 ,the factory ones, I get check file permissions access denied. However I've passed it on this one particularly. It also now gives me a security notice on the lock screen of unauthorised actions have been detected please restart phone to correct them. However even when you restart the phone it stays so it isnt temporary. I have actually even going to factory reset to see believe it or not it stays. So the next step would be one in which I need some input to know which files I need to modify to be able to install BusyBox Superuser and from their custom recovery excetra and we're in I believe correct me if I'm wrong.
Can't post pics yet so someone get at me here and I will send them to you to post. Or on my FB at Mighty.Whity.Titan
Click to expand...
Click to collapse
Can you please share the method that you used to gain read/write access? If you indeed have temp access, I can make it permanent also what firmware build are you on?

Absolutely
I'm not home right now but I'm headed there I'll be there in a couple hours I can if somebody wants to give you their email or email me because I can't post links or anyting I have the file that I used the wrong and I have the driver for Samsung for Odin that I used which I think I've mentioned in my original or previous post and by the way it is not temporary. This is permanent. I did a factory reset and it stays. I just need to know which permissions which file to go to to get my Superuser installed because it's still will not let me install that. But email me or tell me how to send it on here or something that way I can let you guys know or give you guys what I got. I'll tell you this I did not flash it with a v l ROM. I flashed it using a Verizon ROM the only thing that didn't work was my wife I which I think I originally and said back when I made my first comment on this thread I haven't done anything else I set my phone down and it was done clear back there I just didn't realize it. But it is not a VL ROM it's a Verizon ROM a v not a straight talk and my wife I would not which turned out to be something unrelated. I'm in no way trying to keep this from anybody because I know just how much we all want these damn things. But I would sure love to finish the job that I started but I do not mind handing over what I've got.
---------- Post added at 02:53 AM ---------- Previous post was at 02:40 AM ----------
Josh I just emailed you six pictures I just now seen your email in your post and Justin as soon as I get home if you can shoot me an email or get in contact somehow or I can send you everything I got so far once I get there

Here are the pictures