[SOLVED]userinit.sh adb error - G1 Q&A, Help & Troubleshooting

I have ADB installed on my g1 and i also have it partitioned with fat32 and ext2.
When i go to do the "adb push c:\userinit\userinit.sh /system/sd" from this tutorial and i get an error saying "/system/bin/sh: adb: not found"

shockaj said:
I have ADB installed on my g1 and i also have it partitioned with fat32 and ext2.
When i go to do the "adb push c:\userinit\userinit.sh /system/sd" from this tutorial and i get an error saying "/system/bin/sh: adb: not found"
Click to expand...
Click to collapse
are you running that command with terminal or cmd?
Make sure you didn't type adb shell before that command, if you did, you need to type exit, then type that command.

Thank you very much you helped solved my problem, i had typed adb shell in prior to typing in adb push! thank you

Related

(SOLVED)ext3 partition backup through terminal

is this possible?
if so what is the commands I need to use?
i tried using adb:
adb pull /system/sd/ %CD%\sdbackup
but i just get adb:not found
please help!
adb
You cant use adb in terminal. Once you are in terminal you have to throw linux commands not adb. If you have sdk and adb set up on your machine then you can connect the phone and enable debugging, then open up cmd from windows, and then adb remount and throw those add commands.
Theres alot of threads that can show you how to do it.
so i have to adb remount then the pull command??
when using adb I get the #
i type \ls and i get a list of things
but when i type adb or any command with adb i just get
adb: not found
please help

OK I give up. I Need Help PLEASE

I'm at the end of my rope here. I can't get my phone to do a complete wipe. Every time i've tried I get this:
--wiping data...
formatting DATA:...
formatting CACHE:...
formatting SDEXT:...
E:Can't mount /dev/block/mmcblk0
p2
(Invalid Argument)
Error mounting /sd-ext/!
Skipping format...
Data wipe complete.
I've been stuck in a boot loop since like 3am. Please if you can help me, I'm all ears. Right now my phone is useless, and i'm starting to get worried. Thank you in advance
What recovery are you running? It looks like it's erroring out when it attempts to wipe your EXT partition. If you backup the files on your SD and re-partition it, that'll clear anything from EXT.
illogic6 said:
What recovery are you running? It looks like it's erroring out when it attempts to wipe your EXT partition. If you backup the files on your SD and re-partition it, that'll clear anything from EXT.
Click to expand...
Click to collapse
Therein lies the problem tho. I running clockwork 2.0.3.?. I have everything backed up from the fat32 partition, but ext doesn't even show up when i mount my sd card to PC. You don't by any chance have a step by step explanation do you?
ksharp5580 said:
Therein lies the problem tho. I running clockwork 2.0.3.?. I have everything backed up from the fat32 partition, but ext doesn't even show up when i mount my sd card to PC. You don't by any chance have a step by step explanation do you?
Click to expand...
Click to collapse
Can you get to the adb shell? If so, you can run 'sdparted'. Maybe that'll cure the bootloop.
I would strongly suggest flashing an amonra recovery once you have this resolved.
illogic6 said:
Can you get to the adb shell? If so, you can run 'sdparted'.
Click to expand...
Click to collapse
do i just open a cmd prompt and type adb shell?
ksharp5580 said:
do i just open a cmd prompt and type adb shell?
Click to expand...
Click to collapse
If you have the android sdk installed properly, yes. You may have to CD to the tools subdirectory if your path isn't setup. For example ADB is contained in this directory on my computer: C:\android-sdk-windows\tools
You should run 'adb shell' then 'sdparted'. That should walk you through the SD partition process.
illogic6 said:
If you have the android sdk installed properly, yes. You may have to CD to the tools subdirectory if your path isn't setup. For example ADB is contained in this directory on my computer: C:\android-sdk-windows\tools
You should run 'adb shell' then 'sdparted'. That should walk you through the SD partition process.
Click to expand...
Click to collapse
This is where i'm at now. Anything familiar?
C:\android-sdk-windows\tools>adb devices
adb server is out of date. Killing...
* daemon started successfully *
List of devices attached
HT9BGHF04735 recovery
C:\android-sdk-windows\tools>adb shell
~ # sdparted
sdparted
/sbin/sh: sdparted: not found
~ #
ksharp5580 said:
This is where i'm at now. Anything familiar?
C:\android-sdk-windows\tools>adb devices
adb server is out of date. Killing...
* daemon started successfully *
List of devices attached
HT9BGHF04735 recovery
C:\android-sdk-windows\tools>adb shell
~ # sdparted
sdparted
/sbin/sh: sdparted: not found
~ #
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=543985
"to run from computer:
1. download sdparted.txt below to computer
2. connect g1 via usb
3. boot into cm-recovery-v1.4, goto console(alt-x)
4. at your windows cmd prompt type: adb push /path-to/sdparted.txt /sbin/sdparted
5. then type: adb shell chmod 755 /sbin/sdparted
6. to run type adb shell and hit enter.
7. you can now run script"
illogic6 said:
http://forum.xda-developers.com/showthread.php?t=543985
"to run from computer:
1. download sdparted.txt below to computer
2. connect g1 via usb
3. boot into cm-recovery-v1.4, goto console(alt-x)
4. at your windows cmd prompt type: adb push /path-to/sdparted.txt /sbin/sdparted
5. then type: adb shell chmod 755 /sbin/sdparted
6. to run type adb shell and hit enter.
7. you can now run script"
Click to expand...
Click to collapse
Awesome. thanks man. Hope this works
yeah it's your recovery. Install amon_ra 1.6.2 or godspeed recovery if you're not running DD 2.7, or if you're on DD 2.7 install the 1.7.0 recovery from the first page.

