Develop Bugs

[Q] problem downgrading my DHD(1.84)

this is the error i m facing(in bold):
E:\Setup\android\root\Downgrade>adb push misc_version /data/local/tmp
1104 KB/s (15837 bytes in 0.014s)
E:\Setup\android\root\Downgrade>adb shell chmod 777 /data/local/tmp/psneuter
E:\Setup\android\root\Downgrade>adb shell chmod 777 /data/local/tmp/misc_version
E:\Setup\android\root\Downgrade>adb shell /data/local/tmp/psneuter
mmap() failed. Operation not permitted
what should i do?

Well you did not push psneuter there, so you cannot run it You just pushed misc_version.

jkoljo said:
Well you did not push psneuter there, so you cannot run it You just pushed misc_version.
Click to expand...
Click to collapse
i did it its just that i missed it while copying the the text from cmd. here it is:
e:\Setup\android\root\Downgrade>adb push psneuter /data/local/tmp
1661 KB/s (557962 bytes in 0.328s)
e:\Setup\android\root\Downgrade>adb push misc_version /data/local/tmp
1189 KB/s (15837 bytes in 0.013s)
e:\Setup\android\root\Downgrade>adb shell chmod 777 /data/local/tmp/psneuter
e:\Setup\android\root\Downgrade>adb shell chmod 777 /data/local/tmp/misc_version
e:\Setup\android\root\Downgrade>adb shell /data/local/tmp/psneuter
mmap() failed. Operation not permitted
phone connected to Windows7 in charge only mode with usb debugging enabled.

hey,
I am facing the exact same problem, I live in India and my DHD isn't carrier branded or anything.
Earlier when i tried to downgrade, I was getting CID failed...so i did a goldcard and now I am getting the exact same error as mentioned above...can anyone plz help?

Yea, i got that error when i was trying to downgrade too, just a week ago!
my phone was branded, and when i didn't do the GoldCard, i didn't get the error.
but as soon as i did the goldcard, then the error came twice.
what i did was restart the phone, the computer and formatted the SD card and did the whole process again, then i typed
>adb shell /data/local/tmp/psneuter
and i got the error again. I waited like 3-6 seconds and tried the above command again, and it worked.
honestly, i dont know where the problem comes from. but good luck

wrong n missing image files error in bootloader
after the temp root.. when it goes in bootloader , it does say that the image files are missing and wrong image file…
m running on htc desire hd 1.84 stock rom unlocked.
please help me out

Need help with my T-Mobile G2 Root

I am currently reading the root guide, firstly my PC properly detects my phone, do I still need the USB Driver installed? If so how? I already downloaded it.
Secondly "The HTC Desire Z with a firmware version higher than 1.34 and the Desire HD with a firmware version higher then 1.32 have to be downgraded "
Is that speaking of the Android version, If so I am currently "2.2"? Or the build? If so then mine is "1.22.5".
http://forum.xda-developers.com/wik...sion#Rooting_the_Vision_.28G2.2FDZ.29_and_DHD
That's about the current questions I have, new to this.

DroidStation said:
I am currently reading the root guide, firstly my PC properly detects my phone, do I still need the USB Driver installed? If so how? I already downloaded it.
Secondly "The HTC Desire Z with a firmware version higher than 1.34 and the Desire HD with a firmware version higher then 1.32 have to be downgraded "
Is that speaking of the Android version, If so I am currently "2.2"? Or the build? If so then mine is "1.22.5".
http://forum.xda-developers.com/wik...sion#Rooting_the_Vision_.28G2.2FDZ.29_and_DHD
That's about the current questions I have, new to this.
Click to expand...
Click to collapse
If your computer detects your device and, when you run 'adb devices' it shows, then you should be all set. The Desire Z/HD is referring to a different device, the G2 is an HTC Vision.
Sent from my HTC Vision using XDA App

Okay, so that is no to the downgrade I assume, next question.
I downloaded all the files required (4 of them) Do I extract them and add the folders with the files to the phone? Or the files from inside the folders to the phone?

Hi, you just need to extract the files to a temp folder on your computer and run the adb commands from that folder.

One folder? Or leave them in each folder when I extracted them?
Also I downloaded the drivers, because my PC detected everything except the adb, so I assigned the drivers files for the adb.

