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.
Related
Hi Guys,
I am new to this stuff and I am having problems with entering commands for certain stuff.
So, I rooted my Desire and I wanna change the virgin mobile boot image that comes up after the white HTC screen during the booting process and I found the info on the forums here but I am just not getting the last part.
I get into the recovery and all that but where do I type in this command? I tried using the run function on my PC and typed in cmd to open a Command Prompt but after that if I type that stuff in, it doesn't work.
I'd really appreciate if someone can help because it seems like this typing command stuff seems necessary in a lot of the things that I'd like to do with my phone.
Thnx in advance
--------------
How to change boot animation
1. You need to have HTC Sync and Android SDK installed
2. Copy bootanimation.zip to SD Card
3. Turn off Desire and then turn it on while holding back button to enter bootloader(white screen)
4. Once in "white screen" press power button again to enter bootloader
5. Connect Desire with PC
6. Press Volume Down and than Power to enter Recovery
7. Open Command prompt/Terminal and type
Code:
adb shell mount /system
adb push C:\bootanimation.zip /data/local
adb reboot
-----------------
Try the following, may be easier for you:
get adb running (download & extract the sdk, it will be in the tools folder)
the full path will be C:\android-sdk-windows\tools
add adb to path
put bootanimation.zip into the same folder as the adb app (e.g. in the tools folder of the sdk)
open cmd & navigate to the tools folder
adb push bootanimation.zip /data/local
Hey man,
I really appreciate it but I guess I am just not as advanced as some of you guys and your instructions are still not too clear for me. I tried to do what you told me but no luck, so I am guessing I am obviously not doing something right.
Ok, so I got the SDK and extracted but I am not sure what you mean by "Get adb running". Are you referring to the adb.exe file in the tools folder?
And, when I am following your instructions, what stage my phone should be on? In the recovery with the triangle and the ! or just turned on normally?
Sorry for all the hassle man but I really appreciate your help. I am just trying to get a hang of this.
Dodolom said:
Hey man,
I really appreciate it but I guess I am just not as advanced as some of you guys and your instructions are still not too clear for me. I tried to do what you told me but no luck, so I am guessing I am obviously not doing something right.
Ok, so I got the SDK and extracted but I am not sure what you mean by "Get adb running". Are you referring to the adb.exe file in the tools folder?
And, when I am following your instructions, what stage my phone should be on? In the recovery with the triangle and the ! or just turned on normally?
Sorry for all the hassle man but I really appreciate your help. I am just trying to get a hang of this.
Click to expand...
Click to collapse
No, the phone does not need to be in recovery but it needs to be turned on and connected via USB
Open command prompt and type cd C:\android-sdk-windows\tools, hit enter.
Next, type adb, hit enter.
Now, having placed the bootanimation.zip file in the adb SDK tools directory, push it to the phone:
Type adb push bootanimation.zip /data/local in command prompt.
Note: Make sure USB Debugging is enabled on your phone:
Go to Settings on your phone > Select Applications > Select Development > Make sure 'USB Debugging' is checked
thank you so much man. Worked like a charm.
No problem man, its only easy when you know how
Regards,
Mas.
-------------------------------------
Sent via the XDA Tapatalk App
Can be better for all user create the bootanimation.zip inside a update.zip for only flash it. Users not asking, users without problems
Once you a custom rom installed is it possible to install a custom font to your phone?
I've been able to change all my icons with bettercut just want to change the system font now
Sent from my HTC Desire using XDA App
Me too please. I would love to change my system fonts. Just a little bigger
If you are rooted, you can do this if you are familiar with adb commands. The commands would be something similar to this and would be executed while in Recovery Mode with USB connected:
adb shell mount /system
adb shell rm /system/fonts/(font name)
adb push (font name) /system/fonts
adb shell remount
adb shell reboot
Sent from my HTC Desire using XDA App
Thanks Masdroid. I am rooted but not familiar with adb commands. Would you be kind enough to expand a little. I am using windows vista 32 and phone is defrost 1.6
duryard said:
Thanks Masdroid. I am rooted but not familiar with adb commands. Would you be kind enough to expand a little. I am using windows vista 32 and phone is defrost 1.6
Click to expand...
Click to collapse
If you are running Windows, you need to first make sure that you have the Windows Android SDK (http://developer.android.com/sdk/index.html) downloaded and extracted to your computer, use the following path to extract it: C:\android-sdk-windows.
Next, download and place the selected font files to the root of your C: (e.g. C:\[font name])
Then, switch off your phone and boot to Recovery Mode. Once booted into Recovery Mode, first perform a Nandroid backup which you can restore afterwards if anything happens to go wrong. Now, while still in Recovery Mode, open a separate command-line window and then type: cd C:\android-sdk-windows\tools, press enter.
Now type the following commands in adb and hit enter afterwards to execute:
adb shell mount /system
adb shell rm /system/fonts/[font name]
adb push [font name] /system/fonts
adb shell remount
adb shell reboot
The default system fonts that the Desire uses are:
DroidSans.ttf
DroidSans-Bold.ttf
DroidSansMono.ttf
etc. I had some other font (I forget, let's say Helvetica for fun):
Helvetica.ttf
HelveticaBold.ttf
HelveticaMono.ttf
If you rename the Helveticas into the DroidSans names, back up the old fonts somewhere else, and then put your renamed fonts in the /system/fonts folder, it will work. Since we don't have /system write access while in the device, we can't tell Android to look at our different fonts while running - we just have to replace what's there.
I have attached a zip with random the font files I renamed. The non-mono fonts came from a font called Comfortaa; the mono is Vera Sans Mono. These are plug-and-play - back up your old versions of DroidSans.ttf, DroidSans-Bold.ttf and DroidSansMono.ttf and push these to your /system/fonts folder in their place. Replacing DroidSans.ttf pretty much updates everything in the system.
Thanks Masdroid
No worries bud.
Sent from my HTC Desire using XDA App
MasDroid said:
Now, while still in Recovery Mode, open a separate command-line window and then type: cd C:\android-sdk-windows\tools, press enter.
Click to expand...
Click to collapse
What do you mean open a separate command line window, open it where?
And do you know any sites or anything which convert fonts to .ttf?
While your phone is connected via USB and in Recovery Mode (green and black menu), simply open up another command prompt window (Start > Run > type cmd, press Ok). Access adb and execute commands.
Nope, not aware of any sites that convert fonts to .ttf - try Google or Bing
Sent from my HTC Desire using XDA App
did anyone manage to do this? is there not an app or something? like rom manager
Can you tell me how i can do this on mac osx snow leop?
I can't change fonts with root explorer so i want to try with another tutorial..
hello
I have a HTC desire
I am root and in recovery mode, I also copied that are interested in c: \annifont.ttf.
once in the cmd, I type the first line
"Adb shell mount / system" and enter all goes well. For the second,
"Adb shell rm / system / fonts / annifont.ttf" and it goes wrong, he said:
"Rm can not remove '/ system / fonts / annifont.ttf': No such file or directory.
Help, what is the problem??
i must rename the fonts
you can try this app, it's really easy
http://forum.xda-developers.com/showthread.php?t=618019
syfo said:
you can try this app, it's really easy
http://forum.xda-developers.com/showthread.php?t=618019
Click to expand...
Click to collapse
I just wanted to post this too
You have to download HTC Sync (because of the drivers) before you can use this suite on your desire
Hi ! I was trying to change the lockscreen font ( Clockopia.tff ) with Root Explorer ( just renamed the old one and placed another font there ( named Clockopia.tff ofc )), but it resulted in bootloop. So what am I missing here?
A little help would be apreciated! Thought I'd ask in this thread and not create a new one.
EDIT: Found a little program called Type Fresh, installed it to my Desire and changed the font. I was afraid the font was some way corrupted, but I guess not.
Hey all, ive been trying to change my boot screen to the haters gonna hate one for a few days now but cant seem to get it to work at all, i have full root and tried to the fastboot method and recovery/adb method. no matter what it stays the same as the one i had originally, i never get errors when trying to push the files if someone can give me instructions for dummies haha or another method id really appreciate it sorry for being a noob at all this.
I had the same problem
First of all, what rom are you using? Different rooms pull from different places. I might be able to help you out. If you are running cyan6, try this:
Adb reboot recovery
Adb remount (make sure it remounts. Maybe also do adb root to make sure.)
Adb push blahblah.zip /system/customize/resource/bootanimation.zip
Adb push blahblah.zip /system/media/bootanimation.zip
Adb push blahblah.zip /data/local/bootanimation.zip
If you want sound, push that to the same locations. Make sure there is only one of each file in each folder. Then, to check,
Adb reboot
Hope this helps
oh yeah sorry i should have included that i am on evios 1.2 beta 2 rom
I'm not familiar on where to place boot on this rom. Try all three locations I suggested. System customize resource. System media. Data local. Tell me if it works out.
I had this animation on EViO. I just pushed it from my desktop to system/media. Worked fine for me.
how do you push it from the desktop? i tried all 3 methods posted above and none worked. i had the file in the android sdk tools folder though...also whenever i try to do adb remount i get "remount failed:invalid argument" and adb root gives me "error:closed" i tried killing adb and restarting but no luck
This might be an obvious question, but do you have USB debugging enabled on your phone? Under Setting>Applications>Development
You arent going to be able to push anything if you can't get ADB running first.
yeah debugging has been enabled the whole time
ok have you been in recovery mode?
try typing
adb shell
su (make sure #comes up.)
exit (retype until you get back to the tools directory)
then do the push commands to system media, system customize resource, and data local.
Just use this program. Its as easy as it gets.
http://forum.xda-developers.com/showthread.php?t=701295
dkdude36 said:
First of all, what rom are you using? Different rooms pull from different places. I might be able to help you out. If you are running cyan6, try this:
Adb reboot recovery
Adb remount (make sure it remounts. Maybe also do adb root to make sure.)
Adb push blahblah.zip /system/customize/resource/bootanimation.zip
Adb push blahblah.zip /system/media/bootanimation.zip
Adb push blahblah.zip /data/local/bootanimation.zip
If you want sound, push that to the same locations. Make sure there is only one of each file in each folder. Then, to check,
Adb reboot
Hope this helps
Click to expand...
Click to collapse
Putting sound in boot animation doesn't work with cm6. Just to clarify. No one has been able to get it to work unless you found something out to make it work please share as I have hates going to hate also and want to use haters everywhere mp3 and is perfect for it.
Sent from my PC36100 using XDA App
yeah i have also been in recovery mode every time i tried to run a command prompt for adb...i tried that when i hit adb shell i get # but when i type su after the # it says "/sbin/sh: su: not found"
mount: mounting /dev/block/mtdblock4 on /system failed: Device or resource busy
A duplicate file name exists, or the file
cannot be found.
A duplicate file name exists, or the file
cannot be found.
A duplicate file name exists, or the file
cannot be found.
A duplicate file name exists, or the file
cannot be found.
A duplicate file name exists, or the file
cannot be found.
A duplicate file name exists, or the file
cannot be found.
thats what i get when in command prompt when i try to use the program you just posted above
Want a easier way? Use root explorer and copy and paste. Works for my every time. It's in the market. And root explore you can manually turn writeable on and off to move it into system. It's on the top right of screen in root explorer when you go into system folder.
Edit: the command you are tying to put in enables you to push and pull in the system folder. Root explore you can just click a button.
Sent from my PC36100 using XDA App
Good idea
Root explorer works most of the time. If you have the cash, go ahead. You should make site out posted though.
/sbin/sh: reboot: not found
been trying to use adb and i keep on getting that....any of you know a fix?
How do you gain temporary nand unlock? All i wanted to do is copy 2 files into the /system/xbin/bb which doesnt seem to work with root explorer despite super user permission, copy paste just wont work.
Any ideas how to copy paste these 2 files without going to full s-off? Would the adb method work? or any other apk that can do the job?
Thanks in advance for those who can help and any tips is very much appreciated.
In recovery with adb.
TheGhost1233 said:
In recovery with adb.
Click to expand...
Click to collapse
any links to it? a guide perhaps? thanks for the tip.
Make a nandroid before messing with the system partition.
Then:
Code:
adb remount
adb push <file_name> /system/xbin/bb
This is what i think it is just looking at the basic adb commands, here is some more info about moving stuff to the system partition.
TheGhost1233 said:
Make a nandroid before messing with the system partition.
Then:
Code:
adb remount
adb push <file_name> /system/xbin/bb
This is what i think it is just looking at the basic adb commands, here is some more info about moving stuff to the system partition.
Click to expand...
Click to collapse
btw, how do i get to adb with recovery?
You do know that adb is part of the android sdk and not some function/app on the phone?
To get adb working (i hope you already installed it) just boot in to recovery, connect the usb cable, and launch adb via command prompt or terminal.
TheGhost1233 said:
You do know that adb is part of the android sdk and not some function/app on the phone?
To get adb working (i hope you already installed it) just boot in to recovery, connect the usb cable, and launch adb via command prompt or terminal.
Click to expand...
Click to collapse
many thanks! i will try this tommorow.
Use the update.zip I attached in this thread, you don't need to worry about adb then.
http://forum.xda-developers.com/showthread.php?t=885506&page=2
Sent from my HTC Desire using XDA App
Ghettonine said:
many thanks! i will try this tommorow.
Click to expand...
Click to collapse
Ok I did my best, read alot about adb and followed some tips but I just cant seem to get these things working. I need a DETAILED step by step procedure.
I feel such a noob today, can anyone please help?
Basically, I just wanted to copy "ifconfig" and "route" from "/system/xbin" to "system/xbin/bb" and thats it! Im s-on by the way and dont want a full s-off just to copy paste 2 files.
I tried rebooting in recovery with adb and run some commands on "adb shell", many things came out and I have no idea what it ment.
Well many things came out is not such a great description. So i have no idea if something is wrong or something happened which you did not expect.
Boot again in to recovery and connect adb.
The type "adb devices" this should output something like:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
HT##########
If this does not happen you don't have a connection and most likely have driver issues (only if you are on windows). If you do get a connection next thing to do is mount the system partition as read/write. To do this type "adb remount".
The output should be "remount succeeded"
Next type "adb shell"
This should give "#" as output .
Since you know where the files are and where you want them to go type "mv /system/xbin/ifconfig /system/xbin/bb" and hit enter, you don't get any conformation about this. Next type "mv /system/xbin/route /system/xbin/bb"
To check if they go moved correctly type " ls /system/xbin/bb", now you should see the files listed.
Next type "exit" to end the adb shell.
Then type "adb reboot".
If this doesn't work you need to give more info about the errors you get or maybe someone else has a better description.
A completly other method is, if you are able to copy the files to your computer, useing the .zip mercianary linked to, just make sure the system/app folder is empty and that you make the system/xbin/bb folder and place the files in there. Then just follow the instructions.
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]