Database Users

Updated to rooted OK4 keeping knox counter at 0

This morning I was able to update my rooted phone to OK4 from OD3 keeping root and my Knox counter at 0 using metalfan78's [ROM]OK4 Stock Rooted Zip, and stock partitions from the full tar. I was able to use Flashfire to create the stok partitions tar and flash them via Odin. I did this based on another thread I followed to update to OD3 to keep root and Knox at 0 a while back. So far everything seems to be working good for me, I dirty flashed and everything seems to have gone like taking an OTA update.
I got the ROM here and used the odexed version:
http://forum.xda-developers.com/spr...rom-ok4-stock-rooted-zips-12-16-2015-t3272692
Stock partitions file is save to my google drive here, it contains everything from the full tar except the system and cache (not sure how well sharing like this will work):
https://drive.google.com/file/d/0Bw7_CzqViQzSSGZHSE1TS3loN1E/view?usp=sharing
Followed the instructions for the update to OD3 here:
http://forum.xda-developers.com/spr...w-to-update-to-g900pod3-5-0-keeproot-t3136932
Hopefully this will help someone get updated, or just provide stock partitions for other use.
If Knox is already tripped this probably isn't worth the effort
You MUST be rooted already for this to work.
Edit:
1. After a couple hours S Health stopped working about every 5 seconds, making it difficult to do anything. Clearing the data and signing back in seems to have fixed it.
2. Play store continuously fails to download app updates on WiFi or Mobil data.
3. Wiped and reinstalled the ROM with Flashfire on Jan 1. I have not had any issues since.

Thank ya for this post, it has actually been a while since I have updated my phone. I haven't had any issues with any of the apps thus far. It's been a little over 24 hours since I've updated. Also, I think my phone runs a lot smoother with the update than it use to. Also, I don't have any issues with the play store updating. I'll post issues if any occurs.

dave011182 said:
This morning I was able to update my rooted phone to OK4 from OD3 keeping root and my Knox counter at 0 using metalfan78's [ROM]OK4 Stock Rooted Zip, and stock partitions from the full tar. I was able to use Flashfire to create the stok partitions tar and flash them via Odin. I did this based on another thread I followed to update to OD3 to keep root and Knox at 0 a while back. So far everything seems to be working good for me, I dirty flashed and everything seems to have gone like taking an OTA update.
I got the ROM here and used the odexed version:
http://forum.xda-developers.com/spr...rom-ok4-stock-rooted-zips-12-16-2015-t3272692
Stock partitions file is save to my google drive here, it contains everything from the full tar except the system and cache (not sure how well sharing like this will work):
https://drive.google.com/file/d/0Bw7_CzqViQzSSGZHSE1TS3loN1E/view?usp=sharing
Followed the instructions for the update to OD3 here:
http://forum.xda-developers.com/spr...w-to-update-to-g900pod3-5-0-keeproot-t3136932
Hopefully this will help someone get updated, or just provide stock partitions for other use.
If Knox is already tripped this probably isn't worth the effort
You MUST be rooted already for this to work.
Edit:
1. After a couple hours S Health stopped working about every 5 seconds, making it difficult to do anything. Clearing the data and signing back in seems to have fixed it.
2. Play store continuously fails to download app updates on WiFi or Mobil data.
3. Wiped and reinstalled the ROM with Flashfire on Jan 1. I have not had any issues since.
Click to expand...
Click to collapse
I followed your instructions and everything went smoothly, but at least once a day I get a message saying: "Device must restart. Device will restart in 25 seconds.". Do you get this? Any suggestions on how to stop it from happening?

IMBigWillie said:
I followed your instructions and everything went smoothly, but at least once a day I get a message saying: "Device must restart. Device will restart in 25 seconds.". Do you get this? Any suggestions on how to stop it from happening?
Click to expand...
Click to collapse
Sorry for my delayed response.
I was having a random system reboot, and assumed it was from my bad habit of dirty flashing. I think what ultimately fixed it for me was using flashfire to flash the stock tar(as far as it recommended) and inject root. Metalfan recommend flashing via Oden and rooting before installing his rom, but that would have tripped kmix for sure. After flashing the stock tar via flashfire I had no data even on WiFi. I flashed Metalfan's rom to get me working again quickly and haven't had any random reboot issues recently. My knox counter is still at 0.
I'm sure I should recommend wiping data in this process but that's up to you. I can't say for sure that I did, then restored backed up data or not. I was pressed for time that morning, and needed my phone working.

dave011182 said:
Sorry for my delayed response.
I was having a random system reboot, and assumed it was from my bad habit of dirty flashing. I think what ultimately fixed it for me was using flashfire to flash the stock tar(as far as it recommended) and inject root. Metalfan recommend flashing via Oden and rooting before installing his rom, but that would have tripped kmix for sure. After flashing the stock tar via flashfire I had no data even on WiFi. I flashed Metalfan's rom to get me working again quickly and haven't had any random reboot issues recently. My knox counter is still at 0.
I'm sure I should recommend wiping data in this process but that's up to you. I can't say for sure that I did, then restored backed up data or not. I was pressed for time that morning, and needed my phone working.
Click to expand...
Click to collapse
Thanks for getting back so soon! I actually did a clean flash and still am having the issue ... I will definitely try your method tonight!

