Oke seeing we kinda lost the possibility to use DDMS for screenshots in recovery on latest HTC Devices.
There had to be another way to do this so after few hours of google and making a few bat tests here it is.
I made a zipp (easy run me bat included) containing all the stuff needed to make screenshots in recovery.
Basically its easy and it makes use of files from this open source project http://code.google.com/p/android-fb2png/ by Kyan He
I did not write fb2png, my little script is just using it to make the shots.
Download screenshot.rar
Extract it and run the screenshot_run_me bat file.
All the bat does is running the following commands
Code:
[COLOR=Black]@[/COLOR]@echo off
cls
echo.
echo ******************************************************
echo * *
echo * ADB-Screenshot from Recovery *
echo * *
echo * Original idea: Kyan He *
echo * code.google.com/p/android-fb2png *
echo * *
echo * Script: Whiskey103 *
echo * forum.xda-developers.com/showthread.php?p=40260716 *
echo * *
echo * Script update: Korbeny *
echo * *
echo * ADB version: 1.0.31 (August 2013) *
echo * *
echo * Instructions: *
echo * - Boot into recovery *
echo * - Plug in USB cable *
echo * When ready press a key to continue *
echo * *
echo ******************************************************
echo.
pause
cls
adb devices
goto option
:option
cls
echo.
echo.
echo.
echo 1.- Make a screenshot
echo 2.- Exit
echo.
set /p choice=Type the number of your choice
if not '%choice%'=='' set choice=%choice:~0,1%
if '%choice%'=='1' goto screenshot
if '%choice%'=='2' goto exit
cls
echo.
echo.
echo.
echo "%choice%" is not a valid option. Please try again
echo.
echo.
pause
goto option
:screenshot
cls
adb shell mount /data
adb push fb2png /data/local/
adb push dump /data/local/
adb shell chmod 755 /data/local/fb2png
adb shell chmod 755 /data/local/dump
adb shell /data/local/dump
adb pull /data/local/ScreenShots
adb shell rm /data/local/fb2png
adb shell rm /data/local/dump
adb shell rm -r /data/local/ScreenShots
echo.
echo.
echo ******************************************************
echo * *
echo * The screenshot was taken successfully *
echo * *
echo ******************************************************
echo.
echo.
adb shell sync
adb shell umount /data
pause
goto option
:exit
cls
echo.
echo.
echo.
echo ******************************************************
echo * *
echo * The screenshots are stored in the ADB folder *
echo * named as Screenshot_date_time.png *
echo * *
echo ******************************************************
echo.
echo.
pause
exit
But its very useful for example TWRP Themers to show their work without the hassle of using a camcorder or other cam.
Or making screenshots in Aroma, posting recovery script errors, Aroma guides etc. etc.
{
"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"
}
Screenshots are now named/tagged with timestamps huge thx to @Patrics83 (RomCleaner author and scripting expert)
Updated script for making multiple screenshots in one cmd session thanks to @korbeny.
Sneakyghost said:
Maybe for future reference: if you want to decipher what settings to use to decode your Fb0, Gimp's file open dialogue is a huge help as it has some sliders to play with values while it displays the changes in realtime. @Behold_this pointed that out to me while i was searching for the right settings to shoot screenies of the older twrp (using rgb565). Later finding out about what RGB8888 means to ffmpeg was a hitch then when TWRP updated to the new pxl format.
See my pains here: DarkViper TWRP Theme (qHD) using this as a little advertiser too, maybe someone wants to grab my theme and port it to your resolution...
Click to expand...
Click to collapse
And here is a few output samples
Disclaimer: Everybody can use my work without asking permission, all my stuff comes with a "sharing is caring" xda philosophy licence... just credits would be nice
Holy macaroni!
Nice work mate! :thumbup::thumbup:
Works perfect on my HTC One X
Sent from my HTC One X
How does this work!? I'm not able to get this to work with my HTC EVO 4G LTE, it says that the fb2png doesn't exist....
Code:
***********************************************
*
* ADB-Screenshot Util
* If in Recovery: Mount System
* Plug In USB Cable
* Enjoy ;)
*
***********************************************
Press any key to continue . . .
push fb2png /data/local/
failed to copy 'fb2png' to '/data/local/': Is a directory
.
shell chmod 755 /data/local/fb2png
chmod: /data/local/fb2png: No such file or directory
.
shell /data/local/fb2png /data/local/fbdump.png
/sbin/sh: /data/local/fb2png: not found
.
pull /data/local/fbdump.png
remote object '/data/local/fbdump.png' does not exist
.
***********************************************
*
* You will find screenshot in adb folder
* named as fbdump.png
*
***********************************************
Press any key to continue . . .
I remember you told me that it works yeeears ago
Not bad
EVOuser94 said:
How does this work!? I'm not able to get this to work with my HTC EVO 4G LTE, it says that the fb2png doesn't exist....
Code:
***********************************************
*
* ADB-Screenshot Util
* If in Recovery: Mount System
* Plug In USB Cable
* Enjoy ;)
*
***********************************************
Press any key to continue . . .
push fb2png /data/local/
failed to copy 'fb2png' to '/data/local/': Is a directory
.
shell chmod 755 /data/local/fb2png
chmod: /data/local/fb2png: No such file or directory
.
shell /data/local/fb2png /data/local/fbdump.png
/sbin/sh: /data/local/fb2png: not found
.
pull /data/local/fbdump.png
remote object '/data/local/fbdump.png' does not exist
.
***********************************************
*
* You will find screenshot in adb folder
* named as fbdump.png
*
***********************************************
Press any key to continue . . .
Click to expand...
Click to collapse
Hum, works for me on One X, can't think of a reason why it wouldn't work on other devices.
You get some specific error?
Sent from my HTC One X using xda premium
I'm going to try a few things then get back at you. them are the only errors that I have as of yet.
Euphorie said:
I remember you told me that it works yeeears ago
Not bad
Click to expand...
Click to collapse
well DDMS from the android sdk worked for ages... just as of late google/htc decided to not support it in custom recovery.
so we got stuck with ugly screenshots of recovery themes.
Or it was a double work thingy.. port your theme into a device that had DDMS support and take shots there
EVOuser94 said:
I'm going to try a few things then get back at you. them are the only errors that I have as of yet.
Click to expand...
Click to collapse
Well I was able to get it to work, but the picture is not working correctly any ideas?
Sent from my EVO using xda premium
EVOuser94 said:
Well I was able to get it to work, but the picture is not working correctly any ideas?
View attachment 1881757
Sent from my EVO using xda premium
Click to expand...
Click to collapse
can you try this version?
https://www.dropbox.com/s/1d5p00y0qp00nh1/fb2png-0.0.2
just rename it into fb2png and replace the old version.
Work great! thank
But,I have manually mounted /data
why you not use command "adb shell mount /data" in your script?
migascalp said:
Work great! thank
But,I have manually mounted /data
why you not use command "adb shell mount /data" in your script?
Click to expand...
Click to collapse
Actually, a good idea tbh.. Didn't think about that..
Sent from my HTC One X using xda premium
I'm getting this with that newer version.
Code:
***********************************************
*
* ADB-Screenshot Util
* If in Recovery: Mount System
* Plug In USB Cable
* Enjoy ;)
*
***********************************************
Press any key to continue . . .
push fb2png /data/local/
2167 KB/s (34628 bytes in 0.015s)
.
shell chmod 755 /data/local/fb2png
.
shell /data/local/fb2png /data/local/fbdump.png
link_image[1891]: 325 could not load needed library 'libutils.so' for '/data/l
ocal/fb2png' (link_image[1891]: 325 could not load needed library 'libcorkscre
w.so' for 'libutils.so' (reloc_library[1306]: 325 cannot locate 'tgkill'...
))CANNOT LINK EXECUTABLE
.
pull /data/local/fbdump.png
remote object '/data/local/fbdump.png' does not exist
.
***********************************************
*
* You will find screenshot in adb folder
* named as fbdump.png
*
***********************************************
Press any key to continue . . .
My mod:
Code:
@echo off
echo ***********************************************
echo *
echo * ADB-Screenshot Util
echo * If in Recovery: Mount System
echo * Plug In USB Cable
echo * Enjoy ;)
echo *
echo ***********************************************
echo.
rem pause
adb shell mount /data
echo push fb2png /data/local/
adb push fb2png /data/local/
echo .
echo shell chmod 755 /data/local/fb2png
adb shell chmod 755 /data/local/fb2png
echo .
echo shell /data/local/fb2png /data/local/fbdump.png
adb shell /data/local/fb2png /data/local/fbdump.png
echo .
echo pull /data/local/fbdump.png
adb pull /data/local/fbdump.png
echo .
echo ***********************************************
echo *
echo * You will find screenshot in adb folder
echo * named as fbdump.png
echo *
echo ***********************************************
echo.
adb shell sync
adb shell umount /data
pause
Work for me
thank you again
Whiskey103 said:
Hum, works for me on One X, can't think of a reason why it wouldn't work on other devices.
You get some specific error?
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Don't work for me on One X！
---------- Post added at 10:25 AM ---------- Previous post was at 10:09 AM ----------
519ljh said:
Don't work for me on One X！
Click to expand...
Click to collapse
push fb2png /data/local/
failed to copy 'fb2png' to '/data/local/': Is a directory
.
shell chmod 755 /data/local/fb2png
chmod: /data/local/fb2png: No such file or directory
.
shell /data/local/fb2png /data/local/fbdump.png
/sbin/sh: /data/local/fb2png: not found
.
pull /data/local/fbdump.png
remote object '/data/local/fbdump.png' does not exist
.
***********************************************
*
* You will find screenshot in adb folder
* named as fbdump.png
*
519ljh said:
Don't work for me on One X！
---------- Post added at 10:25 AM ---------- Previous post was at 10:09 AM ----------
push fb2png /data/local/
failed to copy 'fb2png' to '/data/local/': Is a directory
.
shell chmod 755 /data/local/fb2png
chmod: /data/local/fb2png: No such file or directory
.
shell /data/local/fb2png /data/local/fbdump.png
/sbin/sh: /data/local/fb2png: not found
.
pull /data/local/fbdump.png
remote object '/data/local/fbdump.png' does not exist
.
***********************************************
*
* You will find screenshot in adb folder
* named as fbdump.png
*
Click to expand...
Click to collapse
Try to edit the .bat file to mount the /data first before anything else takes place. Look at the post above yours, he shows how to mount the data
Sent from my EVO using xda premium
EVOuser94 said:
Try to edit the .bat file to mount the /data first before anything else takes place. Look at the post above yours, he shows how to mount the data
Sent from my EVO using xda premium
Click to expand...
Click to collapse
THX !I made it!
Added mount commands in script.
Just redownload the package.
Sent from my HTC One X using xda premium
thanks Whiskey
works perfect
Whiskey any idea what could be going on with the EVO 4G LTE not working with this? I'm still unable to use this
Sent from my EVO using xda premium
EVOuser94 said:
Whiskey any idea what could be going on with the EVO 4G LTE not working with this? I'm still unable to use this
Sent from my EVO using xda premium
Click to expand...
Click to collapse
Well honestly no idea. Only thing i can come up with is that you are using stuff posted in one x section on your EVO 4G LTE
But i think it needs different parameters inside fb2png
Jotha is kinda facing the same on HTC One. Scrambled shots.
But i will try to dig into it, problem is there is not much information on who wrote fb2png so can be difficult to gather more settings/parameters etc.
Sent from my HTC One X using xda premium
Related
Hey folks,
See this link. It reads that it works for any Moto device running Gingerbread.
http://www.droid-life.com/2011/08/25/droid3-1-click-easy-root-already-released/
OK, I succeeded.
My Droid Pro is upgraded from rooted 2.2.1 to 2.3.3.
Follow the standard method may lose the root status next reboot.
I've modified the bat file (Click to root your DROID 3.bat) bellow. (Refer to http://www.psouza4.com/droid3/, Thanks!)
Good luck!
Code:
@echo off
cls
adb kill-server > NUL
COLOR B0
TITLE DROID 3 Easy Root Script
cls
echo ***************************************************************************
echo * *
echo * DROID 3 Easy Root script v7 *
echo * *
echo ***************************************************************************
echo *
echo * Please make sure you meet these pre-requisites:
echo *
echo * (a) install the correct driver
echo * (b) turn on USB debugging (on your phone under Settings -^> Applications)
echo * (c) plug in your phone and set your USB mode to 'charging only'
echo *
echo * Note: your phone will reboot twice during this procedure. This is normal.
echo *
echo * READY TO ROOT YOUR DROID 3 WHEN YOU ARE!
echo *
COLOR E0
pause
echo *
echo * Waiting for your phone to be connected...
echo *
adb wait-for-device > NUL
COLOR B0
echo * Running exploit [part 1 of 3]...
adb kill-server > NUL
adb shell rm /data/local/12m.bak > NUL
adb shell mv /data/local/12m /data/local/12m.bak > NUL
adb shell ln -s /data /data/local/12m
adb reboot
echo *
echo * Rebooting the phone... please wait.
adb kill-server > NUL
COLOR E0
adb wait-for-device > NUL
adb wait-for-device > NUL
COLOR B0
echo *
echo * Running exploit [part 2 of 3]...
adb shell rm /data/local/12m
adb shell mv /data/local/12m.bak /data/local/12m
adb shell rm /data/local.prop.bak > NUL
adb shell mv /data/local.prop /data/local.prop.bak
adb shell echo "ro.sys.atvc_allow_netmon_usb=0" ^> /data/local.prop
adb shell echo "ro.sys.atvc_allow_netmon_ih=0" ^>^> /data/local.prop
adb shell echo "ro.sys.atvc_allow_res_core=0" ^>^> /data/local.prop
adb shell echo "ro.sys.atvc_allow_res_panic=0" ^>^> /data/local.prop
adb shell echo "ro.sys.atvc_allow_all_adb=1" ^>^> /data/local.prop
adb shell echo "ro.sys.atvc_allow_all_core=0" ^>^> /data/local.prop
adb shell echo "ro.sys.atvc_allow_efem=0" ^>^> /data/local.prop
adb shell echo "ro.sys.atvc_allow_bp_log=0" ^>^> /data/local.prop
adb shell echo "ro.sys.atvc_allow_ap_mot_log=0" ^>^> /data/local.prop
adb shell echo "ro.sys.atvc_allow_gki_log=0" ^>^> /data/local.prop
adb reboot
echo *
echo * Rebooting the phone... please wait.
adb kill-server > NUL
COLOR E0
adb wait-for-device > NUL
adb wait-for-device > NUL
COLOR B0
echo *
echo * Running exploit [part 3 of 3]...
[COLOR="Red"]adb shell mount -o remount,rw /dev/block/system /system
adb shell rm /system/bin/su
adb shell rm /system/xbin/su
adb shell rm /system/bin/busybox
adb shell rm /system/xbin/busybox[/COLOR]
adb push busybox /system/xbin/busybox
adb push su /system/xbin/su
adb push Superuser.apk /system/app/Superuser.apk
adb shell chmod 4755 /system/xbin/su
adb shell chmod 755 /system/xbin/busybox
adb shell chown system.system /data
echo *
echo * ALL DONE! YOUR PHONE SHOULD BE ROOTED!
echo *
echo ******************************************************************************
echo.
echo You may now close this window...
echo.
COLOR A0
adb kill-server > NUL
pause
TITLE Command Prompt
COLOR 07
Did you have to do anything different to get it to work? Mine gets stuck on the first reboot and will not doing anything from that point on. The version I have is an .exe file not a bat file
It worked on my 3rd attempt
After reboot I do not have root
Worked just fine for me at the first time.
Maybe something wrong for you.
Try to make a full wipe (save your data first) and then try to root.
Mine gets caught up in the reboot part, screen just stays at the boatloader screen.
Sent from my DROID Pro using XDA App
Thanks, it worked!
I have to say, Gingerbread makes this phone shine.
I finally know how to get this phone working on my Vodafone NL sim. SMS-texting and data, all working.
Only thing not working: sms delivery receipts.
Oh well.
Can anyone help?
Sent from my DROID Pro using XDA App
Script ran without issue, but didn't appear to do anything .
I've also ready Gingerbreak could do the job but did not work either.
Try this, http://hackslurp.com/2011/08/27/how...-3-x2-cliq-on-android-2-3-4-gingerbread-easy/
Worked for me, droid pro on rogers canada(and using a macbook no less!)
lictor4 said:
Try this, http://hackslurp.com/2011/08/27/how...-3-x2-cliq-on-android-2-3-4-gingerbread-easy/
Worked for me, droid pro on rogers canada(and using a macbook no less!)
Click to expand...
Click to collapse
Thanks, but same issue. Script runs no issue but root apps not working. Terminal Emulator or Root Explorer.
Finally got it to work when it says rebooting you need to unplug the USB cable and manually reboot the phone each time. Wait until the phone fully reboots before plugging the USB back in
Sent from my DROID Pro using XDA App
I've done this several times without success. I've unplugged the phone during the reboot each time and waited for it to fully boot up before plugging it in.
What am I missing?
Hey guys,
Finally, HBOOT update for HKCSL CHT 2.17.832.1 PG7610000 becomes available at HTCdev. have unlocked the bootloader by following the official tutorial with success.
Then the nightmare begin once I start rooting...
I have tried almost all sorts of rooting tools (HTC Supertool3, unlockroot, OneClickRoot) in XDA but none of them did work... (Many thanks to the developer though)
I have also tried to follow this link:
http://forum.xda-developers.com/showthread.php?t=1195275
but I got trapped when trying to flash the recovery UI.
Error Message:
Main Version is older!
update fail
Any clues to the problem?
Some information of my machine:
HBOOT-1.09.0099
Software NUmber: 2.17.832.1
Have you enabled USB-Debugging? Go to the DEV section and find the Wildfire S Manager from eoghan2t7 (here's the link) http://forum.xda-developers.com/showthread.php?t=1431969
then it will work.
theq86 said:
Have you enabled USB-Debugging? Go to the DEV section and find the Wildfire S Manager from eoghan2t7 (here's the link) http://forum.xda-developers.com/showthread.php?t=1431969
then it will work.
Click to expand...
Click to collapse
Thanks for the reply!
USB-Debugging???
Do you mean the one you find in Settings -> Applications -> Development -> USB debugging ??
Of course I have enabled it...
Go to http://shortfuse.org, download latest SuperOneClick and paste log here or send me PM with it.
Thanks again for the help!!
The log after running SuperOneClick:
Code:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
adb server is out of date. killing...
* daemon started successfully *
adb server is out of date. killing...
* daemon started successfully *
export PS1=""
$ export PS1=""
getprop ro.build.version.release > /data/local/tmp/output 2>&1
export TEMPRANDOM=75962
export PS1=END:$TEMPRANDOM;cat /data/local/tmp/output
2.3.5
END:75962export PS1=""
getprop ro.product.manufacturer > /data/local/tmp/output 2>&1
export TEMPRANDOM=93231
export PS1=END:$TEMPRANDOM;cat /data/local/tmp/output
HTC
END:93231export PS1=""
getprop ro.product.model > /data/local/tmp/output 2>&1
export TEMPRANDOM=48750
export PS1=END:$TEMPRANDOM;cat /data/local/tmp/output
HTC Wildfire S A510e
END:48750export PS1=""
getprop ro.build.version.incremental > /data/local/tmp/output 2>&1
export TEMPRANDOM=39931
export PS1=END:$TEMPRANDOM;cat /data/local/tmp/output
214145.1
END:39931export PS1=""
ls -l /system/xbin/su > /data/local/tmp/output 2>&1
export TEMPRANDOM=86202
export PS1=END:$TEMPRANDOM;cat /data/local/tmp/output
/system/xbin/su: No such file or directory
END:86202export PS1=""
ls -l /system/bin/su > /data/local/tmp/output 2>&1
export TEMPRANDOM=88072
export PS1=END:$TEMPRANDOM;cat /data/local/tmp/output
/system/bin/su: No such file or directory
END:88072adb server is out of date. killing...
* daemon started successfully *
adb server is out of date. killing...
* daemon started successfully *
export PS1=""
$ export PS1=""
chmod 755 /data/local/tmp/busybox > /data/local/tmp/output 2>&1
export TEMPRANDOM=53388
export PS1=END:$TEMPRANDOM;cat /data/local/tmp/output
END:53388export PS1=""
/data/local/tmp/busybox whoami > /data/local/tmp/output 2>&1
export TEMPRANDOM=42097
export PS1=END:$TEMPRANDOM;cat /data/local/tmp/output
whoami: unknown uid 2000
END:42097export PS1=""
rm /data/local/tmp/boomsh > /data/local/tmp/output 2>&1
export TEMPRANDOM=21168
export PS1=END:$TEMPRANDOM;cat /data/local/tmp/output
END:21168export PS1=""
rm /data/local/tmp/sh > /data/local/tmp/output 2>&1
export TEMPRANDOM=19002
export PS1=END:$TEMPRANDOM;cat /data/local/tmp/output
END:19002adb server is out of date. killing...
* daemon started successfully *
adb server is out of date. killing...
* daemon started successfully *
$ export PS1=""
Try these methods in given order:
0. Quit HTC Sync.
1. Try to root using this: http://forum.xda-developers.com/attachment.php?attachmentid=841876&d=1325678726
Save the log.
2. Try this: (it is the same but with latest adb and dlls) http://www.mediafire.com/?94d4zza2xcw5u5w
Save the log.
3. a) Download CWM recovery: http://download.clockworkmod.com/recoveries/recovery-clockwork-5.0.2.8-marvel.img
b) enter hboot (must be unlocked via HTCDEV), click fastboot.
c) find on your computer file fastboot.exe, copy it to the place where you downloaded the recovery file.
d) run this command: "fastboot.exe flash recovery recovery-clockwork-5.0.2.8-marvel.img"
if failed try "fastboot.exe boot recovery-clockwork-5.0.2.8-marvel.img"
Save logs.
4. (src: http://forum.xda-developers.com/showthread.php?t=1301388)
- Download http://www.mediafire.com/?z2l7n2gxznz6276
- Extract the tools at the root of your computer (example c:\tools)
- Run Windows CMD and move to the tools folder, then execute these commands
Execute:
Code:
adb push zergRush /data/local/zergRush
adb shell
rm /data/local/tmp/boomsh
rm /data/local/tmp/sh
chmod 755 /data/local/zergRush
/data/local/zergRush
Send me looooogs.
Thanks so much for the help, problem fixed!!
I flashed the recovery .img following you step:
rezo said:
...
3. a) Download CWM recovery: http://download.clockworkmod.com/recoveries/recovery-clockwork-5.0.2.8-marvel.img
b) enter hboot (must be unlocked via HTCDEV), click fastboot.
c) find on your computer file fastboot.exe, copy it to the place where you downloaded the recovery file.
d) run this command: "fastboot.exe flash recovery recovery-clockwork-5.0.2.8-marvel.img"
if failed try "fastboot.exe boot recovery-clockwork-5.0.2.8-marvel.img"
Save logs.
.....
Click to expand...
Click to collapse
Then flash in the root script by this:
http://forum.xda-developers.com/showthread.php?t=1195275
It works!! Thank you so much for all your help!!
Hello beautiful people.
Keep in mind that I'm using Ubuntu 13.10 to do this. I'm trying to transfer my own bootanimation.zip to the OUYA but I can't because the system is set as read-only. adb recognizes my OUYA, if I use "adb devices" it shows the device, but I can't do anything else with it besides that. I read online that if I use "adb remount", it would mount as read/write. I tried that and I got "remount failed: Operation not permitted". I also read something about "adb root", I can't remember what exactly I had to do with that, but I got this "adbd cannot run as root in production builds".
If any more information is needed, please do ask for it. Help is appreciated. Thanks.
try something like
Code:
adb shell
su
mount -o remount /system
gianptune said:
try something like
Code:
adb shell
su
mount -o remount /system
Click to expand...
Click to collapse
After I used that, I tried to push the bootanimation.zip to the OUYA with:
Code:
adb push bootanimation.zip system/media/
And I got this:
Code:
[email protected]:/ # adb push bootanimation.zip system/media/
* daemon not running. starting it now on port 5038 *
* daemon started successfully *
error: device not found
1|[email protected]:/ #
It doesn't recognize it...
Hyd- said:
After I used that, I tried to push the bootanimation.zip to the OUYA with:
Code:
adb push bootanimation.zip system/media/
And I got this:
Code:
[email protected]:/ # adb push bootanimation.zip system/media/
* daemon not running. starting it now on port 5038 *
* daemon started successfully *
error: device not found
1|[email protected]:/ #
It doesn't recognize it...
Click to expand...
Click to collapse
Try adb insecure http://forum.xda-developers.com/showthread.php?t=1687590
djden said:
Try adb insecure http://forum.xda-developers.com/showthread.php?t=1687590
Click to expand...
Click to collapse
I think that worked. I installed that, pushed it to the OUYA while on adb shell and got this:
Code:
1319 KB/s (2971409 bytes in 2.199s)
[email protected]:~$
I couldn't see my bootanimation though, the screen was pitch-black until the "OUYA" voice and logo popped out. I suppose it was an error on my end, I'll have to try with another bootanimation and see. Thanks.
Edit: I tried to push another bootanimation but now it won't recognize it again...
Edit 2: It worked again but without adb shell... I downloaded another bootanimation, and got the same results. Odd...
I'm having the same problem. The above commands presumably changed the filesystem to RW, but now when I try to push my file it says:
cannot stat 'OuyaCWMrecovery6.0.3.2flashable.zip': No such file or directory
I've tried everything I can think of. Restarting everything. Using the entire system path. Trying to leave shell and then run the command (which seems to send it back to r-o filesystem)
trying to rename the zip to make sure I'm typing the full thing correctly.
Any help?
Try doing adb shell as as super user and doing chmod 777 to any relevant directories on your Ouya (like /sdcard/ etc).
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