Database Info

[MOD][12/03/09] ADB Remount, Superuser, and Busybox

I'd been trying to figure out how to set up a few simple things in my rooted, post-MR, but otherwise stock CDMA Hero. Namely, ADB Remount permissions (/default.prop file), set up Superuser to properly manage permissions for apps that require root, and install Busybox. Ideally, I wanted to set these up manually. Turns out it's not as simple as one might hope. ADB Remount, for example, requires that you modify and repackage the boot.img/recovery.img.
So, what I've got here is a minimal update.zip file you can apply to your phone via the recovery console. Nothing crazy, it's just MoDaCo's ROM 1.1, but with everything taken out except for the aforementioned items. Once you patch your phone, just these items will be configured and your phone will still look, run, etc. the same as before. Also, a2sd will be copied to your /system/bin directory, but it's something that had to stay in the file for some reason, otherwise the phone wouldn't boot. Probably a setting Paul built into the boot.img.
In any case, here it is. It's working well for me. Hope it helps some of you out too.
****
Thanks goes to Paul of course (MoDaCo) camalot (Droid Explorer) and dagnasty for telling me about the auto-sign plugin that's available in Droid Explorer.
Instructions for manually installing Busybox over here:
http://forum.xda-developers.com/showthread.php?t=591303
****

I responded on ppcgeeks:
mercado79 said:
IAlso, a2sd will be copied to your /system/bin directory, but it's something that had to stay in the file for some reason, otherwise the phone wouldn't boot. Probably a setting Paul built into the boot.img.
Click to expand...
Click to collapse
Yup. It's a script that was added to the boot.img-ramdisk that copies all of your apps to your sd when apps2sd's requirements are met.

So if the sdcard is not partitioned correctly then ap2sd will not run, yes?

Smacky55 said:
So if the sdcard is not partitioned correctly then ap2sd will not run, yes?
Click to expand...
Click to collapse
"Correctly" is relative. If there is no EXT partition on the sdcard, then the ROM won't try to move your applications to it. But the script runs regardless.

Sorry, meant if sdcard isn't partitioned at all. Thanks for the answer.

flipzmode told me in another thread that even though this script is included, that doesn't mean that the update.zip i posted will enable apps2sd for anyone. there's more required in order to get it to work (i stripped most everything out).

A few simple questions. re -stock 1.56... rom
1) in the zip system folder, its refers to /xbin ; does that require that /system/xbin be pre-existent, or will it create it ?
2) busybox is in /system/bin on mine. Do I need to remove it?
a) if so then due to the "busybox --install -s /system/bin"
command , how do i remove the current symbolic busybox entry points?
b)have $PATH changes been applied to overwrite the current export
3) empty init.sh file?
4) google meta references?
I think I may understand the need to get bootstrap-"root" permissions established, is there another way as well?
Thanks for dealing with these noobie questions.

Thanks for this. worked out great.

willy900wonka said:
A few simple questions. re -stock 1.56... rom
1) in the zip system folder, its refers to /xbin ; does that require that /system/xbin be pre-existent, or will it create it ?
2) busybox is in /system/bin on mine. Do I need to remove it?
a) if so then due to the "busybox --install -s /system/bin"
command , how do i remove the current symbolic busybox entry points?
b)have $PATH changes been applied to overwrite the current export
3) empty init.sh file?
4) google meta references?
I think I may understand the need to get bootstrap-"root" permissions established, is there another way as well?
Thanks for dealing with these noobie questions.
Click to expand...
Click to collapse
sorry willy man. not sure what i can tell you. i'm pretty close to being a newbie myself. i never fully understood what the script was doing. i simply took the original modaco update and compared it to another script paul had posted on his forums last fall.
if you unzip the file, you should be able to see everything that's going on. the file structure is super simple, so modify it to suit your needs and give it a try. worst case, you'll need to revert to a nandroid backup. oh, and don't forget you'll need to sign the file and zip it back up in order to flash it onto the phone.
come to think of it, i guess maybe i should update the script using the latest modaco rom, though i'm not sure how helpful it'd be for everyone. to be honest, i've since bitten the bullet and moved on to flipz's rom and the gumbo kernel. runs beautifully!

