Fascinate JB Rom's incompatible with some SD cards? - Fascinate Q&A, Help & Troubleshooting

I have been systematically tracking down errors since I bought a new Sandisk Class10 SDHC a few days ago, and it appears that there is a compatibility issue with the way JB rom's install on the Fascinate and my new SD card. I am unable to flash ANY JB rom with the new card, although it works fine flashing CM7.2, THS Build2, etc. Read on for details, and please feel free to offer any ideas you have regarding what the real issue might be...
After Odin (Heimdall) to EH03, installing cwm4forcm7 & GB bootloaders, wiping all, and then attempting to flash any JB rom, I end up with the following errors (this is after the bml over mtd checks & multiple flashes between recovery & boot logo):
Installing update...
Format and Mount System, Mount data...
Symlinks and permissions...
set_perm: some changes failed
E:Error in /sdcard(filename)
(Status 7)
Installation aborted.
At this point, the phone will reboot only to Recovery mode. I can flash an older ICS or GB rom and the installation will complete fine, but any JB rom gets me an error and installation aborted.
IF I flash CM7.2 & THS Build2 first (which both install fine with the new SD card), and then flash a JB rom I end up with the following error instead (also after the bml over mtd checks & multiple flashes between recovery & boot logo):
-- Installing: x
finding update package...
Opening update package...
Installing update...
assert failed: run_program("/tmp/updater.sh", "cdma") == 0
E:Error in /sdcard(filename)
(status 7)
Installation aborted.
Occasionally I get this error instead:
E:Can't open /sdcard/filename
(bad)
Installation aborted.
If I put the old card (Samsung Class2) back in with all the exact same files on it (copied from computer, still same MD5), the JB rom's will install fine. I first tried the new SD card with the factory format and from within an existing JB rom, going to a different JB rom. When that didn't work, I odined back and reformatted the card on the phone with stock EH03 and got the same results. I also reformatted the SD card with Gparted on the computer and tried that, etc. etc. Even though I put the exact same files on the new card after each reformat as are on the old card, the new SD card can only flash the non-JB roms. Any idea why?
Droidstyle's guide mentions these type of errors, and suggests to use a higher class card if you get them... but this is an Ultra Class10 UHS-1 card. Perhaps it is too fast or incorporates some new tech that is not compatible with the compatibility checking that the newer Rom's do before they install? If so, perhaps the older roms work because they don't do any compatibility checking prior to install?

What brand Class 10 are you using? Our phones have been known to dislike SanDisk cards for whatever reason. I have a 16 GB Class 10 from Sandisk that goes unused for that very reason.

Related

[Q] Error updating

After I installed CM7 RC0 i wanted to install Folionotion.
I get the following:
update eUpdate...
update system.img...
update boot.img...
assert failed: write_raw_image("/cachee/boot.img", "linux")
E: error in sdcard/update.zip
(Status &)
Insatallation aborted.
What can I do?
I had similar problems when i used a different sd-card, or when i used linux to put the update zip on the card. Make sure the card is formated good, and mabey re-download the update file. Try a different card maybe?
SD card
It looks like my internal SD card is damaged, cant install any thing and after reboot all personal settings are gone!!!!
MTD
I also have a other problem:
Erro no MTD partition on sd-card!!
I think this is the internal sd....help

[Q] CM9: Can't open/sdcard/update.zip

Hey everyone longtime since I've done this kinda thing but i'm a bit stuck
heres what im using
Galaxy SII
Lite'ning Rom v6.1 XXKH3
Android version 2.3.4
ClockworkMod 4.0.0.2
I've downloaded: update-cm-9-20120305-NIGHTLY-galaxys2-signed.zip
I renamed it to update.zip and its on my SD card
When I try to run it I get
"Install from sd card
Finding update
opening update
E:Can't open/sdcard/update.zip
(no such file or directory)
Installation aborted."
Do I need to wipe the phone? Or get to OS 3 and then go to 4?
Thanks for the help
its been about 3 years since I used android, but i'm back!
fixed it. Formatted sd card first durrrr
Formatting didn't fix
I'm getting the same error under the same conditions.
Formatted the SD card as per your suggestion. Used Clockwork to perform the format just to make sure, and put update.zip back on it. (Noticed the format was FAT32.)
Still getting
E: Can't open /sdcard/update.zip
(No such file or directory)
Click to expand...
Click to collapse
Am I going crazy?
I think I'm doing everything else right. See the steps I'm taking.
If you're trying to flash a CM9 nightly, do not rename the file. Go into recovery and:-
1) Install zip from sdcard
2) Choose zip from sdcard (or choose zip from internal sdcard depending on where you have the CM9 nightly you're wanting to flash located).
3) Navigate to the folder where the file you want to flash is.
4) Choose the file
5) Confirm install; "Yes"
6) Reboot & done
Do not use "Apply /sdard/update.zip

