Settings app missing after hard reset - Verizon Motorola Droid Turbo Q&A, Help & Troublesh

So I just did a hard reset on Verizon DT with Marshmallow and after booting and waiting for all the apps optimizing etc the default settings app is missing (and seems like some default widgets as well), nothing happens when I press the battery icon or the gear from the drawer, howeever all the moto bloat succesfully restored. Does anyone know if there is a way to fix it?

scipion_s said:
So I just did a hard reset on Verizon DT with Marshmallow and after booting and waiting for all the apps optimizing etc the default settings app is missing (and seems like some default widgets as well), nothing happens when I press the battery icon or the gear from the drawer, however all the moto bloat successfully restored. Does anyone know if there is a way to fix it?
Click to expand...
Click to collapse
Re-flash last full image which was released? That should reinstall everything. Just make sure it IS the most recent image, that you are not trying to "downgrade" or it will brick the phone if you have a locked bootloader. Even with unlocked you have to be carfult to omit gpt.bin from the flash commands.

Yup, already reflashing it, thx

ChazzMatt said:
Re-flash last full image which was released? That should reinstall everything. Just make sure it IS the most recent image, that you are not trying to "downgrade" or it will brick the phone if you have a locked bootloader. Even with unlocked you have to be carfult to omit gpt.bin from the flash commands.
Click to expand...
Click to collapse
one more questions please so that I don't start a new thread, is it possible to remove the bloat on marshmallow without installing custom rom? debloater doesn't work

scipion_s said:
one more questions please so that I don't start a new thread, is it possible to remove the bloat on marshmallow without installing custom rom? debloater doesn't work
Click to expand...
Click to collapse
You can debloat with titanium backup, but that requires bootloader unlock and root. But it's not custom ROM -- you would still be on rooted stock firmware.
If you're looking for ways to debloat without unlocking your bootloader, I'm not the one to ask. I always unlock my bootloader and root.
Sent via open market LG US998 V30/V30+

Related

HTC One Dev Editon ROOT?

