Develop Bugs

[Q] Galaxy Nexus in Boot Loop after "Unfortunately system UI has stopped" error

[Q] Galaxy Nexus in Boot Loop after "Unfortunately system UI has stopped" error
Hi,
Out of the blue, after dragging about an app folder on my home screen, my system froze and this message popped up:
"Unfortunately system UI has stopped"
I had the option to report or press OK. I clicked OK. The phone operated for a few seconds then the error came back up, this time I couldn't click anything.
At this point I pulled the battery and replaced it. The phone booted up and i opened facebook, then the same error popped up again. Just like before I could click OK the first time but not the second time.
I pulled the battery again and it booted again, but the message soon popped up once more. (after a few seconds) This time however, the phone rebooted itself and after that, it rebooted again.
Eventually it would not go beyond the boot animation.
At this point I was panicking. I attempted rebooting in to Odin mode by holding down the volume down button and power button, but it just keeps telling me to wait or press power to start.
After that I tried fastboot and a factory reset from recovery but that didn't have any effect.
The battery is dead now so I have the phone charging. Any suggestions on where to go from here. If I turn it on it will just loop the boot animation with all the colours over and over.
Thanks!

The factory reset seems to have actually worked. It was taking a while to boot when the battery died right after I did it but when I booted it up this morning after charging it booted normally.
To factory reset boot in to fastboot by pushing and holding volume up + volume down + power then select "Recovery mode" when the image of the android robot shows up press power + volume up to get the menu and select factory reset from there.

Thanks for posting the solution. This was the first hit from a google search for "Galaxy nexus boot loop" and it was just what I needed.
My boot loop seemed to have started for a different reason. Apparently, moving away from a wifi access point while you're still connected causes the boot loop as well. I owned my nexus for about 1 hour before the boot loop happened, so I suppose I was relatively lucky.

Anomaly said:
Hi,
Out of the blue, after dragging about an app folder on my home screen, my system froze and this message popped up:
"Unfortunately system UI has stopped"
I had the option to report or press OK. I clicked OK. The phone operated for a few seconds then the error came back up, this time I couldn't click anything.
At this point I pulled the battery and replaced it. The phone booted up and i opened facebook, then the same error popped up again. Just like before I could click OK the first time but not the second time.
I pulled the battery again and it booted again, but the message soon popped up once more. (after a few seconds) This time however, the phone rebooted itself and after that, it rebooted again.
Eventually it would not go beyond the boot animation.
At this point I was panicking. I attempted rebooting in to Odin mode by holding down the volume down button and power button, but it just keeps telling me to wait or press power to start.
After that I tried fastboot and a factory reset from recovery but that didn't have any effect.
The battery is dead now so I have the phone charging. Any suggestions on where to go from here. If I turn it on it will just loop the boot animation with all the colours over and over.
Thanks!
Click to expand...
Click to collapse
I guess the SD internal is formatted when this happends and you factory reset? I lost all images and sms, damnit

Maybe this works without factory reset
Anomaly said:
The factory reset seems to have actually worked. It was taking a while to boot when the battery died right after I did it but when I booted it up this morning after charging it booted normally.
To factory reset boot in to fastboot by pushing and holding volume up + volume down + power then select "Recovery mode" when the image of the android robot shows up press power + volume up to get the menu and select factory reset from there.
Click to expand...
Click to collapse
Two people say that multiple reboots solved the problem. See http://j.mp/Vgwamr

[Q] Kindle Fire powers on, flashes and shuts down

I have come into my possession a Kindle Fire 1st generation. When I got it, the youngster said it was “hacked for the Amazon App Store”… and the battery was dead. I traded an older laptop for it. I put it on a charger for a day or so and left it. It would boot to the “Stock” logo for several seconds, then the backlight would go slightly brighter and it would shut off.
I started reading up about some of the power-on issues around the web. I found most of my answers on “xda-developers.com” for my TF101 so I gravitated here.
Here is what I’ve done so far:
1. Acquired a factory cable... SO useful.
2. Flashed FFF v1.4a and TWRP v2.4.4.0
3. Played around with fastboot.exe commands -update, flash, erase, getvar, reboot, help
4. Flashed a stock bootloader and recovery… trying to get it to charge.
5. Disassembled and tested battery voltage… 4.10VDC on a 3.7V battery. That sounds good to me.
6. Tried the firekit boot from Live-USB. Won’t stay powered on.
Right now, I’ve flashed the FFF 1.4a and TWRP v2.5. What happens is, in normal boot, the fire boots to the FFF logo (White &Blue) goes to “Booting” and the power switch LED gets slightly brighter, then the backlight goes slightly brighter and the whole thing shuts off. If I push power to go to recovery, the fire shows “Booting.” Then, the power switch goes orange, then it goes off, then the whole thing shuts down. I cannot do any ADB commands because the Fire will not stay powered on in that mode. The factory cable keeps it powered on, but I’m stuck with fastboot.exe commands in that mode.
I do not have a stock charger. I’ve been using my charger from my TF101 and a cable from my phone or the factory cable. I’ve been futzing around with this thing for a few weeks and would like some input. I haven’t found an identical issue so I’ve decided to create a thread.
I’m wondering if I have a bad gate on the memory chip… I’ve seen desktops and laptops shut down with bad memory in the past. I’m reasonably savvy with a command prompt and not afraid to crack a box.

