Database Users

Back to Factory with no computer access.

I everyone!
I just tried to connect my Nexus 4 to my windows 8.1 laptop and the phone is not recognised by the PC. It gives me Code 43 error, I tried everything, form fresh driver install to cable change. I also tried on another W7 laptop and nothing pops up there. The phone charges but in Device Manager it is not listed under Google ADB devices but appears with an exclamation mark under USB controllers saying Device Descriptor Request Failed. I fear it is an hardware problem and RMA is the only option left. However, my phone is Rooted, Stock but with modified build.prop, with TW touch recovery and unlocked. Since I have no access to ADB I cannot use the Android SDK tools or anything to flash the factory img. Is there any way in which I could flash back the sock image and lock the bootloader via recovery only?
Thanks everyone :crying::crying:

you dont need adb to flash the factory img. you need fastboot to flash it, via your bootloader. but, fastboot still needs to see your device, so thd driver still nedds to be installed.

Wouldnt it be possible to flash the 4.3 stock rom zip in his custom recovery, root it and flash the stock recovery with flashify, and then unroot the device?
Sent from my Nexus 4 using xda app-developers app

Thibaultvw said:
Wouldnt it be possible to flash the 4.3 stock rom zip in his custom recovery, root it and flash the stock recovery with flashify, and then unroot the device?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
This was what I was thinking, however, the main issue would be locking the bootloader again
simms22 said:
you dont need adb to flash the factory img. you need fastboot to flash it, via your bootloader. but, fastboot still needs to see your device, so thd driver still nedds to be installed.
Click to expand...
Click to collapse
I dont think is a driver problem, I had driver issues before but i got different errors and solved them easily. I do believe is an hardware failure this time

c0sk said:
This was what I was thinking, however, the main issue would be locking the bootloader again
I dont think is a driver problem, I had driver issues before but i got different errors and solved them easily. I do believe is an hardware failure this time
Click to expand...
Click to collapse
READ THIS 1st
http://forum.xda-developers.com/showthread.php?t=2010312
Scroll down to the 2nd post.

mrhiab said:
READ THIS 1st
http://forum.xda-developers.com/showthread.php?t=2010312
Scroll down to the 2nd post.
Click to expand...
Click to collapse
Thanks, exactly what I was looking for! :victory:
However, since I am already on stock andshould have a backup of the build.prop (i just added a line to get rid of the on screen buttons) would you recommend flashing everything again or just lock bootloader, unroot and flash stock recovery only?

c0sk said:
Thanks, exactly what I was looking for! :victory:
However, since I am already on stock andshould have a backup of the build.prop (i just added a line to get rid of the on screen buttons) would you recommend flashing everything again or just lock bootloader, unroot and flash stock recovery only?
Click to expand...
Click to collapse
Restoring the original build.prop, locking the bootloader, remove root and flash stock recovery will be just fine.

efrant said:
Restoring the original build.prop, locking the bootloader, remove root and flash stock recovery will be just fine.
Click to expand...
Click to collapse
Ok! I did a very stupid thing, I did restore my build.prop but without any backup files. The system does not boot up now! Root has been removed and bootloader locked, however, the custom recovery is still there and I did not copy the stock image! Is there any other way in which I could restore the stock recovery or am I screwed??

c0sk said:
Ok! I did a very stupid thing, I did restore my build.prop but without any backup files. The system does not boot up now! Root has been removed and bootloader locked, however, the custom recovery is still there and I did not copy the stock image! Is there any other way in which I could restore the stock recovery or am I screwed??
Click to expand...
Click to collapse
When you restored your build.prop, did you set the proper permissions, i.e., 644? If not, does your recovery allow you to do so? Try it and see if you boot.
Sent from my Nexus 5 using Tapatalk 2

efrant said:
When you restored your build.prop, did you set the proper permissions, i.e., 644? If not, does your recovery allow you to do so? Try it and see if you boot.
Sent from my Nexus 5 using Tapatalk 2
Click to expand...
Click to collapse
I fixed that problem in a different way, more barbaric but effective. I booted it up and managed to get JDQ39 files on the phone via dropbox: odexed image, boot and recovery. I flashed the first 2 (wanted to keep the recovery for safety and flash the stock one at a second stage). Booted successfully and removed root via SuperSu settings. Once flashed stock recovery, am I right to assume it will be completely stock and therefore ready for RMA? Moreover, can I accept OTA since is fully stock?
Thanks!!!!!
edit: Su installer app was there after flashed recovery and did factory reset

