Issue rooting D851 - T-Mobile LG G3

I was attempting to root my LG-D851 on TMO with PurpleDrake SW version [V10r] and I received this message:
ERROR: Something went wrong. Permaroot doesn't appear to have worked, rebooting phone.
Debug information - 'ls -l /system/xbin/su':
/system/xbin/su: No such file or directory
------------------------
Debug information - 'ls -l /temp/':
-rw-r--r-- root root 2187 1970-03-15 22:45 br_daemon.log
-rw-r--r-- root root 36 1970-03-15 22:44 brd_ready
-rw-r--r-- root root 2 1970-03-15 22:45 error
-rwsr-sr-x root root 157424 2014-07-12 03:54 fakesu
drwx------ root root 1970-03-15 22:45 hidden
-rw-r--r-- root root 28 1970-03-15 22:45 start_restore_complete
------------------------
So, we temprooted your phone, but we weren't able to permaroot it for some reason.
Click to expand...
Click to collapse
Help would be greatly appreciated. If you need more information please let me know.

http://forum.xda-developers.com/showthread.php?t=3004158
[ROOT]How to Root KVT49L.D85110r and Install TWRP. My experience
Sent from my LG-D851 using XDA Free mobile app

Related

logcat error

i get a whole host of errors when trying to install a sense rom with odexed apps deodexed framework.
i can restore a nandroid of same rom but after running thru kitchen this happens?
anybody no why?
09:35:18.602 Warning PackageManager 350 Unknown permission android.permission.WRITE_SECURE_SETTINGS in package com.htc.android.htcime
09:35:18.602 Warning PackageManager 350 Unknown permission android.permission.GET_ACCOUNTS in package com.htc.android.htcime
09:35:18.602 Warning PackageManager 350 Unknown permission android.permission.RECORD_AUDIO in package com.htc.android.htcime
09:35:18.603 Warning PackageManager 350 Unknown permission android.permission.READ_SMS in package com.android.providers.htcmessage
09:35:18.603 Warning PackageManager 350 Unknown permission android.permission.WRITE_SMS in package com.android.providers.htcmessage
09:35:18.604 Warning PackageManager 350 Unknown permission android.permission.RECEIVE_BOOT_COMPLETED in package com.android.providers.downloads
09:35:18.604 Warning PackageManager 350 Unknown permission android.permission.ACCESS_CACHE_FILESYSTEM in package com.android.providers.downloads
this list goes on
Not sure if its the same permissions, but from ADB in recovery, before boot (and after flash) what happenf if you mount /data then chmod 777 /data/data/com.android.x.x?
Then reboot?
cheers dan whats the last bit android.x.x
also if this worked could i nandroid it run it thru kitchen again and install ok next time, or would u need to run chmod every time?
basically all the package names in your logcat.
IF it does work (i'm not sure if its the permissions of the package or that whats in the package cannot get the permissions) then yes a nandroid is a snap shot so all permissions would be stored.
It may be the actual apks and odex files in system/app that need permissions altering. i really dont know for sure, im guessing.
ok cheers dan, im not sure how im gunna set permisions on apks and odex when i cant get past boot loop be different if i had fc,s
adb via recovery, like i said
chmod777 on apks aswell?
weird apprently no such file as system/app!!
Code:
mount /system
chmod 777 /system/app/application1.apk
etc. Obviously there is no application1.apk, you just put the name of the apk or the odex file (case sensitive) there instead.
Not sure what file isn't in system app that you're talking about?
not just file the whole of system app!
technically it would be /system/app (sorry about that).
In adb
Code:
mount /system
cd /system
ls -lh
this is what i got
cd /system
/system # ls -lh
ls -lh
drwxr-xr-x 1 root root 2.0K Nov 8 11:28 app
drwxr-xr-x 1 root shell 2.0K Nov 8 11:29 bin
-rw-r--r-- 1 root root 8.6K Aug 1 2008 build.pr
drwxr-xr-x 1 root root 2.0K Nov 8 11:29 customiz
drwxr-xr-x 1 root root 2.0K Nov 8 11:29 etc
drwxr-xr-x 1 root root 2.0K Nov 8 11:29 fonts
drwxr-xr-x 1 root root 2.0K Nov 8 11:29 framewor
drwxr-xr-x 1 root root 2.0K Nov 8 11:29 lib
drwxr-xr-x 1 root root 2.0K Nov 8 11:28 lost+fou
drwxr-xr-x 1 root root 2.0K Nov 8 11:29 media
drwxr-xr-x 1 root root 2.0K Nov 8 11:29 sd
drwxr-xr-x 1 root root 2.0K Nov 8 11:29 usr
drwxr-xr-x 1 root shell 2.0K Nov 8 11:29 xbin
dan281082 said:
drwxr-xr-x 1 root root 2.0K Nov 8 11:28 app
Click to expand...
Click to collapse
Well thats the /system/app folder and permission there is normal.
Now:
Code:
cd
cd /system/app
ls -lh
just a snap shot
-rw-r--r-- 1 root root 81.7K Aug 1 2008 AccountSyncManager.apk
-rw-r--r-- 1 root root 62.3K Aug 1 2008 AccountSyncManager.odex
-rw-r--r-- 1 root root 144.3K Aug 1 2008 AppSharing.apk
-rw-r--r-- 1 root root 46.9K Aug 1 2008 AppSharing.odex
-rw-r--r-- 1 root root 11.0K Aug 1 2008 ApplicationsProvider.apk
-rw-r--r-- 1 root root 22.4K Aug 1 2008 ApplicationsProvider.odex
-rw-r--r-- 1 root root 3.9K Aug 1 2008 BRCMBluetoothServices.apk
-rw-r--r-- 1 root root 8.8K Aug 1 2008 BRCMBluetoothServices.ode
x
-rw-r--r-- 1 root root 178.7K Aug 1 2008 Bluetooth.apk
-rw-r--r-- 1 root root 218.0K Aug 1 2008 Bluetooth.odex
-rw-r--r-- 1 root root 494.5K Aug 1 2008 Calendar.apk
-rw-r--r-- 1 root root 729.8K Aug 1 2008 Calendar.odex
-rw-r--r-- 1 root root 31.9K Aug 1 2008 CalendarProvider.apk
-rw-r--r-- 1 root root 951.3K Aug 1 2008 CalendarProvider.odex
-rw-r--r-- 1 root root 20.9K Aug 1 2008 CertInstaller.apk
-rw-r--r-- 1 root root 38.8K Aug 1 2008 CertInstaller.odex
-rw-r--r-- 1 root root 3.5K Aug 1 2008 CheckinProvider.apk
-rw-r--r-- 1 root root 102.7K Aug 1 2008 CheckinProvider.odex
-rw-r--r-- 1 root root 15.8K Aug 1 2008 ContactsProvider.apk
-rw-r--r-- 1 root root 680.4K Aug 1 2008 ContactsProvider.odex
-rw-r--r-- 1 root root 6.5K Aug 1 2008 CustomizationSettingsProv
ider.apk
-rw-r--r-- 1 root root 8.1K Aug 1 2008 CustomizationSettingsProv
ider.odex
-rw-r--r-- 1 root root 35.2K Aug 1 2008 CustomizationSetup.apk
-rw-r--r-- 1 root root 115.1K Aug 1 2008 CustomizationSetup.odex
-rw-r--r-- 1 root root 3.0K Aug 1 2008 DCSImpl.apk
-rw-r--r-- 1 root root 23.1K Aug 1 2008 DCSImpl.odex
-rw-r--r-- 1 root root 3.2K Aug 1 2008 DCSUtility.apk
-rw-r--r-- 1 root root 27.3K Aug 1 2008 DCSUtility.odex
-rw-r--r-- 1 root root 6.2K Aug 1 2008 DebugTool.apk
-rw-r--r-- 1 root root 19.6K Aug 1 2008 DebugTool.odex
-rw-r--r-- 1 root root 4.0K Aug 1 2008 DefaultContainerService.a
pk
-rw-r--r-- 1 root root 16.3K Aug 1 2008 DefaultContainerService.o
dex
-rw-r--r-- 1 root root 31.4K Aug 1 2008 DownloadProvider.apk
-rw-r--r-- 1 root root 877.0K Aug 1 2008 DownloadProvider.odex
-rw-r--r-- 1 root root 31.9K Aug 1 2008 DownloadProviderUi.apk
-rw-r--r-- 1 root root 39.3K Aug 1 2008 DownloadProviderUi.odex
-rw-r--r-- 1 root root 7.0K Aug 1 2008 DrmProvider.apk
-rw-r--r-- 1 root root 59.3K Aug 1 2008 DrmProvider.odex
-rw-r--r-- 1 root root 7.3K Aug 1 2008 FilePicker.apk
-rw-r--r-- 1 root root 4.0K Aug 1 2008 FilePicker.odex
-rw-r--r-- 1 root root 62.5K Aug 1 2008 GSD.apk
-rw-r--r-- 1 root root 101.0K Aug 1 2008 GSD.odex
-rw-r--r-- 1 root root 749.2K Aug 1 2008 Gmail.apk
-rw-r--r-- 1 root root 2.2M Aug 1 2008 Gmail.odex
-rw-r--r-- 1 root root 14.2K Aug 1 2008 GoogleCalendarSyncAdapter
.apk
-rw-r--r-- 1 root root 251.9K Aug 1 2008 GoogleCalendarSyncAdapter
.odex
-rw-r--r-- 1 root root 12.1K Aug 1 2008 GoogleContactsSyncAdapter
.apk
-rw-r--r-- 1 root root 295.7K Aug 1 2008 GoogleContactsSyncAdapter
.odex
-rw-r--r-- 1 root root 34.1K Aug 1 2008 GoogleFeedback.apk
-rw-r--r-- 1 root root 85.3K Aug 1 2008 GoogleFeedback.odex
-rw-r--r-- 1 root root 4.3K Aug 1 2008 GooglePartnerSetup.apk
-rw-r--r-- 1 root root 128.0K Aug 1 2008 GooglePartnerSetup.odex
-rw-r--r-- 1 root root 347.0K Aug 1 2008 GoogleQuickSearchBox.apk
-rw-r--r-- 1 root root 454.3K Aug 1 2008 GoogleQuickSearchBox.odex
-rw-r--r-- 1 root root 501.2K Aug 1 2008 GoogleServicesFramework.a
pk
-rw-r--r-- 1 root root 1.2M Aug 1 2008 GoogleServicesFramework.o
dex
-rw-r--r-- 1 root root 296.5K Aug 1 2008 HTCAlbum.apk
-rw-r--r-- 1 root root 1.3M Aug 1 2008 HTCAlbum.odex
-rw-r--r-- 1 root root 307.4K Aug 1 2008 HTCCamera.apk
-rw-r--r-- 1 root root 656.9K Aug 1 2008 HTCCamera.odex
-rw-r--r-- 1 root root 1.0M Aug 1 2008 HTCSetupWizard.apk
-rw-r--r-- 1 root root 203.6K Aug 1 2008 HTCSetupWizard.odex
-rw-r--r-- 1 root root 7.2M Aug 1 2008 HTC_IME.apk
-rw-r--r-- 1 root root 1.1M Aug 1 2008 HTC_IME.odex
-rw-r--r-- 1 root root 5.5K Aug 1 2008 HTMLViewer.apk
-rw-r--r-- 1 root root 8.3K Aug 1 2008 HTMLViewer.odex
-rw-r--r-- 1 root root 37.6K Aug 1 2008 HtcAddProgramWidget.apk
-rw-r--r-- 1 root root 99.8K Aug 1 2008 HtcAddProgramWidget.odex
-rw-r--r-- 1 root root 10.5K Aug 1 2008 HtcCdmaMccProvider.apk
-rw-r--r-- 1 root root 17.0K Aug 1 2008 HtcCdmaMccProvider.odex
-rw-r--r-- 1 root root 945.3K Aug 1 2008 HtcClockWidget.apk
-rw-r--r-- 1 root root 284.2K Aug 1 2008 HtcClockWidget.odex
-rw-r--r-- 1 root root 813.4K Aug 1 2008 HtcContacts.apk
-rw-r--r-- 1 root root 1.8M Aug 1 2008 HtcContacts.odex
-rw-r--r-- 1 root root 543.4K Aug 1 2008 HtcDialer.apk
-rw-r--r-- 1 root root 604.0K Aug 1 2008 HtcDialer.odex
-rw-r--r-- 1 root root 66.8K Aug 1 2008 HtcLocationPicker.apk
-rw-r--r-- 1 root root 84.5K Aug 1 2008 HtcLocationPicker.odex
-rw-r--r-- 1 root root 37.2K Aug 1 2008 HtcLocationService.apk
seem to be all there
should be rw-r--r-- (chmod 644) so not sure where you first and extra - is from, but also looks correct beyond there.
You cd then chmod 644 -R /system/app/* to be sure.
So cd to /data/data and do again please.
so im cd /system/app
chmod 644 -r/system/app/
then cd /data/data then?
dan281082 said:
so im cd /system/app
chmod 644 -r/system/app/
then cd /data/data then?
Click to expand...
Click to collapse
Code:
cd
chmod 644 -R /system/app/*
cd
mount /data
cd /data/data
ls -lh
By the way this is all case sensitive so ensure -R is capital. Also there is a space after -R
EDIT>
FYI, /data/data content should be rwxr-x--x which if it is not, is a chmod 751
latest error
cd
~ # chmod 644 -R /system/app/*
chmod 644 -R /system/app/*
chmod: /system/app/*: No such file or directory
Are you sure it is typed correctly, definitely? I can even do this on a terminal emulator on my phone itself
as /system still mounted?
EDIT> if it is still mounted and still getting that error, try mounting like below:
Code:
mount -o rw -t yaffs2 /dev/block/mtdblock3 /system
ok managed the system chmod. propbable being dumbo!!
cant seem to cd /data/data now but did earlier and permisions were how u said
Code:
cd
mount /data
chmod 777 /data/data
chmod 777 -R /data/data/*
Just for good measure (some of the contents of /data/data have higher permissions levels. This will be extreme but should add full permissions to everything.

[HOWTO][ROOT] Forget about Odin and Heimdall also does not increase counter

Background: Just purchased a Samsung Galaxy SIII i747 running 4.0.4, but alas I have only a mac and need to root + cwm without tripping the counter. I loved my original galaxy and hope this community continues to flourish.
This was inspired by Noxious Ninja at http://forum.xda-developers.com/showthread.php?t=1790104 and miloj at http://forum.xda-developers.com/showthread.php?t=1704209 so give them some props :good:.
Tools Required:
clockworkmod
Temporary su (found in attachment)
debugfs (also found in attachment)
adb (Found in Android SDK)
optional: if you're using windows then you'll need extra drivers
Note: The su and debugfs were not compiled by me however miloj does provide code for su in his post incase you're concerned they both deserve more props :good:.
Now that you've collected all of the necessary tools it's time to get to work. You should type in lines that are black. The color green should be your response. If something is red it's important.
STEP 1: push debug and su onto your device and locate relavent block devices create a symbolic link for our attack to /system
Make sure usb debugging is enabled. First unarchive the attachment and if your path is correct simply.
Code:
macbook-pro:debugfs_su entropy$ adb push debugfs /data/local/
[COLOR="Lime"]2708 KB/s (1862336 bytes in 0.671s)[/COLOR]
macbook-pro:debugfs_su entropy$ adb push su /data/local/
[COLOR="lime"]2795 KB/s (372006 bytes in 0.129s)[/COLOR]
macbook-pro:debugfs_su entropy$ adb shell
[email protected]:/ $ cd /data/local
[email protected]:/data/local $ mv tmp tmp.back
[email protected]:/data/local $ cd /dev/block/platform/msm_sdcc.1/by-name
[email protected]:/dev/block/platform/msm_sdcc.1/by-name $ ls -al
[COLOR="lime"]lrwxrwxrwx root root 1970-01-25 02:16 aboot -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-25 02:16 backup -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-01-25 02:16 boot -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-01-25 02:16 cache -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-01-25 02:16 efs -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-01-25 02:16 fota -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-01-25 02:16 fsg -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-01-25 02:16 grow -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-01-25 02:16 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-25 02:16 modemst1 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-01-25 02:16 modemst2 -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-01-25 02:16 pad -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-01-25 02:16 param -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-01-25 02:16 persist -> /dev/block/mmcblk0p16
[COLOR="Red"]lrwxrwxrwx root root 1970-01-25 02:16 recovery -> /dev/block/mmcblk0p18[/COLOR]
lrwxrwxrwx root root 1970-01-25 02:16 rpm -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-25 02:16 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-25 02:16 sbl2 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-25 02:16 sbl3 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-25 02:16 ssd -> /dev/block/mmcblk0p22
[COLOR="red"]lrwxrwxrwx root root 1970-01-25 02:16 system -> /dev/block/mmcblk0p14[/COLOR]
lrwxrwxrwx root root 1970-01-25 02:16 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-25 02:16 userdata -> /dev/block/mmcblk0p15[/COLOR]
[email protected]:/dev/block/platform/msm_sdcc.1/by-name $ cd /data/local
[email protected]:/data/local $ ln -s /dev/block/mmcblk0p14 tmp #this comes from one of the red highlights specifically the symbolic link to system
[email protected]:/data/local $ exit
macbook-pro:debugfs_su entropy$ adb reboot
STEP 2: perform the attack and clean up
Code:
macbook-pro:debugfs_su entropy$ adb shell
[email protected]:/ $ cd /data/local
[email protected]:/data/local $ toolbox chmod 755 /data/local/debugfs
[email protected]:/data/local $ /data/local/debugfs -w /data/local/tmp
[COLOR="Lime"]debugfs 1.42 (29-Nov-2011)[/COLOR]
debugfs: cd xbin
debugfs: rm su
[COLOR="Red"]rm: File not found by ext2_lookup while trying to resolve filename[/COLOR] #don't worry about this
debugfs: write /data/local/su su
[COLOR="Lime"]Allocated inode: 533[/COLOR]
debugfs: set_inode_field su mode 0106755
debugfs: set_inode_field su uid 0
debugfs: set_inode_field su gid 0
debugfs: quit
[email protected]:/data/local $ rm tmp
[email protected]:/data/local $ mv tmp.back tmp
[email protected]:/data/local $ exit
macbook-pro:debugfs_su entropy$ adb reboot
STEP 3: Great success
Code:
macbook-pro:debugfs_su entropy$ adb shell
[email protected]:/ $ /system/xbin/su
[COLOR="lime"]Now we be 0:0 ![/COLOR]
[email protected]:/ # id
[COLOR="Lime"]uid=0(root) gid=0(root) groups=1003(graphics),1004(input),1007(log),1009(mount),1011(adb),1015(sdcard_rw),3001(net_bt_admin),3002(net_bt),3003(inet),3006(net_bw_stats)[/COLOR]
[email protected]:/ # exit
[email protected]:/ $ exit
STEP 4: Immediately install superuser and force an upgrade to replace the unsecured su
STEP 5: Install Clockwork
Code:
macbook-pro:Downloads entropy$ adb push recovery-clockwork-5.8.4.5-d2att.img /sdcard/
[COLOR="lime"]3660 KB/s (7170048 bytes in 1.912s) [/COLOR]
macbook-pro:Downloads entropy$ adb shell
[email protected]:/ $ su
[email protected]:/ # id
[COLOR="lime"]uid=0(root) gid=0(root) groups=1003(graphics),1004(input),1007(log),1009(mount),1011(adb),1015(sdcard_rw),3001(net_bt_admin),3002(net_bt),3003(inet),3006(net_bw_stats)[/COLOR]
[email protected]:/ # dd if=recovery-clockwork-5.8.4.5-d2att.img of=/dev/block/mmcblk0p18 #this device file comes from step 1 and is for the recovery partition
[COLOR="lime"]14004+0 records in
14004+0 records out
7170048 bytes transferred in 1.844 secs (3888312 bytes/sec)[/COLOR]
[email protected]:/ # reboot recovery
STEP 6: Celebrate and give yourself a pat on the back, because this will be fixed very quickly
First post! Also, maybe the mods could move this to the appropriate forum.
Thanks for posting this so folks in this forum can see it. The link that you give at the top of your post for Noxious Ninja's thread goes directly to his instructions and, though those are in the Verizon forum, the method works for all US GS3 variants. Nice and easy way to root without having to flash anything in Odin, and it doesn't trip the flash counter.
Noxious Ninja has also put a Windows batch script based tool together that automates this process (it would be easy enough to write a bash script for Linux to do the same thing). I just used the Windows based tool to root stock UCALG1, and it worked great.
Here is the link to Noxious Ninja's automated tool.:
http://forum.xda-developers.com/showthread.php?t=1792342
jscott30 said:
Thanks for posting this so folks in this forum can see it. The link that you give at the top of your post for Noxious Ninja's thread goes directly to his instructions and, though those are in the Verizon forum, the method works for all US GS3 variants. Nice and easy way to root without having to flash anything in Odin, and it doesn't trip the flash counter.
Noxious Ninja has also put a Windows batch script based tool together that automates this process (it would be easy enough to write a bash script for Linux to do the same thing). I just used the Windows based tool to root stock UCALG1, and it worked great.
Here is the link to Noxious Ninja's automated tool.:
http://forum.xda-developers.com/showthread.php?t=1792342
Click to expand...
Click to collapse
Yea, they did most of the work. My carrier is AT&T so I was just happy I could make some progress today with everything coming together despite so much segregation between carriers (I understand why). However, I am a little discouraged by the mysterious IMEI disappearances. I was about to flash cm9 and kt747, but am having second thoughts. I miss my captivate I only flashed it once.
arcadia3go said:
Yea, they did most of the work. My carrier is AT&T so I was just happy I could make some progress today with everything coming together despite so much segregation between carriers (I understand why). However, I am a little discouraged by the mysterious IMEI disappearances. I was about to flash cm9 and kt747, but am having second thoughts. I miss my captivate I only flashed it once.
Click to expand...
Click to collapse
IMEI problems have been solved. There are two threads with two slightly different backup methods and restoration methods. I recommend reading them both and backing up both ways. I know I did.
jscott30 said:
Thanks for posting this so folks in this forum can see it. The link that you give at the top of your post for Noxious Ninja's thread goes directly to his instructions and, though those are in the Verizon forum, the method works for all US GS3 variants. Nice and easy way to root without having to flash anything in Odin, and it doesn't trip the flash counter.
Noxious Ninja has also put a Windows batch script based tool together that automates this process (it would be easy enough to write a bash script for Linux to do the same thing). I just used the Windows based tool to root stock UCALG1, and it worked great.
Here is the link to Noxious Ninja's automated tool.:
http://forum.xda-developers.com/showthread.php?t=1792342
Click to expand...
Click to collapse
off topic but great to see you in the GS3 forums.Loved your roms for the Infuse4g
Woah! Odin seems much simpler lol
Not sure using debugfs on the file system is that great an idea. I posted on this exploit on the Full Disclosure mailing list, and here is what Dan Rosenberg had to say in reply to me. Note in particular his sentence: "Using debugfs to modify the filesystem is completely unnecessary and potentially destructive."
just want to point out that in my case i had to specify full path when installing CWM in step 5
from:
dd if=recovery-clockwork-5.8.4.5-d2att.img of=/dev/block/mmcblk0p18 #this device file comes from step 1 and is for the recovery partition
14004+0 records in
to:
dd if=/sdcard/recovery-clockwork-5.8.4.5-d2att.img of=/dev/block/mmcblk0p18 #this device file comes from step 1 and is for the recovery partition
14004+0 records in
have some problems with CMW after root
CMW worked after the immediate reboot, but somehow lost and the 3e Recovery as back.
I initiated a post here:
http://forum.xda-developers.com/showthread.php?p=30708262#post30708262
Now if only someone can figure out and on device root method.
OP, I think I love you!
Thanks so much for this!

Cannot install any application

I have LG G3 D855 International variant.
32 GB 3 gb ram .
I have not yet used SD card & I am only using internal memory.
I am on CLoudy G3 1.2 kitkat ROM (Android version 4.4.2) .
Uptil yesterday G3 was perfectly fine.
I installed TDKR & Godfire and didn't have any issues.
However, today I uninstalled them and was updating Google , Google Plus , Google Maps , Retrica from Playstore when I got error 'Insufficient Storage' ! and apps didn't update.
Morever , I tried Aptoide and installed simple pomodoro app but still same error !!!
Guys I need urgent help,
Since I cannot believe that I will need to format the phone
I have right now 18 GB USED 8.7 GB free ...
I need a good stable kitkat rom which supports Quick Circle , Xposed , Remote etc (I love Stock) and of course it should be PRE ROOTED and alive (Like on kitkat gets updates and still rom is on kitkat) . What I mean is all updates or development are done with kitkat as permanent base
Have you rebooted into TWRP and cleared your cache and dalvik?
Have you tried clear the cache and data for Play Store?
What is the output of this command in a terminal?:
Code:
df
I rebooted into TWRP and cleared my cache and dalvik.
I cleared the cache and data for Play Store too.
However, still same issue.
The output of this command "df" in a terminal is as belows?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hello
You must verify or phone data if that is rong put in to today
Please can you explain me a bit more clearly ??
To my knowledge, almost no work is being done on KitKat for the G3 at present. Most of the developer attention is on Lollipop and most of that is on AOSP. You are welcome to run a KitKat stock-based ROM, but are not likely to get much support.
Looking at your partitions, the thing that strikes me as an issue is that you are nearing capacity on your /system partition. This important partition is kept relatively small on recent versions of Android, since all user installed apps are moved to /data, which also lends itself to your internal "sdcard" (/data/media).
The problem that, while there is more room on the whole of the device, your /system partition is all but full.
My first guess is that something--possibly a third party app store app--is adding apps at the /system partition instead of /data.
It may also be the log files piling up, so you could try deleting those to free up some space.
Obviously, you could also uninstall some unused apps.
Just curious, have you played at all with AOSP ROMs? The install sizes tend to be far smaller, Xposed is really not needed, and there are some really awesome ones. What is your main reason for wanting to stay on KitKat and/or stock?
Which rom is best ?
epidenimus said:
To my knowledge, almost no work is being done on KitKat for the G3 at present. Most of the developer attention is on Lollipop and most of that is on AOSP. You are welcome to run a KitKat stock-based ROM, but are not likely to get much support.
Looking at your partitions, the thing that strikes me as an issue is that you are nearing capacity on your /system partition. This important partition is kept relatively small on recent versions of Android, since all user installed apps are moved to /data, which also lends itself to your internal "sdcard" (/data/media).
The problem that, while there is more room on the whole of the device, your /system partition is all but full. My guess is that something--possibly a third party app store app-- is adding apps at the /system partition instead of /data. It may also be the log files piling up, so you could try deleting those to free up some space.
Click to expand...
Click to collapse
Today I tried installing apk , it gave low space issue.
I updated Pinterest it updated via google play.
I installed different apps they installed.
I tried updating Gapps same issue.
Used Aptoide to install pomodoro paid app again same issue.
I love stock feel & Xposed framework !
Morever game killer is a must have for me.
Alongwith lucky patcher.
Also I am too camera obsessed & love photography.
SO can you please suggest me the best rom suited to my needs ?
I heard lollipop does not support game killer yet & xposed isn't yet fully supported on lollipop.
Morever , guide me so that in future if I need to go back to kitkat cloudy g3 1.2 is it possible ?
Where is Aptoide installing the apps? Gapps go in /system, so that makes sense that they would fail while others would not. If Aptoide is putting them there, too, that explains it. And if you are installing big games to you /system, then that can easily fill up a couple of gigs.
It's quite likely that flashing a new ROM will not resolve your problem if you intend to build it back to what you have now, so it's kind of a moot point to discuss ROMs.
Have a look in your /system/app directory:
Code:
ls -la /system/app/
Ouput of command ...
epidenimus said:
Where is Aptoide installing the apps? Gapps go in /system, so that makes sense that they would fail while others would not. If Aptoide is putting them there, too, that explains it. And if you are installing big games to you /system, then that can easily fill up a couple of gigs.
It's quite likely that flashing a new ROM will not resolve your problem if you intend to build it back to what you have now, so it's kind of a moot point to discuss ROMs.
Have a look in your /system/app directory:
Code:
ls -la /system/app/
Click to expand...
Click to collapse
By the way from Google Play I cannot update Retrica , uTorrent etc .
Only Pinterest magically got updated.
OUTPUT IS AS BELOW :-
[email protected]:/ $ ls -la /system/app/
-rw-r--r-- root root 281208 2008-08-01 17:30 BoardContentProvider.apk
-rw-r--r-- root root 783128 2008-08-01 17:30 BoardContentProvider.odex
-rw-r--r-- root root 234658 2008-08-01 17:30 CertInstaller.apk
-rw-r--r-- root root 37496 2008-08-01 17:30 CertInstaller.odex
-rw-r--r-- root root 12026946 2008-08-01 17:30 ChromeWithBrowser.apk
-rw-r--r-- root root 4950008 2008-08-01 17:30 ChromeWithBrowser.odex
-rw-r--r-- root root 2530269 2008-08-01 17:30 CloudHub.apk
-rw-r--r-- root root 1952328 2008-08-01 17:30 CloudHub.odex
-rw-r--r-- root root 368647 2008-08-01 17:30 DocumentsUI.apk
-rw-r--r-- root root 486944 2008-08-01 17:30 DocumentsUI.odex
-rw-r--r-- root root 111520 2008-08-01 17:30 DrmService.apk
-rw-r--r-- root root 47640 2008-08-01 17:30 DrmService.odex
-rw-r--r-- root root 29749 2008-08-01 17:30 ELTTest.apk
-rw-r--r-- root root 36728 2008-08-01 17:30 ELTTest.odex
-rw-r--r-- root root 1509686 2008-08-01 17:30 FaceLock.apk
-rw-r--r-- root root 74864 2008-08-01 17:30 FaceLock.odex
-rw-r--r-- root root 11258474 2008-08-01 17:30 Gmail2.apk
-rw-r--r-- root root 4891800 2008-08-01 17:30 Gmail2.odex
-rw-r--r-- root root 15221 2008-08-01 17:30 GnssAirTest.apk
-rw-r--r-- root root 14184 2008-08-01 17:30 GnssAirTest.odex
-rw-r--r-- root root 866060 2008-08-01 17:30 GnssPosTest.apk
-rw-r--r-- root root 1658592 2008-08-01 17:30 GnssPosTest.odex
-rw-r--r-- root root 76908 2008-08-01 17:30 GnssTest.apk
-rw-r--r-- root root 69496 2008-08-01 17:30 GnssTest.odex
-rw-r--r-- root root 752819 2008-08-01 17:30 GoogleCalendarSyncAdapter.apk
-rw-r--r-- root root 608600 2008-08-01 17:30 GoogleCalendarSyncAdapter.odex
-rw-r--r-- root root 206568 2008-08-01 17:30 GoogleContactsSyncAdapter.apk
-rw-r--r-- root root 484360 2008-08-01 17:30 GoogleContactsSyncAdapter.odex
-rw-r--r-- root root 8746631 2008-08-01 17:30 GoogleDrive.apk
-rw-r--r-- root root 6783536 2008-08-01 17:30 GoogleDrive.odex
-rw-r--r-- root root 13821776 2008-08-01 17:30 GoogleTTS.apk
-rw-r--r-- root root 3115872 2008-08-01 17:30 GoogleTTS.odex
-rw-r--r-- root root 21033 2008-08-01 17:30 HTMLViewer.apk
-rw-r--r-- root root 16536 2008-08-01 17:30 HTMLViewer.odex
-rw-r--r-- root root 13640915 2008-08-01 17:30 Hangouts.apk
-rw-r--r-- root root 6814224 2008-08-01 17:30 Hangouts.odex
-rw-r--r-- root root 4610527 2008-08-01 17:30 HiddenMenu.apk
-rw-r--r-- root root 1638392 2008-08-01 17:30 HiddenMenu.odex
-rw-r--r-- root root 219615 2008-08-01 17:30 HiddenSIMUnlockMenu.apk
-rw-r--r-- root root 22552 2008-08-01 17:30 HiddenSIMUnlockMenu.odex
-rw-r--r-- root root 16831 2008-08-01 17:30 InterfacePermissions.apk
-rw-r--r-- root root 5336 2008-08-01 17:30 InterfacePermissions.odex
-rw-r--r-- root root 101627 2008-08-01 17:30 KeyChain.apk
-rw-r--r-- root root 30040 2008-08-01 17:30 KeyChain.odex
-rw-r--r-- root root 98177 2008-08-01 17:30 LGATCMDService.apk
-rw-r--r-- root root 244336 2008-08-01 17:30 LGATCMDService.odex
-rw-r--r-- root root 15182 2008-08-01 17:30 LGApduService.apk
-rw-r--r-- root root 28256 2008-08-01 17:30 LGApduService.odex
-rw-r--r-- root root 2385296 2008-08-01 17:30 LGBluetooth4.apk
-rw-r--r-- root root 1607496 2008-08-01 17:30 LGBluetooth4.odex
-rw-r--r-- root root 17466 2008-08-01 17:30 LGDMSGCM.apk
-rw-r--r-- root root 32784 2008-08-01 17:30 LGDMSGCM.odex
-rw-r--r-- root root 27326 2008-08-01 17:30 LGDefaultAccount.apk
-rw-r--r-- root root 25768 2008-08-01 17:30 LGDefaultAccount.odex
-rw-r--r-- root root 2403 2008-08-01 17:30 LGDivXDRM.apk
-rw-r--r-- root root 19084 2008-08-01 17:30 LGDrm.apk
-rw-r--r-- root root 45382239 2008-08-01 17:30 LGEIME.apk
-rw-r--r-- root root 9706272 2008-08-01 17:30 LGEIME.odex
-rw-r--r-- root root 26804251 2008-08-01 17:30 LGEIME_DICT_XT9_bin.apk
-rw-r--r-- root root 1776 2008-08-01 17:30 LGEIME_DICT_XT9_bin.odex
-rw-r--r-- root root 1325560 2008-08-01 17:30 LGEIME_THEME_BLACK3.apk
-rw-r--r-- root root 1792 2008-08-01 17:30 LGEIME_THEME_BLACK3.odex
-rw-r--r-- root root 6434130 2008-08-01 17:30 LGEasySettings.apk
-rw-r--r-- root root 647816 2008-08-01 17:30 LGEasySettings.odex
-rw-r--r-- root root 2347667 2008-08-01 17:30 LGFmRadio.apk
-rw-r--r-- root root 328768 2015-06-17 14:50 LGFmRadio.odex
-rw-r--r-- root root 22635809 2008-08-01 17:30 LGHome_Theme_Optimus.apk
-rw-r--r-- root root 1944 2008-08-01 17:30 LGHome_Theme_Optimus.odex
-rw-r--r-- root root 11210725 2008-08-01 17:30 LGHome_Theme_TahitiBlue.apk
-rw-r--r-- root root 1912 2008-08-01 17:30 LGHome_Theme_TahitiBlue.odex
-rw-r--r-- root root 9399825 2008-08-01 17:30 LGHome_Theme_TahitiPink.apk
-rw-r--r-- root root 1912 2008-08-01 17:30 LGHome_Theme_TahitiPink.odex
-rw-r--r-- root root 7508509 2008-08-01 17:30 LGHome_Theme_TahitiWhite.apk
-rw-r--r-- root root 1920 2008-08-01 17:30 LGHome_Theme_TahitiWhite.odex
-rw-r--r-- root root 1287265 2008-08-01 17:30 LGLIA.apk
-rw-r--r-- root root 2562368 2008-08-01 17:30 LGLIA.odex
-rw-r--r-- root root 19203776 2008-08-01 17:30 LGLockScreenSettings.apk
-rw-r--r-- root root 177600 2008-08-01 17:30 LGLockScreenSettings.odex
-rw-r--r-- root root 393807 2008-08-01 17:30 LGPCSuiteUI.apk
-rw-r--r-- root root 22856 2008-08-01 17:30 LGPCSuiteUI.odex
-rw-r--r-- root root 161270 2008-08-01 17:30 LGPartnerBookmarksProvider.apk
-rw-r--r-- root root 42184 2008-08-01 17:30 LGPartnerBookmarksProvider.odex
-rw-r--r-- root root 308681 2008-08-01 17:30 LGPhotoAlbumWidget.apk
-rw-r--r-- root root 68856 2008-08-01 17:30 LGPhotoAlbumWidget.odex
-rw-r--r-- root root 6949415 2008-08-01 17:30 LGQRemote.apk
-rw-r--r-- root root 1708680 2008-08-01 17:30 LGQRemote.odex
-rw-r--r-- root root 126338 2008-08-01 17:30 LGSearchWidgetProvider.apk
-rw-r--r-- root root 9672 2008-08-01 17:30 LGSearchWidgetProvider.odex
-rw-r--r-- root root 72864 2008-08-01 17:30 LGSmartcardService.apk
-rw-r--r-- root root 164448 2008-08-01 17:30 LGSmartcardService.odex
-rw-r--r-- root root 767090 2008-08-01 17:30 LGSpringCleaning.apk
-rw-r--r-- root root 120456 2008-08-01 17:30 LGSpringCleaning.odex
-rw-r--r-- root root 735035 2008-08-01 17:30 LGSystemServer.apk
-rw-r--r-- root root 759536 2008-08-01 17:30 LGSystemServer.odex
-rw-r--r-- root root 824077 2008-08-01 17:30 LGTangibleIO.apk
-rw-r--r-- root root 188208 2008-08-01 17:30 LGTangibleIdex
-rw-r--r-- root root 146952 2008-08-01 17:30 LGTelephonyProvider.apk
-rw-r--r-- root root 350584 2008-08-01 17:30 LGTelephonyProvider.odex
-rw-r--r-- root root 1201111 2008-08-01 17:30 LGTextLink.apk
-rw-r--r-- root root 851656 2008-08-01 17:30 LGTextLink.odex
-rw-r--r-- root root 461984 2008-08-01 17:30 LGTextLinkAgent.apk
-rw-r--r-- root root 903272 2008-08-01 17:30 LGTextLinkAgent.odex
-rw-r--r-- root root 24407057 2008-08-01 17:30 LGTextLinkEngine.apk
-rw-r--r-- root root 851840 2008-08-01 17:30 LGTextLinkEngine.odex
-rw-r--r-- root root 88400 2008-08-01 17:30 LGTouchControlAreas.apk
-rw-r--r-- root root 44768 2008-08-01 17:30 LGTouchControlAreas.odex
-rw-r--r-- root root 7806863 2008-08-01 17:30 LGWeather.apk
-rw-r--r-- root root 1252912 2008-08-01 17:30 LGWeather.odex
-rw-r--r-- root root 854245 2008-08-01 17:30 LGWeatherService.apk
-rw-r--r-- root root 923392 2008-08-01 17:30 LGWeatherService.odex
-rw-r--r-- root root 41896912 2008-08-01 17:30 LGWeatherTheme.apk
-rw-r--r-- root root 179128 2008-08-01 17:30 LGWeatherTheme.odex
-rw-r--r-- root root 347580 2008-08-01 17:30 LGWernickeManager.apk
-rw-r--r-- root root 1276056 2008-08-01 17:30 LGWernickeManager.odex
-rw-r--r-- root root 2665298 2008-08-01 17:30 LIAInformant.apk
-rw-r--r-- root root 4417624 2008-08-01 17:30 LIAInformant.odex
-rw-r--r-- root root 1300231 2008-08-01 17:30 LIAMrGDBLogger.apk
-rw-r--r-- root root 3392400 2008-08-01 17:30 LIAMrGDBLogger.odex
-rw-r--r-- root root 431160 2008-08-01 17:30 LIAS4URecommender.apk
-rw-r--r-- root root 1629400 2008-08-01 17:30 LIAS4URecommender.odex
-rw-r--r-- root root 1013843 2008-08-01 17:30 LgNfc.apk
-rw-r--r-- root root 515008 2008-08-01 17:30 LgNfc.odex
-rw-r--r-- root root 745011 2008-08-01 17:30 LicenseProvider.apk
-rw-r--r-- root root 8304 2008-08-01 17:30 LicenseProvider.odex
-rw-r--r-- root root 65039 2008-08-01 17:30 LteConfigs.apk
-rw-r--r-- root root 17456 2015-06-17 14:50 LteConfigs.odex
-rw-r--r-- root root 14496337 2008-08-01 17:30 Maps.apk
-rw-r--r-- root root 10264424 2008-08-01 17:30 Maps.odex
-rw-r--r-- root root 388098 2008-08-01 17:30 MediaUploader.apk
-rw-r--r-- root root 466152 2008-08-01 17:30 MediaUploader.odex
-rw-r--r-- root root 210254 2008-08-01 17:30 OneHandController.apk
-rw-r--r-- root root 92320 2008-08-01 17:30 OneHandController.odex
-rw-r--r-- root root 5632 2008-08-01 17:30 PacProcessor.apk
-rw-r--r-- root root 5880 2008-08-01 17:30 PacProcessor.odex
-rw-r--r-- root root 565967 2008-08-01 17:30 PackageInstaller.apk
-rw-r--r-- root root 159984 2008-08-01 17:30 PackageInstaller.odex
-rw-r--r-- root root 5170 2008-08-01 17:30 PermissionToAccessLgeApi.apk
-rw-r--r-- root root 4000 2008-08-01 17:30 PermissionToAccessLgeApi.odex
-rw-r--r-- root root 217202 2008-08-01 17:30 PrintSpooler.apk
-rw-r--r-- root root 147896 2008-08-01 17:30 PrintSpooler.odex
-rw-r--r-- root root 15337
emerald123 said:
Please can you explain me a bit more clearly ��?
Click to expand...
Click to collapse
Go to definitions
Date end time and verify if there da time actual put in actual AB
And you can download any apk play store
Tutorial please !!!
K203 said:
Go to definitions
Date end time and verify if there da time actual put in actual AB
And you can download any apk play store
Click to expand...
Click to collapse
Please can you post a tutorial on how to do it ?
I am a noob lol
Okay, maybe it is not in the /system/app/ directory... But something is consuming that /system partition far more than it should. You may have to poke around a bit to find out what and where.
emerald123 said:
Please can you post a tutorial on how to do it ?
I am a noob lol
Click to expand...
Click to collapse
go to settings are used and date changes to the current date and so
Good kitkat based rom g3 d855 ?
K203 said:
go to settings are used and date changes to the current date and so
Click to expand...
Click to collapse
Are there any good feature packed kitkat based rom for LG G3 D855 ?
I mean Xposed & Quick circle should be supported !
I tried but I guess it still isn't working

Internal Storage Permission issues

Hello there,
I got a problem with my internal sdcard... I dont have access to certain directorys...
I am trying to delete a file from a folder (Downloads) and it works.
I am trying to delete a file from a folder (one which a app created on a other rom (ressurection)) and it doesent work, even as root i get permission denied.
Some Infos:
Old ROM: Ressurection Remix
ROM: Bumped Lollipop, Stock
Model: D-855
Carrier: None
All Commands as root:
Output of "#ls -la /sdcard/":
Code:
Downloads: drwxrwx--- root sdcard_r some-date some-time Downloads
Other Folder: drwxrwx--- root sdcard_r some-date some-time Folder
Output of "#ls -la /sdcard/Folder/":
Code:
-rw-rw---- root sdcard_r some-size some-date some-time File-to-delete
Output of "#rm -f /sdcard/Folder/File-to-delete":
Code:
rm: File-to-delete: Permission denied
Any Ideas?
EDIT:
Could someone send me the output of "ls -la /sdcard/" and "ls -la /storage/external_SD" of his G3, I wanna try to set Owner and Group and permissions of the folders

Question [BOOTLOOP] Can't edit default.prop and build.prop

My Realme RMX3241 is stuck in a bootloop after upgrading Lsposed.
I'm trying to adb logcat during boot to see what is going on. Problem is my pc is unauthorized (probably i never used adb on my phone/ never enabled usb debugging).
I have access to OrangeFox Custom Recovery and i manually added adb_keys to /data/misc/adb but i'm stuck on editing default.prop and build.prop to enable USB Debugging.
/default.prop when edited goes back to normal after reboot
/system_root/system/build.prop cannot be edited, Custom Recovery throws me "Read only partition" Error.
this are all of the occurences of default.prop and build.prop inside my phone:
Code:
1|RMX3241:/ # find / -name "*default.prop*" 2>/dev/null -exec ls -lh {} \;
lrw------- 1 root root 23 2009-01-01 00:00 /system_root/default.prop -> system/etc/prop.default
-rw------- 1 root root 1.1K 2009-01-01 00:00 /vendor/default.prop
-rw-r--r-- 1 root root 2.7K 2022-07-11 05:42 /odm/etc/fingerprint/build.default.prop
lrwxrwxrwx 1 root root 12 1970-01-01 00:00 /default.prop -> prop.default
1|RMX3241:/ # find / -name "*build.prop*" 2>/dev/null -exec ls -lh {} \;
-rw-r--r-- 1 root root 270 2021-04-23 18:00 /my_preload/build.prop
-rw-r--r-- 1 root root 286 2022-07-14 03:36 /my_stock/build.prop
-rw-r--r-- 1 root root 541 2022-07-11 04:12 /my_heytap/build.prop
-rw-r--r-- 1 root root 820 2022-07-11 04:17 /my_region/build.prop
-rw-r--r-- 1 root root 1.0K 2022-07-11 04:18 /my_carrier/build.prop
-rw-r--r-- 1 root root 1.0K 2022-07-11 04:18 /my_carrier/etc/region/build.prop
-rw-r--r-- 1 root root 84 2021-05-07 19:30 /my_company/build.prop
-rw-r--r-- 1 root root 218 2022-07-11 05:39 /my_engineering/build.prop
-rw-r--r-- 1 root root 3.2K 2022-07-11 05:44 /my_product/build.prop
-rw------- 1 root root 861 2009-01-01 00:00 /product/build.prop
-rw------- 1 root root 3.3K 2009-01-01 00:00 /system_root/system/build.prop
-rw-r--r-- 1 root root 1.4K 2009-01-01 00:00 /system_root/system/euclid_build.prop
-rw------- 1 root root 882 2009-01-01 00:00 /system_root/system/system_ext/build.prop
-rw-r--r-- 1 root root 42 2009-01-01 00:00 /vendor/euclid_build.prop
-rw------- 1 root root 15K 2009-01-01 00:00 /vendor/build.prop
-rw------- 1 root root 875 2009-01-01 00:00 /vendor/odm/etc/build.prop
-rw------- 1 root root 93 2022-07-11 05:42 /odm/etc/build.prop
-rw------- 1 root root 1.5K 2022-07-11 05:42 /odm/build.prop
I'm asking because i'm not sure wether i should edit /default.prop and /system_root/default.prop, wether they are the right files to edit and why i cannot edit these files and maybe find another solution to this problem.
Thank you in advance
UPDATE:
it may be a problem of the custom recovery, I asked information here

Categories

Resources