System UI has stopped, Phone locked

[Jack_731]

Hey All,

Device - Motorola One Power
Status - Completely in Stock condition
OS Version - 10(QPTS30.61-18-3)

After I changed a wallpaper on the phone, a popup "System UI has stopped" is perpetually occurring on top of my lock-screen which is making me unable to unlock or use the phone.
User is given with two options on the popup error, App info and Stop app, selecting any of these will give a blank screen and error will popup again repeating the same process.

Situation - USB Debugging is not enabled, USB connection settings set to charging as default.



Troubleshooting and results
1. Normal Mode - Fingerprint accepted, vibration feedback received, PIN mandatory, cannot login as display goes blank after every touch.
2. Safe Mode - Same issues as normal boot.
3. USB OTG-Mouse - Mouse pointer appears on top of the popup error, cannot dismiss, same issue as normal and safe boot.
4. Emergency call mode - Popup appears even on the emergency call.
5. Wipe Cache is unavailable in recovery as the I guess it's the new seamless A/B data structure.

Situation : Data is not backed up and Full Userdata wipe is not an option..

Wipe Data is not an option as I have the only copy of photos of recent family get-together and baby cousin's birthday which I could not back up due to lack of personal time.

Is there any way to get my data back ?
Fastboot?
ADB Zip Sideload?
Factory Mode?

Please help me out guys
Thanks

 

[Jack_731]

Anyone?
Please help guys

 

[sd_shadow]

Anyone?
Please help guys

Without USB debugging enabled,
I don't think there are any options.
You could try to flash firmware and skip the
erase userdata command

But with the bootloader lock likely
Flashing is blocked.


Sent from my ali using XDA Labs

 

[Jack_731]

Without USB debugging enabled,
I don't think there are any options.
You could try to flash firmware and skip the
erase userdata command

But with the bootloader lock likely
Flashing is blocked.


Sent from my ali using XDA Labs

Thank you for replying

USB Debugging is disabled, but when I boot to Recovery and go to 'load zip using ADB', ADB gets loaded in "Sideload" mode and the device is visible in Sideload mode in ADB command prompt.

Questions
1) Can I an sideload an official OTA Zip on a locked bootloader?
Here is a link from google support on that same sideload method for Google Pixel https://support.google.com/pixelphone/thread/17016500?hl=en&dark=1
Am referring to that cause my phone is running Android One, and they have migrated the data structure into the new A/B seamless partition.

Thank you again

 

[sd_shadow]

Thank you for replying



USB Debugging is disabled, but when I boot to Recovery and go to 'load zip using ADB', ADB gets loaded in "Sideload" mode and the device is visible in Sideload mode in ADB command prompt.



Questions

1) Can I an sideload an official OTA Zip on a locked bootloader?

Here is a link from google support on that same sideload method for Google Pixel https://support.google.com/pixelphone/thread/17016500?hl=en&dark=1

Am referring to that cause my phone is running Android One, and they have migrated the data structure into the new A/B seamless partition.



Thank you again

Possibly, but Motorola doesn't openly share the OTA updates like Google

Sent from my Moto E (4) using Tapatalk

 

[Jack_731]

Possibly, but Motorola doesn't openly share the OTA updates like Google

Sent from my Moto E (4) using Tapatalk

Here is a link to a tool made by members of xda https://xdaforums.com/moto-z/development/tool-motorola-ota-link-generator-tool-t3537039

and here is another link of firmwares for motorola one power https://mirrors.lolinet.com/firmware/moto/chef/official/RETIN/

Can you guide on how should I try this way?

Please help me out

Thanks

 

[Jack_731]

Anyone here with the expertise and knowledge to guide me through the process?
Any kind of link or guide or steps in which I can revive my on-device data?
Please help me out.
It will be very helpful to me ..

 

[Jack_731]

Anyone?

Any help will be appreciated

Thanks..

 

[sd_shadow]

