Hello,
About a month ago my fingerprint sensor suddenly stopped working(I was running full stock ROM). It was saying an error occurred try restart device. That obviously didn't help. I saw a post here on XDA that wiping cache of fingerprints app with titanium backup could help. So I rooted device, wiped cache and only thing I did was triggering KNOX(with rooting). Then I saw again here on forum that flashing with GS5's PIT file could help. It didn't. So, my warranty is void now and I don't know wait to do. If somebody here knows how to fix this because I am highly convinced this is software issue I would be very grateful.
Thanks in advance!!
If you're certain that youve already voided your warranty, which not all root methods do, you could attempt flashing a recovery so that you can take a nandroid backup. After youve taken a nandroid try reflashing the original firmware in odin. Completely flashing the original should fix that issue. If it is software related.
Related
I hava a Galaxy S4 GT-i9505 and yesterday i rooted it and installed CWM 5.X.X.X
but now it keeps randomly crashing, it happened while browsing, while using snapchat and watching photos but also while just watching home screen.
When it crashes it freezes for a moment and then shows samsung logo and after a while it is back up and shows my unlock screen wich i dont have to fill in my Pincode like i have to do when i reboot or boot my phone manualy.
I have updated CWM to 6.0.4.7 but still it is crashing
I am running stock 4.4.2 android only CWM and SuperSU
I have searched for a similair problem but couldnt find anything
Sir,
Please wait until mods will move this thread to the device specific forum for more relevant answers.
Stand by
Good luck
I also had such an issue. It happened to me only after installing viper4android on the stock rom.
Deleting the app didn't help.
You will probably have to re-flash the stock rom via Odin. Or change to a custom rom..
I did reroot it flashed stock rom still freezing and rebooting.
I just want to keep 4.4.2 wit root access.
Any other way than achieve this beside cwm with SuperSU?
You need to delete Knox. That's the reason you are experiencing reboots. Afer you root you have to delete Knox.
Get the Knox removal script from here and flash it:
http://forum.xda-developers.com/showthread.php?t=2507931
CWM is totally unrelated to your random reboots.
Thank I will try this tomorrow.
Although when I first booted my phone after rooting it asked something about disabling Knox.
Disabling and deleting are two different things
Good to hear that still got hope
I hope you did a full wipe before re-flashing stock rom, right?
Doing a dirty flash will not help you much.
Yes full whipe factory reset dalvik cache data files, all even formatted my SDcard
Lennyz1988 said:
You need to delete Knox. That's the reason you are experiencing reboots. Afer you root you have to delete Knox.
Get the Knox removal script from here and flash it:
http://forum.xda-developers.com/showthread.php?t=2507931
CWM is totally unrelated to your random reboots.
Click to expand...
Click to collapse
Done this now hoping that it fixes my problems thanks for sharing anyway:fingers-crossed:
(stupid "To prevent spam to the forums, new users must wait four minutes between posts. Sorry for the inconvenience!" message)
Hi all,
Some time ago i asked, and received, some support on these forums on how to properly carry out a nandroid backup... following the sound advice i got, i carried out my backup (using TWRP for the record, with all the options checked), and stored it away for a rainy day... said day came yesterday, when i messed up my system and rendered it instable (i tried to manually delete the dalvik cache directory in order to free up the 2,5GB of space it was taking)... since i knew there was i high chance of this ending in disaster, the last thing i did before the delete was carry out another nandroid, so i could easily return to where i had left off... how wrong i turned out to be
as soon as i the system became instable following my experiment of deleting the d. cache directory, i recovered the latest nandroid (i.e. the one i had made just hours before) and everything seemd to go smoothely until the first reboot... when the following happened:
- first reboot after recovery took ages, much like the first reboot following the flashing of a new rom... not the end of the world, but that was the first sign that all was not well
- the status bar disappeared, and there was no way of making it come back (i.e. nothing to do with the launcher, i typically use apex but i i tried switching to both nova and touchwiz which i also kept up to date but the stats bar was nowhere to be seen)
- even if not having a status bar with all the info on it is acceptable (which of course it isn't, but lets just say), the sytem became completely instable after 5minutes of operation... with each app taking turns to shutting down until i kept getting the message "system UI has closed" over and over, to the point that doing a reboot was challenging since i barely had the time to press on the screen between instances of this bloody error message appearing...
...i did of course try and return to my older nandroid backup, but... lo and behold... exactly same behaviour...
so now i have resorted to formatting the internal memory card and flashing a new rom and basically starting over... just what i hope the nandroid would spare me basically :/
question is: does this sort of error sound familiar to anyone? can someone give me a tip maybe on what i may have done wrong?
any opinion, tips& advice much appreciated
I have the exact same problem. It happens on TW Lollipop ROMs. Haven't found a fix. I'm using Philz Touch Recovery and the old no knox bootloader.
Anyone? I have researched this but cannot find any similar problems reported... it can't just be me and pavelcheto...
Maybe it a recovery fault. Faulty backup or faulty restore.
No problems with my older backups. I restored my KitKat TW backup, working fine. Restoring CM12 backups also works fine. I've looked for a new recovery, Philz is discontinued, CWM hasn't been updated for a year and I really don't like TWRP.
I use TWRP 2.8.3.0 and never have (and hopefully never will) encountered any issues with restoring backups.
Considering i recovered 2 separate backups for a total of 3 times (i tried recovering the first backup twice) i doubt the issue was with the recovery itself... however since pavelcheto had no issues with the kk recovery maybe it could be lollipop related?
Anyone successfully recovered a lollipop nandroid backup?
platypus78 said:
Considering i recovered 2 separate backups for a total of 3 times (i tried recovering the first backup twice) i doubt the issue was with the recovery itself... however since pavelcheto had no issues with the kk recovery maybe it could be lollipop related?
Anyone successfully recovered a lollipop nandroid backup?
Click to expand...
Click to collapse
I recovered my lollipop gpe backup a couple of times without a problem.
Data encryption may cause restoring problems.
I have restored CM12 backups (based on 5.0.2) serveral times, no problem there. I've had issues only with TouchWiz Lollipop ROMs, I have tried different custom roms, all get bugged at restore.
pavelcheto said:
I have tried different custom roms, all get bugged at restore.
Click to expand...
Click to collapse
Just to make sure I understand correctly : you mean all TW custom roms you've restored have had problems?
Wonder if anyone else has managed a bug-free restore of a 5.x TW?
Yes, but only on Lollipop. KitKat TW roms restore just fine. I am using Philz Touch Recovery. I have tried 3 different TW Lollipop roms and they all fail to restore properly. No wallpaper, black wallpaper and no status bar. And after a minute or two System UI starts crashing. If then I do factory reset from recovery and the rom starts normally (welcome guide and stuff) and works fine.
bumping this thread because i cant seem to find a solution for this anywhere.
TheAwesomeBit said:
bumping this thread because i cant seem to find a solution for this anywhere.
Click to expand...
Click to collapse
There's no solution for this as per comments above. TW LP is not restorable. You can flash a new lollipop ROM tho'
Sent from my GT-I9505
Hi guys, I am in DIRE need of your help and expertise.
A few days ago I did the update to Lollipop on my Canadian S4 on Rogers network (not rooted) and everything was fine until this morning when I restarted the phone. It now continues to restart after every 30-40 seconds of running. I barely have time to do anything after it boots up. I have cleared cache with recovery mode and no changes. Safe mode does the same thing so I am certain this must be some kind of Android/Samsung app incompatibility. But why only after a few days? All of my apps are up to date.
I found some similar threads but with no answers:
http://forum.xda-developers.com/galaxy-s4/help/s4-i9505-restarting-t3092871
http://forum.xda-developers.com/galaxy-s4/help/s4-random-reboots-okay-5-0-1-lollipop-t3097361
http://forum.xda-developers.com/galaxy-s4/help/s4-9505-stuck-bootloop-installing-t3100064
Please help!!! I do not want to do a factory reset as I want to save my data. I have read some online posts saying that this is due to Knox crashing or something along those lines? I'm probably not as tech-savvy as most users on this forum so please advise if there is a known fix for this!
I forget to add - I even replaced the battery to rule that out as a culprit. Still restarting the same way.
Hi, I have a similar problem but mine is worst because my S4 restarts after 4-5 seconds...
This is a video I've recorded, is that what happens to your phone?
I've found that the problem should be caused by some app. Your unique solution is to wipe data and reinstall the ROM you have... that's what I've done several times but after installing my apps(Google automatic restoring) the problem happens again.
So here I am instlling my apps one by one and restarting my phone each time to find which is the problematic one... In my case I belive it's Greenify, but I'm not sure. Do you have it installed?
^ Exactly. But it will be about 30-40 seconds later. I have been going in and disabling Google/Samsung apps one at a time as that's all the time I've got before it reboots. It can't be a 3rd party app because it still does it in Safe Mode. The only thing is apps like Knox can't be disabled without root access. That's why I'm thinking it might be the culprit. I may end up rooting it and trying to disable it that way. My other options is hopefully I can recover as much data as possible with TWRP and then do a factory reset...
I would appreciate any ideas and suggestions!
http://forum.xda-developers.com/galaxy-s4-att is the place to ask your questions as this was posted in the international S4 forum. You'll find more people there familiar with your device than us.
That said, have you attempted to flash the ROM again using Odin?
Strephon Alkhalikoi said:
http://forum.xda-developers.com/galaxy-s4-att is the place to ask your questions as this was posted in the international S4 forum. You'll find more people there familiar with your device than us.
That said, have you attempted to flash the ROM again using Odin?
Click to expand...
Click to collapse
Shoot, I didn't see that section. That would have been a more appropriate place to post this.
I have not tried that yet. Will flashing with Odin erase my app data and stored files?
Your media and documents on internal storage should be safe. Apps will be lost. But it might be moot anyway, as flashing the same firmware likely won't fix the issue. Unfortunately, it seems as if a factory reset is your best option to crack the bootloop. If you have anything on internal storage that you want to save, look into flashing a copy of TWRP recovery so you can access its file manager. You should be able to pull your data off that way.
Flashing the recovery should not trip Knox, though I recommend rooting anyway and installing a custom ROM, as custom ROMs don't have Knox.
Strephon Alkhalikoi said:
Flashing the recovery should not trip Knox, though I recommend rooting anyway and installing a custom ROM, as custom ROMs don't have Knox.
Click to expand...
Click to collapse
Pretty sure flashing a custom recovery will trip that knox warranty void flag. Unless you were talking about something else.
I think you're right about that. That's what I get for posting just before heading off to work. Nevertheless, I say "screw Knox". Root anyway.
I can't figure out if I do so any help appreciated.
Everything on my Note 4 works fine except lags and crashes, only thing that has managed to fix that is the Wake Lock App but obviously it's training the battery.
The other issue I had was Private Mode not enabling which still isn't, and also WIFI was not remembering passwords so I used BuildProp Editor to change that Securestorage.support to falst from true and that fixed that.
Was getting the DM-Verity Failure issue whilst on stock unrooted so rooted it and added TWRP to fix that issue.
IMEI & Baseband etc... all showing up perfectly fine too.
Can't figure this one out.
I'm now rooted (thinking this would solve the issue) and on stock.
Any ideas appreciated.
Thanks.
Sorry for the extremely delayed reply, if you haven't already figured it out you probably do have a corrupt EFS. I've been messing with a refurbed unit I got for my wife off and on for months and finally just manually formatted /efs via twrp and rebooted. The stock rom rebuilt things no problem and the lag is gone. I know there was a problem with EFS as logcat showed a *TON* of errors from the SecureStorage package. After formatting the errors are gone. I made several backups via twrp and manually via tar just in case.
Good morning.
After almost 3 years with no problems with a XT907, I have again an issue with it (this time, my father's one). Again, I come to you requesting help.
It all started with all apps crashing over and over. With an old XT907 I have for emergencies, the common fix method is flashing VZW_XT907_4.4.2-KDA20.62-15.1_1FF.xml.zip with RSD Lite v6.1.5 and all solved.
I tried that method with my father unit, and when it started again, all process were still crashing. I thought it was still nothing (just a harder issue), and tried flashing VZW_XT907_4.4.2-KDA20.62-15.1_CFC_1FF_SVC.xml.zip, just deleting all his data, to fix it.
When the process ended, it turned on and it had still the same problem. In this point, I got worried the /system and /data partitions got locked
I re-started, went to stock Recovery, and wiped system and cache. Then, went to Fastboot a third time and tried again flashing VZW_XT907_4.4.2-KDA20.62-15.1_CFC_1FF_SVC.xml.zip. Guess what? Still the same problem
The phone turns on, but ALL apps keep crashing over and over. I can't even take an screenshot, as it immediately reboots.
Someone know what happened with it? And... how to fix this issue?
To make things worse
Fastbook Locked
No Root
Last 4.4.2 stock ROM
by twrp try make Wipe Data Or Repair File System, if not done mybe your internal memory Currpted