Hold the power button until the device shuts off completely. Plug it in to your USB cable power source (not the factory cable), and let it power on automatically. Immediately after it starts to power on, hold the power button to shut it off again. Let it charge in this state for a few hours and try to boot into recovery again.

soupmagnet said:
Hold the power button until the device shuts off completely. Plug it in to your USB cable power source (not the factory cable), and let it power on automatically. Immediately after it starts to power on, hold the power button to shut it off again. Let it charge in this state for a few hours and try to boot into recovery again.
Click to expand...
Click to collapse
Thank you Soupmagnet. I've done this and let it sit for a weekend... sorry I didn't mention it before. With a voltage reading of 4.1, I think I have a full charge (by the way, it doesn't drop over a day or so). You can be assured that I've tried most everything before posting. Please be gentle if I didn't state it previously
One of my issues is I can't get to anything on the fire itself. Even with the factory cable, is shuts off if I choose to continue... hold the power button and choose recovery, normal, reset boot mode. Is it supposed to be able to go to recovery when the factory cable is connected? It only stays powered if I leave it at the FFF logo.

pmrmx774 said:
Thank you Soupmagnet. I've done this and let it sit for a weekend... sorry I didn't mention it before. With a voltage reading of 4.1, I think I have a full charge (by the way, it doesn't drop over a day or so). You can be assured that I've tried most everything before posting. Please be gentle if I didn't state it previously
One of my issues is I can't get to anything on the fire itself. Even with the factory cable, is shuts off if I choose to continue... hold the power button and choose recovery, normal, reset boot mode. Is it supposed to be able to go to recovery when the factory cable is connected? It only stays powered if I leave it at the FFF logo.
Click to expand...
Click to collapse
What command did you use to install TWRP?

soupmagnet said:
What command did you use to install TWRP?
Click to expand...
Click to collapse
Fastboot -i 0x1949 flash recovery c:\KFU\recovery\twrp.img.
This is after I renamed the v2.4.4.0 file to old_twrp.img and downloaded the v2.5 that I found last Friday. Previously, i'd used the KFU. Last week I played around with flashing different bootloader and recovery to see if I could get it past the FFF or stock. At this point it's a challenge to get it to go further than FFF.

pmrmx774 said:
Fastboot -i 0x1949 flash recovery c:\KFU\recovery\twrp.img.
This is after I renamed the v2.4.4.0 file to old_twrp.img and downloaded the v2.5 that I found last Friday. Previously, i'd used the KFU. Last week I played around with flashing different bootloader and recovery to see if I could get it past the FFF or stock. At this point it's a challenge to get it to go further than FFF.
Click to expand...
Click to collapse
Use fastboot to flash this to your system partition and see if you can boot normally.... http://d-h.st/NzN

Perhaps it is hardware, not software
Just had a very similar issue. Turned out to be stupid simple.
Use spudgers to gently take the back off the case (a small flathead screwdriver should do the trick). then check the connection between the battery and the motherboard. In my case, my daughter had dropped it enough times that the connection was not all the way out but not enough in. This caused the exact behavior you are describing. Took me 2 minutes to fuss with once I got motivated.
Jon

Problem with booting G4

Hello, I would like to first tell you the story my LG G4 has gone through and then I tell you the error.
So, at first my phone was working absolutely properly. I accidentally deleted some pictures and to do a recovery, I had to root it. And rooting would be useful for later so why not do it?
So I first unlocked the bootloader through the code from the LG site. After unlocking, the phone reset (because it would be just too good to make some memory changes and nothing more.) But allright. Then I was ready to root. I just booted the phone, everything was fine. I unlocked the developer mode and opened ADB. I rebooted to recovery through
Code:
adb reboot recovery
I was expecting to see some menu with buttons (but that would be just too good). However, I saw just android with a red triangle in the middle. Nothing more. No response to buttons, nothing.
So I thought. Allright, let's boot into recovery using hardware buttons (vol down + power) at startup. Unfortunatelly, it seemed like there is no such mode System just normally booted (and that was just after bootloader unlocking. Recovery mode goodbye.).
I tried to send commands to the phone using diagnostic port. Unfortunately, it responded by FAIL to every command.
I reboot to bootloader and booted an image: "boot-em.img" (from here: google: how-to-root-lg-g4-on-android-6-0-marshmallow-20a20b-firmware. I'm a newbie here. thx for understanding.)
After that the console uploaded the image and booted successfully. Then, however, system started to boot up and was endlessly booting (LG boot animation) till the battery was critical.
I was able to access the EMI number through volume-down button and volume-up button pressed simultaneously.
I was also able to access some factory-reset dialog by holding volume-down and pressing power-button several times. I choosed to reset everything and then accepted it with one more 'are you sure dialog'. System rebooted and was stucked in the LG boot animation.
Then I got to download mode, since recovery mode was lost in hell. Through LG-UP I flashed the original KDZ firmware and everything got back to normal, but recovery mode was still inaccessible through the hardware buttons. I got through the process of setting everything up, getting developer, rebooting to bootloader and I booted TWRP.
TWRP loaded and it responded to double-tap on screen to wake it up. I just checked the menus and let the phone sleep.
After several hours I went back to the phone and double-tapped on display. Nothing. Phone was not responding. I pressed the power button and the phone restarted (I think. It either restarted into the system or was not responding to power button.)
So I got to the system and again rebooted to the TWRP (through fast-boot). I tried to back-up one partition to the disk. During the process phone had turned the display off. So I double tapped. Nothing. I removed the SD card and the phone woke, saying that back-up process was not able to complete. Suddenly it stopped responding to double-tap. It woke up through an interrupt. I re-inserted the card, successfully backed-up the partition to the SD-card and I left the phone laying on the bed plugged in the charger. It stayed that way for 4 hours or so, doing nothing. All of a sudden, a yellow screen was there, (and that's a screen of absolute death that was never supposed to come. Little I knew.) saying that an unexpected critical error happened and to do a memory dump, insert a cable, set up some communication (I don't remember what it was, didn't take a picture of it.) and it could send the memory dump to PC or somewhere. I thought to myself. So, the application is not so stable after all. It said that to reboot just press the power button or something.
And now the problem comes:
The first start: Bootloader booted, LG animation went on and finished. The starting up apps dialog came rolling. Then, system restarted.
The restart: Bootloader booted, LG animation went on and freezed. Then, the phone restarted.
Second restart: The same thing as the first one.
Fourth restart up till now: Bootloader tries to boot and restarts before the LG animation.
I got to download mode and it restarted even there. After re-inserting the batterry I can sometimes get to the Firmware Update window and communicate. There I flashed the official firmware again.
No success, as if I didn't even do it. It restarts before the animation.
Can I do anything with the phone? Hopefully I can. No hardware problem occured (except for a situation where the error could fry the wires inside the mighty System On Chip.)
For the software state I cannot even tell but I might say it's cooked just wrong. That's why I came here.
I know I did some pretty stupid steps. But the error was not done by me. It worked fine and after the yellow screen which came by itself, it just (some bad words).
Thanks for replies.
Phone: LG-G4 H815, European market

Solution
So, I was looking around and believe it or not, this problem disconnected the pins on the motherboard's snapdragon 808.
I think this happened: The device, although it was heated many times during its life, it withstood that so far.
However, a longer run of the TWRP had finished it off. Memory got disconnected while running and it threw a yellow-screen.
Pins got disconnected and from then on it was just a standard common LG bootloop issue.
The continuous process of dying (First it partially loaded, then only animation, then nothing) is explained by this fact that the pins were so-so there and a couple of reboots just got it totaled.
Temporary fix:
Pre-heated the memory chip to 250°C using Hot-Air gun. After 18 seconds at this temperature I pressed the memory on top of the snapdragon down to the board while cooling.
Then I added a little metal square on the metal part that is covering the system on chip. This part is over the SOC where before there was just some tape.
This can work for several days in sleep mode or a couple of 'heat-demanding' operations on the phone.
Permanent solution should be to reball the memory chip on the snapdragon. That's my next step.

Note is stuck in a bootloop - and I can't seem to install recovery/not sure if it's corrupt

Hey all,
Hope you've been keeping safe and well.
So I was flashing the new PixelExperience ROM - and seems like I made an error somewhere along the way.
I'm looking to return to stock, and then give the process another shot - but at the moment my phone is stuck in a bootloop.
The bootloader is unlocked - and the boot goes through the following screens before rebooting:
1. Samsung Logo
2. "The phone's bootloader in unlocked....Press power key to continue"
3. Samsung Note 10+ Logo Screen.
I'm trying my best to try and boot into either download or recovery mode, but to no avail - it just restarts the bootloop on each combination I've tried.
Any solutions on how to get moving with this?
Thanks!

rajalot said:
Hey all,
Hope you've been keeping safe and well.
So I was flashing the new PixelExperience ROM - and seems like I made an error somewhere along the way.
I'm looking to return to stock, and then give the process another shot - but at the moment my phone is stuck in a bootloop.
The bootloader is unlocked - and the boot goes through the following screens before rebooting:
1. Samsung Logo
2. "The phone's bootloader in unlocked....Press power key to continue"
3. Samsung Note 10+ Logo Screen.
I'm trying my best to try and boot into either download or recovery mode, but to no avail - it just restarts the bootloop on each combination I've tried.
Any solutions on how to get moving with this?
Thanks!
Click to expand...
Click to collapse
Timing will be the key. To help out, boot up as you have been, but as early into the boot cycle press and hold the Vol - and power button for up to 5 seconds (until phone manually shuts off) [it will actually reboot the phone])), then the instant it powers off and begins to power back on (try a few times to get used to the timing) press and hold the key combination for recovery or download mode. In my experience whatever combination you go with while booting, the power button only needs to be held for the first 5 seconds or so of the combo button press/hold.
The other button, Vol+ or Vol- should constantly be held until desired mode begins to load.

louforgiveno said:
Timing will be the key. To help out, boot up as you have been, but as early into the boot cycle press and hold the Vol - and power button for up to 5 seconds (until phone manually shuts off) [it will actually reboot the phone])), then the instant it powers off and begins to power back on (try a few times to get used to the timing) press and hold the key combination for recovery or download mode. In my experience whatever combination you go with while booting, the power button only needs to be held for the first 5 seconds or so of the combo button press/hold.
The other button, Vol+ or Vol- should constantly be held until desired mode begins to load.
Click to expand...
Click to collapse
Thanks for your quick and detailed reply man, appreciate it.
Still trying, new cords, ports, the whole buffet. Will keep at it.
Major flag though - my PC doesn't recognise the phone anymore, checked the USB ports in Device Management and nothing comes up. I've tried different cords and ports to no avail.
I have a feeling that because the device doesn't think it's not plugged in - it doesn't boot into recovery.
Just another detail - the flash goes on just before the reboot. Does this signify anything?