Hi, I know it may have been foolish of me to get the Dev edition and im not a dev but it's unlocked, more storage and i think it was the better choice.
With that being said, is there a way to root this device permanently? I see there's an HTC One toolkit but it seems to be only for the ones with the Bootloader locked. This bootloader is unlocked so is there a thread yall can direct me to in order to root and flash a custom rom?
I'd appreciate it Folks
stepinmyworld said:
Hi, I know it may have been foolish of me to get the Dev edition and im not a dev but it's unlocked, more storage and i think it was the better choice.
With that being said, is there a way to root this device permanently? I see there's an HTC One toolkit but it seems to be only for the ones with the Bootloader locked. This bootloader is unlocked so is there a thread yall can direct me to in order to root and flash a custom rom?
I'd appreciate it Folks
Click to expand...
Click to collapse
you don't need to root it, just flash a recovery and then a custom rom and then you'll have a rooted device cause custom roms are all rooted
matt95 said:
you don't need to root it, just flash a recovery and then a custom rom and then you'll have a rooted device cause custom roms are all rooted
Click to expand...
Click to collapse
Thank you! Awesome
matt95 said:
you don't need to root it, just flash a recovery and then a custom rom and then you'll have a rooted device cause custom roms are all rooted
Click to expand...
Click to collapse
One more stupid question about Dev edition: will I be able to flash mods/apps from zip files using custom recovery, without rooting the phone/installing custom rooted ROM? There is a reason I don't want to root - my corporate mail will not work on rooted device, then I will need to use something like Voodoo OTA Root keeper and hide my root all the time, then restore it when I need, do what I need and after it I will need to re-install corporate email and re-enroll to company's server, in order to not get in trouble with company's Information Security, which I do not want.
I am not so interested in custom ROMs, but do interested in few mods and addons that will definitely come soon (e.g. separation of Ringtones sound level from Notification, battery charge percent on the battery icon in status bar, etc)
Thanks!
EugeneR said:
One more stupid question about Dev edition: will I be able to flash mods/apps from zip files using custom recovery, without rooting the phone/installing custom rooted ROM? There is a reason I don't want to root - my corporate mail will not work on rooted device, then I will need to use something like Voodoo OTA Root keeper and hide my root all the time, then restore it when I need, do what I need and after it I will need to re-install corporate email and re-enroll to company's server, in order to not get in trouble with company's Information Security, which I do not want.
I am not so interested in custom ROMs, but do interested in few mods and addons that will definitely come soon (e.g. separation of Ringtones sound level from Notification, battery charge percent on the battery icon in status bar, etc)
Thanks!
Click to expand...
Click to collapse
well i don't think so... if you do not want to be rooted you have to remain with the stock rom and i don't know if every mod is compatible with that
Root issues
matt95 said:
you don't need to root it, just flash a recovery and then a custom rom and then you'll have a rooted device cause custom roms are all rooted
Click to expand...
Click to collapse
I did the same. I just flashed CWM Touch Recovery and Superuser, but AdAway disables every time I reboot and I can't get rid of the Google Bloatware and FB/Twitter - which I don't use. I tried deleting them using ES File Explorer, but they come back every time I reboot. Please help. I hate having the bloatware and knowing that it takes up almost 150 MB makes me mad!!!
/system has kernel protection and you need to flash either a kernel or rom that disables it.
Ah!
gunnyman said:
/system has kernel protection and you need to flash either a kernel or rom that disables it.
Click to expand...
Click to collapse
Ah! I see. Do you know of any kernel that I can safely flash and not break my phone? It's only a week old and I don't want to end up bricking it or something. Also, do you know if I can still receive OTA updates from HTC? Whenever they do come out, that is. Sorry to be asking such a noob-ish question..
Also, is that the same reason AdAway gets auto-disabled at every boot?
Faux123 has a great kernel, and yes the hosts file gets reset for the same reason.
gunnyman said:
Faux123 has a great kernel, and yes the hosts file gets reset for the same reason.
Click to expand...
Click to collapse
Can you please tell me what the potential issues are, if I flash the kernel? Also, please let me know about the OTA updates and if it'll work after rooting and/or flashing a new kernel. Thank you!
Flash the kernel known as elemental X. It seems to have zero issues, I've been running it for a while now and the only difference is I am fully rooted with this kernel.AS far as OTA updates..
well whenever you unlock the bootloader at HTC's website it will definitely reset a non developer edition phone to factory defaults and from there it will remove calculator and a couple of other apps so that HTC knows you're no longer boot loader locked and yes this will prevent OTA updates.
since yours came with an unlocked bootloader in theory you could just flash the kernel and from there when you install SuperSU you will be able to do anything you need to do. With SuperSU you can temporarily turn off root so that you can do things that would normally be prevented/notice that you are rooted.
The Redbox streaming video service app is an example, it will not work on rooted devices but if you go in the SuperSU app and turn on temporary un-root. Then you are able to load the app, watch a show then close the app and restore root all without rebooting..
IIHomieII said:
Flash the kernel known as elemental X. It seems to have zero issues, I've been running it for a while now and the only difference is I am fully rooted with this kernel.AS far as OTA updates..
well whenever you unlock the bootloader at HTC's website it will definitely reset a non developer edition phone to factory defaults and from there it will remove calculator and a couple of other apps so that HTC knows you're no longer boot loader locked and yes this will prevent OTA updates.
since yours came with an unlocked bootloader in theory you could just flash the kernel and from there when you install SuperSU you will be able to do anything you need to do. With SuperSU you can temporarily turn off root so that you can do things that would normally be prevented/notice that you are rooted.
The Redbox streaming video service app is an example, it will not work on rooted devices but if you go in the SuperSU app and turn on temporary un-root. Then you are able to load the app, watch a show then close the app and restore root all without rebooting..
Click to expand...
Click to collapse
Thank you for allaying my fears. I flashed the faux123 kernel because it was suggested "first!" Working fine now. I rebooted and the apps haven't come back after uninstalling them. Thank you so so much for educating me!
PS: How do I Thank you officially? Is there some thank button on here?
---------- Post added at 01:19 AM ---------- Previous post was at 01:05 AM ----------
IIHomieII said:
Flash the kernel known as elemental X. It seems to have zero issues, I've been running it for a while now and the only difference is I am fully rooted with this kernel.AS far as OTA updates..
well whenever you unlock the bootloader at HTC's website it will definitely reset a non developer edition phone to factory defaults and from there it will remove calculator and a couple of other apps so that HTC knows you're no longer boot loader locked and yes this will prevent OTA updates.
since yours came with an unlocked bootloader in theory you could just flash the kernel and from there when you install SuperSU you will be able to do anything you need to do. With SuperSU you can temporarily turn off root so that you can do things that would normally be prevented/notice that you are rooted.
The Redbox streaming video service app is an example, it will not work on rooted devices but if you go in the SuperSU app and turn on temporary un-root. Then you are able to load the app, watch a show then close the app and restore root all without rebooting..
Click to expand...
Click to collapse
Thank button found and clicked!

