Database Users

Wondering if the leaked ROM is really final...

Hi all,
it has been now nearly two weeks since the rom update leaked, and still so sign of an official update on htc website.
I'm wondering if this was really the final rom version, if so i don't know why htc would wait another two weeks after the leak.
I heard that somebody got that rom from an ftp server which is used by htc to upload data before it gets released. In this case two weeks seems also way too long for a deployment.
Are there any signs of the official release? I'm curious to see whether there are any last minute changes done.

well it could do with both orange and tmobile (in the uk) need to add there custom rubbish to there phones?

I read about major improvements in speed.
BUT - I also read about weather DB issues, WiFi issues, a.o problems.
So, I am definitely going to stay put, until an official release.
I am not going to waste time on reinstalling software etc, by flashing something "maybe-this-is-a-rom-very-close-to-the-final-one"!

yeah of course the carrier updates will take more time, but im talking about the htc update for unbranded devices.
since i made the ruu update i can confirm speed updates (but not huge difference), and i can confirm that more often the browser seems to have issues when going online via wlan. connection is there, signal is there, but the browser cant open pages.
and my device actually freezed two times, i couldnt make softreset and had to take the battery out. annoying.
but overall im satisfied with the performance optimization, still i will make another update as soon as the official rom is out..
and another minor thing: updating weather information manually will result in three updates. the app will update the weather data three times in a row, even though you only pressed update once,

I've had none of those problems, just checked the weather and it seems to update just once. I did have to pull the battery a couple of times BEFORE installing this new ROM when my phone totally locked though.

two weeks?? that's wrong.
The user who uploaded it, __htc__, leaked 2.73 on the 3rd of September....5 days ago.
they release to the ftp, this allows the repair centres, factory and call centres to get it, and then they release it on the website.
yes it is the final version.
if you want it, download it now, or dont. it's up to you, but yes this is the final release and it will be up soon.

rom t-mobile
@rhedgehog hi mate this might be silly but will this update work on locked t-mobile or willi have to root said device?
ps dont slap me to hard if its been asked before lol

rhedgehog said:
two weeks?? that's wrong.
The user who uploaded it, __htc__, leaked 2.73 on the 3rd of September....5 days ago.
they release to the ftp, this allows the repair centres, factory and call centres to get it, and then they release it on the website.
yes it is the final version.
if you want it, download it now, or dont. it's up to you, but yes this is the final release and it will be up soon.
Click to expand...
Click to collapse
yeah two weeks was maybe too much. I was hoping this is not final since i have some new issues since i made the ruu update:
- peep widget updates only every 30th try. I'm trying to update the tweets and it doesn't work for about 20 times, and then somehow it works after many more tries. When i open peep app i get an error message that the service is not reachable.
- wifi has problems. many times it seems the connection is dead, when technically everything is ok.
- freezes (but i installed about 40 apps, maybe this was too much...)
- keyboard has sometimes lags. i never had ANY lags inputting text before the update.
- more force closes by 3rd party apps.
- touchflo force closes seem to occur more often also (but i had them before too so this might be the same).
- freezes when the device is in sleep mode. I was at a meeting, not doin anything with the device. Then i wanted to check the time and the display didn't power on. So the device freezed during some background process by android or any 3rd party app. I never had this problem before the update.
the good:
- yes its faster (homescreens)
- even the contacts list has LESS stutter, but stutter is still there. IPHONE 3gs is way ahead in this regard. i don't know why other lists on android are completely fluid while the contacts app list is not fluid.
- battery seems to last longer
overall the first impression was VERY good, but is somehow stained by the problems that surface after some usage time...i'm not 100% sure if the speed update was worth it...waiting for android 1.6 update, maybe this sorts some stuff out..

I'm using Modacos 2.0 rom, and I've not encountered a single one of the issues you are reporting here.
Did you wipe before installing the RUU version? If not, I suggest you give it a try. Alternatively, wipe and install Modaco.
Regards,
Dave

locutus-of-borg said:
@rhedgehog hi mate this might be silly but will this update work on locked t-mobile or willi have to root said device?
ps dont slap me to hard if its been asked before lol
Click to expand...
Click to collapse
the RUU update won't work on a branded device. You need root to install the new rom in this case.

