Related
--This thread is recommended to be viewed on a Pc/Linux (I included you guys too ), OR on your ANDROID-POWERED phone (with XDA or in browser now ).--
--This is for PC and LINUX problems.--
Hallo!
You may have adb errors such as: cannot connect to daemon. This is a common problem beginners commonly forget. Also MAKE SURE you have installed android sdk
If you get adb error like :
adb server is out of date * killing***
daemon still not running
error:cannot connect to daemon
Click to expand...
Click to collapse
That means your device can't be found in adb.
Simply:
1) Make sure USB debugging is on
Found in Settings>Applications>Development
Click to expand...
Click to collapse
2) Make sure you have YOUR PHONES DRIVERS INSTALLED.
They can be installed via HTC Sync.
Click to expand...
Click to collapse
3) Still not working? Instead of using the USB option Charge Only/Disk Drive.
Use HTC Sync USB option.
Click to expand...
Click to collapse
________________________
RUU Problem [May encounter in the future](Thanks miguelca)
--Not for RUU Setup exe.
Out of date daemon error
Click to expand...
Click to collapse
Step 1) Browser to your android sdk folder
Its probably in: C:\android-sdk-windows OR C:\Program Files (x86)\Android\android-sdk (In 64bit edition of windows) OR C:\Program Files\Android\android-sdk
Click to expand...
Click to collapse
Step 2) Enter the platform-tools folder
Its simple just press Platform-tools
Click to expand...
Click to collapse
Step 3) Copy all of the files except: Source.propties, NOTICE.txt, lib, renderscript folder.
Hold Ctrl-A then press the files, then when done right click and press copy.
Click to expand...
Click to collapse
Step 4) Browse to your RUU Folder, and paste the files there.
Enter the RUU folder, right click anywhere press paste (If asks to overwrite press yes.)
Click to expand...
Click to collapse
Step 5) Should be done now!
________________________
[Linux ADB Problems (Thanks Tectas)]
Hallo, now this part of the thread is about linux ADB Problems .
permission denied ?????????
Click to expand...
Click to collapse
If you use Linux and get permission denied ????????? at execution of adb devices, switch to su and execute:
Code:
[B][I][U][COLOR="DarkOrange"][FONT="Lucida Sans Unicode"]adb kill-server
(be sure the path to the adb directory is inside the .Bashrc file or CD to the right directory)
adb start-server[/FONT][/COLOR][/U][/I][/B]
Afterwards you can exit to normal shell and use it like ever.
[End of thread. Please scroll up or down to read reply's, or to read on ]
One addidonal thing,
if you are an linux user and get permission denied ????????? at execution of adb devices, switch to su and execute:
Code:
adb kill-server
(be sure the path to the adb directory is inside the .bashrc file or cd to the right directory)
adb start-server
to start the adbd in su context, afterwards you can exit to normal shell and use it like ever.
It's not as trivial as you say. I had the out of date daemon error while trying to update my phone with the 2.3.5 European RUU by football. The solution was to uncompress the RUU and replace the ADB executable and dll's with updated ones from the Android SDK I had installed. It had nothing to do with USB connections or settings. Probably the RUU wasn't prepared for Windows 7 x64 SP1... I guess.
Sent from my HTC Wildfire S A510e using XDA App
Thanks!
Updated the thread.
XDA_h3n said:
Updated the thread.
Click to expand...
Click to collapse
You're welcome!
Thank you for the nice thread, for updating it quickly and for crediting me too.
It's great when several experiences are compiled in a way that might help many other users.
That's what a community is all about.
My trick is Download Vroot on your Pc and it will install everything you need. (Might replace your current Root Manager if you don't cancel the process of it rooting.) Once you connect your phone to your pc with Vroot it's ask you to install a apk just click okay. Once you see the apk installed wait for it to get a green backrground with wire connected image. Then there you go. Sorry for my Bad English. Hope it Helps.
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!
Install ADB Drivers properly at first
Video Tutorial : Debloat any Realme/Oppo phone
Open command windows in adb directory
Type adb devices
Authorize it from your phone .
After you have done it ,type adb shell ,it should open adb shell.
Then just paste all the text from my script ,it will automatically debloat wait till it's done.
Debloat files-
For ColorOS :
https://drive.google.com/open?id=1JXUjy7O2rOpu55i7jzxIJnPer3idRyv4
For RealmeUI :
https://drive.google.com/file/d/1OUuz6BmKqrNpwrUrQLHK8Inkd6vVRs-Q/view?usp=sharing
Hope it'll be helpful
Thank you for this script
Hello guys . In shizuku app that use pairing adb over network . In this app there is option allow you to use shizuku in your terminal apps like Termux and I use Termux in this case the problem is I can't use this option because I don't know what is steps should I do in locked bootloader and non rooted device I need full access to adb by this way because I don't have PC in real time
The error in the attachment files
AmrMero said:
Hello guys . In shizuku app that use pairing adb over network . In this app there is option allow you to use shizuku in your terminal apps like Termux and I use Termux in this case the problem is I can't use this option because I don't know what is steps should I do in locked bootloader and non rooted device I need full access to adb by this way because I don't have PC in real time
The error in the attachment files
Click to expand...
Click to collapse
https://www.reddit.com/r/termux/comments/i2nrbm
I this allow me to run adb and she'll commands from my device to the same device (local) I think the like to send adb to another device right !?
AmrMero said:
I think the like to send adb to another device right !?
Click to expand...
Click to collapse
I don't understand what you want to ask.
To send ADB command to another device, you can use ADB over WIFI setting in developer option.
I mean I need send adb from my device to my device by shizuku . (All in the same device )
I'm not really sure what your issue is. Shizuku is pretty simple, even if you use it for terminal. You exported the files. You changed the Package ID. So what's the problem? You can use it now.
For example, `adb shell pm disable com.bloatware.app` just becomes `shizuku pm disable com.bloatware.app`. shizuku basically gives you ADB shell access. Use `shizuku` similar to how you'd use `sudo` on Linux.
To test, just do `./shizuku ls`. First time you should get a permission prompt by the shizuku appz asking if you wanna grant permissions to termux.
AmrMero said:
Hello guys . In shizuku app that use pairing adb over network . In this app there is option allow you to use shizuku in your terminal apps like Termux and I use Termux in this case the problem is I can't use this option because I don't know what is steps should I do in locked bootloader and non rooted device I need full access to adb by this way because I don't have PC in real time
The error in the attachment files
Click to expand...
Click to collapse
You said you don't have computer access all the time. So, I'm assuming you have it at least once. If so, try rhis.
1. Connect to computer and enable wireless adb (just google it)
2. Download this app named Remote ADB Shell by Cameron Gutman https://play.google.com/store/apps/details?id=com.cgutman.androidremotedebugger
3. Enter IP as 127.0.0.1 and port as 5555 (assuming you didn't change it in the first step)
Can't say if your Shizuku needs will be satisfied but this way, you'll be able to run commands in adb shell (from your phone) as if doing from computer. Make sure that you don't use aadb sheelll iin the commands