Hi everyone!
I have a Samsung Galaxy S4 GT-i9505 running Android 5.0.1 build oj2.
It has a Google Authenticator database on it which I would like to extract, so I can migrate it over to a new phone.
I would rather not have to cancel and renew all my 2fa accounts currently stored withing Google Authenticator.
It seems I need root access to access the database file.
I found some references to things like motochopper, psneuter, providing temporary root, and I tried a couple of those, but it seems my S4 has been properly patched.
I tried compiling and executing a copy of Towelroot I found on GitHub under /geekben/towelroot, but that didn't work either (maybe I did not correctly compile...)
Priority #1 is not losing access to my Google Authenticator database (no bricking, no factory reset, ...)
What are my options? Does a simple root exploit exist for my S4 that would allow me to copy the db file? I was unable to find it.
I read something about a custom recovery, and then using nandroid to backup, which, I think, would allow me to extract the db from the backup?
I'm not sure about the risks involved; if flashing the custom recovery fails for whatever reason, do I still have 'normal' access to my S4?
Is it at all possible to flash a custom recover without first wiping everything on my S4? I'm reading mixed information.
Any other options perhaps?
Also, my S4 just finished downloading an OTA upgrade to 'something' (it's not showing what it has downloaded, about 490Mb in size) and I may have postponed the upgrade by rebooting.
Perhaps an upgrade to Android 6.0? I don't know if that would be better or worse for what I'm trying to do here...
Thanks in advance for any pointers...
CF-Autoroot via Odin is what you use to root the S4. This will trip Knox, but at this point it shouldn't be an issue as the I9505 hasn't been produced for a couple years now. However, if you downloaded Authenticator from the Play Store Google should have backed up the database, unless doing so creates a security hole.
Backing up and restoring the Authenticator data can be done with ES File Explorer, as I routinely do it with my copy of Authenticator when I need to do a clean install of my N6's custom ROM. Other apps like Titanium Backup may also work, but I don't use Titanium Backup so I don't know how well it would work with Authenticator. Go here for a tutorial on how to backup both app and data using ES File Explorer. Ignore the requirement for the Pro version. The copies of ES File Explorer that I offer from the link in my signature have the ability to backup app and data. Just make sure both of your devices are rooted and have ES File Explorer installed.
EDIT: The one thing that tutorial doesn't mention is that you need to enable root in ES File Explorer; the setting for that can be found in the menu, accessed by tapping on the three lines at the upper left. It also doesn't mention that after enabling root you need to go into the settings, tap on App, and make sure everything on the page is checked before backing up. Otherwise, the app data will not be backed up when you back up the apps.
Ok, this is what I'm reading about Odin and CF-Autoroot at android.wonderhowto.com at /how-to/android-basics-root-with-cf-auto-root-0167401/ (sorry not allowed to post links):
CF Auto Root works by unlocking your device's bootloader, which means that if your bootloader is not already unlocked, you will lose all of the data on your device.
And there are many more articles hinting that my phone will get wiped if I unlock the bootloader, for an S4 as well as other models.
So.... I'm a little confused here. I never touched my S4 with anything special, so I'm guessing that it's bootloader will be locked?
So this will wipe my S4? I can't do that - I'm looking to save and copy my Google Authenticator database as priority #1, not looking to root my phone. I may do so later but rooting is not prio #1.
You're in a bit of a catch-22 here. There's no guarantee you won't lose your data if you run CF-Autoroot, but you have no choice BUT to run CF-Autoroot if you want to retrieve the Authenticator database at all. Since the database is in the /data partition, unavailable to a normal user, root is required in order to access that partition to retrieve the database, and in order to root you have to risk having your data wiped. To restore the database to your other phone also requires root, for the same reason.
The only devices that had locked bootloaders were in the US, so you should be ok running CF-Autoroot. But there are no guarantees here.
Thanks for your input.
Indeed there's a catch-22 here, except that I also have the option of, one by one, cancelling and renewing all my 2fa accounts and not root at all. I'm trying to decide what to do here, as obviously, renewing all ma 2fa in case of dataloss (losing access to my accounts in the process) will be much more difficult than simply re-doing all my 2fa accounts while I still have access. Rooting my new phone is less of an issue as it contains no important data at the moment.
I think I also read about installing a custom recovery, and using that to make a nandroid backup, which would then allow me to extract the file I need from the backup. Is that a possibility? And, if yes, would this be less risky than using CF-Autoroot? Would my S4 still be able to boot and function normally if I flash some total garbage file as a recovery partition? So I could try and flash a custom recovery, and if that fails for some reason, my S4 will still boot as usual?
Thanks
You can install a custom recovery, make a nandroid backup, and retrieve the database that way. You would then have to transfer the nandroid to the other phone, install a custom recovery to the other phone, and then restore just the data. To me that's a lot of work for little gain. Rooting and using ES File Explorer or Titanium Backup to retrieve the data is far simpler to do and causes less headaches.
As to flashing a custom recovery being less risky than CF-Autoroot, no. It's the same level of risk as both the custom recovery and CF-Autoroot are installed in the same fashion. The only difference is that CF-Autoroot runs a temp environment, roots the device, and then commits seppuku.
Thanks again for your input; much appreciated. I'm trying to learn and understand what is happening, and with all the slightly different combinations out there, it is sometimes difficult to know what applies to my S4 and what is not applicable.
So there is at least the boot loader, the recovery image, and the main android image (file system?). Perhaps a kernel partition also?
These will probably be separate flash partitions within the same flash chip.
The boot loader will always be started when I power up the device. When no special key combination is pressed at power-up, the boot loader will simply load the Linux kernel which will eventually load the main operating system which will end up launching android.
With some special key combination is pressed, the boot loader will launch the recovery image in stead.
I wonder, what would happen if, using Odin, I write a completely invalid data file to the recovery image (I pick the wrong image, or the image is corrupt, or by accident I pick a jpg file of my cat in Odin, or the process is interrupted due to a sudden power loss on my phone or even my computer running Odin), and suppose Odin will just go ahead thus destroying the recovery image. My recovery partition is now corrupt, unusable and will crash the system when launched.
Does this brick my phone? Will I still be able to boot normally? Will I still be able to use Odin and try flashing the recovery image a 2nd tine?
2kman said:
Does this brick my phone?
Will I still be able to boot normally?
Will I still be able to use Odin and try flashing the recovery image a 2nd time?
Click to expand...
Click to collapse
No.
Yes.
Yes.
Related
***PLEASE DO NOT SKIP THE INSTRUCTION THAT SAYS MAKE A BACKUP*****
Lots of people are requesting help after not making a backup. And while people are able to help, the files are very large and takes up considerable bandwidth. Much better to EASILY create your own backup.
-------------------------------------------------------------------------
First of all a BIG thanks to @ionioni, this is all his work i am just re-uploading files and some sort of instructions. Much of the instructions are also lifted from ionioni, so thanks from me too!
That's right sources here: https://twrp.me
There Is currently no xposed support for intel 64 bit android
Neither I or the developer take any responsibility for damage to yourself or your tablet, by carrying out anything written here you accept full liability for your actions. I am quite sure xda forums feel the same.
****BIG WARNING , This is ONLY for the Yoga Tab 3 Pro models YT3-X90(F|X|L) Intel Atom powered CherryTrail SoC devices flashing any of these files to another device will more than likely result in BRICK!!****
ANOTHER BIG NOTE.....lollipop can only be rooted using supersu version 2.46 whilst marshmallow version ,as of writing, can ONLY get root using magisk!
You should backup all important data before attempting any of this as you will be losing all data during the process. Titanium backup is good for backing up and restoring apps, other personal files can be moved to external sd or copied to computer.
First off you will need to have fastboot installed on your PC if you havn't already. Find it here......
For windows. https://dl.google.com/android/repository/platform-tools-latest-windows.zip
For Mac. https://dl.google.com/android/repository/platform-tools-latest-darwin.zip
For Linux. https://dl.google.com/android/repository/platform-tools-latest-linux.zip
To gain ROOT access.....
1. download and extract the twrp.img file from the zip attached (YOU MUST EXTRACT FROM THE ZIP!!!) and copy supersu.zip or magisk.zip to tablets external memory card. https://download.chainfire.eu/696/SuperSU/ (LOLLIPOP only supersu v2.46 is supported, other versions cause bootloop) or https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 for MARSHMALLOW.
2. unlock your tab if is not unlocked (this is mandatory in order to boot custom images like TWRP recovery):
a) Enable developer options ( Go settings, at bottom select "About tablet" then press "Build number" 7 times. congrats you are now a developer.)
b) Go back to settings and now at the bottom there is a new option "developer options" in developer options enable "OEM unlocking"
3.Restart in fastboot mode (hold volume + while powering on tablet)
4. In the same foler you have extracted your TWRP.img (in windows) hold shift key while right clicking in the explorer window, select open command window here.
5. At the command prompt (black window that opens) type "fastboot oem unlock" for LOLLIPOP or "fastboot flashing unlock" for MARSHMALLOW. at this point you will be prompted that you want to delete all data, this is obviously a security measure that cannot be avoided.
6. go to step 7.
7. In command window (the little black window you opened earlier) type "fastboot boot twrp-2.8.7.0(6)-x90.img" your tablet should now boot to TWRP. ( This is a live session TWRP has not been flashed to your tablet)
******MAKE A TWRP BACKUP!!!!!!!!!!********* DO NOT SKIP THIS STEP.
Modifying system files will mean that you are unable to take Lenovo OTA Updates, the only way to install new updates is to later restore your TWRP stock backup, then reROOT. thats just the way it is i am afraid.
8. in TWRP install SuperSU.zip (lollipop) or magisk.zip (marshmallow) located at your external memory card.
9. Thats it enjoy Your rooted tablet.
10. If you experience time changing upon reboot use your favourite method to edit build prop, I used buildprop editor found in the playstore. Find "persist.sys.timezone" and change it to your location, I had to set mine to Europe/London.
PS...your tablet will hang on every boot at bootloader error 3 to warn about the unlocked bootloader, PLEASE DO NOT lock your bootloader, this is a small annoyance and makes brick recovery much easier. (just restore your lovely TWRP stock backup.
In order to install new Lenovo OTA update you must restore your TWRP stock backup, then take the OTA, then go through the root process again making a new TWRP stock backup after applying the new OTA.
Just one more BIG WARNING, this twrp comes with an option to reboot to bios. Be warned if you don't know what you are doing and you mess something up in there, FULL BRICK! no one will be able to help you recover.
PPS...there seems to be some issues with using magisk modules on our tab. To install them one must download them and then manually install them from twrp.
https://download.chainfire.eu/696/SuperSU/
Now for the real magic.
this can be achieved with or without root! just make sure, as per the ROOT instructions, the first thing you do in TWRP is make a full backup.
As a yoga tab 3 pro owner you know that your tablet lags, crashes and is generally buggy, mine would frequently crash during periods of long sleep.
there is a solution to this problem that is rather simple but seems to yield huge results. if we just run our tablet with the data partition unencrypted it runs like any other nice android device.
once again myself or the developer take no resposibility for your actions if you would like to try this.
instructions by ionioni.
""encryption of the 'data' partition (the one that holds your installed apps, personal stuff etc) is forced on these devices (even with no password set) the 'data' partition is automatically encrypted at boot time if it 'sees' an un-encrypted 'data' partition. in order to disable the enforced 'data' encryption i made a script that will disable the forced encryption flag in the existing boot (partition) image (encryption can still be triggered by the user in the Settings->Security panel). this will not decrypt an encrypted 'data' partition! will just allow you to boot having an un-encrypted 'data' partition."".........ionioni
1. make sure that when you make your TWRP backup that you include the boot partition (it will be patched by the script to disable forced encryption).
2. copy attached x90-disable_encr.zip to your tab and install from TWRP (once finished it will create also a backup of your original boot partition in the folder where the zip is located, however this is only a safety backup as you should have already backed up your Boot partition when making your TWRP backup)
3. **DO NOT SKIP THIS STEP** to finish, reboot in fastboot mode and input "fastboot format data" in order to have a clean(un-encrypted) 'data' partition on the next boot (and it will no longer be automatically encrypted as long as you have the modified boot)
alternatively you can format 'data' from within TWRP if you use the attached 'data' enabled TWRP.
i can confirm that since i have been running my tablet unencrypted using ionionis zip that i hav had no lagging, no crashing. runs just like any other android device. The kernel memory hog still remains but it works silky smooth.
Should anything go wrong stock rom for MARSHMALLOW can be found here...
https://forum.xda-developers.com/thinkpad-tablet/general/yoga-tab-3-pro-debrick-method-t3776951
Thank you for continuing the work !
Do you have compared the difference between encrypted/decryptet - is it worth to do all the stuff (root, etc.) ?
If you have to say a number in percent, how faster will it be ? You've tested multi-user (2nd user) ? If i setup a second user the tablet is nearly unusable - it's better with disabled encryption?
Sorry that i have a lot of questions, but it sounds not that easy and i think about it if its worth to do it
edit:
if i make a full backup - where is the backup of TWRP stored? Do i need a sdcard? Will it be overwritten by OTA/Update/Rooting/Decryption?
thx for your answers already.
I havnt tried with a second user. I could try for you.
before unencryption performance was sluggish. after unencrypted its just fine.
I know it seems like a lot of detail but it is actually easier than it sounds.
You don't have to have root to run the unencrypted stuff but you still need to oem unlock and make a full backup. Backup must be on external media, either ext sd or usb otg.
Your data would not be mountable in twrp unless unencrypted already. And then if you ever accidentily encrypted you ay be forced to format losing your backups.
External media is the way to go.
Sent from my SAMSUNG-SGH-I317 using Tapatalk
If i try "decryption" than root is not far away (so i also get rid of some "lets say useless" system apps)
If ýou can try to check for multiuser you should have running facebook on both accounts (cause fb need a lot of ram and cpu)
maybe i will try it on weekend. i'll think about it....
What about the other peoples who own this tab?
gtx, juergen
Well I would always go ROOT, as it offers more choice, but of course the choice is ultimately yours.
I can try multi users but unfortunately I am one of those weirdos that does not use facebook. I guess I could try a couple of instances of chrome/Firefox.
Sent from my SAMSUNG-SGH-I317 using Tapatalk
Ok just set up a new user switched between them ran chrome on both with several tabs open. didn't seem too bad.
Indeed more feedback from other users who have benifitted from unencrypted data partition would be useful.
Sent from my SAMSUNG-SGH-I317 using Tapatalk
Thanks for your effort.
Hello,
BIG THANKS for your Root solution !
All working !!! thanks !!
All thanks to ionioni, this is all his work, i was just the guinea pig. Glad you have root, did you run the unencryption zip?
Sent from my Lenovo YT3-X90F using Tapatalk
Thanks ionioni and joesnose!
I rooted my device and ran the unencryption zip, it definitely makes everything a little smoother.
Also, I successfully mounted my exFAT sdcard with the help of lurker0's post here: http://forum.xda-developers.com/showthread.php?t=3126394.
Nice. Thanks for the exfat find.
Sent from my SAMSUNG-SGH-I317 using Tapatalk
joesnose said:
Indeed more feedback from other users who have benifitted from unencrypted data partition would be useful.
Click to expand...
Click to collapse
Since the old thread is locked, I'll repeat myself here:
I rooted my YT3-X90F and decrypted it as well. Result is better overall performance (some1 asked rating in percentage, I would say +40% speed & +60% response).
But, sadly, it still needs restart every ~24hours, because all the freezes and lags come back with time.
Advise:
For those who want to root this device only to make it work with Sixaxis controller - don't even start. Yoga T3 doesn't support required bluetooth drivers (huge shame on Lenovo).
doesn't seem to connect to the ds4 either. Just sticks at pairing.
Sent from my GT-N7105 using Tapatalk
Hi Joesnose and thanks for putting the instructions up (and of course, thanks to ionioni).
I have a couple of questions.
EDIT; oh pants, I have some more (possibly stupid) questions - just to be sure I know what I'm doing !
In the very first instructions about rooting:
1. I download the twrp.img.zip to my PC and unzip it to PC right ?
2. And the SuperSu goes in my ext SD card, not on the PC ?
3. I assume I must connect the YT3 Pro to the PC at some point ? When would that be ??
4. I don't understand instruction 7. It says type "fastboot boot twrp-2.8.7.0(6)-x90.img". Do I need to have that file downloaded or something ? What is twrp-2.8.7.0(6)-x90.img file ?
And what does it mean, "This is a live session TWRP has not been flashed to your tablet" ?
I can see that in the section about unencrypting the data partition that there is a file with a similar name to " twrp-2.8.7.0(6)-x90.img' but it has the words "data-enabled" in the fine name. I'm not sure what to do with this ??
5. At what point do I take a back-up of the original YT3 Pro stock image ? It's listed between 7 and 8 ? Do I do it right after 7 ? How do you make the back-up please ? And I guess I better store another copy somewhere safe, off the SD card too ?
6. If I just root this, can I then get OTA updates normally ? (without having to restore to stock).
7. And, if I do root and/or data unencryption, can the YT3 Pro be put back exactly how it was before changing anything ? Including it getting OTA updates normally ?
8. How do I make back-ups of apps while the YT3 Pro IF I wanted to restore those apps later on on an UNrooted YT3 Pro ? I don't know why I'd want an UNrooted YT3 Pro in the future, but for instance, if I used Titanium Backup, that needs root right ?? For instance, if I want to restore data from a Titanium Backup on an UNrooted YT3 Pro, will it work ? Or can I use something else ?
Sorry about all the questions - I can't believe I've rooted and installed custom ROMs for 4 devices - for some reason this seems different to the others and it was a while ago !
Thanks in advance
Frenchdroid said:
Hi Joesnose and thanks for putting the instructions up (and of course, thanks to ionioni).
I have a couple of questions.
EDIT; oh pants, I have some more (possibly stupid) questions - just to be sure I know what I'm doing !
In the very first instructions about rooting:
1. I download the twrp.img.zip to my PC and unzip it to PC right ?
2. And the SuperSu goes in my ext SD card, not on the PC ?
3. I assume I must connect the YT3 Pro to the PC at some point ? When would that be ??
4. I don't understand instruction 7. It says type "fastboot boot twrp-2.8.7.0(6)-x90.img". Do I need to have that file downloaded or something ? What is twrp-2.8.7.0(6)-x90.img file ?
And what does it mean, "This is a live session TWRP has not been flashed to your tablet" ?
I can see that in the section about unencrypting the data partition that there is a file with a similar name to " twrp-2.8.7.0(6)-x90.img' but it has the words "data-enabled" in the fine name. I'm not sure what to do with this ??
5. At what point do I take a back-up of the original YT3 Pro stock image ? It's listed between 7 and 8 ? Do I do it right after 7 ? How do you make the back-up please ? And I guess I better store another copy somewhere safe, off the SD card too ?
6. If I just root this, can I then get OTA updates normally ? (without having to restore to stock).
7. And, if I do root and/or data unencryption, can the YT3 Pro be put back exactly how it was before changing anything ? Including it getting OTA updates normally ?
8. How do I make back-ups of apps while the YT3 Pro IF I wanted to restore those apps later on on an UNrooted YT3 Pro ? I don't know why I'd want an UNrooted YT3 Pro in the future, but for instance, if I used Titanium Backup, that needs root right ?? For instance, if I want to restore data from a Titanium Backup on an UNrooted YT3 Pro, will it work ? Or can I use something else ?
Sorry about all the questions - I can't believe I've rooted and installed custom ROMs for 4 devices - for some reason this seems different to the others and it was a while ago !
Thanks in advance
Click to expand...
Click to collapse
Ok let me see if I can help.
1. Yes
2. Yes
3.you must have the yt3 connected to your pc as the commands will be sent from your pc. Tablet must be in fastboot mode.
4. Yes sorry, when you extract the twrp.zip the file is called "twrp-2.8.7.6(0)-x90.img"
the twrp recovery is not flashed to your tablet it is just loaded temporarily, in a live session. Once rebooted it is gone. Normal recovery is not overwritten.
To run the unencrytption script one must be in twrp.
5. As soon as you get twrp loaded make a backup to either external sd or usb and yes not a bad idea to have a backup of your backup.
6. No
7. Yes, simply restore your backup before taking an ota update.
8. not sure about this one.
Indeed it appears like a lot of instructions but once you get into it its just like any other device.
Hope that helps.
Sent from my GT-N7105 using Tapatalk
Big thanks for the answers - makes more sense now, especially the bit about a recovery session as I'm used to installing clockwork and using it on the device.
You can install twrp to your device but only do this after you have made a backup from a live session, making sure of course that your backup contains the original recovery.
Sent from my GT-N7105 using Tapatalk
joesnose said:
You can install twrp to your device but only do this after you have made a backup from a live session, making sure of course that your backup contains the original recovery.
Sent from my GT-N7105 using Tapatalk
Click to expand...
Click to collapse
Oh, ? At what point does twrp get installed and how do you do that?
And is it obvious how to include the original recovery in the backup?
I thought I had it nailed!
I found only one way to root the galaxy s7 edge but it includes erasing everything and thats just too much trouble for me since i don't trust backup apps with my apps data and all
my model is sm-935FD
this the method i found :
https://youtu.be/nlj76YvxGYo
thank u
You don't need to erase everything, that is complete horses**t.
First off you need to confirm you have the Exynos international version. If you're on the Snapdragon version, you're s**t out of luck as the bootloader is locked and root isn't possible at this time, nor will it likely ever be.
You then have two option, install CF Autoroot from ODIN and leave your recovery as stock. Or install TWRP over your recovery via ODIN and install SuperSU from a zip file from within TWRP. Either way you won't lose data. See the following threads.
CF Autoroot -- http://forum.xda-developers.com/s7-edge/development/sm-g935-exynos-cf-auto-root-t3337354
TWRP - http://forum.xda-developers.com/s7-edge/development/recovery-official-twrp-hero2lte-3-0-0-0-t3334084
You only need to erase everything if you want to flash custom roms in twrp. Otherwise you can just root with cf autoroot and you're all set
As the others said, flashing cf autoroot in odin won't erase anything, will leave your phone as is and will add supersu.
You should be aware that by rooting you will trip the knox flag, which permanently breaks samsung pay, and will break the following stuff on the stock rom: private mode, secret mode in the browser with fingerprint authentication (which can later be fixed by flashing a custom Rom).
If you want a properly working twrp recovery, you will have to erase everything, including the internal storage of the phone, there is no way around it.
If you absolutely must have root and you're into custom roms then I say do it now, if you're OK with the stock firmware I would advise not to root. This phone doesn't have too much development and you should not expect too many custom ROMs. I personally regret rooting.
I'm erase mi data because I want to do twrp backups, if you don't want to use a custom recovery for flash Roms and use a nandroid only flash supersu.
Beefheart said:
You don't need to erase everything, that is complete horses**t.
First off you need to confirm you have the Exynos international version. If you're on the Snapdragon version, you're s**t out of luck as the bootloader is locked and root isn't possible at this time, nor will it likely ever be.
You then have two option, install CF Autoroot from ODIN and leave your recovery as stock. Or install TWRP over your recovery via ODIN and install SuperSU from a zip file from within TWRP. Either way you won't lose data. See the following threads.
CF Autoroot -- http://forum.xda-developers.com/s7-edge/development/sm-g935-exynos-cf-auto-root-t3337354
TWRP - http://forum.xda-developers.com/s7-edge/development/recovery-official-twrp-hero2lte-3-0-0-0-t3334084
Click to expand...
Click to collapse
Glad I came across this thread, as I was having the same thoughts. How easy is it to just flash recovery back to stock? or do you need to flash the complete firmware package?
TwinCalibre said:
Glad I came across this thread, as I was having the same thoughts. How easy is it to just flash recovery back to stock? or do you need to flash the complete firmware package?
Click to expand...
Click to collapse
Flashing the whole fw of course 1 of the way. Maybe if we can extract stock recovery from the fw then just odin it?.
Sent from my SM-N920C
if your on nougat and try to flash TWRP, your device wont boot....they dont have a decrypt solution to 7.0 right now.
Beefheart said:
You don't need to erase everything, that is complete horses**t.
First off you need to confirm you have the Exynos international version. If you're on the Snapdragon version, you're s**t out of luck as the bootloader is locked and root isn't possible at this time, nor will it likely ever be.
You then have two option, install CF Autoroot from ODIN and leave your recovery as stock. Or install TWRP over your recovery via ODIN and install SuperSU from a zip file from within TWRP. Either way you won't lose data. See the following threads.
CF Autoroot -- http://forum.xda-developers.com/s7-edge/development/sm-g935-exynos-cf-auto-root-t3337354
TWRP - http://forum.xda-developers.com/s7-edge/development/recovery-official-twrp-hero2lte-3-0-0-0-t3334084
Click to expand...
Click to collapse
Have anyone tried and successfully done it?
there are many ways to root
I recommend use TWRP to root with SU apk file
Beefheart said:
You don't need to erase everything, that is complete horses**t.
First off you need to confirm you have the Exynos international version. If you're on the Snapdragon version, you're s**t out of luck as the bootloader is locked and root isn't possible at this time, nor will it likely ever be.
You then have two option, install CF Autoroot from ODIN and leave your recovery as stock. Or install TWRP over your recovery via ODIN and install SuperSU from a zip file from within TWRP. Either way you won't lose data. See the following threads.
CF Autoroot -- http://forum.xda-developers.com/s7-edge/development/sm-g935-exynos-cf-auto-root-t3337354
TWRP - http://forum.xda-developers.com/s7-edge/development/recovery-official-twrp-hero2lte-3-0-0-0-t3334084
Click to expand...
Click to collapse
In nougat it will disable access to data folder and force you to format, but if you flash stock firmware nougat the same it was in and reboot it everything was like before.
Basically backup everything using non root apps and adb then format then restore.
Today I accidentally did oem unlock to OFF then rebooted and then it said custom binary blocked by frp. I then flashed many nougat versions but they all caused force close of 2 things ims service and srbg? I ended up flashing nougat from January 2017 dqlc. I got everything back and working. Next I did twrp and supersu etc but data encryption failed. Then I flashed stock dqlc and got everything back. Use home csc or otherwise it will erase everything. Now I have to backup everything.
Beefheart said:
You don't need to erase everything, that is complete horses**t.
Click to expand...
Click to collapse
That's not horse**** at all. If your storage is encrypted (most of them are by default) then it will force you to format once you flash TWRP. I took ages of trial and error of flashing stock firmwares and bootloaders etc via Odin to get it all back as I couldn't afford wiping (even if I had backed up).
Anyone reading this thread and wanting to try it should be careful.
I also found no way to backup ALL apps and ALL their data & settings reliably without root (Helium gets only part of the job done) so I could not risk wiping and restoring. I have too many apps configured and fined tuned that I use regularly.
Sorry for necro, but I found out the hard way after being badly advised ...
mastabog said:
That's not horse**** at all. If your storage is encrypted (most of them are by default) then it will force you to format once you flash TWRP. I took ages of trial and error of flashing stock firmwares and bootloaders etc via Odin to get it all back as I couldn't afford wiping (even if I had backed up).
Anyone reading this thread and wanting to try it should be careful.
I also found no way to backup ALL apps and ALL their data & settings reliably without root (Helium gets only part of the job done) so I could not risk wiping and restoring. I have too many apps configured and fined tuned that I use regularly.
Sorry for necro, but I found out the hard way after being badly advised ...
Click to expand...
Click to collapse
And finaly do you find a way to restore your data after installing TWRP ?
By now I would hope your important data is 100% redundantly backed up.
Of all the things that can and do go wrong with rooting, data lose shouldn't even enter into the equation unless you really goofed up bad.
Only two types of data users, those who have lost data and those that will...
I consider any data on internal memory 100% expendable. A complete reload/restore takes me about 2 hours and that's without the luxury of rooting.
At any moment I'm (and you should be too) ready to do a factory reset regardless of the cause without critical data lose.
After two forced back to back forced reloads on my 10+ I learned my lesson.
Thanks Blackhawk for your explication
I am on the second part of user which have lost his data but only the configuration not the contact, photo, etc...
But without root they are plenty of data (configuration, autorisation, widget) which take very long time to "reinstall" and those data are not saved if you are not root. And sometime with root also. They are not important but the time to restore them is very long and use a phone without his custumization is very anoying.
That's why I'm loocking for a way to save it without root or root without loosing those data.
jameslevalaisan said:
Thanks Blackhawk for your explication
I am on the second part of user which have lost his data but only the configuration not the contact, photo, etc...
But without root they are plenty of data (configuration, autorisation, widget) which take very long time to "reinstall" and those data are not saved if you are not root. And sometime with root also. They are not important but the time to restore them is very long and use a phone without his custumization is very anoying.
That's why I'm loocking for a way to save it without root or root without loosing those data.
Click to expand...
Click to collapse
A clean wipe of all settings data means no misconfigurations or malware will survive.
Nuke em.
I'll see how well SmartSwitch does saving the home page next reload. If it screws up it will cost another reload... of course.
Only shortcuts/folders, Good Lock, One Handed Operation plus etc kill me with setup time but it's no big deal. I've gotten pretty adapt at it
Poweramp is completely, redundantly, backed up as that would take weeks to sort of recreate, a true nightmare... as it is now, it only takes a few minutes to do.
My music database has existed for over 15 years. I've lost count of the number of backup copies I have for it... plus the source CD/HDCDs.
Currently have 3 up to date copies to be expanded soon to 4.
Overkill for data backup is a good thing.
My phone has been down for over two weeks due to a stupid mistake that I made. Thank you in advance for any assistance that the community is able to provide. The problem in detail is:
(1) Using an earlier version of the powerful BK Disabler app, which exposed individual services within each app and permitted selectively disabling services, I was a bit too aggressive and disabled some system service required for booting the phone. (Shame on me, of course.) The phone boots through the Android sequence, displays the TMO boot screen, sounds the TMO boot zingle, and then freezes and overheats if left in that state, requiring battery removal. Of course nothing is visible at the USB port because the OS is not functioning and therefor the regular USB driver is not functioning. Thus, I cannot get to my data files. Fortunately, the stock recovery USB driver IS funtioning.
(2) The silly Samsung Smart Switch was not working correctly and at each backup has been telling me for over a year that some of my data was not backed up. Of course, you know the old story, "my whole life" is in the phone and I simply cannot lose it. Thus, I am trying to be very careful about what portions of the stock system that I flash to the phone in order to avoid a factory reset scenario.
(3) I have not messed with phone flashing/ROM installation since rooting my original Galaxy S Vibrant back in the day; so I am a bit rusty. The good news is that I can boot into stock recovery, where I can see the currently installed system version: G900TUVU1GQC2 (6.0.1/MMB29M/G900TUVU1GQC2). That appears to be the last-released TMO version, released March 1, 2017. I have downloaded: G900T_TMB_G900TUVU1GQC2_G900TTMB1GQC2_Original.zip from Sammobile. The latter file unzips to: (the same firmware name)_HOME.tar.md5. If I delete the ".md5" from the tar filename, I can uncompress the file to the following eleven component files:
cache.img.ext4 (73,145 KB)
system.img.ext4 (2,377,317 KB)
NON-HLOS.bin (8,581 KB)
boot.img (12,377 KB)
recovery.img (14,095 KB)
aboot.mbn (1,037 KB)
rpm.mbn (224 KB)
sdi.mbn (56 KB)
tz.mbn (354 KB)
sbl1.mbn (311 KB)
modem.bin (54,066 KB)
(4) Specifically, I need to know:
(4)(a) In what portion of the system does BK Disabler set the "no run" flags for apps/services disabled by the user? That is likely the portion of the system that I need to flash over with a fresh image in order to get rid of the flags. I assume that it is "system.img.ext4" but not sure.
(4)(b) The tar file downloaded from Sammobile appears to be the entire stock ROM. It is labeled "_HOME.tar.md5". I have read that flashing using a "CSC_HOME" in the Odin CSC slot will result in a non-destructive flash, which is what I need. However, I can see no file at all labeled "CSC" in the decompressed files (unless "cache.img.ext4" is the CSC file). And even if "cache.img.ext4" is the CSC file, it is not labeled "HOME" in the filename.
(4)(c) I tried flashing only the stock recovery image file in the Odin AP slot, per an old post in the XDA Galaxy S5 General Discussion sectiont (https://forum.xda-developers.com/gal...lipop-t3228871), but no joy.
(4)(d) Thus, I am looking for sage guidance as to what to flash in order to get past the TMO boot screen/jingle without destroying data. Although it seems like overkill, I will just try flashing the stock _HOME.tar.md5 image in the Odin 3.13.1 "AP" slot if I can get some reassurance that doing so will not overwrite my data or format my flash memory.
(4)(e) If I do (4)(d), should I expect my system settings to be retained or to be reset to factory default? If they are reset to factory default, is there a backup file somewhere on the system that I could get to after rooting in order to restore my current system settings? Or does one of the eleven component files in the stock tar image contain default system settings? In the latter case, could I delete that file from the stock tar image in order to prevent overwriting my current system settings?
(4)(f) If I do (4)(d), should I leave the .md5 suffix appended to the file or rename the file by deleting the ".md5" suffix?
I realize that answers to these questions tend to involve developer-level expertise, so I am grateful to anyone who has the knowledge and takes the time to look over my way-too-long post and to think about my problem.
P.S. I promise myself to never, ever fail to root a new phone and create regular nandroid backup images; individual file backups just won't cut it when the phone dies...
PPS. OTA updates and updates via Kies/Samsung Switch, even to new major Android releases, do not delete user data, including photos, contacts, calendar, phone call log, text msgs, downloaded apps, app data, etc. And even system settings are retained, to the degree that they are compatible betweeen Android version releases. So obviously there is a way to flash over the same OS version without data loss. I just need to be sure that the components of the flash image downloaded from Sammobile (as described above) includes the same system components as would be included in an equivalent OTA update and not some script that formats partitions or wipes data before or after the flash. There appears to be some confusion about this, as some swear that user data is retained and others swear that data is lost in the process. The answer to this cannot be an opinion, because computers are state machines and always behave in the same way for a given execution path. Could someone with a definitive answer please help me with this question before I do the Odin flash of the Sammobile Home.tar.md5 system image? Tks!
The first thing you should do and test if it works:
How do I start my Samsung Galaxy S5 in Safe Mode?
The second thing is (will trip the Knox flag and won't work on encrypted phone or when Reactivation Lock is ON):
1. Download TWRP, flash it with Odin, boot TWRP and connect to your PC.
2. Pull everything you need from phone's internal storage and save it somewhere.
3. Make a backup of /data partition and save it somewhere.
The Knox flag will be tripped but the "whole your life" will be backed up in a secure place.
And then decide if you still need the answers on your questions.
Thank you, bbsc! I did not realize that I could access my "whole life" from the TWRP recovery environment. I will follow your instructions and report.
Thank you most sincerely, bbsc!
bbsc said:
The first thing you should do and test if it works:
How do I start my Samsung Galaxy S5 in Safe Mode?
The second thing is (will trip the Knox flag and won't work on encrypted phone or when Reactivation Lock is ON):
1. Download TWRP, flash it with Odin, boot TWRP and connect to your PC.
2. Pull everything you need from phone's internal storage and save it somewhere.
3. Make a backup of /data partition and save it somewhere.
The Knox flag will be tripped but the "whole your life" will be backed up in a secure place.
And then decide if you still need the answers on your questions.
Click to expand...
Click to collapse
Using the fabulous TWRP environment I was able to do individual file backups of my internal data and a complete Nandroid of the device; so very relieved about those files now residing safely on my RAID system! (I had already tried safe boot with no luck.)
Now that my data is secure, I can probably restore boot to the device by re-flashing the stock ROM; but then I would face hours of reconfiguration. I contacted the BK Disabler developer to ask about how his disabler works. However, he did not answer the question but rather insisted that I a factory reset and data loss were the only option. Thankfully he was wrong about that (thanks to your TWRP suggestion)!
I am thinking that BK Disabler must disable/re-enable apps andservices by changing some "disable execution" file permission (e.g., as one could do with ADB using the command "pm disable app_xyz.com"). If that is the case, might I restore boot by doing a "fix permissions" on the system? (My logic is that "disable execution" is an unnatural permission for a system file and so hopefully those would be reset to "enable execution." I would like to try that, unless someone warns me of some great danger in doing so. Apparently earlier versions of TWRP had a "Fix Permissions" button on the Advanced menu. However, my TWRP v3.2.1-0 has a "Fix Contexts" button at the location where the "Fix Permissions" button was before. I cannot find much information on what actions "Fix Contexts" performs. Is it the same as "Fix Permissions" by a different name?
(Although theoretically I could do multiple "pm enables" with ADB, I disabled close to 200 apps and services; so finding all of those would be a nightmare. And, so far as I can tell, there is no wildcard for the "pm" commands in ADB. "Fix permissions" is probably a script.)
I would appreciate any input on this last question before I either press "Fix Contexts" or re-install the OS.
Many thanks!
Bruce
Continuation of the BK Disabler Saga...
BruceElliott said:
Using the fabulous TWRP environment I was able to do individual file backups of my internal data and a complete Nandroid of the device; so very relieved about those files now residing safely on my RAID system! (I had already tried safe boot with no luck.)
Now that my data is secure, I can probably restore boot to the device by re-flashing the stock ROM; but then I would face hours of reconfiguration. I contacted the BK Disabler developer to ask about how his disabler works. However, he did not answer the question but rather insisted that I a factory reset and data loss were the only option. Thankfully he was wrong about that (thanks to your TWRP suggestion)!
I am thinking that BK Disabler must disable/re-enable apps andservices by changing some "disable execution" file permission (e.g., as one could do with ADB using the command "pm disable app_xyz.com"). If that is the case, might I restore boot by doing a "fix permissions" on the system? (My logic is that "disable execution" is an unnatural permission for a system file and so hopefully those would be reset to "enable execution." I would like to try that, unless someone warns me of some great danger in doing so. Apparently earlier versions of TWRP had a "Fix Permissions" button on the Advanced menu. However, my TWRP v3.2.1-0 has a "Fix Contexts" button at the location where the "Fix Permissions" button was before. I cannot find much information on what actions "Fix Contexts" performs. Is it the same as "Fix Permissions" by a different name?
(Although theoretically I could do multiple "pm enables" with ADB, I disabled close to 200 apps and services; so finding all of those would be a nightmare. And, so far as I can tell, there is no wildcard for the "pm" commands in ADB. "Fix permissions" is probably a script.)
I would appreciate any input on this last question before I either press "Fix Contexts" or re-install the OS.
Many thanks!
Bruce
Click to expand...
Click to collapse
Well... I wound up flashing to stock via Odin, rooting with SuperSu and then restoring the /data partition from TWRP. My idea was/is to undo whatever BK Disabler did, given that I have shell command line access now to the entire system from the root directory down from the TWRP environment.
However, after much reading it appears from the app's permissions that KunkunSoft, the BK Disabler dev, is using Samsung's Knox-related Mobile Device Management ("MDM") functionality to put devices using BK Disabler into "Kiosk" mode. Normally, kiosk mode is used to limit the device to running just a few apps and control the display, etc. for demo purposes. However, it appears that he is using this mode in reverse, by including all apps in the kiosk mode other than those selected for disabling. I'm not absolutely sure about that, but it appears to be the case, reading from his web page describing the required permissions for the app.
If so, the question is how to disable this stupid "kiosk mode" from the Linux shell, booted into TWRP. I was able to flash to stock and can boot to stock and start all over; but I'm trying to avoid rethinking about 4-5 years of configuration and tweaking of my beloved S5.
I thought that this project would simply be a matter of changing permissions on a few files, but no such luck. It appears that I must somehow disable kisosk mode, the MDM system, or Knox altogether to get past this hurdle.
Suggestions, anyone?
Thanks,
Bruce
Is there any way to be root without TWRP?* I'm in Oreo and I lost my Imei and cell coverage*. However, I have my backing of the EFS folder. But I can't stick it in the root without being root.
I know I have to wait 8 days for the OEM unlock to activate (I even used the trick to not wait 8 days and it worked for me). And be able to use twrp and install Root per zip file.
But now I haven't been able to do the trick because I can't log in to the samsung account*(Procesing Failed). My fear is that the 8 days will pass and since I cannot log in to my samsung account, the OEM unlock will not be activated even after 8 days.
In short, it would be a great help if anyone knew of these 3 options.
*1.- If you can be root without installing twrp.
*2.- If someone knows how to log in to samsung account, when the error message ("Procesing Failed") appears. I've erased cache of all samsung applications, I've reestablished it from the factory. I have installed full Stock firmware and nothing yet.
*3.- Recover IMEI in another way (I have a TWRP EFS Backup (I already restored it but it didn't work) and I have backup of the EFS folder to replace with the root.
Image that could possibly be useful for point 2.
Knox status: https://ibb.co/kjt908 In download mode it appears as (0x030c).
Download mode: https://ibb.co/nuMySo
Translated with www.DeepL.com/Translator
I found something about point 1, about how to rotate without using a TWRP.
https://forum.xda-developers.com/u12-plus/how-to/guide-how-to-root-u12-magisk-tips-tricks-t3802583
Will there be something similar for our device?.
I welcome any input on the subject. (Y)
Starting from a non-rooted SM-G950W with a locked version 7 bootloader, what does it take to make a disk image backup (like with `dd` or `adb pull`) of the /data/media, without first destroying the data that's there? Is it even possible?
I ask because I did something dumb that truncated (not deleted) all files in shared storage to 0 bytes. If I could take a disk image of /data/media, I'd be able to use offline recovery programs (like PhotoRec) to restore what was on there, but I'm currently blocked from doing that since my phone isn't rooted.
I could root my phone, but it looks like most options for rooting involve wiping out /data/.
After having done some research, it appears that I may have the following options:
Install a custom recovery like TWRP, which will grant me root access in Recovery Mode that I can use to make a disk image. The problem is that my bootloader (version 7) is locked, meaning I'd need to use Safestrap, but that apparently requires root. Is it possible to install an additional custom recovery with a locked bootloader (as opposed to replacing the built-in one) without rooting first, or am I out of luck?
Install an additional custom ROM that has root, leaving the phone's original ROM intact as opposed to replacing it, if that even makes sense.
I think I've gone in circles about what the requirements are for installing a custom recovery or ROM. This post in a G950 rooting thread says it's possible to install a custom recovery image that has root access (at least on the S8+):
https://forum.xda-developers.com/showpost.php?p=81922221&postcount=9
The linked instructions are for installing a custom ROM with Safestrap:
https://forum.xda-developers.com/verizon-galaxy-s8+/development/rom-t3771206
But the link for G950W leads back to the G950 rooting thread, which requires wiping /data/:
https://forum.xda-developers.com/galaxy-s8/development/root-t4060701
Also, the Safestrap install guide says that root is a requirement:
https://forum.xda-developers.com/galaxy-s8/development/recovery-locked-nougat-7-0-safestrap-t3772760
Is there a solution here, or are all options locked out?
Thanks in advance!