Hi all-
I have unknowingly renamed the framework-res.apk file to framework-res.bak, following the suggestion of a website (who had said to copy the file over, not rename it). I had no idea that would make the phone instantly useless, and render everything inoperative
I was rooted. All I need to do is copy the backup back over, but how?
I am able to get into CMM-based Recovery v5.0.2.7 and can mount the system directory and see it on my PC, but for some reason the framework directory is invisible. There is talk on the web about getting to a prompt and typing:
adb push framework-res.apk /system/framework/framework-res.apk
But how in the world do you get to a prompt? I don't see it on any menu, anywhere and the adb command is unrecognized on my OS.
Hoping I'm not ruined...... thanks for any advice.
Samsung Captivate Glide Android 2.3, Ubuntu
To get ADB, you first have to install the Android SDK.
http://developer.android.com/sdk/index.html
Then, you have to put ADB in the PATH variable.
http://www.redmondpie.com/how-to-set-up-android-adb-and-fastboot-on-windows-tutorial/
After that, you can just type adb in the command prompt and it should work.
Hi,
I downloaded the SDK tools and got the adb command, but when I mount the phone with recovery I still don't see any framework directory.
I got to DOS and navigated to the directory where my copied framework-res.apk file was, and ran:
c:\adb\adb push framework-res.apk L:\framework\framework-res.apk
it replied with:
1319 kb/s (7979827 bytes in 5.905s)
However, then I rebooted the phone and it won't get past the SAMSUNG screen at all, it just sits there forever.
- why can't I see the framework directory, even though I have mounted it through CWM based recovery?
- can I see it using the ADB tools?
- has just copying the copied file back over, destroyed the cell phone? I can't possibly see how.
Thanks for any help
OK I found out the problem.
you need to use forward slashes and put the whole pathname in:
C:\adb\adb push framework-res.apk /system/framework/framework-res.apk
Thats assuming you have the adb command in the c:\adb directory.
It seems the phone is working again.
WHEW! Man that file is dangerous. be warned.
Related
Any one out there that can help me understand the last part of Adb.
lol.
I learned how to use Odin and superoneclick.
Now I am on Adb.
I read all I can on Team Whiskeys and XDA website and other googled websites. I installed everything and did the My computer/system properties/advance/Enviroment Variables/Path entries.
I start ADB and then I do in command prompt "adb devices" and whoopie I see my phone.
NOW WHAT?
No body on the instructions or website that I have read goes past that.
How do I push down a Rom to overwrite the system with the new Rom I want to try?
Hope someone out in the Forum has really done this before and will post how they do it.
Need to find someone smart enough to finish the instructions.
Thanks,
CatfishKnight
with adb you can copy files to your sd card or system without ever having to mount your sd card to your phone. that's the main thing I use it for
for instance, I have a rom named Trigger_281.zip on my desktop, to push it I would do
Code:
adb push Trigger_281.zip /sdcard/Trigger_281.zip
you can also pull files by using "adb pull <location of file on phone>"
and so on.
Furthermore if you ever need shell access you can do "adb shell" and run unix commands from console instead of on the phone
birgertime said:
with adb you can copy files to your sd card or system without ever having to mount your sd card to your phone. that's the main thing I use it for
for instance, I have a rom named Trigger_281.zip on my desktop, to push it I would do
Code:
adb push Trigger_281.zip /sdcard/Trigger_281.zip
you can also pull files by using "adb pull <location of file on phone>"
and so on.
Furthermore if you ever need shell access you can do "adb shell" and run unix commands from console instead of on the phone
Click to expand...
Click to collapse
Thanks for showing me how to push to my phone. Now do I install it. In recovery mode as a zip? I thought adv installed it and I just rebooted and it was installed.
birgertime said:
with adb you can copy files to your sd card or system without ever having to mount your sd card to your phone. that's the main thing I use it for
for instance, I have a rom named Trigger_281.zip on my desktop, to push it I would do
Code:
adb push Trigger_281.zip /sdcard/Trigger_281.zip
you can also pull files by using "adb pull <location of file on phone>"
and so on.
Furthermore if you ever need shell access you can do "adb shell" and run unix commands from console instead of on the phone
Click to expand...
Click to collapse
Thanks for showing me how to push to my phone. Now do I install it. In recovery mode as a zip? I thought adb installed it and I just rebooted and it was installed.
It just moves the file to the phone. You have to flash the file yourself if it is a flashable.
You can push a .jpg file if you want, it doesn't matter, it only moves it.
And I think you're getting confused with the 'adb install' command. You can install NON-system APKs by doing that.
Code:
adb install someprogram.apk
birgertime said:
It just moves the file to the phone. You have to flash the file yourself if it is a flashable.
You can push a .jpg file if you want, it doesn't matter, it only moves it.
And I think you're getting confused with the 'adb install' command. You can install NON-system APKs by doing that.
Code:
adb install someprogram.apk
Click to expand...
Click to collapse
I guess I was confused on what ADB could do.
I thought it could push down a Rom and install it onto the phone.
Then I would disconnect it and reboot the phone and I would have the newer rom installed.
I didn't know that it only pushed the ROM onto the sdcard and then I would install the zip from the phone itself.
Finally I got an answer to my question.
LOL.
I have tried on the team whiskey site to and no one answered it. Also all the stuff I read on it really didn't tell me that either.
I really appreciate your answer in helping me understand it.
I am also using Trigger 2.8 like you. But you said you had Trigger2.8.1 saved??
I have only seen Trigger 2.8 today.
^ birgertime is the developer of Trigger. He is already cooking something new in the kitchen.
s15274n said:
^ birgertime is the developer of Trigger. He is already cooking something new in the kitchen.
Click to expand...
Click to collapse
Duhhh... I missed that... LOL. I am brain fried!!! I have installed Odin, SuperOneClick, and ADM. I have be learning all three but was having trouble with understanding what ADB could do. Been reading lots and lots about it all day. Whew. I am tired. Ever instruction got down to connecting and seeing your phone and then it would end there. Finally I got an answer from Birgertime. Thanks.
I have 4 different roms saved to my phone to switch between if I want too. But I love Trigger 2.8 with Overclock v2. Also I am seeing 9 sats out of 11 on my gps. With Overclock v2 and using CPUBoostPro I am right at 2000 with Quadrant.
I rooted and now I keep losing su permissions and I can't boot into cwm recovery. I figure something messed up during the process. I guess I should unroot and then try the process again. I'm trying to use the HOWTO Return to stock properly and safely process.
I have adb installed and when I try to do the first step:
(adb push misc.img /data/local/)
It says this:
adb server is out of date. Killing....
* daemon started successfully *
cannot stat 'misc.img': no such file or directory
I'm sure I have a file in the wrong directory? Any help is appreciated!
From your pc before you run adb push did you:
cd c:\path\to\downloads\
?
I cannot the 100 percent certain that is what you need from your description but I however am 80 percent sure.
this is not a signature I type it in every time maybe sent from my phone or my computer
In the newer ADB version you need to have your command promt directed to the platform-tools directory. So, whatever you are trying to push also needs to be within that directory.
Even if you add it to your $PATH?
I haven't updated my sdk in a long long time so I'm not sure
this is not a signature I type it in every time maybe sent from my phone or my computer
If you have an old version of the Android SDK then misc.img should be placed in the tools directory. Personally I have the SDK version 7 and I had to place the files in Platform-tools.
rizzomegav said:
Even if you add it to your $PATH?
I haven't updated my sdk in a long long time so I'm not sure
this is not a signature I type it in every time maybe sent from my phone or my computer
Click to expand...
Click to collapse
It depends which directory path you have in your $PATH variable. If you have the latest SDK and $PATH is still pointing to "tools" then ADB will not be there... you need to update your $PATH variable to point wherever ADB is located.
stedrocklp said:
In the newer ADB version you need to have your command promt directed to the platform-tools directory. So, whatever you are trying to push also needs to be within that directory.
Click to expand...
Click to collapse
How can I see what version I'm using? I'm new to ADB and was just trying to follow the instructions on the HOWTO so I didn't have to ask a bunch of questions.
My adb is in C:\sdk\platform-tools\
if that helps any. That is also the file that the misc.img file is in
If your adb is in C:\sdk\platform-tools\ did you cd C:\sdk\platform-tools\ first?
Thanks to everyone for the help. I got it figured out last night!
Well I've had my first issue with my shiny new handset! I rooted it this afternoon and decided to modify the build.prop to change the dalvik heap size as recommended by various people. However on rebooting, the phone's now hanging on the splash screen.
I can get into download and recovery ok - any ideas on how to fix this? Is build.prop editable in either of these modes?
If you have adb, boot in to CWM, adb pull /system/build.prop
Edit the file, please note that if you're on windows, DO NOT USE WORD or anything similar, it'll mess up your line endings (Newline Format), I suspect this is what happened in the first place.
In any case, if you need to edit the file in plain notepad, download "ToFroDos" and run todos on the file before editing,
then edit, then run fromdos on the file, then adb push it back on to the device.
Note on Re-uploading: you may need to execute adb remount rw in order to upload the file.
In any case, short form:
1. Boot to recovery
2. adb pull /system/build.prop
3. Edit locally (Making sure to keep the proper newline format (\n))
3.5 adb remount rw
4. adb push ./build.prop /system/build.prop
As said extract the original one from the rom and push it manually via adb push command
Sent from my GT-I9300 using Tapatalk 2
Oddly enough I used the build.prop editor app from the Play store. Seems that the issue was that it didn't put an 'm' at the end of the line specifying the size - so it read as '128'. Anyway, I've done what you suggested, and it worked - excellent stuff, thanks!
Next time, just use Jota Text Editor on your phone
I have use it many times to edit my build.prop file and never have issue
I tried adb pull /system/build.prop, but the build.prop file doesn't appear anywhere on my PC, so I can't edit it. My device appears in adb devices, and the command line responds with "718 KB/s (2943 bytes in 0.004s)" when I enter "adb pull /system/build.prop", but I can't find it
guitarplayer365 said:
I tried adb pull /system/build.prop, but the build.prop file doesn't appear anywhere on my PC, so I can't edit it. My device appears in adb devices, and the command line responds with "718 KB/s (2943 bytes in 0.004s)" when I enter "adb pull /system/build.prop", but I can't find it
Click to expand...
Click to collapse
Make sure you're not in a readonly directory on the host,
a default cmd in windows will start in the dir of %ComSpec% (Usually C:\windows\system32).
Abd will try to put files wherever you're located in you filesystem, unless you tell it otherwise. (adb pull {source} [destination])
Sent from my GT-I9300 using XDA
T0yK4T said:
If you have adb, boot in to CWM, adb pull /system/build.prop
Edit the file, please note that if you're on windows, DO NOT USE WORD or anything similar, it'll mess up your line endings (Newline Format), I suspect this is what happened in the first place.
In any case, if you need to edit the file in plain notepad, download "ToFroDos" and run todos on the file before editing,
then edit, then run fromdos on the file, then adb push it back on to the device.
Note on Re-uploading: you may need to execute adb remount rw in order to upload the file.
In any case, short form:
1. Boot to recovery
2. adb pull /system/build.prop
3. Edit locally (Making sure to keep the proper newline format (\n))
3.5 adb remount rw
4. adb push ./build.prop /system/build.prop
Click to expand...
Click to collapse
How do I do ADB pull/push if I can only get to the stock recovery screen? (The one with Mr. Android on his back with the ! above him)
BTW, I'm on a Note 3
Check the permissions!!!!!
The build.prop file should have 644 permissions.
Check if it fits, else change them using adb.
See other thread
http://forum.xda-developers.com/showthread.php?t=1927198
Hey guys, so I am trying to unlock my bootloader and cmd tells me: can't find "CIDGen.apk" to install. I edited the environment path and directed it to the proper directory with the APK and all of the ADB stuff. I deleted the runme.sh and CIDGen.apk and downloaded a new one to put in there but I still get the same thing. It is not zipped and my path is correct. Please help
Type
CD xxx
Where xxx is the full path to the directory containing the files.
Ok I typed that in. It shows the file directory. Now what?
EDIT: I typed in the install command and it worked!!! Thanks a bunch
Everything went fine. Thanks
Does anyone know how to use linux to push an original sh file or even just the whole bin folder?
I am unable to use the shell command in adb because I really messed that up by replacing my bin folder with another phones bin folder (same phone make and model - Samsung Proclaim).
(whoops, as you can tell I don't understand much about the system files and therefore I shouldn't be messing with them but my phone was stuck in a bootloop and I got google happy and desparate)
But I've read a few things about possibly using linux to get in there and put the originals back. I have been using linux for a short while but I lack the skills necessary to do this.
Does anyone know if this is something that I can learn to do in a few days or is this something that only years of experience can accomplish?
I'm willing to search and read whatever is necessary I just need a push in the right direction.
Download Stock ROM
Open and decompress zip file (or whatever)
not just adb push the sh executable but all /system folder
remount /system
Code:
adb remount
Code:
adb push ./STOCK_DECOMP/system /system
if you get errors on copying app, just copy each internal folder one by one
at least i got internal shell on a Kindle doing this way (just copying an original sh didn't resolve my problem), but all environment was a little messy.
good luck.