Ok, so I formated the card, put the .zip file on the sdcard and tried to press home+power to enter the recovery council. When I hold home and press power I am taking to a screen that has an exclamation point and an image of the phone.
Can anyone help?

partylatino420 said:
Ok, so I formated the card, put the .zip file on the sdcard and tried to press home+power to enter the recovery council. When I hold home and press power I am taking to a screen that has an exclamation point and an image of the phone.
Can anyone help?
Click to expand...
Click to collapse
Boot the phone by holding home only. And...I'm assuming you have the recovery console installed and are rooted.

I think the problem is that a recovery boot image was not previously installed. A green screen with a set of options should've appeared.
http://forum.xda-developers.com/showthread.php?t=596879
I prefer 1.2.3

mercado79 said:
Boot the phone by holding home only. And...I'm assuming you have the recovery console installed and are rooted.
Click to expand...
Click to collapse
I did root the phone but I am not familiar with the recovery council. I tried to search for this but was unsuccessful.
I just got my Hero last week so I am still new to all of this. Can you point me in the right direction?

partylatino420 said:
I did root the phone but I am not familiar with the recovery council. I tried to search for this but was unsuccessful.
I just got my Hero last week so I am still new to all of this. Can you point me in the right direction?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=596879 explanation
code from : http://forum.xda-developers.com/showthread.php?t=583291
13:
Code:
adb push recovery-RA-heroc-v1.5.2.img /sdcard
Pushing is equivalent of copy the file to the root of your sdcard. By the time you finished reading this it should be done. You'll know its done because the ouput will say something like transferred X bytes in X secs.
14:
Code:
adb shell reboot
This will cause the phone to restart automatically. Wait till it is fully booted to continue.
http://tinyurl.com/yc96j2z

partylatino420 said:
I did root the phone but I am not familiar with the recovery council. I tried to search for this but was unsuccessful.
I just got my Hero last week so I am still new to all of this. Can you point me in the right direction?
Click to expand...
Click to collapse
Your google search didn't turn anything up on "recovery council" because the operative use would have actually been "recovery console"..

that did it!! Thanks guys!!!

um, what???
mercado79 said:
So, what I've got here is a minimal update.zip file you can apply to your phone via the recovery console.
Click to expand...
Click to collapse
Apply via the recovery console? Sorry, still very new to this. Thanks!

Recovery Console
Go to the recovery console by holding down home when you power your Android. In that menu, you should see something that says 'flash update from SD card'... or something like that... then you choose the .zip that he has so kindly provided us.
Oh, and you have to put the .zip file that he provided on the SD card if that isn't already obvious :/
I also renamed it update.zip once I copied it to my SD card. Hope this clears it up a little. I just rooted my Hero yesterday.. so I am on the same NOOB level.

Do I need to wipe before flashing this / will this wipe my phone if I flash it?

fallonjp said:
Do I need to wipe before flashing this / will this wipe my phone if I flash it?
Click to expand...
Click to collapse
You shouldn't need to wipe your phone; however I really don't think it's a good idea to use this. I put this together last year when we were still running Android 1.5 so it's WAY out of date. Just go with Nfinite's ROMs. He keeps them almost completely stock (depending on which you choose) and they can serve as great back-up / go-to ROMs.

[Q] Install apk from recovery

I screwed up my phone, there's not launcher, touchwiz, and system ui fail, setting app fails. Everything is screwed up. I'm really new to this, but is there any way to install these things (I have the apks) from recovery?

Ardentes said:
I screwed up my phone, there's not launcher, touchwiz, and system ui fail, setting app fails. Everything is screwed up. I'm really new to this, but is there any way to install these things (I have the apks) from recovery?
Click to expand...
Click to collapse
Push all your stock launcher,systemui,settings apk from stock ROM into a flash able zip
Sent from my GT-S7500 using xda app-developers app