foxmeister said:
I'm using Modacos 2.0 rom, and I've not encountered a single one of the issues you are reporting here.
Did you wipe before installing the RUU version? If not, I suggest you give it a try. Alternatively, wipe and install Modaco.
Regards,
Dave
Click to expand...
Click to collapse
hmm i didn't do a wipe. How can you wipe the unrooted phone manually? i thought the RUU update will wipe the phone. It explicitly says so when updating the device that all data is lost. to me this means: your phone will be wiped...

Shahpur.Azizpour said:
hmm i didn't do a wipe. How can you wipe the unrooted phone manually? i thought the RUU update will wipe the phone. It explicitly says so when updating the device that all data is lost. to me this means: your phone will be wiped...
Click to expand...
Click to collapse
Well, Menu->Security->Factory Data Reset should do the job. To be honest though, I'd be more inclined to trust the "standard" Android way of updating your ROM than the HTC RUU process, because, as far as I'm aware, this'll be their first RUU for an Android device.
Regards,
Dave

Interestingly, the second poster here, http://forum.xda-developers.com/showthread.php?t=557628 , indicates that they had a problem with the factory data reset, but a recovery image wipe fixed it. I wonder if this related to your issues?
Even if you don't want to flash the modified recovery image permanently to your phone, you could boot it using fast boot and then wipe.
Regards,
Dave

how does it work? how can i restore a revocery image? isn't this an issue with the latest RUU update, that flashing recovery rom is not possible anymore or am i mixing things up here?

Steps 1 to 5 in this link, http://forum.xda-developers.com/showpost.php?p=4257045 , tell you what you need to do to boot the modified recovery image. Note that this doesn't flash anything to your phone - it just boots off the image you've supplied. You can permanently flash the recovery image later if you wish, but since you took the RUU root, I guess you don't want to put anything "unofficial" on your phone.
I've no idea if you having RUU'd already will prevent this, and I'm not going to RUU my phone to find out, but I doubt you would be stopped booting using fastboot.
Regards,
Dave

okay, thanks for the info!
Modaco wrote on a thread that doing the RUU update will make it nearly impossible to flash a modified recovery image.
I'm going to work with my current setup for some more days. If i see the mentioned problem reoccuring more often, i will proceed with the steps in your post.
or maybe we will see some changes (if not to the rom itself maybe at least the RUU will get an update) with the official rom update.
bye
shahpur

Just searched and you are right, you can't boot the recovery image if you have the new HBOOT from the RUU. However, the situation is not irreversible!
http://android.modaco.com/content/htc-hero-hero-modaco-com/292396/if-you-flashed-the-2-73-ruu-and-got-the-new-hboot/
Regards,
Dave

got an email from HTC yesterday:
"Thank you for contacting our Customer Support Center. We are dedicated to providing you with the best quality service and answering all of your questions and concerns.
You recently wrote us about an issue that you have encountered with your HTC device.
This update should be available later on this week. Keep an eye on our website.

sorry, was busy working, but it seems you;ve got the answers...
i;ve not had any problems that you have had either with those apps. mine is so much better it's ridiculous. but then i wiped first and again afterwards just to make sure.

Lars8000 said:
got an email from HTC yesterday:
"Thank you for contacting our Customer Support Center. We are dedicated to providing you with the best quality service and answering all of your questions and concerns.
You recently wrote us about an issue that you have encountered with your HTC device.
This update should be available later on this week. Keep an eye on our website.
Click to expand...
Click to collapse
Wow cant wait for tht, but 2bh I wud like T-mob to release their update as well at the same time as I am getting the G2 Touch on friday.

Accelerometer not working

Hi all, I was wondering if you could help with an annoying issue I'm having.
I made a big mistake by updating to an ICS Rom, it worked fine apart from the accelerometer which stopped 100%. I did a backup, but system crashed and that's the end of that backup
1: I've since downgraded to Honey Comb Acer_A500_7.14.14_COM_GEN1, but Accelerometer still won't work, I don't know why, is there some fix or file to replace or anything like that.
2: Second question, because I updated to ICS the boot loader got updated also, is there a way to revert the boot loader back to the original so the end product would be a 100% original
This is a 16GB UK version of the A500, so any help would really be grateful. Even if I can get both the boot loader and OS to original I can then send it off to Acer for repair.
Kindest Regards to all
Garret

