Related
Please help, I've searched around and can't find the solution to my issue, I'm rooting following the XDA wiki for Gfree and using the Android SDK....I've managed to get the ADB to recognize my phone and I "think" that the ADB has been able to push the first 5 files to the SD....but I'm stuck on the last command line.
$ adb push su /sdcard/su
$ adb push Superuser.apk /sdcard/Superuser.apk
$ adb push rage /data/local/tmp/rage
$ adb push busybox /data/local/tmp/busybox
$ adb push root /data/local/tmp/root
$ adb shell chmod 0755 /data/local/tmp/*
when I run $ adb shell chmod 0755 /data/local/tmp/*
I get the following:
Usage: chmod <MODE> <File>
so then I go to terminal emulator on the phone and type
$ /data/local/tmp/rage
I get: /data/local/tmp/rage: not found
Where have I screwed up?
G2_Gordon_G1 said:
Please help, I've searched around and can't find the solution to my issue, I'm rooting following the XDA wiki for Gfree and using the Android SDK....I've managed to get the ADB to recognize my phone and I "think" that the ADB has been able to push the first 5 files to the SD....but I'm stuck on the last command line.
$ adb push su /sdcard/su
$ adb push Superuser.apk /sdcard/Superuser.apk
$ adb push rage /data/local/tmp/rage
$ adb push busybox /data/local/tmp/busybox
$ adb push root /data/local/tmp/root
$ adb shell chmod 0755 /data/local/tmp/*
when I run $ adb shell chmod 0755 /data/local/tmp/*
I get the following:
Usage: chmod <MODE> <File>
so then I go to terminal emulator on the phone and type
$ /data/local/tmp/rage
I get: /data/local/tmp/rage: not found
Where have I screwed up?
Click to expand...
Click to collapse
looks like you screwed up the last command ... didnt write the syntax properly thats why it showed its usage.....
(adb shell chmod 0755 /data/local/tmp/*) this command that is.....
also the last thing showing file not found means the files were never pushed to the phone..... connect your phone to your pc in chagre only and usb debigging connected mode and in command prompt in the adb folder write "adb devices"
it should show somehting like this.....
adb list of devices attached
SH034N34GF
this number over here (SH034N34GF) is an example ... it will show your phone ID... which would be different....
if you see list of devices attached and an empty line below and no serial number as shown in example....
than it means your android usb drivers for adb shell are not set up correctly
in that case ... get the drivers set up properly....
check with adb devices command to confirm your phone is recognized....
than start over with the commands
I've started over and have typed VERY CAREFULLY...
On each of the first five command prompts I get a 40 or so line message that starts with:
Android Debug Bridge version 1.0.26
.......
(list of commands)
.......
and ends with
bug tags are printed.
OK so I guess that's good
So then I type C:\> adb shell chmod 0755 /data/local/tmp/*
and NOW I get
adb server is out of date. killing...
*daemon started successfully*
Bad Mode
Clearly, I'm a noob.....
Now what?
read this guide .... on it search for .... "out of date" author explains how to tackle it
G2_Gordon_G1 said:
I've started over and have typed VERY CAREFULLY...
On each of the first five command prompts I get a 40 or so line message that starts with:
Android Debug Bridge version 1.0.26
.......
(list of commands)
.......
and ends with
bug tags are printed.
OK so I guess that's good
So then I type C:\> adb shell chmod 0755 /data/local/tmp/*
and NOW I get
adb server is out of date. killing...
*daemon started successfully*
Bad Mode
Clearly, I'm a noob.....
Now what?
Click to expand...
Click to collapse
hispeedworm said:
read this guide .... on it search for .... "out of date" author explains how to tackle it
Click to expand...
Click to collapse
In the ADB guide it says:
"By the way, the first adb command that you type may well also come up with some lines similar to "adb deamon out of date" etc, but don't worry, that's normal, just check the rest of the output."
So apparently that's not a problem?
G2_Gordon_G1 said:
In the ADB guide it says:
"By the way, the first adb command that you type may well also come up with some lines similar to "adb deamon out of date" etc, but don't worry, that's normal, just check the rest of the output."
So apparently that's not a problem?
Click to expand...
Click to collapse
im uploading my adb... its minimal with just adb fastboot and few other files.... unzip into a folder on your pc.....use these instead of the android sdk and all..
make sure that folder is linked in windows..... Step 4 of the adb for noobs guide..... reinstall the android usb drivers again following the guide.....
when thats done restart and press F8 ... disable signature verification ... when windows loaded... go to command prompt.... do into the adb directory.....than write adb devices....if it shows you device than start over with the commands.... you should not get the error saying out of date... as i just used this adb shell 2 days back to root my desire Z.....
hope this helps
Thanks! Will try again soon!
http://forum.xda-developers.com/showthread.php?t=1178912
5. Run the following commands from your platform-tools directory.
Code:
> adb push fre3vo /data/local/tmp
> adb shell
$ chmod 777 /data/local/tmp/fre3vo
$ /data/local/tmp/fre3vo -debug -start FAA90000 -end FFFFFFFF
I am able to do "adb push fre3vo", "adb shell", and "chmod 777" without a directory. I tried adding my directory "C:\android-sdk_r16-windows\platform-tools" but it doesn't work, what do I do for "C:\android-sdk_r16-windows\platform-tools/fre3vo -debug -start FAA90000 -end FFFFFFFF"?
Edit: I just probably forgot how to add my directory correctly, could someone show me how? And how to use commands with it?
You would type in the command window "cd c:/(your directory)". Then whatever you type after that will take pplace in the directory you entered.
Sent from my HTC Desire Z using xda premium
Thanks, but it only works for the first command, but doesn't work for the last 2, I even deleted the fre3vo file from the platform-tools folder and put in the folder fre3vo in it instead, and they still do not work.
How do I add fre3vo to my directory correctly? Should the file or folder of fre3vo be in the platform-tools folder?
The fre3vo command is run on the phone via shell.
When you enter adb shell, it opens a prompt with $, this is the terminal for the phone itself. All you need to do it type in those commands.
Think of "adb shell" as "Start > Run > 'cmd' > enter" on Windows.
---------- Post added at 10:56 AM ---------- Previous post was at 10:51 AM ----------
UKTone said:
http://forum.xda-developers.com/showthread.php?t=1178912
5. Run the following commands from your platform-tools directory.
Code:
> adb push fre3vo /data/local/tmp
> adb shell
$ chmod 777 /data/local/tmp/fre3vo
$ /data/local/tmp/fre3vo -debug -start FAA90000 -end FFFFFFFF
I am able to do "adb push fre3vo", "adb shell", and "chmod 777" without a directory. I tried adding my directory "C:\android-sdk_r16-windows\platform-tools" but it doesn't work, what do I do for "C:\android-sdk_r16-windows\platform-tools/fre3vo -debug -start FAA90000 -end FFFFFFFF"?
Edit: I just probably forgot how to add my directory correctly, could someone show me how? And how to use commands with it?
Click to expand...
Click to collapse
I'm going to double post and give a run-down of what you are doing here as it sounds like you're confused.
"adb push fre3vo /data/local/tmp/fre3vo" - You're moving the fre3vo files from c:\blahblahblah\platform-tools to /data/local/tmp/fre3vo on the phone
"adb shell" - You are opening the phone's command line interface through adb (similar to what I said in my previous post).
"chmod 777 /data/local/tmp/fre3vo" - You are setting the read write permissions through the phones terminal for the file on the phone itself
"/data/local/tmp/fre3vo (insert extra commands)" - You are executing the fre3vo file with particular switches attached to the command.
after "chmod 777" I get:
"Usage: chmod <MODE> <FILE>
After "-debug -start FAA90000 -end FFFFFFFF" I get "-debug: permission denied" at the end.
Edit: rebooting phone and cmd, and about to try the other 5 -debug commands
Edit: This last time I just put in the commands without the directories, which seems to be the only way to get chmod 777 to work... You are correct I am confused, I would like to know what exactly to put into my cmd. Also forgot to put the file fre3vo back into platform-tools...
You have to specify the file you are changing permissions on. In this case it would be:
Code:
chmod 777 /data/local/temp/fre3vo
Essentially you are tell the phone: "Hey, that fre3vo file at /data/local/tmp location needs to have read/write access set to 777"
biohazrd51 said:
You have to specify the file you are changing permissions on. In this case it would be:
Code:
chmod 777
Essentially you are tell the phone: "Hey, that fre3vo file at /data/local/tmp location needs to have read/write access set to 777"
Click to expand...
Click to collapse
How?
Also "chmod 777' only works without a directory for me "adb push fre3vo" works without, and with both "cd /data/local/tmp" and "cd C:\android-sdk_r16-windows\platform-tools"
I'm sorry if it seems I a being difficult, I really can't figure this out.
Edit: also it's the "-debug -start FAA90000 -end FFFFFFFF" command that gives me a permission denied, not "chmod 777""
Edit: Reread your other post, I tried "chmod 777 cd /data/local/temp/fre3vo" but it tells me there is no such file or directory.
Ok, i think i understand the problem.
You think that the $ prompt is still the windows prompt, it isn't.
When you are at the command line in windows at the location "c:\blahblahblah\platform-tools" and type in the command "adb shell" you leave the windows command line and enter the Linux/Android command line for the phone. At that point you are entering linux commands, not windows, and they are executing on the phone (you're just viewing it on the PC). Linux commands don't need you to specify folder location like platform-tools.
So when I say
Code:
chmod 777 /data/local/tmp/fre3vo
It means "hey linux/android on the phone, take the Fre3vo file (/fre3vo) at location /data/local/tmp (on the phone) and give it permissions (chmod is the command giving permissions) equal to 777 (read/write/execute)"
chmod = the command to change permissions
777 = the permissions of read/write/execute
/data/local/tmp = the location of the file on the phone (it was moved there by adb push /data/local/tmp/fre3vo)
/fre3vo = the particular file you want to change the permission.
Make sense?
Ok I saw your post about file not found. Exit out of the windows command line and move the fre3vo file back to c:\blahblahblah\platform-tools like you had earlier. Start back over with the adb push command.
Code:
adb push c:\blahblahblah\platform-tools\fre3vo /data/local/tmp/fre3vo
adb = android debugger
push = move the file (from) location (to) location
c:\blahblahblah\platform-tools\fre3vo = location and actual file on the PC
/data/local/tmp/fre3vo = location on the phone you want the file moved to
When it moves successfully you should see something to the effect:
Code:
Fre3vo (275Kb/s)
Yes and no. So after the adb shell I am still supposed to be entering the commands on the cmd correct? Without any directories then? So just "$ chmod 777" but what about the "-debug -start FAA90000 -end FFFFFFFF" there are 5 others I haven't tried yet?
Also trying to add the directory "/data/local/tmp" or "cd /data/local/tmp" makes it fail everytime.
Also I am on the homescreen/standby, should I be somewhere else on the phone, like bootloader or something?
UKTone said:
Yes and no. So after the adb shell I am still supposed to be entering the commands on the cmd correct? Without any directories then? So just "$ chmod 777" but what about the "-debug -start FAA90000 -end FFFFFFFF" there are 5 others I haven't tried yet?
Also trying to add the directory "/data/local/tmp" or "cd /data/local/tmp" makes it fail everytime.
Also I am on the homescreen/standby, should I be somewhere else on the phone, like bootloader or something?
Click to expand...
Click to collapse
I don't think it matters where you are at on the phone.
Yes you would just enter commands like "chmod 777 /data/local/tmp/fre3vo" ($ is something that does not need to be entered).
I'm going to be away from the computer for about an hour. You may want to hop on IRC (do a search for it in these forums) and see if anyone there can walk you through it, otherwise ill be back later.
Sent from my HTC Vision using xda premium
Alright cool, thanks man, sorry if I gave you a headache lol.
And yeah I know, I was just adding that so you know I wasn't doing it before adb shell
No problem. The system ill be at has the sdk installed so I can take screenshots and load them.
Sent from my HTC Vision using xda premium
http://i242.photobucket.com/albums/ff137/UKTone/g21.png
http://i242.photobucket.com/albums/ff137/UKTone/g22.png
These show some of what I've been trying.
You don't need the "cd" before /data/local/tmp/fre3vo
Sent from my HTC Vision using xda premium
http://i242.photobucket.com/albums/ff137/UKTone/g23.png
http://i242.photobucket.com/albums/ff137/UKTone/g24.png
1. I tried without the cd, it doesn't seem to work without it...
2. fre3vo, should the file or the entire folder be in the platform-tools folder?
3. When you told me to do the irc thing, I downloaded mIRC, but while installing it said I didn't have permission to install, so I had to close and right click and run as administrator. This could be a possible problem? And any idea how to fix it?
Edit: By #3 I am thinking maybe this same permission problem is causing "-debug -start FAA90000 -end FFFFFFFF" to give me a permission denied response.
Honestly its been so long since I've done this I don't remember if it is file or folder. Let me review it all and let you know.
Additionally, here are some screenshots of the commands (ignore the prompts beforehand as my setup is probably a bit different than yours, only the commands matter).
By the way, what guide are you using?
Yeah I figured, it's been out for a while.
http://forum.xda-developers.com/showthread.php?t=1178912 I was linked to this guide from this guide http://forum.xda-developers.com/wik...sion#Rooting_the_Vision_.28G2.2FDZ.29_and_DHD
Btw I can't see the screen shots.
To elaborate, place the fre3vo file inside of the fre3vo.zip file and the misc_version file inside the misc_version_01.zipfile in your platform-tools directory
Click to expand...
Click to collapse
My guess would be the files, not folders. You need to execute fre3vo, so it would be a file.
I've never done a downgrade, so someone else might be able to chime in with some experience.
I think you should restar. Push the files to the phone again. Then start adb shell. Then run chmod 777. And try running fre3vo again.
Sent from my HTC Desire Z using xda premium
@ l337m45732 Still gives me a permission denied and I looked here:
http://forum.xda-developers.com/showthread.php?t=1411597
Am I supposed to put superuser on my phone first? If so do I just download it from the play store/market or use linda/astro with an .apk?
I get a permission denied when trying su.
Edit: I think once I get past this permission issue, I will breeze through the rest of the stuff. Also I tried doing everything after unlocking and setting my screen timeout to 30 minutes, still got permission denies.
Edit: I opened SDK Manager and updated everything and now I get it saying ADB servers didn't ACK.
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Windows\system32>adb shell cat /dev/msm_rotator
adb server is out of date. killing...
* daemon started successfully *
/dev/msm_rotator: invalid length
C:\Windows\system32>adb push fre3vo /data/local/tmp
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
C:\Windows\system32>adb push fre3vo /data/local/tmp
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
C:\Windows\system32>
I consider this progress since something other than no such file or directory didn't come up when I tried the directory without cd. I got an ACK from "adb shell cat /dev/msm_rotator" and the solution was to have my phone unlocked at least once/have it fully loaded up. Idk what the solution/problem is with "adb push fre3vo /data/local/tmp" is yet.
Edit: Now it's back to saying cannot stat 'fre3vo': No such file or directory
Edit: so much for progress :
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Windows\system32>adb shell cat /dev/msm_rotator
/dev/msm_rotator: invalid length
C:\Windows\system32>adb push fre3vo /data/local/tmp
cannot stat 'fre3vo': No such file or directory
C:\Windows\system32>adb push fre3vo
Android Debug Bridge version 1.0.29
-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. Overrides ANDROID_SERI
AL
environment variable.
-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
connect <host>[:<port>] - connect to a device via TCP/IP
Port 5555 is used by default if no port number
is specified.
disconnect [<host>[:<port>]] - disconnect from a TCP/IP device.
Port 5555 is used by default if no port number
is specified.
Using this command with no additional arguments
will disconnect from all connected TCP/IP devic
es.
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
(-l means list but don't copy)
(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 forward <local> <remote> - forward socket connections
forward specs are one of:
tcp:<port>
localabstract:<unix domain socket name>
localreserved:<unix domain socket name>
localfilesystem:<unix domain socket name>
dev:<character device name>
jdwp:<process pid> (remote only)
adb jdwp - list PIDs of processes hosting a JDWP transport
adb install [-l] [-r] [-s] <file> - push this package file to the device and i
nstall it
('-l' means forward-lock the app)
('-r' means reinstall the app, keeping its data
)
('-s' means install on SD card instead of inter
nal storage)
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 backup [-f <file>] [-apk|-noapk] [-shared|-noshared] [-all] [-system|-nosy
stem] [<packages...>]
- write an archive of the device's data to <file>
.
If no -f option is supplied then the data is wr
itten
to "backup.ab" in the current directory.
(-apk|-noapk enable/disable backup of the .apks
themselves
in the archive; the default is noapk.)
(-shared|-noshared enable/disable backup of the
device's
shared storage / SD card contents; the defau
lt is noshared.)
(-all means to back up all installed applicatio
ns)
(-system|-nosystem toggles whether -all automat
ically includes
system applications; the default is to inclu
de system apps)
(<packages...> is the list of applications to b
e backed up. If
the -all or -shared flags are passed, then t
he package
list is optional. Applications explicitly g
iven on the
command line will be included even if -nosys
tem would
ordinarily cause them to be omitted.)
adb restore <file> - restore device contents from the <file> backup
archive
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 reboot [bootloader|recovery] - reboots the device, optionally into the boo
tloader or recovery program
adb reboot-bootloader - reboots the device into the bootloader
adb root - restarts the adbd daemon with root permissions
adb usb - restarts the adbd daemon listening on USB
adb tcpip <port> - restarts the adbd daemon listening on TCP on th
e specified port
networking:
adb ppp <tty> [parameters] - Run PPP over USB.
Note: you should not automatically start a PPP 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.
environmental variables:
ADB_TRACE - Print debug information. A comma separated list
of the following values
1 or all, adb, sockets, packets, rwx, usb, sync
, sysdeps, transport, jdwp
ANDROID_SERIAL - The serial number to connect to. -s takes prior
ity over this if given.
ANDROID_LOG_TAGS - When used with the logcat option, only these de
bug tags are printed.
C:\Windows\system32>adb shell
$ chmod 777 /data/local/tmp/fre3vo
chmod 777 /data/local/tmp/fre3vo
Unable to chmod /data/local/tmp/fre3vo: No such file or directory
$ chmod 777
chmod 777
Usage: chmod <MODE> <FILE>
$ /data/local/tmp/fre3vo -debug -start FAA90000 -end FFFFFFFF
/data/local/tmp/fre3vo -debug -start FAA90000 -end FFFFFFFF
/data/local/tmp/fre3vo: not found
$ -debug -start FAA90000 -end FFFFFFFF
-debug -start FAA90000 -end FFFFFFFF
-debug: permission denied
$
Edit: only difference I see is the daemon started successfully and failed, the other had neither, restarting phone and unplugging and going to try again.
Edit: I'm so tired of trying this, is there another way? Mainly just trying to do this http://forum.xda-developers.com/wik...sion#Rooting_the_Vision_.28G2.2FDZ.29_and_DHD for the T-Mobile G2 and I was linked from that to this guide http://forum.xda-developers.com/showthread.php?t=1178912 please help.
Edit: http://theunlockr.com/2011/07/22/how-to-downgrade-a-gingerbread-t-mobile-g2-so-it-can-be-rooted/ :
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Windows\system32>cd C:\android-sdk_r16-windows\tools\
C:\android-sdk_r16-windows\tools>adb push fre3vo /data/local/tmp
683 KB/s (9796 bytes in 0.014s)
C:\android-sdk_r16-windows\tools>adb push misc_version /data/local/tmp/
1645 KB/s (589849 bytes in 0.350s)
C:\android-sdk_r16-windows\tools>chmod 777 /data/local/tmp/fre3vo
'chmod' is not recognized as an internal or external command,
operable program or batch file.
C:\android-sdk_r16-windows\tools>chmod 777 /data/local/tmp/misc_version
'chmod' is not recognized as an internal or external command,
operable program or batch file.
C:\android-sdk_r16-windows\tools>/data/local/tmp/fre3vo -debug
The system cannot find the path specified.
C:\android-sdk_r16-windows\tools>
Edit: It finally freaking worked:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Windows\system32>adb shell cat /dev/msm_rotator
/dev/msm_rotator: invalid length
C:\Windows\system32>adb push fre3vo /data/local/tmp
cannot stat 'fre3vo': No such file or directory
C:\Windows\system32>adb push fre3vo cd /data/local/tmp
Android Debug Bridge version 1.0.29
-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. Overrides ANDROID_SERI
AL
environment variable.
-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
connect <host>[:<port>] - connect to a device via TCP/IP
Port 5555 is used by default if no port number
is specified.
disconnect [<host>[:<port>]] - disconnect from a TCP/IP device.
Port 5555 is used by default if no port number
is specified.
Using this command with no additional arguments
will disconnect from all connected TCP/IP devic
es.
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
(-l means list but don't copy)
(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 forward <local> <remote> - forward socket connections
forward specs are one of:
tcp:<port>
localabstract:<unix domain socket name>
localreserved:<unix domain socket name>
localfilesystem:<unix domain socket name>
dev:<character device name>
jdwp:<process pid> (remote only)
adb jdwp - list PIDs of processes hosting a JDWP transport
adb install [-l] [-r] [-s] <file> - push this package file to the device and i
nstall it
('-l' means forward-lock the app)
('-r' means reinstall the app, keeping its data
)
('-s' means install on SD card instead of inter
nal storage)
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 backup [-f <file>] [-apk|-noapk] [-shared|-noshared] [-all] [-system|-nosy
stem] [<packages...>]
- write an archive of the device's data to <file>
.
If no -f option is supplied then the data is wr
itten
to "backup.ab" in the current directory.
(-apk|-noapk enable/disable backup of the .apks
themselves
in the archive; the default is noapk.)
(-shared|-noshared enable/disable backup of the
device's
shared storage / SD card contents; the defau
lt is noshared.)
(-all means to back up all installed applicatio
ns)
(-system|-nosystem toggles whether -all automat
ically includes
system applications; the default is to inclu
de system apps)
(<packages...> is the list of applications to b
e backed up. If
the -all or -shared flags are passed, then t
he package
list is optional. Applications explicitly g
iven on the
command line will be included even if -nosys
tem would
ordinarily cause them to be omitted.)
adb restore <file> - restore device contents from the <file> backup
archive
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 reboot [bootloader|recovery] - reboots the device, optionally into the boo
tloader or recovery program
adb reboot-bootloader - reboots the device into the bootloader
adb root - restarts the adbd daemon with root permissions
adb usb - restarts the adbd daemon listening on USB
adb tcpip <port> - restarts the adbd daemon listening on TCP on th
e specified port
networking:
adb ppp <tty> [parameters] - Run PPP over USB.
Note: you should not automatically start a PPP 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.
environmental variables:
ADB_TRACE - Print debug information. A comma separated list
of the following values
1 or all, adb, sockets, packets, rwx, usb, sync
, sysdeps, transport, jdwp
ANDROID_SERIAL - The serial number to connect to. -s takes prior
ity over this if given.
ANDROID_LOG_TAGS - When used with the logcat option, only these de
bug tags are printed.
C:\Windows\system32>adb shell
$ chmod 777 /data/local/tmp/fre3vo
chmod 777 /data/local/tmp/fre3vo
$ /data/local/tmp/fre3vo -debug -start FAA90000 -end FFFFFFFF
/data/local/tmp/fre3vo -debug -start FAA90000 -end FFFFFFFF
fre3vo by #teamwin
Please wait...
Attempting to modify ro.secure property...
fb_fix_screeninfo:
id: msmfb
smem_start: 802160640
smem_len: 3145728
type: 0
type_aux: 0
visual: 2
xpanstep: 0
ypanstep: 1
line_length: 1920
mmio_start: 0
accel: 0
fb_var_screeninfo:
xres: 480
yres: 800
xres_virtual: 480
yres_virtual: 1600
xoffset: 0
yoffset: 800
bits_per_pixel: 32
activate: 16
height: 80
width: 48
rotate: 0
grayscale: 0
nonstd: 0
accel_flags: 0
pixclock: 0
left_margin: 0
right_margin: 0
upper_margin: 0
lower_margin: 0
hsync_len: 0
vsync_len: 0
sync: 0
vmode: 0
Buffer offset: 00000000
Buffer size: 8192
Scanning region faa90000...
Scanning region fab80000...
Scanning region fac70000...
Scanning region fad60000...
Scanning region fae50000...
Scanning region faf40000...
Scanning region fb030000...
Scanning region fb120000...
Scanning region fb210000...
Scanning region fb300000...
Scanning region fb3f0000...
Scanning region fb4e0000...
Scanning region fb5d0000...
Scanning region fb6c0000...
Scanning region fb7b0000...
Scanning region fb8a0000...
Scanning region fb990000...
Scanning region fba80000...
Potential exploit area found at address fbb66a00:1600.
Exploiting device...
C:\Windows\system32>
Thanks guys for your help. the first half from the unlockr website did the trick.
Firstly, Merry Christmas!
Note: This worked on version 10.2.4
I received a Kindle Fire 2 today and since then I've been trying to get it rooted, now that I have I though I'd share it here for other people who might be in the same situation.
This is really just a remixing of the tool made by Bin4ry (http://forum.xda-developers.com/show....php?t=1886460) but I couldn't get the script to run on my Mac...
Step 0 - Preparing
You must enable ADB and Unknown App sources from Settings.
Settings > More > Security > Enable ADB
Settings > More > Device > Allow Installation of Applications
Step 1 is to get that tool from here. and extract it somewhere you'll remember.
Step 2 (you can skip this if you already have the android SDK platform-tools in your PATH)
If you don't have the android SDK or adb installed just add the 'stuff' folder from the tool to your path.
In terminal run
Code:
export PATH=$PATH:/path/to/extracted/tool/stuff/
Step 3 - Push the required files
It's probably easiest if you change into the stuff folder first...
Code:
cd /Users/x/Downloads/Root_with_Restore_by_Bin4ry_v18.7z\ Folder/stuff
Then run the following...
Code:
adb push busybox /data/local/tmp/.
adb push su /data/local/tmp/.
adb push Superuser.apk /data/local/tmp/.
adb push ric /data/local/tmp/ric
Then you need to run an adb shell to set some permissions
Code:
adb shell
(you should get a prompt like [email protected]:/)
Run
Code:
chmod 755 /data/local/tmp/busybox
exit
Step 4 - Rooting
This requires another terminal window. Check that you can run adb from there as well (running adb should print the usage information)
In the first window run:
Code:
adb shell "while ! ln -s /data/local.prop /data/data/com.android.settings/a/file99; do :; done" > /dev/null
In the other run
Code:
adb restore fakebackup.ab
You should get a prompt on your Kindle, hit the restore my data button. As you do so the command in the first window should stop (or a few seconds later - if it doesn't stop it and re-run both commands again.)
You can now close the second window!
Run
Code:
adb reboot
, your Kindle should reboot though the screen will be blinking repeatedly (flashing between the lockscreen and the boot animation) don't worry about that as it will be fixed in a sec.
Step 5 - Cleaning Up
Run
Code:
adb shell
If all was successful you should see the prompt change to [email protected]:/
If it did, continue otherwise go back to step 4.
Run these
Code:
/data/local/tmp/busybox mount -o remount,rw /system
/data/local/tmp/busybox mv /data/local/tmp/su /system/xbin/su
/data/local/tmp/busybox mv /data/local/tmp/ric /system/bin/ric
chmod 755 /system/bin/ric
/data/local/tmp/busybox mv /data/local/tmp/su /system/xbin/su
/data/local/tmp/busybox mv /data/local/tmp/Superuser.apk /system/app/Superuser.apk
/data/local/tmp/busybox cp /data/local/tmp/busybox /system/xbin/busybox
chown 0.0 /system/xbin/su && chmod 06755 /system/xbin/su
chmod 655 /system/app/Superuser.apk
chmod 755 /system/xbin/busybox
rm /data/local.prop
reboot
Your Kindle will restart and SuperSU will be available under Apps, your now free to do as you please, though you could follow with Step 3 on this thread to get Google Apps etc working.
Update: a short guide to installing the Play store can be found here.
This worked almost perfect for me but I couldn't get it to run adb commands from the stuff folder so I dumped its contents (minus the adb stuff) into the platform-tools in the android SDK and from then on everything went great. Thanks so much.
didthis work for 10.2.4 users out there
does this work for 10.2.4
worked!
Great work, congratulations and thanks! I'd like to make some comments tho regarding some typos and suggestions.
1.- I'd suggest to install the android SDK as, in fact, adb commands didn't work from the stuff folder. Add a line to .bash_profile with the export PATH command to make permanent access to the adb shell.
2.- Push files from the Root_with_Restore_by_Bin4ry_v18 folder, not the .7z file.
3.- The command is, e.g., adb push busybox /data/local/tmp/ instead of adb push busybox /data/local/tmp/.
4.- In Step 5 the command /data/local/tmp/busybox mv /data/local/tmp/su /system/xbin/su is twice so you'll get an error the second time you execute it.
Also congratulations for instructions on how to install PlayStore - here pay attention to the names playstore.apk and servicesframework.apk which in fact are plstore3.10.10.apk and GoogleServicesFramework.apk respectively -
Once again thanks for your work.
gorganzolia said:
does this work for 10.2.4
Click to expand...
Click to collapse
Yes this worked for 10.2.4
10.2.6
Does this work with 10.2.6?
it worked
Tried it this morning on 10.2.6 and it worked woohoo now how do you stop it from automatically updating
Found out how to stop those automatic updates here http://forum.xda-developers.com/showthread.php?t=2086450
Hi,
I am trying to debug native code on HTC, but I have problem because there is no gdbserver on phone. It should be inside /system/bin/ but phone wasn't rooted. When I rooted phone added -rw permission to /system directory, I tried to adb push gdbserver, but phone ignores every command.
Here is list of everything I did:
First I rooted phone with a help from tutorial "How to Root the HTC Wildfire S (GSM)" on Youtube
Then I installed Terminal and BusyBox for tools
I plugged in phone to PC and in terminal I typed:
Code:
$ adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
SH156TR08018 device
Code:
$ adb shell
adb server is out of date. killing...
* daemon started successfully *
$ su
su
#
Code:
# mount | grep system
mount | grep system
/dev/block/mtdblock3 /system yaffs2 ro,relatime 0 0
System is read-only
Code:
# mount -o remount,rw /dev/block/mtdblock3 /system
mount | grep system
mount | grep system
/dev/block/mtdblock3 /system yaffs2 rw,relatime 0 0
# exit
exit
$ exit
exit
Now, system is read-write
Code:
$ adb push gdbserver /system
adb server is out of date. killing...
* daemon started successfully *
failed to copy 'gdbserver' to '/system/gdbserver': Permission denied
When I copy gdbserver to /sdcard and try to move it, I get:
Code:
# mv /sdcard/gdbserver /system
mv /sdcard/gdbserver /system
failed on '/sdcard/gdbserver' - Cross-device link
So, does anybody knows what is the problem?
Hi all,
If you've bought a Lenovo S850 from their new european retail shops or from other distributors, you probably are in the same situation as I was a few days ago.
Doesn't matter the reasons, you probably got annoyed (as I am) of those HUNDREDS of Lenovo and Google useless apps. Maybe you have tried to root it from a custom recovery, such as TWRP (which is the only one I have found anywhere for this phone) but you failed when you probably saw that it's touchscreen doesn't respond. I know I have tried all of those and a few more but no succes.
Well, last saturday, as my final attempt, I searched once more the web to find something that could help me root it. I have found on Lenovo forums (russian forum) that there's a modified boot.img for this very phone. I have downloaded it, flashed it thru FlashTool, booted the phone and attached it to my PC with USB Debugging switched ON. After typing "adb shell" in the command prompt, I had the surprise to see "[email protected]:/ #" as a result instead of that annoying "$". Well, it's time for attack!
THE METHOD DESCRIBED BELOW PROOVED TO BE SUCCESSFULL ON A LENOVO S850 Smartphone running Android 4.4.2, ROW Firmware S850_ROW_S211_140923 (lastest)
*What You Need*
1. Your Unrooted Android Device.
2 .Windows operated PC.
3. ADB Drivers installed on your PC. You can find them in Flashtool.rar or ADB.rar. Just plug in your switched-off phone and point installation wizzard to the folder.
4. The above mentioned archives: Flashtool.rar and ADB.rar. You have to download them both and extract them to your harddrive, they contain all the tools and resources needed.
*Steps*
1. Open Flash_tool.exe located in FlashTool folder you just extracted. In Flash tool, make sure that "DA DL All With Check Sum" is checked, "USB Mode" and "DA Download All/Speed/Force To High Speed" from Options tab are cheched (screenshoot bellow).
2. In Flash Tool click on "Scatter-loading", navigate to FlashTool folder, then target_bin and choose "MT6582_Android_scatter". It should load just " BOOTIMG". Well, now hit Download (with phone switched off and disconnected), wait for the progress bar to show 0% and connect the phone (still swiched off). It should start flashing boot.img on the phone and, after all is done, a green circle "OK" window should announce a successfull flash. Disconnect phone, switch it on, wait for it to load and reconnect it to PC (AFTER you checked USB debugging in USB computer connection that appeared).
3. Rooting time! Open ADB folder and double-click CMD. You have to put/extract ADB folder to C: drive, otherwise adb commands won't work (and you'll have to manually change directory in command prompt and point it to ADB folder). Now you have to insert the following commands in the window you just opened. Here we go:
Code:
adb devices (with this command you can see if the device is properly installed. if it is ok, it should be listed like "A6EAYPRSA6UGGIT4 device". if anywhing else, reinstall ADB Drivers)
adb shell
mount -o remount,rw /system
mkdir /system/bin/.ext
exit
adb push su /system/xbin/daemonsu
adb push su /system/xbin/su
adb push su /system/bin/.ext/.su
adb push Superuser.apk /system/app/Superuser.apk
adb push install-recovery.sh /system/etc/install-recovery.sh
adb push 99SuperSUDaemon /system/etc/init.d/99SuperSUDaemon
adb shell
chmod 0777 /system/bin/.ext
chmod 06755 /system/bin/.ext/.su
chmod 06755 /system/xbin/su
chmod 0755 /system/xbin/daemonsu
chmod 0755 /system/etc/install-recovery.sh
chmod 0755 /system/etc/init.d/99SuperSUDaemon
chmod 0644 /system/app/Superuser.apk
reboot
A successful session should look like this:
Code:
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\ADB>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
A6EAYPRSA6UGGIT4 device
C:\ADB>adb shell
[email protected]:/ # mount -o remount,rw /system
mount -o remount,rw /system
[email protected]:/ # mkdir /system/bin/.ext
mkdir /system/bin/.ext
[email protected]:/ # exit
exit
C:\ADB>adb push su /system/xbin/daemonsu
3919 KB/s (125424 bytes in 0.031s)
C:\ADB>adb push su /system/xbin/su
3919 KB/s (125424 bytes in 0.031s)
C:\ADB>adb push su /system/bin/.ext/.su
3919 KB/s (125424 bytes in 0.031s)
C:\ADB>adb push Superuser.apk /system/app/Superuser.apk
3961 KB/s (4120012 bytes in 1.015s)
C:\ADB>adb push install-recovery.sh /system/etc/install-recovery.sh
0 KB/s (629 bytes in 1.000s)
C:\ADB>adb push 99SuperSUDaemon /system/etc/init.d/99SuperSUDaemon
0 KB/s (55 bytes in 1.000s)
C:\ADB>adb shell
[email protected]:/ # chmod 0777 /system/bin/.ext
chmod 0777 /system/bin/.ext
[email protected]:/ # chmod 06755 /system/bin/.ext/.su
chmod 06755 /system/bin/.ext/.su
[email protected]:/ # chmod 06755 /system/xbin/su
chmod 06755 /system/xbin/su
[email protected]:/ # chmod 0755 /system/xbin/daemonsu
chmod 0755 /system/xbin/daemonsu
Unable to chmod /system/xbin/daemonsu: Read-only file system
[email protected]:/ # mount -o remount,rw /system
mount -o remount,rw /system
[email protected]:/ # chmod 0755 /system/xbin/daemonsu
chmod 0755 /system/xbin/daemonsu
[email protected]:/ # chmod 0755 /system/etc/install-recovery.sh
chmod 0755 /system/etc/install-recovery.sh
[email protected]:/ # chmod 0755 /system/etc/init.d/99SuperSUDaemon
chmod 0755 /system/etc/init.d/99SuperSUDaemon
[email protected]:/ # chmod 0644 /system/app/Superuser.apk
chmod 0644 /system/app/Superuser.apk
[email protected]:/ # reboot
reboot
C:\ADB>
If anything went right, your phone should be rooted. Mine was (and I'm not a programmer). Here's some screenshoots I made:
Before...
... and After
There's a few screenshoots with SuperSU in action after successful rooting:
I'm not the author of this method, I've just collected and tested different things on my OWN phone until I was able to root it. Use it on your own risk!
The other day, i saw a deal on this tablet at bestbuy (USA) store, which was $159, i thought myself for the specs this tablet has this is indeed good deal, but before I pull trigger, i am checking and see if there's a easy way to root the device, because this tablet is not wildly popular, it is quite hard to find any kind of support here in XDA.
But seems like you were able to root the device, it seems like using moded boot.img, it must be in-secure kernel....Obviously, the biggest question now is if that boot.img also works for tablet sold in USA version, and maybe both European and USA version are identical (probably so)...
jazzespresso said:
The other day, i saw a deal on this tablet at bestbuy (USA) store, which was $159, i thought myself for the specs this tablet has this is indeed good deal, but before I pull trigger, i am checking and see if there's a easy way to root the device, because this tablet is not wildly popular, it is quite hard to find any kind of support here in XDA.
But seems like you were able to root the device, it seems like using moded boot.img, it must be in-secure kernel....Obviously, the biggest question now is if that boot.img also works for tablet sold in USA version, and maybe both European and USA version are identical (probably so)...
Click to expand...
Click to collapse
Have you tried this on the US model (S8-50F) ?
EDIT: Found other method to rooting the S8-50F and other models!
Thread here: http://forum.xda-developers.com/and...o-root-lenovo-tab-s8-50-t2954375#post57190447
Syntax Error
Im getting a syntax error on line 99 for the scatter.txt file, then flash tool closes.
2. In Flash Tool click on "Scatter-loading", navigate to FlashTool folder, then target_bin and choose "MT6582_Android_scatter". It should load just " BOOTIMG". Well, now hit Download (with phone switched off and disconnected), wait for the progress bar to show 0% and connect the phone (still swiched off). It should start flashing boot.img on the phone and, after all is done, a green circle "OK" window should announce a successfull flash. Disconnect phone, switch it on, wait for it to load and reconnect it to PC (AFTER you checked USB debugging in USB computer connection that appeared).
Click to expand...
Click to collapse
Any ideas?
can not root
pls, i have win.8.1 and i can not install flash tool (not exceed 0%) and adb please hlep
and what does " point installation wizzard to the folder." it mean
The OP appears to be referring to the S850 phone. For anyone with the S8-50 tablet I think you'll want this thread http://forum.xda-developers.com/general/general/lenovo-tab-s8-50f-stock-firmware-rom-t2989791
Help me please !!!
I've got lenovo s850 . but it got a new rom from firmware update s850_ROW_s215_150420 what should i do ? Im stuck in 2nd step. Help me
Do nothing
Just tried this and there is one problem, when this command fails chmod 0755 /system/xbin/daemonsu, you have to mount and remount as you did in the output, but you didn't write it to the shell comands....Took me some time to figure it out
Sorry guys,
I would like to know if there is a way to get hold of the factory stock rom for the Lenovo Tab S8 50L and how to install it. I need to reset it to sell it very soon.
The device I have is rooted but I really have to unroot otherwise no business.
Thanks for your help in advance!!
Hi. I'm trying to restore my S850 device, right now whenever I push the power button it powers up for a couple of seconds, I get an Android logo on screen and then it just turns off. I connect it to my PC, but it just appears in the device manager list for 4-5 seconds and then it disappears, after a "failed to install driver message". I'm trying to update the driver manually but the option is greyed out.
I'm looked online again and again, it says in many videos that the device has to be in "META mode", I've tried all the possible combinations but I get nothing.
Can anyone help me?
Can anyone give me boot.img file for stock later ROW firmwire ?
Dear devs, help me out on UNBRICKING LENOVO S850:
Initial Problem was: AFTER TURNING PHONE ON (NORMAL BOOT UP) IT GOT STUCK ON BOOT LOGO.
Very first tried solution: PRESSING BOTH VOL.+POWER PHONE WENT IN LENOVO RECOVERY MODE. THEN I TRIED TO FUSE FORMAT BUT IT FAILED TO FORMAT. PROBLEM REMAINED SAME.
Second Tried Solution: DOWNLOADED OFFICIAL STOCK ROM (A. Lenovo_S850_VIBEUI_V1.5_1419_2_ST_S850_4.4.2 B.Lenovo_S850_ROW_S211_140923 C. Lenovo_S850_ROW_S207_140814. D. Lenovo S850 official firmware flash file) + ALL AVAILABLE SP FLASH TOOLS + USB VCOM DRIVER FOR MEDIATEK AND INSTALLED DRIVERS.
USING ABOVE FILES I TRIED TO DOWNLOAD ALL ROMS WITH DIFFERENT SP FLASH TOOLS VERSIONS BUT ALL THE TIME RED BAR CAME TO 100% THEN BAR STUCK ON 0% FOLLOWED BY ERROR "SDMMC WRITE FAIL".
THEN I TRIED UPGRADING FIRMWARE, SAME AGAIN IT GAVE ERROR "FORMAT FAILED"
THEN I TRIED TO FORMAT USING FLAH TOOL (ALL VERSIONS) AGAIN IT GAVE SAME ERROR "FORMAT FAILED"
bogdann8 said:
Hi all,
If you've bought a Lenovo S850 from their new european retail shops or from other distributors, you probably are in the same situation as I was a few days ago.
Doesn't matter the reasons, you probably got annoyed (as I am) of those HUNDREDS of Lenovo and Google useless apps. Maybe you have tried to root it from a custom recovery, such as TWRP (which is the only one I have found anywhere for this phone) but you failed when you probably saw that it's touchscreen doesn't respond. I know I have tried all of those and a few more but no succes.
Well, last saturday, as my final attempt, I searched once more the web to find something that could help me root it. I have found on Lenovo forums (russian forum) that there's a modified boot.img for this very phone. I have downloaded it, flashed it thru FlashTool, booted the phone and attached it to my PC with USB Debugging switched ON. After typing "adb shell" in the command prompt, I had the surprise to see "[email protected]:/ #" as a result instead of that annoying "$". Well, it's time for attack!
THE METHOD DESCRIBED BELOW PROOVED TO BE SUCCESSFULL ON A LENOVO S850 Smartphone running Android 4.4.2, ROW Firmware S850_ROW_S211_140923 (lastest)
*What You Need*
1. Your Unrooted Android Device.
2 .Windows operated PC.
3. ADB Drivers installed on your PC. You can find them in Flashtool.rar or ADB.rar. Just plug in your switched-off phone and point installation wizzard to the folder.
4. The above mentioned archives: Flashtool.rar and ADB.rar. You have to download them both and extract them to your harddrive, they contain all the tools and resources needed.
*Steps*
1. Open Flash_tool.exe located in FlashTool folder you just extracted. In Flash tool, make sure that "DA DL All With Check Sum" is checked, "USB Mode" and "DA Download All/Speed/Force To High Speed" from Options tab are cheched (screenshoot bellow).
2. In Flash Tool click on "Scatter-loading", navigate to FlashTool folder, then target_bin and choose "MT6582_Android_scatter". It should load just " BOOTIMG". Well, now hit Download (with phone switched off and disconnected), wait for the progress bar to show 0% and connect the phone (still swiched off). It should start flashing boot.img on the phone and, after all is done, a green circle "OK" window should announce a successfull flash. Disconnect phone, switch it on, wait for it to load and reconnect it to PC (AFTER you checked USB debugging in USB computer connection that appeared).
3. Rooting time! Open ADB folder and double-click CMD. You have to put/extract ADB folder to C: drive, otherwise adb commands won't work (and you'll have to manually change directory in command prompt and point it to ADB folder). Now you have to insert the following commands in the window you just opened. Here we go:
Code:
adb devices (with this command you can see if the device is properly installed. if it is ok, it should be listed like "A6EAYPRSA6UGGIT4 device". if anywhing else, reinstall ADB Drivers)
adb shell
mount -o remount,rw /system
mkdir /system/bin/.ext
exit
adb push su /system/xbin/daemonsu
adb push su /system/xbin/su
adb push su /system/bin/.ext/.su
adb push Superuser.apk /system/app/Superuser.apk
adb push install-recovery.sh /system/etc/install-recovery.sh
adb push 99SuperSUDaemon /system/etc/init.d/99SuperSUDaemon
adb shell
chmod 0777 /system/bin/.ext
chmod 06755 /system/bin/.ext/.su
chmod 06755 /system/xbin/su
chmod 0755 /system/xbin/daemonsu
chmod 0755 /system/etc/install-recovery.sh
chmod 0755 /system/etc/init.d/99SuperSUDaemon
chmod 0644 /system/app/Superuser.apk
reboot
A successful session should look like this:
Code:
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\ADB>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
A6EAYPRSA6UGGIT4 device
C:\ADB>adb shell
[email protected]:/ # mount -o remount,rw /system
mount -o remount,rw /system
[email protected]:/ # mkdir /system/bin/.ext
mkdir /system/bin/.ext
[email protected]:/ # exit
exit
C:\ADB>adb push su /system/xbin/daemonsu
3919 KB/s (125424 bytes in 0.031s)
C:\ADB>adb push su /system/xbin/su
3919 KB/s (125424 bytes in 0.031s)
C:\ADB>adb push su /system/bin/.ext/.su
3919 KB/s (125424 bytes in 0.031s)
C:\ADB>adb push Superuser.apk /system/app/Superuser.apk
3961 KB/s (4120012 bytes in 1.015s)
C:\ADB>adb push install-recovery.sh /system/etc/install-recovery.sh
0 KB/s (629 bytes in 1.000s)
C:\ADB>adb push 99SuperSUDaemon /system/etc/init.d/99SuperSUDaemon
0 KB/s (55 bytes in 1.000s)
C:\ADB>adb shell
[email protected]:/ # chmod 0777 /system/bin/.ext
chmod 0777 /system/bin/.ext
[email protected]:/ # chmod 06755 /system/bin/.ext/.su
chmod 06755 /system/bin/.ext/.su
[email protected]:/ # chmod 06755 /system/xbin/su
chmod 06755 /system/xbin/su
[email protected]:/ # chmod 0755 /system/xbin/daemonsu
chmod 0755 /system/xbin/daemonsu
Unable to chmod /system/xbin/daemonsu: Read-only file system
[email protected]:/ # mount -o remount,rw /system
mount -o remount,rw /system
[email protected]:/ # chmod 0755 /system/xbin/daemonsu
chmod 0755 /system/xbin/daemonsu
[email protected]:/ # chmod 0755 /system/etc/install-recovery.sh
chmod 0755 /system/etc/install-recovery.sh
[email protected]:/ # chmod 0755 /system/etc/init.d/99SuperSUDaemon
chmod 0755 /system/etc/init.d/99SuperSUDaemon
[email protected]:/ # chmod 0644 /system/app/Superuser.apk
chmod 0644 /system/app/Superuser.apk
[email protected]:/ # reboot
reboot
C:\ADB>
If anything went right, your phone should be rooted. Mine was (and I'm not a programmer). Here's some screenshoots I made:
Before...
... and After
There's a few screenshoots with SuperSU in action after successful rooting:
I'm not the author of this method, I've just collected and tested different things on my OWN phone until I was able to root it. Use it on your own risk!
Click to expand...
Click to collapse
Should this work for my Lenovo s850t or not? I have not the rooting problem but the problem is something else, that i believe is due to a failed root.
Anyways, I have the phone lenovo s850t, I rooted it in order to gain access to Google play, the rooting made a problem and now the phone displays a continues nonstop error message "unfortunately theme has stopped". I tried my level best to flash the phone but I have failed every time since I can't find the suitable ROM file. I downloaded a dozen ROMs (various versions from different sources) for it and all have the same problem that the scatter file doesn't work.. One rom file's scatter work but that was for s850 not s850t, so flashing process failed. Please please please help me out bcz here no software personnel can repair it, and no lenovo office in our city. I will appreciate your act of kindness.
Here is the screenshot:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hi sir can you please help me after flashing my S850 I suddenly i got problems on network no IMEI