Database Develop

[Help] Pulling apk's from phone to computer.

I am trying to pull the Sprint_Core.apk out of Damage's 2.5 rom and try to mate it with this 1.0 rom.
But every time I try and pull it it will simply give me the adb options, or will say no such file. Here's what I'm doing:
adb remount
adb pull system/app/Sprint_Core.apk C:\My Documents
I have also tried, making /system writeable but still no avail.
Can someone direct me to how I'm commanding this wrong?
Thanks!

adb remount
adb shell
cd system/app/
rm Sprint_Core.apk

Tipharet said:
adb remount
adb shell
cd system/app/
rm Sprint_Core.apk
Click to expand...
Click to collapse
That would remove Sprint_Core from the phone & I think is just trying to get a copy of the Sprint_Core from DM2.5 to use with another ROM...

stephen240 said:
I am trying to pull the Sprint_Core.apk out of Damage's 2.5 rom and try to mate it with this 1.0 rom.
But every time I try and pull it it will simply give me the adb options, or will say no such file. Here's what I'm doing:
adb remount
adb pull system/app/Sprint_Core.apk C:\My Documents
I have also tried, making /system writeable but still no avail.
Can someone direct me to how I'm commanding this wrong?
Thanks!
Click to expand...
Click to collapse
See if this works:
adb pull /system/app/Sprint_Core.apk "c:\my documents\"
Make sure "My Documents" exists in your c:\ drive.

Try this
adb pull system/app/Sprint_Core.apk C:\Sprint_Core.apk
no remount needed it will put right on your c drive dont do that rm stuff unless your tryin to remove it oh wait according to my adb cheat sheet that actually wouldnt do anything without adb shell in there

thatguythatdid said:
Try this
adb pull system/app/Sprint_Core.apk C:\Sprint_Core.apk
no remount needed it will put right on your c drive dont do that rm stuff unless your tryin to remove it oh wait according to my adb cheat sheet that actually wouldnt do anything without adb shell in there
Click to expand...
Click to collapse
Ah, I understand now. Thanks this worked! Kudos to you!

gu1dry said:
That would remove Sprint_Core from the phone & I think is just trying to get a copy of the Sprint_Core from DM2.5 to use with another ROM...
Click to expand...
Click to collapse
He can then just extract the file from the update zip.

adb commands nexus one-read only error

I have been trying for some time now,pushing files via adb commands onto nexus one but keep getting cannot copy file read only file error.I am fully rooted and unlocked.I have also reinstalled the android sdk but always get the same error when I push the image file.has anyone experienced this with their phone. I have a feeling its something to do with the SD card but can't be sure.any help would be appreciated. Thanks.
I know you must be thinking "Jedi"how can he can he call himself an androidjedi when he can't sort this simple problem (to some of you),but I must say even a Jedi needs to learn!

try adb remount before your command

Dunno if this will help but have tried changing the system to rw then try to push

Tried that no cigar

are you trying to push it into your sdcard or the phone system??
and remember the whole folder name has to be in the push so it woul have to look like
C:\Users\Android>ad push "C:\Users\Android\Downloads\Android\Nexus 1\Phone.apk" /sdcard/files
has to have full path of where you are pushing it from/too.. i have mine sdk setup to use adb in any directory as well why you dont see it in the sdk directory

@ilostchild
Thanks i will try that later today and let you know
As for pushing the file - i am trying to push it to the sd card - but i am not really sure as i am following instructions in the [HOW-TO] Revert HBOOT 0.35.0017 to 0.33.0012 thread in the forum
as i need to downgrade my Hboot from #17 to 12
are the commands different for pushing a file to the phone?

the more i think about i think i need to flash the file to the phone - but i will try your adb command format of specifying the location of the file in the comp

androidjedi said:
the more i think about i think i need to flash the file to the phone - but i will try your adb command format of specifying the location of the file in the comp
Click to expand...
Click to collapse
Ooo you want to push to sdcard.. ok then yea, you would type it like this
C:\android-sdk-windows\tools> adb push C:\Users\Android\Downloads\Android\signed-passion-FRF50-from-
ERE27.1e519a24.zip /sdcard*
if you dont have the option to use adb in any directory, then you have to be in the android sdk directory and in tools
cd android-sd-windows
cd tools
adb push(drag the file you want to push in the command prompt window) /sdcard*
sorry i know its detailed and im sure you know all these things.. but it kinda gets the questions out of the way for future problems to come

