[TRICK]Installing Google Dialer after towelroot - Verizon Galaxy Note 3 Q&A, Help & Troubleshooting

I spent a few minutes struggling to install Google Dialer after rooting my latest OTA note 3 with towelroot. Here's what I discovered worked (works for putting anything in the system folder):
Step 1: Install ADB on your computer, push tr.apk (towelroot) and install. Run towelroot, install busybox
Step 2: Open up two command prompts on your computer. In one, ADB shell and su. I will refer to this as "the su terminal" for now. Ignore the second for a bit.
Step 3: type "mount | grep system" and extract the first bit:
Code:
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,seclabel,relatime,
data=ordered 0 0
The important part is the first section, /dev/block/platform/msm_sdcc.1/by-name/system. Also notice that it is mounted as RO, read only.
Step 4: type the following, replacing the /dev/... line with your own from above (maybe the same, idk)
Code:
# mount -o rw,remount /dev/block/platform/msm_sdcc.1/by-name/system
Step 5: Confirm it worked by running mount | grep system again:
Code:
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 rw,seclabel,relatime,
data=ordered 0 0
Note that it is now RW.
Now we run into an issue, if you go to your second terminal and try to use ADB to push to system it still says read only. If you go to adb and try to adb root it says disabled for production builds. If you go into an app such as ES file manager, it still says read only. I also tried pushing the file to the sd card and using MV to move it while in a su shell, but that didn't work either (error about cross device something or other)
However... I found a workaround.
Step 6: On the second terminal, use adb to push your file to somewhere on your sd card, in my case, /storage/emulated/legacy/ worked.
Step 7: on the second terminal, adb shell and su.
Step 8: On the first terminal cd /system/priv-app/ (or any folder where you need to write something)
Step 8.?: On the second terminal cd /storage/emulated/legacy/
Step 9: Run the following commands
First terminal:
Code:
nc -l -p 1234 > com.google.android.dialer-1.1.apk
Second Terminal:
Code:
nc localhost 1234 < com.google.android.dialer-1.1.apk
Finally, on the first terminal, chmod 777 com.google.android.dialer-1.1.apk, and install by tapping within ES file manager or similar, then adb reboot.
You will need to use a tool to create a shortcut for the application, it does not get one this way.
You now have the google dialer installed on your Verizon Note 3, rooted with TowelRoot.
Trick can be used to push to the system folder without adb root or adb remount working.
Enjoy!

Related

How to root the Hero using a MAC

I didn't find any mentions of this in the other threads or a thread dedicated to this, but just wanted to point out that it is very easy to do this on a Mac.
You will need to follow the same instructions in the other guides, but you can do it all from the Mac OS Terminal easily and no need to install drivers, just like you would with Linux.
In case someone wants step by step instructions, here they are modified for Mac OS:
Original instructions by chuckhriczko http://forum.xda-developers.com/showthread.php?t=581577
Step 1:
First you need to download the Android SDK. You can get it from http://developer.android.com/sdk/index.html. Download the Mac OS version and remember where the android-sdk-mac folder is (most likely in your Downloads folder)
The next thing we download is asroot2. This is a script that was developed that runs an exploit in Android's linux that allows us to run root. The link for that is here: http://forum.xda-developers.com/attachment.php?attachmentid=244212&d=1257621154. Unzip that file and place it in a directory of your choice (I used android-sdk-mac/tools). Also download http://www.androidspin.com/downloads.php?dir=amon_ra/RECOVERY/&file=recovery-RA-heroc-v1.2.3.img and place that into the same directory you extracted asroot2.
Step 2:
Connect the phone to the USB port.
Open a terminal and cd into the directory that you extracted the sdk into. Then cd into the tools directory. Then run the following commands:
sudo ./adb push /directory_you_placed_asroot2/asroot2 /data/local/
sudo ./adb shell chmod 0755 /data/local/asroot2
sudo ./adb shell /data/local/asroot2 /system/bin/sh
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cd /system/bin
cat sh > su
chmod 4755 su
type exit until you are back to your Mac's prompt.
Now your phone is officially rooted! We arent done yet though. Now you need to flash the recovery image. If you are still in adb shell type in exit until you are out. You should be in the directory where you extracted the recovery image. If not go there. Type in the following:
sudo /.adb push recovery-RA-heroc-v1.2.3.img /sdcard/
Once that is done, type in sudo ./adb shell. If your command prompt is a dollar sign then type in su and press enter. If it is a pound sign you are good. Then type in the following:
flash_image recovery /sdcard/recovery-RA-heroc-v1.2.3.img
Once that is finished you are done. To reboot into recovery type in
sudo ./adb shell reboot recovery
If you are already in the shell, just type
reboot recovery
You should reboot into recovery mode and you can go from here. You can do a nandroid backup and then follow the other guides to install a different ROM or any other things you want to do.
If there are no instructions for Mac, just follow the Linux/Ubuntu instructions as they will be very similar if not the same.
Actually...
http://forum.xda-developers.com/showthread.php?t=581686
This is the thread I used to root my Hero CDMA from my Macbook, worked just fine...Thanks anyways for giving some love to macusers, guides are usually windows only.
I thought it was weird that there wasn't a Mac dedicated thread. I guess the search doesn't like 3 letter words.

