Hi All,
My end goal was to get my Samsung Tab Active tablet to work with my PS4 via Remote Play app but during my lengthy rooting process I've managed to do something to fail SaftyNet checks which lm guessing its messing with Remote Play app as just get blank screen on it .
First I flashed SuperSU (CF-Auto-Root) via Odin tripping the e-fuse before relising Magisks existed! Magisks seemed a better choice so went about reflashing back to stock from firmware I got from Sammobile site before installing Magisks manager on the tablet. Once Magisks manager was on I patched and flashed the boot.img.tar file via Odin checked SaftyNet tests which failed relising its probaby due to me just reflashing Stock firmware before removing SuperSU the correct way. :silly:
After running Triangle Away app thinking the Knox counter may play a part I went about reversing what I did via flashing: Stock -> SuperSU -> Uninstalling SuperSU via its App -> Stock -> Full format/wipe via Samsung recovery bootup.
After all that still no SaftyNet pass! Hearing about UPDATE-unSU-signed.zip and thinking at this stage the fails must be something SuperSU left behind I installed TWRP with my devises recovery.img I downloaded due to TWRP not listing my devise, TWRP SM-T365 recovery.img found here:
https://forum.xda-developers.com/tab-4/development/root-samsung-galaxy-tab-4-active-lte-sm-t3681330
Flashed UPDATE-unSU-signed.zip via TWRP and . . . SaftyNet still failing.
So after regaining consciousness from repeatedly banging head against the wall I started writing this post as well as getting an older stock file downloading from Sammobile as I type in hope a previous stock + OTA update will help this issue.
Current Binary: Samsung Official
System Status: Official
Knox Warrenty Void: 0x1 (4)
Status if this keeps up: in pieces!
Anyone have thoughts on anything else to try to pass SaftyNet on stock firmware
Related
Well, anybody or devs who can explain to me why the official OTA would trip flash counter for noob like me?
I did flash CWM 5.5.0.4 via ODIN that caused counter to become 1.
Then flashed Super User v0.87 (now updated v0.93) via CWM, and counter stayed at 1.
I did not get into download mode after that, nor flashed anything via CWM.
No custom Rom installed yet.
Installed insecure boot using Samsung Tool Kit V1.0 by Mksip (great tool):good:
Then OTA update this morning.
It downloaded fine, and after backing up Google search by TB, I tried to install.
I went into recovery automatically, and gave me "installation aborted. unverified signature"
So I went into download mode to check, and it shows flash counter now upto 3.
And shows as custom binary, and custom Rom.
I know I did not install any custom ROM yet, why does it think as custom rom and binary?
Is it because of insecure boot I installed?
Any light to this is so much appriciated for my learning for android.
Thanks in advance.
Hi,
My phone quits during the update process to JB in recovery at around 32% and then once booted back into android displays a popup saying failed to update software, try again using kies or use a samsung service centre. It doesn't connect to kies (stays stuck at connecting) and pretty sure samsung will just wipe the phone which I'd rather not do.
I originally had the phone rooted with Siyah 1.5.3 but have since reflashed the stock i9300 3e android recovery, reset the flash counter to 0 and official binary with triangle away and fully removed root from within SuperSU. I have also wiped the cache, any ideas on why the update is still not applying? I would like to stick the stock rom and avoid wiping.
Same here,
Stock Rooted S3 with CWM and busybox. Used Mark Skipper's toolbox for that, and also used that to unroot, flash stock recovery and uninstall busybox. JB update also gets an error at 32%. Do I have to uninstall SU too? Really don't want to do a complete reinstall since CMW didn't manage to backup my phone...
Aladdin Sarsippius said:
Same here,
Stock Rooted S3 with CWM and busybox. Used Mark Skipper's toolbox for that, and also used that to unroot, flash stock recovery and uninstall busybox. JB update also gets an error at 32%. Do I have to uninstall SU too? Really don't want to do a complete reinstall since CMW didn't manage to backup my phone...
Click to expand...
Click to collapse
Haven't tried to update since I unrooted (ota is only available during a few hours in the afternoon here and hasn't become available yet) but it removed the SuperSU.apk when I unrooted. Stweaks app is still there but doesn't work due to the lack of root. The only other non-stock thing left is the kernel but I don't think that should matter seeing as I've used triangle away and reset the counter and binary to official. I'll post on whether it works next time around
Try removing cwm somehow, many people find that this is a problem, same happens with me, apparently cwm fixed it in newer updates.:good:
CWM is the culprit. I really don't know why people insist on using that. It is utterly useless.
Download the ROM you want from samsung-updates.com or through CheckFUSDownloader, extract the .MD5 file from the downloaded ZIP, copy the .md5 file to the device, and flash using MobileOdin.
Then, if you want, just flash SiyahKernel again using Odin.
I had already removed cwm recovery and replaced it with the stock i9300 3e recovery but still didn't work, I downloaded the ota update manually and found it be a small incremental update which still didn't flash in the stock recovery due to a mount error..
in the end I checked the latest update available from checkfus, downloaded it from samfirmware.com and flashed it using odin.. and now got jelly bean without wiping! Reflashed siyah & su binary and everything is good now. Only issue now is the OS sees the device being modified (even after triangle away reset) so a future ota updates is off the cards.
this worked for me.
viva.fidel said:
I had already removed cwm recovery and replaced it with the stock i9300 3e recovery but still didn't work, I downloaded the ota update manually and found it be a small incremental update which still didn't flash in the stock recovery due to a mount error..
in the end I checked the latest update available from checkfus, downloaded it from samfirmware.com and flashed it using odin.. and now got jelly bean without wiping! Reflashed siyah & su binary and everything is good now. Only issue now is the OS sees the device being modified (even after triangle away reset) so a future ota updates is off the cards.
Click to expand...
Click to collapse
in triangle away there is a box that says something like modified workaround, tick that then run triangle away, when it restarts your status will be normal, then go to application manager and remove triangle away. after about 15 minutes go into superSU and unroot.
Hey there. I want to install CM11 to my I9205 but I can't seem to root it. I've read most of the threads about it, but nothing works for me. It just shows me a security warning from KNOX and SuperSU says that there is no binary installed.
FusionGT said:
Hey there. I want to install CM11 to my I9205 but I can't seem to root it. I've read most of the threads about it, but nothing works for me. It just shows me a security warning from KNOX and SuperSU says that there is no binary installed.
Click to expand...
Click to collapse
You probabely have OTA update recently... now you have ROM with Samsung KNOX security system and with new bootloader. If you want to root your Mega and you are willing to accept irreversible tripping Knox counter (= warranty void) you can find many tutorials how to root ypour phone and disable Knox. Basically it needs essentially to instal custom recovery using Odin and then installing Super user from recovery. But ask yourself the troble to find exact procedure.
Note: now you can not downgrade your firmware to version without Knox. Any attempt will end in bricking your phone.
So if you want CM11 you have to root (with tripping flash counter = warranty void), installing custom recovery CWM or TWRP and then installing CM11 ROM nad choosen version of gapps (ROMs AOKP or CN type are lacked all Google apps so if you wnat it you have to flash it separately)
trurl3 said:
You probabely have OTA update recently... now you have ROM with Samsung KNOX security system and with new bootloader. If you want to root your Mega and you are willing to accept irreversible tripping Knox counter (= warranty void) you can find many tutorials how to root ypour phone and disable Knox. Basically it needs essentially to instal custom recovery using Odin and then installing Super user from recovery. But ask yourself the troble to find exact procedure.
Note: now you can not downgrade your firmware to version without Knox. Any attempt will end in bricking your phone.
So if you want CM11 you have to root (with tripping flash counter = warranty void), installing custom recovery CWM or TWRP and then installing CM11 ROM nad choosen version of gapps (ROMs AOKP or CN type are lacked all Google apps so if you wnat it you have to flash it separately)
Click to expand...
Click to collapse
Thanks for the reply. I've managed to install a custom recovery, but I can't seem to make the root work. I have tried both CWM and TWRP, and still can't get SuperSU to work properly.
FusionGT said:
Thanks for the reply. I've managed to install a custom recovery, but I can't seem to make the root work. I have tried both CWM and TWRP, and still can't get SuperSU to work properly.
Click to expand...
Click to collapse
Look here
http://forum.xda-developers.com/showthread.php?t=2700268
and here
http://forum.xda-developers.com/showthread.php?t=2574953
and here
http://www.ibtimes.co.uk/galaxy-mega63-android422-jellybean-root-clockworkmod-recovery-484760
try to use this information.
As I said in other place - in such situation the best way is to start completely anew:
- Download firmware (e.g from Sammobile)
- Install it by Odin
- Install custom recovery
- Root phone
In provided links you should find detailed description how to do it. Bear in mind so for successfull installing custom rom's you HAVE TO disable KNOX e.g as is decribed there
http://tips.techzene.com/2013/11/how-to-disable-knox-security-service.html
Good luck
Hi, I had a phone which had a corrupted EFS. I followed the procedure here -> http://zidroid.com/how-to-fix-failed-to-mount-efs-for-galaxy-s3-gt-i9300/ and the unit is now booting fine. but it is factory mode. I saw the follow up post regarding how to remove the factory mode, but that requires root access. I flashed CWM recovery on my phone, and also SuperSU. However, after I had flashed superSU, KNOX came into the picture. I cant run SuperSU because of KNOX. So I searched how to remove KNOX. Since I still hadnt had ROOT, I tried to remove it using the steps outlined by samsung. However, when I open the KNOX app in the appdrawer, it says It hasnt been installed yet and I need to install it... so I try to install it, but after downloading it cant install it due to it being in factory mode!! (!!!)
So now I am stuck. I need to exit factory mode, and I need root. I cant root because of KNOX. I cant disable KNOX because I need root (or need to install KNOX to remove it??)
I also found a zip file Degrated_Shadow's_KNOX_removerV2.1 but it didn't work..
any help would be appreciated!
The i9300 doesn't have knox.
It does on 4.3.. I get a "An application attempted to access system on your device without authorization" it has the shield logo..
No. The i9300 does not have knox on 4.3 or any other version.
Either you don't have an i9300 or have some other software installed.
I have used ODIN to load the AP, BL, CP and CSC BTU files from Sammobile (G965FXXU7CSK). I then flashed TWRP in the AP slot - all appeared to be successful. (twrp-3.3.1-0-star2lte.img.tar).
I then went straight into TWRP and flashed more files, the objective being to root the phone and not have any issues (obvs!). This may be where I went wrong, I was mixing a couple of old HOW-TOs...
In TWRP, I clicked "Keep Read Only".
I flashed:
no-verity-opt-encrypt-6.0-star.zip
G965_PIE_Root_for_OEM_issue_devices_V5.zip (with an older version of Magisk). (Dr Ketan)
Magisk-v20.3.zip
I have been through it twice, including a full wipe in TWRP before doing everything in ODIN again.
I can get into download mode or TWRP, but if I boot System, it just hangs on the Samsung logo.
I have a Titanium backup ready to put back.
My excuse is that I used to do this a lot in the past, but didn't at all for a year or so, and I may have forgotten something crucial I suspect I could do the whole ODIN thing again and boot, but without root, and I really want root.
EDIT: I needed to use ODIN first because I have been on a beta for WAY longer than I should have been, and wanted to get back to stock + root.
Any ideas please? Or is there a modern S9+ fresh firmware + magisk root tutorial that I have missed somewhere please?
I don't think u can root without format data. Choose the other option from "Keep Read Only".
https://forum.xda-developers.com/galaxy-s9-plus/how-to/guide-root-s9-oem-fix-t3763974/amp/