Hi guys, this is the problem I'm facing. I was running the latest oxygen rom without any problems, until I decided to install polaris office. I downloaded the docmanager apk and read that I have to push it to /system/app. Anyway, I was trying to get system to be writable and testing the mount cmd... I entered mount into the emulator and got a bunch of mounted paths. I'm not sure if that has anything to do with what happened bur anyway I then downloaded busybox installer and installed busybox.
I rebooted and next thing I know, the default oxygen launcher appears instead of the go launcher I had installed and almost all apps are not listed. I check the app manager and it shows all the other apps in their package name with a sd card sign next to them.
I am running oxygen with sdext enabled. I am guessing I did something from the emulator that messed up sdext which has most of my apps.
Can anyone tell me how I can fix this? I'm not really sure what has actually happened, but if you need me to provide more info please let me know.
BTW, I downloaded the market apk again and when I tried to install it, android rebooted. I am guessing that's cause it tried to install it on sdext.
Thanks.
This is a graphical, interactive rooting system with the ability to create/restore backups and factory settings.
This has been tested on systems 1.1.5, 1.2.0 (US/UK), and 1.2.1. It will probably work on earlier versions and should be safe to use on future versions. For best results, however, you should be on 1.2.1 before using this tool.
If you've tried rooting your nook unsuccessfully with another utility, it's best to do a factory restore (from NookManager, choose the "Rescue" option and then "Restore factory.zip") and, if your nook came with older firmware, upgrade to the latest 1.2.1 firmware.
Features:
Root your Nook
Backup/Restore
Restore to factory settings
Disable B&N Apps
Custom plugins
How to root:
1. Download NookManager.
2. Unzip the file you downloaded and write the NookManager.img file to an empty SD card. On Windows, you can use disk imager. Linux and mac users can use dd.
Use a real SD card adapter when writing the image, DO NOT USE YOUR NOOK AS THE SDCARD ADAPTER.
If possible, you should use a dedicated SD card for the NookManager image (so you can easily restore from a backup should you ever screw up your Nook). A 512Mb card is big enough for the NookManager image plus a backup of your Nook.
3. Power off your Nook, insert the SD card and power on.
You should see the NookManager boot screen followed within 15 seconds by the welcome screen.
4. Choose "No, continue without wireless"
the wireless option is for advanced users looking to connect directly to their device
5. Make a backup using NookManager! Choose "Rescue" then "Backup" then "Format remaining space on SD card" and finally "Create backup"
Because NookManager cleans the empty space on the Nooks' internal partitions and compresses the backup, it will take at least 15 minutes (and up to 45 minutes) for the backup to complete. Be patient. The final backup file can be as small as only be a few hundred megabytes, depending on the number of downloaded or sideloaded books you have.
6. Copy the backup image to your computer. Connect your Nook to your computer using the USB cable. Copy the 'backup.full.tgz' and 'backup.full.md5' files from the NookBackup drive to your computer.
This is your backup in case anything happens to your SD card. This backup is tied to your individual Nook so keep it safe. It's important to copy this file while your Nook is still booted from the SD card because Windows will normally hide the NookBackup partition on the SD card. If you ever need access to the NookBackup partition again, just boot your Nook using the NookManager SD card and connect the Nook to your computer with the USB cable.
7. Root! After your backup, press "Back" and "Back" to return to the Main Menu. Press "Root" and then "Root my device"
8. That's it! After rooting, pres "Back" and then "Exit". Remove the SD card and put it someplace safe, in case you need to restore to your backup later.
After rooting, you can install Google Apps using straygecko's excellent NTGAppsAttack package if you want to use Google Market/Gmail/Calendar/etc.
[/LIST]
Technical stuff:
The actual rooting function is minimal and as non-invasive as possible:
uRamdisk is patched to enable ADB
the internal database setting is changed to allow installation of non-market apps
the DroidSansFallback font is replaced with the updated font from jellybean to add support for extended characters
the su/Superuser binary/package is installed
Relaunch is installed
ADB Konnect is installed for enabling/disabling ADB over wireless
on systems running firmware 1.2+, the ModManager jars and package are installed
on 1.2+ systems, the PackageInstaller.apk from the 1.1.2 firmware is installed to resolve issues with package installers
and, finally, the Amazon appstore is installed just to have some easy way of downloading new apps. You can uninstall it using ReLaunch if you don't use it.
The uRamdisk patching is done with scripts rather than copying pre-compiled binaries, so this should be safe for all existing versions of the Nook firmware and (hopefully) will be forward compatible with any new releases.
The rooting procedure is non-destructive and can be run multiple times without causing problems.
Under the hood, this is a minimal linux environment with the nook drivers/binaries and a few core android binaries. The display is generated with imagemagick and written directly to the framebuffer.
If you're connecting to NookManager wirelessly over SSH, the username/password is root/root
Wherever possible, the parts of this system are compiled from source including the Linux kernel, uBoot, and all of the buildroot utilities. The hardware drivers and associated binaries are extracted from the 1.2.0 upgrade package.
The source for the project, including an automated buildscript is available at GitHub.
Support for custom menu items and scripts is documented here.
https://github.com/doozan/NookManager/downloads
NookManager.zip
17.9MB · Uploaded 14 hours ago
File was not found.
Click to expand...
Click to collapse
??
Weird. I deleted/re-upped the file and the download link seems to be working now.
ok..now it works. Thanks
Will this work with NoRefresh?
Thanks for the work on this - it was easy and worked great. And if you're planning to update, maybe add ES File Explorer or Titanium Backup in the pre-installed apps; that would make it easier to install apks directly from your SD card instead of having to do it over wireless adb. But thanks regardless.
Can confirm no refresh works great. Installed FBReader, Opera Mobile, ES File Explorer and Kindle app. Great
I just came from a firmware that had the ability to change the hardware buttons for page turning, any chance of this being added?
Thanks for this! Giving it a try.
Just curious though... I'm trying to create the backup of the device and it seems to take forever to format the free space. It also took forever to find the wireless network and I eventually just rebooted it. How long does it usually take?
I'm using a NST on 1.2.0 and have tried a 2GB Sandisk and a 8GB Dane-elec microsd card.
Gonna try redownloading and re-installing the image.
Install apk
Hi, i successfully root my NGL(1.2.0) but, if i try to install apk (Cool Reader) i got an error window "Out of space" and i'm almost sure it must be enough space to install, may someone can help with this ?
mobamoba said:
maybe add ES File Explorer or Titanium Backup in the pre-installed apps
Click to expand...
Click to collapse
Good suggestion, I've added ES File Explorer
Gvr4-330 said:
it seems to take forever to format the free space..and wifi
Click to expand...
Click to collapse
Thanks for reporting this. There was a glitch with the script that formats the SD card and with the wifi loading. Both issues have been fixed in the latest release.
asprin said:
if i try to install apk (Cool Reader) i got an error window "Out of space"
Click to expand...
Click to collapse
How are you trying to install the apk? I'm also using Cool Reader it installed with "adb install" and runs just fine. For best Nook compatibility, use coolreader 3.1.2-27 (12/11/2012 build) or later.
Originally Posted by asprin
if i try to install apk (Cool Reader) i got an error window "Out of space"
Click to expand...
Click to collapse
You get this error when you try to install application from an .apk file on sdcard or when you try to update application via it's built in updater.
ADB install works fine.
Good suggestion, I've added ES File Explorer
Click to expand...
Click to collapse
I use
Rhythm Software - File Manager
http://rhmsoft.com/?p=96
osowiecki said:
You get this error when you try to install application from an .apk file on sdcard or when you try to update
Click to expand...
Click to collapse
I'm not able to replicate this: I can copy coolreader to my sd card, and install it from there with no problems using ES File Explorer or ReLaunch. Maybe you really do have a disk space issue. Try openinng an adb shell and run "df -h" to see disk usage on your mounted partitions.
mobamoba said:
maybe add ES File Explorer
Click to expand...
Click to collapse
osowiecki said:
I use Rhythm Software - File Manager
Click to expand...
Click to collapse
It turns out you can install apks using the file browser in ReLaunch, so I'll be removing ES File Explorer in any future versions.
jeff_kz said:
I'm not able to replicate this: I can copy coolreader to my sd card, and install it from there with no problems using ES File Explorer or ReLaunch. Maybe you really do have a disk space issue. Try openinng an adb shell and run "df -h" to see disk usage on your mounted partitions.
It turns out you can install apks using the file browser in ReLaunch, so I'll be removing ES File Explorer in any future versions.
Click to expand...
Click to collapse
Thx for respond, mate, I tried install with file browser in ReLaunch from sd card, and i cant imagine that can be space issue cause i just start procedure after factory reset and rooting, anyway, thanks for tip, will try tomorrow install new build, and adb install. In general great work you did :good:
jeff_kz said:
I'm not able to replicate this: I can copy coolreader to my sd card, and install it from there with no problems using ES File Explorer or ReLaunch. Maybe you really do have a disk space issue. Try openinng an adb shell and run "df -h" to see disk usage on your mounted partitions.
It turns out you can install apks using the file browser in ReLaunch, so I'll be removing ES File Explorer in any future versions.
Click to expand...
Click to collapse
df :
/dev: 116452K total, 0K used, 116452K available (block size 4096)
/sqlite_stmt_journals: 4096K total, 0K used, 4096K available (block size 4096)
/rom: 16116K total, 227K used, 15888K available (block size 512)
/system: 285583K total, 210922K used, 74661K available (block size 1024)
/data: 824424K total, 304344K used, 520080K available (block size 4096)
/cache: 237987K total, 4179K used, 233808K available (block size 1024)
/media: 245484K total, 40K used, 245444K available (block size 4096)
/sdcard: 31149680K total, 6924320K used, 24225360K available (block size 16384)
Are you using UK or US Nook?
I'm on US Nook FW 1.2 + v176 kernel
I'm able to reproduce the apk install problems now. The "Not enough free space" error is what android throws when the internal PackageManager can't create the temporary apk file. In this case, it turns out that it's a permissions-related read error from the sdcard. I don't know if this is a matter of the internal PackageManager not running with elevated permissions, or if it's that the sdcard is mounted too restrictively.
If I re-mount the sdcard without the restrictive permissions, I can install apks from the sdcard without any errors:
Code:
umount /sdcard
mount -t vfat /dev/block//vold/179:17 /sdcard
If anyone else has any ideas for making this work, I'm open to any suggestions. In the meantime, "adb install" works just fine for installing packages.
I really suggest grabbing Android Commander if you're new to adb to graphically install apps.
jeff_kz said:
Thanks for reporting this. There was a glitch with the script that formats the SD card and with the wifi loading. Both issues have been fixed in the latest release.
Click to expand...
Click to collapse
Thanks for the quick update. I'm going to try it out now and will report back. I'm very excited
It works! Thanks so much for this! Very easy way to root and backup.
With your tool now I use this to read comics, RSS and books. First I need to say thank you.
I installed "D7 Google Reader" and "Google Drive" which requires Google Login. How could I use this software? Thanks
Also I installed version 0.2, I saw 0.3 comes out. Can I just update 0.2 to 0.3 directly? Thanks
so glad I decided to check the nook thread. Finally BN apps gone . Thank You
hi all, anyone have test factory reset on nstg US ? my backup is corrupt.
Envoyé depuis mon GT-N7100 avec Tapatalk
Having just run through applying the CyanogenMod 10.1(by vijendrahs - refere below) to 4.2.2 on my HTC Desire, I've now come across the above error with some of the applications that I've been trying to install.
I've partitioned my SD card and am running mounts2sd and am using link2sd. I've also downloaded and have tried the marketfix app. I've also tried killing apps and restarting the phone none of which seem to make a difference.
The research I've done indicates that this is appears to have something to do with memory. What I've noticed is that there doesn't seem to be any particular pattern to those apps that will install and those that won't. For example the Tasks app won't install nor will Yahoo but Skype, Maps, and Gmail installed fine.
I am beginning to suspect that the error message might not actually reflect the problem that is being reported. Is there a tool or some debugging routine that I can run to expose any further insights into this?
http://forum.xda-developers.com/showthread.php?t=2070704
Why did u use mounts2sd or link2sd if in threat is recommend a2sd in terminal? I used this ROM with a2sd and all was fine, no any error according memory.
Vijendrah's JB 4.2.2 has build in A2SD. Just open Terminal Emulator from menu and type:
"#su" then hit Enter;
"#a2sd" install then hit Enter;
"Y" then Enter when first question pops-up;
"N" then Enter when second question pops-up;
"Y" then Enter when third question pops-up.
Note: type only what's inside the commas.
Thanks for the replies. In my defense, it was my first attempt at a ROM flash and I probably didn't follow the instructions properly. I I'll try a re-flash over the weekend and see how that goes.
That said, I still think that the error message is misleading unless there is something in the installation routines for those apps that is validating for a minimum amount of available RAM.
Two ideas:
1.Android will give you that error when you try to reinstall app which you tampered with using lucky patcher try running it once before attempting to install and it will remove any leftover odex files it is responsible for.
2.Or the original a2sd script is messing up link2sd, try removing 10apps2sd from system/etc/init.d with root explorer or es file explorer. Reinstall link2sd afterwards.
3.you are simply running out of internal memory, link2sd leaves dalvik in there. You can explore your sdext with es file explorer and see what's going on there or use 'df' command in terminal emulator to check if there really is no space left in internal or sdext
freebird24h said:
Two ideas:
1.Android will give you that error when you try to reinstall app which you tampered with using lucky patcher try running it once before attempting to install and it will remove any leftover odex files it is responsible for.
2.Or the original a2sd script is messing up link2sd, try removing 10apps2sd from system/etc/init.d with root explorer or es file explorer. Reinstall link2sd afterwards.
3.you are simply running out of internal memory, link2sd leaves dalvik in there. You can explore your sdext with es file explorer and see what's going on there or use 'df' command in terminal emulator to check if there really is no space left in internal or sdext
Click to expand...
Click to collapse
Curious. I reran a2sd and answered no to the second question regarding data. Upon reboot, I was able to install apps that previously failed. On the downside, I've lost the home key!
I use MildWild
Hello Team,
When i try to install any app (for eg: facebook) from play store after I installed the ParanoidAndroid 4.0-beta [12-31-13] from this link i get this message. "Insufficient Storage Available"
Few Inputs you might require to help me:
Recovery Software Used:
I used CWM v hercules-6.0.4.3 as recovery software.
ROM File Used:
http://forum.xda-developers.com/devdb/project/dl/?id=2793
GA APPS File used:
http://goo.im/devs/paranoidandroid/roms/gapps//pa_gapps-full-4.4-20131126-signed.zip
I followed the steps mentioned in below URL to install the kitkat update:
http://www.theandroidsoul.com/t-mob...te-now-available-paranoid-android-custom-rom/
When i go to Settings>Storage i see attached screenshot.
cnish_09 said:
Hello Team,
When i try to install any app (for eg: facebook) from play store after I installed the ParanoidAndroid 4.0-beta [12-31-13] from this link i get this message. "Insufficient Storage Available"
Few Inputs you might require to help me:
Recovery Software Used:
I used CWM v hercules-6.0.4.3 as recovery software.
ROM File Used:
http://forum.xda-developers.com/devdb/project/dl/?id=2793
GA APPS File used:
http://goo.im/devs/paranoidandroid/roms/gapps//pa_gapps-full-4.4-20131126-signed.zip
I followed the steps mentioned in below URL to install the kitkat update:
http://www.theandroidsoul.com/t-mob...te-now-available-paranoid-android-custom-rom/
When i go to Settings>Storage i see attached screenshot.
Click to expand...
Click to collapse
I don't understand why you flashed PA 4.0 beta, when you want 4.4? Also, the gapps file you used should only work with 4.4. I have no clue how it would have worked for PA 4.0?
And for future purposes, if it makes it any easier, try TWRP instead of CWM - it's a lot more user friendly. In terms of the insufficient storage, I'm having a feeling that you either haven't wiped your SD card before flashing, or something has gone wrong and the system is not detecting the SD card...
From last week I'm facing this issue.
1) this issue is with some apps only.
- till now i hv seen this error while updating Facebook, Gmail and Tv Sideview app
2) Google Play store completely downloads the app but while updating it says Error: Insufficient Storage.
3)
But I'm able to install other apps from Google Play.
4) Even installing Facebook, Gmail, Sixaxis Controller manually from APK has failed it says Free up some space. While I can still install games as large as 50mb.
5) two weeks later I have rooted my phone, but I haven't done any critical changes which many rooted android users do.
6) some apps I'm using which u may want to know are:
-SuperSU, Root Uninstaller (fr deleting G-books n G-Newstand), GL to SD (but it's unmounted), Link to SD (just installed didn't use it), Rom Toolbox Lite (didn't use it either) and Lucky Patcher.
I have mentioned it because I got to know that it's the issue with those using lucky Patcher....???
Root /dev/log... Folder has just four files. Nothing to clean frm there.
Internal memory : 360mb (I had uninstalled some apps to increase it too 410mb but still facing the same issue)
Help requested. What to do now?
Phone: Sony Xperia M Dual
Model: C2004
Android version: 4.2.2 (Stock Rom) just rooted nothing changed.
======================================
UPDATE: FIXED ||||| PROBLEM SOLVED
====================================
I had changed d Apps2SD option to SD Card which was causing this error. Changed it to Auto again
By the way another fix is to goto lucky Patcher and in it's troubleshooting menu. Choose remove /delte (any logical options which says to clear) patches and backups
PS: i read it smwhere and haven't tried this one.
ijtaba7 said:
From last week I'm facing this issue.
1) this issue is with some apps only.
- till now i hv seen this error while updating Facebook, Gmail and Tv Sideview app
2) Google Play store completely downloads the app but while updating it says Error: Insufficient Storage.
3)
But I'm able to install other apps from Google Play.
4) Even installing Facebook, Gmail, Sixaxis Controller manually from APK has failed it says Free up some space. While I can still install games as large as 50mb.
5) two weeks later I have rooted my phone, but I haven't done any critical changes which many rooted android users do.
6) some apps I'm using which u may want to know are:
-SuperSU, Root Uninstaller (fr deleting G-books n G-Newstand), GL to SD (but it's unmounted), Link to SD (just installed didn't use it), Rom Toolbox Lite (didn't use it either) and Lucky Patcher.
I have mentioned it because I got to know that it's the issue with those using lucky Patcher....???
Root /dev/log... Folder has just four files. Nothing to clean frm there.
Internal memory : 360mb (I had uninstalled some apps to increase it too 410mb but still facing the same issue)
Help requested. What to do now?
Phone: Sony Xperia M Dual
Model: C2004
Android version: 4.2.2 (Stock Rom) just rooted nothing changed.
======================================
UPDATE: FIXED ||||| PROBLEM SOLVED
====================================
I had changed d Apps2SD option to SD Card which was causing this error. Changed it to Auto again
By the way another fix is to goto lucky Patcher and in it's troubleshooting menu. Choose remove /delte (any logical options which says to clear) patches and backups
PS: i read it smwhere and haven't tried this one.
Click to expand...
Click to collapse
move your apps to sd card using link2sd.. here's a guide to it http://www.xda-developers.com/android/guide-on-increasing-application-storage-with-link2sd/