Related
Trying to solve this for a friend.
We're on the pre-NE9 release and I used Towelroot to get the phone root. This was critical because we were migrating from an old S3 to the S5, so it was easier to use Titanium Backup to bring back the apps and savegame data.
Well it turns out my friend needs to run MDM Airwatch and Root cloak isn't working anymore. TBH there really isn't any reason to keep the phone rooted because it just makes OTA difficult too. So I think we're ready to go to an unrooted state.
So the first thing is we're struggling that even after doing a full unroot via SuperSU uninstalling Towelroot, it still doesn't pass MDM. So if anyone has a suggestion go ahead.
I'm not sure whats wrong but even then the OTA won't install either, so I'm suspecting the phone still finds something not in stock state.
So here's my question: Is it possible to install the OTA via Odin and ensure that the apps/data are not lost? I've heard that there's a lot of reasons OTAs can fail, so its more reliable to just use Odin to get the OTA applied. I figure that once we get the OTA updated, perhaps MDM will pass? If not we can always factory reset at that point.
bumpity
dmo580 said:
Trying to solve this for a friend.
We're on the pre-NE9 release and I used Towelroot to get the phone root. This was critical because we were migrating from an old S3 to the S5, so it was easier to use Titanium Backup to bring back the apps and savegame data.
Well it turns out my friend needs to run MDM Airwatch and Root cloak isn't working anymore. TBH there really isn't any reason to keep the phone rooted because it just makes OTA difficult too. So I think we're ready to go to an unrooted state.
So the first thing is we're struggling that even after doing a full unroot via SuperSU uninstalling Towelroot, it still doesn't pass MDM. So if anyone has a suggestion go ahead.
I'm not sure whats wrong but even then the OTA won't install either, so I'm suspecting the phone still finds something not in stock state.
So here's my question: Is it possible to install the OTA via Odin and ensure that the apps/data are not lost? I've heard that there's a lot of reasons OTAs can fail, so its more reliable to just use Odin to get the OTA applied. I figure that once we get the OTA updated, perhaps MDM will pass? If not we can always factory reset at that point.
Click to expand...
Click to collapse
You can't flash the OTA via Odin but you can sideload it by placing it on your ext-sdcard then sideloading from stock recovery. And by MDM I am assuming it's the modem that is not passing verification. Here is the G900V_NE9_Stock_Modem.tar.md5. Flash in PDA slot in Odin(AP in Odin v3.09+) then attempt to take the OTA again.
dmo580 said:
Trying to solve this for a friend.
We're on the pre-NE9 release and I used Towelroot to get the phone root. This was critical because we were migrating from an old S3 to the S5, so it was easier to use Titanium Backup to bring back the apps and savegame data.
Well it turns out my friend needs to run MDM Airwatch and Root cloak isn't working anymore. TBH there really isn't any reason to keep the phone rooted because it just makes OTA difficult too. So I think we're ready to go to an unrooted state.
So the first thing is we're struggling that even after doing a full unroot via SuperSU uninstalling Towelroot, it still doesn't pass MDM. So if anyone has a suggestion go ahead.
I'm not sure whats wrong but even then the OTA won't install either, so I'm suspecting the phone still finds something not in stock state.
So here's my question: Is it possible to install the OTA via Odin and ensure that the apps/data are not lost? I've heard that there's a lot of reasons OTAs can fail, so its more reliable to just use Odin to get the OTA applied. I figure that once we get the OTA updated, perhaps MDM will pass? If not we can always factory reset at that point.
Click to expand...
Click to collapse
go to google play
and download Helium - App Sync and Backup
options for rooted and non rooted try it i used it to backup a app data locally without gmail cloud on my rooted note3 and save the file did the same on my rooted s5 and had it Manuel restore that file just need to create the same file folder and drop the file in it if you do Manuel
so stupid i had passed a ton of level on chuchu rocket i didnt wanna redo
i also used this to do the sms altho helium may have done that for me too SMS Backup & Restore (Kitkat)
INFOLIFE LLC - February 25, 2014
Business
there is non kitkat and kitkat labeled one does it good just doesnt backup pics in the mms txts
This is driving me CRAZY!!!!!
I have installed a custom ROM (XtreStoLite) it has worked amazing, it was my first ever time to install a custom ROM so obviously I was having a good play around with all the tweaks etc, to where it started to slow my phone down a hell of a lot, I decided to do a fresh install of the custom ROM and everything went fine, it was until I was setting up my phone (logging in to google etc) and it asked me for the option of enabling "Reactivation lock", for SOME reason I agreed to it, knowing I shouldn't!!
anyway, this is where it all went abit wrong, I got stuck in a boot loop with the error "custom binary blocked by reactivation lock", after searching the whole internet I found the Odin "error" solution to gain access to my phone again.
My problem is, I don't seem to have an option in Settings > Security to turn off Reactivation Lock, it seems to be there in the search bar of settings, and it is checked but when I try to uncheck it, it takes me straight to the Security settings again.
I need to be able to disable option as I will not be able to access recovery mode otherwise, do you guys have any idea what I could possibly do? I have acess to a root explorer so I may be able to changed some values etc but I wouldn't know where to start to do that!!
Please guys, I'm struggling without my phone and my head feels like it will explode!!!
did you get anywhere with this? Having the same problem myself
I have the same issue, after having installed the same Rom. Now what?
It prevents me from recovery :/
Anyone already any ideas?
Downgrade to a stock KitKat ROM, log in with all accounts, disable reactivation lock > flash whatever you want after that, remember not to enable reactivation lock next time
Sorry to resurrect an old post, I managed to fix it and forgot the post the solution. quite easily actually.
Simply log onto your account via Samsung's web page and delete your account. This will then result to your lock being removed from the account and your phone being free of any errors! You might have to re-flash but it will fix any problems.
Sent from my SM-G900F using XDA Free mobile app
I'm having the same problem, I've deleted my Samsung account and reflashed a stock Rom but it just comes up asking me to enter my Samsung account details and I can't get any further than this screen.
Anything else I can try?
p5x said:
I'm having the same problem, I've deleted my Samsung account and reflashed a stock Rom but it just comes up asking me to enter my Samsung account details and I can't get any further than this screen.
Anything else I can try?
Click to expand...
Click to collapse
Just skip it, i've never had to log in.
Sent from my Tw5ted SM-G900A using Tapatalk
I don't seem to be able to skip it, how did you do it?
p5x said:
I don't seem to be able to skip it, how did you do it?
Click to expand...
Click to collapse
A button at the bottom that said skip, try just htting next without logging in and seeing if theres a way to skip it there.
Sent from my Tw5ted SM-G900A using Tapatalk
i can enter my phone , but i dont want to see this s... and im curiouse if i delete my account and it asks me again to sign in with the account what to do then?
If you delete your account, it'll ask you to sign in anyway. You just have to remake that account.
*** you will lose any purchased you've made with Samsung ***
Sent from my SM-G900F using XDA Free mobile app
Hi all,
A couple quick questions here. I've done some reading up, but most of the information is more in depth than I need at the moment so I'm looking for some quick answers.
My SO has a Verizon S5, that has a locked bootloader, is not rooted, and is still on 5.0.
She swapped carriers a while back, so is no longer on the Verizon network. The IMEI is clean, and her Verizon account is fully paid, and everything on the phone works fine, aside from it being stuck on 5.0.
It will not update via the automated system, because I assume it's trying to reach out to straight talk for the update and gets a response that it's on the newest version.
I downloaded the Verizon OTA update file (approximately 1 gb) for 6.0.1. It's named update.zip to allow for automated updating.
Here are my questions:
1. Would it be ok to just slap the update file on her phone and let it auto-update using the built in software?
2. Are there any major downsides to updating to marshmallow, considering it's an official release on the correct version of that phone?
3. Will root be needed prior (I'm assuming not) for using the OTA update file?
4. Will her information stay intact; email accounts, contacts, apps, samsung account, etc?
5. While root would be nice for locking down some of the bloatware after, it isn't a deal breaker, simplicity is the key here as she is not an advanced user, but would updating via the OTA file remove all possibilities of rooting the device after (it seems to be the impression I get, as her bootloader is locked)?
Thank you very much for your assistance!
Hi bladebarrier, I actually just did the same thing a few weeks ago with a used S5 from Verizon going to Straight Talk.
1. Would it be ok to just slap the update file on her phone and let it auto-update using the built in software?
I'm unsure if that would work, someone else may be able to answer as to that method, however I used the Odin tool v3.11.1, downloaded the PD1 image from here. There are some good video tutorials on YouTube and on writeups on this forum as well regarding how to flash the Marshmallow update using Odin.
2. Are there any major downsides to updating to marshmallow, considering it's an official release on the correct version of that phone?
No downsides that I've noticed and seems to have slightly better battery life.
3. Will root be needed prior (I'm assuming not) for using the OTA update file?
You do not need root to flash it if using the Odin tool.
4. Will her information stay intact; email accounts, contacts, apps, samsung account, etc?
Yes, but it's always a good idea to make a backup of everything.
5. While root would be nice for locking down some of the bloatware after, it isn't a deal breaker, simplicity is the key here as she is not an advanced user, but would updating via the OTA file remove all possibilities of rooting the device after (it seems to be the impression I get, as her bootloader is locked)?
The only thing that the locked boot loader affects for now is the ability to flash custom ROMs. I was able to downgrade to 5.0 Lollipop which you can still root, even after upgrading, however I decided to just go back to Marshmallow and wait for an exploit to be found, if one ever is.
jesimpki89 said:
Hi bladebarrier, I actually just did the same thing a few weeks ago with a used S5 from Verizon going to Straight Talk.
1. Would it be ok to just slap the update file on her phone and let it auto-update using the built in software?
I'm unsure if that would work, someone else may be able to answer as to that method, however I used the Odin tool v3.11.1, downloaded the PD1 image from here. There are some good video tutorials on YouTube and on writeups on this forum as well regarding how to flash the Marshmallow update using Odin.
2. Are there any major downsides to updating to marshmallow, considering it's an official release on the correct version of that phone?
No downsides that I've noticed and seems to have slightly better battery life.
3. Will root be needed prior (I'm assuming not) for using the OTA update file?
You do not need root to flash it if using the Odin tool.
4. Will her information stay intact; email accounts, contacts, apps, samsung account, etc?
Yes, but it's always a good idea to make a backup of everything.
5. While root would be nice for locking down some of the bloatware after, it isn't a deal breaker, simplicity is the key here as she is not an advanced user, but would updating via the OTA file remove all possibilities of rooting the device after (it seems to be the impression I get, as her bootloader is locked)?
The only thing that the locked boot loader affects for now is the ability to flash custom ROMs. I was able to downgrade to 5.0 Lollipop which you can still root, even after upgrading, however I decided to just go back to Marshmallow and wait for an exploit to be found, if one ever is.
Click to expand...
Click to collapse
Thank you very much for your thorough response. It sounds like it will be a nice smooth flash, and I will use the full Odin version instead of the OTA file, to ensure it goes through comfortably.
Odin looked like it wanted to wipe the apps, so I ended up using the stock recovery/installer that's built in, and placing the OTA update file on the external SD card.
That worked like a charm. It took a bit, as expected, but all of the apps and info were ok after.
The only thing I can't sort out is why I can't find an option for the "Themes" setting in touch wiz. Any suggestions? I realize I could have her go to a third party launcher, like nova, but I have all of the theme options on my note 3, that's ported to MM note 5, and the theme option is still right there in the settings list, per normal. Maybe I'm just not seeing it, but I couldn't find an option on her S5 during 5.0, or now on 6.0.1. Is that something they never updated for the older phones?
Quick, recap, I own a galaxy S5 Lolipop 5.1.1 SM-G900W8 build #LMY47X.G900W8VLU1COI4, previously rooted.
It all begin, when my phone been experiencing some battery draining issue. So I decide to do factory rest. But get this at that time my phone was fully rooted, w/Lolipop 5.1.1...
So I've read all the informations I could get online made sure to unroot the phone ( using CF-Auto Root ktlevl-sm G900W8.), with Odin, and reflash the phone with custom recory (G900W8VLU1COI4.tar.md5 file). I've made sure to get the exact one matching my phone carrier.
And after rooted the phone...All went well...Then 24-48 hours after the **** hit the fan.!!!!
They weere dialogue box keep poping up, from Touchwiz has closed, to Unified Daemond has closed just to name a few...
I decided to factory rest the phone again, reflash and rooted same problem occuring occuring.
So I decide not to root and the issue stop but now I'm unable to fully use my phone because it anin't root so certain function of my phone can't benefit such like using Airplane mode or Mobile data toggle using tasker. When my phone was fully rooted I was able to take full advantage of my Tasker profile. I've google the web and came acrros people who expericing the same issue as I did, but can't find a solution.
If there anyone who had that problem and manage to solve it, kindly share your story and solution with me....
Thank you in advance on getting back to me,
Hello fellow people of XDA!
Today I got an OTA update for my S7 edge (SM-G935F). The update has installed fairly fast (after the first reboot). But then, it got stuck on a decrypting loop. I have enabled prior the full phone encryption, and set it to ask for a password at each start. I entered the password correctly, as it said Starting Android... after, and since then, only the rotating padlock is showing. Every like 5 minutes the soft buttons are lighting up for a second, but then nothing is happening. After a while it even gets hot, but still nothing. I had this issue at the previous update too, but it started after like 30-40 minutes. Now 90 minutes have passed and still nothing.
I can reboot to the recovery and bootloader screens, and everything is fine. Knox not tripped, not rooted, everything official. In the recovery screen it says that my CSC is ECT (but according to sammobile it should be CNX).
Some additional info: samsung/hero2ltexx/hero2lte
7.0/NRD90M/G935FXXU2DRAG
I will try to flash a stock rom (PDA: G935FXXS2DRAA, CSC: G935FROM1DQJ3). If that doesn't work, I'll flash today's rom (PDA: same, CSC: G935FVFG1DQI1).
Any tips/help would be greately appreciated! Would not want to fall to the wipe data method, because I don't want to lose everything... But then again, I guess that would remove the boot password...
Thanks!
Update: After waiting for like 10+ hours, nothing has changed. Maybe I shouldn't have forced a reboot after an hour of the ota update? Going to try flashing the firmware now.
Update 2: I flashed the firmware, now the buttons seem to light up less often. But after an hour of decrypting, I guess the ultimate soultion would be to do a factory reset, since no one is helping...
jaszfalvi.tamas said:
Hello fellow people of XDA!
Today I got an OTA update for my S7 edge (SM-G935F). The update has installed fairly fast (after the first reboot). But then, it got stuck on a decrypting loop. I have enabled prior the full phone encryption, and set it to ask for a password at each start. I entered the password correctly, as it said Starting Android... after, and since then, only the rotating padlock is showing. Every like 5 minutes the soft buttons are lighting up for a second, but then nothing is happening. After a while it even gets hot, but still nothing. I had this issue at the previous update too, but it started after like 30-40 minutes. Now 90 minutes have passed and still nothing.
I can reboot to the recovery and bootloader screens, and everything is fine. Knox not tripped, not rooted, everything official. In the recovery screen it says that my CSC is ECT (but according to sammobile it should be CNX).
Some additional info: samsung/hero2ltexx/hero2lte
7.0/NRD90M/G935FXXU2DRAG
I will try to flash a stock rom (PDA: G935FXXS2DRAA, CSC: G935FROM1DQJ3). If that doesn't work, I'll flash today's rom (PDA: same, CSC: G935FVFG1DQI1).
Any tips/help would be greately appreciated! Would not want to fall to the wipe data method, because I don't want to lose everything... But then again, I guess that would remove the boot password...
Thanks!
Update: After waiting for like 10+ hours, nothing has changed. Maybe I shouldn't have forced a reboot after an hour of the ota update? Going to try flashing the firmware now.
Update 2: I flashed the firmware, now the buttons seem to light up less often. But after an hour of decrypting, I guess the ultimate soultion would be to do a factory reset, since no one is helping...
Click to expand...
Click to collapse
Wait, i dont get it, it is prompting you for a password even you didnt set it?
Sent from my S7 Edge using XDA Labs
shah22 said:
Wait, i dont get it, it is prompting you for a password even you didnt set it?
Sent from my S7 Edge using XDA Labs
Click to expand...
Click to collapse
I set a password when I enabled Secure Startup.
jaszfalvi.tamas said:
I set a password when I enabled Secure Startup.
Click to expand...
Click to collapse
Then use that same password, i think there is confusion, there is a password when you enable fingerprint and then a password when you enable secure startup. Be sure not to confuse them. If it still happens, then I guess there's got something wrong with the update, and only way is a factory reset. Btw, i also updated and i normally entered secure boot password and it started okay. Don't know what caused this for you.
Sent from my S7 Edge using XDA Labs
shah22 said:
Then use that same password, i think there is confusion, there is a password when you enable fingerprint and then a password when you enable secure startup. Be sure not to remember them. If it still happens, then I guess there got something wrong with the update, and only way is a factory reset. Btw, i also updated and i normally entered secure boot password and it started okay. Don't know what caused this for you.
Sent from my S7 Edge using XDA Labs
Click to expand...
Click to collapse
I entered the password correctly, as it stated "Starting Android..." then the rotating padlock took forever. More than 10 hours even. But in the end, a factory reset helped me. But rip my photos and memories...
Don't use device encryption anymore and leave OEM unlocking enabled in developer options.
Those two settings cause more hassle if you want to keep data, and make backups from time to time using Samsung Smart switch on computer. Use a microSD card to store and take all your photos from camera.
benjamen50 said:
Don't use device encryption anymore and leave OEM unlocking enabled in developer options.
Those two settings cause more hassle if you want to keep data, and make backups from time to time using Samsung Smart switch on computer. Use a microSD card to store and take all your photos from camera.
Click to expand...
Click to collapse
Right, but i use encryption and i could update without any problem, don't know what caused this issue with him. But one should backup all data BEFORE updating, as i did to save yourself from such hassle.
Sent from my S7 Edge using XDA Labs
benjamen50 said:
Don't use device encryption anymore and leave OEM unlocking enabled in developer options.
Those two settings cause more hassle if you want to keep data, and make backups from time to time using Samsung Smart switch on computer. Use a microSD card to store and take all your photos from camera.
Click to expand...
Click to collapse
Yeah, it's a sure thing I won't turn on Secure Stratup anymore. I don't know what OEM unlock does or does not, but right now, I don't have dev options enabled. If I had a microSD then I couldn't care less about resetting my phone, but since I don't have, because I have two SIM cards and a memory card has no place left, I feel bad.
Still, I don't know caused this issue. I had OTA updates before with full device encryption enabled and I had no issues before. I kinda used the same disk space at every OTA, so it should have took the same time... And I have to mention, that I did not tamper with the software. No root, no custom rom, and software only from the play store.
To enable developer options you click Build number 7 times which is located in the Software information tab in settings.
OEM unlock allows you to flash and boot the phone with custom binaries (Custom Recovery, Kernels, Roms). You can leave OEM unlock disabled if you don't want people that may steal your phone and use it for themselves.
With OEM unlock disabled and a google account signed in, it will block anyone from using the phone after a factory reset on stock Samsung firmware as it will prompt the user to enter the google account that was associated with that device.
Unfortunately there are rare cases that a OTA update may fail. Reflashing correct stock firmware usually fixes it but in worse case scenarios a factory reset will be required.
benjamen50 said:
To enable developer options you click Build number 7 times which is located in the Software information tab in settings.
OEM unlock allows you to flash and boot the phone with custom binaries (Custom Recovery, Kernels, Roms). You can leave OEM unlock disabled if you don't want people that may steal your phone and use it for themselves.
With OEM unlock disabled and a google account signed in, it will block anyone from using the phone after a factory reset on stock Samsung firmware as it will prompt the user to enter the google account that was associated with that device.
Unfortunately there are rare cases that a OTA update may fail. Reflashing correct stock firmware usually fixes it but in worse case scenarios a factory reset will be required.
Click to expand...
Click to collapse
Never had OEM unlock enabled, because I didn't know what is does, so thanks for the info. I reflashed the correct stock firmware, but that didn't help either, so I had to resort to wiping the data... Regarding this, do you know by any chance a good software for recovering data without root?
I don't know of any unfortunately, if anyone has any good paid ones that actually work please post here.