Hi,
I have a Galaxy S3 (I9300), and recently encrypted the device to enable to me to use my employer's exchange email service (NHS.net). The encryption process went without issue and my phone has been working normally since (about 2 weeks). However I have now received a message for a 170Kb OTA firmware update for the phone. When I click "Update now" is says the following:
Unable to update new software. Device is encrypted. Decrypt?
Click to expand...
Click to collapse
If I click OK it takes me to the "Security and lock screen" sub-menu in settings. In here the "Encrypt device" button is greyed out (as expected) and there seems to be nothing more to do. The update does not proceed. If I click cancel the device re-prompts me later anyway.
The problem is that my device keeps on prompting me to update with my only two options either to proceed as above (and get nowhere) OR postpone the update for up to 3 hours and get prompted again.
So now I am trapped in a situation where my device is nagging me to update but gives me no way to do so. As far as I am aware, encryption of an android device is irreversible without a factory reset so I am confused as to why the firmware update even asks for it?
Am I missing something here or is this a crappily designed security update from Samsung? I really don't want to have to factory reset my device then re-download all my software AND re-encrypt my device to use my email for a 170kb update; especially if this will happen again!
Any advice would be much appreciated,
Thanks
MalcontentUK said:
Hi,
I have a Galaxy S3 (I9300), and recently encrypted the device to enable to me to use my employer's exchange email service (NHS.net). The encryption process went without issue and my phone has been working normally since (about 2 weeks). However I have now received a message for a 170Kb OTA firmware update for the phone. When I click "Update now" is says the following:
If I click OK it takes me to the "Security and lock screen" sub-menu in settings. In here the "Encrypt device" button is greyed out (as expected) and there seems to be nothing more to do. The update does not proceed. If I click cancel the device re-prompts me later anyway.
The problem is that my device keeps on prompting me to update with my only two options either to proceed as above (and get nowhere) OR postpone the update for up to 3 hours and get prompted again.
So now I am trapped in a situation where my device is nagging me to update but gives me no way to do so. As far as I am aware, encryption of an android device is irreversible without a factory reset so I am confused as to why the firmware update even asks for it?
Am I missing something here or is this a crappily designed security update from Samsung? I really don't want to have to factory reset my device then re-download all my software AND re-encrypt my device to use my email for a 170kb update; especially if this will happen again!
Any advice would be much appreciated,
Thanks
Click to expand...
Click to collapse
why dont you use kies? maybe that will fix the problem
John Death said:
why dont you use kies? maybe that will fix the problem
Click to expand...
Click to collapse
Hi,
Tried Samsung Kies repeatedly; it downloads the update and then during the "Firmware upgrade in progress" times out after an hour.
Looks like I am the only person experiencing this problem; may have to factory reset the device after all.
MalcontentUK said:
Hi,
Tried Samsung Kies repeatedly; it downloads the update and then during the "Firmware upgrade in progress" times out after an hour.
Looks like I am the only person experiencing this problem; may have to factory reset the device after all.
Click to expand...
Click to collapse
You are not the only one, I am experiencing the exact same problem with encrypted device and not being able to install updates.
So far I have not been able to find a solution.
Manually apply OTA updates is in testing and a few have got it to work: I cant post a link but I did a search on these forums and found a tread about it.
Hope we can find the answer
Encrypted GALAXY S3 update
I am experiencing the exact same problem with encrypted device and not being able to install updates as my device is encrypted due to the Exchange! Hope someone already solved this issue? TIA
FYI
---------------------------------
Update From
IMM76D.I9300BUALE6
to
IMM76D.I9300BUBLG3
Same problem here. I would appreciate any idea. OTA updates usually work fine with my Asus Transformer, so this should be a Samsung related problem.
steinmarder said:
Same problem here. I would appreciate any idea. OTA updates usually work fine with my Asus Transformer, so this should be a Samsung related problem.
Click to expand...
Click to collapse
Update: For my phone, it actually seems possible to decrypt the device via the Security Menu. Samsungs support told me that this has to be done before the update can be installed....
I was also getting this a few weeks ago but when I connected to my pc and ran the update through Kies it updated without having to decrypt first
I've now removed my exchange connection to nhs.net and decrypted so unable to test
Sent from my GT-I9300 using xda app-developers app
neilybealy said:
I was also getting this a few weeks ago but when I connected to my pc and ran the update through Kies it updated without having to decrypt first
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
We too are experiencing this problem despite Samsungs "SAFE" (Samsung Approved For Enterprise) designation on the S III.
What version of KIES did you use? I've tried v2.2 and v2.3
Remove Exchange Email First
Vicntc said:
We too are experiencing this problem despite Samsungs "SAFE" (Samsung Approved For Enterprise) designation on the S III.
What version of KIES did you use? I've tried v2.2 and v2.3
Click to expand...
Click to collapse
I realize this thread is a little old but i'll reply anyway. I've seen on other forums that your enterprise email is causing the issue. You have to remove your enterprise email/exchange acct in order to decrypt the device. Once removed, the option to decrypt should be available. You may then accept the OTA. Your phone is only doing what it's told to do by the exchange server. It might be a ***** to remove the account but i think it would still be easier than a factory reset.
haddy17 said:
I realize this thread is a little old but i'll reply anyway. I've seen on other forums that your enterprise email is causing the issue. You have to remove your enterprise email/exchange acct in order to decrypt the device. Once removed, the option to decrypt should be available. You may then accept the OTA. Your phone is only doing what it's told to do by the exchange server. It might be a ***** to remove the account but i think it would still be easier than a factory reset.
Click to expand...
Click to collapse
Thanks for the post haddy17. We have investigated that option but when you're working with potentially thousands of staff/employees, it's a tad cumbersome to have them remove, upgrade, reconfigure. If it were just me, it would be fine. We're currently trying to get a response from Samsung and while we have made some progress, it's not clear where the end may be...
You are probably using Exchange servers? One way could be to change ActiveSync policy to not require encryption on device. This is selectable feature. Or maybe create two policies and move clients between them from request of user.
There are still shortcomings what comes to corporate security and Android mobiles (well there are issues on other platforms too)
About a week ago, I was reading about Samsung will start pushing an OTA update to limit the phone more and maybe brick them so we can return them.
After reading a few threads, I downloaded package disabler. Unfortunately, the package disabler developer was contacted by Samsung or whatever to not show the OTA packages so that they can push the update.
I have to say, I'm not sure if this is just a rumor or if it's true, a lot of stuff like this can be found in any forum.
Also disabled update automatically and disabled the play store's automatic update as well. Paranoid much...
But I still received the notification of a new update. Now I know that this is what they want so I tried to avoid it. Then it started bugging me, so I'm like let me click on it and cancel it. Don't be fooled, there's no cancel button! There's a counter too! Which was funny. I tried putting the phone into recovery mode in hopes that it would cancel the update, but after the phone rebooted it just installed the updates.
Phone will only charge to 60, and a more annoying pop up will show saying it's illegal to have the phone or give it and have to return it and so on.
Anywhooo, I managed to get the stock rom from the previous version and decided to try and flash it maybe it'll override the update.
IT DID!!! Now my phone charges to 100 again the recall pop up is still there and its the old one not the scary one. I downloaded package disabler 6.3 and managed to block the correct packages to avoid this from happening again.
You can Google "note 7 stock rom" and find yours or you can message me and I'll send you the link.
My phone is a Roger's phone. Downloaded this N930W8VLU2API3 (release date 16.09.2016) this is the build from September.
The download was very slow speed, so be patient!
Settings, developer options, and checked "OEM unlock" and "USB debugging". Then lock screen and security and disabled SD encryption. Screen lock settings none.
TIP
Go to phone and type *#06# and write down the IMEI and S/N just incase something goes wrong and you have to use smart switch to recover the firmware. Also, back up the phone.
After downloading the firmware, I downloaded another copy. I did this to check the files' sizes and see if the download was interrupted or caused files to break.
TIP
UNZIP THE FILES FROM THE FOLDER, do not attempt to only open the zip and choose the files as it might crash.
Files should have "AP, BL, CSC, CP". I opened Odin(3.12), plugged the phone.
Odin should say that the phone is connected in port X.
Chose the files from the unzipped folder. One of the files is almost 4 GB in size, so it will take time for Odin to read. Windows might display (application not responding) on top, ignore it and wait.
Selected and checked all the files in Odin. If there's no check next to it, it won't work.
Put the phone in recovery mode (vol down + home + power), then click (vol up).
Start on Odin. It should pass.
Phone displayed the blue screen and that its installing the "update" which really should be a downgrade. Then it took a while displaying the Samsung logo. It was waving so waited.
Now the phone went back to how it was before the OTA update. :good:
That's exactly what I did after I received the OTA update. not sure if I was lucky or not but my data was still there. Didn't have to restore it. If it deleted your date, it should be fine since you backed it up.
Don't forget to uninstall package disabler then install the 6.3 version and disable the update packages!!!
This has worked for me few days ago!! All went too smooth!
Good Job Raider! This will be useful to so many people.
knight-raider said:
About a week ago, I was reading about Samsung will start pushing an OTA update to limit the phone more and maybe brick them so we can return them.
After reading a few threads, I downloaded package disabler. Unfortunately, the package disabler developer was contacted by Samsung or whatever to not show the OTA packages so that they can push the update.
I have to say, I'm not sure if this is just a rumor or if it's true, a lot of stuff like this can be found in any forum.
Also disabled update automatically and disabled the play store's automatic update as well. Paranoid much...
But I still received the notification of a new update. Now I know that this is what they want so I tried to avoid it. Then it started bugging me, so I'm like let me click on it and cancel it. Don't be fooled, there's no cancel button! There's a counter too! Which was funny. I tried putting the phone into recovery mode in hopes that it would cancel the update, but after the phone rebooted it just installed the updates.
Phone will only charge to 60, and a more annoying pop up will show saying it's illegal to have the phone or give it and have to return it and so on.
Anywhooo, I managed to get the stock rom from the previous version and decided to try and flash it maybe it'll override the update.
IT DID!!! Now my phone charges to 100 again the recall pop up is still there and its the old one not the scary one. I downloaded package disabler 6.3 and managed to block the correct packages to avoid this from happening again.
You can Google "note 7 stock rom" and find yours or you can message me and I'll send you the link.
My phone is a Roger's phone. Downloaded this N930W8VLU2API3 (release date 16.09.2016) this is the build from September.
The download was very slow speed, so be patient!
Settings, developer options, and checked "OEM unlock" and "USB debugging". Then lock screen and security and disabled SD encryption. Screen lock settings none.
TIP
Go to phone and type *#06# and write down the IMEI and S/N just incase something goes wrong and you have to use smart switch to recover the firmware. Also, back up the phone.
After downloading the firmware, I downloaded another copy. I did this to check the files' sizes and see if the download was interrupted or caused files to break.
TIP
UNZIP THE FILES FROM THE FOLDER, do not attempt to only open the zip and choose the files as it might crash.
Files should have "AP, BL, CSC, CP". I opened Odin(3.12), plugged the phone.
Odin should say that the phone is connected in port X.
Chose the files from the unzipped folder. One of the files is almost 4 GB in size, so it will take time for Odin to read. Windows might display (application not responding) on top, ignore it and wait.
Selected and checked all the files in Odin. If there's no check next to it, it won't work.
Put the phone in recovery mode (vol down + home + power), then click (vol up).
Start on Odin. It should pass.
Phone displayed the blue screen and that its installing the "update" which really should be a downgrade. Then it took a while displaying the Samsung logo. It was waving so waited.
Now the phone went back to how it was before the OTA update. :good:
That's exactly what I did after I received the OTA update. not sure if I was lucky or not but my data was still there. Didn't have to restore it. If it deleted your date, it should be fine since you backed it up.
Don't forget to uninstall package disabler then install the 6.3 version and disable the update packages!!!
Click to expand...
Click to collapse
How do you go about doing this"Don't forget to uninstall package disabler then install the 6.3 version and disable the update package" where in the phone i much go to uninstall and disable update package
joseph- said:
How do you go about doing this"Don't forget to uninstall package disabler then install the 6.3 version and disable the update package" where in the phone i much go to uninstall and disable update package
Click to expand...
Click to collapse
In my case, my date wasn't deleted. I had "Package Disabler Pro" application installed (the latest update which didn't show the OTA packages).
I uninstalled it, then downloaded the 6.3 version (which shows the packages) and disabled the OTA files
knight-raider said:
About a week ago, I was reading about Samsung will start pushing an OTA update to limit the phone more and maybe brick them so we can return them.
After reading a few threads, I downloaded package disabler. Unfortunately, the package disabler developer was contacted by Samsung or whatever to not show the OTA packages so that they can push the update.
I have to say, I'm not sure if this is just a rumor or if it's true, a lot of stuff like this can be found in any forum.
Also disabled update automatically and disabled the play store's automatic update as well. Paranoid much...
But I still received the notification of a new update. Now I know that this is what they want so I tried to avoid it. Then it started bugging me, so I'm like let me click on it and cancel it. Don't be fooled, there's no cancel button! There's a counter too! Which was funny. I tried putting the phone into recovery mode in hopes that it would cancel the update, but after the phone rebooted it just installed the updates.
Phone will only charge to 60, and a more annoying pop up will show saying it's illegal to have the phone or give it and have to return it and so on.
Anywhooo, I managed to get the stock rom from the previous version and decided to try and flash it maybe it'll override the update.
IT DID!!! Now my phone charges to 100 again the recall pop up is still there and its the old one not the scary one. I downloaded package disabler 6.3 and managed to block the correct packages to avoid this from happening again.
You can Google "note 7 stock rom" and find yours or you can message me and I'll send you the link.
My phone is a Roger's phone. Downloaded this N930W8VLU2API3 (release date 16.09.2016) this is the build from September.
The download was very slow speed, so be patient!
Settings, developer options, and checked "OEM unlock" and "USB debugging". Then lock screen and security and disabled SD encryption. Screen lock settings none.
TIP
Go to phone and type *#06# and write down the IMEI and S/N just incase something goes wrong and you have to use smart switch to recover the firmware. Also, back up the phone.
After downloading the firmware, I downloaded another copy. I did this to check the files' sizes and see if the download was interrupted or caused files to break.
TIP
UNZIP THE FILES FROM THE FOLDER, do not attempt to only open the zip and choose the files as it might crash.
Files should have "AP, BL, CSC, CP". I opened Odin(3.12), plugged the phone.
Odin should say that the phone is connected in port X.
Chose the files from the unzipped folder. One of the files is almost 4 GB in size, so it will take time for Odin to read. Windows might display (application not responding) on top, ignore it and wait.
Selected and checked all the files in Odin. If there's no check next to it, it won't work.
Put the phone in recovery mode (vol down + home + power), then click (vol up).
Start on Odin. It should pass.
Phone displayed the blue screen and that its installing the "update" which really should be a downgrade. Then it took a while displaying the Samsung logo. It was waving so waited.
Now the phone went back to how it was before the OTA update. :good:
That's exactly what I did after I received the OTA update. not sure if I was lucky or not but my data was still there. Didn't have to restore it. If it deleted your date, it should be fine since you backed it up.
Don't forget to uninstall package disabler then install the 6.3 version and disable the update packages!!!
Click to expand...
Click to collapse
Funny because i tried same thing and odin failed. It won't allow rolling bk to original rom.
knight-raider said:
About a week ago, I was reading about Samsung will start pushing an OTA update to limit the phone more and maybe brick them so we can return them.
After reading a few threads, I downloaded package disabler. Unfortunately, the package disabler developer was contacted by Samsung or whatever to not show the OTA packages so that they can push the update.
I have to say, I'm not sure if this is just a rumor or if it's true, a lot of stuff like this can be found in any forum.
Also disabled update automatically and disabled the play store's automatic update as well. Paranoid much...
But I still received the notification of a new update. Now I know that this is what they want so I tried to avoid it. Then it started bugging me, so I'm like let me click on it and cancel it. Don't be fooled, there's no cancel button! There's a counter too! Which was funny. I tried putting the phone into recovery mode in hopes that it would cancel the update, but after the phone rebooted it just installed the updates.
Phone will only charge to 60, and a more annoying pop up will show saying it's illegal to have the phone or give it and have to return it and so on.
Anywhooo, I managed to get the stock rom from the previous version and decided to try and flash it maybe it'll override the update.
IT DID!!! Now my phone charges to 100 again the recall pop up is still there and its the old one not the scary one. I downloaded package disabler 6.3 and managed to block the correct packages to avoid this from happening again.
You can Google "note 7 stock rom" and find yours or you can message me and I'll send you the link.
My phone is a Roger's phone. Downloaded this N930W8VLU2API3 (release date 16.09.2016) this is the build from September.
The download was very slow speed, so be patient!
Settings, developer options, and checked "OEM unlock" and "USB debugging". Then lock screen and security and disabled SD encryption. Screen lock settings none.
TIP
Go to phone and type *#06# and write down the IMEI and S/N just incase something goes wrong and you have to use smart switch to recover the firmware. Also, back up the phone.
After downloading the firmware, I downloaded another copy. I did this to check the files' sizes and see if the download was interrupted or caused files to break.
TIP
UNZIP THE FILES FROM THE FOLDER, do not attempt to only open the zip and choose the files as it might crash.
Files should have "AP, BL, CSC, CP". I opened Odin(3.12), plugged the phone.
Odin should say that the phone is connected in port X.
Chose the files from the unzipped folder. One of the files is almost 4 GB in size, so it will take time for Odin to read. Windows might display (application not responding) on top, ignore it and wait.
Selected and checked all the files in Odin. If there's no check next to it, it won't work.
Put the phone in recovery mode (vol down + home + power), then click (vol up).
Start on Odin. It should pass.
Phone displayed the blue screen and that its installing the "update" which really should be a downgrade. Then it took a while displaying the Samsung logo. It was waving so waited.
Now the phone went back to how it was before the OTA update. :good:
That's exactly what I did after I received the OTA update. not sure if I was lucky or not but my data was still there. Didn't have to restore it. If it deleted your date, it should be fine since you backed it up.
Don't forget to uninstall package disabler then install the 6.3 version and disable the update packages!!!
Click to expand...
Click to collapse
WORKED FOR ME AS WELL!!! Green Battery is back! now lets see if it charges over 60%
I've downloaded Package Disabler Pro 6.3 on my Note 7 after sucessfully using Odin to go back one software update.
However, I've disabled all the following...
com.policydm
com.sec.android.soagent
com.samsung.android.omcagent
com.wssyncmldm
com.sec.spp.push
Except for the most important ones...
com.samsung.firmware.sensorhub
com.samsung.android.firmware.tsp
Because they don't come up.
Will this be an issue?
Can you not just root and install a custom rom?
marvi0 said:
Can you not just root and install a custom rom?
Click to expand...
Click to collapse
No root for the snapdragon
Maiesta_Miyabi said:
I've downloaded Package Disabler Pro 6.3 on my Note 7 after sucessfully using Odin to go back one software update.
However, I've disabled all the following...
com.policydm
com.sec.android.soagent
com.samsung.android.omcagent
com.wssyncmldm
com.sec.spp.push
Except for the most important ones...
com.samsung.firmware.sensorhub
com.samsung.android.firmware.tsp
Because they don't come up.
Will this be an issue?
Click to expand...
Click to collapse
Did you have a previous version installed?
knight-raider said:
About a week ago, I was reading about Samsung will start pushing an OTA update to limit the phone more and maybe brick them so we can return them.
After reading a few threads, I downloaded package disabler. Unfortunately, the package disabler developer was contacted by Samsung or whatever to not show the OTA packages so that they can push the update.
I have to say, I'm not sure if this is just a rumor or if it's true, a lot of stuff like this can be found in any forum.
Also disabled update automatically and disabled the play store's automatic update as well. Paranoid much...
But I still received the notification of a new update. Now I know that this is what they want so I tried to avoid it. Then it started bugging me, so I'm like let me click on it and cancel it. Don't be fooled, there's no cancel button! There's a counter too! Which was funny. I tried putting the phone into recovery mode in hopes that it would cancel the update, but after the phone rebooted it just installed the updates.
Phone will only charge to 60, and a more annoying pop up will show saying it's illegal to have the phone or give it and have to return it and so on.
Anywhooo, I managed to get the stock rom from the previous version and decided to try and flash it maybe it'll override the update.
IT DID!!! Now my phone charges to 100 again the recall pop up is still there and its the old one not the scary one. I downloaded package disabler 6.3 and managed to block the correct packages to avoid this from happening again.
You can Google "note 7 stock rom" and find yours or you can message me and I'll send you the link.
My phone is a Roger's phone. Downloaded this N930W8VLU2API3 (release date 16.09.2016) this is the build from September.
The download was very slow speed, so be patient!
Settings, developer options, and checked "OEM unlock" and "USB debugging". Then lock screen and security and disabled SD encryption. Screen lock settings none.
TIP
Go to phone and type *#06# and write down the IMEI and S/N just incase something goes wrong and you have to use smart switch to recover the firmware. Also, back up the phone.
After downloading the firmware, I downloaded another copy. I did this to check the files' sizes and see if the download was interrupted or caused files to break.
TIP
UNZIP THE FILES FROM THE FOLDER, do not attempt to only open the zip and choose the files as it might crash.
Files should have "AP, BL, CSC, CP". I opened Odin(3.12), plugged the phone.
Odin should say that the phone is connected in port X.
Chose the files from the unzipped folder. One of the files is almost 4 GB in size, so it will take time for Odin to read. Windows might display (application not responding) on top, ignore it and wait.
Selected and checked all the files in Odin. If there's no check next to it, it won't work.
Put the phone in recovery mode (vol down + home + power), then click (vol up).
Start on Odin. It should pass.
Phone displayed the blue screen and that its installing the "update" which really should be a downgrade. Then it took a while displaying the Samsung logo. It was waving so waited.
Now the phone went back to how it was before the OTA update. :good:
That's exactly what I did after I received the OTA update. not sure if I was lucky or not but my data was still there. Didn't have to restore it. If it deleted your date, it should be fine since you backed it up.
Don't forget to uninstall package disabler then install the 6.3 version and disable the update packages!!!
Click to expand...
Click to collapse
So this is funny but i kinda fixes my phone lol now it charges up to 100. I tried koodo firmware and i was able to restore it. Originally i tried the general Samsung firmware for note 7 nd it kept on failing in odin then i realized wen i put my simcard in back wen first got the phone it looked to koodo. Now i used pkg disabler to disable updates too.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
No previous version installed.
Att version
Mine is SM-930A. It's the AT&T version. Please help.
knight-raider said:
About a week ago, I was reading about Samsung will start pushing an OTA update to limit the phone more and maybe brick them so we can return them.
After reading a few threads, I downloaded package disabler. Unfortunately, the package disabler developer was contacted by Samsung or whatever to not show the OTA packages so that they can push the update.
I have to say, I'm not sure if this is just a rumor or if it's true, a lot of stuff like this can be found in any forum.
Also disabled update automatically and disabled the play store's automatic update as well. Paranoid much...
But I still received the notification of a new update. Now I know that this is what they want so I tried to avoid it. Then it started bugging me, so I'm like let me click on it and cancel it. Don't be fooled, there's no cancel button! There's a counter too! Which was funny. I tried putting the phone into recovery mode in hopes that it would cancel the update, but after the phone rebooted it just installed the updates.
Phone will only charge to 60, and a more annoying pop up will show saying it's illegal to have the phone or give it and have to return it and so on.
Anywhooo, I managed to get the stock rom from the previous version and decided to try and flash it maybe it'll override the update.
IT DID!!! Now my phone charges to 100 again the recall pop up is still there and its the old one not the scary one. I downloaded package disabler 6.3 and managed to block the correct packages to avoid this from happening again.
You can Google "note 7 stock rom" and find yours or you can message me and I'll send you the link.
My phone is a Roger's phone. Downloaded this N930W8VLU2API3 (release date 16.09.2016) this is the build from September.
The download was very slow speed, so be patient!
Settings, developer options, and checked "OEM unlock" and "USB debugging". Then lock screen and security and disabled SD encryption. Screen lock settings none.
TIP
Go to phone and type *#06# and write down the IMEI and S/N just incase something goes wrong and you have to use smart switch to recover the firmware. Also, back up the phone.
After downloading the firmware, I downloaded another copy. I did this to check the files' sizes and see if the download was interrupted or caused files to break.
TIP
UNZIP THE FILES FROM THE FOLDER, do not attempt to only open the zip and choose the files as it might crash.
Files should have "AP, BL, CSC, CP". I opened Odin(3.12), plugged the phone.
Odin should say that the phone is connected in port X.
Chose the files from the unzipped folder. One of the files is almost 4 GB in size, so it will take time for Odin to read. Windows might display (application not responding) on top, ignore it and wait.
Selected and checked all the files in Odin. If there's no check next to it, it won't work.
Put the phone in recovery mode (vol down + home + power), then click (vol up).
Start on Odin. It should pass.
Phone displayed the blue screen and that its installing the "update" which really should be a downgrade. Then it took a while displaying the Samsung logo. It was waving so waited.
Now the phone went back to how it was before the OTA update. :good:
That's exactly what I did after I received the OTA update. not sure if I was lucky or not but my data was still there. Didn't have to restore it. If it deleted your date, it should be fine since you backed it up.
Don't forget to uninstall package disabler then install the 6.3 version and disable the update packages!!!
Click to expand...
Click to collapse
worked thank you
I did the same thing as instructed and was able to downgrade my note 7 snap dragon to a previous stock version before the forced update. Battery is back to 100%, no update messages everything seems to be running great. However I noticed my Secure folder is no longer working. Has anyone else having this issue? When I try to open secure folder or setup the folder it gives me a error message saying " Secure folder cannot be set up because unauthorized software was installed on the device. I got the rom from Sam mobile for my Rogers phone Sept update. Sometimes the error messages says " Failed to create knox mode. Try again. When I use an app to check my if my knox has been tripped is says everything is normal, 0x0 valid warrenty. Any ideas what a solution could be?
By the way... Thanks for posting how to downgrade and get my note 7 back to normal working condition!
goldensun7 said:
I did the same thing as instructed and was able to downgrade my note 7 snap dragon to a previous stock version before the forced update. Battery is back to 100%, no update messages everything seems to be running great. However I noticed my Secure folder is no longer working. Has anyone else having this issue? When I try to open secure folder or setup the folder it gives me a error message saying " Secure folder cannot be set up because unauthorized software was installed on the device. I got the rom from Sam mobile for my Rogers phone Sept update. Sometimes the error messages says " Failed to create knox mode. Try again. When I use an app to check my if my knox has been tripped is says everything is normal, 0x0 valid warrenty. Any ideas what a solution could be?
By the way... Thanks for posting how to downgrade and get my note 7 back to normal working condition!
Click to expand...
Click to collapse
Ok looks like I fixed the problem. I only flashed the larger AP file and not all the files in the stock rom. Once I flashed the other files, secure folder became available.
Be sure to flash all files in the stock rom.
oh man I cant thank you enough for helping me bring some life back into my phone! the 60% was brutal! back to 100% charge now!!!
I did run into some issues, and in case this helps anyone else who couldnt get odin to pass the most important thing is to make sure your downloading the right carrier version of the firmware. You need to use the carrier version that matches the same one the phone was originally activated. In my case, my Bell note 7 was originally activated using a virgin mobile sim card so odin would fail until I used the VMC region instead of BMC.
Thanks again!
would someone be kind enough to post a youtube video for those of us who are not so familiar with using ODIN
Thank You.
Its great that some of you are able to fight back against the 60 percent update, i blocked mine before it even happened but nothing will help us when the carriers block our devices... i just got off the phone with sprint (US) and they told me they will definately block the note 7s in the near future long before the 8 comes out... if someone has a solution, please pm me or post it here if you can...
Personally my story about keeping the no seven is probably a lot different than most people...
In February my now ex wife stole my Note Edge and kicked me out of my own house at gunpoint.... thankfully i got away with my tab 4... but it got stolen when i was homeless from being kicked out and living in my car...
So two devices stolen from me in less than a year, but hope was on the horizon. I had heard the note seven was coming out and so I stayed without a phone for three to four months and got the note seven the day it was released.
The note 7 is my trophy, it is my monument to not ever getting robbed again and then samsung wants to take it.
rkawli said:
would someone be kind enough to post a youtube video for those of us who are not so familiar with using ODIN
Thank You.
Click to expand...
Click to collapse
check youtube there are a lot of instructional vids. the process is the same for every ROM. you can download the ROM from sammobile.com firmware section. let me know if you can't figure it out still. I can try and help.
Hey all,
My phone updated today and ever since I cannot move past the initial lock screen. When unlocked, the UI appears to crash and send me back to the lock screen. My pin code works for turning the phone off, restarting the phone and putting it into emergency mode, which indicates some sort of UI crash.
Because this is a new account I can't post a link to a video of the issue directly, but the YouTube video code is: 8ZhlH-Tt-NU
I have tried the standard fixes like wiping the cache partition and booting into safe mode, but these don't seem to make any difference. Unfortunately I never logged into my Samsung account on this device, so their 'Find My Mobile' service is not an option. I am however signed into my Google account on the device and it does have wifi/network enabled.
The phone is running PPR1.180610.011/G965FXXU2CSA8
On the phones internal memory is a bunch of photos from a recent trip to Japan, I'm a fool for not backing these up sooner but I would hate to lose them.
Has anybody experienced anything like this before, and is there any way for me to get back into the phone, or atleast recover the photos that I took?
Thanks!
Edit:
One potential route out of this I can see is sideloading the same or a subsequent OTA update using ADB to hopefully fix the issue. Unfortunately despite some digging I can't find any updates that will allow installation from: PPR1.180610.011/G965FXXU2CSA8
If anybody has any information on this specific firmware version (Is it beta 3? beta 4? ect.), its installation path and where files relating to it may be listed/hosted it would be appreciated. Also how disasterous would it be to take a mismatched OTA upgrade and modify the metadata to allow it to be sideloaded onto the phone? I assume this would almost certainly break the OS completely but I'm not too sure.
You can try to flash your firmware again with ODIN, but with the HOME_CSC (Important!)
profi_fahrer said:
You can try to flash your firmware again with ODIN, but with the HOME_CSC (Important!)
Click to expand...
Click to collapse
Thanks for the reply Profi I had no idea using HOME_CSC would retain user data. I have tried flashing a few different versions of Pie (wish HOME_CSC) using Odin but with no luck, every time the phone boots I have the same problem. Do you know if there is a sure way to downgrade to Oreo while retaining user data? I have seen a few posts of people attemping this and getting stuck in bootloops, eventually requrining them to factory reset.
To give a final update on this. I attempted the Oreo downgrade, upon reboot the phone was stuck in a bootloop so I updated to Pie again. When the phone booted I tried the pin code as quickly as I could, and after some glitchy graphics on the screen it unlocked. From here I turn on the stay awake while plugged in feature in the developer options and managed to transfer all my data over to PC.
I don't believe it was the firmware changes that actually made any difference, because any further attempts to put my pin in, to remove the pin code for example, failed and cause the same crashing behaviour.
All data is recovered, I have factory reset the phone and all appears to be behaving as normal again. If anybody stumbles upon this with the same issue, all hope is not lost, but unfortunately I was unable to determine a realiable way to overcome it. It seems in this case it was just dumb luck.
Thanks for the assistance.
after using the dialer menu to update to .187 on my lya-09 i can no longer use face unlock. i deleted the stored faces to see if this would fix it and i can no longer even enroll my face, it just sits at the look directly at the screen part and never goes any further. any ideas?
even after a factory reset i still cannot enrol face. it recognises my face is there but does not prompt me to turn my head like it usually does. i have no idea why
What's the dialer menu update method?
Found it.
djisgod I'm sorry that I can't offer you any help, but if you please keep us posted abot your problem and eventual solution. Thx in advance
It's probably seeing the software as modified and not allowing you to use the secure face unlock feature. Or it's broken by the update which might be why they've delayed it.
I'm not sure it is very strange. Does anybody know which apk or app it is that does the face enrolling so i can try and install a different version?
i have done the update, and face unlock works without any problem for me, but i also have the lya-l29
still no luck with this. i have tried reset to factory settings and reinstalling the firmware. neither work.
and now it has suddenly started working again. lol not sure why it stopped but i am glad its back!
which update file have you used to update your phone?
describe exactly which file you've used to update via dialer menu AND even which model do you use?
I used the update for my phone the lya-09 c432. 9.0.0.187 update file. All is working fine now. Not sure what was going on but face unlock is now working again.