Develop Bugs

How to root manually/without Windows

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

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

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

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

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

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

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

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

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

Alright thanks cyansmoke! Keep me informed.

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

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

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

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

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

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

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

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

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

Any suggestions?

[Q] Convert ADB to Terminal Emulator code

Hey all,
Just wondering what the conversion code for Terminal Emulator would be in order to perform an ADB code, i have tried to convert the code myself below and want to be sure it is ok.
Basic objective is to copy the file gps.conf from /sdcard/code/ to /system/etc/ directly using Terminal Emulator on my Desire HD (Froyo 2.2 firmware 1.32....)
CMD prompt:
adb push psneuter /data/local/tmp
adb push misc_version /data/local/tmp
adb shell chmod 777 /data/local/tmp/psneuter
adb shell chmod 777 /data/local/tmp/misc_version
adb shell /data/local/tmp/psneuter
adb shell
mount -o remount,rw /dev/block/mmcblk0p25 /system
exit
adb push gps.conf /system/etc/gps.conf
adb shell
mount -o remount,ro /dev/block/mmcblk0p25 /system
exit
TEmu:
chdir /sdcard/code
cp psneuter /data/local/tmp
cp misc_version /data/local/tmp
chmod 777 /data/local/tmp/psneuter
chmod 777 /data/local/tmp/misc_version
chdir /data/local/tmp/psneuter
mount -o remount,rw /dev/block/mmcblk0p25 /system
cp /sdcard/code/gps.conf /system/etc/
mount -o remount,ro /dev/block/mmcblk0p25 /system
NOTE: that when i tried cp psneuter /data/local/tmp or even cp psneuter /sdcard it says cp: permission denied
Cheers

if all you want to do is copy the file...then whats the point of all of that??!!
im guessing that your not rooted, since your doing some code from the downgrade thread that gives temp root.
But the whole point of that code is to get temp root for FW greater than 1.32.
Since you want 1.32, use a program called Visionary+ and click temproot is you want temporary root. (Visionary+ only works till 1.32 FW)
And you wont be able to copy to a file to the system partition if your not in root mode.
So in the terminal, type
>su
first thing, then carry on.
If you get a # instead of the $ then your in root mode, if not (or if a message appears) then you dont have permission to go into root mode(or your not rooted).
---and i dont think theres any point of the chdir command.
::::::::::But if you want to use that code, then it'll work if you type 'su' first.

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

