Develop Bugs

Ubuntu/Debian install for Slide

Ok so the ubuntu install now works on slide credit goes to eratosthene he updated all the files to make it work all other credit goes to the dev’s listed on the links provided. FYI this was tested on eugenes latest froyo rom.
1. Go to http://nexusonehacks.net/nexus-one-hacks/how-to-install-ubuntu-on-your-nexus-oneandroid/ download the ubuntu.zip file .
2. Unzip to a location on your pc to a folder named ubuntu.
3. Download the ubuntu-slide-v2 from here.
4. Unzip the ubuntu-slide-v2 to the same folder you used in step 2.
5. Create a ubuntu folder on the root of your sdcard .
6. Connect your Slide to the pc verify debugging enabled and storage disabled.
7. Adb push the files in the ubuntu folder to the /sdcard/ubuntu.
8. Then adb shell.
9. cd /sdcard then sh ubuntu.sh
Note: At this point, the scripts are now located in /data/local/bin and the mount point is /data/local/mnt
10. sh /data/local/bin/bootubuntu
11. you should now see [email protected]:/#
Note : install completed only do the following if you want to access ubuntu from android vnc app.
12. apt-get update
13. apt-get install tightvncserver
14. export USER=root
15. vncserver -geometry 480x320
16. • Run the android-vnc-viewer app and specify localhost port 5901 .
UPDATE: This is not working on CM 6 , I'm not sure why please help if you know .

That would be sooooo coool
Sent From My HTC Espresso Running Froyo Thanks to eugene373

Tried it but the install fails , may be the script or may be rights to edit the files im not that good with linux yet so im not sure .

Ok thanks, any help would be apriciated . If we can get a procedure that works ill write up a step by step for everyone and maybe make a video how to also.

Just guessing but it's probably because we don't have rw access to /system.
Until we get an unlocked bootloader it ain't happenin...
I could be completely way off though

I think you are right , if i rember most the errors where do to access issue's with files in the system folder. If it is the bootloader what would need to be done to " unlock " it ?

bled82 said:
I think you are right , if i rember most the errors where do to access issue's with files in the system folder. If it is the bootloader what would need to be done to " unlock " it ?
Click to expand...
Click to collapse
An OTA update would unlock it.

So once we get the froyo ota we should be able to follow the same process as the nexus one then ?

i would say "unlikely," i dont see how an ota would unlock the bootloader in any fashion. but i guess he might have been referencing the possibility of someone using the new ota to create an unlocked bootloader. the whole "how could the bootloader be unlocked," question bothers me, i never seem to get a straight answer

aceraider4 said:
i would say "unlikely," i dont see how an ota would unlock the bootloader in any fashion. but i guess he might have been referencing the possibility of someone using the new ota to create an unlocked bootloader. the whole "how could the bootloader be unlocked," question bothers me, i never seem to get a straight answer
Click to expand...
Click to collapse
Once there is an official OTA devs will be able to extract the keys needed to properly sign files I believe.

I thought the engineering build had an unlocked boot loader on it and once we flashed it that was that ?

Here's an updated zip for you guys. The process is generally the same as on the above-linked nexus one version, I just changed the scripts to move a few files to different places. You'll need to download ubuntu.zip from that post as well. Summary:
unzip ubuntu.zip somewhere
unzip ubuntu-slide.zip in the same place, replace all the files
make a directory called 'ubuntu' on your sdcard
adb push all the files in the zip to that directory
adb shell
cd /sdcard/ubuntu
sh ubuntu.sh
At this point, the scripts are now located in /data/local/bin and the mount point is /data/local/mnt
sh /data/local/bin/bootubuntu
You're now chrooted into the ubuntu install. Have fun.

Thanks going to try it now !!!

Does not work get attached error.

bled82 said:
Does not work get attached error.
Click to expand...
Click to collapse
I haven't tried this but based on your error, try this from the shell:
mkdir /data/local/bin
then run the ubuntu.sh again

falken98 said:
I haven't tried this but based on your error, try this from the shell:
mkdir /data/local/bin
then run the ubuntu.sh again
Click to expand...
Click to collapse
I did cd /data/local then ls and bin is listed , ran mkdir /data/local/bin failed file exists . i cant cd /data/local/bin get error cant cd to /data/local/bin

bled82 said:
I did cd /data/local then ls and bin is listed , ran mkdir /data/local/bin failed file exists . i cant cd /data/local/bin get error cant cd to /data/local/bin
Click to expand...
Click to collapse
This is some other script messed up when bin wasn't there and ended up creating a file called bin instead of it being a directory.
rm /data/local/bin
mkdir /data/local/bin

falken98 said:
This is some other script messed up when bin wasn't there and ended up creating a file called bin instead of it being a directory.
rm /data/local/bin
mkdir /data/local/bin
Click to expand...
Click to collapse
Ok getting closer , Thank you very much . Now when i ran sh .data/local/bin/bootubuntu i get error attached .