[

Hi,
Will this method work on Locked BLs, and if USB Debug is off?
My Phone - Moto One Power

I don't think the ota update method is going to work.
But editing the erase userdata line
Then flashing with LMSA may
As discussed here
https://xdaforums.com/g5-plus/how-to/how-to-flash-stock-loosing-data-t3871703

 

[sd_shadow]

Hey @sd_shadow

this is what I get on my Moto One Power (fastboot getvar all)

(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-chef_retail-38523c9-200122
(bootloader) product: chef
(bootloader) board: chef
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: APAC
(bootloader) storage-type: eMMC
(bootloader) emmc: 64GB SAMSUNG DH6DMB RV=08 PV=05 FV=0000000000000005
(bootloader) ufs: N/A
(bootloader) ram: 4GB SAMSUNG LP4x DIE=16Gb M5=01 M6=06 M7=10 M8=12
(bootloader) cpu: SDM636 1.0 (1)
(bootloader) serialno: ZF6223TFLL
(bootloader) cid: 0x0032
(bootloader) channelid: 0xc0
(bootloader) uid: FDF7898C
(bootloader) verity-state: enforcing (0)

No more info from bootloader.

BL = Locked
USB Debug = Locked
Unrooted

Is there anything I should do?
Thanks

I don't know over half the lines are missing

You should have more like this

(bootloader) verity-state: disabled (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei:  
(bootloader) meid:
(bootloader) date: 11-20-2018
(bootloader) sku: XT1900-1
(bootloader) carrier_sku: XT1900-1
(bootloader) battid: SNN5994A
(bootloader) battery-voltage: 4006
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/payton/payton:9/PPWS29.69
(bootloader) ro.build.fingerprint[1]: -39-6-2/d2226:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.461.11.payton.ret
(bootloader) ro.build.version.full[1]: ail.en.US
(bootloader) ro.build.version.qcom: LA.UM.7.2.r1-04900-sdm660.0
(bootloader) version-baseband: M660_7045.36.01.100R PAYTON_NA_CUST
(bootloader) kernel.version[0]: Linux version 4.4.153-perf-g496fe5a (hud
(bootloader) kernel.version[1]: soncm@ilclbld56) (gcc version 4.9.x 2015
(bootloader) kernel.version[2]: 0123 (prerelease) (GCC) ) #1 SMP PREEMPT
(bootloader) kernel.version[3]:  Thu Oct 31 07:27:03 CDT 2019
(bootloader) git:abl: MBM-3.0-payton_retail-eca8056-191031
(bootloader) git:xbl: MBM-3.0-payton_retail-dec7b7c-191031
(bootloader) git:pmic: MBM-3.0-payton_retail-dec7b7c-191031
(bootloader) git:rpm: MBM-3.0-payton_retail-b0c6622-191031
(bootloader) git:tz: MBM-3.0-payton_retail-fa205ea-dirty-191031
(bootloader) git:hyp: MBM-3.0-payton_retail-fa205ea-dirty-191031
(bootloader) git:devcfg: MBM-3.0-payton_retail-fa205ea-dirty-191031
(bootloader) git:cmnlib: MBM-3.0-payton_retail-fa205ea-dirty-191031
(bootloader) git:cmnlib64: MBM-3.0-payton_retail-fa205ea-dirty-191031
(bootloader) git:keymaster: MBM-3.0-payton_retail-fa205ea-dirty-191031
(bootloader) git:prov: MBM-3.0-payton_retail-fa205ea-dirty-191031
(bootloader) git:storsec: MBM-3.0-payton_retail-fa205ea-dirty-191031
(bootloader) frp-state: no protection (77)
(bootloader) ro.carrier: retus
(bootloader) current-slot: b
(bootloader) running-bl-slot: _b/_b
(bootloader) running-boot-lun: 0
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: yes
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 6
all: listed above
Finished. Total time: 0.250s

 

[sysuicrash0511]

Hey, I just saw your post in my Pixel 3a thread (link if anyone is curious), sorry to hear you ended up in the same boat.

For what it's worth, my 3a suffered from a screen issue before. It's very unlikely (though not impossible) that something was corrupted being processed, but I wanted to add this thought.

Anyway, I hope you find a solution if nothing from my thread works. Although somewhat chaotic (and sometimes unconventional by freezing the UI before it crashes/restarts), it featured every bit me and others were able to think of.
In the end, only a factory reset helped and I lost all data in the process.

I would have been able to rescue everything, if I only had one more second between crashes or hadn't I rebooted in the meantime (no fingerprint allowed), sadly such small obstacles can be complete roadblocks.

So, sorry for not being of bigger help, but if you manage to find a solution which might be applicable to the 3a as well, I'd happily add it to my thread, too.

Good luck.

 

[Jack_731]

Hey, I just saw your post in my Pixel 3a thread (link if anyone is curious), sorry to hear you ended up in the same boat.

For what it's worth, my 3a suffered from a screen issue before. It's very unlikely (though not impossible) that something was corrupted being processed, but I wanted to add this thought.

Anyway, I hope you find a solution if nothing from my thread works. Although somewhat chaotic (and sometimes unconventional by freezing the UI before it crashes/restarts), it featured every bit me and others were able to think of.
In the end, only a factory reset helped and I lost all data in the process.

I would have been able to rescue everything, if I only had one more second between crashes or hadn't I rebooted in the meantime (no fingerprint allowed), sadly such small obstacles can be complete roadblocks.

So, sorry for not being of bigger help, but if you manage to find a solution which might be applicable to the 3a as well, I'd happily add it to my thread, too.

Good luck.

Hey there,

I think we understand each others problems very well,
Don't be sorry, your post has actually helped me understand that am not alone with the current issue.

This is a serious issue in Android Devices (System UI has stopped), and I guess more than 80% of the consumers don't know anything about USB Debugging or would keep that enabled.
First of all, an error popup should not be front and center on any UI, the pop-up should be dismiss-able / can be minimized away from the general display area of any device.
Just like when in older Android UI, even an incoming-call used to take the entire screen, but nowadays, they are part of notifications, if the user is focusing on another app.
The fact that this 'System UI' error occurred on the latest Android 10 update (Feb 2020), makes it even worse., that Android hasn't matured yet to be stable.

In hindsight, yes if we had not restarted the phone the moment we face that "System UI keeps stopping" error, the in-device data could have been saved 100%.
Cause the phone was functional even after the error pops up, and there are certain ways we can circumvent it (except restarting).

At least Google is publicly providing OTAs for Pixels so that users can try sideloading.
Motorola doesn't provide anything official, even though it's an "Android One" device.

I guess I will have to do factory reset after all , If nothing turns up positive.
Will keep you posted.
Thanks
Cheers

 

[Jack_731]

I don't know over half the lines are missing

You should have more like this

(bootloader) verity-state: disabled (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei:  
(bootloader) meid:
(bootloader) date: 11-20-2018
(bootloader) sku: XT1900-1
(bootloader) carrier_sku: XT1900-1
(bootloader) battid: SNN5994A
(bootloader) battery-voltage: 4006
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/payton/payton:9/PPWS29.69
(bootloader) ro.build.fingerprint[1]: -39-6-2/d2226:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.461.11.payton.ret
(bootloader) ro.build.version.full[1]: ail.en.US
(bootloader) ro.build.version.qcom: LA.UM.7.2.r1-04900-sdm660.0
(bootloader) version-baseband: M660_7045.36.01.100R PAYTON_NA_CUST
(bootloader) kernel.version[0]: Linux version 4.4.153-perf-g496fe5a (hud
(bootloader) kernel.version[1]: soncm@ilclbld56) (gcc version 4.9.x 2015
(bootloader) kernel.version[2]: 0123 (prerelease) (GCC) ) #1 SMP PREEMPT
(bootloader) kernel.version[3]:  Thu Oct 31 07:27:03 CDT 2019
(bootloader) git:abl: MBM-3.0-payton_retail-eca8056-191031
(bootloader) git:xbl: MBM-3.0-payton_retail-dec7b7c-191031
(bootloader) git:pmic: MBM-3.0-payton_retail-dec7b7c-191031
(bootloader) git:rpm: MBM-3.0-payton_retail-b0c6622-191031
(bootloader) git:tz: MBM-3.0-payton_retail-fa205ea-dirty-191031
(bootloader) git:hyp: MBM-3.0-payton_retail-fa205ea-dirty-191031
(bootloader) git:devcfg: MBM-3.0-payton_retail-fa205ea-dirty-191031
(bootloader) git:cmnlib: MBM-3.0-payton_retail-fa205ea-dirty-191031
(bootloader) git:cmnlib64: MBM-3.0-payton_retail-fa205ea-dirty-191031
(bootloader) git:keymaster: MBM-3.0-payton_retail-fa205ea-dirty-191031
(bootloader) git:prov: MBM-3.0-payton_retail-fa205ea-dirty-191031
(bootloader) git:storsec: MBM-3.0-payton_retail-fa205ea-dirty-191031
(bootloader) frp-state: no protection (77)
(bootloader) ro.carrier: retus
(bootloader) current-slot: b
(bootloader) running-bl-slot: _b/_b
(bootloader) running-boot-lun: 0
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: yes
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 6
all: listed above
Finished. Total time: 0.250s

This was the error message displayed after the command.

getvar:all FAILED (status read failed (Too many links))

Is there any hardware issue with the phone?

 

[Jack_731]

Hey @sd_shadow,

Can you check these recovery logs to get a clearer picture of this issue?


Especially these lines

ro.adb.secure=1
ro.mot.security.enable=1
ro.opa.eligible_device=true
ro.secure=1
ro.debuggable=0
ro.oem_unlock_supported=1
ro.boot.flash.locked=1
ro.boot.write_protect=0
ro.boot.secure_hardware=1

1) Does it means it is flash protected?
2) If 'fastboot getvar all' command result is not completely getting loaded, does that mean "fastboot flash" command is out of bounds?

Thanks..

 

[Jack_731]

Hey @sd_shadow,

Can you check these recovery logs to get a clearer picture of this issue?


Especially these lines

ro.adb.secure=1
ro.mot.security.enable=1
ro.opa.eligible_device=true
ro.secure=1
ro.debuggable=0
ro.oem_unlock_supported=1
ro.boot.flash.locked=1
ro.boot.write_protect=0
ro.boot.secure_hardware=1

1) Does it means it is flash protected?
2) If 'fastboot getvar all' command result is not completely getting loaded, does that mean "fastboot flash" command is out of bounds?

Thanks..

@sd_shadow
What do you think?
Am a bit concerned , as If I may get stuck while flashing and this phone will end up useless.

If 'fastboot getvar all' command result is not completely getting loaded, does that mean "fastboot flash" command is out of bounds?

Thanks