Database Users

Device stuck at "unfortunatly system ui was stopped"

My father device suddenly decided to get stuck right after boot with the above error message.
I tried reboot into safe mode but got the same result.
I tried to connect it to my PC using abd(after installing drivers), but for some reason adb didn't recognize the device (fastboot however did find it).
Any ideas before doing hard reset?!

System does not mount and i need to extract files by ADB

hi
While working with the device, it reset without prior warning, and since it trying to start and when the Google logo disappears and the animation stage arrives, 3 seconds later it turns himself off.
I entered into the Recovery mode and cleaned Cash - did not help
I thought to take out the battery in case something might be stuck in my memory but I still have not done it because when I dismantled the small panel (on the part of the camera) I accidentally turned on the device and it showed me that it upgrades the apps, which was a good sign for me so I closed the panel and waited for it to finish The 147 applications. At the end he turned himself off
I did not proceed with the matter of dismantling the battery.
I have the default recovery, I did not install recovery applications that expand the possibilities in the recovery mode.
and i don't remember if i turned on the USB debugging.
I decided to transfer the files (pic's, whtsapp) by ADB befor i try the factory reset
but I get sideload instead of recovery
C: \ adb> adb devices
List of devices attached
R ********** sideload (I changed the stereo to asterisks)
and every command I try to run I get
error: closed
Does anyone have an idea of how to copy files or repair the system ?
thanks

You should be able to bring it to fastboot mode by powering it off, then holding Power, Volume up an Volume down until the robot appears.
From there you should see the device with "fastboot devices". You might need to install some drivers at that point.
When in fastboot you should be able to start TWRP with "fastboot boot twrp-3.1.1-0-manta.img". When in TWRP you can see /sdcard in Windows or you can start Advanced > File Manager and copy your data to a USB stick.

thanks bornheim2
i succeeded to load the TWRP
but when i unplug the USB for plugin the OTG the screen start blinking and the devices turned off.
i have charge the device all night
so my guess is that my battery is bad.
can i use usb a male to usb a male adapter
or Hittime smart 3 in 1 Micro USB OTG/Sync/Charging cable
( i can't put links )
to connect the device with OTG to the computer for power and for transfer data to the computer ?
thanks

[email protected] said:
i succeeded to load the TWRP
but when i unplug the USB for plugin the OTG the screen start blinking and the devices turned off.
i have charge the device all night so my guess is that my battery is bad.
Click to expand...
Click to collapse
You should see the device in Windows when TWRP is running (and the device is charged by the PC). That should be enough to save your files.

i don't see it on windows (computer)

[email protected] said:
i don't see it on windows (computer)
Click to expand...
Click to collapse
That might be a driver problem. Do you see it in Device Manager on Windows? Probably with a yellow triangle?

it's good in the devices manager "Android Bootloader Interface"

but after the TWRP it upload, the devices no longer appears in the device manager
and the screen is still blinking

when i run the "fastboot boot twrp-3.1.1-0-manta.img"
it turn in the device manager to "Android ADB recovery interface" and after 1 sec is disconnect

H E L P - bootlooping, COM does not recognize phone

Hi everybody,
ill try to make it short:
My 6p has entered into the bootlooping mode.
I have never unlocked the bootloader/changed ROM/kernal.
After I let it bootloop until the battery is dead it's changing from bootlooping into blinking red dot. Then when I charge it for a couple of minutes it comes back to life after 10~ min it's bootlooping again - so I have a window of possibilities to play with the setting. In that window I have used the "OEM unlocking" option.
In the bootlooping state when I boot into the bootloader and connect it into the PC the device doesn't recognize that it has been connected and a PC ,and the PC recognize a entry of new device but doesn't recognize it is a Nexus 6p.
this situation is the same when I connect the phone when it is alive.
I have installed adb and fastboot with this software
https://forum.xda-developers.com/showthread.php?t=2588979
with the 1.4.3 version it shows in the end of the process "0 files copied" and then I tried the 1.3 version and it showed that 4 files were copied but it also showed an error.
I have also downloaded ADB from google site but it does not work either.
When I try to open the powershell in a folder where I have downloaded an img and type in a fastboot command the computer doens't recognize any type of command.
So if anyone can help me ill be glad.
Thanks in advance,
Matan.

matan4442 said:
Hi everybody,
ill try to make it short:
My 6p has entered into the bootlooping mode.
I have never unlocked the bootloader/changed ROM/kernal.
After I let it bootloop until the battery is dead it's changing from bootlooping into blinking red dot. Then when I charge it for a couple of minutes it comes back to life after 10~ min it's bootlooping again - so I have a window of possibilities to play with the setting. In that window I have used the "OEM unlocking" option.
In the bootlooping state when I boot into the bootloader and connect it into the PC the device doesn't recognize that it has been connected and a PC ,and the PC recognize a entry of new device but doesn't recognize it is a Nexus 6p. Matan.
Click to expand...
Click to collapse
What is the new device identified as....Qualcomm HS-USB QDLoader 9008? Your phone may be stuck in EDL mode. If that is the case you need to search XDA and attempt solutions for that problem first.
Did you previously have your PC setup properly with the correct USB drivers and it was working OK, or just now trying to get your dead phone to communicate? If the former it may be the EDL issue above. If it was the latter, the communication problem may just be the drivers were never set up in the first place. Have you tried a different cable or port on your PC, or another PC?
With no access to the OS you will be unable unlock the bootloader or access to ADB because those have to be enabled FIRST in the OS, so there's no helping you here until you can actually boot into the OS. Do you have access to Recovery mode? Tried a factory reset? If you don't have recovery, that was a major omission.

Yoga Tab 3 Plus (YT-X703F) - "unfortunately system ui has stopped"

Hi there,
Since the upgrade to Nougat 7.1.1, my
Code:
Yoga Tab 3 plus (YT-X703F) is showing the following error "unfortunately system ui has stopped" each time I plugged the usb charger. The screen stay black until I unplug the usb cable. So far, I tried without success
1) Factory reset via the reinitiation menu - Error still present after reinitiation
2) Boot into the recovery console - Not working. The bootloader hang and does not initiate the recovery console. I can restart the tablet into the normal mode after the battery pull method or via [FONT="Courier New"]fastboot reboot[/FONT] command. The recovery console has been either erased or corrupted in the upgrade process.
3) ADB and Fastboot - not working. I cannot authorise the device since the screen is lock into black as above and both tools return the tablet status as unauthorized ([FONT="Courier New"]adb devices[/FONT] or [FONT="Courier New"]fastboot devices[/FONT]).
4) Boot in safe mode. Error is still present. I cannot access the tablet when charging and/or plug to a computer via USB.
Any help would be appreciated...