bled82 said:
Ok getting closer , Thank you very much . Now when i ran sh .data/local/bin/bootubuntu i get error attached .
Click to expand...
Click to collapse
What rom are you using? It looks like you don't have the ext3 module built into your kernel. I set my scripts up to use ext3 (more reliable, I really don't care that it eats into the life of my sd card), but many roms only have ext2. You might try uncommenting the first line of bootubuntu, and changing the ext3 to ext2 on line 10.

eratosthene said:
What rom are you using? It looks like you don't have the ext3 module built into your kernel. I set my scripts up to use ext3 (more reliable, I really don't care that it eats into the life of my sd card), but many roms only have ext2. You might try uncommenting the first line of bootubuntu, and changing the ext3 to ext2 on line 10.
Click to expand...
Click to collapse
I am running froyo using Kanged CM6 newbuild.zip from eugene373 , http://forum.xda-developers.com/showthread.php?t=721515 .

[Q] Boot Screen

Ok so i have looked at all the other posts on how to change the boot screen animation, but none of them seem to work. My phone is running on Android 2.2. Does anybody have any ideas on what i should do?

I JUST did this and it worked for me. I am on the 8/1 2.2 leak as well.
Plug in phone
reboot to recovery
Code:
adb reboot recovery
Once booted in to recovery do
Code:
adb shell
mount -a
It will give you this error. Thats fine (It's just saying it couldnt mount the sdcard which we dont need right now.)
Code:
~ # mount -a
mount -a
mount: mounting /dev/block/mmcblk1 on /sdcard failed: Invalid argument
mount: mounting /dev/block/mmcblk1p2 on /sd-ext failed: No such file or directory
now type exit to get back to your computer prompt.
Now push your bootanimation.zip you want to /system/customize/resource
Code:
adb push bootanimation.zip /system/customize/resource
now now get back in to adb shell and type
Code:
cd /system/customize/resource
then ls *.zip and it should look like this. l = lowercase L
Code:
/system/customize/resource # ls *.zip
ls *.zip
bootanimation.zip VZW_bootanimation.zip
Now we want to rename the vzw boot animation to .back to save it
Code:
mv VZW_bootanimation.zip VZW_bootanimation.back
Then we want to rename the new bootanimation to the vzw bootanimation
Code:
mv bootanimation.zip VZW_bootanimation.zip
OPTIONAL STEP: IF YOU DONT WANT THE DROID SOUND ON BOOT
Code:
mv Droid.mp3 Droid.back
type exit and adb reboot . It should now boot with your new boot animation.

Ok so i just did that twice and every time i try to all it does reboot my phone and its all the same nothing changed

Check where I've been posting. Somewhere along the way I was in a thread that worked for me. I just can't remember where.

Utopia73 said:
Ok so i just did that twice and every time i try to all it does reboot my phone and its all the same nothing changed
Click to expand...
Click to collapse
so you have a bootanimation.zip downloaded to the folder you have adb at? and you followed my steps EXACTLY?
So is it still just showing the stock boot animation?

zerf said:
so you have a bootanimation.zip downloaded to the folder you have adb at? and you followed my steps EXACTLY?
So is it still just showing the stock boot animation?
Click to expand...
Click to collapse
Yes i have everything in the right spot, and followed the steps exactly. I did once more and the animation was gone, now all there is, is a black screen.

Utopia73 said:
Yes i have everything in the right spot, and followed the steps exactly. I did once more and the animation was gone, now all there is, is a black screen.
Click to expand...
Click to collapse
boot your phone to recovery and then adb shell then run this for me and paste in your output.
Code:
ls -l /system/customize/resource/*.zip

zerf said:
boot your phone to recovery and then adb shell then run this for me and paste in your output.
Code:
ls -l /system/customize/resource/*.zip
Click to expand...
Click to collapse
Ok did that. Nothing happened

sorry forgot to tell you to either run mount -a or go in the partitions menu of your phone and mount /system

zerf said:
sorry forgot to tell you to either run mount -a or go in the partitions menu of your phone and mount /system
Click to expand...
Click to collapse
Ok sweet that worked! Although its not the animation i downloaded hmm... oh well this one is cool too.

Utopia73 said:
Ok sweet that worked! Although its not the animation i downloaded hmm... oh well this one is cool too.
Click to expand...
Click to collapse
haha ok.. not sure how you got an animiation you didnt download.... but glad its working. Im guessing you missed the step at the top of my instructions that says mount -a after you adb shell in the first time but anyway let me know if you have any more issues.

zerf said:
haha ok.. not sure how you got an animiation you didnt download.... but glad its working. Im guessing you missed the step at the top of my instructions that says mount -a after you adb shell in the first time but anyway let me know if you have any more issues.
Click to expand...
Click to collapse
Well i saw that...maybe its another mount but instead of mounting in prompt i just went to the partitions menu and did it there. Thank you very much!

Ok i have one last question.
So now that the boot screen has been changed this is what i get when i try to change it again...
Code:
cannot stat 'bootanimation.zip' : No such file or directory
And i can see the file in the folder....so now what?

Utopia73 said:
Ok i have one last question.
So now that the boot screen has been changed this is what i get when i try to change it again...
Code:
cannot stat 'bootanimation.zip' : No such file or directory
And i can see the file in the folder....so now what?
Click to expand...
Click to collapse
where are you seeing this (what directory) and what command are you trying to run?

Not sure what version of 2.2 you're running. I know on SkyRaider you can't put your boots in resource anymore. They now reside in /system/media. You'd need to:
Code:
adb push bootanimation.zip /system/media/
You can also push a custom sound to the same folder, outside of the zip. I'll also take this as an opportunity to shamelessly plug the boot animation I created for SkyRaider. It can be found in the Goodies section of ROM Manager.

zerf said:
where are you seeing this (what directory) and what command are you trying to run?
Click to expand...
Click to collapse
I was trying to run
Code:
adb push bootanimation.zip /system/customize/resource
Ok, now its saying
Code:
adb push bootanimation.zip /system/customize/resource
failed to copy 'bootanimation.zip' to '/system/customize/resource/bootanimation.zip': No space left on device
So maybe i tried to many times or something.

vbhines said:
Not sure what version of 2.2 you're running. I know on SkyRaider you can't put your boots in resource anymore. They now reside in /system/media. You'd need to:
Code:
adb push bootanimation.zip /system/media/
You can also push a custom sound to the same folder, outside of the zip. I'll also take this as an opportunity to shamelessly plug the boot animation I created for SkyRaider. It can be found in the Goodies section of ROM Manager.
Click to expand...
Click to collapse
I tried that too, now its saying
Code:
adb push bootanimation.zip /system/customize/resource
failed to copy 'bootanimation.zip' to '/system/media/bootanimation.zip': No space left on device

Not sure what version of 2.2 you're running. I know on SkyRaider you can't put your boots in resource anymore. They now reside in /system/media. You'd
Click to expand...
Click to collapse
I tried that too, now its saying
adb push bootanimation.zip /system/customize/resource
failed to copy 'bootanimation.zip' to '/system/media/bootanimation.zip': No space left on device
Click to expand...
Click to collapse
You have to push it while in Recovery until we have s-off/full NAND. If you're already doing it in Recovery, make sure you've mounted /system first.
Sent from my ADR6300 using XDA App

[OOPS!] bootloop due to adb push /data/app/<file>.apk, can not delete :(

Hello guys,
I probably did a stupid thing. I could'nt install an apk and figured that I could just push it to my android and see what happens. I didn;t think I would get in a bootloop though .
I had astrid.apk, it's modified so it is transparant. I could not install it in Android.
What i did:
Reboot in recovery
Did the fake flash to start Clockwork mod
Connect the Android to my pc with an USB cable
adb push astrid.apk /data/app
I read that about 1.2MB was written so I guess that went right.
Did I forget a / ?
Is the map app overwritten?
Well, next thing I did was a reboot and now I'm stuck in a bootloop.
I tried to delete the file (rm /data/app/astrid.apk, rm -r /data/app/astrid.apk). But it could not find file or directory.
I did this from the shell i starten with adb shell. And I tried it with adb shell rm ...
Did I screw up that /data/app map? What to do now?
edit:
I can do cd data. But when I do cd app (when in /data) then it says "you can't cd to app"...

it's adb shell, and while you are in there, press cd /data/app. while in the data folder, press 'ls' to list all entries. usually apk's have different names and stuff. look for the app and then press rm /data/app/... .apk
Make sure you are in recovery and have system mounted.

djind said:
it's adb shell, and while you are in there, press cd /data/app. while in the data folder, press 'ls' to list all entries. usually apk's have different names and stuff. look for the app and then press rm /data/app/... .apk
Make sure you are in recovery and have system mounted.
Click to expand...
Click to collapse
"can't cd to /data/app"
img824.imageshack <remove> .us/img824/5049/shellz.jpg
edit:
I think I have overwritten the whole app map with the file astrid.apk, d*mn.
"adb push astrid.apk /data/app"

I would say, just wipe and start over..
This is how I usually do the stuff:
adb remount
adb shell
cd /data/app
ls
look for app to remove
rm ....apk
I am no pro, wipe is easy!

I made a complete nandroid backup this afternoon, I just did a partial restore, "data" and everything works fine again!
Thanks for helping. Lesson learned:
Linux != Windows (a whole map is easily overwritten with a file).

I doubt that you have overwritten a folder with a file. But good that everything is ok now.

djind said:
I doubt that you have overwritten a folder with a file. But good that everything is ok now.
Click to expand...
Click to collapse
I did a cat /data/app and i saw a lot of strange things, also strings and it was clear i saw the contents of astrid.apk. SO I really think I did.

[Q] Temporary Nand Unlock

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.

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]