Database Develop

[Q] hp touchpad /boot directory content?

Hi, this is my list files in /boot
Is normal the bin, etc, dev, sbin, sys, usr...
What are this folders doing here? Thanks
Code:
# ls -l
-rw-r--r-- 1 root root 1435013 Dec 21 19:19 System.map-2.6.35-palm-tenderloin
drwxr-xr-x 2 root root 4096 Feb 4 02:49 bin
-rw-r--r-- 1 root root 490656 Dec 21 19:10 boot-genesis.tar.gz
-rw-r--r-- 1 root root 119203 Dec 21 19:10 boot-images.tar.gz
-rw-r--r-- 1 root root 115484 Dec 21 19:10 boot.bin
-rw-r--r-- 1 root root 75257 Dec 21 19:19 config-2.6.35-palm-tenderloin
drwxr-xr-x 2 root root 4096 Feb 4 02:49 dev
drwxr-xr-x 3 root root 4096 Feb 4 02:49 etc
-rwxr-xr-x 1 root root 1131 Dec 21 19:10 genesis-update.xml
-rwxr-xr-x 1 root root 2196 Dec 21 19:10 image-update.xml
drwxr-xr-x 2 root root 4096 Feb 4 02:49 lib
drwx------ 2 root root 16384 Feb 4 02:46 lost+found
-rw-r--r-- 1 root root 11 Feb 4 03:36 moboot.default
-rw-r--r-- 1 luna luna 0 Feb 4 23:34 moboot.next
-rw-r--r-- 1 root root 30313 Feb 4 03:35 moboot.splash.CyanogenMod.tga
drwxr-xr-x 2 root root 4096 Feb 4 02:49 proc
drwxr-xr-x 2 root root 4096 Feb 4 02:49 realroot
drwxr-xr-x 2 root root 4096 Feb 4 02:49 sbin
drwxr-xr-x 2 root root 4096 Feb 4 02:49 sys
lrwxrwxrwx 1 root root 13 Feb 4 03:37 uImage -> uImage.moboot
-rw-r--r-- 1 root root 3341940 Dec 21 19:19 uImage-2.6.35-palm-tenderloin
lrwxrwxrwx 1 root root 18 Feb 4 03:36 uImage-prev -> uImage.CyanogenMod
-rwxrwxrwx 1 root root 4857082 Feb 3 22:33 uImage.Bodhi
-rw-r--r-- 1 root root 5006686 Feb 4 03:37 uImage.ClockworkMod
-rw-r--r-- 1 root root 4136681 Feb 4 03:35 uImage.CyanogenMod
-rwxr-xr-x 1 root root 64508 Feb 4 23:30 uImage.moboot
lrwxrwxrwx 1 root root 29 Feb 4 02:49 uImage.webOS -> uImage-2.6.35-palm-tenderloin
-rw-r--r-- 1 root root 84 Dec 21 19:22 updatefs-info
drwxr-xr-x 5 root root 4096 Feb 4 02:49 usr

[Q] Invalid Magic (TouchPadBuntu)

Hi,
I have upgraded my moboot to 3.0.5 and upgraded the Cyanogenmod to CM9. Also, i have decided to install TouchPadBuntu to test it. Followed the instructions with some modifications, and everything went fine, but when i try to boot on it via moboot, it gives the error:
Loading '/boot/uImage.TouchPadBuntu'... OK
Checking uImage... Invalid Magic
BOOT FAILED!
Also, ClockRecovery doesn't works too, it returns some numbers (hex codes) on the boot screen.
Someone can give some light?

I'm dealing with same problem, but with Arch Linux.
I think the problem is in /boot free space...
Can you list your files in /boot and your free space in there?
ls -l /boot
df -h /boot

