Related
[solved, see 5th post]
my tablet was rooted, then i uninstalled some system apps, but i figured out some features won't work, so i unrooted, and did a factory reset, now all system apps are gone,
i thought a factory reset will restore it back to the original stock with all system apps no matter that i uninstalled them. now i can't even go to settings->accounts and syncs, it force closes, i guess i uninstalled an app that manage accounts,
is there a way to go back to stock with all system apps without unlocking bootloader, i don't want to do that.
i also do not have any knowledge about unlocking,flashing,roms,...
or can i just reinstall all system apps and do a factory reset, then it will be fine? (but i don't have backups of those system apps)
i'm on firmware .30 ICS
now i just want a clean system, i don't want it to be messed up like this
After researching i found that factory reset does not restore system apps, so no surprise here.
now i have 2 ways to have a "fresh/clean" system:
1. root and copy all missing system apks to /system/app. But can i root now (using the 1 click transformer root tool) because i uninstalled many system apps and i don't know what they are, can this affect the root?
if this way is ok, can someone on firmware .30 ICS please upload all the files in /system/app. Thanks a lot.
2. flash the stock rom. but i don't want to unlock bootloader, (i don't want to void warranty), how can i flash the stock rom? (and where can i download the stock rom .30 ICS? is it the .zip file on asus support website?) i heard some people say "you can flash a STOCK rom with a locked bootloader" but in another device, not tf300.
i think this way is best because it restores everything, which is what i want, i'm hoping i can do this without unlocking my bootloader.
I guess if i can solve this problem, from now i will never delete any system apps. if i knew factory reset does not restore system apps i did not uninstall them . but it just does not make sense, it's called "factory reset", so shouldn't restore to "factory" state?
Please help. Thank you.
nooktablet said:
After researching i found that factory reset does not restore system apps, so no surprise here.
now i have 2 ways to have a "fresh/clean" system:
1. root and copy all missing system apks to /system/app. But can i root now (using the 1 click transformer root tool) because i uninstalled many system apps and i don't know what they are, can this affect the root?
if this way is ok, can someone on firmware .30 ICS please upload all the files in /system/app. Thanks a lot.
2. flash the stock rom. but i don't want to unlock bootloader, (i don't want to void warranty), how can i flash the stock rom? (and where can i download the stock rom .30 ICS? is it the .zip file on asus support website?) i heard some people say "you can flash a STOCK rom with a locked bootloader" but in another device, not tf300.
i think this way is best because it restores everything, which is what i want, i'm hoping i can do this without unlocking my bootloader.
I guess if i can solve this problem, from now i will never delete any system apps. if i knew factory reset does not restore system apps i did not uninstall them . but it just does not make sense, it's called "factory reset", so shouldn't restore to "factory" state?
Please help. Thank you.
Click to expand...
Click to collapse
If you are on ICS you can still root using the debugfs method aka the one click.
Yes you can still download the firmware from Asus. You can try to put the zip within the zip into /sdcard and see if it installs it full but not sure if that would replace the system apps. I don't think there would be harm trying it.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
funnel71 said:
If you are on ICS you can still root using the debugfs method aka the one click.
Yes you can still download the firmware from Asus. You can try to put the zip within the zip into /sdcard and see if it installs it full but not sure if that would replace the system apps. I don't think there would be harm trying it.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
ok, i think i'll go the rooting way.
so can someone on .30 ICS please upload ALL the files in system/app? i need all of them because i don't know what files i deleted and what i did not delete.
Thank you a lot.
UPDATE: Problem solved.
i downloaded .30 firmware from asus website, did a manual update, after updating it restored the system apps. so it solved the problem. thanks funnel71.
to get a "clean" system i did a factory reset, now back to the beginning lol.
so when you accidentally (or purposely) delete system apps, just do a manual update and it will restore, make sure to download the right firmware.
*NOTE: I tried to update my XT1575 Moto-X Pure Edition from a file on this page and it was a disaster! I now have the OTA visible on my phone, see screenshot, that keeps popping up. My phone is currently rooted, unlocked, and has TWRP installed, all courtesy of WinDroid tool. Windroid was painless, easy, and got the job done pretty quickly. Now that I can take the OTA update, is there an instruction page somewhere showing how to take the upgrade and keep root and recovery TWRP? That is the gist of what I really need.
I have a new Motorola Moto-X Pure Edition, rooted and TWRP with WinDroid app from Windows. This made it incredibly easy to unlock bootloader, install TWRPm and root. I am very happy with this system and some Xposed modules. I heard all the hoopla about the new Marshmallow rollout but did not have it offered to me on this phone. So, I did it manually from this page:
Stock/Rooted/Debloated X1575 6.0 MPH24.49-18
So much to choose from so I downloaded the moto_x_pure_edition_rooted_x1575_mph24.49-18_v1-deodexed.zip and flashed it in TWRP, after making a nandroid backup in TWRP. Everything seemed to work fine but I had problems after problems. My 32 GB ext-sdcard "vanished" and the system insisted that I reformat the card as "Portable" or "Permanent". I chose portable. I could not get Xposed working properly. My password manager would not work, when I updated from the play store, I got the message that all Android 6 apps now require a password at first run. Huh? What password? None of the passwords I have for the password managers would open the app.
Before losing 30+ GB of data on my ext-sdcard, I copied it to PC, then when complete I put it back in the phone, allowed the format as portable, then pulled the card and restored my stuff. Nothing was working right and it was pretty scary as this is my only phone. I restored the TWRP backup and had some settling in issues, but it worked, all but for WiFi. I could not turn it on! Like a spring on the switch, the moment you switched on WiFi, it snapped right back to the OFF position. No more WiFi. A friend sent me a stock recovery zip file, CLARK_RETUS_5.1.1_LPH23.116-18_cid9_subsidy-DEFAULT_CFC.xml_SHAWN5162.zip.
This file, once unzipped, will flash the entire phone back to stock. He send me a small modem-flash.bat file because he thinks that I have an Android 6 radio in an Android 5 device. After running the flash-modem.bat, I got my WiFi back.
flash-modem.bat
Code:
@ECHO Off
@Echo Test
C:\adt-bundle-windows-x86_64-20140702\sdk\platform-tools\adb reboot bootloader
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
.fastboot reboot
Now I am really, really gun shy. I now have the dreaded update message on my phone, see screenshot. I found some good instructions here:
[GUIDE] Unlock/Root/Flash for Moto X Style/Pure
Are these instructions safe if I take the OTA update?
What preparations should be made prior to taking OTA aside from a TWRP backup?
Must I really format my ext-sdcard to use Marshmallow?
What other kind of weird things will happen?
Thank you so much, scared "sheetless in Florida"
:
Ohmster said:
*NOTE: I tried to update my XT1575 Moto-X Pure Edition from a file on this page and it was a disaster! I now have the OTA visible on my phone, see screenshot, that keeps popping up. My phone is currently rooted, unlocked, and has TWRP installed, all courtesy of WinDroid tool. Windroid was painless, easy, and got the job done pretty quickly. Now that I can take the OTA update, is there an instruction page somewhere showing how to take the upgrade and keep root and recovery TWRP? That is the gist of what I really need.
I have a new Motorola Moto-X Pure Edition, rooted and TWRP with WinDroid app from Windows. This made it incredibly easy to unlock bootloader, install TWRPm and root. I am very happy with this system and some Xposed modules. I heard all the hoopla about the new Marshmallow rollout but did not have it offered to me on this phone. So, I did it manually from this page:
Stock/Rooted/Debloated X1575 6.0 MPH24.49-18
So much to choose from so I downloaded the moto_x_pure_edition_rooted_x1575_mph24.49-18_v1-deodexed.zip and flashed it in TWRP, after making a nandroid backup in TWRP. Everything seemed to work fine but I had problems after problems. My 32 GB ext-sdcard "vanished" and the system insisted that I reformat the card as "Portable" or "Permanent". I chose portable. I could not get Xposed working properly. My password manager would not work, when I updated from the play store, I got the message that all Android 6 apps now require a password at first run. Huh? What password? None of the passwords I have for the password managers would open the app.
Before losing 30+ GB of data on my ext-sdcard, I copied it to PC, then when complete I put it back in the phone, allowed the format as portable, then pulled the card and restored my stuff. Nothing was working right and it was pretty scary as this is my only phone. I restored the TWRP backup and had some settling in issues, but it worked, all but for WiFi. I could not turn it on! Like a spring on the switch, the moment you switched on WiFi, it snapped right back to the OFF position. No more WiFi. A friend sent me a stock recovery zip file, CLARK_RETUS_5.1.1_LPH23.116-18_cid9_subsidy-DEFAULT_CFC.xml_SHAWN5162.zip.
This file, once unzipped, will flash the entire phone back to stock. He send me a small modem-flash.bat file because he thinks that I have an Android 6 radio in an Android 5 device. After running the flash-modem.bat, I got my WiFi back.
flash-modem.bat
Code:
@ECHO Off
@Echo Test
C:\adt-bundle-windows-x86_64-20140702\sdk\platform-tools\adb reboot bootloader
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
.fastboot reboot
Now I am really, really gun shy. I now have the dreaded update message on my phone, see screenshot. I found some good instructions here:
[GUIDE] Unlock/Root/Flash for Moto X Style/Pure
Are these instructions safe if I take the OTA update?
What preparations should be made prior to taking OTA aside from a TWRP backup?
Must I really format my ext-sdcard to use Marshmallow?
What other kind of weird things will happen?
Thank you so much, scared "sheetless in Florida"
:
Click to expand...
Click to collapse
Two points:
1. You can never ever ever take any OTA with a custom recovery (TWRP) installed. You MUST flash stock recovery prior to taking the OTA.
2. The update will fail if you have made ANY modifications to /system. This includes using TWRP to flash SuperSu to your device.
So if you just do a complete FULL return to stock and have a working lollipop installation, DO NOT INSTALL TWRP OR INSTALL SUPERSU. Take the OTA update. Afterwards you are free to go ahead and flash TWRP. I recommend IMMEDIATELY making a nandroid backup once you have taken the OTA and flashed TWRP.
I also suggest using the new "systemless root" method instead of the traditional root method. If you use systemless root, you won't need to restore /system (as long as you didn't modify it by flashing Xposed, Adaway, or similar. If a future OTA comes out with systemless root, you simply flash the stock kernel (which will unroot you), then accept the new update, then modify the boot image again to re-gain root.
To sum it up: *IF* you are 100% stock on lollipop (no TWRP, no SuperSU), you can go ahead and take the OTA. Afterwards, you can do whatever you would like (flash TWRP, SuperSU, etc). Just keep in mind that if you don't use the new systemless root, you will have to do a full return to stock AGAIN the next time an OTA comes out.
Good Luck.
Hi Ohmster. Hope you are well. I experienced the exact same "mess" as you have. In fact, I had the identical setup (Lollipop, TWRP, Nova, etc.). I tried the FLASH-ALL approach multiple times as well as separate reflash of the modem included in the CLARK_RETUS zip (followed steps line by line). But I'm still stuck without wifi (slides back to "off" immediately). prior to all this, I did a factory wipe as well as subsequent "fastboot -w". Any ideas? I'm on day 3 without a phone Thanks in advance for your wisdom!!
nypeach said:
Hi Ohmster. Hope you are well. I experienced the exact same "mess" as you have. In fact, I had the identical setup (Lollipop, TWRP, Nova, etc.). I tried the FLASH-ALL approach multiple times as well as separate reflash of the modem included in the CLARK_RETUS zip (followed steps line by line). But I'm still stuck without wifi (slides back to "off" immediately). prior to all this, I did a factory wipe as well as subsequent "fastboot -w". Any ideas? I'm on day 3 without a phone Thanks in advance for your wisdom!!
Click to expand...
Click to collapse
Hi Ohmster. Seems that your "positive mojo" did the trick... I tried one more time and finally up and running. Thanks for your posts and wisdom!!!
samwathegreat said:
Two points:
1. You can never ever ever take any OTA with a custom recovery (TWRP) installed. You MUST flash stock recovery prior to taking the OTA.
2. The update will fail if you have made ANY modifications to /system. This includes using TWRP to flash SuperSu to your device.
So if you just do a complete FULL return to stock and have a working lollipop installation, DO NOT INSTALL TWRP OR INSTALL SUPERSU. Take the OTA update. Afterwards you are free to go ahead and flash TWRP. I recommend IMMEDIATELY making a nandroid backup once you have taken the OTA and flashed TWRP.
I also suggest using the new "systemless root" method instead of the traditional root method. If you use systemless root, you won't need to restore /system (as long as you didn't modify it by flashing Xposed, Adaway, or similar. If a future OTA comes out with systemless root, you simply flash the stock kernel (which will unroot you), then accept the new update, then modify the boot image again to re-gain root.
To sum it up: *IF* you are 100% stock on lollipop (no TWRP, no SuperSU), you can go ahead and take the OTA. Afterwards, you can do whatever you would like (flash TWRP, SuperSU, etc). Just keep in mind that if you don't use the new systemless root, you will have to do a full return to stock AGAIN the next time an OTA comes out.
Good Luck.
Click to expand...
Click to collapse
Do you think it would work if I did a Full Unroot using SuperSU and then uninstalled it using TiBu. Then flashed stock recovery using the restore to stock tool. So at that point I would have unrooted, removed SuperSu, and flashed back the stock recovery image. Do you think this would do the trick, or is it just best to completely flash the entire device using the restore to stock tool in full. I can recover from a soft brick but don't want a complete brick. Do you think my method is worth a try and that it wouldn't cause a complete brick condition? I would like to not have to reset my phone completely, but will if that is the only best way to get onto MM. Thanks.
nypeach said:
Hi Ohmster. Seems that your "positive mojo" did the trick... I tried one more time and finally up and running. Thanks for your posts and wisdom!!!
Click to expand...
Click to collapse
Actually my XT1575 is running and is in good shape now. I was lucky, @OldBaldy got on Hangouts with me and walked me through it. He sent me a large file which I believe to be the original stock rom for the Moto-X with a flash.bat file in so as long as you have your Windows drivers installed with ADB and Fastboot working. It took me the entire night to get that working with the correct drivers because Baldy had to go to bed.
The file I really needed for this is a 1.27 GB file, CLARK_RETUS_5.1.1_LPH23.116-18_cid9_subsidy-DEFAULT_CFC.xml_SHAWN5162.zip. He told me NOT to run the FLASH-ALL.bat inside because all he wanted to do was reset the WiFi radio from an Android 6 radio to an Android 5 radio. Baldy was really smart and edited the restore system bat file to a tiny little "StockROM_FlashModem.txt" and it worked! WiFi came right back!
After that, I had to use adb over USB to flash the system back to original lollipop with no root, take the OTA update, then flash the boot.image file, update done, then flash the boot.img before installing SuperSU and most of this we did with ADB over USB. You cannot flash BETA-SuperSU-v2.52.zip until you flash that boot.img file.
If I was smart, I would have copy/pasted all the adb stuff we did into a text file, but of course, I didn't. But yes it is all working quite well now.
BEWARE:
Xposed does work in MM but not everything. I had to go back to TWRP, remove Xposed, and then enable only a couple of them that I know are safe like AdBlocker and Greenify.
I cannot give you anymore details since I screwed it up myself a couple of times and ended up redoing it on my own and again with Baldy's help.
NOTE:
Baldy did want something out of all this help he was giving me, he wanted the very first nandroid TWRP backup system files that I made immediately as soon as I got the update done because that is a perfectly clean backup and if you ever wanted to put your phone back to stock, that backup would do it.
Before giving up on Xposed and being sure that this was lousing up my phone; self boots, black screen, would not boot, bootloop, etc., I finally realized that this phone actually WORKS, man. It has to be the Xposed files,and modules that are causing the problems. And after removing all but the 2 I mentioned, the phone works great now. I will add more modules, very, very slowly and test each one for a couple of days before I clear it and dare add another one.
Ohmster said:
Actually my XT1575 is running and is in good shape now. I was lucky, @OldBaldy got on Hangouts with me and walked me through it. He sent me a large file which I believe to be the original stock rom for the Moto-X with a flash.bat file in so as long as you have your Windows drivers installed with ADB and Fastboot working. It took me the entire night to get that working with the correct drivers because Baldy had to go to bed.
The file I really needed for this is a 1.27 GB file, CLARK_RETUS_5.1.1_LPH23.116-18_cid9_subsidy-DEFAULT_CFC.xml_SHAWN5162.zip. He told me NOT to run the FLASH-ALL.bat inside because all he wanted to do was reset the WiFi radio from an Android 6 radio to an Android 5 radio. Baldy was really smart and edited the restore system bat file to a tiny little "StockROM_FlashModem.txt" and it worked! WiFi came right back!
After that, I had to use adb over USB to flash the system back to original lollipop with no root, take the OTA update, then flash the boot.image file, update done, then flash the boot.img before installing SuperSU and most of this we did with ADB over USB. You cannot flash BETA-SuperSU-v2.52.zip until you flash that boot.img file.
If I was smart, I would have copy/pasted all the adb stuff we did into a text file, but of course, I didn't. But yes it is all working quite well now.
BEWARE:
Xposed does work in MM but not everything. I had to go back to TWRP, remove Xposed, and then enable only a couple of them that I know are safe like AdBlocker and Greenify.
I cannot give you anymore details since I screwed it up myself a couple of times and ended up redoing it on my own and again with Baldy's help.
NOTE:
Baldy did want something out of all this help he was giving me, he wanted the very first nandroid TWRP backup system files that I made immediately as soon as I got the update done because that is a perfectly clean backup and if you ever wanted to put your phone back to stock, that backup would do it.
Before giving up on Xposed and being sure that this was lousing up my phone; self boots, black screen, would not boot, bootloop, etc., I finally realized that this phone actually WORKS, man. It has to be the Xposed files,and modules that are causing the problems. And after removing all but the 2 I mentioned, the phone works great now. I will add more modules, very, very slowly and test each one for a couple of days before I clear it and dare add another one.
Click to expand...
Click to collapse
Hi Ohmster. Thanks again. So are you on Marshmallow? I got back with your info above and back to 5.1.1 (CLETUS). I tried to take the OTA and it downloaded, went to install, and I watched it just say "error" while on the installation screen. I'm going to try again. Let me know if you all set or in the same boat Thanks again!
samwathegreat said:
Two points:
1. You can never ever ever take any OTA with a custom recovery (TWRP) installed. You MUST flash stock recovery prior to taking the OTA.
2. The update will fail if you have made ANY modifications to /system. This includes using TWRP to flash SuperSu to your device.
So if you just do a complete FULL return to stock and have a working lollipop installation, DO NOT INSTALL TWRP OR INSTALL SUPERSU. Take the OTA update. Afterwards you are free to go ahead and flash TWRP. I recommend IMMEDIATELY making a nandroid backup once you have taken the OTA and flashed TWRP.
I also suggest using the new "systemless root" method instead of the traditional root method. If you use systemless root, you won't need to restore /system (as long as you didn't modify it by flashing Xposed, Adaway, or similar. If a future OTA comes out with systemless root, you simply flash the stock kernel (which will unroot you), then accept the new update, then modify the boot image again to re-gain root.
To sum it up: *IF* you are 100% stock on lollipop (no TWRP, no SuperSU), you can go ahead and take the OTA. Afterwards, you can do whatever you would like (flash TWRP, SuperSU, etc). Just keep in mind that if you don't use the new systemless root, you will have to do a full return to stock AGAIN the next time an OTA comes out.
Good Luck.
Click to expand...
Click to collapse
nypeach said:
Hi Ohmster. Thanks again. So are you on Marshmallow? I got back with your info above and back to 5.1.1 (CLETUS). I tried to take the OTA and it downloaded, went to install, and I watched it just say "error" while on the installation screen. I'm going to try again. Let me know if you all set or in the same boat Thanks again!
Click to expand...
Click to collapse
Did you get back to stock using CLARK_RETUS_5.1.1_LPH23.116-18_cid9_subsidy-DEFAULT_CFC.xml_SHAWN5162.zip? I have still not gone through the process yet as I am concerned about messing up the process. I want to ask a few questions here. I am well accustomed to fastboot flashing but want to be exactly sure of what to flash and the reason for doing it. I am on stock 5.1.1 LP with bootloader unlocked and rooted with SuperSU. So first I need to use Shawn5162's zip to restore me back to complete stock without root, then I need to go in and setup the phone to at least get the MM OTA, then install the OTA and hope all goes well. Lastly, to root again I need to use Shawn5162's zip to flash boot.img only, then flash TWRP, and finally flash SuperSU again. Is all this correct? Thank you.
robn30 said:
Did you get back to stock using CLARK_RETUS_5.1.1_LPH23.116-18_cid9_subsidy-DEFAULT_CFC.xml_SHAWN5162.zip? I have still not gone through the process yet as I am concerned about messing up the process. I want to ask a few questions here. I am well accustomed to fastboot flashing but want to be exactly sure of what to flash and the reason for doing it. I am on stock 5.1.1 LP with bootloader unlocked and rooted with SuperSU. So first I need to use Shawn5162's zip to restore me back to complete stock without root, then I need to go in and setup the phone to at least get the MM OTA, then install the OTA and hope all goes well. Lastly, to root again I need to use Shawn5162's zip to flash boot.img only, then flash TWRP, and finally flash SuperSU again. Is all this correct? Thank you.
Click to expand...
Click to collapse
That is the correct firmware. You don't need to remove anything. All you need to do is flash recovery and system, reboot and take the OTA. Make sure you have the new TWRP ( 2.8.7.1 ) downloaded, the 2.8.7.0 won't work with the new bootloader. I used the modified boot image and supersu 2.52 because I did not care about modifying the system partition. You can use Supersu 2.62 for systemless root if you wish. If you're planning to use Xposed, then systemless gives you no added benefits.
Always, before starting something like this, make a nandroid!
Sent from my XT1575 using Tapatalk
OldBaldy said:
That is the correct firmware. You don't need to remove anything. All you need to do is flash recovery and system, reboot and take the OTA. Make sure you have the new TWRP ( 2.8.7.1 ) downloaded, the 2.8.7.0 won't work with the new bootloader. I used the modified boot image and supersu 2.52 because I did not care about modifying the system partition. You can use Supersu 2.62 for systemless root if you wish. If you're planning to use Xposed, then systemless gives you no added benefits.
Always, before starting something like this, make a nandroid!
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
So, I couldn't wait and already did it. I flashed Shawn5162's file in full. Then I took the OTA and updated perfectly. I have already installed TWRP 2.8.7.1 and made a nandroid of my Stock unrooted MM ROM. Now I want to root but want to make sure I understand this step perfectly. Which boot.img do I use? The ones in this thread http://forum.xda-developers.com/moto-x-style/general/root-moto-x-style-xt1572-br-marshmallow-t3259380? The boot.img in that thread is way smaller than the one in Shawn5162's LL zip tool. Just want to be sure I am doing this correctly. Lastly am I using the SU file in that thread as well and following those exact directions? Thanks.
robn30 said:
So, I couldn't wait and already did it. I flashed Shawn5162's file in full. Then I took the OTA and updated perfectly. I have already installed TWRP 2.8.7.1 and made a nandroid of my Stock unrooted MM ROM. Now I want to root but want to make sure I understand this step perfectly. Which boot.img do I use? The ones in this thread http://forum.xda-developers.com/mot...t-moto-x-style-xt1572-br-marshmallow-t3259380? The boot.img in that thread is way smaller than the one in Shawn5162's LL zip tool. Just want to be sure I am doing this correctly. Lastly am I using the SU file in that thread as well and following those exact directions? Thanks.
Click to expand...
Click to collapse
That boot img is for style only, not for pure. There is another called boot_root_mm_clark_retus.zip
Search for that file, it's the one you need for Supersu 2.5.2
You can use either supersu 252 of 256. I used 252 and have had no problems. If you have flashed TWRP, just put the supersu of your choice and the boot_root.zip files on you phone and flash with TWRP.
Sent from my XT1575 using Tapatalk
OldBaldy said:
That is the correct firmware. You don't need to remove anything. All you need to do is flash recovery and system, reboot and take the OTA. Make sure you have the new TWRP ( 2.8.7.1 ) downloaded, the 2.8.7.0 won't work with the new bootloader. I used the modified boot image and supersu 2.52 because I did not care about modifying the system partition. You can use Supersu 2.62 for systemless root if you wish. If you're planning to use Xposed, then systemless gives you no added benefits.
Always, before starting something like this, make a nandroid!
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
IGNORE ME My Bad.... Back at 5.1.1 and staying here for a while Thanks again for your awesome support. I really appreciate it.
nypeach said:
Hi OldBaldy. Sorry I'm still having a tough time. As mentioned, I got back to 5.1.1 per the above process. I read your latest note and flashed the latest twrp (2.8.7.1) and took the MM OTA. It's now flashing the "teamwin" screen over and over. Should I be patient or bail? Thanks again for your patience and help!!!
Click to expand...
Click to collapse
You have to take the OTA BEFORE you flash TWRP. What you need to do now is get back into fastboot and flash the stock recovery img from the 5.1.1 factory image. Then reboot into system and take the OTA. After it installs, then follow the above instructions.
Sent from my XT1575 using Tapatalk
robn30 said:
So, I couldn't wait and already did it. I flashed Shawn5162's file in full. Then I took the OTA and updated perfectly. I have already installed TWRP 2.8.7.1 and made a nandroid of my Stock unrooted MM ROM. Now I want to root but want to make sure I understand this step perfectly. Which boot.img do I use? The ones in this thread http://forum.xda-developers.com/moto-x-style/general/root-moto-x-style-xt1572-br-marshmallow-t3259380? The boot.img in that thread is way smaller than the one in Shawn5162's LL zip tool. Just want to be sure I am doing this correctly. Lastly am I using the SU file in that thread as well and following those exact directions? Thanks.
Click to expand...
Click to collapse
No, that is the wrong root img to flash prior to installing SuperSU 2.52.
File Type: zip boot_root_mm_clark_retus.zip - [Click for QR Code] (10.01 MB, 756 views)
The file you want is in this post #290
Ohmster said:
No, that is the wrong root img to flash prior to installing SuperSU 2.52.
File Type: zip boot_root_mm_clark_retus.zip - [Click for QR Code] (10.01 MB, 756 views)
The file you want is in this post #290
Click to expand...
Click to collapse
Yup, I realized that plus someone else informed me that wasn't the one. I got her all taken care of and she is up and running smooth as can be. The battery on MM is really good. I'm impressed. I also wrote up a huge how to on the whole process and posted it. Should contain all the necessary steps in one place now. It gets a bit crazy having to dig all over the place to gather all that is needed. These threads get quite large and finding stuff gets more difficult as the days go by.
Sent from my XT1575 using Tapatalk
I take no credit for any of this. Monkey saw, monkey did. MAKE SURE YOU FULLY READ THE ORIGINAL POSTS AS THE MONKEY MAY HAVE OMITTED SOMETHING. If you are clueless, not good at following instructions, or apprehensive you might want to pass. If you managed to already get unlocked and TWRPed, I imagine you are good to go. Still, if you break your phone, it's on you.
1. Do a TWRP backup.
2. Flash one of the choices here (READ THE ENTIRE THREAD) :
https://forum.xda-developers.com/moto-x-style/development/rom-marshmallow-6-0-september-2016-t3536120
REBOOT.
I went with the Deodexed one. Check out the Mods too. I added Viper.
3. Get Systemless Root back using using the flash-able Script in Post #8 here (READ ALL 1st):
https://forum.xda-developers.com/moto-x-style/general/systemless-root-info-t3373864
3a. Direct Link here:
https://forum.xda-developers.com/attachment.php?attachmentid=3809946&d=1468261256
REBOOT
I was still stock but Rooted with Xposed and I successfully Dirty Flashed. OP still recommends a CLEAN Install. After running the script, the phone came back looking the same. I did lose my custom Boot Animation and Viper so I re-flashed them. I also flashed the latest SU just to be sure i had the latest. Probably makes no difference.
Build now says MPHS24.49-18-8 and security Patch 09/01/2016.
Be sure and thank the OP's for the flash-able Update and the Systemless script.
THANK YOU OP'S,
Monkey
Except people have to understand... this puts you in a potentially precarious position. Your bootloader, radios, and partition table are all from a previous ROM version, but your system and boot/kernel are from the current release. Meaning your stuck on this or other custom ROMs and cannot go back to "pure" stock, at least until there is official full factory firmware release for the September update.
Not saying this isn't a valid way to do it, but it isn't truly getting the update... not completely, so my advice to others is proceed with caution and know the possible consequences, they may or not matter to you.
acejavelin said:
...Meaning your stuck on this or other custom ROMs and cannot go back to "pure" stock, at least until there is official full factory firmware release for the September update.
Not saying this isn't a valid way to do it, but it isn't truly getting the update... not completely, so my advice to others is proceed with caution and know the possible consequences, they may or not matter to you.
Click to expand...
Click to collapse
When you say "cannot go back" does something get flagged where a TWRP system wipe and restore of a backup would not work?
G_Man18 said:
When you say "cannot go back" does something get flagged where a TWRP system wipe and restore of a backup would not work?
Click to expand...
Click to collapse
No... That's fine. I mean you can't flash the full system image via fastboot.
acejavelin said:
No... That's fine. I mean you can't flash the full system image via fastboot.
Click to expand...
Click to collapse
Thanks for the quick response. I am surprised how many people get in trouble when TWRP backups are easy to do and can get you going when you screw up--which does happen to all of us. I post little but do read quite a bit in these forums; most of my questions have already been answered. You say you will nudge people in the right direction, but from what I have seen, no one on here answers as many questions so meticulously as you. Thanks!
acejavelin said:
Except people have to understand... this puts you in a potentially precarious position. Your bootloader, radios, and partition table are all from a previous ROM version, but your system and boot/kernel are from the current release. Meaning your stuck on this or other custom ROMs and cannot go back to "pure" stock, at least until there is official full factory firmware release for the September update.
Not saying this isn't a valid way to do it, but it isn't truly getting the update... not completely, so my advice to others is proceed with caution and know the possible consequences, they may or not matter to you.
Click to expand...
Click to collapse
I just received the notification for this update, is it okay to take it, or is it going to cause issues. I am unlocked and rooted currently running MPHS24.49-18-4. I would restore back to a non-rooted TWRP backup of the same build, then flash back the original recovery image, clear cache and dalvik, and finally flash the update.
Will this work and is It okay to update to this build? Thanks.
robn30 said:
I just received the notification for this update, is it okay to take it, or is it going to cause issues. I am unlocked and rooted currently running MPHS24.49-18-4. I would restore back to a non-rooted TWRP backup of the same build, then flash back the original recovery image, clear cache and dalvik, and finally flash the update.
Will this work and is It okay to update to this build? Thanks.
Click to expand...
Click to collapse
If you return to stock, meaning the /system and /boot partitions and recovery is stock, it should work... how you get there isn't as important. But you can't just "flash" the OTA zip file, not directly... and I am not positive if the stock recovery supports sideloading official ZIPs or not, but you should be able to accept it and let it apply itself. The lock or unlock state of the bootloader isn't relevant.
So most likely it would work fine... but backup first, just in case something goes wrong.
acejavelin said:
If you return to stock, meaning the /system and /boot partitions and recovery is stock, it should work... how you get there isn't as important. But you can't just "flash" the OTA zip file, not directly... and I am not positive if the stock recovery supports sideloading official ZIPs or not, but you should be able to accept it and let it apply itself. The lock or unlock state of the bootloader isn't relevant.
So most likely it would work fine... but backup first, just in case something goes wrong.
Click to expand...
Click to collapse
Backup is running right now, so that will be good to go. With systemless root can I perform a full unroot using SuperSU or is it better to restore the unrooted TWRP backup? Thanks.
robn30 said:
Backup is running right now, so that will be good to go. With systemless root can I perform a full unroot using SuperSU or is it better to restore the unrooted TWRP backup? Thanks.
Click to expand...
Click to collapse
If you are rooted, it means you did something with root, right? So unless you are going to undo everything root and then unroot, better to restore the pre-root backup
acejavelin said:
If you are rooted, it means you did something with root, right? So unless you are going to undo everything root and then unroot, better to restore the pre-root backup
Click to expand...
Click to collapse
Very good, thanks for the advice. Good thing I made an unrooted backup when I updated to the May Security update. I knew that would come in handy eventually.
robn30 said:
Very good, thanks for the advice. Good thing I made an unrooted backup when I updated to the May Security update. I knew that would come in handy eventually.
Click to expand...
Click to collapse
Update went perfectly smooth by restoring back to an unrooted 24.221.4 TWRP backup, then flashing stock recovery, and finally taking the update to 24.221.8. I did perform a wipe off cache and dalvik at least twice during the process.
Sent from my XT1575 using Tapatalk
robn30 said:
Update went perfectly smooth by restoring back to an unrooted 24.221.4 TWRP backup, then flashing stock recovery, and finally taking the update to 24.221.8. I did perform a wipe off cache and dalvik at least twice during the process.
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
Just to be sure. I ran TWRP from Fastboot in ADB as soon as Unlocked and turned the phone on. So you have confirmed I can then flash Stock recovery and take the "full" Update. Mind providing the link to Stock recovery?
Thanks.
schneid said:
Just to be sure. I ran TWRP from Fastboot in ADB as soon as Unlocked and turned the phone on. So you have confirmed I can then flash Stock recovery and take the "full" Update. Mind providing the link to Stock recovery?
Thanks.
Click to expand...
Click to collapse
Pretty sure there is a post in here somewhere that has a link to the 24.221.4 recovery, but I just used the one in this full firmware download. Just extracted the recovery.img file only and flash it using fastboot. Here is the link.
https://forum.xda-developers.com/showpost.php?p=69103575&postcount=243
Recently I rooted my G5 plus and it worked really well for me. I didn't use SuperSU, instead, have Magisk installed. Unfortunately, now my phone isn't updating. What should I do to unroot it without much problem and without losing any data on my phone? And will it update if I unroot it?
It's a little more complicated than that... to bad there isn't a guide to doing it here somewhere... Hmmm....
https://forum.xda-developers.com/g5-plus/how-to/guide-complex-ota-update-magisk-rooted-t3688175
acejavelin said:
It's a little more complicated than that... to bad there isn't a guide to doing it here somewhere... Hmmm....
https://forum.xda-developers.com/g5-plus/how-to/guide-complex-ota-update-magisk-rooted-t3688175
Click to expand...
Click to collapse
So like can't I simply unroot my phone and install the updates? Isn't there any easy way of uprooting?
dt.dragonborn said:
So like can't I simply unroot my phone and install the updates? Isn't there any easy way of uprooting?
Click to expand...
Click to collapse
Root is only part of the problem, TWRP is another big one.
OTA updates can only be installed on a purely stock device, the install script will check multiple things to verify the device is unmodified and in the correct state before applying, then it applies changes to specific files or partitions, they must be at a known starting condition before changes can be applied.
So, can you simply "unroot and install updates"? No, you must undo all changes to the device that are system related... Return the recovery, boot, and system partitions to their original state or any update will fail. Unrooting does not undo any changes, adds, or deletions you performed with root access, those actions are permanent.
Isn't there an easy way of unrooting? Sure, Magisk and SuperSU both have methods of removal, but that doesn't gain you what is needed to apply an OTA update.
I provided a link previously, that is what you need to do.
dt.dragonborn said:
Recently I rooted my G5 plus and it worked really well for me. I didn't use SuperSU, instead, have Magisk installed. Unfortunately, now my phone isn't updating. What should I do to unroot it without much problem and without losing any data on my phone? And will it update if I unroot it?
Click to expand...
Click to collapse
Which OTA(s) isn't installing?
Sent from my Moto G Plus (5th Gen) using XDA Labs
cdysthe said:
Which OTA(s) isn't installing?
Click to expand...
Click to collapse
I am not much of a tech guy but the update says
New Version-NPN25.1 37-67
Improved audio in Video Capture
Data traffic improvements
acejavelin said:
Root is only part of the problem, TWRP is another big one.
OTA updates can only be installed on a purely stock device, the install script will check multiple things to verify the device is unmodified and in the correct state before applying, then it applies changes to specific files or partitions, they must be at a known starting condition before changes can be applied.
So, can you simply "unroot and install updates"? No, you must undo all changes to the device that are system related... Return the recovery, boot, and system partitions to their original state or any update will fail. Unrooting does not undo any changes, adds, or deletions you performed with root access, those actions are permanent.
Isn't there an easy way of unrooting? Sure, Magisk and SuperSU both have methods of removal, but that doesn't gain you what is needed to apply an OTA update.
I provided a link previously, that is what you need to do.
Click to expand...
Click to collapse
Thank you for this. I unlocked the bootloader, and installed TWRP and Magisk to gain root. This worked fine. However, I decided I wanted to go back to complete stock yesterday. So I uninstalled Magisk and flashed stock firmware using ADB. My phone is now unrooted, has a locked bootloader, and is running stock firmware which is what I wanted. Once I get the phone to boot, almost everything functions normally. However, it seems as though I now do not have any recovery whatsoever (and I assume that's because I did not specifically replace TWRP with stock recovery). So when I boot my phone, it goes to the bootloader and stops. If I then hit "start" on the bootloader, the ROM loads up normally after that. f that were the only issue, I could live with it. But not being able to get to recovery is concerning. And I am not able to get OTAs at the moment.
So, I'll check the other thread you mentioned. I assume I will need to flash stock recovery in order to get where I need to be.
Thank you for the post!
Banking apps can be not running when they think the phone is not safe even the phone is “not” rooted .
And factory reset or OTA update after rooting can make root access botched. Just like unrooting phone. So root checker apps can’t detect rooting after factory reset.
Then can i tell whether my phone has ever been rooted before factory reset without checking knox?
(Cuz broken knox doesnt necessarily mean rooting.)
My phone is reset . Root checking apps say its not rooted. But banking apps dont work.
Is thery any way to check..?
Jenjenjney said:
Banking apps can be not running when they think the phone is not safe even the phone is “not” rooted .
And factory reset or OTA update after rooting can make root access botched. Just like unrooting phone. So root checker apps can’t detect rooting after factory reset.
Then can i tell whether my phone has ever been rooted before factory reset without checking knox?
(Cuz broken knox doesnt necessarily mean rooting.)
My phone is reset . Root checking apps say its not rooted. But banking apps dont work.
Is thery any way to check..?
Click to expand...
Click to collapse
know triggered pretty much means custom recovery, custom rom, or root, and they can all break banking apps. Did you buy the device used?
You might find better support in the specific forum for your device. What is the make and model of the device in question? Additionally, which banking apps aren't working?
Outside of Knox, there's not really any way to tell if a device has been rooted, if it is currently on OEM firmware with a locked bootloader. If the bootloader is unlocked, it most likely has been rooted at some point., but none of that should matter if the device is restored to factory state with OEM firmware and a locked bootloader.
V0latyle said:
You might find better support in the specific forum for your device. What is the make and model of the device in question? Additionally, which banking apps aren't working?
Outside of Knox, there's not really any way to tell if a device has been rooted, if it is currently on OEM firmware with a locked bootloader. If the bootloader is unlocked, it most likely has been rooted at some point., but none of that should matter if the device is restored to factory state with OEM firmware and a locked bootloader.
Click to expand...
Click to collapse
My phone is galaxy note4 910k and samsung phone’s bootloader is already unlocked in korea.
Jenjenjney said:
My phone is galaxy note4 910k and samsung phone’s bootloader is already unlocked in korea.
Click to expand...
Click to collapse
I mean whether it is currently unlocked now, not whether it is unlockable.
If your bootloader is unlocked, your device will fail Play Integrity, and banking apps may not work.
V0latyle said:
I mean whether it is currently unlocked now, not whether it is unlockable.
If your bootloader is unlocked, your device will fail Play Integrity, and banking apps may not work.
Click to expand...
Click to collapse
Samsung phones in korea dont have bootloader locked. They are sold with bootloader unlocked in the first place.
Thats default. So i dont need to unlock it to root or install ROM.,,
Jenjenjney said:
Samsung phones in korea dont have bootloader locked. They are sold with bootloader unlocked in the first place.
Thats default. So i dont need to unlock it to root or install ROM.,,
Click to expand...
Click to collapse
Ah. Well, you have two choices:
Lock your bootloader (only do this if your firmware is completely stock)
Root using Magisk and read this thread, and use the linked module
An unlocked bootloader will result in the device failing integrity attestation, which DRM and banking apps rely on. The only way to fix this is to either use a Magisk module for a partial workaround, or to relock the bootloader.
V0latyle said:
Ah. Well, you have two choices:
Lock your bootloader (only do this if your firmware is completely stock)
Root using Magisk and read this thread, and use the linked module
An unlocked bootloader will result in the device failing integrity attestation, which DRM and banking apps rely on. The only way to fix this is to either use a Magisk module for a partial workaround, or to relock the bootloader.
Click to expand...
Click to collapse
Thanks but i wonder
Is there way to check if my phone was rooted before factory reset…?
I mean reset is not like installing stock rom, so even if files related to rooting are gone after factory reset, i think there are some traces to check,,,
Please…?
I ve never thought factory reset can wipe rooting trace like installing stock rom
Jenjenjney said:
Thanks but i wonder
Is there way to check if my phone was rooted before factory reset…?
I mean reset is not like installing stock rom, so even if files related to rooting are gone after factory reset, i think there are some traces to check,,,
Please…?
Click to expand...
Click to collapse
No - you can reflash factory firmware using Odin, but there's not really any easy way to tell if your device was previously modified.
Jenjenjney said:
I ve never thought factory reset can wipe rooting trace like installing stock rom
Click to expand...
Click to collapse
Factory reset just wipes /data and does not remove the SU binary. In my case, with my Magisk rooted Pixel 5, I could perform a factory reset...but because the boot image is patched, my device would still be rooted, unless I selected "Complete Uninstall" in Magisk. Factory reset and clean flashing factory firmware are not the same thing.
If you don't know what state your device was in previously, the only thing you can really do is perform a reflash of the factory firmware using Odin. This overwrites all partitions including /boot, /recovery, and /system.
Again, even after a complete clean flash, your device will still fail Play Integrity until you lock the bootloader, meaning that banking/DRM apps may not work.
Jenjenjney said:
Thanks but i wonder
Is there way to check if my phone was rooted before factory reset…?
I mean reset is not like installing stock rom, so even if files related to rooting are gone after factory reset, i think there are some traces to check,,,
Please…?
I ve never thought factory reset can wipe rooting trace like installing stock rom
Click to expand...
Click to collapse
no,no way to check if was rooted, samsung device to check own security uses knox, is tripped means device has been modded but not in a specific way like rooting
V0latyle said:
No - you can reflash factory firmware using Odin, but there's not really any easy way to tell if your device was previously modified.
Factory reset just wipes /data and does not remove the SU binary. In my case, with my Magisk rooted Pixel 5, I could perform a factory reset...but because the boot image is patched, my device would still be rooted, unless I selected "Complete Uninstall" in Magisk. Factory reset and clean flashing factory firmware are not the same thing.
If you don't know what state your device was in previously, the only thing you can really do is perform a reflash of the factory firmware using Odin. This overwrites all partitions including /boot, /recovery, and /system.
Again, even after a complete clean flash, your device will still fail Play Integrity until you lock the bootloader, meaning that banking/DRM apps may not work.
Click to expand...
Click to collapse
Thank you.
So factory reset affected the rooting and root checker apps can’t detect rooting , then
No other way to check whether my phone was rooted before reset right?
But still wonder reset can not touch system partition but how come root checker cant detect …
This is another question…
if i rooted my phone and then used rooting hide or unrooting or rootcloak to make banking apps run on my phone then i do factory reset,
would banking apps still run While root checker apps dont detect rooting anymore??
Or those efforts that i make to run banking apps are gone with other rooting traces..?
Jenjenjney said:
Thank you.
So factory reset affected the rooting and root checker apps can’t detect rooting , then
No other way to check whether my phone was rooted before reset right?
But still wonder reset can not touch system partition but how come root checker cant detect …
Click to expand...
Click to collapse
Again, factory reset doesn't necessarily affect root, especially with modern system-as-root, or with recovery hijacks. Factory reset just wipes the /data partition - removing user apps and data. In the case of Magisk, this would remove the Magisk manager app, but would not remove the Magisk patch from the boot image.
Jenjenjney said:
This is another question…
if i rooted my phone and then used rooting hide or unrooting or rootcloak to make banking apps run on my phone then i do factory reset,
would banking apps still run While root checker apps dont detect rooting anymore??
Click to expand...
Click to collapse
No, because as I stated above, performing a factory reset does not remove root nor does it hide your unlocked bootloader. Using Magisk as the example yet again, a factory reset would remove the Magisk app as well as installed modules. However, if there were "permanent" system modifications, these would persist after a factory reset.
Jenjenjney said:
Or those efforts that i make to run banking apps are gone with other rooting traces..?
Click to expand...
Click to collapse
Yes.
So to use my device as an example again: Pixel 5 on OEM firmware, rooted with Magisk 25.2, using Universal SafetyNet Fix 2.3.1 mod 2. I pass BASIC and DEVICE integrity and am able to use banking apps.
If I perform a factory reset, the boot image will still be patched with Magisk, and the bootloader will still be unlocked, so Play Integrity will fail DEVICE at the very least, and most likely BASIC too. Because the Magisk app is installed as a user app, this would be removed during a factory reset, meaning there would be no manager available to manage root permissions or load modules until I installed Magisk again.
The only thing a factory reset does is wipe the /data partition and internal userspace storage. It does not reset or restore anything else, so any modifications to any system partitions will persist after a data wipe.
V0latyle said:
Again, factory reset doesn't necessarily affect root, especially with modern system-as-root, or with recovery hijacks. Factory reset just wipes the /data partition - removing user apps and data. In the case of Magisk, this would remove the Magisk manager app, but would not remove the Magisk patch from the boot image.
No, because as I stated above, performing a factory reset does not remove root nor does it hide your unlocked bootloader. Using Magisk as the example yet again, a factory reset would remove the Magisk app as well as installed modules. However, if there were "permanent" system modifications, these would persist after a factory reset.
Yes.
So to use my device as an example again: Pixel 5 on OEM firmware, rooted with Magisk 25.2, using Universal SafetyNet Fix 2.3.1 mod 2. I pass BASIC and DEVICE integrity and am able to use banking apps.
If I perform a factory reset, the boot image will still be patched with Magisk, and the bootloader will still be unlocked, so Play Integrity will fail DEVICE at the very least, and most likely BASIC too. Because the Magisk app is installed as a user app, this would be removed during a factory reset, meaning there would be no manager available to manage root permissions or load modules until I installed Magisk again.
The only thing a factory reset does is wipe the /data partition and internal userspace storage. It does not reset or restore anything else, so any modifications to any system partitions will persist after a data wipe.
Click to expand...
Click to collapse
Oh i got it!
But i used that phone before magisk came out. So i think if my phone was rooted , defintely via one click rooting apps .
Then the answer to my qustion can be different..?
Btw i also saw people saying that they rooted phone with kingroot app and then they did factory reset, root checker apps dont detect rooting.
Its another curioustiy,
Can i bring back stock camera app via OTA update that i deleted with rooting?
Jenjenjney said:
Oh i got it!
But i used that phone before magisk came out. So i think if my phone was rooted , defintely via one click rooting apps .
Then the answer to my qustion can be different..?
Click to expand...
Click to collapse
No. Regardless of how the device is rooted - whether it's the "old" system-as-root way, where su was installed as a system app, or the "new" systemless root way, a factory reset aka data wipe makes no difference. The only way to get rid of it is to reflash the factory firmware.
Jenjenjney said:
Btw i also saw people saying that they rooted phone with kingroot app and then they did factory reset, root checker apps dont detect rooting.
Click to expand...
Click to collapse
Regardless of the "vendor" the process generally remains the same. Either /recovery is hijacked and the system is forced to load root, or root is installed as a system app, or the boot image is patched to allow user root access.
As an aside, Kingroot is dangerous because of some serious security issues. Magisk avoids these through signature verification and private keys.
Jenjenjney said:
Its another curioustiy,
Can i bring back stock camera app via OTA update that i deleted with rooting?
Click to expand...
Click to collapse
Yes.
Reflashing factory firmware, as I stated previously, overwrites everything with the firmware Samsung originally installed on the device - meaning all included apps.
So if you want to return your device to complete bone stock, you'd reflash the factory firmware in Odin, and you'd use the CSC.tar instead of HOME_CSC.tar (the latter is for updating when you want to keep your user data and apps)
Then, you would lock your bootloader.
V0latyle said:
No. Regardless of how the device is rooted - whether it's the "old" system-as-root way, where su was installed as a system app, or the "new" systemless root way, a factory reset aka data wipe makes no difference. The only way to get rid of it is to reflash the factory firmware.
Regardless of the "vendor" the process generally remains the same. Either /recovery is hijacked and the system is forced to load root, or root is installed as a system app, or the boot image is patched to allow user root access.
As an aside, Kingroot is dangerous because of some serious security issues. Magisk avoids these through signature verification and private keys.
Yes.
Reflashing factory firmware, as I stated previously, overwrites everything with the firmware Samsung originally installed on the device - meaning all included apps.
So if you want to return your device to complete bone stock, you'd reflash the factory firmware in Odin, and you'd use the CSC.tar instead of HOME_CSC.tar (the latter is for updating when you want to keep your user data and apps)
Then, you would lock your bootloader.
Click to expand...
Click to collapse
Just updating software that pops up in phone reinstalls stock apps??
But only updating software via ota in phones still dont allow banking apps run. I mean flashing a stock rom and just updating firm ware in phone via ota is different.
Jenjenjney said:
Just updating software that pops up in phone reinstalls stock apps??
But only updating software via ota in phones still dont allow banking apps run. I mean flashing a stock rom and just updating firm ware in phone via ota is different.
Click to expand...
Click to collapse
Yes, because OTA is generally a partial update, as opposed to a full factory flash.
I've told you several times...If you want banking apps to run on your device, and you don't want to use a root solution, you need to clean flash the factory firmware and lock your bootloader. That is the bottom line.
V0latyle said:
Yes, because OTA is generally a partial update, as opposed to a full factory flash.
I've told you several times...If you want banking apps to run on your device, and you don't want to use a root solution, you need to clean flash the factory firmware and lock your bootloader. That is the bottom line.
Click to expand...
Click to collapse
just doing ota update is going to reinstall stock cam app i deleted -amazing thanks.
Honestly… I am worrying malware app could root my phone . Cuz my phone got factory reset by malware app suddenly. So what i have now is reset phone .Thats why i want to know if my phone was rooted..
+ i used data recovery program after reset So i think thats maybe reason banking apps dont run now . But not sure the name of program so cant check if that programs have rooting feature.
So i just want to know if my phone has ever been rooted before reset. So worrying… i cant even sleep.
Jenjenjney said:
just doing ota update is going to reinstall stock cam app i deleted -amazing thanks.
Honestly… I am worrying malware app could root my phone . Cuz my phone got factory reset by malware app suddenly. So what i have now is reset phone .Thats why i want to know if my phone was rooted..
+ i used data recovery program after reset So i think thats maybe reason banking apps dont run now . But not sure the name of program so cant check if that programs have rooting feature.
So i just want to know if my phone has ever been rooted before reset. So worrying… i cant even sleep.
Click to expand...
Click to collapse
We have gone around and around this topic in this discussion. I have provided the answers for you. Without somehow comparing every partition against untouched firmware, there is no way to know what is currently modified. If everything is stock, there is no way to know whether it was previously modified. Your best option, once again, is to perform a clean flash of the factory firmware, and lock your bootloader. Locking your bootloader enables additional security features that verify whether or not the images have been modified, and will prevent boot if they are, which is why you need to perform a clean flash first. Doing this will remove any potential rootkit or hijack, because you'll be overwriting everything to bone stock.
V0latyle said:
We have gone around and around this topic in this discussion. I have provided the answers for you. Without somehow comparing every partition against untouched firmware, there is no way to know what is currently modified. If everything is stock, there is no way to know whether it was previously modified. Your best option, once again, is to perform a clean flash of the factory firmware, and lock your bootloader. Locking your bootloader enables additional security features that verify whether or not the images have been modified, and will prevent boot if they are, which is why you need to perform a clean flash first. Doing this will remove any potential rootkit or hijack, because you'll be overwriting everything to bone stock.
Click to expand...
Click to collapse
Thanks.. i really appreciate it
I dont use that phone anymore . Just wanted to know how to tell ,,
For the last ..
can i check if my stock camera app was modified? Or hackers can delete stock cam and install modified stock cam with rooting.
Can i analysis this app..?
Jenjenjney said:
Thanks.. i really appreciate it
I dont use that phone anymore . Just wanted to know how to tell ,,
For the last ..
can i check if my stock camera app was modified? Or hackers can delete stock cam and install modified stock cam with rooting.
Can i analysis this app..?
Click to expand...
Click to collapse
Yes, there are ways to compare files to determine whether a copy has been tampered with by comparing it with a known trustworthy original. A Google search turns up several results.