[Q] 4.2.2 Root to 4.4 Root on AT&T

Okay, I am just wanting to clear things up for myself with this question. I've seen it similarly asked on other threads, but I have yet to find answer to them.
Currently, I am Stock + camera update + rooted with RockMyMoto. I haven't frozen or uninstalled or otherwise done anything to system apps or files (I disabled a few through Android itself before root, but never touched them since) I do use Permissions Denied; an app that does what it says for any app I chose, however I only use it for non-system apps. My phone is essentially stock, with root (bootloader locked). Thats all I want for whenever I update to 4.4 at the moment. Speaking of which...
I am trying to determine the best way to go about this. Since I havent done much to my phone, I am curious to know if I can just install the OTA (since I've altered no system files, but I know this isn't usually advised) then apply the latest root method done by jcase. Can it be as straight forward as that? Or do I absolutely need to flash back to STOCK stock, apply the camera update, the apply the 4.4 update, THEN use his method?
Trying to find a method that is at least safe. Preferably safe, quick and easy. But I know these methods aren't always quick .
NameLessThugZero said:
Okay, I am just wanting to clear things up for myself with this question. I've seen it similarly asked on other threads, but I have yet to find answer to them.
Currently, I am Stock + camera update + rooted with RockMyMoto. I haven't frozen or uninstalled or otherwise done anything to system apps or files (I disabled a few through Android itself before root, but never touched them since) I do use Permissions Denied; an app that does what it says for any app I chose, however I only use it for non-system apps. My phone is essentially stock, with root (bootloader locked). Thats all I want for whenever I update to 4.4 at the moment. Speaking of which...
I am trying to determine the best way to go about this. Since I havent done much to my phone, I am curious to know if I can just install the OTA (since I've altered no system files, but I know this isn't usually advised) then apply the latest root method done by jcase. Can it be as straight forward as that? Or do I absolutely need to flash back to STOCK stock, apply the camera update, the apply the 4.4 update, THEN use his method?
Trying to find a method that is at least safe. Preferably safe, quick and easy. But I know these methods aren't always quick .
Click to expand...
Click to collapse
Pawnymoto hijacks the stock recovery so you won't be able to install the update, you need to flash the stick recovery at the least
Sent on my Moto X
flashallthetime said:
Pawnymoto hijacks the stock recovery so you won't be able to install the update, you need to flash the stick recovery at the least
Sent on my Moto X
Click to expand...
Click to collapse
What do I need in order to do that, or should I just RSD lite back to a stock Moto X?
NameLessThugZero said:
What do I need in order to do that, or should I just RSD lite back to a stock Moto X?
Click to expand...
Click to collapse
I would say its safer to rsdlite back to 100% stock, that way you know everything is ready to accept the ota and you won't end up in a bootloop
Sent on my Moto X

Security Issues With Unlocking the Bootloader Without Rooting?

