Root using update.zip? - Galaxy S II General

Hi,
I got my Galaxy S (called Captivate for AT&T) a few day before it hit the store (more than one year ago. I remember that for rooting my capy I just had a update.zip to install and do an update.
I will soon get a new Galaxy SII and was wondering if there was a way to root it like I used to do it with my capy or do I HAVE to go thru odin?
Thanks

You need Odin or Heimdall, there is no other way.

floppy__ said:
do I HAVE to go thru odin?
Click to expand...
Click to collapse
Is odin difficult to use or something? I don't understand... you select the cf-root kernel, make sure odin detects the phone and flash away, easy as pie.

It's not that Odin is hard to use, it's just that you need a computer... With the update.zip you can root on the go
Sent from my SGH-I897 using Tapatalk

Pretty sure you can root the s2 without a computer.
1 - Download rom manager from the market.
2 - Flash clockworkmod for s2 from within rom manager.
3 - That would create an update zip to install cwm to the phone. So reboot into stock recovery and select update zip. Might need to run it twice and you should now have cwm recovery on your phone.
4 - Simply download a kernal (from xda development section) which has root built in. I would recommend either cf-root or speedmod. Reboot into cwm recovery and select flash zip from sd. Navigate to where the kernsl is saved and flash away. Your phone should now be rooted.
Probably download the kernal first so you can flash it as soon as cwm recovery gets installed after flashing the update zip.
I always did it that way on my s1 but maybe things have changed since then.
Sent from my GT-I9100 using XDA Premium App

sxi200 said:
Pretty sure you can root the s2 without a computer.
1 - Download rom manager from the market.
2 - Flash clockworkmod for s2 from within rom manager.
Click to expand...
Click to collapse
ROM Manager requires root.

There was a flaw in the 2e recovery that allowed non signed zip's to run on the sgs1, that's why you could root the phone just by running a zip, later samsung patched that hole with 3e recovery.
All sgs2 phone now run 3e recovery so the only way to root them is by flashing a modified kernel. However there is a new exploit that can root your phone without using odin, but you still need the phone connected to a computer to easily do it.
However running all of the commands from the phone in terminal emulator should work also, its just that there's a ton of them to type out.
@files\adb wait-for-device
@files\adb shell "cd /data/local/tmp/; rm *"
@files\adb push files\zergRush /data/local/tmp/.
@files\adb shell "chmod 777 /data/local/tmp/zergRush"
@files\adb shell "./data/local/tmp/zergRush"
@files\adb wait-for-device
@files\adb push files\busybox /data/local/tmp/.
@files\adb shell "chmod 755 /data/local/tmp/busybox"
@files\adb shell "/data/local/tmp/busybox mount -o remount,rw /system"
@files\adb shell "dd if=/data/local/tmp/busybox of=/system/xbin/busybox"
@files\adb shell "chown root.shell /system/xbin/busybox"
@files\adb shell "chmod 04755 /system/xbin/busybox"
@files\adb shell "/system/xbin/busybox --install -s /system/xbin"
@files\adb shell "rm -r /data/local/tmp/busybox"
@files\adb push files\su /system/bin/su
@files\adb shell "chown root.shell /system/bin/su"
@files\adb shell "chmod 06755 /system/bin/su"
@files\adb shell "rm /system/xbin/su"
@files\adb shell "ln -s /system/bin/su /system/xbin/su"
@files\adb push files\Superuser.apk /system/app/.
@files\adb shell "cd /data/local/tmp/; rm *"
@files\adb reboot

Related

[How to] Root Motorola Atrix with terminal

Maybe I'm the only one but this is the method I prefer to use to root my phone. I'm not always sure which OS I'll be working with when I have to do this and this one works on all of them as long as you have the Android SDK.
Put the files into your platform-tools folder to make them easy to find.
Not sure if I need this but I'm not responsible for bricks or any other complication, etc, etc.
adb push psneuter /data/local/tmp
adb push bin/su /data/local/tmp
adb shell chmod 6755 /data/local/tmp/psneuter
$ ./data/local/tmp/psneuter
adb shell
# mount -o rw, remount /dev/block/mmcblk0p12 /system
# rm /data/local/tmp/su /system/bin/su
#chmod 6755 /system/bin/su
exit
really? psneuter only works for 1.26 froyo
I used this method on 1.83 when I first got the phone. Might need to look back into this. Someone asked about this method so I posted it.
Sent from my MB860 using XDA Premium App

[TUTORIAL]How to manual root official 2.3

I always have problems to root official 2.3 with automatic ways, and found that this caused from some adb miscommunication.
So this is how to do it manual, in case automatic ways stacked.
First install adb-sdk and add its path to system variables, so to don't have to go to adb' s path before you can run it.
Then download doomlord' s rooting tool and extract it to drive C:\DoomLordRoot.v3.
http://forum.xda-developers.com/attachment.php?attachmentid=784296&stc=1&d=1321435888
Preparation steps on device:
1) Dial: *#*#2846579#*#*
2) Go to projectmenu > background settings > log settings > log switch > set Log on
3) Reboot Phone
4) Switch USB Debugging ON
5) uncheck fast boot from settings -> applications
Click to expand...
Click to collapse
Open windows command prompt window and do the above:
Code:
adb push c:\DoomLordRoot.v3\files\zergRush /data/local/tmp/
[COLOR="DarkSlateBlue"]adb shell[/COLOR]
chmod 777 /data/local/tmp/zergRush
./data/local/tmp/zergRush
[COLOR="DarkSlateBlue"]Hit CTRL+C to exit from adb shell[/COLOR]
adb push c:\DoomLordRoot.v3\files\busybox /data/local/tmp/
[COLOR="DarkSlateBlue"]adb shell[/COLOR]
su
chmod 755 /data/local/tmp/busybox
/data/local/tmp/busybox mount -o remount,rw /system
dd if=/data/local/tmp/busybox of=/system/xbin/busybox
chown root.shell /system/xbin/busybox
chmod 04755 /system/xbin/busybox
/system/xbin/busybox --install -s /system/xbin
rm -r /data/local/tmp/busybox
[COLOR="DarkSlateBlue"]Hit CTRL+C to exit again from adb shell[/COLOR]
adb push c:\DoomLordRoot.v3\files\su /system/bin/su
[COLOR="DarkSlateBlue"]adb shell[/COLOR]
su
chown root.shell /system/bin/su
chmod 06755 /system/bin/su
rm /system/xbin/su
ln -s /system/bin/su /system/xbin/su
[COLOR="DarkSlateBlue"]Hit CTRL+C to exit once more from adb shell[/COLOR]
adb push c:\DoomLordRoot.v3\files\Superuser.apk /system/app/
[COLOR="DarkSlateBlue"]adb shell[/COLOR]
su
cd /data/local/tmp/
rm *
reboot
This is basic what the runme.bat file does, just some paths corrected to point to the right locations.
I have the latest official gingerbread (I think v3) and have been trying to root with no luck. I've gone through the steps here but when try to get root access (su), it gives me permission denied...
Any ideas?
Oneclickroot v2. 2 did the work for me or something like this
Sent from my U8800
SS said:
I have the latest official gingerbread (I think v3) and have been trying to root with no luck. I've gone through the steps here but when try to get root access (su), it gives me permission denied...
Any ideas?
Click to expand...
Click to collapse
This probably means that rooting failed.
What messages you get when you run zergrush?
dancer_69 said:
This probably means that rooting failed.
What messages you get when you run zergrush?
Click to expand...
Click to collapse
I got messages for sending 149, then 189 zerglings, then messages about not being able to mount, find or write to directories.
It seems like it wasn't able to get root access to be able to run its process.
In any case, I just downgraded to the previous release and then used ZergRush, which worked perfectly
don't work.
try this, it works for my B528 rom!
http://forum.xda-developers.com/showpost.php?p=23565074&postcount=7