Man, I don't have an Acer iconia, but I have a Samsung galaxy player 5.0 and I just experienced the same issue after trying an ICS ROM.
When I searched for a way to solve my problem, I've seen many many users (increasingly, indeed) with the same kind of problem. It's hard to think that so many users are having accelerometer hardware fail. I believe it's not physical problem, mostly because this kind of issue happens after ppl try modding their phones/tabs or changing roms. I've seen some users talking about removing a sensorfile yamaha.cfg and trying to reboot the device. That didn't solve my problem, or executing:
"sensorcalibutil_yamaha"
It is under /system/bin/, you can see that with root explore.
Unfortunately, didn't work for me. Hope it works for you.
Best regards.

Thanks for your reply, I found a way of down grading the bootloader and OS to 3.0.2 which fixed it, then updated the odds to the latest and back working 100%.

Hello, same issue for me, accelerometer doesn't work anymore! I had yesterday the official ICS fota. Is there a patch somewhere for this problem?

after official Acer ICS update - Accelerometer quit?
My A500 pad just quit doing auto-rotate just about 30 mins after I applied the "official" ICS update to my device. I haven't done anything different, I did lock the pad into portrait to read some stuff, but unlocked it (manual switch) and it was fine then all of a sudden - it stopped rotating between portrait and landscape. The switch now has no effect on it. Of course there's not a setting to change the rotation either. Argh? I was so excited to get ICS - not this goofs on me? I see quite a lot of posts about people who experience this from hacking around on their tablet or phone - I haven't hacked on this one at all - its the "official" stuff... Reset didn't help.

bthorsberg said:
My A500 pad just quit doing auto-rotate just about 30 mins after I applied the "official" ICS update to my device. I haven't done anything different, I did lock the pad into portrait to read some stuff, but unlocked it (manual switch) and it was fine then all of a sudden - it stopped rotating between portrait and landscape. The switch now has no effect on it. Of course there's not a setting to change the rotation either. Argh? I was so excited to get ICS - not this goofs on me? I see quite a lot of posts about people who experience this from hacking around on their tablet or phone - I haven't hacked on this one at all - its the "official" stuff... Reset didn't help.
Click to expand...
Click to collapse
This is the same issue I have on the leak version.
Sent from my PC36100 using XDA

gbyrne2011 said:
Thanks for your reply, I found a way of down grading the bootloader and OS to 3.0.2 which fixed it, then updated the odds to the latest and back working 100%.
Click to expand...
Click to collapse
I need to do the exact same thing. Could you please let me know what you did to start all over and get all the OTAs?
Thanks!

One could conjecture that if the accelerometer is stuffed, so would the orientation detection be.
Cause and effect?
Z.
Sent from my A501 using Tapatalk 2

Same here but a reboot cured it.

anyone find a fix for this ? im on the official with no root ics update and mine has also stopped auto rotating.

What did you use to do the downgrade back to 3.0.2?

gr8buddha said:
anyone find a fix for this ? im on the official with no root ics update and mine has also stopped auto rotating.
Click to expand...
Click to collapse
The only solution I found so far is keepin rebooting, eventually at some point accelerometer starts to work.
Best regards.
Sent from my GT-I9000 using XDA

If any off you had a leak and altered boot loader prior to install, it may have caused that. You should have had a 2 step optimizing process in the update, when I tested it on a leaked/flashed back version the bootloader was wrogn and that issue resulted. The stock had no issue and went through the full hardware optimizing process.
Also you shoudl have applied the market place update first, it has a pre fix to prepare it for patching.

Hey guys, i also have the same issue with accelerometer. I downgraded the a500 to Honeycomb and it fixed now.
I followed this guide: http://forum.xda-developers.com/showthread.php?t=1516012

