Database Users

Can we flash a new recovery image with the Freash Kitchen?

with the fresh kitchen from flipz?

I dont belive he has the function built in but it really is easy to flash a new recovery all you have to do is put the recovery.img on the root of your sdcard then conect your phone and open a cmd prompt then
Code:
cd
cd /locationofsdkonyourcomp/tools
adb remount
if no errors
Code:
adb shell
cd /sdcard
flash_image recovery nameofrecovery.img
wait till you get the #
Code:
reboot recovery
hope this helps

Yes you go to root and click flash 1.6.2 only.

matthewman3 said:
Yes you go to root and click flash 1.6.2 only.
Click to expand...
Click to collapse
guess I was wrong....been awhile since I touched the kitchen but I guess I do remember something like that from the pre kitchen. sorry for the incorrect info.

wtphoto said:
I dont belive he has the function built in but it really is easy to flash a new recovery all you have to do is put the recovery.img on the root of your sdcard then conect your phone and open a cmd prompt then
Code:
cd
cd /locationofsdkonyourcomp/tools
adb remount
if no errors
Code:
adb shell
cd /sdcard
flash_image recovery nameofrecovery.img
wait till you get the #
Code:
reboot recovery
hope this helps
Click to expand...
Click to collapse
thank you for the fast reply bit i get an error
C:\android-sdk-windows\tools>adb shell
* daemon not running. starting it now *
* daemon started successfully *
/ # adb shell
adb shell
/sbin/sh: adb: not found
/ #
Im lost now

kys89012345 said:
thank you for the fast reply bit i get an error
C:\android-sdk-windows\tools>adb shell
* daemon not running. starting it now *
* daemon started successfully *
/ # adb shell
adb shell
/sbin/sh: adb: not found
/ #
Im lost now
Click to expand...
Click to collapse
Dont run the command from Recovery.. Run the commands with the phone booted up.. And you dont type adb shell twice.. type
adb remount
adb shell

Jus10o said:
Dont run the command from Recovery.. Run the commands with the phone booted up.. And you dont type adb shell twice.. type
adb remount
adb shell
Click to expand...
Click to collapse
when i use adb remount I get
adb remount
adb: not found
# Is there something im missing from the file? Im on windows 7 if that helps

kys89012345 said:
when i use adb remount I get
adb remount
adb: not found
# Is there something im missing from the file? Im on windows 7 if that helps
Click to expand...
Click to collapse
You're gonna need to get the Android SDK. You can get that here. Then, unzip it to the root of your C:\ drive and run the setup inside. You'll get a bunch of folders under windows-android-sdk (I think, that might be mixed up). Rename that folder android for ease.
Open command prompt and type:
Code:
cd c:\android\tools
After you do that, run all the commands stated in the posts above.

OMG THANK YOU It worked I hope this post can help others as well!

Just in case these are the commands I used
Thankx to Jus10o and DevinXtreme
C:\android-sdk-windows>cd c:\android\tools
c:\android\tools> cd C:\android\tools
c:\android\tools>adb remount
* daemon not running. starting it now *
* daemon started successfully *
remount succeeded
c:\android\tools>adb shell
# cd /sdcard
cd /sdcard
# flash_image recovery recovery-RA-heroc-v1.5.2.img
flash_image recovery recovery-RA-heroc-v1.5.2.img
# flash_image recovery recovery-RA-heroc-v1.5.2.img
flash_image recovery recovery-RA-heroc-v1.5.2.img
# reboot recovery
reboot recovery
c:\android\tools>

