yashsingh1/xdaforums huggingface dataset:
[Android General] j1gga84:
Hello,

for me this does not work or only partly..

I cannot restore apps via titanium backup from my external SD, allthough I did the workaround with menu - settings - backup folder location and set it to DocumentProvider storage.

When I do so I can backup my apps and data to external SD but NOT restore, what can I do?

I can only restore data but not the App itself..

Setting SElinux to permissive also does not work

I have a screenshot of the logcat in attachment, maybe someone could help me..

I have the problem on Resurrection Remix 5.6.4, BlissPop, AICP11... on CM12.1 it is working..

Thanks & regards
[Android General] paolo200:
Hi

The same thing happened to me

Did you find a fix?
[Android General] j1gga84:
Yes, it works now.

You have to do the same steps mentioned above but you have to create a new folder inside the existing titanium backup folder, put all files inside this folder and then it should work.

Like this storage/external sd/titanium backup/titanium backup

There is also a video on YouTube somewhere but I can't find it anymore..

Regards

Gesendet von meinem SM-G900F mit Tapatalk
[Android General] dragonden4:
Thanks very much. This method is the only one that truly worked!!!:)
[Android General] kykemejia:
Worked!
[G Pad 8.3 General] roirraW "edor" ehT:
Rooting VK810 official stock release 11A (11A is chosen for two reasons: 1. because it's easiest to root with the Stump app and 2. because on anything newer than 11A, you'd have to manually downgrade the bootloader before being able to install TWRP the first time):

1. On the tablet, download the Stump app from http://xdaforums.com/lg-g3/orig-development/root-stump-root-lg-g3-sprint-verizon-t2850906

Credit and thanks @jcase, IOMonster , @autoprime and @PlayfulGod. Credit and thanks azureflux for the music although personally I turn the volume down all the way.

2. Install the Stump app you downloaded. Android should prompt you that it's an app from an unknown source since you didn't download it from the Play Store. It should direct you to the Security Settings option "Unknown sources" which you should checkmark and then attempt again to install the Stump app.

3. Launch the Stump app.

4. Turn the volume all the way down if you want because the music can be annoying for the duration necessary to root the VK810.

5. Choose "Grind".

6. Choose "Brute Force".

7. On the VK810, it can take up to 20 minutes at which time the Stump app should say to reboot the device to implement the root.

8. Once the device is rebooted, go to the Play Store and install SuperSU from https://play.google.com/store/apps/details?id=eu.chainfire.supersu&hl=en

Alternatively you can download the latest non-beta SuperSU zip from http://download.chainfire.eu/supersu (XDA thread with this link at http://xdaforums.com/showthread.php?t=1538053), extract the zip and install the SuperSU app, or the latest Beta version from a link in @Chainfire 's thread at http://xdaforums.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133.

You'll also need this SuperSU.zip for step 8 of the fourth post "Flash to the latest stock ROM so that you can have it with root".

Credit and much thanks to @Chainfire !!!

9. Launch SuperSU, confirm the prompt to update binaries.

Installing the initial (necessary) TWRP v2.7.0.1 and updating it to the latest TWRP v2.8.7.0: Next post.
[G Pad 8.3 General] roirraW "edor" ehT:
Flash to the latest stock ROM so that you can have it with root:

1. Download my ROM from my signature at the bottom of this post. I use ADM "Advanced Download Manager" from the Play Store at https://play.google.com/store/apps/details?id=com.dv.adm&hl=en, especially for downloading larger files like ROMs.

2. Check the MD5 Hash of the ROM zip:

2A. Copy (to the clipboard) the MD5 hash that I have in the filename of the ROM zip you downloaded in step 1 above.

2B. Install [MENTION=2693923]scary alien[/MENTION] 's "AFV File Verifier for Android" from the Play Store at https://play.google.com/store/apps/details?id=sa.afvx&hl=en.

2C. Run the AFV app.

2D. Choose "Input checksum for comparison".

2E. Paste the MD5 hash previously copied to the clipboard in step 2A above.

2F. Choose "Select File".

2G. Navigate to where you have the ROM zip.

2H. Long-press on the ROM zip and choose "Calc MD5 Checksum".

2I. When it's done calculating the MD5 hash of the ROM zip, it'll automatically compare it to the MD5 hash you pasted in step 2E above.

If the hashes match, the downloaded ROM zip is non-corrupt. If the hashes don't match, you have to re-download the ROM zip.​