Techix18 said:
Push all your stock launcher,systemui,settings apk from stock ROM into a flash able zip
Sent from my GT-S7500 using xda app-developers app
Click to expand...
Click to collapse
Soooo, not to sound like a noob, or whatever, but... how do I do that?

re-flash your stock rom/custom rom

akosicarlo said:
re-flash your stock rom/custom rom
Click to expand...
Click to collapse
I don't have the stock rom, all I have is the backup, and the backup is missing the system.img file

you backed up your custom rom?
find it on recovery
Backup and Restore -> Restore

akosicarlo said:
you backed up your custom rom?
find it on recovery
Backup and Restore -> Restore
Click to expand...
Click to collapse
I backed up a stock rom, using mtkdroidtools, however after telling it to prepare the block so that I can use sp flash tools, it gets all of the files ready, but there is no system.img file

what device u are using with?

Ardentes said:
Soooo, not to sound like a noob, or whatever, but... how do I do that?
Click to expand...
Click to collapse
Download your stock firmware and extract the system file from the firmware and grab whatever you need from the stock system file and put it into this sample.zip that i have attached.If you want to add any more things,pls add additional codes into the updater script

If you have cwm recovery then you can use adb to push the respective files to their places and set permissions
sorry for any ty¶°s

Techix18 said:
Download your stock firmware and extract the system file from the firmware and grab whatever you need from the stock system file and put it into this sample.zip that i have attached.If you want to add any more things,pls add additional codes into the updater script
Click to expand...
Click to collapse
I'm getting signature verification failed. Installation aborted

professor_proton said:
If you have cwm recovery then you can use adb to push the respective files to their places and set permissions
sorry for any ty¶°s
Click to expand...
Click to collapse
Unfortunately I don't have cwm, kinda wishing I did though

Ardentes said:
Unfortunately I don't have cwm, kinda wishing I did though
Click to expand...
Click to collapse
"One simply doesn't mess with phone without having a custom recovery "
Still if your ROM boots and your rooted and you have adb on your PC (its a must bro , I personally can't live without it )
Type (not the part in *le something* )
Adb shell *le presses enter*
Su *le presses enter again*
Mount -o rw, remount /system /system *le does it again*
Exit *enter*
Exit *enter*
Example if you want to push systemui
adb push SystemUI.apk /system/app/SystemUI.apk
*enter*
Similarly push all other apps
Adb shell *le presses enter again*
Su
Chmod 644 /system/app/SystemUI.apk
Change the SystemUI.apk to what ever app you want to replace
This Is one of these moments we realise how important adb and custom recoveries are
sorry for any ty¶°s

professor_proton said:
"One simply doesn't mess with phone without having a custom recovery "
Still if your ROM boots and your rooted and you have adb on your PC (its a must bro , I personally can't live without it )
Type (not the part in *le something* )
Adb shell *le presses enter*
Su *le presses enter again*
Mount -o rw, remount /system /system *le does it again*
Exit *enter*
Exit *enter*
Example if you want to push systemui
adb push SystemUI.apk /system/app/SystemUI.apk
*enter*
Similarly push all other apps
Adb shell *le presses enter again*
Su
Chmod 644 /system/app/SystemUI.apk
Change the SystemUI.apk to what ever app you want to replace
This Is one of these moments we realise how important adb and custom recoveries are
sorry for any ty¶°s
Click to expand...
Click to collapse
It isn't recognizing my phone

Ardentes said:
It isn't recognizing my phone
Click to expand...
Click to collapse
Debugging not enabled ???
it hurts when I help someone and they say thanks Instead of pressing the button

professor_proton said:
Debugging not enabled ???
it hurts when I help someone and they say thanks Instead of pressing the button
Click to expand...
Click to collapse
I can't enable debugging, the rom boots fine, as soon as it gets to the lock screen, there are no settings, because setting stops working, touchwiz stops working and so does systemui, and they constantly stop working to the point that I can't do anything.

Ardentes said:
I can't enable debugging, the rom boots fine, as soon as it gets to the lock screen, there are no settings, because setting stops working, touchwiz stops working and so does systemui, and they constantly stop working to the point that I can't do anything.
Click to expand...
Click to collapse
Well that sucks ! And the screwup of the year award goes to you !
Well then the last resort would be flashing stock rom using Odin

professor_proton said:
Well that sucks ! And the screwup of the year award goes to you !
Well then the last resort would be flashing stock rom using Odin
Click to expand...
Click to collapse
I'd love to... if my phone could go into download mode... or if I had the stock rom....

Ardentes said:
I'd love to... if my phone could go into download mode... or if I had the stock rom....
Click to expand...
Click to collapse
Which phone do you have ???
it hurts when I help someone and they say thanks Instead of pressing the button

professor_proton said:
Which phone do you have ???
it hurts when I help someone and they say thanks Instead of pressing the button
Click to expand...
Click to collapse
Its a gt-i9500 galaxys s4 clone. but it has only samsung logos, so I can't determine the original manufacturer.

[DEAD][Script][4.4.2] How to make all apps read External SD Card

This fix Requires ROOT and Busybox installed to /system/xbin
Context: I have been looking for a way to make an app that hides files to read/write files on my external SDcard, The way I found was to edit the platform.xml file to add that missing line as guided here: LINK this is just one of the many articles saying the same thing. which helped some apps work, but not the one i was looking for.
Reason: the point of this script is to make it so you do not have to set permission to the "media_rw" folder after every reboot manually.
Steps:
1) Follow and complete guide linked above, or any other similar guide, if you have not done so already.
*NOTE* some custom ROMs have already implemented this fix
2) After reboot use an app that allows you to make scripts (Ex. Rom Toolbox) this guide will use Rom Toolbox app
- create new script, name it whatever you want. I named it "sdcard permission"
- input this line and save:
Code:
chmod 777 /mnt/media_rw
*NOTE* you do not need to put it as 777 but it is what worked for me as it gave full read/write/execute permissions
3) Set script to run at boot
4) Run script manually then check app to see if it worked
-Alternatively go check /mnt/media_rw to see if it has the new permissions
Now you should be able to access the external SD card after every boot.
NOTE: you may need to redo the guide in the first step after switching ROMs as the new ROM may not have the fix implemented.