[Q] boot looping problems,can't access recovery and install zip from SD card (solved)

A while ago, I decided to work on my old legend and upgrading it with new custom roms.
After factory reset, I have flashed CM10 rom from here and discovered my Hboot version is 0.43 and not compatible with this rom.
So I found this rom instead and made 3 different partitions as instructed. But I have discovered that my phone have lost ability to go to recovery mode during the process and cannot recognize the zip files from SD card although its still in there. I have reformatted the SD card again with one fat32 to see if its problem with partitioning but it is still having same problem.
I can see the red triangle with ! in it and selected "Apply sdcard:update.zip" which keeps giving me error message "E:can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0) Invalid argument"
Is there any solution to get out of this situation?
Thank you for your patience
Yhcho said:
A while ago, I decided to work on my old legend and upgrading it with new custom roms.
After factory reset, I have flashed CM10 rom from here and discovered my Hboot version is 0.43 and not compatible with this rom.
So I found this rom instead and made 3 different partitions as instructed. But I have discovered that my phone have lost ability to go to recovery mode during the process and cannot recognize the zip files from SD card although its still in there. I have reformatted the SD card again with one fat32 to see if its problem with partitioning but it is still having same problem.
I can see the red triangle with ! in it and selected "Apply sdcard:update.zip" which keeps giving me error message "E:can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0) Invalid argument"
Is there any solution to get out of this situation?
Thank you for your patience
Click to expand...
Click to collapse
I have followed this thread and I got an error message saying failed due to low battery. I will just charge the phone for a while and see if it gives same error.
I have done the fastboot recovery method from here and its keep giving me "failed (remote: not allowed)" messages.
my Legend is already rooted and currently on S-off.
I have solved the problem.
It was memory card problem. my legend works after installing CM7 using different SD card.
I am suspecting if its because I have messed up something with memory card while dividing partitions to install a Jelllybean rom,
However the faulty memory card is still functioning well on my pc which made me think there is no problem with it.

Help Please! Boots into CWM, can't load CM .zip

