Hey all. I have the same issue as this guy. Tried to root with Kingo Root, didn't work. Afterwards I rooted with Odin and that worked just fine of course. I have unrooted my phone again and I can't seem to change the kernel version. It's changed to 3.0.31-2788594 [email protected] #1. Even after unroot (with Odin and stock firmware from SamMobile) the kernel version stays 3.0.31-2788594 [email protected] #1.
System is stable @ stock rom now and in download mode it says 0 counts for custom binary download. So no issues there, I just wish to have the kernel changed again in my phone's settings. Anybody can point me a direction how to 'fix' this?
Anybody knows how to change the kernelversion back to something like [email protected]?
Related
So my galaxy tab went kapoot and I want to make sure all signs of rooting are non-existant. So i got a clean flash on there and superuser is gone.
When I download something like titanium backup it is unable to obtain root access so does this mean all sign of rooting are gone?
under kernel it says 2.6.32.9 [email protected]#3
Littleazn248 said:
under kernel it says 2.6.32.9 [email protected]#3
Click to expand...
Click to collapse
Yes, that means busybox and the other su files are most likely gone now, however "[email protected]" doesn't sound like the stock Sammy kernel, you should flash the stock ROM to have the stock kernel instead. In the market dl root checker, and it tells you if the device has root at all.
https://market.android.com/details?id=com.joeykrim.rootcheck&feature=search_result
How do i get the stock kernel on there?
Is this kernel stock
please help
Help me please
Have you ever flashed your device with odin or kies? If so you'll need to flash it back to stock using one of those programs. Just download the stock ROM online and flash it back. The only downside is that apparently some devices record the number of times a ROM has been flashed.
I have a Galaxy Ace...which came with Android 2.2
My partner rooted it and everything was fine. At the same time he upgraded to Gingerbread 2.3.3
But a couple of weeks ago he upgraded it to Gingerbread 2.3.6....and now it says it is root...but it doesn't have access to the root only apps....and it doesn't show the Superuser app that is needed.
Somehow it seems to be in some sort of limbo between unrooted and rooted.
I am well confused. Can anyone out there help please.
It looks like that the latest GB ROM used for the upgrade does not have the root.
You can add root to it. Before you do that, check by using terminal app with su command if the phone is rooted or not.
Sent from my Amazon Kindle Fire using Tapatalk
Thank you....it sounds a bit technical.
I will get my partner to read it in a while.
Although it sounded like I KNOW what I am on about...I am, in fact, a complete beginner when it comes to Android.
Updating from kies or from odin will make your phone unroot again. U need to reroot.
Sent from your phone
julado said:
I have a Galaxy Ace...which came with Android 2.2
My partner rooted it and everything was fine. At the same time he upgraded to Gingerbread 2.3.3
But a couple of weeks ago he upgraded it to Gingerbread 2.3.6....and now it says it is root...but it doesn't have access to the root only apps....and it doesn't show the Superuser app that is needed.
Somehow it seems to be in some sort of limbo between unrooted and rooted.
I am well confused. Can anyone out there help please.
Click to expand...
Click to collapse
a stock rom update resets your phone to most basic version..all things gone root,,clockworkmod etcc.....
u need to re-root follow this thread---
http://forum.xda-developers.com/showthread.php?t=1034145
happy rooting..
Root issue on Ace...
Hello all! I am Julado's partner. I had better explain what this is about in more detail here...
I took the original OS (Froyo) and updated it to Gingerbread (2.3.3) via Kies, I then used SOC to root it using ChainFire method - then installed and performed a TB back up. ALL Good - a few weeks later - I flashed an update using Odin to get 2.3.6 and an updated version of CF's kernel. At THAT point, CWM recovery had root access - but fully booted GingerBread had no SU app or returned root status via test command (both using a script and terminal). Sys info in settings shows 2.3.6 and ROOTED kernel image, but NO ROOT ACCESS is there in GB ~ Just in CWM Recovery.
I have re-flashed the CF kernel a few times and STILL have the same situation. I cannot understand why CWM has ROOT access but FULL 2.3.6 system doesn't.
Can anyone offer my any help please? Or possibly point out the blindingly obvious if I have missed what's clearly staring me in the face! Thanks.
So u already flashed ketut's cfroot kernel and still doesn't have root access in the rom? Thats weird.
Btw kernel name in system settings even if it said root doesnt mean your rooted. thats the build host of the kernel compiler.
Sent from your phone
When you are in GB, you can't root your ace via SOC. It will look success, but actually it's not. You have to root it using update.zip and flash via recovery. Just find it by googling.
Sent from my GT-S5830 using Tapatalk
an0nym0us_ said:
So u already flashed ketut's cfroot kernel and still doesn't have root access in the rom? Thats weird.
Btw kernel name in system settings even if it said root doesnt mean your rooted. thats the build host of the kernel compiler.
Sent from your phone
Click to expand...
Click to collapse
Thanks for the speedy reply!
I understand that the settings name is from build compiler. I have tested for root access with terminal and various apps (even tried downloading & installing SU app myself!!) - but don't understand why CWM DOES have root - but full OS doesn't!
I am truly baffled ATM!
mikeybaby72 said:
Hello all! I am Julado's partner. I had better explain what this is about in more detail here...
I took the original OS (Froyo) and updated it to Gingerbread (2.3.3) via Kies, I then used SOC to root it using ChainFire method - then installed and performed a TB back up. ALL Good - a few weeks later - I flashed an update using Odin to get 2.3.6 and an updated version of CF's kernel. At THAT point, CWM recovery had root access - but fully booted GingerBread had no SU app or returned root status via test command (both using a script and terminal). Sys info in settings shows 2.3.6 and ROOTED kernel image, but NO ROOT ACCESS is there in GB ~ Just in CWM Recovery.
I have re-flashed the CF kernel a few times and STILL have the same situation. I cannot understand why CWM has ROOT access but FULL 2.3.6 system doesn't.
Can anyone offer my any help please? Or possibly point out the blindingly obvious if I have missed what's clearly staring me in the face! Thanks.
Click to expand...
Click to collapse
Sits and grins at screen.....having absolutely NO idea what any of this post means
Would anyone like me to KNIT them an Android
hallidafykzir said:
When you are in GB, you can't root your ace via SOC. It will look success, but actually it's not. You have to root it using update.zip and flash via recovery. Just find it by googling.
Sent from my GT-S5830 using Tapatalk
Click to expand...
Click to collapse
I did get FULL root access after using SOC to root (chainfire method) GB - I rooted 2.3.3 with SOC, NO PROBLEMS! - THEN made TB (needs root) successfully. It was only after using Odin to flash 2.3.6 that SOC root resulted in the current quasi-rooted state.
I have tried re-flashing CF kernel both using Odin AND via CWM (update.zip) method - Neither worked = STILL BAFFLED???!
Hello!
First of all, thank you - Condi - for this great tool.
Unfortunately I managed it to flash a downloaded OTA (signed-nbx03_007-ota-11000.014).
Right now, the device is rooted, has Android 3.2 and Kernel Build10#1 on it.
I was able to disable update notifications with your tool, but everything else is not working right now because of the common Build10 Problem.
Is there a way to get back to stock, even without root but @ 3.2.1 and the upcoming 4.0.3?
Thanks in advance!
Sorry, but this it not really true. The build#10 problem concerns only 3.2.1r2 version. Otherwise you would be not able to root your device with version 3.2.
Could you explain what you mean with "but everything else is not working right now because of the common Build10 Problem.", please?
Regarding your question .. it is really easy to go back to stock .. switch update notifivcation "on" (maybe you have to restore origional build.prop) and install the update version 3.2.1R2 ... done.
Its a bit difficult to explain, but right now I have 3.2 installed.
After switching the update notification to ON, I get the message to update to 3.2 again (!?)
Right now, I have root access in my device. The tool is able to switch notification on/off, but re-root or another step (6-8) is not possible for me.
I get the error that is typical for Build#10 in the script.
I need help from you guys. I have a tmobile galaxy s4, I was rooted with cm11 4.4.2 and I tried to unroot to stock with odin and a firmware, but I fail and got a soft brick the first time. I download different odins and firmwares and finally got it to work, PASS I have stock 4.2.2 m919uvuemk2. but when it restarted I tried to delete wipe cache partition and reboot like it ask me to but it didn't work. Every time I reboot phone it gives me a message before it turns onit says kernel is not seandroid enforcing and set warranty bit kernel. My phone works fine except the wifi, it doesn't turn on. the devise status still say CUSTOM and I can not software update it says your devise your devise has been modify. I checked for root access and there is none. what can I do to fix this problems, should I reroot and use triangle away to delete the BINARY AND KNOX messages and after try to use a 4.3 firmware instead of 4.2.2. I want to have a complete stock phone that I can do OTA updates. Can some one please give the steps and point me in the right direction so I can take care of this problems. Thank You...
Flashed stock Lollipop 5.1.1 ROM using ODIN, Device binary & status are CUSTOM? Help!
Hey guys! First time poster!
A few months back, I tried using CF-Auto root in order to gain root access on my phone, but I flashed something incorrectly and I was never able to get root working correctly. I know because of this, I tripped KNOX, and whenever I rebooted, there was a "Set Warranty Bit: Kernel" at the top of the device.
Due to the recent Marshmallow 6.0.1 upgrade, I want to unroot and get stock firmware, so I decided to do some research and go ahead and try to flash the stock G900T 5.1.1 FOJ4 firmware (tar.md5 file), so I can get my ability to update my phone via OTA updates. I looked up my matching firmware (FOJ4) through Android File Host and then unzipped it to my desktop.
I followed a guide and used ODIN 3.10.7 to flash the stock firmware file onto my phone. I also wiped cache/ factory reset before and after flashing the stock image.
Everything went well and I no longer see the "Set Warranty Bit: Kernel" when I boot. The problem I have is that when I go into download mode, the CURRENT BINARY and SYSTEM STATUS are both CUSTOM.
I was under the impression as long as you flash a stock firmware to your device, you will unroot and your device will be official, and then you'll be able to do OTA updates. Maybe its because I have KNOX tripped? Maybe can someone clarify that for me?
My main questions/concerns are:
1.) Is there anyway to make my device status/binary as OFFICIAL, in order to regain OTA updates?
2.) If I want to download the 6.0.1 Marshmallow update, should I just try through KIES or downloading the tar.md5 file to flashing via ODIN like I did with stock?
3.) Will there be any risk of bricking since my device is still "custom", if I go the above route?
4.) As a last ditch effort, should I just try downloading a different stock Lollipop firmware, and try flashing with ODIN again?
5.) What does this sub think of Marshmallow 6.0.1 update? Is it worth it?
Thank you guys in advance! Hope you have an awesome day!
@Root_S5_Please
#2 with Odin will work and is the correct way to go, #3 will not happen as long as you use Odin, you can't untrip Knox but that's OK since it doesn't have any effect on functionality. #4 is unnecessary and won't do anything to help. Someone else will have to answer #5, I Odined the update and immediately went back to CM13