Hi I've searched the forums to the best of my ability, and cant figure out how to install a system app. I pulled the app (Via ADB Pull) and tried to push it back into /system/app and it works, but never installs? And i cant find it with astro or other software. =( Im using a G1 with Cyan, If you need more information please tell me!
Pushing does install. It doesn't have the install text like adb install does, but that is how you push files so it should work.
You could check to see if you have it set as read only, or delete the file then copy over the new one.
Im not sure what i did but i just kept trying and rebooting untill something worked =/ Lol Thanks though.. What do you mean by Read Only?
System partition is read-only by default, you need to change it to read-write if you want to install or push anything to it. I can never remember commands but they are all over this forum.
Hi all:
I have read and searched and tried and tried and FAILED. I can not enable sideloading on my Captivate after the JH7 update.
Is there any such thing as a "One Click Sideload Enabler".
Now, I don't mean something like the Wonder Machine, or Droid Explorer (which I am currently using to install apps). I mean a way to easily enable sideloading on the actual phone itself.
Before the update I used Unleash the Beast, which worked perfectly. Sadly it will not work after the update, and the developer seems to be gone
Any thoughts?
Thanks!!!
You need to root and then modify settings.db to allow side loading. I know of no other way. This is how i have done it in the past.
Hi:
That is the first thing I tried. I have tried to edit with sql lite, as well as root explorer, it shows the value of non-market apps changing to 1, then I transfer it back to phone, but I am still unable to install non-market apps.
I think a main part of the problem is that when I try to copy the settings.db file to desktop through cmd prompt, it does not copy. I actually had to use root explorer to copy it, then transfered it to PC, then made the changes.
I was actually hoping for something similar to what Unleash the Beast did. After you installed UTB, you could then just use Terminal editor to very easily enable sideloading. I believe UTB has a script of some sort which made that possible.
Thanks!
+1 for a non-market app / sideloading "update.zip" (JH7 compatible of course).
The problem with an update.zip format fix is that we'd essentially have to overwrite your settings.db, and you would lose any customization off of stock not already made.
Perhaps an update.zip that contained sqlite3 and a shell script ?
Hi:
Thanks so much to everyone who replied. After trying a million times, I was finally able to get sideloading enabled. It seems that my JH7 update hadn't properly flashed. After reinstalling the update things went smoothly.
Thanks again!
Glad to hear it.
Hi, just got a NC today. Am a total noob to Android (no smartphone) and am hoping someone can help me out. I have read and searched a bit of the posts in these NC forums, but there is just A LOT and I'm kinda lost. To start out..
After playing around with the stock 1.2 ROM for a bit, I installed the latest nightly (177) CM7 with this guide,
http://forum.xda-developers.com/showthread.php?t=1030227
Before this, I also switched to the older 1/5GB app/data partition with DeanGibson's zips via CWM. The installs are fine, although CM7's UI is thoroughly confusing. My questions are:
By installing CM7, am I also rooted as part of the process? If not, is there any additional benefit to get root?
Is ManualNooter needed if I have CM7, or is it redundant? Can I install it on top of CM7?
I can't get most apps from the Market ("your device is not compatible"). I also went to Amazon.com to try and get its AppStore app, but it gives the same error. Is this a noob issue, or is there a real problem, and is there a workaround if the latter?
What's a simple way to access network shares on my Windows network?
Is there a way to dismount & remove the microSD w/o turning the NC off?
Links would be fine. TIA for any help.
You are rooted! You might want to install clock work mod from the market... I'm not sure about the computability issue as I have never had it myself.
Sent from my NookColor using XDA Premium App
If I'm understanding this correctly, you were able to go from completely stock to CM7 without rooting with manualnooter first? I'm buying a NC next week and i was unsure root was needed to go to CM7.
You are already rooted.
Market fixes: http://forum.xda-developers.com/showthread.php?t=1255689
Sent from my LG Optimus V using Tapatalk
@sevs753
Yes, apparently the CM7 install does the root thing for you. Still not quite sure if it's needed for anything else other than allowing custom ROMs.
I'm a little flustered with Android at the moment. Trying to edit the build.prop as some others have mentioned to temp fix the market problem, only to find that I can't download ES Explorer (what others are reportedly using) to edit the file. Was going to edit it in terminal emulator & nano, but found that the soft keyboard has no cursor keys. So I found an ES Explorer apk, and now am trying to figure out how to sideload the app--I believe that's the correct lingo for Android.
I also found that many embedded flash videos don't play (Youtube does). I thought this was a done deal with 2.3 and CM7, but apparently not. Tried to download Flash 10.3 from market, but again am blocked.
Am also trying to find the parameters of what is allowable for video playback for 2.3. For HC, you can play up to 720p and high profile H264 with "reasonable" params. I've been encoding various test clips, and it looks like the max is 854x480 at baseline profile, same as with the stock ROM.
Change your LCD density to 240 and your market will start working. It makes the icons really large but you get used to it. The best way to change the density is by editing the build.prop line that is default: qemu.sf.lcd_density=161
Change that 161 to 240 and then save your build.prop and reboot. Problem should then be solved.
I edit the build.prop with root explorer (Paid version) - you have to change from r/o to r/w first, then change back to r/o after you are done editing.
Shandon84321 said:
Change your LCD density to 240 and your market will start working. It makes the icons really large but you get used to it. The best way to change the density is by editing the build.prop line that is default: qemu.sf.lcd_density=161
Change that 161 to 240 and then save your build.prop and reboot. Problem should then be solved.
I edit the build.prop with root explorer (Paid version) - you have to change from r/o to r/w first, then change back to r/o after you are done editing.
Click to expand...
Click to collapse
That's quite a jump. Most people are changing to 160 which is also a standard density.
Until you really get familiar with the CM7 and the NC, I suggest you try CM7 off uSD card.
patruns said:
That's quite a jump. Most people are changing to 160 which is also a standard density.
Click to expand...
Click to collapse
With 160 you will be clearing Market app data daily for it to keep working. 240 seems to keep working... I guess because almost all phones are set to 240.
DizzyDen said:
With 160 you will be clearing Market app data daily for it to keep working. 240 seems to keep working... I guess because almost all phones are set to 240.
Click to expand...
Click to collapse
+1 on this. I was going forever on 240 without a hiccup.
Note that ICS has also been demonstrated to change the UI depending on the density, with 160 for a tablet UI (honeycomb-ish) and 240 for phone UI (gingerbread-ish). Came across a couple references showing that density was the only thing that needed to be changed to make this happen.
I kind of suspect this may be part of why density is becoming such a big issue. It also fits with the fact that tablet-related apps show up in the market at 160 but not at 240. Perhaps Google is setting market up ahead of ICS release to handle this?
skwalas said:
+1 on this. I was going forever on 240 without a hiccup.
Note that ICS has also been demonstrated to change the UI depending on the density, with 160 for a tablet UI (honeycomb-ish) and 240 for phone UI (gingerbread-ish). Came across a couple references showing that density was the only thing that needed to be changed to make this happen.
I kind of suspect this may be part of why density is becoming such a big issue. It also fits with the fact that tablet-related apps show up in the market at 160 but not at 240. Perhaps Google is setting market up ahead of ICS release to handle this?
Click to expand...
Click to collapse
If i remember correctly this also happens on Honeycomb.
Sent from my LG Optimus V using Tapatalk
You're at the same spot I was at earlier last week. I just got my NC, and read about and made the cm7 sd card. To get market working correctly this is what I did:
- installed cm7 and gapps using this guide - http://forum.xda-developers.com/showthread.php?t=1000957
- once that was working I went to the market and got titanium backup installed
- once that's installed, I went to applications/manage/market and force closed market, cleared the cache, and uninstalled updates
- then I went to titanium and found marketupdater.apk and uninstalled it
- after that I opened market again, if force closed once but opened fine the second time. I now have the old style market and everything seems to work well.
I haven't used manualrooter, I only followed the above guide. As for unmounting the card, I have no idea. I'm probably going to keep things as they are, I really like being able to turn the NC off, take the card out, and have it back as stock.
koopakid08 said:
If i remember correctly this also happens on Honeycomb.
Sent from my LG Optimus V using Tapatalk
Click to expand...
Click to collapse
I believe honeycomb had the capability built in but was not supposed to be enabled. Would have to dig around for links n such.
I just want to say thanks for all those who replied. I'm taking some time trying different stuff on the NC, now that I've gotten a basic handle on CM7. I'll be sure to try some of the tips & info proffered.
Re: Market issue - I tried w/ File Expert to change file.prop's attribs so I can edit them, but the changes don't take. Since the entire /system partition is RO, I'm assuming I need to remount it to RW before I can do anything to the files, per NookDev's instruction. Am further assuming I'll need to install the SDK so I can get ADB running.
@Kingston73: I'm sure there are apps that do it more efficiently, but mount/unmount SD is in Settings | Storage.
More questions:
Is there a way to not have a wallpaper and have the default black background changed to something else? I like having just a plain background.
I'm using the default browser for now. Most of the sites with embedded Flash don't work (no Flash installed). I tried installing Flash 10.3 from the Adobe site, but it gives the same error as Market's. Can 10.3 be installed into CM7 at all, or is this because of the LCD density issue (which I'll get around to fixing)?
Thanks again for all your help. Am learning both Android and CM7 as I go along.
Noob^2 said:
I just want to say thanks for all those who replied. I'm taking some time trying different stuff on the NC, now that I've gotten a basic handle on CM7. I'll be sure to try some of the tips & info proffered.
Re: Market issue - I tried w/ File Expert to change file.prop's attribs so I can edit them, but the changes don't take. Since the entire /system partition is RO, I'm assuming I need to remount it to RW before I can do anything to the files, per NookDev's instruction. Am further assuming I'll need to install the SDK so I can get ADB running.
@Kingston73: I'm sure there are apps that do it more efficiently, but mount/unmount SD is in Settings | Storage.
More questions:
Is there a way to not have a wallpaper and have the default black background changed to something else? I like having just a plain background.
I'm using the default browser for now. Most of the sites with embedded Flash don't work (no Flash installed). I tried installing Flash 10.3 from the Adobe site, but it gives the same error as Market's. Can 10.3 be installed into CM7 at all, or is this because of the LCD density issue (which I'll get around to fixing)?
Thanks again for all your help. Am learning both Android and CM7 as I go along.
Click to expand...
Click to collapse
Flash will install fine from the market if you are in the old market. It doesn't care about the density.
More questions:
Is there a way to not have a wallpaper and have the default black background changed to something else? I like having just a plain background.
Click to expand...
Click to collapse
You can set or remove wallpaper upon your will.
I'm using the default browser for now. Most of the sites with embedded Flash don't work (no Flash installed). I tried installing Flash 10.3 from the Adobe site, but it gives the same error as Market's. Can 10.3 be installed into CM7 at all, or is this because of the LCD density issue (which I'll get around to fixing)?
Click to expand...
Click to collapse
Flash 10.3 installed and worked w/o any issue with CM7.
If you can't download it directly from Market, try to sideload it.
Oh, and, recommend trying Opera browser
patruns said:
Flash will install fine from the market if you are in the old market. It doesn't care about the density.
Click to expand...
Click to collapse
Flash should install fine with the new market too, if density is at 160 (or 240) and market data is freshly cleared. It is possible that in some cases the market will update itself too quickly for the 160 fix to stick long enough to install, and this has happened to me on occasion. If installing the basic "problematic" apps (flash, facebook, repligo, maps, etc.) for the first time, would suggest working with 240 dpi to get all the apps on your nook, then revert to 160 if that is your preferred screen sizing going forward.
Thanks for the continuing tips. I did get Flash 10.3 to install via sideloading. I still can't get Market to lift its "partial-ban", since the only version I have is 3.1.3 and there is no rollback. I did manage to edit build.prop to 160, then 240, (and cleared cache) but the ban is still present. I think us Johnny-come-latelies are just a bit screwed until some shining knight comes through with a fix.
To relate my further misadventures with CM7 and Market, I'm recounting some of my steps, in hope that they'll help someone else.
Networking to Windows boxes: I used CIFS Manager, which worked straightaway. Before that, I tried the networking function of ES File Explorer and Astro (w/ SMB plugin), but they both crashed or hung.
Finding a good file manager: I tried File Expert, ES File Explorer, and Astro File Manager. They have more functions than CM7's built-in file mgr, but the built-in mgr is the fastest at reading off large directories from the network (which still isn't that fast). This is critical for me, since most of my media will be accessed via wifi.
Finding a better terminal emulator: The built-in one is kinda barebone. Looks like Better Terminal Emulator Pro is the only game in town?
Finding a better keyboard: Since I'm a commandline guy, Hacker's Keyboard fits the bill. Well, at least until my BT keyboard arrives.
Getting USB HDD/key to work: Ordered a Tekkeon TekCharge MP1550 4xAA batt pack and a Y-cable, along with a 90-degree micro-USB cable.
Install font for Viet or any language not already on CyanogenMod 7:
I have a collection of Viet songs/movies, and most of them have UTF-8 filenames. I used this below to change the font so CM7 can see the files (it's also what I used to edit build.prop). There are easier ways to do this, but here you don't need to install anything else.
1. Get DejaVu Fonts from dejavu-fonts.org (personally, I used Arial.ttf from my Windows box since I know it covers Viet)
2. Get DejaVuSans.ttf and rename to DroidSansFallback.ttf
3. Copy DroidSansFallback.ttf to root dir of SD card
4. Insert SD card into NC and mount it (Settings | Storage)
5. Run Terminal Emulator
6. Enter su (confirm when asked) (all commands case-sensitive)
7. Enter mount. Note device node & FS for /system. For CM7, it's /dev/block/mmcblk0p5 /system ext4 (ro[...])
8. Enter mount -o rw,remount -t ext4 /dev/block/mmcblk0p5 /system (node & FS must match)
9. Enter mount again to check, it should read /dev/block/mmcblk0p5 /system ext4 (rw[...])
10. Enter chmod 4755 /system/fonts/DroidSansFallback.ttf
11. Enter dd if=/sdcard/DroidSansFallback.ttf of=/system/fonts/DroidSansFallback.ttf
12. Reboot. File and partition permissions should return to default.
I found that local UTF8 filenames are recognized, but not files over the network. After some hair pulling and a bunch more Googling, I stumbled on the extra needed step.
13. Unmount the CIFS share in CIFS Manager. Long-press to edit the share, enter iocharset=utf8 in the Options box. Save and remount.
Other apps chosen: EzPDF for PDFs, Aldiko for ePubs, FBReader for Mobis, PerfectViewers for CBRs, OverDrive for library checkouts, MoboPlayer for SD MKVs (doesn't work for AVI/XviD).
To-Do's:
. Try Opera like another had suggested. The default browser is pretty limited.
. Check out some of the compilers & editors for Android.
. Find a decent office suite.
Question:
. I'm having trouble with file associations with the built-in file mgr (am assuming it is part of ADW). The association is lost after a few files, and apparently it associates all file types in the share with the single app, regardless of extension. Is this an ADW issue, or did I just miss a setting somewhere?
Noob^2 said:
Thanks for the continuing tips. I did get Flash 10.3 to install via sideloading. I still can't get Market to lift its "partial-ban", since the only version I have is 3.1.3 and there is no rollback. I did manage to edit build.prop to 160, then 240, (and cleared cache) but the ban is still present. I think us Johnny-come-latelies are just a bit screwed until some shining knight comes through with a fix.
Click to expand...
Click to collapse
Are you actually clearing the market data specifically? if you're just clearing cache (such as through rom manager), that's a completely different thing and won't fix the problem. You need to clear the application data for the market specifically.
Would be seriously odd that you couldn't get the apps. Note that if you've flashed gapps through rom manager, it should install the old market. selecting "uninstall updates" in the application manager screen for the market should take you back to that old market, but it will update very quickly unless the market updater apk is already disabled.
Hi
First post here, I'm new to Android and rooting but I know my way around computer systems in general so hoping you guys can help me, haven't seen a thread about this exact problem so far.
I've semi-bricked (bootlooped) my Samsung Galaxy Ace running Gingerbread, having rooted it last month using the upd_1 package and enjoying a bloatware-free phone, happily installing apps onto my second partition on my SD card. I've not changed my ROM, just the stock is good enough for me for now. However I was getting continually prompted by Homescreen Selector nags at powering up for some reason and I thought I could disable it by applying Freeze using LInk2SD, but since doing that I continually get the Samsung logo, the orange "explosion" (I'm with Orange) then a vibration and the whole cycle repeats. My guess is the operating system can't find the selector.apk app since I froze it.
I thought the solution would be simple - use adb shell to rename back from selector.fro to selector.apk. However I'm unable to find any such file in my system/app folder. There are a load of other apk and odex files but not that one. When I type su I get "permission denied", though I definitely rooted my phone but I don't think I have my bootloader unlocked.
I don't have CWM installed or any backups unfortunately (yes, I know...), so even if I took one now prior to a factory reset, surely the same problem would come back if I were to restore from any backup I were to take now. I can get into Recovery and Download screens ok but don't want to restore the whole ROM unless I have to, since I know it's only one APK that is at fault.
So, please can anyone tell me how to locate the selector.fro file to turn it back to selector.apk? Or can't I do that without unlocking the bootloader first, or is there another solution?
Many thanks in advance,
Graham
Wouldnt it be possible to make a zip of the selector.apk and flash it? Rename the zip-file to "update" (since you're unable to browse to your specific file).
QNBT said:
Wouldnt it be possible to make a zip of the selector.apk and flash it? Rename the zip-file to "update" (since you're unable to browse to your specific file).
Click to expand...
Click to collapse
Hi, thanks for the response
Do you mean copy a zip of selector.apk to the SD card and run it from there, same as I did when I rooted? Where can I obtain a copy of that apk from? I can't find it on my computer or via Google...
gkey2112 said:
Hi, thanks for the response
Do you mean copy a zip of selector.apk to the SD card and run it from there, same as I did when I rooted? Where can I obtain a copy of that apk from? I can't find it on my computer or via Google...
Click to expand...
Click to collapse
You can extract it from the ROM's zip file, just locate it as you would on your phone.
But I don't have a ROM zip file. I'm not using a custom ROM, just stock. I may go down the custom ROM route one day, but for now I just want my phone to work again in the quickest way possible.
All I need is a copy of the original stock home selector APK. Can anyone help here please?
Found the file!
Never mind, got the apk from another thread. Flashing tonight...
I rooted my HTC One M7 yesterday and I tried to modify the screen dpi from the build.prop via different apps and text editors. But everytime I rebooted the phone, the saves were lost.
Marsustorm said:
I rooted my HTC One M7 yesterday and I tried to modify the screen dpi from the build.prop via different apps and text editors. But everytime I rebooted the phone, the saves were lost.
Click to expand...
Click to collapse
/system partition is write protected by the kernel. Use an unsecured kernel or push your modified build.prop file from a custom recovery.
Btw modifying files in /system will cause issue with future ota updates.
Would you mind giving me a step by step instructions for the easier one? I'm pretty new to the Android scene.
Edit: I'm doing this to play HS on my phone (on the regular setting it says that a 6'' screen is required)
Marsustorm said:
Would you mind giving me a step by step instructions for the easier one? I'm pretty new to the Android scene.
Edit: I'm doing this to play HS on my phone (on the regular setting it says that a 6'' screen is required)
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=57570982&postcount=2