[Q] Android 4.3 knox issues after root - Android Q&A, Help & Troubleshooting

Hi, so I tried searching but I couldn't find anyone with the same problem.
So I upgraded Android 4.1.2 to 4.3 a couple of days on my galaxy s3 & I noticed that the root was gone with the update, little did I know that there was this awesome new Knox software (solving problems by creating new ones, heh) which would prevent superSU from starting after rooting. Not to mention this amazing Samsung program also wouldn't start on rooted devices so there was no way I could uninstall it either.
So I realized I had done a mistake and did a hard reset, however, when the phone started again I saw that SuperSU was still there and I was getting the same error as before & Knox (would you believe it) still refused to start. So I heard that my only option now is to flash my Galaxy S3 with 4.3 with Odin to clean it completely, however I'm not able to find a Rom to do it with ever since SAMSUNG released the update in KIES.
I don't really care for Knox and would like it gone completely. I just want my phone to work again with root, my warranty already ran out anyway.
Any help appreciated. Thank you.

Related

[Q] Question re root limbo on GT-I9300 post Kies firmware update

Hi, appreciate this is my first post and thus my question will be regarded with a certain amount of skepticism.. am only posting cos I think my issue is unusual and have not been able to find a similar question/answer through my searches on this forum
Basically, the issue is I rooted my Galaxy S3 (GT-I9300) a month or so ago, installed clockwork mod and superuser etc,. however I held off flashing a ROM because I figured my OTA jellybean update was imminent and wanted to see what the touchwiz jellybean looked like before installing Cyanogen or another ROM. wasn't sure if the OTA would come thru once I shed the stock ROM
So I waited for weeks for the OTA (am on Orange, now Everything Everywhere, in the UK) and have not received it.. last week I went onto Kies and saw there was a new firmware update, so I updated thru Kies thinking that might be what was needed to receive the OTA JB update. updated the firmware but still no JB update - however, now when I check my root status on Root Checker, or try to use any app that requires root, I'm told that I don't have "proper" root access.
My question is updating the firmware over Kies, did that mess up my root access.. am I now unrooted? (this doesn't seem correct) It seems to me I am in a limbo of sorts - not properly rooted anymore, but not fully unrooted either. I want to root the thing again so I can install cyanogen or supernexus, and I would appreciate advice on what to do - should I do a factory reset and then root again as before, or will this cause issues.. was just gon soldier ahead and do it but aware that this may cause problems if my phone already has files from the previous attempt on there.. for example the SGS3 toolkit V.6.0.0 I'm using says not to proceed with its root operations on a phone "that's already rooted" so am hesitant to proceed. Any advice would be appreciated. cheers
You've lost root with the update, just root again and it's all good.

[Q] Soft Brick, Help!

I've been trying to get my phone back on stock rom for hours or at least to the point where I can use it. Ive tried several methods in the past day. However, I have not been able to do it without success. This was all for the purpose of updating to 4.3 since I hadn't updated since I rooted my phone. First I unrooted it through Supersu and tried to apply the update but it wouldnt work so then I factory reset it. I applied the update again but it didnt seem to want to update to 4.3 . So then I went to TWRP and cleaned out the files, but I never checked to it to the system. After that It was stuck into a boot loop. It never got past the Galaxy s4 boot image. I still have a back up of everything after I rooted my phone, but after applying the following system recovery
stockroms.net/file/GalaxyS4/SPH-L720/L720VPUAMDC_L720SPTAMDC_SPR.zip
I am no longer able to use TWRP and my phone is still in the same situation. All I know about my phone without acess to the information in the about phone section is that it is a Verison Galaxy S4 and before I did anything it was on an android 4.2.2 rooted stock. On the box it say its a SPHl720BKK. If anyone could help me that would be greatly appreciated before I hard brick my phone with the little experiance i have.
santiagorook said:
I've been trying to get my phone back on stock rom for hours or at least to the point where I can use it. Ive tried several methods in the past day. However, I have not been able to do it without success. This was all for the purpose of updating to 4.3 since I hadn't updated since I rooted my phone. First I unrooted it through Supersu and tried to apply the update but it wouldnt work so then I factory reset it. I applied the update again but it didnt seem to want to update to 4.3 . So then I went to TWRP and cleaned out the files, but I never checked to it to the system. After that It was stuck into a boot loop. It never got past the Galaxy s4 boot image. I still have a back up of everything after I rooted my phone, but after applying the following system recovery
stockroms.net/file/GalaxyS4/SPH-L720/L720VPUAMDC_L720SPTAMDC_SPR.zip
I am no longer able to use TWRP and my phone is still in the same situation. All I know about my phone without acess to the information in the about phone section is that it is a Verison Galaxy S4 and before I did anything it was on an android 4.2.2 rooted stock. On the box it say its a SPHl720BKK. If anyone could help me that would be greatly appreciated before I hard brick my phone with the little experiance i have.
Click to expand...
Click to collapse
You're posting in a forum for the SCH-I545. That's a Verizon Galaxy S4.
The SPH-L720 is an international phone, You'll need to post on a forum for that particular variant of the GS4 if you expect any help.

Samsung Knox Odin Problems

Hello! I am new to this forum but I am in a little fickle.
I have the Samsung Note 2 TMOBILE and couple weeks ago, I updated to 4.3 through regular OTA. I then rooted and flashed Cyanogenmod 11 and thus, voided my Samsung Knox Warranty bugger thing. I then attempted to go back to stock by flashing stock 4.1.1 through Odin and it worked! I tried to do OTA update again but I realized that the Samsung Knox Void kept me from reaching update services... So I was stuck at 4.1.1 Stock. From there, I was able to flash other custom roms and everything worked.
However, this is a problem for me. The 4.1.2 update from Tmobile was what enabled LTE on my note 2. So right now, I have the old baseband(?) that does not allow LTE. I even attempted to flash a non-knox 4.1.2 (which allowed LTE) through Odin and everything worked until the last second, but it flashed FAIL and I was unable to update my baseband(?).
I was wondering if there is another way to enable LTE by updating to 4.1.2 in any way? Or is this completely unable due to the Samsung Knox?
Thank you in advance.

[Q] [Troubleshoot] Can't root or unroot my phone

About a month ago I rooted my Samsung Galaxy Grand(the single sim version) with the help of Klingo Root, worked like a charm and had no problems at all. I even uninstalled all the bloatware samsung and the carrier had installed. About 3 weeks ago then an official update poped-up, so I updated my phone through Samsung Kies. Everything went fine, but after the reboot of the phone I noticed that all the bloatware was back, so I just figured, maybe i have to uninstall it again.
But then disaster struck SuperU said there is no SU Binary installed, so I though could have the update unrooted my phone? So I tried rooting it again with Klingo, doesn't work, I tried Framaroot, doesn't work either, I even tried to install Clockworkmod with Odin and it doesn't work. I even repeated the procedure while factory resetting my phone.
Has anyone else encountered this? It seems my phone is somewhere in between being unrooted and rooted? Everything else works fine.
Help! I just want to uninstall the carrier bloatware!
Difference In Android Firmware
ne6c said:
About a month ago I rooted my Samsung Galaxy Grand(the single sim version) with the help of Klingo Root, worked like a charm and had no problems at all. I even uninstalled all the bloatware samsung and the carrier had installed. About 3 weeks ago then an official update poped-up, so I updated my phone through Samsung Kies. Everything went fine, but after the reboot of the phone I noticed that all the bloatware was back, so I just figured, maybe i have to uninstall it again.
But then disaster struck SuperU said there is no SU Binary installed, so I though could have the update unrooted my phone? So I tried rooting it again with Klingo, doesn't work, I tried Framaroot, doesn't work either, I even tried to install Clockworkmod with Odin and it doesn't work. I even repeated the procedure while factory resetting my phone.
Has anyone else encountered this? It seems my phone is somewhere in between being unrooted and rooted? Everything else works fine.
Help! I just want to uninstall the carrier bloatware!
Click to expand...
Click to collapse
When you update your software it actually update your firmware. So the previous method will not work for this firmware.
1. you need to do it with different method if developers found it for you
2. just installed previous version of android .
3. May be fixed by factory reset..
4. You can even install prerooted custom rom like CM11
As per my experience new update will not that much compactible for all phones..
Hi, I'll start from the beginning, so I have a smart phone vodafone 2 (Alcatel V860) I wanted to upload the new software but accidentally I uploaded a backup of the tablet, after uploading the backup phone can not be connected as the flash mode, or in any way, you can not enter the recovery can not in any way connect the computer, the phone is as if dead. when I connect it to the computer when it is turned off the sound indicating that a new device has been detected, however, this software can not be installed. I hope that there will be a magician who already had a similar problem and knows what to do. Please help as soon as possible, if anyone knows what's going on I can talk about it on skype because it seems to me that it will be hard to even describe.
Thanks in advance.
aditya.kamble said:
When you update your software it actually update your firmware. So the previous method will not work for this firmware.
1. you need to do it with different method if developers found it for you
2. just installed previous version of android .
3. May be fixed by factory reset..
4. You can even install prerooted custom rom like CM11
As per my experience new update will not that much compactible for all phones..
Click to expand...
Click to collapse
Can I then "downgrade" through Samsung Kies then?
Flash Firmware through Odin...
ne6c said:
Can I then "downgrade" through Samsung Kies then?
Click to expand...
Click to collapse
No... Samsung kies doesnt provide feature to downgrade android.
You need to flash firmware package through odin.
you can google it for your device or search on xda...
All the best..
Press Thanks button for each person helped you...

[Q] sgh-i527 no touch response after 4.4.2 update.

I have a at&t mega i527. A few days ago. I pressed update and it updated. I eyed to take the battery out before it would compete and now the touch screen is not responsive. I have tried everything. . Kies. Odin. Adb sideload. Nothing had worked. I even replaced the screen. Nothing I try had worked. Does anybody have any ideas thati could try. I feel like I've tried everything. Any ideas or help will be greatly appreciated
Back to stock you go...
Problem is tho, I do not know where the update failed in between 4.2 and 4.4.2. Go to THIS THREAD and try the 4.4.2 (UCUBNE7) BUT BE ADVISED that you cannot root UCUBNE7 at this time per THIS THREAD:crying::crying::crying::crying::crying:
It looks like we may be close, but my girlfriend's Active just installed a post 4.4.2 update that updated security policy manager to remove the root vulnerability that was found recently. Samsung/AT&T seems to have a team dedicated to stamping out root for anything KitKat.
I would personally stay pre kit-kat (UCUAMK2) if at all possible. That firmware is located at THIS THREAD:good:

Categories

Resources