Reserved just in case

Buddyjohn said:
This fix Requires ROOT and Busybox installed to /system/xbin
Context: I have been looking for a way to make an app that hides files to read/write files on my external SDcard, The way I found was to edit the platform.xml file to add that missing line as guided here: LINK this is just one of the many articles saying the same thing. which helped some apps work, but not the one i was looking for.
Reason: the point of this script is to make it so you do not have to set permission to the "media_rw" folder after every reboot manually.
Steps:
1) Follow and complete guide linked above, or any other similar guide, if you have not done so already.
*NOTE* some custom ROMs have already implemented this fix
2) After reboot use an app that allows you to make scripts (Ex. Rom Toolbox) this guide will use Rom Toolbox app
- create new script, name it whatever you want. I named it "sdcard permission"
- input this line and save:
Code:
chmod 777 /mnt/media_rw
*NOTE* you do not need to put it as 777 but it is what worked for me as it gave full read/write/execute permissions
3) Set script to run at boot
4) Run script manually then check app to see if it worked
-Alternatively go check /mnt/media_rw to see if it has the new permissions
Now you should be able to access the external SD card after every boot.
NOTE: you may need to redo the guide in the first step after switching ROMs as the new ROM may not have the fix implemented.
Click to expand...
Click to collapse
I have a Samsung Galaxy S3 and been trying all kind of things to get to media_rw folder to keep its read writable and nothing worked so far. I did everything in you post to see if it would help/work but script not working. I can only keep permissions if I set manually set permission using root browser and then it working until I reboot the phone and I tried adding the script using ROM Toolbox pro but its not even changing the media_rw permission when run it.
This my first time using the script tool but to me seems to be setup properly. If needed I will get some screenshots of the script windows to show how I set it up. I am just posting this now to see if anyone can help or wants to ask some questions.
I know how permissions work in Windows and getting up to speed with Android. I been trying to make the media_rw folder r/w to be able to able to path it to my Titanium Backup folder on my external SD.
This looks similar to setting boot bat files in Windows so I know it should work but no go so far.