Hi, i have attached the errors... one is TouchPadBuntu error, and the other is Cyanogenmod error that is appearing sometimes yes, sometimes no...
http://img19.imageshack.us/img19/5138/imagem0000m.jpg
http://img828.imageshack.us/img828/4153/imagem0001.jpg
Also, here is my /boot
Code:
[email protected]:/# ls -l /boot
-rw-r--r-- 1 root root 1430215 Jul 30 2011 System.map-2.6.35-palm-tenderloin
drwxr-xr-x 2 root root 4096 Oct 14 02:59 bin
-rw-r--r-- 1 root root 490764 Jul 30 2011 boot-genesis.tar.gz
-rw-r--r-- 1 root root 119371 Jul 30 2011 boot-images.tar.gz
-rw-r--r-- 1 root root 115392 Jul 30 2011 boot.bin
-rw-r--r-- 1 root root 75277 Jul 30 2011 config-2.6.35-palm-tenderloin
drwxr-xr-x 2 root root 4096 Oct 14 02:59 dev
drwxr-xr-x 3 root root 4096 Oct 14 02:59 etc
-rwxr-xr-x 1 root root 1131 Jul 30 2011 genesis-update.xml
-rwxr-xr-x 1 root root 2224 Jul 30 2011 image-update.xml
drwxr-xr-x 2 root root 4096 Oct 14 02:59 lib
drwx------ 2 root root 16384 Oct 14 02:56 lost+found
-rw-r--r-- 1 root root 11 Oct 14 03:51 moboot.default
-rw-r--r-- 1 luna luna 0 Feb 9 01:57 moboot.next
-rw-rw-rw- 1 root root 30313 Feb 8 00:58 moboot.splash.CyanogenMod.tga
-rw-r--r-- 1 luna 10000 14046 Sep 8 2001 moboot.splash.webOS.tga
-rw-r--r-- 1 root root 4 Feb 8 01:51 moboot.verbose.TouchPadBuntu
drwxr-xr-x 2 root root 4096 Oct 14 02:59 proc
drwxr-xr-x 2 root root 4096 Oct 14 02:59 realroot
drwxr-xr-x 2 root root 4096 Oct 14 02:59 sbin
drwxr-xr-x 2 root root 4096 Oct 14 02:59 sys
lrwxrwxrwx 1 root root 13 Feb 8 01:51 uImage -> uImage.moboot
-rw-r--r-- 1 root root 3333228 Jul 30 2011 uImage-2.6.35-palm-tenderloin
-rw-r--r-- 1 root root 5006686 Feb 8 00:57 uImage.ClockworkMod
-rw-r--r-- 1 root root 4136681 Feb 8 00:58 uImage.CyanogenMod
-rw-r--r-- 1 root root 1106 Feb 8 02:53 uImage.TouchPadBuntu
-rw-r--r-- 1 root root 64508 Feb 8 01:50 uImage.moboot
lrwxrwxrwx 1 root root 29 Oct 14 02:58 uImage.webOS -> uImage-2.6.35-palm-tenderloin
-rw-r--r-- 1 root root 84 Jul 30 2011 updatefs-info
drwxr-xr-x 5 root root 4096 Oct 14 02:59 usr
[email protected]:/# df -h /boot
Filesystem Size Used Available Use% Mounted on
/dev/root 31.0M 22.1M 8.9M 71% /boot

Hi folks,
I have corrected my problem downloading uImage.TouchPadUbuntu again via CURL direclty to /boot. To do this i have to use mount -O rw,remount /boot and execute the curl command here.
After this, i rebooted the touchpad and now have ubuntu on it. But using touchscreen as mouse is sucking a lot, and response of my touch on virtual keyboard too... but fine to test!

I also solved my problem, I think the problem was pretty like yours!
My solution post.

Reboot loop after upgrading from CM 10.0 stable to CM 10.1 nightly

Hi
I was running CM 10 stable and on friday I installed CM 10.1 nightly 20130111. I installed after factorty reset, cache and dalvik cache wipe. After rebooting I saw a message that android is upgrading along with "optimising" 96 apps. After finishing optimisation it went to home screen and instantly message "Unfortunatley, the process com.android.phone has stopped" popped up. when I hit ok, it popped up again and again and then phone rebooted.
Now it is stuck in reboot loop.
Please help.
Thanks

