Related
3rd thread, about 4th rom flashed
constant issues with builds. have gone from stock to:
cm 6.1.3 -apps crashing, random crash notices i.e "phone book has crashed force close" - "the process com.android.phone has stopped unexpectedly"
cm 7 - random reboots, opening browser caused power cycle, wifi issues, lag (thread posted, no solutions at the forefront)
currently on tripnraver pre release. now another issue. no signal what so ever.
original baseband on this xperia x10a is .55. it is suggested to use with bands 52 or 49.
loading either of these basebands. which ive done. doesn't seem to fix the no signal problem. the description states should be backwards compatible even if appropriate bb is not installed on device. yet no luck.
attempting to flash either baseband fails to resolve this problem. currently trying to flash back to stock and try another full reinstall and baseband flash in flashtool.
any ideas would be a great help. having to flash x number of times between roms is getting quite time consuming
thanks everyone.
if you want to stay on the miui rom, you can flash the baseband patch located here and stay on whatever baseband works best for you (I'm on .55 and find it fantastic), then when you load the rom, go to dev tools>bad behaviour>crash the system server.
http://forum.xda-developers.com/showthread.php?t=1011608
Otherwise, I would recommend wolfbreaks cm 6.1.3, as it is the most stable. You must have done something wrong during installation as I never had an issue with his roms.
The only issue I have ever had with any rom is MiUi and thats because I used the wrong baseband. You must be doing something wrong for you to be having problems
if you want, try this flash, it's trips miui pre-final with the baseband patch implemented.
http://www.multiupload.com/KCKE9K2WKN
worked with my .54 baseband
thanks so much for the links to the baseband patches. i remember coming across a thread that posted it but unfortunately forgot to book mark. so im definitely going to go ahead and try with the patch installed. hopefully all works well
each rom ive flashed has been done properly according to instructions. cache wiped, dalvik, and full reset as per menu options in xrecovery.
one way or another i experienced lag for the most part, and as mentioned some random crashes. never had reset on wolfs rom just error messages at times. trips rom worked excellent, smooth and quick. hopefully with the patch implemented everything will work flawlessly
thanks you guys
*Updated
Flashed over rom with baseband patch. signal working. everything running smooth.
except for when using camera zoom. zoom default displays 0x. as soon as the option is selected it spawns an immediate force close
any patches? or similar outcome for anyone else?
i will outline my steps below so everyones up to speed on how i performed this flash.
- flashed back stock in SEUS
- root with one click (success)
- installed busy box (market)
- installed xrecovery apk
- booted into xrec
1. full factory reset
2. wipe cache
3. wipe dalvik cache
4. wipe battery stats
5. install custom zip from sd card
6. selected trips rom with bb patch implemented
5. reboot
Camera zoom doesn't work in most ROMs yet and the lag you were experiencing was likely just the FW "settling" it can take a little bit and a couple reboots sometimes for the phone to calibrate itself properly.
Sent from my X10i using XDA Premium App
thanks cmoney. maybe ill try my luck with cm7. give it a few reboots and hope for the best. great rom. im really loving trips iphonesque style
clean smooth and quick. everythings working great. hoping the zoom may get fixed soon enough. only other inquiry i have with regards to this rom is the apps2sd.
this feature is essential to myself personally. and it is not working as ive noticed on this rom. ive read a thread with regards to a fix for the last release. i checked the settings for an enable option in case the feature requires being manually set as active but nothing listed. within sd settings state reads as unavailable. if anyone has an answer as to whether this fix will function with the current pre release. ill be going ahead with completeling the flash and reporting what i find back on this thread.
thanks again everyone
Try Wolfbreaks rom. It's very very stable for me. It has cam and everything upto date.
im going to flash back to wolfbreaks updated 6.1.3 unless anyone can point me in the direction of a fix for trips rom.
the smooth and fluid feel of trips rom was brilliant. i am hopeful someone has directions for an apps2sd fix as i have flashed the build twice and the same issue has occured.
thesoundofsilence said:
im going to flash back to wolfbreaks updated 6.1.3 unless anyone can point me in the direction of a fix for trips rom.
the smooth and fluid feel of trips rom was brilliant. i am hopeful someone has directions for an apps2sd fix as i have flashed the build twice and the same issue has occured.
Click to expand...
Click to collapse
works for me on trips newest....
i just downloaded the new version 1.0
this is ridiculous. without the baseband patch. crash system server. no signal
now apps to sd is saying "apps2sd is not supported on this device"
this is an xperia x10, so obviously there must be something wrong here.
can anyone elaborate on exactly what to do about this because im going to attempt to flash back the rom, flash the bb patch right after, reboot. i assume this will only solve my signal issue. but this apps to sd is getting extremely frustrating and i can not figure out why it is not showing an enabled status.
- Flashed 1.0 with baseband patch - network signal resolved.
- apps to sd is STILL not working. and i really dont know what to do about this. everything else on this rom is perfect. is there something im missing? i came across a patch for apps2sd fix but this was for a previous version. would it be needed here? is there a setting that must be enabled first in order to start apps to sd as a service.
- as mentioned previously within the main menu, under sd card settings. message states "apps2sd is not supported on device" and on previous build would display "apps2sd unavailable". its simply impossible that the phone doesn't support it. as with every other rom the feature has worked. froyo would support it. the question is how do i go about enabling said feature?
thesoundofsilence said:
i just downloaded the new version 1.0
this is ridiculous. without the baseband patch. crash system server. no signal
now apps to sd is saying "apps2sd is not supported on this device"
this is an xperia x10, so obviously there must be something wrong here.
can anyone elaborate on exactly what to do about this because im going to attempt to flash back the rom, flash the bb patch right after, reboot. i assume this will only solve my signal issue. but this apps to sd is getting extremely frustrating and i can not figure out why it is not showing an enabled status.
- Flashed 1.0 with baseband patch - network signal resolved.
- apps to sd is STILL not working. and i really dont know what to do about this. everything else on this rom is perfect. is there something im missing? i came across a patch for apps2sd fix but this was for a previous version. would it be needed here? is there a setting that must be enabled first in order to start apps to sd as a service.
- as mentioned previously within the main menu, under sd card settings. message states "apps2sd is not supported on device" and on previous build would display "apps2sd unavailable". its simply impossible that the phone doesn't support it. as with every other rom the feature has worked. froyo would support it. the question is how do i go about enabling said feature?
Click to expand...
Click to collapse
I dunno man, it works fine for me, but I copied data from my 0.3.2 xrecovery image, so that might be why. try flashing that apps2sd fix for 0.3.2, should work fine
damn it. i just found that thread. found the links to the fixes. so far ive tried miui32_a2sd_fix.zip. and flashed that over with xrec prior to reboot. which did nothing.
there are two more links so im going to try those two flashes as well and hope that one of them will do the trick. if its working when utilizing .32 patches then ideally the bloody thing would have to work here. thanks for the input though dtox. much appreciated
I don't know what else to suggest man
From the feedback I see in the miui thread, everyone else is reporting it working!
Did you factory wipe, wipe cache partition, and wipe dalvik cache before install? then flash the miui 1.0.zip, and flash immediately the baseband patch then reboot into the rom.
Remember not all apps allow apps2sd so use something like android system info, go into the applications tab click on one, click manage and then see if the option "move to sd" is highlighted. Like I said check a few though, not all apps can be moved
i just replied in the dev section lol but yes i have gone ahead and checked the applications menu. specifically downloaded a file i have moved to sd on a previous occasion from the market.
nothing
the "apps to sd" selection is completely greyed out. no matter what application i click on or download. i did a full wipe, full install, and selected the apps2sd fix immediately after rom and bbpatch flash, prior to rebooting. issue still remains.
we'll see i guess. thanks again dtox
thesoundofsilence said:
i just replied in the dev section lol but yes i have gone ahead and checked the applications menu. specifically downloaded a file i have moved to sd on a previous occasion from the market.
nothing
the "apps to sd" selection is completely greyed out. no matter what application i click on or download. i did a full wipe, full install, and selected the apps2sd fix immediately after rom and bbpatch flash, prior to rebooting. issue still remains.
we'll see i guess. thanks again dtox
Click to expand...
Click to collapse
Try it again but without the fix...
i did that to it doesnt work i get the same message displayed
i tried with fix and without. another thing to note is that the rom itself says it should work with a different baseband as it has elements of unified. (which it doesn't) i had to flash the bb patch to get signal.
im not sure whats up with this but until i figure it out for a certainty ive flashed back over to wolf breaks rom. hopefully something will surface and i can give trips rom another go.
thesoundofsilence said:
i did that to it doesnt work i get the same message displayed
i tried with fix and without. another thing to note is that the rom itself says it should work with a different baseband as it has elements of unified. (which it doesn't) i had to flash the bb patch to get signal.
im not sure whats up with this but until i figure it out for a certainty ive flashed back over to wolf breaks rom. hopefully something will surface and i can give trips rom another go.
Click to expand...
Click to collapse
No idea man, like I said it is fine for everyone else so I'm so no big development will arise that will make it function with your phone....
maybe it has something to do with 10a. i dont know. but the point is it shouldn't even be doing this regardless. hypothetically if its froyo and it has apps2sd built in. it should work. its not the way ive flashed. the phone supports it. so my only conclusion the rom must not be as compatible as stated. and from reading different posts about the prev builds sometimes the patches worked at other times they didnt. and also the fact that the rom is claimed to work without the need for a bbpatch. yet without the patch instaled phone caught no single. i guess certain unexplainable glitches can be bound to happen at times but any how ill give it one last go.
if nothing comes out of that then im giving up on that build because it seems relatively hopeless.
lol I'm using an x10a...
Still man you're the only person reporting this. Don't you find that strange? What baseband are you using anyhow?
May I have your attention please.
Greeting to all who may be concerned or able to fix camera failed issue on Samsung Galaxy S4 i9500 !!!
I know that there are other threads with similar topic, but I think we should recindle this issue as serious problem.
The story goes:
I bought slightly used S4 i9500 phone with no guarantee. It worked fine, was taking pictures and all. Splendid.
It was on some stock firmware. Some german version I think.
Then crappy and useles bloatware began to bother me. Just mountains of really crappy and uselles meaningless bloatware.
I wanted to remove that horses*it apps and therefore I rooted the phone flashing adam kernel and cofface cwm.
One lovely day i tried to take photo, camera opened with black window and showed camera failed notification with persistancy.
i flashed some newer stock firmware, it opened and was taking pictures till i tried some camera modes (action or something) and it froze with pink screen.
After that event, nothing was helpfull to fix this problem.
1. I flashed countles stock roms, nearly all available custom roms, new and old (think over 20 flashes).
2. Prior to flashing I did: Wiping dalvik, system, data, cache, preload, or full wipe, hard resets, wiping sdcard and external card.
3. Tried also nand erase (it took some time to revive phone afterwards).
4. Tried solutions like clear camera cache and data.
5. Tried turning off phone, taking battery out for some time, with full recharge,
6. Tried non stock camera apps. (e.g. camera fx, camera mx..)
7. Tried removing camera app by deleting it with titanium backup, or with root exploer - then installing it back to system apps with root explorer.
8. Tried switching sd cards- 8gb, 16, 32, 64 gb, no card, and tried settings without saving pics to sd card but internal storage.
9. Tried turning off gps, and location services
10. Tried limiting processes to 4 only.
11. Tried flashing with odin, or via cwm cofface or philz.
12. I opened phone with screwdriver to check for posible visible faults or something - all ok.
13. Flashed official firmware claimed to solve camera problems.
Maybe something more i did?- i cant remember, if i do i will notify about it.
And I ordered camera module from internet, will try to replace it - we will se what happens.
In the meantime, if someone, some wise one, genious or ordinary person, knows how to fix this persisting problem PLEASE HELP!
You will help me, and help others that have this problem.
Samsung officials, if you somehow should read this, take this into consideration. There are many eyes upon you. Provide solution for this.
Any one - SOS
FIXED IT.
Since no one cared enough to even try to help me with this problem I will not post the solution !
Said enough.
duxerica said:
FIXED IT.
Since no one cared enough to even try to help me with this problem I will not post the solution !
Said enough.
Click to expand...
Click to collapse
I too like you tried everything and found nothing. Camera takes forever to open. Hope you decide to share the solution.Knowledge should be shared.Don't be bitter about it.I'm sure if someone had a solution they would have posted it.
cheers.
duxerica said:
FIXED IT.
Since no one cared enough to even try to help me with this problem I will not post the solution !
Said enough.
Click to expand...
Click to collapse
Likewise, some people may have missed your post or nothing good to add, still I too would like to know what finally worked as I tried most of what you did.
Bests
M
If you have message "Camera failed"...
First of all try this: Open Camera app from the "Application manager" and do "Clear data", then restart the phone.
Second: Do a Factory reset (of course save your data!).
Third: Reinstall Android OS.
If this not help you, you have a hardware problem. You need to change the camera.
-------------------
Video tutorial:
http://youtu.be/3nzetqisty0
Earlier today I was mucking about and decided to play around with the fingerprint scanner for the first time. When I went in to settings and clicked the fingerprint manager, I received an error stating that the scanner is borked, and to reset my device to fix it. Rebooting did not fix the issue.
Soon I found another person with the same issue, who said that he was able to fix it by flashing stock NJ7 via Odin. After a bit of chatter we realized that neither he nor I had set up the fingerprint scanner before flashing a ROM. We basically booted the phone and went straight to rooting it, and flashing ROMs on it.
I can confirm that re-flashing the stock ROM via odin allowed me to set up the scanner successfully, and that the functionality has not been affected by any subsequent ROM flashing.
I do not understand the mechanism behind why this happens, it is just my experience. Perhaps there is some sort of validation that is run the first time you use the scanner, making sure you are running official firmware, and then setting a flag somewhere? How then would that flag be saved for all subsequent rom flashes? Hidden partition or some ****? Hardware flag? I dunno I don't get it, but I figured out how to fix it by golly. Hopefully this helps someone else.
If any others can confirm the same issue, we may want to add this as a step in the rooting/romming how-to threads, so that others don't run into the same issue.
One good thing is that when I flashed stock via odin, it didn't wipe my data. I was able to then flash TWRP and then Dynamic Kat again, keeping all of my settings the whole way through. Ended up not being as much of a hassle as I thought it was going to be :good:
Thank you for sharing this, I have to say in my case it is not working now i did get the phone rooted and then added jovys rom then did my setup the fingerprint scanner worked for me, then i installed dynamic rom and then the later update of same rom and then the fingerprint scanner is no longer working for me there is a new update for the rom i am going to flash and see if it works now as in a previous version the bloat from samsu g had been removed and with jovys rom being stock rooted it was still there, so i am wondering if it has to do with some of the bloat from Samsung and it being removed that breaks the fingerprint scanner, i will report after i flash the new version of dynamic.
santos.moreno3 said:
Thank you for sharing this, I have to say in my case it is not working now i did get the phone rooted and then added jovys rom then did my setup the fingerprint scanner worked for me, then i installed dynamic rom and then the later update of same rom and then the fingerprint scanner is no longer working for me there is a new update for the rom i am going to flash and see if it works now as in a previous version the bloat from samsu g had been removed and with jovys rom being stock rooted it was still there, so i am wondering if it has to do with some of the bloat from Samsung and it being removed that breaks the fingerprint scanner, i will report after i flash the new version of dynamic.
Click to expand...
Click to collapse
I first noticed the problem while I was on Dynamic Kat 1.1 and thought the same thing, that it was something to do with the Sammy apps, but it still didn't work after updating to DK 1.2. I've had it both working and non-working whilst running the same ROM (1.2,) and the only thing different between the two instances was the fact that I configured it while I was in stock in one instance.
This is important information. Hopefully the devs will be able to fix this asap. Thanks!!
Wow thank you BotsOne! I'm having the same issue. I'll try this in the morning. Before I rooted, I set up the fingerprint scanner and it worked fine the I switched back to swipe, then rooted. After rooting I installed Jovys rom and lo it hasn't worked since. Does the lock screen have to be set to fingerprint scanner at the time of flashing roms or can you set it up once and move on from that point forward? Thanks again!
android242 said:
Wow thank you BotsOne! I'm having the same issue. I'll try this in the morning. Before I rooted, I set up the fingerprint scanner and it worked fine the I switched back to swipe, then rooted. After rooting I installed Jovys rom and lo it hasn't worked since. Does the lock screen have to be set to fingerprint scanner at the time of flashing roms or can you set it up once and move on from that point forward? Thanks again!
Click to expand...
Click to collapse
Honestly I'm not sure. We need a few more people with the same error to get to the bottom of what's going on here. I could be way off with my assumption. We need a bit more info.
Cool I'll try tomorrow and report back..
BotsOne said:
Earlier today I was mucking about and decided to play around with the fingerprint scanner for the first time. When I went in to settings and clicked the fingerprint manager, I received an error stating that the scanner is borked, and to reset my device to fix it. Rebooting did not fix the issue.
Soon I found another person with the same issue, who said that he was able to fix it by flashing stock NJ7 via Odin. After a bit of chatter we realized that neither he nor I had set up the fingerprint scanner before flashing a ROM. We basically booted the phone and went straight to rooting it, and flashing ROMs on it.
I can confirm that re-flashing the stock ROM via odin allowed me to set up the scanner successfully, and that the functionality has not been affected by any subsequent ROM flashing.
I do not understand the mechanism behind why this happens, it is just my experience. Perhaps there is some sort of validation that is run the first time you use the scanner, making sure you are running official firmware, and then setting a flag somewhere? How then would that flag be saved for all subsequent rom flashes? Hidden partition or some ****? Hardware flag? I dunno I don't get it, but I figured out how to fix it by golly. Hopefully this helps someone else.
If any others can confirm the same issue, we may want to add this as a step in the rooting/romming how-to threads, so that others don't run into the same issue.
One good thing is that when I flashed stock via odin, it didn't wipe my data. I was able to then flash TWRP and then Dynamic Kat again, keeping all of my settings the whole way through. Ended up not being as much of a hassle as I thought it was going to be :good:
Click to expand...
Click to collapse
Yes, I am quoting the entire op...
Give me some more evidence of this and I will edit the Root & Recovery Guide immediately... I have seen conflicting posts on this matter too... Also, is not clear if private mode does continue to work after rooting or not... Can anyone confirm... (without flashing any roms... from original unrooted to rooted) Private mode... does work or not??? (Private mode is not suppose to work after rooting... but some say it does work???)
Nice post! Come on people... help...
Before you back up your rom, disable fingerprint scanner and delete saved fingerprints. If you don't and you go do your backup and ever plan on using the scanner again on that backup, it won't work. One of the guys thinks it has to do with the fingerprints being encrypted so when you restore, it can't decrypt it and locks you out.
I can confirm personally that disabling it before you do your backup then flashing a new rom then restoring your old backup, the fingerprint scanner will still work. Just have to set it up again. But that is a whole lot easier then flashing stock with odin again and starting over.
inphamous36 said:
Before you back up your rom, disable fingerprint scanner and delete saved fingerprints. If you don't and you go do your backup and ever plan on using the scanner again on that backup, it won't work. One of the guys thinks it has to do with the fingerprints being encrypted so when you restore, it can't decrypt it and locks you out.
I can confirm personally that disabling it before you do your backup then flashing a new rom then restoring your old backup, the fingerprint scanner will still work. Just have to set it up again. But that is a whole lot easier then flashing stock with odin again and starting over.
Click to expand...
Click to collapse
I think this may be an additional problem for flashers, but not necessarily the same one I am addressing. The reason I say this is because I hadn't configured the scanner at all previous to when I discovered that mine didn't work, the error completely prevents me from opening the fingerprint manager. I couldn't even enable the fingerprint function to begin with. Does that make sense?
Not trying to argue just trying to make sure we are on the same page =)
Just noticed my fingerprint scanner isn't working. Wtf lol
Sent from my SM-N910T using Tapatalk
i notice this problem as soon as i flashed first rom the only way o get it working again is flashing back to stock odin but no matter what i do as soon as i flash a rom I get a error message ? here the post another member had the same problem
http://forum.xda-developers.com/note-4-tmobile/help/fingerprint-sensor-error-t2918069
inphamous36 said:
Before you back up your rom, disable fingerprint scanner and delete saved fingerprints. If you don't and you go do your backup and ever plan on using the scanner again on that backup, it won't work. One of the guys thinks it has to do with the fingerprints being encrypted so when you restore, it can't decrypt it and locks you out.
I can confirm personally that disabling it before you do your backup then flashing a new rom then restoring your old backup, the fingerprint scanner will still work. Just have to set it up again. But that is a whole lot easier then flashing stock with odin again and starting over.
Click to expand...
Click to collapse
Thats not entirely accurate.
I set up my stock rom with the FP scanner...backed up in twrp as usual and i have flashed 4 roms since then and had to set it up gain each time and never had a problem. Ive never disabled it once.
sent from Canada via my Note 4, 3, 2 or One X+
So what exactly must be done to preserve fingerprint scanner functionality before flashing a custom rom?
force70 said:
Thats not entirely accurate.
I set up my stock rom with the FP scanner...backed up in twrp as usual and i have flashed 4 roms since then and had to set it up gain each time and never had a problem. Ive never disabled it once.
sent from Canada via my Note 4, 3, 2 or One X+
Click to expand...
Click to collapse
Have you tried restoring a backup and using the scanner? That's when it breaks. I can flash roms fine without having to disable it, but it didn't work after I restored a rom that had it enabled. Locked out of it
JawjaBill said:
So what exactly must be done to preserve fingerprint scanner functionality before flashing a custom rom?
Click to expand...
Click to collapse
I can tell you my history. I setup the fingerprint scanner right away before flashing anything as it is a must have feature for me. Later, I flashed a couple different ROM's and never had an issue. Just had to setup the fingerprint again. So my guess is if you set it up before flashing any ROM, you should be good. At least I was. I haven't had to disable before flashing or anything like that.
COCODRILO45 said:
i notice this problem as soon as i flashed first rom the only way o get it working again is flashing back to stock odin but no matter what i do as soon as i flash a rom I get a error message ? here the post another member had the same problem
http://forum.xda-developers.com/note-4-tmobile/help/fingerprint-sensor-error-t2918069
Click to expand...
Click to collapse
force70 said:
Thats not entirely accurate.
I set up my stock rom with the FP scanner...backed up in twrp as usual and i have flashed 4 roms since then and had to set it up gain each time and never had a problem. Ive never disabled it once.
sent from Canada via my Note 4, 3, 2 or One X+
Click to expand...
Click to collapse
JawjaBill said:
So what exactly must be done to preserve fingerprint scanner functionality before flashing a custom rom?
Click to expand...
Click to collapse
inphamous36 said:
Have you tried restoring a backup and using the scanner? That's when it breaks. I can flash roms fine without having to disable it, but it didn't work after I restored a rom that had it enabled. Locked out of it
Click to expand...
Click to collapse
keitht said:
I can tell you my history. I setup the fingerprint scanner right away before flashing anything as it is a must have feature for me. Later, I flashed a couple different ROM's and never had an issue. Just had to setup the fingerprint again. So my guess is if you set it up before flashing any ROM, you should be good. At least I was. I haven't had to disable before flashing or anything like that.
Click to expand...
Click to collapse
And... We ALL agree that Private Mode is Not working...? Right... No Private Mode since rooting... Right? There is absolutely nobody with Private Mode still working after rooting...
TEKHD said:
And... We ALL agree that Private Mode is Not working...? Right... No Private Mode since rooting... Right? There is absolutely nobody with Private Mode still working after rooting...
Click to expand...
Click to collapse
I think once you root the KNOX counter gets tripped preventing private mode.
keitht said:
I think once you root the KNOX counter gets tripped preventing private mode.
Click to expand...
Click to collapse
Yeap I know... but there is this:
http://forum.xda-developers.com/galaxy-s5/development/mod-enable-private-mode-knox-0x1-t2904723
That almost nobody seems to know... It's actually possible to regain Private Mode after a tripped Knox... (Not impossible)
TEKHD said:
And... We ALL agree that Private Mode is Not working...? Right... No Private Mode since rooting... Right? There is absolutely nobody with Private Mode still working after rooting...
Click to expand...
Click to collapse
Well now....never tried it but just did and its working for me. Rooted, jovy23 deodexed stock, twrp.
The day i got my phone i odin'd update then installed twrp, then wiped everything but int & ext sdcard, rebooted to recovery, wiped again then flashed the deodexed stock rom.....just tested fingerprint unlock last night for the first time, no problems and just now tested private mode and again that works for me.
keitht said:
I think once you root the KNOX counter gets tripped preventing private mode.
Click to expand...
Click to collapse
So I've been searching all the internet regarding my problem and found none to have my problem.
I was using popwiz rom and after a while my fingerprint sensor stopped working with the error "An error has occureed with the fingerprint sensor. If this message appears repeatedly, restart your device."
Because I needed my G900FQ, I ignored the issue for a while. Found S7 insanity which has a fingerprint bug and forgot about the problem.
Yesterday wanted to check out official MM for my S5, and had to reflash stock lollipop. Then I remembered my fingerprint problem so I tried to set it up. I kept getting that nasty error, tried deleting cache, tried deleting data with Titanium. Reflashed stock 2 times again, nothing worked. Until I was ready to give up and go to bed. Then it suddenly started working. Managed to set it up and activate fingerprint unlock.
Now is the bummer!
I CAN UNLOCK with fingerprint if waiting about 3 seconds after turning screen on.
I CANNOT ADD FINGER through settings, I get the nasty error message.
Tried to enter factory tests and under NormalScan button says Version 0.0.0.0 and in SensorInfo says Ready and stays that way.
I tried to enter factory tests very fast after unlocking with fingerprint and I got, only once and for a brief moment, the right Version and SensorInfo, and Normal Scan showed data and graph.
Now I will try to install official MM firmware with Odin.
Anyone has any ideas to what the cause may be ? And maybe a solution ?
Thanks in advance
L.E. I installed official MM firmware and now fingerprint sensor works when unlocking and adding fingers, but when I try to unlock my phone while it is connected to a power source I get the nasty error message again and prompts me for my backup password. Any advice would be deeply appreciated.
Flash a stock ROM and factory reset?
It seems you did not read the whole thread before suggesting me this...
I did that many times. Lollipop and MM official stock... Its like the sensor is not responding in some situations , but in other situations it does. And this seems to be pretty random..
*Detection* said:
Flash a stock ROM and factory reset?
Click to expand...
Click to collapse
laurent.siku said:
It seems you did not read the whole thread before suggesting me this...
I did that many times. Lollipop and MM official stock... Its like the sensor is not responding in some situations , but in other situations it does. And this seems to be pretty random..
Click to expand...
Click to collapse
It seems you don't even know what you typed, nowhere in your OP did you mention factory resetting and then flashing a stock ROM
Only that you flashed stock ROMs, flashing stock ROMs does nothing to reset anything and will leave behind bugs from the previous ROM if the issue is with an app / data etc
Before getting clever, read what you type
It's obvious that by flashing a stock rom over a custom one will leave bugs. Did full wipe (system, data, cache&dalvik, even phone internal sd) before flashing stock, every time. Thanks anyway..
*Detection* said:
It seems you don't even know what you typed, nowhere in your OP did you mention factory resetting and then flashing a stock ROM
Only that you flashed stock ROMs, flashing stock ROMs does nothing to reset anything and will leave behind bugs from the previous ROM if the issue is with an app / data etc
Before getting clever, read what you type
Click to expand...
Click to collapse
Well maybe next time add that fairly important info to your main post, instead of hoping everyone is psychic, and then throwing a hissy fit when they suggest something you have not stated you already tried.
I have followed the guide to flash the unlocked firmware and root my S7 Edge (http://forum.xda-developers.com/ver...de-flashing-sm-935u-firmware-verizon-t3415145) and all has been working well this weekend. This morning my phone gives me a persistent popup notification about a service provider update and "my device will restart to configure features supported by new sim card." The only option is to press ok and allow it to reboot. I cannot use my phone while this notification is active, and I am unable to kill it in any way. When the phone reboots to recovery, the configuration fails with "dm-verity verification failed". I then reboot system or power off and the endless cycle continues.
Has this happened to anyone else, has anyone figured out a way around this? I think I can reflash the firmware and start over from scratch, but this is of course not ideal.
Thank you for any help you may provide.
I wasn't getting any notifications however i did have some strange behavior going on and rebooted only to get the dm-verity verification failed and was no longer able to boot it would just sit at the Samsung splash screen I then had to factory reset re-post and re-setup everything, hopefully your experience won't need that since you are still able to boot!
Sent from my SM-G935U using Tapatalk
Thank you for the response, it's always nice to know someone has had similar problems. Looks like I will have to try reflashing the firmware. After your re-setup, did you do anything to prevent the issue from reoccurring?
Everything is again in working order. If anyone finds this and has the same problem, after flashing the Verizon fixes the phone is identified (in the about device setting) as the SM-G935V version again and is set to download updates automatically. I unchecked this option and I hope this should prevent it from happening again.
Not really wasn't sure exactly what happened the first time but thankfully (knock on wood) ??? it hasn't happened again.
Sent from my SM-G935V using Tapatalk
mine did it too. had to reinstall the whole thing.
drmatthews1 said:
Has this happened to anyone else, has anyone figured out a way around this? I think I can reflash the firmware and start over from scratch, but this is of course not ideal.
Thank you for any help you may provide.
Click to expand...
Click to collapse
shawnten said:
mine did it too. had to reinstall the whole thing.
Click to expand...
Click to collapse
I encountered this issue today and found a solution:
http://forum.xda-developers.com/galaxy-s7/help/whats-package-service-provider-update-t3425169
This happens when you install the xPosed module xTouchWiz. Generally it's perfectly fine to use. HOWEVER DO NOT CHECK THE DISABLE DVFS BOX! This is what causes this!
Dameon87 said:
This happens when you install the xPosed module xTouchWiz. Generally it's perfectly fine to use. HOWEVER DO NOT CHECK THE DISABLE DVFS BOX! This is what causes this!
Click to expand...
Click to collapse
Going to have to disagree with you there, I have had DVFS disabled since I've rooted and have never seen this issue. I should say though that I'm on the international firmware, so maybe it's something with the Verizon firmware?
thedrizzle said:
Going to have to disagree with you there, I have had DVFS disabled since I've rooted and have never seen this issue. I should say though that I'm on the international firmware, so maybe it's something with the Verizon firmware?
Click to expand...
Click to collapse
This has been my experience, as well as a few others. I'm not 100% sure it's that setting in particular, but I am 100% sure that it is caused by a setting in xTouchWiz. I had the issue once before, and it was a clean install save for xTouchwiz and me running through all the options. Since then, I've limited the choices in xTouchwiz and have not experienced the issue since. When I have some time I'll run through it and see if I can replicate the behavior again, since I'm working on a ROM.
There is a simple fix...
I agree, XtouchWiz drops a bomb when installed and it will cripple your phone. I never played with DVFS, I personally though it was the disable TIMA that set it off. An easy fix for anyone who stumbled on this. Power off your phone, remove the sim card, power up your phone, freeze a service called AutoPreconfig, power down and insert sim, good to go.
More info http://forum.xda-developers.com/gal...ge-service-provider-update-t3425169?nocache=1
Shout out to Wired4Fun for this easy fix.