Having trouble flashing a new recovery image....

Hi everyone,
I'm using a mac, trying to flash a new recovery image, more specifically the darchstar/godspeed recovery image: http://forum.xda-developers.com/showthread.php?t=672324
I've got the recovery image on the SD Card (not in any folders...right on the top level)
When I issue the flash_image recovery /sdcard/Darchstar-OC-recovery-r2.img command, it's not doing anything.
I've tried issuing it from Terminal on my mac, and using a the android terminal application.
Thanks in advance for any help!
do it with terminal emulator on the actual phone. That's what I usually do
su
flash_image recovery /sdcard/XXXXX.img
adb shell
#flash-blah blah blah.
I am trying to do this as well and when i type su into the command line it tells me permission denied. What am I doing wrong?
silentpanda said:
I am trying to do this as well and when i type su into the command line it tells me permission denied. What am I doing wrong?
Click to expand...
Click to collapse
On terminal emulator your forgetting to type su doing so will give terminal emulator root access. SuperUser Permissions will pop up and ask if its ok click allow.
Try..
Adb remount
adb shell
cd /sdcard
flash_image recovery Darchstar-OC-recovery-r2.img

[Q] ADB permission denied

Hi,
my ADB doesn't work correctly. I plug the phone into the pc with USB Debugging enabled (stock V20m 2.3.4) and run adb.
I can type su and the phone shows shell was given su rights, so the connection must be ok.
But I can't give any command. When I type in adb remount it says permission denied. The same problem with any other command like adb pull /system/app/Camera.apk
Everytime comes permission denied.
What can I do? Please help me.
You're running a kernel which doesn't enable the adb remount option (or rather default.prop in the ramdisk doesn't). To get around it:
Code:
adb shell
su
mount -o remount,rw /dev/block/mmcblk0p1 /system
...this basically does the same thing. There may be something else wrong though, as pulling an app from /system/app should work without it.
EDIT: Make sure you're not in the adb shell when running adb commands. Pull and push commands for example must be run in the computer-shell, not the adb shell.
Thank you very much!
TrymHansen said:
EDIT: Make sure you're not in the adb shell when running adb commands. Pull and push commands for example must be run in the computer-shell, not the adb shell.
Click to expand...
Click to collapse
That was the solution for the problem with pull/push files.

Unable to use ADB Push on 3t

I'm unable to use the adb push command on my rooted OnePlus 3t running OOS 4.0.2. My device shows up after typing adb shell and im also able to execute 'su' command but after that if i try adb push <source> <destination> it returns the following
OnePlus3T:/ $ su
OnePlus3T:/ # adb push 1Carbon /sdcard/
sush: adb: not found
127|OnePlus3T:/ #
I've already downloaded the latest platform-tools and drivers.
is there any solution for this? Thanks in advance!
UTK18 said:
I'm unable to use the adb push command on my rooted OnePlus 3t running OOS 4.0.2. My device shows up after typing adb shell and im also able to execute 'su' command but after that if i try adb push <source> <destination> it returns the following
OnePlus3T:/ $ su
OnePlus3T:/ # adb push 1Carbon /sdcard/
sush: adb: not found
127|OnePlus3T:/ #
I've already downloaded the latest platform-tools and drivers.
is there any solution for this? Thanks in advance!
Click to expand...
Click to collapse
You don't do adb shell,that means your running this command from your phone's terminal which isn't what your trying to do.sp instead of adb shell just do the ADB push command
HeXDeMoN said:
You don't do adb shell,that means your running this command from your phone's terminal which isn't what your trying to do.sp instead of adb shell just do the ADB push command
Click to expand...
Click to collapse
Ohh such a beginners mistake there xD Also, im trying to push some pics via adb so that their timestamp is preserved and it requires me to run adb as root. i now tried adb root and then the push command which worked but timestamps were still altered. what am i doing wrong now?
Anyone?
Bump.

Categories

Resources