kys89012345 said:
Just in case these are the commands I used
Thankx to Jus10o and DevinXtreme
C:\android-sdk-windows>cd c:\android\tools
c:\android\tools> cd C:\android\tools
c:\android\tools>adb remount
* daemon not running. starting it now *
* daemon started successfully *
remount succeeded
c:\android\tools>adb shell
# cd /sdcard
cd /sdcard
# flash_image recovery recovery-RA-heroc-v1.5.2.img
flash_image recovery recovery-RA-heroc-v1.5.2.img
# flash_image recovery recovery-RA-heroc-v1.5.2.img
flash_image recovery recovery-RA-heroc-v1.5.2.img
# reboot recovery
reboot recovery
c:\android\tools>
Click to expand...
Click to collapse
I think you might of had a typo??
You cd /android/tools twice and did you flash it twice just in case lol not a big deal just saying
You can also rename "android-sdk-windows" to "android" and then put all of the files that are inside of "android" (thats in your "android-sdk-windows" right now) inside of the renamed "android" (that used to be "android-sdk-windows") .. sorta hard to explain.. but lets say it looks like this now.
c:/android/tools __AND NOT THIS__ c:/android-sdk-windows/android/tools
it will save alot of typing when you need to go to android/tools folder or if you ever need to refer to it in any way

Jus10o said:
You can also rename "android-sdk-windows" to "android" and then put all of the files that are inside of "android" (thats in your "android-sdk-windows" right now) inside of the renamed "android" (that used to be "android-sdk-windows") .. sorta hard to explain.. but lets say it looks like this now.
c:/android/tools __AND NOT THIS__ c:/android-sdk-windows/android/tools
it will save alot of typing when you need to go to android/tools folder or if you ever need to refer to it in any way
Click to expand...
Click to collapse
I'm pretty sure that's what he already did. Ha. I put that in my instructions for him. And his output looks like C:\android\tools

Automated ADB script

Hey all,
I'm trying to create a linux script that executes some adb commands. For example, I would like it to be able to automatically exchange nv_data.bin (which need 'su' rights as you certainly know). The problem begins here:
if I execute command: 'adb shell cp x.x y.y' is fine,
but 'adb shell su cp x.x y.y' is just now working.
So I would need help with this. How can I make it work? I tried adb shell & su and stuff like this, but just did not work... THanks in advance!

94kram01 said:
Hey all,
I'm trying to create a linux script that executes some adb commands. For example, I would like it to be able to automatically exchange nv_data.bin (which need 'su' rights as you certainly know). The problem begins here:
if I execute command: 'adb shell cp x.x y.y' is fine,
but 'adb shell su cp x.x y.y' is just now working.
So I would need help with this. How can I make it work? I tried adb shell & su and stuff like this, but just did not work... THanks in advance!
Click to expand...
Click to collapse
adb shell su -c ls

Thanks! It seems to work, but somehow it just did not ask for permission on the phone, so returns 'Permission denied.' I checked phone, but it didn't ask me if I want to enable or not.

Try
Code:
adb shell su -c "ls" -root

Hm, now it asks for it. Thanks! Is it possible, to ask for permission only once, at the beginning, and then be able to do everything?

94kram01 said:
Hm, now it asks for it. Thanks! Is it possible, to ask for permission only once, at the beginning, and then be able to do everything?
Click to expand...
Click to collapse
I'd think if u call it with -root it should only ask once.
Not sure though.

If it asks more than once, could you push a script to the device (somewhere that normally has full r/w access), run it with a single command, then delete it?

[Q] ADB Remount: Remount failed: Operation not permitted

So I was trying earlier to use ADB while trying to add WIFI to one of the ROMs.. I guess I mistyped something and now it is giving me this error..
How can I fix this? It's not really irking me but sometimes I just want to push a file through ADB and I don't want to keep having this error..
Code:
C:\adt-bundle-windows\sdk\platform-tools>adb remount
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
remount failed: Operation not permitted
C:\adt-bundle-windows\sdk\platform-tools>adb remount
remount failed: Operation not permitted
C:\adt-bundle-windows\sdk\platform-tools>adb devices
List of devices attached
003cf8f9ded1abcc device
C:\adt-bundle-windows\sdk\platform-tools>adb root
adbd cannot run as root in production builds
C:\adt-bundle-windows\sdk\platform-tools>adb remount
remount failed: Operation not permitted
C:\adt-bundle-windows\sdk\platform-tools>adb shell
[email protected]:/ $ su
su
[email protected]:/ # exit
exit
[email protected]:/ $ exit
exit
C:\adt-bundle-windows\sdk\platform-tools>adb root
adbd cannot run as root in production builds
C:\adt-bundle-windows\sdk\platform-tools>adb remount
remount failed: Operation not permitted
C:\adt-bundle-windows\sdk\platform-tools>
For some reason if I delete the whole adt-bundle-windows and extract it again from the .zip file.. It mounts but keeps getting the error
Code:
C:\adt-bundle-windows\sdk\platform-tools>adb remount
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
remount failed: Operation not permitted
I'll be going to sleep soon, so if you need me to do something, I might not get back to you till morning.
Thanks for helping me!