I can´t install apk to my X10i via CMD adb??

Can not find a usbdriver for ADB that works for sony ericsson x10i?
http://code.google.com/p/adb-file-explorer/
//dong 2007
dong2007 said:
Can not find a usbdriver for ADB that works for sony ericsson x10i?
Click to expand...
Click to collapse
Not looked hard enough ADB, Fastboot, and Nandroid for Noobs
It is not for X10i, but G1 and droid?
Shall i first install Android SDK?
dong2007 said:
It is not for X10i, but G1 and droid?
Click to expand...
Click to collapse
Worked for me.
dong2007 said:
Shall i first install Android SDK?
Click to expand...
Click to collapse
nephron said:
This Guide is for windows only. If you are using Mac OS X please go here: ADB For Dummies
If you are using Linux please go here: [HOW-TO]Set up Android SDK/ADB/Fastboot on Ubuntu Linux
--------------------------------------------------------------------------
Things you need:
Android SDK - Download
Winrar - Download (32bit) Download (64bit)
Windows PC
USB Cable
--------------------------------------------------------------------------
Setting up the Android SDK
Download the file from above
Unzip to your desktop
Take the "android-sdk-windows" folder and move it to the root of your hard drive (C:\)
Right click on My Computer and click properties
Select the Advanced Tab or Advanced System Setting (Vista/Windows 7)
Select Environment Variables...
Press New
For Variable Name type: adb
For Variable Value type: C:\android-sdk-windows\tools
Now, [Get new sdk (1.5r3) to work]
1. Run SDK Setup.exe
2. If it gives you an error go to settings and click on "Force http//....."
3. Select all options and let it download and install
If you cant get the setup to work, Download the USB-DRIVERS folder - HERE (Windows XP/Vista/Windows 7)
--------------------------------------------------------------------------
Preparing your phone for ADB
Go to Settings on your phone
Select Applications
Select Development
Make sure 'USB Debugging' is checked
--------------------------------------------------------------------------
Installing Drivers
Plug in your phone through USB and DO NOT MOUNT IT!!!!!
Your computer should see a new device and try to install Android 1.0 driver (If it doesnt, scroll down to the "Im not getting a notification of Android ADB when i plug in my USB" section)
Let it load
Once it cant find them select "Install drivers from my pc"
The drivers you need are in the Android SDK 1.5r2 folder (C:\android-sdk-windows\usb_driver)
Depending on your OS pick x86 or amd64
You ADB Android Device should now be installed! Good Job
For Android SDK 1.5r3+
1. Run SDK Setup.exe
2. If it gives you an error go to settings and click on "Force http//....."
3. Select all options and let it download and install
If you cant get the setup to work, Download the USB-DRIVERS folder - HERE (Windows XP/Vista/Windows 7)
--------------------------------------------------------------------------
Check if your phone is detected by ADB
Open up Command Prompt (Go to run, type in cmd, press enter)
Type in
Code:
cd C:\android-sdk-windows\tools === Press Enter
adb devices === You should see your device listed
adb shell === you should see # in the next line
Now you are all set to run adb commands
Note: for a list of commands type in 'adb' in cmd
CONGRATS YOU NOW HAVE ADB FULLY RUNNING!
--------------------------------------------------------------------------
"Im not getting a notification of Android ADB when i plug in my USB"
Why: Your computer has detected your phone but as a protable device and as a storage device.
Fix: This took me a lot of research and time to figure out so this is what your are going to do.
First download USBDeview - Here
Unzip it
Run USBDeview.exe as Administrator
You will see all drivers being used on your computer
Highlight and Uninstall all drivers with the description have HTC Android (Should be 3 of them)
Right Click on the driver and press uninstall
Once done, Unplug your phone and plug it back in
You should now get the notification of the ADB device
Follow the steps above to install the drivers
--------------------------------------------------------------------------
When Typing just adb in cmd you will get whats called a "usage doc" which gives you a lits of commands that you can use:
Code:
-d - directs command to the only connected USB devic
e
returns an error if more than one USB device is
present.
-e - directs command to the only running emulator.
returns an error if more than one emulator is r
unning.
-s <serial number> - directs command to the USB device or emulator w
ith
the given serial number
-p <product name or path> - simple product name like 'sooner', or
a relative/absolute path to a product
out directory like 'out/target/product/sooner'.
If -p is not specified, the ANDROID_PRODUCT_OUT
environment variable is used, which must
be an absolute path.
devices - list all connected devices
device commands:
adb push <local> <remote> - copy file/dir to device
adb pull <remote> <local> - copy file/dir from device
adb sync [ <directory> ] - copy host->device only if changed
(see 'adb help all')
adb shell - run remote shell interactively
adb shell <command> - run remote shell command
adb emu <command> - run emulator console command
adb logcat [ <filter-spec> ] - View device log
adb jdwp - list PIDs of processes hosting a JDWP transport
adb install [-l] [-r] <file> - push this package file to the device and instal
l it
('-l' means forward-lock the app)
('-r' means reinstall the app, keeping its data
)
adb uninstall [-k] <package> - remove this app package from the device
('-k' means keep the data and cache directories
)
adb bugreport - return all information from the device
that should be included in a bug report.
adb help - show this help message
adb version - show version num
scripting:
adb wait-for-device - block until device is online
adb start-server - ensure that there is a server running
adb kill-server - kill the server if it is running
adb get-state - prints: offline | bootloader | device
adb get-serialno - prints: <serial-number>
adb status-window - continuously print device status for a specifie
d device
adb remount - remounts the /system partition on the device re
ad-write
adb root - restarts adb with root permissions
networking:
adb ppp <tty> [parameters] - Run PPP over USB.
Note: you should not automatically start a PDP connection.
<tty> refers to the tty for PPP stream. Eg. dev:/dev/omap_csmi_tty1
[parameters] - Eg. defaultroute debug dump local notty usepeerdns
adb sync notes: adb sync [ <directory> ]
<localdir> can be interpreted in several ways:
- If <directory> is not specified, both /system and /data partitions will be u
pdated.
- If it is "system" or "data", only the corresponding partition
is updated.
--------------------------------------------------------------------------
Commands that you should know
adb push - Insert file to phone such as Stock.apk to /data/app_s
Code:
adb push <pathtofile.apk> <file system location> - Example: adb push c:\app.apk /data/app
adb pull - Remove file from phone such as Stock.apk from /data/app_s
Code:
adb pull <pathtofile.apk> - Example: adb pull /data/app_s/Stock.apk
adb install - Install app to phone
Code:
adb install <path to file> - Example: adb install c:/apps/apps2sd.apk
adb uninstall - Uninstall app from phone
Code:
adb uninstall <name of application> - Example: adb uninstall linda.apk
For more ADB Commands go - Here
--------------------------------------------------------------------------
Thats it for ADB! Congrats and if you have any questions please ask me or if anything is missing or not correct please tell me. I got all of this from research and personal experience.
Click to expand...
Click to collapse
XperiaX10iUser said:
Worked for me.
Click to expand...
Click to collapse
Okej I will try it out..
I can´t install Calculator.apk or the modified youtube.apk (High quality set as default) on my X10i????
for the calculator(is it a system apk) ? if yes then you have to push it to /system/app, if not try installing after signing it.
For youtube.apk i am sure it is a system apk and you need to push it to system/app
realunited123 said:
for the calculator(is it a system apk) ? if yes then you have to push it to /system/app, if not try installing after signing it.
For youtube.apk i am sure it is a system apk and you need to push it to system/app
Click to expand...
Click to collapse
I tried this method:
adb shell mount -o remount,rw -t yaffs2 /dev/block/mtdblock2/system
adb push YouTube.apk /sdcard/YouTube.apk
adb shell dd if=/sdcard/YouTube.apk of=/system/app/YouTube.apk
adb shell rm /sdcard/YouTube.apk
adb shell reboot
but still falied ?
I have obviously put youtube.apk into SDcard folder
dong2007 said:
I tried this method:
adb shell mount -o remount,rw -t yaffs2 /dev/block/mtdblock2/system
adb push YouTube.apk /sdcard/YouTube.apk
adb shell dd if=/sdcard/YouTube.apk of=/system/app/YouTube.apk
adb shell rm /sdcard/YouTube.apk
adb shell reboot
but still falied ?
I have obviously put youtube.apk into SDcard folder
Click to expand...
Click to collapse
looking at the screen shot you gave i am sure you haven't pushed it to sdcard .
it should be
Code:
adb push "the path where you have the apk" /sdcard/YouTube.apk
unless you have copied it to android-sdk folder.
And it seems it didn't mount the system to r/w .
Try these:
Code:
adb shell mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
adb push "the path where you have the apk" /sdcard/YouTube.apk
adb shell dd if=/sdcard/YouTube.apk of=/system/app/YouTube.apk
adb reboot
realunited123 said:
looking at the screen shot you gave i am sure you haven't pushed it to sdcard .
it should be
Code:
adb push "the path where you have the apk" /sdcard/YouTube.apk
unless you have copied it to android-sdk folder.
And it seems it didn't mount the system to r/w .
Try these:
Code:
adb shell mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
adb push "the path where you have the apk" /sdcard/YouTube.apk
adb shell dd if=/sdcard/YouTube.apk of=/system/app/YouTube.apk
adb reboot
Click to expand...
Click to collapse
now I get this message
Try This....
dong2007 said:
now I get this message
Click to expand...
Click to collapse
First step push the .apk file to your sdcard. then unmount your sdcard.
Then...
Code:
adb shell [B]{press enter}[/B]
$ su
su
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
note the space between the /mtdblock2 and /system...[you typed it without the space the first time]...
now check with the mount command...
Code:
# mount
there should be a few lines of output check for this one...
Code:
/dev/block/mtdblock2 /system yaffs2 rw 0 0
Note the "rw".... it indicates your fs is mounted now as read-write if it is "ro" [read only] then you made a mistake somewhere along the line...
if it is mounted succesfully as rw... then try this...
Code:
#dd if=/sdcard/YouTube.apk of=/system/app/YouTube.apk
then
Code:
#reboot
hope it helps...
dong2007 said:
now I get this message
Click to expand...
Click to collapse
well have you rooted your phone ? which method did you use ?
realunited123 said:
well have you rooted your phone ? which method did you use ?
Click to expand...
Click to collapse
I use Universal Androot (One Click Root), and my phone are rooted. I can use Marketacces, TB, root explorer and Quickbot...
dong2007 said:
I use Universal Androot (One Click Root), and my phone are rooted. I can use Marketacces, TB, root explorer and Quickbot...
Click to expand...
Click to collapse
OK. Maybe reboot you phone and try again ?
sam_a200 said:
First step push the .apk file to your sdcard. then unmount your sdcard.
Then...
Code:
adb shell
$ su
su
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
note the space between the /mtdblock2 and /system...[you typed it without the space the first time]...
now check with the mount command...
Code:
# mount
there should be a few lines of output check for this one...
Code:
/dev/block/mtdblock2 /system yaffs2 rw 0 0
Note the "rw".... it indicates your fs is mounted now as read-write if it is "ro" [read only] then you made a mistake somewhere along the line...
if it is mounted succesfully as rw... then try this...
Code:
#dd if=/sdcard/YouTube.apk of=/system/app/YouTube.apk
then
Code:
#reboot
hope it helps...
Click to expand...
Click to collapse
Still not working, i get this message.
Shall i mount or unmount my sdcard, when I start cmd??
I have the unmount...
realunited123 said:
OK. Maybe reboot you phone and try again ?
Click to expand...
Click to collapse
do it automatically via cmd when I use the formula which
(it is actually the only Ossetians it makes the mobile..)
adb shell mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
adb push YouTube.apk /sdcard/YouTube.apk
adb shell dd if=/sdcard/YouTube.apk of=/system/app/YouTube.apk
adb shell rm /sdcard/YouTube.apk
adb shell reboot
dong2007 said:
Still not working, i get this message.
Shall i mount or unmount my sdcard, when I start cmd??
I have the unmount...
Click to expand...
Click to collapse
you don't need to mount the sdcard... Maybe try ADB magic ? search the forums for it.
dong2007 said:
Still not working, i get this message.
Shall i mount or unmount my sdcard, when I start cmd??
I have the unmount...
Click to expand...
Click to collapse
Please do read my post again...edited it with further explanations... after typing "adb shell" press enter you will get a new line with "$" symbol... now type "su"... and go on...
sam_a200 said:
Please do read my post again...edited it with further explanations... after typing "adb shell" press enter you will get a new line with "$" symbol... now type "su"... and go on...
Click to expand...
Click to collapse
Now i get message "permission denied" :S
Now can i install the modifed Youtube apk via astro :S
so something must be right
I´ve the modified youtube installed now on my X10i, and it starting with high quality now

