[04.12.2012][ICS/JB]Universal Rooting for most phones, Any ROM, now with CWM6 - Galaxy S II Original Android Development
Root your ICS/JB phone S2 + Samsung + not Samsung phones - No more waiting for custom kernels
This topic provides universal root methods to bypass the use of custom kernels. I took the time to write it as I was tired from waiting for a Dev to publish a custom kernel for the last firmware released.
I will try here to reference most threads and ways to root your phone. Some methods will let you root as soon as you get the new ROM, no more waiting for some dev to release a kernel for you.
I will not list here custom kernels that come with root, you can find them in other threads.
As a general rule, do not forget to take extra precautions when you flash anything: ALWAYS DO A NANDROID BACKUP IN CWM
Method 1 - Recommended
Push superuser + Busybox (Now v1.20.2 from Linus Yang) in recovery
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Now, on the i9100 and some other phones (N7000...), you can flash the attached signed zip files in stock recovery, no more need to CWM.
A BIG BIG THANK YOU TO Chainfire for his support that made it possible and to Entropy512 who pushed me to look for a fix
Attached is the CWM Recovery 4.x non touch version, confirmed safe for wiping. It will not superbrick your phone
>>>>>> Now it is even getting greater with attached Clockworkmod v6.0.1.2 !!!! <<<<<<
>>>>>> Also probably safe from brickbug <<<<<<
Pros
Universal and will probably work on any ICS phone, if you have a CWM image. No longer wait for a modded kernel
On the i9100 and some other phones (N7000...), you can now even root from the stock recovery, no need to the cwm image
No PC needed, only an android device and the zip files that you download to your sd card
Fully reversible unroot without PC needed
No Yellow Triangle (Only for phones with a zip CWM image)
No custom counter increased (Only for phones with a zip CWM image)
Only copies superuser +/- busybox, nothing else is touched, neither /data nor the kernel
No brick risk while flashing cwm even if things go wrong as it will be always overwritten by stock recovery after a reboot
Click to expand...
Click to collapse
Cons
None since I switched to the CWM4 and CWM6 recoveries (no more superbrick risks under 4.0.4 ICS kernels, only CWM5.x was affected)
Click to expand...
Click to collapse
Special notes about busybox
The zip files attached in this post install busybox only in /system/xbin. I do not put any symlink in /system/bin
If you previously installed other versions of busybox, I advise to run Busybox Uninstaller v1.0 zip in the thread dedicated to it here: http://forum.xda-developers.com/showthread.php?t=1853419
It will clean any orphan symlink that could be left from a previous install. After that, install busybox from any of the attached files in this post
The uninstaller in this post, only removes busybox package from /system/xbin. I do not delete any package put in bin, as it is assumed it was put there by another program, not my script. It will not remove any symlink either. So, run the Busybox Uninstaller v1.0 for that
Click to expand...
Click to collapse
This method was first inspired from Rachmat3 thread here and Chainfire script here (do not forget to thank them). I modified it to work in stock recovery, enhanced script, include Chainfire superSU last version + BusyBox last binary. I also keep a ChainsDD superuser version.
Instructions
For phones affected by the superbrick bug (i9100, N7000) and that has a stock recovery accepting update.zip files (most phones with a temporary cwm.zip file at Clockworkmod site:
You can flash the attached files directly in stock recovery 3e, no need to cwm:
Download the root file:
- Root_SuperSU.0.96.Only-signed.zip for Chainfire SuperSU (the one that comes with CF_Root) without busybox.- Root_SuperSU.0.96-FreeSpace.zip for Chainfire SuperSU without busybox (use only if you have issues with previous one, usually for phones having a /system partition with 0 free space).- Root_SuperSU.0.96-Busybox.1.20.2-S2-signed.zip to install superSU + busybox v1.20.2 from Linus Yang.- Root_Superuser_3.1.3_Busybox_1.20.2-Update1-signed.zip if you prefer the classic ChainsDD superuser + Busybox from Linus Yang.- Root_Busybox_1.20.2_Only_XXX.zip to install only Busybox from Linus Yang.
I advise Chainfire SuperSU for 2 reasons: it lets you unroot from within superSU application and it lets you migrate to ChainsDD superuser if you like later
.
Copy the Root_XXX.zip file you downloaded to externalsd card
Boot into stock recovery (volume up+home+power), and select "apply update from external storage". Now select the Root_XXX.zip file downloaded above and you are rooted
To unroot, do the above steps and replace the file Root_XXX.zip by the attached Unroot_SuperUser-Busybox-Uninstaller-Update2-signed.zip. It will delete superuser, su and busybox packages.
For a complete removal of busybox, look here at my Busybox Uninstaller which will remove ALL busybox symlinks (over 600 files depending on installers used before):
http://forum.xda-developers.com/showthread.php?t=1853419
To get temporary cwm (to make nandroid backups...) or if stock recovery gives you a signature error, follow the next more universal steps.
Click to expand...
Click to collapse
.
.
For most (if not all?) ICS phones having a CWM image at Clockworkmod site:
Download attached cwm-touch-6.0.x.x-i9100.zip for the i9100 Galaxy S2. This is the touch version but it also works with volume up/down keys and power button to select menu.
CWM6 is now thought to be probably safe for wipe, no superbrick risks under ICS 4.0.4: read more here
I also attached the cwm6 non touch version and the recovery-clockwork-4.0.1.5-galaxys2.zip. CWM4 is also confirmed to be safe for wipe by Entropy512 Recognized Developer
For other phones, download the cwm image from here http://clockworkmod.com/rommanager
.
Put the previously downloaded cwm-touch-6.0.x.x-i9100.zip file on your external sd card
Download the attached root file you want as per instructions above
I advise Chainfire SuperSU for 2 reasons: it lets you unroot from within superSU application and it lets you migrate to ChainsDD superuser if you like later
Copy the Root_XXX.zip file you downloaded to internal or external sd card
Boot into stock recovery (volume up+home+power), and select "apply update from external storage". Now select the cwm-touch-6.x.x.x-i9100.zip file you copied in previous step (this step gives a temporary flash that will disappear after reboot)
You get CWM recovery interface (this custom recovery is temporary, not permanent)
Inside CWM, select "install zip from sdcard". Then, select "choose zip from sdcard". Now, scroll down to the "Root_XXX.zip" file and hit power button to install it.
It will add SuperSU or Superuser last version apk to system/app, last superuser binary (su) to system/xbin and busybox last version to system/xbin, all with correct file permissions.
Reboot and you get permanent root + busybox installed on your stock kernel.
To unroot, do the above steps and replace the file Root_XXX.zip by the attached Unroot_SuperUser-Busybox-Uninstaller-Update2-signed.zip. It will delete superuser, su and busybox packages.
For a complete removal of busybox, look here at my Busybox Uninstaller which will remove ALL busybox symlinks (over 600 files depending on installers used before):
http://forum.xda-developers.com/showthread.php?t=1853419
Click to expand...
Click to collapse
Fix common issues: You end with both ChainsDD and Chainfire superuser and SuperSU
Also another symptom is having constantly superuser asking for updates from market.
Some people are getting duplicates from previous root methods using ChainsDD superuser instead of Chainfire superSU or vice versa when they come from SuperSU and switch to superuser.
Also, this can happen when you updated let's say to a future Chainfire SuperSU v1.0 and later you use one of my outdated scripts (with version 0.94 for example).
The cause is that I do not delete anything from /data/app. I can add it, it is not an issue, but till these brick things are fixed, I chose not to do it.
The solution is very easy:
Just uninstall from stock application manager all superuser applications. The /system/app application will stay as system applications cannot be removed normally in application manager
After that, just update your superuser application from market. Updates are put in /data/app and original copy will stay in /system/app.
Click to expand...
Click to collapse
Method 2
CF_Root + stock kernel + [optional] Mobile Odin Free version
Here, you use an older CF_Root kernel, and flash your newer stock kernel
First, get a CF_Root kernel from CF_Root thread here http://forum.xda-developers.com/showthread.php?t=1103399. Just get the nearest one to your ROM. You can download any ICS kernel, it will do the job for the root only purpose
Flash the CF_Root kernel with odin
Now, flash again your stock kernel with odin. You can get a stock kernel from lyriquidperfection thread http://forum.xda-developers.com/showthread.php?t=1619525
Do not forget to thank / donate to him
No stock kernels for you? use Mobile Odin free version (see below)
After flashing the stock kernel, root will usually stay and you will be reverted back to your stock recovery instead of CWM recovery
Click to expand...
Click to collapse
Method 3
Insecure Kernels + SuperOneClick + [optional] Mobile Odin Free
Not tested by me. You get superuser instead of Chainfire superSU + an older busybox
First, get an insecure kernel from here http://forum.xda-developers.com/showthread.php?t=1619525
Do not forget to thank/donate lyriquidperfection
No insecure kernel for your ROM? Just try a kernel from same ICS version, it usually works fine for rooting
Flash the insecure kernel with odin
Download SuperOneClick v2.3.3 from here http://shortfuse.org/?p=193 and look at this thread for an overview: http://forum.xda-developers.com/showthread.php?t=803682
Put your phone on USB debugging mode (System Settings / Developer Options)
Launch SuperOneClick and root using auto or psneuter method. Do not use the ZergRush Exploit as it is meant for older exploited GB versions
Now, flash again your stock kernel with odin. You can get a stock kernel from lyriquidperfection thread http://forum.xda-developers.com/showthread.php?t=1619525
Do not forget to thank / donate to him
No stock kernel for your ROM? Use Mobile Odin Free version (see below)
Click to expand...
Click to collapse
Method 4
Insecure Kernels + S2 Root - For SAMSUNG Devices
The tool and all instructions are on lyriquidperfection thread:
http://forum.xda-developers.com/showthread.php?t=1125414
It will do the same as in method 3, but using a newer and better supported tool than SuperOneClick
You have to flash an insecure kernel, root with S2Root and flash again your stock kernel
It roots using Chainfire SuperSU and busybox 1.20.1 at time of posting
Author is a recognized developer and offers great support
You are still depending on author to release a custom kernel for all your new ROMs
Click to expand...
Click to collapse
Mobile Odin Free version
Flash your stock kernel from complete ROM file
Now that Intratech stopped releasing stock kernels in his thread, rooting using methods 2 and 3 can be a problem. In fact, you will not be able to flash your newer original stock kernel after rooting with insecure or cf_root older kernel. You can look in above lyriquidperfection thread for a stock kernel to flash in odin. But, if you do not like to wait for him to release a kernel, you can get Mobile Odin Free version
Download Mobile Odin Free version from here http://forum.xda-developers.com/showthread.php?t=1347899
Do not forget to thank donate to Chainfire
From your stock tar.md5 ROM file, extract the zimage file (your stock kernel)
Put zimage file on external sd card
Run Mobile Odin and specify the zimage file in kernel box like in this image:
Flash, you get your stock kernel and root is normally left
Click to expand...
Click to collapse
Mobile Odin Pro (Payed) version
Root + Flash - You should consider buying it.
With this method, you will have SuperSU from chainfire (that can be updated from market) but no Busybox.
You can install busybox from market or from attached CWM_Root_Busybox_1.20.2_Only_(No_SuperSU)-S2-Update2-signed.zip file in this thread
Buy Mobile Odin Pro from market here https://play.google.com/store/apps/details?id=eu.chainfire.mobileodin.pro
If you want to flash a full new rom, put the tar file on the external_sd. Point all boxes to the ROM tar file. Enable EverRoot option like in image below. Flash
If you flashed your ROM using odin and only want to root, proceed like in Example 4 above to flash only the kernel (zimage file from your actual ROM). Enable EverRoot option and flash
Now, install BusyBox from market or flash my CWM_Root_Busybox_1.20.2_Only_(No_SuperSU)-S2-Update2-signed.zip file with cwm to get last busybox.
Click to expand...
Click to collapse
Chainfire - adbd Insecure app
Getting switchable insecure kernel WITH stock kernel
One of the advantages for some people in CF_Root kernel is the insecure mode. Now, you can have insecure kernel like behavior without flashing a custom kernel. There is a magic app for that, signed Chainfire.
Thread + free download link here:
http://forum.xda-developers.com/showthread.php?t=1687590
And you can buy it from market to support author:
https://play.google.com/store/apps/details?id=eu.chainfire.adbd
Instructions, quoted from chainfire
If you are running a stock (made by the phone manufacturer) kernel on your device, chances are adbd is running in "secure" mode, even if you are rooted. This app lets you run adbd in "insecure" mode, which gives you root access in "adb shell", allows access to system files and directories through "adb push/pull", and lets you run the "adb remount" command to make your /system partition writable.
Of course, your device must already be rooted for this to work. It may not work with "S-ON" devices and locked bootloaders.
This app does not make any permanent changes to your device - a reboot will undo any modification. That's why there is also the option to enable this feature at boot.
Note that if you have USB connected when the app activates or deactivates adbd root mode, you may need to unplug/replug the cable or run "adb kill-server" on your computer before adb will work again.
Click to expand...
Click to collapse
Feel free to comment or suggest enhancements
Big Thanks! Very usefull post.
Links seems down. Ive took it from Your post #382 in http://forum.xda-developers.com/showthread.php?t=1501719&page=39
Method #1 working very well with LPD kernel. Thanks Again.
Yes, sorry
It is a forum problem, hope it is fixed. I will update it as soon as it is fixed
While waiting for forum to fix my attachments, I edited post 1 with mediafire mirrors to the files
Sorry
nabuhonodozor said:
Big Thanks! Very usefull post.
Links seems down. Ive took it from Your post #382 in http://forum.xda-developers.com/showthread.php?t=1501719&page=39
Method #1 working very well with LPD kernel. Thanks Again.
Click to expand...
Click to collapse
Happy it helped
Hi, I always install new ics Sammy roms using Mobile Odin pro, but didn't know that busybox wasn't installed, so I need to know what is the point of installing it? What is the real use of busybox? I've been using my s2 rooted just with mobile Odin pro without any issue... Every root app that I need like titanium backup, root explorer, etc. Are working great, so I don't know what busybox is for...
Sorry for the dumb question and thanks in advance for the help!
Enviado desde mi GT-I9100 usando Tapatalk 2
Maybe you once installed a CF_Root or other kernel that comes with busybox
If you do not format /system, most system apps are kept, include busybox
Titanium backup uses its internal busybox version, not the /system one
Root explorer does not use busybox I think, but not sure
To know if it is installed or not, look for busybox file in /system/xbin or /system/bin
thanks ,hey can you also post way to change cf root's recovery (non touchable) to tuch recovery that would be really awesome :highfive:
apk_xiz said:
thanks ,hey can you also post way to change cf root's recovery (non touchable) to tuch recovery that would be really awesome :highfive:
Click to expand...
Click to collapse
This is not cf_root or a kernel, sorry
CWM from cf_root is proprietary coded by Chainfire
Phil3759 said:
This is not cf_root or a kernel, sorry
CWM from cf_root is proprietary coded by Chainfire
Click to expand...
Click to collapse
oh ok my bad
Phil3759 said:
Maybe you once installed a CF_Root or other kernel that comes with busybox
If you do not format /system, most system apps are kept, include busybox
Titanium backup uses its internal busybox version, not the /system one
Root explorer does not use busybox I think, but not sure
To know if it is installed or not, look for busybox file in /system/xbin or /system/bin
Click to expand...
Click to collapse
OK, thanks a lot for the help!
Enviado desde mi GT-I9100 usando Tapatalk 2
apk_xiz said:
oh ok my bad
Click to expand...
Click to collapse
Unless you frequently use cwm, there is really no need to use cf_root. Only really missing thing is insecure kernel to have adb access as root. I will edit post 1 for adding insecure behavior without flashing
Sent from my GT-I9100 using Tapatalk 2
Done,
I added a paragraph at the end with instructions to have adb shell root access like in insecure kernels
Updated first post with new SuperSU 0.93
If you already used this method, no need to flash again, just open superSU and update through market. After that, open app and it will update the su binary
i think guides belong in the general section
nice guide though
Forum attachments are fixed now
You can download again from forum, but I will keep mediafire mirrors
edit 2: fixed the 0kb download attachments corrupted uploads when forum was broken
Mobile Odin
Thanks for the great guide Phil. A couple of questions..
I have Mobile Odin Pro and I want CWM as well so i have to do this?
Flash new rom with superuser injected, cwm manager and everoot ticked.
Flash CWM with instructions from 1st method
Flash with CWM CWM_Busybox_Only_1.20.1.zip
thats it? I guess this emulates a CF-ROOT kernel right?
thanks again.
No, Chainfire CWM manager app will detect a CF_Root kernel and refuse to launch if another kernel is there
Only CF_Root has Chainfire CWM, a custom written CWM
Other kernels include custom CWM too, look for them
The CWM image here will give you all functions from the original CWM project, but you need to launch it from stock recovery. Just keep the zip on your external sd card, that's it, only more 2 clicks. At the end, you get all CWM functions
Phil3759 said:
No, Chainfire CWM manager app will detect a CF_Root kernel and refuse to launch if another kernel is there
Only CF_Root has Chainfire CWM, a custom written CWM
Other kernels include custom CWM too, look for them
The CWM image here will give you all functions from the original CWM project, but you need to launch it from stock recovery. Just keep the zip on your external sd card, that's it, only more 2 clicks. At the end, you get all CWM functions
Click to expand...
Click to collapse
I see. I won't tick cwm manager and install the original CWM.
Thanks bro.
borolo222 said:
I see. I won't tick cwm manager and install the original CWM.
Thanks bro.
Click to expand...
Click to collapse
In any case, you need CWM image for the method in post 1
From CWM, you flash root file
But on reboot, you will still have your original stock recovery. To launch CWM, you have to launch it from your stock recovery
Related
zergrush won't get in
Hi everyone, do you have idea why I can't root my phone?, the zergrush didn't go through, that's how I understand the screenshot
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Just use CF kernel to root phone using Odin. Nice instructions are included in it. http://forum.xda-developers.com/showthread.php?t=1103399
ok, I've finally rooted my phone using Code: GT-I9100G_DZKI1_insecure and followed by zergrush I can now see a superuser icon, now my next question is, what to do next to mod the phone? is my phone ready now? ...actually I installed this app called "Root Check Basic" from the droid market, when I tapped it, it was requesting for a super root access, and there's an "allow" or "deny" button..do i need to allow that ?
addbot said: ok, I've finally rooted my phone using Code: GT-I9100G_DZKI1_insecure and followed by zergrush I can now see a superuser icon, now my next question is, what to do next to mod the phone? is my phone ready now? ...actually I installed this app called "Root Check Basic" from the droid market, when I tapped it, it was requesting for a super root access, and there's an "allow" or "deny" button..do i need to allow that ? Click to expand... Click to collapse So it can check you have root. All root apps will request. Yes, "allow" Sent from my GT-I9100 using xda premium
ok, it worked..i now have a super root access...now my next question is, what to do next to this phone, to mod it ? btw, i don't have clockwork mod recovery and other stuffs? why is that? ..all i have is the superuser icon :/
addbot said: ok, it worked..i now have a super root access...now my next question is, what to do next to this phone, to mod it ? btw, i don't have clockwork mod recovery and other stuffs? why is that? ..all i have is the superuser icon :/ Click to expand... Click to collapse I answered that in your previuos thread.................. http://forum.xda-developers.com/showpost.php?p=21647119&postcount=24 You can always try this G kernel, has root and CWM Recovery v5: [KERNEL][I9100G][2.3.5]MyGKernel - CWM5, Root, CIFS You can flash a lot of stuff,. but be careful, look for compatible ROMS, mods, themes for your G version! And don't forget; Hit thanks when you have the time.............. It's what we do on XDA when some has tried to be of help. Cheers
I got a question about the binary counter at the download mode, is that harmful ?, because it is increment whenever I flash something thru odin..is there a way to reset that counter ?
If you search it, it will come. Sent from my GT-I9100 using XDA App
addbot said: I got a question about the binary counter at the download mode, is that harmful ?, because it is increment whenever I flash something thru odin..is there a way to reset that counter ? Click to expand... Click to collapse Jig is used to reset binary counter. Kaze105 said: Just use CF kernel to root phone using Odin. Nice instructions are included in it. http://forum.xda-developers.com/showthread.php?t=1103399 Click to expand... Click to collapse Flashing insecure kernel thru odin increases binary count and causes yellow triangle. Zergrush is the way to root without increasing binary count and without having yellow triangle. But this is only allowed in 2.3.3 and 2.3.4 and early 2.3.5 builds. So what I can suggest for addbot is to flash a 2.3.3 rom then do the zergrush method to remove yellow triangle. This is also possible Nandroidbackup>flash 2.3.3 stock rom>zergrush, put a rooted kernel like siyah(one kernel for all variants)>Nandroid restore.
addbot said: I got a question about the binary counter at the download mode, is that harmful ?, because it is increment whenever I flash something thru odin..is there a way to reset that counter ? Click to expand... Click to collapse It's not harmful. As you would have read, that rooting (anyway,........evidence of it) will most likely void your warranty. You need a USB jig to reset it (found in eBay for a couple dollars, or make yourself). Certain bootloaders, I think after KI3 (don't quote me on the number ) are locked, so thew jig won't reset. But it may still force your phone into Download Mode if the hard key method won't won't. I am not sure if the jig will reset on a 9100G or indeed your firmware version. Intratech's thread here has the old bootloader used to flash locked 9100 bootloaders (so jig will work), but I'm not sure if it is compatible with 9100G. Before even thinking of flashing it, make sure 100% confirmed to work on your model, otherwise you'll have a real hard brick.
drigz08 said: Jig is used to reset binary counter. Flashing insecure kernel thru odin increases binary count and causes yellow triangle. Zergrush is the way to root without increasing binary count and without having yellow triangle. But this is only allowed in 2.3.3 and 2.3.4 and early 2.3.5 builds. So what I can suggest for addbot is to flash a 2.3.3 rom then do the zergrush method to remove yellow triangle. This is also possible Nandroidbackup>flash 2.3.3 stock rom>zergrush, put a rooted kernel like siyah(one kernel for all variants)>Nandroid restore. Click to expand... Click to collapse thanks sir. UpInTheAir said: It's not harmful. As you would have read, that rooting (anyway,........evidence of it) will most likely void your warranty. You need a USB jig to reset it (found in eBay for a couple dollars, or make yourself). Certain bootloaders, I think after KI3 (don't quote me on the number ) are locked, so thew jig won't reset. But it may still force your phone into Download Mode if the hard key method won't won't. I am not sure if the jig will reset on a 9100G or indeed your firmware version. Intratech's thread here has the old bootloader used to flash locked 9100 bootloaders (so jig will work), but I'm not sure if it is compatible with 9100G. Before even thinking of flashing it, make sure 100% confirmed to work on your model, otherwise you'll have a real hard brick. Click to expand... Click to collapse thanks.... btw, how to change this default appearance of my phone?, is that what we call "custom rom", OR is that by using a theme?
addbot said: btw, how to change this default appearance of my phone?, is that what we call "custom rom", OR is that by using a theme? Click to expand... Click to collapse There aren't a great deal for 9100G around XDA. Plenty for the 9100/T etc. Just have a search inthe themes and apps forum or Development for compatible ROMs. Some ROMs are already themed, but some others need the add-ons (if you want). Another way to theme / personalise is to use the UOT Kitchen to create your own flashable zip. Instructions are there. You will need to upload your framework-res.apk and SystemUI.apk from your ROM. You'll need a root file explorer such as; root explorer or es file explorer. Ensure they have root access first Remeber: To make a full nan-droid backup in CWM recovery before, so if it goes "pear shaped" you can easily retore.
UpInTheAir said: There aren't a great deal for 9100G around XDA. Plenty for the 9100/T etc. Just have a search inthe themes and apps forum or Development for compatible ROMs. Some ROMs are already themed, but some others need the add-ons (if you want). Another way to theme / personalise is to use the UOT Kitchen to create your own flashable zip. Instructions are there. You will need to upload your framework-res.apk and SystemUI.apk from your ROM. You'll need a root file explorer such as; root explorer or es file explorer. Ensure they have root access first Remeber: To make a full nan-droid backup in CWM recovery before, so if it goes "pear shaped" you can easily retore. Click to expand... Click to collapse I downloaded the clockwork rom manager v.4.8.1.3 from droid market..and I can see a menu "Install ROM from SD Card", does that mean, I can also use this option to install a .apk file that I placed inside my sd card ?
addbot said: I downloaded the clockwork rom manager v.4.8.1.3 from droid market..and I can see a menu "Install ROM from SD Card", does that mean, I can also use this option to install a .apk file that I placed inside my sd card ? Click to expand... Click to collapse I don't use ROM manager anymore as alot is not compatible with SGS2. Do not use option to flash recovery as will corrupt your recovery/kernel partition. Try Chainfire's CWM Manager instead. It is attached. Before, ensure phone menu / settings / applications / unknown sources (checked). Install same as any other app, use Package Installer. Give SuperUser permission "allow" when requested.
UpInTheAir said: I don't use ROM manager anymore as alot is not compatible with SGS2. Do not use option to flash recovery as will corrupt your recovery/kernel partition. Try Chainfire's CWM Manager instead. It is attached. Before, ensure phone menu / settings / applications / unknown sources (checked). Install same as any other app, use Package Installer. Give SuperUser permission "allow" when requested. Click to expand... Click to collapse ok, but my question is, how to install this .apk file ? , do i need to create a folder inside the sd card and place it there ? ..if I do that..how will my phone find that .apk file to install it?
addbot said: ok, but my question is, how to install this .apk file ? , do i need to create a folder inside the sd card and place it there ? ..if I do that..how will my phone find that .apk file to install it? Click to expand... Click to collapse Simple, 1. Put the .apk file anywhere (you can remeber) on you internal or external sdcard. 2. Use File explorer (My files) and navigate to the .apk. 3 .Tap on the .apk and use option "Package installer". Done or, 1. Use root file explorer such as root explorer (es file explorer free on market, may need to change app settings for root) and copy .apk. 2. Navigate to data/app, change option to mount r/w and paste. 3. Boot into CWM recovery 4. Clear cache and advance/wipe dalvik 5. Reboot, will take a few minutes, be patient
UpInTheAir said: Simple, 1. Put the .apk file anywhere (you can remeber) on you internal or external sdcard. 2. Use File explorer (My files) and navigate to the .apk. 3 .Tap on the .apk and use option "Package installer". Done or, 1. Use root file explorer such as root explorer (es file explorer free on market, may need to change app settings for root) and copy .apk. 2. Navigate to data/app, change option to mount r/w and paste. 3. Boot into CWM recovery 4. Clear cache and advance/wipe dalvik 5. Reboot, will take a few minutes, be patient Click to expand... Click to collapse cool!, ok, i just wanna verify again..the only way I can install an app to the external sd card is , by installing it the way it should be installed from droid app or manually and then 1 ) Applications 2 ) Manage Applications 3 ) Select App 4 ) tap "Move to SD card" button is that it ? ( will that help in lessening the burden of the device memory ? )
Yep, that's it. Downside is if you mount your sdcard to anything, app or widget etc will stop functioning. Won't really help lessen the burden of RAM, but free up more internal memory though. Sent from my GT-I9100 using xda premium
UpInTheAir said: I don't use ROM manager anymore as alot is not compatible with SGS2. Do not use option to flash recovery as will corrupt your recovery/kernel partition. Try Chainfire's CWM Manager instead. It is attached. Before, ensure phone menu / settings / applications / unknown sources (checked). Install same as any other app, use Package Installer. Give SuperUser permission "allow" when requested. Click to expand... Click to collapse darn, wasn't able to install this , i placed that .apk file in my external sd card, wen to my files and tried tapping that .apk, it failed installing.i dunno why
addbot said: darn, wasn't able to install this , i placed that .apk file in my external sd card, wen to my files and tried tapping that .apk, it failed installing.i dunno why Click to expand... Click to collapse Use 2nd method from my post #16. Will work.
[Q] Kernal/Busybox questions
Is busyBox built into CWM recovery kernals? is this common practice? if so, and "I believe it is" How can I update my busyBox Version? The experience Im having is on stock 2.3.4 when I check with root checker pro .apk it shows BusyBox Version 1.19.2cm71 installed in /sbin/ So I try to update to BusyBox version 1.19.4stericson via his BusyBox installer .apk Then check with Root checker Pro .apk and all is well Untill I reboot My phone Imediatly after reboot Root cheker shows the old Busy Box version again. So I geuse what Im asking for is verification basicly. Is there not a tool to incorporate CWM into existing stock recovery like the one used for the OG transformer Tab? By the way to all comers who would like to bash my noobness Bring it! I say this because I can learn more from the bashing than from no response/answer at all. That being said Thanks to the Devs that do chime in with direct, and helpful responses. Its much appreciated by me as this is my main source of refferance for android learning. My post count is so low because I read !
busybox is a binary located in either /system/bin or /system/xbin its not something included in a kernel
If you newwest busybox then search and find a cwm zip for root and flash it... Easiest way.. Sent from my GT-I9100 using xda premium
Pirateghost said: busybox is a binary located in either /system/bin or /system/xbin its not something included in a kernel Click to expand... Click to collapse Thanks for your response, but I Know what busybox is and where its supposed to be but if you have CWM recovery do me a favor and check your "/sbin" folder on "root of phone" not in the "/system" folder there you will see "busybox" in "/sbin". Also there is an app called "root checker" by Joey something or other if you run this app and swipe to the left you'll see the screen verify busybox click it and it will tell you where its installed and what version is installed. I originaly thought same as your reply and its true as long as you install busybox While using stock recovery. Meaning if I install busybox to "/system/xbin" with CWM recovery installed my newer busybox version won't stick. (Only good until reboot) I've completely reverted to stock 2.3.4 GB and checked the /sbin folder before and after installing codeworkx 5.0.2.3 CWM revovery and These were my findings. However on the skyRocket I do not seem to have this problem I believe this is why. Pirateghost said: skyrocket has separate recovery partition.....their CWM isnt injected into kernel.... Click to expand... Click to collapse While Great for My "I727" that doesnt help me on my "I777"
rdannar said: If you newwest busybox then search and find a cwm zip for root and flash it... Easiest way.. Sent from my GT-I9100 using xda premium Click to expand... Click to collapse Thanks but not at all what I was talking about.
Phatboyj420 said: Thanks but not at all what I was talking about. Click to expand... Click to collapse if it doesn't stick you probably have two versions... One in bin and one in xbin. delete old one. flash in cwm so it corrects symlink to newwest busybox. your syymlink are probably not correct. The install script changes the symlink of the file.. That is why you use cwm to flash Sent from my GT-I9100 using xda premium
rdannar said: if it doesn't stick you probably have two versions... One in bin and one in xbin. delete old one. flash in cwm so it corrects symlink to newwest busybox. your syymlink are probably not correct. The install script changes the symlink of the file.. That is why you use cwm to flash Sent from my GT-I9100 using xda premium Click to expand... Click to collapse Thanks again but your still off please re-read O.P. Ive done all that you suggest. in doing so I,ve learned that when I manualy delete busybox from "/sbin" it gets re-written upon reboot. The only Rom with CWM recocery That I've found this not to be true in is "task650's" latest ICS release UCPLC5, It does initialy install busybox but not to "/sbin" and it does'nt get re-written on every reboot. Thus allowing the users busybox update to stick. Thanks for that Task.
I experience the same troubles with GB SpeedMod Kernel v2.21 which includes CWM 5.0.2.3, so I searched around and found this thread. Running StockROM (GB 2.3.6) the updates of BusyBox (have it in /system/xbin) work perfectly, no second version anywhere (/system/bin or /sbin). Flashing SpeedMod Kernel with CWM delivers a second copy of BusyBox into /sbin, where busybox itself is a symlink to recovery in the same directory. Bad enough that an update to the latest BusyBox version seems to be fine but doesn't stick after reboot (as mentioned by Phatboyj420, for clarification: the update in /system/xbin sticks but the update or deletion of BusyBox in /sbin is reverted as part of kernel during reboot), so e.g. Ghost Commander shows some errors (owner and file permissions) which are related to this mixed version status and disappear after updating BusyBox (till the next reboot). To confirm that CWM delivers BusyBox to /sbin I looked into the source of SpeedMod v2.21 (find it here!). Just unpack it and have a look into /initramfs/out/sbin.
DisasterROM_v8 user Q /A
hello Today was the first time I joined. DisasterROM_v8 bugs will tell. Was a supersu DisasterROM_v7 DisasterROM_v8 do not have su and superuser privileges error appears. Rom developers solve problems related supersu by Please 8.0 7.0 original rom the xbin su was not xbin busybox and su-related files.Re-upload please. Xbin 7.0 and 8.0 below screen syaseun comparison photos. I'm sorry, but I've used Google translate. Can write well by the developers who made Erom! Installed su binary and supersu can not be installed. Problems.!
Reflash any other compatible kernel. Something like Philz kernel : http://forum.xda-developers.com/showthread.php?t=1877270
jl10101 said: Reflash any other compatible kernel. Something like Philz kernel : http://forum.xda-developers.com/showthread.php?t=1877270 Click to expand... Click to collapse I have a solution. 1. Download http://downloadandroidrom.com/file/tools/SuperSU/CWM-SuperSU-v0.99.zip and put on sd card 2. Reboot into recovery 3. flash this zip 4. In recovery go to advanced, and Fix permissions 5. Reboot and enjoy your rom with working superuser 6. Run Google play and let the supersu app to update
[Q]Rooting by push SU - Phil3759
Sorry i have to ask here, cause i can't ask in the related thread http://forum.xda-developers.com/showthread.php?t=1746794 Instructions For phones affected by the superbrick bug (i9100, N7000) and that has a stock recovery accepting update.zip files (most phones with a temporary cwm.zip file at Clockworkmod site: Quote: You can flash the attached files directly in stock recovery 3e, no need to cwm: Download the root file: - Root_SuperSU.0.96.Only-signed.zip for Chainfire SuperSU (the one that comes with CF_Root) without busybox. - Root_SuperSU.0.96-FreeSpace.zip for Chainfire SuperSU without busybox (use only if you have issues with previous one, usually for phones having a /system partition with 0 free space). - Root_SuperSU.0.96-Busybox.1.20.2-S2-signed.zip to install superSU + busybox v1.20.2 from Linus Yang. - Root_Superuser_3.1.3_Busybox_1.20.2-Update1-signed.zip if you prefer the classic ChainsDD superuser + Busybox from Linus Yang. - Root_Busybox_1.20.2_Only_XXX.zip to install only Busybox from Linus Yang. I advise Chainfire SuperSU for 2 reasons: it lets you unroot from within superSU application and it lets you migrate to ChainsDD superuser if you like later . Copy the Root_XXX.zip file you downloaded to externalsd card Boot into stock recovery (volume up+home+power), and select "apply update from external storage". Now select the Root_XXX.zip file downloaded above and you are rooted To unroot, do the above steps and replace the file Root_XXX.zip by the attached Unroot_SuperUser-Busybox-Uninstaller-Update2-signed.zip. It will delete superuser, su and busybox packages. For a complete removal of busybox, look here at my Busybox Uninstaller which will remove ALL busybox symlinks (over 600 files depending on installers used before): http://forum.xda-developers.com/show....php?t=1853419 To get temporary cwm (to make nandroid backups...) or if stock recovery gives you a signature error, follow the next more universal steps. Click to expand... Click to collapse the instruction is using 96 Root_SuperSU.0.96.Only-signed.zip but i noticed there is a same zip with higher number Root_SuperSU.0.98.Only-signed.zip what's the different between the two ? for my SGS2 with jelly bean 4.1.2 which one should i use ? also will the unroot method using Unroot_SuperUser-Busybox-Uninstaller-Update2-signed.zip will work for the Root_SuperSU.0.98.Only-signed.zip Thank you
Just install a custom kernel like Philz which will give you cwm recovery and root.
archiles said: the instruction is using 96 Root_SuperSU.0.96.Only-signed.zip but i noticed there is a same zip with higher number Root_SuperSU.0.98.Only-signed.zip what's the different between the two ? for my SGS2 with jelly bean 4.1.2 which one should i use ? Click to expand... Click to collapse The difference is in the versions of SuperSU app. You can use either one mate. archiles said: also will the unroot method using Unroot_SuperUser-Busybox-Uninstaller-Update2-signed.zip will work for the Root_SuperSU.0.98.Only-signed.zip Click to expand... Click to collapse Yup, it should. :good:
immortalneo said: The difference is in the versions of SuperSU app. You can use either one mate. Yup, it should. :good: Click to expand... Click to collapse Ok, kewl. thank you. andrewwright said: Just install a custom kernel like Philz which will give you cwm recovery and root. Click to expand... Click to collapse I was thinking of installing custom kernel, but they don't have the LSD version. at least yesterday i checked on the thread there wasn't thanks for the help!
Use lsw. Or lss
There is LSD version mate. Check some more. "To err is human, to forgive is divine." Sent from my SGS II
The only update is super user with philz kernel. Only reason I said lws/lss is because it's newer and updated. But you can go with lsd.
Replacing kingo superuser to supersu
I was new for rooting and choose the easiest way to root(kingoroot not kingroot) my samsung galaxy j1 ace... and now i want to switch to supersu from kingo superuser... as kingroot being more famous... i didnt found any tutorials too... some are using supersu me... i have no idea what to do... i want to clear the remainants of kingo too... help me...
A procedure is here: https://forum.xda-developers.com/an...g/replace-kingoroot-supersu-manually-t3573361 My device stores applications in directories in /data/app, ex: com.kingoapp.apk-1, com.kingouser.com-2, eu.chainfire.supersu-1, with subdirectories, lib and oat... Any help to transpose the procedure above into this environment?
pascal.malaise said: A procedure is here: https://forum.xda-developers.com/an...g/replace-kingoroot-supersu-manually-t3573361 My device stores applications in directories in /data/app, ex: com.kingoapp.apk-1, com.kingouser.com-2, eu.chainfire.supersu-1, with subdirectories, lib and oat... Any help to transpose the procedure above into this environment? Click to expand... Click to collapse can u suggest me something easy???... like with terminal....
Revert to stock rom and try the manual rooting using SuperSU. You'll need a compatible custom recovery to install supersu.
rolland.arriza said: Revert to stock rom and try the manual rooting using SuperSU. You'll need a compatible custom recovery to install supersu. Click to expand... Click to collapse terminal or supersu me will work?
http://www.ccnworldtech.com/2017/03/how-to-replace-kinguserkingo-superuser.html?m=1 will it work???
yashasvi.malik said: can u suggest me something easy???... like with terminal.... Click to expand... Click to collapse plss help....
yashasvi.malik said: terminal or supersu me will work? Click to expand... Click to collapse Have you reverted to stock rom? You can just do a factory reset (root access should be removed too). Install the necessary drivers. Download a custom recovery for your device (TWRP maybe, search it here in the forum). Download the supersu flashable zip (this is an older version, just update after install). Also download the latest ADB drivers (awesome app). Then you root: (1) Copy the supersu zip to your device storage. Copy/move the custom recovery to the root folder of your ADB. (2) Open ADB: Code: adb reboot bootloader wait for the device to go into fastboot, then: Code: fastboot boot "recovery.img" (3) Navigate the new custom recovery and select "Install" and select the supersu zip file, then reboot. (4) Check root access. Goodluck