3. Optionally download one or more of my debloat zip files in the third post of my ROM thread in my signature below. If you don't flash my "no OTA" debloat zip, then don't take any OTAs you get offered if there are ever any more, or you might get soft bricked, which I won't go into recovering from here.

4. If you didn't already do so in step 8 of the second post "Rooting VK810 official stock release 11A", download the latest non-beta SuperSU zip from http://download.chainfire.eu/supersu (XDA thread with this link at http://xdaforums.com/showthread.php?t=1538053) or the latest Beta version from a link in [MENTION=631273]Chainfire[/MENTION] 's thread at http://xdaforums.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133.

5. Copy/move anything you want to keep from internal storage like the files you downloaded in the previous sections.

6. I strongly suggest wiping everything from TWRP (Data, Cache, System, Dalvik and Internal Storage). Wiping all of these things, especially if you use my debloat zip(s) will clear up garbage/folders that were left behind by previous bloat.

7. Flash my ROM.

8. Flash SuperSU.zip (downloaded in step 4 above). This step is VERY IMPORTANT if you want to get back into custom recovery without having to re-flash a stock ROM and go through the whole process again.

9. Optionally flash one or more of my debloat zip files. If you don't flash my "no OTA" debloat zip, then don't take any OTAs you get offered if there are ever any more, or you might get soft bricked, which I won't go into recovering from here.

Flashing the debloat zip(s) before the first boot of the ROM will give the advantage of never having the data/cache entries or internal storage folders for the debloated apps created, the latter is why I recommend a wipe of internal storage.

In order to get back into TWRP/custom recovery from rooted Lollipop or above ROMs:

http://xdaforums.com/showpost.php?p=64601845&postcount=5
[G Pad 8.3 General] roirraW "edor" ehT:
In order to get back into TWRP/custom recovery from rooted Lollipop or above ROMs:

1. Download the corresponding "aboot only" (aboot is the bootloader) found in the same place to download as my ROM zip. Corresponding means if you installed the latest 36B VK810 stock ROM, then download the 36B VK810 aboot zip file.

2. Download the 4.2.2 aboot package from http://xdaforums.com/showpost.php?p=54533937&postcount=2

Credit and thanks [MENTION=1649356]paperWastage[/MENTION] !

The download link is about three quarters down in that second post.

3. Move this aboot.4.2.2.img file into the top of the internal storage (meaning, not in a folder).

4. In Terminal Emulator type (make sure no typos, or can copy/paste to be sure):

su

dd if=/sdcard/aboot.4.2.2.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot

5. You can now reboot into recovery via your preferred method.

6. Once you're finished in TWRP, you need to re-flash the newer aboot zip downloaded in step 1 above. If you forget, the ROM won't boot. You should be able to long-press the power button to force the device off, then use the manual method to get back into TWRP mentioned in step 22 in the previous section above. Re-flash the newer aboot zip, then reboot from TWRP and the ROM will boot.

You can alternatively dirty flash my ROM zip instead of just the aboot. You'd have to re-flash SuperSU.zip and any debloat zips too.
[G Pad 8.3 General] roirraW "edor" ehT:
Reserved
[G Pad 8.3 General] JBurch/cry:
Update

Ok, so I installed TWRP and flashed the new version. I then cleaned out my internal memory and loaded several files to the external SD card for the final process. I flashed "ViKtory810ROM_v36B_00+5.0.2+with+36B+aboot+[no+custom+recovery+after]+-+MD5+50fe66dfd0b57a50694accef47263a94" first. Then I flashed "UPDATE-SuperSU-v2.46". Next I flashed "VK810.4G+36B_00+5.0.2+-+no+OTA+-+MD5+b031ab290cde9f6fa0e30db8ef61223a". Then flashed "VK810.4G+36B_00+5.0.2+debloat+-+all+EXCEPT+still+has+OTA+-+MD5+e215ad72cb4fc9d5841217faa5048444". Then I flashed "VK810.4G+36B_00+5.0.2+debloat+-+LG+apps+&+UI+sounds+-+MD5+9a15512ed7754ef7fccf8b017c631199". I flashed them in that order from TWRP v2.8.7.0. After reboot the new ROM loads up and it seems to be working ok except for one issue. I keep getting an error popping up that says "Unfortunately, the process com.android.phone has stopped. Then it shows activation complete and shows my phone number listed under that. After that the pop up appears and say Unfortunetly, the process com.android.phone has stopped. I clear the pop up and it says activating tablet again, then shows the activation complete with my phone number all over again. Then the pop up appears again. This is an endless cycle of happening. I haven't done anything on the tablet as of yet. I want to know what your thinking. Is there something I need to do with one of the settings? I'm also noticing its not connecting to the cell towers. Ok, hope you can help. Thanks again!
[G Pad 8.3 General] roirraW "edor" ehT:
You're welcome! Everything debloated in the LG/etc debloat zip is also debloated in the debloat All, FYI.