[Q] About root Motorola RAZR 201M(XT902)

Hello everyone...
I have a Motorola RAZR 201M(XT902) in Japan and use Motofail2go to root it.But it doesn't work.
(follow http://forum.xda-developers.com/showthread.php?p=32889627)
I installed Sudoku.apk and push the motofail2go to the device(also su,Superuser.apk,busybox).
when
$ run-as com.motorola.bug2go /data/local/tmp/motofail2go prep2
Here is the error message:
"run-as: exec failed for /data/local/tmp/motofail2go Error: Operation not permitted"
and i try $ run-as com.motorola.bug2go
but error message : "run-as: exec failed"
Anyone help? Thanks...
Sorry buddy. Nothing works. We 201m users are SOL.
Have you tried this?
http://www.droidrzr.com/index.php/topic/15208-root-motochopper-yet-another-android-root-exploit/
Thanks Paul!
No luck with that either. Appreciate the feedback, however.
I hope somebody will study the XT902 root.
goodayoo said:
I hope somebody will study the XT902 root.
Click to expand...
Click to collapse
I really want this thing rooted. How do one go about figuring out how to root it? I assume because of it's lack of popularity, no one has done it, but I'm willing to do the grunt work if there's some sort of guide or assistance. I changed over to DoCoMo with the GS4 and now have this paperweight that I would want to actually use.
Thanks!
Almalieque said:
I really want this thing rooted. How do one go about figuring out how to root it? I assume because of it's lack of popularity, no one has done it, but I'm willing to do the grunt work if there's some sort of guide or assistance. I changed over to DoCoMo with the GS4 and now have this paperweight that I would want to actually use.
Thanks!
Click to expand...
Click to collapse
There some Japanese guys doing some things to try and get root. They are active. The site has a lot of rather unpleasant (read offensive) advertisements. PM if you are interested (its in Japanese)
root
help!!!
Root and Unlocked bootloaders!
Proceed at yor own risk
hungln03 said:
help!!!
Click to expand...
Click to collapse
1)Prep
Android SDKと各種ドライバを導入する。
以下の必要ファイルをC:\***(何でも良い)に配置する。
 ・XT902_SBMの中身(http://www1.axfc.net/uploader/so/2991543 >>125氏)
 ・su(http://www1.axfc.net/uploader/so/2918729 password:f10d)
 ・Superuser.apk(in the above downloaded)
 ・busybox(in the above downnloaded)
201M Plug the phone into the comp
any port will do
2)adb pushで必要ファイルを/data/local/tmp転送
コマンドプロンプトを開く
C:\Users\(ユーザー名) >cd C:\***
adb push su /data/local/tmp
adb push Superuser.apk /data/local/tmp
adb push busybox /data/local/tmp
adb push unlock_security_module /data/local/tmp
adb push break_setresuid /data/local/tmp/
adb push mole-plough-ccsecurity.so /data/local/tmp/
adb push mole-plough-lsm.so /data/local/tmp/
3)unlock_security_module(temp root)
adb shell
[email protected]:/ $ cd /data/local/tmp/
[email protected]:/data/local/tmp $ chmod 777 *
[email protected]:/data/local/tmp $ ./unlock_security_module
[email protected]:/data/local/tmp $ ./break_setresuid
(unlock_security_moduleが動いてMIYABIとNANDロック解除)
 (色々表示されるので↓が出る間で待つ)
 Unlocked LSM.
 Do setresuid...
 OK.
 [email protected]:/data/local/tmp #
 (#if done correctly temp root should be achieved)
271 :270:2013/09/15(日) 23:31:42.67 ID:tIg7fkl6
4)system putting together su,Superuser.apk,busybox
[email protected]:/data/local/tmp # mount -o rw,remount /system /system
[email protected]:/data/local/tmp # cat /data/local/tmp/su > /system/xbin/su
[email protected]:/data/local/tmp # cat /data/local/tmp/busybox > /system/xbin/busybox
[email protected]:/data/local/tmp # cat /data/local/tmp/Superuser.apk > /system/app/Superuser.apk
[email protected]:/data/local/tmp # chmod 644 /system/app/Superuser.apk
[email protected]:/data/local/tmp # cd /system/xbin
[email protected]:/system/xbin # chown root.root su
[email protected]:/system/xbin # chown root.root busybox
[email protected]:/system/xbin # chmod 6755 su
[email protected]:/system/xbin # chmod 755 busybox
[email protected]:/system/xbin # mount -o ro,remount /system /system
After the opperation is done it is ok to remove the cable from the pc。
check and see if「SuperSU」was installed if it wasn't download chainfire (su) from the play store
⇒SU --> update
Fro the play store download busybox。
⇒busybox -->update
Get the right CWM.img http://forum.xda-developers.com/showthread.php?t=2298521の201M
put the CWM.img you downloaded in motoapoc file you find here
adb push unlock /data/local/tmp/
adb shell chmod 755 /data/local/tmp/unlock
adb shell
cd /data/local/tmp/
chmod 777 *
./unlock_security_module
./break_setresuid
./unlock
New Command prompt
5)Inserting CWM(PC Operation)
adb shell "su -c 'mount -o remount,rw /system'"
adb shell "su -c 'mv /system/etc/install-recovery.sh /system/etc/install-recovery.bak'"
adb shell "su -c 'mv /system/recovery-from-boot.p /system/recovery-from-boot.bak'"
adb push cwm.img /data/local/tmp/cwm.img > nul
adb shell "su -c 'dd if=/data/local/tmp/cwm.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery'"
adb shell "su -c 'rm /data/local/tmp/cwm.img'"
adb reboot recovery
You should be in CWM
Cheers! I take 0 credit. Long Live the Developers!!
I don't own the 902, but it's good to see this. I know quite a few people have been looking for this. You should start your own thread with the procedures, so it will get more publicity.
Thank u!
thank u so much.!1
sbeaber4 said:
Proceed at yor own risk
271 :270:2013/09/15(日) 23:31:42.67 ID:tIg7fkl6
Get the right CWM.img http://forum.xda-developers.com/showthread.php?t=2298521の201M
put the CWM.img you downloaded in motoapoc file you find here
adb push unlock /data/local/tmp/
adb shell chmod 755 /data/local/tmp/unlock
adb shell
cd /data/local/tmp/
chmod 777 *
./unlock_security_module
./break_setresuid
./unlock
New Command prompt
5)Inserting CWM(PC Operation)
adb shell "su -c 'mount -o remount,rw /system'"
adb shell "su -c 'mv /system/etc/install-recovery.sh /system/etc/install-recovery.bak'"
adb shell "su -c 'mv /system/recovery-from-boot.p /system/recovery-from-boot.bak'"
adb push cwm.img /data/local/tmp/cwm.img > nul
adb shell "su -c 'dd if=/data/local/tmp/cwm.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery'"
adb shell "su -c 'rm /data/local/tmp/cwm.img'"
adb reboot recovery
You should be in CWM
Cheers! I take 0 credit. Long Live the Developers!!
Click to expand...
Click to collapse
Can you tell me more about this step
Confirm?
Can confirm if the latest instructions have worked for your 201m?
That your rooted and bootloader unlock.
Thanks a bunch!
Boot loader is unlocked and CWM is installed. Initially I still
Had temp root so I flashed slim beans xt907 rom. It works. I'm unable to test data with it as I don't have a SoftBank sim. Also I still can't connect to the play store.
sbeaber4 said:
Boot loader is unlocked and CWM is installed. Initially I still
Had temp root so I flashed slim beans xt907 rom. It works. I'm unable to test data with it as I don't have a SoftBank sim. Also I still can't connect to the play store.
Click to expand...
Click to collapse
Thanks for the feedback.
Still awaiting more confirmation with others. It's a step forward though.
I've had my phone for almost a year now. If I cancel my softbank service or run the contract to the end I want an option to root and unlock the bootloader in the future.
could u provide more friendly filehost?
i can't find the download button there
Root! (temp root that is...)
I'm just posting to confirm I've rooted my 201m (xt902).
Props to sbeaber4!
From my limited knowledge since it's temp root if I restart my phone I lose root access...
Next step in the future unlock bootloader.
Peace y'all.
Quick Tip
zenstarlight said:
I'm just posting to confirm I've rooted my 201m (xt902).
Props to sbeaber4!
From my limited knowledge since it's temp root if I restart my phone I lose root access...
Next step in the future unlock bootloader.
Peace y'all.
Click to expand...
Click to collapse
Found that if I a did restart my phone root was lost but I found a quick fix without going through the whole process again.
Just do these steps
unlock_security_module(temp root)
adb shell
[email protected]:/ $ cd /data/local/tmp/
[email protected]:/data/local/tmp $ ./unlock_security_module
Just enter those three steps then you're back to temp root
Also you can just to a quick reboot with link2sd or any other app that just reboots the android ui. You don't have to enter commands every time you reboot unless it's a full reboot.
Help for Gaigin rooting 201M
sbeaber4 said:
Proceed at yor own risk
...
You should be in CWM
Cheers! I take 0 credit. Long Live the Developers!!
Click to expand...
Click to collapse
Noob on XDA, and rooted a MT4G in the past wth help from these forums.
Can someone help translate the kanji for rooting the 201M? Will rooting allow you to change the device location and prevent random all Japanese pop-up alerts/"are you sure" messages? Thanks for any help
kprower said:
Noob on XDA, and rooted a MT4G in the past wth help from these forums.
Can someone help translate the kanji for rooting the 201M? Will rooting allow you to change the device location and prevent random all Japanese pop-up alerts/"are you sure" messages? Thanks for any help
Click to expand...
Click to collapse
Once CWM is online you might be able to flash a VZW or Aussie stock ROM. Actually, you could probably flash CM... That'll fix the Japanese popups. Of course, it also could very possibly brick it. Proper precautions must be made... On my tablet at the moment, does anyone know if sbf.droid-developers has 902 images?
Sent from my Nexus 7 using Tapatalk 4