Velocity Cruz Tablet Bloatware Removal (ADB Method)

How to Remove Bloatware from the Velocity Cruz Tablet
Downloads and Setup
Unfortunately, I can't post links in the forum (yet!). For the links to these sources, check out my post with the same title on the Slatedroid Forum...If someone with link posting privileges would be willing to add the links below, I would greatly appreciate it.
1] Download and install the ADB drivers on your device from the Velocity Micro support site. Detailed instructions are available on their site.
2] Download and install the Android SDK on your computer.
3] Connect your Tablet to your computer via the USB cable and mount the device
4] Open your SDK directory on your desktop computer and navigate to the tools directory
5] Write down or copy the directory path to this tools directory (you will use it again below!)
Remove the Bloat
6] For Windows users, select Run from your Start menu
7] Type cmd.exe in the text field and click ok
8] At the command line, use the following series of commands:
cd C:\xxx\android-sdk-windows\tools (where the xxx is the path to your SDK directory)
adb shell (you should see a # sign after this)
cd /system/app (this changes your directory to the app directory on the Tablet where the apk's are located)
ls (optional: will allow you to view all of the apk's that are installed so that you know what to remove)
mount -o remount,rw /system (provide yourself with write permission on the system directory to remove files)
Then for each of the apk files that you want to remove, type:
rm /system/app/filename.apk (replace filename with the actual name of the file)
You can change the system directory permission back to read only with the following command if you would like:
mount -o remount,r /system
Copy and Paste
>cd C:\xxx\android-sdk-windows\tools
>adb shell
# cd /system/app
#ls
#mount -o remount,rw /system
#rm /system/app/filename.apk
#mount -o remount,r /system

Ad Blocking on ZTE Open

Until there are ad blocking apps for FFOS it needs a DIY method.
I'll assume you know how to use adb and have it set up on your machine. I'll also assume you have rooted your phone following the instructions here.
I use Linux so my commands may be a bit off in places.
1. Collect a suitable hosts file. I used the one on my Android phone but this one seems to update regularly http://winhelp2002.mvps.org/hosts.txt
2. Save the file as 'hosts' to a known location on your PC.
3. Open a shell window (command window) on your PC and check adb works.
Code:
adb devices
should return roamer2. If not, on your phone, go to settings > More Information > Developer - and check Remote Debugging.
4. In the shell window - change directory to where you have saved the hosts file. then type:-
Code:
adb push hosts /sdcard/
5. When that completes type:-
Code:
adb shell
you'll see $ prompt
Code:
su
If you are rooted correctly you'll see # prompt
Code:
mount -o remount,rw /system
Mounts the system folder for read / write permissions.
Code:
cat /system/etc/hosts
Should show just '127.0.0.1 localhost'
Save this if you want as hosts.old
Code:
busybox mv /system/etc/hosts /system/etc/hosts.old
Now replace the hosts file with the new one:-
Code:
busybox mv /sdcard/hosts /system/etc/hosts
To check your hosts file has been replaced type
Code:
cat /system/etc/hosts
And lots of domain names will whiz past.
All done.

[ROOT][LB] Xperia Z (C6602) running Android 5.0.2 (10.6.A.0.454)

Hi Everyone,
Recently I have updated my XZ to lollipop 5.0.2 and after updating the Root is lost. I have been struggling to Root the latest firmware and finally I managed to get it rooted. I am posting the instructions so that it might help anyone.
I have a Locked Bootlaoder but it should also work with Unlocked Bootloader.
This has been tested on Xperia Z C6602, Lollipop 5.0.2 (FW: 10.6.A.0.454) and I will not be responsible if you try it on other device and if you do not follow the instructions carefully and accidently mess up with your phone.
Prerequisites
1. Upgrade to Lollipop 5.0.2.
2. Install drivers and configure ADB on your PC.
3. Enable USB debugging on your phone and Allow installation of apps from unknown sources under security settings.
Read the instructions carefully before proceeding.
Steps:-
1. Go to my google drive link and download the data.zip file. https://drive.google.com/file/d/0B1LQ910-5UYpNk5udEF4Qnd6T2M/view
2. Extract the contents into your working ADB directory (where adb.exe is located).
3. Connect your phone to PC via USB cable.
3. Copy KingRoot-4.1.0.249.apk file to your phone. Install the apk and run it. Make sure you are connected to internet as the KingRoot tool uses internet connection to download suitable exploit for your device on the go. After you run it, click Try Root option and let it complete till 100%. It will confirm that Rooting is successful. Now your phone is rooted.
If you do not like KingRoot and KingUser (for any reason) and want to switch to SuperSU then follow these steps:
1. Make sure you have extracted all the apps from data.zip into ADB directory. Browse to your ADB directory, press & hold Shift Key on Keyboard then right click on empty space to open context menu and select Open command window here. In command windows, type “adb devices” without quotes. You should be able to see your device listed. Then type the following commands carefully in same order (copy paste is better way to prevent any typo )
adb push su /data/local/tmp
adb push busybox /data/local/tmp
adb shell
2. You will be taken to a shell prompt with $ sign. In the shell type the following commands and keep your eye on your phone, when prompted, give the access permission:
su
mount -o remount,rw /system
cat /data/local/tmp/su >/system/xbin/daemonsu && chmod 0755 /system/xbin/daemonsu
cat /data/local/tmp/busybox >/system/xbin/busybox && chmod 0755 /system/xbin/busybox
daemonsu -d &
Leave the command Window running and do not disconnect your phone while you continue with the rest of steps.
3. Open the KingUser app in your phone, open settings (at the top right corner) and click Root authorization setting and then Remove Root permission. The app will be uninstalled automatically.
4. Uninstall the other two remaining KingRoot apps from your phone (KingRoot and the other one with Chinese language and the blue icon).
5. Go back to the Command window running adb, and type the following commands:
cat /data/local/tmp/su > /system/xbin/su && chmod 0755 /system/xbin/su
busybox chattr -ia /system/xbin/ku.sud
busybox chattr -ia /system/xbin/supolicy
busybox chattr -ia /system/xbin/pidof
rm /system/xbin/ku.sud
rm /system/xbin/supolicy
rm /system/xbin/pidof
rm /system/bin/debuggerd
rm /system/bin/debuggerd_real
rm /system/bin/debuggerd64
busybox chattr -ia /system/bin/install-recovery.sh
busybox chattr -ia /system/bin/rt.sh
rm /system/bin/install-recovery.sh
rm /system/bin/rt.sh
busybox chattr -ia /system/bin/.usr/.ku
rm -rf /system/bin/.usr
rm /system/usr/icu/icusuflag.conf
busybox chattr -ia /system/usr/iku/isu
rm -rf /system/usr/iku
rm /system/kroot_*
rm /sdcard/kr-stock-conf
rm -rf /sdcard/Kingroot
Again leave this command window running and do not disconnect your phone.
6. Copy Superuser.apk file (from extracted data.zip folder) into phone’s sdcard.
7. Go to your phone and Install Superuser.apk, Run it and let it update the SU binary.
8. Reboot your phone and enjoy the ROOT access on your latest Android 5.0.2 Lollipop.
I have used King's Root to root my phone. My issue is random reboot whenever an app tires to get root access. And titanium backup is not able to backup (it keeps on saying insufficient storage on 20GB free storage area) or delete any app. Plus, I also get random reboot whenever an app having root access is updated over Play Store. And from random reboot it reboots some times and sometimes it doesn't reboot.
So, if anyone having same issue kindly ping back.
(I will post update after reflashing the ftf)
Replace KingUser app with SuperSU
DrXperience said:
I have used King's Root to root my phone. My issue is random reboot whenever an app tires to get root access. And titanium backup is not able to backup (it keeps on saying insufficient storage on 20GB free storage area) or delete any app. Plus, I also get random reboot whenever an app having root access is updated over Play Store. And from random reboot it reboots some times and sometimes it doesn't reboot.
So, if anyone having same issue kindly ping back.
(I will post update after reflashing the ftf)
Click to expand...
Click to collapse
To deal with random reboot issue, I would suggest you to replace KingUser app with SuperSU as described above.
For TitaniumBackup issue, try this:
Open TitaniumBackup, Go to MENU -- Preferences -- Backup folder location.
You will see Storage provider: (Click to change) and you will see multiple option of storage providers. Select second option DocumentProvider Storage and then click on SD Card option and at the bottom of screen you will see select "SD Card". Click on this option. It is important that you do not select any folder inside SD Card, you only have to select the SD Card option. Now select <<Create a new folder>> and then select USE THE CURRENT FOLDER.
To make it more clear, I have attached the snapshots, please go through snapshots one by one and you will be able to fix insufficient free storage error in TB.
SurenderK said:
To deal with random reboot issue, I would suggest you to replace KingUser app with SuperSU as described above.
For TitaniumBackup issue, try this:
Open TitaniumBackup, Go to MENU -- Preferences -- Backup folder location.
You will see Storage provider: (Click to change) and you will see multiple option of storage providers. Select second option DocumentProvider Storage and then click on SD Card option and at the bottom of screen you will see select "SD Card". Click on this option. It is important that you do not select any folder inside SD Card, you only have to select the SD Card option. Now select <<Create a new folder>> and then select USE THE CURRENT FOLDER.
To make it more clear, I have attached the snapshots, please go through snapshots one by one and you will be able to fix insufficient free storage error in TB.
Click to expand...
Click to collapse
Okay I will give it a shot :highfive:
And you have not provided download link. Provide that in your first post.
Download link sent
DrXperience said:
And you have not provided download link. Provide that in your first post.
Click to expand...
Click to collapse
Hey DrXperience,
Check your PM, I have sent the download link through PM....
Try both links, one should be working
can i have download link plz?
SmunksRiley said:
can i have download link plz?
Click to expand...
Click to collapse
Hey SmunksRiley,
Please check your PM. I have sent the link.
Sent from my C6602 using xda Forums PRO
hi sir
sir can i have a link to i need to replace kings app to avoid random reboot
bagsey said:
sir can i have a link to i need to replace kings app to avoid random reboot
Click to expand...
Click to collapse
Hey, please check your PM. I have sent the download link
Sent from my C6602 using xda Forums PRO
SurenderK said:
Hi Everyone,
Recently I have updated my XZ to lollipop 5.0.2 and after updating the Root is lost. I have been struggling to Root the latest firmware and finally I managed to get it rooted. I am posting the instructions so that it might help anyone.
I have a Locked Bootlaoder but it should also work with Unlocked Bootloader.
This has been tested on Xperia Z C6602, Lollipop 5.0.2 (FW: 10.6.A.0.454) and I will not be responsible if you try it on other device and if you do not follow the instructions carefully and accidently mess up with your phone.
Prerequisites
1. Upgrade to Lollipop 5.0.2.
2. Install drivers and configure ADB on your PC.
3. Enable USB debugging on your phone and Allow installation of apps from unknown sources under security settings.
Read the instructions carefully before proceeding.
Steps:-
1. Go to my google drive link and download the data.zip file. https://drive.google.com/file/d/0B1LQ910-5UYpNk5udEF4Qnd6T2M/view
2. Extract the contents into your working ADB directory (where adb.exe is located).
3. Connect your phone to PC via USB cable.
3. Copy KingRoot-4.1.0.249.apk file to your phone. Install the apk and run it. Make sure you are connected to internet as the KingRoot tool uses internet connection to download suitable exploit for your device on the go. After you run it, click Try Root option and let it complete till 100%. It will confirm that Rooting is successful. Now your phone is rooted.
If you do not like KingRoot and KingUser (for any reason) and want to switch to SuperSU then follow these steps:
1. Make sure you have extracted all the apps from data.zip into ADB directory. Browse to your ADB directory, press & hold Shift Key on Keyboard then right click on empty space to open context menu and select Open command window here. In command windows, type “adb devices” without quotes. You should be able to see your device listed. Then type the following commands carefully in same order (copy paste is better way to prevent any typo )
adb push su /data/local/tmp
adb push busybox /data/local/tmp
adb shell
2. You will be taken to a shell prompt with $ sign. In the shell type the following commands and keep your eye on your phone, when prompted, give the access permission:
su
mount -o remount,rw /system
cat /data/local/tmp/su >/system/xbin/daemonsu && chmod 0755 /system/xbin/daemonsu
cat /data/local/tmp/busybox >/system/xbin/busybox && chmod 0755 /system/xbin/busybox
daemonsu -d &
Leave the command Window running and do not disconnect your phone while you continue with the rest of steps.
3. Open the KingUser app in your phone, open settings (at the top right corner) and click Root authorization setting and then Remove Root permission. The app will be uninstalled automatically.
4. Uninstall the other two remaining KingRoot apps from your phone (KingRoot and the other one with Chinese language and the blue icon).
5. Go back to the Command window running adb, and type the following commands:
cat /data/local/tmp/su > /system/xbin/su && chmod 0755 /system/xbin/su
busybox chattr -ia /system/xbin/ku.sud
busybox chattr -ia /system/xbin/supolicy
busybox chattr -ia /system/xbin/pidof
rm /system/xbin/ku.sud
rm /system/xbin/supolicy
rm /system/xbin/pidof
rm /system/bin/debuggerd
rm /system/bin/debuggerd_real
rm /system/bin/debuggerd64
busybox chattr -ia /system/bin/install-recovery.sh
busybox chattr -ia /system/bin/rt.sh
rm /system/bin/install-recovery.sh
rm /system/bin/rt.sh
busybox chattr -ia /system/bin/.usr/.ku
rm -rf /system/bin/.usr
rm /system/usr/icu/icusuflag.conf
busybox chattr -ia /system/usr/iku/isu
rm -rf /system/usr/iku
rm /system/kroot_*
rm /sdcard/kr-stock-conf
rm -rf /sdcard/Kingroot
Again leave this command window running and do not disconnect your phone.
6. Copy Superuser.apk file (from extracted data.zip folder) into phone’s sdcard.
7. Go to your phone and Install Superuser.apk, Run it and let it update the SU binary.
8. Reboot your phone and enjoy the ROOT access on your latest Android 5.0.2 Lollipop.
Click to expand...
Click to collapse
The following lines in script gives error
busybox chattr -ia /system/xbin/ku.sud
chattr: stat /system/xbin/ku.sud: No such file or directory
busybox chattr -ia /system/bin/.usr/.ku
chattr: stat /system/bin/.usr/.ku: No such file or directory
busybox chattr -ia /system/usr/iku/isu
chattr: stat /system/bin/usr/iku/isu: No such file or directory
DrXperience said:
The following lines in script gives error
busybox chattr -ia /system/xbin/ku.sud
chattr: stat /system/xbin/ku.sud: No such file or directory
busybox chattr -ia /system/bin/.usr/.ku
chattr: stat /system/bin/.usr/.ku: No such file or directory
busybox chattr -ia /system/usr/iku/isu
chattr: stat /system/bin/usr/iku/isu: No such file or directory
Click to expand...
Click to collapse
Hi,
Ignore the error if it says No such file or directory. Proceed to next commands and once completed reboot your device. You will get SuperSU working and KingUser replaced.
Sent from my C6602 using xda Forums PRO
SurenderK said:
Hi Everyone,
Recently I have updated my XZ to lollipop 5.0.2 and after updating the Root is lost. I have been struggling to Root the latest firmware and finally I managed to get it rooted. I am posting the instructions so that it might help anyone.
I have a Locked Bootlaoder but it should also work with Unlocked Bootloader.
This has been tested on Xperia Z C6602, Lollipop 5.0.2 (FW: 10.6.A.0.454) and I will not be responsible if you try it on other device and if you do not follow the instructions carefully and accidently mess up with your phone.
Prerequisites
1. Upgrade to Lollipop 5.0.2.
2. Install drivers and configure ADB on your PC.
3. Enable USB debugging on your phone and Allow installation of apps from unknown sources under security settings.
Read the instructions carefully before proceeding.
Steps:-
1. Go to my google drive link and download the data.zip file. https://drive.google.com/file/d/0B1LQ910-5UYpNk5udEF4Qnd6T2M/view
2. Extract the contents into your working ADB directory (where adb.exe is located).
3. Connect your phone to PC via USB cable.
3. Copy KingRoot-4.1.0.249.apk file to your phone. Install the apk and run it. Make sure you are connected to internet as the KingRoot tool uses internet connection to download suitable exploit for your device on the go. After you run it, click Try Root option and let it complete till 100%. It will confirm that Rooting is successful. Now your phone is rooted.
If you do not like KingRoot and KingUser (for any reason) and want to switch to SuperSU then follow these steps:
1. Make sure you have extracted all the apps from data.zip into ADB directory. Browse to your ADB directory, press & hold Shift Key on Keyboard then right click on empty space to open context menu and select Open command window here. In command windows, type “adb devices” without quotes. You should be able to see your device listed. Then type the following commands carefully in same order (copy paste is better way to prevent any typo )
adb push su /data/local/tmp
adb push busybox /data/local/tmp
adb shell
2. You will be taken to a shell prompt with $ sign. In the shell type the following commands and keep your eye on your phone, when prompted, give the access permission:
su
mount -o remount,rw /system
cat /data/local/tmp/su >/system/xbin/daemonsu && chmod 0755 /system/xbin/daemonsu
cat /data/local/tmp/busybox >/system/xbin/busybox && chmod 0755 /system/xbin/busybox
daemonsu -d &
Leave the command Window running and do not disconnect your phone while you continue with the rest of steps.
3. Open the KingUser app in your phone, open settings (at the top right corner) and click Root authorization setting and then Remove Root permission. The app will be uninstalled automatically.
4. Uninstall the other two remaining KingRoot apps from your phone (KingRoot and the other one with Chinese language and the blue icon).
5. Go back to the Command window running adb, and type the following commands:
cat /data/local/tmp/su > /system/xbin/su && chmod 0755 /system/xbin/su
busybox chattr -ia /system/xbin/ku.sud
busybox chattr -ia /system/xbin/supolicy
busybox chattr -ia /system/xbin/pidof
rm /system/xbin/ku.sud
rm /system/xbin/supolicy
rm /system/xbin/pidof
rm /system/bin/debuggerd
rm /system/bin/debuggerd_real
rm /system/bin/debuggerd64
busybox chattr -ia /system/bin/install-recovery.sh
busybox chattr -ia /system/bin/rt.sh
rm /system/bin/install-recovery.sh
rm /system/bin/rt.sh
busybox chattr -ia /system/bin/.usr/.ku
rm -rf /system/bin/.usr
rm /system/usr/icu/icusuflag.conf
busybox chattr -ia /system/usr/iku/isu
rm -rf /system/usr/iku
rm /system/kroot_*
rm /sdcard/kr-stock-conf
rm -rf /sdcard/Kingroot
Again leave this command window running and do not disconnect your phone.
6. Copy Superuser.apk file (from extracted data.zip folder) into phone’s sdcard.
7. Go to your phone and Install Superuser.apk, Run it and let it update the SU binary.
8. Reboot your phone and enjoy the ROOT access on your latest Android 5.0.2 Lollipop.
Click to expand...
Click to collapse
Sadly my phone reboots as soon as I get to the point where I mount /system ("mount -o remount,rw /system" ). Probably caused by RIC, any suggestions on how to avoid this?
cruzersteve said:
Sadly my phone reboots as soon as I get to the point where I mount /system ("mount -o remount,rw /system" ). Probably caused by RIC, any suggestions on how to avoid this?
Click to expand...
Click to collapse
Hi,
Please check this xda thread. Might help you out.
http://forum.xda-developers.com/xpe...b-definitive-root-remount-reboot-fix-t2317432
Sent from my C6602 using xda Forums PRO
Anyone tryed on c6603?
hey surrenderk, i did the mistake of following this tutorial and literally copy pasted everything despite not having a sony, but an infinix hot note, just because i wanted to remove kinguser and kingroot and have superuser as the dedfault application for handling root access. any way to reverse everything we just did, coz i cant update via ota?? shell commands to undo everything perhaps that affected the "system" folder or that affected normal working of device??thanks!!
Jokichu said:
hey surrenderk, i did the mistake of following this tutorial and literally copy pasted everything despite not having a sony, but an infinix hot note, just because i wanted to remove kinguser and kingroot and have superuser as the dedfault application for handling root access. any way to reverse everything we just did, coz i cant update via ota?? shell commands to undo everything perhaps that affected the "system" folder or that affected normal working of device??thanks!!
Click to expand...
Click to collapse
Which device and software are you using??
Are you observing any strange behaviour in your device after making changes?
Sent from my C6602 using xda Forums PRO
Hey surrenderk yep, the problem is that somehow, I can't see any Ota update. It's says it's up to date, while I know there's an upgrade. In the steps we did, did we in any way change anything related to that??
I was already rooted, and had kinguser, and used kingroot. Whenever an Ota update came I could just unroot, perform the update then root again, easy.
However since I followed your tutorial steps with the adb shell, I received an Ota update, and did the unroot as usual, but the system found several files failing the root integrity tests, thus failing to update. My questions are
1.all these rm commands we used, did we remove/delete any core essential android file from the system folder? Bin folder? (debuggered /real/64) kroot_*, iku, kr-stock-conf, icusuflag.conf,
2.what do the rt.sh and install-recovery.sh scripts do?
My phone had become unstable, and could not play videos well nor audio files, it kept stuttering like it's buffering from an online Stream. Anyways, I am now unrooted and did a factory reset which fixed the video/audio glitch but still cannot "see" any new update although it's there. I just want want that update.
Sent from my Infinix-X551 using XDA Free mobile app
Question:
Why is the link not available in the OP?
Why is the link only shared thru PM?
Isn't this XDA - a sharing community?
This thread is just a little too weird.

Categories

Resources