Trying to update after rooting the device and this is what you are met with. I remember with older devices you could still update even though it broke root, and you would have to reroot. Which what I was hoping to do. Apparently they have figured out how to block you now. Especially since I can never get Kies to work right.
Only way I found to bring otas back is to uninstall supersu, odin flash stock Rom, and try again
Dude download xposed module and download Wanamaker kit to trick the system thinking it's still official. I tried this with and twrp couldn't install the latest version. If you are still on stock recovery good for you
Sent from my SM-T230NU using XDA Free mobile app
Related
I'm currently on 4.0.4 (Canadian version) N8010 and I want to update to 4.1.2 (canadian? not sure if it really makes a difference). I get the notification for the update, but when I select it, it fails, and it also fails with Kies.
When I first got the note I opted for the exynos exploit to root my tablet. I was under the impression that if I disabled root from the app my status would revert back to "non-custom". I've uninstalled exynosabuse and busybox (i think supersu uninstalled with the root disabled) and I've restarted multiple times and waited a few hours. No change. I think I'll try to re-enable root and restore some apps that I froze with titanium backup to see if it reverts back.
The other option I guess would be to get the Canadian rom and flash via Oden. although I think that would wipe by note, which i would like to avoid. I found some links to the canadian rom, but they're down.
Thanks for the help/advice.
Njord0 said:
I'm currently on 4.0.4 (Canadian version) N8010 and I want to update to 4.1.2 (canadian? not sure if it really makes a difference). I get the notification for the update, but when I select it, it fails, and it also fails with Kies.
When I first got the note I opted for the exynos exploit to root my tablet. I was under the impression that if I disabled root from the app my status would revert back to "non-custom". I've uninstalled exynosabuse and busybox (i think supersu uninstalled with the root disabled) and I've restarted multiple times and waited a few hours. No change. I think I'll try to re-enable root and restore some apps that I froze with titanium backup to see if it reverts back.
The other option I guess would be to get the Canadian rom and flash via Oden. although I think that would wipe by note, which i would like to avoid. I found some links to the canadian rom, but they're down.
Thanks for the help/advice.
Click to expand...
Click to collapse
Did you install a custom recovery or do you still have stock recovery installed and can you tell us your ROM's build number.
.
kkretch said:
Did you install a custom recovery or do you still have stock recovery installed and can you tell us your ROM's build number.
.
Click to expand...
Click to collapse
I still have the stock rom, I haven't installed anything custom, just use the exploit for the root access.
Build number: IMM76D.N8010WALG4
Njord0 said:
I still have the stock rom, I haven't installed anything custom, just use the exploit for the root access.
Build number: IMM76D.N8010WALG4
Click to expand...
Click to collapse
Without a stock 4.1.2 firmware for your device it looks like you are going to have to do a factory reset to use Kies.
I think your options are limited..........
Have you considered using a firmware from another country?
You know there is a backup program called Helium that does not need root, you may want to consider using it to backup all of your data and then do a factory reset.
I don't know if I have helped you any............
Hey guys,
I just got my phone and it updated to 4.4 pretty much out of the box. I still wanted to root so I used a method I found on here (will find if necessary) which is supposed to not trip the KNOX by putting the phone into "Custom Mode." Everything went fine until I tried to use ROM Manager to install CM.
When I boot I get the message "System software not authorized by Verizon Wireless has been found on your phone. Please turn off your phone and go to the nearest Verizon Wireless store for help." I've tried reflashing using Odin, clearing the cache and factory resets, but I get the same error every time.
I'm currently downloading another stock ROM which might work, but I wanted to see if anyone else has had this problem?
Thank you!
mortified21 said:
Hey guys,
I just got my phone and it updated to 4.4 pretty much out of the box. I still wanted to root so I used a method I found on here (will find if necessary) which is supposed to not trip the KNOX by putting the phone into "Custom Mode." Everything went fine until I tried to use ROM Manager to install CM.
When I boot I get the message "System software not authorized by Verizon Wireless has been found on your phone. Please turn off your phone and go to the nearest Verizon Wireless store for help." I've tried reflashing using Odin, clearing the cache and factory resets, but I get the same error every time.
I'm currently downloading another stock ROM which might work, but I wanted to see if anyone else has had this problem?
Thank you!
Click to expand...
Click to collapse
You are permanently stuck on the TW 4.3 OTA because the bootloader is signed with special keys that prevents:
-installing a custom recovery
-flashing custom roms/kernels
-downgrading your software below 4.3
If you can boot into download mode, do this 4.3 soft brick method.
With TW 4.3 OTA, all you can do is root using a tool called: Saferoot.
If you have 4.3 stock firmware you can root and that's it, no custom recovery, no custom rom, kernel, nothing, and just a heads up there are like 10 threads where people don't read and have done what you have, you need to flash the Odin 4.3 image for you phone to work again, never take an ota, enjoy your locked down device now
Sent from my SCH-I535 using XDA Premium 4 mobile app
SlimSnoopOS said:
You are permanently stuck on the TW 4.3 OTA because the bootloader is signed with special keys that prevents:
-installing a custom recovery
-flashing custom roms/kernels
-downgrading your software below 4.3
If you can boot into download mode, do this 4.3 soft brick method.
With TW 4.3 OTA, all you can do is root using a tool called: Saferoot.
Click to expand...
Click to collapse
Worked perfectly! Thank you so much!
mortified21 said:
Worked perfectly! Thank you so much!
Click to expand...
Click to collapse
My pleasure but all the thanks is owed to ThePagel, make sure to post your success in his thread. The more people that report their success with that method, then the less fear someone else may have in using that should they suffer the same experiences. :victory::good::good:
If you need any updates on the state of TW 4.3 then keep this discussion thread bookmarked.
I did the same thing today. The 4.3 update installed by itself!!! So i rooted it using Saferoot,
i installed rom manager, clicked the Install rom from sd card and i got that message. it will repeat that message and it wont boot. So i went into Odin mode and hit the volume down button to restart it. And after that it booted normally.
So basically i am stuck with 4.3? and is there 4.4 out for our phones yet?
also forgot to mention, it says my OS is custom when i first realized it updated.
AURMEND said:
I did the same thing today. The 4.3 update installed by itself!!! So i rooted it using Saferoot,
i installed rom manager, clicked the Install rom from sd card and i got that message. it will repeat that message and it wont boot. So i went into Odin mode and hit the volume down button to restart it. And after that it booted normally.
So basically i am stuck with 4.3? and is there 4.4 out for our phones yet?
also forgot to mention, it says my OS is custom when i first realized it updated.
Click to expand...
Click to collapse
Once you successfully updated with 4.3, you stuck with 4.3, there is no going back or flash anything and 4.3 is the latest factory rom for now. There's no 4.4 yet for our phone. There is custom 4.4 but only for people who didn't take the 4.3 update. Since they still have unlocked bootloader so they could load any custom rom.
buhohitr said:
Once you successfully updated with 4.3, you stuck with 4.3, there is no going back or flash anything and 4.3 is the latest factory rom for now. There's no 4.4 yet for our phone. There is custom 4.4 but only for people who didn't take the 4.3 update. Since they still have unlocked bootloader so they could load any custom rom.
Click to expand...
Click to collapse
Dang this sucks. I have no idea how it installed automatically then. I was listening to music the whole time. And I was trying to get a custom 4.4 after the update...
AURMEND said:
Dang this sucks. I have no idea how it installed automatically then. I was listening to music the whole time. And I was trying to get a custom 4.4 after the update...
Click to expand...
Click to collapse
Yep! sucks big time!!
I have a SCH I535 S3 on Verizon
Build: JS5VRUCNC1S15J.I53
Android 4.3
I535VRUCNC1
It is rooted using a method i found on XDA, but I do not remember the exact method details.
I received the OTA offer about a month ago and all attempts to get it to install have failed.
What I have tried:
*1. Full phone reset then OTA attempt
*2. Wipes cache then OTA attempt
I searched all over for manual updates but a lot of the sites seem sketchy. *If the seem ok, the download links don't work.
Should I unroot next?
Yes you must be completely stock to take the ota. If all else fails there is always odin
Sent from my SCH-I535 using XDA Free mobile app
There's a log file that you can look at to see why the update is failing. I used this to find out why my phone wasn't updating... and it was because I had a frozen app (Amazon Books). I restored that app, and the update took place. You simply need to look at (or post) the log from the update. Alternatively, you can always ODIN as mentioned above.
So I have tripped KNOX already. I'm using TWRP, Xstrolite 2.3.
I've tried unchecking superSU root and retrying. I've tried using root cloaker.
Is there an easy way to not have the bootloader unlocked? Or is it once I flashed TWRP, its unlocked forever.
Has anyone else been able to successfully use Android Pay? Post your experience
I'm in the same boat as you, I've tried disabling SuperSU and using root cloak as well to no avail. I've also got the Xtrestolite ROM running Unikernel V8 and I keep getting compatibility errors no matter what I seem to do. Could it be possible that Android Pay is detecting that KNOX is compromised and therefore disabling Android Pay? The only other thing I can think of is that running a custom ROM somehow prevents Android Pay from being compatible. I'm almost tempted to make a nandroid backup and temporarily install the stock ROM to see if that solves the problem.
derwreck said:
I'm in the same boat as you, I've tried disabling SuperSU and using root cloak as well to no avail. I've also got the Xtrestolite ROM running Unikernel V8 and I keep getting compatibility errors no matter what I seem to do. Could it be possible that Android Pay is detecting that KNOX is compromised and therefore disabling Android Pay? The only other thing I can think of is that running a custom ROM somehow prevents Android Pay from being compatible. I'm almost tempted to make a nandroid backup and temporarily install the stock ROM to see if that solves the problem.
Click to expand...
Click to collapse
Exactly.. Or that we're running a custom recovery too.
My thought is that the xstolite rom makes your phone be seen as a s6 edge.. Wonder if that affects things too. Though I've changed in the build prop back to 920T.
Would be a big bummer for us who've tripped Knox getting screwed out of android and Samsung pay. Others with rooted phones, have said it works.
tlxxxsracer said:
Exactly.. Or that we're running a custom recovery too.
My thought is that the xstolite rom makes your phone be seen as a s6 edge.. Wonder if that affects things too. Though I've changed in the build prop back to 920T.
Would be a big bummer for us who've tripped Knox getting screwed out of android and Samsung pay. Others with rooted phones, have said it works.
Click to expand...
Click to collapse
I also changed the build prop to reflect my SM-G920F model. I really wish I could get Android Pay to function on this device, I tripped KNOX with the full understanding that I was going to lose the ability to use Samsung Pay but never did I imagine that using a custom ROM would cause me to compromise Android Pay as well. I purchased an international unlocked model of the S6 so naturally, the bootloader was unlocked from the factory, I don't know if having an unlocked bootloader necessarily causes you to lose Android Pay. It either has to be due to the fact that we're running a custom ROM, custom recovery, or because KNOX is tripped and it's preventing AP to run like it should.
Try installing the stock rom for your phone. Then under supersu simply uncheck root and see if adding the cards work
I have it running and got my bank card added haven't had a chance to use it though. I'm using TWRP on WanamLite, Adam kernel, with Xposed and a whole lot of stock apps deleted including KNOX and private mode. All I did was unroot, install, AP, root, profit. I'm guessing its something missing from XtreStoLite.
Sent from my SM-G920F
Infekxion said:
I have it running and got my bank card added haven't had a chance to use it though. I'm using TWRP on WanamLite, Adam kernel, with Xposed and a whole lot of stock apps deleted including KNOX and private mode. All I did was unroot, install, AP, root, profit. I'm guessing its something missing from XtreStoLite.
Sent from my SM-G920F
Click to expand...
Click to collapse
When you said you unrooted.. did you uncheck the root box in SU app or uninstalled all together and then reinstalled?
Full unroot under the Cleanup section
Sent from my SM-G920F
think its reading something in the buildprop similar to how google wallet did.
i also tried modifying a few things in build prop to show official firmware nomenclature to no avail.
Infekxion said:
Full unroot under the Cleanup section
Sent from my SM-G920F
Click to expand...
Click to collapse
After you did full unroot. did you reboot? and to reinstall root, you flashed zip again? or what
After unrooting within SU app I just activated my card then reflashed the zip in recovery.
Sent from my SM-G920F
wouldn't let me set it up on my g920a rooted with custom rom at first.
all i did was go to my super su app from chainfire disabled root and without reboot went back into android pay after i closed it and it let me set up my cards from my Google wallet and a new one. then i went back to the su app and enabled su again.
rob219 said:
wouldn't let me set it up on my g920a rooted with custom rom at first.
all i did was go to my super su app from chainfire disabled root and without reboot went back into android pay after i closed it and it let me set up my cards from my Google wallet and a new one. then i went back to the su app and enabled su again.
Click to expand...
Click to collapse
What rom are you on?
Sent from my SM-G920F
Infekxion said:
What rom are you on?
Sent from my SM-G920F
Click to expand...
Click to collapse
XtreStoLite 1.5 on att
So has anyone got this working on XtreStoLite 2.3 ? Maybe just something that needs to be added to the rom?
Mrzoops said:
So has anyone got this working on XtreStoLite 2.3 ? Maybe just something that needs to be added to the rom?
Click to expand...
Click to collapse
So i did a fresh install but with Tyrannus rom 5.1, it runs the same base as Xstolite (I believe)
I got android pay working on tyrannus rom 5.1
maybe try backing up your current setup, wipe and flash the rom and first thign you do is try android pay and see if it works. Thats what I did on the rom im running now
I got it working on Tyrannus as well...briefly...although I am not sure how I did it.
Currently on XtreStoLite 2.3, using Xposed + No Device Check and an app called SafetyNet Helper...it says my device is good to go, but Android Pay won't work still.
I hope someone is able to pinpoint what prevents it from working and how to spoof it. I tend to have my phone in my hands a lot more than my wallet.
K, got it working. Fresh install of Tyrannus 5.1, did NOT install Xposed. Immediately turned SU off after 1st boot, before updating Google Play Services. Was then able to activate Android Pay and add cards.
Update 20150924: tried to use it at McDonalds for tap and pay. Android Pay started when tapped but never completed the transaction and I had to use my card.
Hey guys, first time on this forum because I've run out of options otherwise. So last night i decided to finally root my phone after reading about it a lot. The root it self went just fine and it was working great. I then tried to download xposed using TWRP. However, that put my phone into a bootloop. It keeps restarted after it comes to the Samsung logo. I did some research and people said to simple put it back to the stock firmware so i downloaded some ( had trouble downloading because sammobile wouldn't work for me) However, now every time I try to flash it back to the stock firmware using odin it says failed and comes up with an error on the phone saying SW REV CHECK FAIL DEVICE 3, BINARY 1. The phone is a SM-G920W8. Any suggestions cause right now I have a $700 paper weight and no back up phone. I'm kinda freaking out haha.
Thanks for the help. I can send screen shots if you guys need them.
same problem.is there a way to install xposed framework without these annoying problems?
how to install the custom recovery and xposed properly?
Yeah, use the correct Xposed for S6.
There's an uninstall tool for the Xposed you've already installed (look in OP for Xposed you installed), that should have been your first step after bootloop. Try now, see if it will uninstall.
There's a Windows tool called SamFirm, or an Android app + website called Updato, use those to download stock ROMs if you still need to.
Then search for Wanam Xposed s6, and use that version.
Sent from my SM-G920W8 using Tapatalk