Root Lollipop for Xperia tablet Z & add SuperSU without downgrading to Kitkat + ftf

Root Lollipop for Xperia tablet Z & add SuperSU without downgrading to Kitkat + ftf
** DISCLAIMER: I AM NOT A DEVELOPER. I DO THIS AS A HOBBY AND SHARE MY FINDINGS IN CASE SOMEONE ELSE FINDS THEM USEFUL. **
** THIS WORKED ON MY DEVICE BUT IT MAY NOT WORK ON YOURS. APPLY AT YOUR OWN RISK **​
You don't need to have root to apply this procedure. Your bootloader doesn't have to be unlocked.
This has been tested with SGP311, 10.6.A.0.454, Lollipop 5.0.2, Customized TW version, but it should work fine on any other customization of 10.6.A.0.454.
This procedure installs superSU root binaries and busybox on your system.
Requirements
1- Upgrade to Lollipop 5.0.2. Either flash an ftf using flashtool or if you are in a region where the update is available take the OTA. You can get the unmodified Customized TW version from here.
2- Make sure your PC can communicate with your tablet via adb.
The success of this method depends on following the procedure very carefully. So read the instructions and make sure you understand every step before you try it.
Procedure
1- Install and run Kingroot 4.0. You can google and download it or you can use the one in the attached zip file. When Kingroot runs it is all in Chinese, but basically you need to be connected to the internet for it to work. It will do its thing and show progress up to 100% after which you can exit the program. Now your phone is rooted. The following steps replaces the Kinguser with SuperSU.
2- Unzip the attached file in your adb directory and then open an adb terminal and make sure the PC can see your phone (you can check that by typing adb devices). Then type the following:
Code:
adb push su /data/local/tmp
adb push busybox /data/local/tmp
adb shell
3- In the shell that you get type the following and make sure you give the access permission when the tablet prompts you:
Code:
su
4- Continue by typing the following commands:
Code:
mount -o remount,rw /system
cat /data/local/tmp/su >/system/xbin/daemonsu && chmod 0755 /system/xbin/daemonsu
cat /data/local/tmp/busybox >/system/xbin/busybox && chmod 0755 /system/xbin/busybox
daemonsu -d &
The key is to keep this session running while you continue with the rest, so be careful with typos and monitor this window for any errors.
5- At this point, leave the adb terminal window running and go to your tablet, open the Kinguser app, open settings (the wheel at the top right corner of the screen), Root authorization setting, and Remove Root permission. The app may self-uninstall.
6- In any case, after this is done, uninstall the two or three remaining Kingroot apps that are still on your tablet (Kinguser, KingRoot, and the other one with the blue icon and Chinese text under it).
7- Back to the adb terminal, and type the following:
Code:
cat /data/local/tmp/su > /system/xbin/su && chmod 0755 /system/xbin/su
busybox chattr -ia /system/xbin/ku.sud
busybox chattr -ia /system/xbin/supolicy
busybox chattr -ia /system/xbin/pidof
rm /system/xbin/ku.sud
rm /system/xbin/supolicy
rm /system/xbin/pidof
rm /system/bin/debuggerd
mv /system/bin/debuggerd_real /system/bin/debuggerd
rm /system/bin/debuggerd64
busybox chattr -ia /system/bin/install-recovery.sh
busybox chattr -ia /system/bin/rt.sh
rm /system/bin/install-recovery.sh
rm /system/bin/rt.sh
busybox chattr -ia /system/bin/.usr/.ku
rm -rf /system/bin/.usr
rm /system/usr/icu/icusuflag.conf
busybox chattr -ia /system/usr/iku/isu
rm -rf /system/usr/iku
rm /system/kroot_*
rm /sdcard/kr-stock-conf
rm -rf /sdcard/Kingroot
rm -rf /data/data-lib/com.kingroot.RushRoot
rm -rf /data/data-lib/com.kingroot.kinguser
rm -rf /data/data-lib/king
Again, leave the adb terminal window running and go to your tablet.
8- Install superSU (from the attached file) on your phone, run it, and let it update the SU binary.
9- Reboot the tablet. After about 5 minutes your root is ready.
Troubleshooting
If you get this error: "can't stat /system/bin/debuggerd no such file or directory" the solution is here: http://forum.xda-developers.com/showpost.php?p=61386604&postcount=31
Download link
http://forum.xda-developers.com/attachment.php?attachmentid=3307248&d=1431343293
najoor said:
When Kingroot runs it is all in Chinese, but basically you need to be connected to the internet for it to work.
Click to expand...
Click to collapse
KingRoot is China's most popular one-click Android root tool, now translated in English and ready to serve you.
XDA Forum: KINGROOT: The One-Click Root Tool for Almost All Devices
Upgraded last night & was waiting for someone to post a guide. Thanks for the hard work! So happy to uninstall all of the built-in sony bloatware!
If I remember correctly after rooting the device all you have to do is install supersu and open it. It will prompt you to remove the Chinese root app and everything will be done automatically. Please correct me if this is not the case.
Thanks so much! Very easy to follow
botsaris said:
If I remember correctly after rooting the device all you have to do is install supersu and open it. It will prompt you to remove the Chinese root app and everything will be done automatically. Please correct me if this is not the case.
Click to expand...
Click to collapse
Yes, I guess this method will work. I'd used kingroot before and SuperSU get rid of it. I haven't tried it in lollipop but i guess it will work.
botsaris said:
If I remember correctly after rooting the device all you have to do is install supersu and open it. It will prompt you to remove the Chinese root app and everything will be done automatically. Please correct me if this is not the case.
Click to expand...
Click to collapse
donedos said:
Yes, I guess this method will work. I'd used kingroot before and SuperSU get rid of it. I haven't tried it in lollipop but i guess it will work.
Click to expand...
Click to collapse
King root 4 does not let you or supersu or anyone else remove or touch it unless you relinquish root privilege. Otherwise what would be the point of such a long post like this?!
najoor said:
** DISCLAIMER: I AM NOT A DEVELOPER. I DO THIS AS A HOBBY AND SHARE MY FINDINGS IN CASE SOMEONE ELSE FINDS THEM USEFUL. **
** THIS WORKED ON MY DEVICE BUT IT MAY NOT WORK ON YOURS. APPLY AT YOUR OWN RISK **​
You don't need to have root to apply this procedure. Your bootloader doesn't have to be unlocked.
This has been tested with SGP311, 10.6.A.0.454, Lollipop 5.0.2, Customized TW version, but it should work fine on any other customization of 10.6.A.0.454.
This procedure installs superSU root binaries and busybox on your system.
Requirements
1- Upgrade to Lollipop 5.0.2. Either flash an ftf using flashtool or if you are in a region where the update is available take the OTA. You can get the unmodified Customized TW version from here.
2- Make sure your PC can communicate with your tablet via adb.
The success of this method depends on following the procedure very carefully. So read the instructions and make sure you understand every step before you try it.
Procedure
1- Install and run Kingroot 4.0. You can google and download it or you can use the one in the attached zip file. When Kingroot runs it is all in Chinese, but basically you need to be connected to the internet for it to work. It will do its thing and show progress up to 100% after which you can exit the program. Now your phone is rooted. The following steps replaces the Kinguser with SuperSU.
2- Unzip the attached file in your adb directory and then open an adb terminal and make sure the PC can see your phone (you can check that by typing adb devices). Then type the following:
Code:
adb push su /data/local/tmp
adb push busybox /data/local/tmp
adb shell
3- In the shell that you get type the following and make sure you give the access permission when the tablet prompts you:
Code:
su
4- Continue by typing the following commands:
Code:
mount -o remount,rw /system
cat /data/local/tmp/su >/system/xbin/daemonsu && chmod 0755 /system/xbin/daemonsu
cat /data/local/tmp/busybox >/system/xbin/busybox && chmod 0755 /system/xbin/busybox
daemonsu -d &
The key is to keep this session running while you continue with the rest, so be careful with typos and monitor this window for any errors.
5- At this point, leave the adb terminal window running and go to your tablet, open the Kinguser app, open settings (the wheel at the top right corner of the screen), Root authorization setting, and Remove Root permission. The app may self-uninstall.
6- In any case, after this is done, uninstall the two or three remaining Kingroot apps hat are still on your tablet (Kinguser, KingRoot, and the other one with the blue icon and Chinese text under it).
7- Back to the adb terminal, and type the following:
Code:
cat /data/local/tmp/su > /system/xbin/su && chmod 0755 /system/xbin/su
busybox chattr -ia /system/xbin/ku.sud
busybox chattr -ia /system/xbin/supolicy
busybox chattr -ia /system/xbin/pidof
rm /system/xbin/ku.sud
rm /system/xbin/supolicy
rm /system/xbin/pidof
rm /system/bin/debuggerd
rm /system/bin/debuggerd_real
rm /system/bin/debuggerd64
busybox chattr -ia /system/bin/install-recovery.sh
busybox chattr -ia /system/bin/rt.sh
rm /system/bin/install-recovery.sh
rm /system/bin/rt.sh
busybox chattr -ia /system/bin/.usr/.ku
rm -rf /system/bin/.usr
rm /system/usr/icu/icusuflag.conf
busybox chattr -ia /system/usr/iku/isu
rm -rf /system/usr/iku
rm /system/kroot_*
rm /sdcard/kr-stock-conf
rm -rf /sdcard/Kingroot
Again, leave the adb terminal window running and go to your tablet.
8- Install superSU (from the attached file) on your phone, run it, and let it update the SU binary.
9- Reboot the tablet. After about 5 minutes your root is ready.
Download link
http://forum.xda-developers.com/attachment.php?attachmentid=3307248&d=1431343293
Click to expand...
Click to collapse
thank you for your hard work .
but it has a problem .
at first type "adb push su /data/local/tmp" ,the KingRoot was allow "root", and then conlose was promot "error: device unauthorized. Please check the confirmation dialog on your device."
need retype "adb push su /data/local/tmp" .
and goon.
中文看这里:
http://bbs.gfan.com/android-7970307-1-1.html
@najoor :
Thanks - worked fine for me :good:
Thank you very much, works perfectly
Thanks a million bro.. works like a charm on Xperia Z 5.0.2!!
Wow , thats bro. Still expecting the lollipop for my c6603
What's wrong with just using King Root for root access instead of SuperSU?
Not working for me... tablet reboots on remount system as rw
Does this method work with SGP321?
Thank you for the tutorial. SuperSU works flawless on my SGP311.
Total time: 10 minutes :good:
I managed to root my Xperia Z (C6602) by following these instructions
najoor said:
** DISCLAIMER: I AM NOT A DEVELOPER. I DO THIS AS A HOBBY AND SHARE MY FINDINGS IN CASE SOMEONE ELSE FINDS THEM USEFUL. **
** THIS WORKED ON MY DEVICE BUT IT MAY NOT WORK ON YOURS. APPLY AT YOUR OWN RISK **​
You don't need to have root to apply this procedure. Your bootloader doesn't have to be unlocked.
This has been tested with SGP311, 10.6.A.0.454, Lollipop 5.0.2, Customized TW version, but it should work fine on any other customization of 10.6.A.0.454.
This procedure installs superSU root binaries and busybox on your system.
Requirements
1- Upgrade to Lollipop 5.0.2. Either flash an ftf using flashtool or if you are in a region where the update is available take the OTA. You can get the unmodified Customized TW version from here.
2- Make sure your PC can communicate with your tablet via adb.
The success of this method depends on following the procedure very carefully. So read the instructions and make sure you understand every step before you try it.
Procedure
1- Install and run Kingroot 4.0. You can google and download it or you can use the one in the attached zip file. When Kingroot runs it is all in Chinese, but basically you need to be connected to the internet for it to work. It will do its thing and show progress up to 100% after which you can exit the program. Now your phone is rooted. The following steps replaces the Kinguser with SuperSU.
2- Unzip the attached file in your adb directory and then open an adb terminal and make sure the PC can see your phone (you can check that by typing adb devices). Then type the following:
Code:
adb push su /data/local/tmp
adb push busybox /data/local/tmp
adb shell
3- In the shell that you get type the following and make sure you give the access permission when the tablet prompts you:
Code:
su
4- Continue by typing the following commands:
Code:
mount -o remount,rw /system
cat /data/local/tmp/su >/system/xbin/daemonsu && chmod 0755 /system/xbin/daemonsu
cat /data/local/tmp/busybox >/system/xbin/busybox && chmod 0755 /system/xbin/busybox
daemonsu -d &
The key is to keep this session running while you continue with the rest, so be careful with typos and monitor this window for any errors.
5- At this point, leave the adb terminal window running and go to your tablet, open the Kinguser app, open settings (the wheel at the top right corner of the screen), Root authorization setting, and Remove Root permission. The app may self-uninstall.
6- In any case, after this is done, uninstall the two or three remaining Kingroot apps hat are still on your tablet (Kinguser, KingRoot, and the other one with the blue icon and Chinese text under it).
7- Back to the adb terminal, and type the following:
Code:
cat /data/local/tmp/su > /system/xbin/su && chmod 0755 /system/xbin/su
busybox chattr -ia /system/xbin/ku.sud
busybox chattr -ia /system/xbin/supolicy
busybox chattr -ia /system/xbin/pidof
rm /system/xbin/ku.sud
rm /system/xbin/supolicy
rm /system/xbin/pidof
rm /system/bin/debuggerd
rm /system/bin/debuggerd_real
rm /system/bin/debuggerd64
busybox chattr -ia /system/bin/install-recovery.sh
busybox chattr -ia /system/bin/rt.sh
rm /system/bin/install-recovery.sh
rm /system/bin/rt.sh
busybox chattr -ia /system/bin/.usr/.ku
rm -rf /system/bin/.usr
rm /system/usr/icu/icusuflag.conf
busybox chattr -ia /system/usr/iku/isu
rm -rf /system/usr/iku
rm /system/kroot_*
rm /sdcard/kr-stock-conf
rm -rf /sdcard/Kingroot
Again, leave the adb terminal window running and go to your tablet.
8- Install superSU (from the attached file) on your phone, run it, and let it update the SU binary.
9- Reboot the tablet. After about 5 minutes your root is ready.
Download link
http://forum.xda-developers.com/attachment.php?attachmentid=3307248&d=1431343293
Click to expand...
Click to collapse
I managed to ROOT & replace the KingRoot with my favorite root manager app SuperSU in my Xperia Z (C6602) running Android 5.0.2 (10.6.A.0.454) by following the above instructions. You are awesome man..
Thanks a lot.
I swapped Kingroot for superSU with your instructions, thank you.
But I have the same question, especially when there is an eglish version of Kingroot.
SickBeast said:
What's wrong with just using King Root for root access instead of SuperSU?
Click to expand...
Click to collapse
JulianK87 said:
I swapped Kingroot for superSU with your instructions, thank you.
But I have the same question, especially when there is an eglish version of Kingroot.
Click to expand...
Click to collapse
I heard many people facing random reeboot issue while any app requests su access and superSU works fine for them as a replacement.
Sent from my C6602 using xda Forums PRO
TiBckUp does not work well with KR
Sent from my VGN-NS10J_S using Tapatalk