Hi, complete noob here, will try to explain as best I can. Trying to get cyanogenmod 12.1 booted from SD. This is my first attempt for flashing any ROM on any device. I followed the acclaim tutorial on CM webpage (wiki.cyanogenmod.com...can't post link because I'm a forum noob). I can boot into CWM (v5.5.0.4) but when I go to install zip from sdcard, I get lots of errors. Without copy/paste, I'll do my best to state the important parts:
...
Installing update...
Warning: Nofile_contextscould not detect filesystem for /dev/block/platform/omap/omap_hsmmc.1/by-name/system, assuming ext4
mount: failed to mount /dev/block/platform/omap/omap_hsmmc.1/by-name/system at /system: No such file or directory
unmount of /system failed; no such volume
The error continues with nearly the same thing but for .../by-name/userdata at /data.
It again repeats the error with the /system (same as above)
Error ends with:
script succeeded: result was [0.200000]
Install from sdcard complete.
When I reboot the system, it goes back into stock B&N startup as if the ROM was not updated. No surprise considering the errors. I tried again and this time used CWM to enter "mounts and storage" and manually mounted /data and /system. The error for /data went away but the /system errors (x2) remain.
I've now tried cm-12.1-20151007-SNAPSHOT-YOG4PAO331-acclaim.zip and cm-12.1-20150901-SNAPSHOT-YOG4PAO236-acclaim.zip with the same result.
Oddly enough, when I tried older versions (have tried cm-11-20150831-SNAPSHOT-XNG3CAO3FN-acclaim.zip and cm-10.2-20131102-SNAPSHOT-M1-acclaim.zip), those files give me a different error. They say (example for CM v11):
Installing update...
E:Error in /sdcard/cm-11-20150831-SNAPSHOT-XNG3CAO3FN-acclaim.zip
(Status 0)
Installation aborted.
Is something wrong with my SD?!? I am using Linux Mint and Gparted to format the SD. I have the boot and lba flags on. Since I'm getting CWM to boot on the NT, I feel like the SD is OK and the error is in the .zip file or some setting on the NT itself. Does anybody have any ideas??
Potentially related side note: I've alternatively used the dd command and USB Image Writer to copy an img file to the SD (tried twrp-2.8.6.0-acclaim-sdcard.img and cm-12.1-20151007-SNAPSHOT-YOG4PAO331-acclaim-recovery.img) and everytime I get an error when I try to mount it on my laptop. I'd be happy to post the whole error, but the synopsis is "mount: wrong fs type, bad option, bad superblock on /dev/sdb1, missing codepage or helper program, or other error". Using sudo fdisk -l /dev/sdb shows that "Disk /dev/sdb doesn't contain a valid partition table". Putting it in the NT and trying to boot does nothing, just black screen after the n logo when it should go to recovery.
So I've tried numerous paths (~20 tries total) and every one seems to have a road block. I hope something in here makes sense to somebody a whole lot smarter than me! Please help!
~Nate
Are you sure that's the right CWM for CM 12.x? To flash 10.2 long ago I used CWM 6.0.2.x
Seems unlikely that an earlier version would be used for CM 12.x
That's a good point, your're on to something. I saw that in the cyanogenmod tutorial it says CWM doesn't support CM > 10.1.3. So your almost certainly right. (Why that's the active link in the beginner tutorial is still confusing to me.) I also see that CWM says it is not in active development for acclaim. So now on to twrp.
I tried the "Bootable SD card" instructions on the twrp acclaim page but can't get that to work. I've copied the img file to the root of the SD and renamed it to recovery.img but I don't know how to "boot TWRP using the cyanoboot menu from your sdcard". There is no cyanoboot menu on the sd card, it's only the img file, so no wonder nothing boots. How do I get the cyanoboot menu on the sd? My initial search led me to a page that has complex instructions on formatting the sd. Is that really the only way to get cyanoboot and ultimately get twrp to run??
Alternatively I've tried to burn the img to the sd using the dd command (thinking that an img file is meant to image an entire sd, not just live as a file on the sd). That gives me the errors that I posted originally (see section "Potentially related side note"). So I think you're right that I need a recovery other than CWM, but how do I get twrp to work?
Being a noob I feel like I'm missing something obvious but have been working for hours (ok, days) with no success.
Yeah, I think it *might* be that CWM is not going to cut it for CM 12.x, but the truth is I have no experience with TWRP so you're asking the wrong guy
I assume you looked at the "official" CM 12 thread here. For me the problem is what it is for you. There's not enough info there for someone who can follow good directions but is not already very familiar with all the ins and outs. What's needed is for digixmax to write a "how-to", but the last one he did was for CM 11. His directions are very clear. I was able to follow them as a noob for CM 10.2 without any trouble.
The hard way to do this is to sneak up on it by starting with CM 10.2, updating to CM 11 following digixmax's directions and then....well there must be a way to go from CM 11 to CM 12....maybe.....
I notice the sparse directions at CyanogenMod for CM 12 on Acclaim do refer to CWM so who knows?
coloradonate said:
Hi, complete noob here, will try to explain as best I can. Trying to get cyanogenmod 12.1 booted from SD. This is my first attempt for flashing any ROM on any device. I followed the acclaim tutorial on CM webpage (wiki.cyanogenmod.com...can't post link because I'm a forum noob). I can boot into CWM (v5.5.0.4) but when I go to install zip from sdcard, I get lots of errors. Without copy/paste, I'll do my best to state the important parts:
...
Installing update...
Warning: Nofile_contextscould not detect filesystem for /dev/block/platform/omap/omap_hsmmc.1/by-name/system, assuming ext4
mount: failed to mount /dev/block/platform/omap/omap_hsmmc.1/by-name/system at /system: No such file or directory
unmount of /system failed; no such volume
The error continues with nearly the same thing but for .../by-name/userdata at /data.
It again repeats the error with the /system (same as above)
Error ends with:
script succeeded: result was [0.200000]
Install from sdcard complete.
When I reboot the system, it goes back into stock B&N startup as if the ROM was not updated. No surprise considering the errors. I tried again and this time used CWM to enter "mounts and storage" and manually mounted /data and /system. The error for /data went away but the /system errors (x2) remain.
I've now tried cm-12.1-20151007-SNAPSHOT-YOG4PAO331-acclaim.zip and cm-12.1-20150901-SNAPSHOT-YOG4PAO236-acclaim.zip with the same result.
Oddly enough, when I tried older versions (have tried cm-11-20150831-SNAPSHOT-XNG3CAO3FN-acclaim.zip and cm-10.2-20131102-SNAPSHOT-M1-acclaim.zip), those files give me a different error. They say (example for CM v11):
Installing update...
E:Error in /sdcard/cm-11-20150831-SNAPSHOT-XNG3CAO3FN-acclaim.zip
(Status 0)
Installation aborted.
Is something wrong with my SD?!? I am using Linux Mint and Gparted to format the SD. I have the boot and lba flags on. Since I'm getting CWM to boot on the NT, I feel like the SD is OK and the error is in the .zip file or some setting on the NT itself. Does anybody have any ideas??
Potentially related side note: I've alternatively used the dd command and USB Image Writer to copy an img file to the SD (tried twrp-2.8.6.0-acclaim-sdcard.img and cm-12.1-20151007-SNAPSHOT-YOG4PAO331-acclaim-recovery.img) and everytime I get an error when I try to mount it on my laptop. I'd be happy to post the whole error, but the synopsis is "mount: wrong fs type, bad option, bad superblock on /dev/sdb1, missing codepage or helper program, or other error". Using sudo fdisk -l /dev/sdb shows that "Disk /dev/sdb doesn't contain a valid partition table". Putting it in the NT and trying to boot does nothing, just black screen after the n logo when it should go to recovery.
So I've tried numerous paths (~20 tries total) and every one seems to have a road block. I hope something in here makes sense to somebody a whole lot smarter than me! Please help!
~Nate
Click to expand...
Click to collapse
Your description sounds exactly like the SD card was not properly formatted with an MSDOS partition table with a primary partition as FAT32. From the CyanogenMod wiki: "Put the micro SD card (SD card from now on) in the computer. Backup all the information on the SD card. Everything on it will be deleted. Make a new MSDOS partition table and add a FAT32 partition as the first primary partition with a minimum of 300 MB. Then make sure you enable the boot and lba flags. This can be done in Ubuntu using GParted. Formats like EXT2, EXT3, and EXT4 do not work. It is not necessary to allocate the entire card. You can add other partitions to the card, but they need to be manually mounted on your Nook anyway." When you set up the partition table a the primary partition, the format must be written/saved to the SD card. Unmount the SD card and mount it again to ensure that the formatting took. Once that is verified then you can write to files to the SD card, unmout it again, and insert it into the Tablet and go through the install steps.
I'm looking at putting 12.1 on my Tablet, which currently has 10.2 and runs pretty well. But the basic setup instructions for the SD card are the same - MSDOS table with a FAT32 primary partition. You can add 3 more FAT32 partitions, but they must be primary and FAT32.
Thanks for the reply. Unfortunately I did partition just like it asked. It is set as Primary, Fat 32, and the boot and lba flags are on.
I'm still stuck, but I'm understanding a few things. The Cyanogenmod install wiki is obviously out of date (even though it says it was last modified Oct. 25, 2015 when I looked tonight). The wiki has you download CWM 5.0.x, which is a 2012 file intended to work with CM 10.x. Then later in the same wiki it says that CWM no longer supports CM>10.1.3, so obviously it is not up to date for CM 11.x and 12.x. Unfortunately the wiki was not updated to provide a link to a recovery that works...at least not that I've found. I've lost faith in that wiki.
I'm totally fine using Twrp, but I can't even get a version of twrp that works with the latest CWM 12.1 release. Should be simple, but for some reason can't get it to work. If anybody is still willing to try to help me, please point me in the right direction!
And here's a total noob question that may solve my problems: why does the cyanogenmod downloads page have a link for the .zip and a "recovery" .img? Is that img THE recovery that I should be using for that particular version of CM? I tried writing the image to the SD but have the same SD errors as I previously reported.
So...did you try following these directions? They are sketchier than I am comfortable with but it is the "official" thread. And there's certainly a recovery link there.
I'm thinking about upgrading from 10.21 but I just can't find directions that make me feel like I'm not going to trash what I already have
2 things to report: 1) I'll respond to the reply above. 2) got it working with CM 11!
1) Yes I have tried following that and read it more times than I can count, but my extreme noobiness has left me floundering in tutorial after tutorial. I tried fastboot, couldn't get it to install. Finally got it to install, couldn't get it to connect to the NT. I tried bootable SD, couldn't get it. Tried root, couldn't get that. Why couldn't I get any of that to work?? I have absolutely no idea, but I hit dead end after dead end and was left unbelievably frustrated by this whole thing. On to #2...
2) I got CM 11 to work! I don't care one bit that it's not 12.1, what's important is that I got CM finally running on my stock NT! I followed this tutorial (http://forum.xda-developers.com/showthread.php?t=2692403). It required one *very* slight modification that I posted at the very end of that thread (post #14.) Don't laugh at my excitement, I'm just happy this things is finally over. (For now at least...I'm sure I'll be digging further now that I've gotten this far.)
I'm really glad that worked for you I still remember how I felt when I got CM 10.21 working starting from stock on an ebay special.
You've given me a little push to get serious about upgrading to CM 11 or perhaps CM 12. I need to read (and reread) those posts until I feel like I've got it down. Your discovery will help, I'm sure.
Just to wrap up this thread, I got CM12.1 to work! Please refer to my last post (post #18) in the following thread for somewhat detailed instructions for how I did it: http://forum.xda-developers.com/showthread.php?t=2692403&page=2#post63932363
I hope that explains it all to anyone interested, or anyone else who was floundering around like I was. Now I'm happily running CM12.1 and loving it. Thanks to all the developers, especially Digixmax for the post that finally helped me through this!

Using an SD card to install/boot OS onto phone

Help, I want to know if theres anyway i can use an SD card to install or use it as a boot for my phone, I have a verykool rs90 and it currently doesnt have a OS, it gets stuck at the logo and its not recognized by my computer so I cant flash it, is there anyway i can do this through an SD card, PLS HELP
Zoulder said:
Help, I want to know if theres anyway i can use an SD card to install or use it as a boot for my phone, I have a verykool rs90 and it currently doesnt have a OS, it gets stuck at the logo and its not recognized by my computer so I cant flash it, is there anyway i can do this through an SD card, PLS HELP
Click to expand...
Click to collapse
In your previous thread you said you can boot the phone into Recovery mode, you further said that you've managed to get the update zip ready on the sd card but when you try to install it it says signature verfication failed and installation aborted . So it's evident that you can install OTA/ROM from external SD-card. BTW: To initiate mounting and booting from external SD-card instead of internal memory would require a heavy mod of Android's kernel ( read: boot.img ) and a specially prepared external SD-card ( replicating eMMC partition table by partitioning SD-card & flashing factory firmware images to these newly created partitions ).
That's what probably happened when you tried to flash
Finding update package...
Opening update package...
Verifying update package...
E:No signature (xxx files)
E:Verification failed
Installation aborted.
FYI:
Basically the ZIP File Signature Verification flag will enable flashing only if the ZIP file is signed properly by the developer. If ZIP isn't properly signed then it's treated as malware.
Advice:
Contact OEM's CS to get an orderly signed update.zip for your 7 years old low-end phone.

Categories

Resources