Sorry you're having trouble. I haven't had that experience at all. Did you wipe Data, Cache and Dalvik too? Sadly, without being able to fully use Android you won't be able to get back into TWRP since you have to temporarily redowngrade the bootloader (aboot.img) to get into it (the last section "In order to get back into TWRP/custom recovery from rooted Lollipop or above ROMs").

I know there's a way in Android to boot in a "safe mode" but I've only done it by accident and can't recall how. I don't know if that would make any difference anyway.

If you can use the hardware keys to get into the stock-looking recovery you could try re-wiping Cache but I wouldn't have much hope of that doing the trick, either.

I hate to say but if none of these things work the only way to get back into TWRP without the use of Android is to use LG Flash Tool 2014 to re-flash the 11A KDZ and start over.

I guess I'm going to have to write the detailed instructions for how to check MD5 hashes and add that into the OP, as that would be something I would ask if was done when anyone has problems after a flash.
[G Pad 8.3 General] roirraW "edor" ehT:
[MENTION=4534004]JBurch/cry[/MENTION] I wrote up directions for checking MD5 hashes on Android - they're in the section for flashing my ROM. I realized that this won't help you in your current situation unless you take the MicroSD card out and put it in another Android device and check the hash on there.

I'm debating whether I should write up directions for checking MD5 hashes on Windows too.
[G Pad 8.3 General] JBurch/cry:
So uh ya

So um ya, I failed to do what you stated on task 3 of your Rom installation. You told me to do this before installation:

3. I strongly suggest wiping everything from TWRP (Data, Cache, System, Dalvik and Internal Storage). Obviously, first copy/move anything you want to keep from internal storage like the files you downloaded in the previous sections. Wiping all of these things, especially if you use my debloat zip(s) will clear up garbage/folders that were left behind by previous bloat.

So.... I pulled a stupid.....When reading this I thought you meant to go into my folders "on the tablet" and manually delete the things I put in there. I didn't realise you meant to do it through TWRP before installation lol. So after coming to grips with the idea that I now need to start completely over,,,, I rebuilt the entire thing correctly in 20 minutes. Sad this took me 3 days to learn everything by reading over countless forums. Your help was absolutely necessary to bring it all together. My tablet is fully upgraded and that was the best money I've spent in along time. The next time i get a device, you'll get first crack at helping me. If everything goes well, I'll make sure to double the donation next time. Your experience is valuable and should come at a cost. Thank you and I look forward to talking with you in the future. Take care! Now to get busy using this thing.
[G Pad 8.3 General] roirraW "edor" ehT:
Cool! Glad at least it was something simple, even if a little bit painful to fix. You must at least be a fast learner. :)

Maybe I'll separate that into two steps to distinguish them.

Enjoy! I hope we get 5.1.1 someday because 5.1.1 on the G3 is so much better than 5.0.x was. You're welcome and thank you! I never even took donations until a few months back when one or two people wanted me to.

Most of the time I enjoy just seeing someone successfully do whatever they're trying to do.
[G Pad 8.3 General] FL4NKENSTEIN:
Thank you, I felt so much better using this than some sketch chinese program.
[G Pad 8.3 General] roirraW "edor" ehT:
You're welcome! I know what you mean.
[G Pad 8.3 General] Soundsofsublime:
Hey. Not sure if I am posting in the correct thread so apologises if warranted.

I recently rooted my vk810 with king root. Seemed to be the only thing to work. Only after I rooted did I realize that king root probably was not the wisest way to go.

So I'm about to attempt to unroot and hopefully get this thing rooted and a decent rom working. I like the tablet but all the verizon crap and associated bloatware are driving me nuts.

A little background, I've used linux distros for a while now, but not comfortable with command line stuff. I'm that copy and paste guy...

Any ideas on where to begin? I see Mr warrior seems to be the guy. Just about all related searches end with a post by him. Kudos for helping everyone he has so far. People like him are the reason why the linux/android world is such a great place!

Thanks in advance!
[G Pad 8.3 General] roirraW "edor" ehT:
Just follow all of the directions in the first through fifth posts and they'll get you there. You'll need a Windows PC.

