Samsung Knox Odin Problems - Android Q&A, Help & Troubleshooting

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.

Related

[Q] AT&T trying to update Galaxy S3 while rooted & TWRP Recovery Installed

Hi guys
I just got my wife a Samsung Galaxy S3 I747 for ATT using Straight Talk. I purchased one for my self about 3 months ago, same model. Both were purchased used, mine had 4.1.2 and my wife's has 4.1.1. I rooted and installed CWM Recovery on mine. I wanted to update my wife's to at least 4.1.2 like mine or even 4.1.3.
From my understanding, once you root and install a recovery mod, such as TWRP or the ClockWorkMod Recovery, that your phone will not be able to update via your service provider.
The problem is, I got her phone yesterday, and I tried to update it, but it kept saying it was at the latest update/firmware. I even installed Kies, but it reported the same thing. After a few hours, I decided I would root it and install TWRP and maybe install a new ROM with the FW on it later. Well, this morning, the phone reported that an important update was available. Somewhat confused, b/c I thought it couldn't be the FW b/c yesterday it said the phone was at the latest FW, and plus the fact the update is, as I thought, refused by the service provider or phone, when it is rooted or a recovery mod is installed. When it finished, of course it asked to reboot. I was curious how this was going to play out.
When it rebooted, it loaded the TWRP Recovery. Being still new to all this, I wasn't sure how to proceed, so I clicked the reboot button, but nothing happen, so I tried the shutdown button. The phone powered off with no issues. I turned it back on and it loaded successfully to the home screen. I checked the status of the update, and it said it failed. No surprise there, I'm just happy it didn't brick her phone during the process.
Is this normal? Should I just disable updates from my provider? Is it possible to install the update and then just reapply the root and recovery mod?
Thanks
Mike
Modify_inc said:
Hi guys
I just got my wife a Samsung Galaxy S3 I747 for ATT using Straight Talk. I purchased one for my self about 3 months ago, same model. Both were purchased used, mine had 4.1.2 and my wife's has 4.1.1. I rooted and installed CWM Recovery on mine. I wanted to update my wife's to at least 4.1.2 like mine or even 4.1.3.
From my understanding, once you root and install a recovery mod, such as TWRP or the ClockWorkMod Recovery, that your phone will not be able to update via your service provider.
The problem is, I got her phone yesterday, and I tried to update it, but it kept saying it was at the latest update/firmware. I even installed Kies, but it reported the same thing. After a few hours, I decided I would root it and install TWRP and maybe install a new ROM with the FW on it later. Well, this morning, the phone reported that an important update was available. Somewhat confused, b/c I thought it couldn't be the FW b/c yesterday it said the phone was at the latest FW, and plus the fact the update is, as I thought, refused by the service provider or phone, when it is rooted or a recovery mod is installed. When it finished, of course it asked to reboot. I was curious how this was going to play out.
When it rebooted, it loaded the TWRP Recovery. Being still new to all this, I wasn't sure how to proceed, so I clicked the reboot button, but nothing happen, so I tried the shutdown button. The phone powered off with no issues. I turned it back on and it loaded successfully to the home screen. I checked the status of the update, and it said it failed. No surprise there, I'm just happy it didn't brick her phone during the process.
Is this normal? Should I just disable updates from my provider? Is it possible to install the update and then just reapply the root and recovery mod?
Thanks
Mike
Click to expand...
Click to collapse
It is perfectly normal. You described the expected sequence for a phone with any custom recovery. OTA updates download then reboot into stock recovery. Absent that ..what you said.
For your update path, I. urge you to visit xda's i747 forum & read up on the controversy & pitfalls of AT&T's OTA 4.3
Look out for:
locked bootloader
Knox Warranty bit
one way upgrade
(on pain of brick)
It's different this time around.

[Q] AT&T Galaxy S4 Root Problems: Can't Update OR Unroot???

My SGH-I337 (ATT GS4) has been rooted for a month or two now but lately it's been having issues so I tried to restore it to stock. But, I manually removed the root via SuperSU so I would be able to update to 4.4 (I've been stuck on 4.2.2 because I was never notified 4.3 came out). Every time I update OTA it fails at 25%, so I tried via Kies. My firmware isn't even supported to update like that. I tried unrooting with Odin but that also didn't work. I've restored it to factory settings now, but the boot image still says custom and I can't use Yellow Triangle because that doesn't support locked AT&T basebands (which I read is unfixable). Is there ANY way I can fix this and get 4.4????
TL;DR
My phone is too rooted to OTA update but not rooted enough for Odin to work and I want KitKat
ghdawg6197 said:
My SGH-I337 (ATT GS4) has been rooted for a month or two now but lately it's been having issues so I tried to restore it to stock. But, I manually removed the root via SuperSU so I would be able to update to 4.4 (I've been stuck on 4.2.2 because I was never notified 4.3 came out). Every time I update OTA it fails at 25%, so I tried via Kies. My firmware isn't even supported to update like that. I tried unrooting with Odin but that also didn't work. I've restored it to factory settings now, but the boot image still says custom and I can't use Yellow Triangle because that doesn't support locked AT&T basebands (which I read is unfixable). Is there ANY way I can fix this and get 4.4????
TL;DR
My phone is too rooted to OTA update but not rooted enough for Odin to work and I want KitKat
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2663992

[Q] Android 4.3 knox issues after root

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.

Samsung Galaxy S4 Problem [Need Help Badly]