ilostchild said:
Ooo you want to push to sdcard.. ok then yea, you would type it like this
C:\android-sdk-windows\tools> adb push C:\Users\Android\Downloads\Android\signed-passion-FRF50-from-
ERE27.1e519a24.zip /sdcard*
if you dont have the option to use adb in any directory, then you have to be in the android sdk directory and in tools
cd android-sd-windows
cd tools
adb push(drag the file you want to push in the command prompt window) /sdcard*
sorry i know its detailed and im sure you know all these things.. but it kinda gets the questions out of the way for future problems to come
Click to expand...
Click to collapse
thanks for spending time on this-i am new to the android world so any help is welcome-however detailed or not
thanks will try that

ilostchild said:
Dunno if this will help but have tried changing the system to rw then try to push
Click to expand...
Click to collapse
how do i change the system to read write as i am still getting cannot copy file read only file error

androidjedi said:
how do i change the system to read write as i am still getting cannot copy file read only file error
Click to expand...
Click to collapse
do adb shell
su
Mount -o remount,rw /dev/block/mtdblock3 /system
then exit and exit
then do push

ilostchild said:
do adb shell
su
Mount -o remount,rw /dev/block/mtdblock3 /system
then exit and exit
then do push
Click to expand...
Click to collapse
tried that did the push and all i got was 950 KB/s <0 bytes in 76044.000s>
looks like its not pushing the file not sure what to do now

androidjedi said:
tried that did the push and all i got was 950 KB/s <0 bytes in 76044.000s>
looks like its not pushing the file not sure what to do now
Click to expand...
Click to collapse
Umm if you got that mesage you may have pushed it in right..

ilostchild said:
Umm if you got that mesage you may have pushed it in right..
Click to expand...
Click to collapse
does not seem to have worked for some reason as after flashing it should reboot in htc mode and then i would be able to flash a rom with the hboot12

May i ask what are you trying to push into your phone/sdcard?

ilostchild said:
May i ask what are you trying to push into your phone/sdcard?
Click to expand...
Click to collapse
I am trying to follow the instructions on the thread which can be found in the the following link forum.xda-developers.com/showthread.php?t=726258
basically trying to flash two image files that enable downgrading the Hboot from 0.35.0017 to 0.33.0012

androidjedi said:
I am trying to follow the instructions on the thread which can be found in the the following link forum.xda-developers.com/showthread.php?t=726258
basically trying to flash two image files that enable downgrading the Hboot from 0.35.0017 to 0.33.0012
Click to expand...
Click to collapse
managed to do it after just following the instructions and inoring what i thought was an error i managed to downgrade my happy days have a good weekend
will no doubt ask you for help another time cheers and thanks a lot

Welcome and congratz
Sent from my Nexus One using XDA App

HELP! Su was in the folder but device not found!