Unable to boot Xperia Z3 Compact? (Able to boot into fastboot, not recovery, no logo)

Messing around with my Z3 compact, which was already rooted and I'm sure the bootloader was already unlocked when I first rooted it. Anyways I tried to install Magisk for testing purposes, now I have a non-functional phone. Now I can't boot into recovery mode (I had TWRP) or into the regular mode.
I can boot into fastboot mode (plug in USB + hold Power & Volume UP --> 3 Vibrations --> Blue LED Notification). I checked using flashtoolx64 and it does detect the phone is in fastboot mode.
However when i try to flash the stock firmware, where I have to restart the phone in flashmode (Power off --> hold Volume Down --> Plug in USB), Windows says there is an error recognizing the device. and when I check device manager, it says the USB Device entry is: Unknown USB Device (Configuration Descriptor Request Failed). Could this be a driver issue?
I couldn't find any other solutions for restoring the system without going into flashmode, because it looks like i can't even get that working. I would appreciate any solutions that utilize fastboot mode, since that is the only mode I can get into with the computer recognizing it.
-Edit 1-
Silly me, it turns out I was able to get into flashmode afterall (Power Off > Volume Down > Plug in USB).
After double checking and re-installing the Sony Xperia USB drivers, I thought the phone was done. I tried plugging in the phone using the back USB ports instead of the front and voila flashtools can push the stock firmware. My guess is that the "Configuration Descriptor Request" error I saw in the Device Manager was because I was using the front USB ports on my PC.
-Edit 2-
Apologies, clicked on the wrong forum when it should have been posted in the troubleshooting forum. This thread can be closed/deleted since I figured out what's wrong (see edit 1)