Related
My son asked me to write a quick'n'dirty app for him (click a button, play a sound file) so that he could annoy one of his friends (go figure!)
I did so (using Eclipse, and packaged/signed using the Export Wizard then zipaligned)- and sent it to him via gmail... but he got a parse error. I also sent it to my Fuze (on which I've installed HaRET & Eclair - thanks XDA!). Same problem: "Parse Error: There is a problem parsing the package"
So I hooked my Fuze up via USB and simply copied the file to an SD folder. The apk installs from SD via File Manager without any problem (and works as it did in the emulator). I've attached the apk, if that will help diagnosis.
Is there a known bug with the 'install from gmail'? Should I just put my personal apps onto an accessible filestore (that my son can browse to)?
Any other mechanisms to allow me to email the apk so he can save it locally? (I'm a noob regarding android - this is my first app, and he just got the phone)
Thanks in advance!
I am not sure, but I believe that when you open an attachment from an email, it gets downloaded into the "Download" folder in your phone or SD card. And then it is installed from there. Have you tried installing through SD card? i.e. place the file in the SD card and use any file manager to install it.
Thanks for taking the time to read & respond!
JokerAce said:
I am not sure, but I believe that when you open an attachment from an email, it gets downloaded into the "Download" folder in your phone or SD card. And then it is installed from there.
Click to expand...
Click to collapse
This is what I was doing - the install failed at this point. Gmail provides only a 'preview' button... no way to save the attachment in a generic sense -- I can see the sense in limiting stupid saves to protect noobs from themselves... but this is Android, why isn't this configurable behavior?
Have you tried installing through SD card? i.e. place the file in the SD card and use any file manager to install it.
Click to expand...
Click to collapse
this is what I did, and it worked... My son also downloaded the file on his computer, and synced to SD then installed...
My main question... what the hell is Gmail doing to the file during the download process? The file is obviously OK (it works when saved/transferred via PC from the gmail attachment... just not on the 'droid version of gmail)
tonycoyle said:
Thanks for taking the time to read & respond!
This is what I was doing - the install failed at this point. Gmail provides only a 'preview' button... no way to save the attachment in a generic sense -- I can see the sense in limiting stupid saves to protect noobs from themselves... but this is Android, why isn't this configurable behavior?
this is what I did, and it worked... My son also downloaded the file on his computer, and synced to SD then installed...
My main question... what the hell is Gmail doing to the file during the download process? The file is obviously OK (it works when saved/transferred via PC from the gmail attachment... just not on the 'droid version of gmail)
Click to expand...
Click to collapse
I have had success installing from gmail in the stock app, I clicked the 'install' button...
-htc desire
I had the same problem I while back when I still had my Tattoo. The problem was solved with tAttachApkInstaller (found in the market).
I'm a pretty experienced computer person. But I am a nube with the Nook Color I received for Christmas. I bought an 8 Gigabyte Cyanogen 7 chip on eBay. Ran the system from the SD chip so I can still go back to my Nook Color Barnes & Nobel system when I want or need to. Booted right up and I was good to go. Happy! Happy!
First what I've got: Cyanogen Mid 7.1.0 Rc1-encore.
Build GRJ22
Kernal 2.6.32.9
Android version is 2.3.4
Got Market up and running, connected on my WiFi network. Enabled Blue Tooth for an external keyboard. Downloaded Null Keyboard. Still monkeying around with that. Decided to try a little overclocking. Downloaded and installed Nook Tweaks. But it says I need to update my operating system. I've tried every step suggested for creating an updated SD chip. (I want to keep the 8 Gig SD chip so I can have that to fall back on if I screw up.) I've searched, read, and experimented. But I don't seem to be able to create my own SD Chip from scratch.
Bought two blank 16 Gigabyte San Disk Class 4 chips. I have a USB based card reader/writer running off a Windows XP laptop. I've got Win32 disk imager on the laptop. I've tried downloading an update to write to the new SD chips. But there are so many variations. It seems everybody and his brother has a variety that is the latest and greatest. I've searched all over the Nook forums for two weeks. Found lots of step by step instructions. The only problem is that many of these are several months old. So some of the systems they mention are now months old.
So, here are my questions:
1. I think what I need to download is CM7 7.2. But there are some later flavors that add numbers after the 2. Can anyone suggest the best CM7 system that will support the features of the Nook Tweaks App?
2. Is there anything I must do to the SD Chip before I use Win32 disk imager to write the system onto my 16 Gig SD chip? Example do I have to format it in the Nook, or does Win 32 disk imager do that when it writes the OS and files to the chip?
3. I'm assuming I'll have to reinstall some of my programs on this updated OS. I'm OK with that. I want something stable. Nightly builds seem like extra confusion. And are there versions by some particular developers that are better than others? Example: one sticky suggested CM7.2 by mrg666.
4. Can someone explain what Mount and Unmount means for my Nook chips? I can remove my SD Chip without Unmounting. But my understanding is that I should select Unmount before I do. Do I have to Mount it again when I place the SD chip for the upgrade? Since this will be an upgrade, I don't see how I can mount it. This is yet another area of my confusion.
I'm not stupid. But I am confused. And the terminology and acronyms so many of the experienced folks use here is confusing - at least to me. Any help will be greatly appreciated.
As long as I'm asking questions. While I was in the native Nook Color OS, it upgraded from version 1.3 to 1.4. Is there some way I can save the native Nook Color Barnes & Nobel Operating System and my books to a spare SD Chip?
Thanks in advance for any help!
Bach On
bachon said:
So, here are my questions:
1. I think what I need to download is CM7 7.2. But there are some later flavors that add numbers after the 2. Can anyone suggest the best CM7 system that will support the features of the Nook Tweaks App?
2. Is there anything I must do to the SD Chip before I use Win32 disk imager to write the system onto my 16 Gig SD chip? Example do I have to format it in the Nook, or does Win 32 disk imager do that when it writes the OS and files to the chip?
3. I'm assuming I'll have to reinstall some of my programs on this updated OS. I'm OK with that. I want something stable. Nightly builds seem like extra confusion. And are there versions by some particular developers that are better than others? Example: one sticky suggested CM7.2 by mrg666.
4. Can someone explain what Mount and Unmount means for my Nook chips? I can remove my SD Chip without Unmounting. But my understanding is that I should select Unmount before I do. Do I have to Mount it again when I place the SD chip for the upgrade? Since this will be an upgrade, I don't see how I can mount it. This is yet another area of my confusion.
I'm not stupid. But I am confused. And the terminology and acronyms so many of the experienced folks use here is confusing - at least to me. Any help will be greatly appreciated.
As long as I'm asking questions. While I was in the native Nook Color OS, it upgraded from version 1.3 to 1.4. Is there some way I can save the native Nook Color Barnes & Nobel Operating System and my books to a spare SD Chip?
Click to expand...
Click to collapse
1) I believe 7.1 RC has an older kernel (maybe even .29, can't remember) that won't allow all the features of the Nook Tweaks. I'd recommend upgrading to full release 7.1 which can be found if you search around.
2) You shouldn't have to do anything, but after you write the image, you may have to expand the partitions to give you full access to the storage space. i.e. writing a 2GB image leaves 14GB unallocated space you will not be able to access until you do.
3) I haven't tried other builds, but reading up on the threads (and usually the first post) can give you an idea of what works, what doesn't, what kind of problems are being run into by users.
4) Mounting/Unmounting is essentially allowing the system to use the drive/card. I think of it as the Windows Safely Remove USB device kind of thing. The system will automatically mount the SD card when you insert it. You can mount cards, partitions, etc. Though I don't think you can unmount a Sd card while running an OS off it.
bachon said:
I'm a pretty experienced computer person. But I am a nube with the Nook Color I received for Christmas. I bought an 8 Gigabyte Cyanogen 7 chip on eBay. Ran the system from the SD chip so I can still go back to my Nook Color Barnes & Nobel system when I want or need to. Booted right up and I was good to go. Happy! Happy!
First what I've got: Cyanogen Mid 7.1.0 Rc1-encore.
Build GRJ22
Kernal 2.6.32.9
Android version is 2.3.4
Got Market up and running, connected on my WiFi network. Enabled Blue Tooth for an external keyboard. Downloaded Null Keyboard. Still monkeying around with that. Decided to try a little overclocking. Downloaded and installed Nook Tweaks. But it says I need to update my operating system. I've tried every step suggested for creating an updated SD chip. (I want to keep the 8 Gig SD chip so I can have that to fall back on if I screw up.) I've searched, read, and experimented. But I don't seem to be able to create my own SD Chip from scratch.
Bought two blank 16 Gigabyte San Disk Class 4 chips. I have a USB based card reader/writer running off a Windows XP laptop. I've got Win32 disk imager on the laptop. I've tried downloading an update to write to the new SD chips. But there are so many variations. It seems everybody and his brother has a variety that is the latest and greatest. I've searched all over the Nook forums for two weeks. Found lots of step by step instructions. The only problem is that many of these are several months old. So some of the systems they mention are now months old.
So, here are my questions:
1. I think what I need to download is CM7 7.2. But there are some later flavors that add numbers after the 2. Can anyone suggest the best CM7 system that will support the features of the Nook Tweaks App?
2. Is there anything I must do to the SD Chip before I use Win32 disk imager to write the system onto my 16 Gig SD chip? Example do I have to format it in the Nook, or does Win 32 disk imager do that when it writes the OS and files to the chip?
3. I'm assuming I'll have to reinstall some of my programs on this updated OS. I'm OK with that. I want something stable. Nightly builds seem like extra confusion. And are there versions by some particular developers that are better than others? Example: one sticky suggested CM7.2 by mrg666.
4. Can someone explain what Mount and Unmount means for my Nook chips? I can remove my SD Chip without Unmounting. But my understanding is that I should select Unmount before I do. Do I have to Mount it again when I place the SD chip for the upgrade? Since this will be an upgrade, I don't see how I can mount it. This is yet another area of my confusion.
I'm not stupid. But I am confused. And the terminology and acronyms so many of the experienced folks use here is confusing - at least to me. Any help will be greatly appreciated.
As long as I'm asking questions. While I was in the native Nook Color OS, it upgraded from version 1.3 to 1.4. Is there some way I can save the native Nook Color Barnes & Nobel Operating System and my books to a spare SD Chip?
Thanks in advance for any help!
Bach On
Click to expand...
Click to collapse
1. Use Win32DiskImager.exe to burn the "generic-sdcard-v1.3.img" onto your "virgin" sdcard.
2. Use Easeus Partition Manager to resize the boot partition on your newly bootable sdcard to 200MB .
3. copy "encore_CM72-Mirage-01262012.zip" to root of sdcard, and rename it to "update_CM72-Mirage-01262012.zip".
4. copy "gapps-gb-20110828-signed.zip" to root of sdcard and rename it to "update-gapps-gb-20110828-signed.zip" .
Put the scard in the Nook and it should boot and fully install the Android system, CM72, Google apps, and then turn itself off. Turn it back on and you should get the Google Android setup screens.
Useful utilities are SDformatter from Sandisk site, Easeus Partition Manager, and Win32Diskimager.exe.
Hope this helps.
Leapinlar just posted an expanded Generic SD Image that does away with manually expanding the boot partition - I believe it's around 200mb... I just tried it and it works great! You can find it here: http://d01.megashares.com/index.php?d01=NcUqquQ
Please take time to thank Leapinlar (and Verygreen) - he worked hard on this!
Downloading it now. Many Thanks to you for the help!
If we're being honest, the only thing you did wrong is spend money on a pre-imaged sdcard. The people pumping those out are profiteers fleecing the underinformed, on the backs of the generous.
Nothing on you, the process can seem daunting, and the ready-to-run sdcards seem like an easier way. It just rankles me that people who had no hand in the work are always the ones selling these. Everything anybody could need is available for free right here.
Progress - but still some questions.
OK. I'm getting closer - thanks to all for their answers. But I want to better understand these steps. Please bear with me. This is the kind of thing that I find confusing. Many of the nubes (like me) can read the step-by-step procedures. But the experienced folks seldom explain WHY and exactly WHAT the purpose of the steps are. And I'm sorry to say that they sometimes leave out crucial details. I'm not just asking for me - but for the many nubes here. (See below.)
So let's take these suggested steps and use them as Question and Answer to help other nubes like me better understand what is being done and why.
Suggested Step 1. Use Win32DiskImager.exe to burn the "generic-sdcard-v1.3.img" onto your "virgin" sdcard.
Please check my understanding of what these steps represent and correct if I am wrong.
Generic-sdcard-v1.3.img is like a template. So this first step creates the four required partitions on my SDcard. My Nook Color is going to require this to be able to install or update the Android operating system. Is that right?
Suggested step 2. Use Easeus Partition Manager to resize the boot partition on your newly bootable sdcard to 200MB.
The Generic -sdcard-v1.3.img template doesn't make the BOOT partition quite large enough for the zipped files I'm going to need to copy to it. (Boot partition is sometimes called the Root.) So step 2 does that. Am I right?
Suggested step 3. copy "encore_CM72-Mirage-01262012.zip" to root of sdcard, and rename it to "update_CM72-Mirage-01262012.zip".
Before I do this: each of these zipped variants is like the equivalent of the Operating System on a computer hard drive. And there are multitudes of these operating systems out there for my Nook Color. Right?
So now I copy the zipped encore file from my hard drive to the Boot/Root partition of the SDcard. A simple copy and paste is fine for doing this. And I should NOT expand the zipped file. Right?
Question for Clarification here: if this zipped encore file was my very first install of a non-Barnes & Nobel Operating system on my Nook Color - is it still necessary to rename it to update, or can I keep the original name of this zipped file?
Since I already installed CM7.1.0 RC1-encore on my Nook Color, this newer zipped file ("encore_CM72-Mirage-01262012.zip") is an upgrade. So I need to rename the first part of that encore file to be update . My Nook Color won't know what to do if I don't do that.
So I now have one file called "update_encore_CM72-Mirage-01262012.zip" into the Boot/Root Partition on the SD card.
Is this correct?
Suggested step 4. copy "gapps-gb-20110828-signed.zip" to root of sdcard and rename it to "update-gapps-gb-20110828-signed.zip" .
I have no clue as to the purpose of this step. This gapps-gb file file has a completely different number than the encore file. Example: the encore file had the number 01262012 - the gapps file you suggested has the number 20110828.
Another person who responded to my original post mentioned a different gapps file that automatically enlarged the Boot/Root partition to 200 Megabytes. It had a different name and number than the one you suggested. It seems logical to me that the gapps zip and the encore zip must work together.
How can I (and others) know which ones are compatible with one another?
I copied "gapps-gb-20110930-237-signed.zip over to the Boot/Root of the SD card. And I renamed it to "update_gapps-gb-20110930-237-signed.zip".
So, at this point there were two zipped files in the Boot/Root Partition of my SD card. They are:
update_encore_CM72-Mirage-01262012.zip
and
update_gapps-gb-29119839-237-signed.zip
Note: because I don't know the relationship between these two archived zipped files - I have no idea if they are compatible.
You also wrote:
Suggested step 5. Put the scard in the Nook and it should boot and fully install the Android system, CM72, Google apps, and then turn itself off. Turn it back on and you should get the Google Android setup screens.
OK. I did this. And my Nook did the update process. I saw maybe 20 or so files that appeared on the screen (for some reason it happens in landscape mode).
My Nook Color then shut itself off.
So far, so good.
So I press the power button and the Nook Color starts up.
BUT now it tries to do the Update process again. It cannot find the zipped files this time since they have already been expanded. So it just shuts the machine down. Restarting several times results in the very same thing.
The Nook Color does not take me into the Android Operating system where I can begin setting up the apps I want.
So - what went wrong?
My guess is that the Encore and the Gapps files I used were incompatible. Are there other issues that could be the cause if this failure?
Please know that if I can solve this (with the help of some of the more patient people in this forum) my hope is to create a post that can be turned into a Sticky for Nubes. I hope you folks won't give up on me. I'm trying not only to do what is needed for me, but also to help other nubes understand the process.
Thanks to all of you!!!
Bach On
I can understand your feelings on this. But the truth is that I did not know how to do it. I agree that the information is here. But frankly, it is not in an easy to understand form. This is a huge website. And there is so much information that it is daunting to find the right steps.
I could probably fix my car when it has a problem. There are lots of resources on the Internet to tell me what to do. But I usually take it to a mechanic who is experienced at doing the needed repairs.
I wanted to know what the Android Operating system was like on my Nook Color. And I paid $18.00 for an 8 Gig Sani SD chip with the operating system. I was impressed enough with this operating system that I now want to know more. And I don't feel fleeced.
Maybe they are making a few bucks on the efforts of others. But they helped ease me into the process much quicker than I could have done it on my own. And now I am wanting to learn to do it myself. I only hope that I can help others as I learn.
Take care!
BO
bachon said:
OK. I'm getting closer - thanks to all for their answers. But I want to better understand these steps. Please bear with me. This is the kind of thing that I find confusing. Many of the nubes (like me) can read the step-by-step procedures. But the experienced folks seldom explain WHY and exactly WHAT the purpose of the steps are. And I'm sorry to say that they sometimes leave out crucial details. I'm not just asking for me - but for the many nubes here. (See below.)
So let's take these suggested steps and use them as Question and Answer to help other nubes like me better understand what is being done and why.
Suggested Step 1. Use Win32DiskImager.exe to burn the "generic-sdcard-v1.3.img" onto your "virgin" sdcard.
Please check my understanding of what these steps represent and correct if I am wrong.
Generic-sdcard-v1.3.img is like a template. So this first step creates the four required partitions on my SDcard. My Nook Color is going to require this to be able to install or update the Android operating system. Is that right?
Suggested step 2. Use Easeus Partition Manager to resize the boot partition on your newly bootable sdcard to 200MB.
The Generic -sdcard-v1.3.img template doesn't make the BOOT partition quite large enough for the zipped files I'm going to need to copy to it. (Boot partition is sometimes called the Root.) So step 2 does that. Am I right?
Suggested step 3. copy "encore_CM72-Mirage-01262012.zip" to root of sdcard, and rename it to "update_CM72-Mirage-01262012.zip".
Before I do this: each of these zipped variants is like the equivalent of the Operating System on a computer hard drive. And there are multitudes of these operating systems out there for my Nook Color. Right?
So now I copy the zipped encore file from my hard drive to the Boot/Root partition of the SDcard. A simple copy and paste is fine for doing this. And I should NOT expand the zipped file. Right?
Question for Clarification here: if this zipped encore file was my very first install of a non-Barnes & Nobel Operating system on my Nook Color - is it still necessary to rename it to update, or can I keep the original name of this zipped file?
Since I already installed CM7.1.0 RC1-encore on my Nook Color, this newer zipped file ("encore_CM72-Mirage-01262012.zip") is an upgrade. So I need to rename the first part of that encore file to be update . My Nook Color won't know what to do if I don't do that.
So I now have one file called "update_encore_CM72-Mirage-01262012.zip" into the Boot/Root Partition on the SD card.
Is this correct?
Suggested step 4. copy "gapps-gb-20110828-signed.zip" to root of sdcard and rename it to "update-gapps-gb-20110828-signed.zip" .
I have no clue as to the purpose of this step. This gapps-gb file file has a completely different number than the encore file. Example: the encore file had the number 01262012 - the gapps file you suggested has the number 20110828.
Another person who responded to my original post mentioned a different gapps file that automatically enlarged the Boot/Root partition to 200 Megabytes. It had a different name and number than the one you suggested. It seems logical to me that the gapps zip and the encore zip must work together.
How can I (and others) know which ones are compatible with one another?
I copied "gapps-gb-20110930-237-signed.zip over to the Boot/Root of the SD card. And I renamed it to "update_gapps-gb-20110930-237-signed.zip".
So, at this point there were two zipped files in the Boot/Root Partition of my SD card. They are:
update_encore_CM72-Mirage-01262012.zip
and
update_gapps-gb-29119839-237-signed.zip
Note: because I don't know the relationship between these two archived zipped files - I have no idea if they are compatible.
You also wrote:
Suggested step 5. Put the scard in the Nook and it should boot and fully install the Android system, CM72, Google apps, and then turn itself off. Turn it back on and you should get the Google Android setup screens.
OK. I did this. And my Nook did the update process. I saw maybe 20 or so files that appeared on the screen (for some reason it happens in landscape mode).
My Nook Color then shut itself off.
So far, so good.
So I press the power button and the Nook Color starts up.
BUT now it tries to do the Update process again. It cannot find the zipped files this time since they have already been expanded. So it just shuts the machine down. Restarting several times results in the very same thing.
The Nook Color does not take me into the Android Operating system where I can begin setting up the apps I want.
So - what went wrong?
My guess is that the Encore and the Gapps files I used were incompatible. Are there other issues that could be the cause if this failure?
Please know that if I can solve this (with the help of some of the more patient people in this forum) my hope is to create a post that can be turned into a Sticky for Nubes. I hope you folks won't give up on me. I'm trying not only to do what is needed for me, but also to help other nubes understand the process.
Thanks to all of you!!!
Bach On
Click to expand...
Click to collapse
You'll need to try again ! A couple observations:
1. Watch the process evolve on the screen of your Nook. You may see a clue as to why your build did not work.
2. use the Google Apps file from my earlier post,"gapps-gb-20110828-signed.zip"
available at the bottom of this page, http://wiki.cyanogenmod.com/index.php?title=Latest_Version .
3. If you don't have an CM ...zip file beginning with "update-" , you will be told , on the screen, that it is missing and must be renamed.
4. Most importantly, watch the screen as the process unfolds. It will be educational and if problems persist, may yield some clues to the problem.
Breaking this down for you and trying to answer/explain your questions:
bachon said:
OK. I'm getting closer - thanks to all for their answers. But I want to better understand these steps. Please bear with me. This is the kind of thing that I find confusing. Many of the nubes (like me) can read the step-by-step procedures. But the experienced folks seldom explain WHY and exactly WHAT the purpose of the steps are. And I'm sorry to say that they sometimes leave out crucial details. I'm not just asking for me - but for the many nubes here. (See below.)
So let's take these suggested steps and use them as Question and Answer to help other nubes like me better understand what is being done and why.
Suggested Step 1. Use Win32DiskImager.exe to burn the "generic-sdcard-v1.3.img" onto your "virgin" sdcard.
Please check my understanding of what these steps represent and correct if I am wrong.
Generic-sdcard-v1.3.img is like a template. So this first step creates the four required partitions on my SDcard. My Nook Color is going to require this to be able to install or update the Android operating system. Is that right?
Click to expand...
Click to collapse
Generic-sdcard.... is a disk image file... it includes the script for partitioning the uSD (if needed), formatting the partitions, installing ROM and gapps.
bachon said:
Suggested step 2. Use Easeus Partition Manager to resize the boot partition on your newly bootable sdcard to 200MB.
The Generic -sdcard-v1.3.img template doesn't make the BOOT partition quite large enough for the zipped files I'm going to need to copy to it. (Boot partition is sometimes called the Root.) So step 2 does that. Am I right?
Click to expand...
Click to collapse
Correct... the sd image will have a single partition (root partition is labeled "boot") that is ~114 MB... ROMs are getting larger... resizing it now will save headache later.
bachon said:
Suggested step 3. copy "encore_CM72-Mirage-01262012.zip" to root of sdcard, and rename it to "update_CM72-Mirage-01262012.zip".
Click to expand...
Click to collapse
This rename is due to the installer/updater script looking for specific naming at the beginning of the filename (update-* or cm_encore_full*)... note the * is an OS wildcard meaning anything. After any ROMs have been installed, the installer/updater looks for a file named gapps-gb-* for processng.
bachon said:
Before I do this: each of these zipped variants is like the equivalent of the Operating System on a computer hard drive. And there are multitudes of these operating systems out there for my Nook Color. Right?
Click to expand...
Click to collapse
There are various ROMs and variations of them, yes. Some name them differently to avoid confusion with standard "official" ROMs. It would be easier for uSD installers if the maintained the "update-" naming convention.
bachon said:
So now I copy the zipped encore file from my hard drive to the Boot/Root partition of the SDcard. A simple copy and paste is fine for doing this. And I should NOT expand the zipped file. Right?
Click to expand...
Click to collapse
Yes... copy/paste... do NOT extract (that's what the installer/updater does)
bachon said:
Question for Clarification here: if this zipped encore file was my very first install of a non-Barnes & Nobel Operating system on my Nook Color - is it still necessary to rename it to update, or can I keep the original name of this zipped file?
Click to expand...
Click to collapse
See the answer above regarding what the installer/updater script expects for the naming.
bachon said:
Since I already installed CM7.1.0 RC1-encore on my Nook Color, this newer zipped file ("encore_CM72-Mirage-01262012.zip") is an upgrade. So I need to rename the first part of that encore file to be update . My Nook Color won't know what to do if I don't do that.
So I now have one file called "update_encore_CM72-Mirage-01262012.zip" into the Boot/Root Partition on the SD card.
Is this correct?
Click to expand...
Click to collapse
See above.
bachon said:
Suggested step 4. copy "gapps-gb-20110828-signed.zip" to root of sdcard and rename it to "update-gapps-gb-20110828-signed.zip" .
Click to expand...
Click to collapse
You do NOT need to rename gapps and it is NOT recommended you do so... the installer/updater will install any and all cm_full_* and update-* files... then process gapps. I personally recommend a 2 step process for this... install the ROM without gapps on the drive... then place gapps on the drive and boot into recovery again for the install of that... has just fixed issues in the past this way.
bachon said:
I have no clue as to the purpose of this step. This gapps-gb file file has a completely different number than the encore file. Example: the encore file had the number 01262012 - the gapps file you suggested has the number 20110828.
Click to expand...
Click to collapse
the number is referencing the date, some are YYYYMMDD some are MMDDYYYY.
bachon said:
Another person who responded to my original post mentioned a different gapps file that automatically enlarged the Boot/Root partition to 200 Megabytes. It had a different name and number than the one you suggested. It seems logical to me that the gapps zip and the encore zip must work together.
Click to expand...
Click to collapse
There is no gapps installer that enlarges the boot partition... they are referencing an updated uSD image file with a larger boot partition due to ICS builds... also note that ICS builds require different gapps than the CM7 variants and become even more confusing... for CM7 stick with the gapps that is on the CM7 wiki pages.
bachon said:
How can I (and others) know which ones are compatible with one another?
Click to expand...
Click to collapse
This gets daunting... answer above.
bachon said:
I copied "gapps-gb-20110930-237-signed.zip over to the Boot/Root of the SD card. And I renamed it to "update_gapps-gb-20110930-237-signed.zip".
So, at this point there were two zipped files in the Boot/Root Partition of my SD card. They are:
update_encore_CM72-Mirage-01262012.zip
and
update_gapps-gb-29119839-237-signed.zip
Note: because I don't know the relationship between these two archived zipped files - I have no idea if they are compatible.
Click to expand...
Click to collapse
See answer above regarding naming conventions and recommendation pertaining one step install (with both files on SD) v. two step (ROM first then gapps seperately)
bachon said:
You also wrote:
Suggested step 5. Put the scard in the Nook and it should boot and fully install the Android system, CM72, Google apps, and then turn itself off. Turn it back on and you should get the Google Android setup screens.
OK. I did this. And my Nook did the update process. I saw maybe 20 or so files that appeared on the screen (for some reason it happens in landscape mode).
My Nook Color then shut itself off.
So far, so good.
So I press the power button and the Nook Color starts up.
BUT now it tries to do the Update process again. It cannot find the zipped files this time since they have already been expanded. So it just shuts the machine down. Restarting several times results in the very same thing.
The Nook Color does not take me into the Android Operating system where I can begin setting up the apps I want.
So - what went wrong?
My guess is that the Encore and the Gapps files I used were incompatible. Are there other issues that could be the cause if this failure?
Click to expand...
Click to collapse
Once the installer/updater installs a zip file... it deletes it... also note... the first boot after an install take a VERY LONG TIME
bachon said:
Please know that if I can solve this (with the help of some of the more patient people in this forum) my hope is to create a post that can be turned into a Sticky for Nubes. I hope you folks won't give up on me. I'm trying not only to do what is needed for me, but also to help other nubes understand the process.
Thanks to all of you!!!
Bach On
Click to expand...
Click to collapse
This would be very good to do... hopefully I have provided enough information to get you started.
Success.
I’m going to post this under my original post so nubes can find it more quickly. Many won’t take time to drill down into the thread. It would still be helpful of some of the experts would address some of the questions asked in this long winded report. [/B]
I discovered some mistakes in my understanding in the Question and Answer part of this LONG post. I’m going to try to correct it.
OK. I'm getting closer - thanks to all for their answers. But I want to better understand these steps. Please bear with me. This is the kind of thing that I find confusing. Many of the nubes (like me) can read the step-by-step procedures. But the experienced folks seldom explain WHY and exactly WHAT the purpose of the steps are. And I'm sorry to say that they sometimes leave out crucial details. I'm not just asking for me - but for the many nubes here. (See below.)
So let's take these suggested steps and use them as Question and Answer to help other nubes like me better understand what is being done and why.
Suggested Step 1. Use Win32DiskImager.exe to burn the "generic-sdcard-v1.3.img" onto your "virgin" sdcard.
Please check my understanding of what these steps represent and correct if I am wrong.
Generic-sdcard-v1.3.img is like a template. So this first step creates the four required partitions on my SDcard. My Nook Color is going to require this to be able to install or update the Android operating system. Is that right?
Self Correction: NO. The Generic–sdcard-v1.3.img only creates the Boot/Root partition and writes the files needed to make the sdcard bootable in the Nook Color.
Suggested step 2. Use Easeus Partition Manager to resize the boot partition on your newly bootable sdcard to 200MB.
The Generic -sdcard-v1.3.img template doesn't make the BOOT partition quite large enough for the zipped files I'm going to need to copy to it. (Boot partition is sometimes called the Root.) So step 2 does that. Am I right?
Suggested step 3. copy "encore_CM72-Mirage-01262012.zip" to root of sdcard, and rename it to "update_CM72-Mirage-01262012.zip".
Self Correction: there is a typo in the previous statement. The encore file should be renamed “update-cm-72-Mirage-0126012.zip”. I had an underscore symbol instead of a dash. I also had “encore” as the word after update. I believe it needs to begin with “update-cm”.
And one more thing. Some operating systems omit the .zip suffix on the filename. The Nook Color seems unable to recognize the archive without .ZIP at the end of the archive name.
Before I do this: each of these zipped variants is like the equivalent of the Operating System on a computer hard drive. And there are multitudes of these operating systems out there for my Nook Color. Right?
So now I copy the zipped encore file from my hard drive to the Boot/Root partition of the SDcard. A simple copy and paste is fine for doing this. And I should NOT expand the zipped file. Right?
Question for Clarification here: if this zipped encore file was my very first install of a non-Barnes & Nobel Operating system on my Nook Color - is it still necessary to rename it to update, or can I keep the original name of this zipped file?
Since I already installed CM7.1.0 RC1-encore on my Nook Color, this newer zipped file ("encore_CM72-Mirage-01262012.zip") is an upgrade. So I need to rename the first part of that encore file to be update . My Nook Color won't know what to do if I don't do that.
So I now have one file called "update_encore_CM72-Mirage-01262012.zip" into the Boot/Root Partition on the SD card.
Is this correct?
Suggested step 4. copy "gapps-gb-20110828-signed.zip" to root of sdcard and rename it to "update-gapps-gb-20110828-signed.zip" .
Self Correction: Still not sure about the compatibility issues. But as with the other Zip archive, the archive name must be renamed to read “update-gapps-bg-20110828-signed zip”. (The quotes and final period are not used in the name.) Again, the .ZIP suffix must be on the end of the archive name.
I have no clue as to the purpose of this step. This gapps-gb file file has a completely different number than the encore file. Example: the encore file had the number 01262012 - the gapps file you suggested has the number 20110828.
Another person who responded to my original post mentioned a different gapps file that automatically enlarged the Boot/Root partition to 200 Megabytes. It had a different name and number than the one you suggested. It seems logical to me that the gapps zip and the encore zip must work together.
How can I (and others) know which ones are compatible with one another?
I copied "gapps-gb-20110930-237-signed.zip over to the Boot/Root of the SD card. And I renamed it to "update_gapps-gb-20110930-237-signed.zip".
So, at this point there were two zipped files in the Boot/Root Partition of my SD card. They are:
update_encore_CM72-Mirage-01262012.zip
and
update_gapps-gb-29119839-237-signed.zip
Note: because I don't know the relationship between these two archived zipped files - I have no idea if they are compatible.
You also wrote:
Suggested step 5. Put the scard in the Nook and it should boot and fully install the Android system, CM72, Google apps, and then turn itself off. Turn it back on and you should get the Google Android setup screens.
OK. I did this. And my Nook did the update process. I saw maybe 20 or so files that appeared on the screen (for some reason it happens in landscape mode).
My Nook Color then shut itself off.
So far, so good.
So I press the power button and the Nook Color starts up.
BUT now it tries to do the Update process again. It cannot find the zipped files this time since they have already been expanded. So it just shuts the machine down. Restarting several times results in the very same thing.
The Nook Color does not take me into the Android Operating system where I can begin setting up the apps I want.
So - what went wrong?
My guess is that the Encore and the Gapps files I used were incompatible. Are there other issues that could be the cause if this failure?
Please know that if I can solve this (with the help of some of the more patient people in this forum) my hope is to create a post that can be turned into a Sticky for Nubes. I hope you folks won't give up on me. I'm trying not only to do what is needed for me, but also to help other nubes understand the process.
Thanks to all of you!!!
Bach On
Final Remarks on the post: after correcting the typos, the update took place and the Nook Color shut itself down.
There were then four Active Partitions on the sdcard. So one or more of the archives created the 3 extra partitions that weren’t there.
The Nook Color then booted up and I was allowed to setup Market, Wifi, etc. I will have to reinstall applications I had working before. No problem there.
BO
You got it - congrats!
If you want to try some of the CM9 nightlies (lots of fun on an extra card) - I've had good success by doing everything together... SP2, CM9 nightly and gapps together in one install and boot... and it does get you to Android Setup right off the bat!
see http://forum.xda-developers.com/showthread.php?t=1444943 for more info. Sam has also included the new expanded Generic SD image there.
Nobody has answered my question about compatibility between the encore zip and the gapps zip. Not sure, yet, which does what and if there are issues that must be understood in choosing these. I did get it done, but I want to be able to explain it to others.
Thanks for all the help, folks!
BO
Sam Adams said:
Leapinlar just posted an expanded Generic SD Image that does away with manually expanding the boot partition - I believe it's around 200mb... I just tried it and it works great! You can find it here: http://d01.megashares.com/index.php?d01=NcUqquQ
Please take time to thank Leapinlar (and Verygreen) - he worked hard on this!
Click to expand...
Click to collapse
I saw that posted in the ICS thread. Does it work for CM 7, as well? I can't see why not, but figured I'd ask. Thanks.
If I remember correctly I used it for making a CM7 card. Works fine because it's just for getting the card ready for whatever you're going to put on it and use.
I'm old though so my memory fails often. :what:
Sent from my NookColor running CM7.2-RC0 MiRaGe - KANG 02012012 using TapaTalk
bachon said:
Nobody has answered my question about compatibility between the encore zip and the gapps zip. Not sure, yet, which does what and if there are issues that must be understood in choosing these. I did get it done, but I want to be able to explain it to others.
Thanks for all the help, folks!
BO
Click to expand...
Click to collapse
You need to read my previous and long post in this thread answering your questions
bachon said:
Nobody has answered my question about compatibility between the encore zip and the gapps zip. Not sure, yet, which does what and if there are issues that must be understood in choosing these. I did get it done, but I want to be able to explain it to others.
Thanks for all the help, folks!
BO
Click to expand...
Click to collapse
There is no direct compatibility issue here other than getting a good base set appropriate for either CM7 or ICS/CM9.
The ROM is the ROM and will run quite happily without gapps. Think of it as your basic Windows OS.
Gapps is a set of Google applications. They are not part of the base OS but are quite important because they give you some basic applications like Calendars and eMail. Most important of all they give a Vending application which allows you to access the Google apps market. Once there you can load and update other apps including the Google apps themselves.
For CM7 you can start with the 20110828 labelled version.
To emphasise the independence of the ROM and the gapps many CM7 install instructions recommended installing the ROM first and getting it going and the wifi set up before even installing gapps.
For ICS/CM9 there are several versions available because they come pre-loaded with tablet/ICS versions of the Google apps which are more appropriate than than the CM7 ones. Quite a few of the alpha CM9 ROM builds point to a good starting gapps. For example, this link is to one of the popular ICS and includes a link to a decent starting gapps.
I did read your very informative post. I've started to prepare an introductory post for possible submission. I'd like to run this by you for your input, if you don't mind.
I'm going to provide you with an e-mail address: [email protected]
If you send a brief e-mail to that address then I send my draft. If you don't want to fool with it, no hard feelings.
Thanks!
BO
No problem at all... just send it to [email protected]
Can't get cm7 to boot from sd card
This is the closest thread I can find to my problem; please excuse me if some of my language is not accurate.
Wrote the generic-sdcard-v1.3ICS-large.img to a 16 gig sd card with win32diskimager.exe. . Copied cm-7.2.0-encore.zip and the gapps zip file to the sd card and renamed the cm file to update-cm-7.20encore.zip. Ejected the sd card, put into my nook. Nook booted from the card and successfully ran through the installation of the android system and gapps and shut down. Cannot successfully boot from the sd disk. It will show the cyanogen flash screen and "loading" and then go to a blank screen. It will sometimes go to the screen with the skateboarding robot with the arrow going around in a circle. I have tried the process many times and get the same result. I was successful once in getting the android system to boot and thought aha, finally there. Computer would not recognise the nook so played with that - and decided I need to reflash the sd card. No success since then - getting very frustrated.
Thanks for any help.
JPB
My wife has a NC and likes it the way it is, i.e. BN store, but I would like to add an app that does not require root. I was thinking that I could use a clockwork recovery SD card with a zip of the app, just like we do with google apps.
Will this work?
How do I make a apk into a flashable zip?
The app is You Version Bible
Thanks
-EDIT-
So I have figured this out, it is possible to install apps (that do not require root) with out rooting anything. I would call it side loading via CWM sd card.
The key was to use the mount paths from ManualNooter (\META-INF\com\google\android\updater-script)
0.1.) Get apks for you apps (either with titanium or copy from 'data/app')
0.2.) Get a apk for 'Nook Color App Manager' (search the android market, can't post links yet)
1.) Start with the ManualNooter file and remove all folders but 'data' and 'META-INF'
2.) Delete all files in the 'data/app' folder
3.) Place the apks you want to install in the 'data/app' folder
4.) Edit '\META-INF\com\google\android\updater-script' using a programing text editor (otherwise you will not see the line spaces) remove all sections except the following: 'Mounting partitions...' 'Installing apks to /data/app...' 'Unmounting Partitions...'
5.) Save the script file and put all this back together in the zip.
6.) Use the CWM sd card to install the file. (if you don't know how, use google)
7.) Remove card and reboot after done. A new app App Manager will show up in your nook app list, go to the home page to run it and add links for your new installed apps.
Note: I did not post an files as I used other peoples work i.e. GMPOWER and apps from the market
So I have done lots of research and even tried this. I think I got the app installed but in this case there is no way to show the app in the stock launcher as it only lists apps it installs.
For reference I will include the procedure to install apps via CMW(Clockwork Mod Recovery)
Thread
You download the file attached to post 17 in the above thread, it is a empty zip that can be filled with your apks that you want. Simply place the new file on a CWM sd card and install the file via regular instructions in the above post.
If I ever find a script to add a link to the stock launcher I will post that and then this might be a usable idea for side loading apps.
I'd like to change the wallpaper on the root u-tube home screen, but I don't see how one can access the internal folders. I'd like to be use adb push but I don't know the path for the 'Picture', or 'Wallpaper gallery Home' that are possible locations for adding the images.
You do mean the desktop wallpaper?
I'm boring. I just changed the default wallpaper to solid white.
In /system/framework/framework-res.apk
Replace /res/drawable-mdpi/default_wallpaper.png
To answer your original question: I don't know.
Thanks for the information; however being a complete beginner that does help me get a little bit closer to what I'd like to do but there is still much that I don't really understand. How do I access that location? And should I add my new image to the subfolder with a totally differently name, or should I rename the my image to that of the default.png and replace the old image?
If I adb push to the nook my image renamed to match the old wallpaper image, will that work?
still trying to replace home image in rooted Nook ST
I have a question for someone who knows more than I about android systems. Thanks to Thank Meter 78 who pointed out the file I need to change in order to replace the home image is in
/system/framework/framework-res.apk
and that I need to replace in that apk
/res/drawable-mdpi/default_wallpaper.png
Will the following procedure work properly without screwing up my newly rooted Nook?
Using Root Explorer I copied the 'framework-res.apk', and saved it to my Nook sd card. Then copied that apk file to my windows xp computer and changed the extension to 'zip' and unzipped it. The png file thus is available for replacement by another image of identical size and name.
Will it be correct for me to rename the modified .zip extenson file containing a new default_wallpaper.png file back to its original .apk extension, copy/paste it to the sd card, insert the sd card into the Nook, and the using Root Explorer to copy the apk file and paste it back to the drawable-mdpi folder where it will replace the nook apk (being sure that I change the r/o to r/w permission for the folder, and change it back after the replacement)?
Could there be adverse effects of the replacement?
My friends all call me Renate...
Yes, that procedure works, correcting for your typo.
Unzip, replace PNG, zip, copy back to /system/framework/framework-res.apk
You don't need to set it back to r/o. It's better/easier to just reboot, preferably with ADB.
You should always backup at reasonable intervals and before major changes.
Heck, I've bricked my Nook a dozen times.
Thanks Renate!
Ok, the actual answer is:
The gallery uses the mediastore images database.
The crawler can't find anything even if it's right under its nose.
The databases are stored in /data/data/com.android.providers.media/databases
There's internal.db and another db for each unique SD card inserted.
The crawler is equally lame finding MP3's also.
That's why both Music and Gallery say "no media".
Renate NST said:
Ok, the actual answer is:
The gallery uses the mediastore images database.
The crawler can't find anything even if it's right under its nose.
The databases are stored in /data/data/com.android.providers.media/databases
There's internal.db and another db for each unique SD card inserted.
The crawler is equally lame finding MP3's also.
That's why both Music and Gallery say "no media".
Click to expand...
Click to collapse
1) I thought the original question was about u-tube (I guess "Youtube" ;-))
2) ad gallery - I was always wondering how to make it see the JPGs I had as screensavers... Would you have any ideas how to fix this (i.e. make the crawler work)? Or maybe the other way round, how often is the crawler running? Would battery be improved if it was turned off/killed?
The Media Scanner service is what scans.
Normally it is activated on insertion of an SD card.
It does not run continuously.
It ignores directories with file in it called ".nomedia"
The MediaScannerConnection can be used to request scanning of a single file.
Level 8 API (we're 7) can request scanning of multiple files.
It seems to turn its nose up at files and not put them in its database.
ajislav said:
2) ad gallery - I was always wondering how to make it see the JPGs I had as screensavers... Would you have any ideas how to fix this (i.e. make the crawler work)? Or maybe the other way round, how often is the crawler running? Would battery be improved if it was turned off/killed?
Click to expand...
Click to collapse
Are you asking about having your own pics as screensavers?
I did that by connecting my NST to the PC, and creating a folder (one word name) under screensavers/ and copying the pics into that folder. It then shows up in the screensavers menu, and you can select it. The location from within the nook is /media/screensavers
--
The emulator's MediaScanner works fine, the Nook's appears broken.
You can manually enter images into the MediaStore:
(This requires sqlite3 installed or pull the database and do it on your desktop.)
Code:
sqlite3 /data/data/com.android.providers.media/databases/internal.db
insert into images (_data, mime_type) values('/media/myphoto.png', 'image/png');
.q
Call up Gallery.
You will see a blank thumbnail because one has not been generated yet.
Click on that.
Renate NST said:
The emulator's MediaScanner works fine, the Nook's appears broken.
You can manually enter images into the MediaStore:
(This requires sqlite3 installed or pull the database and do it on your desktop.)
Code:
sqlite3 /data/data/com.android.providers.media/databases/internal.db
insert into images (_data, mime_type) values('/media/myphoto.png', 'image/png');
.q
Call up Gallery.
You will see a blank thumbnail because one has not been generated yet.
Click on that.
Click to expand...
Click to collapse
Isn't their any way to repair the nooks MediaScanner? like, re-install it, clear the app data, copy another one in from another android 2.1 device? I don't understand why it isn't working, or why it can't be fixed. I've tried backing up the app and re-installing it, deleting the external db's, running media scan apps. Disabling it, re-enabling it...
I am getting my Nook ST from ebay very soon. Please help me understand the process:
What is the difference between just rooting using Nook Manager and flashing a ROM like 1337?
I am assuming, I can still install APKs after rooting?
thanks
S
sany said:
I am getting my Nook ST from ebay very soon. Please help me understand the process:
What is the difference between just rooting using Nook Manager and flashing a ROM like 1337?
I am assuming, I can still install APKs after rooting?
thanks
S
Click to expand...
Click to collapse
Rooting with NookManager gives you access to "root" directories that are normally off limits to users. It also allows for various customizations. It sets the security flag for installing from "unknown sources", allowing you to install apps via a file manager (or ADB), as opposed to getting them from the PlayStore (which you can't anymore). And it installs a base set of apps to get you going, like a file manager, launcher, browser, etc. That is customizable.
Custom ROMs like the 1337 simply enable different features that some people like. Perhaps better to use the system "as-is" for a bit before you decide to wipe it out? Then you'll have a better idea of what you'd like to have.
nmyshkin said:
Rooting with NookManager gives you access to "root" directories that are normally off limits to users. It also allows for various customizations. It sets the security flag for installing from "unknown sources", allowing you to install apps via a file manager (or ADB), as opposed to getting them from the PlayStore (which you can't anymore). And it installs a base set of apps to get you going, like a file manager, launcher, browser, etc. That is customizable.
Custom ROMs like the 1337 simply enable different features that some people like. Perhaps better to use the system "as-is" for a bit before you decide to wipe it out? Then you'll have a better idea of what you'd like to have.
Click to expand...
Click to collapse
Thank you @nmyshkin, I think my liking will be towards Nook Manager. So I will try to get ready with the Nook Manager installation files and instruction. The only thing confusing here in the forum is there are too many threads and geeting lost which and where to start. Hope if I start with the original thread which is from way back 2012, it will still work. My understanding is if I am on a new firmware 2.1.2 I will rewrite the modification files to nook manager as per that thread.
thanks again
S
sany said:
Thank you @nmyshkin, I think my liking will be towards Nook Manager. So I will try to get ready with the Nook Manager installation files and instruction. The only thing confusing here in the forum is there are too many threads and geeting lost which and where to start. Hope if I start with the original thread which is from way back 2012, it will still work. My understanding is if I am on a new firmware 2.1.2 I will rewrite the modification files to nook manager as per that thread.
thanks again
S
Click to expand...
Click to collapse
Here's how you get started:
1. When you get your NST, execute a factory reset. This will return the device to an out-of-the-box condition. To do this, power up and as soon as you see the "Read Forever, your Nook is starting up" screen, hold the two lower hardware buttons until you see a screen prompt.
2. Register your device with B&N.
3. Update the firmware to 1.2.2 (https://su.barnesandnoble.com/nook/nook2/1.2.2/351e26527e80156183e74be2da2ce89f/nook_1_2_update.zip)
4. Prepare a NookManager card according to the instructions here: https://forum.xda-developers.com/nook-touch/development/nst-g-updating-nookmanager-t3873048, making whatever changes/additions you want in terms of base software such as a file manager, browser, launcher, etc.
5. Run NookManager. Before you do anything else I suggest you make a backup of the newly updated and registered NST. That way if something goes wrong, you won't have to go all the way back to a factory reset. After the backup, root the NST and exit NookManager.
After that, it's pretty much up to you. Any time you want to make another backup, just reboot with the NookManager card inserted and make a backup. Just remember that the backup will replace whatever is on the NookManager card, so if you wanted to keep that one, you need to have copied it to your PC first.
nmyshkin said:
Here's how you get started:
1. When you get your NST, execute a factory reset. This will return the device to an out-of-the-box condition. To do this, power up and as soon as you see the "Read Forever, your Nook is starting up" screen, hold the two lower hardware buttons until you see a screen prompt.
2. Register your device with B&N.
3. Update the firmware to 1.2.2 .
Click to expand...
Click to collapse
Very helpful! thanks again.
nmyshkin said:
2. Register your device with B&N.
Click to expand...
Click to collapse
How important is this step - do I really need to register? any advantages and disadvantages?
sany said:
How important is this step - do I really need to register? any advantages and disadvantages?
Click to expand...
Click to collapse
The device software is designed to sell ebooks from B&N. Anything that frustrates this design (like not registering or disabling parts of the B&N system) tends to raise all kinds of internal alarms and the system dialogs constantly with itself, worrying about its purpose in life, its inability to "phone home", and generally fritters away a lot of its battery charge on rehearsing for a role it cannot assume.
In short, the path of least resistance results in the least system hand-wringing, improved battery life, etc. You don't need to enter any credit card information. All you need is an email address (which I suppose could be fake) and a password. Then you can forget about it if you have no interest in purchasing ebooks from B&N. I have completely ignored the B&N system except for the Reader and Library which I find adequate--and simple--enough for my needs. But everything else is hidden. It just lives its happy little digital life waiting for that one special day when I will buy an ebook with a patience only electrons can exhibit. Meanwhile I have all kinds of other stuff that I am interested in and there don't seem to be any issues or conflicts with the B&N system.
My 2 cents.
Installed but no apps
nmyshkin said:
Here's how you get started:
1. When you get your NST, execute a factory reset. This will return the device to an out-of-the-box condition. To do this, power up and as soon as you see the "Read Forever, your Nook is starting up" screen, hold the two lower hardware buttons until you see a screen prompt.
2. Register your device with B&N.
3. Update the firmware to 1.2.2 (https://su.barnesandnoble.com/nook/nook2/1.2.2/351e26527e80156183e74be2da2ce89f/nook_1_2_update.zip)
4. Prepare a NookManager card according to the instructions here: https://forum.xda-developers.com/nook-touch/development/nst-g-updating-nookmanager-t3873048, making whatever changes/additions you want in terms of base software such as a file manager, browser, launcher, etc.
5. Run NookManager. Before you do anything else I suggest you make a backup of the newly updated and registered NST. That way if something goes wrong, you won't have to go all the way back to a factory reset. After the backup, root the NST and exit NookManager.
After that, it's pretty much up to you. Any time you want to make another backup, just reboot with the NookManager card inserted and make a backup. Just remember that the backup will replace whatever is on the NookManager card, so if you wanted to keep that one, you need to have copied it to your PC first.
Click to expand...
Click to collapse
I successfully backed up and rooted the device. Firmware is 1.2.2.
But I don't have any apps. Not even the base software. See screenshot. Even the extras like es file explorer were not installed. Since I don't have any file explorer, I am unable to install any apps. I want to go for ADB method as last resort. Please advice.
Thanks
sany said:
I successfully backed up and rooted the device. Firmware is 1.2.2.
But I don't have any apps. Not even the base software. See screenshot. Even the extras like es file explorer were not installed. Since I don't have any file explorer, I am unable to install any apps. I want to go for ADB method as last resort. Please advice.
Thanks
Click to expand...
Click to collapse
You can try for ADB (more headaches there), but it would be better now to get some useful apps and have a way to conveniently side-load others. You are supposed to be able to install apps from Relaunch in the file manager screen. That would involve copying the apk file to the NST via a USB connection, then locating that apk file using the file folder browser and tapping on the icon. I could never get that to work, but it is supposed to work.
Failing that, you need to revisit NookManager. You must not have done the customization correctly if none of the apps you wanted were installed. If you can get that fixed, you can simply root again with NookManager (right on top of what you have now) and it will fix the problem IF you get it set up correctly.
There are four steps required to add an app to the NookManager rooting routine:
1. Copy the apk file to the folder files/data/app on the NookManager SD card
2. in the folder "scripts" on the NookManager SD card, copy and rename one of the "install_x" files so it represents the app you just moved into the folder in step 1. So, if you want ES File Explorer, you might rename the file "install_esfileexplorer"
3. Edit the file you just copied and renamed, changing the name of the apk file in the first line to exactly match the filename of the apk file you have replaced in files/data/app. So continuing the example, "es_file_explorer.apk" (which is the name of the apk file as I provided it). Then edit the "echo" statement so it reads something like "echo ES File Explorer installed"
4. Locate the file scripts/do_root. Copy and rename one of the "install_x" files so it matches what you did earlier, in this case "install_es_file_explorer". There are no contents to edit.
You need to do those four steps for each app you want to add to the install list. To remove an app you don't want (like the Amazon App Store), remove the apk file from files/data/app, remove the "install_x" file for that app from the folder "scripts", and remove the "install_x" file for that app from the file scripts/do_root.
nmyshkin said:
Here's how you get started:
1. When you get your NST, execute a factory reset. This will return the device to an out-of-the-box condition. To do this, power up and as soon as you see the "Read Forever, your Nook is starting up" screen, hold the two lower hardware buttons until you see a screen prompt.
2. Register your device with B&N.
3. Update the firmware to 1.2.2 (https://su.barnesandnoble.com/nook/nook2/1.2.2/351e26527e80156183e74be2da2ce89f/nook_1_2_update.zip)
4. Prepare a NookManager card according to the instructions here: https://forum.xda-developers.com/nook-touch/development/nst-g-updating-nookmanager-t3873048, making whatever changes/additions you want in terms of base software such as a file manager, browser, launcher, etc.
5. Run NookManager. Before you do anything else I suggest you make a backup of the newly updated and registered NST. That way if something goes wrong, you won't have to go all the way back to a factory reset. After the backup, root the NST and exit NookManager.
After that, it's pretty much up to you. Any time you want to make another backup, just reboot with the NookManager card inserted and make a backup. Just remember that the backup will replace whatever is on the NookManager card, so if you wanted to keep that one, you need to have copied it to your PC first.
Click to expand...
Click to collapse
Thanks, I followed all those steps...I will take a relook at it. But without es file explorer, I thought there is already a file manager. How to I get there as I can't see anything in the app drawer? (Screenshot in previous post).
sany said:
Thanks, I followed all those steps...I will take a relook at it. But without es file explorer, I thought there is already a file manager. How to I get there as I can't see anything in the app drawer? (Screenshot in previous post).
Click to expand...
Click to collapse
I know very little about Relaunch, but I believe you need to tap on the open door in the upper right corner to get out of the app drawer.
Oh okay! I was expecting to launch file manager from app drawer. So when relaunch opens we are already in file explorer.
One more question: how do we make dictionary work in the default nook reader, that is when you you open a book from library. I thought pressing on a particular word will present me the option. I only see option to bookmark. I have to read the manual again.
sany said:
Oh okay! I was expecting to launch file manager from app drawer. So when relaunch opens we are already in file explorer.
One more question: how do we make dictionary work in the default nook reader, that is when you you open a book from library. I thought pressing on a particular word will present me the option. I only see option to bookmark. I have to read the manual again.
Click to expand...
Click to collapse
That's how the dictionary works for me. Hold your finger on a word until it is highlighted. Then a series of options pops up from the bottom, one of which is "Look up".
nmyshkin said:
You can try for ADB (more headaches there), but it would be better now to get some useful apps and have a way to conveniently side-load others. You are supposed to be able to install apps from Relaunch in the file manager screen. That would involve copying the apk file to the NST via a USB connection, then locating that apk file using the file folder browser and tapping on the icon. I could never get that to work, but it is supposed to work.
Failing that, you need to revisit NookManager. You must not have done the customization correctly if none of the apps you wanted were installed. If you can get that fixed, you can simply root again with NookManager (right on top of what you have now) and it will fix the problem IF you get it set up correctly.
There are four steps required to add an app to the NookManager rooting routine:
1. Copy the apk file to the folder files/data/app on the NookManager SD card
2. in the folder "scripts" on the NookManager SD card, copy and rename one of the "install_x" files so it represents the app you just moved into the folder in step 1. So, if you want ES File Explorer, you might rename the file "install_esfileexplorer"
3. Edit the file you just copied and renamed, changing the name of the apk file in the first line to exactly match the filename of the apk file you have replaced in files/data/app. So continuing the example, "es_file_explorer.apk" (which is the name of the apk file as I provided it). Then edit the "echo" statement so it reads something like "echo ES File Explorer installed"
4. Locate the file scripts/do_root. Copy and rename one of the "install_x" files so it matches what you did earlier, in this case "install_es_file_explorer". There are no contents to edit.
You need to do those four steps for each app you want to add to the install list. To remove an app you don't want (like the Amazon App Store), remove the apk file from files/data/app, remove the "install_x" file for that app from the folder "scripts", and remove the "install_x" file for that app from the file scripts/do_root.
Click to expand...
Click to collapse
\
I followed all your instructions above and successfully installed all apps. To summarise my observation after the successful installation:
1. Only Opera browser app and ES File Explorer app works
2. Yalp app store does not work at all - it just takes me to the next screen with options to 'update' or 'run'. Pressing update keeps searching forever and 'run' takes me back to the previous screen. After several tests, I decided to uninstall the app.
I tried to install youversion bible app which also works (but its a old version) so several features not available. But at least it works.
I noticed wifi outage issues intermittently on the opera browser and also once while trying the yalp store app. It said I was not connected, but I know for a fact I was connected when I connect to the Nook store etc.,
Overall, I am wondering what did I gain out of the whole process. Not much I can do with the custom installation. So I might return back to a original nook after playing with this setup for a while. This leaves me with couple of questions that I will start on a new thread.
Thanks again @nmyshkin for your patience in explaining.
S
To go back to original nook state - do I need to simply go into settings>Device Info> Erase & Deregister Device to get it back to out of box condition? Will this cancel the rooting?
Or do I have to stick the nook manager card and restore from backup?
sany said:
To go back to original nook state - do I need to simply go into settings>Device Info> Erase & Deregister Device to get it back to out of box condition? Will this cancel the rooting?
Or do I have to stick the nook manager card and restore from backup?
Click to expand...
Click to collapse
Erase and deregister will remove root and restore to out-of-the-box state unless you have done something serious. In that case, a factory re-image should solve the problem. That is done by powering off, then powering on and holding down the two lower hardware buttons as soon as the "Read Forever" screen appears. Wait for the prompt and follow it.
Re: Yalp Store, I just checked mine a minute ago and it's running fine. Very rarely it goes down and can't log in to the PlayStore, but it generally comes back later in the day.
Okay - so maybe I should try yalpstore at different times.