I accidentally posted this in the wrong forum last night. Here we go again.
I've been having issues with losing my touch screen lately no matter what ROM I flash. So I decided to unroot the phone and then reroot it. Upon unrooting I can get to 1.5 but when I try to upgrade to 1.6 I get this error.
E:failure at line 2: assert file_contains("System:build.prop:, "ro.build.fingerprint=tmobile/kila/dream:1.5/crc1/150275:user/ota-rel-keys.release-keys") == "true" || file_contain("System:build.prop" , "ro.build.fingerprint=tmobile/kila/dream/trout:1installation aborted.
Can anyone tell me what this means? I'm wondering if whatever is throwing this error is causing my other problems. Once I start losing my touch screen within a short period of time everything else stops working. I can't even take or make calls without a force close of android.process.
Related
I've got a rooted Verizon Note 3.
Every day I get alerted to install the latest OTA update. Unfortunately, it downloads but fails during the install. When it starts back up, the update entry says:
Last attempt to Update Software:
update_SM-N900V_NC4_to_NK1
Result: Update failed, 402
Every day it asks me to update, every day it fails. I'd like to update if possible but do not know how to go about troubleshooting. Failing that, I'd like to stop the darned update from pestering me every single day.
Any advice?
I just found out that "Stuck in the Middle" means that the upgrade is failing. Another thread covers the same thing I'm experiencing. I've frozen SDM.apk using Titanium and will see how that goes.
http://forum.xda-developers.com/verizon-galaxy-note-3/help/stuck-middle-t3012569
Regards
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.
Hi i hope you can help me, I'm trying to put the stock e612f, I do all the steps of the KDZ and reaches the part of == FINISHED == and the phone reboots, but when loads, does not return to the stock, keeps the same.
I tried several times, KDZ finish well but the phone keeps the same, the stock is not installed.
I have to do an additional step? How can i fix this?
I have a galaxy note 4 sm-n910t on marshmallow. four days ago it started lagging and freezing suddenly and at times just powered down continuously at times it showed "mmc read failed" on boot put when i take the battery out and try again it boots up. i performed a factory reset but the problem continued and i even went further to flash with odin but the problem didnt go away.
After updating last year to 6.0.1 i see "dm-verity verification failed need to check drk first" at the bottom left corner of the screen when i boot into recovery. it didnt affect the phone i has been working perfectly until now. its not rooted.
I really need help my phone lags even when texting :crying:
The mmc_read fail is a known fault with the Note 4. It needs a new motherboard/logic board for a permanent fix. A temporary fix is to download Wake Lock by darken from the Play Store and use setting 4, PARTIAL_WAKE_LOCK. It won't fix it but you might get a bit more use out of it. Don't let it switch off or reboot though as you may have problems starting it up again.
Big Elf said:
The mmc_read fail is a known fault with the Note 4. It needs a new motherboard/logic board for a permanent fix. A temporary fix is to download Wake Lock by darken from the Play Store and use setting 4, PARTIAL_WAKE_LOCK. It won't fix it but you might get a bit more use out of it. Don't let it switch off or reboot though as you may have problems starting it up again.
Click to expand...
Click to collapse
Thanks it really helped :good:
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.