Related
Hi I was on the last step of installing Cyanogen Nighly build 116 on my SGS2 and got to step 7 of the guide on their wiki
http://wiki.cyanogenmod.com/wiki/Samsung_Galaxy_S_II:_Full_Update_Guide
but I couldnt find my external SD card on Clockwork mod recovery. I tried to reboot back to my normal samsung OS so I could use USB to put the 2 update zip files on my internal storage but the phone is now boot looping. I boot up to the samsung logo then the phone restarts.
What do I do please?
Hi again,
I have tried booting in download mode which does nothing but show me the android man withthe word Downloading... underneath (VolDown, Home, Power). I have tried booting back to Clockwork Mod recovery (VolUp, Home, Power) and I have tried messing around with adb to see if it sees any devices- which it does, it sees
304D19A75555E24E
but it doesnt accept adb push update.zip I guess because the phone is busy rebooting :S
My guess would be you've installed a different version of CWM recovery. Choose "Install zip from internal Sdcard" instead.
oinkylicious said:
My guess would be you've installed a different version of CWM recovery. Choose "Install zip from internal Sdcard" instead.
Click to expand...
Click to collapse
Hi
It says Clockwork Mod Recovery v4.0.1.4
It doesnt have an option other than install zip from sdcard
and it doesnt see the external sd card either.
I have
- reboot system now
- apply update from sdcard
- wipedata/factory reset
- wipe cache partitions
- install zip from sdcard
- backup and restore
- mounts and storage
- advanced
- power off
I chose install zip from sd card
then chose zip from sdcard
and I get the internal listing of files on the internal phone storage but no access to the external sd card. There is a folder there called, external_sd but when I select it, it just says No files found. It shows this when the sd card is inserted and uninserted though.
Do you know any way I can put the update files on the internal phone memory from my PC? I have adb installed and the android sdk. but adb wont push files to the phone. I used to know a way to boot the phone with fastboot but dont remember how to do that any more
You need to tell it where to save the file if you're going to do adb push, i.e. adb push update.zip /sdcard/cm7.zip, but you might need to mount somewhere to store it in mounts and storage first for it to work.
oinkylicious said:
You need to tell it where to save the file if you're going to do adb push, i.e. adb push update.zip /sdcard/cm7.zip, but you might need to mount somewhere to store it in mounts and storage first for it to work.
Click to expand...
Click to collapse
ah but I cant get it to boot so I cant get it to mount. The closest I can get is getting adb to recognise it as a device while it is bootlooping (it only gets up to the Samsung logo then reboots)
I did try "adb push update.zip /sdcard/cm7.zip"
failed to copy 'update.zip' to 'sdcard/cm7.zip' : Read-only file system
The phone is still rebooting over and over. Out of curiosity, would CWM not give the option to install zip from the external sd card if the phone didnt have root?
I bought this phone from a friend and he said the phone did have root but I actually am not sure if it does. Would that also cause me not to be able to use adb to push the file because the internal sd card was read only?
Either way - how do I get the phone back to a usable state please?
I mean from within CWM recovery, which you said you can access (ADB should work there after 30 seconds or so).
oinkylicious said:
I mean from within CWM recovery, which you said you can access (ADB should work there after 30 seconds or so).
Click to expand...
Click to collapse
booted to CWM - waiting for pc to notice phone exists so I can use adb...
... nothing is happening. (tried using mount usb storage too)
EDIT1: I rebooted CWM and when it came back - tada - windows noticed it. Ran the ADB command and the copy has worked over 36s.
Watch this space...
EDIT2: Got the phone to finally let me upload update.zip (the 116 nightly build from cyanogen) and gapps (for cyanogen7) using the mount option under Clockwork Mod recovery
installed update.zip
installed gapps.zip
rebooted and...
stuck at
Samsung
GALAXY S II
GT-I9100
/!\
``
nothing is happening, the phone doesnt boot... but CWM has changed colour to a pretty blue and I am now on v5.0.2.7. What am I meant to do next? I ran out of steps on http://wiki.cyanogenmod.com/wiki/Samsung_Galaxy_S_II:_Full_Update_Guide
Flash the update twice in succession, if the first one was quick.
oinkylicious said:
Flash the update twice in succession, if the first one was quick.
Click to expand...
Click to collapse
yes your right, it was quick. I flashed it again - much slower this time and it seems to be working - I finally got off the stuck screen. Currently watching the new cyanogen mod 7 boot screen.
Big thanksometer - if your anywhere near me i'd buy you a coffee.
Hey guys, today i was messing around with my nook tablet and i tried to restore it and i acidently deleted everything. now when ever i boot its goes straight to CWM recovery. ive tried to flash recovery and stock reboot and nothing worked. Is there anyway to restore it using usb or anything else? thanks.
I ran into similar difficulty with this earlier today. What worked for me eventually was using
the CMW Windows installer on my SD card, which nerfed it down from 32GB to 2GB,
formatted that 2GB partition,
put the "acclaim_update.zip" folder in the root,
inserted the sd card,
plugged the tablet into the charger,
power+n cycled once, then regular boot and it went it.
Your results may vary, though. It took a few tries before I finally got it to boot from SD
How exactly do i do that?
Fix for the Cyanoboot CWM bootlooping...
It could help someone, haven't seen this simple fix around so i decided to post it up here.
1. boot into CWM from sdcard, see here to download the sdcard version , instructions to burn the image to your sdcard are there too.
2. once you have finished burning the image into your sdcard you will see the size of your sdcard will be reduced to less than 50 MB, CLICK on your sdcard and you will see some files in there.
3. Download 8gb-16gb_cwm_internal.zip from my thread and copy-paste it to your sdcard so you can flash CWM internal using CWM sdcard version. HOPE YOU DONT GET CONFUSED.
4. Safely eject your sdcard from PC, power off your nook(long press power button), put the sdcard back into your nook, power on your nook.
5. It will boot into CWM sdcard then flash 8gb-16gb_cwm_internal.zip, reflash the ROM of your like (It should be on Internal sdcard, you can also swap to another sdcard containing the ROM while in CWM sdcard or resize CWM sdcard [50mb] with a partition tool software so you can copy a ROM to it).
6. Remove the sdcard from your Nook and select reboot system now from CWM
Done!
Your Nook tablet should now boot normally!!!
NOTE: the 8gb-16gb_cwm_internal.zip made by @succulent has few options missing so consider to install another internal CWM later. This process will just make you fix the bootlooping process and boot your device normally.
~ V
Flash "acclaim_update.zip"
I recently made a thread on how to flash "acclaim_update.zip" in CWM so head on over to it and see if it works for you and remember do a factory reset from CWM. http://forum.xda-developers.com/showthread.php?t=1762024
hi i just bought a samsung mega 6.3 in indonesia, it's a 16 version but i didn't check it before i root it, however i seem to remember when i plug it onto my computer it was 11 or 12 gb storage
so after rooting using guide in this thread " http://forum.xda-developers.com/showthread.php?t=2355680&page=3 ", when i plug it on my computer it shows only 128 mb storage, why is it happening? and if i checked setting - more - storage it says "8 gb (why 8 gb instead of 16 gb or 12 gb?).
if i open application manager from setting - application manager it says 352 mb used out of 12 gb free.
I used odin 3.07 to flash vcoreroot-v2.tar, followed by original kernel KERNEL-XSE-I9200XXUAMEE-1369705836.tar, followed by cwm recovery v6.0.3.2 - i9200-cwm-recovery
please help me. thank you so much
oh and the storage on the pc is empty without any folder, and i can't copy files onto it...
please helpppppp
The internal storage ( sdcard ) is only a folder on your data partition ( /data/media ). The entire 16GB is not allotted to your sdcard. It is shared. So you will not see the entire 16GB when you mount your sdcard on your PC. So no worried there. Also make sure your usb debugging is on before connecting your phone to PC.
Regarding root, the easiest method is to flash cwm recovery and then flash the SU zip file. If you use twrp recovery, the recovery will do the rooting for you. Just remember to reboot to recovery first after flashing the twrp recovery, else recovery will get overwritten by stock recovery.
I suggest, you flash your stock rom again and re-root. You could also try this app to root your phone using windows.
The internal storage ( sdcard ) is only a folder on your data partition ( /data/media ). The entire 16GB is not allotted to your sdcard. It is shared. So you will not see the entire 16GB when you mount your sdcard on your PC. So no worried there. Also make sure your usb debugging is on before connecting your phone to PC. ===> debugging is already on. yes however it shows up only 128 mb, and i couldn't copy any data onto it
Regarding root, the easiest method is to flash cwm recovery and then flash the SU zip file. If you use twrp recovery, the recovery will do the rooting for you. Just remember to reboot to recovery first after flashing the twrp recovery, else recovery will get overwritten by stock recovery.
Click to expand...
Click to collapse
i also couldn't get into the recovery mode, it was 2 red lines and it just restart, i've re root it twice using the same method...
0664348999
finally after 5 hours of works and skipping actual job. im able to get my pc to read the whole 12 gb of the storage,
by using steps and original firmware from hxxp://honai-android.blogspot.com/2013/11/how-to-update-galaxy-mega-63-i9200-with.html
for anyone who might stumble upon the same problem
thank you for helping @Silesh.Nair
[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'll try to make it brief. Some time ago, my stock Nook slowed down like a mule so I decided to root it, then applied Trimmer to enable trim. Beforehand I'd checked the eMMc with a Brickbug app and it popped up with "sane chip", as I'd read some Nooks had a faulty Samsung eMMc.
It went into a bootloop, and only started showing shredded Nook letters on an abstract background during boot. Then I tried various bootable SD cards to try to flash various stuff, as per available XDA threads, especially - leapinlar's, verygreen's and amaces'. First it would not complete the flashing of a ROM, just froze towards the end, then eventually wouldn't boot up at all.
Here's the weird part. Without an SD card, it doesn't boot up at all.
When I make a bootable SD, it only boots to TWRP 2.6.0.0 (some other versions [amaces] it won't boot to), but doesn't see any zips on the card and won't let me flash anything, even though it previously did, but wouldn't complete the flash.
Whatever else I burn on the card, it either doesn't boot up at all, or boots to whatever it is you can see on the attached printscreens, and won't mount anything. So if I'm guessing right, the eMMc is not borked, as it seems the device boots to some remnants of something that's there, and not on the SD.
Is there a way of fixing that mess? I'd appreciate any ideas.
Best
W.
You can try to flash this flashable_fix_bootdata-ovation.zip which typically should cure corrupted or missing bootdata issues.
Hi, thanks but how? The only thing I tried so far that the Nook boots to is a TWRP 2.6.0.0. bottable card and it won't see the zips on it. So how can I flash the fix bootdata zip?
wojtasys said:
Hi, thanks but how? The only thing I tried so far that the Nook boots to is a TWRP 2.6.0.0. bottable card and it w on't see the zips on it. So how can I flash the fix bootdata zip?
Click to expand...
Click to collapse
Have you tried the verygreen's old SD-based CWM recovery?
If you mean the one from that thread:
https://forum.xda-developers.com/showthread.php?t=2600572
I have. The download links for the initial card image don't work. I looked elsewhere - nowhere to be found.
Sorry about the trouble, guys, forgot to update the dns when the server moved. I just updated it, but it'll take some time to propagate. The actual new ip address is now 178.34.187.142 - you can place it into your hosts file if you don't want to wait.
Nook HD+ Bootloop error
OK, I tried the succulentboot.zip from your folder:
https://www.mediafire.com/folder/6a4rivb8kkdfu/Nook HD+):
Now the zips on the sd are accessible, so I tried flashing the flashable_fix_bootdata-ovation and the screen shows the result.
I tried flashing stock recovery too and it says it's done that, but I guess without the fixed bootfiles it won't work anyway.
wojtasys said:
OK, I tried the succulentboot.zip from your folder:
https://www.mediafire.com/folder/6a4rivb8kkdfu/Nook HD+):
Now the zips on the sd are accessible, so I tried flashing the flashable_fix_bootdata-ovation and the screen shows the result.
I tried flashing stock recovery too and it says it's done that, but I guess without the fixed bootfiles it won't work anyway.
Click to expand...
Click to collapse
Assuming that your flashing of stock recovery was successful (recovery's reports of successful completion can sometimes be erroneous) and also your factory backup partition is still intact, you can try to initiate a factory reset by using the "8 failed boots" method: with the Nook in the power-off state, power it on, then as soon as the boot screen appears hold down the power button until it powers off, do this 8 times, and the Nook should go into stock recovery to revert to factory-fresh state.
Flashing your flashable_restore_stock-recovery-ovation zip ends with the screen I'm attaching.
Then I tried "8 failed boots" but it only boots to CWM SD, without the card - it doesn't power up at all.
Eventually, nothing changes.
Tried putting the stock ROM on the card and flashing that, but the partition size is too small, even though its a 16GB card.
wojtasys said:
Now the zips on the sd are accessible, so I tried flashing the flashable_fix_bootdata-ovation and the screen shows the result.
Click to expand...
Click to collapse
If the issue is about the two files, you could mount /bootdata and copy them manually (ADB shell should be functional with any of these recoveries). You'd extract BCB and BootCnt from ZIP, and copy them onto SD card, then do something like:
Code:
mkdir -p /bootdata
mount -t vfat /dev/block/mmcblk0p6 /bootdata
cd /external_sd or /sdcard or /emmc (wherever SD card root is mounted)
cp BCB BootCnt /bootdata/
Or, you could edit the updater-script inside ZIP to remove the device assert line like in the attachment here. By the way, are the updated images here also failing?
Flashing your flashable_fix_bootdata-ovation-no-assert.zip shows "install from sd card complete" but the device still won't power up without the card.
Trying to mount bootdata results in "error mounting bootdata".
There's no adb command line in that sd recovery, just adb sideload. TWRP 2.6 had it but it didn't access the files on the sd.
Then, I'm not sure I'll know how to edit the updater-script inside ZIP to remove the device assert line.
Chances are your EMMC is hosed, in which case you can try running CM entirely off SD card using the succulent special build available at https://iamafanof.wordpress.com/201...-4-4-4-for-bricked-no-emmc-nook-hd-04nov2014/.