My friend has got Note 3 N9005 model. The problem are irritating autofocus and shutter sounds - both insanely loud and the first one so piercing that in quiet environment head hurts. As far as I see, some of Note 3 users have shutter sound toggle in camera settings. After reading bit of threads on xda I think it's CSC setting. However I don't want to root it or modify system in any way to not trip Knox counter and lose OTA updates. He's also from Poland, so I think CSC should be XEO (like in my S3). However, after entering recovery there are lines:
Code:
# MANUAL MODE #
-- Appling Multi-CSC...
Applied the CSC-code : XEF
Successfully applied multi-CSC
I tried flashing Poland firmware (downloaded from sammobile.com) through Odin PDA field, but it only updated firmware to the latest version (even not changing system state to "Modified"). CSC is still the same and in camera settings there is no sound toggle.
My question is - where can I download official CSC for Poland which has ability to turn off shutter sound and will flashing it trip Knox counter?
You can turn the volume of the phone to zero and the camera will be silent.Alternatively you can use a free app called silent camera.
why dont you use Wanam xposed to disable shutter sound
noteworthy said:
You can turn the volume of the phone to zero and the camera will be silent.Alternatively you can use a free app called silent camera.
Click to expand...
Click to collapse
Setting volume to vibration and complete mute from Accessibility settings doesn't affect camera at all and all camera apps from Play Store make much worse photos than stock camera app (not to mention functionality).
vndnguyen said:
why dont you use Wanam xposed to disable shutter sound
Click to expand...
Click to collapse
Xposed needs root to work and I don't want to root device or modify /system partition in any way, that could affect Knox or OTAs. I'm also afraid that all that no-Knox-tripping root methods doesn't remain after OTA update - either root disappears, Knox counter increments, system becomes "Modified" or device bootloops.
Konpon96 said:
Setting volume to vibration and complete mute from Accessibility settings doesn't affect camera at all and all camera apps from Play Store make much worse photos than stock camera app (not to mention functionality).
Xposed needs root to work and I don't want to root device or modify /system partition in any way, that could affect Knox or OTAs. I'm also afraid that all that no-Knox-tripping root methods doesn't remain after OTA update - either root disappears, Knox counter increments, system becomes "Modified" or device bootloops.
Click to expand...
Click to collapse
The Android version in your country must force camera sound.Turning off the volume works for my N3.
Not all camera apps are bad.Pro capture takes very good photos with better control than the stock app but you have to pay for it.This app also has a silent feature but if your Android version forces camera sound then it may not work.
noteworthy said:
The Android version in your country must force camera sound..
Click to expand...
Click to collapse
Yup this. Some countries require the sound to be on by Law. And cannot be disabled (officially at least)
My N1 when I first bought it also had forced camera sound even with the volume off.The only way I could stop the very loud camera sound was by putting a finger over the speaker hole.This muted the sound about 50%.Better than nothing and less annoying.
The problem is that CSC on friend's Note 3 is XEF (so French one) and flashing official Polish PDA from sammobile doesn't change it (multi-CSC, so it works with a lot of firmwares afaik). And as far as I see there is boolean in CSC which determines ability to silent shutter. I'm not sure if it's safe to dump CSC, edit it and then flash back, so where I can get XEO CSC file to flash with Odin without affecting Knox?
PS. In Poland it's legal to make photos without shutter/AF sounds, so Polish CSC should allow to mute them, just like in my XEO-CSCed S3.
vndnguyen said:
why dont you use Wanam xposed to disable shutter sound
Click to expand...
Click to collapse
Wanam Xposed doesn't disable all the camera sounds.
donalgodon said:
Wanam Xposed doesn't disable all the camera sounds.
Click to expand...
Click to collapse
Yes, but I've found a workaround for this issue. Just disable Smart stabilization and there is no more shutter sound
I've found a way that could change CSC. It involves rooting, but with Root de la Vega, so it shouldn't increment Knox. I would root, use bassie1995's CSC changer to change CSC to XEO (http://www.droidviews.com/how-to-change-csc-in-samsung-galaxy-phones/) and then reflash stock, not-rooted 4.3. However I'm wondering - if root itself doesn't trip Knox and OTAs, will changing CSC do it? Theoretically there isn't any flashing involved - just changing CSC from already-installed multi-CSC.
Related
Good News Folks!!!
I just downgraded my SM-P605 from NEE 4.4.2 back to NEE MJ9 4.3!! Knox not trigerred.
Step to downgrade from 4.4.2 back to 4.3:
1. Reboot to Download Mode (Power+Vol. Down) then Vol. Up to continue
2. Run Odin from PC (I used 3.09)
3. Uncheck Auto Reboot box
4. Check AP box, then find your NEE 4.3 MJ9 .tar firmware
5. Press Start
It takes about 2-3 minuttes until showing All threads completed.(succeed 1/failed 0) in the message box.
6. Turn off your note by holding down power button for few seconds
7. Press Vol. Up + Power button to boot into recovery
8. Wipe cache
9. Wipe user data
10. Reboot system
No SW rev failed during downgrade and Knox remains 0x0
Don't forget to hit Thanks button..
I love it. Begging for thanks without telling what you did.
I hope someone with a rooted p605 can manually save this Kitkat OTA(NEE region) file before Samsung start to lock bootloader from ability to downgrade from KK to JBean.
...
Adalean said:
What was the reason/why would you choose to downgrade back to 4.3?
Click to expand...
Click to collapse
Well, I had do install 4.3 firmware back cos there's no 4.4 firmware to flash trough Odin yet as I messed my tab trying to get s pen work after rooting. Now I'll just upgrade back to 4.4 and wait for root that doesn't break s pen.
droidan said:
Knox remains 0x0
Click to expand...
Click to collapse
KNOX trips when a non-KNOX or non-official bootloader is installed. 4.3 on the N10.1-14 had a KNOX enabled bootloader so downgrading from 4.4 wouldn't be an issue; at least for KNOX. People in other forums that moved to 4.3 from earlier s/w with non-KNOX enabled bootloaders are the ones who were freaking out because once KNOX is on a device you can't go back.
The “KNOX Warranty Void” bit (or simply KNOX bit) is used to detect if a non-KNOX kernel has been loaded on the device. It is a one-time programmable bit in e-fuse, which can only be turned from “0” to “1” (i.e. burned). If a non-KNOX boot loader or kernel has been put on the device, KNOX can no longer guarantee the security of the KNOX container. As a result, this KNOX bit will be burned to “1”, indicating that this device can no longer use the KNOX container service.https://www.samsungknox.com/en/blog...ox-enabled-devices-and-knox-warranty-void-bit
BarryH_GEG said:
KNOX trips when a non-KNOX or non-official bootloader is installed. 4.3 on the N10.1-14 had a KNOX enabled bootloader so downgrading from 4.4 wouldn't be an issue; at least for KNOX. People in other forums that moved to 4.3 from earlier s/w with non-KNOX enabled bootloaders are the ones who were freaking out because once KNOX is on a device you can't go back.
The “KNOX Warranty Void” bit (or simply KNOX bit) is used to detect if a non-KNOX kernel has been loaded on the device. It is a one-time programmable bit in e-fuse, which can only be turned from “0” to “1” (i.e. burned). If a non-KNOX boot loader or kernel has been put on the device, KNOX can no longer guarantee the security of the KNOX container. As a result, this KNOX bit will be burned to “1”, indicating that this device can no longer use the KNOX container service.https://www.samsungknox.com/en/blog...ox-enabled-devices-and-knox-warranty-void-bit
Click to expand...
Click to collapse
And your point is?
droidan said:
And your point is?
Click to expand...
Click to collapse
Pretty simple. Explaining to folks here who may not know what trips KNOX along with an explanation of how it works from a Samsung VP. I thought it was pretty clear.
Anyone tried on the P600? I've been stalling the update due to a bad experience with my previous p600.
elzeus said:
Anyone tried on the P600? I've been stalling the update due to a bad experience with my previous p600.
Click to expand...
Click to collapse
I guess Barry may have a good solution..
"
4.3 on the N10.1-14 had a KNOX enabled bootloader so downgrading from 4.4 wouldn't be an issue;....."
Normally and afaik you cant downgrade to an earlier android iteration. It is not possible. You can only jump to fws with the same bootloader. Not every fw get a new bootloader. Maybe with the ota of nee fw wasnt flashed the bootloader correctly. I think when you flash the same fw with Odin, you cant downgrade anymore.
hanspampel said:
Normally and afaik you cant downgrade to an earlier android iteration. It is not possible. You can only jump to fws with the same bootloader. Not every fw get a new bootloader. Maybe with the ota of nee fw wasnt flashed the bootloader correctly. I think when you flash the same fw with Odin, you cant downgrade anymore.
Click to expand...
Click to collapse
That's why I pointed it out..
Typing *#2663# and updating Wacom files did the trick for me to get the SPen to work without any hassle.
droisntns said:
Well, I had do install 4.3 firmware back cos there's no 4.4 firmware to flash trough Odin yet as I messed my tab trying to get s pen work after rooting. Now I'll just upgrade back to 4.4 and wait for root that doesn't break s pen.
Click to expand...
Click to collapse
Sent from my Samsung Galaxy Note 10.1 2014 LTE (P605)
droidan said:
Good News Folks!!!
I just downgraded my SM-P605 from NEE 4.4.2 back to NEE MJ9 4.3!! Knox not trigerred.
Step to downgrade from 4.4.2 back to 4.3:
1. Reboot to Download Mode (Power+Vol. Down) then Vol. Up to continue
2. Run Odin from PC (I used 3.09)
3. Uncheck Auto Reboot box
4. Check AP box, then find your NEE 4.3 MJ9 .tar firmware
5. Press Start
It takes about 2-3 minuttes until showing All threads completed.(succeed 1/failed 0) in the message box.
6. Turn off your note by holding down power button for few seconds
7. Press Vol. Up + Power button to boot into recovery
8. Wipe cache
9. Wipe user data
10. Reboot system
No SW rev failed during downgrade and Knox remains 0x0
Don't forget to hit Thanks button..
Click to expand...
Click to collapse
I did not want to downgrade back to 4.3 anymore. Here's why:
1. Full support for wireless printing is available for many apps
2. The Samsung clock widget in Android 4.3 has been replaced with the Nexus-like clock in Android 4.4. The font is much thinner that the previous version. It also includes a world clock, alarm, stopwatch, and a timer. The personal message feature is still available as an option.
3. The settings menu is still multi panel, with some Galaxy S5 icons. You can even resize the columns.
4. KNOX 2.0 is here, similar to the one on the S5.
KNOWN ISSUES
1. Lock screen effect does not work correctly (no ink effect)
2. I don't know if I downgrade to MK1 from ND2, will it trip KNOX? (United States version) ND2 uses KNOX 2.0.
Current build number: KOT49H.P600UEUCND2
KiwiBird97 said:
I did not want to downgrade back to 4.3 anymore. Here's why:
1. Full support for wireless printing is available for many apps
2. The Samsung clock widget in Android 4.3 has been replaced with the Nexus-like clock in Android 4.4. The font is much thinner that the previous version. It also includes a world clock, alarm, stopwatch, and a timer. The personal message feature is still available as an option.
3. The settings menu is still multi panel, with some Galaxy S5 icons. You can even resize the columns.
4. KNOX 2.0 is here, similar to the one on the S5.
KNOWN ISSUES
1. Lock screen effect does not work correctly (no ink effect)
2. I don't know if I downgrade to MK1 from ND2, will it trip KNOX? (United States version) ND2 uses KNOX 2.0.
Current build number: KOT49H.P600UEUCND2
Click to expand...
Click to collapse
I agree with you.
I believe we all like Kitkat.
Almost all the recent Samsung devices will not allow us to revert back to 4.3 after updating 4.4, EXCEPT Note 3 SM-N900W8 with earlier KK botloader. I guess that's the only variant of Note 3 that can be rooted and installed TWRP/CWM recovery without tripping knox.
I hope Chainfire may look thru this NEE P605XXUCNE2 bootloader/firmware. Hopefully, he will find something like the way he did with SM-N900W8.
hanspampel said:
Normally and afaik you cant downgrade to an earlier android iteration. It is not possible. You can only jump to fws with the same bootloader. Not every fw get a new bootloader. Maybe with the ota of nee fw wasnt flashed the bootloader correctly. I think when you flash the same fw with Odin, you cant downgrade anymore.
Click to expand...
Click to collapse
I tried 2 times(down, up, down then up again) with Odin, confirmed working.
droidan said:
I agree with you.
I believe we all like Kitkat.
Almost all the recent Samsung devices will not allow us to revert back to 4.3 after updating 4.4, EXCEPT Note 3 SM-N900W8 with earlier KK botloader. I guess that's the only variant of Note 3 that can be rooted and installed TWRP/CWM recovery without tripping knox.
I hope Chainfire may look thru this NEE P605XXUCNE2 bootloader/firmware. Hopefully, he will find something like the way he did with SM-N900W8.
Click to expand...
Click to collapse
:good:
Support for Chainfire!
droidan said:
I tried 2 times(down, up, down then up again) with Odin, confirmed working.
Click to expand...
Click to collapse
Confirmed working. Downgraded successfully. Knox 0x0.
droisntns said:
Well, I had do install 4.3 firmware back cos there's no 4.4 firmware to flash trough Odin yet as I messed my tab trying to get s pen work after rooting. Now I'll just upgrade back to 4.4 and wait for root that doesn't break s pen.
Click to expand...
Click to collapse
If you want full sd card write function that the dips at Google killed. That alone is reason enough. I see no speed or battery improvement with Kitkat, so 4.3 is the way to go, IF you want card write function for 3rd party apps.
shayind4 said:
Confirmed working. Downgraded successfully. Knox 0x0.
Click to expand...
Click to collapse
Did you downgrade on the p600?
I successfully rooted my Samsung Galaxy A8(Indian variant A800F). While experimenting withe the DPI values by ROM Manager's build.prop editor I made the mistake of changing it to 160. So all the UI elements were gone(Icons, Notification Bar, etc).
Then I had the bright Idea of resetting the phone which somehow did not revert to the original DPI settings. This in turn disabled USB Debugging and now I'm unable to use ADB. Moreover the FRP Lock is turned on too so I guess Download Mode won't work either.
The only thing I can do right now is taking screen shots and turning the phone off(Shutdown Dialogue Box is visible too). I did not take a backup at the time nor did I flash any recovery.
Hope I made my issue clear.
Now what options do I have left?
Can re-flashing the firmware do the trick?
Would the Samsung service centre guys re-flash the firmware even after the KNOX getting tripped off. Or I'll have to do that myself?
Any sort of help is highly appreciated. Thanks!
Yes you should be able to flash stock firmware again but no guarantee it'll work. All you need to do is get the original firmware from sammobile and Odin, downloaded both, extract all the Odin files to your PC, also extract the md5.tar file from the firmware zip, boot to download and connect, if it connects then that's a start, once connected click "ap" box and choose the firmware you just downloaded, wait a couple of mins for Odin to check the md5 is correct then hit start.
Sent from my SM-A500FU using XDA-Developers mobile app
Great. Will try that and post the results.
Just wanted to ask if this manual procedure may somehow make my situation even worse. Or is it completely safe to flash?
Really don't want to get into a deeper mess.
And thanks for the quick response
sanu23kumar said:
Great. Will try that and post the results.
Just wanted to ask if this manual procedure may somehow make my situation even worse. Or is it completely safe to flash?
Really don't want to get into a deeper mess.
And thanks for the quick response
Click to expand...
Click to collapse
Completely safe, that's the beauty of ODIN.
sanu23kumar said:
I successfully rooted my Samsung Galaxy A8(Indian variant A800F). While experimenting withe the DPI values by ROM Manager's build.prop editor I made the mistake of changing it to 160. So all the UI elements were gone(Icons, Notification Bar, etc).
Then I had the bright Idea of resetting the phone which somehow did not revert to the original DPI settings. This in turn disabled USB Debugging and now I'm unable to use ADB. Moreover the FRP Lock is turned on too so I guess Download Mode won't work either.
The only thing I can do right now is taking screen shots and turning the phone off(Shutdown Dialogue Box is visible too). I did not take a backup at the time nor did I flash any recovery.
Hope I made my issue clear.
Now what options do I have left?
Can re-flashing the firmware do the trick?
Would the Samsung service centre guys re-flash the firmware even after the KNOX getting tripped off. Or I'll have to do that myself?
Any sort of help is highly appreciated. Thanks!
Click to expand...
Click to collapse
you can flash it with service firmware (that means the firmware that one have all the file separately,pda csc cp bl pit) from,joomla or any other forum. it will reset the phone to its factory state.in ksa knox counter tripping not void the warranty.you can take the phone to any customer care without any problem.
How did you rooted it?
sanu23kumar said:
I successfully rooted my Samsung Galaxy A8(Indian variant A800F). While experimenting withe the DPI values by ROM Manager's build.prop editor I made the mistake of changing it to 160. So all the UI elements were gone(Icons, Notification Bar, etc).
Then I had the bright Idea of resetting the phone which somehow did not revert to the original DPI settings. This in turn disabled USB Debugging and now I'm unable to use ADB. Moreover the FRP Lock is turned on too so I guess Download Mode won't work either.
The only thing I can do right now is taking screen shots and turning the phone off(Shutdown Dialogue Box is visible too). I did not take a backup at the time nor did I flash any recovery.
Hope I made my issue clear.
Now what options do I have left?
Can re-flashing the firmware do the trick?
Would the Samsung service centre guys re-flash the firmware even after the KNOX getting tripped off. Or I'll have to do that myself?
Any sort of help is highly appreciated. Thanks!
Click to expand...
Click to collapse
How did you rooted it?
I used Smart Switch to unbrick after a having a FRP lock bootloop
I rooted my galaxy s8 few days ago and now i flash the stock rom with odin i need a lot of options which i can't use it when my device is rooted but after the new stock rom when i want to open private mode in samsung browser i can't it show me this message
- rooting detected for your security , secrete mode can't be used on rooted device
Also the security folder not work please a need help
No body can help me ??
Stiiti said:
I rooted my galaxy s8 few days ago and now i flash the stock rom with odin i need a lot of options which i can't use it when my device is rooted but after the new stock rom when i want to open private mode in samsung browser i can't it show me this message
- rooting detected for your security , secrete mode can't be used on rooted device
Also the security folder not work please a need help
Click to expand...
Click to collapse
Issue is due to tripping your knox.
How can i fix it
Once Knox is tripped that's it there is no 'fix'
At the moment the only way to fix is replace motherboard or buy a new phone
Just means you cannot use some Samsung related apps like secure folder,Samsung pay Samsung private browser etc.
spawnlives said:
Once Knox is tripped that's it there is no 'fix'
At the moment the only way to fix is replace motherboard or buy a new phone
Just means you cannot use some Samsung related apps like secure folder,Samsung pay Samsung private browser etc.
Click to expand...
Click to collapse
Eh, that's not a bad thing... There are plenty of way better alternatives on Gplay or F-Droid
There are 3 potential ways around it:
1. Custom ROMs based on stock that software set the Knox to be 0x0 (not tripped).
2. Use Magisk and hide your root on that app in particular.
3. Download a modded APK of Samsung browser that doesn't check for root
Helo,
is there a way to change CSC without change KNOX status? Have you seen any documentation to do this? Or linked necessery files?
What CSC is preffered if I need call recording option on call menu?
thank you
update: based on a nice answer from another topic, I think its possible, because we just use another (signed) binary to do this. Am I right?
https://forum.xda-developers.com/showpost.php?p=79969137&postcount=46
ps: can somebody confirm that official call recording option exist in allowed countries? (so worth to change CSC)
Hi, I just managed to unlock the call recording feature in my A40 - and it works! However, the overall procedure changed the Knox status. I am pretty sure it will not work without rooting the phone, because you have to gain r/w access in the system partition.
if you are familiar with flashing thing with odin just download the frimware with the csc you want and flash it but youll loose your files, also you can only flash the home csc but theres a chance the csc wont change but you wont loose your data , or flash the CSCblabla.md5 and itll work
Warning: Do this at your own risk, I am not responsible for any damage that is caused to your device. This method worked for me and should work for everyone.
Credit to yakapa40 on XDA for the apk. This would be impossible without him!
You must make sure the model numbers are the same for the country you want to change to. To check that go to
https://www.sammobile.com/firmwares/recent/
and type in your device model number. leave country code blank. The countries that are listed are those that will work on your specific device. DO NOT TRY TO CHANGE TO A DIFFERENT MODEL NUMBER COUNTRY!
MAKE sure device has above 70% battery just to be safe
OK lets start!
Backup all your data on samsung cloud and google
This will **erase** all your data
Download samsung drivers
https://www.hardreset.info/download/samsung-drivers/
Check the CSC code you want from
https://forum.xda-developers.com/showthread.php?t=2546689 credit to Jasi2169
Important later
download the firmware you want from sammobile (slow download speed) or
https://samfw.com/ for faster download speeds.
It will be a zip file so use winrar to extract and you should get 5 files that start with
AP (System &Recovery)
BL (Bootloader)
CP (Modem / Radio)
CSC\_ (Country / Region / Operator)
HOME\_CSC (Country / Region / Operator)
DELETE the home file
Next download Odin
https://dl2018.sammobile.com/Odin3-v3.14.4.zip
Extract the Odin file and run as administrator
Add each file to its respective field in Odin
Now we need to put the phone in download mode to do that go to:
https://www.hardreset.info/devices/samsung/samsung-galaxy-a51/download-mode/
keep trying until it works.
Next plug the device in and press start. It should take about 3-4 mins for odin to say PASS
DO NOT UNPLUG THE PHONE AT ANY POINT EVEN AFTER ODIN SAYS PASS
Let the phone do its thing and dont worry if it takes too long on the Samsung screen.
You should then be greeted with the welcome screen BUT it may not be the correct language so set it to English (I flashed UK firmware and it came in Russian)
Set the phone up but dont worry about apps we are going to reset the phone again
Head over to (APK provided by yakapa40)
https://drive.google.com/file/d/1hU3vl_V7NsRgI_RsQywytORoB8isJ1ni/view?usp=sharing
on your device or PC and download it. Extract and it should be a apk file. Download it with your device.
Allow unknown sources and it should says done and not open (that is normal)
put you device in flight mode/airplane mode
hold down the home screen and go to themes
Galaxy themes
My stuff
Select mysterious theme(make sure not to click update)
Select try it out
Go to Settings
About phone
Legal information
Change Carrier or whatever third option is (the one that says android 10)
Choose and install the CSC you want (that 3 letter code) remove sim and it will restart phone
again, dont worry if its on the Samsung screen for too long.
You should be back on the welcome screen and you are done!!!
Set up the phone and enjoy!!!
Credit to yakapa40 again on XDA for the apk. This would be impossible without him!
Does it work to enable the NFC on the latam version?
holach said:
Does it work to enable the NFC on the latam version?
Click to expand...
Click to collapse
if the phone has nfc then it will work. NFC is hardware not software.
this method void warranty? ¡Saludos!
carloselvirus said:
this method void warranty? ¡Saludos!
Click to expand...
Click to collapse
no
thanks! i did it and it worked great
If i flash a firmware my brightness problem will go away?
GeorgeEdwardoo said:
If i flash a firmware my brightness problem will go away?
Click to expand...
Click to collapse
If your actual screen is faulty then it wont work but no harm in trying since warranty is not voided
hey, my galaxy theme has not try out option in airplane mode ,, it says check network connection (it has only two button check connection and try again , no try out)... what should I do?
I already installed the mysterious theme and select "try it out", I went to "settings", About phone and in "Legal Information", the option "Change Carrier" does not appear, what could be the problem?
The software version says it is October 1, 2020. Thanks!
danao78 said:
I already installed the mysterious theme and select "try it out", I went to "settings", About phone and in "Legal Information", the option "Change Carrier" does not appear, what could be the problem?
The software version says it is October 1, 2020. Thanks!
Click to expand...
Click to collapse
Just got a new phone with the same software version and the same problem. Did you ever come up with a solution?
Thanks.
Edit: actually this is closer to my problem.
armanate said:
hey, my galaxy theme has not try out option in airplane mode ,, it says check network connection (it has only two button check connection and try again , no try out)... what should I do?
Click to expand...
Click to collapse
oldnoob said:
Just got a new phone with the same software version and the same problem. Did you ever come up with a solution?
Thanks.
Edit: actually this is closer to my problem.
Click to expand...
Click to collapse
Can anybody share the app the link is no working no more
Hi, I changed csc on my A51 in order to enable native call recording feature ( Italian stock firmware and Vietnam XXV CSC ) but after last OTA update ( build a515fxxu5eug5 ) google pay stopped working due to "unsafe firmware", as it was rooted.
Which is your advice ?
andr123a said:
Hi, I changed csc on my A51 in order to enable native call recording feature ( Italian stock firmware and Vietnam XXV CSC ) but after last OTA update ( build a515fxxu5eug5 ) google pay stopped working due to "unsafe firmware", as it was rooted.
Which is your advice ?
Click to expand...
Click to collapse
interesting.. is that means if you skip OTA everything will works ? is your phone boatload unlocked ?
bizkit_120 said:
interesting.. is that means if you skip OTA everything will works ? is your phone boatload unlocked ?
Click to expand...
Click to collapse
No. I think there was some problem with THAT update....because after further updates it started working again...
(Stock Bootloader)
Sounds like very thing works fine now on your phone? How s that call recording func ,works as expected with Bluetooth headphones connected as well ? What about caller id ,assume since region has changed It won't gonna detect correct local numbers,am I right? Thanks for sharing!
Nono, everything about calls (and recording) works perfectly, with headphones, too