I followed the instructions exactly but now device not found and I folowed the video exactly, su is in the folder (((
adb shell
rm -r /data/local/tmp
ln -s /data/ /data/local/tmp
exit
adb reboot
adb shell
echo 'ro.kernel.qemu=1' > /data/local.prop
exit
abd reboot
adb shell mount -o remount,rw /system
adb push su /system/xbin/su
The adverts are back on the screen, what do I do please
Its nearly 2am in the morning

device is found now, what point do I pick up the command prompts up at?
please

Rovers82517 said:
please
Click to expand...
Click to collapse
ah, man, I'm seriously lost, it fails everytime with these 2 commands,
adb shell mount -o remount,rw /system
adb push su /system/xbin/su
the su file is definately in the platform-tools folder :/

Rovers82517 said:
ah, man, I'm seriously lost, it fails everytime with these 2 commands,
adb shell mount -o remount,rw /system
adb push su /system/xbin/su
the su file is definately in the platform-tools folder :/
Click to expand...
Click to collapse
If your drivers are installed correctly now, use the root tool in development section. Then there are no mistakes. If you insist on the manual method though, you need to put the su file and superuser.apk in your folder titled carol and Start over completely

onemeila said:
If your drivers are installed correctly now, use the root tool in development section. Then there are no mistakes. If you insist on the manual method though, you need to put the su file and superuser.apk in your folder titled carol and Start over completely
Click to expand...
Click to collapse
the files are in there, I've checked and double checked.
when I can get it to see the device again the command prompt has a # instead of a $
I can't afford to brick this thing, I don't know of any other methods, can you tell me what you mean or post the link?
It's gone 2am now I could do with even a little sleep tonight
Thank you for replying
ah, my bad, I know what tool you mean cheers dude

Rovers82517 said:
the files are in there, I've checked and double checked.
when I can get it to see the device again the command prompt has a # instead of a $
I can't afford to brick this thing, I don't know of any other methods, can you tell me what you mean or post the link?
It's gone 2am now I could do with even a little sleep tonight
Thank you for replying
ah, my bad, I know what tool you mean cheers dude
Click to expand...
Click to collapse
No problem, sometimes it just takes a lot of banging your head.

still no luck
I've copied both files to 'carol' as well as platform-tools, what have I done wrong?

Fixed but I'm not sure how
It repeatedly said file not found but in the end I decided to skip to step 4 on QemuRoot and it had worked lol very strange
Think I'll leave it a while before I attempt custom roms lol
Thanks for your help peeps

Rovers82517 said:
It repeatedly said file not found but in the end I decided to skip to step 4 on QemuRoot and it had worked lol very strange
Think I'll leave it a while before I attempt custom roms lol
Thanks for your help peeps
Click to expand...
Click to collapse
From my personal experience is best way how to root kindle fire by qemu (development part of forum) its quite easy... to solve problem if your device isn't found I had to create folder .android in my “documents“ like it is when you will instantly sdk
You have to create it via command line... mkdir .android
Create there required file how it is described in qemu thread. Reinstal kindle adb drivers and try qemu once more.. that worked for me like a charm.
Tomorrow when I will be on PC I will post step by step guide
Kerbik

About flash CMW V20A

Hello,
I had posted this in Frequently Asked Questions about the LG Optimus 4x HD but got no help so I post here for a last try.
Just followed all dexter's steps in this thread to flash CMW
http://forum.xda-developers.com/showthread.php?t=2180138
but I got stuck here. Tried to read 34 pages of the thread but still couldnt solve my problem
My LG was rooted and unlocked.
Any help? thanks
Ekio

The error message says it all: no such file or directory. Change /mnt/sdcard/ to /storage/external_SD/

AlderCass said:
The error message says it all: no such file or directory. Change /mnt/sdcard/ to /storage/external_SD/
Click to expand...
Click to collapse
Tried and still not such files and directory thx anyway

ekiong said:
Tried and still not such files and directory thx anyway
Click to expand...
Click to collapse
Are u sure, u have copied the neede files to the root of ur SD-Card? Seems not... U have to unpack the zip-files for CWM and copy both files to the root of ur SD-Card... After that the commands should work...

Bogeyof said:
Are u sure, u have copied the neede files to the root of ur SD-Card? Seems not... U have to unpack the zip-files for CWM and copy both files to the root of ur SD-Card... After that the commands should work...
Click to expand...
Click to collapse
Omg I already did
Look pics

ekiong said:
Omg I already did
Look pics
Click to expand...
Click to collapse
I needed to allow SuperSU access before I be able to do it...
Pay attention to your phone, when you give the command "adb shell", if Superuser/SuperSU don't ask permition.
Its just a idea...

RuedasLocas said:
I needed to allow SuperSU access before I be able to do it...
Pay attention to your phone, when you give the command "adb shell", if Superuser/SuperSU don't ask permition.
Its just a idea...
Click to expand...
Click to collapse
I did it in recovery mode and tried it in terminal app aswell, but nothing happened with "cat /mnt/sdcard/recovery-6028.img >/dev/block/mmcblk0p1"

ekiong said:
Omg I already did
Look pics
Click to expand...
Click to collapse
Looks like the path to your SD card is different to mine. Try replacing /mnt/sdcard/ in the original command with /sdcard/ , ie:
Code:
su
cat /sdcard/recovery-6028.img >/dev/block/mmcblk0p1
sync
Code:
su
cat /sdcard/unsecure-boot-mmcblk0p2.img >/dev/block/mmcblk0p2
sync
Also no need to get aggravated, none of us are being rewarded for helping you here but we're trying to help anyway...
*edit*
ooops didn't look at all the screenshots. The last one shows your SD card path actually is indeed the same as mine. I'm all out of ideas then.
---------- Post added at 06:48 PM ---------- Previous post was at 06:40 PM ----------
ekiong said:
I did it in recovery mode and tried it in terminal app aswell, but nothing happened with "cat /mnt/sdcard/recovery-6028.img >/dev/block/mmcblk0p1"
Click to expand...
Click to collapse
Did you do it in recovery mode from the start? When I did it it was when the phone was just switched on normally into the main OS.

ekiong said:
I did it in recovery mode and tried it in terminal app aswell, but nothing happened with "cat /mnt/sdcard/recovery-6028.img >/dev/block/mmcblk0p1"
Click to expand...
Click to collapse
AlderCass said:
Looks like the path to your SD card is different to mine. Try replacing /mnt/sdcard/ in the original command with /sdcard/ , ie:
Code:
su
cat /sdcard/recovery-6028.img >/dev/block/mmcblk0p1
sync
Code:
su
cat /sdcard/unsecure-boot-mmcblk0p2.img >/dev/block/mmcblk0p2
sync
Also no need to get aggravated, none of us are being rewarded for helping you here but we're trying to help anyway...
*edit*
ooops didn't look at all the screenshots. The last one shows your SD card path actually is indeed the same as mine. I'm all out of ideas then.
Click to expand...
Click to collapse
Where the hell did you found that path /mnt/sdcard/....... ???

Tutorial CWM
Dude forget what they say everyone tells different way, read here what i writeto you and make the steps like me.
1. Unlock Bootloader and get SU Permissions
2. Go to PlayStore download SuperSU and than start give permisions to it to update Binary , than go to Setting in SuperSU and install in System
3. Reboot Phone
4. Copy the 2 IMG data to root from SD and rename recovery-6028.img > recovery.img & unsecure-boot-mmcblk0p2.img > boot.img
this to IMG data must be unpacked from RAR(Zip) from Dexter.
5. make sure you have Unknow Sources and USB Debug Active , and also make sure that Superuser is replaced by SuperSU after reboot
6. Go to PlayStore and Download Android Terminal Emulator
and give in Terminal
Type "su" without quotes and than accept the permissions from SuperSU after that give in
----------------------------------------------------------------------------------------------------------------------------------
cat /mnt/sdcard/recovery.img >/dev/block/mmcblk0p1
sync
IF YOU USE UNSECURE BOOT tha use this
su
cat /mnt/sdcard/boot.img >/dev/block/mmcblk0p2
sync
Hope it helps and youv got it run :laugh:

RuedasLocas said:
Where the hell did you found that path /mnt/sdcard/....... ???
Click to expand...
Click to collapse
It's in the system root for me, it's a symlink. Though it didn't work for me in the cat command, which is why I suggested using /storage/external_SD/ instead which did work for me. It looks like the OP has the files in the right places, and the hash in the command line screenshot implies that SU is working correctly, so I'm all out of ideas now.
---------- Post added at 06:57 PM ---------- Previous post was at 06:55 PM ----------
x0BlackTeresis0x said:
Dude forget what they say everyone tells different way, read here what i writeto you and make the steps like me.
Click to expand...
Click to collapse
Little bit arrogant, we're all trying to help here, so I hope for your sake your way works for the OP

AlderCass said:
Looks like the path to your SD card is different to mine. Try replacing /mnt/sdcard/ in the original command with /sdcard/
Also no need to get aggravated, none of us are being rewarded for helping you here but we're trying to help anyway...
Click to expand...
Click to collapse
Sorry man, just had a bad feeling .
--------------------------------------------------------------------------
x0BlackTeresis0x said:
Dude forget what they say everyone tells different way, read here what i writeto you and make the steps like me.
1. Unlock Bootloader and get SU Permissions
2. Go to PlayStore download SuperSU and than start give permisions to it to update Binary , than go to Setting in SuperSU and install in System
3. Reboot Phone
4. Copy the 2 IMG data to root from SD and rename recovery-6028.img > recovery.img & unsecure-boot-mmcblk0p2.img > boot.img
this to IMG data must be unpacked from RAR(Zip) from Dexter.
5. make sure you have Unknow Sources and USB Debug Active , and also make sure that Superuser is replaced by SuperSU after reboot
6. Go to PlayStore and Download Android Terminal Emulator
and give in Terminal
Type "su" without quotes and than accept the permissions from SuperSU after that give in
----------------------------------------------------------------------------------------------------------------------------------
cat /mnt/sdcard/recovery.img >/dev/block/mmcblk0p1
sync
IF YOU USE UNSECURE BOOT tha use this
su
cat /mnt/sdcard/boot.img >/dev/block/mmcblk0p2
sync
Hope it helps and youv got it run :laugh:
Click to expand...
Click to collapse
Tried and looked like I'm typing in word lol, nothing happen, still android system recovery, not CMW.
Need CWM to wipe battery status, battery goes down to 93% in 1 min after full chagring.

ekiong said:
Sorry man, just had a bad feeling .
--------------------------------------------------------------------------
Tried and looked like I'm typing in word lol, nothing happen, still android system recovery, not CMW.
Need CWM to wipe battery status, battery goes down to 93% in 1 min after full chagring.
Click to expand...
Click to collapse
Remove micro sd from the phone.
Stick to the guide, pay atention to the phone screen behavior soo, keep the screen always on, in case of SuperSU ask for permition...
Dexter_nlb said:
......
GUIDE:
1. when you are running unlocked bootloader and is rooted goto step 2.
2. download attached zip files and extract content to internal sdcard location
3. use adb shell or terminal from market and execute the commands below
4. you are now running with native CWM recovery and unsecure boot, which enable adb root at boot instantly.
5. boot into recovery, by rebooting device and hold VOL-DOWN during bootup. (from power-off = keep holding vol-down during power on)
execute these 3 commands for recovery image install
Code:
su
cat /mnt/sdcard/recovery-6028.img >/dev/block/mmcblk0p1
sync
execute these 3 commands for unsecure boot image install
Code:
su
cat /mnt/sdcard/unsecure-boot-mmcblk0p2.img >/dev/block/mmcblk0p2
sync
or see screenshot here
do this at your own risk, and do NOT try this on old 4.0.3, which is not with unlocked bootloader, and you are required to install KDZ again.
THANKS to:
skydev - for his continued effort in finding root and giving our device full freedom with boot/recovery.
Click to expand...
Click to collapse
Copy and past the command lines from the post, like that you'll be sure that you don't miss write the path.
And like I use to say, be creative
Good luck !

RuedasLocas said:
Remove micro sd from the phone.
Stick to the guide, pay atention to the phone screen behavior soo, keep the screen always on, in case of SuperSU ask for permition...
Copy and past the command lines from the post, like that you'll be sure that you don't miss write the path.
And like I use to say, be creative
Good luck !
Click to expand...
Click to collapse
Still no such file, I give up :angel:
Thx every one

ekiong said:
Still no such file, I give up :angel:
Thx every one
Click to expand...
Click to collapse
You tried this? Only the path changes, but... I ran out of ideas.
Like I told you, be creative. Change /sdcard/ to /sdcard0/... don't know man...
"01. You must have Root access (https://mega.co.nz/#!0opzyBjS!DSoW-CaTRi49JcW58yvwCCEug4hz6VmnevdJ1prcdpE)
02. Extract both *.img files somewhere
03. Copy those files to your phone (no matter if internal or external storage, I used /sdcard/Unlocking/ so below commands will contains my directory)
04. Run terminal app on your phone or adb shell from PC while you have connected phone
05. Run those commands:
su
cat /sdcard/recovery-6028.img >/dev/block/mmcblk0p1
sync
su
cat /sdcard/unsecure-boot-mmcblk0p2.img >/dev/block/mmcblk0p1
sync
REMEMBER!
If your folder is different than /sdcard replace it in those commands above!
Methods and necessary files are found also here: http://forum.xda-developers.com/showthread.php?t=2180138
All credits goes to Dexter_nlb from xda community."

RuedasLocas said:
You tried this? Only the path changes, but... I ran out of ideas.
Like I told you, be creative. Change /sdcard/ to /sdcard0/... don't know man...
"01. You must have Root access (https://mega.co.nz/#!0opzyBjS!DSoW-CaTRi49JcW58yvwCCEug4hz6VmnevdJ1prcdpE)
02. Extract both *.img files somewhere
03. Copy those files to your phone (no matter if internal or external storage, I used /sdcard/Unlocking/ so below commands will contains my directory)
04. Run terminal app on your phone or adb shell from PC while you have connected phone
05. Run those commands:
su
cat /sdcard/recovery-6028.img >/dev/block/mmcblk0p1
sync
su
cat /sdcard/unsecure-boot-mmcblk0p2.img >/dev/block/mmcblk0p1
sync
REMEMBER!
If your folder is different than /sdcard replace it in those commands above!
Methods and necessary files are found also here: http://forum.xda-developers.com/showthread.php?t=2180138
All credits goes to Dexter_nlb from xda community."
Click to expand...
Click to collapse
OH MY GOD I'm stupid, I copied files with ZERO byte.
sorry I used airdroid to copy them to my phone. But only their icons moved into my phone, not contents.
It works now THANKSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS :laugh:
Close thread and my stupid problem :silly:

Install a recovery without a pc?

Hi everyone, I searched but didn't found but if any thread out there about installing a recovery without a pc(rooted with towelroot and installed super su and busybox and recovery-less). I know it's irrelevant but if there is a way to do it, it'll be super-awesome!!

As far as I know a PC is needed. This because we cant flash anything without a PC or a recovery..
Perhaps a developer can create a script that can be used with a script thing on the phone?
~~ Regards

This might be a revolutionary idea, @MrSteve555 introduced flash tool on the go and if this also happens, we might not need pc every time.

pranavthombare said:
This might be a revolutionary idea, @MrSteve555 introduced flash tool on the go and if this also happens, we might not need pc every time.
Click to expand...
Click to collapse
It's easy .
Download the latest recovery-flashable recovery package from dssmex.
Extract /data/local/tmp from the zip to same path on your phone.
Then run these commands from terminal:
Code:
chmod 755 data/local/tmp/step1.sh
sh /data/local/tmp/step1.sh
This way you can do pretty much everything without PC

You are awesome buddy. Thanks

Help
MrSteve555 said:
It's easy .
Download the latest recovery-flashable recovery package from dssmex.
Extract /data/local/tmp from the zip to same path on your phone.
Then run these commands from terminal:
Code:
chmod 755 data/local/tmp/step1.sh
sh /data/local/tmp/step1.sh
This way you can do pretty much everything without PC
Click to expand...
Click to collapse
Can you plz elaborate extraction step..
i m confused,which file to be extracted to the phone at which path!

You can use terminal emulator. .or mobile uncle tool to install recovery without pc
Press thanks

pradip.108 said:
You can use terminal emulator. .or mobile uncle tool to install recovery without pc
Press thanks
Click to expand...
Click to collapse
Actually the recovery partition is missing (I think so.).
How to use terminal emulator for installation ??

Then, download a terminal emulator onto your
and fire it up.
Once in the terminal emulator, type the following
commands one line at a time, waiting after each
line for the appropriate prompt:
$ su
# dd if=/sdcard/recovery.img of=/dev/block/
mmcblk0p18
# reboot recovery
Your device should then boot into the custom
recovery, which serves as immediate confirmation
that you did things correctly.
Sent from my GT-I8262 using XDA Free mobile app

No need to type commands just use root browser and just click on step1.sh and execute script as root and its done.
Hit " Thanks " if helpful.. :good:

Ok done?
Sent from my GT-I8262 using XDA Free mobile app

MrSteve555 said:
It's easy .
Download the latest recovery-flashable recovery package from dssmex.
Extract /data/local/tmp from the zip to same path on your phone.
Then run these commands from terminal:
Code:
chmod 755 data/local/tmp/step1.sh
sh /data/local/tmp/step1.sh
This way you can do pretty much everything without PC
Click to expand...
Click to collapse
After executing the script in the logs i have :
installation : OK
Model Number : C5303
Version : Unknow --> (ERROR: NOT COMPATIBLE)