For those experiencing this DATA 0 sum and unable to mount DATA on a rooted S7 Edge device if upgrading to Oreo.
I had this issue and solved it by re-installing CF-Auto Root from h*ttps://desktop.firmware.mobi/ (without the asterisk*).
Simply follow the instructions to create the CF-Auto root files for your particular device and run it thru ODIN .
My DATA count reappeared after the ODIN was completed. Now I'm able to backup my ROM as well as the DATA.
Hope this helps a few souls on XDA as it worked for me.
By the way... this works just fine with the "TGP_G93xx_XXU3ERL3_v2.7.0" as well as with an Oreo Stock rom.
After install, Data was displaying zero.
Ran the CF-Auto Root using Odin included in the package created on firmware.mobi
and Data is working fine.
I had a similar problem over the month for it, a TWRP change helped
I have the same problem with TGP custom firmware on oreo 8. The only solution I habe found is to format data first. But this is very time wasting with backup making.
Can I install cf auto root when magisk is installed?
Pow35 said:
For those experiencing this DATA 0 sum and unable to mount DATA on a rooted S7 Edge device if upgrading to Oreo.
I had this issue and solved it by re-installing CF-Auto Root from h*ttps://desktop.firmware.mobi/ (without the asterisk*).
Simply follow the instructions to create the CF-Auto root files for your particular device and run it thru ODIN .
My DATA count reappeared after the ODIN was completed. Now I'm able to backup my ROM as well as the DATA.
Hope this helps a few souls on XDA as it worked for me.
Click to expand...
Click to collapse
Dont have CF-Auto Root for SC-02H DCM?
siderxx22 said:
I have the same problem with TGP custom firmware on oreo 8. The only solution I habe found is to format data first. But this is very time wasting with backup making.
Can I install cf auto root when magisk is installed?
Click to expand...
Click to collapse
i installed the GTP Kernel 6.12 today and after completed, it was showing again "Failed to mount /data (invalid argument)" so...
I ran CF-Auto Root again and my Data Count was back on.
I did have to run the TWRP thru ODIN then ran SuperSU zip file thru TWRP to regain root... then everything was back to normal.
It seems that I do have to run CF-auto Root every time I do an upgrade to the Oreo Rom or Kernel...
I lose the Data Count but I DO NOT FORMAT IT!!! I simply run CF-Auto Root to regain the count... then run TWRP and SuperSU if needed.
It should work with Magisk as well... altho, I wouldn't be surprised if you had to run the ZIP file again to gain Root again.
Pow35 said:
i installed the GTP Kernel 6.12 today and after completed, it was showing again "Failed to mount /data (invalid argument)" so...
I ran CF-Auto Root again and my Data Count was back on.
I did have to run the TWRP thru ODIN then ran SuperSU zip file thru TWRP to regain root... then everything was back to normal.
It seems that I do have to run CF-auto Root every time I do an upgrade to the Oreo Rom or Kernel...
I lose the Data Count but I DO NOT FORMAT IT!!! I simply run CF-Auto Root to regain the count... then run TWRP and SuperSU if needed.
It should work with Magisk as well... altho, I wouldn't be surprised if you had to run the ZIP file again to gain Root again.
Click to expand...
Click to collapse
for Failed to mount /data (invalid argument) try ->
https://www.youtube.com/watch?v=T-7neHzSIvc
linus2014 said:
for Failed to mount /data (invalid argument) try ->
https://www.youtube.com/watch?v=T-7neHzSIvc
Click to expand...
Click to collapse
I'm sorry linus2014 but... your video requires to format the partition(DATA) in order to repair it and I can see that your issue is the entire system is refusing
to mount as you're unable to even format in the first place.
In the situation that I am referring to, I am able to format the phone and reinstall without any problem.
The issue is that after Installing the Oreo ROM, although able to do a full Backup in TWRP, It becomes impossible to backup the DATA with it as the Count is ZERO.
I've tried your solution before as well but... It literally removes all the DATA (APPS) as it actually formats the Partition(DATA) in order to do the repair.
That requires to reinstall everything and is time consuming.
So, what I do is simply what I've explained in my post... I do not do a repair, I simply run CF-Auto Root and afterwards, my DATA count shows the
actual value once again and this, without losing any APPS.
I do have to reinstall TWRP and SuperSU but, this is peanuts compared to reinstalling all APPS and settings.
Thanks for the post, it is most appreciated.
drnism said:
Dont have CF-Auto Root for SC-02H DCM?
Click to expand...
Click to collapse
They don't seem to have anything for the Japanese Edge, Is your Phone, OEM locked? It would be one of the reason it's not available perhaps.
Is this 'failed to mount /data' issue a bug in TWRP? Would like to unterstand why TWRP failed with this error after a successful setup of oreo?
siderxx22 said:
Is this 'failed to mount /data' issue a bug in TWRP? Would like to unterstand why TWRP failed with this error after a successful setup of oreo?
Click to expand...
Click to collapse
In my situation, after completing the Installation of the Custom ROM, TWRP needed to reinstall it. DATA Count was showing
as well as the DATA mounted properly until I began installing APPs, then DATA fail to mount but everything else worked just fine.
Using the STOCK Rom for the SM-G935-W8, Rooting and TWRP worked fine even after installing the APPs.
Just an observation as I have no knowledge of programming.
Pow35 said:
i installed the GTP Kernel 6.12 today and after completed, it was showing again "Failed to mount /data (invalid argument)" so...
I ran CF-Auto Root again and my Data Count was back on.
I did have to run the TWRP thru ODIN then ran SuperSU zip file thru TWRP to regain root... then everything was back to normal.
It seems that I do have to run CF-auto Root every time I do an upgrade to the Oreo Rom or Kernel...
I lose the Data Count but I DO NOT FORMAT IT!!! I simply run CF-Auto Root to regain the count... then run TWRP and SuperSU if needed.
It should work with Magisk as well... altho, I wouldn't be surprised if you had to run the ZIP file again to gain Root again.
Click to expand...
Click to collapse
no need so confusing...just flash this file first with twrp if you want updating your rom or kernel after updated flash this file again to keep it mounted than to gain root just flash magisk.zip or supersu zip...
Thank you!
I'm not a programmer but just someone who found a way to solve an issue the way I was able to... and trying to offer my limited knowledge in hoping someone would provide a better option.
Thank you for providing this file. It will save time.
another option for this...if you really can't mount data just use modded twrp from @Tkkg1994
https://forum.xda-developers.com/s7...te-3-0-0-0-t3334084/post77296095#post77296095
Pow35 said:
For those experiencing this DATA 0 sum and unable to mount DATA on a rooted S7 Edge device if upgrading to Oreo.
I had this issue and solved it by re-installing CF-Auto Root from h*ttps://desktop.firmware.mobi/ (without the asterisk*).
Simply follow the instructions to create the CF-Auto root files for your particular device and run it thru ODIN .
My DATA count reappeared after the ODIN was completed. Now I'm able to backup my ROM as well as the DATA.
Hope this helps a few souls on XDA as it worked for me.
Click to expand...
Click to collapse
Hi,
Once the phone model has been selected, you need to load what:
Boot image
Recovery Image
Boot + Recovery Image
and in which format?
Thank you
texas2607 said:
Hi,
Once the phone model has been selected, you need to load what:
Boot image
Recovery Image
Boot + Recovery Image
and in which format?
Thank you
Click to expand...
Click to collapse
Are you using odin?
Then you need .tar files
Hi,
in fact I just saw that my phone (SM-G935F under Oreo with the rom G935FXXS4ESC5) is not compatible with Cf-Auto root. That's why I was looking for the loading link
Do you have another solution for my SM-G935F with the rom G935FXXS4ESC5 ?
Related
Ok, I am on FP5, I guess I lost CWM, can I just flash Imnuts CWM With odin?, and how can I root it?
jorge3687 said:
Ok, I am on FP5, I guess I lost CWM, can I just flash Imnuts CWM With odin?, and how can I root it?
Click to expand...
Click to collapse
*sigh* look around...
Sent from my SCH-I510 using xda premium
jorge3687 said:
Ok, I am on FP5, I guess I lost CWM, can I just flash Imnuts CWM With odin?, and how can I root it?
Click to expand...
Click to collapse
Here you gotaken from my thread)
5. How to root a pure stock FP1 and make CWM stick after reboot - Turn off your phone, use ODIN to flash CWM (0302 blue latest version - http://imnuts.net/zU2jkn) with "reboot" option unchecked,
After completed, disconnect the usb cable, pull the battery, reinstall battery, hold down volume up+home+power to boot into cwm,
(if you failed to boot into cwm and your phone boot up you have to redo the process). Now flash Super user package zip (Superuser-3.0.7-efgh-signed.zip - and su-bin-3.0.3.2-efghi-signed.zip (both can be download from here (look for Gingerbread) : http://androidsu.com/superuser/
Reboot phone. Use Root explore (or Root browser lite or ES file explorer) go to /system/ect/install-recovery.sh script, tab on mount R/W button (upper top). Long press on the script and in the popup menu, select permission, unchecked all permission then save the file.
Shutdown phone, re-Odin cwm again, once done reboot, now cwm should stick. Once phone came up, to verify root on your phone, you can download "root checker basic" from the Market. If you have issue, download "superuser update fixer" app from the market and run it.(no reboot required). That's it.
Wow great help with links and everything thanks a lot
Sent from my SCH-I510 using xda premium
Just to add to this very helpfull Post, this are the problems I run into and how I fixed them so that if anyone comes up with the same issues, you have the solution:
1. Flashing CWM with odin was failing, I changed usb port, I rebooted the computer, and the problem was that I was doing it without the battery, as soon as I put the battery in the phone and tried odin, it was succesfull, so, what I think is that there is not enough power to the phone just using the usb cable and that is why it was failing to flash.
2. after I flashed superuser and su-bin files, rebooted the phone, but as soon as my phone was on, and connected to the internet, for some reason, the phone automatically downloaded and updated this two files, so I could not change the recovery sh script, my solution, disabled data, reflash cwm, and the root files, then I was able to change the permissions of the file.
I AM NOW ROOTED!!!! thanks buhohitr
ok, now I lost root, for some reason, I installed titanium backup and the app told me the phone is not rooted, I used the superuser update fixer and it says that it cannot fix the root, that I need to download and uptaded update.zip, what can I do?
jorge3687 said:
ok, now I lost root, for some reason, I installed titanium backup and the app told me the phone is not rooted, I used the superuser update fixer and it says that it cannot fix the root, that I need to download and uptaded update.zip, what can I do?
Click to expand...
Click to collapse
Again, please look around...
Sent from my SCH-I510 using xda premium
jorge3687 said:
ok, now I lost root, for some reason, I installed titanium backup and the app told me the phone is not rooted, I used the superuser update fixer and it says that it cannot fix the root, that I need to download and uptaded update.zip, what can I do?
Click to expand...
Click to collapse
Did you mount /system before you flash the superuser zip? if not boot into cwm, mount, then flash superuser zip file.
Edit: Also verify that you do have root by other methods, I heard the current of Titanium backup having issue.
buhohitr said:
Did you mount /system before you flash the superuser zip? if not boot into cwm, mount, then flash superuser zip file.
Edit: Also verify that you do have root by other methods, I heard the current of Titanium backup having issue.
Click to expand...
Click to collapse
There were some problems with the instructions: the steps you gave me were to install legacy super user files, which gave me temporary root only, and yes I mounted system in CWM, also the original thread has some confusing directions, such as downloading the whole package for ARM, and then stating to get the legacy 3.0.7-efghi signed, which is a contradiction, it is one or the other.
this is what I did and all works perfect:
1. download this two files and put them on your sd card http://downloads.noshufou.netdna-cdn.com/superuser/Superuser-3.1.3-arm-signed.zip
http://downloads.androidsu.com/superuser/su-bin-3.0.3.2-efghi-signed.zip
3. MOUNT /SYSTEM in CWM and flash the two files
4. Reboot and verify root with root checker basic, this is all you have to do!!!
jorge3687 said:
There were some problems with the instructions: the steps you gave me were to install legacy super user files, which gave me temporary root only, and yes I mounted system in CWM, also the original thread has some confusing directions, such as downloading the whole package for ARM, and then stating to get the legacy 3.0.7-efghi signed, which is a contradiction, it is one or the other.
this is what I did and all works perfect:
1. download this two files and put them on your sd card http://downloads.noshufou.netdna-cdn.com/superuser/Superuser-3.1.3-arm-signed.zip
http://downloads.androidsu.com/superuser/su-bin-3.0.3.2-efghi-signed.zip
3. MOUNT /SYSTEM in CWM and flash the two files
4. Reboot and verify root with root checker basic, this is all you have to do!!!
Click to expand...
Click to collapse
Nice! glad you got it working.
I have the same question. I don't really know how to root. I've always just flashed an already rooted rom via Odin. I don't truly know how to root on my own.
---------- Post added at 02:22 AM ---------- Previous post was at 02:02 AM ----------
yourbrokenoven said:
I have the same question. I don't really know how to root. I've always just flashed an already rooted rom via Odin. I don't truly know how to root on my own.
Click to expand...
Click to collapse
I see all the replies with answers now. Don't know why they weren't there before.
yourbrokenoven said:
I have the same question. I don't really know how to root. I've always just flashed an already rooted rom via Odin. I don't truly know how to root on my own.
---------- Post added at 02:22 AM ---------- Previous post was at 02:02 AM ----------
I see all the replies with answers now. Don't know why they weren't there before.
Click to expand...
Click to collapse
well, since I could not get help from the experts, I just did it myself and wrote the process for other people to make it easier.
Okay, this method only gives me root temporarily. Once I reboot again, I no longer have root. Going back into recovery... Clockwork mod is gone! Back to stock recovery!
Any ideas? Can't find anything helpful on the forums via search.
Sigh... http://forum.xda-developers.com/showthread.php?t=1832040
Sent from my SCH-I510 using xda premium
read back the first posts, there is the solution
[QUOTE=yourbrokenoven;31313626]Okay, this method only gives me root temporarily. Once I reboot again, I no longer have root. Going back into recovery... Clockwork mod is gone! Back to stock recovery!
Any ideas? Can't find anything helpful on the forums via search.[/QUOTE]
jorge3687 said:
read back the first posts, there is the solution
[QUOTE=yourbrokenoven;31313626]Okay, this method only gives me root temporarily. Once I reboot again, I no longer have root. Going back into recovery... Clockwork mod is gone! Back to stock recovery!
Any ideas? Can't find anything helpful on the forums via search.
Click to expand...
Click to collapse
[/QUOTE]
I had already tried the above without success. CWM was overwritten each time. There was another file to delete as well somewhere in system/ect which was also supposed to prevent recovery overwriting,mbut that solution proved just as fruitless.
I got itt working through trial and error, though. As it turns out, recovery actually UNmounts system after you flash a single file, so you must REmount after each if you are flashing multiple files. I do not see this "feature" explained anywhere. Maybe this is something fundamental about Linux which has escaped me over the years of android phone ownership.
Thank you for trying to help me even though.
It unmounts for safety reasons, and it's done by the package itself, not the recovery by default. You don't want power to be pulled from a filesystem in unix when it's mounted. The real issue isn't the unmount, but the mount itself seems wonky on this phone, so depending on how the CWM package is written, there's a good chance it won't be successful when it tries to mount the filesystems. It's better to mount them yourself if you're working with a package that wasn't specifically written with this phone in mind, and you even need to mount on some that are.
I'm hoping someone can help. i have looked in the forums but can't get an solid advice, recently got my galaxy s7 rooted it using cf auto root, i then downloaded latest firmware update for my device from sammobile, used odin to install but it failed and i can't even factory reset my phone as it says Dm-verity verification failure. any help would be great
follow the twrp steps and you will be fine
Studio1b said:
follow the twrp steps and you will be fine
Click to expand...
Click to collapse
Can you elaborate as I'm new to samsung modding been using nexus for a long time
did you follow : http://forum.xda-developers.com/galaxy-s7/development/recovery-official-twrp-herolte-t3333770
If you only want a bootable system partition or writable data in TWRP:
Download dm-verity and force encryption disabler.
Without exiting TWRP, transfer no-verity-opt-encrypt.zip to your device over MTP* and flash it using [Install] in TWRP.
Studio1b said:
did you follow : http://forum.xda-developers.com/galaxy-s7/development/recovery-official-twrp-herolte-t3333770
If you only want a bootable system partition or writable data in TWRP:
Download dm-verity and force encryption disabler.
Without exiting TWRP, transfer no-verity-opt-encrypt.zip to your device over MTP* and flash it using [Install] in TWRP.
Click to expand...
Click to collapse
So your saying i can disable no verity and will be able to install ota via odin? I never used this guide ill check it out
tonyafc said:
So your saying i can disable no verity and will be able to install ota via odin? I never used this guide ill check it out
Click to expand...
Click to collapse
If you do the steps you will be able to restore to stock with kies or smartwatch or odin
or flash a rom once u reboot back to twrp
Studio1b said:
If you do the steps you will be able to restore to stock with kies or smartwatch or odin
or flash a rom once u reboot back to twrp
Click to expand...
Click to collapse
Should i flash the Dm-verity disabler? And I'm already on the stock do you mean latest firmware/ota?
1st off why would u want to do that.
this is what you need to do : CF-AUTO / TWRP / dm-verity / flash custom rom.
If you want a stock rom with root then you need to do everything but flash a custom rom
any time a ota update is forced you will be unrooted, your best best is to do what what i just said
Studio1b said:
any time a ota update is forced you will be unrooted, your best best is to do what what i just said
Click to expand...
Click to collapse
false if using latest CFAR/superSU version
sanriver12 said:
false if using latest CFAR/superSU version
Click to expand...
Click to collapse
So can i get twrp and receive ota on my device or use odin for ota?
tonyafc said:
So can i get twrp and receive ota on my device or use odin for ota?
Click to expand...
Click to collapse
OTA updates will be blocked
https://plus.google.com/+Chainfire/posts/XMFgencRR11
sanriver12 said:
OTA updates will be blocked
https://plus.google.com/+Chainfire/posts/XMFgencRR11
Click to expand...
Click to collapse
So does this mean i cant install latest firmware from sammobile using odin?
Will this void warranty or trip knox guys?
121man said:
Will this void warranty or trip knox guys?
Click to expand...
Click to collapse
Hi
Yes it will......
Guys I am in need of help. I did not fully understand step 10 and just skipped originally. I did notice I could not wipe anything but thought I would be fine so I just dirty flashed custom ROM assuming wipe would work afterwards and I can clean install after.
I am obviously stuck now with 0MB internal storage shown along with no access to phone since it says upon boot that verification has failed and that I need to reset my phone.
Now, I do have important photos/datas which I do not want to lose... I did hear other guys restored their nandroid backup and were fine.
My question is, is there any way for me to access and back up my internal data somehow? I did hear something like flashing a stock firmware via Odin without the cache inside. Could someone confirm that this would work please? Would really appreciate a response. Thanks guys.
EDIT: I did try this:
If you only want a bootable system partition or writable data in TWRP:
Download dm-verity and force encryption disabler.
Without exiting TWRP, transfer no-verity-opt-encrypt.zip to your device over MTP* and flash it using [Install] in TWRP.
But TWRP would not allow me to flash because it said it could not mount storage.
New update arrive to me, unfortunately i can't flash cause my system partition was modified, anybody tried and flashed it for those on stock?
Edit: a little dismayed, july 1 security patch? Its almost the middle of September now
Same situation here. Can flash the ota.
I rooted and changed to twrp.
I think it's because of the recovery. Don't you?
Is there a way to flash back to the stock recovery without a complete flash to stock?
zagzag99 said:
Same situation here. Can flash the ota.
I rooted and changed to twrp.
I think it's because of the recovery. Don't you?
Is there a way to flash back to the stock recovery without a complete flash to stock?
Click to expand...
Click to collapse
Nope, im on stock recovery, but i must have made a mistake in one of my mods, i used systemless root and systemless xposed so system partition doesn't get touched but it errors in stock recovery, i was able to flash systemless root by booting twrp directly from fastboot and made sure to keep system as read only
thirdzcee said:
Nope, im on stock recovery, but i must have made a mistake in one of my mods, i used systemless root and systemless xposed so system partition doesn't get touched but it errors in stock recovery, i was able to flash systemless root by booting twrp directly from fastboot and made sure to keep system as read only
Click to expand...
Click to collapse
I had OTAs until 1.3
Then flashed TWRP
Now it fails claiming of fingerprints mismatch.
It expects sub reversion 726.6502 and somehow I'm on 700.6952
Is that how it fails at your end?
---------- Post added at 08:41 PM ---------- Previous post was at 08:40 PM ----------
Is there a easy twrp flashable stock?
zagzag99 said:
Is there a easy twrp flashable stock?
Click to expand...
Click to collapse
Yes, with the Full OTA. Settings -> About tablet -> System upgrade -> 3 dots (upper right) -> Advanced -> Check full upgrade. After flashing, you'll need to reflash TWRP and root.
zagzag99 said:
I had OTAs until 1.3
Then flashed TWRP
Now it fails claiming of fingerprints mismatch.
It expects sub reversion 726.6502 and somehow I'm on 700.6952
Is that how it fails at your end?
---------- Post added at 08:41 PM ---------- Previous post was at 08:40 PM ----------
Is there a easy twrp flashable stock?
Click to expand...
Click to collapse
Mine is a little different
Verifying update package...
I:comment is 1547 bytes; signature 1529 bytes from end
I:whole-file signature verified against RSA key 0
I:verify_file returned 0
Installing update...
sysutil: mmapped 4 ranges
Source: nvidia/sb_na_wf/shieldtablet:6.0.1/MRA58K/40827_726.6502:user/release-keys
Target: nvidia/sb_na_wf/shieldtablet:6.0.1/MRA58K/49349_766.5399:user/release-keys
Verifying current system...
contents of partition "/dev/block/platform/sdhci-tegra.3/by-name/LNX" didn't match EMMC:/dev/block/platform/sdhci-tegra.3/by-name/LNX:6707200:862bcf55773c989cdbbd825be96f070c7e2c3462:6715392:a817ba108d1571790ab6a6eb6750e1566dc0a32e
file "EMMC:/dev/block/platform/sdhci-tegra.3/by-name/LNX:6707200:862bcf55773c989cdbbd825be96f070c7e2c3462:6715392:a817ba108d1571790ab6a6eb6750e1566dc0a32e" doesn't have any of expected sha1 sums; checking cache
failed to stat "/cache/saved.file": No such file or directory
failed to load cache file
script aborted: "EMMC:/dev/block/platform/sdhci-tegra.3/by-name/LNX:6707200:862bcf55773c989cdbbd825be96f070c7e2c3462:6715392:a817ba108d1571790ab6a6eb6750e1566dc0a32e" has unexpected contents.
"EMMC:/dev/block/platform/sdhci-tegra.3/by-name/LNX:6707200:862bcf55773c989cdbbd825be96f070c7e2c3462:6715392:a817ba108d1571790ab6a6eb6750e1566dc0a32e" has unexpected contents.
E:Error in @/cache/recovery/block.map
(Status 7)
Installation aborted.
I:Saving locale "en_US"
thirdzcee said:
Nope, im on stock recovery, but i must have made a mistake in one of my mods, i used systemless root and systemless xposed so system partition doesn't get touched but it errors in stock recovery, i was able to flash systemless root by booting twrp directly from fastboot and made sure to keep system as read only
Click to expand...
Click to collapse
I suspect it has to do with the fact that systemless root modifies the bootloader and the delta OTA checks that. Try uninstalling root from SuperSU (it does say uninstallation is required for OTA to proceed) and see if OTA proceeds.
Isira said:
Yes, with the Full OTA. Settings -> About tablet -> System upgrade -> 3 dots (upper right) -> Advanced -> Check full upgrade. After flashing, you'll need to reflash TWRP and root.
Click to expand...
Click to collapse
Thanks, i just did the full ota flash... Waiting for the art pre compile of all my apps now.
Isira said:
I suspect it has to do with the fact that systemless root modifies the bootloader and the delta OTA checks that. Try uninstalling root from SuperSU (it does say uninstallation is required for OTA to proceed) and see if OTA proceeds.
Click to expand...
Click to collapse
Thank you, uninstalled magisk OTA went fine for me, now ill have to wait to go back home to root again, systemlessly
where is the OTA file located? I tried data/data/com.nvidia.ota/files/rom but it's not there.
*edit nvm, found it, under app_download folder and not the files/rom folder
Full OTA k1 1.4 for recovery
https://mega.nz/#!Q1VUVBrR!v40m3Q4s-rqcfCYQmEqIw0MzEJTI897Sd7ZousmhcKU
Hi folks, I'm having an issue with the update; I have rooted my Shield K1, have attempted to update to 1.4 using FlashFire app on Stock recovery, I have a 64GB Samsung EVO SD card and my storage was on adoptive. The update/flash started fine, but on reboot the error message "Unfortunately, Setup Wizard has stopped" comes up, I click OK and nothing happens. Does anyone know how I can rectify this issue please?
I found that by downloading the full image (which you can do via the built in updater on the tablet via Settings), I could use Flashfire to install and root it, no data lost. Didn't work with the smaller OTA file, but the full file worked flawless.
Thanks, but I can't get past the error message. I have seen another way to flash the update and have found out I did one of the steps wrong, if I can get it working again I'll post.
chewdiggy said:
Thanks, but I can't get past the error message. I have seen another way to flash the update and have found out I did one of the steps wrong, if I can get it working again I'll post.
Click to expand...
Click to collapse
You tried wiping cache?
Isira said:
Yes, with the Full OTA. Settings -> About tablet -> System upgrade -> 3 dots (upper right) -> Advanced -> Check full upgrade. After flashing, you'll need to reflash TWRP and root.
Click to expand...
Click to collapse
Hey mate what is the best version of supersu to flash?
Sent from my SHIELD Tablet K1 using Tapatalk
thirdzcee said:
You tried wiping cache?
Click to expand...
Click to collapse
I have now wiped the cache and it is back to defaults. Thank you thirdzcee. Will not make that mistake again, I assure you.
robgee789 said:
Hey mate what is the best version of supersu to flash?
Click to expand...
Click to collapse
Use Flashfire, it'll do it all for you. (although it does appears to come with 2.76 instead of 2.78 of SuperSU, but updates itself anyway).
I have been having issues on my k1 since the 1.4 firmware I tried doing the toggle able system-less root and xposed but i lose touch and the tablet just doesn't work and i end up having to reinstall the 1.4 update at this point i'm sitting at fresh wiped tablet i dont yet.
I have narrowed my issues down to bad SD card as adopted storage.
i just downloaded the update by accident but i dont want to flash it because i have root and twrp so i moved the ota and restarted my tablet, but the notification is still there, any ideas on how to remove the notification?
Heyo!
So.. I recently got the 930F and rooted successful with odin, but my question is now, how do I successfully flash a working TWRP without having all the issues ppl describe below the twrp thread for sgs7?
greetz
after flashing TWRP with odin, enter your new recovery.
Wipe everything, then flash the rest of the files. You won't be able to boot otherwise.
You must in Odin remove the hook at autoreboot.
And then manually switch off the mobile phone with "Home-Vol--Power", then start with "Home-Vol+-Power" and wait until the TWRP screen comes and then let go.
Senaxo said:
You must in Odin remove the hook at autoreboot.
And then manually switch off the mobile phone with "Home-Vol--Power", then start with "Home-Vol+-Power" and wait until the TWRP screen comes and then let go.
Click to expand...
Click to collapse
But I didnt flash TWRP yet, cuz I used the CF-Root method by Chainfire, just rooted with odin and got supersu installed, i cant even boot into a recovery? my phone just starts normally, doesnt samsung have a normal recovery?
can I just re-root with a method with TWRP included without worries or am I gonna brick my phone?
bump
i suggest to full wipe after installing TWRP.
Abuzar Uzair said:
i suggest to full wipe after installing TWRP.
Click to expand...
Click to collapse
Why would you suggest a full wipe? Is it needed?
I did the same thing... used CF-Auto-Root to root my S7 and noticed that I didn't have TWRP. So I just downloaded TWRP Manager from the Play Store and used that to flash TWRP to Recovery. It worked perfectly as far as I can tell, no need to wipe anything.
Unless I've missed something?
d3adm8n said:
Why would you suggest a full wipe? Is it needed?
I did the same thing... used CF-Auto-Root to root my S7 and noticed that I didn't have TWRP. So I just downloaded TWRP Manager from the Play Store and used that to flash TWRP to Recovery. It worked perfectly as far as I can tell, no need to wipe anything.
Unless I've missed something?
Click to expand...
Click to collapse
The full wipe will disable data & sd encryption, so you will not face any problem while flashing roms & kernals, or creating twrp backup.
d3adm8n said:
Why would you suggest a full wipe? Is it needed?
I did the same thing... used CF-Auto-Root to root my S7 and noticed that I didn't have TWRP. So I just downloaded TWRP Manager from the Play Store and used that to flash TWRP to Recovery. It worked perfectly as far as I can tell, no need to wipe anything.
Unless I've missed something?
Click to expand...
Click to collapse
Did it really work? ive read a few other posts about ppl bricking their phones by doing that D:
bump
bump
Maybe a good read if your on Nougat?
https://forum.xda-developers.com/galaxy-s7/how-to/root-official-stock-nougat-7-0-100-t3540765
johnny8910 said:
Maybe a good read if your on Nougat?
https://forum.xda-developers.com/galaxy-s7/how-to/root-official-stock-nougat-7-0-100-t3540765
Click to expand...
Click to collapse
That's completely unrelated to my issue
Kickazz080 said:
Heyo!
So.. I recently got the 930F and rooted successful with odin, but my question is now, how do I successfully flash a working TWRP without having all the issues ppl describe below the twrp thread for sgs7?
greetz
Click to expand...
Click to collapse
I don't know if I'm too late, but this is what I did and it was the easiest way to get TWRP.
Go to the Play Store and download 'TWRP Manager App', when on there hit 'Install TWRP', look for the SG7 type for TWRP and choose the latest datedTWRP (People tend to get Recovery is not seandroid enforcing error because they use an out-of-date recovery image).
It will say there was an error flashing recovery and give the option to Reboot or Reboot Later, but it actually has managed to get TWRP onto your phone so just reboot there and then.
Boom you have TWRP; remember the first thing to do is Format Data.
Good Luck
AzzyC said:
I don't know if I'm too late, but this is what I did and it was the easiest way to get TWRP.
Go to the Play Store and download 'TWRP Manager App', when on there hit 'Install TWRP', look for the SG7 type for TWRP and choose the latest datedTWRP (People tend to get Recovery is not seandroid enforcing error because they use an out-of-date recovery image).
It will say there was an error flashing recovery and give the option to Reboot or Reboot Later, but it actually has managed to get TWRP onto your phone so just reboot there and then.
Boom you have TWRP; remember the first thing to do is Format Data.
Good Luck
Click to expand...
Click to collapse
Format data when I first boot the phone after the twrp-installation-restart? or before flashing rom/kernel?
Kickazz080 said:
Format data when I first boot the phone after the twrp-installation-restart? or before flashing rom/kernel?
Click to expand...
Click to collapse
Format Data after TWRP Installation because our S7 phone has dm-verity and you will not be able to flash zips and ROMs properly. Formatting will get rid of that verity encryption.
Another reason why to format data after TWRP installation is because as this method does not fully get rid of stock recovery and is left dormant, so formatting the data will let TWRP read your Data.
AzzyC said:
Format Data after TWRP Installation because our S7 phone has dm-verity and you will not be able to flash zips and ROMs properly. Formatting will get rid of that verity encryption.
Another reason why to format data after TWRP installation is because as this method does not fully get rid of stock recovery and is left dormant, so formatting the data will let TWRP read your Data.
Click to expand...
Click to collapse
Is there any chance of me ****ing up and losing my imei or smth?
Kickazz080 said:
Is there any chance of me ****ing up and losing my imei or smth?
Click to expand...
Click to collapse
Nope. That is not part of the Data partition so the format shouldn't affect - IMEI No. is part of the EFS partition.
If you do come with any problems though, quote me and I'm here to help. But believe I'm telling you what even I did and I'm running ROMS and shiz now.
I've wrote it in many thread and I report here for users that want:
stay stock and updated
root (with Magisk)
unencrypted
never lose data and configuration
Here's my procedure, I'm using it since since I bought my S8 exynos (jun 2017), never had a problem, never lost a single bit of my data. And I don't know any alternative until now.
G950FXXU4DSDA (pie) tested​
I assume you have:
unencrypted device
oem unlock option checked (never uncheck it)
stock rom: any system mod is ok, but you'll lose it
What you need:
last odin (download here)
last stock rom for your country (download here)
last twrp on your exynos device (download here)
last Magisk zip on your device (download here)
Here's the steps:
if you haven't did before, create a magisk config file executing this two command on a shell (this file remain until you clean /data partition):
Code:
echo KEEPVERITY=false>>/data/.magisk;
echo KEEPFORCEENCRYPT=false>>/data/.magisk;
extract the rom and delete CSC_OXM_G950Fxxx (you don't need it, this file do the factory reset we don't want)
reboot you phone in download mode (boot with voldown+power+bixby)
connect your phone (you already have the driver, right?)
select all files in odin
uncheck auto-reboot option
press start
at the end manually restart the phone with voldown+power
the phone will boot in stock recovery and complete the installation ("Installing system update..." and "Erasing...")
keep attention because when rebooting you have to put your finger on voldown+power+bixby to return in download mode (if system boot your data partition will be encrypted)
in odin select TWRP file in AP slot
check auto-reboot option
put your finger on volup+power+bixby and keep there
press start
after a while you'll be in TWRP and you can relase the finger
flash Magisk
reboot in system
Then you can do any other mod you wan't, my favourites here.
I wrote this thread because all the guides I found skip the important (and tricky) 9-10 step and my tests results in:
interrupted csc install (twrp tried to execute a script producing "Error installing zip file 'CACHE:recovery/sec_omc.zip'")
empty CSC (Phone Info app) and no /system/omc folder
phone works well, but i'm not sure I was using VoLTE because I didn't see the icon
dial codes aren't working
korean operator "KT" voice in settings
Anyone else tried this method? Hoping to give it a try later this week when I have some time should something go wrong
so on s8 works too. nice. I've been doing this on my S7 edge every FW update. dirty flash, then root then xposed. So I hope this trick works in my S8 too.
are you on Nougat or Oreo?
Yea it works just fine, dirty flash can cause issues though. Might wanna let people know that.
t12icky0 said:
Yea it works just fine, dirty flash can cause issues though. Might wanna let people know that.
Click to expand...
Click to collapse
this way works like an ota for my experience, not a single issue in one year of updates
Can i root in your way? Im on CRD7 all stock, unroted.
If i follow your guide will be my phone rooted?
Sent from my SM-G950F using Tapatalk
zelenko said:
Can i root in your way? Im on CRD7 all stock, unroted.
If i follow your guide will be my phone rooted?
Sent from my SM-G950F using Tapatalk
Click to expand...
Click to collapse
if you've never modify the phone, you're encrypted
if you,re encrypted, you need to format your data partition to get root permission (for what I know is not possible / not safe to stay encrypted)
you can follow my guide adding a format data step before flashing supersu, but the phone will be factory reset
so after doing this i'll still get ota updates and i can install them fine plus having the root privileges ?
No, I've never tried ti install otas (I expect it will fail).
To stay updated you have to repeat the procedure whit the new stock image, usually released before the ota.
pie tested ​:good:
Does is still work? I want to upgrade to Pie but dont want to wipe and lose all data.
Is it still rooted after?
Sorry i'm a noob
S8 rooted
TWRP and Magisk
can you help me please???
silverik1 said:
Does is still work? I want to upgrade to Pie but dont want to wipe and lose all data.
Is it still rooted after?
Sorry i'm a noob
S8 rooted
TWRP and Magisk
Click to expand...
Click to collapse
Confirming, it's working perfectly
@c3k ,
Thanhs for this great solution !!
m.
I still have the stock rom and rooted with magisk. But in twrp I can not mount the data partition. Is it because it's still encrypted ?
... that's what I assume but it`s strange because you should be decrypted already after formatting data installing twrp, magisc etc. ...
m.
Yeah..I know...any suggestions ?
... it sounds like a data format is needed then ... Or does this method from c3k work for you ... ?
You `ve the latest TWRP installed?
m.
How do I install the latest one if I have an older version ? Can I use flashify for it ?
Or with twrp itself ?
I install new twrp via the installed one as an img file.
m.