Heres the screenshots of my script that failed to run and the output file hoping to get some advice why script did not work.

Is this thread dead? Should I seek answers elsewhere?

techmanc said:
Is this thread dead? Should I seek answers elsewhere?
Click to expand...
Click to collapse
yes this thread is dead, lots of apps are updating compatibility finally, also there are some xposed modules that essentially does what i did on here. so this is dead.

Buddyjohn said:
yes this thread is dead, lots of apps are updating compatibility finally, also there are some xposed modules that essentially does what i did on here. so this is dead.
Click to expand...
Click to collapse
can yuo point me to some threads that are still working cause I still not been able to get RW access to media_rw folder.

techmanc said:
can yuo point me to some threads that are still working cause I still not been able to get RW access to media_rw folder.
Click to expand...
Click to collapse
try these three xposed modules, i recommend enabling one at a time to see which works, reboot after enabling one.
http://forum.xda-developers.com/xposed/modules/app-handleexternalstorage-t2693521
http://forum.xda-developers.com/xposed/modules/kitkat-sd-card-access-t2790992
http://forum.xda-developers.com/xposed/modules/xposed-disablesignaturecheck-t2789267

also i just realized why it was failing on yours. make sure you have busybox installed to system/xbin
that will make the script work. or atleast should.

Buddyjohn said:
also i just realized why it was failing on yours. make sure you have busybox installed to system/xbin
that will make the script work. or atleast should.
Click to expand...
Click to collapse
Looked s Busybox says installed to /system/bin heres the screenshot do I click install to move or use smart install. Never did much with app just know it was needed for rooting.

techmanc said:
Looked s Busybox says installed to /system/bin heres the screenshot do I click install to move or use smart install. Never did much with app just know it was needed for rooting.
Click to expand...
Click to collapse
Install it to /xbin

Buddyjohn said:
Install it to /xbin
Click to expand...
Click to collapse
What the difference between installing to /xbin vs /system/bin might I ask?

techmanc said:
What the difference between installing to /xbin vs /system/bin might I ask?
Click to expand...
Click to collapse
Honestly I am not to sure, I just assumed xbin was the right one as a lot of older mods and roms required busybox on xbin. so i tried it and it worked.

build prop help

i saved original build prop in my pc and and i want pull in my device with adb i do not have any info about this step my device go directly to black screen in firmware update
how i can push my build prop in my lg g3 d850 with pc win 7 64bit
help my

anasmilan said:
i saved original build prop in my pc and and i want pull in my device with adb i do not have any info about this step my device go directly to black screen in firmware update
how i can push my build prop in my lg g3 d850 with pc win 7 64bit
help my
Click to expand...
Click to collapse
Download android sdk, install it as google tells you. Go to the folder your build prop is at, hold shift, press the right mouse button, press on open command prompt. Type this in it:
adb shell
su
stop
mount -o rw, remount /system
push build.prop /system/build.prop
mount -o ro, remount /system
reboot
If you cant do that, you can always reflash the firmware

push not found
Remorcer said:
Download android sdk, install it as google tells you. Go to the folder your build prop is at, hold shift, press the right mouse button, press on open command prompt. Type this in it:
adb shell
su
stop
mount -o rw, remount /system
push build.prop /system/build.prop
mount -o ro, remount /system
reboot
If you cant do that, you can always reflash the firmware
Click to expand...
Click to collapse
i moved the build prop file to platform-tools file in sdk and i try go to command prompt with shift and Type this command
adb shell
su
stop
mount -o rw, remount /system
push build.prop /system/build.prop
tell me push: not found
see the pic
and i try the flash tools with the same tot & dll
the flash tools error
read model is deffrent

I use pushbullet for small stuff like this then just move it and set permissions with root explorer
Sent from my LG-D850 using Tapatalk 2

no android in device
screwyluie said:
I use pushbullet for small stuff like this then just move it and set permissions with root explorer
Sent from my LG-D850 using Tapatalk 2
Click to expand...
Click to collapse
the phone go direct to frimware update how i can use pushbullet in this mode?