You need an insecure kernel to have root in adb. Or root your phone.

klin1344 said:
You need an insecure kernel to have root in adb. Or root your phone.
Click to expand...
Click to collapse
i'm using franco.kernel - test 5.. and i am rooted? i can use supersu, ti backup, root explorer
Sent from my Nexus 4 using Tapatalk 2

Bump, any help on this?

Bumping this. I am having the same issue. Rooted on the latest stock andriod. Custom kernel as well.

You need an insecure boot.img
Either download the one on this post or enable root over adb if you are running CyanogenMod or AOKP.

Use the set of commands in the sticky.
Doesn't need an insecure kernel.

I've had this happen before. I fixed it by first killing adb with "adb kill-server", then do "adb root" to make adb run as root. Then you can "adb remount" to write to the filesystem, then push away! Hope that helps.

ess.boyer said:
I've had this happen before. I fixed it by first killing adb with "adb kill-server", then do "adb root" to make adb run as root. Then you can "adb remount" to write to the filesystem, then push away! Hope that helps.
Click to expand...
Click to collapse
This worked for me. I was pulling my hair out trying to get the system rw. adb root, did the trick. Make sure you set the phone in to root for adb in Settings/Developer option/Root Access

You are the f'ing man.

What is "adb kill-server".
ess.boyer said:
I've had this happen before. I fixed it by first killing adb with "adb kill-server", then do "adb root" to make adb run as root. Then you can "adb remount" to write to the filesystem, then push away! Hope that helps.
Click to expand...
Click to collapse
@ess.boyer;35057736 , thanks in advance , boss I am new user of android. I use Lenovo A789(ICS 4.0.4, MKT6577 from China) .I have rooted by mobile with SP_Flash_Tool_v3.1222.00 . Now I have remount problem. I want to solve it. What is "adb kill-server" . How can I get"adb kill-server"
and how can I able "adb remount" to write to the filesystem . Please help.

GUYS GUYS
i had this problem with Cyanogen and my kernel is Googy max
ye ADB ROOT command will work. But you can use adbd insecure APP and you don't need adb root command any more

what do i do with the img file??

[Q] Need help pushing a system file with adb

I have bricked my device when I tried to copy framework-res.apk to the system folder. I renamed the old framework-res.apk to framework-res.apk.bak but before I could paste the new one the phone freaked out and rebooted and now I'm stuck at the ATT white screen. I have adb access though so I'm hoping I can just push the framework-res file using adb. Every time I try this though I get an error saying file system is read only. I know all I probably need to do is get the computer to mount system as read/write. I just don't know how to do this. Is there anyone out there who can help me out?

Modified from:
http://forum.xda-developers.com/showthread.php?p=41339365
You may need to do:
mount -o remount,rw /system
chmod 777 /system/framework

Thank you for your quick reply. I'm kind of a novice when it comes to adb so bear with me, but when I use those commands I get 'mount' is not recognized as an internal or external command. I'm not sure if it matters or not but I'm running windows XP and my working directory is in c:\android-sdk\platform-tools when I tried executing "mount -o remount,rw /system".
Okay I tried changing the command to "adb shell mount -o remount,rw /system" now I get the error mount operation not permitted. I hope this doesn't mean I borked it. . . Also want to note that I did root the phone.

