Develop Bugs

Rooter needed

To make long story short, ive tried so many different ways to root my LG-NITRO p930, using various methods i found on here but couldnt get it to go. Anyone here near Sacramento,CA area who would do it for some cash?.

Doomlords rooting method was the only one that worked for me. It was far easier to use than all the other methods and it only took two times. I tried superoneclick over twenty times and got nowhere with it.
Sent from my LG-P930 using xda app-developers app

Did you try twsparky?
Sent from my LG-P930 using xda app-developers app

I may have when I initially started trying to root this thing but I don't remember. I found the method I mentioned previously and have been using it exclusively ever since.
Sent from my LG-P930 using xda app-developers app

I used DoomLord after superoneclick failed a couple times.
Sent from my LG-P930 using xda app-developers app

DoomsLord
Ive tried doomsloard method:
CONFIRM ALL THE ABOVE THEN
Press any key to continue . . .
--- STARTING ----
--- WAITING FOR DEVICE
--- creating temporary directory
mkdir failed for tmp, File exists
--- cleaning
rm failed for *, No such file or directory
--- pushing zergRush
2501 KB/s (23060 bytes in 0.009s)
--- correcting permissions
--- executing zergRush
[**] Zerg rush - Android 2.2/2.3 local root
[**] (C) 2011 Revolutionary. All rights reserved.
[**] Parts of code from Gingerbreak, (C) 2010-2011 The Android Exploid Crew.
[+] Found a GingerBread ! 0x00000118[*] Scooting ...[*] Sending 149 zerglings ...[*] Sending 189 zerglings ...
[-] Hellions with BLUE flames !
--- WAITING FOR DEVICE TO RECONNECT
if it gets stuck over here for a long time then try:
disconnect usb cable and reconnect it
toggle "USB DEBUGGING" (first disable it then enable it)
--- DEVICE FOUND
--- pushing busybox
3200 KB/s (1075144 bytes in 0.328s)
--- correcting permissions
--- remounting /system
mount: permission denied (are you root?)
--- checking free space on /system
142 KB/s (439 bytes in 0.003s)
export: 13%: bad variable name
--- copying busybox to /system/xbin/
/system/xbin/busybox: cannot open for write: Read-only file system
--- correcting ownership
Unable to chmod /system/xbin/busybox: Read-only file system
--- correcting permissions
Unable to chmod /system/xbin/busybox: Read-only file system
--- installing busybox
--install: applet not found
--- pushing SU binary
failed to copy 'files\su' to '/system/bin/su': Read-only file system
--- correcting ownership
Unable to chmod /system/bin/su: No such file or directory
--- correcting permissions
Unable to chmod /system/bin/su: No such file or directory
--- correcting symlinks
rm failed for /system/xbin/su, Read-only file system
link failed Read-only file system
--- pushing Superuser app
failed to copy 'files\Superuser.apk' to '/system/app/./Superuser.apk': Read-only
file system
--- cleaning
--- rebooting
ALL DONE!!!
Press any key to continue . . .
My phone reboots after what you see above displays, but my phone isnt rooted.
Android version 2.3.5
Baseband P930-MDM9200B-V10J-FEB-26-2012-XX 1
Kernel 2.6.35.11
Build number GRJ90

It may take a few times. Make sure USB debugging is enabled and also that installation of non market apps is enabled. If its not enabled then SU won't be able to install.
Sent from my LG-P930 using xda app-developers app

Yea i did all of that but doesnt seem to work. I'm regreting getting this LG phone -_-

V10J and NO Root: I am FRUSTRATED!