anasmilan said:
i moved the build prop file to platform-tools file in sdk and i try go to command prompt with shift and Type this command
adb shell
su
stop
mount -o rw, remount /system
push build.prop /system/build.prop
tell me push: not found
see the pic
and i try the flash tools with the same tot & dll
the flash tools error
read model is deffrent
Click to expand...
Click to collapse
I wrote a script, it should be easier now.
Put build.prop into the Puuuuush folder and run PUSH_BUILD.PROP
EDIT: Sorry, I told you the wrong commands. it should be fixed now with this tool.

Remorcer said:
I wrote a script, it should be easier now.
Put build.prop into the Puuuuush folder and run PUSH_BUILD.PROP
EDIT: Sorry, I told you the wrong commands. it should be fixed now with this tool.
Click to expand...
Click to collapse
Does it work if i can only power on the phone in download mode?
I have my phone soft bricked because of a corrupted build.prop and i need to replace it.

anasmilan said:
the phone go direct to frimware update how i can use pushbullet in this mode?
Click to expand...
Click to collapse
my bad, I thought you were just looking to transfer the file
unless I've missed something you can't do ADB in recovery or download mode. which has always seemed stupid to me.
you'll need to use ODIN to flash the rom again

screwyluie said:
my bad, I thought you were just looking to transfer the file
unless I've missed something you can't do ADB in recovery or download mode. which has always seemed stupid to me.
you'll need to use ODIN to flash the rom again
Click to expand...
Click to collapse
ODIN is for samsung phones.
After I modified the build.prop file I forgot to change the file rights and now it is stuck on a black screen with the led on green/blue
I have a backup of the original file on the SD.
The phone can get into download mode.
I have already tried the factory reset but nothing.
I have tried the unroot metod from the post:
http://forum.xda-developers.com/att-lg-g3/general/unroot-return-to-factory-stock-att-lg-g3-t2820827
But I got this message:
PID: BS02S140706002625
IMEI:
Model: D850
DLL: D850
BIN: LGD850AT-01-V10D-310-410-JUN-19-2014+0
SWV: LGD850AT-00-V10D-310-410-JUN-19-2014+0
SWOV: LGD850AT-00-V10D-ATT-US-JUN-19-2014+0
Device Model is different!
Check Phone or DLL!
My phone model is the AT&T LG G3 32Gb D850 Metalic Black
Please, can someone helpme?
I am desperate!

Sorry I'm a Samsung guy, lg tool or whatever it is.
There is a file from the g2 that makes it so the model doesn't matter you'll need that
Sent from my LG-D850 using Tapatalk 2

http://forum.xda-developers.com/showthread.php?t=2827381
You mean this file

Same thng happened to me
Ok i edited the build.prop, apparently I did something wrong, I can only boot to black screen with blue/green flashing led. I did back up my original build.prop, and I can get phone into download mode....just not sure what to do from here. I am using a mac, but I can get to a PC if needed. Any help would be GREATLY appreciated.

DIRKxxxDIGGLER said:
Ok i edited the build.prop, apparently I did something wrong, I can only boot to black screen with blue/green flashing led. I did back up my original build.prop, and I can get phone into download mode....just not sure what to do from here. I am using a mac, but I can get to a PC if needed. Any help would be GREATLY appreciated.
Click to expand...
Click to collapse
I'm really desperate, anyone that can help me get my phone back up I would really appreciate it....just get it back to stock or anything. I am willing to donate to anyone that can help me get my phone up. I know I'll get ripped apart for messing with my phone that was above my ability, I have learned my lesson I understand, just need help please. Thanks for anyone that can get me back up.

DIRKxxxDIGGLER said:
I'm really desperate, anyone that can help me get my phone back up I would really appreciate it....just get it back to stock or anything. I am willing to donate to anyone that can help me get my phone up. I know I'll get ripped apart for messing with my phone that was above my ability, I have learned my lesson I understand, just need help please. Thanks for anyone that can get me back up.
Click to expand...
Click to collapse
Woot! got it fixed!