Does it present any security issues to unlock a bootloader without rooting? I don't mean if you lose your phone, I mean is there a security issue with any apps you install?
That's always a risk. Read playstore comments before installing anything.
Has nothing to do with being rooted or not...or boot loader state.
Sent from my Moto X cellular telephone...
Cozume said:
Does it present any security issues to unlock a bootloader without rooting? I don't mean if you lose your phone, I mean is there a security issue with any apps you install?
Click to expand...
Click to collapse
You could have asked at AC and I would answer it over there.
Unlocking bootloader and/or running custom recovery is a big risk. When you unlocked bootloader, all the partitions in your phone can be accessed and modified. I can flash custom recovery to your phone. Custom recovery give full root access to the phone. It is then easily possible to copy all your data from the phone and also disable the lock for your phone. Although if you encrypt your phone, then custom recovery will require the password to give access to the /data partition, which is where all the user datas are. I guess if someone is determine enough, then they can make an image copy of your phone and try to decrypt it.
If you want to keep your data safe, disable USB Debugging (because exploits can be used with ADB to gain access to the phone), use stock recovery and lock bootloader. However, if the phone brick then you can't get back your data in the phone.
eksasol said:
Unlocking bootloader and/or running custom recovery is a big risk. When you unlocked bootloader, all the partitions in your phone can be accessed and modified.
Click to expand...
Click to collapse
but can an app do this? And if so, what permissions would the app need to do this. Also, I am not talking about flashing a custom recovery; just an unlocked bootloader.
eksasol said:
If you want to keep your data safe, disable USB Debugging (because exploits can be used with ADB to gain access to the phone), use stock recovery and lock bootloader.
Click to expand...
Click to collapse
but can an app do harm to your phone if you have USB debugging enabled? I know a person who finds your phone can. I am asking about apps.
Cozume said:
but can an app do this? And if so, what permissions would the app need to do this. Also, I am not talking about flashing a custom recovery; just an unlocked bootloader.
Click to expand...
Click to collapse
If the phone isn't root, then probably not, unless there is some security holes it can exploit. With root it is possible to modify the whole system. Motorola and HTC have an extra layer to prevent simple root to modify the system partition, but as you can see, just visit dev section if you want to remove it.
but can an app do harm to your phone if you have USB debugging enabled? I know a person who finds your phone can. I am asking about apps.
Click to expand...
Click to collapse
It is possible for apps to get access to sensitive data and change system settings with USB Debugging enabled. Helium required it turned on to make backup of your contacts, sms and apps data for example.
If you have an older Android phone, you don't need to do anything except to enable USB Debugging and run a program to install root. But we're trusting apps like SuperUser and SuperSU to control apps access to root, so that's a layer of protection. But KitKat is much safer now.
You don't need root to install malware and virus to your phone. Just download an infected app or use unreliable app stores like Aptoide. Also if you have the option "Unknown sources" enabled, which almost all of us do, the app can utilize it to automatically install other apps in the background.
Point I'm trying to make is, if the phone have unlocked bootloader, or even locked bootloader with custom recovery, and someone else have a hold of it, then all bets are off.
eksasol said:
If the phone isn't root, then probably not, unless there is some security holes it can exploit. With root it is possible to modify the whole system.
Click to expand...
Click to collapse
great, that is what I want to know. I knew a human being in possession of your phone could do more damage if it were unlocked, which is why I got rid of the bootloader unlocked warning message.
BTW - do you know if flashing the original kit kat boot logo to replace the bootloader warning message presents a problem for accepting the OTA update to 4.4.2?
eksasol said:
Motorola and HTC have an extra layer to prevent simple root to modify the system partition, but as you can see, just visit dev section if you want to remove it.
Click to expand...
Click to collapse
Ok so then on my Moto X, since flashing a new logo doesn't even require root, it shouldn't have affected any system files and then it would be safe to take the OTA after removing the bootloader unlocked warning?
eksasol said:
It is possible for apps to get access to sensitive data and change system settings with USB Debugging enabled. Helium required it turned on to make backup of your contacts, sms and apps data for example.
Click to expand...
Click to collapse
good to know!
eksasol said:
But we're trusting apps like SuperUser and SuperSU to control apps access to root, so that's a layer of protection.
Click to expand...
Click to collapse
ok, that is how I understand it. Unless I give the app access to root through SuperSU, it can't.
eksasol said:
But KitKat is much safer now.
Click to expand...
Click to collapse
why is this?
eksasol said:
Also if you have the option "Unknown sources" enabled, which almost all of us do, the app can utilize it to automatically install other apps in the background.
Click to expand...
Click to collapse
thanks, Amazon app store required that to be enabled to load apps from their app store.
Cozume said:
great, that is what I want to know. I knew a human being in possession of your phone could do more damage if it were unlocked, which is why I got rid of the bootloader unlocked warning message.
Click to expand...
Click to collapse
BTW - do you know if flashing the original kit kat boot logo to replace the bootloader warning message presents a problem for accepting the OTA update to 4.4.2?
Ok so then on my Moto X, since flashing a new logo doesn't even require root, it shouldn't have affected any system files and then it would be safe to take the OTA after removing the bootloader unlocked warning?
Click to expand...
Click to collapse
That depend on the checking that the dev put in the OTA package. On the Nexus device, if you are missing any original system APK, modify the radio partition, modify GPS setting file, or modify the build.prop, etc, the OTA will fail. So I assume the same with Moto X OTA. The safest bet is to make sure all the partition are original first (except the /data partition where your data resides) before receiving an OTA.
ok, that is how I understand it. Unless I give the app access to root through SuperSU, it can't.
Click to expand...
Click to collapse
Yes. The actual component of root isn't the SuperSU app, but a 'su' binary. Without the SuperSU app, anything can have full fledged root access. You need SuperSU to control that access.
why is this?
Click to expand...
Click to collapse
For many reason, I'm not a developer so I can only talk about what I know and seen from a user perspective. It used to be that you can flash an exploited update.zip to modify the stock recovery of Android, in order to make it ignore the package signatures, so the recovery could flash any package without the correct signature. Now there are no such exploits for latest stock recovery. With USB Debugging enabled in Android 4.3 or newer, it would not even allow access when connected to a PC unless you accept to trust that PC in a pop up dialog in the phone, I'm not sure if it's mean the phone is totally invulnerable to exploits (like memory overflow), you'll have to ask someone smarter. Also apps like Framaroot that I just linked won't work anymore.
eksasol said:
That depend on the checking that the dev put in the OTA package. On the Nexus device, if you are missing any original system APK, modify the radio partition, modify GPS setting file, or modify the build.prop, etc, the OTA will fail. So I assume the same with Moto X OTA. The safest bet is to make sure all the partition are original first (except the /data partition where your data resides) before receiving an OTA. My guess is if you tried it with modified logo it will either fail or overwrite it.
Click to expand...
Click to collapse
OK, I think I am going to unroot and flash back to stock just to be sure.
Thanks again! I would hit the thanks button but I used up all my thanks today and it won't let me.
Cozume said:
OK, I think I am going to unroot and flash back to stock just to be sure.
Thanks again! I would hit the thanks button but I used up all my thanks today and it won't let me.
Click to expand...
Click to collapse
You already gave me enough thanks at AC.
eksasol said:
You already gave me enough thanks at AC.
Click to expand...
Click to collapse
what is your user name there?
Cozume said:
what is your user name there?
Click to expand...
Click to collapse
someguy
Why so paranoid? Have you read any posts on xda of such things....I haven't.
If you are sideloading apps the risk increases for sure. But apps on the play store would have tonnes of comments about it if the app was screwing up the system.
Sent from my Moto X cellular telephone...
eksasol said:
someguy
Click to expand...
Click to collapse
ok great!
kj2112 said:
Why so paranoid? Have you read any posts on xda of such things....I haven't.
If you are sideloading apps the risk increases for sure. But apps on the play store would have tonnes of comments about it if the app was screwing up the system.
Click to expand...
Click to collapse
I am just trying to understand how all of this works.
Okay one thing why are you trying to unlock the bootloader without rooting?? Or did I read everything wrong? And yes unlocking the bootloader allows you to write to every partition of the phone. Except when HTC and you're s-on you have to manually flash the boot.img via fastboot. But with moto. There is no point in unlocking the bootloader if you're not doing anything. Two it voids your warranty. Three it can disable functions on your phone like features, camera options I think and yeah etc. But if you follow instructions you won't have any problems ever rooting or shouldn't if you semi have a brain and know how to follow instructions if not well you can somewhat brick :$ I don't mess with moto much but I have. Sorry this thread was in my latest and scrolling through xda. Lol. You can unlock you're phone straight from the moto website. But if you're not rooting. Eh no point.
Sent from my Rezound using xda-developers app. CyanogenMod 11. S-off
I just read this thread, particularly page 2 why we can't relock the Motorola bootloader (yet it seems), unlike Nexus devices, I think it's really bad for security.
edit: link: http://forum.xda-developers.com/showthread.php?t=2575586&page=2
pball52998 said:
Okay one thing why are you trying to unlock the bootloader without rooting??
Click to expand...
Click to collapse
I rooted but a friend of mine is unlocked but not rooted. She wanted to be unlocked because it wipes your device so wanted to do it before she got the phone all set up. She is afraid of rooting. Anyhow, maybe she shouldn't have unlocked but she did.
pball52998 said:
There is no point in unlocking the bootloader if you're not doing anything. Two it voids your warranty.
Click to expand...
Click to collapse
She has the dev ed so it doesn't void her warranty. And she may want to Wifi tether in the future so I told her she needs to unlock and root for that so get the dev ed. She did and unlocked but is afraid to go any further.
pball52998 said:
You can unlock you're phone straight from the moto website. But if you're not rooting. Eh no point.
Click to expand...
Click to collapse
It increases the phone's resale value to unlock it.
eksasol said:
I just read this thread, particularly page 2 why we can't relock the Motorola bootloader (yet it seems), unlike Nexus devices, I think it's really bad for security.
Click to expand...
Click to collapse
I thought I saw a thread where someone could relock the Moto X bootloader.
And what about this?
Re-Lock Your Bootloader
It should just be a command like fastboot_oem_lock or something but idk. And two if she has the dev edition. Root that thing!!! XD that's what it's for!! Just install twrp via goo manager. Wipe factory reset all that good stuff. After making a back up. Notice after backing up. Then flashing rom and gapps In that order. I mean its a lot easier than htc rezound or htc one, htc in general and such lol.
Sent from my crappy apple iPad.....
pball52998 said:
Wipe factory reset all that good stuff. After making a back up.
Click to expand...
Click to collapse
well, I didn't wipe and do a factory reset when I rooted so I guess I did it wrong, lol! That is what she is afraid of - not doing it right and messing up her phone.
And I don't have a backup, but do I really need one if I can flash the factory images?