Hi everyone! I got the Nitro yesterday and I have tried EVERY possible method under the sun to get root onto my 2.3.5 V10J stock firmware. I am generally good at stuff, but the unbricking tutorial really confuses me. Is there any other way to just get CWM onto the phone and then install a pre-rooted ROM? Or an easier way to root? I tried superoneclick a 100 times, and it just behaves read only. does not allow the software to access root. This is the error I get with all rooting scripts!
---------------------------------------------------------------
Easy rooting toolkit (v4.0)
created by DooMLoRD
using exploit zergRush (Revolutionary Team)
Credits go to all those involved in making this possible!
---------------------------------------------------------------
[*] This script will:
(1) root ur device using latest zergRush exploit (21 Nov)
(2) install Busybox (1.18.4)
(3) install SU files (binary: 3.0.3 and apk: 3.0.6)
(4) some checks for free space, tmp directory
(will remove Google Maps if required)
[*] Before u begin:
(1) make sure u have installed adb drivers for ur device
(2) enable "USB DEBUGGING"
from (Menu\Settings\Applications\Development)
(3) enable "UNKNOWN SOURCES"
from (Menu\Settings\Applications)
(4) [OPTIONAL] increase screen timeout to 10 minutes
(5) connect USB cable to PHONE and then connect to PC
(6) skip "PC Companion Software" prompt on device
---------------------------------------------------------------
CONFIRM ALL THE ABOVE THEN
Press any key to continue . . .
--- STARTING ----
--- WAITING FOR DEVICE
adb server is out of date. killing...
* daemon started successfully *
--- creating temporary directory
mkdir failed for tmp, File exists
--- cleaning
rm failed for *, No such file or directory
--- pushing zergRush
failed to copy 'files\zergRush' to '/data/local/tmp/./zergRush': Permission deni
ed
--- correcting permissions
Unable to chmod /data/local/tmp/zergRush: No such file or directory
--- executing zergRush
./data/local/tmp/zergRush: not found
--- WAITING FOR DEVICE TO RECONNECT
if it gets stuck over here for a long time then try:
disconnect usb cable and reconnect it
toggle "USB DEBUGGING" (first disable it then enable it)
--- DEVICE FOUND
--- pushing busybox
failed to copy 'files\busybox' to '/data/local/tmp/./busybox': Permission denied
--- correcting permissions
Unable to chmod /data/local/tmp/busybox: No such file or directory
--- remounting /system
/data/local/tmp/busybox: not found
--- checking free space on /system
failed to copy 'files\makespace' to '/data/local/tmp/./makespace': Permission de
nied
Unable to chmod /data/local/tmp/makespace: No such file or directory
./data/local/tmp/makespace: not found
--- copying busybox to /system/xbin/
/data/local/tmp/busybox: cannot open for read: No such file or directory
--- correcting ownership
Unable to chmod /system/xbin/busybox: Read-only file system
--- correcting permissions
Unable to chmod /system/xbin/busybox: Read-only file system
--- installing busybox
--install: applet not found
rm failed for /data/local/tmp/busybox, No such file or directory
--- pushing SU binary
failed to copy 'files\su' to '/system/bin/su': Read-only file system
--- correcting ownership
Unable to chmod /system/bin/su: No such file or directory
--- correcting permissions
Unable to chmod /system/bin/su: No such file or directory
--- correcting symlinks
rm failed for /system/xbin/su, Read-only file system
link failed Read-only file system
--- pushing Superuser app
failed to copy 'files\Superuser.apk' to '/system/app/./Superuser.apk': Read-only
file system
--- cleaning
rm failed for *, No such file or directory
--- rebooting

Apparently there is atm no way to get cwm or cwm recovery on your phone w/out going through oh no!'s rom which as a prerequisite you must follow the unbricking method.
If you want go to my profile and check out my recent posts in the nitro general subforum and youll see my little journey....which others were annoyed with ...lmao.
I am currently rooted, running stock ics and love it. I have no issues phone runs near perfect.
I did not "unbrick" my phone and just flashed an older rom (v18) and rooted.
Sparky's root method is the only method that will root this phone via ics.
I made a thread explaining in detail some steps that were not mentioned.
Dont bother with doomlord, oneclick.
Since the tapatalk search function sucks balls use the xda search function from the actual browser.
Hope that helps. Maybe someone else will chime in.
Dont fear the unbrick.
Take your time
Read slow and also read through other peoples posts and what they did wrong, how they remedied it blah blah...
Dont take any short cuts unless for sure, you know exactly what you are doing.
Make sure you have everything ready and have read through prior to doing it.
Nothing to fear flashing is pretty straight forward.
Just take your time.
:beer:
Sent from my LG-P930 using Tapatalk 2

