Related
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
Need some help here:
I need to delete some of the backups I made with CWM recovery. I already have them backed up onto my PC, but need to delete them to make some room. For some reason I cant.
Ive tried root explorer, es file explorer, and my PC. Im unable to change the permissions of the files, and if you look at the pics I attached youll see they have some strange permissions, but I cant change them.
I am able to move the files anywhere else in the sd card folder, rename them, but no matter what I cant delete them. And when I try from my PC it shows them disappear, but they are actually still there.
If there is a way to format the sd card folder I will, but thats not an option in the settings, or CWM. Can someone please help me out here? This is really frustrating me. Thanks
No issues here when I delete backups using ROM Toolbox.
UnknownFearNG said:
No issues here when I delete backups using ROM Toolbox.
Click to expand...
Click to collapse
I tried through ROM Toolbox and still couldnt delete them.
Gam3r 4 Life said:
I tried through ROM Toolbox and still couldnt delete them.
Click to expand...
Click to collapse
Same, tried with multiple apps too.
I posted this in the other thread, but figured I would do so here in case other people needed the "fix".
Ok, so some good news and some bad news.
The good news is, I was able to put together a flashable zip that WILL DELETE the entire CWM backup directory from the sdcard. It is available here:
http://core.routed.com/CWM_Backup_Wipe.zip
You simply need to flash it via CWM. Easy peasy. I confirmed that the directory/files were all removed, AND the storage space is now available for other files (I checked df before and after).
The bad news is, before attempting to delete the directory, I first tried changing the permissions (recursively) to see if that was a better "fix" for this problem. Unfortunately, even with the directory 777 and the files 666, I still could not manually delete them through the system. Which means, whatever bug is causing this problem is much more severe than a file/directory permission thing.
In any case, until the CWM developer can figure out a way to fix this bug, at least we have a way to manually remove the backups and get our storage space back.
The script in the zip is very simple. It just does a recursive delete on /sdcard/clockworkmod/backup.
Enjoy!
phonic said:
I posted this in the other thread, but figured I would do so here in case other people needed the "fix".
Ok, so some good news and some bad news.
The good news is, I was able to put together a flashable zip that WILL DELETE the entire CWM backup directory from the sdcard. It is available here:
http://core.routed.com/CWM_Backup_Wipe.zip
You simply need to flash it via CWM. Easy peasy. I confirmed that the directory/files were all removed, AND the storage space is now available for other files (I checked df before and after).
The bad news is, before attempting to delete the directory, I first tried changing the permissions (recursively) to see if that was a better "fix" for this problem. Unfortunately, even with the directory 777 and the files 666, I still could not manually delete them through the system. Which means, whatever bug is causing this problem is much more severe than a file/directory permission thing.
In any case, until the CWM developer can figure out a way to fix this bug, at least we have a way to manually remove the backups and get our storage space back.
The script in the zip is very simple. It just does a recursive delete on /sdcard/clockworkmod/backup.
Enjoy!
Click to expand...
Click to collapse
Just saying thanks for this, I hope they figure a fix out soon. Flash worked perfectly, for some storage space back. :good:
I have been searching for ages trying to find this answer and although I've found some threads about this file I can't find where it is kept? In the guides it says to backup this file when upgrading the same ROM or reinstalling it so you don't lose settings etc, which is what I want to do. I have ES File Explorer on my phone and have searched the root files for it to no avail!
As far as I know, if you're on NAND you won't have that file. But I think if you make a backup, you can find it in /sdcard/clockworkmod/backup/your-bacukp .. If you're using cwm.
Marvlesz said:
As far as I know, if you're on NAND you won't have that file. But I think if you make a backup, you can find it in /sdcard/clockworkmod/backup/your-bacukp .. If you're using cwm.
Click to expand...
Click to collapse
I'm using the SD method not NAND. I don't have CWM installed but I'm assuming in ROM manager you create a backup from there, which places it in the backup folder you mention above?
Pezza4u said:
I'm using the SD method not NAND. I don't have CWM installed but I'm assuming in ROM manager you create a backup from there, which places it in the backup folder you mention above?
Click to expand...
Click to collapse
Oh, excuse me. You're using SD, then it's probably located under /sdcard/your-rom-folder/
That folder is usually called "Android", but it may differ from ROM to ROM. I don't remember the data.img being on the root of the sd.
Marvlesz said:
Oh, excuse me. You're using SD, then it's probably located under /sdcard/your-rom-folder/
That folder is usually called "Android", but it may differ from ROM to ROM. I don't remember the data.img being on the root of the sd.
Click to expand...
Click to collapse
Thanks. Is it a file I'm looking for as I'm under the impression it is with the .img, similar to an ISO file? Although in the android folder there is a folder called data, which has several folders in.....is this it?
If it is then I think the extension on the name is confusing me as I thought it was an actual file!
Actually, back in the time when I used to use android SD. The data was stored in a file with a ".img" extension. I am not sure about now, maybe they changed it?
I am not familiar with this "data" folder you're referring to.
Pezza4u said:
Thanks. Is it a file I'm looking for as I'm under the impression it is with the .img, similar to an ISO file? Although in the android folder there is a folder called data, which has several folders in.....is this it?
If it is then I think the extension on the name is confusing me as I thought it was an actual file!
Click to expand...
Click to collapse
Yes, that is it. It may have slightly different names depending on the rom. The data file is used by the sd android as the data partition by a nand android. Your apps and data are generally stored in this file. There can be some exceptions, like apps moved with Apps2sd and similar things.
It is usually good to have a backup of this file.
---
If at first you don't succeed, skydiving is probably not for you..* * (via Tapatalk)
Thanks....now that I know where it is I can back it up
Hello guys,
I want to flash a custom ROM and I have made a Nandroid Backup using the latest clockworkmod.
I cannot seem to find the clockworkmod folder on my phone. Funny thing is that when I use restore option in the CWM, it shows the path of the backup as sdcard/clockworkmod/backup
Already tried checking data/media, but my data folder doesnt have a media subfolder.
Any suggestions?
PS: I use ES File Explorer and I did check the 'Hidden Files' option in it. Using CWM 6.0.2.3
PPS: I had flashed CWM 6.0.2.3 on 6.0.1.9
-Thanks!
try /mnt/shell/emulated/
croques said:
try /mnt/shell/emulated/
Click to expand...
Click to collapse
emulated doesn't exist in /mnt/shell/
Should I try reflashing the CWM?
I have storage/emulated/. Even that doesn't contain cwm folder though.
So weird.
w1ndhawk said:
emulated doesn't exist in /mnt/shell/
Click to expand...
Click to collapse
it does on mine? And clockworkmod is there as a directory.
w1ndhawk said:
Should I try reflashing the CWM?
Click to expand...
Click to collapse
No; it'll be there somewhere. Poke around.
Are you sure ES file Explorer is set to allow / (root) exploration?
croques said:
it does on mine? And clockworkmod is there as a directory.
No; it'll be there somewhere. Poke around.
Are you sure ES file Explorer is set to allow / (root) exploration?
Click to expand...
Click to collapse
Root Explorer wasn't enabled x_x. Sorry, first android ever! Haha!
Yes, now I can see clockworkmod/backups in the mnt/shell/emulated. Thanks a million.
Emulated folder contains almost all the folders/files that are present on my SD Card. Could you explain what is emulated folder though and why isn't the cwm folder just stored in sdcard/clockworkmod/backups? I have a nexus 4.
And off topic but: after I take a nandroid backup, I should probably save it on my computer right? And of course, that begs another question. How can I find this file through windows explorer?
Further, how do I manually explore paths (by typing it in) on the android. Or do I have to keep changing home directory in settings?
Sorry for so many question. I know what its like to having to answer to noobs
w1ndhawk said:
Could you explain what is emulated folder though and why isn't the cwm folder just stored in sdcard/clockworkmod/backups? I have a nexus 4.
Click to expand...
Click to collapse
Someone more knowledgeable will be along in a minute.
w1ndhawk said:
And off topic but: after I take a nandroid backup, I should probably save it on my computer right? And of course, that begs another question. How can I find this file through windows explorer?
Click to expand...
Click to collapse
You can't use Windoze explorer AFAIK.
I use adb. Since you've rooted your phone... adb must be set up. Open a command window in Windows (run cmd -w) (I don't use Windoze so you're on your own a bit here) and type
Code:
adb shell
You then can use 'ls' and 'cd <directory>' to see what's there and move around.
You'll probably want to use 'adb pull <foldername>' at some time to get the backup onto your PC. Google around for adb commands. I've spoon fed you enough to be getting on with.
w1ndhawk said:
Further, how do I manually explore paths (by typing it in) on the android. Or do I have to keep changing home directory in settings?
Sorry for so many question. I know what its like to having to answer to noobs
Click to expand...
Click to collapse
Sorry; I don't understand the question. And knowledge it like a mosaic floor covered in sand... you've spent your time clearing sand and finding whats beneath a different part from me. No noob should need to apologize in a nice forum.
Get rid of CWM and use TWRP. It's much better and stores backups in the proper location (virtual SD) which you can browse with Windows
Your clockworkmod backups will be in /data/media/clockworkmod
Yep, time for me to research on my own. Enough spoon feeding.
Instead of using commands, I just copy pasted the backup created by CWM to my sdcard using ES Root Explorer so that I could see it using Windows Explorer.
Will give TWRP a try in the future though.
The question about ES file explorer was, how can I explore the file system by typing in the path manually. For example, in windows you can manually type in the path in windows explorer and it will take you there.
EDIT:
The copying thing doesn't work. I think I will have to flash TWRP.
EDIT 2:
Tried again and it DID WORK!!! (the copying thing) Using TWRP is obviously easier though.
w1ndhawk said:
Yep, time for me to research on my own. Enough spoon feeding.
Instead of using commands, I just copy pasted the backup created by CWM to my sdcard using ES Root Explorer so that I could see it using Windows Explorer.
Will give TWRP a try in the future though.
The question about ES file explorer was, how can I explore the file system by typing in the path manually. For example, in windows you can manually type in the path in windows explorer and it will take you there.
EDIT:
The copying thing doesn't work. I think I will have to flash TWRP.
EDIT 2:
Tried again and it DID WORK!!! (the copying thing) Using TWRP is obviously easier though.
Click to expand...
Click to collapse
Oops. Missed the part about you already checking /data/.
w1ndhawk said:
The copying thing doesn't work. I think I will have to flash TWRP.
Click to expand...
Click to collapse
With Nexus 4, Google have seen fit not to implement a USB browsable file system.
It seems to be the trend for Android. I don't think TWRP will help much.
The only way to 'easily' get stuff is to master adb. Although in linux there's this.
Perhaps someone else has a Windoze alternative.
croques said:
With Nexus 4, Google have seen fit not to implement a USB browsable file system.
It seems to be the trend for Android. I don't think TWRP will help much.
The only way to 'easily' get stuff is to master adb. Although in linux there's this.
Perhaps someone else has a Windoze alternative.
Click to expand...
Click to collapse
The SD partition is perfectly accessible through MTP
Michealtbh said:
The SD partition is perfectly accessible through MTP
Click to expand...
Click to collapse
And MTP is perfectly accessible through nothing.
(I swear, I just want to back hand smack the person who thought their creation called "MTP" was a good thing. MTP = Massive Trauma Protocol)
Hey guys.
I'm a bit intrigued. There's an unknown folder in the root of my phone's internal memory. I delete it every few weeks when I check the storage and sweep all the junk I might find in there.
Here's the folder structure.
GT-I9505\Internal storage\.sp\.94\.743\.cache\LazyList.
Inside that last folder (LazyList), there's a 23 KB file named 663014360. It has no extension. Opening it with Notepad / WordPad reveals a lot of unreadable characters (of course...).
I am having a hard time tracing it back to any app (if it's an app that's creating it, or the ROM itsellf ).
Does anyone here know what this .sp sh*t is all about...?
For what it's worth, I am running the latest SlimKat ROM.
Formhault said:
Hey guys.
I'm a bit intrigued. There's an unknown folder in the root of my phone's internal memory. I delete it every few weeks when I check the storage and sweep all the junk I might find in there.
Here's the folder structure.
GT-I9505\Internal storage\.sp\.94\.743\.cache\LazyList.
Inside that last folder (LazyList), there's a 23 KB file named 663014360. It has no extension. Opening it with Notepad / WordPad reveals a lot of unreadable characters (of course...).
I am having a hard time tracing it back to any app (if it's an app that's creating it, or the ROM itsellf ).
Does anyone here know what this .sp sh*t is all about...?
For what it's worth, I am running the latest SlimKat ROM.
Click to expand...
Click to collapse
try this app - https://play.google.com/store/apps/details?id=com.kokanes.fileextensiondirectory
Sent from my GT-I9500
Formhault said:
Hey guys.
I'm a bit intrigued. There's an unknown folder in the root of my phone's internal memory. I delete it every few weeks when I check the storage and sweep all the junk I might find in there.
Here's the folder structure.
GT-I9505\Internal storage\.sp\.94\.743\.cache\LazyList.
Inside that last folder (LazyList), there's a 23 KB file named 663014360. It has no extension. Opening it with Notepad / WordPad reveals a lot of unreadable characters (of course...).
I am having a hard time tracing it back to any app (if it's an app that's creating it, or the ROM itsellf ).
Does anyone here know what this .sp sh*t is all about...?
For what it's worth, I am running the latest SlimKat ROM.
Click to expand...
Click to collapse
It is very good that although you are deleting the launcher's (or some other app) cache, it restores it.
I can understand that you're mad about it and you would like that your launcher (or app) shall not create any cache and consequently would work slower.
As well I appreciate your huge work with tracing it (5th link in google search provides the answer what is it).
If you really care what is, your work would be pretty simple. Factory reset your phone, start each built in ROM app and check the folder after. Then, install your apps one by one, starting each of it and each time after closure checking the folder. Easy.
anu.cool said:
try this app - https://play.google.com/store/apps/details?id=com.kokanes.fileextensiondirectory
Click to expand...
Click to collapse
Sorry, but that app is of no use to me since the file in question has no extension.
spamtrash said:
It is very good that although you are deleting the launcher's (or some other app) cache, it restores it.
I can understand that you're mad about it and you would like that your launcher (or app) shall not create any cache and consequently would work slower.
As well I appreciate your huge work with tracing it (5th link in google search provides the answer what is it).
If you really care what is, your work would be pretty simple. Factory reset your phone, start each built in ROM app and check the folder after. Then, install your apps one by one, starting each of it and each time after closure checking the folder. Easy.
Click to expand...
Click to collapse
What exactly did you use as a search term on Google?
I know most apps create folders that are legible (com.android.thisgameproducer). Buth with this given specific folder's structure, I don't know what it could be.
For what it's worth, I have been trying to find an answer to this for some months. But only now I made a topic about it. I did my research, which turned out nothing... :/
Formhault said:
. I did my research, which turned out nothing... :/
Click to expand...
Click to collapse
Have you:
wiped your phone, and then used titanium backup for freezing each app, restoring it, and verifying which one creates it? did you repeated the same for each installed by you app? Well, if this folder/file is NOT created by one application (or installed, or embedded into the ROM), then only one explanation is that your phone is used by E.T at night while he "phone home" and this is his encrypted message.:cyclops:
about extension/filetype:does the file have header?
spamtrash said:
Have you:
wiped your phone, and then used titanium backup for freezing each app, restoring it, and verifying which one creates it? did you repeated the same for each installed by you app? Well, if this folder/file is NOT created by one application (or installed, or embedded into the ROM), then only one explanation is that your phone is used by E.T at night while he "phone home" and this is his encrypted message.:cyclops:
about extension/filetype:does the file have header?
Click to expand...
Click to collapse
You know where that .sp folder comes from? Perhaps you were able to find something on Google that I didn't all this time...
I don't know what that header is / should be...
I know I could wipe all and start over again and check each app... But that's too time consuming... Hence I am asking here.
Formhault said:
You know where that .sp folder comes from? Perhaps you were able to find something on Google that I didn't all this time...
I don't know what that header is / should be...
I know I could wipe all and start over again and check each app... But that's too time consuming... Hence I am asking here.
Click to expand...
Click to collapse
1. No idea which particular app makes the cache file, but it is clear that it is cach for one app you have installed, or one you have embedded in ROM.
2. Header is the two first bytes of file in the notepad viewer: for example, PK is characteristic for zip files and by changing the extension you could see what's inside.
3. No one who does not have your ROM AND your specific set of apps installed would be able to provide the answer, therefore without doing your homework, it is unlikely that you'd have information you want.
spamtrash said:
1. No idea which particular app makes the cache file, but it is clear that it is cach for one app you have installed, or one you have embedded in ROM.
2. Header is the two first bytes of file in the notepad viewer: for example, PK is characteristic for zip files and by changing the extension you could see what's inside.
3. No one who does not have your ROM AND your specific set of apps installed would be able to provide the answer, therefore without doing your homework, it is unlikely that you'd have information you want.
Click to expand...
Click to collapse
Well, I don't really know what homework I should do here, as the folder structure is weird (come on, just numbers? ) and the file has no obvious meaning whatsoever. I'm usually a tech guy, but when all I see is numbers, I'm really not that wise... :silly:
Since I know for a fact that I don't have any rogue apps installed, guess I should leave it be and carry on.
But anyway, just for the heck of it, I opened the file in Notepad. Here's the first line (as seen in Notepad, lol).
Code:
ÿØÿà JFIF ÿÛ „
(1#%(:3=<[email protected]\[email protected]_bghg>Mqypdx
I'm sorry, but this is way out of my league. :/
Mod Edit
Thread closed at the request of the [OP]
malybru
Forum Moderator