rajalot said:
Thanks for your quick and detailed reply man, appreciate it.
Still trying, new cords, ports, the whole buffet. Will keep at it.
Major flag though - my PC doesn't recognise the phone anymore, checked the USB ports in Device Management and nothing comes up. I've tried different cords and ports to no avail.
I have a feeling that because the device doesn't think it's not plugged in - it doesn't boot into recovery.
Just another detail - the flash goes on just before the reboot. Does this signify anything?
Click to expand...
Click to collapse
I'm not familiar with any significance the flash may point to. You've probably already done this.....but be sure to reboot PC....
Have you tried booting to recovery yet?

Cannot boot into download mode

Hi everybody, yesterday I was playing with my old Galaxy A50 trying to install a custom rom unsuccessfully.
I repeated the procedure three times installing TWRP and then Havoc OS but every time I tried to reboot from TWRP to OS I was stuck at the warning screen saying that the phone bootloader was unlocked and booting into download mode to reflash TWRP was blocked as it showed "only official binaries can be installed" (yes I installed Samsung disabler but still).
Still I was able to get the phone into download mode and reinstall the stock firmware as it seemed to be the only way to install and boot TWRP.
But at 4th time repeating the process I got frustrated, shut down the computer and left the phone on the warning screen still connected to computer usb cable.
Then I got back and noticed the phone was off as the battery died.
Indeed the battery died, so I put the phone in charging and after it reached 100% I tried to boot into download mode again to reflash stock firmware.
But here's the strange thing, I cannot boot into download mode anymore as pressing vol up+vol down while connecting usb cable, shows the lightning charge logo for 5 secs and then reboots infinitely with the same pattern.
If I force reboot by pressing vol down+power it shows the Samsung logo with the warning below it, then skips to another screen with another warning suggesting to press power button to continue (which does nothing) and after a while reboots to samsung logo.
So it doesn't seem it is bricked, it looks more like a battery controller fault, so I tried to detach the battery flex from the board, hoping it would reset the controller but it's still the same.
Also I tried with the flex detached and still no download mode is possible.
Was the download mode somehow erased? (if it's even possible considering it's the motherboard firmware)
If you need photos, videos or even a call on zoom, Skype, webex I would be glad to show you

same i got the same problem i can't find nothing for this when i press volume up and down and put the otg cable its simply charges but it gets stuck on the logo image there's no way to fix this but the only way is to open the phone,change the emmc and put one from samsung,close the phone flash a custom rom and you are done.

If you can enter recovery, do it. As soon as your phone gets into it, select the power off variant and then try to enter the download mode.
It seems like you did not unlock the bootloader, did you?

The bootloader Is unlocked i can't enter in the recovery because the phone locks on charging logo and its fully charged but when i try without charger It doesn't start.