Database Develop

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

Just and FYI

I have a v6 stock phone, no root, no cwm. Thought I would run through the ADB manual method of root to see what happens. I get to this point...
Code:
>adb devices (verifies you are connected)
>adb push rageagainstthecage-arm5.bin /data/local/temp/rage
(if the above command fails due to read-only, type 'adb usb' then 'adb root' to validate root status, then 'adb devices' again to verify connection)
>adb push su /data/local/temp/su
>adb shell chmod 777 /data/local/temp/rage
>adb shell ./data/local/temp/rage
When I try to do the SU because I get the $ I get Permissions denied.
I know that this method does not work but I wanted to see where it fails. It appears that they may have fixed the glitch that allowed the rage exploit to work.
I also tried cubes other way and it failed as well.
Code:
Open ADB shell
Your command prompt should be "$"
Run
kill `busybox pidof adbd`
Re-run ADB shell, your command prompt should change to "#"
Just thought I would toss this out there in case someone wanted to know...

Thanks for the heads up on this good info to know when I get my rev on Saturday
Sent from my SHIFTAO5P using XDA Premium App

Haxcid said:
I have a v6 stock phone, no root, no cwm. Thought I would run through the ADB manual method of root to see what happens. I get to this point...
Just thought I would toss this out there in case someone wanted to know...
Click to expand...
Click to collapse
Mm, I went through that last night, then downgraded to the V4 software as shown by the other post - still, none of it worked for me.

Pull your SDcard out when trying to root after the downgrade. Or format the SD card. It should work then.

Onemsomic's ICS 3.1RC no GPS lock!

I wanted to ask this in the actual thread but 10 post limit...
Anyway,
I can't get any GPS lock on my I9000, Onemsomic's ICS RC3.1, JVU modem.
I tried changing the NetworkLocation.apk by following this post http://forum.xda-developers.com/showthread.php?p=21351809#post21351809
but since I have absolutely no idea how to use ADB I couldn't do the "change mode to 0644" step.
Someone help a noob?
Thanks.

Well, first off, download the *.apk provided in that post and place it on the sdcard.
adb is a command line tool, so you must insert those commands on a terminal emulator (maybe you got one installed, if not, download one from the market, I can recommend "Android Terminal Emulator").
So, open your terminal emulator and go to the directory where you placed your *.apk. this example has been wrote with the *.apk in the sdcard folder:
Code:
su
cd /mnt/sdcard
adb start-server
adb remount
adb push NetworkLocation.apk /system/app/NetworkLocation.apk
adb chmod 0644 /system/app/NetworkLocation.apk
adb reboot
Note: I wrote this example following my common sense, so I'm not completely sure if this will work!
Cheers!

AurosGamma said:
Well, first off, download the *.apk provided in that post and place it on the sdcard.
adb is a command line tool, so you must insert those commands on a terminal emulator (maybe you got one installed, if not, download one from the market, I can recommend "Android Terminal Emulator").
So, open your terminal emulator and go to the directory where you placed your *.apk. this example has been wrote with the *.apk in the sdcard folder:
Code:
su
cd /mnt/sdcard
adb start-server
adb remount
adb push NetworkLocation.apk /system/app/NetworkLocation.apk
adb chmod 0644 /system/app/NetworkLocation.apk
adb reboot
Note: I wrote this example following my common sense, so I'm not completely sure if this will work!
Cheers!
Click to expand...
Click to collapse
I get a "device not found" error after adb remount. What should I do?

hadar.shamir said:
I get a "device not found" error after adb remount. What should I do?
Click to expand...
Click to collapse
Well I have been looking here and there, and I found that adb doesn't work directly on the phone, you must use adb from your pc. So, this is what you should do from now on:
Install Java SDK
Install Android SDK
Turn on "USB Debugging" in your SGS settings
Connect the Device to the PC
And finally, use the following commands (from the PC):
Code:
// Go to the folder where you put the *.apk
cd C:\users\exampleuser\Documents\ // or /home/exampleuser/Documents/ if you're using linux
adb start-server
adb remount
adb push NetworkLocation.apk /system/app/NetworkLocation.apk
adb chmod 0644 /system/app/NetworkLocation.apk
adb reboot
Note:
The text after the double-slash ( // ), must not be written in the console, they are just comments
You need to install the SDK's because there it is where the adb tool (and tools needed by adb) is found, so, good luck!

[Q] change "relocked" to "locked" when putting phone back to stock?

[Q] change "relocked" to "locked" when putting phone back to stock?
I followed this thread but mine says "relocked" and it still says S-OFF. is it possible to get it to say "locked" without going through the whole process of unlocking, rooting, and using revone again?
I'm sending my phone back to get the screen replaced which isn't under warranty, so does it even matter that it says "relocked?"

mcarswell said:
I followed this thread but mine says "relocked" and it still says S-OFF. is it possible to get it to say "locked" without going through the whole process of unlocking, rooting, and using revone again?
I'm sending my phone back to get the screen replaced which isn't under warranty, so does it even matter that it says "relocked?"
Click to expand...
Click to collapse
Use revone -l to change back to "locked"

There is not a way without rerooting for Tue device to day say locked and not relocked BUT you can easily get rid of S-Off. It doesn't take long either...
1.) Reroot.
2.) Download revone to computer.
3.) Navigate Using Command Prompt to where revone file is located on computer and move the Downloaded file to /data/local/tmp using the command "adb push revone /data/local/tmp" without quotations while phone is booted into OS and connected to computer.
3.) Use Command Prompt with phone connected to computer to run these commands or you can use Terminal Emulator app without a computer but will need a computer later on to run RUU again...
3A.) adb shell
3B.) su(SU Will Now Request SU Access For ADB Shell, Grant It)
3C.) cd /data/local/tmp
3D.) chmod 755 revone
4.) Reboot device
5.) Once device is fully booted back up run these commands again while connected to computer
5A.) adb shell
5B.) su(Will Not Need To Request Access Again)
5C.) cd /data/local/tmp
5D.) ./revone -P(If It Tells You "No Need To Reboot" Then Move On To Step 7 And If It Tells You To "Reboot To Continue" Move On To Step 6).
6.) Reboot
7.) Once fully booted back into OS open another command prompt and run these commands with Command Prompt while connected to computer.
7A.) adb shell
7B.) su
7C.) cd /data/local/tmp
7D.) ./revone -s 0 -u(To Be Safe).
7E.) Reboot
8.) Once again open another command prompt window and run these commands
8A.) adb shell
8B.) su
8C.) cd /data/local/tmp
8D.) ./revone -t -l
9.) Reboot
10.) Run RUU And Allow It To Successfully Complete.
11.) Once booted back into OS open command prompt and type in the final two commands
11A.) adb reboot bootloader
12.) Once it boots into bootloader and recognizes device type in this command
12A.) fastboot oem writesecureflag e
Sent from my HTCONE using Tapatalk 4

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.