Related
So I just got a Rogers Note II and aching for multiview I decided to check for software update. I know it is not there but I just felt like tapping the button in a feeble hopeful attempt.
I get the "Your device has been modified. Software updates are not available"....WHAT?
Can someone explain this? I haven't rooted it
stiggy86 said:
So I just got a Rogers Note II and aching for multiview I decided to check for software update. I know it is not there but I just felt like tapping the button in a feeble hopeful attempt.
I get the "Your device has been modified. Software updates are not available"....WHAT?
Can someone explain this? I haven't rooted it
Click to expand...
Click to collapse
From what I have read on the Triangle Away forum, Samsung devices all use a flash counter in a hidden partition and 'unauthorized' flashing causes this counter to increase (hence the 'modified' triangle warning). However, since Chainfire has been making a great bypass and counter reset for a while, Samsung decided to put in some form of 'watchdog' that monitors the actual android system for modified or additional files in the software layer.
That being said, I'm guessing there is some type of faulty reporting from within your android system. Of course without a rooted device, you should not be able to affect anything that requires root access, and therefore not trigger any of this nonsense. Maybe you have some app that Samsung doesn't want you to have on it, like stock Google Calendar
My suggestion would be to take it back to the Rogers store. Or just wait for the update leaks, and update from samsung-updates.com, and flash via Kies. I've already sent them the info they need to receive the update when it is released.
Cheers
I am creating this thread because I have not found another ZACT rooting/flashing thread yet and I am hopping that a dev will pop in and start working on this, or help walk me through what I can do to get the ball rolling. Check out my first thread, The future of phones is coming
I received 2 phones a few weeks ago now. I wasn't thinking and just jumped the gun and updated to 4.3 on one of them (the other is my fiances and have instructed her NOT to do the update). I am unable to cf-auto-root with the sprint s3 method, so no root. I read if I get the recovery.img from the phone I can post in on Chainfire's cf-auto-root page and he can make a cf-auto-root for the zact s3. I can not get a recovery.img to send in because it is my understanding that to adb pull the recovery I need root. cant get root because I dont have a recovery.img?
I spoke with zact team members a few times. I told them I was having issues with 4.3 and wanted to go back to 4.2.2. A few people were helpful at first. Unfortunately, they are so small, I seem to keep running into the same people, and then they stop trying to help. What I have learned is, they "have confirmed with there Team, that if you process the software downgrade, the Zact software will not work on your phone. This is based upon how our software interfaces with the firmware." SO, that being said we would need to find out what software they have installed and have it integrated into any roms made. Does that sound right?
They also WILL NOT share the MSL. Which is another reason I want root. I still plan on cloning the phone as a backup if I have issues with flashing. but without the msl, i cant change the qualcomm settings to connect to dfs/cdma to back clone it.
I am not a developer, I could use some direction. I feel ZACT will start growing once people realize how much you can save compared to a sprint plan. I have noticed that I get better service then a lot of the people I work with. I am on prl version 24017, which I have not seen before either.
devildogwillbur said:
I am creating this thread because I have not found another ZACT rooting/flashing thread yet and I am hopping that a dev will pop in and start working on this, or help walk me through what I can do to get the ball rolling. Check out my first thread, The future of phones is coming
I received 2 phones a few weeks ago now. I wasn't thinking and just jumped the gun and updated to 4.3 on one of them (the other is my fiances and have instructed her NOT to do the update). I am unable to cf-auto-root with the sprint s3 method, so no root. I read if I get the recovery.img from the phone I can post in on Chainfire's cf-auto-root page and he can make a cf-auto-root for the zact s3. I can not get a recovery.img to send in because it is my understanding that to adb pull the recovery I need root. cant get root because I dont have a recovery.img?
I spoke with zact team members a few times. I told them I was having issues with 4.3 and wanted to go back to 4.2.2. A few people were helpful at first. Unfortunately, they are so small, I seem to keep running into the same people, and then they stop trying to help. What I have learned is, they "have confirmed with there Team, that if you process the software downgrade, the Zact software will not work on your phone. This is based upon how our software interfaces with the firmware." SO, that being said we would need to find out what software they have installed and have it integrated into any roms made. Does that sound right?
They also WILL NOT share the MSL. Which is another reason I want root. I still plan on cloning the phone as a backup if I have issues with flashing. but without the msl, i cant change the qualcomm settings to connect to dfs/cdma to back clone it.
I am not a developer, I could use some direction. I feel ZACT will start growing once people realize how much you can save compared to a sprint plan. I have noticed that I get better service then a lot of the people I work with. I am on prl version 24017, which I have not seen before either.
Click to expand...
Click to collapse
WARNING!! If you process that downgrade, you will trip KNOX security, then your phone will be bricked. Also, ESN cloning is illegal to talk about on XDA.
sent from my GS3
I will trip knox security? What exactly does Knox do, and what do you mean by that? I though Knox just makes it read 0x1 on the odin screen if you flash now? If thats what you mean, I already did that by flashing cf-auto-root. Its my understanding that the boot loader is the issue when downgrading. but on this site, they say that only at&t users should not try it, and technically this is a sprint phone I believe. Just with added software.
If I am wrong please let me know.
Also, I think you mean that it is not acceptable, not illegal. Illegal would imply I could get arrested for commenting about phone cloning on this site. And although cloning your personal phone for your own uses is not illegal, I will not mention it again on these forums. Thanks for the warnings.
sent from my GS3
Also, I guess I am not necessarily trying to downgrade, just trying to find out what needs to be done so that I can flash or ANYTHING to get away for 4.3 issues. Since the upgrade, my fiance sent me an mms and it has popped up in my messages 5 times, so it looks like she keeps sending it, but I am unable to open it because it wont download.
The more important issue is root. I want to be able to use my root apps to backup, re install my old backups from my last s3, and attempt to get my msl to try and fix the mms issue.
sent from my GS3
Today has been a productive day so far... using Skunk Ape1's root method "[Tutorial] Rooting the Sprint GalaxyS3 the Easy Way" I was able to get twrp recovery installed. (I wasn't able to do this before because prior the only method i knew was to go to goo.manager and that didn't recognize my device) SO, with twrp installed, i flashed the zip file from Skunk Ape1's root method. Following the instructions to the T everything seemed to work fine. After reboot, I had a knox message popped up, saying "SECURITY NOTICE: Unauthorized access to a secured area has..." I relive that root has been installed but knox is keeping locked up still. I am going to look for this mysterious "Knox remover script" that you will see in the first post on that page, then I will attempt root again.
I have officially given up on root currently. I have tried every root method I can find, my flash counter is somewhere around 13. I was able to use the knox removal script from here If anyone has suggestions for root, I am open to ideas. Thanks.
Finally did it
So, today i was just realizing the lack of space i had on my phone from downloading stuff and photos so i wanted to clean it up. I moved all the important stuff off, and though it would be a good time to factory reset and just have a clean new phone to start over again. ( I missed flashing and this was the closest thing I had) So, during the process of factory resting i wanted to clean everything so i click data, cach, internal external.. system.. yeah well bad idea. my phone rebooted and go stuck on the boot. So i restarted in recovery and reset again and this time is warned me that there was no OS installed... F*ck... Zact customer service wont give me the "custom software" that they installed so im screwed.
After hours of thinking and trying to do stupid odd ball things that i knew wouldnt work. I downloaded a sprint stock 4.3 tar file and odined to my phone. started up fine. works great. so... what zact said about flashing roms bricking this phone was BS.. the only custom thing i have seen was in the zact mobile app that came installed had some extra features used to send usage info and reboot stuff for zact troubleshooting. so with stock sprint rom, and zact mobile app im back to my phone working. AND with that, im going to move on to the rooting, and flashing of this piece of crap. Ill be back with more details later.
I have installed CyanogenMod with full root!!!
well first off, i had the CMinstaller set up but it did not recognize my device so after a while i decided to attempt to cf_auto_root, which seemed to work but failed root checker. I wanted to try another method. I had CMinstaller still up* I was attempting THIS method to root. I was using philz_touch_6.15.4-d2spr.tar.md5 that I flashed using Odin 3.07 (that I have had for a long time on my pc. so google that one)https://www.google.com/search?q=odin+3.07&oq=odin+3.07&aqs=chrome..69i57.3464j0j1&sourceid=chrome&ie=UTF-8 After i installed Philz touch, i noticed CMinstaller noticed my phone and started downloading system files. I continued what i was doing with the root method and installed DE-SAMSUNGNIZER_KNOX_REMOVAL_SCRIPT_V1.0 and UPDATE-SuperSU-v1.93 just as CMinstaller finished its download, so i said what the hey, and clicked install. next thing i knew i was running cyanogenmod with full root!!! please someone else verify this and let me know if you get it going too.
Deleted
Stock 4.3 with root
so yeah, just for to check i flashed back to stock 4.3 (not sure who uploaded it but it works) It does have knox so be warned. I then followed the root method in my previous post and it worked fine. i have stock with root. If someone can try it without using that tar file, let me know. Cant really go back once you do it so i cant try the root method with the zact "custom software" myself. Let me know what you find out. Hope this helps someone.
Thanks
Thanks for posting your struggles and successes. With Zact shutting down I was curious about what I could do with my kids' S3s if I don't like the Sprint plan that they are rolling us into. I may be trying this in a couple weeks...
Zact to Ting
Barnsie said:
Thanks for posting your struggles and successes. With Zact shutting down I was curious about what I could do with my kids' S3s if I don't like the Sprint plan that they are rolling us into. I may be trying this in a couple weeks...
Click to expand...
Click to collapse
What I would do and have done for my fiance and myself, get on Zact.com live chat ask them to Deactivate your phones. and give them the DEC on the back of the phones. It takes about one min for it to complete per phone. Then go on over to Ting.com and start up a new account with them using your old zact phone. Ting also lists the MSL that i struggled so much trying to get. I would recommend flashing a stock rooted rom debloated, to get all that ZACT crap off your phones. and start out fresh.
Hey guys, new member although I've lurked for a while. I have been searching up and down the last couple of days to find a way to get past KNOX and reroot my device. Me being kinda rustic and not thinking about it, accepted an OTA firmware update a few days ago. Of course I lost root access. What I didn't know about at the time was how big of a problem KNOX had become recently.Well, this firmware update introduced KNOX onto my device. I've heard stories of people being able to use Kingo and Saferoot on 4.2.2 and 4.3 after KNOX. This has not been the case with me, and I'm wondering if anyone has had success with this. Odin doesn't work either. I noticed that write protection is set as yes when in ODIN mode, and I suspect this is KNOX preventing changes to the ROM. As a result I haven't even been able to reflash the stock ROM image I have, whereas I have heard that you can reflash stock ROM's, but can't go backwards as far as version number. Thanks for your help in advance.
HansBlenkers said:
Hey guys, new member although I've lurked for a while. I have been searching up and down the last couple of days to find a way to get past KNOX and reroot my device. Me being kinda rustic and not thinking about it, accepted an OTA firmware update a few days ago. Of course I lost root access. What I didn't know about at the time was how big of a problem KNOX had become recently.Well, this firmware update introduced KNOX onto my device. I've heard stories of people being able to use Kingo and Saferoot on 4.2.2 and 4.3 after KNOX. This has not been the case with me, and I'm wondering if anyone has had success with this. Odin doesn't work either. I noticed that write protection is set as yes when in ODIN mode, and I suspect this is KNOX preventing changes to the ROM. As a result I haven't even been able to reflash the stock ROM image I have, whereas I have heard that you can reflash stock ROM's, but can't go backwards as far as version number. Thanks for your help in advance.
Click to expand...
Click to collapse
Flash anything with ODIN will trip the KNOX. Kingo is basing their root method on Saferoot, just with a GUI to make things simpler. And Saferoot should work with ROM that is before KK (4.4). If your OTA update is 4.4 than Saferoot won't work, since Saferoot is using a vulnerability prior 4.4 version. Does Kingo or Saferoot give any error message?
And just to double check, for both Saferoot or Kingo to work, you need to enable USB ADB and debugging mode.
TNCS said:
Flash anything with ODIN will trip the KNOX. Kingo is basing their root method on Saferoot, just with a GUI to make things simpler. And Saferoot should work with ROM that is before KK (4.4). If your OTA update is 4.4 than Saferoot won't work, since Saferoot is using a vulnerability prior 4.4 version. Does Kingo or Saferoot give any error message?
And just to double check, for both Saferoot or Kingo to work, you need to enable USB ADB and debugging mode.
Click to expand...
Click to collapse
Hey thanks for the reply. I do have USB ADB and debugging turned on. I've also tried reinstalling kies and the USB drivers them selves. I don't really care if an Odin flash trips Knox, as I don't think I have a warranty to worry about. The OTA update brought my firmware upto date , so I'm still on 4.2.2. This means that technically Saferoot or Kingo should work as advertised. This brings me back to the Write Protection set to Yes, and it's the only thing I could see preventing me from rooting my phone.
EDIT: Well I just found out that the Mini USB I use to charge my mouse started shorting other USB devices. Not like short then come back on, it was so bad every port on the computer shut down and I had to restart to get them working again. It was also the cable I was using to plug my phone in. Will update again when I try another cable.
EDIT 2: Just tried with the cable I usually use for charging my phone. No change on Kingo, still get a Root Failed, Need Root error.
HansBlenkers said:
Hey thanks for the reply. I do have USB ADB and debugging turned on. I've also tried reinstalling kies and the USB drivers them selves. I don't really care if an Odin flash trips Knox, as I don't think I have a warranty to worry about. The OTA update brought my firmware upto date , so I'm still on 4.2.2. This means that technically Saferoot or Kingo should work as advertised. This brings me back to the Write Protection set to Yes, and it's the only thing I could see preventing me from rooting my phone.
EDIT: Well I just found out that the Mini USB I use to charge my mouse started shorting other USB devices. Not like short then come back on, it was so bad every port on the computer shut down and I had to restart to get them working again. It was also the cable I was using to plug my phone in. Will update again when I try another cable.
EDIT 2: Just tried with the cable I usually use for charging my phone. No change on Kingo, still get a Root Failed, Need Root error.
Click to expand...
Click to collapse
At this stage I can only suggest to try on a different PC (use don't need Kies, just the Samsung driver will do) with a cable that your are 100% sure it working. If it still not working, my only guess is your network provider enable a looked boot loader in the OTA update you just did (hence the Write Protection flag). If that the case, nothing can be done at this point.
Same Boat
Im in the same boat did realize that KNOX would change so much. I need to reroot so hopefully someone can figure it out without tripping knox.
It fails because of the Security notice....Unauthorized access to a secured area has been blocked. Tap to learn more. If you notice when you check USB debugging, look below at Verify apps via USB. It is checked and grayed out. It isn't checked when USB debugging is off. I don't know how this was circumvented on the S4. But I'm peeved I let the update happen. They conveniently left out any info about security, and I'm tempted to return the phone and get one that hasn't been updated. Figure they weren't forthcoming about what the update contained so I can raise enough stink, get an old phone, download the update, pass it off to someone who can hopefully pull everything but the bootloader and create a tar to flash via odin. If that's possible and someone is willing to do it. If I had another spare line, I'd get another phone to donate for the cause.
I think if we're on Knox we need Odin to Root because anything that gets transferred via USB will be blocked. I even tried rootkeeper, and it was blocked.
The tough part is, unless it's a premium phone, it's not getting the level of dev support we're used to (well I'm used to...haha). Rooting through odin, custom recovery....used to taking it for granted. And with Sprint EOL'ing the phone, it's not really going to gain any momentum, though I did only pay 99 cents for it on a spare line. Kinda ticks me off Samsung has gone this direction when they used to be so dev friendly. Almost enough to make the S4 my last Samsung.
TNCS said:
At this stage I can only suggest to try on a different PC (use don't need Kies, just the Samsung driver will do) with a cable that your are 100% sure it working. If it still not working, my only guess is your network provider enable a looked boot loader in the OTA update you just did (hence the Write Protection flag). If that the case, nothing can be done at this point.
Click to expand...
Click to collapse
the concern is not tripping knox from the bootloader perspective. The problem is the knox security app that can't be removed without root. So for everyone that has OTA updated to NA7, going the odin route to root is the only option as far as I know. I know I don't care about tripping the counter. I just want control back of my phone. And the only way to do that at the moment is to return it for a pre knox version which I'm apt to do at the moment since there is a lack of development, and the ones that are developing don't even have the phone. Kudos to them, but there's not much help once you've updated to NA7. And unfortunately, the update doesn't tell you it's locking down your phone. Then you're stuck in a quandary, because the update also provides updates for Spark, so unless someone does a dump of the download and someone can pick it apart and provide a zip sans Knox, we'll have to deal with a stock phone.
dbpaddler said:
the concern is not tripping knox from the bootloader perspective. The problem is the knox security app that can't be removed without root. So for everyone that has OTA updated to NA7, going the odin route to root is the only option as far as I know. I know I don't care about tripping the counter. I just want control back of my phone. And the only way to do that at the moment is to return it for a pre knox version which I'm apt to do at the moment since there is a lack of development, and the ones that are developing don't even have the phone. Kudos to them, but there's not much help once you've updated to NA7. And unfortunately, the update doesn't tell you it's locking down your phone. Then you're stuck in a quandary, because the update also provides updates for Spark, so unless someone does a dump of the download and someone can pick it apart and provide a zip sans Knox, we'll have to deal with a stock phone.
Click to expand...
Click to collapse
I was (after a good bit of tinkering, and deleting my modem on accident) able to install CWM and flash a CW11 version s0be is currently developing, and it's working pretty well as far as I can tell. Unfortunately, due to the lack of support on this forsaken Sprint device, I haven't been able to find a modem I can flash onto the damned thing to get it working properly again. I don't advise the route I took, firstly because of the effort it took, but I also damned near bricked it about 5 different times, and needed to use a Linux VM. Also, because of the lack of developers on this thing, if you delete your modem and A: don't have a friend (brother in my case, has same phone) you can pull a modem.bin off of and B: don't know how to build that .bin into a working .zip or a flashable tar.md5 you might get stuck with an unusable device at the end of the day. Really, the only thing Knox has done for us is complicate things a hell of a lot more than they need to be. Although, tbh, that might (most likely) have been my stupidity that deleted the modem. In any case, check it (s0be's CM11 development) out, it's coming along nicely. Just be careful with it.
........
thank you very mach
Well first, I am new here, so hi!
Second, I have spent hours researching this and if I can get this to work it seems like the best way to root my Samsung Galaxy Tab 3 7.0 SM-T217s.
Now... On my unrooted, regular, tablet, how can I stop KNOX? When I use Kingo ROOT to try and root it, the tablet has a notification that says it blocked an unsecure app from using some areas. (or something like that). If I go to that, I have to tap update policies and then it says it is updated and brings up the application in settings. From here I cannot do anything with the app, other than force stop, which doesn't work.
So... I need to know, how can I stop KNOX from keeping me from rooting with Kingo ROOT?
If this is not possible, are there any other easy ways to root? I don't really get all this flashy ROM things.
EDIT:
I have spent hours without any solution to this I meant.
Also, sorry if this is wrong area... But since KNOX is an app thought it went here
So I downloaded the new Android Pay app last night, but it doesn't seem to work if you have a custom ROM installed. I'm currently on Resurrection and it gives me the error "Google is unable to verify that your device or the software running on it is Android compatible".
This needs to change.
UPDATE - I found a workaround that *may* help out. Go into SuperSU and disable root (or disable however you want), try adding your cards again, and then go re-enable root. This has worked for many people on other phones with this error, but it didn't help on my T-Mobile S4
Let me know if you get it to work on another ROM (or even if it works at all on stock right now)
Dowload - http://www.mediafire.com/download/1bvbsouwtcz9mx2/Android_Pay_1.0.102576552_930000657.apk
deke997 said:
So I downloaded the new Android Pay app last night, but it doesn't seem to work if you have a custom ROM installed. I'm currently on Resurrection and it gives me the error "Google is unable to verify that your device or the software running on it is Android compatible".
This needs to change.
UPDATE - I found a workaround that *may* help out. Go into SuperSU and disable root (or disable however you want), try adding your cards again, and then go re-enable root. This has worked for many people on other phones with this error, but it didn't help on my T-Mobile S4
Let me know if you get it to work on another ROM (or even if it works at all on stock right now)
Dowload - http://www.mediafire.com/download/1bvbsouwtcz9mx2/Android_Pay_1.0.102576552_930000657.apk
Click to expand...
Click to collapse
Disabling SuperSU worked for me. It allowed Android Pay to verify my phone.
Not sure I like that I HAVE to have a Lock Screen setup. And, why can't Android Pay have a lock screen built into it like the new Google Wallet does. Wouldn't we want two part authentication?
Rob
I just installed Danvdh's new 5.1 GPE rom and I'm pretty sure Android Pay was already installed. Haven't tested it yet, though. Looking forward to seeing if Xposed will work alright to keep root enabled while using Pay.
HampTheToker said:
I just installed Danvdh's new 5.1 GPE rom and I'm pretty sure Android Pay was already installed. Haven't tested it yet, though. Looking forward to seeing if Xposed will work alright to keep root enabled while using Pay.
Click to expand...
Click to collapse
I re-enabled SuperSU after the install, and it seems to be working. However, it looks like updating also checks root. So, I had to disable root again to have the update to Android Pay take. But, re-enabled root after the update, and things seem to be working.
Rob
You all that state you have it working on T-MO SGH-M919, must be running the T-MO 4.4.4 software. I had it working too - even on a ROOTED 4.4.4. device. Once I install a CyanogenMod Custom LOLLIPOP ROM - and re-installed the AndroidPay, it no longer works. You get the message that ANDROID CANNOT BE VERIFIED (or some crap like that).
Phone works perfect for everything but that...and of course my GoogleWallet was upgraded and no longer has the TAP TO PAY feature...and you cannot get that one back either.
So I guess I need to find out how to get my phone back to STOCK T-MO 4.4.4, none of the downloads anywhere can actually be downloaded any more (unless anyone has a valid link one of those).
Thanks,
*BH*
I'll give you fair warning, as I participated in the lengthy discussion thread over at the Nexus 5 forum (the thread that had the Google developer participating). Here's the lowdown.
Due to liability pressure from Visa, MasterCard, and the others, Android Pay is very...uptight about its operating environment. It basically won't accept any environment it can't trust, and that basically boils down to a system that is stock and unaltered. Anything that can undermine Android's security model (root, custom ROMS, Xposed Framework, etc.) is red-flagged and the app will break. Now, before anyone begins moaning about how Google Wallet worked before, that will be going away soon under pressure from MasterCard. The new system is tokenized and closer to Chip transactions, which is where everyone will be going over the next few months, and under these new rules, if Google can't show due diligence in trying to maintain a chain of trust throughout the transaction (IOW, try their best to ensure a clean environment with no exploitable features), Google faces the bill for instances of fraud. Any attempt to address this problem simply cannot be done the way Android is setup now. Since anything with root access can do anything to the OS, there's just no way to corral this, not even with Marshmallow. Anyone who has used Samsung Pay will notice they take precautions, too. They're a little more lenient with root because they can protect the chain with Knox. Trip Knox and Samsung Pay balks.
Odds are, this development may make phone manufacturers turn back to things like Secure Elements (or some other system outside Android's scope) to provide a way to ensure a chain of trust even with root present. That's likely why Apple isn't too concerned with Apple Pay working with jailbroken phones (all Apple Pay-ready iPhones carry Secure Elements). Until further development, that's just the way it is with Android Pay.