So, I had tryed to install at root and flash a Rom onto my Samsung Galaxy s4 i337 using MF3. I was running Android 4.2.2 and when I had tried to unroot my device, something happened and I wasn't able to FULLY get the root off my device. A couple days ago, I had wanted to upgrade to the Android KitKat 4.4 so when I completed the process. It went into Download mode, and then just crashed. Right now it shows an error message saying
"System software not authorized by AT&T has been found on my phone. Please turn off your phone and go to the nearest AT&T store for help."
Also in the top left hand corner it says Secure fail:Kernel so obviously it means I am missing a Kernel of some sort.
Please help me!
How were you trying to upgrade - via OTA? So you have not successfully flashed 4.3 or 4.4.2 through Odin, correct? But you should be able to find everything you need here:
http://forum.xda-developers.com/showthread.php?t=2616221
and/or
http://forum.xda-developers.com/showthread.php?t=2663545
There's a couple different ways to go depending on if you are trying to save your bootloader to be able to downgrade again easier, if wanted, or not.

[Q] Soft Bricked VZW Note 2

Ok I desperately need some help here. I first got my Note 2 February of last year and quickly rooted it and loaded up Scott's Clean Rom (whichever version was available at the time). I kept going through the updates for Clean Rom and had no issues and was still running Clean Rom until a few weeks ago. Since he was no longer making updates to it I decided just to return to stock since I didn't need root capabilities anymore. I went through the steps in this post, [GUIDE][VZW Edition]How to Root/Rom/Return to Stock the VZW Galaxy Note II! to flash the Official VRAMC3 4.1.2 update to return to stock and had no issues. Everything worked perfectly for several days. Then a friend of mine let me borrow his Note 3 out since I was thinking about buying one. While I had the Note 3, he accepted the latest factory update on my Note 2. Now I'm soft bricked, hopefully not hard bricked.
When I boot up the phone it just sits on the Galaxy Note 2 logo. I can't get into recovery but I can still get into Odin mode. I first tried using Odin to flash the pit file to repartition the phone, and even though I knew it probably wouldn't work I then tried loading the Official VRAMC3 4.1.2 update again. Of course it failed. I've tried multiple times since then to load the Official 4.3 updates, even the newest one that just came out a few days ago. No matter what I have tried I still cannot get the phone to load past the Galaxy Note 2 logo or get into recovery. Also when I go into Odin Mode here is exactly what it reads.
PRODUCT NAME: SCH-1605
CUSTOM BINARY DOWNLOAD: No
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
KNOX WARRANTY VOID: 0
AP SWREV: A2
Any help would be greatly appreciated. I can't buy the Note 3 like I want to until I'm able to fix and sell this phone, so I'm currently stuck using my old HTC Thunderbolt that barely runs at this point. Thanks in advance!!
xashaffer said:
Ok I desperately need some help here. I first got my Note 2 February of last year and quickly rooted it and loaded up Scott's Clean Rom (whichever version was available at the time). I kept going through the updates for Clean Rom and had no issues and was still running Clean Rom until a few weeks ago. Since he was no longer making updates to it I decided just to return to stock since I didn't need root capabilities anymore. I went through the steps in this post, [GUIDE][VZW Edition]How to Root/Rom/Return to Stock the VZW Galaxy Note II! to flash the Official VRAMC3 4.1.2 update to return to stock and had no issues. Everything worked perfectly for several days. Then a friend of mine let me borrow his Note 3 out since I was thinking about buying one. While I had the Note 3, he accepted the latest factory update on my Note 2. Now I'm soft bricked, hopefully not hard bricked.
When I boot up the phone it just sits on the Galaxy Note 2 logo. I can't get into recovery but I can still get into Odin mode. I first tried using Odin to flash the pit file to repartition the phone, and even though I knew it probably wouldn't work I then tried loading the Official VRAMC3 4.1.2 update again. Of course it failed. I've tried multiple times since then to load the Official 4.3 updates, even the newest one that just came out a few days ago. No matter what I have tried I still cannot get the phone to load past the Galaxy Note 2 logo or get into recovery. Also when I go into Odin Mode here is exactly what it reads.
PRODUCT NAME: SCH-1605
CUSTOM BINARY DOWNLOAD: No
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
KNOX WARRANTY VOID: 0
AP SWREV: A2
Any help would be greatly appreciated. I can't buy the Note 3 like I want to until I'm able to fix and sell this phone, so I'm currently stuck using my old HTC Thunderbolt that barely runs at this point. Thanks in advance!!
Click to expand...
Click to collapse
Did you try to go into Odin and flash this:
VRUEMJ9 4.3- http://www.androidfilehost.com/?fid=23269279319197589(ONLY USE THIS IF YOU TOOK THE 4.3 OTA!! There currently is no bootloader unlock method for 4.3 which means you can no longer flash custom roms, recoveries, or kernels!!!)
with the pit inlcuded.. If not do so.. Then report back.. If you can not get past "Note 2" screen then see, now, if you can get into recovery.. Press UP+HOME+POWER.. and then proceed to do a Factory Reset.
lacoursiere18 said:
Did you try to go into Odin and flash this:
VRUEMJ9 4.3- USE THIS IF YOU TOOK THE 4.3 OTA!! There currently is no bootloader unlock method for 4.3 which means you can no longer flash custom roms, recoveries, or kernels!!!)
with the pit inlcuded.. If not do so.. Then report back.. If you can not get past "Note 2" screen then see, now, if you can get into recovery.. Press UP+HOME+POWER.. and then proceed to do a Factory Reset.
Click to expand...
Click to collapse
That was the first thing that I tried and I still could not get pass the logo or get into Recovery. I will try it again though shortly and let you know what happens.
Just tried it. According to Odin everything Passes, but it still won't go past the logo screen and still won't go into recovery. Any other ideas?

Categories

Resources