Develop Bugs

[Thinktank] Root

I know Paul over at MoDaCo announced he has root but I think that should not prevent us from trying to figure it out ourselves.
I have been fiddling around with the device and its filesystem and, as some might have tried, most commands are very restricted and you can't even list the /system folder.
Recently I found a directory which has write permissions and installed busybox there through adb, here are the instructions:
Download a precompiled busybox binary from http://benno.id.au/blog/2007/11/14/android-busybox
Push it using adb: adb push busybox /data/local/rights
Start a shell: adb shell
Change directory to the folder: cd /data/local/rights
Give it execution permissions: chmod 755 busybox
Play around with it: ./busybox ls /system
Figure out how we can use the new capabilities to root the phone
Any thoughts?

I was trying something also.. although I dont really know what I am doing mostly, I was trying to use some kernel exploits to get root access without luck. Good learning experiece though..
It would be nice if he gave a hint..

[Q] youtube app porting help!!! please!!!

can someone please post DETAILED isntructions to put froyo or gingerbread youtube app thing on samsung epic 4g. ive tried so many time and cant do it. and i delted the stock youtube app with titanium but cant install the other app and i dont wanna pay for root explorer cuz idk if its gonna help at all. i tried using the cmd promt but it says permission denied everytime and it also says adb is not recognized as an internal storage.. PLEASE SOMEONE HELP MEEE I DONT HAVE A YOUTUBE AP AT ALL NOW!!!!!

betterment66 said:
can someone please post DETAILED isntructions to put froyo or gingerbread youtube app thing on samsung epic 4g. ive tried so many time and cant do it. and i delted the stock youtube app with titanium but cant install the other app and i dont wanna pay for root explorer cuz idk if its gonna help at all. i tried using the cmd promt but it says permission denied everytime and it also says adb is not recognized as an internal storage.. PLEASE SOMEONE HELP MEEE I DONT HAVE A YOUTUBE AP AT ALL NOW!!!!!
Click to expand...
Click to collapse
The new YouTube.apk just needs to be placed in '/system/app'. What I did was remove the original YouTube.apk and put the new one in its place and voila. Here is the method adapted for Windows (I think it's all right for Windows). This is also assuming you rooted with a one click root that included the remount script and that you have adb on your computer (the one click rooter should have adb included with it).
1. in the cmd prompt, go to the folder where you have adb and type:
Code:
adb.exe shell
2. inside shell:
Code:
$ su
# remount rw
# mkdir /sdcard/backup
# cp /system/app/YouTube.apk /sdcard/backup
# rm /system/app/YouTube.apk
# exit
$ exit
3. now in the cmd prompt again:
Code:
adb.exe push \path\to\YouTube.apk /system/app
4. Reboot the phone.

gremlyn1 said:
The new YouTube.apk just needs to be placed in '/system/app'. What I did was remove the original YouTube.apk and put the new one in its place and voila. Here is the method adapted for Windows (I think it's all right for Windows). This is also assuming you rooted with a one click root that included the remount script and that you have adb on your computer (the one click rooter should have adb included with it).
1. in the cmd prompt, go to the folder where you have adb and type:
Code:
adb.exe shell
2. inside shell:
Code:
$ su
# remount rw
# mkdir /sdcard/backup
# cp /system/app/YouTube.apk /sdcard/backup
# rm /system/app/YouTube.apk
# exit
$ exit
3. now in the cmd prompt again:
Code:
adb.exe push \path\to\YouTube.apk /system/app
4. Reboot the phone.
Click to expand...
Click to collapse
ok i get to remount rw but the when i type in the nect code it says
mkdir falied for /sdcard/backup read-only filesystem

I install it using terminal emulator.
All I do is type
Su
#rm /system/app/YouTube.apk
#cp /sdcard/DirectoryWithTheYoutubeApp/YouTube.apk /
system/app
Or after you rm, just use the "My Files" app and go on your sdcard and click YouTube.apk and it'll install and work fine. But remember to sign out of youtube before you close it by going to your page and clicking sign out or else it'll keep force closing after you start it up.
I hope I helped...
Sent from my SPH-D700 using XDA App

you guys are gonna freaking kill me. ALL THE TROUBLE I WAS HAVING WAS BECAUSE I HAD MY SDCARD MOUNTED THE WHOLE TIME I WAS TRYING TO DO THIS THE MINUTE I TRIED IT WITHOUT IT BEING MOUNTED IT WORKED...IM SO DUMB!!!!! LOL BUT THANKS FOR THE HELP ALL OF U!!!!!! U GUYS ROCK!!!! N SO DOES THE NEW UTUBE APP .....BTW I UNDERSTAND UR NOT SUPPOSED TO SIGN IN TO IT RIGHT???

I just uninstalled the original, put the modded youtube.apk in the SDX backup folder and installed (restored) it with SDX stock app remover. Simple, fast and no typing required.
Glad you got it worked out though.

me 2!!! this app rocks

Glad it's working! Having the SD card mounted while trying to adb is a common mistake and always a good first troubleshooting check.

[Q] Bloatware Help

I rooted my Evo, running Fresh's newest update but I have a question about removing bloatware. There are a bunch of apps that I don't want or need, but most of them are defaults and I can't remove them. I've tried using Titanium's default app removal software but when the phone reboots, it's all still there. Anybody know an easier way to remove it other than taking the ROM on my computer and removing the apk's before sending it to my SD card?

You can remove using Root Explorer if you have it. It's a paid market app.
I prefer the below methods:
If you installed the Android SDK you should be able to use ADB to remove system apps.
ADB:
adb remount
adb shell
cd /system/app/
rm appnameyouwanttoremove.apk
adb reboot
Terminal Emulator is a free app on the market that also works great. Here is the code to enter when in TE:
TERMINAL EMULATOR:
su
cd /system/app/
mount -o remount,rw /dev/mtdblock3 /system
rm appnameyouwanttoremove.apk
reboot
DONE AND DONE!

Terminal Emulator "not found"

I'm trying to use Terminal Emulator and no matter what I try to enter it tells me its not found. I am rooted and it has been given SU rights. I've also tried to uninstall and reinstall but nothing works. Any ideas?

presumedsublime said:
I'm trying to use Terminal Emulator and no matter what I try to enter it tells me its not found. I am rooted and it has been given SU rights. I've also tried to uninstall and reinstall but nothing works. Any ideas?
Click to expand...
Click to collapse
I don't quite understand your issue here. Are you trying to launch Terminal Emulator and get this message?
A few things to try:
1. Clear Terminal Emulator's cache and data, retry.
2. Uninstall, restart, install again, retry.
Alternative route: Install Connectbot and do what you need to do.

I'm trying to get to cd /system/etc/init.d but each time i type it in it says "cd /system/etc/init.d: not found:

presumedsublime said:
I'm trying to get to cd /system/etc/init.d but each time i type it in it says "cd /system/etc/init.d: not found:
Click to expand...
Click to collapse
Just did it on my phone using Connectbot and no issues. I don't know.
Would anyone else like to chime in with assistance?

Okay connect bot worked but now it won't let me run "remount rw". It says "mount: can't find rw in /proc/mounts

Try "mount -o remount,rw /system" or similar
And it could be possible the init.d directory isn't there...
sent from my miui-ified epic

Thanks for your help. I was trying to copy a file to the system/etc/init.d directory through emulator since I've never done it before. Decided to save some time and use Root Explorer.

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]