I've gotten the error message "Unfortunately, System UI has stopped" twice now. The first time, I got around it by re-installing my ROM (something I'd rather not try again, because of how many contacts and data I keep on my phone and how long restoring everything takes). The second time, opening a specific app (Gallery in my case) stopped the errors. I have an SGH-T989 running TWRP 2.6.3.0 and BlackLiquid 2.9.2.
I've found people suggest all of the following as potential fixes:
Force closing specific apps (one that came up frequently was "FaceLock").
Wiping the system UI cache.
Fixing permissions with CWM.
And to add my own personal experience (as mentioned above):
Opening a specific app.
When I encountered the following, I also attempted the following, all of which failed:
Wiping the phone cache in TWRP 2.6.3.0.
Wiping the dalvik-cache in TWRP 2.6.3.0.
Backing up the internal SD, wiping it, restoring the ROM sans cache.
Fixing permissions using TWRP 2.6.3.0.
So, tl;dr - What, if any, consistent, generic reason is there for system UI to crash? (i.e. consistently throw the error message "Unfortunately, System UI has stopped.")
Original post 2013/10/09 08:43PM
Hi, I've been persistently getting the error message "Unfortunately, System UI has stopped" whenever my phone is on. I got annoyed enough with it that I just wiped my phone and re-installed the ROM I had, but that was a rather tedious process that I'd rather not run through again if I encountered it.
I have a Samsung Galaxy S2 T-Mobile (model SGH-T989) with TWRP 2.6.3.0 and BlackLiquid 2.9.2.
I first started having problems with my phone (not the System UI problem) earlier in the day when trying to enter data in fields using Google Chrome - the keyboard would not appear when I selected a text field. In an attempt to fix this, I installed Google Keyboard, which led to no success. From that point on, features would occasionally crash, until at some point later on in the day, as a result of no particular incident that I can recall, I started receiving this error message ("Unfortunately, System UI has stopped"). The notification reappeared within seconds of closing it, and whenever I rebooted my phone, the delay between notifications only increased slightly, and after a minute or so, the notification would refresh almost instantly.
Uninstalling Google Keyboard did not help. I could not clear the System UI cache. Rebooting did nothing except, as mentioned, temporarily increase the time between notification. After dropping my phone once though (not intentionally) and rebooting, it was fine for a few seconds, but then crashed (in all other instances it crashed on startup) - this lasted maybe two reboots.
I ultimately elected to use TWRP to backup my files, perform a system wipe, and then reinstall BlackLiquid. This seems to have fixed my issues, but I'd like to have an idea of any fixes that people are aware of.
Google and searching xda and similar forums told me that:
This error is not isolated to BlackLiquid/LiquidSmooth, but prevalent across all ROMs, including stock ROMs.
Certain apps, e.g. "Face Lock" have a tendency to cause this issue; force closing them will work.
Wiping the System UI cache may work.
Does anyone have any other fixes or reasons this happens? Or possibly for future reference, a set of diagnostics I could run? (I'm new to Android development - I just rooted my phone this past weekend.)
Original follow-up post 2013/10/22 11:43PM
When I first made this thread, I had just reflashed my phone and installed a new ROM to get around the issue as a quick and dirty fix.
Unfortunately, the problem has resurfaced, and in this instance, no app was updated or changed to cause this issue - it just happened spontaneously happened again.
I still have TWRP 2.6.3.0 installed, and none of the following have worked:
- Wiping the cache.
- Wiping the dalvik-cache.
- Fixing permissions.
Research tells me that the "Fix Permissions" option has been since removed from CWM as it is now obsolete.
I would like to note that when I reboot my phone, I will get the "Unfortunately..." error message at the lock screen (the system UI will appear in the background and then crash), but when I use the power/lock button to lock my phone/turn off the screen and turn the screen back on (turning the screen back on can take 5-10s), it does stop the message from occurring at the lock screen (i.e. until I can enter my PIN).
Does anyone have any other solutions?
Mostly wrong permissions fix permissions n wipe cache via Clock Work Mod
Sent from my Xperia Live with Walkman using xda app-developers app
Recurring Problem
When I first made this thread, I had just reflashed my phone and installed a new ROM to get around the issue as a quick and dirty fix.
Unfortunately, the problem has resurfaced, and in this instance, no app was updated or changed to cause this issue - it just happened spontaneously happened again.
I still have TWRP 2.6.3.0 installed, and none of the following have worked:
- Wiping the cache.
- Wiping the dalvik-cache.
- Fixing permissions.
Research tells me that the "Fix Permissions" option has been since removed from CWM as it is now obsolete.
I would like to note that when I reboot my phone, I will get the "Unfortunately..." error message at the lock screen (the system UI will appear in the background and then crash), but when I use the power/lock button to lock my phone/turn off the screen and turn the screen back on (turning the screen back on can take 5-10s), it does stop the message from occurring at the lock screen (i.e. until I can enter my PIN).
Does anyone have any other solutions?
Thnx
Brainjitzu
Before installing the rom again also try formating system in mount option in recovery hopefully your problem will be resolved .
Sent from my X10S using xda app-developers app
After opening Gallery (the stock app), the problem seems to have gone away - I haven't had the problem for about 18h now.
Does anyone have any idea why this is the case?
Accidental duplicate post, sorry.
Notifications has stopped
me too .
anybody solved ??
I'm bumping this thread because it's an annoying problem. I have a Lenovo P780 and tried different roms, but still I always get this error after some time. I discovered something weird. When I connect my phone to my PC via usb, the error disappears and everything, even the taskbar thing on the top. When I disconnect it, sadly the error returns.
A possible solution.
I have this issue too, but in my case the issue was caused by a wrong formatted card:
I created by mistake a logical partition, instead primary partition on my card.
Is important also to check in this case your SD card, try to power off, remove it the SD card from the device (phone/table) and power on the device without the SD card.
If that is fixe it, then that is the cause in your case too.
In my case is about an Sony Xperia V (LT25i) and below is a a piece of my log cat:
Code:
05-21 18:25:13.552: W/MountService(829): getVolumeState(/storage/sdcard1): Unknown volume
05-21 18:25:13.552: E/AndroidRuntime(1393): FATAL EXCEPTION: main
05-21 18:25:13.552: E/AndroidRuntime(1393): java.lang.RuntimeException: Unable to create service com.sonyericsson.usbux.service.UsbService: java.lang.IllegalArgumentException
05-21 18:25:13.552: E/AndroidRuntime(1393): at android.app.ActivityThread.handleCreateService(ActivityThread.java:2651)
05-21 18:25:13.552: E/AndroidRuntime(1393): at android.app.ActivityThread.access$1600(ActivityThread.java:150)
05-21 18:25:13.552: E/AndroidRuntime(1393): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1380)
05-21 18:25:13.552: E/AndroidRuntime(1393): at android.os.Handler.dispatchMessage(Handler.java:99)
05-21 18:25:13.552: E/AndroidRuntime(1393): at android.os.Looper.loop(Looper.java:213)
05-21 18:25:13.552: E/AndroidRuntime(1393): at android.app.ActivityThread.main(ActivityThread.java:5225)
05-21 18:25:13.552: E/AndroidRuntime(1393): at java.lang.reflect.Method.invokeNative(Native Method)
05-21 18:25:13.552: E/AndroidRuntime(1393): at java.lang.reflect.Method.invoke(Method.java:525)
05-21 18:25:13.552: E/AndroidRuntime(1393): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:741)
05-21 18:25:13.552: E/AndroidRuntime(1393): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:557)
05-21 18:25:13.552: E/AndroidRuntime(1393): at dalvik.system.NativeStart.main(Native Method)
05-21 18:25:13.552: E/AndroidRuntime(1393): Caused by: java.lang.IllegalArgumentException
05-21 18:25:13.552: E/AndroidRuntime(1393): at android.os.Parcel.readException(Parcel.java:1448)
05-21 18:25:13.552: E/AndroidRuntime(1393): at android.os.Parcel.readException(Parcel.java:1395)
05-21 18:25:13.552: E/AndroidRuntime(1393): at android.os.storage.IMountService$Stub$Proxy.getVolumeState(IMountService.java:241)
05-21 18:25:13.552: E/AndroidRuntime(1393): at android.os.storage.StorageManager.getVolumeState(StorageManager.java:564)
05-21 18:25:13.552: E/AndroidRuntime(1393): at com.sonyericsson.usbux.service.SdCard.getState(SdCard.java:94)
05-21 18:25:13.552: E/AndroidRuntime(1393): at com.sonyericsson.usbux.service.UsbNotifications.<init>(UsbNotifications.java:60)
05-21 18:25:13.552: E/AndroidRuntime(1393): at com.sonyericsson.usbux.service.UsbService.onCreate(UsbService.java:214)
05-21 18:25:13.552: E/AndroidRuntime(1393): at android.app.ActivityThread.handleCreateService(ActivityThread.java:2641)
05-21 18:25:13.552: E/AndroidRuntime(1393): ... 10 more
05-21 18:25:13.582: I/ActivityManager(829): Start proc com.sonymobile.gpssatellitesnotification for broadcast com.sonymobile.gpssatellitesnotification/.GpsSatellitesListener: pid=1523 uid=10058 gids={50058, 1028}
05-21 18:25:13.612: I/ActivityManager(829): START u0 {act=android.intent.action.MAIN cat=[android.intent.category.HOME] flg=0x10000000 cmp=com.sonyericsson.initialbootsetup/.HomeActivity} from pid 0
05-21 18:25:13.622: W/ContextImpl(829): Calling a method in the system process without a qualified user: android.app.ContextImpl.bindService:1481 android.bluetooth.BluetoothA2dp.<init>:164 android.bluetooth.BluetoothAdapter.getProfileProxy:1169 android.media.AudioService$AudioServiceBroadcastReceiver.onReceive:4280 android.app.LoadedApk$ReceiverDispatcher$Args.run:770
05-21 18:25:13.622: V/WiredAccessoryManager(829): init()
05-21 18:25:13.812: I/ActivityManager(829): Start proc com.sonyericsson.android.bootinfo:remote for service com.sonyericsson.android.bootinfo/.MiscTaService: pid=1553 uid=1000 gids={41000, 1015, 1028, 3002, 3001, 3003, 3007, 1021, 3004, 3005, 1000, 3009, 1023}
05-21 18:25:13.812: I/ActivityManager(829): START u0 {act=android.intent.action.MAIN cat=[android.intent.category.HOME] flg=0x10008000 cmp=com.sonyericsson.setupwizard/.SetupWizardEntry (has extras)} from pid 1365
05-21 18:25:13.853: I/ActivityManager(829): Start proc android.process.acore for content provider com.android.providers.contacts/.SemcCallLogProvider: pid=1563 uid=10010 gids={50010, 1028}
05-21 18:25:13.863: I/ActivityManager(829): Start proc com.google.android.gms for broadcast com.google.android.gms/com.google.android.location.internal.NlpNetworkProviderSettingsUpdateReceiver: pid=1569 uid=10050 gids={50050, 3003, 2001, 1007, 3006, 1028, 1015, 3002, 3001}
05-21 18:25:13.913: I/ActivityManager(829): START u0 {cmp=com.sonyericsson.setupwizard/.screens.ImportantInformationScreen} from pid 1286
05-21 18:25:13.943: E/ActivityThread(1208): Failed to find provider info for com.sonymobile.settings.illumination
05-21 18:25:13.973: E/ActivityThread(1208): Failed to find provider info for com.sonymobile.settings.illumination
05-21 18:25:13.973: E/ActivityThread(1208): Failed to find provider info for com.sonymobile.settings.illumination
05-21 18:25:14.263: W/MountService(829): getVolumeState(/storage/usbdisk): Unknown volume
05-21 18:25:14.263: E/AndroidRuntime(1117): FATAL EXCEPTION: main
05-21 18:25:14.263: E/AndroidRuntime(1117): java.lang.RuntimeException: Unable to create service com.android.systemui.SystemUIService: java.lang.IllegalArgumentException
05-21 18:25:14.263: E/AndroidRuntime(1117): at android.app.ActivityThread.handleCreateService(ActivityThread.java:2651)
05-21 18:25:14.263: E/AndroidRuntime(1117): at android.app.ActivityThread.access$1600(ActivityThread.java:150)
05-21 18:25:14.263: E/AndroidRuntime(1117): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1380)
05-21 18:25:14.263: E/AndroidRuntime(1117): at android.os.Handler.dispatchMessage(Handler.java:99)
05-21 18:25:14.263: E/AndroidRuntime(1117): at android.os.Looper.loop(Looper.java:213)
05-21 18:25:14.263: E/AndroidRuntime(1117): at android.app.ActivityThread.main(ActivityThread.java:5225)
05-21 18:25:14.263: E/AndroidRuntime(1117): at java.lang.reflect.Method.invokeNative(Native Method)
05-21 18:25:14.263: E/AndroidRuntime(1117): at java.lang.reflect.Method.invoke(Method.java:525)
05-21 18:25:14.263: E/AndroidRuntime(1117): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:741)
05-21 18:25:14.263: E/AndroidRuntime(1117): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:557)
05-21 18:25:14.263: E/AndroidRuntime(1117): at dalvik.system.NativeStart.main(Native Method)
05-21 18:25:14.263: E/AndroidRuntime(1117): Caused by: java.lang.IllegalArgumentException
05-21 18:25:14.263: E/AndroidRuntime(1117): at android.os.Parcel.readException(Parcel.java:1448)
05-21 18:25:14.263: E/AndroidRuntime(1117): at android.os.Parcel.readException(Parcel.java:1395)
05-21 18:25:14.263: E/AndroidRuntime(1117): at android.os.storage.IMountService$Stub$Proxy.getVolumeState(IMountService.java:241)
05-21 18:25:14.263: E/AndroidRuntime(1117): at android.os.storage.StorageManager.getVolumeState(StorageManager.java:564)
05-21 18:25:14.263: E/AndroidRuntime(1117): at com.android.systemui.usb.StorageNotification.checkUsbStorageState(StorageNotification.java:107)
05-21 18:25:14.263: E/AndroidRuntime(1117): at com.android.systemui.usb.StorageNotification.<init>(StorageNotification.java:96)
05-21 18:25:14.263: E/AndroidRuntime(1117): at com.android.systemui.statusbar.phone.PhoneStatusBarPolicy.<init>(PhoneStatusBarPolicy.java:182)
05-21 18:25:14.263: E/AndroidRuntime(1117): at com.android.systemui.statusbar.phone.PhoneStatusBar.start(PhoneStatusBar.java:497)
05-21 18:25:14.263: E/AndroidRuntime(1117): at com.android.systemui.SystemUIService.onCreate(SystemUIService.java:100)
05-21 18:25:14.263: E/AndroidRuntime(1117): at android.app.ActivityThread.handleCreateService(ActivityThread.java:2641)
05-21 18:25:14.263: E/AndroidRuntime(1117): ... 10 more
@nandude I suspect the SD card in your case too, because when you connect the phone to PC normally the SD card is mounted on the PC and is not scanned by the phone, but once you disconnect your phone from PC the SD card is scanned again. Try to change how is attached the SD card to PC (MTP or MSC).
Try my workaround. http://forum.xda-developers.com/showthread.php?t=2759479
Never underestimate a kid whose poor in cash but rich in time.
Actually I found out what caused me this error. When the battery drains lower than 20%, the battery icon or the numbers should change color or something. Well, in my case there was some problem with it, so it just gave the System UI error. That was why when I plugged it in, the error disappeared. At least now I know when will that error show up.
nandude said:
Actually I found out what caused me this error. When the battery drains lower than 20%, the battery icon or the numbers should change color or something. Well, in my case there was some problem with it, so it just gave the System UI error. That was why when I plugged it in, the error disappeared. At least now I know when will that error show up.
Click to expand...
Click to collapse
Thanks for this information. I've been searching for hints regarding this issue that causes System UI has stopped. I will observe this in my custom ROM.
nandude said:
Actually I found out what caused me this error. When the battery drains lower than 20%, the battery icon or the numbers should change color or something. Well, in my case there was some problem with it, so it just gave the System UI error. That was why when I plugged it in, the error disappeared. At least now I know when will that error show up.
Click to expand...
Click to collapse
Definitely not my issue then lol. Ahhh can't get rid of this damm systemui pop up error.
nandude said:
Actually I found out what caused me this error. When the battery drains lower than 20%, the battery icon or the numbers should change color or something. Well, in my case there was some problem with it, so it just gave the System UI error. That was why when I plugged it in, the error disappeared. At least now I know when will that error show up.
Click to expand...
Click to collapse
The same case with my lenovo a3000. The message pop up when it reaches 15% of battery. That happened when i installed rooted apps but i cant figure out what is that app that cause my device in failure. The last option i got is to reflash the rom. :crying:
Ragkhuza said:
Try my workaround. http://forum.xda-developers.com/showthread.php?t=2759479
Never underestimate a kid whose poor in cash but rich in time.
Click to expand...
Click to collapse
I had this issue too and tried wiping the cache and the Dalvik cache but no joy. The only thing that resolved it was reflash with the stock rom that was already running on my Galaxy Note 4 SM-M910F
mine N9005 running omega rom (4.4.2) - not sure what caused it - i installed few apps, connect with gear, etc etc then got this issue., only when i long press the two soft buttons! (ie to get recent apps)
i tried every methods from google to fix: None works. cant believe it is so easy to mess with android...
can i just dirty flash the same rom? lazy to do clean install
tones160 said:
Definitely not my issue then lol. Ahhh can't get rid of this damm systemui pop up error.
Click to expand...
Click to collapse
I had this issue after i rooted my note 2 and installed DN4, it came with some stock third party apps that were integrated into the system as it was a custom rom. I think the app that i got rid off that caused the system ui pop up making it impossible to use the phone. It was some custom battery app which would have an icon displayed instead of the regular samsung battery. I tried the cache wipe, davlik nothing worked kept getting the error on boot up. Finally i just factory re-set, re-flashed DN4 and everything works fine now. I would assume the error is due to deleting a certain app that's integrated into the os.
look for a stable build which will compatible to your device
Dear Sir,
i ported ios 8 (mt6582) & install it in karbonn Titanium S4 Plus(mt6582) via twrp that is also a ported twrp by me , & file flash successfully but when it power on it there are many massages shown again & again that "unfortunately process com.android.systemui has stopped." & it pop up again & again so plz tell me how i can fix this reply fast plzz. my email for contact : [email protected]
And another problem when i off screen by power button then it never wakes up by again taping power button then i have to restart it . plz help,,,, i port this rom very difficultly plzz help me.
Hi,
I want to install Cyanogenmod on my Nexus S. To do this my bootloader needs to be unlocked which wipes the phone. Before I do that, I want to make a backup. For some apps I need root to do a proper backup and there's my problem. I followed half a dozen guides, but they either A) wipe the phone or B) somehow don't work for me. So now I hope you can help me.
My Phone: Nexus S (crespo, I9023XXKI1) with stock Android (4.1.2), no root (obviously)
What I've tried so far:
- Downloaded android-sdk (platform tools and usb drivers)
- Installed USB drivers
- "adb backup -f ... -apk ..." works fine for some apps, but for others the backup is incomplete
- "fastboot devices" works and lists my device
- "fastboot flash recovery ..." doesn't work (says it needs an unlocked bootloader)
- "fastboot oem unlock" will wipe the phone
What can I do to get root and make a proper backup before wiping my phone?
Heres a log of my last try:
Code:
Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. Alle Rechte vorbehalten.
c:\Users\Sebastian\AppData\Local\Android\android-sdk\platform-tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
373......0EC device
c:\Users\Sebastian\AppData\Local\Android\android-sdk\platform-tools>adb reboot bootloader
c:\Users\Sebastian\AppData\Local\Android\android-sdk\platform-tools>fastboot devices
373......0EC fastboot
c:\Users\Sebastian\AppData\Local\Android\android-sdk\platform-tools>fastboot flash recovery recovery-clockwork-6.0.4.3-crespo.img
sending 'recovery' (5388 KB)...
OKAY [ 0.687s]
writing 'recovery'...
FAILED (remote: Bootloader Locked - Use "fastboot oem unlock" to Unlock)
finished. total time: 0.716s
c:\Users\Sebastian\AppData\Local\Android\android-sdk\platform-tools>fastboot oem unlock
... // Here I said "no" on the phone
OKAY [ 20.560s]
finished. total time: 20.564s
c:\Users\Sebastian\AppData\Local\Android\android-sdk\platform-tools>
Hyperbo said:
Hi,
I want to install Cyanogenmod on my Nexus S. To do this my bootloader needs to be unlocked which wipes the phone. Before I do that, I want to make a backup. For some apps I need root to do a proper backup and there's my problem. I followed half a dozen guides, but they either A) wipe the phone or B) somehow don't work for me. So now I hope you can help me.
My Phone: Nexus S (crespo, I9023XXKI1) with stock Android (4.1.2), no root (obviously)
What I've tried so far:
- Downloaded android-sdk (platform tools and usb drivers)
- Installed USB drivers
- "adb backup -f ... -apk ..." works fine for some apps, but for others the backup is incomplete
- "fastboot devices" works and lists my device
- "fastboot flash recovery ..." doesn't work (says it needs an unlocked bootloader)
- "fastboot oem unlock" will wipe the phone
What can I do to get root and make a proper backup before wiping my phone?
Heres a log of my last try:
Code:
Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. Alle Rechte vorbehalten.
c:\Users\Sebastian\AppData\Local\Android\android-sdk\platform-tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
373......0EC device
c:\Users\Sebastian\AppData\Local\Android\android-sdk\platform-tools>adb reboot bootloader
c:\Users\Sebastian\AppData\Local\Android\android-sdk\platform-tools>fastboot devices
373......0EC fastboot
c:\Users\Sebastian\AppData\Local\Android\android-sdk\platform-tools>fastboot flash recovery recovery-clockwork-6.0.4.3-crespo.img
sending 'recovery' (5388 KB)...
OKAY [ 0.687s]
writing 'recovery'...
FAILED (remote: Bootloader Locked - Use "fastboot oem unlock" to Unlock)
finished. total time: 0.716s
c:\Users\Sebastian\AppData\Local\Android\android-sdk\platform-tools>fastboot oem unlock
... // Here I said "no" on the phone
OKAY [ 20.560s]
finished. total time: 20.564s
c:\Users\Sebastian\AppData\Local\Android\android-sdk\platform-tools>
Click to expand...
Click to collapse
Backing up contacts, pictures and other personal data can be done without root using just a simple file manager or mounting your device to your computer, but app data is another story, you are 99% guaranteed to lose it, minus apps like launchers that will make a backup file on the SD card.. I have searched myself for a good resolution, but there hasn't been one yet..
That's what I feared. Even Helium (formerly Carbon) from the ClockworkMod Team doesn't work. When I try to backup any apps it just says: "An error occured while perfoming your app backup. A log of the error has been sent to ClockworkMod. Click Backup to attempt to backup the remaining apps." However, the backup of (only) SMS works fine with Helium.
Is there anything else I could try?
Hyperbo said:
That's what I feared. Even Helium (formerly Carbon) from the ClockworkMod Team doesn't work. When I try to backup any apps it just says: "An error occured while perfoming your app backup. A log of the error has been sent to ClockworkMod. Click Backup to attempt to backup the remaining apps." However, the backup of (only) SMS works fine with Helium.
Is there anything else I could try?
Click to expand...
Click to collapse
As far as I know, Helium can backup app data without root. I wonder why it doesn't work. Can you share the log file if you have?
I was on a business trip and could try it just today. I didn't find a helium log file, so I looked at the link in your signature. I used the adb logcat variant. Here are my results:
Helium Version: 1.1.2.1 (not premium)
After starting the adb log on the console I backuped the SMS and it worked as expected. Then I tried an app for which the backup failed in the past (gnucash), but strangely it went through. I tried it again and it failed. I tried other apps, but couldn't reproduce the success. I chose the gnucash app because with the normal "adb backup -f ..." call it works just fine, so helium shouldn't have any problems.
Here is the log of one of the tries. First the successful SMS backup then the failed gnucash backup:
Code:
I/Carbon (14917): startBackup invoked: file
I/Carbon (14917): com.android.providers.telephony
D/PhoneStatusBar( 354): addNotification score=0
I/Carbon (14917): Releasing locks.
I/Carbon (14917): Acquiring full lock.
I/CarbonNonce(14917): Nonce: 9352e3b8-6553-4b27-a014-96283d88a017
I/Carbon (14917): bu 1 backup
D/SizeAdaptiveLayout( 354): [email protected] view [email protected] measured out of bounds at 95px clamped to 96px
D/dalvikvm(14917): GC_FOR_ALLOC freed 963K, 13% free 13649K/15559K, paused 157ms, total 161ms
I/Carbon (14917): Demux atomic: false
D/dalvikvm(14917): GC_FOR_ALLOC freed 806K, 15% free 13363K/15559K, paused 68ms, total 69ms
I/Carbon (14917): Writing package: com.android.providers.telephony
I/CarbonBackup(14917): Package: com.android.providers.telephony
D/SizeAdaptiveLayout( 354): [email protected] view [email protected] measured out of bounds at 95px clamped to 96px
D/dalvikvm(14917): GC_CONCURRENT freed 1606K, 13% free 13544K/15559K, paused 22ms+12ms, total 115ms
D/dalvikvm(14917): WAIT_FOR_CONCURRENT_GC blocked 44ms
D/dalvikvm(14917): GC_CONCURRENT freed 1849K, 13% free 13544K/15559K, paused 21ms+7ms, total 93ms
D/dalvikvm(14917): WAIT_FOR_CONCURRENT_GC blocked 30ms
D/dalvikvm(14917): GC_CONCURRENT freed 1848K, 13% free 13543K/15559K, paused 20ms+8ms, total 101ms
D/dalvikvm(14917): WAIT_FOR_CONCURRENT_GC blocked 43ms
D/dalvikvm(14917): GC_CONCURRENT freed 1847K, 13% free 13543K/15559K, paused 18ms+10ms, total 109ms
D/dalvikvm(14917): WAIT_FOR_CONCURRENT_GC blocked 55ms
D/dalvikvm(16484): GC_CONCURRENT freed 445K, 6% free 9865K/10439K, paused 12ms+3ms, total 1067ms
I/ActivityManager( 247): Start proc android.process.acore for content provider com.android.providers.contacts/.CallLogProvider: pid=16516 uid=10007 gids={3003, 1015, 1028}
I/ActivityThread(16516): Pub call_log: com.android.providers.contacts.CallLogProvider
I/ActivityThread(16516): Pub com.android.voicemail: com.android.providers.contacts.VoicemailContentProvider
I/ActivityThread(16516): Pub user_dictionary: com.android.providers.userdictionary.UserDictionaryProvider
I/ActivityManager( 247): Process com.android.backupconfirm (pid 16090) has died.
I/ActivityThread(16516): Pub applications: com.android.providers.applications.ApplicationsProvider
I/ActivityThread(16516): Pub contacts;com.android.contacts: com.android.providers.contacts.ContactsProvider2
D/dalvikvm(16516): GC_CONCURRENT freed 233K, 5% free 8230K/8583K, paused 82ms+15ms, total 135ms
D/dalvikvm(14917): GC_CONCURRENT freed 1831K, 13% free 13561K/15559K, paused 15ms+5ms, total 101ms
D/dalvikvm(14917): WAIT_FOR_CONCURRENT_GC blocked 36ms
D/dalvikvm(14917): GC_FOR_ALLOC freed 390K, 14% free 13501K/15559K, paused 53ms, total 54ms
D/dalvikvm(14917): GC_FOR_ALLOC freed 2K, 12% free 13755K/15559K, paused 42ms, total 42ms
I/CarbonParser(14917): Finished demuxing com.android.providers.telephony
I/Carbon (14917): Completed: com.android.providers.telephony
I/Carbon (14917): Releasing locks.
I/Carbon (14917): Stopping.
W/InputMethodManagerService( 247): Window already focused, ignoring focus gain of: [email protected] [email protected]
D/dalvikvm(16516): GC_CONCURRENT freed 51K, 3% free 8593K/8775K, paused 45ms+5ms, total 130ms
D/dalvikvm(16484): GC_CONCURRENT freed 361K, 5% free 10040K/10503K, paused 39ms+49ms, total 566ms
D/dalvikvm(14917): GC_FOR_ALLOC freed 769K, 13% free 13796K/15751K, paused 162ms, total 164ms
I/ExternalStorage(14917): main: /storage/sdcard0
I/ExternalStorage(14917): other main: /storage/sdcard0
I/ExternalStorage(14917): Vol: /storage/sdcard0
I/ExternalStorage(14917): vols in list: 0
I/ActivityManager( 247): Process com.google.android.apps.plus (pid 16214) has died.
D/dalvikvm(16484): GC_CONCURRENT freed 492K, 6% free 10152K/10759K, paused 43ms+15ms, total 152ms
I/Carbon (14917): startBackup invoked: file
I/Carbon (14917): org.gnucash.android
D/PhoneStatusBar( 354): addNotification score=0
I/Carbon (14917): Releasing locks.
I/Carbon (14917): Acquiring full lock.
I/CarbonNonce(14917): Nonce: 36bea2ce-0ba5-4f0e-88d2-650fea91196b
I/Carbon (14917): bu 1 backup org.gnucash.android
W/System.err(14917): java.io.IOException: Connection refused
D/SizeAdaptiveLayout( 354): [email protected] view [email protected] measured out of bounds at 95px clamped to 96px
W/System.err(14917): at android.net.LocalSocketImpl.connectLocal(Native Method)
W/System.err(14917): at android.net.LocalSocketImpl.connect(LocalSocketImpl.java:238)
W/System.err(14917): at android.net.LocalSocket.connect(LocalSocket.java:98)
W/System.err(14917): at com.koushikdutta.shellproxy.ShellProcess2.<init>(ShellProcess2.java:124)
W/System.err(14917): at com.koushikdutta.shellproxy.ShellProcess2.exec(ShellProcess2.java:30)
W/System.err(14917): at com.koushikdutta.backup.BackupServiceHelper$11.onContinue(BackupServiceHelper.java:735)
W/System.err(14917): at com.koushikdutta.async.future.Continuation.next(Continuation.java:119)
W/System.err(14917): at com.koushikdutta.async.future.Continuation.start(Continuation.java:154)
W/System.err(14917): at com.koushikdutta.backup.BackupRestoreService$1$4.run(BackupRestoreService.java:246)
I/Carbon (14917): Releasing locks.
I/Carbon (14917): Stopping.
I/System.out(14917): Connection refused
E/ActivityThread(14917): Service com.koushikdutta.backup.BackupRestoreService has leaked ServiceConnection [email protected] that was originally bound here
E/ActivityThread(14917): android.app.ServiceConnectionLeaked: Service com.koushikdutta.backup.BackupRestoreService has leaked ServiceConnection [email protected] that was originally bound here
E/ActivityThread(14917): at android.app.LoadedApk$ServiceDispatcher.<init>(LoadedApk.java:965)
E/ActivityThread(14917): at android.app.LoadedApk.getServiceDispatcher(LoadedApk.java:859)
E/ActivityThread(14917): at android.app.ContextImpl.bindService(ContextImpl.java:1191)
E/ActivityThread(14917): at android.app.ContextImpl.bindService(ContextImpl.java:1183)
E/ActivityThread(14917): at android.content.ContextWrapper.bindService(ContextWrapper.java:394)
E/ActivityThread(14917): at android.media.MediaScannerConnection.connect(MediaScannerConnection.java:116)
E/ActivityThread(14917): at com.koushikdutta.backup.data.FileBackupPackage.<init>(FileBackupPackage.java:34)
E/ActivityThread(14917): at com.koushikdutta.backup.BackupRestoreService$1.startBackup(BackupRestoreService.java:128)
E/ActivityThread(14917): at com.koushikdutta.backup.BackupFragment$11.onServiceConnected(BackupFragment.java:340)
E/ActivityThread(14917): at android.app.LoadedApk$ServiceDispatcher.doConnected(LoadedApk.java:1097)
E/ActivityThread(14917): at android.app.LoadedApk$ServiceDispatcher$RunConnection.run(LoadedApk.java:1114)
E/ActivityThread(14917): at android.os.Handler.handleCallback(Handler.java:615)
E/ActivityThread(14917): at android.os.Handler.dispatchMessage(Handler.java:92)
E/ActivityThread(14917): at android.os.Looper.loop(Looper.java:137)
E/ActivityThread(14917): at android.app.ActivityThread.main(ActivityThread.java:4745)
E/ActivityThread(14917): at java.lang.reflect.Method.invokeNative(Native Method)
E/ActivityThread(14917): at java.lang.reflect.Method.invoke(Method.java:511)
E/ActivityThread(14917): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:786)
E/ActivityThread(14917): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:553)
E/ActivityThread(14917): at dalvik.system.NativeStart.main(Native Method)
D/dalvikvm(16484): GC_CONCURRENT freed 554K, 7% free 10213K/10887K, paused 22ms+16ms, total 128ms
I/Ads (14917): Ad is not visible. Not refreshing ad.
I/Ads (14917): Scheduling ad refresh 60000 milliseconds from now.
W/InputMethodManagerService( 247): Window already focused, ignoring focus gain of: [email protected] attribute=null
D/dalvikvm( 247): GC_CONCURRENT freed 1764K, 18% free 22183K/26887K, paused 17ms+12ms, total 234ms
Does the log help anyone figuring out whats wrong with my phone?
Hyperbo said:
Does the log help anyone figuring out whats wrong with my phone?
Click to expand...
Click to collapse
Sorry, I didn't get time to reply back. I saw the log and couldn't find much. I'll look at it carefully and get back to you in a day or two.
dont worry bro
here are instructions on how to unlock your Google Nexus S with fast boot and the standard recovery mode.
1.Turn off the phone completely.
2.Now hold down the volume up and power button.
3.You should have now entered Standard Recovery Mode.
4.Connect your phone to your PC/Mac via USB
5.Open command prompt (CMD on Windows) or Terminal (For Mac OSX)
6.Enter ¡®fastboot devices¡¯ without quotes to check whether your phone is connected via USB
7.Type ¡®adb reboot bootloader¡¯
8.Type ¡®fastboot oem unlock¡¯
9.Use volume keys to select ¡®yes, unlock bootloader¡¯
10.Use power button to select option
11.Your new bootloader is unlocked.
NOTE: This unlock performs a factory reset on your Android phone.
You can backup all your data using Go backup app or some other 3rd party app.
For more info you can visit Nexus s Hacks .com
Thanks for your reply. I've already tried what you sugested (see my first post). Step 8 is the problem because it wipes the phone (as you have written). To solve this you suggested the app Go Backup. In the german version of the play store it says that in order to backup your application data, it needs root. This sends me back to square one
Nevertheless I've tried the app. It displays a warning when it starts, that my phone is unrooted. After the backup process it says that it could only backup the app, but not the data, which doesn't help me when doing a factory reset.
Raakib zargar said:
here are instructions on how to unlock your Google Nexus S with fast boot and the standard recovery mode.
1.Turn off the phone completely.
2.Now hold down the volume up and power button.
3.You should have now entered Standard Recovery Mode.
4.Connect your phone to your PC/Mac via USB
5.Open command prompt (CMD on Windows) or Terminal (For Mac OSX)
6.Enter ¡®fastboot devices¡¯ without quotes to check whether your phone is connected via USB
7.Type ¡®adb reboot bootloader¡¯
8.Type ¡®fastboot oem unlock¡¯
9.Use volume keys to select ¡®yes, unlock bootloader¡¯
10.Use power button to select option
11.Your new bootloader is unlocked.
NOTE: This unlock performs a factory reset on your Android phone.
You can backup all your data using Go backup app or some other 3rd party app.
For more info you can visit Nexus s Hacks .com
Click to expand...
Click to collapse
Hyperbo said:
Thanks for your reply. I've already tried what you sugested (see my first post). Step 8 is the problem because it wipes the phone (as you have written). To solve this you suggested the app Go Backup. In the german version of the play store it says that in order to backup your application data, it needs root. This sends me back to square one
Nevertheless I've tried the app. It displays a warning when it starts, that my phone is unrooted. After the backup process it says that it could only backup the app, but not the data, which doesn't help me when doing a factory reset.
Click to expand...
Click to collapse
K Then You will need a pc for this:
*Download MoboRobo for pc
*Connect your device using usb cable and debugging on and backup anything you want even contacts and text messages i,e SMSs.....GoodLuck
---------- Post added at 08:08 AM ---------- Previous post was at 07:52 AM ----------
Hyperbo said:
Thanks for your reply. I've already tried what you sugested (see my first post). Step 8 is the problem because it wipes the phone (as you have written). To solve this you suggested the app Go Backup. In the german version of the play store it says that in order to backup your application data, it needs root. This sends me back to square one
Nevertheless I've tried the app. It displays a warning when it starts, that my phone is unrooted. After the backup process it says that it could only backup the app, but not the data, which doesn't help me when doing a factory reset.
Click to expand...
Click to collapse
K Then You will need a pc for this:
*Download MoboRobo for pc
*Connect your device using usb cable and debugging on and backup anything you want even contacts and text messages i,e SMSs.....GoodLuck
I ended up wiping my phone and losing the app data that couldn't be backed up. It wasn't worth all the hassle.
Thread can be closed.
Raakib zargar said:
K Then You will need a pc for this:
*Download MoboRobo for pc
*Connect your device using usb cable and debugging on and backup anything you want even contacts and text messages i,e SMSs.....GoodLuck
---------- Post added at 08:08 AM ---------- Previous post was at 07:52 AM ----------
K Then You will need a pc for this:
*Download MoboRobo for pc
*Connect your device using usb cable and debugging on and backup anything you want even contacts and text messages i,e SMSs.....GoodLuck
Click to expand...
Click to collapse
I've tried 3 CM based ROMs with different kernels and recoveries. All of them give this error when I try to install non-market apks like the ones from humble bundle. Specifically, larger apks which require extra files in the internal storage partition. Also, titanium backup freezes when I try to restore them. Does anybody have any idea what this is about? AOSP ROMs work fine.
Code:
12-19 12:35:24.806 I/PackageManager(820): Verification timed out for file:///mnt/sdcard/badland_android_46.apk
12-19 12:35:24.806 I/PackageManager(820): Continuing with installation of file:///mnt/sdcard/badland_android_46.apk
12-19 12:35:24.813 D/Finsky (14536): [1] PackageVerificationReceiver.onReceive: Verification requested, id = 43
12-19 12:35:24.816 D/Finsky (14536): [1] PackageVerificationService.cancelVerificationIntent: Cancel active verification id=43
12-19 12:35:25.105 E/Vold (185): Error creating imagefile (Read-only file system)
12-19 12:35:25.105 E/Vold (185): ASEC image file creation failed (Read-only file system)
12-19 12:35:25.105 W/Vold (185): Returning OperationFailed - no handler for errno 30
12-19 12:35:25.106 E/PackageHelper(22123): Failed to create secure container smdl1450163079.tmp
12-19 12:35:25.106 W/DefContainer(22123): Failed to copy package at /mnt/sdcard/badland_android_46.apk
12-19 12:35:25.106 W/DefContainer(22123): java.io.IOException: Failed to create container smdl1450163079.tmp
12-19 12:35:25.106 W/DefContainer(22123): at com.android.defcontainer.DefaultContainerService.copyPackageToContainerInner(DefaultContainerService.java:323)
12-19 12:35:25.106 W/DefContainer(22123): at com.android.defcontainer.DefaultContainerService.access$000(DefaultContainerService.java:67)
12-19 12:35:25.106 W/DefContainer(22123): at com.android.defcontainer.DefaultContainerService$1.copyPackageToContainer(DefaultContainerService.java:108)
12-19 12:35:25.106 W/DefContainer(22123): at com.android.internal.app.IMediaContainerService$Stub.onTransact(IMediaContainerService.java:60)
12-19 12:35:25.106 W/DefContainer(22123): at android.os.Binder.execTransact(Binder.java:446)
12-19 12:35:25.242 I/art (820): Explicit concurrent mark sweep GC freed 71196(3MB) AllocSpace objects, 20(8MB) LOS objects, 27% free, 42MB/58MB, paused 1.163ms total 133.773ms
12-19 12:35:25.246 D/InstallAppProgress(29894): Installation error code: -18
Geo2160 said:
I've tried 3 CM based ROMs with different kernels and recoveries. All of them give this error when I try to install non-market apks like the ones from humble bundle. Specifically, larger apks which require extra files in the internal storage partition. Does anybody have any idea what this is about?
Code:
12-19 12:35:24.806 I/PackageManager(820): Verification timed out for file:///mnt/sdcard/badland_android_46.apk
12-19 12:35:24.806 I/PackageManager(820): Continuing with installation of file:///mnt/sdcard/badland_android_46.apk
12-19 12:35:24.813 D/Finsky (14536): [1] PackageVerificationReceiver.onReceive: Verification requested, id = 43
12-19 12:35:24.816 D/Finsky (14536): [1] PackageVerificationService.cancelVerificationIntent: Cancel active verification id=43
12-19 12:35:25.105 E/Vold (185): Error creating imagefile (Read-only file system)
12-19 12:35:25.105 E/Vold (185): ASEC image file creation failed (Read-only file system)
12-19 12:35:25.105 W/Vold (185): Returning OperationFailed - no handler for errno 30
12-19 12:35:25.106 E/PackageHelper(22123): Failed to create secure container smdl1450163079.tmp
12-19 12:35:25.106 W/DefContainer(22123): Failed to copy package at /mnt/sdcard/badland_android_46.apk
12-19 12:35:25.106 W/DefContainer(22123): java.io.IOException: Failed to create container smdl1450163079.tmp
12-19 12:35:25.106 W/DefContainer(22123): at com.android.defcontainer.DefaultContainerService.copyPackageToContainerInner(DefaultContainerService.java:323)
12-19 12:35:25.106 W/DefContainer(22123): at com.android.defcontainer.DefaultContainerService.access$000(DefaultContainerService.java:67)
12-19 12:35:25.106 W/DefContainer(22123): at com.android.defcontainer.DefaultContainerService$1.copyPackageToContainer(DefaultContainerService.java:108)
12-19 12:35:25.106 W/DefContainer(22123): at com.android.internal.app.IMediaContainerService$Stub.onTransact(IMediaContainerService.java:60)
12-19 12:35:25.106 W/DefContainer(22123): at android.os.Binder.execTransact(Binder.java:446)
12-19 12:35:25.242 I/art (820): Explicit concurrent mark sweep GC freed 71196(3MB) AllocSpace objects, 20(8MB) LOS objects, 27% free, 42MB/58MB, paused 1.163ms total 133.773ms
12-19 12:35:25.246 D/InstallAppProgress(29894): Installation error code: -18
Click to expand...
Click to collapse
Hope you are not talking about cracks and warez. Not allowed on XDA.
Verstuurd vanaf mijn Nexus 5 met Tapatalk
Ofc not. I've mentioned clearly that the ones I have tried are from humble bundle. Also, I forgot to mention that restoring big apps like these through titanium causes it to freeze, even if they were downloaded from google play.
Try different gapps versions? Like.. There's PA gapps.. Banks gapps..
a maguro wrote this.
I didn't mention that I used different gapps for the ROMs because I didn't think the issue is related to gapps. I've even tried no gapps. What's the reasoning behind suggesting a different gapps package, since I'm not even trying to install google dependent apks?
Probably the same as yours then.
Does it work on stock?
Stock ROM, stock based ROMs like optipop and AOSP based ROMs like omni rom work fine.
The error you're getting is "read only".
Can you manually create files in the same location a on your /sdcard?
Geo2160 said:
I've tried 3 CM based ROMs with different kernels and recoveries. All of them give this error when I try to install non-market apks like the ones from humble bundle. Specifically, larger apks which require extra files in the internal storage partition. Also, titanium backup freezes when I try to restore them. Does anybody have any idea what this is about? AOSP ROMs work fine.
Click to expand...
Click to collapse
Sorry for bumping an old thread, but try this: http://forum.xda-developers.com/showpost.php?p=58409922&postcount=4845
Jani- said:
Sorry for bumping an old thread, but try this: http://forum.xda-developers.com/showpost.php?p=58409922&postcount=4845
Click to expand...
Click to collapse
Thanks a lot anyway! I can now go back to trying CM based ROMs.
That solution worked for me too. Thanks.
Jani- said:
Sorry for bumping an old thread, but try this: http://forum.xda-developers.com/showpost.php?p=58409922&postcount=4845
Click to expand...
Click to collapse
That solution unfortunately doesn't work for me. Under Settings > Apps > Menu I don't see "Preferred install location". Maybe because my Nexus 5 doesn't have a SD card?
I'm on CM 12.1-20150804-NIGHTLY. Any idea how I can fix this? Would really like to be able to restore apps via Titanium Backup and install apps from Amazon App-Shop.
Thanks!
Update:
Found a solution myself If you don't see the option "Preferred install location" like me you can set it via terminal:
Either open a shell on your phone via adb (adb shell) or with a terminal application on your phone, then type
su (to get superuser rights)
pm set-install-location 1 (to set install location to internal [0 = auto, 1 = internal, 2 = external])
I'm a novice enthusiast when it comes to phones. When my wife needed a replacement phone after hers started to fail (I blame repeated gravity-related incidents, but she insists that's not it), I decided to see if I could transform my old V20 into a "new" V20 for her. I didn't know what was to come, but I was going to do it!
This can also serve as a pseudo-guide for other novices, and something to laugh at for those more experienced as I list all the steps I took, and all the mistakes I made through the process. If you are going to use this as a guide, make sure you read it completely before starting! I've made mistakes, and I list them here, but don't repeat them!
Big list of files
Stuff for Linux live environment:
Etcherv1.7.9 https://github.com/balena-io/etcher/releases
steadfasterX's FWUL/mAid_v4.0-RC3_x86_64.iso https://leech.binbash.rocks:8008/mAid/
Stuff for Windows:
Android SDK Platform Tools (adb and fastboot) https://developer.android.com/studio/releases/platform-tools#downloads
LGMobileDriver_WHQL_Ver_4.8.0.exe http://tool.lime.gdms.lge.com/dn/downloader.dev?fileKey=UW00120120425
LGUP_Store_Frame_Ver_1_14_3.msi http://downloads.codefi.re/autoprime/LG/Flash_Tools/LGUP/
LGUP_Common_DLL_Ver_1_0_40_2.msi https://drive.google.com/uc?id=1MQ7u7ghlNNzjAgVkCpCmswdtZjeB3l6p&export=download&confirm=t
CXZa's utilities https://forum.xda-developers.com/t/lg-tools-lg-kdz-dll-tool-lgup_ui-fixer-lg-kdz-downloader.3916444/
Files you'll want on your external SD card:
H91810p_00_0717.kdz https://forum.xda-developers.com/t/...-and-including-20h-now-n00b-friendly.3773443/
Phoenix591's h918-20g-prerooted.zip https://forum.xda-developers.com/t/...-20g-20h-oreo-flashable.3848854/post-77987795
topjohnwu's Magisk-v23.0.zip (renamed from .apk) https://github.com/topjohnwu/Magisk/releases/tag/v23.0
TeamWin's twrp-3.6.1_9-0-h918.img https://dl.twrp.me/h918/
rootchecker apk https://apkpure.com/p/com.joeykrim.rootcheck
(optional but highly recommended) Darnrain1's Auto_Debloat v7.4 https://forum.xda-developers.com/t/...hones-volte-and-wifi-calling-working.4432865/
(optional) F-droid apk https://f-droid.org
(optional) laf_restore.zip https://forum.xda-developers.com/t/laf-restore-zip-file.4398879/
(optional) Phoenix591's encrypt-v3.zip https://forum.xda-developers.com/t/recovery-unofficial-twrp-3-3-1-1-2019-10-25.3720239/
Credits:
@topjohnwu for Magisk
@Phoenix591 for 20g in zip format and TWRP
@npjohnson for TWRP
@CXZa for their awesome LG utilities
@runningnak3d for the core of the project: lafsploit
@75th for updated method of using lafsploit
@steadfasterX for their amazing FWUL/mAid and SALT
@me2151 for their original root exploit Dirty Santa
@demasta123 for finding and sharing laf_restore.zip
@Darnrain1 for the excellent debloat script
What I did:
Flashed mAid_v4.0-RC3_x86_64.iso to my thumbdrive via Etcher.
Put the thumbdrive into my little Lenovo laptop and booted (had to reboot cause the bootloader menu was super brief), and selected "Search for GRUB2 configuration on external media"
Logged in (password is 'linux')
Connected to WiFi
Started V20 in download mode (VOLUP+USB)
Opened SALT and under Advanced found that none of my partitions were displayed (which I expected because the V20 has Universal Flash Storage).
In SALT there's three buttons on the bottom. The leftmost one allowed me to change all the ummm sources? builds? to 'develop' and then I restarted SALT. Now I can see the partitions!
Clicked the backup option and selected Custom. All the partitions appeared to be selected, but I can't see the whole window because it doesn't allow itself to be resized smaller than a certain point which was too large for my little laptop screen. Since it appeared that all the partitions were checkmarked, I tapped Enter and it prompted me for a location to save the 60GB(!) backup.
I opened the file browser and I found the laptop's internal hard drive listed as '158 GB Volume'. Clicking it prompted for a password so I tried 'linux' and it worked! I created a directory at /home/user/Documents/H918, then copied the very cryptic path from the address bar of the file browser over to SALT and started the backup.
I babysat the laptop so it would not fall asleep or w/e just in case that would ruin the backup.
It hung during the backup (possibly because I was looking for a way to change the mouse senstivity and the screen timeout) so I had to forcibly power off the laptop and reboot into FWUL/mAid. I had to remove the battery from the phone to get it out of download mode. I did everything as before but this time I am only backing up the userdata partition as it is by far the largest, and I am touching NOTHING during the process other than the occasional mouse jiggle. If/When that's done I'll backup everything else. I very much doubt I need the userdata but better safe than sorry. The speed is slow; less than 1GB/minute.
Hung again, and I discovered that my poor little laptop was super hot, so I think that my laptop's cooling has failed, or for some reason it doesn't engage in FWUL/mAid. I'll need to either find a cooling solution, or more likely use my big desktop for this.
I used my desktop to do this, and was able to extract all the partitions as .img files. I also captured my device info and saved it to the PC as well. I was going to do the rest of the steps right from FWUL/mAid but outside of SALT, I couldn't get anything to work. I think it was missing Java because nothing was listed for echo $JAVA_HOME and the ADB tool would not launch. I'll just do the rest from Windows.
Back in Windows I tried compressing the images with 7zip but it was being a resource hog so I'll do it later and let it run overnight since I want this super compressed.
I went through the process of unlocking the bootloader:
Booted up phone to OS.
Skipped/Bypassed as much of the initial setup as possible. For some reason it keeps telling me it will "process my request" when it has connection to the Internet (cell data or wifi). Don't know WTF that is. Hope it is wiped during the process of rooting and installing a new ROM.
PC didn't have drivers, but I ran the LGMobileDriver_WHQL_Ver_4.8.0.exe and it installed them.
Set USB mode to file transfer.
Enabled USB debugging.
Enabled Dev Options.
Enabled OEM unlock.
adb reboot bootloader
fastboot oem unlock
fastboot reboot
Since the userdata was wiped I had to go through the setup again, enabled dev options, usb debugging (oem unlock was enabled and greyed out unsurprisingly).
adb reboot bootloader
fastboot getvar unlocked (reported as yes; so the bootloader is successfully unlocked!)
Now for flashing H91810p_00_0717.kdz, I head back to FWUL/mAid to use SALT.
Or not. SALT doesn't work because LG changed something in regards to being able to flash as of MM, but it appears I can do this in Windows with LGUP.
A (device-specific?) DLL file is required for LGUP and after much searching I learned that it is extracted directly from the KDZ. Fortunately CXZa has some nifty tools available, one of which is a dll extractor which is perfect for this. The readme for the dll extractor said I should install LGUP_Common_DLL_Ver_1_0_40_2.msi in addition to LGUP_Store_Frame_Ver_1_14_3.msi so I did so. I used the dll extractor to get the needed dll file from H91810p_00_0717.kdz. The option to copy to the LGUP folder didn't appear to work so I tried again and told it to not copy the dll. It doesn't say as such but it places the extracted dll in the folder that the kdz was in with the same name as the KDZ +.dll.
Copied and renamed the extracted dll to 'C:\Program Files (x86)\LG Electronics\LGUP\model\Common\LGUP_Common.dll'
Upgraded LGUP with CXZa's tools (not really necessary but neat)
Ran LGUP as admin, selected UPGRADE, for the BIN file I selected the H91810p_00_0717.kdz that I downloaded from the link in the original lafsploit thread by runningnak3d, and clicked start (and held my breath...)
It worked! The phone rebooted as part of the process directly to the OS, and Settings > Phone Info shows "H91810p" so I should be ready for the next part which is following the updated lafsploit instructions by 75th with some minor edits by me for clarity: :
Boot from your FWUL/mAid USB stick.
Put your phone into download mode.
Double click the LG folder that is on the desktop.
Double click on open-lglafsploit.desktop and you will be at a terminal prompt.
Enter the following into that terminal. I'd copypasta the first line at least:
git clone https://gitlab.com/runningnak3d/lglaf -b h918-miscwrte
cd lglaf
./step1.sh
When you are told to, pull the USB cable, and the phone will power off. You now have TWRP on your laf partition.
I then booted to Download mode (VOLUP+USB) again and the phone booted to the TWRP 3.2.1-3 image installed on the laf partition. I did not mount system as rw (keep as read only). Chose Install > Install Image > and browsed to the TWRP image (twrp-3.6.1_9-0-h918.img) on my external SD. For the location to flash it I selected Recovery, and then swiped to flash.
When complete I hit the Back button twice, and changed to Install Zip. Selected Magisk-v23.0.zip, and swiped to confirm flash. When done wiped cache/dalvik, then reboot system. I opted to not install the TWRP app.
Back in the OS I turned on wifi because Magisk had to download the full app. Once Magisk was done I turned off wifi because holy **** why are outbound firewalls not a thing on phones!? Then w/in the Magisk app I selected Install, checkmarked both Preserve AVB 2.0/dm-verity and Preserve force encryption (I learned later this was a big mistake), and then chose the Direct Install method, and rebooted when it completed.
I then installed the root checker apk, and it verified that I was rooted!
Spoiler: THIS IS THE PART WHERE I AM ACTUALLY RETARDED
Read this section if you want to laugh at me, but don't follow any of the steps because it was a massive mistake due to my catastrophic stupidity.
Recovery and download mode issues?
If I am in the OS I can use adb reboot recovery and it will boot to TWRP 3.6.1_9-0 as expected. However if I do the hw key combo of VOLDN+PWR release PWR, hold PWR again, it takes me to what appears to be some stock "recovery" that only gives me the option to factory reset the device. Oddly, you have to tell it to reset your device and it will load TWRP 3.6.1_9-0 instead of doing a factory reset.
Also, if I try to go to download mode (which should have been replaced with a version of TWRP as part of the lafsploit process) it only brings me to a screen that says "Welcome to Fastboot Mode". This would be fine, but if I run fastboot reboot recovery it reboots not into recovery, but into the OS so I wonder if this fastboot mode is broken in some way. The *only* thing I can think of that may have caused fastboot to replace TWRP is installing Magisk as its process of patching the image(s) may have changed the laf partition from TWRP to fastboot. I also end up here if I am in TWRP and select reboot to bootloader, so is "download mode" == "bootloader"? I thought they were different tbh...
Next step is to get onto stock Oreo so I can run the debloater. To get oreo, Darnrain1 says "I have learned from experience that v20h has kernel panic green screen errors. Best to use v20g if you can." https://forum.xda-developers.com/t/...hones-volte-and-wifi-calling-working.4432865/
Ok so I'm wrong about the lafsploit TWRP being gone. When I attempted to flash to an Oreo ROM (H91820g_00_1010.kdz) via LGUP, it rebooted to TWRP 3.2.1-3! So the TWRP used to replace Download mode (the laf partition) is still there, but why do I get a fastboot prompt when I attempt to boot to download mode via the VOLDN+USB?
Summary:
In Android OS, adb reboot bootloader --> fastboot prompt
In Android OS, adb reboot recovery --> TWRP 3.6.1_9-0
In Android OS, adb reboot fastboot --> Android OS
In fastboot prompt, fastboot reboot bootloader --> fastboot prompt
In fastboot prompt, fastboot reboot recovery --> Android OS
In fastboot prompt, fastboot reboot --> Android OS
Within (either) TWRP, reboot bootloader --> fastboot prompt
Within (either) TWRP, reboot recovery --> TWRP 3.6.1_9-0
VOLDN+PWR, release PWR for 1s, hold PWR again --> TWRP 3.6.1_9-0 (after being prompted to factory reset)
VOLDN+USB --> fastboot prompt
Since LGUP won't work w/o the original laf partition for download mode, I had to find a copy of the laf_restore.zip at https://forum.xda-developers.com/t/laf-restore-zip-file.4398879/ since the links for it in the OP were dead. Flashed it via recovery TWRP 3.6.1_9-0, wiped cache/dalvik (probably not needed tbh), then reboot system.
Copied and renamed the dll extracted from H91820g_00_1010.kdz to 'C:\Program Files (x86)\LG Electronics\LGUP\model\Common\LGUP_Common.dll'. I suspect that I can just use the latest version of the dll, but I'm not going to risk anything so I will just use the one extracted from the very KDZ I'm flashing.
Ran LGUP as admin, selected UPGRADE, for the BIN file I selected the H91820g_00_1010.kdz file.
After reboot the phone reported its software version as H91820g. Magisk was still installed, but not surprisingly, root had been lost. This time there wasn't an easy Direct Install option so I'll need to extract the boot image so that Magisk can patch it, then I can flash it.
PROBLEM! Looks like the KDZ isn't just the OS, but also (all?) other partitions including recovery! I no longer have TWRP for my recovery. I really hope I can flash H91810p_00_0717.kdz back and redo lafsploit.
I was able to use LGUP to flash back to H91810p with the only complaint that the phone couldn't be decrypted so it had to be reset, which wasn't a problem and I let it do so.
I think I'm ****ed. Although I was able to reflash H91810p, I cannot run the lafsploit again because I only get "fastboot mode" when I hold VOLDN and plug in the USB. This fastboot mode doesn't work with the lafsploit script. I also do not have a recovery. adb reboot recovery sends me to a screen with a dead android mascot with a red triangle and the text "No command". Neither adb devices[ICODE] nor [ICODE]fastboot devices will list the phone in this mode, and LGUP doesn't see it. My recovery is totally broken.
I attempted fastboot flash recovery twrp-3.6.1_9-0-h918.img but got:
Sending 'recovery' (24948 KB) OKAY [ 3.608s]
Writing 'recovery' FAILED (remote: 'unknown command')
fastboot: error: Command failed
I used LGUP to once again reflash H91810p, and even though that should wipe everything, I also did the VOLDN+PWR, release PWR, press PWR, and told it to factory reset (no TWRP here of course so it actually factory reset). I jumped through initial ****up again and enabled dev options and USB debugging.
Now the phone isn't seen by LGUP. In device manager it shows as "Android Sooner Single ADB Interface". No COM ports. WTF!?
I tried running LGMobileDriver_WHQL_Ver_4.8.0.exe again. It didn't throw errors but nothing changed. Tried uninstalling the "sooner" device and reinstalling the LGMobileDriver. The "sooner" device just reappeared.
Windows Explorer gave me a hint though. It just showed "V20" listed with no access to its storage. On the phone I changed its USB mode to file transfer and now it shows up as a COM port. I'd forgotten that I had set the phone to always do file transfer before wiping it so it always showed up as a COM port in DM. God I'm dumb.
Now for something really ghetto. Since LGUP does send the phone into download mode when I tell it to flash, and I need to be in that mode to run the lafsploit script, I'm going to tell it to flash my phone and yank the USB cable as soon as the phone powers off for a reboot into DL mode.
It seems to have actually worked? Below is the output of my run of step1.sh:
This will install TWRP.
You do NOT need to do ANYTHING!
If it fails, NO damage is done to your phone.
If the hash check fails, it will make five attempts.
If after five attempts, it does not get a hash match, it will abort.
NO damage has been done to your phone.
You can re-run this script as many times as you want, however,
if you are not getting a hash match, you should try a different PC,
or a different cable, or a different USB port.
Press any key to continue...
Flashing... this will take a while.
Flashing TWRP to lafbak. Please wait...
Traceback (most recent call last):
File "/home/android/programs/lglafsploit/lglaf/./partitions.py", line 471, in <module>
main()
File "/home/android/programs/lglafsploit/lglaf/./partitions.py", line 421, in main
lglaf.try_hello(comm)
File "/home/android/programs/lglafsploit/lglaf/lglaf.py", line 401, in try_hello
data = comm.read(0x20, timeout=HELLO_READ_TIMEOUT)
File "/home/android/programs/lglafsploit/lglaf/lglaf.py", line 240, in read
buff = self._read(need, timeout=timeout)
File "/home/android/programs/lglafsploit/lglaf/lglaf.py", line 359, in _read
array = self.usbdev.read(self.ep_in, 2**14, timeout=timeout)
File "/usr/lib/python3.9/site-packages/usb/core.py", line 1029, in read
ret = fn(
File "/usr/lib/python3.9/site-packages/usb/backend/libusb1.py", line 846, in bulk_read
return self.__read(self.lib.libusb_bulk_transfer,
File "/usr/lib/python3.9/site-packages/usb/backend/libusb1.py", line 954, in __read
_check(retval)
File "/usr/lib/python3.9/site-packages/usb/backend/libusb1.py", line 602, in _check
raise USBTimeoutError(_strerror(ret), ret, _libusb_errno[ret])
usb.core.USBTimeoutError: [Errno 110] Operation timed out
Dumping lafbak for hash check...
[ 100 % ] 2022-04-25 20:22:36,237 partitions: INFO: Wrote 50331648 bytes to h918-twrp-tmp.img
Trimming trailing zeros
Checking hash...
TWRP hash: S260cb44d98c67f5ad11fb4512577b6ad4754d9fc8173802ae15d7f5c3aa39e3c
Test dump hash: S97ccbe70f0431f824a0f46c4256f0e7f3c1b6e0e9ac35f69978fbd58fe2b55be
Hash check failed! Retrying for 5 times.
Attempt 1 - Press ctrl C to break
Flashing TWRP to lafbak. Please wait...
[ 100 % ] 2022-04-25 20:23:58,271 partitions: INFO: Done after writing 29798400 bytes from h918-twrp.img
Dumping lafbak for hash check...
[ 100 % ] 2022-04-25 20:24:02,820 partitions: INFO: Wrote 50331648 bytes to h918-twrp-tmp.img
Trimming trailing zeros
Checking hash...
TWRP hash: S260cb44d98c67f5ad11fb4512577b6ad4754d9fc8173802ae15d7f5c3aa39e3c
Test dump hash: S260cb44d98c67f5ad11fb4512577b6ad4754d9fc8173802ae15d7f5c3aa39e3c
Hash check passed. Copying TWRP to laf
Flash sucessful! Unplug your USB cable and your phone will power off.
Once your phone is off, go back into download mode - hold vol up and plug the USB cable back in.
Once TWRP loads, you need to flash TWRP onto recovery.
Attempt 2 - Press ctrl C to break
Flashing TWRP to lafbak. Please wait...
Traceback (most recent call last):
File "/home/android/programs/lglafsploit/lglaf/./partitions.py", line 471, in <module>
main()
File "/home/android/programs/lglafsploit/lglaf/./partitions.py", line 421, in main
lglaf.try_hello(comm)
File "/home/android/programs/lglafsploit/lglaf/lglaf.py", line 401, in try_hello
data = comm.read(0x20, timeout=HELLO_READ_TIMEOUT)
File "/home/android/programs/lglafsploit/lglaf/lglaf.py", line 240, in read
buff = self._read(need, timeout=timeout)
File "/home/android/programs/lglafsploit/lglaf/lglaf.py", line 359, in _read
array = self.usbdev.read(self.ep_in, 2**14, timeout=timeout)
File "/usr/lib/python3.9/site-packages/usb/core.py", line 1029, in read
ret = fn(
File "/usr/lib/python3.9/site-packages/usb/backend/libusb1.py", line 846, in bulk_read
return self.__read(self.lib.libusb_bulk_transfer,
File "/usr/lib/python3.9/site-packages/usb/backend/libusb1.py", line 954, in __read
_check(retval)
File "/usr/lib/python3.9/site-packages/usb/backend/libusb1.py", line 602, in _check
raise USBTimeoutError(_strerror(ret), ret, _libusb_errno[ret])
usb.core.USBTimeoutError: [Errno 110] Operation timed out
Dumping lafbak for hash check...
Traceback (most recent call last):
File "/home/android/programs/lglafsploit/lglaf/./partitions.py", line 471, in <module>
main()
File "/home/android/programs/lglafsploit/lglaf/./partitions.py", line 421, in main
lglaf.try_hello(comm)
File "/home/android/programs/lglafsploit/lglaf/lglaf.py", line 401, in try_hello
data = comm.read(0x20, timeout=HELLO_READ_TIMEOUT)
File "/home/android/programs/lglafsploit/lglaf/lglaf.py", line 240, in read
buff = self._read(need, timeout=timeout)
File "/home/android/programs/lglafsploit/lglaf/lglaf.py", line 359, in _read
array = self.usbdev.read(self.ep_in, 2**14, timeout=timeout)
File "/usr/lib/python3.9/site-packages/usb/core.py", line 1029, in read
ret = fn(
File "/usr/lib/python3.9/site-packages/usb/backend/libusb1.py", line 846, in bulk_read
return self.__read(self.lib.libusb_bulk_transfer,
File "/usr/lib/python3.9/site-packages/usb/backend/libusb1.py", line 954, in __read
_check(retval)
File "/usr/lib/python3.9/site-packages/usb/backend/libusb1.py", line 602, in _check
raise USBTimeoutError(_strerror(ret), ret, _libusb_errno[ret])
usb.core.USBTimeoutError: [Errno 110] Operation timed out
Trimming trailing zeros
sha256sum: test.img: No such file or directory
Checking hash...
TWRP hash: S260cb44d98c67f5ad11fb4512577b6ad4754d9fc8173802ae15d7f5c3aa39e3c
Test dump hash: S
Hash check failed! Retrying for 5 times.
rm: cannot remove 'h918-twrp-tmp.img': No such file or directory
rm: cannot remove 'test.img': No such file or directory
Attempt 3 - Press ctrl C to break
Flashing TWRP to lafbak. Please wait...
Traceback (most recent call last):
File "/home/android/programs/lglafsploit/lglaf/./partitions.py", line 471, in <module>
main()
File "/home/android/programs/lglafsploit/lglaf/./partitions.py", line 421, in main
lglaf.try_hello(comm)
File "/home/android/programs/lglafsploit/lglaf/lglaf.py", line 401, in try_hello
data = comm.read(0x20, timeout=HELLO_READ_TIMEOUT)
File "/home/android/programs/lglafsploit/lglaf/lglaf.py", line 240, in read
buff = self._read(need, timeout=timeout)
File "/home/android/programs/lglafsploit/lglaf/lglaf.py", line 359, in _read
array = self.usbdev.read(self.ep_in, 2**14, timeout=timeout)
File "/usr/lib/python3.9/site-packages/usb/core.py", line 1029, in read
ret = fn(
File "/usr/lib/python3.9/site-packages/usb/backend/libusb1.py", line 846, in bulk_read
return self.__read(self.lib.libusb_bulk_transfer,
File "/usr/lib/python3.9/site-packages/usb/backend/libusb1.py", line 954, in __read
_check(retval)
File "/usr/lib/python3.9/site-packages/usb/backend/libusb1.py", line 602, in _check
raise USBTimeoutError(_strerror(ret), ret, _libusb_errno[ret])
usb.core.USBTimeoutError: [Errno 110] Operation timed out
Dumping lafbak for hash check...
Traceback (most recent call last):
File "/home/android/programs/lglafsploit/lglaf/./partitions.py", line 471, in <module>
main()
File "/home/android/programs/lglafsploit/lglaf/./partitions.py", line 421, in main
lglaf.try_hello(comm)
File "/home/android/programs/lglafsploit/lglaf/lglaf.py", line 401, in try_hello
data = comm.read(0x20, timeout=HELLO_READ_TIMEOUT)
File "/home/android/programs/lglafsploit/lglaf/lglaf.py", line 240, in read
buff = self._read(need, timeout=timeout)
File "/home/android/programs/lglafsploit/lglaf/lglaf.py", line 359, in _read
array = self.usbdev.read(self.ep_in, 2**14, timeout=timeout)
File "/usr/lib/python3.9/site-packages/usb/core.py", line 1029, in read
ret = fn(
File "/usr/lib/python3.9/site-packages/usb/backend/libusb1.py", line 846, in bulk_read
return self.__read(self.lib.libusb_bulk_transfer,
File "/usr/lib/python3.9/site-packages/usb/backend/libusb1.py", line 954, in __read
_check(retval)
File "/usr/lib/python3.9/site-packages/usb/backend/libusb1.py", line 602, in _check
raise USBTimeoutError(_strerror(ret), ret, _libusb_errno[ret])
usb.core.USBTimeoutError: [Errno 110] Operation timed out
Trimming trailing zeros
sha256sum: test.img: No such file or directory
Checking hash...
TWRP hash: S260cb44d98c67f5ad11fb4512577b6ad4754d9fc8173802ae15d7f5c3aa39e3c
Test dump hash: S
Hash check failed! Retrying for 5 times.
rm: cannot remove 'h918-twrp-tmp.img': No such file or directory
rm: cannot remove 'test.img': No such file or directory
Attempt 4 - Press ctrl C to break
Flashing TWRP to lafbak. Please wait...
Traceback (most recent call last):
File "/home/android/programs/lglafsploit/lglaf/./partitions.py", line 471, in <module>
main()
File "/home/android/programs/lglafsploit/lglaf/./partitions.py", line 421, in main
lglaf.try_hello(comm)
File "/home/android/programs/lglafsploit/lglaf/lglaf.py", line 401, in try_hello
data = comm.read(0x20, timeout=HELLO_READ_TIMEOUT)
File "/home/android/programs/lglafsploit/lglaf/lglaf.py", line 240, in read
buff = self._read(need, timeout=timeout)
File "/home/android/programs/lglafsploit/lglaf/lglaf.py", line 359, in _read
array = self.usbdev.read(self.ep_in, 2**14, timeout=timeout)
File "/usr/lib/python3.9/site-packages/usb/core.py", line 1029, in read
ret = fn(
File "/usr/lib/python3.9/site-packages/usb/backend/libusb1.py", line 846, in bulk_read
return self.__read(self.lib.libusb_bulk_transfer,
File "/usr/lib/python3.9/site-packages/usb/backend/libusb1.py", line 954, in __read
_check(retval)
File "/usr/lib/python3.9/site-packages/usb/backend/libusb1.py", line 602, in _check
raise USBTimeoutError(_strerror(ret), ret, _libusb_errno[ret])
usb.core.USBTimeoutError: [Errno 110] Operation timed out
Dumping lafbak for hash check...
Traceback (most recent call last):
File "/home/android/programs/lglafsploit/lglaf/./partitions.py", line 471, in <module>
main()
File "/home/android/programs/lglafsploit/lglaf/./partitions.py", line 421, in main
lglaf.try_hello(comm)
File "/home/android/programs/lglafsploit/lglaf/lglaf.py", line 401, in try_hello
data = comm.read(0x20, timeout=HELLO_READ_TIMEOUT)
File "/home/android/programs/lglafsploit/lglaf/lglaf.py", line 240, in read
buff = self._read(need, timeout=timeout)
File "/home/android/programs/lglafsploit/lglaf/lglaf.py", line 359, in _read
array = self.usbdev.read(self.ep_in, 2**14, timeout=timeout)
File "/usr/lib/python3.9/site-packages/usb/core.py", line 1029, in read
ret = fn(
File "/usr/lib/python3.9/site-packages/usb/backend/libusb1.py", line 846, in bulk_read
return self.__read(self.lib.libusb_bulk_transfer,
File "/usr/lib/python3.9/site-packages/usb/backend/libusb1.py", line 954, in __read
_check(retval)
File "/usr/lib/python3.9/site-packages/usb/backend/libusb1.py", line 602, in _check
raise USBTimeoutError(_strerror(ret), ret, _libusb_errno[ret])
usb.core.USBTimeoutError: [Errno 110] Operation timed out
Trimming trailing zeros
sha256sum: test.img: No such file or directory
Checking hash...
TWRP hash: S260cb44d98c67f5ad11fb4512577b6ad4754d9fc8173802ae15d7f5c3aa39e3c
Test dump hash: S
Hash check failed! Retrying for 5 times.
rm: cannot remove 'h918-twrp-tmp.img': No such file or directory
rm: cannot remove 'test.img': No such file or directory
Attempt 5 - Press ctrl C to break
Flashing TWRP to lafbak. Please wait...
Traceback (most recent call last):
File "/home/android/programs/lglafsploit/lglaf/./partitions.py", line 471, in <module>
main()
File "/home/android/programs/lglafsploit/lglaf/./partitions.py", line 421, in main
lglaf.try_hello(comm)
File "/home/android/programs/lglafsploit/lglaf/lglaf.py", line 401, in try_hello
data = comm.read(0x20, timeout=HELLO_READ_TIMEOUT)
File "/home/android/programs/lglafsploit/lglaf/lglaf.py", line 240, in read
buff = self._read(need, timeout=timeout)
File "/home/android/programs/lglafsploit/lglaf/lglaf.py", line 359, in _read
array = self.usbdev.read(self.ep_in, 2**14, timeout=timeout)
File "/usr/lib/python3.9/site-packages/usb/core.py", line 1029, in read
ret = fn(
File "/usr/lib/python3.9/site-packages/usb/backend/libusb1.py", line 846, in bulk_read
return self.__read(self.lib.libusb_bulk_transfer,
File "/usr/lib/python3.9/site-packages/usb/backend/libusb1.py", line 954, in __read
_check(retval)
File "/usr/lib/python3.9/site-packages/usb/backend/libusb1.py", line 602, in _check
raise USBTimeoutError(_strerror(ret), ret, _libusb_errno[ret])
usb.core.USBTimeoutError: [Errno 110] Operation timed out
Dumping lafbak for hash check...
Traceback (most recent call last):
File "/home/android/programs/lglafsploit/lglaf/./partitions.py", line 471, in <module>
main()
File "/home/android/programs/lglafsploit/lglaf/./partitions.py", line 421, in main
lglaf.try_hello(comm)
File "/home/android/programs/lglafsploit/lglaf/lglaf.py", line 401, in try_hello
data = comm.read(0x20, timeout=HELLO_READ_TIMEOUT)
File "/home/android/programs/lglafsploit/lglaf/lglaf.py", line 240, in read
buff = self._read(need, timeout=timeout)
File "/home/android/programs/lglafsploit/lglaf/lglaf.py", line 359, in _read
array = self.usbdev.read(self.ep_in, 2**14, timeout=timeout)
File "/usr/lib/python3.9/site-packages/usb/core.py", line 1029, in read
ret = fn(
File "/usr/lib/python3.9/site-packages/usb/backend/libusb1.py", line 846, in bulk_read
return self.__read(self.lib.libusb_bulk_transfer,
File "/usr/lib/python3.9/site-packages/usb/backend/libusb1.py", line 954, in __read
_check(retval)
File "/usr/lib/python3.9/site-packages/usb/backend/libusb1.py", line 602, in _check
raise USBTimeoutError(_strerror(ret), ret, _libusb_errno[ret])
usb.core.USBTimeoutError: [Errno 110] Operation timed out
Trimming trailing zeros
sha256sum: test.img: No such file or directory
Checking hash...
TWRP hash: S260cb44d98c67f5ad11fb4512577b6ad4754d9fc8173802ae15d7f5c3aa39e3c
Test dump hash: S
Hash check failed! Retrying for 5 times.
rm: cannot remove 'h918-twrp-tmp.img': No such file or directory
rm: cannot remove 'test.img': No such file or directory
Hash check failed after 5 attempts - exiting
[[email protected] lglaf]$
Strange that it ran 5 times even though appears to have worked the first time? Well let's see if it works.
I followed the instructions to get back into download mode by plugging the USB cable back in while holding VOLUP...
{
"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"
}
It's ****ing volume up and USB. Volume up. UP. UUUUUUUUUUPPPPPPPPP! At some point my brain decided "DOWNload mode is accessed by pressing volume DOWN + USB"
With 10p and the original laf back on the phone I went through the same steps as before for lafsploit and got TWRP 3.6.1_9-0 flashed onto recovery again. I figured that since I have to re-run Magisk after flashing 20g there isn't any point to doing it now so I skipped it this time.
Then w/in recovery I flashed h918-20g-prerooted.zip, wiped cache, and rebooted to System. Once there I went into Magisk and did the recommended Direct Install method for patching the image and rebooted. Tested with a root checker app and we have root!
Sweet, now it is time to debloat the phone and get it set up for actual use, but first I will check to make sure my tools are still accessable.
VOLUP+USB will show TWRP 3.2.1-3 briefly then the phone reboots... which is super odd, but not a dealbreaker since the VOLDN+PWR, release PWR for 1s, press PWR method gets me to actual recovery (TWRP 3.6.1_9-0).
Going into recovery I find that the device is encrypted and asks for a password that I never configured (was this set up on first boot of 20g, or did Magisk do this?). Reading online looks like you can virtually never decrypt your data in TWRP, but if you want to make any changes you'll need to get rid of the encryption. That's a shame because it's like you can have either a secure device (encrypted), or a usable one (rooted and debloated). I need a usable one so goodbye encryption.
Wipe > Format data > reboot
It booted to something called "Secure start-up" and said "Decryption unsuccessful" and that I needed to reset the phone. Sure, whatever. It then rebooted to recovery (TWRP 3.6.1_9-0). Weird. But data was not encrypted this time. Tried rebooting to system and got the same secure startup thing. Tried resetting again and back to recovery. Decided to just flash the 20g zip again and reboot.
I am at Secure start-up again! WTH?! I told it to reset to get me back to TWRP and here under Wipe I selected
Dalvik
System
Data
Internal Storage
Cache
and did a Format Data again. Then told it to reboot to Recovery, not System.
Back in TWRP I told it to mount System and allow modifications. Changed the filesysem of System from vfat to ext4 to make extra sure System was nuked. Reboot System (it shouldn't boot to anything if the ****er is actually wiped this time). Hung on LG logo, so I'm pretty sure I was able to remove the old OS.
Pulled battery, and did the VOLDN+PWR, release PWR for 1s, press PWR dance to get into "factory reset" which in reality leads to TWRP 3.6.1_9-0. Flashed 20g again, hopefully with better success.
Secure start-up! Why won't this thing die?! I initially thought that it was the ROM itself, or wiping data in TWRP irrevokably ****ed it somehow. Further reading lead me to this post by Theraze who clued me in that TWRP for V20 has a bug that doesn't properly clear the encryption flag. Fantastic.
I would go back and start over but I don't think I can. I'd need to use the LGUP utility, but since the phone doesn't present itself as a COM port anymore I
don't think it will work. On a whim I tried LGUP... and after like a full minute it ****ing sees the phone! I will try flashing H91810p_00_0717.kdz onto it again. It booted to TWRP 3.2.1-3 lol. I forgot we replaced the laf dl mode with TWRP.
Went to TWRP 3.6.1_9-0, flashed laf_restore.zip, rebooted to system ~SuCKurE sTarTuP~. Ran LGUP again and told it to flash 10p again. (I really wish the default option was UPGRADE and not REFURBISH; I'm sure I'm going to **** it up one of these times)
I can't believe it. I literally cannot believe it. After flashing H91810p_00_0717.kdz via LGUP I am at the Secure start-up screen. The only difference is it looks slightly different due to it being Nougat this time instead of Oreo. I told it to reset the phone JIC it will actually work, and went to pour myself a stiff drink.
Resetting actually worked. Holy. ****.
FWUL/mAid, lafsploit, flash TWRP 3.6.1_9-0 to recovery, reboot to recovery (no encryption prompt), reboot system, no secure setup.
Tried VOLDN+PWR, release PWR for 1s, press PWR, but it did not put me into recovery. It erased my device. Power off, VOLUP+USB, went into TWRP 3.2.1-3. Reboot recovery. Dead droid "no command" again. GDI.
TWRP 3.2.1-3, flash laf_restore (glad it let me; was worried that I couldn't flash the laf partition while on lafTWRP), reboot system. LGUP to flash 10p AGAIN. Didn't erase the device so didn't need to do setup again at least.
FWUL/mAid, lafsploit again.
In TWRP 3.2.1-3 I did nothing but flash TWRP 3.6.1_9-0 to Recovery and reboot system. Then I ran adb reboot recovery. Dead droid, no command. ****.
LGUP to flash 10p yet again, but this time after it booted up, I did the VOLDN+PWR dance and told it to factory reset. It rebooted and I did setup again, and rebooted to system once before shutting down.
FWUL/mAid and lafsploit yet again.
Unplugged USB and the phone powered off like it should. Then VOLUP+USB. Swiped to allow modifications.
Wiped:
Dalvik
Data
Internal Storage
Cache
Format Data:
Formatting Data using make_ext4fs...
Failed to mount '/data/ (Device or resource busy)
Failed to mount '/data/ (Device or resource busy)
Unable to recreate /data/media folder.
You may need to reboot recovery to be able to use /data again.
Updating partition details...
Failed to mount '/data/ (Device or resource busy)
...done
Unable to mount storage
Opening TWRP's terminal and doing ls shows a /data with lost and found so it's there and empty.
Ran the following command via the TWRP terminal in case the GUI method of flashing is somehow not working:
dd if=/external_sd/Docs/TWRP/twrp-3.6.1_9-0-h918.img of=/dev/block/bootdevice/by-name/recovery
I tried running the following but the file didn't exist:
rm /system/recovery-from-boot.p
Flashed Magisk23.0.zip and again 'Failed to mount '/data/ (Device or resource busy)'. Tried to wipe dalvik/cache but it failed. Reboot System.
Went through initial ****up again. Completed and did adb reboot recovery.
Got to TWRP 3.6.1_9-0. This time. Swiped to allow modifications. Reboot system.
adb reboot recovery
Got TWRP 3.6.1_9-0 so it *might* be working now. Reboot > power off.
Tried VOLDN+PWR dance and it took me to recovery.
I think the lesson is wipe the **** out of the device after getting into lafTWRP both before and after flashing new TWRP to Recovery. Also swipe to allow modification so if there's secret sauce behind the scenes in System that's killing recovery TWRP it is neutralized during the process of getting 3.6.1_9-0 flashed. I am unsure if flashing Magisk is required as part of the process. I don't believe it is as I think mounting system as rw and wiping the other partitions is what's really needed, but I don't think it actually harms anything. (later on I learned that wiping is only part of it; Magisk and no-verity-opt-encrypt are what's needed to stop the encryption that was causing secure startup)
I rebooted to system and again adb reboot recovery. I went to TWRP 3.6.1_9-0 but it did not prompt me about swiping to make modifications so I immediately did reboot system. I was expecting Secure startup but it didn't appear, thank ****.
Back to recovery and I flashed no-verity-opt-encrypt-6.1.zip in the hopes that it would prevent Suckure startup from occuring again when I flash 20g in a minute. Wiped dalv/cache tho probably unnecessary. Reboot system.
No problems thus far. Time to flash 20g again.
Rebooted to recovery and told it to flash 20g. Since I've learned how amazing and cathartic wiping is, I formated data, and then wiped:
Dalvik/Cache
Data (probably not needed)
Internal Storage
Cache
Reboot system.
Secure start-up. *sigh*
VOLDN+PWR dance actually worked this time so that's nice. Swiped to allow modifications. Flashed no-verity-opt-encrypt-6.1.zip. Format data, wipe dalvik data internal cache again. Reboot system.
Secure start-up.
Recovery > flashed laf_restore > reboot system. Secure startup ofc, but I can run LGUP and flash 10p KDZ again to start over. Again.
I'm 99.999% sure that encryption being enabled is the problem.
In https://forum.xda-developers.com/t/twrp-3-1-1-0-touch-recovery.3603760/post-73129295 me2151 says that "Encryption unsuccessful is because you did not do supersu or something to disable force-encrypt". Note that he says "Encryption unsuccessful" but the problem I have is "decryption unsuccessful". Not sure if a typo or a different issue.
Phoenix591 says https://forum.xda-developers.com/t/twrp-3-1-1-0-touch-recovery.3603760/post-75429764 "You need to either root or install no-verity-opt-encrypt to keep stock from replacing twrp with stock recovery iirc"
This makes me think that I'll need to flash Magisk *and* no-verity-opt-encrypt to ensure that there is no encryption at all for the data partition.
FWUL/mAid froze while I was doing this so I hope my notes are correct as they're from my highly fallible memory:
lafsploit
VOLUP+USB > lafTWRP
Left system as ro
Format data (It even mentions we'd need to reenter recovery for data to be accessible again ffs. No wonder I was getting Failed to mount '/data/ (Device or resource busy). I need to learn how to read.)
Reboot > Power off
VOLUP+USB > lafTWRP
System ro
Wipe dalv, data, internal, cache
Flash Magisk (it mentions that forceencryption is enabled and will keep it that way when patching)
Flash no-verity-opt-encrypt-6.1.zip (to override the forced encryption)
Flash TWRP 3.6.1_9-0 to recovery
Reboot recovery
Made it to TWRP 3.6.1_9-0, yay
I would have left ro if prompted; for some reason the prompt about system modifications is inconsistant; sometimes it asks, sometimes not
Reboot system
Did first time setup again, dev options, turn on wifi, let magisk update and let it reboot
Back in system used Magisk's Direct Install method leaving "preserve AVB" UN-checked in case AVB forces encryption back on. Interestingly there wasn't an option for 'Preserve force encryption' so I think no-verity-opt-encrypt is working.
Rebooted
Installed root check app and we have root
Reboot recovery
Format data
Reboot RECOVERY (NOT system!)
Wipe dalv, data, internal, cache
Reboot RECOVERY (NOT system!) <-- not sure if needed, but I'm so sick of secure setup
Flash 20g zip
Flash magisk
Flash no-verity-opt-encrypt
Reboot system this time
Oh my ****ing god it's not at secure setup! It's at the normal first time setup for Oreo!
Did first time setup again, dev options, turn on wifi, let magisk update and let it reboot
Back in system used Magisk's Direct Install method leaving "preserve AVB" UN-checked in case AVB forces encryption back on (still no Preserve force encryption) and rebooted
Installed root checker and it's rooted
Tested adb reboot recovery and it worked
Tested VOLDN+PWR dance and it worked
Time for debloat
Already in recovery from testing the methods to get into recovery
Wipe > advanced > just dalvik and cache this time (hope this is all I need to do)
Flash Auto_Debloat v7.4
Swiped to wipe dalv/cache JIC
Reboot system
Success!
I suspect that (but haven't tried) flashing encrypt-v3.zip at this point will encrypt userdata and have it decryptable in TWRP. It might not work with the official TWRP 3.6.1_9-0, but Phoenix591 says it should with his version of TWRP. However, this adventure has gone on long enough so I'm not keen on trying it. Maybe later when I have some energy.
Well that was a trip. Skimmed through didn't read everything. Liked the touch of memes properly used. Congrats.
lol thank you. It was quite the journey but I feel like I learned from it so it was a good experience.
Oh fer... yep. Lol That's about what a nightmare (journey is a good word, too lol) rooting phones can be & precisely why 7% (at the VERY most) of cell phone users really end up doing it. I'm just glad to be a part of (the even smaller) percentage of us that enjoy helping one another. Thanks to all for being so helpful.
Good job Sidney & thank you.
Nice report. Read bits here and there - as usual.
And very detailed. I should start taking notes too...
SidneyD said:
dead android mascot with a red triangle and the text "No command"
Click to expand...
Click to collapse
Some stock recoveries does this. Next time try pressing power and then Vol Up shortly...
always good to see users sharing their knowledge and congrats that you was steadfast enough going through all this !
Thanks for that and as a little site note: SALT can extract KDZs too, ofc even with the DLL needed for LGup later
I found that attempting to format my thumb drive back to a general purpose storage device only showed 60MB of space. I've experienced this before and knew that I had to use the diskpart command to fix the partitions. I fixed it by following the guide at: https://www.diskpart.com/articles/how-to-format-usb-drive-in-command-prompt-7201.html
Be careful about selecting the correct disk number!
SidneyD said:
I found that attempting to format my thumb drive back to a general purpose storage device only showed 60MB of space. I've experienced this before and knew that I had to use the diskpart command to fix the partitions. I fixed it by following the guide at: https://www.diskpart.com/articles/how-to-format-usb-drive-in-command-prompt-7201.html
Be careful about selecting the correct disk number!
Click to expand...
Click to collapse
Awesome. Thx Sidney.
Thanks for the guide. Were you able to keep VoLTE? Does this re Sim Lock the phone? Thanks from a nervous noob