c0sk said:
I fixed that problem in a different way, more barbaric but effective. I booted it up and managed to get JDQ39 files on the phone via dropbox: odexed image, boot and recovery. I flashed the first 2 (wanted to keep the recovery for safety and flash the stock one at a second stage). Booted successfully and removed root via SuperSu settings. Once flashed stock recovery, am I right to assume it will be completely stock and therefore ready for RMA? Moreover, can I accept OTA since is fully stock?
Thanks!!!!!
edit: Su installer app was there after flashed recovery and did factory reset
Click to expand...
Click to collapse
The way you removed SuperSU must have not worked properly. (I've never tried doing it from the SuperSU settings.) In any case, there's nothing more you can do now, so might as well send it in for RMA.

[GUIDE] [OSPREY] [MM] 【6.0/6.0.1】Install TWRP, Root and Xposed successfully on 6.0

[GUIDE] [OSPREY] [MM] 【6.0/6.0.1】Install TWRP, Root and Xposed successfully on 6.0
1) Unlock your bootloader . for complete unlocking process go here.
https://m.youtube.com/watch?v=sw675ipX-ds&feature=youtu.be
IT WILL RESET ALL YOUR DATA.
2) Turn on USB debugging on
3) Boot your device into bootloader mode
4) flash TWRP recovery v2.8.7 r5. http://forum.xda-developers.com/devdb/project/?id=11051#downloads
5) Boot into TWRP recovery
6) Flash supersu zip v2.62-3. http://download.chainfire.eu/751/SuperSU/BETA-SuperSU-v2.62-3-20151211162651.zip
7) After succsesfull flashing wipe cache/dalvik cache . reboot system. If it asks to install Root. DO NOT INSTALL ROOT AT THIS STAGE.
8) wait till Boot finishes.
9) If you want to install Xposed Boot into TWRP recovery.
10) Flash Xposed installer xposed-v79-sdk23-arm.zip. http://forum.xda-developers.com/showthread.php?t=3034811.
Thanks for contributors of TWRP, Supersu and Xposed.

I am G-Root...ed
Thanks man!, being trying a lot with no succes... till now... Excelent Work :good:

abhijeetc9762 said:
1) Turn on USB ) .
Click to expand...
Click to collapse
do we have twrp for moto g turbo?

The phone has to have the bootloader unlocked?
The whole thing will completely reset the device?

abhijeetc9762 said:
3) flash TWRP recovery v2.8.7 r5.
Click to expand...
Click to collapse
Will this work without flashing TWRP? Can I just boot TWRP using fastboot, then flash SuperSU 2.62-3 and reboot? In that way, after reboot it will be system recovery and as SuperSU 2.62-3 is a systemless root, there won't be any modification in /system. Thus, I can receive OTA updates in future directly.
Did anybody try this with XT1550?

soumyajit_nayak said:
Will this work without flashing TWRP? Can I just boot TWRP using fastboot, then flash SuperSU 2.62-3 and reboot? In that way, after reboot it will be system recovery and as SuperSU 2.62-3 is a systemless root, there won't be any modification in /system. Thus, I can receive OTA updates in future directly.
Did anybody try this with XT1550?
Click to expand...
Click to collapse
You don't have chance anyway after rooting. You have to have Flash the firmware again to receive OTA
Sent from my MotoG3 using XDA Premium 4 mobile app

soumyajit_nayak said:
Will this work without flashing TWRP? Can I just boot TWRP using fastboot, then flash SuperSU 2.62-3 and reboot? In that way, after reboot it will be system recovery and as SuperSU 2.62-3 is a systemless root, there won't be any modification in /system. Thus, I can receive OTA updates in future directly.
Did anybody try this with XT1550?
Click to expand...
Click to collapse
Yes, you can do it that way, I've done it several times. Like someone said though, it's simpler to just flash TWRP and be done with it rather than wait for OTA's that you probably can't flash anyway.

Tel864 said:
Yes, you can do it that way, I've done it several times. Like someone said though, it's simpler to just flash TWRP and be done with it rather than wait for OTA's that you probably can't flash anyway.
Click to expand...
Click to collapse
In an earlier post you indicated that you can simply do a full unroot with SuperSU and receive OTA updates. Did that only apply to 5.1.1 and not 6.0?
Tel864 said:
I was able to d/l the update, but had to unroot to install the update. If you're using SuperSU to root, it's a simple matter to use the SuperSU app and do a full unroot, then just root again after the update.
Click to expand...
Click to collapse

Kakaroth89 said:
The phone has to have the bootloader unlocked?
The whole thing will completely reset the device?
Click to expand...
Click to collapse
Same question. Coming from a Nexus 4 phone, it was necessary to unlock the bootloader first. According to the instructions here, that is unnecessary?
EDIT (01-20-2016): Thanks for adding the missing unlock bootloader step to the instructions. I just ordered a Moto G yesterday.

pjc123 said:
Same question. Coming from a Nexus phone, it was necessary to unlock the bootloader first. According to the instructions here, that is unnecessary?
Click to expand...
Click to collapse
To root you will need an unlocked bootloader.

Any one?
Rooted xt1550 with supersu 2.62 and then deleted moto bloatware, now phone stuck on black screen after rebooting. Any help abt deleting bloatware?

Seems fine..but
just done this and boot up looks normal but seems forever to boot up. It has not boot up yet, what is the estimated time to wait?