Rollback OS + Bootloader back to Rooted HC 3.2.1
Use this to Rollback OS + Bootloader back to Rooted HC 3.2.1
WARNING EXTREMELY DANGEROUS | YMMV | WARNING EXTREMELY DANGEROUS
http://forum.xda-developers.com/showthread.php?t=1516012
WARNING EXTREMELY DANGEROUS | YMMV | WARNING EXTREMELY DANGEROUS

the guides to rollback posted above can be used on an official pad , with no hack or root stuffs ?

No, it rolls you back to rooted 3.2.1. with stock bootloader. Once ur back, you can load your official 3.2 rom on an SD, use Pwr + Volume down to update to it. Then OTA to ICS.
Just saw a guy posted a system of methods to completely wipe all the system files (not just most) and clean install ICS which supposedly fixes the accelerometer problem.

Accelerometer / ICS
I sent my tab back to Acer for repair, they say they replaced the "motherboard" and it did work fine on stock ICS as returned for a while. Periodically it would stick in orientation and not auto-rotate, but a power cycle with a few minutes in between seemed to always bring it back ok. NOW - nothing I do brings it back - its working the very same way it was when it originally experienced this issue. I don't want to send this slab back to Acer every couple of months and deal with setting it back up when they ship it to me a week or so later. This is rediculous or am I just being picky?
Anyhow - How bout a reference or link for the info on downgrading, wiping ICS and re-installing from scratch as mentioned above? That would be helpful if I knew where to look.
UPDATE: This morning, based on another post about finding errors in the bootlog, I downloaded the bootlog capture app, ran it, and poof - the auto-rotate function came back to life - like magic. I'm sure it was NOT the app, but rather the fact that I had powered down the unit and let it sit all night long without touching it or powering it on/off, etc. so at least for now, I won't be sending it back to Acer for Warranty repair (AGAIN). BUT I might be listing it rather quickly on ebay and shopping for another tab that doesn't have this issue....

I have had this issue and normally a power cycle fixes it. I did have one time where it did not but I found an article that said to do a hard reset. You do this with a paper clip pushed into the very small hole. I did not lose any data.
Marc
Sent from my A500 using xda app-developers app

take a look at this. It work for me.
http://androidforums.com/acer-iconi...veral-a500-ics-related-symptoms-problems.html........
delete the last dots.

[Q] Buttons and bottom half of screen unresponsive.

After the update to 4.4.2 my Galaxy Note 3(unrooted), the buttons(home, power and volume not soft keys) and the bottom half of the screen are sometimes unresponsive. It starts functioning again either after a quick lock and unlock or automatically after a few seconds. Is this a bug in the new update or a problem with the digitizer? I have tried resetting the phone a couple of times. Can someone help me?

jake262 said:
After the update to 4.4.2 my Galaxy Note 3(unrooted), the buttons(home, power and volume not soft keys) and the bottom half of the screen are sometimes unresponsive. It starts functioning again either after a quick lock and unlock or automatically after a few seconds. Is this a bug in the new update or a problem with the digitizer? I have tried resetting the phone a couple of times. Can someone help me?
Click to expand...
Click to collapse
factory reset won't remove bugs.
cause u didn't have this problem in previous firmware it s not because of hardware.
so try flash compatible stock rom from another region.
if problem remains take it to official service.
:good:

x102x96x said:
factory reset won't remove bugs.
cause u didn't have this problem in previous firmware it s not because of hardware.
so try flash compatible stock rom from another region.
if problem remains take it to official service.
:good:
Click to expand...
Click to collapse
It was an official update so short of rooting it and flashing a new firmware i don't see any other options.

jake262 said:
It was an official update so short of rooting it and flashing a new firmware i don't see any other options.
Click to expand...
Click to collapse
rooting is not necessary for flashing stock rom.

I'm having the same problems. Screen locks up often when I'm browsing in Chrome. For Gods sake this has 3gb of RAM!!!!!
Sent from my Nexus 7 using Tapatalk

x102x96x said:
factory reset won't remove bugs.
cause u didn't have this problem in previous firmware it s not because of hardware.
so try flash compatible stock rom from another region.
if problem remains take it to official service.
:good:
Click to expand...
Click to collapse
ok so i flashed a stock kitkat firnware. the problem is still there.