transact said:
Hi
I was running CM 10 stable and on friday I installed CM 10.1 nightly 20130111. I installed after factorty reset, cache and dalvik cache wipe. After rebooting I saw a message that android is upgrading along with "optimising" 96 apps. After finishing optimisation it went to home screen and instantly message "Unfortunatley, the process com.android.phone has stopped" popped up. when I hit ok, it popped up again and again and then phone rebooted.
Now it is stuck in reboot loop.
Please help.
Thanks
Click to expand...
Click to collapse
Have you tried wiping data again from recovery and then boot?

ishangoyal said:
Have you tried wiping data again from recovery and then boot?
Click to expand...
Click to collapse
Yeah, multiple times.
I tried to flash stock firmware back but I think system is read only now.
When I flashed stockfirmware from samfirmware also with odin and pit file, I was able to go to stock recovery but phone never booted to stock firmware. Then I flashed semaphore . this time I could see semaphore logo and then cyanogenmod animation. Seeing cyanogen animation was a surprise as it should have been wiped when i flashed stockfirmare.
I went to recovery mode again did factory reset, cache wipe, dalvik cache. Then mounted usb and copied latest nightly of 10.1 and gapps to customroms folder on my sdcard.
After copying I rebooted into recovery mode again and selected install from zip on sdcard but to my surprise the new files I copied were not there but the files I deleted were still there.
It seems like phone didn't allow me to alter content of sdcard. To test I mounted the usb storage again and created some dummy files like default.txt, default.ini and default.zip in root of sdcard and deleted some files from my backup files of fuellog folder. After unmounting and going through files on phone I discovered that new files are not there and old files are still present.
Another thing is that I have factory reset multiple times, wiped cache partition and cleared dalvik cache as well but every time I mount usb from recovery I have .android_secure folder filled with my previous apps from CM 10.0, which I think shouldn't be there after factory reset.
So I guess it is something to do with permissions. I have done 'fix permissions' multiple times but that also didn't helped.
One more thing I noticed is that after I flash CM10.1 from old file still in my sdcard, on first boot I get com.phone.android error but then on second boot I saw option to complete action using apex, nova or trebuchet laucnher behing the com.android.phone error. I think I shouldn't see that message as it is suppose to be new install with factory reset.
after I click ok on the error message, the phone reboots again but this time it stuck on cyanogen animation. it never goes past animation on 3rd boot.
I have really no idea what is happening.
Is there a way to reset everything through adb? or reset file permissions? I could access my device using adb but had no idea what I could do or not do.
File system view when phone is booting and stuck at cyanogen animation
Code:
drwxr-xr-x root root 2013-01-15 10:29 acct
-rw-r--r-- root root 614 2013-01-15 10:29 boot.txt
drwxrwx--x system cache 2013-01-15 10:29 cache
-rwxr-x--- root root 264080 2013-01-15 10:29 charger
dr-x------ root root 2013-01-15 10:29 config
lrwxrwxrwx root root 2013-01-15 10:29 d -> /sys/kernel/debug
drwxrwx--x system system 2013-01-11 17:08 data
drwxrwx--x system system 2013-01-15 10:29 datadata
-rw-r--r-- root root 163 2013-01-15 10:29 default.prop
drwxr-xr-x root root 2013-01-15 10:29 dev
drwxr-xr-x radio radio 2013-01-14 21:30 efs
lrwxrwxrwx root root 2013-01-15 10:29 emmc -> /storage/sdcard1
lrwxrwxrwx root root 2013-01-15 10:29 etc -> /system/etc
-rw-r----- root root 568 2013-01-15 10:29 fstab.aries
-rwxr-x--- root root 109484 2013-01-15 10:29 init
-rwxr-x--- root root 555 2013-01-15 10:29 init.aries.gps.rc
-rwxr-x--- root root 5375 2013-01-15 10:29 init.aries.rc
-rwxr-x--- root root 3899 2013-01-15 10:29 init.aries.usb.rc
-rwxr-x--- root root 1238 2013-01-15 10:29 init.cm.rc
-rwxr-x--- root root 2487 2013-01-15 10:29 init.goldfish.rc
-rwxr-x--- root root 18768 2013-01-15 10:29 init.rc
-rwxr-x--- root root 1795 2013-01-15 10:29 init.trace.rc
-rwxr-x--- root root 3915 2013-01-15 10:29 init.usb.rc
-rw-r--r-- root root 340 2013-01-15 10:29 lpm.rc
drwxr-xr-x root root 2013-01-14 22:02 lvm
drwxrwxr-x root system 2013-01-15 10:29 mnt
dr-xr-xr-x root root 1970-01-01 10:00 proc
drwxr-xr-x root root 2013-01-14 21:28 radio
drwxr-xr-x root root 2013-01-15 10:29 res
drwxr-x--- root root 2013-01-15 10:29 sbin
lrwxrwxrwx root root 2013-01-15 10:29 sdcard -> /storage/sdcard0
d---r-x--- root sdcard_r 2013-01-15 10:29 storage
drwxr-xr-x root root 2013-01-15 10:29 sys
drwxr-xr-x root root 2013-01-11 17:01 system
-rw-r--r-- root root 1489 2013-01-15 10:29 ueventd.aries.rc
-rw-r--r-- root root 272 2013-01-15 10:29 ueventd.goldfish.rc
-rw-r--r-- root root 5220 2013-01-15 10:29 ueventd.rc
lrwxrwxrwx root root 2013-01-15 10:29 vendor -> /system/vendor
file system view when in recovery
Code:
drwxr-xr-x 18 root root 0 Jan 15 00:12 .
drwxr-xr-x 18 root root 0 Jan 15 00:12 ..
drwxr-xr-x 3 root root 0 Jan 15 00:12 acct
-rw-r--r-- 1 root root 586 Jan 15 00:12 boot.txt
drwxrwx--x 1 system cache 4096 Jan 14 23:29 cache
-rwxr-x--- 1 root root 264080 Jan 15 00:12 charger
dr-x------ 2 root root 0 Jan 15 00:12 config
lrwxrwxrwx 1 root root 17 Jan 15 00:12 d -> /sys/kernel/debug
drwxrwx--x 12 system system 0 Jan 15 00:12 data
-rw-r--r-- 1 root root 2887 Jan 15 00:12 default.prop
drwxr-xr-x 13 root root 3040 Jan 15 00:12 dev
drwxr-xr-x 2 root root 0 Jan 15 00:12 efs
d--------- 2 system system 0 Jan 15 00:12 emmc
drwxr-xr-x 2 root root 0 Jan 15 00:12 etc
-rw-r----- 1 root root 568 Jan 15 00:12 fstab.aries
-rwxr-x--- 1 root root 109484 Jan 15 00:12 init
-rwxr-x--- 1 root root 10349 Jan 15 00:12 init.rc
-rw-r--r-- 1 root root 340 Jan 15 00:12 lpm.rc
drwxr-xr-x 4 root root 0 Jan 14 11:02 lvm
dr-xr-xr-x 73 root root 0 Jan 1 1970 proc
drwxr-xr-x 3 root root 0 Jan 15 00:12 res
drwxr-x--- 2 root root 0 Jan 15 00:12 sbin
d--------- 2 system system 0 Jan 15 00:12 sdcard
drwxr-xr-x 12 root root 0 Jan 15 00:12 sys
drwxr-xr-x 3 root root 0 Jan 15 00:12 system
drwxr-xr-x 2 root root 0 Jan 15 00:12 tmp
-rw-r--r-- 1 root root 1489 Jan 15 00:12 ueventd.aries.rc
-rw-r--r-- 1 root root 272 Jan 15 00:12 ueventd.goldfish.rc
-rw-r--r-- 1 root root 5220 Jan 15 00:12 ueventd.rc
-rw-r--r-- 1 root root 3899 Jan 15 00:12 usb.rc
lrwxrwxrwx 1 root root 14 Jan 15 00:12 vendor -> /system/vendor
I hope they give some kind of clue.
please help.
thanks

