Related
it keeps telling me there's a tmobile software update, but when i try to update, it restarts the phone and goes into clockworkmod recovery and then i just exit back to the phone and nothing happens.
how do i update it or just turn the notification off?
Download 2.3.6 stock ROM (http://forum.xda-developers.com/showthread.php?t=1391174) and update via odin. I did same thing.
it wont erase my data won't it?
DeathBlimp said:
it keeps telling me there's a tmobile software update, but when i try to update, it restarts the phone and goes into clockworkmod recovery and then i just exit back to the phone and nothing happens.
how do i update it or just turn the notification off?
Click to expand...
Click to collapse
You cannot updatee if you are rooted. If you dont want to update, I believe you can freeze the notification using BloatFreezer or similar. If you do want to update you can either (1) do so via Kies or (2) un-root and then update ota. Either way you will be unrooted and have to re-root
i did update to 2.3.6 when i received the OTA and I click update and realize that i am rooted (root using superoneclick). I let the update goes through and after few minutes, my sgs2 is updated to 2.3.6 with wifi calling and great battery life. I think i will stay stock rooted until Nick (dev for Miui vibrant) made Miui for SGS2
Edit: Like everyone said, every phone is not created equal. Like mine, got updated even its rooted
samdobbs said:
You cannot updatee if you are rooted. If you dont want to update, I believe you can freeze the notification using BloatFreezer or similar. If you do want to update you can either (1) do so via Kies or (2) un-root and then update ota. Either way you will be unrooted and have to re-root
Click to expand...
Click to collapse
I tried an app called voodoo OTA rootkeeper, I got it to temp-unroot my phone but after a restart it went into clockworkmod recovery. i restarted it again and it went back into unrooted mode.
i also cannot find bloatfreezer on android market.
bikrame said:
Download 2.3.6 stock ROM (http://forum.xda-developers.com/showthread.php?t=1391174) and update via odin. I did same thing.
Click to expand...
Click to collapse
thanks, but where do i get the PIT file? or do i need one? would i also need to re-partition? i dont see those information in that thread
DeathBlimp said:
thanks, but where do i get the PIT file? or do i need one? would i also need to re-partition? i dont see those information in that thread
Click to expand...
Click to collapse
You just need one file. I am at work now. i will go home and check and write details tomorrow.
Sorry .
Sent from my SGH-T989 using XDA App
Look at Page 13 of same thread. There is full description.
I've been a long time lurker, first time post.
I have been running the official AT&T ICS release I927UCLH2, and was notified of an update for my phone from Device Management. I am now updated to I927UCLJ3 baseband. To my surprise, my keyboard backlight is now working. So far, everything looks good. There is no sign of this update on the Samsung ICS page. Maybe AT&T is just going to push it out and forgo Kies altogether? Who knows?
GrepACE said:
I've been a long time lurker, first time post.
I have been running the official AT&T ICS release I927UCLH2, and was notified of an update for my phone from Device Management. I am now updated to I927UCLJ3 baseband. To my surprise, my keyboard backlight is now working. So far, everything looks good. There is no sign of this update on the Samsung ICS page. Maybe AT&T is just going to push it out and forgo Kies altogether? Who knows?
Click to expand...
Click to collapse
I get notified too; however because I have CWM installed, it interrupts the installation and I can't install the update.
Any thoughts on what to do to get it installed?
PacoL250 said:
I get notified too; however because I have CWM installed, it interrupts the installation and I can't install the update.
Any thoughts on what to do to get it installed?
Click to expand...
Click to collapse
Seconded here. Do we have to remove CWMR in order to update from the new OTA update?
I just got a software push from AT&T for my Captivate Glide. After the restart, the keyboard lights now work! About phone says: Android v. 4.0.4. Baseband v. I927ULCLJ3. Build number IMM76D. I'll see if other things have been fixed like, ringtones that stop working and clock being x time slow. Both of which required a system restart
Gizmokid2005 said:
Seconded here. Do we have to remove CWMR in order to update from the new OTA update?
Click to expand...
Click to collapse
I reloaded the stock recovery from my LH2 install and tried the OTA update. It downloads the update but fails to install with an "Update Failed" after the reboot.
I never rooted my phone only installed CWM for the Keyboard fix and to backup with CWM. Wish I had never installed CWM now.
Just got off the phone with AT&T myself, the rep said it should be available on Kies, they want me to try the new firmware before they'll continue warranty procedure on my wife's glide.
Edit: Well it's not, but it should be soon I guess.
Second Edit: On phone with samsung, they say the update is still "on hold" on his system. At&t told me to call them if I needed help with the firmware update.
Thanks for the info. Kies kept crashing on me so could not try it and OTA says I need to way 24hrs to try again.
Will try Kies on a second computer.
Is there any way to reset the 24hour AT&T update time without erasing the data partition?
PacoL250 said:
I get notified too; however because I have CWM installed, it interrupts the installation and I can't install the update.
Any thoughts on what to do to get it installed?
Click to expand...
Click to collapse
Gizmokid2005 said:
Is there any way to reset the 24hour AT&T update time without erasing the data partition?
Click to expand...
Click to collapse
I was able to flash back to the 4.0.4 default ROM from samfirmware and then disable automatic time update and move my day ahead one.
Official update get!
Gizmokid2005 said:
I was able to flash back to the 4.0.4 default ROM from samfirmware and then disable automatic time update and move my day ahead one.
Official update get!
Click to expand...
Click to collapse
I might have to try something similar since Kies nows says that "You device does not support upgrading via Kies". Since I did not root my phone it must either not be happy with the flashes I have done to recovery even though I have flashed back to stock recovery or the Keyboard fix I did.
This blows.
does anyone know if i flash with a stock AT&T from sam firmware on a Rogers i927(r) will I be able to update to the new AT&T version on Kies ?
VideoRoy said:
I might have to try something similar since Kies nows says that "You device does not support upgrading via Kies". Since I did not root my phone it must either not be happy with the flashes I have done to recovery even though I have flashed back to stock recovery or the Keyboard fix I did.
This blows.
Click to expand...
Click to collapse
Success!!
Here are my steps:
1. Restore a backup I made with CWMR before when I first installed it before making any mods.
2. Reinstall stock Recovery before doing anything else.
3. Get OTA update even though less than 24 hours since I restored a previous point in time.
Doing the stock ROM was my second choice but since I had a backup at least most of my apps and settings were recovered.
Good luck!
2.3.6 phone says no OTA update. I'll try Kies later.
Sent from my SAMSUNG-SGH-I927 using xda app-developers app
is there someone who would upload it somehow, so I could flash it via ODIN, or something? I cannot update OTA, cause I live outside the US and at&t doesn't reach this destination. . .
Can somwone post the stock LH2 recovery please?
Sent from my SGH-I927 using xda app-developers app
SamMobile download link
This ROM version is downloadable from SamMobile Firmware Page:
link
Downloading is in progress.
You can flash this with Odin.
Is this the same as before with Samsung Touchwiz for the homescreen ?
yohan4ws said:
Is this the same as before with Samsung Touchwiz for the homescreen ?
Click to expand...
Click to collapse
Yes it is essentially the same, but all the things that were wrong are supposedly fixed
Sent from my SGH-I927 using xda premium
How do I root this ?? I have CWM installed on it but am not sure where to get a CWM zip to install SU...
I found an odin flashable I927UCLH2.md5 and used it, and when into settings, about phone, software update, and it gave me an update and I'm downloading it right now.
The phone is now at I927UCLJ3. So AT&T can OTA push it instead of trying to force the phone to work with kies
First thread = noob question
Hi, what exactly does mean: "Set warranty Bit: Kernel" after root?
(Using the search function I couldn't find it)
Thanks
reply
PansenJim said:
First thread = noob question
Hi, what exactly does mean: "Set warranty Bit: Kernel" after root?
(Using the search function I couldn't find it)
Thanks
Click to expand...
Click to collapse
Same question here. It isn't a tragic issue, but still annoying on boot.
Same here
Same here, it's OK but if there's any way to get rid of this, I'd be glad :good:
Is there any way too get rid of that annoying message? After I root, and install custom recovery it appears on every boot and even when I enter in recovery is annoying -.-
rolo143 said:
Is there any way too get rid of that annoying message? After I root, and install custom recovery it appears on every boot and even when I enter in recovery is annoying -.-
Click to expand...
Click to collapse
Only way is to flash back stock firmware = loose root.
ladislav.heller said:
Only way is to flash back stock firmware = loose root.
Click to expand...
Click to collapse
Baseband will loose too.-_-!
So there's no way to have custom recovery + root without having that message.. right? Or at least for now. ..
Sent from my GT-I9195L using Tapatalk
ladislav.heller said:
Only way is to flash back stock firmware = loose root.
Click to expand...
Click to collapse
Yea ok. But Knox wont let you flash back to stock.
I tried.
The messages are from Knox.
Its to tell Tmobile we modified the phone...
Dont you just love Samsung now?
rolo143 said:
Is there any way too get rid of that annoying message? After I root, and install custom recovery it appears on every boot and even when I enter in recovery is annoying -.-
Click to expand...
Click to collapse
No one mentions which JB but if you upgrade or re-install Chainfire's Super SU, I believe current is 1.80, upon installation it will mention Knox asking annoying questions and do you wish to disable Knox. Answer OK, and it will do so upon re-establishing root. You can go into System/apps and rename, move or delete the Knox apps, I suggest 'rename' if you are new to this. (just add .bak to .apk's) Use Root Explorer or ES File Explorer as R/W root and you should be OK.
EDIT: Knox files to rename or whichever, KNOXAgent.apk KNOXStore.apk ContainerAgent.apk
ie: rename Knox...xx.apk.bak
I create a directory on the Ext SD, /App_Bak and just move what I de-bloat or don't need while testing, that way I have them if needed later.
I rooted using the old method, by flashing custom recovery first, then flashing the zip file "rootkit" and then having Superuser.apk on my phone. It worked even with the latest firmware, but now I have that yellow message thing. .
Sent from my GT-I9195L using Tapatalk
rolo143 said:
I rooted using the old method, by flashing custom recovery first, then flashing the zip file "rootkit" and then having Superuser.apk on my phone. It worked even with the latest firmware, but now I have that yellow message thing. .
Sent from my GT-I9195L using Tapatalk
Click to expand...
Click to collapse
Which ROM do you have now? And have you gone to the Play Store and updated to the latest Super SU?
When you update SU it re installs and will, with permission disable Knox. I'm guessing you have. Try a reflash w/Odin 4.2.2 and just repeat the S4_Mini_Rootkit and update SU. Kinda' do it over...Sometimes that helps.
Sorry I'm not too clear right now, been up 25 hrs and gotta' sleep. I'm older than dirt and can't go the distance any more.
EDIT:Apologies, missed the part about you having the latest firmware. If you are on 4.3, others have had success so IDK, unless you have an earlier SU than 1.80.
My Bad...Another EDIT: Did you by chance go into system/apps and delete KNOXAgent.apk, KNOXStore.apk, ContainerAgent.apk ? Just maybe......... I gotta' sleep, bye.
Lol... I don't have Knox security warnings, I deleted all Knox files. The message in yellow says "Set Warranty Bit: kernel" on Samsung boot logo, but that's it. I think is nothing to worry about, but if I can get rid of it, that would be great. It appeared after I installed TWRP Recovery. .
Sent from my GT-I9195L using Tapatalk
rolo143 said:
Lol... I don't have Knox security warnings, I deleted all Knox files. The message in yellow says "Set Warranty Bit: kernel" on Samsung boot logo, but that's it. I think is nothing to worry about, but if I can get rid of it, that would be great. It appeared after I installed TWRP Recovery. .
Sent from my GT-I9195L using Tapatalk
Click to expand...
Click to collapse
Yeah, that's still that blasted Knox, doing it's "Set Warranty Bit: kernel", you are tripped at 0x1 with an eFuse.
I was going to play with TWRP, I think I'll retain CWN for a bit. It still might be worth a shot to go back to square one with the baseline Arco68-CWN setup with 1.8 SU and at least see if the warning goes away. Or have you already?
(I'm kind of tempted to duplicate your setup, I'm curious about this.) Can you clarify? Are you on 4.3, or did I misunderstand and you're on 4.2.2 ?
I'm on 4.2.2.. I stupidly updated my phone via OTA, because I thought it would have 4.3 but surprise! I got a Knox firmware and I can't go back. And I think TWRP or CWM it doesn't matter, I think when you flash any recovery that isn't stock, the warning activates..
Sent from my GT-I9195L using Tapatalk
rolo143 said:
I'm on 4.2.2.. I stupidly updated my phone via OTA, because I thought it would have 4.3 but surprise! I got a Knox firmware and I can't go back. And I think TWRP or CWM it doesn't matter, I think when you flash any recovery that isn't stock, the warning activates..
Sent from my GT-I9195L using Tapatalk
Click to expand...
Click to collapse
The OTA explains your problem. 4.2.2 is fine, the below root process deals with Knox.
Re-do with the Arco68 root from square one. Stick with CWM for now, TWRP may not be fully stable with the S4 Mini at this time, CWM is. Using it removes any question.
http://forum.xda-developers.com/showthread.php?t=2364980
(make sure to click the Arco68 thanks)
Got the same message in my galaxy 4 mini
Hi guys! First of all consider I'm a graphic designer and have no idea about rooting and getting in phones softwares hahaha, but I have so bad luck that after purchising my Samsung S4 mini (GT i9195) on a trip in France about a month ago and trying to use it here in Buenos Aires with a local SIM, I got Samsung's Region Lock message pop up. I gave it to a friend from work and not only he couldn't fix it, but also returned it to me with this tiny annoying message in the initial animation that says "Warranty bit: kernel" (really bad caption attached).
So here I am, trying to fix the region lock and also the Warranty Bit message. The most important thing is the region lock, of course, but now I think my friend rooting the phone caused this message to appear.
The thing is, can I fix both things? In order to fix the region lock I need to have the device rooted, and, in the other hand, the root left this message.
Can anyone help me? I swear I've tried to understand it on my own but there are so many thecnical vocabulary I just don't get.
Couldn't thank you enough!
Hope you are all doing great,
best
Laurie.
Laurie, if you don't want to see that yellow message you have to install stock ROM with Odin, your warranty still voided.
have you tried region lock away I'm not sure if it works but it won't hurt trying.
sent from my i9192 with CM11 by sekil
set warranty bit kernel
I have galaxy s5 sm900f but i think every phone is the same text proplem . I try many difference roms and only one work without that text is alliance rom. Every others roms always come text kernel is not seandroid enforcing and set warranty bit. I dont know what is difference that rom i use philz recovery.
Also where is the best place to get the stock ROM files so we can use Odin and load them? Thanks for all your help!
Sammobile dot com
Mine Note II is SGH-I317M with baseband version of I317MVLUCMK5 and KNOX.
I have tried CF-Auto-Root and Root SuperSU but weren't able to root my note II.
I have tried using different version of Odin, reinstalled the USB driver and tried using philz touch and cwm6 root to backup and root.
Nothing worked........Can't even start SuperSU.....
KNOX keep giving me security notice "An attempt to access a secure area on your device without authorisation has been blocked."
I also tried an updated Superuser. Still nothing worked....
Any idea anyone?
Thank you very much.
Stewegg said:
Mine Note II is SGH-I317M with baseband version of I317MVLUCMK5 and KNOX.
I have tried CF-Auto-Root and Root SuperSU but weren't able to root my note II.
I have tried using different version of Odin, reinstalled the USB driver and tried using philz touch and cwm6 root to backup and root.
Nothing worked........Can't even start SuperSU.....
KNOX keep giving me security notice "An attempt to access a secure area on your device without authorisation has been blocked."
I also tried an updated Superuser. Still nothing worked....
Any idea anyone?
Thank you very much.
Click to expand...
Click to collapse
You need to disable knox first
http://forum.xda-developers.com/showthread.php?p=49860203
Stewegg said:
Can't even start SuperSU
Click to expand...
Click to collapse
This is really weird, when I did this to my SGH-I747/M it was updated to stock 4.3 so it had KNOX and I got the same message as you but to disable it, all I did was open SuperSU and it prompts me to disable KNOX and then it's "fully" rooted and I could install a custom recovery after that.
I know it worked on the S3 because it's currently rooted running a custom ROM. Are you using the right version of Odin? I was trying to use 1.85 I think it was and it wasn't working at first, I tried 3.09 and it worked like a dream.
Did you remember to go into the Security Settings and turn off Reactivation Lock? I know this can play a factor when rooting with KNOX.
Also, KNOX never goes away, even though I'm running an AOSP ROM now on the S3, it still shows the KNOX counter with 0x1, even with it disabled. I can also not get any ROM's lower then 4.3 to work anymore so I can no longer run RootBox 4.2.2 on the S3.
I'm not sure if it's just me, or just my phone, but since that KNOX update was already on it when I got the phone used, it will not let me go to any ROM's lower then 4.3
VeeDaub said:
This is really weird, when I did this to my SGH-I747/M it was updated to stock 4.3 so it had KNOX and I got the same message as you but to disable it, all I did was open SuperSU and it prompts me to disable KNOX and then it's "fully" rooted and I could install a custom recovery after that.
I know it worked on the S3 because it's currently rooted running a custom ROM. Are you using the right version of Odin? I was trying to use 1.85 I think it was and it wasn't working at first, I tried 3.09 and it worked like a dream.
Did you remember to go into the Security Settings and turn off Reactivation Lock? I know this can play a factor when rooting with KNOX.
Also, KNOX never goes away, even though I'm running an AOSP ROM now on the S3, it still shows the KNOX counter with 0x1, even with it disabled. I can also not get any ROM's lower then 4.3 to work anymore so I can no longer run RootBox 4.2.2 on the S3.
I'm not sure if it's just me, or just my phone, but since that KNOX update was already on it when I got the phone used, it will not let me go to any ROM's lower then 4.3
Click to expand...
Click to collapse
Where is the Reactivation Lock located?
I can not find it in the Security Settings.
mrevankyle said:
You need to disable knox first
http://forum.xda-developers.com/showthread.php?p=49860203
Click to expand...
Click to collapse
I was following the steps in the post you have posted.
When I tried to flash the DrKetan_MultiTool_AdvanceV5, it gives me an error: E:signature verification failed. and stopped the flash.
Any idea?
Stewegg said:
I was following the steps in the post you have posted.
When I tried to flash the DrKetan_MultiTool_AdvanceV5, it gives me an error: E:signature verification failed. and stopped the flash.
Any idea?
Click to expand...
Click to collapse
hey man i have the same phone as you, just found an easy way to root it after struggling. Just updated to Stock 4.3 Bell Firmware using odin, completely fresh phone.
How to root it:
1. Flash philz recovery in odin "philz_touch_6.19.3-t0lteatt.tar.md5" (Download mode= Vol Down + Home + Power)
2. Reboot back into android once
3. Power off phone
4. Boot into recovery (Vol Up + Home + Power)
5. Goto philz settings->Reroot rom (or something to that effect)
6. Recovery will tell you done, and to reboot and install SuperSU from Play Store
7. Reboot download and install SuperSU from Play Store
8. Open SuperSU it will immediately ask if you would like to disable Knox.. say yes
9. Done
Link to philz recovery tar for our phone i317M
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/t0lteatt/philz_touch_6.19.3-t0lteatt.tar.md5
Does this work?
My wife's Rogers note2 is bone stock running I317MVLUCMK5.
She is paranoid about Knox and possibly killing her phone.
She wants me to get it rooted, but I'm struggling to find a clear cut answer.
Also, it would be better if anyone knows how to (if possible) downgrade to 4.1.2 and start from there... As I know how to do that one like the back of my hand.
Sent from my SGH-I317 using Tapatalk
Stewegg said:
Mine Note II is SGH-I317M with baseband version of I317MVLUCMK5 and KNOX.
I have tried CF-Auto-Root and Root SuperSU but weren't able to root my note II.
I have tried using different version of Odin, reinstalled the USB driver and tried using philz touch and cwm6 root to backup and root.
Nothing worked........Can't even start SuperSU.....
KNOX keep giving me security notice "An attempt to access a secure area on your device without authorisation has been blocked."
I also tried an updated Superuser. Still nothing worked....
Any idea anyone?
Thank you very much.
Click to expand...
Click to collapse
Simple. First get the root. Like the su binary and stuff. once you are rooted get suersu. What I mean by first get root is literally get root through a program or something. After this you will have root but you wont have root access. So get supersu now and launch the app. It will ask to update your su binary. Say yes. then the thing will say something about knox then ask you if you want to try to disable knox. Tap yes and knox should be disabled and your su binary should be updated and working.
I'm exactly in the middle of nowhere .. Try to root with CF method. After the first try and reboot. I got the knox alert "unauthorized, bla, bla" the thing is that I can't get the full root or return to stock. Also when I tried to install knox in order to Uninstaller it, I can't. My phone is not allowed to use knox any more... I already tried to download Su and update it in order to disable knox with no success.... Stupid knox and stupid 4.3:crying:
My phone is I317M Rogers, it run stock 4.3. I followed this guide, http://forum.xda-developers.com/showthread.php?t=2618261 rooted success.
Eun-Hjzjined said:
Does this work?
My wife's Rogers note2 is bone stock running I317MVLUCMK5.
She is paranoid about Knox and possibly killing her phone.
She wants me to get it rooted, but I'm struggling to find a clear cut answer.
Also, it would be better if anyone knows how to (if possible) downgrade to 4.1.2 and start from there... As I know how to do that one like the back of my hand.
Sent from my SGH-I317 using Tapatalk
Click to expand...
Click to collapse
ifentanez said:
I'm exactly in the middle of nowhere .. Try to root with CF method. After the first try and reboot. I got the knox alert "unauthorized, bla, bla" the thing is that I can't get the full root or return to stock. Also when I tried to install knox in order to Uninstaller it, I can't. My phone is not allowed to use knox any more... I already tried to download Su and update it in order to disable knox with no success.... Stupid knox and stupid 4.3:crying:
Click to expand...
Click to collapse
koodiifin said:
hey man i have the same phone as you, just found an easy way to root it after struggling. Just updated to Stock 4.3 Bell Firmware using odin, completely fresh phone.
How to root it:
1. Flash philz recovery in odin "philz_touch_6.19.3-t0lteatt.tar.md5" (Download mode= Vol Down + Home + Power)
2. Reboot back into android once
3. Power off phone
4. Boot into recovery (Vol Up + Home + Power)
5. Goto philz settings->Reroot rom (or something to that effect)
6. Recovery will tell you done, and to reboot and install SuperSU from Play Store
7. Reboot download and install SuperSU from Play Store
8. Open SuperSU it will immediately ask if you would like to disable Knox.. say yes
9. Done
......
Click to expand...
Click to collapse
koodiifin's way worked perfectly!
Thank you koodiifin!
So 2013 I rooted my phone, my Android version is still 4.1.2 Jelly Bean.
I only rooted, I never installed a custom ROM or anything,
My phone says "modified" and if I try to update it says "Your device have been modified".
So I went to the SuperSU app and pressed "Unroot", My phone was no longer rooted (I believe? Some apps said my phone wasen't rooted).
Yet I coulden't update my phone because it was still "Modified", so I Factory reset it and it still says its modified!
Can someone please help me?
solution
iTriforce said:
So 2013 I rooted my phone, my Android version is still 4.1.2 Jelly Bean.
I only rooted, I never installed a custom ROM or anything,
My phone says "modified" and if I try to update it says "Your device have been modified".
So I went to the SuperSU app and pressed "Unroot", My phone was no longer rooted (I believe? Some apps said my phone wasen't rooted).
Yet I coulden't update my phone because it was still "Modified", so I Factory reset it and it still says its modified!
Can someone please help me?
Click to expand...
Click to collapse
1.Open the Triangle Away app, confirm your Galaxy Note 2 model (in my case a GT-N7100)
2. Next, it will ask you to download an add-on.
3.Next, choose “Reset flash counter”.
4.Your Note 2 will reboot and hit Volume Up button to reset binary counter
if u want link for app pm me .
wanipravin19 said:
1.Open the Triangle Away app, confirm your Galaxy Note 2 model (in my case a GT-N7100)
2. Next, it will ask you to download an add-on.
3.Next, choose “Reset flash counter”.
4.Your Note 2 will reboot and hit Volume Up button to reset binary counter
if u want link for app pm me .
Click to expand...
Click to collapse
Thank you, I tried to use the app but it didn't work, so I manually installed the 4.4.2 kitkat and my phone works great and is now rooted again!
how did you manually install 4.4.2 ?
I have the same problem, android version 4.3 unrooted
I just want to update to 4.4.2 without root but it says your device is modified, help pls
sadecedeniz said:
how did you manually install 4.4.2 ?
I have the same problem, android version 4.3 unrooted
I just want to update to 4.4.2 without root but it says your device is modified, help pls
Click to expand...
Click to collapse
Flash using Odin.