Develop Bugs

Unlocked Motorola Backflip Questions?

I just bought an unlocked Motorola Backflip off ebay.
I had a few questions.
If I do a hard reset, do I need to unlock it again?
If I 'clear storage' or reset defaults, do I need to unlock it again?
When the Android 2.1 upgrade comes this fall, will I need to unlock it again after upgrading?

Anderdroid said:
I just bought an unlocked Motorola Backflip off ebay.
I had a few questions.
If I do a hard reset, do I need to unlock it again?
If I 'clear storage' or reset defaults, do I need to unlock it again?
When the Android 2.1 upgrade comes this fall, will I need to unlock it again after upgrading?
Click to expand...
Click to collapse
I did a hard reset (Factory refresh) and did NOT have to do Re _Unlock...I hope this helps

hard reset will not lock the phone i did it yesterday no problem go for it

how to root moto backflip???
plzzz help

motorola backflip rooted
I used these guide whith my backflip.Instructions :
Setup:
- Install adb unless you haven't done so and Motorola drivers unless you haven't done so
- Download attached archive
- Extract to a directory, I used c:\Moto_MSM_Root
- Make sure you have USB degugging enabled
- Change connection to PC Mode
Process:
- Open command prompt
- cd c:\wherever-your-sdk-tools-folder-is
- adb devices (to verify the connection)
- cd c:\Moto_MSM_Root
- adb push Superuser.apk /sdcard/Superuser.apk
- adb push su /sdcard/su
(optional) - adb push busybox /sdcard/busybox
- adb push rageagainstthecage-arm5.bin /data/local/tmp/rageagainstthecage-arm5.bin
- adb shell
- cd data/local/tmp
- chmod 0755 rageagainstthecage-arm5.bin
- ./rageagainstthecage-arm5.bin
- let the process run until it returns you to c:/Moto_MSM_Root (be patient, but may need to reboot the phone)
- cd c:/wherever-your-sdk-tools-folder-is
- adb kill-server
- adb devices (to verify the connection)
- adb shell
If you end up with "#" prompt, do the following. Otherwise reboot the phone and try again "adb shell". If even that doesn't give "#" prompt, go back to step "./rageagainstthecage-arm5.bin". There are mixed results atm., but some succeeded. See this post for possible way:
- mount -o rw,remount /dev/block/mtdblock1 /system
- cat /sdcard/su > /system/xbin/su
- chown root.root /system/xbin/su
- chmod 6755 /system/xbin/su
- cat /sdcard/Superuser.apk > /system/app/Superuser.apk
- chown root.root /system/app/Superuser.apk
- chmod 644 /system/app/Superuser.apk
(optional) - cat /sdcard/busybox > /system/bin/busybox
(optional) - chown root.root /system/bin/busybox
(optional) - chmod 755 /system/bin/busybox
- mount -o ro,remount /dev/block/mtdblock1 /system
- exit
- : google for......." Moto_MSM_Root "

how to unlock my backflip whit op lock?somoane can help me

How to root manually/without Windows

There is already an excellent write-up on how to use SuperOneClick to root your Optimus V.
Unfortunately, you may not have a Windows machine available to run the util, or your PC hates the LG drivers, or you may wish to control how you go about rooting your device.
Hence this short write-up which, obviously, relies on pieces I got from that other write-up.
I. Rooting your device
1. You still need ADB!
2. Download the LG Optimus V Tools package from http://nexus.zteo.com/projects/tools/
3. Unzip it
4. Command-line:
Code:
adb push psneuter /data/local/tmp/
adb push su /data/local/tmp/
adb shell
cd /data/local/tmp
chmod 777 psneuter
chmod 777 su
./psneuter
5. You should be kicked out of the shell
6. Command-line:
Code:
adb shell
mount -o remount,rw -t yaffs2 /dev/block/mtdblock5 /system
cat /data/local/tmp/su > /system/bin/su
mount -o remount,ro -t yaffs2 /dev/block/mtdblock5 /system
(Oh look you are root!)
That's it. You now have permanent root access.
After rebooting your phone, adb should be back to logging you in as a regular user but typing "su" will do the trick.
Note: I realize that the version of SuperUser.apk that comes with SuperOneClick might be re-usable here. I haven't had any success with it but you may.
II. Flashing a new ROM
1. After rooting your device, obviously...
2. Get an image for the ROM you wish to flash...
Currently, my favourite one is a fairly recent version of Zefie's CM7.
You can find it by googling "update-cm-7-04282011-NIGHTLY-thunderc-Xionia-signed.zip" -- I will refer to it, below, as <your_rom_zip_file>
3. Get a minimum Google Apps package for flashing as well.
Here, I would google "gapps-gb-20110325-signed.zip" -- I will refer to it, below, as <your_gapps_zip_file>
3. Command-line:
Code:
adb push flash_recovery /data/local/tmp/
adb push recovery.img /sdcard/
adb push Debug-FormatSYSTEM.zip /sdcard/
adb push <your_rom_zip_file> /sdcard/
adb push <your_gapps_zip_file> /sdcard/
adb shell
su
chmod 777 /data/local/tmp/flash_recovery
/data/local/tmp/flash_recovery /sdcard/recovery.img
reboot recovery
4. In recovery: Flash Debug-FormatSYSTEM.zip
5. In recovery: Wipe cache and dalvik-cache
6. In recovery: Flash <your_rom_zip_file> -- this will take a while
7. Do not reboot!
8. In recovery: Flash <your_gapps_zip_file>
9. Now, reboot.
10. Let your phone think about life for a few minutes
11. Select "Skip" when your phone asks you to create/enter your account info
12. Launch the market; now, enter your main account information

