How can i root it again? - OnePlus 7T Questions & Answers

i rooted my 7T successfully first time. 10.0.6 HD65AA Global
When i tried to install edxposed in Magisk , it got stuck in fastboot.
then i flashed stock_boot.image and boot to unrooted system , all good.
But when i tried to root it same way again, it wont work anymore. once flash magisk_boot.img, only reboot to fastboot.
Any one can help ?
Thanks a lot

I am having almost same problem. After flashing stock image when i went back to patched image again it boots normally but no magisk install option.

https://forum.xda-developers.com/oneplus-7t/how-to/magisk-twrp-root-module-uninstall-t4002843/page5
Sent from my OnePlus7TPro using XDA Labs

Lossyx said:
https://forum.xda-developers.com/oneplus-7t/how-to/magisk-twrp-root-module-uninstall-t4002843/page5
Sent from my OnePlus7TPro using XDA Labs
Click to expand...
Click to collapse
Thanks for your reply.
but i got stuck in the first 2 steps to make a unsecure_adb_recovery.img,
I couldnt get 'payload dumper' working.. keep getting error running python:crying:
Can anyone please upload a unsecure_adb_recovery.img?

I have made the unsecure_adb_recovery.img.
now that I'm in adb shell, cannot go to folder /data/ adb/modules,
says permission denied : ,, how can i Get permission?
1|OnePlus7T:/ $ cd data
cd data
OnePlus7T:/data $ cd adb
cd adb
/system/bin/sh: cd: /data/adb: Permission denied
2|OnePlus7T:/data $ ls
ls
ls: .: Permission denied
1|OnePlus7T:/data $

solved ,
need to reboot to recovery to have root permission
reroot success!

jzjzjjz said:
solved ,
need to reboot to recovery to have root permission
reroot success!
Click to expand...
Click to collapse
Can you explain what exactly did you do ?

zanderzone said:
Can you explain what exactly did you do ?
Click to expand...
Click to collapse
i followed this guide
https://forum.xda-developers.com/oneplus-7t/how-to/magisk-twrp-root-module-uninstall-t4002843

Related

Tried to Root G2 (S-ON)

