My M1 suddenly popped up a notification saying "system UI has stopped working" and then went on a reboot lap that eventually lead to a boot screen saying
E: couldn't load bitmap fill_ball (error -7)
Warning: Nofile_contexts
Supported API:3
The phone is only 2 weeks old and never rooted. I have never encountered anything like this before and am afraid to do something wrong without consulting others, please help. I have tried clearing the cache and updating to the latest firmware via the option "update from external storage" and yet these did not help solve the situation. From my research, I have learned that doing a factory restore does not give a 100% guaranteed fix so I do not know what to do anymore.
I am a complete amateur in fixing these things, can someone guide me through the process of how to save my phone?
Reflash
Hey, did you try reflashing the stock firmware?
Here's a link: https://forum.xda-developers.com/as...ow-to/guide-revert-to-stock-rom-lock-t3798420
Else, visit the service centre. Reflashing takes less than an hour.
Related
My internal memory was getting full and so I was trying to clean up some junk. Well, I must have deleted too much!!! After trying to reboot, I received error message "Could not do normal boot"and it goes into odin. I tried to use odin to flash it back to stock, but no luck. It appears like I need a bootloader in order to solve this issue. Any suggestions? Thank you so very much.
I replied to the other thread that you started about this.
Spring L720T "Spark" model Samsung S4 running 5.0.1 phone is rooted but running stock ROM.
This is wife's phone so I don't have every detail as she apparently didn't pay a ton of attention to what was going on.
Some sort of OTA update apparently came through and tried to install itself. It warned that there as not enough room to perform the install. She uninstalled a program, went back to the system update and hit 'try again'.
The next time she looked it had booted into recovery mode with the following errors:
Finding update package....
E:unknown volume for path [@cache/recovery/block.map]
E:Can't mount @/cache/recovery/block.map
E:invalid volume path...check recovery.fstab
It gave this message twice and then aborted installation. I didn't see that information until just now or I would have tried to find recovery.fstab already. As it is, I don't know where that file lives but I will go try to find it.
She rebooted the phone and now when it boots, it gives a "unfortunately, system ui has stopped error".
Because of that, Touchwiz doesn't seem to be working. Home button does nothing, the notification bar is gone, no swipe down, etc.
I tried rebooting.
I tried taking out SIM, sdcard, and battery, letting it sit for a minute, then reinstalling all three and rebooting - no luck.
I tried booting into recovery, clearing the cache partition and then rebooting - no change.
I decided I would install a new launcher and maybe that would fix it. I can't get a launcher to complete the installation process within the play store. It will download and get partway through installing and then just hang.
Any ideas about what we can do to fix the problem? Is there a touchwiz update somewhere that I can install to fix the issue maybe? Any other ideas?
Thanks in advance for your help!
Well first, questions regarding your device belong in the Sprint S4 forums. However, your question is easy enough to answer. As long as you can still get into download mode by pressing volume down, home, and power, you can install a firmware package. Take a look in the general forum here or in the Sprint forums. There should be instructions on how to flash the firmware.
DOH! I posted too quickly without paying attention. Thought I was in the wrong forum, sorry.
My wife is hoping to keep her current setup (folders, etc) so I was trying to avoid flashing, but if I can't figure anything else out I will certainly do that. I wonder what went wrong with the update and if this is an isolated issue.
Any way to move this thread to the appropriate forum?
Problem solved. I did a factory reset and all is well - though bloaty.
It's good that you got it solved. To move this thread from the International forums where it was originally posted, report your opening post on the thread to a moderator and ask them to move the thread to the Sprint forums.
Me too here. I will try factory reset.
FE is rebooting every minute after recent Dec. update. Cleared delvik cache and says "can't find /misc partition." from reading it seems clearing everything to reset will cause the phone not to start so am waiting. if some way not to lose everything I'll try that first.
Seems the only answers are:
1) ignore it, that error doesnt matter anymore. Some can. Except many wipe data and then can't restart anyway.
2) others say Samsung replaced their phones (or replaced the board) because unfixable due to some weird hardware-update Matrix electro-wedgie.
3) people tried to rebuild /misc and was a nightmare that didnt end with anything beside tears.
I was first thinking I could just re-do the last update and be all good like a normal update.. But that doesn't work I think tho not sure why. If so, how so?
Thank you, good sirs.
-Please respond as tho talking to your mom or a small child. Thanks
You can try flashing stock firmware in Odin.
Yes this post is correctly dated. I've had this device a LOOOONNNGGG time.
The device has been rooted since shortly after I bought it new years ago. I've had very few problems since... which is why it's never been replaced.
I believe I have the stock ROM, sorry it's been a while.
When I start the device it gets stuck at the splash screen with the sprint logo.
I can get the device to "download mode" but I don't know what to do once there and I'm not sure I can do anything from here.
I can get the device to "android system recovery."
I know I installed TWRP when I rooted and installed the rooted ROM but when I boot to recovery it doesn't go there.
I've wiped the "cache partition" but the problem remained. I'm not sure what else to do from here and still be able to salvage data.
I'm trying to salvage the data on the internal storage. I'm pretty sure I could successfully "wipe data/ factory reset" and get it to "function" again but that's not the priority. I'm going to replace it regardless of success or failure. Data recovery is the priority here. (pictures and videos of my young children as well as less important stuff like contacts.)
I have an old laptop with an old version of ubuntu I can use or a newer one with windows 7 to work with. I mention this in case it makes this easier to help?
Thank you very much if you try to take a stab at this or refer someone that might!
Update:
So I managed to install TWRP via Odin.
I booted to this recovery and my data partition appears to be empty?
When I try to back up I get the error message "unable to mount '/data'"
I tried doing a wipe, not one of the fancy extra options ones just the regular wipe and it failed.
Any guidance will be extremely appreciated.
Edit:
So I've come to the conclusion that the data isn't accessible because of encryption and my pass code. Is there any way to enter it via recovery and access this info?
Is anybody out there?
Edit 2:
I hope this helps someone someday. I haven't solved the problem but I think I'm making progress.
First I had an old version of TWRP. I installed the latest for my device and tried backing up again. I'm not sure but I think it's working. TWRP dosen't seem to need my password for the backup. I imagine I'll just need it to access the data later.
Edit 3:
No sooner did I save the last edit and my backup failed.
Process ended with error : 255
Hey there,
My friend downloaded and installed Color OS6 update. His phone got bricked. He has tried all the things but couldn't solve the issue yet. It's been more than a week. Can you please link me to any solutions.
Also, the official update to fix the issue, i.e., http://download.c.realme.com/osupdate/RMX1801EX_11_OTA_0210_all_YkJueYPOAFXQ.ozip isn't installing and displaying "Installation Failed" after waiting forever. Service Centre guys are saying that they will do it, but data will have to be wiped.
In order to fix the bootloop, data needs to be reformatted via the stock recovery, then only flash the latest OTA. Should work(at least for me).