I am trying to flash zip files from my SD card in cmw.. I go to choose zip from sd then after choose external_sd/ when i choose it, it does absolutely nothing( I hit the home button and it says no file exists but i know the files are there). I also manually mounted the SD... I was originally trying to do the fix speaker sound.. But due to the fact i could not get the sd to read, i did it from the internal memory. Now i cannot use my phone app at all it just crashes. I now want to flash a new rom on to fix the issue, but as i said i can't flash the zip from the SD. If anyone can give me some assistance it would be greatly appreciated.
For flashing Roms you ALWAYS put them on your sdcard WHICH IS THE INTERNAL UNREMOVEABLE SDCARD. Your external sdcard on Samsung roms is called external_SD and in cm7 it is called emmc. On stock based roms (Samsung roms) you will always have to put the files on the sdcard NOT the external removeable sdcard.
Sent From My KickAss ATT SGS2 SPORTING CM7
Sounds like you already have a rom installed. Which one? Or are you still on stock? If stock, you can't flash from stock 3e recovery.
Assuming you have CWM Recovery, put the flashable zip on the root of the internal sdcard *not* the external sdcard, and not in any directory. If your directory structure on the sdcard is fairly long, the files may be hidden at the bottom, and you will have to scroll down to see them. Use the vol+ button to scroll in the up direction is easiest. Then you should be able to install the rom by selecting "install zip from sdcard" and then "choose zip from sdcard". Do not use "choose zip from internal sdcard".
I am running a stock rom rooted.. I was falling a sleep while typing it.. I ment I was trying to choose the rom in CWM.. I saved the ROM on my external SD so i can try to pull the file and flash my phone to it.. What i am saying is when i go to pick the ZIP under in CWM i can't access it. As i wrote in my original post
If you have stock rom plus root by Entropy512, then the kernel is straight stock with 3e recovery, and you can not flash a rom from 3e recovery. You will need to install a kernel which contains ClockworkMod Recovery first. See the guide linked in my signature for detailed instructions on how to do that.
And go back and read both RockRatt's post and my previous post, to learn that you can not install a rom from the external sd card. And you should spend some time reading in general, so you have a basic understanding of what you are doing. And then do some more reading.
external sd
monkey28rb said:
I am running a stock rom rooted.. I was falling a sleep while typing it.. I ment I was trying to choose the rom in CWM.. I saved the ROM on my external SD so i can try to pull the file and flash my phone to it.. What i am saying is when i go to pick the ZIP under in CWM i can't access it. As i wrote in my original post
Click to expand...
Click to collapse
Why is it so difficult to put the zipfile on internal sdcard for flashing purposes,
then after flashing using a file manager simply move the zipfile to external sdcard?
Of course if you were using CWM Manager you would not have the
problem in the first place, CWM Manager (apk) can be downloaded
here: http://megaupload.com/?d=TGXMLL1G it is fully compatible with
CWM recovery but you do not need to go into recovery mode.
With this app you will have access to external sdcard with no problem.
It has most of the same options and features as you would see in Rom
Manager but it's fully compatible with our phones and flashable zipfile
roms, kernels, modems and mods. (it even installs apps )apk).
This is a perfect solution to backup and restore roms too.
(fully CWM compatible Nandroid with option to name the backup)
Check it out!
I'm trying to make Official CM RC2 into a SDC version. I followed the instructions from the boot.zip. Replaced vold.fstab and replaced the updater script. This should be like any other SDC ROM, correct? I didn't completely format my SD card because it's already set up for SDC, I just need to install the SDC ROM and GAPPS and I'm good to go. But when I go to install the RC2 SDC ROM it gives an error after "installing update" in recovery. It says...
symlink: some symlinks failed
E:Error in /emmc/cm-10.1.0-RC2-acclain SDC.zip (I put the zips on my internal storage so I could find them easier)
(status 7)
I'm not sure what this error message means. Do something wrong in the SD boot process or what. Help would be appreciated. Thanks in advance.
datallboy said:
I'm trying to make Official CM RC2 into a SDC version. I followed the instructions from the boot.zip. Replaced vold.fstab and replaced the updater script. This should be like any other SDC ROM, correct? I didn't completely format my SD card because it's already set up for SDC, I just need to install the SDC ROM and GAPPS and I'm good to go. But when I go to install the RC2 SDC ROM it gives an error after "installing update" in recovery. It says...
symlink: some symlinks failed
E:Error in /emmc/cm-10.1.0-RC2-acclain SDC.zip (I put the zips on my internal storage so I could find them easier)
(status 7)
I'm not sure what this error message means. Do something wrong in the SD boot process or what. Help would be appreciated. Thanks in advance.
Click to expand...
Click to collapse
First of, you need to make sure that you have the appropriate version of CWM recovery for CM7, see http://forum.xda-developers.com/showthread.php?t=1640958.
Second, the symlink failures most likely have to do with your using the wrong version of updater-script for CM7 -- hence there would likely be some "symbolic link" commands in the script that try to link files that don't exist in CM7. To do this right, you'll need to edit the internal-install version of updater-script for CM7 to change the various internal target partitions to the corresponding SD target partitions. (You can compare the internal vs. SD versions of updater-script for CM10 which Succulent created for his CM10.x builds to get an idea of the needed changes). Then you'll need to find the right version of Gapps for CM7 and do the same for its updater-script. As a short cut you can try to use the updater-scripts Succulent created for his SD-based CM7 builds.
Finally, I believe the SD-based ROM uses a different version of boot.img than that of the EMMC-based ROM (the EMMC boot.img is actually a concatenation of Cyanoboot (aka flashing_boot.img) and CM10 boot.img). You might try to swap in the boot.img from a previous version of SD-based CM7 but it's likely a hit-n-miss.
digixmax said:
First of, you need to make sure that you have the appropriate version of CWM recovery for CM7, see http://forum.xda-developers.com/showthread.php?t=1640958.
Second, the symlink failures most likely have to do with your using the wrong version of updater-script for CM7 -- hence there would likely be some "symbolic link" commands in the script that try to link files that don't exist in CM7. To do this right, you'll need to edit the internal-install version of updater-script for CM7 to change the various internal target partitions to the corresponding SD target partitions. (You can compare the internal vs. SD versions of updater-script for CM10 which Succulent created for his CM10.x builds to get an idea of the needed changes). Then you'll need to find the right version of Gapps for CM7 and do the same for its updater-script. As a short cut you can try to use the updater-scripts Succulent created for his SD-based CM7 builds.
Finally, I believe the SD-based ROM uses a different version of boot.img than that of the EMMC-based ROM (the EMMC boot.img is actually a concatenation of Cyanoboot (aka flashing_boot.img) and CM10 boot.img). You might try to swap in the boot.img from a previous version of SD-based CM7 but it's likely a hit-n-miss.
Click to expand...
Click to collapse
It's not CM7, it's CM10.1 RC2. I already had my SD card running on succulent build SDC version. So I thought just following the instructions and replacing the files from sd boot.zip would work.
I figured out the status 7 error is for ROM protection. If someones trying to flash the wrong ROM it's a precautionary measure. Obviously I have the right ROM for acclaim though.
I don't want to internally flash anything. I need more space in the data partition.
Sorry, I don't know how I read "CM7" into your post.
In any event, you're in luck: Succulent has just released a CM10.1 RC3-based build for SD: http://goo.im/devs/succulent/acclaim/cyanogenmod/sdcard/cm_acclaim_10.1.0-RC3_31MAY2013_HD_SDC.zip.
digixmax said:
Sorry, I don't know how I read "CM7" into your post.
In any event, you're in luck: Succulent has just released a CM10.1 RC3-based build for SD: http://goo.im/devs/succulent/acclaim/cyanogenmod/sdcard/cm_acclaim_10.1.0-RC3_31MAY2013_HD_SDC.zip.
Click to expand...
Click to collapse
Well, this snuck past me. Thanks!
Hey guys,
I flashed NeatROM recently for the 4.3 update.
Followed these steps before flashing:
-Install CWM Recovery with Odin
-Download, and save zip to internal sdcard
-Go to recovery, Select Wipe data, Wipe cache
-Go to Advance and Select Wipe dalvik cache
-Go to Mounts and storage, select Format system
-Select Install Rom from SD card
Click to expand...
Click to collapse
Everything went well and the rom works fine.
I went in to flash a custom kernel earlier and when I selected install from zip I noticed that all my data/folders from the previous rom were still present. The new data is now in a ' 0\ ' folder.
I was running a 4.1.2 rom with Siyah kernel before I flashed 4.3. I also had a build of carbon flashed as a second rom for a short time. I'm guessing this has something to do with the data left behind.
I just want to start with a clean slate and wipe the internal SD completely; will megawipe (http://forum.xda-developers.com/showthread.php?t=1832326&page=38) do what I need it or do I need to format the SD from within CWM?
Thanks in advance.
p.s. after such a wipe is it better to flash a new rom via ODIN or would it be okay just use a zip from an external SD.
quizco said:
Hey guys,
I flashed NeatROM recently for the 4.3 update.
Followed these steps before flashing:
Everything went well and the rom works fine.
I went in to flash a custom kernel earlier and when I selected install from zip I noticed that all my data/folders from the previous rom were still present. The new data is now in a ' 0\ ' folder.
I was running a 4.1.2 rom with Siyah kernel before I flashed 4.3. I also had a build of carbon flashed as a second rom for a short time. I'm guessing this has something to do with the data left behind.
I just want to start with a clean slate and wipe the internal SD completely; will megawipe (http://forum.xda-developers.com/showthread.php?t=1832326&page=38) do what I need it or do I need to format the SD from within CWM?
Thanks in advance.
p.s. after such a wipe is it better to flash a new rom via ODIN or would it be okay just use a zip from an external SD.
Click to expand...
Click to collapse
You need to format /data partition. Megawipe will work. But, IHMO, no need for that. Just do it yourself from CWM.
Also, theres a big difference between odin "roms" and flashable zip roms.
If you flash something via Odin, it means that's probably (or surely) an official Samsung firmware without modifications. A flashable zip one is a custom rom.
Depends what you need/want. Most of us here use custom roms that we flash via cwm.
Thanks for the quick reply, bornlivedie.
bornlivedie said:
You need to format /data partition. Megawipe will work. But, IHMO, no need for that. Just do it yourself from CWM.
Click to expand...
Click to collapse
I'll do it via the CWM /data format over the weekend. Cheers.
bornlivedie said:
Also, theres a big difference between odin "roms" and flashable zip roms.
If you flash something via Odin, it means that's probably (or surely) an official Samsung firmware without modifications. A flashable zip one is a custom rom.
Depends what you need/want. Most of us here use custom roms that we flash via cwm.
Click to expand...
Click to collapse
My mistake for not being clearer in my original post; I have flashed a few custom roms before so I did know that Odin's generally reserved for flashing official sammy roms and customs go through custom recoveries.
Thanks for the heads up and the concern though. Much appreciated.
Going to 4.3 I'd recommend formatting the internal sd in CWM, also system, data and preload. If you read neat rom thread you see similar advice, the 5.4 aroma installer comes with Philz 5.15 recovery which is the best CWM to use.
[Caveat emptor: adopt/follow this guide at your own risk].
[Important Note: this process is applicable for CM11 builds that still maintains two separate partitions for /data and /media – as the case with CM10.x and stock ROMs (see http://forum.xda-developers.com/showthread.php?p=48612997#post48612997 for more info). If/when these two partitions get merged in some future CM11 builds (as being contemplated by our NT CM developers – see http://forum.xda-developers.com/showthread.php?t=2560827&page=28) this installation process will not be valid for those future builds with merged /data+media partition].
The following is the process using SD-based recovery to install CM11 internally (i.e., on emmc) on a Nook Tablet running stock ROM. [If your NT is already running CM10.x, see http://forum.xda-developers.com/showthread.php?t=2670589 for a simpler process to update from CM10 to CM11]. This same process can also be used to install CM12.x -- see http://forum.xda-developers.com/showpost.php?p=64624390&postcount=21 for needed corresponding versions of CM12 ROM, Android 6.0 GApps, and EMMC-based CWM recovery.
Using a disk partition tool (such as MiniTool Partition Wizard Home Edition) create on SD card a Primary FAT32 partition, and set the partition ID type for the partition to 0x0C FAT32 LBA and set its Active flag. Once this is done, the partition should appear as a (read/write accessible) drive under Windows
Obtain and copy to the SD card the following files:
first MLO, then next u-boot.bin and flashing_boot.img in succulent_boot.zip obtained from https://www.mediafire.com/folder/xjwc1a482a6ll/Nook_Tablet
TWRP (TeamWin Recovery Project) version 2.6.3.0 or later, e.g., openrecovery-twrp-2.6.3.1-acclaim-sdcard.img from http://techerrata.com/browse/twrp2/acclaim, rename it to recovery.img before copying to SD card.
the flashable_CWM_6.0.4.5_chrmhoffmann.zip zip file from https://www.mediafire.com/folder/xjwc1a482a6ll/Nook_Tablet which contains the CWM recovery v0.2 provided by Chris Hoffmann (in the first post of the XDA Official CM11 thread http://forum.xda-developers.com/showthread.php?t=2560827).
the zip file of CM11 ROM build of your choice from http://download.cyanogenmod.org/?device=acclaim (see http://www.cyanogenmod.org/blog/cm-11-m4-post-release-items for considerations in choosing nightlies vs. snapshot/stable builds).
the zip file of the Gapps package corresponding to CM11 – e.g., from http://wiki.cyanogenmod.org/w/Google_Apps
Put the SD card into the NT, and boot from its power off by inserting a powered USB cable. Press and hold the N button as soon as CyanoBoot comes up to get the boot menu to display.
Select SDC Recovery.
[Optional step but highly recommended] Select Backup to backup your NT current ROM config (/boot, /recovery, /system, and /data).
Select Wipe data & factory reset.
Select install zip from SD card and install flashable CWM recovery zip file.
Select install zip from SD card and install CM11 zip file.
Select install zip from SD card and install Gapps zip file.
Remove SD card and select reboot.
Once the NT boots up, set up the wifi connectivity and your google account info. If you had previously used Google backup service on your NT your apps will be auto-downloaded (but their settings will not be auto-restored).
Notes
If the Nook fails to boot off SD -- the two most common symptoms of failed SD boot and their likely causes are:
The NT boots straight to stock -- most likely the boot partition's type and/or flag are not correctly set, or the NT cannot find the MLO in the boot partition (make sure that MLO is the very first file to be copied to the freshly made /boot partition).
The NT screen stays dark for seemingly a long time then eventually boots to stock -- most likely the MLO or u-boot.bin are corrupted. When in doubt, compare the size of the two copies of the files in bytes.
Installing CM11 ROM and Gapps will override your NT's current boot, recovery, ROM, and Apps, so make sure that you backup all this stuff using recovery backup function, for easy in reverting to previous ROM if desired. See my post at http://forum.xda-developers.com/showthread.php?p=48612997#post48612997 for more "Info and Tips for Mitigating Risks in Rooting and Flashing Custom-ROM".
Also, I would advise against using any other functions of the recovery without first carefully researching to understand what they really do.
My thanks to all the developers who collective work created the wonderful CM11 ROM for the NT as well as the tools and info I made use of to install it.
bad boot image
I have followed your instructions carefully. But got an error message after selecting SDC recovery option from the boot menu..
booti: bad boot image magic (in memory).
I have tried to seat the card several times, no difference. This is a SanDisk 16GB class 10 card. I have installed CM11 on it, and worked. So the card can work. Now I want to install CM11 internally.
Don't know what else to try at this point. Please help. Thanks!
---------- Post added at 10:55 PM ---------- Previous post was at 10:28 PM ----------
gammaworks said:
I have followed your instructions carefully. But got an error message after selecting SDC recovery option from the boot menu..
booti: bad boot image magic (in memory).
Click to expand...
Click to collapse
Never mind, I have picked the wrong recovery.img. Ooops.
did not work for me
Installing it internally for the first time. Did not work...
set_metadata_recursive: some changes failed
E:Error executing updater binary in zip '/sdcard/cm-11-... SNAPSHOT-M4-acclaim.zip'
Error flashing zip '/sdcard/cm-11...SNAPSHOT-m4-acclaim.zip'
It appears I have bricked my nook tablet.
gammaworks said:
Installing it internally for the first time. Did not work...
set_metadata_recursive: some changes failed
E:Error executing updater binary in zip '/sdcard/cm-11-... SNAPSHOT-M4-acclaim.zip'
Error flashing zip '/sdcard/cm-11...SNAPSHOT-m4-acclaim.zip'
...
Click to expand...
Click to collapse
Which version of SD based recovery did you use?
Also, you might want to consider to first flash CM10.x (see http://forum.xda-developers.com/showpost.php?p=51377882&postcount=163) then later update to CM11.
come back from the dead
digixmax said:
Which version of SD based recovery did you use?
Also, you might want to consider to first flash CM10.x (see http://forum.xda-developers.com/showpost.php?p=51377882&postcount=163) then later update to CM11.
Click to expand...
Click to collapse
Thanks. An youtube video helped me out in the end: watch?v=3YYXtGAt6GY
What did I do differently this time? After installed openrecovery-twrp-2.7.0.0-acclaim-sdcard.img onto emmc, I rebooted NT without a SD card. The TWRP boot menu came up. I put the SD card back in. The SD card has CM11 and Gapps zip files. I then selected internal EMMC recovery (that is the key I think):
factory reset
install cm-11-20140405-SNAPSHOT-M5-acclaim.zip
install pa_gapps-modular-mini-4.4.2-20140321a-signed.zip
Now I have Android 4.4.2 running on my NT.
gammaworks said:
...
What did I do differently this time? After installed openrecovery-twrp-2.7.0.0-acclaim-sdcard.img onto emmc
...
Click to expand...
Click to collapse
The TWRP openrecovery-twrp-2.7.0.0-acclaim-sdcard.img is for SD card, the corresponding version for emmc openrecovery-twrp-2.7.0.0-acclaim.img.
gammaworks said:
Thanks. An youtube video helped me out in the end: watch?v=3YYXtGAt6GY
What did I do differently this time? After installed openrecovery-twrp-2.7.0.0-acclaim-sdcard.img onto emmc, I rebooted NT without a SD card. The TWRP boot menu came up. I put the SD card back in. The SD card has CM11 and Gapps zip files. I then selected internal EMMC recovery (that is the key I think):
factory reset
install cm-11-20140405-SNAPSHOT-M5-acclaim.zip
install pa_gapps-modular-mini-4.4.2-20140321a-signed.zip
Now I have Android 4.4.2 running on my NT.
Click to expand...
Click to collapse
I did the same as you and get stuck at the CM boot screen. Tried 2x reflashing and keep getting stuck at the CM boot screen with the spinning arrow.
nm, 3rd time was the charm for some reason . Going through setup now, thanks!
bobzdar said:
I did the same as you and get stuck at the CM boot screen. Tried 2x reflashing and keep getting stuck at the CM boot screen with the spinning arrow.
nm, 3rd time was the charm for some reason . Going through setup now, thanks!
Click to expand...
Click to collapse
How long did you wait for the first-time boot to complete?
FWIW successful first-time boot typically takes 3 to 4 min.
digixmax said:
How long did you wait for the first-time boot to complete?
FWIW successful first-time boot typically takes 3 to 4 min.
Click to expand...
Click to collapse
I waited around 15 minutes the first two times. I could tell it was doing something different the 3rd time as the swirling arrow would stop briefly as it presumably loaded things while the first two times it just swirled non-stop.
Great procedures
digixmax said:
[Caveat emptor: adopt/follow this guide at your own risk].
[Important Note: this process is applicable for CM11 builds that still maintains two separate partitions for /data and /media – as the case with CM10.x and stock ROMs (see http://forum.xda-developers.com/showthread.php?p=48612997#post48612997 for more info). If/when these two partitions get merged in some future CM11 builds (as being contemplated by our NT CM developers – see http://forum.xda-developers.com/showthread.php?t=2560827&page=28) this installation process will not be valid for those future builds with merged /data+media partition].
The following is the process using SD-based recovery to install CM11 internally (i.e., on emmc) on a Nook Tablet running stock ROM. [If your NT is already running CM10.x, see http://forum.xda-developers.com/showthread.php?t=2670589 for a simpler process to update from CM10 to CM11].
Using a disk partition tool (such as MiniTool Partition Wizard Home Edition) create on SD card a Primary FAT32 partition, and set the partition ID type for the partition to 0x0C FAT32 LBA and set its Active flag. Once this is done, the partition should appear as a (read/write accessible) drive under Windows
Obtain and copy to the SD card the following files:
first MLO, then next u-boot.bin and flashing_boot.img in succulent_boot.zip obtained from https://www.mediafire.com/folder/xjwc1a482a6ll/Nook_Tablet
TWRP (TeamWin Recovery Project) version 2.6.3.0 or later, e.g., openrecovery-twrp-2.6.3.1-acclaim-sdcard.img from http://techerrata.com/browse/twrp2/acclaim, rename it to recovery.img before copying to SD card.
the flashable_CWM_6.0.4.5_chrmhoffmann.zip zip file from https://www.mediafire.com/folder/xjwc1a482a6ll/Nook_Tablet which contains the CWM recovery v0.2 provided by Chris Hoffmann (in the first post of the XDA Official CM11 thread http://forum.xda-developers.com/showthread.php?t=2560827).
the zip file of CM11 ROM build of your choice from http://download.cyanogenmod.org/?device=acclaim (see http://www.cyanogenmod.org/blog/cm-11-m4-post-release-items for considerations in choosing nightlies vs. snapshot/stable builds).
the zip file of the Gapps package corresponding to CM11 – e.g., from http://wiki.cyanogenmod.org/w/Google_Apps
Put the SD card into the NT, and boot from its power off by inserting a powered USB cable. Press and hold the N button as soon as CyanoBoot comes up to get the boot menu to display.
Select SDC Recovery.
[Optional step but highly recommended] Select Backup to backup your NT current ROM config (/boot, /recovery, /system, and /data).
Select Wipe data & factory reset.
Select install zip from SD card and install flashable CWM recovery zip file.
Select install zip from SD card and install CM11 zip file.
Select install zip from SD card and install Gapps zip file.
Remove SD card and select reboot.
Once the NT boots up, set up the wifi connectivity and your google account info. If you had previously used Google backup service on your NT your apps will be auto-downloaded (but their settings will not be auto-restored).
Notes
If the Nook fails to boot off SD -- the two most common symptoms of failed SD boot and their likely causes are:
The NT boots straight to stock -- most likely the boot partition's type and/or flag are not correctly set, or the NT cannot find the MLO in the boot partition (make sure that MLO is the very first file to be copied to the freshly made /boot partition).
The NT screen stays dark for seemingly a long time then eventually boots to stock -- most likely the MLO or u-boot.bin are corrupted. When in doubt, compare the size of the two copies of the files in bytes.
Installing CM11 ROM and Gapps will override your NT's current boot, recovery, ROM, and Apps, so make sure that you backup all this stuff using recovery backup function, for easy in reverting to previous ROM if desired. See my post at http://forum.xda-developers.com/showthread.php?p=48612997#post48612997 for more "Info and Tips for Mitigating Risks in Rooting and Flashing Custom-ROM".
Also, I would advise against using any other functions of the recovery without first carefully researching to understand what they really do.
My thanks to all the developers who collective work created the wonderful CM11 ROM for the NT as well as the tools and info I made use of to install it.
Click to expand...
Click to collapse
Your procedures worked out great. I've managed to take a stock Nook Table and have it running KitKat 4.4.4 in 3 day. The 1st 2 days I had only managed to root it and play around a bit. Thanks to every ones great work I'm up and running. 1st boot was a bit interesting as I renamed openrecovery-twrp-2.6.3.1-acclaim-sdcard.img to recovery.img.img but after review the SD Card / rebuilding there were no more issues. it it booted and worked great. Thanks again ===
I ran into a problem and am hoping for a hand. My NT boots perfectly form the SD card and loads up the recovery screen while following the instructions, I made a backup, but when I go to do the data wipe and factory reset or start to install the CWM file I get an error of "E: Unable to mount '/BootData' ".
I have tried starting over by resetting up the Nook and registering it again, but same thing. If I pull out the SD card it boots right up into use as a standard NT ready to register and go.
I am going to try again starting over and with a different version of TWRP just in case that is the issue.
Thanks for the help!
Allkair said:
I ran into a problem and am hoping for a hand. My NT boots perfectly form the SD card and loads up the recovery screen while following the instructions, I made a backup, but when I go to do the data wipe and factory reset or start to install the CWM file I get an error of "E: Unable to mount '/BootData' ".
I have tried starting over by resetting up the Nook and registering it again, but same thing. If I pull out the SD card it boots right up into use as a standard NT ready to register and go.
I am going to try again starting over and with a different version of TWRP just in case that is the issue.
...
Click to expand...
Click to collapse
Did you try TWRP v2.6.3.0 (openrecovery-twrp-2.6.3.0-acclaim-sdcard.img at http://techerrata.com/browse/twrp2/acclaim)?
Working
Thanks for the help. Along the way I did get it working on the night of 11/10, I just forgot to post that . 9th try is the charm I guess? In any case I tried first with TWRP 2.8.1.0 and then went back to 2.6.3.1 and then on my last attempt tried again with 2.8.1.0 and it worked so I have a NT running the last monthly of 11 and so far no issues. The sad news is that I have no idea what I did different to make it work the final time vs the first couple of try's.
YES YES YES!! It works! I've been struggling for more weeks than I care to admit to install CM 12. I've followed nearly every tutorial I can find and pursued WAY too many paths (bootable SD, fastboot, root) and couldn't get anything to work. Probably my very minimal knowledge of this subject is the culprit, but I've done a ton of research. Finally I decided to give CM 11 a shot and found this post. What a life saver!! Thank you everyone for your contributions to make this possible even for laymen like me!
FWIW, I couldn't get it to work with the "flashable_TWRP_2.6.3.1.zip" included in the mediafire folder provided by digixmax. I deleted that from the SD, downloaded 2.6.3.1 from the TWRP website (note: SD version) and it worked! I also tried the non-SD version of TWRP 2.6.3.1 and it didn't work...required the SD version to work. You guys rock!
coloradonate said:
...
FWIW, I couldn't get it to work with the "flashable_TWRP_2.6.3.1.zip" included in the mediafire folder provided by digixmax. I deleted that from the SD, downloaded 2.6.3.1 from the TWRP website (note: SD version) and it worked! I also tried the non-SD version of TWRP 2.6.3.1 and it didn't work...required the SD version to work. You guys rock!
Click to expand...
Click to collapse
You need to use the SD version of CWM or TWRP to flash CM from SD.
flashable_TWRP_2.6.3.1.zip is a flashable zip to flash and install TWRP itself into EMMC.
So if I download the most recent TWRP and CM 12.1 zip, could I simply replace the 2 older TWRP and CM 11 files on my SD? Would that actually work to get 12.1? It seems like the other files are only related to the bootloader and should be universal to work with any recovery and CM zip. Somehow I doubt it's that easy..
coloradonate said:
So if I download the most recent TWRP and CM 12.1 zip, could I simply replace the 2 older TWRP and CM 11 files on my SD? Would that actually work to get 12.1? It seems like the other files are only related to the bootloader and should be universal to work with any recovery and CM zip. Somehow I doubt it's that easy..
Click to expand...
Click to collapse
The function of the 2 files MLO and u-boot.bin is to boot the NT and load CyanoBoot (the 3rd file flashing_boot.img) which in turns would enable you to select and load the recovery.img file on the SD card; hence they should be invariant of the CM version you want to flash.
All you need is a copy of SD-based (TWRP) recovery.img version that is compatible with CM12.x and the GApps package.
Wow, it worked with 12.1! I have stumbled upon THE thread that finally helped me get this to work. Countless dead ends and I finally found it.
I took the plunge and tried installing cm12.1. Per post #1 in this thread, I used the same flashing_boot.img, MLO, and u-boot.bin that's in digixmax's mediafire folder. Also used the same flashable_CWM_6.0.4.8_chrmhoffmann.zip per post #1.
The files that are different from post #1 in this thread are: the most recent CM12.1 release (as of tonight: cm-12.1-20151117-SNAPSHOT-YOG7DAO1K6-acclaim.zip), the most recent TWRP for SD (as of tonight: twrp-2.8.6.0-acclaim-sdcard.img; renamed to recovery.img before copying to SD as suggested) and a compatible gapps version. A little google searching led me to the pico gapps from TKruzze that I got from post #1 of this link (http://forum.xda-developers.com/android/software/tk-gapps-t3116347). I downloaded this from the BasketBuild link under "Proper DPI Play Services" of the Pico Modular Package in post #1 of that link I just mentioned. I followed the same directions that were in post #1 of this thread that originally gave me success with CM11, and sure enough it all worked great with CM12.1. I'm now running CM12.1 and couldn't be happier.
A HUGE THANK YOU to digixmax and everyone else who contributed to the creation of these seemingly universal files (e.g., flashing_boot.img, MLO, u-boot.bin, etc.) to enable this to work. And of course a THANK YOU to the CWM, TWRP and CM developers. Seriously, you guys rock.
can someone check if my files are correct? especially the first 3 since I cant boot from SD no matter how many time I reformat, redownload, recopy....
ddvche said:
can someone check if my files are correct? especially the first 3 since I cant boot from SD no matter how many time I reformat, redownload, recopy....
Click to expand...
Click to collapse
Did you boot from power-off by inserting a powered USB cable?
Also, make sure that MLO is the very first file you copy to the freshly reformatted, empty SD card.
Hi,
I found a CM 12.1 ROM for my Galaxy Exhibit II 4G (SGH-T679) over on this thread, but the ROM is listed as OS2SD.
I searched online but could find no mention of what OS2SD is.
The creator of the ROM posted this in the thread:
Notes for OS2SD:
Before you start: I cannot stress enough cwm backups/restoring will not work with this OS2SD release! And data MUST be formated NOT Optional!
1. You MUST Backup All data or it WILL be lost!
2. You MUST Format /system, /data, /cache, and /sdcard0 in cwm/twrp.
At this point you can format sdcard0 as ext4.
3. Install the new CWM/TWRP the old one will not work from now on!
If you didnt before now would also be a good time to format the internal storage which in the new recovery is now /data to ext4.
4. Once formated first flash the OS2SD rom
5. Then flash GAPPS and/or other packages.
At this point you can restore data. Note the kernel is special so you cant use older ones so you can only restore things like /data backups and adb/titanium backups.
6. Then reboot and enjoy the extra space!
Click to expand...
Click to collapse
Does this mean that my CWM backups will not work? (They are stored on my SD card)
Also, does it mean I have to get a new recovery?
Thanks!
ejj28 said:
Hi,
I found a CM 12.1 ROM for my Galaxy Exhibit II 4G (SGH-T679) over on this thread, but the ROM is listed as OS2SD.
I searched online but could find no mention of what OS2SD is.
The creator of the ROM posted this in the thread:
Does this mean that my CWM backups will not work? (They are stored on my SD card)
Also, does it mean I have to get a new recovery?
Thanks!
Click to expand...
Click to collapse
From what i could understand from searching around OS2SD is OS to SDcard, it requires the SDcard to be partitioned with some tool, and make it as internal storage where you can install the rom on it and gapps and kernel and recovery, anyway, i suggest you ask there in Q&A thread of your phone as well, you will get a faster and a better answer than mine of course..good luck
Regards Migo