Related
There's already a guide here for obtaining permanent root using VISIONary, but some folks in #G2ROOT are having issues with the way that VISIONary modifies parititons. Using rage directly is a bit cleaner, since you know exactly what it's going to touch at each step of the way. I did NOT come up with any of this on my own, I'm building completely off of work that others have done. Speaking of which-
None of this would be possible without the tireless work that scotty2 put in. He stayed with the project for well over a month, through lots of smashed hopes and dead ends, until the solution was finally found. Were it not for his work, as well as the help of a few other key folks- we wouldn't be here. He deserves our thanks and some donations! We're talking hundreds of hours of work here, a couple bucks is not too much for that. His paypal is:
[email protected]Send him some love! I'm not asking for anything myself, because I spent a half hour putting this together, and that doesn't deserve any donations!
[size=+2]G2 ROOT INSTRUCTIONS[/size]
=================================================
These are modified instructions based on the ones posted at http://bit.ly/g2root that use Visionary. A number of people have run into issues with the way that Visionary juggles around temporary partitions, and using the original root exploit is a much easier, and cleaner method for achieving permanent root. This tutorial will walk you through the rooting process by first achieving temporary root, and moving on to permanent root.
[size=+1]REQUIREMENTS[/size]
=================================================
Visionary disabled at boot or uninstalled completely
Android Terminal Emulator app
ADB
vision-combined-root.zip (Attached to this post, OR these two files: )
G2TempRoot.zip (http://forum.xda-developers.com/showthread.php?t=797042) NOTE: only download the files! Don't follow these instructions yet
vision-perm-root.zip (http://forum.xda-developers.com/showthread.php?t=833965) NOTE: again, just download the files from the thread.
In the commands to run below, $ or # represent the prompt and should NOT be entered as part of the commands.
[size=+2]VERY IMPORTANT![/size]Visionary has caused filesystem corruption for some users during the rooting process. Before attempting the instructions below, make sure that you have "auto run on boot" turned OFF, and reboot your system. Since you will not need visionary anyway after this, you might as well just uninstall visionary and reboot NOW before doing anything.
[size=+1]TEMP ROOT[/size]
=================================================
ON YOUR PC:
Unzip the G2TempRoot files to a folder. From a cmd window or terminal, navigate to that folder and execute these commands:
Code:
$ adb push su /sdcard/su
$ adb push Superuser.apk /sdcard/Superuser.apk
$ adb push rage /data/local/tmp/rage
$ adb push busybox /data/local/tmp/busybox
$ adb push root /data/local/tmp/root
$ adb shell chmod 0755 /data/local/tmp/*
ON YOUR PHONE:
Launch Terminal Emulator
/data/local/tmp/rage
Wait for the message: "Forked #### childs."
Menu > Reset Term - Terminal Emulator will exit.
Launch Terminal Emulator, it Force Closes. Launch a second time, and you'll have a root shell
**NOTE**: in the original directions from the XDA thread, you are instructed to run the /data/local/tmp/root script here. DON'T do this
just yet. Leave the terminal window open.
[size=+1]PERM ROOT[/size]
=================================================
ON YOUR PC:
unzip the vision-perm-root.zip and navigate to that folder. There will be four files. You will need to push two of these to your phone- hboot-eng.img, and one of the wpthis-[..].ko files.
If you HAVE applied the OTA update, push wpthis-OTA.ko.
If you HAVE NOT applied the OTA update, push wpthis-pre-OTA.ko.
Code:
$ adb push hboot-eng.img /data/local
$ adb push wpthis-OTA.ko /data/local
ON YOUR PHONE:
You should still have terminal emulator up, at a root prompt. Now run:
Code:
# insmod /data/local/wpthis-OTA.ko
You should see:
Code:
init_module 'wpthis-OTA.ko' failed (Function not implemented)
That means it worked. This next step is CRUCIAL. You must make sure that you are writing to the proper partition here or you could brick your phone. To be absolutely clear- the partition is mmcblk(zero)p(one)(eight)
Code:
dd if=/data/local/hboot-eng.img of=/dev/block/mmcblk0p18
You should see some messages indicating that it was written. Next, run:
Code:
# /data/local/tmp/root
This will lock in root, and give you 'su' access in the future. Next, run:
Code:
# sync
Now wait at least a minute, just to be safe. After waiting, reboot your phone using the power button. After it finishes starting up, launch the terminal emulator, and type 'su'. You should get the prompt asking you to grant permissions. If you got the prompt, congratulations! You have permanent root!
I used these instructions and they worked brilliantly.
Sounds like it's a little safer than using VISIONary, which some people in the thread are reporting can get confused and not let you root because it thinks you already have root, etc.
I love it when a plan comes together. Perma-root. thanks man, i never had much luck getting visonary to work so this was spot on. worked like a charm
*not smart enough*
*leaves thread*
I really try to leave ADB out of the equation since I'm not comfortable navigating it.... I suppose I could dedicate my time to learning it, but it's not worth it since I would only use it once every two years to root my phone. In 16 hours I'm sure there will probably be a one click perm root method out anyway.
It worked flawlessly!
I always get so stressed when I root my phones, especially without tutorial vids.
I first did my G1 and that worked perfectly fine.
My second attempt at rooting was with my MT3G and that resulted in a bricked device because one of the lines of code was incorrect in the thread.
This, however, was clearly and plainly spelled out exactly to what happened to my phone.
I give you my thanks.
Awesome- glad to hear it's working well for people. If anybody sees areas that I could improve in the description just let me know.
sinistersai4d4d said:
I really try to leave ADB out of the equation since I'm not comfortable navigating it....
Click to expand...
Click to collapse
ADB is worth it IMHO because it makes moving files around easy, whether you're rooted or not. You don't have to turn on SD card storage, you can just do adb pull/push etc to grab or put files when you need them. Worth the effort. The one click root should be out within the next couple days though, you are right about that one.
trigeek,
I already perm rooted earlier, but just wanted to say you gave a very nicely detailed explanation that anyone should be able to follow. Well done!
Great guide. I liked it a lot more than Unforgivens just because it doesn't rely on VisionARY which might mess things up.
Guide worked absolutely great, no problems. I did not try the visionary method first, but for some reason I just felt safer doing it in adb.
Thank you!
Sorry for the noob question...? but does this mean we have fully rooted to G2 and now we can load ROMS on it when they come out ????
Edit: Nevermind I didnt see the sticky
RaffieKol said:
Sorry for the noob question...? but does this mean we have fully rooted to G2 and now we can load ROMS on it when they come out ????
Click to expand...
Click to collapse
You got it!
RaffieKol said:
Sorry for the noob question...? but does this mean we have fully rooted to G2 and now we can load ROMS on it when they come out ????
Edit: Nevermind I didnt see the sticky
Click to expand...
Click to collapse
Custome ROMs, custom Recovery...the whole 9 yards
Thanks for posting this, it was so easy!
Thank you so very much it was a success
this is my first rooting on an android device... im freaking out... but here i go.... if something happens i will just report my phone lost and get a new one i guess ahahah still... im scared.
Issues
I was temp rooted before using rage and then thru Visionary. But I decided to go back to stock till we have permanent root. I perm rooted today using this method. But I'm having the following issues:
1) adb remount
- remount failed: Operation not permitted
2) when using Root Explorer in /system, toggling Mount R/W does not work
- the only way to mount it R/O is thru terminal/adb shell. Once mounted R/O, the only way to mount R/W again is thru a reboot. Issuing mount -o remount ro /system either in terminal or adb shell does not work.
i actually changed my mind... im going to wait for a one click untended root i guess.... to scary...
joackie27 said:
I was temp rooted before using rage and then thru Visionary. But I decided to go back to stock till we have permanent root. I perm rooted today using this method. But I'm having the following issues:
1) adb remount
- remount failed: Operation not permitted
2) when using Root Explorer in /system, toggling Mount R/W does not work
- the only way to mount it R/O is thru terminal/adb shell. Once mounted R/O, the only way to mount R/W again is thru a reboot. Issuing mount -o remount ro /system either in terminal or adb shell does not work.
Click to expand...
Click to collapse
make sure you have debugging enabled.
juanshop said:
i actually changed my mind... im going to wait for a one click untended root i guess.... to scary...
Click to expand...
Click to collapse
Not gonna happen.
then i guess.... im going to jump in it.... wish me luck...
So after 7 attempts, i decided i should seek help.
I've been trying to root my g2 using VISIONary r14.
1. I installed visionary r14 [i have usb debugging on] i leave all the check boxes unchecked and hit temp root
2. after temp root is finished, i hit attempt perm root.
phone reboots. i see superuser permission in the app drawer, all seems to be
fine.
3. Now I plug my phone to my PC via usb [i have the androidSDK and all drivers installed properly]
i change directory to C:\AndroidSDK\tools\
check adb devices and my device is listed.
then i shoot the following commands
adb push wpthis-OTA.ko /data/local/wpthis-OTA.ko
adb push hboot_7230_0.84.2000_100908.nb0/data/local/hboot_7230_0.84.2000_100908.nb0
adb shell
su
and this returns permission denied.
Ive searched everywhere and everyone says when the superuser prompt shows up check "Remember" and click yes. However this does not show up for me, at all.
I even go into terminal and try it, terminal also gives me 'Permission Denied'
any help anyone?
I'd just do it using the rage method. You obviously understand how to use some simple commands in adb, it's just that there's a few (read: not many) more. It's stickied in the development section.
Sent from my T-Mobile G2 running Cyanogenmod.
Yes rage way is the way to go. I think its a total of about 4 lines you need to enter
Sent from my HTC Vision using XDA App
yeah i ended up using the rage method, it was a lot easier than i thought it would be.
I did it using visionary r13 and terminal emulator. No pc. Go to youtube look up Blackprince310 he made a video on it. If it it doesn't work try permroot option on r13.
Sent from my T-Mobile G2 using XDA App
I would love to go the rage way, but I cannot get any permissions to do so...
Visionary r14 gives me a parsing error and does not install....
I've spent about 8 hours today trying to get this done!!! sigh!
Crey23 said:
I would love to go the rage way, but I cannot get any permissions to do so...
Visionary r14 gives me a parsing error and does not install....
I've spent about 8 hours today trying to get this done!!! sigh!
Click to expand...
Click to collapse
What steps have you taken? The rage way does not require visionary at all.
Sent from my HTC Vision using XDA App
shortlived said:
What steps have you taken? The rage way does not require visionary at all.
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
right!!! I've been sitting at my pc for about 8 or 9 hours trying to root.
I continue to get adb: permission denied message no matter what I try. I follwed the adb for dummies guide that didnt work. I tried the VISONary r14 apk, I can't even open it.....
I'm beggining to wonder if I should run recovery first, get back to stock, and then try to root....how will that affect all my apps? Will it work?
Well you can always back them up with titanium backup. But yea i think you should do a factory reset then try the rage method. Follow the guide word for word. If you still got problems post em here i will try to help as much as i can. The whole process should take around 5min.
Sent from my HTC Vision using XDA App
I dont know how to link to a post with the xda app so here is the guide quoted
trigeek said:
There's already a guide here for obtaining permanent root using VISIONary, but some folks in #G2ROOT are having issues with the way that VISIONary modifies parititons. Using rage directly is a bit cleaner, since you know exactly what it's going to touch at each step of the way. I did NOT come up with any of this on my own, I'm building completely off of work that others have done. Speaking of which-
None of this would be possible without the tireless work that scotty2 put in. He stayed with the project for well over a month, through lots of smashed hopes and dead ends, until the solution was finally found. Were it not for his work, as well as the help of a few other key folks- we wouldn't be here. He deserves our thanks and some donations! We're talking hundreds of hours of work here, a couple bucks is not too much for that. His paypal is:
[email protected]Send him some love! I'm not asking for anything myself, because I spent a half hour putting this together, and that doesn't deserve any donations!
[size=+2]G2 ROOT INSTRUCTIONS[/size]
=================================================
These are modified instructions based on the ones posted at http://bit.ly/g2root that use Visionary. A number of people have run into issues with the way that Visionary juggles around temporary partitions, and using the original root exploit is a much easier, and cleaner method for achieving permanent root. This tutorial will walk you through the rooting process by first achieving temporary root, and moving on to permanent root.
[size=+1]REQUIREMENTS[/size]
=================================================
Visionary disabled at boot or uninstalled completely
Android Terminal Emulator app
ADB
vision-combined-root.zip (Attached to this post, OR these two files: )
G2TempRoot.zip (http://forum.xda-developers.com/showthread.php?t=797042) NOTE: only download the files! Don't follow these instructions yet
vision-perm-root.zip (http://forum.xda-developers.com/showthread.php?t=833965) NOTE: again, just download the files from the thread.
In the commands to run below, $ or # represent the prompt and should NOT be entered as part of the commands.
[size=+2]VERY IMPORTANT![/size]Visionary has caused filesystem corruption for some users during the rooting process. Before attempting the instructions below, make sure that you have "auto run on boot" turned OFF, and reboot your system. Since you will not need visionary anyway after this, you might as well just uninstall visionary and reboot NOW before doing anything.
[size=+1]TEMP ROOT[/size]
=================================================
ON YOUR PC:
Unzip the G2TempRoot files to a folder. From a cmd window or terminal, navigate to that folder and execute these commands:
Code:
$ adb push su /sdcard/su
$ adb push Superuser.apk /sdcard/Superuser.apk
$ adb push rage /data/local/tmp/rage
$ adb push busybox /data/local/tmp/busybox
$ adb push root /data/local/tmp/root
$ adb shell chmod 0755 /data/local/tmp/*
ON YOUR PHONE:
Launch Terminal Emulator
/data/local/tmp/rage
Wait for the message: "Forked #### childs."
Menu > Reset Term - Terminal Emulator will exit.
Launch Terminal Emulator, it Force Closes. Launch a second time, and you'll have a root shell
**NOTE**: in the original directions from the XDA thread, you are instructed to run the /data/local/tmp/root script here. DON'T do this
just yet. Leave the terminal window open.
[size=+1]PERM ROOT[/size]
=================================================
ON YOUR PC:
unzip the vision-perm-root.zip and navigate to that folder. There will be four files. You will need to push two of these to your phone- hboot-eng.img, and one of the wpthis-[..].ko files.
If you HAVE applied the OTA update, push wpthis-OTA.ko.
If you HAVE NOT applied the OTA update, push wpthis-pre-OTA.ko.
Code:
$ adb push hboot-eng.img /data/local
$ adb push wpthis-OTA.ko /data/local
ON YOUR PHONE:
You should still have terminal emulator up, at a root prompt. Now run:
Code:
# insmod /data/local/wpthis-OTA.ko
You should see:
Code:
init_module 'wpthis-OTA.ko' failed (Function not implemented)
That means it worked. This next step is CRUCIAL. You must make sure that you are writing to the proper partition here or you could brick your phone. To be absolutely clear- the partition is mmcblk(zero)p(one)(eight)
Code:
dd if=/data/local/hboot-eng.img of=/dev/block/mmcblk0p18
You should see some messages indicating that it was written. Next, run:
Code:
# /data/local/tmp/root
This will lock in root, and give you 'su' access in the future. Next, run:
Code:
# sync
Now wait at least a minute, just to be safe. After waiting, reboot your phone using the power button. After it finishes starting up, launch the terminal emulator, and type 'su'. You should get the prompt asking you to grant permissions. If you got the prompt, congratulations! You have permanent root!
Click to expand...
Click to collapse
Sent from my HTC Vision using XDA App
Sent from my HTC Vision using XDA App
i need help, i perm rooted my phone now it got stuck at the HTC start up! what should i do?? pls reply ASAP!
Original Thread
qzfive said:
In attempt to get root apps working on my Chacha after obtaining root shell via zergRush, I remembered an old exploit that my old Desire Z used called VISIONary+ that ran an exploit called rageagainstthecage (has since been patched by HTC) and mounted a ramdisk at /system/xbin, copied the su and busybox binaries to this ramdisk, and installed Superuser.apk as a normal application, which allowed for an almost fully functional root until reboot.
I opened up the VISIONary.apk with WinRAR and found a shell script with individual shell commands which match everything the application does. I typed these commands into adb shell running from my computer with my Chacha connected:
adb shell /data/local/zergRush (to obtain temproot via shell)
Once zergRush was done:
adb remount
adb shell mkdir /system/xbin (told me it already exists, assuming this is normal)
adb push Superuser.apk /data/app/
adb shell chmod 0644 /data/app/Superuser.apk
adb shell mount -t tmpfs none /system/xbin (this creates a ramdisk out of /system/xbin for the su and busybox binaries since they can't be pushed to the physical /system/xbin due to locked bootloader)
adb push busybox /system/xbin
adb shell chmod 4755 /system/xbin/busybox
adb push su /system/xbin/su
adb shell chmod 4755 /system/xbin/su
adb shell /system/xbin/busybox --install -s /system/xbin
After I typed all of that into adb on my computer, I obtained temproot on my Chacha (opened SetCPU, was asked for a Superuser prompt, haven't tested anything else yet). If anyone is willing to try this, please do so and report back. If this is better suited in the Development section, please inform me and I will remake this in Development.
EDIT: a modified su/Superuser.apk was required for this to work on newer Sense ROMs (Chacha included) - I have attached the modified su binary (must unzip) and Superuser.apk
VISIONary+ obtained from: http://android.modaco.com/topic/320350-19nov-r14-visionary-one-click-root/
Modified su/Superuser.apk from: http://forum.xda-developers.com/showthread.php?t=886999&highlight=superuser
-----
EDIT 2: attached a .zip which contains a .bat script which executes these commands for you, to make it easier and quicker to apply/reapply this temp root. Use the contents of temproot.zip instead.
Click to expand...
Click to collapse
Test it by myself and it works.
If you're running zergrush more than once you need to remove boomsh and sh.
type the following into adb shell:
1) "rm /data/local/tmp/boomsh"
2) "rm /data/local/tmp/sh"
App tested to be OK
-setcpu
-Titanium Backup (Backup and restore Data app only.)
-Root Explore (can't edit /system unless s-off)
Something that will never happen unless s-off
-flash custom rom
-flash recovery
-motify system, etc.
Bug:
-Speaker won't work ?
Is there some way not to loose root in such case after reboot ? Otherwise I don't see how temp root could be really useful.
Can we uninstall the stock apps using this method?
Sent from my HTC Wildfire S A510e using XDA App
drsjlazar said:
Can we uninstall the stock apps using this method?
Sent from my HTC Wildfire S A510e using XDA App
Click to expand...
Click to collapse
Something that will never happen unless s-off
-flash custom rom
-flash recovery
-motify system, etc.
Have I answered your question ?! NO
Reboot problem.....
It worked pretty well but my phone reboots if I keep it locked for a while.Any suggestions????
Wow, nice to know this works on other devices
The only "bugs" I noticed when I do this on my Chacha (similar device/same processor), is that the SD card unmounts itself when zergRush runs (might be part of the exploit zergRush does?), and that if I do this too early (ie. the "HTC Quietly Brilliant" bootanimation), it throws my phone into a bootloop -- haven't noticed any speaker bugs as of yet.
EDIT: I only get reboots when something tries modifying the /system partition - because my device is still S-ON (I'm trying to find an XTC Clip), the bootloader triggers a reboot
--Just another thought: since this mounts a ramdisk, would it work on any device that's temprootable?
Hmmm. Is it possible to make a fake flash of the recovery? Anyone try this?
qzfive said:
Wow, nice to know this works on other devices
The only "bugs" I noticed when I do this on my Chacha (similar device/same processor), is that the SD card unmounts itself when zergRush runs (might be part of the exploit zergRush does?), and that if I do this too early (ie. the "HTC Quietly Brilliant" bootanimation), it throws my phone into a bootloop -- haven't noticed any speaker bugs as of yet.
EDIT: I only get reboots when something tries modifying the /system partition - because my device is still S-ON (I'm trying to find an XTC Clip), the bootloader triggers a reboot
--Just another thought: since this mounts a ramdisk, would it work on any device that's temprootable?
Click to expand...
Click to collapse
Yes...I have used zergRush many times and it unmounts the SD card everytime.....so I think its not a bug......you answered my question of reboots tough,thanks.
And maybe this temproot method just might work for every device.
It doesnt work on htc pico (s"on).
Zergrush dont succeed
Sent from my Dell Streak using XDA App
jitin02 said:
It doesnt work on htc pico (s"on).
Zergrush dont succeed
Sent from my Dell Streak using XDA App
Click to expand...
Click to collapse
Maybe HTC patched zergRush on the Pico/Explorer
Guyz, ya don't have to fight with mills, take a look at my topic: http://forum.xda-developers.com/showthread.php?p=21167193
THIS GUIDE NO LONGER WORKS BECAUSE ANDROID ISN'T WHAT IT USED TO BE BACK IN 2013-14.
PLEASE STOP WASTING TIME TO FOLLOW THIS OBSOLETE METHOD 1. PLEASE REFER ONLY TO METHOD 3
The Ultimate Guide to Rooting any Android Device Manually !!!!
Wanting to ROOT Your Phone but can't do Because Of No rooting Guides or want to learn to root any device ? Then , This Guide Is For YOU
OK So lets start....
**What You Need**
1.Your Unrooted Android Device.
2.ADB Drivers Installed On Your PC. If you Don't Have Download From Here :
Code:
adbdriver.com/
3. The Most Inportant Root Kit Made By Me (N'ayam Amarsh'e) - Download From The Attachment.
4.Strength And Courage 'Coz Rooting Voids Your Warranty... If You have a samsung device then Don't Worry Your warranty is gone forever... But if you own any other, maybe you can void it or maybe......
I've Written Android Device as ADV to make it more easy....
**Steps**
So you have the adb drivers installed let's go....
1. Open The root kit by Extracting The Rootkit with WinRAR....
2.Turn 'USB DEBUGGING' 'ON' in your ADV...
3. Connect your ADV to Your PC...
4.In the root kit Open Cmd.exe File ... [ IF YOU CAN'T OPEN CMD, GOTO C:/WINDOWS/SYSTEM32/ COPY CMD .EXE TO YOUR ROOTKIT FOLDER]
5. In CMD window Type the following command...
Code:
->adb devices *Your device will get listed in the window if it doesn't check your adb drivers or if you have followed the steps properly...
->adb push busybox /data/local/tmp
->adb push su /data/local/tmp
->adb push Superuser.apk /data/local/tmp
If you Succeed Move On ...
6.Then You need Root Shell Type :
Code:
adb shell
Note that you see a "$" sign in the command prompt. That means you are not in 'su' shell.
7.Next run the following commands in the shell to change permissions and get some limited privileges for the Superuser files:
Code:
->chmod 6755 /data/local/tmp/su
->chmod 755 /data/local/tmp/busybox
->chmod 644 /data/local/tmp/Superuser.apk
{Note}The names of the files are case sensitive!
8.Done ? Now You need to open a copy of linux which has nautilus... So enter your linux (I recommend using ubuntu 11.4) and type in the terminal (ctrl+alt+T)
Code:
->sudo nautilus
this will open nautilus with root privileges...
You can just boot it from USB so no hassle of installing it... http://www.cyberciti.biz/tips/download-ubuntu-linux-11-04-iso-cd-dvd-images-natty-narwhal.html
Having your ADV connected with USB to PC switch it off and put it in download/recovery mode...
superlouro said:
DEVICE OFFLINE?
! SOLUTION ! (click me)
Click to expand...
Click to collapse
9.In The Exploring Window navigate to
Code:
/data/local/tmp
and move/cut 'su' and 'busybox' to
Code:
/system/bin
...
10.From the tmp Folder you went earlier Move/cut 'Superuser.apk' to
Code:
/system/app
11.Now Reboot You ADV ... Congrats ! You're now ROOTED !
Many Users Are Having Problem with This Method, If you can't do the method 1. Try Method 2.
METHOD 2
PLEASE DON'T ASK ME ABOUT THIS METHOD, THIS IS JUST FOR A TRY, MY BROTHER FOUND THIS METHOD TO BE WORKING, I HAVEN'T TRIED IT YET!
This is linux based method, It's quite easy if you follow every step correctly...
You need to download psneuter, https://github.com/tmzt/g2root-kmod/tree/master/scotty2/psneuter
When you have it execute the following...
Code:
adb devices
Code:
adb push psneuter /data/local/tmp
This will copy the file to your device and now we'll execute it..
Code:
adb shell
cd /data/local/tmp
chmod 777 psneuter
./psneuter
Now You'll see
Code:
adb kill-server
adb devices
adb shell
now # will appear in place of $, or after typing $su.
Code:
# mount -o remount,rw -t rfs /dev/block/st19/system
# exit
$ adb push busybox /system/bin
$ adb push su /system/bin
$ adb install Superuser.apk
$ adb shell
# chmod 4755 /system/bin/busybox
# chmod 4755 /system/bin/su
# mount -o remount,ro -t rfs /dev/block/st19/system
# exit
$ adb reboot
Now your device will reboot and you can see SuperUser App in your app drawer...
----------------------------------------------------------------------
METHOD 3
There is no chance of the phone not getting rooted with my method but If you don't want to do the above methods, Try these, I'm pretty sure they will root your device with ease...
1. Framroot App [Not On Google Play]-http://forum.xda-developers.com/apps/framaroot/root-framaroot-one-click-apk-to-root-t2130276
2.KingoRoot App - www.kingoapp.com
3.One Click Root Free/Pro (My Favorite app, roots many devices with No-Brick Guarantee) - www.oneclickroot.com
4.Root Master App - forum.xda-developers.com/showthread.php?t=2672150
5.z4root App - http://forum.xda-developers.com/showthread.php?t=833953
6.Easy rooting toolkit App-http://forum.xda-developers.com/showthread.php?t=1321582
7.Vroot Software - http://vrootdownload.info/ or http://www.mgyun.com/en/getvroot
8.SRSRoot Software - http://www.srsroot.com
9.Unlock Root Software - http://www.unlockroot.com/download.html
10.Universal Androot App - forum.xda-developers.com/attachment.php?attachmentid=391774
ONLY FOR MTK DEVICES- MTK DROID TOOLS- http://forum.gsmhosting.com/vbb/f60...3-2014-imei-repair-rooting-tool-more-1780568/
HOPE THESE WILL DO....
Press Thanks To appreciate me to Work On Other Guides And Roms....
Your Appreciation Is Needed...
And This GUIDE IS Originally By N'ayam Amarsh'e
I have any error. Device is offline.
---------- Post added at 09:13 AM ---------- Previous post was at 09:02 AM ----------
uukasz92 said:
I have any error. Device is offline.
Click to expand...
Click to collapse
Problem solved i download another adb drivers and work fine
In /UserData/local/tmp i only have one file "directory" and nothing else. It's look like something block the data folder.
uukasz92 said:
In /UserData/local/tmp i only have one file "directory" and nothing else. It's look like something block the data folder.
Click to expand...
Click to collapse
that means you have not properly pushed the files into the directory.... Try installing adb drivers again and do the same steps...Good luck
When you open cmd just type ' adb devices' if your device gets listed then you can start if it doesn't check your drivers...
After uinstall all adb drivers and phone drivers comand prompt shows me a device code and status ofline. At the begining i install atached to therad package of adb drivers. But lately some where in Internet I find some update package of adb drivers. And there was the same sort of files like in your package. I put them there and replace and after that adb shows the device is working and status is online but your guide still does not work. Question is where is real problem ? I checked and Debug Mod is on, drivers are installed.
Try this , download android commander and try to copy the busybox , su and superuser to data/local/tmp
N'ayam Amarsh'e said:
Try this , download android commander and try to copy the busybox , su and superuser to data/local/tmp
Sent from my Mi-492 using xda app-developers app
Click to expand...
Click to collapse
I used the same files in android commander because program can't finde my device to.
Which phone you have.... Try to download its original drivers this might help...
I using Samsung Galaxy Grand Neo (GT-I9060) Jelly Bean 4.2.2
Now is working. But how to move "su" and busybox into system/bin ? Android commander says " You need root to do this." when i try to copy does files into system/bin. Folders are protected and I dont have premission to do anything with them.
uukasz92 said:
I using Samsung Galaxy Grand Neo (GT-I9060) Jelly Bean 4.2.2
Now is working. But how to move "su" and busybox into system/bin ? Android commander says " You need root to do this." when i try to copy does files into system/bin. Folders are protected and I dont have premission to do anything with them.
Click to expand...
Click to collapse
Sorry I forgot that Android Commander works only for rooted phones... Silly Me...
OK you will need to do it with Droid Explorer
OR
linux and in the linux you'll have to type 'sudo nautilus' it'll open it with root privilages...
N'ayam Amarsh'e said:
Sorry I forgot that Android Commander works only for rooted phones... Silly Me...
OK you will need to do it with Droid Explorer
OR
linux and in the linux you'll have to type 'sudo nautilus' it'll open it with root privilages...
Click to expand...
Click to collapse
And in your guide need little correct. In step 9 should be /data/local/tmp not /UserData/local/tmp. Does are two diffrent folders. And before I think I do something wrong when all files be already on right place
Droid Explorer cant change folders premission too. Command prompt says : Read-only drirectory. I don't know what to do now.
uukasz92 said:
And in your guide need little correct. In step 9 should be /data/local/tmp not /UserData/local/tmp. Does are two diffrent folders. And before I think I do something wrong when all files be already on right place
Click to expand...
Click to collapse
thanks.... Guide is updated now
Good 1 helped alot
harmeet singh said:
Good 1 helped alot
Click to expand...
Click to collapse
I am happy that I helped....
Hi! First thank you for that guide. I rooted several devices but with a noname(10.1" A10 dual core) china tablet I have some problems so I hope your solution works.
I have some problems/questions:
1. Step 5: Are you sure it's:
Code:
adb push su /data/local/tmp
instead of
adb push su /data/local/tmp[B][SIZE="5"]/[/SIZE][/B]
I'm currently not able to look at the data folder but if I change the directions e.g to /test/local/tmp it just creates a "tmp" file and overwrites the file with every push command.
2. Step 6: If it's a $ it's not rootet, what should be there if it's rooted? I have a # there. Rootchecker says it's rooted since the beginning, but I cant access with superuser/supersu etc.
3. Step 8 doesn't work. I use a virtual box with ubuntu 13.10(Stinson: new is always better?) for the first time. With "sudo nautilus" I get the message that root access is not granted(failed to register client). I used "gksudo nautilus" instead... does that matter?
4. I can't connect my device to the virtual box. I tried to add the usb device but didn't work. USB Developer Android[0223] is in virtual box connected. However, I dont know where to find it in ubuntu. I'm a ubuntu noob sorry :/
5. Is there another way to get rw permissions?
Thanks in advance :good:
thankyou for information i think is hard for me
Very nice, ty
Humbel said:
Hi! First thank you for that guide. I rooted several devices but with a noname(10.1" A10 dual core) china tablet I have some problems so I hope your solution works.
I have some problems/questions:
1. Step 5: Are you sure it's:
Code:
adb push su /data/local/tmp
instead of
adb push su /data/local/tmp[B][SIZE="5"]/[/SIZE][/B]
I'm currently not able to look at the data folder but if I change the directions e.g to /test/local/tmp it just creates a "tmp" file and overwrites the file with every push command.
2. Step 6: If it's a $ it's not rootet, what should be there if it's rooted? I have a # there. Rootchecker says it's rooted since the beginning, but I cant access with superuser/supersu etc.
3. Step 8 doesn't work. I use a virtual box with ubuntu 13.10(Stinson: new is always better?) for the first time. With "sudo nautilus" I get the message that root access is not granted(failed to register client). I used "gksudo nautilus" instead... does that matter?
4. I can't connect my device to the virtual box. I tried to add the usb device but didn't work. USB Developer Android[0223] is in virtual box connected. However, I dont know where to find it in ubuntu. I'm a ubuntu noob sorry :/
5. Is there another way to get rw permissions?
Thanks in advance :good:
Click to expand...
Click to collapse
For Your First Answer You Need not to worry /tmp and /tmp/ are the same...
2.Have you tried typing 'adb shell' then ' su ' if yes there's your solution.... If not then you have problem with su binary or busybox....
3.You have an Ubuntu 11.4 .iso file so burn it to a blank disk and boot your live disk .... It should be all right then...
4.Answer in 3....
5.Answer in 3....
6.Press Thanks if I helped...
bro im confused wt to do exactly in that sudo ... step pls give a brief explaination
Hello Everyone! I would like to make a guide for Rooting our Sony Xperia Z1s for T-mobile, I tried this with Android 4.3 Firmware 14.2.C.0.159.
This is my first Post so if i make a mistake please let me Know.
Thanks to Jcase and his pwn file to make this root Posible.
This is just the way how i did it and worked for me.
I AM NOT RESPOSIBLE FOR BRICKED DEVICES, THIS IS JUST A GUIDE FOR THOSE WHO DON'T KNOW HOW TO USE THE JCASE EXPLOID.
Requirements:
Well, first of all you have to make sure that your computer have the correct adb drivers installed and you can go into it.
Debugging mode On. (Developer options, USB Debugging Checked)
Download the JCASE pwn (http://forum.xda-developers.com/showpost.php?p=53407127&postcount=1004)
Download the Adb Drivers Updated (http://www.mediafire.com/download/41lx6p71xxit1ax/ADB+Drivers_Updated.zip) Thanks to Droidextra.org, UJJWAL KUMAR.
Process:
1- With the two zip files downloaded you will unzip it in the Local Disk (C), Create a folder with a name like "Root Tool" And unzip the files there, just like these: Check attached picture.
2- Press Shift on the keyboard and right click and then "open a Command Prompt here"
3- Check if your Sony Xperia Z1s its working well in the adb typing: adb devices. If it says failed, you have to check your adb drivers, if not, you're going good.
4- So if all its going well, just type this on command prompt (Thanks JCASE)
adb push pwn /data/local/tmp/pwn
adb shell chmod 755 /data/local/tmp/pwn
adb shell /data/local/tmp/pwn
5- wait for the adb to finish.
6- Unplug you're phone and restart it.
7- Install Super Su apk (Can download it from Play Store or latest Apk)
8- Open SuperSu and update binarys with Normal Mode
Now you must be Root, if SuperSu can't update Binarys try again from 2.
If you are not able to Write to system try this: http://forum.xda-developers.com/show...57358331140130
If this works for you please say thanks to Jcase who made this can be possible.
I tried this but nothing happens I attached what happens in cmd
Sent from my C6916 using XDA Free mobile app
---------- Post added at 08:12 PM ---------- Previous post was at 08:06 PM ----------
not working for me this is what I get in CMD
C:\Root Tool>adb push pwn /data/local/tmp/pwn
2792 KB/s (574722 bytes in 0.201s)
C:\Root Tool>
C:\Root Tool>adb shell chmod 755 /data/local/tmp/pwn
C:\Root Tool>
C:\Root Tool>adb shell /data/local/tmp/pwn
superangel16 said:
Hello Everyone! I would like to make a guide for Rooting our Sony Xperia Z1s for T-mobile, I tried this with Android 4.3 Firmware 14.2.C.0.159.
This is my first Post so if i make a mistake please let me Know.
Thanks to Jcase and his pwn file to make this root Posible.
This is just the way how i did it and worked for me.
I AM NOT RESPOSIBLE FOR BRICKED DEVICES, THIS IS JUST A GUIDE FOR THOSE WHO DON'T KNOW HOW TO USE THE JCASE EXPLOID.
Requirements:
Well, first of all you have to make sure that your computer have the correct adb drivers installed and you can go into it.
Debugging mode On. (Developer options, USB Debugging Checked)
Download the JCASE pwn (http://forum.xda-developers.com/showpost.php?p=53407127&postcount=1004)
Download the Adb Drivers Updated (http://www.mediafire.com/download/41lx6p71xxit1ax/ADB+Drivers_Updated.zip) Thanks to Droidextra.org, UJJWAL KUMAR.
Process:
1- With the two zip files downloaded you will unzip it in the Local Disk (C), Create a folder with a name like "Root Tool" And unzip the files there, just like these: Check attached picture.
2- Press Shift on the keyboard and right click and then "open a Command Prompt here"
3- Check if your Sony Xperia Z1s its working well in the adb typing: adb devices. If it says failed, you have to check your adb drivers, if not, you're going good.
4- So if all its going well, just type this on command prompt (Thanks JCASE)
adb push pwn /data/local/tmp/pwn
adb shell chmod 755 /data/local/tmp/pwn
adb shell /data/local/tmp/pwn
5- wait for the adb to finish.
6- Unplug you're phone and restart it.
7- Install Super Su apk (Can download it from Play Store or latest Apk)
8- Open SuperSu and update binarys with Normal Mode
Now you must be Root, if SuperSu can't update Binarys try again from 2.
If this works for you please say thanks to Jcase who made this can be possible.
Click to expand...
Click to collapse
Just use z2 exploit 11 run it twice.
Sent from my C6916 using xda premium
Im getting this error whenever I try open SuperSU.. Tried your method about 6 or 7 times, same error everytime.. any advice?
48bloo said:
Im getting this error whenever I try open SuperSU.. Tried your method about 6 or 7 times, same error everytime.. any advice?
Click to expand...
Click to collapse
Sorry about that, SuperSu its giving to you this error because the rooting it's not done, please check that your phone its adb recognizable with "adb devices" in CMD, Remember to Unistall Super Su if you get the error and Reboot in order to try again.
Damented said:
I tried this but nothing happens I attached what happens in cmd
Sent from my C6916 using XDA Free mobile app
---------- Post added at 08:12 PM ---------- Previous post was at 08:06 PM ----------
not working for me this is what I get in CMD
C:\Root Tool>adb push pwn /data/local/tmp/pwn
2792 KB/s (574722 bytes in 0.201s)
C:\Root Tool>
C:\Root Tool>adb shell chmod 755 /data/local/tmp/pwn
C:\Root Tool>
C:\Root Tool>adb shell /data/local/tmp/pwn
Click to expand...
Click to collapse
Please try again pressing enter just once at each code.
superangel16 said:
Sorry about that, SuperSu its giving to you this error because the rooting it's not done, please check that your phone its adb recognizable with "adb devices" in CMD, Remember to Unistall Super Su if you get the error and Reboot in order to try again.
Click to expand...
Click to collapse
Okay so after working at this for a couple of hours I finally got it to work. For some reason, I wasn't able to uninstall SuperSu because it had been installed as a system app and I could only disable it, or uninstall updates from it. After trying over and over, I found this link.
http://forum.xda-developers.com/showpost.php?p=53442704&postcount=1075&nocache=1&z=9157358331140130
Here, they include the exact same method in this thread, with one extra step; creating a boot script to maintain root/system permissions. Im not exactly sure how it works, but i followed the instructions provided by the links and then, after rebooting, was able to install binaries, and achieve full root (FINALLY!!) So if anybody has the same problem I did, try this out
48bloo said:
Okay so after working at this for a couple of hours I finally got it to work. For some reason, I wasn't able to uninstall SuperSu because it had been installed as a system app and I could only disable it, or uninstall updates from it. After trying over and over, I found this link.
http://forum.xda-developers.com/showpost.php?p=53442704&postcount=1075&nocache=1&z=9157358331140130
Here, they include the exact same method in this thread, with one extra step; creating a boot script to maintain root/system permissions. Im not exactly sure how it works, but i followed the instructions provided by the links and then, after rebooting, was able to install binaries, and achieve full root (FINALLY!!) So if anybody has the same problem I did, try this out
Click to expand...
Click to collapse
Nice! I'm happy To heard that! JCase said in his post that some people will have this problem to write to system, but in my case i was able to, now we have to find a working recovery in order to have a custom rom or something like that, Some people say that xzdualrecovery works for z1s, but it is in beta version, if you find something please let us know.
Guys not to be mean but we posted this a while back shows you how to root what to install for recovery as well as a deodex and perm root http://forum.xda-developers.com/showthread.php?t=2783626
Tactic13 said:
Guys not to be mean but we posted this a while back shows you how to root what to install for recovery as well as a deodex and perm root http://forum.xda-developers.com/showthread.php?t=2783626
Click to expand...
Click to collapse
Oh! Excellent! thank you so much now we can all get the final access, i searched before but no luck, thank you. Now just have to buy a new phone, mine was robbed on friday , just 3 days of use .......
superangel16 said:
Oh! Excellent! thank you so much now we can all get the final access, i searched before but no luck, thank you. Now just have to buy a new phone, mine was robbed on friday , just 3 days of use .......
Click to expand...
Click to collapse
Not full access bootloader is still locked but you can flash things onto your phone and as well as backups. Also sorry on the phone thing.
Tactic13 said:
Not full access bootloader is still locked but you can flash things onto your phone and as well as backups. Also sorry on the phone thing.
Click to expand...
Click to collapse
Hey Thanks for Reply, that's the reason because i said de Final Acces, because we can acces to bootloader because branded phones can't have bootloader unlocked.:fingers-crossed:
Has anyone taken the update? Will we lose root?
POMF2K said:
Has anyone taken the update? Will we lose root?
Click to expand...
Click to collapse
I can't be sure of that because is a said I lose my phone, but ever when you do a official update you lose root.
Sent from my C6603 using XDA Free mobile app
superangel16 said:
I can't be sure of that because is a said I lose my phone, but ever when you do a official update you lose root.
Sent from my C6603 using XDA Free mobile app
Click to expand...
Click to collapse
I did not lose root. I check the box in SuperSU to try to retain root.
Kept root, now I just have to fix all the issues 4.4 has created.
POMF2K said:
I did not lose root. I check the box in SuperSU to try to retain root.
Kept root, now I just have to fix all the issues 4.4 has created.
Click to expand...
Click to collapse
Which box in SuperSU was it?
Doc
superangel16 said:
Please try again pressing enter just once at each code.
Click to expand...
Click to collapse
So you have to enter each line and then enter and then the next line and enter. Correct?
Sent from my C6916 using Xparent Cyan Tapatalk 2
superangel16 said:
Hello Everyone! I would like to make a guide for Rooting our Sony Xperia Z1s for T-mobile, I tried this with Android 4.3 Firmware 14.2.C.0.159.
This is my first Post so if i make a mistake please let me Know.
Thanks to Jcase and his pwn file to make this root Posible.
This is just the way how i did it and worked for me.
I AM NOT RESPOSIBLE FOR BRICKED DEVICES, THIS IS JUST A GUIDE FOR THOSE WHO DON'T KNOW HOW TO USE THE JCASE EXPLOID.
Requirements:
Well, first of all you have to make sure that your computer have the correct adb drivers installed and you can go into it.
Debugging mode On. (Developer options, USB Debugging Checked)
Download the JCASE pwn (http://forum.xda-developers.com/showpost.php?p=53407127&postcount=1004)
Download the Adb Drivers Updated (http://www.mediafire.com/download/41lx6p71xxit1ax/ADB+Drivers_Updated.zip) Thanks to Droidextra.org, UJJWAL KUMAR.
Process:
1- With the two zip files downloaded you will unzip it in the Local Disk (C), Create a folder with a name like "Root Tool" And unzip the files there, just like these: Check attached picture.
2- Press Shift on the keyboard and right click and then "open a Command Prompt here"
3- Check if your Sony Xperia Z1s its working well in the adb typing: adb devices. If it says failed, you have to check your adb drivers, if not, you're going good.
4- So if all its going well, just type this on command prompt (Thanks JCASE)
adb push pwn /data/local/tmp/pwn
adb shell chmod 755 /data/local/tmp/pwn
adb shell /data/local/tmp/pwn
5- wait for the adb to finish.
6- Unplug you're phone and restart it.
7- Install Super Su apk (Can download it from Play Store or latest Apk)
8- Open SuperSu and update binarys with Normal Mode
Now you must be Root, if SuperSu can't update Binarys try again from 2.
If you are not able to Write to system try this: http://forum.xda-developers.com/show...57358331140130
If this works for you please say thanks to Jcase who made this can be possible.
Click to expand...
Click to collapse
Hello, three commands you wrote down. Do I need to write them exactly like that with a space in between each line and then enter? Or do I need to type one command and then ENTER after each command?
Thanks in advance
Sent from my C6916 using Xparent Cyan Tapatalk 2
superangel16 said:
Hello Everyone! I would like to make a guide for Rooting our Sony Xperia Z1s for T-mobile, I tried this with Android 4.3 Firmware 14.2.C.0.159.
This is my first Post so if i make a mistake please let me Know.
Thanks to Jcase and his pwn file to make this root Posible.
This is just the way how i did it and worked for me.
I AM NOT RESPOSIBLE FOR BRICKED DEVICES, THIS IS JUST A GUIDE FOR THOSE WHO DON'T KNOW HOW TO USE THE JCASE EXPLOID.
Requirements:
Well, first of all you have to make sure that your computer have the correct adb drivers installed and you can go into it.
Debugging mode On. (Developer options, USB Debugging Checked)
Download the JCASE pwn (http://forum.xda-developers.com/showpost.php?p=53407127&postcount=1004)
Download the Adb Drivers Updated (http://www.mediafire.com/download/41lx6p71xxit1ax/ADB+Drivers_Updated.zip) Thanks to Droidextra.org, UJJWAL KUMAR.
Process:
1- With the two zip files downloaded you will unzip it in the Local Disk (C), Create a folder with a name like "Root Tool" And unzip the files there, just like these: Check attached picture.
2- Press Shift on the keyboard and right click and then "open a Command Prompt here"
3- Check if your Sony Xperia Z1s its working well in the adb typing: adb devices. If it says failed, you have to check your adb drivers, if not, you're going good.
4- So if all its going well, just type this on command prompt (Thanks JCASE)
adb push pwn /data/local/tmp/pwn
adb shell chmod 755 /data/local/tmp/pwn
adb shell /data/local/tmp/pwn
5- wait for the adb to finish.
6- Unplug you're phone and restart it.
7- Install Super Su apk (Can download it from Play Store or latest Apk)
8- Open SuperSu and update binarys with Normal Mode
Now you must be Root, if SuperSu can't update Binarys try again from 2.
If you are not able to Write to system try this: http://forum.xda-developers.com/show...57358331140130
If this works for you please say thanks to Jcase who made this can be possible.
Click to expand...
Click to collapse
Hey boss, I did everything exactly as instructed and my phone has no problem being identified in adb devices but every time I run the commands I get the first 2 commands looking like it went OK but the last command just can't execute.
C:\Users\TEMP\Downloads\xperia root>adb devices
List of devices attached
CB5A1Z18JC device
C:\Users\TEMP\Downloads\xperia root>adb push pwn /data/local/tmp/pwn
2806 KB/s (574722 bytes in 0.200s)
C:\Users\TEMP\Downloads\xperia root>adb shell chmod 755 /data/local/tmp/pwn
C:\Users\TEMP\Downloads\xperia root>adb shell /data/local/tmp/pwn
/system/bin/sh: /data/local/tmp/pwn: can't execute: Is a directory
C:\Users\TEMP\Downloads\xperia root>
Please help.
Bill Idol said:
Hey boss, I did everything exactly as instructed and my phone has no problem being identified in adb devices but every time I run the commands I get the first 2 commands looking like it went OK but the last command just can't execute.
C:\Users\TEMP\Downloads\xperia root>adb devices
List of devices attached
CB5A1Z18JC device
C:\Users\TEMP\Downloads\xperia root>adb push pwn /data/local/tmp/pwn
2806 KB/s (574722 bytes in 0.200s)
C:\Users\TEMP\Downloads\xperia root>adb shell chmod 755 /data/local/tmp/pwn
C:\Users\TEMP\Downloads\xperia root>adb shell /data/local/tmp/pwn
/system/bin/sh: /data/local/tmp/pwn: can't execute: Is a directory
C:\Users\TEMP\Downloads\xperia root>
Please help.
Click to expand...
Click to collapse
Thank yoy sir for follow my instructions, i am sorry for the delay to answer, i lost my phone. Well i see you are getting a problem to get into the last step in this guide, please check the Jcase post to get you're problem solved; http://forum.xda-developers.com/showpost.php?p=53407127&postcount=1004.
Hope you can solve it!