Some people have told about an app called "SuperSU Me" (not by [MENTION=631273]Chainfire[/MENTION]) to replace Kingroot with SuperSU. I have no experience with that or links to it, however.

Thanks and you're welcome!
[G Pad 8.3 General] Slingb1ade:
Lost on step 3.20

i think i messed up somewhere in the "VK810_twrp_2.7.0.1.zip" copy/paste section using X-PLORE. when i type in the "cd /data/local/temp" command in the emulator it

returns "sh: cd: /data/local/temp: no such file or directory". any help would be greatly appreciated.

for the record, this is my first time trying any type of root process.

thanks

***********************

update: i figured it out.
[G Pad 8.3 General] roirraW "edor" ehT:
Thanks for the update. What did you figure out was the trouble? Didn't do the "SU" command first?
[G Pad 8.3 General] zaccheo:
How to unlock boot loader anyone suggest me
[G Pad 8.3 General] roirraW "edor" ehT:
No one has done it. Someone more knowledgeable than I would have to tackle it.
[G Pad 8.3 General] Slingb1ade:
i didn't pay attention to the provided instructions "20. In Terminal Emulator type (make sure no typos, or can copy/paste to be sure)"

i was typing temp, needed to type tmp.
[G Pad 8.3 General] roirraW "edor" ehT:
Ah, I didn't notice when I read your previous message. :)
[G Pad 8.3 General] Slingb1ade:
Starting Over

Well, not sure what went wrong? I made it through step #4 and then problems started.

I keep getting "Unfortunately the process com.android.phone has stopped" pop-up error.

When I try to reboot back into recovery I get:

----------------------------------------

Secure booting Error!

Cause : boot certification verify

----------------------------------------

Hopefully, it goes a little better this try.
[G Pad 8.3 General] roirraW "edor" ehT:
Huh. You had wiped data, cache and Dalvik?

You can't get back into custom recovery on Lollipop on the VK810.4G without following the instructions in the last section, which can only be done in running Android which obviously wasn't an option for you.
[G Pad 8.3 General] roirraW "edor" ehT:
Did you solve this? Did you start back from the beginning, which would've been necessary in your case?
[G Pad 8.3 General] mikekoz:
I just recently had experience with it. It soft bricked my 810! :confused::mad: . It worked fine, removed Kingroot, installed Supersu, and I updated the Supersu binary. I opened a few apps that needed root, and Supersu was doing its thing. Then I restarted my tablet and, the rest, is history! (all is does is show the Verizon splash screen). Going to follow the instructions in this thread when I get home to get it back among the living! :laugh: Just remember the old saying, if it ain't broke, do not fix it!! Kingroot was doing the same thing Supersu would have done on my tablet, but I just HAD to change it. :(:D
[G Pad 8.3 General] roirraW "edor" ehT:
That sucks. Thanks for the report. I'll definitely try to remember to note that if I ever recommend it for a user of this device again.

A lot of people want to change from Kingroot for various reasons, mainly because sometimes it ends up putting apps you didn't want on your device, and it's made in China so a lot of people aren't sure if we can trust it.

I understand and generally agree regarding the "ain't broke don't fix it" though. :)
[G Pad 8.3 General] mikekoz:
[/COLOR]

Kingroot did initially install 2 extra apps on my tablet. One was in Chinese and I have no idea what it was all about, and the other was some sort of ram/cache cleaning app. Both were easily uninstalled. As far as the app being made in China, so are all of these tablets! :D
[G Pad 8.3 General] KyPbP:
KDZ 36B

http://csmgdl.lgmobile.com/dn/downloader.dev?fileKey=FW4BNLT132FHAF0EA0FCJHB/VK81036B_00.kdz
[G Pad 8.3 General] ssimaa:
vk810 Help me

Hello Can anyone help with a brick vk810 need .tot file 4.2.2 or 4.4.2
[G Pad 8.3 General] roirraW "edor" ehT:
http://www.lgbbs.com:41/thread-838-1-1.html

Costs money (I think $10 U.S.). You'll also need a .DLL that they also have on there separately, but you might be able to use a .DLL from one of the VK810 KDZs, which I have extracted and available in my VK810 KDZ thread in my signature below.