Manual method of adbd Insecure

This method is similar to Chainfire's adbd Insecure, I tried Chainfire method, adb wireless didn't work for me, so I made my own, I needed to use adb wireless on some devices.
I made this adbd for my BLU Studio 5.0 C Cell phone, but I am sure it will work for other arm devices.
Anyway long story short, you need a rooted device, you push a script and an adbd file to /system/xbin then you add a line to /etc/install-recovery.sh to load the script each boot.
To install download replace_adbd.zip
extract zip place all three files on sdcard, and use rooted file manager to copy them to to their correct places, or use adb.
adb shell
mount -o rw,remount /system
adb push adbd /system/xbin/adbd
adb push adbd-Insecure /system/xbin/adbd-Insecure
adb push install-recovery.sh /system/etc/install-recovery.sh
adb shell
chmod 755 /system/xbin/adbd
chmod 755 /system/xbin/adbd-Insecure
chmod 755 /system/etc/install-recovery.sh
reboot
Or use file manager like ES File Explorer File Manager to copy files from sdcard to correct place and set permission then reboot.
https://www.androidfilehost.com/?fid=24052804347763661
#
# ADDITIONAL_DEFAULT_PROPERTIES
#
ro.secure=1
ro.allow.mock.location=0
persist.mtk.aee.aed=on
ro.debuggable=0
ro.adb.secure=1
persist.sys.usb.config=mtp,adb
persist.service.acm.enable=0
ro.mount.fs=EXT4
ro.persist.partition.support=no
[email protected] STUDIO 5.0 C:/ #
credits
@carliv for CarlivScreenshot
http://forum.xda-developers.com/android/development/tool-carlivscreenshot-screenshots-t3075992
@Chainfire for the ideal of making adbd insecure
http://forum.xda-developers.com/showthread.php?t=1687590
Download link didn't sync correctly, file was corrupt first link, I have now changed the link, this one should now work correctly.
Thanks, I will test on my device and report back. I've always wanted some manual way instead of using the app.
@vampirefo
Is it possible to integrate in your batch the latest version of adbd demon get from adb insecuere 2.0.apk?
Is it possible to check the adbd version? How to?
Is it possible to create a dos batch with all need commands via adb commands? Like
adb shell mount -o rw,remount /system
adb push adbd /system/xbin/adbd
adb push adbd-Insecure /system/xbin/adbd-Insecure
adb shell cp /system/etc/install-recovery.sh /system/etc/install-recovery.sh.old
adb push install-recovery.sh /system/etc/install-recovery.sh
adb shell chmod 755 /system/xbin/adbd
adb shell chmod 755 /system/xbin/adbd-Insecure
adb shell chmod 755 /system/etc/install-recovery.sh
adb reboot
Thanks.
bovirus said:
@vampirefo
Is it possible to integrate in your batch the latest version of adbd demon get from adb insecuere 2.0.apk?
Is it possible to check the adbd version? How to?
Is it possible to create a dos batch with all need commands via adb commands? Like
adb shell mount -o rw,remount /system
adb push adbd /system/xbin/adbd
adb push adbd-Insecure /system/xbin/adbd-Insecure
adb shell cp /system/etc/install-recovery.sh /system/etc/install-recovery.sh.old
adb push install-recovery.sh /system/etc/install-recovery.sh
adb shell chmod 755 /system/xbin/adbd
adb shell chmod 755 /system/xbin/adbd-Insecure
adb shell chmod 755 /system/etc/install-recovery.sh
adb reboot
Thanks.
Click to expand...
Click to collapse
Yes, one can use the adbd binary from adb insecure 2.0.apk.
There isn't any version number to check, we both just build the adbd binary from source, mine was built from CM 12.1 source, not sure about chainfire's.
Chainfire's may have used AOSP source.
Yes one can create a Windows batch file, to execute the adb commands, or create a flashable zip, provided the devices has a custom recovery.
Sent from my Venue 8 3830 using Tapatalk

Categories

Resources