Related
Hi all, this thread was for the G1, will this work for the Desire also?
To "install" this, just adb push the two files in the zip below onto your phone with:
Code:
adb shell mount -o remount,rw /system
adb push zipalign /system/bin
adb push zipalign_apks /system/sd/zipalign_apks.sh
adb shell chmod 755 /system/bin/zipalign /system/sd/zipalign_apks.sh
adb shell mount -o remount,ro /system
Then anytime you want to run the script just do:
Code:
adb shell sh /system/sd/zipalign_apks.sh
Or in terminal:
Code:
su
sh /system/sd/zipalign_apks.sh
http://forum.xda-developers.com/attachment.php?attachmentid=253174&d=1259952938
Is there a clockwork3 in an update.zip? When I do it manually, the screen locks on the Samsung screen.
I used oden with d18 and d28. Also do the CM7 nightlies work as well as they do on the evo!
Thanks so much.
Sent from my PC36100 using XDA App
Sent from my PC36100 using XDA App
Do you have root and a terminal app?
Yes sir
Sent from my PC36100 using XDA App
The first thing you need is the OneClickRootCWM3.zip. You need a few files out of it.
Below is a copy of the code from the run.bat that does all the clockwork stuff. We're going to be translating this into something you can do without a computer.
Code:
:Redirector
echo Installing clockworkmod redirector
adb push recovery /system/bin/recovery
adb push recoveryfiles /system/bin/recoveryfiles/
adb push recoveryres /system/bin/recoveryres/
adb shell busybox chmod -R 0755 /system/bin/recoveryfiles/*
adb shell busybox chmod -R 0755 /system/bin/recoveryres/*
adb shell chmod 0755 /system/bin/recovery
adb shell sync
goto:Clockwork
:Clockwork
echo Installing clockworkmod recovery...
adb push redbend_ua /data/local
adb shell chmod 755 /data/local/redbend_ua
adb push zImage /data/local/tmp/zImage
adb shell /data/local/redbend_ua restore /data/local/tmp/zImage /dev/block/bml8
If you paid attention to the code, you probably noticed which files we want. They are:
recovery
recoveryfiles/* (the whole folder)
recoveryres/* (the whole folder again)
redbend_ua
zImage
Put these files somewhere easy to find on your sdcard, such as a folder named cwm.
Now, open a terminal on your phone. We'll start with the redirect, just like the one-click does. If you put the files in a folder called cwm, then enter the lines below one at a time into the terminal.
Code:
remount rw
cp /sdcard/cwm/recovery /system/bin/
cp /sdcard/cwm/recoveryfiles /system/bin/
cp /sdcard/cwm/recoveryres /system/bin/
##Then you *may* have to copy the subfolder in recovery res by doing the following
cp /sdcard/cwm/recoveryres/* cp/system/bin/recoveryres/
busybox
chmod -R 0755 /system/bin/recoveryfiles/*
chmod -R 0755 /system/bin/recoveryres/*
exit (to exit busybox and drop back to toolbox)
chmod 0775 /system/bin/recovery
sync
I don't remember for sure, but your phone may reboot now. If it does, then enter "remount rw" again so that you have write access to the system. Now to finish installing cwm.
Code:
cp /sdcard/cwm/redbend_ua /data/local/
chmod 755 /data/local/redbend_ua
cp /sdcard/cwm/zImage /data/local/tmp/zImage
/data/local/redbend_ua restore /data/local/tmp/zImage /dev/block/bml8
That last line calls redbend_ua with the "restore" flag and puts "/data/local/tmp/zImage" into the place where the recovery belongs, or "/dev/block/bml8" The phone should reboot now and you will have your new recovery.
Then if you want to clean up the left over stuff
Code:
rm /data/local/redbend_ua
rm /data/local/tmp/zImage
Have fun.
Is there a simple, non-CWM flashing one-click root for stock EB13 Epics (I just want to tether to my rooted nook)?
I ask because a few months back I rooted my DI18 Epic with a "One Click Root" and, for some reason, all my apps became unlinked from the android market, and nothing I did worked to restore their connections. After a few hours of panic, I unrooted using the accompanying "One Click Unrooter," and the problem went away.
Then, I noticed my bluetooth was't working. I took it to the Sprint store, they ordered me a replacement phone, and then wouldn't exchange it because CWM was on my current phone. I got them to exchange it eventually, but I felt like a complete dumbass for not knowing it didn't come off in the one-click-unrooting process.
So, is there a way to just get root? And then is there a simple way to get rid of it (uninstall SU and such as well) in case I have to exchange the hardware?
I've read a lot of stuff about flashing stock with Odin, but all the dl links for Odin are 404'd, and I'd rather not have to go back to fresh stock every time I need to take my phone in. What's your advice?
SuperOneClick v1.7 worked for me.
Trickee360 said:
Is there a simple, non-CWM flashing one-click root for stock EB13 Epics (I just want to tether to my rooted nook)?
Click to expand...
Click to collapse
I don't know about "one-click", z4root might work, but there's anecdotal reports of it not working on Android 2.2.1. The one-click w/CWM redirector is the easiest way to root and definitely recommended if you want to do anything more advanced (ROMs, etc.). You can always return to stock everything with Odin.
That said, if all you want is root and nothing more, the manual version is relatively simple. It's really just three steps:
Use an exploit (rageagainstthecage-arm5.bin) to get "temporary root" (an ADB root shell).
Install Superuser's su binary to /system/xbin with the appropriate permissions (root.shell 4755).
Sideload Superuser.apk as a regular program, or download it from the market.
In which case "unrooting" is trivial. Just delete /system/xbin/su with root-explorer or something, and after remove Superuser via "Manage applications".
A while back I wrote up semi-detailed directions for doing this. They should work on EB13 with some modification. Here's some notes for EB13:
"rageagainstthecage-arm5.bin", "su", and "Superuser.apk" are all included in the one click package, that's the easiest place to get them.
Actually running "rageagainstthecage-arm5.bin" is the trickest part. There's a few ways to do it, and due to the nature of the exploit, sometimes only one or two of them will work for anyone. You can tell it works if on the next run of "adb shell" you get a "#" prompt instead of "$". Try these three ways in order until one of them works:
Code:
adb push rageagainstthecage-arm5.bin /data/local/tmp
adb shell chmod 755 /data/local/tmp/rageagainstthecage-arm5.bin
adb shell /data/local/tmp/rageagainstthecage-arm5.bin
Code:
adb push rageagainstthecage-arm5.bin /data/local/tmp
adb shell chmod 755 /data/local/tmp/rageagainstthecage-arm5.bin
adb shell (press return, and type below at the "$" prompt):
/data/local/tmp/rageagainstthecage-arm5.bin
Code:
adb push rageagainstthecage-arm5.bin /data/local/tmp
adb push root.sh /data/local/tmp
adb shell chmod 755 /data/local/tmp/rageagainstthecage-arm5.bin
adb shell chmod 755 /data/local/tmp/root.sh
adb shell /data/local/tmp/root.sh
With the last method's root.sh from the one-click package.
Once you have root, and have verified such by getting a "#" prompt with "adb shell", then run:
Code:
adb shell rm /data/local/tmp/rageagainstthecage-arm5.bin
adb shell rm /data/local/tmp/root.sh
adb shell mount -wo remount /dev/block/stl9 /system
adb push su /system/xbin
adb shell chmod 4755 /system/xbin/su
adb shell mount -ro remount /dev/block/stl9 /system
adb install Superuser.apk
If you do nothing more, OTA updates should apply just fine. The only caveat is that /system/xbin/su will lose the appropraite permissions, so Superuser will no longer work. To restore it, do the same steps above to regain "temporary root", then run:
Code:
adb shell rm /data/local/tmp/rageagainstthecage-arm5.bin
adb shell rm /data/local/tmp/root.sh
adb shell mount -wo remount /dev/block/stl9 /system
adb shell chmod 4755 /system/xbin/su
adb shell mount -ro remount /dev/block/stl9 /system
You shouldn't have to push a new "su" binary since it's already there, and similarly, you don't need to reinstall Superuser.
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?
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