Firstly, Merry Christmas!
Note: This worked on version 10.2.4
I received a Kindle Fire 2 today and since then I've been trying to get it rooted, now that I have I though I'd share it here for other people who might be in the same situation.
This is really just a remixing of the tool made by Bin4ry (http://forum.xda-developers.com/show....php?t=1886460) but I couldn't get the script to run on my Mac...
Step 0 - Preparing
You must enable ADB and Unknown App sources from Settings.
Settings > More > Security > Enable ADB
Settings > More > Device > Allow Installation of Applications
Step 1 is to get that tool from here. and extract it somewhere you'll remember.
Step 2 (you can skip this if you already have the android SDK platform-tools in your PATH)
If you don't have the android SDK or adb installed just add the 'stuff' folder from the tool to your path.
In terminal run
Code:
export PATH=$PATH:/path/to/extracted/tool/stuff/
Step 3 - Push the required files
It's probably easiest if you change into the stuff folder first...
Code:
cd /Users/x/Downloads/Root_with_Restore_by_Bin4ry_v18.7z\ Folder/stuff
Then run the following...
Code:
adb push busybox /data/local/tmp/.
adb push su /data/local/tmp/.
adb push Superuser.apk /data/local/tmp/.
adb push ric /data/local/tmp/ric
Then you need to run an adb shell to set some permissions
Code:
adb shell
(you should get a prompt like [email protected]:/)
Run
Code:
chmod 755 /data/local/tmp/busybox
exit
Step 4 - Rooting
This requires another terminal window. Check that you can run adb from there as well (running adb should print the usage information)
In the first window run:
Code:
adb shell "while ! ln -s /data/local.prop /data/data/com.android.settings/a/file99; do :; done" > /dev/null
In the other run
Code:
adb restore fakebackup.ab
You should get a prompt on your Kindle, hit the restore my data button. As you do so the command in the first window should stop (or a few seconds later - if it doesn't stop it and re-run both commands again.)
You can now close the second window!
Run
Code:
adb reboot
, your Kindle should reboot though the screen will be blinking repeatedly (flashing between the lockscreen and the boot animation) don't worry about that as it will be fixed in a sec.
Step 5 - Cleaning Up
Run
Code:
adb shell
If all was successful you should see the prompt change to [email protected]:/
If it did, continue otherwise go back to step 4.
Run these
Code:
/data/local/tmp/busybox mount -o remount,rw /system
/data/local/tmp/busybox mv /data/local/tmp/su /system/xbin/su
/data/local/tmp/busybox mv /data/local/tmp/ric /system/bin/ric
chmod 755 /system/bin/ric
/data/local/tmp/busybox mv /data/local/tmp/su /system/xbin/su
/data/local/tmp/busybox mv /data/local/tmp/Superuser.apk /system/app/Superuser.apk
/data/local/tmp/busybox cp /data/local/tmp/busybox /system/xbin/busybox
chown 0.0 /system/xbin/su && chmod 06755 /system/xbin/su
chmod 655 /system/app/Superuser.apk
chmod 755 /system/xbin/busybox
rm /data/local.prop
reboot
Your Kindle will restart and SuperSU will be available under Apps, your now free to do as you please, though you could follow with Step 3 on this thread to get Google Apps etc working.
Update: a short guide to installing the Play store can be found here.

This worked almost perfect for me but I couldn't get it to run adb commands from the stuff folder so I dumped its contents (minus the adb stuff) into the platform-tools in the android SDK and from then on everything went great. Thanks so much.

didthis work for 10.2.4 users out there
does this work for 10.2.4

worked!
Great work, congratulations and thanks! I'd like to make some comments tho regarding some typos and suggestions.
1.- I'd suggest to install the android SDK as, in fact, adb commands didn't work from the stuff folder. Add a line to .bash_profile with the export PATH command to make permanent access to the adb shell.
2.- Push files from the Root_with_Restore_by_Bin4ry_v18 folder, not the .7z file.
3.- The command is, e.g., adb push busybox /data/local/tmp/ instead of adb push busybox /data/local/tmp/.
4.- In Step 5 the command /data/local/tmp/busybox mv /data/local/tmp/su /system/xbin/su is twice so you'll get an error the second time you execute it.
Also congratulations for instructions on how to install PlayStore - here pay attention to the names playstore.apk and servicesframework.apk which in fact are plstore3.10.10.apk and GoogleServicesFramework.apk respectively -
Once again thanks for your work.

gorganzolia said:
does this work for 10.2.4
Click to expand...
Click to collapse
Yes this worked for 10.2.4

10.2.6
Does this work with 10.2.6?

it worked
Tried it this morning on 10.2.6 and it worked woohoo now how do you stop it from automatically updating
Found out how to stop those automatic updates here http://forum.xda-developers.com/showthread.php?t=2086450

[Q] Reading usb drive in cmw and in adbfire.

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

[GUIDE] Fix SuperSU on DragonBoard 410c (root)

Ensure you have drivers setup properly and are able to adb shell to your 410c
Install SuperSU 2.46 over adb or "Chainfire SuperSU" from Google Play if you have it installed
Download UPDATE-SuperSU-v2.46.zip and extract it to your microSD card that you use for your 410c
adb root
adb shell
cd /mnt/media_rw/sdcard1/UPDATE-SuperSU-v2.46/
cp ./arm/chattr.pie /data/local/tmp/chattr.pie
chmod 0755 /data/local/tmp/chattr.pie
mount -o rw,remount /system
cp /mnt/media_rw/sdcard1/UPDATE-SuperSU-v2.46/arm64/supolicy /system/xbin/supolicy
chmod 0755 /system/xbin/supolicy
cp /mnt/media_rw/sdcard1/UPDATE-SuperSU-v2.46/arm64/libsupol.so /system/lib64/libsupol.so
chmod 0755 /system/lib64/libsupol.so
cp /mnt/media_rw/sdcard1/UPDATE-SuperSU-v2.46/arm64/su /system/xbin/su
chmod 0755 /system/xbin/su
cp /mnt/media_rw/sdcard1/UPDATE-SuperSU-v2.46/arm64/su /system/xbin/daemonsu
chmod 0755 /system/xbin/daemonsu
/system/xbin/daemonsu –d
Exit but DO NOT restart your 410c yet
On your 410c, open the SuperSU app and select “Normal” to finish the process

I followed through all the steps in your post, but when I opened the SuperSU app in the end, it still shows the message that "There is no SU binary installed, and SuperSU cannot install it...". Do you have any idea what else I could try to fix it? Thanks!!

Root access is granted but once device reboots root access is denied. Also where is “Normal” in SuperSU?