Hi all,
i do push files onto sdcard using command in windows
I do the following:
mksdcard -l mySDCard 128M C:\sdcard.img
Addition Emulator Options "-sdcard sdcard.img"
adb push C:\login.jpg /sdcard/pic01.jpg
I have problem. When I try to use "adb push", I have the message
failed to copy 'C:\login.jpg' to '/sdcard/pic01.jpg': Read-only file system
Please tell me how can rectify this error
Thks a lot
Dinesh Subramanian
Maybe the command: adb remount will help?
Hello!
What am I doing wrong?
1. Write "adb logcat".
2. It says "-waiting for device-".
3. I turn on my device.
4. After it have boot-looped like 2 times (this is the error im trying to fix), I press CTRL-C.
And there is no log?
I have also tried "adb logcat > logcat.txt but the logcat.txt is empty. :S
Please help!
"Solved!" .
I read a thread,it's DT for Cypress.
It says:
- run the following command
Code:insmod /system/lib/modules/ax8mt.ko
But I don't know how to run the command.Who can tell me what should I do?
sorry for my bad English and thanks for answering
Gourcuff said:
I read a thread,it's DT for Cypress.
It says:
- run the following command
Code:insmod /system/lib/modules/ax8mt.ko
But I don't know how to run the command.Who can tell me what should I do?
sorry for my bad English and thanks for answering
Click to expand...
Click to collapse
i think it says u run it using dmesg in shell
EDIT:
use command prompt
go to ur adb folder
type in:
adb shell dmseg
and don't forget to write the "su"
_________________________________________
end line -------> correct me if I'm wrong...
thanks for answering and I have solved the problem.
or if you want to be easy
using adb,, on page 3 u can see it
Please help me... I've got a similar problem.
I just enabled multitouch for my x8.
In order to enable it I use these commands at terminal emulator:
su (enter)
insmod /system/lib/modules/ax8mt.ko (enter)
I don't want to make multitouch running on startup (so I haven't changed my hw_config.sh) because of an annoying bug... the screen shuts down after several seconds as if I weren't touching it at all!
Can I create a *.sh file with these commands (su and insmod...) so that I can run it everytime I need to enable multitouch instead of writing them in the terminal?
I created and executed (with root explorer) a *.sh file with these exact lines but it didn't work. What did I do wrong? Should I write it differently in the *.sh file?
For all of you that code apps on PC that use ADB, if you ever wanted to flash a zip file from your app using the recovery it's quite simple. You've seem ROM Manager do it, now why can't you?
Please note that this method can be used in any programming language that has the control to run commands from ADB, Terminal, or the shell itself. I won't be posting any code, but I will be posting the commands needed to do so.
I use ClockWork Recovery on my Android device(Works with AmonRA too). We first need to set the recovery to read commands and not just boot normally.
Using ADB:
Code:
adb shell "echo 'boot-recovery ' > /cache/recovery/command"
Using Terminal/Shell:
Code:
echo 'boot-recovery ' > /cache/recovery/command
Next we need to set our command, Here's a list of commands supported by several recoveries(Open-Source ftw!):
* --send_intent=anystring - write the text out to recovery.intent
* --update_package=path - verify install an OTA package file
* --wipe_data - erase user data (and cache), then reboot
* --wipe_cache - wipe cache (but not user data), then reboot
* --set_encrypted_filesystem=on|off - enables / diasables encrypted fs
Click to expand...
Click to collapse
We'll be using the "update_package" at this time, but feel free to try the others. Now basically the syntax for our "update_package" is "--update_package=PARTITION:NAME.zip", most likely the package will be on the SD Card and for now I'll use the name "update.zip" for the package, so now it looks like "--update_package=SDCARD:update.zip".
Now how do we set/write that command to the recovery?
Using ADB:
Code:
adb shell "echo '--update_package=SDCARD:update.zip' >> /cache/recovery/command"
Using Terminal/Shell:
Code:
echo '--update_package=SDCARD:update.zip' >> /cache/recovery/command
Now that we have set/written the command for the recovery we now lastly reboot into the recovery:
Using ADB:
Code:
adb shell "reboot recovery"
Using Terminal/Shell:
Code:
reboot recovery
If all is done correctly then your device should reboot into the recovery and immediately try to flash the zip file. Any errors will be printed during the process, and if any errors within the recovery should be printed on your device screen.
For those who don't know how to use ADB in coding language, Google it, or here are some simple instructions to do so:
1. Initialize a new process which is the "adb.exe"
2. Send commands to it like a console window
3. Read the output
If you guys need anymore help just ask me
--Simran
Thanks Simran!
this line : echo '--update_package=SDCARD:update.zip' >> /cache/recovery/command works with every flashable zip file?
Nothing?
Is it possible to flash a rom zip folder without using a recovery?
Hello
SimranSingh said:
...
Click to expand...
Click to collapse
Does not work on android 8.1, twrp 3.2
but anyway what's the difference between > and >>?
I hope you are still around to answer
---------- Post added at 02:44 PM ---------- Previous post was at 01:58 PM ----------
chdiryoung said:
Is it possible to flash a rom zip folder without using a recovery?
Click to expand...
Click to collapse
don't think so... I have never seen any way of flashing roms that doesn't involve a recovery like cwm or twrp in some way or another
How to make it reboot once flashing is done?
mathew..denniss said:
How to make it reboot once flashing is
Click to expand...
Click to collapse
Like , from the script itself.
This unbricking method requires that you have adb working and have root access.
First, download the latest system update for your device.
For the 7" HDX, they are posted at
http://www.amazon.com/gp/help/customer/display.html?nodeId=201357190.
For the 8.9" HDX, they are posted at
http://www.amazon.com/gp/help/customer/display.html/ref=hp_left_v4_sib?ie=UTF8&nodeId=201357220.
Now, please note that I DO NOT have a Kindle Fire HDX, so if this doesn't work, let me know and I will remove it immediately.
Try these commands:
Code:
adb shell
su
mount -o rw,remount /cache
mkdir /cache/recovery
echo install /cache/kindleupdate.bin > /cache/recovery/openrecoveryscript
chmod 0777 /cache/recovery/openrecoveryscript
exit
exit
adb push your-downloaded-update.bin /cache/kindleupdate.bin
adb reboot recovery
The only thing that you have to do is replace "your-downloaded-update.bin" with the path to your downloaded update. (To make it easier and avoid typos, I always just drag and drop the file into the terminal/command prompt window.)
Please also note that IT IS OKAY if the command "mkdir /cache/recovery" fails, as long as the error message says file already exists or something along those lines.
If this helped you repair your beloved HDX, feel free to hit that "Thanks" button.
Sent from my Nexus 7 using Tapatalk
r3pwn said:
This unbricking method requires that you have adb working and have root access.
First, download the latest system update for your device.
For the 7" HDX, they are posted at
http://www.amazon.com/gp/help/customer/display.html?nodeId=201357190.
For the 8.9" HDX, they are posted at
http://www.amazon.com/gp/help/customer/display.html/ref=hp_left_v4_sib?ie=UTF8&nodeId=201357220.
Now, please note that I DO NOT have a Kindle Fire HDX, so if this doesn't work, let me know and I will remove it immediately.
Try these commands:
Code:
adb shell
su
mount -o rw,remount /cache
mkdir /cache/recovery
echo install /cache/kindleupdate.bin > /cache/recovery/openrecoveryscript
exit
exit
adb push your-downloaded-update.bin /cache/kindleupdate.bin
adb reboot recovery
The only thing that you have to do is replace "your-downloaded-update.bin" with the path to your downloaded update. (To make it easier and avoid typos, I always just drag and drop the file into the terminal/command prompt window.)
Please also note that IT IS OKAY if the command "mkdir /cache/recovery" fails, as long as the error message says file already exists or something along those lines.
If this helped you repair your beloved HDX, feel free to hit that "Thanks" button.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Nice. Never thought of the simple echo install. Sometimes I think having the device can be a hindrance. You tend to focus on problems, even at the expense of finding solutions. This should be the way EVERYONE with adb access recovers. Really nothing in here that could cause further issue! I like that.
GSLEON3 said:
Nice. Never thought of the simple echo install. Sometimes I think having the device can be a hindrance. You tend to focus on problems, even at the expense of finding solutions. This should be the way EVERYONE with adb access recovers. Really nothing in here that could cause further issue! I like that.
Click to expand...
Click to collapse
Thanks. I thought about adding a wipe system command, but if the download was corrupted, they'd be screwed. So I left it out.
Sent from my Nexus 7 using Tapatalk
I went ahead and added another command to the OP that may/may not help. It couldn't possibly cause any harm, though. Has anyone actually tried and confirmed this to be working?
Sent from my iPod touch using Tapatalk
When I try this, I send adb reboot recovery, the device restarts but says it failed to boot, and gives the options: "reset to factory defaults" or reboot. Is this different than factory reset or is it the same as factory reset. I know we aren't supposed to do a factory reset right?
---------- Post added at 05:17 PM ---------- Previous post was at 04:57 PM ----------
I just realized that it failed to copy the update .bin file. After a long time it said failed to copy file: Permission denied
dcoig1 said:
When I try this, I send adb reboot recovery, the device restarts but says it failed to boot, and gives the options: "reset to factory defaults" or reboot. Is this different than factory reset or is it the same as factory reset. I know we aren't supposed to do a factory reset right?
---------- Post added at 05:17 PM ---------- Previous post was at 04:57 PM ----------
I just realized that it failed to copy the update .bin file. After a long time it said failed to copy file: Permission denied
Click to expand...
Click to collapse
Are you sure you have root?
r3pwn said:
Are you sure you have root?
Click to expand...
Click to collapse
I am sure that the device was rooted before the bootloop condition. I can enter 'adb shell' and then 'su' with no problem from a command prompt. However, I do not think that we are superuser when we use the command 'adb push' from the commandline unless we use 'adb root' first and it won't let me do that. When i enter 'adb root' from the command prompt I get the response: "adbd cannot run as root in production builds"
dcoig1 said:
I am sure that the device was rooted before the bootloop condition. I can enter 'adb shell' and then 'su' with no problem from a command prompt. However, I do not think that we are superuser when we use the command 'adb push' from the commandline unless we use 'adb root' first and it won't let me do that. When i enter 'adb root' from the command prompt I get the response: "adbd cannot run as root in production builds"
Click to expand...
Click to collapse
Hmmmm. Try pushing it to /sdcard and change the path in your echo command to reflect that.
I am guessing that somehow the /cache/kindleupdate.bin is in a secure area that we cannot push to. Is there any area that we can push to? It seems we may have to push somewhere else and then move into the secured area using adb shell with su permission like here:
http://forum.xda-developers.com/showthread.php?t=1687590&page=5
but we don't have an sdcard with our devices.
---------- Post added at 10:35 PM ---------- Previous post was at 10:31 PM ----------
we actually do have an sdcard directory though... i will try to push there
---------- Post added at 10:54 PM ---------- Previous post was at 10:35 PM ----------
so i pushed the update file to the /sdcard/ directory then moved the file to the /cache/ directory, then renamed to kindleupdate.bin . Still does not help the system recovery issue. When I enter 'adb reboot recovery' it brings up a screen which says:
"Kindle Fire System Recovery
Your Kindle doesn't seem to be able to boot.
Reseting your device to Factory defaults may
help you to fix this issue.
Volume up/down to move highlight;
power button to select.
------------------------------------
Reboot your Kindle
Reset to Factory Defaults
-------------------------------------
---------- Post added at 11:48 PM ---------- Previous post was at 10:54 PM ----------
If it makes any difference I am not bricked at the grey kindle logo but the white and orange. It just keeps refreshing the animation over and over... nothing seems to ever happen. What should I normally see when I boot to recovery? An extra option to update or something?
No. What I meant was try pushing it to /sdcard then changing the echo command to reflect that.
so then:
adb shell
su
mount -o rw,remount /cache
mkdir /cache/recovery
echo install /sdcard/kindleupdate.bin > /cache/recovery/openrecoveryscript
exit
exit
adb push your-downloaded-update.bin /sdcard/kindleupdate.bin
adb reboot recovery
dcoig1 said:
so then:
adb shell
su
mount -o rw,remount /cache
mkdir /cache/recovery
echo install /sdcard/kindleupdate.bin > /cache/recovery/openrecoveryscript
exit
exit
adb push your-downloaded-update.bin /sdcard/kindleupdate.bin
adb reboot recovery
Click to expand...
Click to collapse
Yes. Try that.
EDIT: Wait. It'll probably say permission denied or some other lame error, so add
mount -o rw,remount /data
After the cache remount then change everything that references "/sdcard/" to "/data/media/0/".
That didn't work either. I keep getting the same result. I don't get errors using the sdcard directory though either, but I also tried with data/media/0. No errors, just doesn't work for me.
so do i.
adb push "bin" to sdcard can work,but after reboot recovery,
only show on screen like this：
Kindle Fire System Recovery
Your Kindle doesn't seem to be able to boot.
Reseting your device to Factory defaults may
help you to fix this issue.
Volume up/down to move highlight;
power button to select.
------------------------------------
Reboot your Kindle
Reset to Factory Defaults
-------------------------------------
Do not reset to factory defaults
I wanted to mention fastboot works. Read more...
I tried a different approach.
adb shell
su
adb remount
mkdir "/data/media/0/Updates
exit
exit
adb push C:\update-kindle-13.3.2.4_user_324002120.bin "/data/media/0/Updates/update-kindle-13.3.2.4_user_324002120.bin
Faznx92 said:
I wanted to mention fastboot works. Read more...
Click to expand...
Click to collapse
Not really. Not nearly as useful as the KFHD's. No useful commands work.
ChittyChittyGangBang said:
I tried a different approach.
adb shell
su
adb remount
mkdir "/data/media/0/Updates
exit
exit
adb push C:\update-kindle-13.3.2.4_user_324002120.bin "/data/media/0/Updates/update-kindle-13.3.2.4_user_324002120.bin
Click to expand...
Click to collapse
And did this help you unbrick your device?
Unbrick my Kindle
Sorry to interrupt, but my kindle fire HDX 7" is also bricked, I can not get past the gray "Kindle Fire" screen, I can get into fastboot. My device is not detected in ADB. Is there any hope for my kindle or is it dead?
r3pwn said:
Not really. Not nearly as useful as the KFHD's. No useful commands work.
And did this help you unbrick your device?
Click to expand...
Click to collapse
Nope. Ended up wasting half a weekend on it.
I just sent it back and bought a Samsung Galaxy Tab. Now I have GPS and IR in addition to a device that works like a Droid device should.