Don't know if it's legitimate.
[G Pad 8.3 General] AirForceOnes0010:
I made it all the way to the end but finally require help.. I downloaded what I think is the correct 4.2.2. aboot, the name of the file is vk810.4g_4.2.2_aboot.img_&_instructions.7z. The instructions txt just gives an error so I'm going off the OP. I moved it to the top of internal sd and did the terminal emulator step but TE just says 'no such file or directory' I checked the TE bit 3 times before hitting enter.. Has something changed since OP was written? Everything else was spot on to this point, I love how snappy this device is now
[G Pad 8.3 General] roirraW "edor" ehT:
I haven't looked back at my directions in detail. I did see the link I posted in the instructions which point to the original thread that has the 4.2.2 aboot.img and the instructions to flash it, not the 7-zip archive of it I have on AFH. Don't get me wrong, there's nothing wrong with the one I uploaded, just that from my quick scan of my instructions via TapaTalk (so admittedly I might've missed something), my directions don't reference my 7-zip archive of the 4.2.2 aboot.

I'm detail oriented so it's tough for me not to pick. :)

I did just test my 7-zip archive of the 4.2.2 aboot and here's what I found. The most recent version of X-plore File Manager indeed doesn't seem to handle this 7-zip archive. You can view the contents of it but it either doesn't extract it at all or doesn't extract it right. ZArchiver in the Play Store worked perfect for me though, and after extracting it using that, I was able to view the Instructions.txt just fine in X-plore File Manager.

So either I never tested my 7-zip of the aboot in X-plore, but I'm sure I did because in extreme circumstances I've had to re-download my own file and re-extract it before using it. Or X-plore stopped working correctly either with 7-zips in general or specific 7-zips that were made with certain settings.

I'm tired from work and running around doing errands after work so I hope that helps. I will definitely put it in my queue to pursue the issue of 7-zips in X-plore when I have a chance, to find out what's going on and what can be done about it, and if I do indeed need to change the OP, but since I refer to the other post/download of the aboot, and the instructions in that thread to flash it, I doubt if I need to change the OP.

If I missed something due to only looking over my own posts very quickly, forgive me and don't be afraid to point it out. I know I do refer to X-plore in some of my posts but just too tired to look at the details right now.

Let me know how it works out regardless!
[G Pad 8.3 General] AirForceOnes0010:
I really appreciate the clarity in your answer, you are def part of what makes xda a great community and resource. However I still need help lol. So with zarchiver I unzipped the 7z "here" as I already had it at the top of the internal sd. The instructions in the 7z now work but I'm stuck at basically the same point. I put in "su" into TE and it goes down to root@altev, then the instructions in the 7z for doing it on the device say to type "cd sdcard/aboot" which isn't in the OP, but hitting enter just says no such file or directory still.. Doing it like the OP says no such f or d still too. I have that feeling like I'm missing something tiny and simple..
[G Pad 8.3 General] roirraW "edor" ehT:
You're welcome! And thank you very much!

What I was trying to say is that the OP actually points to another thread for both the aboot download and the instructions to flash it. Those instructions work perfect.

However, you should be able to completely ignore that "cd" line of the instructions and just proceed with the next line. There shouldn't be any reason to CD (change directory) to anywhere since 1) the next command gives the full path to the aboot you just extracted at the top level of the internal storage (sdcard). And 2) if anything, the instruction should be "cd sdcard" instead since my instructions don't say to extract it into a subfolder called aboot - again, you shouldn't have to do that, though; you should be able to proceed straight to the dd command. Sorry about that.

So obviously I screwed up the instructions both in the instructions.txt and I also have those same wrong instructions as the description for the download of that 7-Zip of the aboot.

I'll fix at least the instructions in the description on AFH when I have the chance although I'm not too worried about it since my OP doesn't refer to that download at all.

Thanks for bringing that to my attention so I can fix it! ?
[G Pad 8.3 General] AirForceOnes0010:
I'm glad you're figuring things out! I'm STILL stuck.. I noticed that the OP says "dd if=/sdcard/aboot.4.2.2.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot" and the instructions from the 7z says "dd if=/sdcard/aboot.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot" however after trying both in TE, it STILL says no such file or directory.. I don't get it
[G Pad 8.3 General] roirraW "edor" ehT:
The difference is just the name of the file.

I couldn't tell you what's wrong without being there. I just used my freshly extracted 7-Zip of the 4.2.2 aboot yesterday to downgrade the bootloader and get into TWRP. I had a weird instance sometime in the past where putting the aboot at the top of the internal storage, the terminal emulator command couldn't find it there. I had to temporarily copy it to just root, then dd if=aboot.img or dd if=/aboot.img - I don't recall which I had to do. The full line, just change /sdcard/aboot.img to just aboot.img or /aboot.img. When I rebooted after getting done in TWRP, the aboot.img was gone from root. This most recent time I didn't have to do that, though.