If on Recovery, it says S-ON, is that a Problem?
triumphantpower said:
If on Recovery, it says S-ON, is that a Problem?
Click to expand...
Click to collapse
If it says S-ON, you don't have permaroot. Did you follow the guide in the wiki?
Sent from my T-Mobile G2 using XDA App
I watched a Video from BlackPrince310. I got far into it, until I had to use the Terminal. I'm not sure what Wiki are you talking about.. Link?
(Thank You for the speedy reply btw)
triumphantpower said:
I watched a Video from BlackPrince310. I got far into it, until I had to use the Terminal. I'm not sure what Wiki are you talking about.. Link?
(Thank You for the speedy reply btw)
Click to expand...
Click to collapse
YouTube *really* shouldn't be the go to for things like this, unless you like bricks. This guide is by the folks who actually engineered the hack: http://forum.xda-developers.com/wik...sion#Rooting_the_Vision_.28G2.2FDZ.29_and_DHD
Sent from my T-Mobile G2 using XDA App
oh alright, Thank You OriginalGabriel.
But is rage an adb command or an app from the Market?
and where would the HTC G2 Drivers have to be installed?
triumphantpower said:
and where would the HTC G2 Drivers have to be installed?
Click to expand...
Click to collapse
If you've used adb (eg. you have the SDK installed on your computer), then you have the drivers already installed. Otherwise, unzip the file and when you plug your computer into your phone, point the hardware wizard to the folder that you unzipped
Rage is an included binary in gfree_temp-root.zip
Got it Thank You.
I got to where I have to use ADB, and while trying to $ adb push su /sdcard/su
It won't let allow me, it'll say access denied. (I've even put adb shell before that command)
I type in adb shell:
*daemon not running. starting it now on port 5037*
*daemon started successfully* and then any other command I type after that is Denied
triumphantpower said:
I type in adb shell:
*daemon not running. starting it now on port 5037*
*daemon started successfully* and then any other command I type after that is Denied
Click to expand...
Click to collapse
on your phone be sure you have menu>settings>applications>development>usb debugging checked (on)
I do. Using this Tutorial: http://forum.xda-developers.com/wik...sion#Rooting_the_Vision_.28G2.2FDZ.29_and_DHD
I got all the way to the Permaroot Section. When I have to issue these commands:
# cd /data/local
# chmod 777 gfree
# ./gfree -f
#sync
my phone reset before I got to type sync.
And before I got the chance to type the next lines of text, I had to turn on my phone issued them and got an error message of file exists and something else. I Booted my phone and it still says SHIP S-ON
triumphantpower said:
I do. Using this Tutorial: http://forum.xda-developers.com/wik...sion#Rooting_the_Vision_.28G2.2FDZ.29_and_DHD
I got all the way to the Permaroot Section. When I have to issue these commands:
# cd /data/local
# chmod 777 gfree
# ./gfree -f
#sync
my phone reset before I got to type sync.
And before I got the chance to type the next lines of text, I had to turn on my phone issued them and got an error message of file exists and something else. I Booted my phone and it still says SHIP S-ON
Click to expand...
Click to collapse
After you do the temp root, shut down adb (I am using a windows machine so I ctrl alt del and find it in task manager and shut it down that way) It should restart by itself when you do the perm root commands. ( you probably know this, but don't enter the # sign, it should be there by itself)
Thank You sooo much! I got the S-Off now finally, thank you very much!
Is there anything else I should do before I decided to Install a Custom ROM? Can I install a ROM from this Recovery? or Do I need to do a further step. According to the Tutorial I have Perm Root now but I've never used this Recovery before
triumphantpower said:
Thank You sooo much! I got the S-Off now finally, thank you very much!
Is there anything else I should do before I decided to Install a Custom ROM? Can I install a ROM from this Recovery? or Do I need to do a further step. According to the Tutorial I have Perm Root now but I've never used this Recovery before
Click to expand...
Click to collapse
Download ROM manager from the market, spend the few bucks for the upgrade and then install clockworkmod recovery through ROM Manager (if you haven't done this already). Then, do some more reading about doing a Nandroid backup and you're ready to go! Now, the fun begins....lol!
I don't mind buying ROM Manager Premium but can I do that with the Free Version? I downloaded the Free Version of ROM Manager v3.0.0.7 and when I selected Flash Clockwork Mod Recovery it gave me "an error occurred while attempting to run privileged commands!". Does the Paid Version go past that or am I missing something?
triumphantpower said:
I don't mind buying ROM Manager Premium but can I do that with the Free Version? I downloaded the Free Version of ROM Manager v3.0.0.7 and when I selected Flash Clockwork Mod Recovery it gave me "an error occurred while attempting to run privileged commands!". Does the Paid Version go past that or am I missing something?
Click to expand...
Click to collapse
do you have the superuser app now in your applications drawer?
edit: Also, disconnect the phone from the USB. That might give ROM manager a problem accessing your sd card if you're still connected.
yeah I have Superuser Permissions but it FC's when you try to open it
triumphantpower said:
yeah I have Superuser Permissions but it FC's when you try to open it
Click to expand...
Click to collapse
Try uninstalling ROM Manager and after that see if you still get a force close when you try to open Superuser.
Interesting Idea. I tried it, and still the same. Superuser FC's @[email protected]
triumphantpower said:
Interesting Idea. I tried it, and still the same. Superuser FC's @[email protected]
Click to expand...
Click to collapse
what happens when, in ROM Manager, you select "fix permissions"?

[Q] ADB PUSH : Permission Denied (AlphaRevX Rooted)

Hi Guys,
I have rooted my Wildfire with AlphaRevX long time back and i tried many different ROMs.
Currently i have installed JokerDroid4.2 ROM.
When i start adb shell its going to normal user($) but not root(#) and when i type su in the shell its going to root(#).
So, when i want to push files to /system/app using adb push its throwing exception of permission denied.
I have seen many threads regarding this problem but couldnot find proper answer to my problem.
Workaround im using is pusing my files to /data/local and after getting root access using adb shell and su im moving it to /system/app
(OfCourse throughout the process /system is mounted as re-write)
Please solve my problem..
EDIT : I allowed the superuser to give permission to adb shell when i typed su command but when i use adb push its not asking me for permission from superuser.
Thanks,
Sandeep
You need to set permision /rw ,to system folder via root explore,then do adb push
bittu4u4ever said:
Hi Guys,
I have rooted my Wildfire with AlphaRevX long time back and i tried many different ROMs.
Currently i have installed JokerDroid4.2 ROM.
When i start adb shell its going to normal user($) but not root(#) and when i type su in the shell its going to root(#).
So, when i want to push files to /system/app using adb push its throwing exception of permission denied.
I have seen many threads regarding this problem but couldnot find proper answer to my problem.
Workaround im using is pusing my files to /data/local and after getting root access using adb shell and su im moving it to /system/app
(OfCourse throughout the process /system is mounted as re-write)
Please solve my problem..
EDIT : I allowed the superuser to give permission to adb shell when i typed su command but when i use adb push its not asking me for permission from superuser.
Thanks,
Sandeep
Click to expand...
Click to collapse
Sent from my Wildfire using XDA App
luxandroid said:
You need to set permision /rw ,to system folder via root explore,then do adb push
Sent from my Wildfire using XDA App
Click to expand...
Click to collapse
(OfCourse throughout the process /system is mounted as re-write)
Click to expand...
Click to collapse
As mentioned in my question i hav permission of rw(read-write) already throught the process..
I am using hell fire,pushed or pulled files but not as root user,just went to my tools folder where adb is and did adb push,try like that...
Sent from my Wildfire using XDA App
Have you already tried "adb remount"?
cobje said:
Have you already tried "adb remount"?
Click to expand...
Click to collapse
This should indeed solve all your problems. Just type that command, wait for the "remount succeeded" notification and than try to write in your system folders.
The reason is that your /system is not mounted as read/write (r/w) when you boot your phone, but as read-only (r/o). So afther the remount command /systemfiles will stay r/w, but when you reboot your phone, it will return r/o again.
Erwin

[Q] Copying files to /system | S-ON | HTC One X

I have rooted my HTC One X and want to copy files in /system/xbin folder. My phone shows S-ON. And Eclipse is not able to copy files to /system and adb push from shell is also not working. Is there a way I can copy files to /system/xbin?
I am running stock ROM.
My phone is NOT associated with any vendor.
adb remount
adb push filename /system/xbin
Sent from my HTC One X
You can also use es file explorer and go into the options tick up to root and the request root and then tick mount as r/w.
Then just move files as you will.
Sent from my HTC One X using XDA Premium HD app
realunited123 said:
adb remount
adb push filename /system/xbin
Sent from my HTC One X
Click to expand...
Click to collapse
The above way does not seem to work. Whenever I use adb remount(or adb mount) it says operation not permitted and I am trying to this from root privileges
My OS is :- Ubuntu 12.04
ADB(platform-tools) -> Rev 20
If you need anything more please ask me .
Additional Question
treebill said:
You can also use es file explorer and go into the options tick up to root and the request root and then tick mount as r/w.
Then just move files as you will.
Sent from my HTC One X using XDA Premium HD app
Click to expand...
Click to collapse
First of all thanx it worked. I think I will have to live with this way A ADB/Eclipse based would have been cool
Will the files moved from SDcard to phones root in anyway lose and privileges(like losing executable)? If yes, please suggest a way to restore it.
KillerTheLord said:
The above way does not seem to work. Whenever I use adb remount(or adb mount) it says operation not permitted and I am trying to this from root privileges
My OS is :- Ubuntu 12.04
ADB(platform-tools) -> Rev 20
If you need anything more please ask me .
Click to expand...
Click to collapse
When doing adb shell su do you get any toast notification on your phone? Or does it just say denied ?
Strange it works perfectly here Also are you using SuperSU or any other superuser app?
---------- Post added at 03:37 PM ---------- Previous post was at 03:36 PM ----------
KillerTheLord said:
First of all thanx it worked. I think I will have to live with this way A ADB/Eclipse based would have been cool
Will the files moved from SDcard to phones root in anyway lose and privileges(like losing executable)? If yes, please suggest a way to restore it.
Click to expand...
Click to collapse
Yes you need to change the permissions after moving from sdcard. Use Root Explorer(Long press on the file--> Change permissions)
realunited123 said:
When doing adb shell su do you get any toast notification on your phone? Or does it just say denied ?
Strange it works perfectly here Also are you using SuperSU or any other superuser app?
---------- Post added at 03:37 PM ---------- Previous post was at 03:36 PM ----------
Yes you need to change the permissions after moving from sdcard. Use Root Explorer(Long press on the file--> Change permissions)
Click to expand...
Click to collapse
I am using SuperSU as Super User App. And I think I am doing something wrong here. You mentioned about adb shell su. I think I might be wrong here. Here is how I tried to execute the command.
[email protected]: <path to platformtools> ./adb remount
remount failed: Operation not permitted
do I have to raise ADB shell to SU level. If yes, how?
KillerTheLord said:
I am using SuperSU as Super User App. And I think I am doing something wrong here. You mentioned about adb shell su. I think I might be wrong here. Here is how I tried to execute the command.
[email protected]: <path to platformtools> ./adb remount
remount failed: Operation not permitted
do I have to raise ADB shell to SU level. If yes, how?
Click to expand...
Click to collapse
Strange. Are you using the stock kernel ? If that is the case then it does not have insecure adbd (ro.secure=0) so remount will not work. Try a custom kernel.
Does adb has SU permissions from recovery ? Try booting into recovery, mounting the system partitions and try to push something from adb. Check the SuperSU app to update binary but that should not be a problem.
realunited123 said:
Strange. Are you using the stock kernel ? If that is the case then it does not have insecure adbd (ro.secure=0) so remount will not work. Try a custom kernel.
Does adb has SU permissions from recovery ? Try booting into recovery, mounting the system partitions and try to push something from adb. Check the SuperSU app to update binary but that should not be a problem.
Click to expand...
Click to collapse
Yes I have rooted the phone but the ROM is stock(I was thinking to put in CM9 Alpha).
About the second thing. I know how to boot my phone into recovery(Vol Down + Power -> From Screen -> Recovery(ClockwerkMod))
But about the rest I don't know.
Sorry about my annoying questions this is my first time I am dealing with rooting and stuff.
KillerTheLord said:
Yes I have rooted the phone but the ROM is stock(I was thinking to put in CM9 Alpha).
About the second thing. I know how to boot my phone into recovery(Vol Down + Power -> From Screen -> Recovery(ClockwerkMod))
But about the rest I don't know.
Sorry about my annoying questions this is my first time I am dealing with rooting and stuff.
Click to expand...
Click to collapse
I guess you are using stock kernel then. Try franco's or faux's kernel.
adb remount wont work from os on stock boot.img.
After rebooting into recovery go to mounts and storage-->mount /system and then push something from adb. See if that works.
KillerTheLord said:
Yes I have rooted the phone but the ROM is stock(I was thinking to put in CM9 Alpha).
About the second thing. I know how to boot my phone into recovery(Vol Down + Power -> From Screen -> Recovery(ClockwerkMod))
But about the rest I don't know.
Sorry about my annoying questions this is my first time I am dealing with rooting and stuff.
Click to expand...
Click to collapse
I think this app does exactly what you want :
http://forum.xda-developers.com/showthread.php?t=1687590
realunited123 said:
I guess you are using stock kernel then. Try franco's or faux's kernel.
adb remount wont work from os on stock boot.img.
After rebooting into recovery go to mounts and storage-->mount /system and then push something from adb. See if that works.
Click to expand...
Click to collapse
Well this didn't work either. I hope to switch to some other ROM in future(I hate HTC Sense ). But as of now Root Explorer did the job. I mounted my sdcard and copied files to it and used Root Explorer to move files to /system and then changed permissions.
Thanks for help it really made it easy .
make sure your path devs are oke for su.
in terminal run:
sudo su
adb kill-server
adb devices
you should see your HOX HTxxxxx nr.
and here you should be able to connect eclipse to HOX by adb.
NikMel said:
make sure your path devs are oke for su.
in terminal run:
sudo su
adb kill-server
adb devices
you should see your HOX HTxxxxx nr.
and here you should be able to connect eclipse to HOX by adb.
Click to expand...
Click to collapse
The problem was not accessing the device using ADB. The problem was I was not able to write to root system. ES Explorer and Root Explorer both did the job for me. I will be putting the final instructions for the process(detailed ones) soon.
Instructions onw how to copy files to root file system on HTC One X with S-ON
1) Unlock and Root your phone. Follow instructions below
http://www.youtube.com/watch?v=gIeq8Jx28cs
and then
http://www.youtube.com/watch?v=80lMHUgxwww
2) Install ES Explorer(File Manager) Link :- https://play.google.com/store/apps/details?id=com.estrongs.android.pop&hl=en
3) Connect device to computer(even if it is not recognized by ADB/Computer)
4) In Phone select Disk drive option. Now the phone's storage will be mounted on your computer as removable device.
5) Copy the files you want to send to phone's root system to any folder here.
6) Change phone's mode to charge only and wait for 2-3 secs(let phone remount sdcard)
7) Open ES Explorer and open menu(those 3 dots at bottom and select Settings)
8) Tick the following options
Up to Root
Root Explorer
Mount File System
9) A dialog box for permission will open Grant it.
10) Now copy files from /sdcard/<Folder where u put files> to where ever you want o copy files to.
11) Long press on file to change permissions and stuff.
Post here if you are stuck someone will surely help you.

