Develop Bugs

Framework push not working

Well. Im just trying to do a little modding like notification bar.etc. nothing to wild. I have skyraider mod and i pulled the framework and added the bar color and pushing it back to the phone nothing happens. I've used abd and emulator but nothing seems to overwrite the main one. I tried the reboot recovery but no luck. Im lost and clueless what to do next. Oh the files are the correct name and png. Please help.
Sent from my droidinc

dadsterflip said:
Well. Im just trying to do a little modding like notification bar.etc. nothing to wild. I have skyraider mod and i pulled the framework and added the bar color and pushing it back to the phone nothing happens. I've used abd and emulator but nothing seems to overwrite the main one. I tried the reboot recovery but no luck. Im lost and clueless what to do next. Oh the files are the correct name and png. Please help.
Sent from my droidinc
Click to expand...
Click to collapse
Try going into recovery, mounting the system folder then go to the command prompt and type adb shell (make sure phone is connected to PC) then cd /system/app and then rm framework-res.apk after that type exit to leave the shell and then try your adb push framework-res.apk /system/app

So framework-res.apk/system/app? Sorry i get confuse tere are so many commands in my head that im confusing some lol been at this for a while now sorry for the slow process intake. When i push i type
C:/ adb push /sdcard/framework-res.apk /system/framework/framework-res.apk. im sorry to ask can you type in the command what you would use. Please. Thx again
Sent from my DROIDINC using XDA App

Boot the phone (volume - and power)
wait for the file tests to complete,
switch to recovery,
mount the system partition,
connect the phone,
then open a cmd window on the PC
cd to the folder the apk file is in on the PC.
adb push framework-res.apk /system/framework/framework-res.apk
Disconnect the cable, unmount the system partition, and reboot the phone.

Thx alot. Im sure its te same as clockwork recovery. To do the recovery option. Thx again
Sent from my DROIDInc using XDA App