jack_slapped said:
Thank you for your quick reply. I'm kind of a novice when it comes to adb so bear with me, but when I use those commands I get 'mount' is not recognized as an internal or external command. I'm not sure if it matters or not but I'm running windows XP and my working directory is in c:\android-sdk\platform-tools when I tried executing "mount -o remount,rw /system".
Click to expand...
Click to collapse
You need to do some reading before you go any further - please. ADB is a command shell, and the commands he gave you are for running IN ADB after it's successfully connected to the phone.
There are lots of good writeups on using ADB all over the place.

jack_slapped said:
Okay I tried changing the command to "adb shell mount -o remount,rw /system" now I get the error mount operation not permitted. I hope this doesn't mean I borked it. . . Also want to note that I did root the phone.
Click to expand...
Click to collapse
You need to get INTO the shell first -- then execute the commands.
Also, always stop the system before modifying stuff, especially framework!
like so:
Code:
> [B]adb shell[/B]
$ [B]su[/B]
# [B]mount -o rw,remount /system[/B]
# [B]stop[/B]
# **[I]cp or mv whatever here[/I]**
# [B]reboot[/B]
your cmd prompt will return after reboot

alacrify said:
You need to do some reading before you go any further - please. ADB is a command shell, and the commands he gave you are for running IN ADB after it's successfully connected to the phone.
There are lots of good writeups on using ADB all over the place.
Click to expand...
Click to collapse
I know believe me when I say I'm trying to read as much as I possibly can. Nobody wants this phone fixed more than me. It's just alot of new stuff and I'm not entirely familiar with it. I think I'm connected with adb and started a shell using "adb -s myserial shell". I input the first command and got "mount: operation not permitted". Not really sure why it would say that considering I rooted the device.

