Before Christmas I tried to do a OTA update on my Prime, which has not been successful and I have not been able to use the Prime since.
It has previously been rooted and previously have always been successful in using Voodoo OTA Rootkeeper to retain root after updates. I've not unlocked the Prime.
Now when I try to boot it spends a while 'optimizing' the applications (as if it was the first time i've booted it since the update), and then once it is started, no apps will startup, all of them resulting in saying "unfortunately xyz has stopped"
A video of the problem: youtu.be/e1yfTtGiR78 (sorry can't post full link as am a new user).
I'd like to get it working again, possibly installing the Androwook ROM (or at the very least, just working on the stock rom). What steps do I need to do from where I am at the moment?
There are many threads about flashing roms, brick-fixing (some more up to date than others), but I'd just like a bit of advice about this problem and what I should do next (maybe some good links?). I haven’t gone near doing any flashing on the Prime, and it would be nice to seperate the things I could do, from the things I -should- do (I don't know where to start).
I believe as the Nvidida logo is on the bottom right this means I'm on the JB bootloader? Currently the settings menu shows I'm on android 4.1.1, but not sure if this is pre or post the failed update.
Thanks for any help,
Steve
A factory reset will fix you up. You'll lose your data
Hold vol down + power when booting to access the boatloader menu. Select wipe with vol down and use vol up to confirm.
Hi,
Thanks, I've done the reset, but I still seem to have the same problem.
imageshack.us/photo/my-images/502/imag0217c.jpg
I can't actually proceed throuh the inital set up, because it closes itself when it gets to the account setup page.
Any ideas?
I have resolved this.
I downloaded the latest firmware from the ASUS support website, extracted the zip file from within the downloaded zip file and renamed it to EP201_SDUPDATE.ZIP .
Put this on a microSD card (which I had formatted to FAT32), inserted it into the Prime, then booted into the bootloader menu.
Selected the RCK option, it did the update, and 10 minutes later it was up and running again.
From what I have read, it won't try to complete the update if it thinks you have already got that version installed already, but I guess it knew it hadn't successfully completed the update previously.
Glad it's working again.
Hi guys please help me i need to have my phone working back |:.... today i updated my wiko fever 4g but i got an error... now when i boot it an android icon shows with "no command." text. Tryed with v.39 program on wiko website but its not working for me... when arrow becomes green download wont start.
I'm thinking to recover system fom sd card but i cannot find roms please help me |: thanks in advance
Same issue here... Finally decided to upgrade the system from stock firmware, and got "error" when it rebooted the phone. Then "no command".
Darknezz89 said:
Hi guys please help me i need to have my phone working back |:.... today i updated my wiko fever 4g but i got an error... now when i boot it an android icon shows with "no command." text. Tryed with v.39 program on wiko website but its not working for me... when arrow becomes green download wont start.
I'm thinking to recover system fom sd card but i cannot find roms please help me |: thanks in advance
Click to expand...
Click to collapse
I solved my issue by restoring Lollipop (v.39) with the tool from the wiko website and then performing the update again; the phone started again (at v.41) and I was able to download Marshmallow from the next system update.
Issue was probably caused by some configuration or application.
Still slowly downloading Marshmallow now, so cannot say anything about the next update, but I guess that will go well, since the phone is reset now.
Just to follow up: Marshmallow is working fine on my Wiko Fever, much better than Lollipop. Amazing update.
Instructions for others after having read some comments from other people experiencing issues with the upgrade:
- BACKUP all your data before upgrading from Lollipop to Marshmallow, as if you would buy a new phone; I luckily did, as I wanted to set the microSD from removable to internal
- remove the microSD and (after having a backup of all your data as per step above) format the card as FAT32 on your PC; better to have a clean MicroSD card for after the upgrade I think
- reboot the phone in recovery mode and do a: wipe cache+reset to factory settings
- once the phone is reset and started, proceed with upgrading to Marshmallow
- don't know if needed after the upgrade to do an additional wipe cache+factory settings reset, doesn't harm to do it though
- be unhappy for the hours lost in restoring the phone data + apps + reconfigure everything
- be happy of the improved phone software
Questions upon questions.
So, i got the notification for the update last week, and i saved it until today to install it. The file downloaded was just 7 mb, i had enough battery for the intallation of the update (30% recomended by the software), something got messed up and an error message with the dead android character appeared. I know i lost all my things contacts and sd card... tried to hard reset the damn thing and nothing. I already googled the problem and i found nothing similar to what i get, i'm stuck in the recovery screen and the phone doenst shut down, every time i force it, it just boots back up after 15 30 seconds. I got to be honest i tought it was just another update but aparently its a "new" operating androind system. They could have told me with a update log or something...
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.
Last week on Thursday, I allowed Verizon to install their Software Update 21 (April 2020.) It made it as far as the going through the optimizing apps and then was stuck in a boot loop. The phone would be usable for about a minute, then would freeze, and then reboot. If I clicked on the System Update option in settings, it would say that a system update was in progress. I chatted with Verizon, and they ended up telling me that the only way to stop the update was to do a factory reset, which I am doing everything I can not to do that as I don't want to lose my data.
I changed it into maximum power mode and it did stop the update for that time being and I was able to use the phone, texting, etc. This allowed me to at least connect the phone to my computer to backup all of the directories. After many reboots, on Friday it finally stopped doing the update and gave me an error which I think was 410. It thought it was updated, though did show as failed. When checking for updates, it said it was the current version. Twice I was able to get the phone to stop by freezing when going to the app and stopping some programs (sadly, I was not able to remember the exact combination that worked) which allowed me to use the phone like normal. All this while, I was uninstalling a large amount of the apps that I had installed hoping that would minimize whatever may have been causing the problem.
Went to each of the google and samsung apps, stopped, disable, and reverted them all back to factory defaults. Guess that was a bad idea, from then on I received an error as soon as the phone started which caused it to go directly into recovery mode. I chatted with samsung and they thought it might be a hardware issue. I still think it is related to their software update, so not a hardware issue.
By using Odin, I loaded the firmware from March 2020, and when it rebooted, it did go as far as optimizing the apps, though anytime it booted up, it would never get past the white verizon loading screen. It took me hours before I discovered that Odin was failing to load the firmware on the phone as the Windows 10 laptop only had USB 3.0 ports which don't always work with Odin, and ended up being successful using my old Windows XP laptop as the USB 2.0 ports worked fine. After a bit hanging on the verizon loading screen, it would reboot and never went past. I have been able to load the March and April 2020, though none of them will ever get past that white verizon loading screen. I did see something say that in loading TWRP, I could possibly do a full backup of the phone which is what I would like to do.
One time I only loaded the AB file for a different version than I had loaded, and it was the first time it went beyond the white screen, only to tell me that the verification failed and it would need for me to do a factory reset. I was able to reboot the phone without actually doing the reset.
I have read many posts here and the forums on androidcentral, and with so many things, I really needed to post to get guidance from people here that can point me in the right direction for any other things that I can try. As you have read, doing everything that I can to get the phone working by keeping my data. Any help would really be appreciated.