IMBigWillie said:
Thanks for getting back so soon! I actually did a clean flash and still am having the issue ... I will definitely try your method tonight!
Click to expand...
Click to collapse
You may also want to try using flashfire to create your own stock partitions tar to flash in this process to be sure my file on drive isn't somehow corrupted. If you used it in the first place. Use the flash firmware package option, wait for it to read the file partitions, then the download icon to create your partitions file. Use what's highlighted by default, create your file, and transfer it to your computer. Flash what is selected by default from the tar and reboot into download mode to flash the partitions file just created.
If all you want is stock root and your data works you shouldn't need to flash anything else at that point.

Extract Google Authenticator database from unrooted S4 i9505?

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.

[Q] XT1768 getting September Security Update

Hello all,
Been a LONG while since I've actively played around with rooting and unlocking an android device. I finally "upgraded" from my very aged Galaxy S4 to the Moto E4 XT1768. I have successfully unlocked the bootloader, got TWRP installed, rooted with Magisk, and gotten Xposed installed with my favorite modules.
This morning, I got a prompt that a new security update is available, and like a noob, I tried to take the update. This resulted in me getting stuck in a loop where the phone only wanted to boot into TWRP. I got that fixed thanks to XDA, got the pending and failing update completely cleared and am booted back into the device normally, and have frozen the moto update service.... but now...
Is there a way without completely flashing back to stock rom? I know how to take titanium or nand/twrp backups, but I feel like this would still be hours of work to go back to stock, flash, re-root restore all apps blah blah. what are the chances of there being a dirty-flashable zip put out at this point?

The way I normally do these type of upgrades is to download the firmware (from here), use fastboot commands to wipe (erase) and flash the needed partitions (everything but data and recovery), boot to TWRP - flash the no-verity-opt-encrypt.zip & root, and then reboot to system - done. It's easy enough for me, but I know some prefer to being able to use a flashable zip in TWRP.
Also, I have to ask - did you get your e4 cheap? It's was replaced by the e5, some other phones seem to be getting replaced like the G6 series (it's gone on clearance at some places), so they can be had cheap.

bast525 said:
Hello all,
Been a LONG while since I've actively played around with rooting and unlocking an android device. I finally "upgraded" from my very aged Galaxy S4 to the Moto E4 XT1768. I have successfully unlocked the bootloader, got TWRP installed, rooted with Magisk, and gotten Xposed installed with my favorite modules.
This morning, I got a prompt that a new security update is available, and like a noob, I tried to take the update. This resulted in me getting stuck in a loop where the phone only wanted to boot into TWRP. I got that fixed thanks to XDA, got the pending and failing update completely cleared and am booted back into the device normally, and have frozen the moto update service.... but now...
Is there a way without completely flashing back to stock rom? I know how to take titanium or nand/twrp backups, but I feel like this would still be hours of work to go back to stock, flash, re-root restore all apps blah blah. what are the chances of there being a dirty-flashable zip put out at this point?
Click to expand...
Click to collapse
Flashing back to stock and taking the updates is really the best way. Unless you can find a complete firmware package of the new update which of course takes back to stock as well. Really the only way to do it. @MotoJunkie01 makes some TWRP flashable stock roms. And he also creates the partition updater which updates your oem partition and other important things that can't be done in the Twrp flashable stock ROM.

madbat99 said:
Flashing back to stock and taking me updates is really the best way. Unless you can find a complete firmware package of the new update which of course takes back to stock as well. Really the only way to do it. @MotoJunkie01 makes some TWRP flashable stock roms. And he also creates the partition updater which updates your oem partition and other important things that can't be done in the Twrp flashable stock ROM.
Click to expand...
Click to collapse
Speaking of that, @ALI12 just posted a stock firmware package for the NCQS26.69-64-10 build. He gave me approval to use it to update my firmware thread to the latest build, so I'll be updating that OP shortly.

MotoJunkie01 said:
Speaking of that, @ALI12 just posted a stock firmware package for the NCQS26.69-64-10 build. He gave me approval to use it to update my firmware thread to the latest build, so I'll be updating that OP shortly.
Click to expand...
Click to collapse
This will be for the XT1766, correct? Or will same build work for XT1768 (me thinks not)?

So what would the easiest/quickest way be to get updated with all of my apps and data intact? Twrp backup of data partition? Or would there be any way to do this without wiping data at all?

bast525 said:
So what would the easiest/quickest way be to get updated with all of my apps and data intact? Twrp backup of data partition? Or would there be any way to do this without wiping data at all?
Click to expand...
Click to collapse
If you're going to slash a firmware package you'll want to wipe everything. Especially data. Make a backup of your data first of course. After you flash TWR P you can try restoring your data and see if everything comes back. but everything in your downloads folder and all of that will be gone once you format data to remove encryption again.