Hey first of all let me tell you that I appreciate this guide. Now my problem is that I am such a noob that I may be doing this wrong.I download the file to my optimus.Then in an explorer I extract it, correct? After that once I put in the first line of command on terminal emulator I get an error that says "adb: permission denied". Please help this guide is my last resort.Whatever I do I can not root through windows.It would be nice if you could explain in more detail every step. Thanks!

help
can u please add a little more detail thank u very much appreciated.

SouthParkFan15:
adb is a tool that you run on your computer; it is available for Windows, Mac OS X and Linux. It is part of the Google SDK.
thizizjohnny:
Could you give me a little more detail regarding what detail you are interested in?

How do I unzip?.. is extract the same thing? I'm running Linux mint 10. How do I get adb? Excuse my noobness.
Sent from my VM670 using XDA App

Oh and one last thing.. does this work on android version 2.2.1?
Sent from my VM670 using XDA App

Yes this works with 2.2.1.
On Linux Mint, you can use the package manager or the unzip command in a terminal window.
apk:
Download the SDK at http://developer.android.com/sdk/index.html
Install it, then run "android" and select "Install platform tools"

I finally got adb on my system, but when I type in "adb devices" nothing comes up and when I do any command that involves the phone i get "error:device not found".Yes I have usb debugging on and yes I have all the right drivers installed and yes I have tried rebooting a million times, and no my computer has never recognized my phone the way it should.Let me also point out that though pdanet or droid explorer they can't find my device. Help please I'm desperate!

Oh, my. Sorry to read that.
Problem is, in 2.2.x, the exploits that give you root access rely on ADB itself so you couldn't be more out of luck.
On second thought...this may seem a bit weird but there may be a way. I have to think about it. It would involve using a file manager that agrees to "see" /data/local/tmp, running psneuter from there and keeping our fingers crossed. I'll keep you updated.

Alright thanks cyansmoke! Keep me informed.

I ran all of the steps for rooting and I didn't get one error. It didn't seem to work though. When I launch adb again after rebooting my phone I get permission denied when I try to run su.
Here is the cap from my command line. I have no idea why it didn't take.
C:\phone\LGOptimusVTools>adb shell
$ cd /data/local/tmp
cd /data/local/tmp
$ chmod 777 psneuter
chmod 777 psneuter
$ chmod 777 su
chmod 777 su
$ ./psneuter
./psneuter
property service neutered.
killing adbd. (should restart in a second or two)
C:\phone\LGOptimusVTools>adb shell
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock5 /system
mount -o remount,rw -t yaffs2 /dev/block/mtdblock5 /system
# cat /data/local/tmp/su > /system/bin/su
cat /data/local/tmp/su > /system/bin/su
# mount -o remount,ro -t yaffs2 /dev/block/mtdblock5 /system
mount -o remount,ro -t yaffs2 /dev/block/mtdblock5 /system
# exit
exit
C:\phone\LGOptimusVTools>adb shell
$ su
su
su: permission denied
$

It's possible that you have another su in your path that takes precedence.
Please try typing:
/system/bin/su

Hey, do you know if there is a way to upgrade my device to froyo 2.2.2? It's currently 2.2.1 and whenever I go to update system it says something like "Your system is up to date".Incase you have forgotten I have the optimus v that can't establish connections with the computer.So what I could do?I'm thinking that If I do that then maybe it could fix all of my problems (or some of them).Thanks