jake262 said:
ok so i flashed a stock kitkat firnware. the problem is still there.
Click to expand...
Click to collapse
flashed original rom via odin 3.09. Them hard reset. I have the same problem with screen. Is software problem.
Sorry for my bad English.

jake262 said:
After the update to 4.4.2 my Galaxy Note 3(unrooted), the buttons(home, power and volume not soft keys) and the bottom half of the screen are sometimes unresponsive. It starts functioning again either after a quick lock and unlock or automatically after a few seconds. Is this a bug in the new update or a problem with the digitizer? I have tried resetting the phone a couple of times. Can someone help me?
Click to expand...
Click to collapse
While phone works just pull out the battery and also don't use cover. I think its just about samsungs politics. ..
Sorry for my English

Same issue
jake262 said:
After the update to 4.4.2 my Galaxy Note 3(unrooted), the buttons(home, power and volume not soft keys) and the bottom half of the screen are sometimes unresponsive. It starts functioning again either after a quick lock and unlock or automatically after a few seconds. Is this a bug in the new update or a problem with the digitizer? I have tried resetting the phone a couple of times. Can someone help me?
Click to expand...
Click to collapse
I also have the exact same problem... I already did the factory reset but no luck. I increased the sensitivity but still happens...Can anyone help us? or it is caused by the recent upgrade of OS to kitkat version... Thanks.

GOOD NEWS!
I have been having this issue as well. Lots of research on the net has provided me with no real solutions. I think there is something missing in this update. I do not know what it is im not that smart but something is wrong across the board.
I have done a master reset back to factory and within minutes of the set up it started lagging/ not responding again. Figured i would give it a few days and well nothing changed so I contacted T-mobile and spoke with Tech Support located in Texas and he concluded that it is an SD card. He says that the SD card was on the phone prior to the update and is causing the issue since its old. WTF! I told him that the processor, ram, HDD, CPU are all considered old now. Personally I think its a stupid response.
I am going to give this a shot anyways. NO SD card no pictures no music.... Already within 15 minutes of no SD card issues are still there. I am really starting to hate this phone because of this update. Hoping to get a replacement (new) with 4.3 still on it. NO UPDATE for me till i know this and several issues are fixed.
I know i could root but i dont feel i should have to to fix any issues.
Has anyone else found a solution or heard of one yet?

Just try this , go to setting / general / power save , swith it on.
Then wait a moment before you try your phone again.
my wife phone got this issue because of over heating.
after switching the power save , the issue is gone.

update... contacted Tmobile within the last hour and apparently this rep said this is a known issue. She contacted Samsung and Google (could be blowing smoke up you know what) but she came back and said they are very aware of the issues and are vigorously working on a fix and your informations will be one of the first ones to get it. She was saying 4.4 (kitkat) screwed up a lot of Samsung devices. BTW she was also having the same problems. All replacement phones will come with 4.4 so exchanging is out of the question.
Regarding the power saving thing ill give it a shot. It was on before the master reset. Noticed it was off when i went in. On now so ill try then.

Home button not working at all (tried several fixes)