I went from Stock ATT 2.5.6 V10J to ATT STOCK V10F .Using [GUIDE] Unbrick, Root, And Install CWM by mattman86 . Its long but doable its not even that long really .O tip uninstall all the drivers you might have installed and use the one that come with the unbricking pack ,its the key to the whole thing. Im in CM10 Nightly now .Good luck and dont get frustrated its rootable its just not a one click root.

Just keep trying to run the root. I used super one click and it took me at least 20-30 attempts to successfully root. If it asks you if your version is 2 or higher or fails to push any files to the phone, the root will not take. Just reboot the phone and keep trying.

Try using viperMOD PrimeTime v4.6, that's a lot easier and faster, despite what everyone else says, you can root 10j.
Good Luck

[Q] i cannot root my Samsung Galaxy W (I8150) using DoomLord v.3 rooting toolkit

---------------------------------------------------------------
Easy rooting toolkit (v3.0)
created by DooMLoRD
using exploit zergRush (Revolutionary Team)
Credits go to all those involved in making this possible!
---------------------------------------------------------------
[*] This script will:
(1) root ur device using latest zergRush exploit (16 Nov)
(2) install Busybox (1.18.4)
(3) install SU files (binary: 3.0.3 and apk: 3.0.6)
[*] Before u begin:
(1) make sure u have installed adb drivers for ur device
(2) enable "USB DEBUGGING"
from (Menu\Settings\Applications\Development)
(3) enable "UNKNOWN SOURCES"
from (Menu\Settings\Applications)
(4) [OPTIONAL] increase screen timeout to 10 minutes
(5) connect USB cable to PHONE and then connect to PC
(6) skip "PC Companion Software" prompt on device
---------------------------------------------------------------
CONFIRM ALL THE ABOVE THEN
Press any key to continue . . .
--- STARTING ----
--- WAITING FOR DEVICE
adb server is out of date. killing...
* daemon started successfully *
--- cleaning
--- pushing zergRush"
2882 KB/s (23056 bytes in 0.007s)
--- correcting permissions
--- executing zergRush
[**] Zerg rush - Android 2.2/2.3 local root
[**] (C) 2011 Revolutionary. All rights reserved.
[**] Parts of code from Gingerbreak, (C) 2010-2011 The Android Exploid Crew.
[+] Found a GingerBread ! 0x0002a118
[+] Found a Samsung, running Samsung mode
[*] Scooting ...
[*] Sleeping a bit (~40s)...
[*] Waking !
[*] Sending 149 zerglings ...
[*] Sleeping a bit (~40s)...
[*] Waking !
[*] Sending 189 zerglings ...
[-] Hellions with BLUE flames !
--- WAITING FOR DEVICE TO RECONNECT
if it gets stuck over here for a long time then try:
disconnect usb cable and reconnect it
toggle "USB DEBUGGING" (first disable it then enable it)
--- DEVICE FOUND
--- pushing busybox
3054 KB/s (1075144 bytes in 0.343s)
--- correcting permissions
--- remounting /system
mount: permission denied (are you root?)
--- copying busybox to /system/xbin/
/system/xbin/busybox: cannot open for write: Read-only file system
--- correcting ownership
Unable to chmod /system/xbin/busybox: No such file or directory
--- correcting permissions
Unable to chmod /system/xbin/busybox: No such file or directory
--- installing busybox
/system/xbin/busybox: not found
--- pushing SU binary
failed to copy 'files\su' to '/system/bin/su': Read-only file system
--- correcting ownership
Unable to chmod /system/bin/su: No such file or directory
--- correcting permissions
Unable to chmod /system/bin/su: No such file or directory
--- correcting symlinks
rm failed for /system/xbin/su, Read-only file system
link failed Read-only file system
--- pushing Superuser app
failed to copy 'files\Superuser.apk' to '/system/app/./Superuser.apk': Read-only
file system
--- cleaning
--- rebooting
ALL DONE!!!
Press any key to continue . . .