Not sure what im doing wrong. I mount the phone using recovery. Type in adb shell. Everything connects. Then goes into a # sign.
I type in. Cd c:/androidinc (that's where my framework-res.apk is) but it doesn't change anything it doesn't recognized the file or the path. Doesn't make sense. I tried abd remount and says successful then i do a . Abd push /system/framework/framework-res.apk then just a regular menu comes up when you type just abd. Soooo any help would be great. And i've tried the method on previous post.
Sent from my DROIDinc using XDA App

dadsterflip said:
Not sure what im doing wrong. I mount the phone using recovery. Type in adb shell. Everything connects. Then goes into a # sign.
I type in. Cd c:/androidinc (that's where my framework-res.apk is) but it doesn't change anything it doesn't recognized the file or the path. Doesn't make sense. I tried abd remount and says successful then i do a . Abd push /system/framework/framework-res.apk then just a regular menu comes up when you type just abd. Soooo any help would be great. And i've tried the method on previous post.
Sent from my DROIDinc using XDA App
Click to expand...
Click to collapse
You don't need to go into adb shell. If you do then the cd or any other PC command will not work since it is trying to do it on the phone..
So, just go into recovery, mount system then cd to you PC folder and do the adb push

Hold shift and right click anywhere in the c:/androidinc folder (assuming you are using windows). Select "Open a new command window here". Make sure you mount the system partition in clockworkmod recovery. Now type the following command:
adb push framework-res.apk /system/framework/
After it pushes, unmount the system partition and reboot the device.
Should be good to go from there.

Can't move any apk into /sys/app using root explorer

Hi guys I want to install keyboardmanager by installing from /sys/app try as I may i just can't move any apk into the root sys folder. Have read write permission in the folder but after paste or copy request the file remains on the sd. Can copy files from sd to /.
Have searched and searched but can't find out why I can move files to this path. I need access as would like to remove some stock apps also.
Rooted with evoke and am running a desire with cyanogen 6.1.0 stable and clockwork mod recovery 2.5.0.7
Any help would be much appreciated.
Q&ASent from my GT-P1000 using XDA App

Are you S-OFF?
If not you do not truly have RW access, just the appearance of it in File Explorer.
Try booting into recovery and using adb to move it, or go through the steps to S-OFF.

Try copying it to /system/app/
Not /sys/app/...wrong place.

Mercianary: I think he used sys as short for system.
To answer the question. The desire is nandlocked so even with root you can't write to system while it is booted. You need to hack the phone on bootloader level (get s-off) to gain this write access.

@cwakerly From what i understand, you are trying to install an apk from your sd card to /system/app while the phone is on and running? As suggested above, you cannot do this via a File Explorer app unless you have full root to the /system partition (S-OFF). Try it via ADB instead and follow these steps:
Perform a Nandroid backup first just incase anything were to go wrong.
1. You need to have USB Debugging enabled, HTC Sync and Android SDK installed (http://developer.android.com/sdk/index.html).
2. To get adb running on the Windows OS platform, for example, download & extract the Android SDK to the following path: C:\android-sdk-windows.
3. Turn on your phone and connect it to your PC via a USB port, and then boot into Recovery mode..
4. Instead of placing the apk onto the SD card, place it into C:\android-sdk-windows\tools in Windows.
5. Open command prompt and type cd C:\android-sdk-windows\tools, hit enter.
6. Type adb shell mount /system, then hit enter, to mount the /system partition.
7. Type adb push keyboardmanager.apk /system/app, hit enter.
8. Type adb reboot.
Let me know if that is what you meant and if it works for you.

Hey guys thanks so much for suggestions will try them and let you know if it works
Sent from my HTC Desire using XDA App

hi i have installed sdk, htc sync and java plug ins.
using command line when i try to run adb shell mount /system command i get the following error message:
'adb' is not recognised as an internal or external command. operable program or batch file.
any ideas what's happing here?

Have you navigated to the tools folder of the sdk?
Mine is C:\android-sdk-windows\tools
Yours maybe something similar....
Sent from my HTC Desire using XDA App

cwakerly said:
hi i have installed sdk, htc sync and java plug ins.
using command line when i try to run adb shell mount /system command i get the following error message:
'adb' is not recognised as an internal or external command. operable program or batch file.
any ideas what's happing here?
Click to expand...
Click to collapse
try it in smaller chunks, type adb shell, you will then get a # sign, now type mount /system

hi have navigated to tools folder of sdk, still the same error message. when i type adb shell i get the same error!

If you have latest sdk you need the "other" tools folder. I'm not at my pc so I'm not sure the exact name.
Sent from my HTC Desire using Tapatalk

if you haven't got it done yet use this update.zip
open the zip then put the apk you want to install in /system/app then zip it back up. it wont be signed so turn off signature verification in recovery before you flash it.

Hurray using the update zip worked!! Thank you everyone for your help on this
Have a great Christmas.
Craig
Sent from my HTC Desire using XDA App

[Q] Can not install foreign language fonts on Desire.

I rooted my phone and have a gingerbread rom on it. I have tried to install dejaVu fonts on the Desire, I followed the Droids instructions but that didn't work. How can I install the fonts? Please help.

Narekrocks said:
I rooted my phone and have a gingerbread rom on it. I have tried to install dejaVu fonts on the Desire, I followed the Droids instructions but that didn't work. How can I install the fonts? Please help.
Click to expand...
Click to collapse
Do you have s-off? If so, you can use Font Changer Lite from the Martetplace to achieve this, otherwise, if you do not have s-off, then you can only r/w to the /system partition while in Recovery Mode using ADB commands.
To do this via ADB, you first have to install the Android SDK - http://dl.google.com/android/installer_r08-windows.exe (for Windows)
You do not require the API's in the download.
Once downloaded, it will most likely be extracted to the following path: C:\Program Files\android-sdk-windows.
Important: Perform a Nandroid Backup (which you can later restore just incase anything goes wrong during this procedure).
Now, with your dejaVu fonts (.ttf files), rename each one to Arial, for example:
DejaVu.tff renamed to Arial.ttf
Dejavu-Bold.ttf renamed to Arial-Bold.ttf
... and so on.
Now, place your renamed font files into C:\Program Files\android-sdk-windows\tools
Connect your phone to your PC via USB and access Recovery Mode from your phone.
We are now going to overwrite the existing Arial fonts (system default fonts) with your Arial (DejaVu) fonts by pushing them from the android-sdk-tools folder, to the phone, in /system/fonts.
Open a command prompt window and type the following:
cd C:\Program Files\android-sdk-windows\tools, hit enter.
adb shell mount /system, hit enter.
adb push Arial.ttf system/fonts, hit enter.
adb push Arial-Bold.ttf system/fonts, hit enter.
... and so on.
adb reboot

[Q] I can't change the fonts in my rooted android

Hi,
I have my rooted htc desire with a custom rom (Oxygen).
I'm not able to change the fonts in /system/fonts. I used adb, but I get error!!
I tried this
> adb remount
> adb push ./DroidSans.ttf /system/fonts
> failed to copy './DroidSans.ttf' to '/system/fonts/DroidSans.ttf': Directory not empty
Any advise??

Try using absolute system.
But ADB thinks you're trying to move the font to a location that points to a file and not a folder, what I would do is
adb remount
adb push [drag the file into the terminal/cmd window, location will appear] /system/fonts/
and you're done.

It didn't work
I got the same error

sahaf525 said:
Hi,
I have my rooted htc desire with a custom rom (Oxygen).
I'm not able to change the fonts in /system/fonts. I used adb, but I get error!!
I tried this
> adb remount
> adb push ./DroidSans.ttf /system/fonts
> failed to copy './DroidSans.ttf' to '/system/fonts/DroidSans.ttf': Directory not empty
Any advise??
Click to expand...
Click to collapse
I did not go through all that drama, use an app called type fresh once rooted and i was gold!
just do a search "type fresh app" the first hit has details, sorry cant post links yet

I got this error message:
Error remounting
Could not remount /system
Any way,, I changed the fonts before flashing the rom to my phone & it worked with me
Many Thanks,,,

I use Font Changer.
It works like a charm!
If that helps. (I have to reboot each time i want to instal a new font and i use oxygen too).

can not mount system in read-write mode using adb without recovery mode

I wanted to change my device model, so I copied build.prop from another mobile to my mobile. I am already rooted. But unfortunately I did not change the o.s. from gingerbread to froyo in build.prop ( I have android 2.2 FROYO) When I rebooted, there were many errors. It is now showing no sim card. Mobile network search gives error. Effectively, I can not use the mobile. Terminal emulator, X-plore etc. stopped working. Only Rom toolkit free version works and astro file manager works. Other programs are forcefully closed. Needles to say, I must replace new build.prop with new one.
Using adb I can only pull files but can not write as it is in read only mode.
adb root and adb remount works only if you are in recovery mode ? Y mobile does not have any custom recovery so when I boot in recovery mode it hangs.
Superuser has installed su in system\bin directory. But from adb shell I can use su also. It gives permission denied error. Hence I can not remount the system.
I have read similar threads and found that on some mobiles adb root or adb shell su works but on some not.
I am using Vista 32 bit with admin rights, still can not use root in adb.
Please tell me, how can I mount system read-write. I can not install root explore as google play and even internet is not working.
Please help.

maheshchavan said:
Using adb I can only pull files but can not write as it is in read only mode.
Click to expand...
Click to collapse
activate USB debugging then in console
Code:
adb shell
su
mount -o rw,remount /dev/block/mmcblk0p1 /system
adb push build.prop /system/build.prop
check where is your build.prop

ruscan.calin said:
activate USB debugging then in console
Code:
adb shell
su
mount -o rw,remount /dev/block/mmcblk0p1 /system
adb push build.prop /system/build.prop
check where is your build.prop
Click to expand...
Click to collapse
OMG ruscan.calin i COULD KISS YOU! I had tried to change my OG EVO 4G's buildprop file to another phone so that I could purchase & download an incompatible Google Play app. However after I restarted the phone wouldn't start! It would boot into my rooted HTC EVO 4G Android 2.3.3 and HTC Sense 2.1 but it would get stuck on the wallpaper with just the notification bar at the top and all buttons would be frozen. However I noticed when I plugged in my phone to my computer via usb the computer recognized it. I always keep my phone with USB debugging enabled so I thought I should be good right? I have spent the last 4 hours trying to install and setup adb with no real previous experience with it. I am familiar with dos from years ago and that helped me as it's basic procedure, commands, etc. Then I found out how to install the HTC drivers which I needed and then download the Android SDK with adb that's included which many guides show easily. I started the command prompt (cmd), typed my adb devices command and hurray it showed my phone! I connected and quickly navigated to the build.prop system folder! Luckily when I changed the file I made a bak backup and left it in the same folder. Now the main issue was figuring out how to change the naming of the files which I did via usual adb commands (mv build.prop.bak build.prop). But then to no avail I couldn't get it to write due to it being a system read only folder! Arg! Then I found your post on here, above, and typed it in simply leaving out the adb push portion and replacing that with the mv file command instead and first changing the name of the bad file and then replacing the bak file as the good copy! I exited back to the adb main and unplugged my phone. Moment of truth and man was everything flashing through my head at once! I booted up and YESSSSSSSSSSSSSS, it worked! I went back into root explorer and got rid of the offending leftovers and I've learned my lesson! I just don't want to think about what would have happened if I hadn't found this post. Thank you and if anyone else makes this hug mistake let me know and maybe I can help. Moral of the story don't mess with the build.prop or any system folder unless you know what you're doing! Thanks again!
Quick Guide to Fix Android "build.prop" Issues:
1. Find and download USB drivers for your phone by model or type (HTC EVO 4G's HTC Fastboot drivers): http://downloads.unrevoked.com/HTCDriver3.0.0.007.exe
2. Download and install Android SDK and choose adb: http://developer.android.com/sdk/index.html
Guide: http://htcevohacks.com/htc-evo-hacks/how-to-install-android-sdk-and-adb-drivers-for-htc-evo-4g/
3. Run a command prompt from the "c:/program files/android/android-sdk/platform-tools/" directory. I had to copy the command prompt to get it to open there but sometimes a right-click action will do it. The guide below will help just navigate down to "Using ADB" and skip the rest.
Guide: http://www.howtogeek.com/114667/how...y-default-move-almost-any-app-to-the-sd-card/
4. Once you open the command prompt and you're in the "c:/program files/android/android-sdk/platform-tools/" foler type "adb devices" and your device should appear. If it does move on to next step.
5. Then type adb shell and use the ls command to see directories. Then you'll need to navigate to the system folder by typing "cd system" and then type "ls" to look around in the directory (similar to "dir" in DOS). You should now see the bad build.prop file.
6. You'll need to rename the file or push a correct version. First you need to use the "adb shell" command again and then "su" and finally "mount -o rw,remount /dev/block/mmcblk0p1 /system" to make the directory writable (see ruscan.calin post above for additional info).
Note: I only had to rename my build.prop as I already had my old one in the same system folder. You may have to copy the bad build.prop to your computer, edit it and then push it back to the same system directory. These directions are only for renaming files in the same folder. For the info on how to copy the file to your computer and push it back to your phone go to step *10 below or use the guide below it.
7. I already had the bad build.prop in the system directory with my old one which I had named build.prop.bak. If you have this too simply rename by changing the name first of the bad file to anything by typing "mv build.prop build.prop.bad" or similar.
8. Next rename the build.prop.bak to build.prop by typing "mv build.prop.bak build.prop". Everything should go smoothly and move onto the next step.
9. Finally, If no error messages are found, simply type "adb reboot" or "adb shell reboot" (Depending which version of ADB you have). You should be done, your phone will reboot like normal (working, lol) and everything should be working again! YAY!
*10. To copy the build.prop to your phone type "adb pull /system/build.prop c:\" and the file should be placed in the main c:/ directory on your computer. Navigate to the root (c:/) directory and then right click and "open with" the "build.prop" file using a notepad or other file editor. Then use the text editor (Notepad, etc) to change back what you originally changed to mess everything up. There is tons of stuff on the net to let you know what to fill back in depending on your phone model/type. Or it's possible to get a previous version from an old Nandroid backup or similar. Save the changed text file and make sure its named the same "build.prop" and make sure it's still in the root directory (If you're having issues on this step or just want more insight check out the guides and threads below for more help).
Guide 1: http://androidforums.com/admire-all...p-computer-not-phone-using-root-explorer.html
Guide 2: http://www.modaco.com/topic/328943-quick-guide-to-modifying-buildprop-with-adb/
Guide 3: http://forums.androidcentral.com/sp...-replaced-build-prop-phone-wont-start-up.html
*11. We've already made the directory writable in step 6 so we simply need to push the file back to the phone. If any error message appear re-do step 6 to make writable again. Otherwise push the modified file back to the phone by typing "adb push c:\build.prop /system/". Back to step 9 above! Yay!
If anyone wants to help cleanup this quick guide or make any changes feel free. I just wanted something so that if anyone else has this issue they won't have to worry or search forever to find a solution. OMG it's 2:30AM, to bed... I ride! LOL
Enjoy,
5th :highfive:

THANK YOU!!! Totally saved me today.
One thing that I noticed. After pushing the correct build.prop, I had to fully power down, then turn back on my Razr for it to load up the fixed build.prop.

error message,Help please
Hello, when i am going to mount and change the permission i am getting constant error od device not found or sh:not found.
What to do?Help me please?

jigarpattani said:
Hello, when i am going to mount and change the permission i am getting constant error od device not found or sh:not found.
What to do?Help me please?
Click to expand...
Click to collapse
What step are you on? What phone do you have? More info please?

i am have problem whit my pantech flex i need to use the build.prop.bak but when i type the su it stay in blank do nothing any ideas pls help

ehy there hope someone can help me...i have an archos 97b platinum, messed up with build.prop. So i pulled out and restored but can't push in any way. I have a cwm installed, tablet rooted but i alwais got "permission denied" at push command. Other error is operation not permitted" if i try remount command from adb. i can do mount -o rw,remount /dev/block/mtdblock7 /system but after that push still give me permission denied.
any suggestion?
http://imgur.com/FDLp4fl
i open a 2nd cmd, give the mount -o rw,remount /dev/block/mtdblock7 /system , and system is now rw, but from the first cmd when i give "push build.prop /system (or /system/build.prop) it will always return me permission denied
help

dev.block
i want to view to dev/block using adb shell #
eg . what block is boot.img
what block is recovery.img
what block is system.img
what block is cache.ing
adb shell getprop mtd is not work . Pls Help Me & sent to mail [email protected]