Related
Hey guys,I've been testing roms today om my device,so I made a nandroid of my LeeDroid 2.2.3 setup.I checked my first backup with AFV(Android File Verifier,very nice app,I found it in the market) and cache.img and data.img were corrupted.I deleted it and made another backup.I checked with AFV and all was ok.I installed MDJ's rom,RCMixHD 6 and some other stuff,but later,when I wanted to come back to my LeeDroid rom,I tried to restore but CWM(3.0.2.8) gave me an MD5 Mismatch message.Now I have to start from scratch once again.Luckily enough,I backed up everything with Titanium,just in case.
Thing is,it's not the first time this is happening.At first I thought it was my CWM version,but none has worked well,and I've had 2.5.1.3,3.0.0.6,3.0.2.4,3.0.2.6 and 3.0.2.8.Anybody knows why this is happening?Cause I'm getting sick of it!Plus there is no AmonRA for the DHD.
Anyway,is there any way of manually restoring my supposedely corrupted data.img via adb or something?Even if it is corrupted,something won't work well but at least I will have tried!
Many thanks in advance,
Apostolis
Idea:
Could I "trick" CWM into restoring the "broken" nandroid backups by generating a new MD5 with MD5 Generator?If yes,there won't be any real danger other than having bootloops etc,right?
Two thoughts
Your SD card is corrupt
You actually have some corrupt data on data which is erroneously leading a AFV to report a corrupted backup
Personally I backup and restore all the time with nandroid with no hassle, I suppose the other thing is a rom specific issue as I'm using cm.
You've not been renaming your backup files or anything have you?* You shouldn't be getting MD5 mismatch errors unless the file has been changed somehow since it was created.
*because that's exactly what I did; renamed them when I moved them to my pc for easier filing. Then of course none of them worked until I eventually realised and changed them back
//sent from my Desire HD using Tapatalk; all errors entirely intentional.
Thanks for your replies guys.
Firstly,there is a chance the SD is ****ed up,because I had some photos' thumbnails missing the other day.Now,if something in /data was corrupted...Well,maybe!I'll format my SD sooner or later and see...It's 16 freakin' gigabytes!
Secondly,no,I never renamed my backups to anything else.
Can anyone answer my question though?Could I trick CWM into restoring those backups?Would it hurt to try?
tolis626 said:
Could I trick CWM into restoring those backups?Would it hurt to try?
Click to expand...
Click to collapse
I don't think you can, It's a safety feature to prevent you from flashing a corrupt image.
How have you flashed your recoveries? Via ROM Manager or fastboot?
MD5 checksums are generated from the contents of a file, filenames are not included in this generation, unless of course there are filenames within the file that have been modified.
andyharney said:
I don't think you can, It's a safety feature to prevent you from flashing a corrupt image.
How have you flashed your recoveries? Via ROM Manager or fastboot?
MD5 checksums are generated from the contents of a file, filenames are not included in this generation, unless of course there are filenames within the file that have been modified.
Click to expand...
Click to collapse
Ahaa...
I flash my recoveries through fastboot.Since I learned how to use it(I was afraid I'd somehow **** up at first)I flash them through fastboot.How is that relevant?
Anyway,I haven't modified anything.If I had,it'd make sense,but it doesn't.I didn't mess with the backup's files in any way,yet it got corrupted.Am starting to get desperate here...
I only asked because I know *sometimes* you have to flash recoveries twice within ROM Manager.
If the MD5 of the Recovery.img you flash is correct, then the problem has to be somewhere else. Other than checking your SDcard for errors & formatting, I'm not sure much else can be done.
andyharney said:
I only asked because I know *sometimes* you have to flash recoveries twice within ROM Manager.
If the MD5 of the Recovery.img you flash is correct, then the problem has to be somewhere else. Other than checking your SDcard for errors & formatting, I'm not sure much else can be done.
Click to expand...
Click to collapse
Pff...I start to miss my Desire's flexibility!
Anyway,many thanks for your time man!Will see what I'll do...
I just checked my card for errors and there was indeed something wrong!Possibly my card is damaged somehow.It gives me problems too often.Or it's the phone,cause I used the same card on my Desire with no problems at all.Time will tell...
You can expect more people reporting similar issues here soon.I posted in LeeDroid's thread about it as a reply to andreasy and he has a similar problem.
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
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
Hi all,
I've decided to try and copy my nandroid backup that I made the other day (first ever since I've just rooted my phone) to my PC.
Long story short, I attempted to use Root explorer to cut and paste the backup's folder into a folder that is visible on my PC so I could get a copy onto my PC, and then cut and paste the nandroid back into its original folder (tedious, but I don't have enough space to have 2 copies of the nadroid on my phone at the same time). This, however, fails, and I can't see the backup folder in the folder that I can see on my PC despite it being visible in this same PC-visible folder via root explorer after its supposedly pasted it.
So I went via option 2, using ADB to pull the folder.
After another amount of research I found a path that does pull the folder (mnt/shell/emulated/clockworkmod/backup .... data/media/clockworkmod/backup = remote object doesn't exist error).
It appears to pull the folder successfully (an identically named folder appears in "platform tools" folder on my PC), however the size of this pulled folder is only ~500mb, and I'm certain the nandroid backup took up at least 3-4GB on my phone after it was created.
The pulled folder also doesn't show all the files that I can see within the nandroid backup's folder via root explorer.
I did notice the "read-only" checkbox of the pulled folder appears filled in, which I take it means not all files in the folder have read-only properties. Is it possible there are (still) hidden files within the pulled folder that would account for the difference in size and number of visible files compared to the original nandroid folder on the phone?
any clarificaion of this would be good - I'm keen to have a copy of my backup on my PC as a safeguard, but this scenario has baffled me despite an hr's worth of research
No one?
Surely someone has an idea about this..
I have experienced incomplete adb pulls also, and so I just stick to using MTP from within Windows. It's the only way for mention ensure a complete copy.
Sent from my Nexus 4 using XDA Free mobile app
lolcakes203 said:
I have experienced incomplete adb pulls also, and so I just stick to using MTP from within Windows. It's the only way for mention ensure a complete copy.
Sent from my Nexus 4 using XDA Free mobile app
Click to expand...
Click to collapse
How are you doing this?
I use cwm and the backup folder isn't visible if I use mmtp (Windows file explorer etc), hence why I'm having to use other methods.
salxtai said:
How are you doing this?
I use cwm and the backup folder isn't visible if I use mmtp (Windows file explorer etc), hence why I'm having to use other methods.
Click to expand...
Click to collapse
It's possible that the computer and phone may be calculating file sizes differently. I would check the MD5 sums to see if they are the same on the computer and phone rather than guessing
lopezk38 said:
It's possible that the computer and phone may be calculating file sizes differently. I would check the MD5 sums to see if they are the same on the computer and phone rather than guessing
Click to expand...
Click to collapse
Apologies for my ignorance, but I've been searching how to do this via Google and I must be really dumb because I'm not following how to do md5 checks. Could you explain it please?
salxtai said:
Apologies for my ignorance, but I've been searching how to do this via Google and I must be really dumb because I'm not following how to do md5 checks. Could you explain it please?
Click to expand...
Click to collapse
For Windows you need to download a program to check MD5. Microsoft has one available here, although it is a command line operated program. There are other programs that have a GUI for checking MD5 if you don't want to bother with the command line.
On your phone, using your file explorer and long pressing the backup should give you the option somewhere to calculate MD5 sums (Probably in properties). I don't know if root explorer does, I've never used it before, but I use Solid Explorer which does give me the option to calculate MD5 in the properties menu
I'm not sure why you're backup folder isn't visible, when I connect though USB, all my SD card folders are shown, including the CWM Folder.
Sent from my Nexus 4 using XDA Free mobile app
lopezk38 said:
For Windows you need to download a program to check MD5. Microsoft has one available here, although it is a command line operated program. There are other programs that have a GUI for checking MD5 if you don't want to bother with the command line.
On your phone, using your file explorer and long pressing the backup should give you the option somewhere to calculate MD5 sums (Probably in properties). I don't know if root explorer does, I've never used it before, but I use Solid Explorer which does give me the option to calculate MD5 in the properties menu
Click to expand...
Click to collapse
After a while of trying to work out the command line, I've think I've got it (but would like confirmation that this is correct).
- Pointed the fciv.exe command to the nandroid.md5 file located in the backup folder I had pulled from the phone via ADB
- using Solid explorer (root explorer also has this but I only worked this out after I worked out that I had look at the properties of the .md5 file itself w/in the explorer app, rather than the whole folder), I found the MD5 sum from within the backup folder
-- verdict: both numbers outputted by each source match.
Now my next question is, if I were to delete the backup on my phone, how do I go about putting it back into the "hidden" CWM backup folder where it came from later?
(seeing as I wasn't able to copy it using root explorer, and can't see the folder via MTP on my PC)
lolcakes203 said:
I'm not sure why you're backup folder isn't visible, when I connect though USB, all my SD card folders are shown, including the CWM Folder.
Sent from my Nexus 4 using XDA Free mobile app
Click to expand...
Click to collapse
I have no idea either, and its really really annoying me.
Have you made some sort of permission changes to the folder/s themselves?
I have "show hidden folders" enabled under view options in windows explorer and have tried "show system folders", but that hasn't resovled it.
salxtai said:
After a while of trying to work out the command line, I've think I've got it (but would like confirmation that this is correct).
- Pointed the fciv.exe command to the nandroid.md5 file located in the backup folder I had pulled from the phone via ADB
- using Solid explorer (root explorer also has this but I only worked this out after I worked out that I had look at the properties of the .md5 file itself w/in the explorer app, rather than the whole folder), I found the MD5 sum from within the backup folder
-- verdict: both numbers outputted by each source match.
Now my next question is, if I were to delete the backup on my phone, how do I go about putting it back into the "hidden" CWM backup folder where it came from later?
(seeing as I wasn't able to copy it using root explorer, and can't see the folder via MTP on my PC)
Click to expand...
Click to collapse
You can use ADB push in recovery the folder. Just make sure you mount /data
I do have those settings enabled in control panel, but aside from that I'm not sure what else could be there. In terms of USB settings, I have USB debugging enabled in developer options, and in the storage menu I have mtp selected, not the other one. I think that is all the USB settings that I have changed.
Sent from my Nexus 4 using XDA Free mobile app
salxtai said:
I have no idea either, and its really really annoying me.
Have you made some sort of permission changes to the folder/s themselves?
I have "show hidden folders" enabled under view options in windows explorer and have tried "show system folders", but that hasn't resovled it.
Click to expand...
Click to collapse
The CWM backup folder shouldn't be able to be accessed with MTP. Android only allows you to access your user's folder (You can only have multiple users on tablets, but the user based file structure is still there) through USB. User folders have a number attached to them to mark which user they are for, which is why you have that folder named 0 with all your stuff in it, because you are user #0. Since CWM backups are saved in a separate branch, Android does not make them available to USB for security reasons. lolcakes203 probably has a modified version of CWM (Or you can change the save directory in CWM? I haven't used CWM in forever), or he has TWRP which saves backups in your user folder so you can access them through USB
Ahh yes I am using PhilZ CWM and that may be why I can see the backup.
Sent from my Nexus 4 using XDA Free mobile app
lopezk38 said:
You can use ADB push in recovery the folder. Just make sure you mount /data
Click to expand...
Click to collapse
Sorry, not sure I'm following the command line instructions - how would this command line look in full?
I've used multiple apps from Google Play and checked the md5 value on multiple files that I downloaded and knew were good because I flashed them and everything worked perfectly yet every single file that I check fails the md5 check on every app that I try. I don't have a single file that I have flashed that passes an md5 check. I assume I am doing something wrong but the apps seem pretty straightforward in terms of how to use them. Is there any legitimate reason that a good file would fail an md5 check?
jhs39 said:
I've used multiple apps from Google Play and checked the md5 value on multiple files that I downloaded and knew were good because I flashed them and everything worked perfectly yet every single file that I check fails the md5 check on every app that I try. I don't have a single file that I have flashed that passes an md5 check. I assume I am doing something wrong but the apps seem pretty straightforward in terms of how to use them. Is there any legitimate reason that a good file would fail an md5 check?
Click to expand...
Click to collapse
Hello... How do you download the files that fail the md5 check?
A browser?
Is your connection stable enough?
Try with this download manager: https://play.google.com/store/apps/details?id=com.dv.adm
And try checking the same files that fail on your current download method. I've never had or seen such issue before. Did you update the app you use to download lately?
Good luck...
5.1 said:
Hello... How do you download the files that fail the md5 check?
A browser?
Is your connection stable enough?
Try with this download manager: https://play.google.com/store/apps/details?id=com.dv.adm
And try checking the same files that fail on your current download method. I've never had or seen such issue before. Did you update the app you use to download lately?
Good luck...
Click to expand...
Click to collapse
A lot of the files that I'm downloading are from XDA. Some download through Chrome and I think some might download through whatever download manager is built into Android. I've downloaded the latest version of Flash Kernel 3 times and it fails the md5 check every time. I flashed the kernel and it seems to be operating perfectly anyway.
The apps are all a little different but this is the basic procedure I'm using. I open the downloaded file and the app calculates the md5 value and stores it. Then I open the md5 file that I downloaded alongside the other download. The app always says the values don't match. Does it sound like I'm doing something wrong?
I will check out the download manager you mentioned. Thanks for the suggestion.
jhs39 said:
A lot of the files that I'm downloading are from XDA. Some download through Chrome and I think some might download through whatever download manager is built into Android. I've downloaded the latest version of Flash Kernel 3 times and it fails the md5 check every time. I flashed the kernel and it seems to be operating perfectly anyway.
The apps are all a little different but this is the basic procedure I'm using. I open the downloaded file and the app calculates the md5 value and stores it. Then I open the md5 file that I downloaded alongside the other download. The app always says the values don't match. Does it sound like I'm doing something wrong?
I will check out the download manager you mentioned. Thanks for the suggestion.
Click to expand...
Click to collapse
No. The way you do it should work I guess. Give me a link of the app you use to check the md5 and at least two links of files you downloaded that fails checking. I'll try it myself and report back...
5.1 said:
No. The way you do it should work I guess. Give me a link of the app you use to check the md5 and at least two links of files you downloaded that fails checking. I'll try it myself and report back...
Click to expand...
Click to collapse
Here is a link for one of the apps I tried:
https://play.google.com/store/apps/details?id=sa.afvx
I deleted them all from my phone since I couldn't get any of them to work for me.
Here are links for various builds of Flash Kernel. They all fail md5 check for me though I flashed them and they seem to function perfectly:
http://nchancellor.net/Downloads/Kernels/
I checked md5 for the 3 most recent builds and like every other file on my phone it failed the md5 check on multiple apps from Google Play.
jhs39 said:
Here is a link for one of the apps I tried:
https://play.google.com/store/apps/details?id=sa.afvx
I deleted them all from my phone since I couldn't get any of them to work for me.
Here are links for various builds of Flash Kernel. They all fail md5 check for me though I flashed them and they seem to function perfectly:
http://nchancellor.net/Downloads/Kernels/
I checked md5 for the 3 most recent builds and like every other file on my phone it failed the md5 check on multiple apps from Google Play.
Click to expand...
Click to collapse
Hello...
The problem is: with the app you used (afv), I haven't found an option to compare the md5 of the kernel zip against the hash generated in the md5sum file. So I used the PC. Open the md5sum file with a text editor rename to .txt on Android and open it. Check the kernel md5, they match.
The three last kernel match their respective md5sum. Check the attached screenshots.
That's what the program is for so I'm not sure why you couldn't find an option to compare the md5 values. I tried several other apps as well. I guess I'm either doing something wrong or everything that downloads to my phone is screwed up. Thanks anyway.
jhs39 said:
That's what the program is for so I'm not sure why you couldn't find an option to compare the md5 values. I tried several other apps as well. I guess I'm either doing something wrong or everything that downloads to my phone is screwed up. Thanks anyway.
Click to expand...
Click to collapse
Check this: http://winmd5.com
There are several apps that allow you to compare a file, with an existing md5 file...
The md5 hash of the file you want to test, is stored in the *.md5 or *.md5sum file, which is nothing more than a txt file with an "md5" or "md5sum" extension.
As you can see on the link above, you can add a file to generate a hash and you can add a *.md5 or *.md5sum file at the bottom. The app will generate a hash for the file which will be compared to the hash stored in the md5 or md5sum file.
If you simply generate a hash of each file, they won't match at all...
If you.foumd a way to do that thing with the AFV app, let me know. I haven't found it... :good:
It seem you can also do it on Android with BusyBox in a terminal emulator, but I haven't checked yet...
Unfortunately I don't want to transfer files downloaded onto my phone onto my computer so I can check the Md5. I want to actually be able to do it on my phone and I'm not technically adept enough to do it with a terminator emulator within Busybox. I'm obviously missing something here because there are more than a dozen apps in the Play Store that supposedly allow you to check the md5 value of a file but I can't get anything to work for me.
jhs39 said:
Unfortunately I don't want to transfer files downloaded onto my phone onto my computer so I can check the Md5. I want to actually be able to do it on my phone and I'm not technically adept enough to do it with a terminator emulator within Busybox. I'm obviously missing something here because there are more than a dozen apps in the Play Store that supposedly allow you to check the md5 value of a file but I can't get anything to work for me.
Click to expand...
Click to collapse
Well... Let me try to explain again :angel:
You dl flash kernel zip... It's md5 is supposed to be: dj358df39fk359sde (for example)
Flash generated a *.md5sum file which you can use to compare against the flash zip... You can't use an app from the play store, because the hash of the flash zip and the *.md5sum file won't be the same...
The fact is: the hash value of the flash zip is stored in the *.md5sum file. But if you generate a hash for this *.md5sum file, it will be something else than the flash zip...
You can use the *.md5sum file in an app as in my previous post. It will generate a hash for the flash zip and "read the value" stored in the *.md5sum file, just like the screenshots I posted, and of course it will match...
Hoping I've been clear enough...
5.1 said:
Well... Let me try to explain again :angel:
You dl flash kernel zip... It's md5 is supposed to be: dj358df39fk359sde (for example)
Flash generated a *.md5sum file which you can use to compare against the flash zip... You can't use an app from the play store, because the hash of the flash zip and the *.md5sum file won't be the same...
The fact is: the hash value of the flash zip is stored in the *.md5sum file. But if you generate a hash for this *.md5sum file, it will be something else than the flash zip...
You can use the *.md5sum file in an app as in my previous post. It will generate a hash for the flash zip and "read the value" stored in the *.md5sum file, just like the screenshots I posted, and of course it will match...
Hoping I've been clear enough...
Click to expand...
Click to collapse
No I understand what you did and why you are saying what I did with the Android apps didn't work--the apps were generating a new md5 hash value rather than simply copying it from the file. What I don't understand is why I can't find an Android app that does what you did on the computer. I appreciate your help but like I previously stated I have no interest in transferring files to my computer so I can check their integrity. I want to do this completely on my phone.
jhs39 said:
No I understand what you did and why you are saying what I did with the Android apps didn't work--the apps were generating a new md5 hash value rather than simply copying it from the file. What I don't understand is why I can't find an Android app that does what you did on the computer. I appreciate your help but like I previously stated I have no interest in transferring files to my computer so I can check their integrity. I want to do this completely on my phone.
Click to expand...
Click to collapse
Ah... I think I just misunderstood you understood me..!
Of course, moving files on PC and back on the phone is not convenient at all.
About Android apps... I don't get it either. I searched yesterday on the play store as well. In app reviews, i also saw some requests for such feature, but unfortunately, it seems like devs didn't notice are not interested in adding the feature in their app.
Hopefully one will do it... :good:
jhs39 said:
I've used multiple apps from Google Play and checked the md5 value on multiple files that I downloaded and knew were good because I flashed them and everything worked perfectly yet every single file that I check fails the md5 check on every app that I try. I don't have a single file that I have flashed that passes an md5 check. I assume I am doing something wrong but the apps seem pretty straightforward in terms of how to use them. Is there any legitimate reason that a good file would fail an md5 check?
Click to expand...
Click to collapse
You could try using either Solid Explorer or Root Explorer. Both give MD-5, SHA-1 under properties. If one of these mismatch, I don't flash. I'm looking for a solution for SHA-256 which Google uses for images. @5.1
v12xke said:
You could try using either Solid Explorer or Root Explorer. Both give MD-5, SHA-1 under properties. If one of these mismatch, I don't flash. I'm looking for a solution for SHA-256 which Google uses for images. @5.1
Click to expand...
Click to collapse
This is probably a stupid question but I assume you write down the value you get from root explorer so you can compare it with the value in the md5 value. It's a very long number to match in your head unless you have a fantastic memory.
jhs39 said:
This is probably a stupid question but I assume you write down the value you get from root explorer so you can compare it with the value in the md5 value. It's a very long number to match in your head unless you have a fantastic memory.
Click to expand...
Click to collapse
Good question. SE has both a generated checksum and a "compare" field you paste the known good MD5 into and it compares it for you.... but I just look at the first few leading and trailing digits. That's really all you need. One byte out of place and the MD5 blows up. RE just gives you the MD5 under file properties, but it is enough using the method above. SE is great!
jhs39 said:
This is probably a stupid question but I assume you write down the value you get from root explorer so you can compare it with the value in the md5 value. It's a very long number to match in your head unless you have a fantastic memory.
Click to expand...
Click to collapse
Got an idea. Maybe not the best, but a workaround for the time being. Tap twice recent button to switch from file explorer file properties to md5 checker app... Or use multi window.
This way you can keep an eye on both hash...
Cheers...
---------- Post added at 12:32 AM ---------- Previous post was at 12:29 AM ----------
v12xke said:
Good question. SE has both a generated checksum and a "compare" field you paste the known good MD5 into and it compares it for you.... but I just look at the first few leading and trailing digits. That's really all you need. One byte out of place and the MD5 blows up. RE just gives you the MD5 under file properties, but it is enough using the method above. SE is great!
Click to expand...
Click to collapse
Still an issue when having this case: http://nchancellor.net/Downloads/Kernels/
Where do you find the proper md5 hash? If not in the *.md5sum?
5.1 said:
Still an issue when having this case: http://nchancellor.net/Downloads/Kernels/
Where do you find the proper md5 hash? If not in the *.md5sum?
Click to expand...
Click to collapse
It is within *.md5sum... open it with any text editor and the first line is the hash. As an example the md5 hash from flash-angler-20170315-1537.zip.md5sum is e88c47c885a0e03e7944569e839022e9. @jhs39
Edit: If using Windows, you may have to use "open with" the first time and let Windows know you want to use Notepad or Wordpad to open files with the *.md5sum extension
v12xke said:
It is within *.md5sum... open it with any text editor and the first line is the hash. As an example the md5 hash from flash-angler-20170315-1537.zip.md5sum is e88c47c885a0e03e7944569e839022e9. @jhs39
Click to expand...
Click to collapse
Read my previous posts and see the screenshots, I know about that.
It is just a waist of time. Just looking for a proper solution, not involving messing with files. Still the best though...