Is it safe to do a system update

I have a Droid Turbo that is currently on version 5.1 (23.21.44) and I just recently unfroze the system update notifications for my phone because of the news of MM. I am currently rooted and have an unlocked bootloader but I don't have TWRP installed and would rather not install it for now if I don't have to.
The system update that it is trying to push to my phone isn't MM, instead it is version 23.21.49.en.US. Is it safe to just take this update while being rooted and with an unlocked bootloader? I'm also not sure how many updates I'll have to make my way through before reaching the MM update, but if there are other updates, should it also be safe to go ahead with those as well? I know I could install TWRP and flash the MM ROM that way but I would prefer to do the updates officially if it is not risking a bricked phone.
Thanks for any advice.
EDIT: I forgot to finish the title of the thread...
AirJordanTS said:
I have a Droid Turbo that is currently on version 5.1 (23.21.44) and I just recently unfroze the system update notifications for my phone because of the news of MM. I am currently rooted and have an unlocked bootloader but I don't have TWRP installed and would rather not install it for now if I don't have to.
The system update that it is trying to push to my phone isn't MM, instead it is version 23.21.49.en.US. Is it safe to just take this update while being rooted and with an unlocked bootloader? I'm also not sure how many updates I'll have to make my way through before reaching the MM update, but if there are other updates, should it also be safe to go ahead with those as well? I know I could install TWRP and flash the MM ROM that way but I would prefer to do the updates officially if it is not risking a bricked phone.
Thanks for any advice.
EDIT: I forgot to finish the title of the thread...
Click to expand...
Click to collapse
It's safe, but it will be unsuccessful until you unroot your phone and undo any other system modifications that you've done (xposed, for example). There's a huge part of the update script that checks every single file in your system partition to make sure nothing has been modified.
Ok great, thanks.
The only other modification I can think that I've made is enabling mobile Hotspot through editing a setting somewhere. Do you know if that would be affected or would need changed back?
AirJordanTS said:
Ok great, thanks.
The only other modification I can think that I've made is enabling mobile Hotspot through editing a setting somewhere. Do you know if that would be affected or would need changed back?
Click to expand...
Click to collapse
You did that by modifying /system/build.prop. That change might be okay, but I would change it back if I were you just to be safe. The change is going to be overwritten anyway once the OTA is done.
AirJordanTS said:
Ok great, thanks.
The only other modification I can think that I've made is enabling mobile Hotspot through editing a setting somewhere. Do you know if that would be affected or would need changed back?
Click to expand...
Click to collapse
It's possible it may miss overlooking that. The worst that could happen was the update just doesn't take. It fails and nothing is changed. There is a pure MM official version that you can Flash in TWRP. It will update everything, radios and all, but will not relock the bootloader. I recommend you download Titanium Backup and backup all of your apps and their data to be restored after the update. A factory reset is recommended after the update. Also, don't forget to back up all of your photos, documents, music, etc. 24.81.5 is MM. Your update was a prep for MM.
Thanks for the advice guys.
I didn't realize it but I had TWRP installed so I decided to flash a stock ROM and proceed with the OTA updates from there. The problem currently is that I'm being locked out of my phone because of the Google "verify your account" page. I reset my account password on that page and now I'm not able to log in.

