Related
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
Note to moderation team: I wanted to post my contribution directly into the author's thread but I'm not allowed to do so.
If my post is right, maybe you could merge my post with the original discussion.
Hi everyone,
I'd like to to provide my feedback regarding the following tool written by Bin4ry.
Tool is available here:
http://forum.xda-developers.com/showthread.php?t=1886460
First of all, I'd like to thank Bin4ry for his job, because with the help of his tool, I have successfully rooted my noname (*) tablet, running ICS 4.0.4.
However, it did not work out at the very first try: the tool said everything went fine but after reboot, my tablet was still not rooted.
Actually, I entered the guts of Bin4ry's script, and find out this trick.
The original script contains this section:
Code:
:NORMAL
IF %ric% == 1 GOTO RICSTUFF
echo Going to copy files to it's place
stuff\adb.exe 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"
GOTO FINISH
Actually, I think that the command "/data/local/tmp/busybox" is missing at some locations.
So I rewrote the script as follows and got my tablet rooted !!
Code:
:NORMAL
IF %ric% == 1 GOTO RICSTUFF
echo Going to copy files to it's place
stuff\adb.exe shell "/data/local/tmp/busybox mount -o remount,rw /system"
stuff\adb.exe shell "/data/local/tmp/busybox mv /data/local/tmp/su /system/xbin/su"
stuff\adb.exe shell "/data/local/tmp/busybox mv /data/local/tmp/Superuser.apk /system/app/Superuser.apk"
stuff\adb.exe shell "/data/local/tmp/busybox cp /data/local/tmp/busybox /system/xbin/busybox"
stuff\adb.exe shell "/data/local/tmp/busybox chown 0.0 /system/xbin/su"
stuff\adb.exe shell "/data/local/tmp/busybox chmod 06755 /system/xbin/su"
stuff\adb.exe shell "/data/local/tmp/busybox chmod 655 /system/app/Superuser.apk"
stuff\adb.exe shell "/data/local/tmp/busybox chmod 755 /system/xbin/busybox"
stuff\adb.exe shell "/data/local/tmp/busybox rm /data/local.prop"
stuff\adb.exe shell "/data/local/tmp/busybox reboot"
GOTO FINISH
Note: I'm typing from memory because sadly, I erased my own modified file hope I'm not typing too much stupid things because my memory might play me some tricks. But the general idea is here.
Said differently, I simply added the command "busybox" before "chmod" and "chown" commands.
Don't ask me why but it did work. Actually, I discovered this trick by typing the aformentionned commands one a time and find out that simply chmoding a file did not actually change its properties.
I did not rewritte the entire script, but it might be necessary to add the "busybox" command prior to any other "chmod" or "chown" commands (in the ":RICSTUFF" for instance. My tablet did not require to enter this section so I did not bother modify it).
Hope this trick will help someone. If someone finds out it solves its issue, it might be useful to modify Bin4ry's script in a next version of the tool.
(*) more precisely, my tablet is a Finetech by Akor, model TG166.
Want to try to use this method to root Docomo P-02E but something concern.
If rooting is not success, it must be kept unrooted. But will it brick the phone?
Thank you and regards,
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
The first question I am not sure can be done but if it can I would like to know how. When applying prerooted firmwares in cmw recovery is it possible for it to look on mounted usb storage? I see the usb storage folder but when I click it is always empty so to install new firmware I have to transfer it to the internal sd of the fire tv first.
Secondly there is an option in the adb fire program where it asks if the firmware you want to install is located on a usb storage. Everytime I try to use this feature it can't find the drive or it finds the drive but does not see the firmware I have on it and again I have to transfer it to the unit.
Thanks in advance for the help.
danknasty said:
The first question I am not sure can be done but if it can I would like to know how. When applying prerooted firmwares in cmw recovery is it possible for it to look on mounted usb storage? I see the usb storage folder but when I click it is always empty so to install new firmware I have to transfer it to the internal sd of the fire tv first.
Secondly there is an option in the adb fire program where it asks if the firmware you want to install is located on a usb storage. Everytime I try to use this feature it can't find the drive or it finds the drive but does not see the firmware I have on it and again I have to transfer it to the unit.
Thanks in advance for the help.
Click to expand...
Click to collapse
I'd be interested in knowing more about your issue with adbFire not finding a drive. This is the first report I've seen of that. Regarding firmware installs...From adbFire's Help system:
Install AFTV firmware
Install firmware to AFTV. Upgrade (or downgrade) your AFTV firmware. This works for firmware on a mounted USB drive/stick and for firmware on your PC. When updating firmware from USB storage, adbFire looks on all devices for files with an extension of ".bin" or ".zip" and presents them for your choice.
Installing firmware from a usb stick/drive is nearly twice as fast as installing a firmware file located on your PC or LAN.
Please note that installation of firmware via Amazon's Native Recovery (this method) has been effectively obsoleted with the availibility of ClockworkMod, compiled for the Fire TV by [email protected]
IMPORTANT: Do not attempt to install custom Clockwork Mod firmware via Amazon Native Recovery. It will not work!
Click to expand...
Click to collapse
jocala said:
I'd be interested in knowing more about your issue with adbFire not finding a drive. This is the first report I've seen of that. Regarding firmware installs...From adbFire's Help system:
Click to expand...
Click to collapse
Yes I have tried both .zip and .bin but had no luck. The farthest I have gotten is I mount the drives via adbfirm and it will recognize a drive then tell me there is no firmware on the drive. Could it be the brand of usb stick I am using or does it need to be a powered usb?
danknasty said:
Yes I have tried both .zip and .bin but had no luck. The farthest I have gotten is I mount the drives via adbfirm and it will recognize a drive then tell me there is no firmware on the drive. Could it be the brand of usb stick I am using or does it need to be a powered usb?
Click to expand...
Click to collapse
If the drive is mounted, the linux find command should locate any *.bin or *.zip files, your brand or hub won't have any effect. I'm mainly replying to let you know I've read your post -- I won't have access to my rooted ftv until Monday morning at the earliest. It would also be helpful to see a log captured after you attempt to find firmware on your mounted drive. You should see something in the log like this:
searching usb for files
"./adb" shell su -c find /storage/usb -name *.bin -o -name *.zip
Click to expand...
Click to collapse
Followed by other stuff.
jocala said:
If the drive is mounted, the linux find command should locate any *.bin or *.zip files, your brand or hub won't have any effect. I'm mainly replying to let you know I've read your post -- I won't have access to my rooted ftv until Monday morning at the earliest. It would also be helpful to see a log captured after you attempt to find firmware on your mounted drive. You should see something in the log like this:
Followed by other stuff.
Click to expand...
Click to collapse
How would I go about capturing a log for you. Also just curious about my first question I wasn't sure is it possible to read a mounted usb in the custom recovery menu or must the fire tv be fully booted.
Also.. not sure if this helps but when I mount the usb stick using stick mount on the fire tv it does not give me the error of nothing found but the select firmware menu comes up and this is the only choice I have available "sh: find: not found"
danknasty said:
How would I go about capturing a log for you. Also just curious about my first question I wasn't sure is it possible to read a mounted usb in the custom recovery menu or must the fire tv be fully booted.
Also.. not sure if this helps but when I mount the usb stick using stick mount on the fire tv it does not give me the error of nothing found but the select firmware menu comes up and this is the only choice I have available "sh: find: not found"
Click to expand...
Click to collapse
None of my comments apply when booted to a custom recovery, you need to check with rbox for that.
adbFire logs are found using the File-View Log menu command. The various non-Kodi commands also require my busybox and the various support scripts, aka System Tools; I don't support busybox from other sources. I also ask that you be using the current version of adbFire when seeking support, currently 1.22.
jocala said:
None of my comments apply when booted to a custom recovery, you need to check with rbox for that.
adbFire logs are found using the File-View Log menu command. The various non-Kodi commands also require my busybox and the various support scripts, aka System Tools; I don't support busybox from other sources. I also ask that you be using the current version of adbFire when seeking support, currently 1.22.
Click to expand...
Click to collapse
Ok here is my log I opened it up today and tried to install firmware from usb.
adbFire v1.22
031315120328
Windows
------------
server started
"./adb.exe" start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
starting server
initial open
192.168.0.36
server started
"./adb.exe" start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
connection attempt
"./adb.exe" connect 192.168.0.36:5555
unable to connect to 192.168.0.36:5555:5555
process time duration: 25 seconds
opening preferences dialog
Saving Device Record
updating database adbfire.db
server started
"./adb.exe" start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
connection attempt
"./adb.exe" connect 192.168.0.34:5555
connected to 192.168.0.34:5555
"./adb.exe" shell su -c ps | grep smbd
samba off!
process time duration: 5 seconds
firmware installation query
firmware installation started
"./adb.exe" shell su -c cp /sdcard/command /cache/recovery/
"./adb.exe" shell su -c chmod 777 /cache/recovery/command
searching usb for files
"./adb.exe" shell su -c find /storage/usb -name *.bin -o -name *.zip
sh: find: not found
opening adblog dialog
danknasty said:
"./adb.exe" shell su -c find /storage/usb -name *.bin -o -name *.zip
sh: find: not found
Click to expand...
Click to collapse
The various non-Kodi commands also require my busybox and the various support scripts, aka System Tools; I don't support busybox from other sources.
Click to expand...
Click to collapse
The find command is missing. Install System Tools. This will install busybox as mentioned above, which will give you find.
The Install Firmware command should check for System Tools and warn you if they are missing. That will be fixed in the next update.
jocala said:
The find command is missing. Install System Tools. This will install busybox as mentioned above, which will give you find.
The Install Firmware command should check for System Tools and warn you if they are missing. That will be fixed in the next update.
Click to expand...
Click to collapse
I installed system tools about 3 times as I am on the latest rooted firmware. But I just tried again and now and still no luck this is the log I get now.
opening adblog dialog
starting busybox install
"./adb.exe" push ./busybox /sdcard/
632 KB/s (1356524 bytes in 2.095s)
"./adb.exe" push ./install-recovery-2.sh /sdcard/
8 KB/s (62 bytes in 0.007s)
"./adb.exe" push ./install-recovery.sh /sdcard/
23 KB/s (630 bytes in 0.026s)
"./adb.exe" push ./xbin.tar /sdcard/
795 KB/s (2836480 bytes in 3.480s)
/system mounted rw
"./adb.exe" shell su -c mount -o remount,rw /system
"./adb.exe" shell su -c cp /sdcard/busybox /system/xbin
"./adb.exe" shell su -c chmod 0755 /system/xbin/busybox
"./adb.exe" shell su -c /system/xbin/busybox tar xf /sdcard/xbin.tar -C /system
"./adb.exe" shell su -c chmod 0755 /system/xbin/*.sh
"./adb.exe" shell su -c chmod 0755 /system/xbin/01mntdrives
"./adb.exe" shell su -c chmod 0755 /system/xbin/02sshd
"./adb.exe" shell su -c chmod 0755 /system/xbin/mount.exfat-fuse
"./adb.exe" shell su -c chmod 0755 /system/xbin/ntfs-3g
"./adb.exe" shell su -c /system/xbin/binstall.sh
rm failed for /sdcard/binstall.sh, No such file or directory
rm failed for /sdcard/buninstall.sh, No such file or directory
rm failed for /sdcard/ntfs-3g, No such file or directory
rm failed for /sdcard/mount.exfat-fuse, No such file or directory
rm failed for /sdcard/mntdrives.sh, No such file or directory
mount: Device or resource busy
"./adb.exe" shell ls /system/xbin/which
/system/xbin/which
"./adb.exe" shell su -c rm /sdcard/xbin.tar
"./adb.exe" shell su -c tar xf /sdcard/samba.tar -C /data/data
tar: can't open '/sdcard/samba.tar': No such file or directory
"./adb.exe" shell su -c rm /sdcard/samba.tar
rm failed for /sdcard/samba.tar, No such file or directory
"./adb.exe" shell su -c mkdir /system/etc/init.d
"./adb.exe" shell su -c chmod 777 /system/etc/init.d
"./adb.exe" shell su -c cp /sdcard/install-recovery* /system/etc/
"./adb.exe" shell su -c chmod 0755 /system/etc/install-recovery*
"./adb.exe" shell su -c rm /sdcard/install-recovery*
"./adb.exe" shell su -c cp /system/etc/init.bueller.sh /system/etc/init.bueller.sh.old
"./adb.exe" shell su -c cp /system/xbin/init.bueller.sh /system/etc/
"./adb.exe" shell ls /system/xbin/mntdrives.backup
/system/xbin/mntdrives.backup: No such file or directory
"./adb.exe" shell ls /system/xbin/mntdata.backup
/system/xbin/mntdata.backup: No such file or directory
"./adb.exe" shell ls /system/xbin/mntdata.backup
/system/xbin/mntdata.backup: No such file or directory
busybox installed!
/system mounted ro
"./adb.exe" shell su -c mount -o remount,ro /system
process time duration: 47 seconds
firmware installation query
firmware installation started
"./adb.exe" shell su -c cp /sdcard/command /cache/recovery/
"./adb.exe" shell su -c chmod 777 /cache/recovery/command
searching usb for files
"./adb.exe" shell su -c find /storage/usb -name *.bin -o -name *.zip
no files found
"./adb.exe" shell su -c /system/xbin/mntdrives.sh
USB drive(s) mounted
"./adb.exe" shell su -c /system/xbin/mntdrives.sh
"./adb.exe" shell su -c /data/data/com.funkyfresh.samba/files/samba-rc start
sh: /data/data/com.funkyfresh.samba/files/samba-rc: not found
"./adb.exe" shell su -c ps | grep smbd
samba off!
firmware installation query
firmware installation started
"./adb.exe" shell su -c cp /sdcard/command /cache/recovery/
"./adb.exe" shell su -c chmod 777 /cache/recovery/command
searching usb for files
"./adb.exe" shell su -c find /storage/usb -name *.bin -o -name *.zip
no files found
opening adblog dialog
searching usb for files
"./adb.exe" shell su -c find /storage/usb -name *.bin -o -name *.zip
no files found
Click to expand...
Click to collapse
I just noticed you're not using adbFire to mount your drive; I can't support stickmount, sorry. If you can change your mount location to be under /storage/usb it might work, idk. I know it does work with System Tools installed and adbFire mounting the usb drives.
I used adb Fire to mount my drive originally and it gives me the message that no firmwares are on the drive. Here is a log of me mounting in adb fire succesfully but then it unable to find the file.
"./adb.exe" shell su -c rm -r /storage/usb/*/
usb drive unmounted
"./adb.exe" shell su -c mount -o remount,ro /
/ mounted ro
"./adb.exe" shell su -c mount -o remount,ro /
process time duration: 2 seconds
"./adb.exe" shell su -c /system/xbin/mntdrives.sh
USB drive(s) mounted
"./adb.exe" shell su -c /system/xbin/mntdrives.sh
"./adb.exe" shell su -c /data/data/com.funkyfresh.samba/files/samba-rc start
sh: /data/data/com.funkyfresh.samba/files/samba-rc: not found
"./adb.exe" shell su -c ps | grep smbd
samba off!
firmware installation query
firmware installation started
"./adb.exe" shell su -c cp /sdcard/command /cache/recovery/
"./adb.exe" shell su -c chmod 777 /cache/recovery/command
searching usb for files
"./adb.exe" shell su -c find /storage/usb -name *.bin -o -name *.zip
no files found
opening adblog dialog
danknasty said:
I used adb Fire to mount my drive originally and it gives me the message that no firmwares are on the drive.
Click to expand...
Click to collapse
Sorry, I can't duplicate your error on a clean system, with System Tools installed , multiple drives mounted with firmware sitting on each, just for purposes of testing. All firmwares were found, every time. The find command is pretty straightforward.
You may have some weird edge case I've overlooked in code, but I'd need to see a log from a clean system w/o third-party busybox, mount tools, etc. If we can spotlight a bug, I'd be happy to fix it.
jocala said:
Sorry, I can't duplicate your error on a clean system, with System Tools installed , multiple drives mounted with firmware sitting on each, just for purposes of testing. All firmwares were found, every time. The find command is pretty straightforward.
You may have some weird edge case I've overlooked in code, but I'd need to see a log from a clean system w/o third-party busybox, mount tools, etc. If we can spotlight a bug, I'd be happy to fix it.
Click to expand...
Click to collapse
I tried this when i first unboxed the unit and was unable to get it to read anything could it be the way I have the usb stick formatted or the way the zip file is named?
danknasty said:
I tried this when i first unboxed the unit and was unable to get it to read anything could it be the way I have the usb stick formatted or the way the zip file is named?
Click to expand...
Click to collapse
adbFire drive mount supports vfat,ex-fat,ext2-4,hpfs+ and ntfs. Install Firmware will find files with embedded spaces ,e.g. "test file.zip" or "test file.bin" but not "test file zip" or "test file bin".
jocala said:
adbFire drive mount supports vfat,ex-fat,ext2-4,hpfs+ and ntfs. Install Firmware will find files with embedded spaces ,e.g. "test file.zip" or "test file.bin" but not "test file zip" or "test file bin".
Click to expand...
Click to collapse
my stick is a fat32 and the files is named update.zip so it should work?... The weird thing is it seems to get farther when I mount it using stick mount (it brings up a menu) then it does when I mount in adb fire although I have yet to get either method to work. I am gonna restore one a little later and do everything from adbfire and see if I can get you a log or mabye it will work.
Ok so I started from scratch and I am having the same issue here is the log.. I notice it saying the mount is busy I am not sure what that means.... I also installed es file explorer and I do not see the mounted usb storage anywhere on the sdcard even after it says it has mounted succesfully.
adbFire v1.22
031315181935
Windows
------------
server started
"./adb.exe" start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
starting server
initial open
192.168.0.34
server started
"./adb.exe" start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
connection attempt
"./adb.exe" connect 192.168.0.34:5555
unable to connect to 192.168.0.34:5555:5555
process time duration: 25 seconds
opening preferences dialog
Saving Device Record
updating database adbfire.db
server started
"./adb.exe" start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
connection attempt
"./adb.exe" connect 192.168.0.38:5555
connected to 192.168.0.38:5555
process time duration: 5 seconds
"./adb.exe" install -r ./tr.apk
pkg: /data/local/tmp/tr.apk
Success
573 KB/s (111652 bytes in 0.190s)
"./adb.exe" install -r ./su.apk
pkg: /data/local/tmp/su.apk
Success
558 KB/s (2336291 bytes in 4.082s)
Root software installed.
Run towelroot on the FireTV
to finish rooting process.
process time duration: 25 seconds
opening preferences dialog
Saving Device Record
updating database adbfire.db
Amazon update state toggled
amazon updates
"./adb.exe" shell su -c pm disable com.amazon.dcp
Package com.amazon.dcp new state: disabled
Amazon updates off, com.amazon.dcp disabled
"./adb.exe" shell pm list packages -d
package:com.amazon.dcp
starting busybox install
"./adb.exe" push ./busybox /sdcard/
702 KB/s (1356524 bytes in 1.885s)
"./adb.exe" push ./install-recovery-2.sh /sdcard/
6 KB/s (62 bytes in 0.009s)
"./adb.exe" push ./install-recovery.sh /sdcard/
30 KB/s (630 bytes in 0.020s)
"./adb.exe" push ./xbin.tar /sdcard/
689 KB/s (2836480 bytes in 4.018s)
/system mounted rw
"./adb.exe" shell su -c mount -o remount,rw /system
"./adb.exe" shell su -c cp /sdcard/busybox /system/xbin
"./adb.exe" shell su -c chmod 0755 /system/xbin/busybox
"./adb.exe" shell su -c /system/xbin/busybox tar xf /sdcard/xbin.tar -C /system
"./adb.exe" shell su -c chmod 0755 /system/xbin/*.sh
"./adb.exe" shell su -c chmod 0755 /system/xbin/01mntdrives
"./adb.exe" shell su -c chmod 0755 /system/xbin/02sshd
"./adb.exe" shell su -c chmod 0755 /system/xbin/mount.exfat-fuse
"./adb.exe" shell su -c chmod 0755 /system/xbin/ntfs-3g
"./adb.exe" shell su -c /system/xbin/binstall.sh
rm failed for /sdcard/binstall.sh, No such file or directory
rm failed for /sdcard/buninstall.sh, No such file or directory
rm failed for /sdcard/ntfs-3g, No such file or directory
rm failed for /sdcard/mount.exfat-fuse, No such file or directory
rm failed for /sdcard/mntdrives.sh, No such file or directory
mount: Device or resource busy
"./adb.exe" shell ls /system/xbin/which
/system/xbin/which
"./adb.exe" shell su -c rm /sdcard/xbin.tar
"./adb.exe" shell su -c tar xf /sdcard/samba.tar -C /data/data
tar: can't open '/sdcard/samba.tar': No such file or directory
"./adb.exe" shell su -c rm /sdcard/samba.tar
rm failed for /sdcard/samba.tar, No such file or directory
"./adb.exe" shell su -c mkdir /system/etc/init.d
"./adb.exe" shell su -c chmod 777 /system/etc/init.d
"./adb.exe" shell su -c cp /sdcard/install-recovery* /system/etc/
"./adb.exe" shell su -c chmod 0755 /system/etc/install-recovery*
"./adb.exe" shell su -c rm /sdcard/install-recovery*
"./adb.exe" shell su -c cp /system/etc/init.bueller.sh /system/etc/init.bueller.sh.old
"./adb.exe" shell su -c cp /system/xbin/init.bueller.sh /system/etc/
"./adb.exe" shell ls /system/xbin/mntdrives.backup
/system/xbin/mntdrives.backup: No such file or directory
"./adb.exe" shell ls /system/xbin/mntdata.backup
/system/xbin/mntdata.backup: No such file or directory
"./adb.exe" shell ls /system/xbin/mntdata.backup
/system/xbin/mntdata.backup: No such file or directory
busybox installed!
/system mounted ro
"./adb.exe" shell su -c mount -o remount,ro /system
process time duration: 29 seconds
"./adb.exe" shell su -c /system/xbin/mntdrives.sh
USB drive(s) mounted
"./adb.exe" shell su -c /system/xbin/mntdrives.sh
"./adb.exe" shell su -c /data/data/com.funkyfresh.samba/files/samba-rc start
sh: /data/data/com.funkyfresh.samba/files/samba-rc: not found
"./adb.exe" shell su -c ps | grep smbd
samba off!
stock recovery installation starts
recovery installation started
pushing C:/Users/1/Desktop/adbfw122/adbfw122/stkrecovery/recovery-stock-51.1.0.img to /sdcard/
"./adb.exe" push "C:/Users/1/Desktop/adbfw122/adbfw122/stkrecovery/recovery-stock-51.1.0.img" /sdcard/recovery.img
594 KB/s (10485760 bytes in 17.223s)
"./adb.exe" shell su -c dd if=/sdcard/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
20480+0 records in
20480+0 records out
10485760 bytes transferred in 1.556 secs (6738920 bytes/sec)
"./adb.exe" shell rm /sdcard/recovery.img
process time duration: 29 seconds
firmware installation query
firmware installation started
"./adb.exe" shell su -c chmod 777 /cache/recovery
Unable to open /cache/recovery: No such file or directory
/cache/recovery/ not found
"./adb.exe" shell su -c mkdir -p /cache/recovery/
"./adb.exe" shell su -c chmod 777 /cache/recovery
"./adb.exe" shell su -c cp /sdcard/command /cache/recovery/
"./adb.exe" shell su -c chmod 777 /cache/recovery/command
searching usb for files
"./adb.exe" shell su -c find /storage/usb -name *.bin -o -name *.zip
no files found
opening adblog dialog
Hi,
To Remove Hands Free Activation you should remove Spirint apps in system directory follow by commands below:
Code:
adb shell su -c mount -o rw,remount /system
adb shell
su
cd system
cd priv-app
rm -r SprintAndroidExtension2
rm -r SprintDM
rm -r SprintSetupWizard
rm -r SprintSyncMLPhoneIF
rm -r SprintSyncMLSvc
touch like button if this thread helps you.
Thank you for this!
why i am getting read only file error??
crixus190 said:
why i am getting read only file error??
Click to expand...
Click to collapse
becuase you need root permision
This worked. Thank you!