DroidStation said:
One folder? Or leave them in each folder when I extracted them?
Also I downloaded the drivers, because my PC detected everything except the adb, so I assigned the drivers files for the adb.
Click to expand...
Click to collapse
If you installed the android sdk(which you should of) place any files you plan on using adb with and put in "platform-tools" folder located in the android-sdk-windows folder that your installation should of created. If you want to leave the unzipped files in individual folders it will add a lot of extra time to the process. If everything is in platform-tools you don't need to quit changing the path. At least that's how I do it..easier and quicker
dont send me pm's crying about how i hurt your feelings in a thread

Alright, I am back, No offense taken, thanks for posting.
I am almost done to do the root I have setup the android sdk and it's filling working.
I would like a little more clarification on the files though, the "4" files that I downloaded. Now from the post mentioned above you said to place the files in the "platform-tools" folder, zipped or unzipped?

Well, I placed all the files, clockwork, etc.. Into the "platform-tools" folder located on my "C:\android-sdk-windows\platform-tools"
Now when I run adb I get these errors.
C:\Users\Frank>adb push psneuter /data/local/tmp/
cannot stat 'psneuter': No such file or directory
C:\Users\Frank>adb push psneuter /data/local/tmp/
cannot stat 'psneuter': No such file or directory
C:\Users\Frank>adb push gfree /data/local/tmp/
cannot stat 'gfree': No such file or directory
C:\Users\Frank>adb push busybox /data/local/tmp/
cannot stat 'busybox': No such file or directory
C:\Users\Frank>adb push hboot-eng.img /data/local/tmp
cannot stat 'hboot-eng.img': No such file or director
C:\Users\Frank>adb push root_psn /data/local/tmp/
cannot stat 'root_psn': No such file or directory
C:\Users\Frank>adb push flash_image /data/local/tmp/
cannot stat 'flash_image': No such file or directory
C:\Users\Frank>adb push su /sdcard/
cannot stat 'su': No such file or directory
C:\Users\Frank>adb push Superuser.apk /sdcard/
cannot stat 'Superuser.apk': No such file or director
C:\Users\Frank>adb shell chmod 755 /data/local/tmp/*
Click to expand...
Click to collapse

Run the adb command from the platform tool folder.
C:\android-sdk-windows\platform-tools"\adb push psneuter ...

So for example..
C:\android-sdk-windows\platform-tools adb push psneuter /data/local/tmp/ ?
Is that correct, can you write a line for example please? Sorry if I am asking for much, just want to make sure that I get this right.

almost:
C:\android-sdk-windows\platform-tools\adb push psneuter /data/local/tmp/

Now I receive this.
C:\Users\Frank>C:\android-sdk-windows\platform-tools\adb push psneuter /data/loc
al/tmp/
cannot stat 'psneuter': No such file or directory
Click to expand...
Click to collapse
I entered this command.
C:\android-sdk-windows\platform-tools\adb push psneuter /data/local/tmp/

At the command prompt, type:
Code:
cd C:\android-sdk-windows\platform-tools
Then type the adb push commands...

I do apologize for being difficult but I still run into these issues.
C:\android-sdk-windows\platform-tools>adb push psneuter /data/local/tmp/
cannot stat 'psneuter': No such file or directory
C:\android-sdk-windows\platform-tools>adb push gfree /data/local/tmp/
cannot stat 'gfree': No such file or directory
C:\android-sdk-windows\platform-tools>adb push busybox /data/local/tmp/
cannot stat 'busybox': No such file or directory
C:\android-sdk-windows\platform-tools>adb push hboot-eng.img /data/local/tmp/
cannot stat 'hboot-eng.img': No such file or directory
C:\android-sdk-windows\platform-tools>adb push root_psn /data/local/tmp/
cannot stat 'root_psn': No such file or directory
C:\android-sdk-windows\platform-tools>adb push flash_image /data/local/tmp/
cannot stat 'flash_image': No such file or directory
C:\android-sdk-windows\platform-tools>adb push su /sdcard/
cannot stat 'su': No such file or directory
C:\android-sdk-windows\platform-tools>adb push Superuser.apk /sdcard/
cannot stat 'Superuser.apk': No such file or directory
C:\android-sdk-windows\platform-tools>adb shell chmod 755 /data/local/tmp/*
Click to expand...
Click to collapse
Do I unzip the ".zip" files?

Okay, well I decided to use a different directory with just the required files and here are my results from running the commands all at once.
C:\Users\Frank\Desktop\G2>adb push psneuter /data/local/tmp/
push: psneuter/psneuter.c -> /data/local/tmp/psneuter.c
push: psneuter/psneuter -> /data/local/tmp/psneuter
2 files pushed. 0 files skipped.
1657 KB/s (561954 bytes in 0.331s)
C:\Users\Frank\Desktop\G2>adb push gfree /data/local/tmp/
cannot stat 'gfree': No such file or directory
C:\Users\Frank\Desktop\G2>adb push busybox /data/local/tmp/
cannot stat 'busybox': No such file or directory
C:\Users\Frank\Desktop\G2>adb push hboot-eng.img /data/local/tmp/
cannot stat 'hboot-eng.img': No such file or directory
C:\Users\Frank\Desktop\G2>adb push root_psn /data/local/tmp/
cannot stat 'root_psn': No such file or directory
C:\Users\Frank\Desktop\G2>adb push flash_image /data/local/tmp/
push: flash_image/flash_image -> /data/local/tmp/flash_image
1 file pushed. 0 files skipped.
1511 KB/s (68108 bytes in 0.044s)
C:\Users\Frank\Desktop\G2>adb push su /sdcard/
cannot stat 'su': No such file or directory
C:\Users\Frank\Desktop\G2>adb push Superuser.apk /sdcard/
cannot stat 'Superuser.apk': No such file or directory
C:\Users\Frank\Desktop\G2>adb shell chmod 755 /data/local/tmp/*

Perhaps I need to change the file names on the commands?
These are the files/folders on the directory.
flash_image
gfree_05
gfree_root_psn
psneuter
vision.hboot-0.76.2000
recovery-clockwork-3.0.2.4-vision

Put the files you want to push in the same directory as adb.exe

Well, now I only get some errors, are you sure the commands are using the correct file names?
C:\android-sdk-windows\platform-tools>adb push psneuter /data/local/tmp/
adb server is out of date. killing...
* daemon started successfully *
push: psneuter/psneuter.c -> /data/local/tmp/psneuter.c
push: psneuter/psneuter -> /data/local/tmp/psneuter
2 files pushed. 0 files skipped.
1270 KB/s (561954 bytes in 0.432s)
C:\android-sdk-windows\platform-tools>adb push gfree /data/local/tmp/
cannot stat 'gfree': No such file or directory
C:\android-sdk-windows\platform-tools>adb push busybox /data/local/tmp/
cannot stat 'busybox': No such file or directory
C:\android-sdk-windows\platform-tools>adb push hboot-eng.img /data/local/tmp/
cannot stat 'hboot-eng.img': No such file or directory
C:\android-sdk-windows\platform-tools>adb push root_psn /data/local/tmp/
cannot stat 'root_psn': No such file or directory
C:\android-sdk-windows\platform-tools>adb push flash_image /data/local/tmp/
push: flash_image/flash_image -> /data/local/tmp/flash_image
1 file pushed. 0 files skipped.
468 KB/s (68108 bytes in 0.142s)
C:\android-sdk-windows\platform-tools>adb push su /sdcard/
cannot stat 'su': No such file or directory
C:\android-sdk-windows\platform-tools>adb push Superuser.apk /sdcard/
cannot stat 'Superuser.apk': No such file or directory
C:\android-sdk-windows\platform-tools>adb shell chmod 755 /data/local/tmp/*
Click to expand...
Click to collapse
Here are the commands I am running.
adb push psneuter /data/local/tmp/
adb push gfree /data/local/tmp/
adb push busybox /data/local/tmp/
adb push hboot-eng.img /data/local/tmp/
adb push root_psn /data/local/tmp/
adb push flash_image /data/local/tmp/
adb push su /sdcard/
adb push Superuser.apk /sdcard/
adb shell chmod 755 /data/local/tmp/*
Click to expand...
Click to collapse
Here are the file names I have.
flash_image
gfree_05
gfree_root_psn
psneuter
vision.hboot-0.76.2000
recovery-clockwork-3.0.2.4-vision

Okay, I finally ran all the commands fine, needed to have them as the actual files.
I ran this command, but nothing happened.
"adb shell chmod 755 /data/local/tmp/*"
I that normal or do I need to change the "*" to something?
Because when I try to run the temp root command I receive this.
C:\android-sdk-windows\platform-tools>adb shell /data/local/tmp/psneuter
/data/local/tmp/psneuter: permission denied

The "*" means everything in that folder so no you are fine there.
Sent from my HTC Vision using XDA App

[Q] Needing help with HTC Desire Z root

Hey everyone
Lately i've been trying to downgrade/root my phone the HTC Desire Z,
but once i came across step 15 some problem ocurred. Once i pasted this command below in the cmd.
adb install AndroidTerm.apk
adb push busybox /data/local/tmp/
adb push gfree /data/local/tmp/
adb push rage /data/local/tmp
adb push root /data/local/tmp/
adb shell chmod 0755 /data/local/tmp/*
adb push su /sdcard/
adb push Superuser.apk /sdcard/
Then i received this as result.
C:\androidsdk\tools>adb install AndroidTerm.apk
1380 KB/s (49478 bytes in 0.035s)
pkg: /data/local/tmp/AndroidTerm.apk
Failure [INSTALL_FAILED_ALREADY_EXISTS]
C:\androidsdk\tools>adb push busybox /data/local/tmp/
1716 KB/s (1926944 bytes in 1.096s)
C:\androidsdk\tools>adb push gfree /data/local/tmp/
1874 KB/s (134401 bytes in 0.070s)
C:\androidsdk\tools>adb push rage /data/local/tmp
752 KB/s (5392 bytes in 0.007s)
C:\androidsdk\tools>adb push root /data/local/tmp/
112 KB/s (575 bytes in 0.005s)
C:\androidsdk\tools>adb shell chmod 0755 /data/local/tmp/*
Unable to chmod /data/local/tmp/misc_version: Operation not permitted
C:\androidsdk\tools>adb push su /sdcard/
failed to copy 'su' to '/sdcard//su': Permission denied
C:\androidsdk\tools>adb push Superuser.apk /sdcard/
failed to copy 'Superuser.apk' to '/sdcard//Superuser.apk': Permission denied
Does anyone know what the exact problem is? , because i cant get further through the tutorial now.
The one i'm using atm is the http://forum.xda-developers.com/showthread.php?t=905261
but translated in dutch.
Hopefully someone can help me !

Downgrade help

I am following these steps
http://theunlockr.com/2011/07/22/how-to-downgrade-a-gingerbread-t-mobile-g2-so-it-can-be-rooted/
I typed /data/local/tmp/fre3vo -debug -start FBA90000 -end FFFFFFFF
it then says exploiting device and then goes back to C:\androidsdk\tools and I never get the # command prompt. Looking for advice on what to do next.
Thanks in advance.

Did you retry 'adb shell' when it sends you back to C:\androidsdk\tools?
Cause the exploit is meant to kick you out of shell, then you have to go back in it.
-Nipqer

Nipqer said:
Did you retry 'adb shell' when it sends you back to C:\androidsdk\tools?
Cause the exploit is meant to kick you out of shell, then you have to go back in it.
-Nipqer
Click to expand...
Click to collapse
Yes, and I am now following this guide http://forum.xda-developers.com/showthread.php?t=999796 .
Am I ok to proceed even though I am getting permission denied below?
C:\AndroidSDK\tools>adb push hboot_7230_0.76.2000_100820.nb0 /data/local
1709 KB/s (1048576 bytes in 0.599s)
C:\AndroidSDK\tools>adb shell
$ md5sum /data/local/hboot_7230_0.76.2000_100820.nb0
md5sum /data/local/hboot_7230_0.76.2000_100820.nb0
md5sum: permission denied
$

obas said:
Yes, and I am now following this guide http://forum.xda-developers.com/showthread.php?t=999796 .
Am I ok to proceed even though I am getting permission denied below?
C:\AndroidSDK\tools>adb push hboot_7230_0.76.2000_100820.nb0 /data/local
1709 KB/s (1048576 bytes in 0.599s)
C:\AndroidSDK\tools>adb shell
$ md5sum /data/local/hboot_7230_0.76.2000_100820.nb0
md5sum /data/local/hboot_7230_0.76.2000_100820.nb0
md5sum: permission denied
$
Click to expand...
Click to collapse
i also get this following this guide http://forum.xda-developers.com/showthread.php?t=999796 .
Am I ok to proceed even though I am getting permission denied below?
C:\AndroidSDK\tools>adb push hboot_7230_0.76.2000_100820.nb0 /data/local
1709 KB/s (1048576 bytes in 0.599s)
C:\AndroidSDK\tools>adb shell
$ md5sum /data/local/hboot_7230_0.76.2000_100820.nb0
md5sum /data/local/hboot_7230_0.76.2000_100820.nb0
md5sum: permission denied
$

That guide is for removing eng hboot, if you have eng hboot, there would be easier ways to remove it.
You need to get a root shell to proceed.
You could get help faster if you went to the #g2root channel on freenode irc [link]
-Nipqer

Nipqer said:
That guide is for removing eng hboot, if you have eng hboot, there would be easier ways to remove it.
You need to get a root shell to proceed.
You could get help faster if you went to the #g2root channel on freenode irc [link]
-Nipqer
Click to expand...
Click to collapse
I went to that page and got no help . I was wondering if you could look over my steps before I attempt this any further, does this look like it will work.
C:\AndroidSDK\tools>adb push fre3vo /data/local/tmp
adb server is out of date. killing...
* daemon started successfully *
956 KB/s (9796 bytes in 0.010s)
C:\AndroidSDK\tools>adb push misc_version /data/local/tmp/misc_version
1405 KB/s (15837 bytes in 0.011s)
C:\AndroidSDK\tools>adb shell chmod 777 /data/local/tmp/fre3vo
C:\AndroidSDK\tools>adb shell chmod 777 /data/local/tmp/misc_version
C:\AndroidSDK\tools> /data/local/tmp/fre3vo -debug -start FBA90000 -end FFFFFFFF
---- Also if the above process looks good can my next command be the following
$ adb push PC10IMG_Vision_TMOUS_1.19.531.1_Radio_12.21.60.09b _26.02.01.15_M2_release_149459_signed.zip /sdcard/PC10IMG.zip ????

Yeah should be working.
If no one responds immediatly in irc just wait a bit. It's not the most active channel, but someone will come along to help.
I'm not sure why it's not working for you.
-Nipqer

Nipqer said:
Yeah should be working.
If no one responds immediatly in irc just wait a bit. It's not the most active channel, but someone will come along to help.
I'm not sure why it's not working for you.
-Nipqer
Click to expand...
Click to collapse
Actually everything worked up till this command
$ adb push PC10IMG_Vision_TMOUS_1.19.531.1_Radio_12.21.60.09b_26.02.01.15_M2_release_149459_signed.zip /sdcard/PC10IMG.zip
when I did that it said "file not found" I do believe. So I then tried $ adb push PC10IMG.zip /sdcard/PC10IMG.zip and I got the same error.
I have both the PC10IMG_Vision_TMOUS_1.19.531.1_Radio_12.21.60.09b_26.02.01.15_M2_release_149459_signed.zip and PC10IMG.zip in the androidsdk\tools folder so this should work right? not sure why I am getting file not found.
Thanks for all you help also I am also there I can feel it

You can use the TAB key to auto-complete file names, so you can make sure you're not misspelling anything.
Make sure the adb push command is done in a C:\> prompt, not $/# (push before adb shell)
-Nipqer

Nipqer said:
You can use the TAB key to auto-complete file names, so you can make sure you're not misspelling anything.
Make sure the adb push command is done in a C:\> prompt, not $/# (push before adb shell)
-Nipqer
Click to expand...
Click to collapse
Ok, now I'm confused because this link http://forum.xda-developers.com/showthread.php?t=1178912 has this command under the "downgrade" section.
$ adb push PC10IMG_Vision_TMOUS_1.19.531.1_Radio_12.21.60.09b_26.02.01.15_M2_release_149459_signed.zip /sdcard/PC10IMG.zip
$ adb reboot bootloader
That seems to me they are saying to do adb push from the $ command.

[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