If you've read the sticky posts in this forum, you should've realized that there is only one method for rooting the W.
-- xda app / Pristine No-Mod CM9b3 / DXKL1 baseband / GT-I8150 --

root methode
pepoluan said:
If you've read the sticky posts in this forum, you should've realized that there is only one method for rooting the W.
-- xda app / Pristine No-Mod CM9b3 / DXKL1 baseband / GT-I8150 --
Click to expand...
Click to collapse
is it Via recovery mode with udapte file .zip... because im stuck, cannot find the file in recovery mode... please help

iriedrum said:
is it Via recovery mode with udapte file .zip... because im stuck, cannot find the file in recovery mode... please help
Click to expand...
Click to collapse
You need CWM or Any other custom recovery first

7amada100 said:
You need CWM or Any other custom recovery first
Click to expand...
Click to collapse
Eh? No need...
Sent from my GT-I8150 using xda app-developers app
---------- Post added at 10:27 AM ---------- Previous post was at 10:24 AM ----------
iriedrum said:
is it Via recovery mode with udapte file .zip... because im stuck, cannot find the file in recovery mode... please help
Click to expand...
Click to collapse
The file *must* be named "update.zip" and it *must* be located in the root directory of the internal SD Card.
Sent from my GT-I8150 using xda app-developers app

Arc Rooting

I want to root my xperia arc s and everytime i wanter to root i get this:
Code:
Easy rooting toolkit (v4.0)
created by DooMLoRD
using exploit zergRush (Revolutionary Team)
Credits go to all those involved in making this possible!
---------------------------------------------------------------[*] This script will:
(1) root ur device using latest zergRush exploit (21 Nov)
(2) install Busybox (1.18.4)
(3) install SU files (binary: 3.0.3 and apk: 3.0.6)
(4) some checks for free space, tmp directory
(will remove Google Maps if required)[*] Before u begin:
(1) make sure u have installed adb drivers for ur device
(2) enable "USB DEBUGGING"
from (Menu\Settings\Applications\Development)
(3) enable "UNKNOWN SOURCES"
from (Menu\Settings\Applications)
(4) [OPTIONAL] increase screen timeout to 10 minutes
(5) connect USB cable to PHONE and then connect to PC
(6) skip "PC Companion Software" prompt on device
---------------------------------------------------------------
CONFIRM ALL THE ABOVE THEN
Press any key to continue . . .
--- STARTING ----
--- WAITING FOR DEVICE
--- creating temporary directory
mkdir failed for tmp, File exists
--- cleaning
rm failed for *, No such file or directory
--- pushing zergRush
1608 KB/s (23060 bytes in 0.014s)
--- correcting permissions
--- executing zergRush
[**] Zerg rush - Android 2.2/2.3 local root
[**] (C) 2011 Revolutionary. All rights reserved.
[**] Parts of code from Gingerbreak, (C) 2010-2011 The Android Exploid Crew.
[+] Found a GingerBread ! 0x00000118[*] Scooting ...[*] Sending 149 zerglings ...[*] Sending 189 zerglings ...
[-] Hellions with BLUE flames !
--- WAITING FOR DEVICE TO RECONNECT
if it gets stuck over here for a long time then try:
disconnect usb cable and reconnect it
toggle "USB DEBUGGING" (first disable it then enable it)
--- DEVICE FOUND
--- pushing busybox
3534 KB/s (1075144 bytes in 0.297s)
--- correcting permissions
--- remounting /system
mount: permission denied (are you root?)
--- checking free space on /system
85 KB/s (439 bytes in 0.005s)
--- Free space on /system : 179448 bytes
--- no cleanup required
--- copying busybox to /system/xbin/
/system/xbin/busybox: cannot open for write: Read-only file system
--- correcting ownership
Unable to chmod /system/xbin/busybox: No such file or directory
--- correcting permissions
Unable to chmod /system/xbin/busybox: No such file or directory
--- installing busybox
/system/xbin/busybox: not found
--- pushing SU binary
failed to copy 'files\su' to '/system/bin/su': Read-only file system
--- correcting ownership
Unable to chmod /system/bin/su: No such file or directory
--- correcting permissions
Unable to chmod /system/bin/su: No such file or directory
--- correcting symlinks
rm failed for /system/xbin/su, Read-only file system
link failed Read-only file system
--- pushing Superuser app
failed to copy 'files\Superuser.apk' to '/system/app/./Superuser.apk': Read-only
file system
--- cleaning
--- rebooting
ALL DONE!!!
Press any key to continue . . .
any idea? I unlocked bootloader.

