OK. Pardon Adndroid Noooobness.
I have the device incompatible Android Market problem with NC.
Running CM7
I found two fixes.
1. Set DPI to 160
2. Edit Build.prop to make nook present itself as smamsung *something S*
I downloaded ROM Toolbox and after going through what I think is EVERY icon and setting I cannot find where or how to change the DPI setting.
I have modified the build.prop file using ES File Explorer but cannot get the file to copy back from the sdcard to the system folder. Protected or in use probably. Tried booting to CW to copy but dont know how to do that either.
How can I get actully appy either of these. I have searched but cannot find this answer.
Thanks
How about just reverting to the old market, clearing the market data/cache and uninstalling the market updater app?
did not seem to help for me
Did that as well and that did not work. As soon as I connected to the Market it closed and updated. This was after removing the updater and clearing the cache.
On another note, does anyone have the BN reader.apk and the Kindle.apk. Hope I have that terminology right, and the instructions for installing apk files. Sure I can find those instructions.
Thanks
To edit the file in /system, start up Terminal, become root by typing "su" and remount the /system partition by typing "mount -o rw,remount /system". Then you can edit all you like. When you're done type "mount -o ro,remount /system" or just reboot.
aegrotatio said:
To edit the file in /system, start up Terminal, become root by typing "su" and remount the /system partition by typing "mount -o rw,remount /system". Then you can edit all you like. When you're done type "mount -o ro,remount /system" or just reboot.
Click to expand...
Click to collapse
I have CM7 on an SD card and tried this command. I get the following:
mount: not found
Any suggestions?
I tried this command and I am not sure I am putting it in right. I do not a space "remount/system" and a bunch of commands come up. I do use a space and nothing. Either way, I am unable to edit or copy a new file in. Copy failed or cannot save file.
Do I have to copy from within the Terminal window? After running this command I go into ES file explorer to edit or copy with no luck.
<Set DPI to 160>
There is an app called LCDDensity which allows you to alter the DPI on the nook. If the market allows you to download it, or you are able to sideload it, you might try that.
What happens for me is my market will stop working, then I use LCDDensity to set the DPI to 160 or 240, and reboot. Then the market works, but only for a day or two, and then things seem to reset. (I have tried freezing and renaming the market app, and market updater app, but it doesn't seem to have any effect. Then again I'm new to these things myself, and could be missing something silly.)
It isn't an ideal solution, but it seems fine unti a more permanent fix comes along.
Related
I can't use adb, please don't call me a noob.
I want to install rogro82 modified launcher.
http://forum.xda-developers.com/showthread.php?t=538871&page=10
there's a code in the thread to install using terminal, but it doesn't work.
Can anyone please provide the code to install through terminal.
Thanks!
put it on your sdcard
su
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
cp Launcher.apk /system/app
reboot
try that?
You dont even need the code. Just put the .apk into your sd,download Linda File manager or OI file manager, and install with that. It works like a charm. I myself used Linda.
Thanks, but just found out. (also thanks futango )
You can install it using AppManager... since it's .apk.
So far I have ZERO problems too!
Ah ok, didn't think it would work though ...because it installs to /data/app. Eh whatever. good job getting it to work. Switch thread title please.
im having a problem figuring it out?
hey
you can either find the system.apk you want and adb it out
or recompile the update.zip file and remove the apks you dont want
tho word of warning messing around with system apks can cause some system instabilites
or rm -r /system/app/nameofapp.apk
or you can...
purchase the SUFBS, a rooted browser, from the market.
You can set /system and /data to rewritable with the push of a button and just delete them through the file browser or use the builtin terminal to do it as described above.
Hey guys, I just used root explorer v 2.2 to delete the annoying apps built into the system (amazon mp3)
I am now trying to move my apps into the system so that they cannot easyly be removed. I want to send over lookout and sim checker. That way a theif would not be able to easily delete the apps.
when I select the "move" option (with sim checker) then go to the system apps dirrectpry and then select "paste", it says paste and shows a progress indicator for like 1 second then when I check to see if it actually did the move, it hasn't can anyone help me out
I know I have full root access as I have clicked to allow it and am remounted as r/w so that's not the problem.
Any help to get those two apps into my read only system directory would be greatly apprecaited.
Oh ya I think ill add that I have also tryed to simply change the permissions of the app to readonly (with root explorer) but that did not stop the basic android app manager from uninstalling it.
Try to use adb to move it.
so i went and installed adb, i know its working as well with a little test, could someone please write out a sample command for me to use for this purpose of moving an app out of the apps to sd location and into the system apps.
asb123 said:
so i went and installed adb, i know its working as well with a little test, could someone please write out a sample command for me to use for this purpose of moving an app out of the apps to sd location and into the system apps.
Click to expand...
Click to collapse
mv /system/sd/app/*lookout* /system/app
mv /system/sd/app/*checker* /system/app
It really depends on the name of the file though, if it has lookout in it, then it will be moved to /system/app. The * tells it to move anything with that in the file name
type adb and it will give you the commands + switches
adb pull
adb push
In response to your first attempt, it sounds like system is not being mounted as rw. If it were, the copying would work (I do this all of the time with SUFBS). Try to mount the system as rw via the terminal then copy.
JAguirre1231 said:
mv /system/sd/app/*lookout* /system/app
mv /system/sd/app/*checker* /system/app
It really depends on the name of the file though, if it has lookout in it, then it will be moved to /system/app. The * tells it to move anything with that in the file name
Click to expand...
Click to collapse
so i have the command prompt cd to andorid adk\tools
when i now type in the above :
mv /system/sd/app/*lookout* /system/app
it doesnt recognize the command
so i have C:\android-sdk-windows\tools> mv /system/sd/app/*lookout* /system/app
and it doesnt recognize mv as a command
cloverdale said:
In response to your first attempt, it sounds like system is not being mounted as rw. If it were, the copying would work (I do this all of the time with SUFBS). Try to mount the system as rw via the terminal then copy.
Click to expand...
Click to collapse
hey, sorry for the noob question but could you tell me the command for this. I know in the app i was using it says remount as rw and i do have access to change the system app folder (delted apps) but how can i remount as RW in terminal whats the command? And after, do i need to manually remount back to what i was so that it is back to being unchangeable?
asb123 said:
so i have the command prompt cd to andorid adk\tools
when i now type in the above :
mv /system/sd/app/*lookout* /system/app
it doesnt recognize the command
so i have C:\android-sdk-windows\tools> mv /system/sd/app/*lookout* /system/app
and it doesnt recognize mv as a command
Click to expand...
Click to collapse
If you have the tools directory in your PATH (as you should) no need to cd to the directory. Anyways, sorry to move it in adb do
adb remount
adb shell
*previous commands*
exit
Bingo!
it says failed on /systen/sd/app/com.lookout.apk - cross-device link
asb123 said:
it says failed on /systen/sd/app/com.lookout.apk - cross-device link
Click to expand...
Click to collapse
Ou have 2 android phones plugged in or an emulator running ath the same time
i dont have two phones plugged in and i dont have an emulator that i know of...
but on the bright side i mannaged to solve my problem using droid explorer. I successfully have gotten lookout entrenhed into the system so that it cannot be uninstalled from the menu.
BUT when i tried the same thing for sim checker it did not work, it would not copy into system\apps
i did manage to get it inot system\app but using the copy rather than move option in root explorer, after reinstalling using the simchecker in system\app
but it is showing up as still uninstallable. I have no idea why simcheck is not working but it worked for lookout...
I have used the Terminal Emulator and the command busybox mount -o remount,rw /system, and with that I can copy files to System/App directory (I thought it was system/Apps, but there is no s in sight). For some strange reason when I use Root Explorer it says that the file is copied, but it isn't. With ES File Explorer I can copy the files there though. Next step should be to choose the keyboard in the Nook Color Tools, but it doesn't show up. I deleted the original LatinIME.apk and replaced it with a scandinavian keyboard, but it still doesn't show up. Now I only see the Gingerbread keyboard. Can anybodyt please tell me what I'm doing wrong here?
Using Nook Color, CM7 nighly 107.
Got Netflix working a while back by modifying the build.prop file using ES File Explorer - no issues.
Tried again to make some mods and cannot save it anymore. ES reports "writable - NO"
Tried to "su chmod 666" it and it comes back with "File system read-only"
Is anybody else seeing this? What am I missing?
Thanks...
I encountered a similar situation during the build.prop edit while using ES File Explorer on my NC running CM7 on internal memory.
Possibly, the permissions in the program need to be changed to enable it to "write".
Here's what I did: Menu==>Settings==>Root options. "Check" Root Explorer and if my memory serves me correctly, click "Yes" to get past the "Experimental Feature", toggle the "Cyanogen Mod" (if you're using CM7) radio button, click OK and check the "Mount File System" box to make the system writable.
Now, it should be writable. Hope this helps.
dhyamato said:
... check the "Mount File System" box to make the system writable.
Click to expand...
Click to collapse
Thanks for the tip, that wasn't it
I remember setting those originally. I just checked again and "Root Explorer" and "Mount FIle System" are both checked.
mwilli20 said:
Using Nook Color, CM7 nighly 107.
Got Netflix working a while back by modifying the build.prop file using ES File Explorer - no issues.
Tried again to make some mods and cannot save it anymore. ES reports "writable - NO"
Tried to "su chmod 666" it and it comes back with "File system read-only"
Is anybody else seeing this? What am I missing?
Thanks...
Click to expand...
Click to collapse
In 106 SU wasn't working correctly until I reinstalled it. You can't modify build.prop without superuser rights. Check the thread about SU / Superuser missing in 106 (and I bet 107) for instructions. It worked for me.
DiDGR8 said:
Check the thread about SU / Superuser missing in 106 (and I bet 107) for instructions. It worked for me.
Click to expand...
Click to collapse
Interesting... the OP withdrew his post: (apparently it's back in 107)
http://forum.xda-developers.com/showthread.php?t=1131369
However when I checked it, the SU app was misbehaving, Force closing, refusing to respond to the menu command. So I reinstalled it. Now it's OK.
Unfortunately I still cannot edit the build.prop file.
I don't think it's a superuser problem because without SU access ES cannot even see the system folder!!! I can see it, and edit the file, just cannot save it.
You might try fixing permissions under recovery.
have you tried the app: nook netflix fixer?
I've changed it successfully on the past 6 consecutive nightlies using adbwireless pull/push. However since 106 I've hsd to reflash su. N108 hasn't given me the su issue. Is it fixed?
Same problem with the build.prop file: cannot save changes, or copy over it. Running in nightly 108 today. Tried both Root Explorer and ES File manager.
I think you need to change the build.prop file properties to be rw using chmod. Don't forget to mount system as rw before doing the chmod.
Sent from my Huawei Ascend using XDA App
foltz61 said:
I think you need to change the build.prop file properties to be rw using chmod.
Click to expand...
Click to collapse
Tried that (sudo chmod 666...), get the same message. "file system is read-only"
backup and restore fresh start....?
I'm not great at linux but I do it differently. Try chmod +rw /system/build.prop . Make sure you have system mounted as RW first. I'd also check superuser to make sure whatever terminal/file explorer you are using still has root privileges.
Sent from my Huawei-M860 using XDA App
foltz61 said:
Try chmod +rw /system/build.prop
Click to expand...
Click to collapse
666 is the same thing as +rw in this case...
It looks like the "fresh start" suggestion a couple of posts up is the best
All those numbers always confuse me . Sorry. Good luck.
Sent from my Huawei-M860 using XDA App
bike2002 said:
have you tried the app: nook netflix fixer?
Click to expand...
Click to collapse
Thanks! That did it!
Does anybody know why this app can modify the build.prop file while ES File Explorer cannot?
I had to mount the folder containing build.prop with rw access in order to use chmod. I think the latest version of the netflix fixer may do the same (see my post in that thread). In short, I used;
Code:
su
busybox mount -0 rw,remount /dev/block/mmcblk1p3 /system
in the terminal before using the chmod command in order to give myself rw permissions in the folder. I'm only two days old at this, so it beats me why root doesn't have normal rw permissions on the folder.
NCKevo said:
I had to mount the folder containing build.prop with rw access in order to use chmod...
Click to expand...
Click to collapse
Thanks for the tip. I ran the command successfully (by the way, small typo, I believe it's -o not -0) and was able to chmod and edit the file with vi.
That's where confusion began. I reboot and after the reboot I was able to modify the file without remounting the /system directory. The mount command does not surive a reboot does it?
Have you tried just pulling the build.prop
Code:
c:/<target_folder> adb pull /system/build.prop
then editing it with note pad then pushing it back and rebooting>
mwilli20 said:
That's where confusion began. I reboot and after the reboot I was able to modify the file without remounting the /system directory. The mount command does not surive a reboot does it?
Click to expand...
Click to collapse
That is confusing. What are the full (i.e. ls -l) permissions on the file now? (It's possible that it somehow ended up with o+w, but I don't understand how - vi isn't exactly known for changing permissions on-the-fly.)
Rodney