transact said:
Yeah, multiple times.
I hope they give some kind of clue.
please help.
thanks
Click to expand...
Click to collapse
That's a really weird and detailed explanation .. however I am unable to explain the behaviour of your phone.. what I can suggest is formating the sd card too (if you have backup of data that is) and format /system too manually along with wiping data, cache and dalvik cache.. after that flash CM10.1 nightly twice.. don't flash gapps atm.. after that reboot recovery.. wipe data, cache again (not /system this time) and flash nightly again.. fix permissions and then reboot..
I know repetition like this doesn't make much sense but nor does your problem..
Hope this will help.

if you are comeing from cm10.0 ant flashing cm10.1 it is recommend to wipe /system befor flashing

System/app/PartnerBookmarksProvider.apk" has unexpected contents

How to fix this update problem
Finding update package.....
Opening update package....
Verifying update package....
Installing update....
Verifying current system.....
System/app/PartnerBookmarksProvider.apk" has unexpected contents
Installation aborted
Write host_mode :0 done

Install TWRP
Place original file
Install stock Recovery again

It's a virus!
My hone was infected and PartnerBookmarksProvider.apk was the app that triggered the virus.
Here is the list of apk that got installed as root (my phone isn't even rooted!)
Thelist is sorted by time. you can see when the app (PartnerBookmarksProvider) got installed the viruses started to flood now I don't even know how to remove them. So think twice before installing it.
Any Idea how to solve it?
-rw-r--r-- root root 2674688 19/08/2016 15:36 KingoUser.apk
-rw-r--r-- root root 31 19/08/2016 17:12 OPBKEY_2d4f7e56b3ef4b45f0b89a9b23696e4bab0d
-rw-r--r-- root root 180224 19/08/2016 17:38 system0816.apk
-rw-r--r-- root root 3080528 16/08/2016 2:59 FB_57.apk
-rw-r--r-- root root 1971150 15/08/2016 18:29 lm-jinwf_mp_14_musicplayer0712.apk
-rw-r--r-- root root 20282 15/08/2016 18:49 com.android.display.apk
-rw-r--r-- root root 294310 15/08/2016 18:49 com.android.telephone.views.apk
-rw-r--r-- root root 119 15/08/2016 19:15 Androidevice
-rw-rw-r-- root root 1205501 15/08/2016 23:08 com.system.cap.qs42.iupdater.apk
-rw-r--r-- root root 6017692 14/08/2016 4:46 lm-Booster_tx01.apk
#NOM? root root 31 12/08/2016 7:41 com.sms.server.socialgraphop.db
-rw-r--r-- root root 1398951 12/08/2016 7:44 com.glb.filemanager.apk
-rw-r--r-- root root 2770328 12/08/2016 8:08 com.beny.compass.apk
-rw-r--r-- root root 857425 12/08/2016 8:09 com.tensor3d.s1.apk
#NOM? root root 51 12/08/2016 9:08 OPBKEY_aiwozhh_18e2a07cbb1acb44f8b8b27bb8654fa21ded
-rw-r--r-- root root 773511 12/08/2016 9:08 cm1.apk
#NOM? root root 31 12/08/2016 9:08 com.aiwozhh.server.socialgraphop.db
-rw-r--r-- root root 32545 12/08/2016 9:18 AndroidFileManger.apk
-rw-r--r-- root root 75232 12/08/2016 9:19 GloablBCServiceInfo.apk
-rw-r--r-- root root 1 12/08/2016 9:19 cd89800001
-rw-r--r-- root root 562737 12/08/2016 9:24 lm-Compass0714.apk
-rw-r--r-- root root 314441 12/08/2016 10:14 yijialing1.apk
-rw-r--r-- root root 53647 12/08/2016 10:18 CertificateInstallerProviders.apk
-rw-r--r-- root root 227958 12/08/2016 10:18 InstallerProtect.apk
-rw-r--r-- root root 4647 12/08/2016 10:20 CameraDevicesOptimization.apk
-rw-r--r-- root root 2771641 12/08/2016 10:43 com.glb.news.apk
-rw-r--r-- root root 2767858 12/08/2016 10:44 com.zhaoy.calculator.apk
-rw-r--r-- root root 2767841 12/08/2016 10:44 com.zhaoy.minifilemanager.apk
-rw-r--r-- root root 3695992 12/08/2016 10:45 Browser.apk
-rw-r--r-- root root 1151352 12/08/2016 10:45 Calculator.apk
-rw-r--r-- root root 2108322 12/08/2016 10:45 Calendar.apk
-rw-r--r-- root root 4954507 12/08/2016 10:45 Email.apk
-rw-r--r-- root root 8921088 12/08/2016 10:45 LatinIME.apk
-rw-r--r-- root root 8423276 12/08/2016 10:45 Maps.apk
-rw-r--r-- root root 8374746 12/08/2016 10:45 YouTube.apk
-rw-r--r-- root root 21112 12/08/2016 10:54 1004.apk
-rw-r--r-- root root 578831 12/08/2016 10:57 system0804.apk
-rw-r--r-- root root 67246 12/08/2016 11:07 web3.0_20160713.apk
-rw-r--r-- root root 251727 12/08/2016 11:24 webcps0615.apk
-rw-r--r-- root root 46788 12/08/2016 11:26 68_20160715.apk
-rw-r--r-- root root 801255 12/08/2016 11:26 admobcps.apk
-rw-r--r-- root root 2911374 12/08/2016 11:41 aisha0725.apk
-rw-r--r-- root root 596372 12/08/2016 19:28 lm-13_FileExplorer10803.apk
-rw-r--r-- root root 978541 12/08/2016 20:36 GoogleUp0812.apk
#NOM? root u0_a 74 6063 09/08/2016 11:44 ChromeCustomizations.apk
#NOM? root u0_a 74 18733 09/08/2016 11:44 PartnerBookmarksProvider.apk
-rw-r--r-- root root 15619975 12/10/2015 3:15 movie.mp4
-rw-r--r-- root root 4904345 12/10/2015 3:16 Gmail2.apk
-rw-r--r-- root root 502096 12/10/2015 3:16 GoogleCalendarSyncAdapter.apk
-rw-r--r-- root root 206547 12/10/2015 3:16 GoogleContactsSyncAdapter.apk
-rw-r--r-- root root 282060 12/10/2015 3:16 frozenkeyboard.apk

Anyone still using Stock MM?

I just hope some obe still on stock MM that is rooted at least. Guys im fully porting Nougat to H811 without the need of TMO or LG but i need your help. I need to pull some files from root folder that are auto created once you flash the Stock. With those files i can successfully make this port easier porting wifi calling and Volte. Anything else is just flawlessly working great. Please i need you help with this issue if anyone can.
Thanks
Sent from my LG-H811 using Tapatalk

No but I have backup
If that helps

I am running rooted stock 20v.
Sent from my LG-H811 using XDA-Developers Legacy app

Awesome bro.
Can you see if at root you see a folder name cust or carrier?
Thanks bro
Sent from my LG-H811 using Tapatalk

TecknoFreak said:
Awesome bro.
Can you see if at root you see a folder name cust or carrier?
Thanks bro
Sent from my LG-H811 using Tapatalk
Click to expand...
Click to collapse
Cust yes
Carrier yes
They are empty though

deltadiesel said:
Cust yes
Carrier yes
They are empty though
Click to expand...
Click to collapse
Ok thanks bro
I guess i have to figure this out the hard way. Lol
Sent from my LG-H811 using Tapatalk

TecknoFreak said:
Ok thanks bro
I guess i have to figure this out the hard way. Lol
Sent from my LG-H811 using Tapatalk
Click to expand...
Click to collapse
Unless it deletes on first boot or
Because I'm not actually using T-Mobile service on m T-Mobile 811
I'm not sure.... Never go in there

deltadiesel said:
Unless it deletes on first boot or
Because I'm not actually using T-Mobile service on m T-Mobile 811
I'm not sure.... Never go in there
Click to expand...
Click to collapse
No most likely those files got deleted by either a mod or custom rom
Sent from my LG-H811 using Tapatalk

TecknoFreak said:
No most likely those files got deleted by either a mod or custom rom
Sent from my LG-H811 using Tapatalk
Click to expand...
Click to collapse
My backup is not mod or custom
Its stock lg T-Mobile

deltadiesel said:
My backup is not mod or custom
Its stock lg T-Mobile
Click to expand...
Click to collapse
It doesnt matter once they get deleted the back up will not keep them as those files r located out of the system and they are in root which your backup will not safe
Sent from my LG-H811 using Tapatalk

TecknoFreak said:
It doesnt matter once they get deleted the back up will not keep them as those files r located out of the system and they are in root which your backup will not safe
Sent from my LG-H811 using Tapatalk
Click to expand...
Click to collapse
I guess. If your saying is because I rooted before I made backup theyre not there I guess you are right...but I'm not sure
All I know is I backed up EVERYTHING...including system cache firmware image data dalvik etc

deltadiesel said:
I guess. If your saying is because I rooted before I made backup theyre not there I guess you are right...but I'm not sure
All I know is I backed up EVERYTHING...including system cache firmware image data dalvik etc
Click to expand...
Click to collapse
Yeah that wont back up root\
Sent from my LG-H811 using Tapatalk

My Root folder is empty!
Sent from my LG-H811 using XDA-Developers Legacy app

Waiting4MyAndroid said:
My Root folder is empty!
Sent from my LG-H811 using XDA-Developers Legacy app
Click to expand...
Click to collapse
Ok thanks bro. I will figure it out later if is possible and rhe only way to make that happen with tmo is by reverse engineer a lot of crap which i gave up for now.
Sent from my LG-H811 using Tapatalk

I'm running stock 20R and rooted. I have never installed a ROM on my phone. It's been on 20R since I got the phone and I don't see cust or carrier folder in root. My wife also has a H811 with stock 20R so I'll check her phone later to see if she has them.

probaina said:
I'm running stock 20R and rooted. I have never installed a ROM on my phone. It's been on 20R since I got the phone and I don't see cust or carrier folder in root. My wife also has a H811 with stock 20R so I'll check her phone later to see if she has them.
Click to expand...
Click to collapse
Wow this can be it. Maybe my lucky day. Lol
Can you please check of at root path you see a folder name ../cust ?
Sent from my LG-H811 using Tapatalk

I've checked my phone and my wife's h811 and u can't find ./cust in the root path. Could this be somewhere else? Here's a list if everything that's in mine:
[email protected]:/ $ ls -l
drwxr-xr-x root root 2015-01-22 06:37 acct
drwxrwx--- system cache 2017-09-25 21:20 cache
lrwxrwxrwx root root 1969-12-31 14:00 charger -> /sbin/healthd
dr-x------ root root 2015-01-22 06:37 config
lrwxrwxrwx root root 2015-01-22 06:37 d -> /sys/kernel/debug
drwxrwx--x system system 2017-08-22 04:42 data
-rw-r--r-- root root 546 1969-12-31 14:00 default.prop
drwxr-xr-x root root 2017-09-17 14:37 dev
lrwxrwxrwx root root 2015-01-22 06:37 etc -> /system/etc
-rw-r--r-- root root 77988 1969-12-31 14:00 file_contexts
dr-xr-x--- system system 1969-12-31 14:00 firmware
-rw-r----- root root 1891 1969-12-31 14:00 fstab.fota
-rw-r----- root root 1289 1969-12-31 14:00 fstab.p1
-rwxr-x--- root root 1175792 1969-12-31 14:00 init
-rwxr-x--- root root 4291 1969-12-31 14:00 init.alphap.bt_vendor.rc
-rwxr-x--- root root 3108 1969-12-31 14:00 init.class_main.sh
-rwxr-x--- root root 1478 1969-12-31 14:00 init.environ.rc
-rwxr-x--- root root 1711 1969-12-31 14:00 init.lge.audio.rc
-rwxr-x--- root root 631 1969-12-31 14:00 init.lge.early.rc
-rwxr-x--- root root 1055 1969-12-31 14:00 init.lge.fs.rc
-rwxr-x--- root root 8162 1969-12-31 14:00 init.lge.log.rc
-rwxr-x--- root root 3073 1969-12-31 14:00 init.lge.modem_log.rc
-rwxr-x--- root root 4291 1969-12-31 14:00 init.lge.power.rc
-rwxr-x--- root root 9323 1969-12-31 14:00 init.lge.rc
-rwxr-x--- root root 894 1969-12-31 14:00 init.lge.svelte.rc
-rwxr-x--- root root 774 1969-12-31 14:00 init.lge.usb.default.sh
-rwxr-x--- root root 21023 1969-12-31 14:00 init.lge.usb.rc
-rwxr-x--- root root 6535 1969-12-31 14:00 init.lge.usb.sh
-rwxr-x--- root root 4279 1969-12-31 14:00 init.msm8992.crash.sh
-rwxr-x--- root root 2035 1969-12-31 14:00 init.msm8992.sensor.sh
-rwxr-x--- root root 6464 1969-12-31 14:00 init.msm8992_core.rc
-rwxr-x--- root root 5998 1969-12-31 14:00 init.p1.power.rc
-rwxr-x--- root root 277 1969-12-31 14:00 init.p1.rc
-rwxr-x--- root root 8737 1969-12-31 14:00 init.p1_core.rc
-rwxr-x--- root root 2045 1969-12-31 14:00 init.p1_product.rc
-rwxr-x--- root root 7374 1969-12-31 14:00 init.qcom.class_core.sh
-rwxr-x--- root root 12931 1969-12-31 14:00 init.qcom.factory.sh
-rwxr-x--- root root 30016 1969-12-31 14:00 init.qcom.rc
-rwxr-x--- root root 8545 1969-12-31 14:00 init.qcom.sh
-rwxr-x--- root root 27314 1969-12-31 14:00 init.rc
-rwxr-x--- root root 335 1969-12-31 14:00 init.recovery.p1.rc
-rwxr-x--- root root 10264 1969-12-31 14:00 init.target.rc
-rwxr-x--- root root 387 1969-12-31 14:00 init.time_in_state.sh
-rwxr-x--- root root 1921 1969-12-31 14:00 init.trace.rc
-rwxr-x--- root root 3896 1969-12-31 14:00 init.usb.rc
-rwxr-x--- root root 301 1969-12-31 14:00 init.zygote32.rc
-rwxr-x--- root root 531 1969-12-31 14:00 init.zygote64_32.rc
-rw-r--r-- root root 1143 1969-12-31 14:00 lge.fota.rc
-rw-r--r-- root root 4000 1969-12-31 14:00 lge.fota.update.rc
drwxr-xr-x root system 2015-01-22 06:37 mnt
drwxrwxr-x system system 2016-06-13 14:30 mpt
drwxr-xr-x root root 1969-12-31 14:00 oem
drwxrwx--x system system 2015-01-22 06:37 persist
drwxrwx--x system system 2014-12-31 15:08 persist-lg
dr-xr-xr-x root root 1969-12-31 14:00 proc
-rw-r--r-- root root 18270 1969-12-31 14:00 property_contexts
drwxr-xr-x root root 1969-12-31 14:00 res
drwx------ root root 2017-01-10 18:17 root
drwxr-x--- root root 1969-12-31 14:00 sbin
lrwxrwxrwx root root 2015-01-22 06:37 sdcard -> /storage/self/primary
-rw-r--r-- root root 3825 1969-12-31 14:00 seapp_contexts
-rw-r--r-- root root 7 1969-12-31 14:00 selinux_version
-rw-r--r-- root root 506714 1969-12-31 14:00 sepolicy
-rw-r--r-- root root 19205 1969-12-31 14:00 service_contexts
-rw-r--r-- root root 607 1969-12-31 14:00 set_emmc_size.sh
drwxr-xr-x system system 2014-12-31 15:00 sns
drwxr-xr-x root root 2017-09-17 14:38 storage
drwxr-xr-x root root 2014-12-31 19:47 su
dr-xr-xr-x root root 2015-01-22 06:37 sys
drwxr-xr-x root root 2015-01-01 22:43 system
lrwxrwxrwx root root 2015-01-22 06:37 tombstones -> /data/tombstones
-rw-r--r-- root root 12806 1969-12-31 14:00 ueventd.p1.rc
-rw-r--r-- root root 4845 1969-12-31 14:00 ueventd.rc
lrwxrwxrwx root root 2015-01-22 06:37 vendor -> /system/vendor
[email protected]:/ $

It should be there

I aldo need this folder and the files inside if you have it from stock /root/data/ipsec/