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.
Related
Hi all,
Excuse the noobness but trying to get my head straight before I dive into rooting and flashing custom ROMS
I currently have a Telstra Australia S2 on kernel DVKF4. My aim is to root and flash Litening ROM
I think to flash Litening ROM I do not have to Root I can just go ahead and flash it however I would like to take a backup of my current firmware first, if I go ahead an install Litening my original Telstra will be gone and wont be able to back it up now?
If I understand this correctly I first need to root and I need to flash an insecure ROM. Now currently the DVKF4 insecure ROM hasnt been uploaded yet... Can I use any old kernel to get root access?
I know if I do this I will get the yellow warning label but will this even matter since after I gain root I am going to flash litening anyway so that will replace the kernel anyway with the litening one and I will not get the yellow warning. Correct?
Anyhoo I wanted to backup current Telstra firmware in case I need to flash it back for warranty. Also I would have to unroot it. So in order to do this I would firstly restore the backup made which would flash back the original telstra ROM but the phone will still be rooted?
Since I made the backup with the 'any old' kernel to get root does that when I restore I am going to have that kernel still on phone and giving me yellow warning?
OK so I would have to flash back the correct DVKF4 kernel to get rid of it again. So I would have to flash back the original (secure) kernel to get rid of this and user superoneclick to unroot and then its back to its original state? (besides the download counter of unsigned ROMS which can be reset with jig)
Also does the yellow warning come up even if you use an insecure kernel which is the same version your firmware needs?
I thought it's the kernel which gives the root access but it's not is it? It just allows superoneclick to install the superuser files etc?
Thanks!
icanfly77 said:
Hi all,
Excuse the noobness but trying to get my head straight before I dive into rooting and flashing custom ROMS
I currently have a Telstra Australia S2 on kernel DVKF4. My aim is to root and flash Litening ROM
I think to flash Litening ROM I do not have to Root I can just go ahead and flash it however I would like to take a backup of my current firmware first, if I go ahead an install Litening my original Telstra will be gone and wont be able to back it up now?
True but you may find copy on Branded roms post dev section or use vanilla Samsung stock rom .
If I understand this correctly I first need to root and I need to flash an insecure ROM. Now currently the DVKF4 insecure ROM hasnt been uploaded yet... Can I use any old kernel to get root access?
Depends upon what the instructions say but generally as near to possible as your rom .
I know if I do this I will get the yellow warning label but will this even matter since after I gain root I am going to flash litening anyway so that will replace the kernel anyway with the litening one and I will not get the yellow warning. Correct?
Incorrect you will need the USB recovery jig to remove the warning and reset the custom rom counter to zero the easy way .
Anyhoo I wanted to backup current Telstra firmware in case I need to flash it back for warranty. Also I would have to unroot it. So in order to do this I would firstly restore the backup made which would flash back the original telstra ROM but the phone will still be rooted?
A backup via CWM of a phone will restore what you backup .
To restore unrooted you will need to save unrooted in the first instance .
Original rom or branded rom flashed via Odin will remove root .
I thought it's the kernel which gives the root access
Yes if you use the usual method no if you use another method .
Root & CWM kernel.
http://forum.xda-developers.com/showthread.php?t=1103399
jje
Click to expand...
Click to collapse
JJEgan said:
icanfly77 said:
A backup via CWM of a phone will restore what you backup .
To restore unrooted you will need to save unrooted in the first instance .
Click to expand...
Click to collapse
Hey thanks but how do I make a backup of the unrooted current carrier ROM? Don't I first need to gain root access to be able to run CWM and make the backup?
Or is there a way I can go into recovery now with the device currently unrooted and stock carrier ROM and make a backup?
Thanks
Click to expand...
Click to collapse
icanfly77 said:
Hey thanks but how do I make a backup of the unrooted current carrier ROM? Don't I first need to gain root access to be able to run CWM and make the backup?
Click to expand...
Click to collapse
As was pointed out above by JJEgan, either wait for the Telstra carrier branded firmware to hit this thread.
Or you can try the root/unroot method as described here. Good luck
mrxd said:
As was pointed out above by JJEgan, either wait for the Telstra carrier branded firmware to hit this thread.
Or you can try the root/unroot method as described here. Good luck
Click to expand...
Click to collapse
yeah thanks I get that part it's just that he mentioned if I want back a backup of an unrooted rom I need to make the backup while unrooted but I did not think this was possible since you need to root first before being able to backup?
Just after some clarification about that.. Thanks
I have a sgs2 and rooted it with odin oneclick... now i cant upgrade to the latest firmware.. i think it's 2.3.4 (or if there is an even newer version out now) since it's rooted, can anyone help me out how to do this upgrade (to latest firmware) the easy way so i dont loose anything on the phone.
My current kernel is 2.6.35.7-I9100XWKDD-CL161513.........
Build number gingerbread xwke2 if this info helps..
Im would be very happy if someone would be so kind and help me with this, thanks in advance for any help.
Can you not use kies? Should still be able to use it rooted.
Root has nothing to do with KIES upgrades... If KIES says "This is the latest firmware" then it is indeed the latest firmware for your country/code... 2.3.4 is not yet released officially to many countries and country codes yet...
If you flashed somewhat BETA or custom ROM you get error like "You cannot upgrade this" or something similiar to that...
I get a error failure report, and to try using kies or something else. I tried doing the upgrade on the phone directly, checking for updates and downloading and installing, but everytime i get this error failure report
My phone is unlocked, and now i flashed it with original kernel to remove that annoying ! mark in bootup, so now i dont have a unsecure kernel any longer... but even with this original kernel now i couldnt upgrade the firmware using only the phone
Is it a must to use kies ? if so i will try it, cause i have a working kies on one computer. I just thought i could do it directly on the phone under checking for updates, but that way dont work for me.
So it does not matter if my phone is rooted when i want to update my firmware to newer like 2.3.4 or newer ?
You can just grab a stock rom from the thread in original dev and flash it via odin, kg6 is a good 2.3.4 rom, kh1 and 3 are a bit unknown at the moment.
Your best bet is to flash cf root on your phone, take a nandroid backup via it, use titanium backup or equivalent for your user apps and user app data (and some system data, as shown in green in the app) and do a full wipe, flash the new stock, and restore using titanium or equivalent.
The nandroid is a snapshot of your phone at the time, which will allow you to roll back to a known good point at any time.
Sent from my GT-I9100 using XDA Premium App
No rooting wont effect kies. Try Kies first, See if indeed there is a update available to you. Like the previous poster said 2.3.4 is not available in all countries yet...
If your desperate to update you can use odin to upgrade the firmware instead..but that will wipe all data on your phone, so you will have to use Titatium Backup first. But if I were you I'd just use kies, and wait for the official update in your country.
Hmm if you can't update with KIES and you don't want to wipe then your best bet is to flash with ODIN with one of the frankenstien firmwares provided at one of the threads in the original development forum.
It did worked using kies on my computer, but it's still 2.3.3... guess it updated something minor then.
Thanks everyone for your help !
Does anyone know if i can remove the question mark in bootup and still be able to overclock the phone ?
boarne71 said:
It did worked using kies on my computer, but it's still 2.3.3... guess it updated something minor then.
Updates are as and when the provider of the phone updates the firmware .
They do not use all Samsung updates and often push them out much later .
Does anyone know if i can remove the question mark in bootup and still be able to overclock the phone
Yes via the instructions in root thread
Root + CWM .
http://forum.xda-developers.com/showthread.php?t=1103399
Or by using the USB jig .
jje
Click to expand...
Click to collapse
I know after root i can flash with the original, but that seams to remove the possibility to overclock the device but the root are still there after flashing with original.
boarne71 said:
I know after root i can flash with the original, but that seams to remove the possibility to overclock the device but the root are still there after flashing with original.
Click to expand...
Click to collapse
No you flash root then flash original wipes root .
You would be better to find an overclocking rom and work from the instructions there .
jje
It's flashing the kernel im talking about. When rooting a phone you flash the phone with a unsecure kernel, then after it's rooted you can flash it back to original kernel so the "!" mark wont show in bootup.
Now i wounder how to do that and still keep the overclocking feature, anyone know how to do that ?
boarne71 said:
It's flashing the kernel im talking about. When rooting a phone you flash the phone with a unsecure kernel, then after it's rooted you can flash it back to original kernel so the "!" mark wont show in bootup.
Or ue the USB jig .
Now i wounder how to do that and still keep the overclocking feature, anyone know how to do that
If the overclocking features are part of the kernel then flashing original kernel replaces the kernel that has the overclocking features .
jje
Click to expand...
Click to collapse
Yes that was what o thought Thanks everyone so much for all your help!!
I guess i just have to live with this "!" mark on bootup, no big deal
Look at chainfires post number 2 on this thread to remove triangle and still keep insecure kernal here
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, I am a complete noob with android software and these forum websites.
I bought a the standard Galaxy S2 GT-I9100 a few months ago, rooted it but since then I still have no root access. This is the first time I've signed up for any website to ask for help, because I cant find any solution to fixing it.
I followed a simple guide, which instructed to use odin, and the Siyah kernal. It said the root was successful and superuser + CWM was installed.
On the Superuser Binary Updater, its says the latest version is 3.1.1 but I only have 3.0.3.2. When I try update, it says "Gaining root access... fail!"
The 'Root Checker Basic' app tells me "This device does not have proper root access"
I was suggested to use OneClickRoot. I try it, and it tells me my device is already rooted.
I am using:
Android version 4.1.2
Baseband version I9100XXLS8
Kernal version 3.0.31 siyah-s2-v6.0b5
Please help me gain root access without wiping the data off my phone. I dont want to modify the way the system looks or works, all I want is root access. Sorry if this posted in the wrong place, this site is confusing for me
Flash Siyah again (through CWRecovery if the flash was successful enough to install it, if not through Odin again).
MistahBungle said:
Flash Siyah again (through CWRecovery if the flash was successful enough to install it, if not through Odin again).
Click to expand...
Click to collapse
I've tried doing it again through Odin and still no change. Is it possible that I'm doing it wrong? After many searches I see there's multiple ways of rooting the device..
Can you please link me to correct instructions for using Odin? Just to be sure I'm doing it right
Siyah tar file in PDA section of Odin, click start. I don't know why people think this sort of thing is complicated when it's really very simple.
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]?