Does it matter if TWRP is configured as "Read Only" or not?

Tel864 said:
To root you will need an unlocked bootloader.
Click to expand...
Click to collapse
And this procedure will do a factory reset?
I mean all the procedure, not just unlocking the bootloader

Kakaroth89 said:
And this procedure will do a factory reset?
I mean all the procedure, not just unlocking the bootloader
Click to expand...
Click to collapse
No, all your data and apps will still be there.

Tel864 said:
No, all your data and apps will still be there.
Click to expand...
Click to collapse
I lost all apps and data when I unlocked bootloader.. I did not unlock until after the 6.0 upgrade.

MrTooPhone said:
Does it matter if TWRP is configured as "Read Only" or not?
Click to expand...
Click to collapse
Do no tick as read only.
Sent from my MotoG3 using XDA Premium 4 mobile app

OP updated for bootloader unlocking procedure
Sent from my MotoG3 using XDA Premium 4 mobile app

abhijeetc9762 said:
5) Boot into TWRP recovery
Click to expand...
Click to collapse
@abhijeetc Excellent instructions. One recommendation is to address the issue with the "read only" TWRP option. I am sometimes presented with this option during TWRP boot (not sure why this option is not presented every time since I never check "don't show again"). I am not sure if "read only" makes a difference or not. But I can confirm I was soft bricked after enabling read only and flashing 2.66. I did not wipe Dalvik/Cache either. I was successful with 2.62-3 but was not presented "read only" option either. Also, you may want to recommend a Nandroid back up prior to any attempt flashing root. Just a recommendation.

I notice under developer settings (tap Build Number a bunch of times in the "About Phone" section to access developer mode) it has the option "OEM unlocking - Allow bootloader to be unlocked" as an option. Does that make this process any easier or is it necessary? I bought my phone straight from motomaker.

The Easy Way To Get The "Update"

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

how to restore my phone to stock android

What is the easiest way to go about removing my root from my phone and restoring it to stock Android. Is there anyway I can do this without a computer. I am asking because I am on vacation and can't log back into Snapchat because I am rooted.

jdugery said:
What is the easiest way to go about removing my root from my phone and restoring it to stock Android. Is there anyway I can do this without a computer. I am asking because I am on vacation and can't log back into Snapchat because I am rooted.
Click to expand...
Click to collapse
If you're rooted with superSU the best option would be to use the full unroot option

jdugery said:
What is the easiest way to go about removing my root from my phone and restoring it to stock Android. Is there anyway I can do this without a computer. I am asking because I am on vacation and can't log back into Snapchat because I am rooted.
Click to expand...
Click to collapse
Return to stock without a computer (except for recovery) is possible if you still have your backup from before you rooted on your device... if you haven't made significant changes with root (like Xposed or something) just restore the system and boot partitions, clear cache and reboot and you should be good.
If you all you need is to get rid of root, then go into SuperSU app settings, and find Full Unroot and let it do it's thing. Root will be gone, but honestly there is only about 75% chance of still passing SafetyNet API check since /system has been modified it, it could still fail the check... If that happens you will probably need to use a computer and fastboot back to stock or flash Magisk and enable Magisk Hide.

acejavelin said:
Return to stock without a computer (except for recovery) is possible if you still have your backup from before you rooted on your device... if you haven't made significant changes with root (like Xposed or something) just restore the system and boot partitions, clear cache and reboot and you should be good.
If you all you need is to get rid of root, then go into SuperSU app settings, and find Full Unroot and let it do it's thing. Root will be gone, but honestly there is only about 75% chance of still passing SafetyNet API check since /system has been modified it, it could still fail the check... If that happens you will probably need to use a computer and fastboot back to stock or flash Magisk and enable Magisk Hide.
Click to expand...
Click to collapse
Is there anyway to return to stock if you don't have a recovery dating to before you rooted?

jdugery said:
Is there anyway to return to stock if you don't have a recovery dating to before you rooted?
Click to expand...
Click to collapse
Not without a computer.

jdugery said:
Is there anyway to return to stock if you don't have a recovery dating to before you rooted?
Click to expand...
Click to collapse
What is your model? Twrp ver? Android ver. - full 24.???
I can upload my backup for xt1572 reteu.

dzidexx said:
What is your model? Twrp ver? Android ver. - full 24.???
I can upload my backup for xt1572 reteu.
Click to expand...
Click to collapse
So does returning to a stock TWRP backup do the trick? Because in the past I've used the stock firmware and stuff thread I found and it had some TWRP backups available for download. And that is doable without a computer for sure.
This is the link I just grabbed a stock TWRP backup. https://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833

If you have xt1575 RETUS and the same version 24.49-18-xx you can download it and restore boot+system in twrp.
For a future:
Always do backup before rooting and again before modifying system. @jdugery
---------- Post added at 11:56 AM ---------- Previous post was at 11:48 AM ----------
Ps
Snapchat needs run & login before rooting.

How can i tell if my phone has ever been rooted before factory reset

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.