Hi Experts,
I have accidentally deleted some important files in my Samsung S9+ Secure Folder, and trying to find the best way to recover them. Looking for the Experts advice!
I read through the forums but it seems rooting and wiping the device is a must, and looks like rooting the device will kill my Secure Folder and Samsugn Pay forever. Despite this, I think it still needs to be done. Please if anyone could offer me some advice, it is greatly appreciated. I am also fairly new to Android, so please bear with me on the very technical side of things.
What I have tried:
1. Download file recovery apps in secure folder but it only restores files from the downloads/pictures/videos folders but my files did not sit there...
2. Tried multiple windows software and play store apps, all asking the device to be rooted first
2. Tried to root my device with Kingo Root, King Root, One Click Root and Towelroot, all failed to root....
Thanks in advance for any advice on this.
Jeffrey
Umm..... The whole point of the secure folder is to house content that you don't want people to be able to access!
So no, there's absolutely no way to do it.
Sent from my SM-G965W using Tapatalk
Devhux said:
Umm..... The whole point of the secure folder is to house content that you don't want people to be able to access!
So no, there's absolutely no way to do it.
Sent from my SM-G965W using Tapatalk
Click to expand...
Click to collapse
Thanks Devhux. But if I root the device and do a disk recovery treating it like a normal hard drive, applications should still be able to run a thorough scan on everything deleted on it?
Unfortunately, no. The secure folder is heavily encrypted. Considering that Knox is certified by the US Department of Defense and NSA, you're not going to get at the data that was in Secure Folder.
Also note that Android works differently due to using Media Transfer Protocol (MTP) when connecting to a Windows computer. That in itself won't let you create a disk "image" like you can on a regular computer.
There's also the issue that if you're running a Snapdragon 845 model of the S9+ you won't be able to root anyways.
Sent from my SM-G965W using Tapatalk
Got it, thanks for the details. I guess there is nothing I can do about this then.
I think you should root your Samsung S9+ first. Then try with an Android recovery software or app. Also, this Android data recovery must be helpful with you.
www.android-data-recovery.com
If he root the phone, Knox will be tripped and a secured folder won't work anymore. Why you didn't log in your account in the first place? So Samsung Cloud will do a backup and when you reinstall the phone, everything will be downloaded again.
Related
I have tried numerous things with the HDX to get it rooted again, SuperOneClick and numerous other one click root applications that failed, of course. The best way to get root, I figured, is to downgrade the OS. I have the .BIN file and, as the Amazon website states (for upgrade, of course) that we must stick it to internal storage, then do the usual upgrade business. However, the downgrade doesn't work. The is a file somewhere on the system that prevents it, and I wonder if we could find it and delete it, using the PC if necessary. Thanks for your cooperation.
ferrouskid said:
I have tried numerous things with the HDX to get it rooted again, SuperOneClick and numerous other one click root applications that failed, of course. The best way to get root, I figured, is to downgrade the OS. I have the .BIN file and, as the Amazon website states (for upgrade, of course) that we must stick it to internal storage, then do the usual upgrade business. However, the downgrade doesn't work. The is a file somewhere on the system that prevents it, and I wonder if we could find it and delete it, using the PC if necessary. Thanks for your cooperation.
Click to expand...
Click to collapse
I'm just curious as to if you never had root or lost root.
zXiC said:
I'm just curious as to if you never had root or lost root.
Click to expand...
Click to collapse
Yes I did have root, I used AOSP ROM, and made it almost pure android. I found a nice tool called "Android Commander" that has the ability to access the system files from the pc. I was attempting to flash the previous version of Mojito OS using the casebook utility but failed, and as far as I figured I might just be able to extract and maybe delete the file the check for automatic updates, and thus do a manual update on the kindle, which literally requires dropping in the .BIN file into internal storage and the lb upgrade it. Then use the old root method, so if you are interested you could help me locate that file
Hello everyone,
This is my first Galaxy Gear. I am digging the communication watch very much. However, As silly as this may sound i really want to add my own ringtone/Notification. There is so much fun potential with this from **** Tracy, Jetsons, Power Rangers and many more that i think would be great. I have high hopes for this $400 investment. But i really want to change the the sounds. Thanks for your time.
Inspector Gadget for me. I really hope someone chimes in with a workable method.
artyourmind said:
Hello everyone,
This is my first Galaxy Gear. I am digging the communication watch very much. However, As silly as this may sound i really want to add my own ringtone/Notification. There is so much fun potential with this from **** Tracy, Jetsons, Power Rangers and many more that i think would be great. I have high hopes for this $400 investment. But i really want to change the the sounds. Thanks for your time.
Click to expand...
Click to collapse
Lots of us do but Samsung has locked down the file system section with the sounds in it, and they didn't give us an external folder to work with. This is why we need root my friend.
sbrownla said:
Lots of us do but Samsung has locked down the file system section with the sounds in it, and they didn't give us an external folder to work with. This is why we need root my friend.
Click to expand...
Click to collapse
How does one root it? If i have never done it before should i not touch it? haha I was looking around for info on it but am terrified to try it.
artyourmind said:
How does one root it? If i have never done it before should i not touch it? haha I was looking around for info on it but am terrified to try it.
Click to expand...
Click to collapse
I'm no pro at it but from what I have gathered, rooting requires first installing an insecure boot image that allows the device to have root turned on and off via SDB (like ADB but for the Gear devices). SDB is basically a command-line interfacing shell we use to manage the Gear's files and system settings, among other things. Turning root on through SDB allows user access and the ability to modify "system" level files and applications.
Samsung has locked up access to quite a bit of files on the Gear S, including ringtones and sounds for example. In contrast, on your Android phone Google and your manufacturer have created alternate folders outside of the "system" level that can hold sounds and ringtones that the system can also assign, and that you can modify, without having to have direct access to the actual system itself.
What a modder, who is able to figure out how to obtain root, is able to do is find an exploit in the boot process, and modify a boot image, package it up and make it available to us as a flashable file or a small application. With the Tizen Gear/2/Neo, there is an insecure boot image that any user can use Odin to flash. After flashing that insecure image, they can turn root access on or off.
I think that's about it. The hardest part is figuring out where the boot exploit is. Pulling apart the insecure boot image that was posted by someone else somewhere on here, as a file to flash the device with using Odin, could reveal helpful information. But it would have to be modified to suit the Gear S.
I don't want to test it out though until I can find the full stock firmware for my Gear S (AT&T) but it isn't available for some weird reason. All of the other versions are available. Without that stock image for my device I can't restore to my factory Gear. I'd have to flash a foreign version and I'm not about to try that.
sbrownla said:
I'm no pro at it but from what I have gathered, rooting requires first installing an insecure boot image that allows the device to have root turned on and off via SDB (like ADB but for the Gear devices). SDB is basically a command-line interfacing shell we use to manage the Gear's files and system settings, among other things. Turning root on through SDB allows user access and the ability to modify "system" level files and applications.
Samsung has locked up access to quite a bit of files on the Gear S, including ringtones and sounds for example. In contrast, on your Android phone Google and your manufacturer have created alternate folders outside of the "system" level that can hold sounds and ringtones that the system can also assign, and that you can modify, without having to have direct access to the actual system itself.
What a modder, who is able to figure out how to obtain root, is able to do is find an exploit in the boot process, and modify a boot image, package it up and make it available to us as a flashable file or a small application. With the Tizen Gear/2/Neo, there is an insecure boot image that any user can use Odin to flash. After flashing that insecure image, they can turn root access on or off.
I think that's about it. The hardest part is figuring out where the boot exploit is. Pulling apart the insecure boot image that was posted by someone else somewhere on here, as a file to flash the device with using Odin, could reveal helpful information. But it would have to be modified to suit the Gear S.
I don't want to test it out though until I can find the full stock firmware for my Gear S (AT&T) but it isn't available for some weird reason. All of the other versions are available. Without that stock image for my device I can't restore to my factory Gear. I'd have to flash a foreign version and I'm not about to try that.
Click to expand...
Click to collapse
Are there other exploits used to root non US versions that might help?
Of the Gear S? Nothing I have been able to find at all. But of the Gear 2 yes and those will be telling. I'm going to take a little time to look at what's in the Gear 2 root image. I highly doubt I'm going to magically become smart enough to crack the code but I'm definitely learning a LOT as I poke around.
Seems like a very weird oversight by Samsung. Why not allow custom ringtones? I am hopeful this will be changed in an upcoming update.
ozaghloul said:
Seems like a very weird oversight by Samsung. Why not allow custom ringtones? I am hopeful this will be changed in an upcoming update.
Click to expand...
Click to collapse
It is ... but they need to know we care ...
Okay so I was told to come here because my phone doesn't have its' own forum yet (Not at all surprising..), so I'm just going to quote my post back on the other thread that told me to come here instead.
Mc Fow1er said:
Okay so I've had this phone for little over 10 months now and within that time I've managed to achieve root (unreliable but it works at the very least) in that time as well as learned a fair amount about Linux and android alike (Not a whole lot but I know some stuff) though I've now come to the point of I actually want to give my phone a proper root instead of this faulty solution I have currently. I (barely) managed to get my phone rooted using Kingoroot and I've played plenty with my phones' innards in that time, removed system apps, added my own selection to the system but some apps in my phone that use root don't work even with root permission granted which is why I'm wanting to replace Kingoroot with ChainFires' SuperSU binaries, could anybody help me with simple instructions for someone who doesn't actually know very much regarding how root and SU bins work inside of android? My phone's using 4.4.2 kitkat.
Just a few disclaimers first to get misconceptions out the way:
1. I do not have a custom recovery nor is one available for my phone (Samsung galaxy young 2 (SM-S130H) for those who want to know)
2. I'm currently unable to use the internet on my phone as I lack Wi-Fi to do so (router is dead) so I'm manually installing app packages through ADB, so if something needs an internet connection on my phone it's not going to work for me, for now..PC still has net access.
3. I have access to ADB shells' SU but not ADB root so I hope you don't need that from me.
4. This phone does not have a fastboot mode. (That I can find anyway..) Only a download mode from what I've found.
Can anybody help me out with telling me what I'll need to be doing in regards to getting this done?
Click to expand...
Click to collapse
So, can anyone here knowledge on the matter can assist me with this instead of me having to figure it out on my own?
I have a Samsung Galaxy tab s6 which I know to be hacked. I need to prove it was hacked. The person who did it, probably took my phone and entered in recovery mode in order to install malicious APK or unlock the phone.
I entered in recovery mode and used the option "read recovery logs".
It is hard to read it in the screen since there is no search option and the logs are long.
Is there a way I can copy these log files? I know they go to \cache\recovery.
I tried to access this folder using fx App, but I have no permission.
The tablet is not rooted.
Can I get these logs somehow using ADB in recovery? How?
Can I get these logs by rooting the phone first? Won't the logs be lost if I do it?
Is there a hint on what to look in these logs in order to prove someone inserted a USB drive or SD card and installed some .zip?
No anti vírus os detecting malware, but you know, this is not guaranteed to work or the spyware might have deleted itself when the spyer realized I was browsing for solutions. Do you know any other way I can prove I was hacked?
Just want to start out by saying, I HATE HATE HATE how Android has to keep everything so secretive and hard to access. Android works great, but when you want to do something as simple as grabbing files from an app, everything tries its hardest to stand in your way from root access bs to apps detecting if Magisks non functional anti hide is on the system. Enabling root and using root file access apps are so damn useless and crash all the time. Worst part is, they don't even show the files you are looking for when you find the right directories so wtf, what's even the point. /rant
I have a game/app that stores files on my expanded SD card storage. The files get downloaded *somewhere* and my phone detects the 5 GB of storage its using. How can I find the exact directory my phone is using that calculates the size of the files, and how can I gain access to these files to copy over FTP / USB / ADB etc to my computer.
I've spent so many hours trying to figure this out. Closest I got was making ADB backup pulls for the app but the archive is corrupt / incomplete every time so nothing will extract in full.
My device is a Samsung Note 3 running Android 7.1 Lineage.
Figured I would come here for help since I bet there's some Android developers that know a simple trick or two to just extract some simple unencrypted files. Very very much appreciated for any tips or guidance!
blalnstk200 said:
Just want to start out by saying, I HATE HATE HATE how Android has to keep everything so secretive and hard to access. Android works great, but when you want to do something as simple as grabbing files from an app, everything tries its hardest to stand in your way from root access bs to apps detecting if Magisks non functional anti hide is on the system. Enabling root and using root file access apps are so damn useless and crash all the time. Worst part is, they don't even show the files you are looking for when you find the right directories so wtf, what's even the point. /rant
I have a game/app that stores files on my expanded SD card storage. The files get downloaded *somewhere* and my phone detects the 5 GB of storage its using. How can I find the exact directory my phone is using that calculates the size of the files, and how can I gain access to these files to copy over FTP / USB / ADB etc to my computer.
I've spent so many hours trying to figure this out. Closest I got was making ADB backup pulls for the app but the archive is corrupt / incomplete every time so nothing will extract in full.
My device is a Samsung Note 3 running Android 7.1 Lineage.
Figured I would come here for help since I bet there's some Android developers that know a simple trick or two to just extract some simple unencrypted files. Very very much appreciated for any tips or guidance!
Click to expand...
Click to collapse
There is a note 3 section
https://forum.xda-developers.com/galaxy-note-3/help
Sent from my mata using XDA Labs
sd_shadow said:
There is a note 3 section
https://forum.xda-developers.com/galaxy-note-3/help
Sent from my mata using XDA Labs
Click to expand...
Click to collapse
? I need help with Android the software, not Note 3 hardware
blalnstk200 said:
? I need help with Android the software, not Note 3 hardware
Click to expand...
Click to collapse
Every manufacturer implements Android differently
Sent from my mata using XDA Labs