I don't think that it will help you no.
OK it's taking longer than I thought because my wife's LGV, after I restored it to stock, decided that it would not allow psneuter anymore.
Thus, I will need you to run these commands for me and let me know how that went:
1. First, copy psneuter to the root of your SD Card.
2. Then, download Terminal Emulator from the market
3. Run Terminal Emulator, type:
Code:
cp /sdcard/psneuter /data/local/tmp/
chmod 777 /data/local/tmp/psneuter
/data/local/tmp/psneuter
Now, if we are lucky, you should get kicked out of the terminal app (I know it's weird but there is a claim that it goes through adb(!))
Restart the terminal emulator. If we are double-lucky, your prompt should have changed from '$' to '#'
Fingers crossed. Still surprised to hear that terminal emulator would go through adb. No, let me rephrase that: I am moderately surprised, in fact, considering the limitations put on non-rooted apps.

After I put psneuter on the root of my sdcard.I go to terminal emulator and put in the first code and it says "cp: permission denied".Any suggestions?

SouthParkFan15 said:
After I put psneuter on the root of my sdcard.I go to terminal emulator and put in the first code and it says "cp: permission denied".Any suggestions?
Click to expand...
Click to collapse
Ah, my bad, no "cp" by default.
New instructions:
Code:
cat /sdcard/psneuter > /data/local/tmp/
chmod 777 /data/local/tmp/psneuter
/data/local/tmp/psneuter

After I put in the first code I get an error message saying "cannot create /data/local/tmp/: is a directory".

*facepalm*
Of course I should have written:
Code:
cat /sdcard/psneuter > /data/local/tmp/psneuter

I put in "cat /sdcard/psneuter > /data/local/tmp/psneuter" and I get an error message saying "cannot create /data/local/tmp/psneuter: directory nonexistent".

Any suggestions?

[HOWTO] (Manually) Rooting the Kindle Fire 2 with a Mac

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

[Q] Linux user with some questions about root methods.

Okay folks, I am a rooting newb where it comes to this wonderous device known as the Optimus G, and I need some questions answered.
First lemme fill you all in on some details where the computer I might be using to root my Optimus G is concerned. I run Zorin OS 6.1 64bit Core edition (yes, Linux) and that obviously that begs my first question, of any of the rooting methods mentioned in the development part of this forum, are there any that will work with Linux? And if so which ones or is there some kind of special magic I'll need to cast or some kind of coding wizardry level I'll have to obtain in order to be able to root my Optimus G?
Second, to fill you in on the phone, yes I have updated to ZV9 so if that borks me if you could please let me know?
Third, and Fourth actually are my concerns over being able to fix whatever possible brick type damage might be done. 3)How stable are the root/unlock methods, meaning there would be no way to reverse them? Of course I mean outside of accepting an OTA update which I already know better than to do on a custom ROM (had a Samsung Epic 4g before this so yeah I know how that goes.)
and 4)Is there an LGNPST (sp?) version for Linux or will I have to figure out a wa to maybe run it on WINE or something along those lines?
I'd ask about ROMS but I know everybody has an opinion of their own and I don't so much mind the stock one, though I might get the debloated version and see what else I can do with that.
Thanks in advance everybody for any help you all can give.

1) You can root through linux, although I don't know about which distros. I did it on ubuntu, using one of the links in the link in my sig.
2) AFAIK, you have to be on zv7/8 to root or unlock. You will have to use LGNPST to go back to one of those, and as far as I've ever heard that is a windows program only.
3) Both the root and unlock methods are reversible through whatever program you use to do it.
4) ???

You forgot profit!!!!
Sent from my LG-LS970 using xda premium

As long as you can attain a root shell and install ADB aka Android SDK, and as long as after that you can run ADB shell and then receive a prompt from your device you should be able to push the necessary files and then run the exploit and install the superuser binary there should be no issues. I actually took the windows root method, and used the commands in my Debian box and it worked very well. The only thing that I would be concerned with is weather not you can get a root shell in your specific version once that is attained, run ADB start-server as root then finish.
Basically I took this root method, and modded the script to fit linux.
(as noted from my post on the last page of that thread)
Preparation
ADB can be found either from the android sdk(tools only) or from the 'stuff' folder, in the archive below (i ran the one from the sdk)
Download this zip file, and extract the 'stuff' folder to a newly created 'root' folder on your Desktop
Open a terminal and cd to ~/Desktop/root
My adb location is coded into my $PATH variable so when I issue adb, it runs ~/android-sdk-linux/platform-tools/adb but you can either set up an alias (to the one included which would be alias adb=~/Desktop/root/stuff/adb if you follow the below extraction procedures or the one from the sdk which could be anywhere)
Before running the root I ran:
Code:
su -
adb start-server
exit
Then to test whether or not I had the correct version of adb, I ran:
Code:
adb shell
You should see your prompt change to that of the phone. if it displays any type of error message, please check your version of adb. to exit this prompt and continue with the root, simply type exit and press enter.
ROOT:
Paste the following into your terminal (which should now be in the ~/Desktop/root directory)
Code:
adb "wait-for-device"
adb push stuff/busybox /data/local/tmp/.
adb push stuff/su /data/local/tmp/.
adb push stuff/Superuser.apk /data/local/tmp/.
adb shell chmod 755 /data/local/tmp/busybox
adb restore stuff/fakebackup.ab
echo 'Select "Restore my data" on your phone!'
adb shell "while ! ln -s /data/local.prop /data/data/com.android.settings/a/file99; do :; done" > /dev/null
echo "Your phone will now reboot twice, DO NOT DISCONNECT USB!"
adb reboot
adb "wait-for-device"
adb shell "/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/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"
echo "Rooting Complete!"
echo "SuperSU should now be available in your applications drawer!"
Assimilated using the interface that interacts with the advanced internet.

[GUIDE][ROOT] Lenovo S850 (ROW)

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