Question [BOOTLOOP] Can't edit default.prop and build.prop - Realme Narzo 30 5G (AKA Realme 8 5G)

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

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.

[Q] FXP319 soft bricked my c1905?

Hi,
recently i updated via CWM my unblocked, rooted xperia m (C1905). Phone has FXP317, earlier i updated radio installing stock 4.3 and it going well, besides fatal GPS, as usual
After upgrade form FXP317 to FXP319 and reboot phone, it running veeeryy slow and suddenly hangs up. After restart to CWM (it lasts couple minutes), i try to install it again (install from zip) and it failed - it shows problem with mounting /DATA.
Now i attempt to format /DATA but it failed - CWM says that partition can't be mounted.
Another try - flash stock rom (Flasher form Androxyde) gives
Code:
19/048/2014 07:48:57 - INFO - Device connected in flash mode
19/049/2014 07:49:06 - INFO - Selected Bundle for Xperia M C1905. FW release : Google Android 4.3 (Jelly Bean). Customization : 15.4.A.0.23
19/049/2014 07:49:06 - INFO - Preparing files for flashing
19/049/2014 07:49:53 - INFO - Please connect your device into flashmode.
19/049/2014 07:49:54 - INFO - Opening device for R/W
19/049/2014 07:49:54 - INFO - Reading device information
19/049/2014 07:49:54 - INFO - Phone ready for flashmode operations.
19/049/2014 07:49:54 - INFO - Current device : Unknown: Mar 7 2014/10:51:59 - YT910M7GB9 - Unknown: Mar 7 2014/10:51:59 - Unknown: Mar 7 2014/10:51:59 - Unknown: Mar 7 2014/10:51:59
19/049/2014 07:49:54 - INFO - Start Flashing
19/049/2014 07:49:54 - INFO - Processing loader.sin
19/049/2014 07:49:54 - INFO - Checking header
19/049/2014 07:49:54 - INFO - Flashing data
19/049/2014 07:49:55 - INFO - Processing of loader.sin finished.
19/049/2014 07:49:55 - INFO - Loader : S1_Root_dbe9 - Version : loader_MSM8X30_10 / Boot version : S1_Boot_MSM_8227_5 / Bootloader status : ROOTED
19/049/2014 07:49:55 - INFO - Processing partition-image.sin
19/049/2014 07:49:55 - INFO - Checking header
19/049/2014 07:49:55 - INFO - Flashing data
19/049/2014 07:49:55 - INFO - Processing of partition-image.sin finished.
19/049/2014 07:49:55 - INFO - Parsing boot delivery
19/049/2014 07:49:55 - INFO - Phone boot version : S1_Boot_MSM_8227_5. Boot delivery version : S1_Boot_MSM_8227_5
19/049/2014 07:49:55 - INFO - Boot delivery up to date. Nothing to do
19/049/2014 07:49:55 - INFO - Processing kernel.sin
19/049/2014 07:49:55 - INFO - Checking header
19/049/2014 07:49:55 - INFO - Flashing data
19/049/2014 07:49:55 - ERROR - Processing of kernel.sin finished with errors.
19/049/2014 07:49:55 - INFO - Ending flash session
19/049/2014 07:49:55 - ERROR - ERR_SEVERITY="MINOR";ERR_CODE="0017";ERR_DYNAMIC="0x8020001C ";
Soft from SONY - SUS, PC Companion, EMMA did't recognize my phone and gives up.
Meanwhile i flash kernel and i made fatal mistake (i thought so) - i tried to flash wrong kernel (it has 83 bytes), but after choosing the right file I could install the appropriate kernel.
Now i have CWM 6.0.4.8, and i can connect phone in flash mode, also in fastboot but i can't flash any rom because i can't mount /data
Command adb devices -l gives
List of devices attached
YT910M7GB9 recovery product:C1905 model:C1905 device:nicki
How to mount /data or how to do the re-partition? What should I do to flash the stock rom?
Have you flashed the stock ROM again? Does it still show the same error?
elmkzgirxp said:
Have you flashed the stock ROM again? Does it still show the same error?
Click to expand...
Click to collapse
Yes, i did and same again. I have stock ROM 4.1.2, stock ROM 4.3. One thing - phone starts and - after maybe 30 min or so - stops on "Encryption unsuccessful bla bla bla". I try even recovery backup form http://forum.xda-developers.com/showthread.php?p=51574842 but it failed - folder /system cannot be restored.
I'm thinking about partitioning internal memory, but i don't know how. I have an access via flashmode and i'm looking for solution about using adb
Encryption? How'd that get there?
elmkzgirxp said:
Encryption? How'd that get there?
Click to expand...
Click to collapse
In my case - remove battery, wait 5 sec, i turn on the phone and wait about 30 min - after that long boot this is all i see.
TomekParuszewski said:
In my case - remove battery, wait 5 sec, i turn on the phone and wait about 30 min - after that long boot this is all i see.
Click to expand...
Click to collapse
Why not refer here... This might solve your problem.
elmkzgirxp said:
Why not refer here... This might solve your problem.
Click to expand...
Click to collapse
Thx, so far i don't find exactly the same problem as mine, but now i try rubber band trick. I don't know how this will help, will see
Exact same problem
With fxp 18
TomekParuszewski said:
Thx, so far i don't find exactly the same problem as mine, but now i try rubber band trick. I don't know how this will help, will see
Click to expand...
Click to collapse
Hmm, according to the definition of soft brick, and therefore that I can enter fastboot mode and flashmode and CWM, the phone is not soft bricked, but there is a problem with partitions or privileges SU, because I can not reflash rom. The system is still not able to mount the directory / data.
I will try connect to phone by the adb command and see, err, i don't know what - i must check available commands. Right now i'm waiting for CWM
After get into adb shell i get:
Code:
C:\SDK\sdk\platform-tools>adb shell
~ # ←[6nsu
su
/sbin/sh: su: not found
~ # ←[6ndf
df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 440892 128 440764 0% /dev
tmpfs 440892 8 440884 0% /tmp
tmpfs 440892 0 440892 0% /storage
tmpfs 440892 0 440892 0% /mnt/secure
tmpfs 440892 0 440892 0% /mnt/fuse
/dev/block/platform/msm_sdcc.1/by-name/cache
252136 4660 247476 2% /cache
~ # ←[6nls -l
ls -l
__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
drwxr-xr-x 2 root root 0 May 21 04:33 boot
-rw-r--r-- 1 root root 579 May 21 04:33 boot.txt
drwxrwx--x 6 system cache 4096 May 17 10:36 cache
-rwxr-x--- 1 root root 284696 May 21 04:33 charger
drwxr-xr-x 3 root root 0 May 21 04:33 data
drwxr-xr-x 2 root root 0 May 21 04:33 datadata
-rw-r--r-- 1 root root 3920 May 21 04:33 default.prop
drwxr-xr-x 10 root root 3260 May 21 04:33 dev
drwxr-xr-x 2 root root 0 May 21 04:33 emmc
drwxr-xr-x 2 root root 0 May 21 04:33 etc
drwxr-xr-x 2 root root 0 May 21 04:33 external_sd
-rw-r--r-- 1 root root 10961 May 21 04:33 file_contexts
-rw-r----- 1 root root 1213 May 21 04:33 fstab.qcom
-rwxr-x--- 1 root root 187840 May 21 04:33 init
-rwxr-x--- 1 root root 2704 May 21 04:33 init.qcom.syspart_fixup.sh
-rwxr-x--- 1 root root 2892 May 21 04:33 init.rc
-rwxr-x--- 1 root root 512 May 21 04:33 init.recovery.qcom.rc
drwxr-xr-x 2 root root 0 May 21 04:33 internal_sd
-rw-r--r-- 1 root root 14452 Jan 1 1970 logo.rle
drwxrwxr-x 5 root system 0 May 21 04:33 mnt
dr-xr-xr-x 131 root root 0 Jan 1 1970 proc
-rw-r--r-- 1 root root 2161 May 21 04:33 property_contexts
drwxr-xr-x 2 root root 0 May 21 04:33 recovery
drwxr-xr-x 3 root root 0 May 21 04:33 res
drwx------ 2 root root 0 May 13 22:52 root
drwxr-x--- 2 root root 0 May 21 04:33 sbin
drwxr-xr-x 2 root root 0 May 21 04:33 sd-ext
lrwxrwxrwx 1 root root 11 May 21 04:33 sdcard -> /data/media
-rw-r--r-- 1 root root 660 May 21 04:33 seapp_contexts
-rw-r--r-- 1 root root 95689 May 21 04:33 sepolicy
d---r-x--- 2 root sdcard_r 40 May 21 04:33 storage
dr-xr-xr-x 14 root root 0 May 21 04:33 sys
drwxr-xr-x 3 root root 0 May 21 04:33 system
drwxrwxr-x 2 root shell 60 May 21 04:33 tmp
-rw-r--r-- 1 root root 8196 May 21 04:33 ueventd.qcom.rc
-rw-r--r-- 1 root root 7275 May 21 04:33 ueventd.rc
C:\SDK\sdk\platform-tools>adb remount
remount failed: Success
C:\SDK\sdk\platform-tools>adb devices -l
List of devices attached
YT910M7GB9 recovery product:C1905 model:C1905 device:nicki
C:\SDK\sdk\platform-tools>adb shell
~ # ←[6nls -l
ls -l
__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
drwxr-xr-x 2 root root 0 May 21 04:33 boot
-rw-r--r-- 1 root root 579 May 21 04:33 boot.txt
drwxrwx--x 6 system cache 4096 May 17 10:36 cache
-rwxr-x--- 1 root root 284696 May 21 04:33 charger
drwxr-xr-x 3 root root 0 May 21 04:33 data
drwxr-xr-x 2 root root 0 May 21 04:33 datadata
-rw-r--r-- 1 root root 3920 May 21 04:33 default.prop
drwxr-xr-x 10 root root 3260 May 21 04:33 dev
drwxr-xr-x 2 root root 0 May 21 04:33 emmc
drwxr-xr-x 2 root root 0 May 21 04:33 etc
drwxr-xr-x 2 root root 0 May 21 04:33 external_sd
-rw-r--r-- 1 root root 10961 May 21 04:33 file_contexts
-rw-r----- 1 root root 1213 May 21 04:33 fstab.qcom
-rwxr-x--- 1 root root 187840 May 21 04:33 init
-rwxr-x--- 1 root root 2704 May 21 04:33 init.qcom.syspart_fixup.sh
-rwxr-x--- 1 root root 2892 May 21 04:33 init.rc
-rwxr-x--- 1 root root 512 May 21 04:33 init.recovery.qcom.rc
drwxr-xr-x 2 root root 0 May 21 04:33 internal_sd
-rw-r--r-- 1 root root 14452 Jan 1 1970 logo.rle
drwxrwxr-x 5 root system 0 May 21 04:33 mnt
dr-xr-xr-x 131 root root 0 Jan 1 1970 proc
-rw-r--r-- 1 root root 2161 May 21 04:33 property_contexts
drwxr-xr-x 2 root root 0 May 21 04:33 recovery
drwxr-xr-x 3 root root 0 May 21 04:33 res
drwx------ 2 root root 0 May 13 22:52 root
drwxr-x--- 2 root root 0 May 21 04:33 sbin
drwxr-xr-x 2 root root 0 May 21 04:33 sd-ext
lrwxrwxrwx 1 root root 11 May 21 04:33 sdcard -> /data/media
-rw-r--r-- 1 root root 660 May 21 04:33 seapp_contexts
-rw-r--r-- 1 root root 95689 May 21 04:33 sepolicy
d---r-x--- 2 root sdcard_r 40 May 21 04:33 storage
dr-xr-xr-x 14 root root 0 May 21 04:33 sys
drwxr-xr-x 3 root root 0 May 21 04:33 system
drwxrwxr-x 2 root shell 60 May 21 04:33 tmp
-rw-r--r-- 1 root root 8196 May 21 04:33 ueventd.qcom.rc
-rw-r--r-- 1 root root 7275 May 21 04:33 ueventd.rc
~ # ←[6ndf
df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 440892 128 440764 0% /dev
tmpfs 440892 8 440884 0% /tmp
tmpfs 440892 0 440892 0% /storage
tmpfs 440892 0 440892 0% /mnt/secure
tmpfs 440892 0 440892 0% /mnt/fuse
/dev/block/platform/msm_sdcc.1/by-name/cache
252136 4660 247476 2% /cache
C:\SDK\sdk\platform-tools>adb shell
~ # ←[6ndf -h
df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 430.6M 128.0K 430.4M 0% /dev
tmpfs 430.6M 8.0K 430.6M 0% /tmp
tmpfs 430.6M 0 430.6M 0% /storage
tmpfs 430.6M 0 430.6M 0% /mnt/secure
tmpfs 430.6M 0 430.6M 0% /mnt/fuse
/dev/block/platform/msm_sdcc.1/by-name/cache
246.2M 4.6M 241.7M 2% /cache
~ # ←[6nfdisk
fdisk
BusyBox v1.22.1 static (2014-04-06 21:24 +0200) multi-call binary.
Usage: fdisk [-ul] [-C CYLINDERS] [-H HEADS] [-S SECTORS] [-b SSZ] DISK
Change partition table
-u Start and End are in sectors (instead of cylinders)
-l Show partition table for each DISK, then exit
-b 2048 (for certain MO disks) use 2048-byte sectors
-C CYLINDERS Set number of cylinders/heads/sectors
-H HEADS
-S SECTORS
~ # ←[6nfdisk -l
fdisk -l
~ # ←[6nfdisk -l
fdisk -l
~ # ←[6n^C
C:\SDK\sdk\platform-tools>
C:\SDK\sdk\platform-tools>adb shell
~ # ←[6nls
ls
boot logo.rle
boot.txt mnt
cache proc
charger property_contexts
data recovery
datadata res
default.prop root
dev sbin
emmc sd-ext
etc sdcard
external_sd seapp_contexts
file_contexts sepolicy
fstab.qcom storage
init sys
init.qcom.syspart_fixup.sh system
init.rc tmp
init.recovery.qcom.rc ueventd.qcom.rc
internal_sd ueventd.rc
~ # ←[6ndf
df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 440892 128 440764 0% /dev
tmpfs 440892 8 440884 0% /tmp
tmpfs 440892 0 440892 0% /storage
tmpfs 440892 0 440892 0% /mnt/secure
tmpfs 440892 0 440892 0% /mnt/fuse
/dev/block/platform/msm_sdcc.1/by-name/cache
252136 4660 247476 2% /cache
~ # ←[6ncd data
cd data
/data # ←[6nls
ls
media
/data # ←[6n^C
C:\SDK\sdk\platform-tools>adb shell
~ # ←[6nls -l
ls -l
__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
drwxr-xr-x 2 root root 0 May 21 04:33 boot
-rw-r--r-- 1 root root 579 May 21 04:33 boot.txt
drwxrwx--x 6 system cache 4096 May 17 10:36 cache
-rwxr-x--- 1 root root 284696 May 21 04:33 charger
drwxr-xr-x 3 root root 0 May 21 04:33 data
drwxr-xr-x 2 root root 0 May 21 04:33 datadata
-rw-r--r-- 1 root root 3920 May 21 04:33 default.prop
drwxr-xr-x 10 root root 3260 May 21 04:33 dev
drwxr-xr-x 2 root root 0 May 21 04:33 emmc
drwxr-xr-x 2 root root 0 May 21 04:33 etc
drwxr-xr-x 2 root root 0 May 21 04:33 external_sd
-rw-r--r-- 1 root root 10961 May 21 04:33 file_contexts
-rw-r----- 1 root root 1213 May 21 04:33 fstab.qcom
-rwxr-x--- 1 root root 187840 May 21 04:33 init
-rwxr-x--- 1 root root 2704 May 21 04:33 init.qcom.syspart_fixup.sh
-rwxr-x--- 1 root root 2892 May 21 04:33 init.rc
-rwxr-x--- 1 root root 512 May 21 04:33 init.recovery.qcom.rc
drwxr-xr-x 2 root root 0 May 21 04:33 internal_sd
-rw-r--r-- 1 root root 14452 Jan 1 1970 logo.rle
drwxrwxr-x 5 root system 0 May 21 04:33 mnt
dr-xr-xr-x 131 root root 0 Jan 1 1970 proc
-rw-r--r-- 1 root root 2161 May 21 04:33 property_contexts
drwxr-xr-x 2 root root 0 May 21 04:33 recovery
drwxr-xr-x 3 root root 0 May 21 04:33 res
drwx------ 2 root root 0 May 13 22:52 root
drwxr-x--- 2 root root 0 May 21 04:33 sbin
drwxr-xr-x 2 root root 0 May 21 04:33 sd-ext
lrwxrwxrwx 1 root root 11 May 21 04:33 sdcard -> /data/media
-rw-r--r-- 1 root root 660 May 21 04:33 seapp_contexts
-rw-r--r-- 1 root root 95689 May 21 04:33 sepolicy
d---r-x--- 2 root sdcard_r 40 May 21 04:33 storage
dr-xr-xr-x 14 root root 0 May 21 04:33 sys
drwxr-xr-x 3 root root 0 May 21 04:33 system
drwxrwxr-x 2 root shell 60 May 21 04:33 tmp
-rw-r--r-- 1 root root 8196 May 21 04:33 ueventd.qcom.rc
-rw-r--r-- 1 root root 7275 May 21 04:33 ueventd.rc
I don't have any information about partitions (filesystem tmpfs)!
TomekParuszewski said:
I don't have any information about partitions (filesystem tmpfs)!
Click to expand...
Click to collapse
Firstly you need mount partitions through recovery: item mounts and storage
Also from there try to format all of them and then flash via flashtool / via ZIP / restore backup.
Here is possibility that your NAND-flash (internal 4GB memory chip) broken or have a lot bad sectors.
Bonoboo said:
Firstly you need mount partitions through recovery: item mounts and storage
Also from there try to format all of them and then flash via flashtool / via ZIP / restore backup.
Here is possibility that your NAND-flash (internal 4GB memory chip) broken or have a lot bad sectors.
Click to expand...
Click to collapse
Unfortunately, I can not mount / data or / system. After a very long time the command mount / data, then throws an error, the contents of which I can not remember now. I will try to rewrite its contents exactly as it appears. is below:
(i'm wainting rught now - 14:29)
I have version 6.0.4.8 CWM and I see no formatting options. I tried to upload the CWM 6.0.4.7 from this post http://forum.xda-developers.com/showthread.php?t=2494793 but I could not do that. I still have my version. My bad, of course i have format command.
Does this mean that my phone died? Do I still have any chance to fix it?
TomekParuszewski said:
After a very long time the command mount / data, then throws an error, the contents of which I can not remember now. I will try to rewrite its contents exactly as it appears.
Click to expand...
Click to collapse
Command from ADB? Try from recovery menu.
And output of command will be helpful.
TomekParuszewski said:
Does this mean that my phone died?
Click to expand...
Click to collapse
Don't give up for now.
UPD: I googled ERR_DYNAMIC=0x8020001C and found 7 threads with same problem with Xperia M:
1, 2, 3, 4, 5, 6, 7
All them have error while flashing different parts: kernel and data.
And no solution there for now.
Bonoboo said:
Command from ADB? Try from recovery menu.
And output of command will be helpful.
Don't give up for now.
Click to expand...
Click to collapse
thank you for your words of encouragement - I'm gonna fight to the end
BTW - in time when i'm waiting to output for command mount /data from recovery, I have access to the phone via adb (but it's normal after all, i suppose)
Bonoboo said:
UPD: I googled ERR_DYNAMIC=0x8020001C and found 6 threads with same problem with Xperia M:
1, 2, 3, 4, 5, 6
All them have error while flashing different parts: kernel and data.
And no solution there for now.
Click to expand...
Click to collapse
yes, most of them i've seen, thx
Just info :
Re-partition method not available for now.
Maybe when flashing via flashtool keep tick only on partition-image.sin restore stock.
There is some method to erase internal memory via adb, but it for other model.
And I don't know will it help here.
Questions:
1. So your device not was encrypted, right?
2. Try mounts and storage > format all
3. Try mount via menu in recovery
Bonoboo said:
Just info :
Re-partition method not available for now.
Maybe when flashing via flashtool keep tick only on partition-image.sin restore stock.
There is some method to erase internal memory via adb, but it for other model.
And I don't know will it help here.
Questions:
1. So your device not was encrypted, right?
3. You sure that in mounts and storage no format options?
4. Try mount via menu in recovery?
2. How about post error while mounting?
Click to expand...
Click to collapse
Answers:
If i'm wait long enough, phone boot to screen "Encryption unsuccessful", so i don't know - I do not encrypt the phone as I remember
Sorry, of course there is format command in recovery, my bad
I will try again and write exact message from the screen
Sorry for messing numbers, I edited post.
TomekParuszewski said:
in time when i'm waiting to output for command mount /data from recovery, I have access to the phone via adb (but it's normal after all, i suppose)
Click to expand...
Click to collapse
Seems not. Reboot.
Try formatting.
Just note about adb output earlier.
ls shows temporary FS that recovery creates in RAM.
By fact blocks devices in /dev/block/ and we can do something with them, like recreate partitions using mke2fs
Or erase them by dd if=/dev/zero
Try commands:
cat /proc/partitions
mount
fdisk -l /dev/block/mmcblk0p17
fdisk -l /dev/block/mmcblk0p5
And try flashing via flashtool:
– untick wipe data and cache
– tick all in Exclude section except partition
Here useful commands (similar problem for Samsung, restoring partition table helps)
And here list of all our partitions relatively number:
FOTAKernel -> /dev/block/mmcblk0p23
LTALabel -> /dev/block/mmcblk0p16
TA -> /dev/block/mmcblk0p1
aboot -> /dev/block/mmcblk0p6
alt_aboot -> /dev/block/mmcblk0p12
alt_rpm -> /dev/block/mmcblk0p15
alt_s1sbl2 -> /dev/block/mmcblk0p10
alt_sbl1 -> /dev/block/mmcblk0p8
alt_sbl2 -> /dev/block/mmcblk0p9
alt_sbl3 -> /dev/block/mmcblk0p11
alt_tz -> /dev/block/mmcblk0p13
boot -> /dev/block/mmcblk0p17
cache -> /dev/block/mmcblk0p26
fsg -> /dev/block/mmcblk0p21
modem -> /dev/block/mmcblk0p18
modemst1 -> /dev/block/mmcblk0p19
modemst2 -> /dev/block/mmcblk0p20
persist -> /dev/block/mmcblk0p24
ramdump -> /dev/block/mmcblk0p22
rpm -> /dev/block/mmcblk0p14
s1sbl2 -> /dev/block/mmcblk0p4
sbl1 -> /dev/block/mmcblk0p2
sbl2 -> /dev/block/mmcblk0p3
sbl3 -> /dev/block/mmcblk0p5
system -> /dev/block/mmcblk0p25
tz -> /dev/block/mmcblk0p7
userdata -> /dev/block/mmcblk0p27
Bonoboo said:
Sorry for messing numbers, I edited post.
Seems not. Reboot.
Try formatting.
Just note about adb output earlier.
ls shows temporary FS that recovery creates in RAM.
By fact blocks devices in /dev/block/ and we can do something with them, like recreate partitions using mke2fs
Or erase them by dd if=/dev/zero
Try commands:
cat /proc/partitions
mount
fdisk -l /dev/block/mmcblk0p17
fdisk -l /dev/block/mmcblk0p5
And try flashing via flashtool:
– untick wipe data and cache
– tick all in Exclude section except partition
Here useful commands (similar problem for Samsung, restoring partition table helps)
And here list of all our partitions relatively number:
Click to expand...
Click to collapse
ok, here the log from CWM - i don't know when each event occurred
Code:
persist.audio.low.latency.rec=false
persist.debug.wfd.enable=1
persist.radio.apm_sim_not_pwdn=1
persist.timed.enable=true
persist.fuse_sdcard=true
keyguard.no_require_sim=true
telephonu.lteOnCdmaDevice=0
DEVICE_PROVISIONED=1
I: Checking for extendedcommand
I:Skipping for extendedcommand, file not found...
I:Can't partition non mmcblk device: /devices/platform/msm_sdcc.3/mmc_host/mmc1
I:using /data/media for /sdcard/0/clockworkmod/.no_confirm.
mount: mounting /dev/block/platform/msm_sdcc.1/by-name/userdata on /data failed: invalid argument
W:failed to mount /dev/block/platform/msm_sdcc.1/by-name/userdata (File exists)
I:using /data/media for /sdcard/0/clockworkmod/.many_confirm.
mount: mounting /dev/block/platform/msm_sdcc.1/by-name/userdata on /data failed: invalid argument
W:failed to mount /dev/block/platform/msm_sdcc.1/by-name/userdata (File exists)
I:Can't partition non mmcblk device: /devices/platform/msm_sdcc.3/mmc_host/mmc1
And here is the result of your command
Code:
C:\adt-bundle-windows-x86-20140321\adt-bundle-windows-x86-20140321\sdk\platform-
tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
YT910M7GB9 recovery
C:\adt-bundle-windows-x86-20140321\adt-bundle-windows-x86-20140321\sdk\platform-
tools>adb shell
~ # ←[6ncat /proc/partitions
cat /proc/partitions
major minor #blocks name
179 0 3866624 mmcblk0
179 1 2048 mmcblk0p1
179 2 128 mmcblk0p2
179 3 256 mmcblk0p3
179 4 256 mmcblk0p4
179 5 512 mmcblk0p5
179 6 512 mmcblk0p6
179 7 512 mmcblk0p7
179 8 128 mmcblk0p8
179 9 256 mmcblk0p9
179 10 256 mmcblk0p10
179 11 512 mmcblk0p11
179 12 512 mmcblk0p12
179 13 512 mmcblk0p13
179 14 512 mmcblk0p14
179 15 512 mmcblk0p15
179 16 16384 mmcblk0p16
179 17 20480 mmcblk0p17
179 18 65536 mmcblk0p18
179 19 3072 mmcblk0p19
179 20 3072 mmcblk0p20
179 21 3072 mmcblk0p21
179 22 5120 mmcblk0p22
179 23 16384 mmcblk0p23
179 24 4096 mmcblk0p24
179 25 1228800 mmcblk0p25
179 26 256000 mmcblk0p26
179 27 2183151 mmcblk0p27
179 32 1955840 mmcblk1
179 33 1954816 mmcblk1p1
~ # ←[6nls -la /dev/block/mmcblk*
ls -la /dev/block/mmcblk*
__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
brw------- 1 root root 179, 0 May 21 11:43 /dev/block/mmcblk0
brw------- 1 root root 179, 1 May 21 11:43 /dev/block/mmcblk0p1
brw------- 1 root root 179, 10 May 21 11:43 /dev/block/mmcblk0p10
brw------- 1 root root 179, 11 May 21 11:43 /dev/block/mmcblk0p11
brw------- 1 root root 179, 12 May 21 11:43 /dev/block/mmcblk0p12
brw------- 1 root root 179, 13 May 21 11:43 /dev/block/mmcblk0p13
brw------- 1 root root 179, 14 May 21 11:43 /dev/block/mmcblk0p14
brw------- 1 root root 179, 15 May 21 11:43 /dev/block/mmcblk0p15
brw------- 1 root root 179, 16 May 21 11:43 /dev/block/mmcblk0p16
brw------- 1 root root 179, 17 May 21 11:43 /dev/block/mmcblk0p17
brw------- 1 root root 179, 18 May 21 11:43 /dev/block/mmcblk0p18
brw------- 1 root root 179, 19 May 21 11:43 /dev/block/mmcblk0p19
brw------- 1 root root 179, 2 May 21 11:43 /dev/block/mmcblk0p2
brw------- 1 root root 179, 20 May 21 11:43 /dev/block/mmcblk0p20
brw------- 1 root root 179, 21 May 21 11:43 /dev/block/mmcblk0p21
brw------- 1 root root 179, 22 May 21 11:43 /dev/block/mmcblk0p22
brw------- 1 root root 179, 23 May 21 11:43 /dev/block/mmcblk0p23
brw------- 1 root root 179, 24 May 21 11:43 /dev/block/mmcblk0p24
brw------- 1 root root 179, 25 May 21 11:43 /dev/block/mmcblk0p25
brw------- 1 root root 179, 26 May 21 11:43 /dev/block/mmcblk0p26
brw------- 1 root root 179, 27 May 21 11:43 /dev/block/mmcblk0p27
brw------- 1 root root 179, 3 May 21 11:43 /dev/block/mmcblk0p3
brw------- 1 root root 179, 4 May 21 11:43 /dev/block/mmcblk0p4
brw------- 1 root root 179, 5 May 21 11:43 /dev/block/mmcblk0p5
brw------- 1 root root 179, 6 May 21 11:43 /dev/block/mmcblk0p6
brw------- 1 root root 179, 7 May 21 11:43 /dev/block/mmcblk0p7
brw------- 1 root root 179, 8 May 21 11:43 /dev/block/mmcblk0p8
brw------- 1 root root 179, 9 May 21 11:43 /dev/block/mmcblk0p9
brw------- 1 root root 179, 32 May 21 11:43 /dev/block/mmcblk1
brw------- 1 root root 179, 33 May 21 11:43 /dev/block/mmcblk1p1
~ # ←[6nmount
mount
rootfs on / type rootfs (rw,seclabel,relatime)
tmpfs on /dev type tmpfs (rw,seclabel,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,seclabel,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,seclabel,relatime)
selinuxfs on /sys/fs/selinux type selinuxfs (rw,relatime)
tmpfs on /tmp type tmpfs (rw,seclabel,relatime)
tmpfs on /storage type tmpfs (rw,seclabel,relatime,mode=050,gid=1028)
tmpfs on /mnt/secure type tmpfs (rw,seclabel,relatime,mode=700)
tmpfs on /mnt/fuse type tmpfs (rw,seclabel,relatime,mode=775,gid=1000)
/dev/block/platform/msm_sdcc.1/by-name/cache on /cache type ext4 (rw,seclabel,re
latime,data=ordered)
~ # ←[6nfdisk -l /dev/block/mmcblk0p17
fdisk -l /dev/block/mmcblk0p17
Disk /dev/block/mmcblk0p17: 20 MB, 20971520 bytes
4 heads, 16 sectors/track, 640 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0p17 doesn't contain a valid partition table
~ # ←[6nfdisk -l /dev/block/mmcblk0p5
fdisk -l /dev/block/mmcblk0p5
Disk /dev/block/mmcblk0p5: 0 MB, 524288 bytes
4 heads, 16 sectors/track, 16 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0p5 doesn't contain a valid partition table
~ # ←[6n
C:\adt-bundle-windows-x86-20140321\adt-bundle-windows-x86-20140321\sdk\platform-
tools>
If both partitions are incorrect, should I try to flash?

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