to unroot and restore S20FE

Hello,
As it is impossible for me to use some apps I would like to restore my S20FE as it was initially
I unrooted, reinitialized it but I still have, for some apps, pops up saying that firmware was modified and that app could not work
Is it possible to remove all specifi modification from my S20FE ( 781B, snapdragon version)
cbouillot said:
Hello,
As it is impossible for me to use some apps I would like to restore my S20FE as it was initially
I unrooted, reinitialized it but I still have, for some apps, pops up saying that firmware was modified and that app could not work
Is it possible to remove all specifi modification from my S20FE ( 781B, snapdragon version)
Click to expand...
Click to collapse
Use Odin to reflash the factory firmware, then lock the bootloader.
Depending on the apps you're having trouble with, you may be able to use Magisk modules to restore functionality while retaining root. See this thread. However, be aware that since Samsung likes to throw their own wrench into the works in the form of Knox Guard, Samsung specific apps that depend on Samsung specific security features may not work.
V0latyle said:
Use Odin to reflash the factory firmware, then lock the bootloader.
Depending on the apps you're having trouble with, you may be able to use Magisk modules to restore functionality while retaining root. See this thread. However, be aware that since Samsung likes to throw their own wrench into the works in the form of Knox Guard, Samsung specific apps that depend on Samsung specific security features may not work.
Click to expand...
Click to collapse
Hello
Thanks; would you have a procedure to recommend me to lock the bootloader ? Perhaps I failed at this step
cbouillot said:
Hello
Thanks; would you have a procedure to recommend me to lock the bootloader ? Perhaps I failed at this step
Click to expand...
Click to collapse
After you've used Odin to flash the original factory firmware, use the same process you used to unlock the bootloader; since the device is already unlocked, you will be prompted to lock it.
To unlock it, when i am on the screen "unlock bootloader" should I press yes (up) or no (down)
I just tried again with up
anyway to ckeck if bootloader it locked or not
EDIT: Ok , I tried again and it ask me if I want to lock it
That would mean that despite I resinstalled original firmware and loc the bootloader , it is detected as "modified"
I confirmed; it is locked with a samsung firmware but still not abble to install some apps
Any idea ?

Categories

Resources