Are you on GB or ICS?
Sent from my Nexus 7 using XDA Premium HD app

Re: [Q] Clean Install?
If you have the boot loader unlocked than its very easy to root your device.
Note:
Whenever, you flash a stock ftf firmware you will loose root status.
So,having this tool readily available on your desktop is important.
[1]Use the tool from this thread:
[Arc/Arc S]Auto root for unlocked bootloader-no flashing needed-by bazoocase.
[2]Xrecovery-another awesome tool
After you have unlocked your device,I presume you are on stock firmware 0.431 or 0.587.But not rooted,yes.
Now for magic.Run the tool,connect your phone and in less than a second or two your phone will be rooted.With the script in the tool you will now have superuser on your device.
Download busy box from market.
Next run the [2]Xrecovery which will install CWM to your device.
Enjoy flashing ROMs and kernels after this.
For any further enquiries just send me a msg.I will most certainly reply.

[Root] How to root z1s and get it to stick on reboot.

Z1s Root+Reovery+Deodex Android 4.3 Updated 6/18/14​
This was put together by @ayuready1989 and @Tactic13
This Not A Rom "Do NOT WIPE ANYTHING JUST FLASH AS IS"
This is a Patch to keep root on reboot as well as deodex your current rom.[
NO LONGER USED
Please use Root 4.4.4 on z1s
Once you have recovery you can flash this instead of using the script it does not require you to make the script.
First of all we would like to thank @jcase for getting the initial root, @[NUT] for the recovery @xsacha for the ta backup and @RyokoN for some of the tools, if we forgot someone just send us a message.
Okay now for the fun part.​
Make sure that you have usb debugging enabled.
Root with jcase method.
Install SuperSU from market reboot.
Run adb shell su -c "/system/xbin/kill_ric.sh"
Then adb shell su -c "mount -o remount,rw /system"
Install Recovery But use the one for the z1 Locked boatloader.
Finaly Flash Deodex + Root Devhost Minor
Optional
Backup Ta image. Ta Backup
We will keep working on this as well as start working on a rom just wanted to get this out to you guys.
You assume all the stand disclaimers when you flash this that not is to say that we wont help you.

Mine Just in case i need it.

Tactic13 said:
Mine Just in case i need it.
Click to expand...
Click to collapse
+1

This is what i get when trying to install recovery. Supersu working fine. I just used it for TB. Should I try SuperUser instead?
==============================================
= =
= PhilZ Touch, CWM and TWRP Dual Recovery =
= Maintained by [NUT] =
= =
= For Many Sony Xperia Devices =
= =
==============================================
[ 1. Installation on ROM rooted with SuperSU ]
[ 2. Installation on ROM rooted with SuperUser ]
[ 3. Installation on unrooted ROM ]
[ 4. Exit ]
Please choose install action. [1,2,3,4]?1
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
=============================================
Waiting for Device, connect USB cable now...
=============================================
Device found
=============================================
Step2 : Sending the recovery files.
=============================================
9 KB/s (29 bytes in 0.003s)
3847 KB/s (15759 bytes in 0.004s)
244 KB/s (501 bytes in 0.002s)
2880 KB/s (11798 bytes in 0.004s)
5030 KB/s (56662 bytes in 0.011s)
1504 KB/s (3082 bytes in 0.002s)
187 KB/s (385 bytes in 0.002s)
5489 KB/s (657704 bytes in 0.117s)
5318 KB/s (2875482 bytes in 0.528s)
5240 KB/s (2581087 bytes in 0.481s)
5347 KB/s (1845510 bytes in 0.337s)
384 KB/s (8658 bytes in 0.022s)
=============================================
Step3 : Setup of dual recovery.
=============================================
Look at your device and grant supersu access
Press any key to continue AFTER granting root access.
-rwxr-xr-x 1 shell shell 657704 Apr 30 05:38 /data/local/tmp/recovery/busybox
Press any key to continue . . .
##########################################################
#
# Installing XZDR version 2.7.123 BETA
#
#####
Temporarily disabling the RIC service, remount rootfs and /system writable to allow installation.
mount: permission denied (are you root?)
blockdev: applet not found
mount: permission denied (are you root?)
Copy recovery files to system.
cp: can't create '/system/bin/recovery.twrp.cpio.lzma': Read-only file system
cp: can't create '/system/bin/recovery.cwm.cpio.lzma': Read-only file system
cp: can't create '/system/bin/recovery.philz.cpio.lzma': Read-only file system
chmod: /system/bin/recovery.twrp.cpio.lzma: No such file or directory
chmod: /system/bin/recovery.cwm.cpio.lzma: No such file or directory
chmod: /system/bin/recovery.philz.cpio.lzma: No such file or directory
Rename stock mr
mv: can't rename '/system/bin/mr': Read-only file system
Copy mr wrapper script to system.
cp: can't create '/system/bin/mr': File exists
chmod: /system/bin/mr: Read-only file system
Rename stock chargemon
mv: can't rename '/system/bin/chargemon': Read-only file system
Copy chargemon script to system.
cp: can't create '/system/bin/chargemon': File exists
chmod: /system/bin/chargemon: Read-only file system
Copy dualrecovery.sh to system.
cp: can't create '/system/bin/dualrecovery.sh': Read-only file system
chmod: /system/bin/dualrecovery.sh: No such file or directory
Copy rickiller.sh to system.
cp: can't create '/system/bin/rickiller.sh': Read-only file system
chmod: /system/bin/rickiller.sh: No such file or directory
Installing NDRUtils to system.
cp: can't create '/system/app/NDRUtils.apk': Read-only file system
chmod: /system/app/NDRUtils.apk: No such file or directory
Copy disableric to system.
cp: can't create '/system/xbin/disableric': Read-only file system
chmod: /system/xbin/disableric: No such file or directory
Creating /system/.XZDualRecovery to store a backup copy of busybox.
mkdir failed for /system/.XZDualRecovery, Read-only file system
Copy busybox to system.
cp: can't create '/system/xbin/busybox': File exists
cp: can't create '/system/.XZDualRecovery/': Is a directory
chmod: /system/xbin/busybox: Read-only file system
Trying to find and update the gpio-keys event node.
Found and will be using /dev/input/event4!
Trying to find and update the power key event node.
Found and will be monitoring /dev/input/event3!
Speeding up backups.
Make sure firstboot goes to recovery.
=============================================
DEVICE WILL NOW TRY A DATA SAFE REBOOT!
=============================================
=============================================
Your installation has already cleaned up after itself if you see the install.bat/install.sh exit.
=============================================
=============================================
Installation finished. Enjoy the recoveries
=============================================
Press any key to continue . . .

Re run the root as well as the second set of commands and on your phone it should ask you to grant root access to adb. But i installed SuperSu and used option 1.

same here, supersu and option 1,but make sure /sbin/xbin/kill_ric.sh is ran before u install recovery a couple times(2-3) just to make sure.
this is the specific one i used, for winblows V4
http://forum.xda-developers.com/showthread.php?t=2426739

So last night jcase remotely tested the exploit and rooted my Z1s. I installed the recovery this morning as instructed here and then flashed the deodex and root zip. Now my phone cannot achieve root via the adb commands or by itself. Furthermore the su binary that supersu had installed is gone and supersu cannot install it again. Any ideas what happened?
EDIT: Hmm, i installed the updated root method from the OP and that appears to have fixed it. Now to see if root sticks.

themacman1000 said:
So last night jcase remotely tested the exploit and rooted my Z1s. I installed the recovery this morning as instructed here and then flashed the deodex and root zip. Now my phone cannot achieve root via the adb commands or by itself. Furthermore the su binary that supersu had installed is gone and supersu cannot install it again. Any ideas what happened?
EDIT: Hmm, i installed the updated root method from the OP and that appears to have fixed it. Now to see if root sticks.
Click to expand...
Click to collapse
cool. if asked to fix root after cwm flash it seems safe to always chose to fix it

ayuready1989 said:
strange, the zip doesnt touch /system/xbin/su .. try the su fix that cwm asks for when trying to reboot after flashing a zip . ive selected yes and no, still the same result. still had root.. but flash via cwm and apply the fix root fix it asks, dont disable flash recovery though
Click to expand...
Click to collapse
Oh. When I first installed the deodex via philztouch it asked if i wanted to disable flashing of stock recovery. I said yes... That must have been my problem. However, everything works now, even rebooting holds root and system r/w. Also, can you link me to how you installed xposed? Edit: Nevermind, found out how myself

themacman1000 said:
Oh. When I first installed the deodex via philztouch it asked if i wanted to disable flashing of stock recovery. I said yes... That must have been my problem. However, everything works now, even rebooting holds root and system r/w. Also, can you link me to how you installed xposed?
Click to expand...
Click to collapse
alrighty, nice to know it works, thanks for actually giving feedback @themacman1000 now time for the modules and tweaks

themacman1000 said:
Oh. When I first installed the deodex via philztouch it asked if i wanted to disable flashing of stock recovery. I said yes... That must have been my problem. However, everything works now, even rebooting holds root and system r/w. Also, can you link me to how you installed xposed? Edit: Nevermind, found out how myself
Click to expand...
Click to collapse
I installed this apk.
http://dl-count.xposed.info/modules/de.robv.android.xposed.installer_v32_de4f0d.apk
Sent from my iPad using Tapatalk

I'm curious if Z1 roms would work for the Z1s... Considering they're basically the same phone... I did a full backup on mine, now considering trying that out...

I have don't its a pain in the but to get back you will lose everything.
We don't have a 4.4.2 kernel if we did we might be able to.

It's good to see T-Mobile roms,when you're overseas you can use WiFi Calling to call back to the US free.:thumbup::thumbup:
Sent from my HTC One_M8 using Tapatalk 2

Well you have the start right here it deodex the rom and root sticks

Tactic13 said:
I have don't its a pain in the but to get back you will lose everything.
We don't have a 4.4.2 kernel if we did we might be able to.
Click to expand...
Click to collapse
I was actually thinking 4.3 roms... I figured 4.4 wouldn't work, but 4.3 maybe?

adb shell chmod 755 /data/local/tmp/pwn
/system/bin/sh: chmod755: not found
Please help

jahjah440 said:
adb shell chmod 755 /data/local/tmp/pwn
/system/bin/sh: chmod755: not found
Please help
Click to expand...
Click to collapse
There's supposed to be a space between chmod and 755.

Elysian893 said:
There's supposed to be a space between chmod and 755.
Click to expand...
Click to collapse
Thank you I actually got it working before I had forgotten to give elevated permission to write to /data
I have achieved root!

what are the steps to installing the rom for this phone? do we have to delete anything in recovery?
---------- Post added at 06:03 PM ---------- Previous post was at 05:51 PM ----------
how do i backup the TA, complete sony noob here
---------- Post added at 06:05 PM ---------- Previous post was at 06:03 PM ----------
LaosPerson said:
what are the steps to installing the rom for this phone? do we have to delete anything in recovery?
---------- Post added at 06:03 PM ---------- Previous post was at 05:51 PM ----------
how do i backup the TA, complete sony noob here
Click to expand...
Click to collapse
nevermind, i just had to read the z2 link thing