jack_slapped said:
I know believe me when I say I'm trying to read as much as I possibly can. Nobody wants this phone fixed more than me. It's just alot of new stuff and I'm not entirely familiar with it. I think I'm connected with adb and started a shell using "adb -s myserial shell". I input the first command and got "mount: operation not permitted". Not really sure why it would say that considering I rooted the device.
Click to expand...
Click to collapse
Be sure to follow gwbard's directions a little closer. The first command inside the ADB shell is "su" which will elevate you to root - this will be necessary in order to execute the "mount" command.
From your command line (assuming in Windows), you'll run the "adb shell" command that gwbard showed. It should give you a prompt that ends with a dollar sign. Once you execute the "su" command, you'll see that change to a pound/hash sign (#).

gwbard said:
You need to get INTO the shell first -- then execute the commands.
Also, always stop the system before modifying stuff, especially framework!
like so:
Code:
> [B]adb shell[/B]
$ [B]su[/B]
# [B]mount -o rw,remount /system[/B]
# [B]stop[/B]
# **[I]cp or mv whatever here[/I]**
# [B]reboot[/B]
your cmd prompt will return after reboot
Click to expand...
Click to collapse
Dude you are the man! That did the trick. I really appreciate it. I'm still trying to figure out exactly what a shell is and how that ties into adb but I learned a good bit about it from today. I've used linux before and I have heard of a shell but never really understood what exactly it was. Anyways thanks again for everyone who helped me get this working.

Aou said:
Be sure to follow gwbard's directions a little closer. The first command inside the ADB shell is "su" which will elevate you to root - this will be necessary in order to execute the "mount" command.
From your command line (assuming in Windows), you'll run the "adb shell" command that gwbard showed. It should give you a prompt that ends with a dollar sign. Once you execute the "su" command, you'll see that change to a pound/hash sign (#).
Click to expand...
Click to collapse
Yea I posted that last one before I saw his instructions. They were right on point. Thanks guys!

jack_slapped said:
Dude you are the man! That did the trick. I really appreciate it. I'm still trying to figure out exactly what a shell is and how that ties into adb but I learned a good bit about it from today. I've used linux before and I have heard of a shell but never really understood what exactly it was. Anyways thanks again for everyone who helped me get this working.
Click to expand...
Click to collapse
When you click "start" and type "cmd", you're starting a shell. They're command interpreters that extend functionality in specific ways. like "dir" for the Windows/DOS command shell, and "su" or "mount" for adb. Lots of good writeups on that around too

[Q] Help - adb shell permission denied, after Vega Tools problem

I am trying to install a custom ROM to Advent Vega tablet (here in Brazil, sold as Toshiba MyPad). Tried a lot of things, for a long time.
When I try to install CWM, using nvflash or adb, it appears not to work. When I booted into Recovery, very few options appear, only to restore a backup and Wipe data. No option for install zip from sdcard and others I am used to in other devices.
So, I installed Vega Tools 4.1, and tried other ways. One of the tries was an option to install Corvus over Stock ROM.
After running that, my problem got worse. Now, the tablet does not boot anymore. I can yet put it in flash and use adb.
I realized that the script ran by VegaTools did this "amazing" thing:
adb-windows.exe shell /sbin/busybox rm -r /system/* ; /sbin/busybox mkdir -p /system/bin ; /sbin/busybox cp /data/mcr/sh /system/bin/sh
adb-windows.exe shell /sbin/busybox sync
So, it destroyed the /system and the following commands did not work to rebuild it to the new ROM.
Ok, my situation now is:
I copied /system/bin files to the devices using adb push, but now when I try to get into the device via adb shell I receive:
C:\Users\claroedu\Downloads\Software\Android\Toshiba MyPad\windows>adb -s 037c70c141dfc1d7 shell
- exec '/system/bin/sh' failed: Permission denied (13) -
So, I cannot get into the device to fix the permissions, and cannot do anything else.
Another very strange thing: after I ran that trash script, now adb find 2 devices, when threre is only one connected:
C:\Users\claroedu\Downloads\Software\Android\Toshiba MyPad\windows>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
037c70c141dfc1d7 device
emulator-5554 device
Before that, only the emulator one appeared.
Can you guys provide me some help, on how to fix this? Firstly, how could I get into adb shell again, bypassing this "permission denied" error?
I am using adb on windows.
Thanks a lot for any help, in advance.
Eduardo
EDIT: now the things appear to be even worse. Now, the tablet is in an infiite loop. It appears as adb device, and few seconds after, reboots

No one can help me?
eclaro said:
I am trying to install a custom ROM to Advent Vega tablet (here in Brazil, sold as Toshiba MyPad). Tried a lot of things, for a long time.
When I try to install CWM, using nvflash or adb, it appears not to work. When I booted into Recovery, very few options appear, only to restore a backup and Wipe data. No option for install zip from sdcard and others I am used to in other devices.
So, I installed Vega Tools 4.1, and tried other ways. One of the tries was an option to install Corvus over Stock ROM.
After running that, my problem got worse. Now, the tablet does not boot anymore. I can yet put it in flash and use adb.
I realized that the script ran by VegaTools did this "amazing" thing:
adb-windows.exe shell /sbin/busybox rm -r /system/* ; /sbin/busybox mkdir -p /system/bin ; /sbin/busybox cp /data/mcr/sh /system/bin/sh
adb-windows.exe shell /sbin/busybox sync
So, it destroyed the /system and the following commands did not work to rebuild it to the new ROM.
Ok, my situation now is:
I copied /system/bin files to the devices using adb push, but now when I try to get into the device via adb shell I receive:
C:\Users\claroedu\Downloads\Software\Android\Toshiba MyPad\windows>adb -s 037c70c141dfc1d7 shell
- exec '/system/bin/sh' failed: Permission denied (13) -
So, I cannot get into the device to fix the permissions, and cannot do anything else.
Another very strange thing: after I ran that trash script, now adb find 2 devices, when threre is only one connected:
C:\Users\claroedu\Downloads\Software\Android\Toshiba MyPad\windows>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
037c70c141dfc1d7 device
emulator-5554 device
Before that, only the emulator one appeared.
Can you guys provide me some help, on how to fix this? Firstly, how could I get into adb shell again, bypassing this "permission denied" error?
I am using adb on windows.
Thanks a lot for any help, in advance.
Eduardo
EDIT: now the things appear to be even worse. Now, the tablet is in an infiite loop. It appears as adb device, and few seconds after, reboots
Click to expand...
Click to collapse
Please, any help?