How did you end up fixing it?
Sent from my LG-D850 using XDA Free mobile app

ApkMultiTool

Anybody know how to change the destination folder when installing the modified apk?

wileout said:
Anybody know how to change the destination folder when installing the modified apk?
Click to expand...
Click to collapse
What do you mean exactly?
Are you installing using a flashable zip or the application?
A flashable zip is the easiest way so you can edit the installer script to place it in whatever directory you wish.
I never use the apk tools themselves for installing.
You can also boot to recovery and mount system.
Then from terminal, EX:
Code:
adb push MyCoolMod.apk /system/app
Let me know if that helps, or if you need more info, or are deadset on using that app to install and we can go from there.

santod040 said:
What do you mean exactly?
Are you installing using a flashable zip or the application?
A flashable zip is the easiest way so you can edit the installer script to place it in whatever directory you wish.
I never use the apk tools themselves for installing.
You can also boot to recovery and mount system.
Then from terminal, EX:
Code:
adb push MyCoolMod.apk /system/app
Let me know if that helps, or if you need more info, or are deadset on using that app to install and we can go from there.
Click to expand...
Click to collapse
I was trying to use the tool to push iy becaude i cant get adb to push it at all...but the tool keeps trying to push it to data/app or something like that and i need it to go to system/priv-app

ok tried adb pushing it again and no go even doing it with your command. any ideas?

wileout said:
ok tried adb pushing it again and no go even doing it with your command. any ideas?
Click to expand...
Click to collapse
My bad, forgot a slash, try it again.
Code:
adb push MyCoolMod.apk /system/priv-app/

santod040 said:
My bad, forgot a slash, try it again.
Code:
adb push MyCoolMod.apk /system/priv-app/
Click to expand...
Click to collapse
I did that man it just restarts adb like i put in a bad command or it says cannot stat blah blah blah file or directory not found

Ive had tigerstown tryin to help me out too and he has no idea whats going on

well got adb to push it but I lost my clock widget all together lol

wileout said:
well got adb to push it but I lost my clock widget all together lol
Click to expand...
Click to collapse
Using stock data cable? Had that be a problem on other devices when pushing files.
Sent from my HTC6525LVW using Tapatalk

wileout said:
well got adb to push it but I lost my clock widget all together lol
Click to expand...
Click to collapse
You need to do:
adb remount /system rw
adb push test.apk /system/priv-app

jsaxon2 said:
You need to do:
adb remount /system rw
adb push test.apk /system/priv-app
Click to expand...
Click to collapse
Do i replace test with the name of the file?

wileout said:
Do i replace test with the name of the file?
Click to expand...
Click to collapse
Yes sir.
You also need to have the file in your adb directory and start the command prompt from there.
There are other ways to do it, but this should work for you.

jsaxon2 said:
Yes sir.
You also need to have the file in your adb directory and start the command prompt from there.
There are other ways to do it, but this should work for you.
Click to expand...
Click to collapse
I got the widget back by going into the priv-app folder and clicking it and installing it but now it force closes so im assuming its something on my end with how it was signed and stuff

wileout said:
I got the widget back by going into the priv-app folder and clicking it and installing it but now it force closes so im assuming its something on my end with how it was signed and stuff
Click to expand...
Click to collapse
After you push to the /system/priv-app folder, did you reboot? That should have installed it for you. Might also be a permissions problem. Make sure the permissions on your file are the same as the permissions on the rest of the files in that folder.

jsaxon2 said:
After you push to the /system/priv-app folder, did you reboot? That should have installed it for you. Might also be a permissions problem. Make sure the permissions on your file are the same as the permissions on the rest of the files in that folder.
Click to expand...
Click to collapse
Ok ill try that...thanks for your help ill report back

jsaxon2 said:
After you push to the /system/priv-app folder, did you reboot? That should have installed it for you. Might also be a permissions problem. Make sure the permissions on your file are the same as the permissions on the rest of the files in that folder.
Click to expand...
Click to collapse
Tried that and im still getting force closes so its something on my end im assuming