(Edit 1) Found a fix already! Read post 2!!!
Hello there,
I've been having a OnePlus Two since 4 months already, and had like 2 or 3 home button not working issues.
They used to fixed by themselves after a couple of days of not working, but not this last time.
I tried already the reinstalling system (after formatting system via TWRP), clean it several times, hard reset (hold power button for more than 20 seconds), complete drain battery and fully charge it again, force stop fingerprint service, take out the tempered glass screen protector, and none of those solutions worked.
I here attach (copy the link, can't upload a video directly to this post) a video in which you can see that whenever I power on the screen (still locked), the home button works for several times, but as soon as I unlock it (pattern lock) it stops working. This makes me think that the problem is software, not hardware, but as I said before, already tried reinstalling OOS 3.0, wiping system, cache, data, internal storage, etc.
I compressed the video so it wouldnt be too big, but quality is good enough, just rise the volume so you can listen to the "vibration" that the home button produce.
Any help would be appreciated.
Sincerely,
Daniel Castro

Fix for the issue!
Forum people, I found a fix!
Ok, the solution for making the home button work again (with fingerprint sensor) is the following.
-Factory reset while in OOS 3.0
-Set up everything up and then reboot into fastboot mode
-Install OOS 2.1 via fastboot (you will need to search the forums for it)
-Set up everything up and try to set up fingerprint (it wont work)
-Copy OOS 3.0 (Beta) in the root of the phone
-Reboot into stock recovery and flash OOS 3.0 (beta)
-Factory reset it and set up everything again
-Voila!
Feel free to try this method and reply to this threat or P.M. me for any help.
Sincerely,
Daniel Castro

I have the same problem
Tomorrow i'll try your method
I've posted a questione about this issue,
I think the One plus team should find a solution to this problem that afflict many users

Also, don't forget to rotate your phone 720 degrees, counter clock wise! ? hocus pocus....

DCastro555 said:
Forum people, I found a fix!
Ok, the solution for making the home button work again (with fingerprint sensor) is the following.
-Factory reset while in OOS 3.0
-Set up everything up and then reboot into fastboot mode
-Install OOS 2.1 via fastboot (you will need to search the forums for it)
-Set up everything up and try to set up fingerprint (it wont work)
-Copy OOS 3.0 (Beta) in the root of the phone
-Reboot into stock recovery and flash OOS 3.0 (beta)
-Factory reset it and set up everything again
-Voila!
Feel free to try this method and reply to this threat or P.M. me for any help.
Sincerely,
Daniel Castro
Click to expand...
Click to collapse
Will it erase my internal storage during that fast boot step? So I can backup all my data.
Sent from my ONE A2003 using Tapatalk

these fixes are all coincidences... we need to request a definitive fix from One plus team if is a software issue.

LOL9988 said:
Will it erase my internal storage during that fast boot step? So I can backup all my data.
Sent from my ONE A2003 using Tapatalk
Click to expand...
Click to collapse
It will erase everything, make a backup before starting the process.

faustin95 said:
these fixes are all coincidences... we need to request a definitive fix from One plus team if is a software issue.
Click to expand...
Click to collapse
Most probably hardware design fault, solution would be to redesign the phone and release a fixed design, will probably not happen unless oneplus3 is the solution.
And I second that it's just coincident behind these back and forth flashing of firmwares "solving" it, almost religious. But what are people to do when oneplus is not a company that takes responsibility for they're mistakes.

pitrus- said:
Most probably hardware design fault, solution would be to redesign the phone and release a fixed design, will probably not happen unless oneplus3 is the solution.
And I second that it's just coincident behind these back and forth flashing of firmwares "solving" it, almost religious. But what are people to do when oneplus is not a company that takes responsibility for they're mistakes.
Click to expand...
Click to collapse
If it works, its worth a try . And yeah, but we are not in any OnePlus Forum, neither debating about if they are gonna do anything about their own issue, we are trying to fix what an irresponsable company wont.

can we make together an official request to one plus to give us an answer or explanation about this? a lot of users are facing this issue, it's not normal
This is my second opt I bought that this problem has happened
sorry for my english

I had also tried lot of things but home button is not responsive at all.. H2os,exodus,oxygen 2.1 ,3.0 same everywhere
---------- Post added at 04:01 AM ---------- Previous post was at 03:59 AM ----------
Error is: when i open fingerprint setting
Enrollment not working try differnt finger or try again ... Nd fingerprint autotest not starting also

i've turned to stock i've updated to oxygen 3.0 bet and the button worked again

i think rooting installing twrp and installing different roms may be the cause of this issue

faustin95 said:
i think rooting installing twrp and installing different roms may be the cause of this issue
Click to expand...
Click to collapse
Unfortunately that is not the case, it's a hardware design bug.
However you can f-k up your finger scanner by damage your persistant-partition if you flash up and down between different ROM/bootloader revisions. But it's easily fixed by flashing the image file for that partition again.

pitrus- said:
Unfortunately that is not the case, it's a hardware design bug.
Click to expand...
Click to collapse
it's a driver issue

faustin95 said:
it's a driver issue
Click to expand...
Click to collapse
50/50 moisture sensitivity and driver issue.

Home button has been working fine for a year, installed 3.0.1 today and suddenly home button only works in OOS 3.0.1. No longer works in CM 13, yet works fine in OOS 3.0.1. Definitely a driver issue.
Tried installing OOS 2.2.1, wiping, then installing Grarak's CM 13 and home button refuses to work. Wiped system, data, cache, installed OOS 3.0.1 and home button works again. Tried wiping again and installed CM 13, home button stopped working. Wiped and reinstalled OOS 3.0.1, home button works again.

Odd thing, my phone will only work with CM13 roms and OOS 2.2.0 or less for fps and home button. Nothing will fix or ever work.

For me, the home button stopped working for a short while on Graraks, then it just jumped back to life again and I haven't had any more home button blackouts after that. If it's a driver issue, it's an extremely intermittent one.
The fingerprint scanner has stopped working from time to time at lockscreen, but this is acceptable for an official hackjobb supported scanner until official sources are released ?

Need Help with this!
Hi everyone!
I have a OP 2 for more than one and a half years now and never had any issues with it(stayed stock...) until recently. I didnt update the phone to the latest version and was putting it off, and today in the afternoon when I tried to unlock my phone it said the 'Fingerprint hardware is not available' and after unlocking the phone with the pattern, it IMMEDIATELY LOCKS ITSELF BACK !!! after split second it just locks the screen while everything is working like connection, wifi, messages, notifications, etc. but due to this I cannot access anything on the phone, can't go to settings and switch to onscreen nav bar buttons, can't force stop/wipe cache the com.fingerprints.serviceext either, tried restarting it several times, downloaded the update but can't even install it because the phone just locks! I have no idea what would fix it and I am avoiding a full reset and wipe on the phone(also based on all i have read, dont think it would fix it anyways)
If anyone knows whats the problem or has dealt with it or knows someone who has, please help me out here on how to fix this and what to do. I did not root it or flash custom ROM's on it yet so literally dont know why it happened.
Thanks,
Max

Flashlight being used by another app. Camera doesn't work

After flashing the unbranded firmware and rooting the phone, I'm not able to use the camera app. Opening it just says "Camera Failed. In the slide down menu, the flashlight icon is turned on even though I'm not actually using the flashlight. and I cant turn it off either. How do I fix this?
I've tried: clearing data & cache of camera app, clearing the cache partition, setting default settings of the camera app, changed camera storage from SD card to internal & vice versa

TommyQuid said:
After flashing the unbranded firmware and rooting the phone, I'm not able to use the camera app. Opening it just says "Camera Failed. In the slide down menu, the flashlight icon is turned on even though I'm not actually using the flashlight. and I cant turn it off either. How do I fix this?
I've tried: clearing data & cache of camera app, clearing the cache partition, setting default settings of the camera app, changed camera storage from SD card to internal & vice versa
Click to expand...
Click to collapse
Sucks no one responded to your post. I rooted my sons S7 Edge and sometime after it acquired the same issue yours has/has. I had another S7 Edge phone so I ended up rooting that one and giving it to him. I still have his old one with the camera fail issue but I've yet to try to figure out what caused it to happen. I know my response doesn't help with info or duration from OP post to reply, I just wanted to let you know that your post wasn't ignored by everyone. Unfortunately I have nothing substantial to contribute.

kanesglove said:
Sucks no one responded to your post. I rooted my sons S7 Edge and sometime after it acquired the same issue yours has/has. I had another S7 Edge phone so I ended up rooting that one and giving it to him. I still have his old one with the camera fail issue but I've yet to try to figure out what caused it to happen. I know my response doesn't help with info or duration from OP post to reply, I just wanted to let you know that your post wasn't ignored by everyone. Unfortunately I have nothing substantial to contribute.
Click to expand...
Click to collapse
So I ended up putting that phone back to stock then rooting it again and it had the exact same issue yours has. I did a clean root too and the issue is still present. From there I decided to again run it back to stock and this time do a nand erase all and repartition the device. After all was finished I checked the device and I'll be goddamned... it still has the same issue. So if the problem persists after all that reformatting is it safe to say that it's a hardware issue? I'm out of ideas. Sorry I couldn't help you.

kanesglove said:
So I ended up putting that phone back to stock then rooting it again and it had the exact same issue yours has. I did a clean root too and the issue is still present. From there I decided to again run it back to stock and this time do a nand erase all and repartition the device. After all was finished I checked the device and I'll be goddamned... it still has the same issue. So if the problem persists after all that reformatting is it safe to say that it's a hardware issue? I'm out of ideas. Sorry I couldn't help you.
Click to expand...
Click to collapse
you guys offer little information at all so this is why no one helps you. Maybe tell what firmware version you flashed what root version you did etc. There is a big difference between bootloader revB/11 and the others

Holy ****. Did I just get constructive suggestions from jrkruse?! Dude if you told me I could fix my phone by sucking a fart out of a wallaby's ass I'd do it cuz the advice came from you, and if there's one thing I know it's that you know your ****. You're ****in' awesome. I feel so special now. Ok sorry about that...
Well, I'm not too sure about the OP but I can tell you about the phone I have that seems to have the same issue.
My S7 Edge is a SM-G935V on android 7.0 on update 4BQK2. Prior to rooting I put everything to stock then I did a NAND erase and repartition. No issues with any of that.
I rooted my phone from this post
G935V Root Method. No Lag! No Heat!
G935V Root Method. No Lag! No Heat!
I AM NOT RESPONSIBLE FOR ANY OF YOUR ISSUES! ALL I CAN DO IS RECOMMEND A GOOD PSYCHOLOGIST! Hey guys. Stumbled on this by accident. I HAVE ABSOLUTELY NO IDEA WHY IT WORKS, BUT IT DOES. THE METHOD HAS BEEN TESTED BY ME AND A FEW OTHER PEOPLE HERE...
forum.xda-developers.com
which directs to your older method for gaining root privileges.
[DISCONTINUED] ROOT Method For Nougat
DISCONTINUED New Thread Found Here This Root Method For S7 Nougat Nougat_S7_Root_2_82_All_Carriers_V2.zip Includes Fingerprint Fix [Latest Verison] Nougat_S7_Root_2_81_All_Carriers_V2.zip Includes Fingerprint Fix Nougat_S7_Root_2_79_All.zip...
forum.xda-developers.com
I also flashed Unzip the Nougat_S7_Root_2_82_All_Carriers_V2.
Then I flashed the BL file in the BL slot from the G935U firmware with odin checking "Phone Bootloader Update". I used the BL file from G935UUES4BRA1 since it's the closest update for the U brand to the firmware this phone is on (G935VVRU4BQK2)
I'm aware that there are newer methods for gaining root access but I chose this method cuz I used it back in 2017-2018, I had read all the posts in the thread, and I knew it worked.
I currently have 3 S7 Edge phones all on the same firmware and build and are all rooted with the same combo method I just explained. The other 2 phones also have xposed installed and they both work well.. expect mine says weird stuff instead of the callers information. I think it only does it if they're a contact but in the notification tab it says an example like this 5556661234;verstat=No-TN-Validation. No clue how to fix that.
The phone that is having the same issue as the OP still had access to the private/secure folder when it was rooted; which I thought was weird cuz mine doesn't and from what I understood private mode gets disabled if the phone's rooted. Maybe it only gets disabled if you install xposed? I don't know. My son had the phone with the issue and it was his first smart phone and he dropped it a few times (with a case) so I was thinking it's an effect from something he downloaded from the play store (he's 20 now but pretty still very ignorant with android). Now I'm not sure if it's a software or hardware issue since the problem persisted after the NAND erase.
Something to note about my sons old phone also is that it has 2 thin pink lines running down one side of the screen (defective/dead pixels) and when the screen turns off it it flashes once before actually turning off. One time over the phone I tried troubleshooting the issue with him and he ended up being able to use his camera immediately after rebooting the phone though once he exited the camera app it wouldn't open again. We were trying a bunch of things, force closing any app I thought would be related to the issue. Not sure what allowed it work when it did, but even now right after a reboot the camera app still crashes.

This was long ago, I've since lost the phone. But, I was on the A bootloader and on OREO rooted using @/billa's method using an ENGboot file. I tried everything possible to get the camera to work including flashing back to stock but nothing helped. I just gave up finally. @kanesglove maybe try safely updating the firmware. Hope it helps