(Solved) [Android 6.x] SuperSU Root not working - Cannot obtain root on Marshmallow

SOLVED!
While I was S-OFF, I was not Bootloader Unlocked...
HUGE thanks to Andybones and santod040!!
Solution a few posts down.
--ORIGINAL POST--
I cannot obtain Root on my Marshmallow 6.0 Verizon HTC One M9 phone (HTC6535LVW) . I have tried all the methods, and have flashed all the ROMs.
I have gone through the steps of upgrading to Android 6.0 both manually, and letting OTA do it from the oldest RUU I could find.
Here is some minor info...
Code:
hTC download mode
*** LOCKED ***
htc_himawl PVT S-OFF
CID-11111111
LK-1.0.0.0000
[email protected]
OpenDSP-15.6.1.00522.8994_1026
OS-3.37.605.7
Jan 28 2016,20:52:56(669662)
The recovery.log seems to spit out errors every time it flashes SuperSU which leads me to believe it is an issue with SuperSU, but I cannot for the life of me figure out why...
Here is the outline of my entire process from start to finish, including a suggestion from a forum member in the beginning.
Code:
C:\adb>md5sum 3.37.605.7_FULL_firmware.zip
0285e23f98c44aebe9150f1e2c33a3b4 *3.37.605.7_FULL_firmware.zip
C:\adb>md5sum 3.37.605.7_HIMA_WL_M60_SENSE70_VZW_MR_Full_DEODEX.zip
6164c613d0fe7eb09fe111944848bc80 *3.37.605.7_HIMA_WL_M60_SENSE70_VZW_MR_Full_DEO
DEX.zip
C:\adb>md5sum 3.37.605.7_HIMA_WL_M60_SENSE70_VZW_MR_Full_ODEX.zip
250a94e294a0fc0f10f9b4abf3e456e5 *3.37.605.7_HIMA_WL_M60_SENSE70_VZW_MR_Full_ODE
X.zip
C:\adb>md5sum 3.37.605.7_NoBoot_TWRP3.00-1_firmware.zip
2979ebc4e8b64a7b8fc24e99e6f5a2fb *3.37.605.7_NoBoot_TWRP3.00-1_firmware.zip
C:\adb>md5sum 3.37.605.7_Stock_BootImg.zip
3272dcc7aee5b38dc335a6cdaf076417 *3.37.605.7_Stock_BootImg.zip
Those are the MD5sums of all the files. They match with what is provided on android file host.
Next, I flashed the Full firmware and booted to the stock recovery and did a wipe.
Code:
C:\adb>htc_fastboot oem rebootRUU
... OKAY
Execution time is 16(ms)
C:\adb>htc_fastboot flash zip 3.37.605.7_FULL_firmware.zip
sending 'zip'... (74990 KB) OKAY
sending time = 4.796 secs
writing 'zip'... (bootloader) HOSD CL#669662
(bootloader) GPT is up-to-dated. [17408]
(bootloader) Perform pre-update
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) [email protected]
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) [email protected]
FAIL90 hboot pre-update! please flush image again immediately
FAILED (remote: 90 hboot pre-update! please flush image again immediately )
For "hboot-preupdate" response, restart the same procedure for device HT54DSV054
60...
< waiting for device >
sending 'zip'... (74990 KB) OKAY
sending time = 4.826 secs
writing 'zip'... (bootloader) HOSD CL#669662
(bootloader) GPT is up-to-dated. [17408]
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]
(bootloader) [email protected]
(bootloader) Update zip file OK
(bootloader) [email protected]
OKAY
Flash Zip Complete
Execution time is 15(s)
C:\adb>htc_fastboot reboot-bootloader
rebooting into bootloader... OKAY
Execution time is 3(ms)
Following that, I rebooted to download mode again, and flashed the NoBoot firmware with TWRP.
Code:
C:\adb>htc_fastboot flash zip 3.37.605.7_NoBoot_TWRP3.00-1_firmware.zip
< waiting for device >
sending 'zip'... (65327 KB) OKAY
sending time = 4.306 secs
writing 'zip'... (bootloader) HOSD CL#669662
(bootloader) GPT is up-to-dated. [17408]
(bootloader) Perform pre-update
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) [email protected]
FAIL90 hboot pre-update! please flush image again immediately
FAILED (remote: 90 hboot pre-update! please flush image again immediately )
For "hboot-preupdate" response, restart the same procedure for device HT54DSV054
60...
< waiting for device >
sending 'zip'... (65327 KB) OKAY
sending time = 4.335 secs
writing 'zip'... (bootloader) HOSD CL#669662
(bootloader) GPT is up-to-dated. [17408]
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]%
(bootloader) [email protected]
(bootloader) [email protected]
(bootloader) Update zip file OK
(bootloader) [email protected]
OKAY
Flash Zip Complete
Execution time is 17(s)
C:\adb>htc_fastboot reboot-bootloader
rebooting into bootloader... OKAY
Execution time is 3(ms)
C:\adb>
I booted into Recovery and wiped my SD Card out. Then I copied up the DEODEX'ed ROM 3.37.605.7_HIMA_WL_M60_SENSE70_VZW_MR_Full_DEODEX.zip to the SD Card. The MD5 is below...
Code:
C:\adb>adb shell md5sum /external_sd/3.37.605.7_HIMA_WL_M60_SENSE70_VZW_MR_Full_
DEODEX.zip
6164c613d0fe7eb09fe111944848bc80 /external_sd/3.37.605.7_HIMA_WL_M60_SENSE70_VZ
W_MR_Full_DEODEX.zip
I then installed the zip using TWRP. I pulled the /tmp/recovery.log file before rebooting to the System. I was not asked to install SU by TWRP, and there for did not allow TWRP to install Root or SU for me.
Recovery.log file is below...
Code:
ui_print
3.37.605.7_HIMA_WL_M60_SENSE70_VZW_MR_Full.zip Successfully Installed!
script succeeded: result was [3.37.605.7_HIMA_WL_M60_SENSE70_VZW_MR_Full.zip Successfully Installed!]I:Updater process ended with RC=0
I:Legacy property environment disabled.
Updating partition details...
I:Data backup size is 388MB, free: 22144MB.
I:Unable to mount '/usb_otg'
I:Actual block device: '', current file system: 'vfat'
I:Unable to mount '/sd-ext'
I:Actual block device: '', current file system: 'ext4'
...done
I:Set page: 'flash_done'
I:TWFunc::Set_Brightness: Setting brightness control to 255
I:operation_end - status=0
There was not a lot of information in this log file when installing only the ROM.
Next I rebooted into the system, this boot process took a long time (as expected for first boots). I went through the setup of the phone and made sure NOT to RESTORE any old settings or apps. I did not want any old data coming back to haunt me. I checked in my App Drawer for SuperSU and did not see it. I installed Root Checker from the App store and it told me I did not have root.
I decided to try flashing the SuperSU 2.65 zip file manually and seeing if that would give me root. I rebooted to recovery and started the flash process.
I downloaded SuperSU from this thread http://forum.xda-developers.com/showthread.php?t=1538053 and this link https://download.chainfire.eu/921/SuperSU/UPDATE-SuperSU-v2.65-20151226141550.zip
SuperSU did not provide an md5sum, so all I can compare it to is the local to the phone ->
Code:
C:\adb>md5sum UPDATE-SuperSU-v2.65-20151226141550.zip
419d48a14d8ae9f247cd9266e14ad8cf *UPDATE-SuperSU-v2.65-20151226141550.zip
C:\adb>adb shell md5sum /external_sd/UPDATE-SuperSU-v2.65-20151226141550.zip
419d48a14d8ae9f247cd9266e14ad8cf /external_sd/UPDATE-SuperSU-v2.65-201512261415
50.zip
C:\adb>
---CONTINUING---
I then installed the SuperSU Zip and pulled the /tmp/recovery.log
--Added as attachment to this post--
I hit Reboot System button and it rebooted right to the System. It did not ask me to install Root or SU
Again I used Root Checker (https://play.google.com/store/apps/details?id=com.joeykrim.rootcheck&hl=en) and was informed I do not have Root.
This is where I sit, with Marshmallow 6.0 Stock and no root method available.
This is my folder structure after the SuperSU.zip tried to install root (Captured using adb while booted into recovery)
Root Structure
Code:
drwxr-xr-x 2 root root 0 Feb 29 04:22 boot
drwxrwx--- 5 system cache 4096 Feb 29 04:14 cache
drwxrwxrwx 2 root root 0 Feb 29 04:22 carrier
lrwxrwxrwx 1 root root 13 Jan 1 1970 charger -> /sbin/healthd
drwxrwxrwx 2 root root 0 Feb 29 04:22 cota
drwxrwx--x 37 system system 4096 Feb 29 04:15 data
-rw-r--r-- 1 root root 3013 Jan 1 1970 default.prop
drwxr-xr-x 11 root root 4340 Feb 29 04:22 dev
drwxrwxrwx 2 root root 0 Feb 29 04:22 devlog
drwxr-xr-x 2 root root 0 Feb 29 04:22 etc
drwxrwxrwx 5 root root 16384 Jan 1 1970 external_sd
-rw-r--r-- 1 root root 14727 Jan 1 1970 file_contexts
-rw-r----- 1 root root 1041 Jan 1 1970 fstab.qcom
-rwxr-x--- 1 root root 1150888 Jan 1 1970 init
-rwxr-x--- 1 root root 2844 Jan 1 1970 init.rc
-rwxr-x--- 1 root root 4061 Jan 1 1970 init.recovery.htc_hima.rc
drwxr-xr-x 3 root root 0 Jan 1 1970 license
drwxr-xr-x 2 root root 0 Jan 1 1970 oem
drwxrwxrwx 2 root root 0 Feb 29 04:22 preload
dr-xr-xr-x 323 root root 0 Jan 1 1970 proc
-rw-r--r-- 1 root root 3350 Jan 1 1970 property_contexts
drwxr-xr-x 2 root root 0 Feb 29 04:22 recovery
drwxr-xr-x 4 root root 0 Jan 1 1970 res
drwx------ 2 root root 0 Feb 16 20:51 root
drwxr-x--- 2 root root 0 Feb 29 04:22 sbin
drwxrwxrwx 2 root root 0 Feb 29 04:22 sd-ext
drwxrwx--- 15 media_rw media_rw 4096 Feb 29 04:13 sdcard
-rw-r--r-- 1 root root 703 Jan 1 1970 seapp_contexts
-rw-r--r-- 1 root root 63 Jan 1 1970 selinux_version
-rw-r--r-- 1 root root 143489 Jan 1 1970 sepolicy
-rw-r--r-- 1 root root 9769 Jan 1 1970 service_contexts
drwxr-xr-x 2 root root 0 Feb 29 04:22 sideload
drwxr-xr-x 2 root root 0 Jan 1 1970 supersu
dr-xr-xr-x 25 root root 0 Feb 29 04:22 sys
drwxr-xr-x 5 root root 0 Jan 1 1970 system
drwxrwxr-x 2 root shell 60 Feb 29 04:22 tmp
drwxr-xr-x 5 root root 0 Jan 1 1970 twres
-rw-r--r-- 1 root root 10948 Jan 1 1970 ueventd.qcom.rc
-rw-r--r-- 1 root root 4726 Jan 1 1970 ueventd.rc
drwxrwxrwx 2 root root 0 Feb 29 04:22 usb_otg
drwxr-xr-x 4 root root 0 Jan 1 1970 vendor
/system
Code:
drwxr-xr-x 102 root root 4096 Feb 29 03:33 app
drwxr-xr-x 3 root shell 12288 Feb 29 03:34 bin
-rw-r--r-- 1 root root 13791 Aug 1 2008 build.prop
drwxr-xr-x 8 root root 4096 Feb 29 03:33 customize
drwxr-xr-x 3 root root 4096 Feb 29 03:33 embms
drwxr-xr-x 21 root shell 4096 Feb 29 03:33 etc
drwxr-xr-x 2 root root 12288 Feb 29 03:34 fonts
drwxr-xr-x 3 root root 4096 Feb 29 03:33 framework
drwxr-xr-x 8 root root 20480 Feb 29 03:34 lib
drwxr-xr-x 6 root root 20480 Feb 29 03:34 lib64
drwxr-xr-x 2 root root 16384 Feb 29 03:33 lost+found
drwxr-xr-x 6 root root 4096 Feb 29 03:33 media
drwxr-xr-x 143 root root 4096 Feb 29 03:34 priv-app
drwxr-xr-x 5 root root 4096 Feb 29 03:34 rfs
drwxr-xr-x 3 root root 4096 Feb 29 03:34 tts
drwxr-xr-x 10 root root 4096 Feb 29 03:34 usr
drwxr-xr-x 10 root shell 4096 Feb 29 03:34 vendor
drwxr-xr-x 2 root shell 12288 Feb 29 03:34 xbin
/data
Code:
-rw------- 1 system system 6117378 Feb 29 04:14 SuperSU.apk
drwx------ 2 root root 4096 Feb 29 03:37 adb
drwxrwxr-x 2 system system 4096 Feb 29 03:50 anr
drwxrwx--x 13 system system 4096 Feb 29 04:12 app
drwx------ 2 root root 4096 Feb 29 03:37 app-asec
drwxrwx--x 2 system system 4096 Feb 29 03:37 app-lib
drwxrwx--x 2 system system 4096 Feb 29 03:37 app-private
drwxrwx--- 3 media audio 4096 Feb 29 03:37 audio
drwx------ 5 system system 4096 Feb 29 04:11 backup
drwxr-xr-x 2 shell shell 4096 Feb 29 03:37 bootchart
lrwxrwxrwx 1 root root 45 Feb 29 03:37 bugreports -> /data/data/com.android.shell/files/bugreports
drwxrwx--x 2 system system 4096 Feb 29 03:37 connectivity
drwxrwxrwx 2 system system 4096 Feb 29 03:37 core
drwxrwx--x 5 root root 4096 Feb 29 03:37 dalvik-cache
drwxrwx--x 257 system system 12288 Feb 29 04:11 data
drwxrwx--x 4 system system 4096 Feb 29 03:37 dpm
drwxrwx--- 4 drm drm 4096 Feb 29 03:50 drm
-rw-rw---- 1 system audio 0 Feb 29 04:18 effect_endpoint_update
drwxrwx--x 2 system system 4096 Feb 29 03:37 fota
drwxrwx--- 2 system system 4096 Feb 29 03:37 fpc
drwxrwx--- 2 system wifi 4096 Feb 29 03:37 hostapd
drwxr-x--x 3 root root 4096 Feb 29 03:37 local
drwxrwx--- 2 root root 4096 Jan 1 1970 lost+found
drwxrwx--- 4 media_rw media_rw 4096 Feb 29 03:37 media
drwxrwx--- 3 mediadrm mediadrm 4096 Feb 29 03:53 mediadrm
drwxrwx--t 33 system misc 4096 Feb 29 03:52 misc
drwxrwx--- 3 nfc nfc 4096 Feb 29 03:57 nfc
drwx------ 2 root root 4096 Feb 29 04:19 property
drwxrwx--x 2 system system 4096 Feb 29 03:37 resource-cache
drwx--x--x 2 system system 4096 Feb 29 03:37 security
drwxr-xr-x 2 system system 4096 Feb 29 03:37 shared
drwx------ 2 system system 4096 Feb 29 03:37 ss
-rw------- 1 root root 12525041 Feb 29 04:15 stock_boot_de7d99827c496cadeb26cc0fdb7c50ee7c87aeb6.img.gz
-rw-r--r-- 1 root root 33554432 Feb 29 04:15 su.img
drwxrwxr-x 19 system system 4096 Feb 29 04:19 system
drwx------ 2 system system 4096 Feb 29 03:51 time
drwxrwx--x 6 system system 4096 Feb 29 03:37 tombstones
drwx--x--x 2 system system 4096 Feb 29 03:37 user
drwx------ 2 system system 4096 Feb 29 03:43 usf
drwxrwxr-x 2 wifi wifi 4096 Feb 29 03:37 wifi_log
/data/app
Code:
drwxr-xr-x 4 system system 4096 Feb 29 03:49 air.com.goodgamestudios.empirefourkingdoms-1
drwxr-xr-x 4 system system 4096 Feb 29 04:08 air.com.sgn.cookiejam.gp-2
drwxr-xr-x 4 system system 4096 Feb 29 04:11 com.android.vending-1
drwxr-xr-x 4 system system 4096 Feb 29 04:10 com.joeykrim.rootcheck-1
drwxr-xr-x 4 system system 4096 Feb 29 04:10 com.king.farmheroessaga-2
drwxr-xr-x 4 system system 4096 Feb 29 03:50 com.machinezone.gow-1
drwxr-xr-x 4 system system 4096 Feb 29 04:05 com.moonton.magicrush-2
drwxr-xr-x 4 system system 4096 Feb 29 04:09 com.sgn.geniesandgems.gp-2
drwxr-xr-x 4 system system 4096 Feb 29 03:49 com.usablenet.mobile.walgreen-1
drwxr-xr-x 4 system system 4096 Feb 29 04:04 com.verizonmedia.go90.enterprise-2
drwxrwxr-x 3 system system 4096 Feb 29 03:37 mcRegistry
---CONTINUING---
/system/bin
Code:
-rwxr-xr-x 1 root shell 43432 Aug 1 2008 ATFWD-daemon
-rwxr-xr-x 1 root shell 14192 Aug 1 2008 MOC_ecryptfs_add_passphrase
-rwxr-xr-x 1 root shell 14192 Aug 1 2008 MOC_umount_ecryptfs
-rwxr-xr-x 1 root shell 10168 Aug 1 2008 PktRspTest
-rwxr-xr-x 1 root shell 38576 Aug 1 2008 StoreKeybox
lrwxrwxrwx 1 root root 6 Feb 29 03:34 acpi -> toybox
-rwxr-xr-x 1 root shell 10192 Aug 1 2008 adsprpcd
-rwxr-xr-x 1 root shell 210 Aug 1 2008 am
lrwxrwxrwx 1 root root 13 Feb 29 03:34 app_process -> app_process64
-rwxr-xr-x 1 root shell 22108 Aug 1 2008 app_process32
-rwxr-xr-x 1 root shell 22456 Aug 1 2008 app_process64
-rwxr-xr-x 1 root shell 70608 Aug 1 2008 applypatch
-rwxr-xr-x 1 root shell 213 Aug 1 2008 appops
-rwxr-xr-x 1 root shell 215 Aug 1 2008 appwidget
-rwxr-xr-x 1 root shell 30840 Aug 1 2008 atrace
-rwxr-xr-x 1 root shell 26552 Aug 1 2008 audiod
-rwxr-xr-x 1 root shell 38492 Aug 1 2008 awb_camera
lrwxrwxrwx 1 root root 6 Feb 29 03:34 basename -> toybox
-rwxr-xr-x 1 root shell 51152 Aug 1 2008 bcc
-rwxr-xr-x 1 root shell 14224 Aug 1 2008 blkid
lrwxrwxrwx 1 root root 6 Feb 29 03:34 blockdev -> toybox
-rwxr-x--- 1 root system 26480 Aug 1 2008 bma150_usr
-rwxr-xr-x 1 root shell 199 Aug 1 2008 bmgr
-rwxr-xr-x 1 root shell 59328 Aug 1 2008 bootanimation
-rwxr-xr-x 1 root shell 34752 Aug 1 2008 brctl
-rwxr-xr-x 1 root shell 14192 Aug 1 2008 btfmtest
-rwxr-xr-x 1 root shell 156 Aug 1 2008 bu
-rwxr-xr-x 1 root shell 10096 Aug 1 2008 bugreport
lrwxrwxrwx 1 root root 6 Feb 29 03:34 bzcat -> toybox
lrwxrwxrwx 1 root root 6 Feb 29 03:34 cal -> toybox
-rwxr-xr-x 1 root shell 39224 Aug 1 2008 cand
lrwxrwxrwx 1 root root 6 Feb 29 03:34 cat -> toybox
lrwxrwxrwx 1 root root 6 Feb 29 03:34 chcon -> toybox
lrwxrwxrwx 1 root root 6 Feb 29 03:34 chgrp -> toybox
lrwxrwxrwx 1 root root 6 Feb 29 03:34 chmod -> toybox
lrwxrwxrwx 1 root root 6 Feb 29 03:34 chown -> toybox
lrwxrwxrwx 1 root root 6 Feb 29 03:34 chroot -> toybox
-rwxr-xr-x 1 root shell 47160 Aug 1 2008 cir_fw_update
lrwxrwxrwx 1 root root 6 Feb 29 03:34 cksum -> toybox
-rwxr-xr-x 1 root shell 59584 Aug 1 2008 clatd
lrwxrwxrwx 1 root root 6 Feb 29 03:34 clear -> toybox
-rwxr-xr-x 1 root shell 145168 Aug 1 2008 climax_hostSW
-rwxr-xr-x 1 root shell 120792 Aug 1 2008 clockd
-rwxr-xr-x 1 root shell 5928 Aug 1 2008 closediag
-rwxr-xr-x 1 root shell 5928 Aug 1 2008 closemodem
lrwxrwxrwx 1 root root 6 Feb 29 03:34 cmp -> toybox
-rwxr-xr-x 1 root shell 22552 Aug 1 2008 cnd
lrwxrwxrwx 1 root root 6 Feb 29 03:34 comm -> toybox
-rwxr-xr-x 1 root shell 207 Aug 1 2008 content
lrwxrwxrwx 1 root root 6 Feb 29 03:34 cp -> toybox
lrwxrwxrwx 1 root root 6 Feb 29 03:34 cpio -> toybox
-rwxr-xr-x 1 root shell 14192 Aug 1 2008 cplay
-rwxr-xr-x 1 root shell 464984 Aug 1 2008 curl
lrwxrwxrwx 1 root root 6 Feb 29 03:34 cut -> toybox
lrwxrwxrwx 1 root root 10 Feb 29 03:34 dalvikvm -> dalvikvm64
-rwxr-xr-x 1 root shell 17912 Aug 1 2008 dalvikvm32
-rwxr-xr-x 1 root shell 14192 Aug 1 2008 dalvikvm64
lrwxrwxrwx 1 root root 6 Feb 29 03:34 date -> toybox
-rwxr-xr-x 1 root shell 4572 Aug 1 2008 dbg_corefile.sh
lrwxrwxrwx 1 root root 7 Feb 29 03:34 dd -> toolbox
-rwxr-xr-x 1 root shell 42540 Aug 1 2008 debuggerd
-rwxr-xr-x 1 root shell 47056 Aug 1 2008 debuggerd64
-rwxr-xr-x 1 root shell 112172 Aug 1 2008 dex2oat
lrwxrwxrwx 1 root root 7 Feb 29 03:34 df -> toolbox
-rwxr-xr-x 1 root shell 112736 Aug 1 2008 dhcpcd
-rwxr-xr-x 1 root shell 14192 Aug 1 2008 diag_callback_client
-rwxr-xr-x 1 root shell 22456 Aug 1 2008 diag_dci_sample
-rwxr-xr-x 1 root shell 10168 Aug 1 2008 diag_klog
-rwxr-xr-x 1 root shell 23352 Aug 1 2008 diag_mdlog
-rwxr-xr-x 1 root shell 18480 Aug 1 2008 diag_qshrink4_daemon
-rwxr-xr-x 1 root shell 26896 Aug 1 2008 diag_socket_log
-rwxr-xr-x 1 root shell 14600 Aug 1 2008 diag_uart_log
lrwxrwxrwx 1 root root 6 Feb 29 03:34 dirname -> toybox
-rwxr-xr-x 1 root shell 170280 Aug 1 2008 dmagent
lrwxrwxrwx 1 root root 6 Feb 29 03:34 dmesg -> toybox
-rwxr-xr-x 1 root shell 169040 Aug 1 2008 dnsmasq
lrwxrwxrwx 1 root root 6 Feb 29 03:34 dos2unix -> toybox
-rwxr-xr-x 1 root shell 133240 Aug 1 2008 downloadcs
-rwxr-xr-x 1 root shell 137280 Aug 1 2008 downloadsensorhub
-rwxr-xr-x 1 root shell 133240 Aug 1 2008 downloadtp
-rwxr-xr-x 1 root shell 156 Aug 1 2008 dpm
-rwxr-xr-x 1 root shell 22472 Aug 1 2008 dpmd
-rwxr-xr-x 1 root shell 63096 Aug 1 2008 drmserver
lrwxrwxrwx 1 root root 7 Feb 29 03:34 du -> toolbox
-rwxr-xr-x 1 root shell 54888 Aug 1 2008 dual_camera
-rwxr-xr-x 1 root shell 34352 Aug 1 2008 dualcal_camera
-rwxr-xr-x 1 root shell 67544 Aug 1 2008 dumpstate
-rwxr-xr-x 1 root shell 14264 Aug 1 2008 dumpsys
-rwxr-xr-x 1 root shell 212912 Aug 1 2008 e2fsck
-rwxr-xr-x 1 root shell 6000 Aug 1 2008 ebtables
lrwxrwxrwx 1 root root 6 Feb 29 03:34 echo -> toybox
lrwxrwxrwx 1 root root 4 Feb 29 03:34 egrep -> grep
-rwxr-xr-x 1 root shell 19000 Aug 1 2008 energy-awareness
lrwxrwxrwx 1 root root 6 Feb 29 03:34 env -> toybox
-rwxr-xr-x 1 root shell 333416 Aug 1 2008 exfatck
-rwxr-xr-x 1 root shell 263784 Aug 1 2008 exfatdebug
-rwxr-xr-x 1 root shell 276072 Aug 1 2008 exfatinfo
-rwxr-xr-x 1 root shell 251496 Aug 1 2008 exfatlabel
lrwxrwxrwx 1 root root 6 Feb 29 03:34 expand -> toybox
lrwxrwxrwx 1 root root 6 Feb 29 03:34 expr -> toybox
lrwxrwxrwx 1 root root 6 Feb 29 03:34 fallocate -> toybox
lrwxrwxrwx 1 root root 6 Feb 29 03:34 false -> toybox
lrwxrwxrwx 1 root root 4 Feb 29 03:34 fgrep -> grep
lrwxrwxrwx 1 root root 6 Feb 29 03:34 find -> toybox
-rwxr-xr-x 1 root shell 38840 Aug 1 2008 fingerprintd
-rwxr-xr-x 1 root shell 71272 Aug 1 2008 flash_camera
-rwxr-xr-x 1 root shell 35504 Aug 1 2008 fm_qsoc_patches
-rwxr-xr-x 1 root shell 18368 Aug 1 2008 fmconfig
-rwxr-xr-x 1 root shell 10096 Aug 1 2008 fmfactorytest
-rwxr-xr-x 1 root shell 26480 Aug 1 2008 fmfactorytestserver
lrwxrwxrwx 1 root root 6 Feb 29 03:34 free -> toybox
-rwxr-xr-x 1 root shell 67512 Aug 1 2008 fsck.f2fs
-rwxr-xr-x 1 root shell 34672 Aug 1 2008 fsck_msdos
-rwxr-xr-x 1 root shell 5928 Aug 1 2008 ftm_powertest
-rwxr-xr-x 1 root shell 55248 Aug 1 2008 gatekeeperd
-rwxr-xr-x 1 root shell 397672 Aug 1 2008 gdbserver
lrwxrwxrwx 1 root root 6 Feb 29 03:34 getenforce -> toybox
lrwxrwxrwx 1 root root 7 Feb 29 03:34 getevent -> toolbox
lrwxrwxrwx 1 root root 6 Feb 29 03:34 getprop -> toybox
-rwxr-xr-x 1 root shell 36288 Aug 1 2008 grep
lrwxrwxrwx 1 root root 6 Feb 29 03:34 groups -> toybox
-rwxr-xr-x 1 root shell 10096 Aug 1 2008 gzip
-rwxr-xr-x 1 root shell 17960 Aug 1 2008 hcheck-v2
lrwxrwxrwx 1 root root 6 Feb 29 03:34 head -> toybox
-rwxr-xr-x 1 root shell 213 Aug 1 2008 hid
-rwxr-xr-x 1 root shell 252120 Aug 1 2008 hld
-rwxr-xr-x 1 root shell 593288 Aug 1 2008 hostapd
-rwxr-xr-x 1 root shell 47056 Aug 1 2008 hostapd_cli
lrwxrwxrwx 1 root root 6 Feb 29 03:34 hostname -> toybox
-rwxr-xr-x 1 root shell 260776 Aug 1 2008 htc_ebdlogd
lrwxrwxrwx 1 root root 6 Feb 29 03:34 hwclock -> toybox
lrwxrwxrwx 1 root root 6 Feb 29 03:34 id -> toybox
-rwxr-xr-x 1 root shell 34752 Aug 1 2008 idmap
lrwxrwxrwx 1 root root 6 Feb 29 03:34 ifconfig -> toybox
lrwxrwxrwx 1 root root 7 Feb 29 03:34 iftop -> toolbox
-rwxr-xr-x 1 root shell 194 Aug 1 2008 ime
-rwxr-xr-x 1 root shell 67616 Aug 1 2008 ims_rtp_daemon
-rwxr-xr-x 1 root shell 6096 Aug 1 2008 imscmservice
-rwxr-xr-x 1 root shell 165936 Aug 1 2008 imsdatadaemon
-rwxr-xr-x 1 root shell 120784 Aug 1 2008 imsqmidaemon
lrwxrwxrwx 1 root root 6 Feb 29 03:34 inotifyd -> toybox
-rwxr-xr-x 1 root shell 203 Aug 1 2008 input
lrwxrwxrwx 1 root root 6 Feb 29 03:34 insmod -> toybox
-rwxr-xr-x 1 root shell 96752 Aug 1 2008 installd
lrwxrwxrwx 1 root root 7 Feb 29 03:34 ioctl -> toolbox
lrwxrwxrwx 1 root root 7 Feb 29 03:34 ionice -> toolbox
-rwxr-xr-x 1 root shell 223552 Aug 1 2008 ip
-rwxr-xr-x 1 root shell 398520 Aug 1 2008 ip6tables
-rwxr-xr-x 1 root shell 485344 Aug 1 2008 ipacm
-rwxr-xr-x 1 root shell 10168 Aug 1 2008 ipacm-diag
-rwxr-x--- 1 root system 390016 Aug 1 2008 iptables
-rwxr-xr-x 1 root shell 10096 Aug 1 2008 irsc_util
-rwxr-xr-x 1 root shell 14192 Aug 1 2008 keypress
-rwxr-xr-x 1 root shell 133296 Aug 1 2008 keystore
lrwxrwxrwx 1 root root 6 Feb 29 03:34 kill -> toybox
-rwxr-xr-x 1 root shell 866768 Aug 1 2008 ld.mc
-rwxr-xr-x 1 root shell 177612 Aug 1 2008 linker
-rwxr-xr-x 1 root shell 270144 Aug 1 2008 linker64
-rwxr-xr-x 1 root shell 18296 Aug 1 2008 lmkd
lrwxrwxrwx 1 root root 6 Feb 29 03:34 ln -> toybox
lrwxrwxrwx 1 root root 6 Feb 29 03:34 load_policy -> toybox
lrwxrwxrwx 1 root root 7 Feb 29 03:34 log -> toolbox
-rwxr-xr-x 1 root shell 26488 Aug 1 2008 logcat
-rwxr-xr-x 1 root shell 79808 Aug 1 2008 logd
lrwxrwxrwx 1 root root 6 Feb 29 03:34 logname -> toybox
-rwxr-xr-x 1 root shell 18320 Aug 1 2008 logwrapper
lrwxrwxrwx 1 root root 6 Feb 29 03:34 losetup -> toybox
lrwxrwxrwx 1 root root 7 Feb 29 03:34 ls -> toolbox
-rwxr-xr-x 1 root shell 148320 Aug 1 2008 lsc_camera
lrwxrwxrwx 1 root root 6 Feb 29 03:34 lsmod -> toybox
lrwxrwxrwx 1 root root 7 Feb 29 03:34 lsof -> toolbox
lrwxrwxrwx 1 root root 6 Feb 29 03:34 lsusb -> toybox
-rwxr-xr-x 1 root shell 14192 Aug 1 2008 make_ext4fs
-rwxr-xr-x 1 root shell 26712 Aug 1 2008 make_f2fs
-rwxr-xr-x 1 root shell 145336 Aug 1 2008 mcDriverDaemon
-rwxr-xr-x 1 root shell 6088 Aug 1 2008 mcStarter
lrwxrwxrwx 1 root root 6 Feb 29 03:34 md5sum -> toybox
-rwxr-xr-x 1 root shell 653648 Aug 1 2008 mdnsd
-rwxr-xr-x 1 root shell 210 Aug 1 2008 media
-rwxr-xr-x 1 root shell 26204 Aug 1 2008 mediaserver
-rwxr-xr-x 1 root shell 120944 Aug 1 2008 memlock
lrwxrwxrwx 1 root root 6 Feb 29 03:34 mkdir -> toybox
-rwxr-xr-x 1 root shell 284264 Aug 1 2008 mkexfat
lrwxrwxrwx 1 root root 6 Feb 29 03:34 mknod -> toybox
lrwxrwxrwx 1 root root 6 Feb 29 03:34 mkswap -> toybox
lrwxrwxrwx 1 root root 6 Feb 29 03:34 mktemp -> toybox
-rwxr-xr-x 1 root shell 87732 Aug 1 2008 mm-qcamera-app
-rwxr-xr-x 1 root shell 22108 Aug 1 2008 mm-qcamera-daemon
-rwxr-xr-x 1 root shell 26152 Aug 1 2008 mm-qjpeg-dec-test
-rwxr-xr-x 1 root shell 26152 Aug 1 2008 mm-qjpeg-enc-test
-rwxr-xr-x 1 root shell 34344 Aug 1 2008 mm-qomx-idec-test
-rwxr-xr-x 1 root shell 38440 Aug 1 2008 mm-qomx-ienc-test
-rwxr-xr-x 1 root shell 445352 Aug 1 2008 mm-vidc-omx-test
-rwxr-xr-x 1 root shell 419 Aug 1 2008 mobicore-startup.sh
lrwxrwxrwx 1 root root 6 Feb 29 03:34 modinfo -> toybox
-rwxr-xr-x 1 root shell 217 Aug 1 2008 monkey
lrwxrwxrwx 1 root root 6 Feb 29 03:34 more -> toybox
lrwxrwxrwx 1 root root 7 Feb 29 03:34 mount -> toolbox
lrwxrwxrwx 1 root root 6 Feb 29 03:34 mountpoint -> toybox
-rwxr-xr-x 1 root shell 75432 Aug 1 2008 msm-vidc-test
-rwxr-xr-x 1 root shell 30584 Aug 1 2008 msm_irqbalance
-rwxr-xr-x 1 root shell 26672 Aug 1 2008 mtpd
lrwxrwxrwx 1 root root 6 Feb 29 03:34 mv -> toybox
lrwxrwxrwx 1 root root 7 Feb 29 03:34 nandread -> toolbox
-rwxr-xr-x 1 root shell 10112 Aug 1 2008 ndc
-rwxr-xr-x 1 root shell 236128 Aug 1 2008 netd
-rwxr-xr-x 1 root shell 439080 Aug 1 2008 netmgrd
-rwxr-xr-x 1 root shell 42960 Aug 1 2008 netsharing
lrwxrwxrwx 1 root root 6 Feb 29 03:34 netstat -> toybox
lrwxrwxrwx 1 root root 7 Feb 29 03:34 newfs_msdos -> toolbox
lrwxrwxrwx 1 root root 6 Feb 29 03:34 nice -> toybox
lrwxrwxrwx 1 root root 6 Feb 29 03:34 nl -> toybox
-rwxr-xr-x 1 root shell 6000 Aug 1 2008 nl_listener
lrwxrwxrwx 1 root root 6 Feb 29 03:34 nohup -> toybox
-rwxr-xr-x 1 root shell 215040 Aug 1 2008 oatdump
lrwxrwxrwx 1 root root 6 Feb 29 03:34 od -> toybox
-rwxr-xr-x 1 root shell 34424 Aug 1 2008 oemwvtest
-rwxr-xr-x 1 root shell 5928 Aug 1 2008 opendiag
-rwxr-xr-x 1 root shell 5928 Aug 1 2008 openmodem
lrwxrwxrwx 1 root root 6 Feb 29 03:34 paste -> toybox
lrwxrwxrwx 1 root root 6 Feb 29 03:34 patch -> toybox
-rwxr-xr-x 1 root shell 67064 Aug 1 2008 patchoat
lrwxrwxrwx 1 root root 6 Feb 29 03:34 pgrep -> toybox
lrwxrwxrwx 1 root root 6 Feb 29 03:34 pidof -> toybox
-rwxr-xr-x 1 root root 47240 Aug 1 2008 ping
-rwxr-xr-x 1 root shell 47656 Aug 1 2008 ping6
lrwxrwxrwx 1 root root 6 Feb 29 03:34 pkill -> toybox
-rwxr-xr-x 1 root shell 191 Aug 1 2008 pm
-rwxr-xr-x 1 root shell 10184 Aug 1 2008 pm-proxy
-rwxr-xr-x 1 root shell 43512 Aug 1 2008 pm-service
lrwxrwxrwx 1 root root 6 Feb 29 03:34 pmap -> toybox
-rwxr-xr-x 1 root shell 51328 Aug 1 2008 pnpmgr
-rwxr-xr-x 1 root shell 14216 Aug 1 2008 port-bridge
-rwxr-xr-x 1 root shell 279888 Aug 1 2008 pppd
lrwxrwxrwx 1 root root 6 Feb 29 03:34 printenv -> toybox
lrwxrwxrwx 1 root root 6 Feb 29 03:34 printf -> toybox
lrwxrwxrwx 1 root root 7 Feb 29 03:34 prlimit -> toolbox
lrwxrwxrwx 1 root root 7 Feb 29 03:34 ps -> toolbox
lrwxrwxrwx 1 root root 6 Feb 29 03:34 pwd -> toybox
-rwxr-xr-x 1 root shell 26672 Aug 1 2008 qcom-system-daemon
-rwxr-xr-x 1 root shell 10096 Aug 1 2008 qemu-props
-rwxr-xr-x 1 root shell 18288 Aug 1 2008 qemud
-rwxr-xr-x 1 root shell 5928 Aug 1 2008 qfipsverify
-rwxr-xr-x 1 root shell 22056 Aug 1 2008 qjpeg-dma-test
drwxr-xr-x 2 root shell 4096 Feb 29 03:33 qmi-framework-tests
-rwxr-xr-x 1 root shell 156824 Aug 1 2008 qmuxd
-rwxr-xr-x 1 root shell 10112 Aug 1 2008 qrngtest
-rwxr-xr-x 1 root shell 30872 Aug 1 2008 qseecom_sample_client
-rwxr-xr-x 1 root shell 22064 Aug 1 2008 qseecom_security_test
-rwxr-xr-x 1 root shell 14592 Aug 1 2008 qseecomd
-rwxr-xr-x 1 root shell 283280 Aug 1 2008 racoon
-rwxr-xr-x 1 root shell 63480 Aug 1 2008 radish
lrwxrwxrwx 1 root root 6 Feb 29 03:34 readlink -> toybox
lrwxrwxrwx 1 root root 6 Feb 29 03:34 realpath -> toybox
-rwxr-xr-x 1 root shell 6000 Aug 1 2008 reboot
-rwxr-xr-x 1 root shell 10680 Aug 1 2008 regdbdump
lrwxrwxrwx 1 root root 7 Feb 29 03:34 renice -> toolbox
-rwxr-xr-x 1 root shell 188 Aug 1 2008 requestsync
-rwxr-xr-x 1 root shell 42864 Aug 1 2008 resize2fs
lrwxrwxrwx 1 root root 6 Feb 29 03:34 restorecon -> toybox
-rwxr-xr-x 1 root shell 37256 Aug 1 2008 rfs_access
-rwxr-xr-x 1 root shell 18312 Aug 1 2008 rild
lrwxrwxrwx 1 root root 6 Feb 29 03:34 rm -> toybox
lrwxrwxrwx 1 root root 6 Feb 29 03:34 rmdir -> toybox
lrwxrwxrwx 1 root root 6 Feb 29 03:34 rmmod -> toybox
-rwxr-xr-x 1 root shell 21112 Aug 1 2008 rmnetcli
-rwxr-xr-x 1 root shell 39944 Aug 1 2008 rmt_storage
lrwxrwxrwx 1 root root 6 Feb 29 03:34 route -> toybox
-rwxr-x--- 1 root shell 14192 Aug 1 2008 run-as
lrwxrwxrwx 1 root root 6 Feb 29 03:34 runcon -> toybox
-rwxr-xr-x 1 root shell 6000 Aug 1 2008 schedtest
-rwxr-xr-x 1 root shell 14264 Aug 1 2008 screencap
-rwxr-xr-x 1 root shell 116752 Aug 1 2008 screenrecord
-rwxr-xr-x 1 root shell 30576 Aug 1 2008 sdcard
-rwxr-xr-x 1 root shell 26552 Aug 1 2008 secure_camera_sample_client
lrwxrwxrwx 1 root root 6 Feb 29 03:34 sed -> toybox
lrwxrwxrwx 1 root root 7 Feb 29 03:34 sendevent -> toolbox
-rwxr-xr-x 1 root shell 10096 Aug 1 2008 sensorservice
lrwxrwxrwx 1 root root 6 Feb 29 03:34 seq -> toybox
-rwxr-xr-x 1 root shell 18360 Aug 1 2008 service
-rwxr-xr-x 1 root shell 18360 Aug 1 2008 servicemanager
lrwxrwxrwx 1 root root 6 Feb 29 03:34 setenforce -> toybox
lrwxrwxrwx 1 root root 6 Feb 29 03:34 setprop -> toybox
lrwxrwxrwx 1 root root 6 Feb 29 03:34 setsid -> toybox
-rwxr-xr-x 1 root shell 178 Aug 1 2008 settings
-rwxr-xr-x 1 root shell 10104 Aug 1 2008 setup_fs
-rwxr-xr-x 1 root shell 161736 Aug 1 2008 sgdisk
-rwxr-xr-x 1 root shell 289432 Aug 1 2008 sh
lrwxrwxrwx 1 root root 6 Feb 29 03:34 sha1sum -> toybox
-rwxr-xr-x 1 root shell 194752 Aug 1 2008 shub_dbg
lrwxrwxrwx 1 root root 6 Feb 29 03:34 sleep -> toybox
-rwxr-xr-x 1 root shell 190 Aug 1 2008 sm
lrwxrwxrwx 1 root root 6 Feb 29 03:34 sort -> toybox
lrwxrwxrwx 1 root root 6 Feb 29 03:34 split -> toybox
-rwxr-xr-x 1 root shell 14264 Aug 1 2008 ssr_diag
-rwxr-xr-x 1 root shell 14192 Aug 1 2008 ssr_setup
lrwxrwxrwx 1 root root 7 Feb 29 03:34 start -> toolbox
lrwxrwxrwx 1 root root 6 Feb 29 03:34 stat -> toybox
lrwxrwxrwx 1 root root 7 Feb 29 03:34 stop -> toolbox
lrwxrwxrwx 1 root root 6 Feb 29 03:34 strings -> toybox
-rwxr-xr-x 1 root shell 30632 Aug 1 2008 subsystem_ramdump
-rwxr-xr-x 1 root shell 14208 Aug 1 2008 surfaceflinger
-rwxr-xr-x 1 root shell 192 Aug 1 2008 svc
lrwxrwxrwx 1 root root 6 Feb 29 03:34 swapoff -> toybox
lrwxrwxrwx 1 root root 6 Feb 29 03:34 swapon -> toybox
lrwxrwxrwx 1 root root 6 Feb 29 03:34 sync -> toybox
lrwxrwxrwx 1 root root 6 Feb 29 03:34 sysctl -> toybox
lrwxrwxrwx 1 root root 6 Feb 29 03:34 tac -> toybox
lrwxrwxrwx 1 root root 6 Feb 29 03:34 tail -> toybox
lrwxrwxrwx 1 root root 6 Feb 29 03:34 tar -> toybox
lrwxrwxrwx 1 root root 6 Feb 29 03:34 taskset -> toybox
-rwxr-x--- 1 root system 96880 Aug 1 2008 tc
lrwxrwxrwx 1 root root 6 Feb 29 03:34 tee -> toybox
-rwxr-xr-x 1 root shell 172 Aug 1 2008 telecom
-rwxr-xr-x 1 root shell 14264 Aug 1 2008 test_diag
-rwxr-xr-x 1 root shell 26152 Aug 1 2008 test_module_pproc
-rwxr-xr-x 1 root shell 84232 Aug 1 2008 tftp_server
-rwxr-xr-x 1 root shell 18360 Aug 1 2008 thermal-monitor
lrwxrwxrwx 1 root root 6 Feb 29 03:34 time -> toybox
-rwxr-xr-x 1 root shell 34768 Aug 1 2008 time_daemon
lrwxrwxrwx 1 root root 6 Feb 29 03:34 timeout -> toybox
-rwxr-xr-x 1 root shell 10096 Aug 1 2008 tinycap
-rwxr-xr-x 1 root shell 10096 Aug 1 2008 tinymix
-rwxr-xr-x 1 root shell 10168 Aug 1 2008 tinypcminfo
-rwxr-xr-x 1 root shell 10096 Aug 1 2008 tinyplay
-rwxr-xr-x 1 root shell 148184 Aug 1 2008 toolbox
lrwxrwxrwx 1 root root 7 Feb 29 03:34 top -> toolbox
lrwxrwxrwx 1 root root 6 Feb 29 03:34 touch -> toybox
-rwxr-xr-x 1 root shell 310800 Aug 1 2008 toybox
-rwxr-xr-x 1 root shell 170224 Aug 1 2008 tpd_daemon
lrwxrwxrwx 1 root root 6 Feb 29 03:34 tr -> toybox
lrwxrwxrwx 1 root root 6 Feb 29 03:34 true -> toybox
lrwxrwxrwx 1 root root 6 Feb 29 03:34 truncate -> toybox
-rwxr-xr-x 1 root shell 18288 Aug 1 2008 tzdatacheck
-rwxr-xr-x 1 root shell 3814 Aug 1 2008 uiautomator
lrwxrwxrwx 1 root root 6 Feb 29 03:34 umount -> toybox
lrwxrwxrwx 1 root root 6 Feb 29 03:34 uname -> toybox
-rwxr-x--- 1 root root 39344 Aug 1 2008 uncrypt
lrwxrwxrwx 1 root root 6 Feb 29 03:34 uniq -> toybox
lrwxrwxrwx 1 root root 6 Feb 29 03:34 unix2dos -> toybox
lrwxrwxrwx 1 root root 7 Feb 29 03:34 uptime -> toolbox
lrwxrwxrwx 1 root root 6 Feb 29 03:34 usleep -> toybox
-rwxr-xr-x 1 root shell 10112 Aug 1 2008 vdc
lrwxrwxrwx 1 root root 6 Feb 29 03:34 vmstat -> toybox
-rwxr-xr-x 1 root shell 514712 Aug 1 2008 vold
lrwxrwxrwx 1 root root 7 Feb 29 03:34 watchprops -> toolbox
lrwxrwxrwx 1 root root 6 Feb 29 03:34 wc -> toybox
lrwxrwxrwx 1 root root 6 Feb 29 03:34 which -> toybox
lrwxrwxrwx 1 root root 6 Feb 29 03:34 whoami -> toybox
-rwxr-xr-x 1 root shell 18064 Aug 1 2008 wifi_otp_programming
-rwxr-xr-x 1 root shell 68344 Aug 1 2008 wifitest
-rwxr-xr-x 1 root shell 190 Aug 1 2008 wm
-rwxr-xr-x 1 root shell 118512 Aug 1 2008 wpa_cli
-rwxr-xr-x 1 root shell 1805728 Aug 1 2008 wpa_supplicant
lrwxrwxrwx 1 root root 6 Feb 29 03:34 xargs -> toybox
lrwxrwxrwx 1 root root 6 Feb 29 03:34 yes -> toybox
I can provide any other data upon request...
Thank you for your time.
Why is your bootloader locked?
Is it really or is that my faux hboot?
Sent from my HTC6535LVW using Tapatalk
santod040 said:
Why is your bootloader locked?
Is it really or is that my faux hoot?
Sent from my HTC6535LVW using Tapatalk
Click to expand...
Click to collapse
I'm guessing its really locked? ....I'll shoot myself in the foot if this is the entire issue. When I used the XTC2 Clip I enabled S-OFF and everything was unlocked to my knowledge.
MrTrip said:
I'm guessing its really locked? ....I'll shoot myself in the foot if this is the entire issue. When I used the XTC2 Clip I enabled S-OFF and everything was unlocked to my knowledge.
Click to expand...
Click to collapse
Pretty sure that's your problem...it's still locked, although s-off.
Sent from my HTC6535LVW using Tapatalk
santod040 said:
Pretty sure that's your problem...it's still locked, although s-off.
Sent from my HTC6535LVW using Tapatalk
Click to expand...
Click to collapse
I'm making a flying trip across town to grab my Clip, I will report back ASAP. I will absolutely be floored if this was the issue...
MrTrip said:
I'm making a flying trip across town to grab my Clip, I will report back ASAP. I will absolutely be floored if this was the issue...
Click to expand...
Click to collapse
Hopefully this fixes it.
This is a thread to unlock BL using terminal.
But if already on your way and prefer using the clip I'd go that method.
http://forum.xda-developers.com/one-m9/general/how-to-lock-unlock-bootloader-htcdevs-t3092036
Actually, you need SU for that to work, my bad.
Glad you have a clip.
santod040 said:
Pretty sure that's your problem...it's still locked, although s-off.
Sent from my HTC6535LVW using Tapatalk
Click to expand...
Click to collapse
andybones said:
Hopefully this fixes it.
This is a thread to unlock BL using terminal.
But if already on your way and prefer using the clip I'd go that method.
http://forum.xda-developers.com/one-m9/general/how-to-lock-unlock-bootloader-htcdevs-t3092036
Actually, you need SU for that to work, my bad.
Glad you have a clip.
Click to expand...
Click to collapse
This fixed it. Holy crud. Did I miss somewhere in the thread that S-OFF and ALSO Bootloader Unlocked?!
I thought Locked meant I was SIM locked, not BOOTLOADER locked...Oh...my...god I'm retarded...It is official :silly::silly::good::silly::silly::good::good:
4 days of total hell because of a locked bootloader, even though S-OFF let me do everything else... :silly::silly::silly:
Thank you guys SO MUCH, I'm sorry I've been a pill. I never needed Bootloader unlocked for Root before because it was system-mode not system-less...
CRUDDDD
Edit: I executed those commands in the Recovery, as I had root in Recovery and was able to set Bootloader to unlocked.
How were you using TWRP ?
I knew there were (2) steps involved in rooting the M9, one was getting S-OFF and the other was unlocking the bootloader. Since you were using TWRP, I thought that meant your bootloader must be unlocked. Or, I'm confusing what's needed...
hallstevenson said:
How were you using TWRP ?
I knew there were (2) steps involved in rooting the M9, one was getting S-OFF and the other was unlocking the bootloader. Since you were using TWRP, I thought that meant your bootloader must be unlocked. Or, I'm confusing what's needed...
Click to expand...
Click to collapse
Once S-OFF you can flash whatever you want, minus modifying bootloader. When I became S-OFF on Android 5 I flashed Recovery, installed Root, and went on my day. The bootloader was never unlocked, and I was unaware of this because I had root and everything seemed to function normally. Come to find out I missed out on a lot having a locked bootloader still, even though I had root.
Once 6.0 came along, root went system-less and required patching boot, but I couldn't do this because the bootloader was locked, hence no root. :good:
It should be noted, because I know I followed a guide somewhere, that 6.0+ REQUIRES unlocked bootloader to achieve Root.
hallstevenson said:
How were you using TWRP ?
I knew there were (2) steps involved in rooting the M9, one was getting S-OFF and the other was unlocking the bootloader. Since you were using TWRP, I thought that meant your bootloader must be unlocked. Or, I'm confusing what's needed...
Click to expand...
Click to collapse
Even on the m8 you could flash twrp while locked but s-off. Number one reason I kept ruu mode flashable twrp zips posted. M9 simply came not caring while in download mode.
Fwiw, this was my number one concern with the mass influx of clip holders working on other members phones. The troubleshooting experience is not there to support the operations taking place. This statement is not meant to chide the op...just food for thought.
Motorola
Envoyé de mon XT1563 en utilisant Tapatalk
Having the same bit of trouble as MrTrip did, I'm very confused, before I made the attempt to go to Marshmellow from Lollipop I has SU and everything was fine and dandy. Can't remember if I had my Booloader unlocked before, but now it certinaly shows up as locked now which is confusing. Regardless, maybe someone knows here, since I am S-OFF I should be able to go the HTCDev route and unlock the bootloader correct?
**Edit** Crap, forgot the whole Verizon is garbage and locks their phones from HTCDev. Still confusing, because I did have it unlocked at one point with a Java Card...
wingman1487 said:
Having the same bit of trouble as MrTrip did, I'm very confused, before I made the attempt to go to Marshmellow from Lollipop I has SU and everything was fine and dandy. Can't remember if I had my Booloader unlocked before, but now it certinaly shows up as locked now which is confusing. Regardless, maybe someone knows here, since I am S-OFF I should be able to go the HTCDev route and unlock the bootloader correct?
**Edit** Crap, forgot the whole Verizon is garbage and locks their phones from HTCDev. Still confusing, because I did have it unlocked at one point with a Java Card...
Click to expand...
Click to collapse
You only need to run a single adb command to unlock that boot loader as long as you are s-off.
Sent from my HTC6545LVW using Tapatalk
dottat said:
You only need to run a single adb command to unlock that boot loader as long as you are s-off.
Sent from my HTC6545LVW using Tapatalk
Click to expand...
Click to collapse
But don't you have to be Rooted to run that?
http://forum.xda-developers.com/verizon-one-m9/help/m9-s-0ff-unlock-t3385095
wingman1487 said:
But don't you have to be Rooted to run that?
http://forum.xda-developers.com/verizon-one-m9/help/m9-s-0ff-unlock-t3385095
Click to expand...
Click to collapse
Easiest way is to boot to twrp and do it. You need an ruu mode version of twrp to flash?
Flash this like you would an ruu or firmware zip. Then boot to recovery and run your adb command. Note you won't need to su as you already have root privs in twrp.
https://www.androidfilehost.com/?fid=24457741883933189
Sent from my HTC6545LVW using Tapatalk
dottat said:
Easiest way is to boot to twrp and do it. You need an ruu mode version of twrp to flash?
Flash this like you would an ruu or firmware zip. Then boot to recovery and run your adb command. Note you won't need to su as you already have root privs in twrp.
https://www.androidfilehost.com/?fid=24457741883933189
Sent from my HTC6545LVW using Tapatalk
Click to expand...
Click to collapse
Humm, think I'm missing something.
Code:
c:\ADB>fastboot flash zip RUUmodeTWRP3_0_0_1.zip
target reported max download size of 800000000 bytes
sending 'zip' (12898 KB)...
OKAY [ 1.671s]
writing 'zip'...
(bootloader) HOSD CL#669662
(bootloader) ERR Model ID not matched
(bootloader) ERR [SD_UPDATE_ERR] MODEL ID NOT ALLOWED
(bootloader) ERR [SD_UPDATE_ERR] sddownload failed: 10
(bootloader) ERR Update zip file failed.
(bootloader) Update zip file OK
(bootloader) ERR ZIP ERROR CODE, 10
(bootloader) [email protected]
FAILED (remote: 10 RU_MODELID_FAIL modelid in android-info mismatched )
finished. total time: 2.767s
Try this zip instead
https://www.androidfilehost.com/?fid=24438995911973227
Same result

Yet another just-out-of-warranty brick...

Problem: My beloved 32GB Pixel XL froze while I was typing the other night and I hard reset it. It froze during the boot animation, then rebooted, and then froze during the boot animation again. Done this ~30 times with no joy. It's just over a year old so no warranty.
Background: Bootloader unlocked. Stock rom v 7.1 (build NPF26J). Rooted.
What I've tried:
Clearing Dalvik/cache in TWRP
Factory reset through recovery (both TWRP and stock)
Begging it to work
Flashing factory images for 7.1 and 8.1
locking and unlocking the bootloader multiple times before flashing above factory images
Formatting Data and doing an Advanced Wipe in TWRP to recreate partitions then flashing both of the above factory stock images
At this point, it won't even go to the boot animation. It just goes to black after the white screen that says, "Google" then reboots. If it's rebooting for the first time after a factory image flash, it reboots into stock recovery.
Tried running e2fsck -cfv on userdata and system. This is the output:
userdata:
Code:
e2fsck 1.43.3 (04-Sep-2016)
sh: badblocks: not found
userdata: Updating bad block inode.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
userdata: ***** FILE SYSTEM WAS MODIFIED *****
172 inodes used (0.01%, out of 1630208)
2 non-contiguous files (1.2%)
0 non-contiguous directories (0.0%)
# of inodes with ind/dind/tind blocks: 0/0/0
Extent depth histogram: 165
146606 blocks used (2.25%, out of 6509568)
0 bad blocks
1 large file
21 regular files
141 directories
0 character device files
0 block device files
0 fifos
0 links
1 symbolic link (1 fast symbolic link)
0 sockets
------------
163 files
system:
Code:
/dev/block/platform/soc/624000.ufshc/by-name # e2fsck -cfv system
e2fsck 1.43.3 (04-Sep-2016)
sh: badblocks: not found
/: Updating bad block inode.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 3A: Optimizing directories
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/: ***** FILE SYSTEM WAS MODIFIED *****
2517 inodes used (1.95%, out of 129024)
13 non-contiguous files (0.5%)
4 non-contiguous directories (0.2%)
# of inodes with ind/dind/tind blocks: 0/0/0
Extent depth histogram: 2310/7
472130 blocks used (91.48%, out of 516099)
0 bad blocks
1 large file
2043 regular files
273 directories
0 character device files
0 block device files
0 fifos
0 links
192 symbolic links (192 fast symbolic links)
0 sockets
------------
2508 files
Noticed something very odd about the partition table--there's no /cache! Gonna try to create it somehow.
Code:
/dev/block/platform/soc/624000.ufshc/by-name # [6nls -al
total 0
drwxr-xr-x 2 root root 1340 1970-01-01 02:09 .
drwxr-xr-x 4 root root 1440 1970-01-01 02:09 ..
lrwxrwxrwx 1 root root 16 1970-01-01 02:09 aboot_a -> /dev/block/sda17
lrwxrwxrwx 1 root root 16 1970-01-01 02:09 aboot_b -> /dev/block/sda18
lrwxrwxrwx 1 root root 16 1970-01-01 02:09 apdp_a -> /dev/block/sda29
lrwxrwxrwx 1 root root 16 1970-01-01 02:09 apdp_b -> /dev/block/sda30
lrwxrwxrwx 1 root root 15 1970-01-01 02:09 board_info -> /dev/block/sdf1
lrwxrwxrwx 1 root root 36 1970-01-01 02:09 boot -> /dev/block/bootdevice/by-name/boot_b
lrwxrwxrwx 1 root root 16 1970-01-01 02:09 boot_a -> /dev/block/sda19
lrwxrwxrwx 1 root root 16 1970-01-01 02:09 boot_b -> /dev/block/sda20
lrwxrwxrwx 1 root root 15 1970-01-01 02:09 bootlocker_a -> /dev/block/sda1
lrwxrwxrwx 1 root root 15 1970-01-01 02:09 bootlocker_b -> /dev/block/sda2
lrwxrwxrwx 1 root root 16 1970-01-01 02:09 cdt -> /dev/block/sdd12
lrwxrwxrwx 1 root root 16 1970-01-01 02:09 cmnlib32_a -> /dev/block/sda13
lrwxrwxrwx 1 root root 16 1970-01-01 02:09 cmnlib32_b -> /dev/block/sda14
lrwxrwxrwx 1 root root 16 1970-01-01 02:09 cmnlib64_a -> /dev/block/sda15
lrwxrwxrwx 1 root root 16 1970-01-01 02:09 cmnlib64_b -> /dev/block/sda16
lrwxrwxrwx 1 root root 16 1970-01-01 02:09 ddr -> /dev/block/sdd11
lrwxrwxrwx 1 root root 16 1970-01-01 02:09 devcfg_a -> /dev/block/sda23
lrwxrwxrwx 1 root root 16 1970-01-01 02:09 devcfg_b -> /dev/block/sda24
lrwxrwxrwx 1 root root 15 1970-01-01 02:09 devinfo -> /dev/block/sdf4
lrwxrwxrwx 1 root root 15 1970-01-01 02:09 devinfobak -> /dev/block/sdd5
lrwxrwxrwx 1 root root 15 1970-01-01 02:09 dip -> /dev/block/sdd7
lrwxrwxrwx 1 root root 15 1970-01-01 02:09 dpo -> /dev/block/sdd6
lrwxrwxrwx 1 root root 15 1970-01-01 02:09 frp -> /dev/block/sde1
lrwxrwxrwx 1 root root 15 1970-01-01 02:09 fsc -> /dev/block/sdd8
lrwxrwxrwx 1 root root 15 1970-01-01 02:09 fsg -> /dev/block/sdf3
lrwxrwxrwx 1 root root 16 1970-01-01 02:09 hosd_a -> /dev/block/sda21
lrwxrwxrwx 1 root root 16 1970-01-01 02:09 hosd_b -> /dev/block/sda22
lrwxrwxrwx 1 root root 16 1970-01-01 02:09 hyp_a -> /dev/block/sda11
lrwxrwxrwx 1 root root 16 1970-01-01 02:09 hyp_b -> /dev/block/sda12
lrwxrwxrwx 1 root root 15 1970-01-01 02:09 keymaster_a -> /dev/block/sda3
lrwxrwxrwx 1 root root 15 1970-01-01 02:09 keymaster_b -> /dev/block/sda4
lrwxrwxrwx 1 root root 15 1970-01-01 02:09 metadata -> /dev/block/sde5
lrwxrwxrwx 1 root root 15 1970-01-01 02:09 mfg -> /dev/block/sdf2
lrwxrwxrwx 1 root root 15 1970-01-01 02:09 misc -> /dev/block/sdd1
lrwxrwxrwx 1 root root 16 1970-01-01 02:09 modem_a -> /dev/block/sda25
lrwxrwxrwx 1 root root 16 1970-01-01 02:09 modem_b -> /dev/block/sda26
lrwxrwxrwx 1 root root 15 1970-01-01 02:09 modemst1 -> /dev/block/sdd9
lrwxrwxrwx 1 root root 16 1970-01-01 02:09 modemst2 -> /dev/block/sdd10
lrwxrwxrwx 1 root root 16 1970-01-01 02:09 msadp_a -> /dev/block/sda27
lrwxrwxrwx 1 root root 16 1970-01-01 02:09 msadp_b -> /dev/block/sda28
lrwxrwxrwx 1 root root 15 1970-01-01 02:09 persist -> /dev/block/sdd3
lrwxrwxrwx 1 root root 15 1970-01-01 02:09 pg1fs -> /dev/block/sde3
lrwxrwxrwx 1 root root 15 1970-01-01 02:09 pg2fs -> /dev/block/sde4
lrwxrwxrwx 1 root root 15 1970-01-01 02:09 pmic_a -> /dev/block/sda9
lrwxrwxrwx 1 root root 16 1970-01-01 02:09 pmic_b -> /dev/block/sda10
lrwxrwxrwx 1 root root 15 1970-01-01 02:09 ramdump -> /dev/block/sde2
lrwxrwxrwx 1 root root 16 1970-01-01 02:09 reserve0 -> /dev/block/sda36
lrwxrwxrwx 1 root root 16 1970-01-01 02:09 reserve3 -> /dev/block/sdd13
lrwxrwxrwx 1 root root 15 1970-01-01 02:09 reserve4 -> /dev/block/sde6
lrwxrwxrwx 1 root root 15 1970-01-01 02:09 reserve5 -> /dev/block/sdf5
lrwxrwxrwx 1 root root 15 1970-01-01 02:09 rpm_a -> /dev/block/sda7
lrwxrwxrwx 1 root root 15 1970-01-01 02:09 rpm_b -> /dev/block/sda8
lrwxrwxrwx 1 root root 15 1970-01-01 02:09 sec -> /dev/block/sdd4
lrwxrwxrwx 1 root root 15 1970-01-01 02:09 ssd -> /dev/block/sdd2
lrwxrwxrwx 1 root root 38 1970-01-01 02:09 system -> /dev/block/bootdevice/by-name/system_b
lrwxrwxrwx 1 root root 16 1970-01-01 02:09 system_a -> /dev/block/sda33
lrwxrwxrwx 1 root root 16 1970-01-01 02:09 system_b -> /dev/block/sda34
lrwxrwxrwx 1 root root 15 1970-01-01 02:09 tz_a -> /dev/block/sda5
lrwxrwxrwx 1 root root 15 1970-01-01 02:09 tz_b -> /dev/block/sda6
lrwxrwxrwx 1 root root 16 1970-01-01 02:09 userdata -> /dev/block/sda35
lrwxrwxrwx 1 root root 38 1970-01-01 02:09 vendor -> /dev/block/bootdevice/by-name/vendor_b
lrwxrwxrwx 1 root root 16 1970-01-01 02:09 vendor_a -> /dev/block/sda31
lrwxrwxrwx 1 root root 16 1970-01-01 02:09 vendor_b -> /dev/block/sda32
lrwxrwxrwx 1 root root 15 1970-01-01 02:09 xbl_a -> /dev/block/sdb1
lrwxrwxrwx 1 root root 15 1970-01-01 02:09 xbl_b -> /dev/block/sdc1
Edit: NVM. Looks like the /cache partition is gone for the Pixel XL.
Do you work for the FBI?
I should also mention that I haven't been able to flash TWRP permenantly, either. I can get it to boot temporarily through fastboot but when flashing the zip in TWRP, it hangs and reboots at "Running boot image patcher on slot A". Not sure if that's because I haven't been able to get into Android and set a pin, though.
nabbed said:
Do you work for the FBI?
Click to expand...
Click to collapse
lol wut
Have you tried the Skipsoft Unified Android Toolkit? I have no association with the dev whatsoever, but I purchased the pro version, or whatever you call it, and it works flawlessly to update, install, backup, flash, etc. my Pixel.
https://skipsoft.net/skipsoft-unified-android-toolkit/
Sent from my SM-G955U using Tapatalk
Edit: double-post.
I tried that out earlier today. Tried out flashing just the recovery and a 8.0 stock ROM. No joy. Doesn't even get to boot animation. Is there a particular option I should try in the pro version?
RT Wolf said:
I tried that out earlier today. Tried out flashing just the recovery and a 8.0 stock ROM. No joy. Doesn't even get to boot animation. Is there a particular option I should try in the pro version?
Click to expand...
Click to collapse
Have you tried to install factory update, using flash-all and edit flash-all by removing the -w
Make sure you open cmd and type fastboot reboot bootloader. Then just double click flash-all, a new cmd will open and just let it run, it will stop for a few minutes, let it sit, it will start again.
I know this is pretty old but im curious as to if anyone has had this problem and fixed it. Believe it or not Ive had this exact problem for a week now. This may seem like a joke when i say this but i actually fixed this by banging the phone against my knee out of frustration. I tried everything...diff boot slots, every factory image from 7 to 10, flash anything and everything in TWRP. TWRP would freeze anytime a ROM was flashed almost immediately. Factory images would never get passed the white screen with the single "G" on the sreen. Then one time i tapped the screen and the phone booted further. So i banged it against my knee and finshed the setup and made it to stock 8.1 with the bootloader locked *shrugs*
This kind of behavior looks like UFS failure. It's mostly caused by either condensation, liquid damage, or moisture. It can be none of these, and naturally happen with just time. The least you could try is putting it to a heat gun where the UFS chip is. If you live in US you can take it to a uBreakiFix center to repair, they know how to do chipset repair. If you dont, try to take a look around for shop, ask them if they know how to do chip repair.

Categories

Resources