[Guide] [Z1s] for Root For Sony Xperia Z1s T-mobile (C6916)

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!

Moto 360 5.0.1 update file

http://android.clients.google.com/p...ned-metallica-LWX48P-from-KNX01S.98cdf4ca.zip
to update:
Go into a shell on the watch with su and...
mount -o rw,remount /dev/block/mmcblk0p15 /cache
mv /sdcard/98cdf4ca90c4693edd379d67cdcf86e283058b81.signed-metallica-LWX48P-from-KNX01S.98cdf4ca.zip /cache/98cdf4ca90c4693edd379d67cdcf86e283058b81.signed-metallica-LWX48P-from-KNX01S.98cdf4ca.zip
echo 'boot-recovery ' > /cache/recovery/command
echo '--update_package=/cache/98cdf4ca90c4693edd379d67cdcf86e283058b81.signed-metallica-LWX48P-from-KNX01S.98cdf4ca.zip' >> /cache/recovery/command
echo '--wipe_cache' >> /cache/recovery/command
echo 'reboot' >> /cache/recovery/command
reboot recovery
Nice ty
See above
abuttino said:
See above
Click to expand...
Click to collapse
I was trying to do it thought ADB I'm just new to this and I ended up re posting in the wrong thread.
Im Not new to flashing via recover on phones but on adb through commands I always feel sketchy about it.
I keep getting permission denied
Ive ran root a few times I have the drivers install right for sure not sure what im doing wrong
NUGZZ420 said:
I keep getting permission denied
Ive ran root a few times I have the drivers install right for sure not sure what im doing wrong
Click to expand...
Click to collapse
Throw an "su" command in the shell before anything else. It will only work if you're rooted.
I don't really get it how to connect via shell to my watch. Is it the same as installing apk's over adb bluetooth debugging bridge?
Could you provide further instructions how to install the update manually?
Thanks!
Kamekazegoldi said:
I don't really get it how to connect via shell to my watch. Is it the same as installing apk's over adb bluetooth debugging bridge?
Could you provide further instructions how to install the update manually?
Thanks!
Click to expand...
Click to collapse
Is your watch rooted? If not, you can't do it
No further questions thanks!
abuttino said:
http://android.clients.google.com/p...ned-metallica-LWX48P-from-KNX01S.98cdf4ca.zip
to update:
Go into a shell on the watch with su and...
mount -o rw,remount /dev/block/mmcblk0p15 /cache
mv /sdcard/98cdf4ca90c4693edd379d67cdcf86e283058b81.signed-metallica-LWX48P-from-KNX01S.98cdf4ca.zip /cache/98cdf4ca90c4693edd379d67cdcf86e283058b81.signed-metallica-LWX48P-from-KNX01S.98cdf4ca.zip
echo 'boot-recovery ' > /cache/recovery/command
echo '--update_package=/cache/98cdf4ca90c4693edd379d67cdcf86e283058b81.signed-metallica-LWX48P-from-KNX01S.98cdf4ca.zip' >> /cache/recovery/command
echo '--wipe_cache' >> /cache/recovery/command
echo 'reboot' >> /cache/recovery/command
reboot recovery
Click to expand...
Click to collapse
Worked (almost) perfect! Except, the "mv" command caused it to error out with "Invalid Arguement:Cross-Device Link" (Due to the implementation of blocked cross device linking with the mv command, bypassable by just cp'ing) Just replaced it with "cp" and the problem was solved.
Though this has already been said, the 4.4w1 insecure boot.img no longer roots 5.0.1. Probably due to incompatibilliuies, I'll work up a new rooted boot.img this weekend. Sadly looks like its going to require flashing the boot.img, not just booting it.
How do you go on a shell on your watch?
You have to have the bootloader unlocked and rooted hooked up via Modded USB cable. Then use the super tool script iin the dev section to install drivers for fastboot. Then back out to that folder make sure you not clicked on anything right click anywhere I think but I right click on the fastboot file while holding the SHIFT key and open in command window the type adb devices to make sure you hooked up right and you have accepted it on your phone Witch you must click accept the adb on your phone to accept the computer access. Once you know your hooked up right type adb shell and boom there you go.
having some trouble.
I've got shell, and then su, i've got a prompt with #
Tried the mv command, and like that other guy, got a cross link error. So i tried cp instead of mv, and now get no such file or directory...
I should mention I'm doing this from adb on Windows. Am I missing something??
Prfndhatrdofman said:
having some trouble.
I've got shell, and then su, i've got a prompt with #
Tried the mv command, and like that other guy, got a cross link error. So i tried cp instead of mv, and now get no such file or directory...
I should mention I'm doing this from adb on Windows. Am I missing something??
Click to expand...
Click to collapse
Try this its what worked for me
coming from KNX01S, but I keep running into "Status 7" with the stock recovery and "Error executing updater script" with TWRP. Anybody have any better luck flashing this?
SOLVED!: I removed the get prop lines in the beginning of the update script and sideloaded in TWRP!
If anybody would like the modified package it can be found here: https://dl.dropboxusercontent.com/u/...360/update.zip
This was not my fix only copied and pasted
NUGZZ420 said:
Try this its what worked for me
coming from KNX01S, but I keep running into "Status 7" with the stock recovery and "Error executing updater script" with TWRP. Anybody have any better luck flashing this?
SOLVED!: I removed the get prop lines in the beginning of the update script and sideloaded in TWRP!
If anybody would like the modified package it can be found here: https://dl.dropboxusercontent.com/u/...360/update.zip
This was not my fix only copied and pasted
Click to expand...
Click to collapse
That Dropbox link seems to be down, do you still have that modified TWRP zip?
Found the original post, here's the original link: https://dl.dropboxusercontent.com/u/9407677/Moto 360/update.zip
Looks like the link text got shortened when copying/pasting, but it's all good now! Thanks for sharing!
Prfndhatrdofman said:
having some trouble.
I've got shell, and then su, i've got a prompt with #
Tried the mv command, and like that other guy, got a cross link error. So i tried cp instead of mv, and now get no such file or directory...
I should mention I'm doing this from adb on Windows. Am I missing something??
Click to expand...
Click to collapse
Make sure your using "/cache" instead of "/cache/"
nissanskylinebam said:
That Dropbox link seems to be down, do you still have that modified TWRP zip?
Found the original post, here's the original link: https://dl.dropboxusercontent.com/u/9407677/Moto 360/update.zip
Looks like the link text got shortened when copying/pasting, but it's all good now! Thanks for sharing!
Click to expand...
Click to collapse
Sorry I had been running all day and beat here my own just in case it helps same zip just my own link
5.0.1 update zip Mirror https://www.dropbox.com/s/naliirhnblh6ihg/update.zip?dl=0
npjohnson said:
Worked (almost) perfect! Except, the "mv" command caused it to error out with "Invalid Arguement:Cross-Device Link" (Due to the implementation of blocked cross device linking with the mv command, bypassable by just cp'ing) Just replaced it with "cp" and the problem was solved.
Though this has already been said, the 4.4w1 insecure boot.img no longer roots 5.0.1. Probably due to incompatibilliuies, I'll work up a new rooted boot.img this weekend. Sadly looks like its going to require flashing the boot.img, not just booting it.
Click to expand...
Click to collapse
Look forward to flashing the Rooted boot.img.
Thank you for doing it.
Update Today
In past day i have update to 5.0.1 LWX48P release. Today i have received automatic update on my watch to 5.0.1 LWX48T release. I don't know what is change but in past day I noticed a problem centering of my display; after update now the display is centered
http://shabbypenguin.com/?developer=Tools&folder=Superuser
flash that in TWRP to get root
latest update: https://mega.co.nz/#!dNBnyT7Q!qtPkmgOV-jrajJAAKDLE6cQWVHyDGi3OsEwmTq5jfOU LWX48T-from-LWX48P follow OP's instructions but change teh file names

Categories

Resources