Help rooting and customizing your s6 edge plus

I was looking at the help section here recently and I noticed a fair number of people having issues being FPR blocked, failing to root, and bricking their device. There are some differences rooting this device from a normal s6 or other devices. First read this: https://forum.xda-developers.com/s6...ecovery-official-twrp-galaxy-s6-edge-t3354492
and get TWRP. on the site it says install the image with odin and boot into twrp immediately and flash super user to avoid any issues. This normally works ok, if you just want stock rooted. I have my own method that i use to REALLY avoid issues. Follow their tutorial until the point of being in TWRP(Also do this with a good charge in phone battery). First things first, you need to pre select a rom for your device, for nougat i am partial to Dr Ketan and his note 5 / s6e+ rom. If you choose something else you may require Gapps, and there is also a call audio fix. You can choose Super User or Magisk as both work. You can put the files into the phones internal memory as a wipe will not delete data such as your download folder, or you can use the usb dongle that comes with phones after the s7 to connect a usb flash drive. either way those files need to be on the device or USB, BEFORE you flash twrp. Once inside twrp immediately create a full backup(including boot and modem, check everything). once that is done you can do a standard wipe, flash the rom, flash superuser or magisk. then reboot. you wont get an fpr block. it wont fail to flash firmware via odin, it will be rooted. and twrp will stick and you wont lose the recovery upon reboot. happy rooting n flashing!

Can a mod sticky this or keep it near the top somehow please? It will help avoid a lot of subsequent posts and help to keep the troubleshooting from being in numerous different threads.

Follow up questions after restoring my s8

So now that my phone is recovered I've discovered that its only reading up to 16gb of internal storage. I have a backup of my phone before it was bricked made in twrp and want to know if I can restore that as it was made of an october patch fw and now my phone runs a december patch. Also, will this backup be corrupted or incorrect in any way because I didn't allow system modifications before creating it?
Second, can anyone drop a foolproof rooting guide for Sm-G950FD that does not result in the official binary nightmare or any other bricking horsecrap?

Unbrick-me said:
So now that my phone is recovered I've discovered that its only reading up to 16gb of internal storage. I have a backup of my phone before it was bricked made in twrp and want to know if I can restore that as it was made of an october patch fw and now my phone runs a december patch. Also, will this backup be corrupted or incorrect in any way because I didn't allow system modifications before creating it?
Second, can anyone drop a foolproof rooting guide for Sm-G950FD that does not result in the official binary nightmare or any other bricking horsecrap?
Click to expand...
Click to collapse
If it's showing incorrect storage you will need to flash stock again, you need to use the CSC file not home-csc. The pit file to repartition the device is inside the CSC file. You will need to wipe data also. As for your backup did you backup all partitions or only data? I don't use twrp backups because for some reason after restoring I always run into issues. Hope this helps in some way :good:

Unbrick-me said:
So now that my phone is recovered I've discovered that its only reading up to 16gb of internal storage. I have a backup of my phone before it was bricked made in twrp and want to know if I can restore that as it was made of an october patch fw and now my phone runs a december patch. Also, will this backup be corrupted or incorrect in any way because I didn't allow system modifications before creating it?
Second, can anyone drop a foolproof rooting guide for Sm-G950FD that does not result in the official binary nightmare or any other bricking horsecrap?
Click to expand...
Click to collapse
Some say as simple as a factory reset can fix it but if not for sure what previous poster stated

callumbr1 said:
If it's showing incorrect storage you will need to flash stock again, you need to use the CSC file not home-csc. The pit file to repartition the device is inside the CSC file. You will need to wipe data also. As for your backup did you backup all partitions or only data? I don't use twrp backups because for some reason after restoring I always run into issues. Hope this helps in some way :good:
Click to expand...
Click to collapse
Yes I did backup all partitions, I backed up every option there was, which leads me to a new question. I've read up on TWRP's site https://twrp.me/faq/whattobackup.html that restoring the extra partitions carelessly could result in a brick. Is it safe to take these partitions out of the backup folder and restore everything else? I think it might end up causing issues or something since that would change the hash, hopefully I'm wrong about that tho.

Hello! I've rooted my phone today successfully without ending up in the official binary hell. I did this by following normal S8 rooting procedures but I allowed system modifications everytime TWRP booted and I flashed rmm state bypass mesa, no verity and the latest magisk. In that order. In addition, the required wiping of my device before rooting seemingly fixed my storage issue! Hooray!

Unbrick-me said:
Hello! I've rooted my phone today successfully without ending up in the official binary hell. I did this by following normal S8 rooting procedures but I allowed system modifications everytime TWRP booted and I flashed rmm state bypass mesa, no verity and the latest magisk. In that order. In addition, the required wiping of my device before rooting seemingly fixed my storage issue! Hooray!
Click to expand...
Click to collapse
Hello, that's great news glad it's all sorted for you! Happens often with the storage partition. As for the rmm, you should only have to flash the rmm zip once only then it should work every time.