Several users have complained that they get blank screens and cannot flash new roms to their Nook Color. And sometimes they end up in a recovery bootloop where it will do nothing but boot to recovery no matter what they choose in the boot menu. Sometimes this is due to corrupted partitions on internal memory.
DizzyDen has prepared some .img files that can be burned to emmc to repair some of these issues, and they work well. But some of the files are very large and it takes a little knowledge of adb commands on the part of the users. And some users cannot get adb working on their machines. So I started investigating other solutions, and I have made some tools that work that I hope are user friendly.
Dean Gibson has a thread that describes how to repartition emmc to set the partition sizes for data and media to the user's preference. He repartitions partitions p6 (data), p7 (cache) and p8 (media). In studying his zip, I figured out how to make his tool repair partitions p4 (extended), p5 (system), p6 (data), p7 (cache), and p8 (media). And I was able to add additional commands to also repair partition p1 (boot). I asked Dean's permission to post his tools as modified by me and he agreed. Thanks Dean!
So that takes care of partitions 1, 4, 5, 6, 7, and 8.
Partitions 2 and 3 are very special and one must be very careful with them. Partition 2 is 'rom', which holds information that is specific to the user's device (serial number, etc.), and it is used by the system to set flags for deciding whether to boot to recovery or not and set the boot count that is used to decide whether to do a reset to factory conditions (8 failed boots). Partition 3 is 'factory' and holds the factory.zip file used by the 8 failed boot reset (if you want to learn more about the 8 failed boot reset, go to my tips thread linked in my signature). It also holds a backup of the device information in partition 2. So it is possible to repair partition 2 if partition 3 is still intact.
A few users have somehow managed to flash Nook Tablet ROMs to their Nook Colors and really messed up partition 4. (Edit: and now I know how it happened, some idiot recommended that they remove the first line of the updater script. NEVER do that! That line is a safety check to make sure you are flashing to the right device. You can also defeat the safety check by using an old CWM that has the toggle, 'disable asserts'. Never do that either.) And since partition 4 is the extended partition that holds partitions 5, 6, 7, and 8, they get messed up too. To repair those partitions along with partition 1, use CWM recovery to flash the two zips attached below. Be warned that everything in emmc media (p8) will be wiped out, so you may want to back that up first if you still can. The first zip to flash is 'NookColor-emmc-repair-partitions-1-4-5-6-7-8.zip'. It will recreate those partitions on emmc. As soon as you have sucessfully flashed that zip, you must reboot the Nook Color back to CWM so that the updated partition table is read by CWM. Then you need to flash 'NookColor-emmc-format-partitions-5-6-7-8.zip' (partitions 1 and 4 do not need formatting). It will format the newly created partitions to the correct structure. Now you can use CWM to restore an earlier nandroid backup or flash your favorite ROM (including stock, get version 1.4.3 that I have modified to be flashable with CWM here, or DizzyDen has posted some excellent 1.4.1 stock ROMs here). If you are going to flash a stock ROM, you must be sure to use the format zip or the stock ROM will not boot properly.
If you are in a recovery bootloop, the first thing I recommend trying is to use my CWM version 5.5.0.4 bootable SD that is discussed in my tips thread linked in my signature and has been modified to help get out of some kinds of recovery flag bootloops. If you are in a recovery bootloop that just hangs, it may get you out of it after exiting my CWM with the 'reboot' command in the menu. But if you are still in the loop after doing that, it may be because your device info is missing or corrupted in partition 2. It will not boot to a ROM without this info. (Specifically, it needs a file in /rom/devconf named DeviceID. It is a text file with your 16 digit serial number in it followed by a line feed, 17 bytes.) Try flashing with CWM my 'NookColor-emmc-repair-partition-2.zip' attached to this post to recreate that info. But I recommend this as a last resort, since messing with that partition is risky. That zip will recreate the partition, reset the flags and copy your device specific information from partition 3. But your partition 3 must be intact for this to work. If it is not, the zip will abort and do nothing.
Additionally, for those that do not want to use CWM, I have made a bootable SD that has an older version of TWRP here. Newer versions of TWRP will return an error message when trying to flash these zips. It also has been modified to get you out of some kinds of bootloops.
Two points of information. First, I have included a temporary copy of CWM 5.5.0.4 on the boot partition of my repair so that if tries to reboot to emmc before you put a ROM on it, it goes to CWM. It will be removed as soon as you restore a backup or flash a ROM. Second, the new partition scheme created with my zip is for the original Nook Color's 1GB data and 5GB media. If you want one of the other schemes (5GB data/1GB media or 2GB data/4GB media) go to Dean Gibson's thread and flash his zips after you have repaired your system with mine. See his thread here.
I'm adding a little extra information about emmc partition structure for those interested. With any MBR disk there can be a maximum of four primary partitions. So to have more than four partitions the last primary partition is created as an extended partition so multiple logical partitions can be made inside it. The emmc structure is: p1 (boot, fat, primary), p2 (rom, fat, primary), p3 (factory, ext3, primary), p4 (extended, going from end of p3 to end of the disk), p5 (system, ext2, logical, inside the extended), p6 (data, ext3, logical, inside the extended), p7 (cache, ext3, logical, inside the extended) and p8 (media, fat, logical, inside the extended).
You save my nook color
Thank you so much. My serial number and other information were recovered successfully. Without those information I could not boot into any rom. If you cannot boot into ROM after following the first 2 steps, try recover partition 2. It works for me.
:laugh::laugh::laugh::laugh::laugh:
Thanks
My nook has been stuck in a "will not boot" state for about a week. I could run CWM and cyanoboot, but when ever I tried to boot CM I would get stuck at the "loading..." screen. I tried loading both CM7 & CM9 but neither one would boot.
I ran both repair scripts, reloaded CM7.1 and success!
Thanks Leapinlar! :good:
THANK YOU!!!!!!
Right from my 1st install I couldn't get the bar at the bottom of the screen, which made using the Kindle app more than a little difficult. This finally cleared everything off so I could start with a clean slate, and BINGO! I know have the bottom bar on all the screens. I assume when I go in to the Kindle app it will be ok now also (I just have to format a 16gb microSD and put in the Nook Color 1st).
I can't thank you enough!!!!
Ugh! Tried this method too, and I still cannot get the nook to boot into CWR or CWM. I tried the 8 boots thing too, but I don't know if I ever did it right because I have cyanogen mod installed on emmc. Not sure how to repair the partition if I cannot even boot into anything that allows me to flash the zip to the chip. I thought it may be the sd, but the sd cards work on my other nook. I have now basically dissembled my nook color trying to find any other solution I wish I knew what happened in the first place.
czarofthefrozentundra said:
Ugh! Tried this method too, and I still cannot get the nook to boot into CWR or CWM. I tried the 8 boots thing too, but I don't know if I ever did it right because I have cyanogen mod installed on emmc. Not sure how to repair the partition if I cannot even boot into anything that allows me to flash the zip to the chip. I thought it may be the sd, but the sd cards work on my other nook. I have now basically dissembled my nook color trying to find any other solution I wish I knew what happened in the first place.
Click to expand...
Click to collapse
Did you try my version of the CWM bootable SD card? It is on my tips thread and has been modified to boot in certain types of recovery bootloops. Unless you get CWM running you cannot flash things to internal memory. And depending on where in the boot process it hangs, you may not be able to get adb working to put things there either. And the 8 failed boots will not work unless you have stock recovery still on emmc.
Sent from my NookColor using Tapatalk
leapinlar said:
Did you try my version of the CWM bootable SD card? It is on my tips thread and has been modified to boot in certain types of recovery bootloops. Unless you get CWM running you cannot flash things to internal memory. And depending on where in the boot process it hangs, you may not be able to get adb working to put things there either. And the 8 failed boots will not work unless you have stock recovery still on emmc.
Sent from my NookColor using Tapatalk
Click to expand...
Click to collapse
Yup. Tried the card. I believe I replaced the emmc with cyanogenmod back in the day. Starts, goes to loading, turns black, then done. Cannot do anything after that. Bummer, sounds like it is actually toast.
czarofthefrozentundra said:
Yup. Tried the card. I believe I replaced the emmc with cyanogenmod back in the day. Starts, goes to loading, turns black, then done. Cannot do anything after that. Bummer, sounds like it is actually toast.
Click to expand...
Click to collapse
If you can get adb working while it is sitting there black, you can push the stock recovery files to partition one. Then you may be able to do the 8 failed boots. You can extract the stock recovery files from my zip in my tips thread.
leapinlar said:
If you can get adb working while it is sitting there black, you can push the stock recovery files to partition one. Then you may be able to do the 8 failed boots. You can extract the stock recovery files from my zip in my tips thread.
Click to expand...
Click to collapse
Worth a shot. Have nothing more to lose other than time. Maybe adb will work with you card in it. It didn't work with everything else I tried.
OMG OMG thank you soooo much for this thread , you saved my reading addict self from going insane ......
You've done a great job on collecting all of these useful things, especially for those who are stuck with their Nook Color boot looping. (I was once that guy) Dean helped me out with his data zips as well way back! Thanks for all this! :good: :victory:
Much thanks, leapinlar. Restored a nandroid with TWRP that was corrupted and lost my boot partition. I used your first 2 repair zips and I'm back in business. Your many contributions are greatly appreciated.
Mike T
OMG! Thank you so much for putting this up! Back at the beginning of the year I was having problems with my NC not going into USB Mode and only showing a black arrow when trying to load books and following this finally fixed it. Great write-up and instructions, thanks for the hard work.
I've been trying to restore my NOOK for about 2 weeks and this post has gotten me the farthest but i'm stuck at the point where my nook will start up, the "Read Forever" splash screen will come up and then it attempts to recover the system since i see an greenish Android screen come up for a second and then i get an error screen saying "Install Failed" with an image of a nook with an exclamation point in it's screen. I'm assuming i've really messed the nook up but here is where I am.
I've reformatted the partitions using your 1-4,5,6,7,8 zip
Rebooted to recovery
Formatted partiions 5,6,7,8 with your zip
Flashed your 1.4.3 stock rom
At this point I can't get any further since it appears something else is wrong and i didn't want to attempt the reformatting of partition 2 without asking if there is anything else i should try. Any help would be appreciated.
Thanks
jmiklus01 said:
I've been trying to restore my NOOK for about 2 weeks and this post has gotten me the farthest but i'm stuck at the point where my nook will start up, the "Read Forever" splash screen will come up and then it attempts to recover the system since i see an greenish Android screen come up for a second and then i get an error screen saying "Install Failed" with an image of a nook with an exclamation point in it's screen. I'm assuming i've really messed the nook up but here is where I am.
I've reformatted the partitions using your 1-4,5,6,7,8 zip
Rebooted to recovery
Formatted partiions 5,6,7,8 with your zip
Flashed your 1.4.3 stock rom
At this point I can't get any further since it appears something else is wrong and i didn't want to attempt the reformatting of partition 2 without asking if there is anything else i should try. Any help would be appreciated.
Thanks
Click to expand...
Click to collapse
Do the partition 2 repair. That is what is messed up and causing the reboot.
Sent from my Nook HD+ using Tapatalk
leapinlar said:
Do the partition 2 repair. That is what is messed up and causing the reboot.
Sent from my Nook HD+ using Tapatalk
Click to expand...
Click to collapse
I've tried the partition2 zip and received an error trying to mount the factory partition. Status 7 was the error code. Is there a way to fix this?
jmiklus01 said:
I've tried the partition2 zip and received an error trying to mount the factory partition. Status 7 was the error code. Is there a way to fix this?
Click to expand...
Click to collapse
Oh, that is really bad news. That means your partition 3 is corrupted and there is no way to retrieve your device info, like serial number, etc. PM me and maybe I can help you get it partly working, but much of the device info is lost if that partition is truly corrupted.
Sent from my BNTV600 using Tapatalk
Restore NC back to stock
View attachment 1500490
leapinlar said:
Oh, that is really bad news. That means your partition 3 is corrupted and there is no way to retrieve your device info, like serial number, etc. PM me and maybe I can help you get it partly working, but much of the device info is lost if that partition is truly corrupted.
Sent from my BNTV600 using Tapatalk
Click to expand...
Click to collapse
I've been trying to restore my daughter NC back to stock for couple months now and no success.
I did flash the P 1-4-5-6-7-8.zip and got this message after reboot:
"CWM-based Recovery v5.5.0.4
E: Can't mount /cache/recovery/command
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
during the reboot, there is a menu option to hit "n" for reboot mode option. when i hit "n" it gives me (attachment).
but it won't let me move up or down to select except for the 1st option
Help would be very appreciated
big64dave said:
View attachment 1500490
I've been trying to restore my daughter NC back to stock for couple months now and no success.
I did flash the P 1-4-5-6-7-8.zip and got this message after reboot:
"CWM-based Recovery v5.5.0.4
E: Can't mount /cache/recovery/command
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
during the reboot, there is a menu option to hit "n" for reboot mode option. when i hit "n" it gives me (attachment).
but it won't let me move up or down to select except for the 1st option
Help would be very appreciated
Click to expand...
Click to collapse
During reboot it should automatically go to CWM because everything else is wiped. The boot menu only lets you make the first choice because that is all that is there, everything else is wiped. You need to continue to use the CWM to flash the format zip next. Then you can flash a ROM. If the CWM that pops up is not working, use the bootable CWM SD.
leapinlar said:
During reboot it should automatically go to CWM because everything else is wiped. The boot menu only lets you make the first choice because that is all that is there, everything else is wiped. You need to continue to use the CWM to flash the format zip next. Then you can flash a ROM. If the CWM that pops up is not working, use the bootable CWM SD.
Click to expand...
Click to collapse
Thx for replied, the Nook just stock on loading and it won't let me do anything except for power up and down
Related
I have been playing with HC, CM7 etc on my Nook color and decided to go back to running auto-nooker on top of stock, but I want to keep the SD CWR image I made, which has a lot of free space for me to play with future ROM. Has someone packed an CWR zip for auto-nooker?
Thanks.
mathfeel said:
I have been playing with HC, CM7 etc on my Nook color and decided to go back to running auto-nooker on top of stock, but I want to keep the SD CWR image I made, which has a lot of free space for me to play with future ROM. Has someone packed an CWR zip for auto-nooker?
Thanks.
Click to expand...
Click to collapse
BOOM Wining.
http://forum.xda-developers.com/showthread.php?t=932145
therealguppy said:
BOOM Wining.
Click to expand...
Click to collapse
LOL. Thanks.
My current ROM is phiremod nook V4.1. After flashing this and reboot. The Nook U picture flashes, then it's flashing "A N D R O I D _" prompt at the lower left and nothing...
There are three of us currently stuck on that damned android_ screen right now. As I posted in the other one if you get out of this please post your steps!
I reflashed phiremod nook V4.1. That boots pass ANDROID_.
Hmm maybe this is due to CM7 using EXT4 and stock using EXT3,
after flashing the Stock restore also try flash the Restore Boot Partition..
http://forum.xda-developers.com/showthread.php?t=914690
At the bottom of the first post on this one you can find the Restore Boot. which restores Stock B&N boot.
I already did that. Right now as I turn it on, it displays the "Touch the Future of Reading" line instead of the "Loading..." line from CWR. Or do you think this is not sufficient?
There is message when installing repartition-boot-with-stock.zip:
"This will install stock boot 1.0.1 Eclaire --- This won't boot with Froyo!"
Can this the issue too?
EDIT: During the 5 minutes delay b/t post, I installed repartition-boot-with-stock.zip and Nook Color-v1.1.0-r2.zip, now it boots and stucked at the Nook icon with the "Contain Reader Mobile by Adobe" line.
Okay, so I restore stock image, albeit 1.0.1 using images form this page:
http://forum.xda-developers.com/showthread.php?t=919353
Steps:
1. download/extract boot.img and system.img to bootable sdcard (with CWRv3.0.0.6)
2. boot using sdcard, mount /sdcards
3. use adb to dd the image as described in article.
4. repeat failed boot to force recovery.
I thought this would restore /system and /boot ext3 again, but it doesn't...still getting stuck at "ANDROID_" prompt after reflashing the Nook Color v1.1 above. I am going back to CM7...sigh...
EDIT: Actually, it DID work! My problem was when I reflashed Nook Color v1.1-r2.zip, I wiped system and data, which I shouldn't have.
therealguppy said:
Hmm maybe this is due to CM7 using EXT4 and stock using EXT3,
after flashing the Stock restore also try flash the Restore Boot Partition..
http://forum.xda-developers.com/showthread.php?t=914690
At the bottom of the first post on this one you can find the Restore Boot. which restores Stock B&N boot.
Click to expand...
Click to collapse
FYI I've been in the same boat as you a couple of times now with my Nook not wanting to boot. And it seems it gets to different points each time before locking up and not booting. I'm starting to think the same thing as your comments here. This whole ext4 stuff is what seems to be causing issues for a lot of folks specially when wanting to go back to a different ROM or stock. To further compound it is the fact the newest CWR is 3.0.1.0 and all bootable sdcard files are still 3.0.0.6 or 3.0.0.5. With that said I can tell you making a backup using the 3.0.1.0 CWR that is on the internal mem and then getting stuck booting is no good. Reason being from wha tI've found so far is if you take your 3.0.1.0 backup and put it on a bootable sdcard that has 3.0.0.6 so you can restore, it does not work right from what I've found. The only way I've found to fix it easily so far is to first flash the " Remove CWR * .zip from the link posted here. After that then flash the repartition-boot-with-stock.zip file. Once I've flash those 2 files I'm able to flash a new ROM and have it boot like it should.
Another way I've got around it was to power the device on into recovery with no sdcard in the device. Once it booted into recovery ( ie CWR 3.0.1.0 ) I put the sdcard in the device that had my 3.0.1.0 CWR backup. I restored that backup using the actual 3.0.1.0 recovery from internal mem. Once finished tried to boot and it got stuck. When it did I then powered it down and fire it back up but this time booting to the sdcard and then I flashed the repartition-boot-with-stock.zip and it would finally boot up like it should.
Bottom line IMO at least is it seems to be hit or miss on what is the best way to get it back up and running after the boot partition gets hosed. And that can make it a bit frustrating.
Sorry I don't have time to read all of this. Just keep in mind that > 3.0.0.6 formats to ext4 (ie CM). For stock and froyo, use 3.0.0.5 to format to ext2 and 3..
System, data and cache need formatting before flashing a new rom.
Repartitioning boot is only useful if your NC doesn't boot.
Sent from my HTC Desire using XDA App
thought 3.0.1.0 was supposed to work for everything.
Ok, backstory, picked up this Nook Color on craigslist, came with Honeycomb v4 on microSD, booted fine into that, but without uSD would boot to 'n' screen and freeze/stall. Got another uSD formatted with CWM Recovery and the clean original nook image to try and load that from scratch. While following the instructions to restore the original image I would get errors while trying to format system and data (something to the effect of Error cannot format system/!). So I tried to install both CWM to the internal and CM7 to the internal and both would say install complete from microSD, but when booting without the uSD, it would still try to boot into the original nook software and hand on the 'n'.
I tried this to see if my partitions were messed up, but I had the same partition structure and size as it should be (according to the post):
http://forum.xda-developers.com/showthread.php?p=13003431#post13003431
Possibly because I ran this "repartition-boot-with-stock" from this post:
http://forum.xda-developers.com/showthread.php?t=914690
Please help, would prefer to run this off the internal!
Got CM7 running off yet another microSD with this thread:
http://forum.xda-developers.com/showthread.php?t=1000957
Assuming the partition table is in tact then try formatting /system /data /cache in Clockworkmod.
If that doesn't work if might be time to entertain the possibility that you were sold a Nook with a bad emmc.
Sent from my NookColor using XDA App
When I try to format /system /data /cache in CWM, I get an error message. What is the function of the emmc?
mattdogg02 said:
When I try to format /system /data /cache in CWM, I get an error message. What is the function of the emmc?
Click to expand...
Click to collapse
Putting it in PC terms, the emmc functions as the ROM for the bios, and as the solid state drive for whatever you're running on internal memory.
(What is the term for the tablet/smartphone equivalent of the "bios"?)
akaCat said:
(What is the term for the tablet/smartphone equivalent of the "bios"?)
Click to expand...
Click to collapse
Bootloader.
As to the OP - It's still possible your internal flash is bad but the fact that you can list your partition table gives me hope that isn't the case.
I read through JoJa15's post you linked in "Dummies Guide to Fixing 'My Nook Won't Boot'" - It sounds like you listed your partition table per his post and found that it matched what he posted but didn't modify anything right?
The fact that your partition table appears to be in tact is good but the contents of those partitions could be complete gibberish which may explain why CWM errors out when trying to format them. What is the exact error CWM is giving?
I think the next "safe" step is to have a look at DeanGibson's post here: http://forum.xda-developers.com/showthread.php?t=1094371
Dean's CWM scripts will essentially blow away partitions 6-8 (/data / cache and /emmc) and re-create them. If your problem happens to be in one of those partitions then his tool may be a quick fix without having to play with fdisk. That said, I doubt it will work since you can't format /system (partition 5) and his tool doesn't touch the /system partition.
At that point you are pretty much left playing with fdisk, unless you can sweet talk DeanGibson into putting together a CWM flash that will re-do partitions 4 and 5 (extended partition and /system partition) which he may do.
From there it boils down to how comfortable you are with the Linux commands dd and fdisk...?
Good Luck,
Martian21
Ok, followed Dean's instructions with the packages from his post, but still no go.
The error I'm getting when going to Mounts and Storage Menu and running the format /system /data /cache options are:
ClockworkMod Recovery v3.0.2.8
Formatting /system...
Error formatting /system!
Formatting /data...
Error formatting /data!
Formatting /cache...
Error formatting /cache!
Really want to try and get this resolved as I want to install stuff onto the internal!
No one with any other advice on this?
mattdogg02 said:
No one with any other advice on this?
Click to expand...
Click to collapse
Your previous post showed that you were using clockworkmod recovery v3.0.2.8, that version does not have support for the “blue dot” NC. Not knowing for sure if your NC is really a “blue dot” or an original one, I would follow these steps.
1. Create a bootable CWM v3.2.0.1 SD card using the image located HERE. The instructions for it are located HERE. I know the post says v3.0.2.1, but it is miss-marked.
2. Once the card is made, download the repartitioning files located HERE, and the stock 1.2 image file “update-nc-stock-1.2-signed.zip” located HERE.
3. Put all those zip files onto the SD Card
4. Shut down the NC
5. Insert and start the bootable SD card
6. Follow the directions to flash the repartitioning files
7. Once that completes, flash the stock 1.2 image
8. When that is done, remove the SD card, and reboot the device
Hopefully at this point, you will be booting into a stock 1.2.0 system. You can now do whatever you want with the device.
Hi all,
My Nook seems to have broken over night, more than likely the trim command was fired and broken my partition table.
I would return the item, but the Cyanogen Boot logo still appears. Is there anyway to remove it based on the nooks current bricked status?
smurfster said:
Hi all,
My Nook seems to have broken over night, more than likely the trim command was fired and broken my partition table.
I would return the item, but the Cyanogen Boot logo still appears. Is there anyway to remove it based on the nooks current bricked status?
Click to expand...
Click to collapse
If it shows that logo, it is not likely bricked by the trim command. Try making a bootable CWM per my HD/HD+ CWM thread and try flashing a plain stock zip from item 6.
Sent from my BN NookHD+ using XDA Premium HD app
leapinlar said:
If it shows that logo, it is not likely bricked by the trim command. Try making a bootable CWM per my HD/HD+ CWM thread and try flashing a plain stock zip from item 6.
Sent from my BN NookHD+ using XDA Premium HD app
Click to expand...
Click to collapse
Thanks for the reply,
Ive now tried different SD cards and both ways of creating a bootable sd card. but nothing works. I cant get past the cyanogen boot screen.
The TWRP image did boot but didnt get passed the splashscreen.
Any advice?
smurfster said:
Thanks for the reply,
Ive now tried different SD cards and both ways of creating a bootable sd card. but nothing works. I cant get past the cyanogen boot screen.
The TWRP image did boot but didnt get passed the splashscreen.
Any advice?
Click to expand...
Click to collapse
I have this EXACT same problem, I would love to find a way to get the cyanoboot splash screen to go away so I can get it exchanged for a new one.
Both of you only have two choices.
If you left stock recovery on internal before it screwed up, you can do the 8 failed boot procedure and it will reset itself to stock.
If you replaced stock recovery with CWM or TWRP, you must boot to it or a bootable CWM SD so you can flash the plain stock zip I have in item 6 in my HD/HD+ CWM thread linked in my signature. To get to your custom recovery on internal, power up from the powered off condition and hold both the power and n button simultaneously for 5-8 seconds. Then first release power and then a couple of seconds later the n key. It should show the cyanoboot logo followed by the recovery.
If you cannot do any of those things, you are screwed.
Sent from my BN NookHD+ using XDA Premium HD app
leapinlar said:
Both of you only have two choices.
If you left stock recovery on internal before it screwed up, you can do the 8 failed boot procedure and it will reset itself to stock.
If you replaced stock recovery with CWM or TWRP, you must boot to it or a bootable CWM SD so you can flash the plain stock zip I have in item 6 in my HD/HD+ CWM thread linked in my signature. To get to your custom recovery on internal, power up from the powered off condition and hold both the power and n button simultaneously for 5-8 seconds. Then first release power and then a couple of seconds later the n key. It should show the cyanoboot logo followed by the recovery.
If you cannot do any of those things, you are screwed.
Sent from my BN NookHD+ using XDA Premium HD app
Click to expand...
Click to collapse
Looks like im screwed. It is strange though how the TWRP bootable image actually attempts to boot?
UPDATE: http://forum.xda-developers.com/showpost.php?p=44797803&postcount=73
I tried this and have managed to boot into cwm.
I then noticed a error that kept repeating. E:unknown volume for path [/cache/recovery/command]
So I then did the following
1. wipe data/factory reset
2. wipe cache partition
3. mounts and storage > format /boot
4. mounts and storage > format /system
5. mounts and storage > format /data
6. mounts and storage > format /emmc
7. mounts and storage > format /data and /data/media (/sdcard)
Alot of this did cause mounting problems. but I did notice I could mount /boot and browse sdcard from the "install zip" option. The only problem is the partion in the SD i can see isnt the partition that CWM can see.
I'm going to try and sideload the stock recovery using adb when I get in from work as I dont have the usb cable on me.
If you made a backup of stock prior to loading another ROM, you may have better luck restoring it than flashing the stock zip. That has been my experience. In addition to doing the restore, you may need to flash the stock recovery zip.
Sent from HD+ MAG2GA CM 10.2 from SD
Well I couldnt get ADB to work with my tablet. So I couldnt sideload the stock emmc. So I then used "Paragon ExtFS for Windows" to copy the files to the other correct ext3 partition on the MicroSD.. I then booted into recovery and attempted to flash the zip. It didnt work, I recieved a error stating
E: unknown volume for path [/cache/recovery/last_log]
E: cant mount /cache/recovery/last_log
Looks like the nooks dead.
I got nook hd+ and used cm version 10.2 something for a while.
The device keeps crashing and restarting like crazy.
1 out of 10 times, it launches, but before I do anything, it crashes. Hell.
It has been crashing and restarting quite often these days, but since last night, all it does is crashing and restarting.
To make matters worse, I tried to format the device and install cm again. It did not work.
I made booting SD card and chose 'wipe data/ factory reset'. And nook said it wiped /data /cache data wipe complete etc. However, files were still there in internal storage.
On top of that, I had to try 4 times to install newest cm-11. It aborted.
Next, I tried to installnookjdplus factory2.2.0 . It had error. (status 6) to ne specific.
So, I tried newest cwm recovery. It installed, but nook still crashed.
I persevered and tried to install cm 11. It installed, but still crash and restart.
Hell. I literally spent whole day doing this. I am confused and frustrated and angry and experiencing a few other negative emotions English language dows not have in words.
Please, some advice.
Venrun said:
I got nook hd+ and used cm version 10.2 something for a while.
The device keeps crashing and restarting like crazy.
1 out of 10 times, it launches, but before I do anything, it crashes. Hell.
It has been crashing and restarting quite often these days, but since last night, all it does is crashing and restarting.
To make matters worse, I tried to format the device and install cm again. It did not work.
I made booting SD card and chose 'wipe data/ factory reset'. And nook said it wiped /data /cache data wipe complete etc. However, files were still there in internal storage.
On top of that, I had to try 4 times to install newest cm-11. It aborted.
Next, I tried to installnookjdplus factory2.2.0 . It had error. (status 6) to ne specific.
So, I tried newest cwm recovery. It installed, but nook still crashed.
I persevered and tried to install cm 11. It installed, but still crash and restart.
Hell. I literally spent whole day doing this. I am confused and frustrated and angry and experiencing a few other negative emotions English language dows not have in words.
Please, some advice.
Click to expand...
Click to collapse
CM10.x, CM11, and stock ROM need different versions of CWM recovery.
See http://forum.xda-developers.com/showthread.php?t=2679899 for info/pointers on flashing CM11.
To go back to stock ROM, see http://forum.xda-developers.com/showthread.php?t=2062613(item #6).
When switching between CM10, CM11, and stock ROM, you need to do "wipe /data & factory reset".
If none of the above helps the your problem might be due to an unruly app or hardware related.
digixmax said:
CM10.x, CM11, and stock ROM need different versions of CWM recovery.
See http://forum.xda-developers.com/showthread.php?t=2679899 for info/pointers on flashing CM11.
To go back to stock ROM, see http://forum.xda-developers.com/showthread.php?t=2062613(item #6).
When switching between CM10, CM11, and stock ROM, you need to do "wipe /data & factory reset".
If none of the above helps the your problem might be due to an unruly app or hardware related.
Click to expand...
Click to collapse
Ok. At least I got my biggest problem now.
I think my roblem is wipe data/factory reset does not do job it is supposed to do.
I still see folders and files in internal memory after factory reset. I think that is why install aborts and crashes even after successful install.
I think my problem is that wipe data/factory reset does not do its job
It gives me message it is formatting data cache and stuff. And last day they gave me data wipe complete. But the problem is, in internal memory, I can still see old folders and old files.
I think he should be gone if it is formatted. Where do I get the meaning of factory reset wrong?
Its not what is wrong with me. And how can I make factory reset work
And second question is that I tried to install B&N original operating system from cwm-based recovery. I tried a few different versions of
nookHDplus-factory-2.1.1-plain-stock.zip
However it always fail to install. Install aborted for some reason.
Thanks. It seem helpful.
digixmax said:
CM10.x, CM11, and stock ROM need different versions of CWM recovery.
See http://forum.xda-developers.com/showthread.php?t=2679899 for info/pointers on flashing CM11.
To go back to stock ROM, see http://forum.xda-developers.com/showthread.php?t=2062613(item #6).
When switching between CM10, CM11, and stock ROM, you need to do "wipe /data & factory reset".
If none of the above helps the your problem might be due to an unruly app or hardware related.
Click to expand...
Click to collapse
Thanks a lot for your advice
Going back to stock Rom 6 explains error message and aborting of install.
However the problem is where do I get CWM V 60036 or eariler?
Googling does not work.9
Venrun said:
Thanks a lot for your advice
Going back to stock Rom 6 explains error message and aborting of install.
However the problem is where do I get CWM V 60036 or eariler?
Googling does not work.9
Click to expand...
Click to collapse
You can get v6036 on that same thread digimax referenced above (my CWM thread linked in my signature). And a data wipe does not wipe your media files. To do that, go to mounts and storage and select wipe "data and datamedia".
Sent from my SM-T707V using XDA Premium HD app
thanks
leapinlar said:
You can get v6036 on that same thread digimax referenced above (my CWM thread linked in my signature). And a data wipe does not wipe your media files. To do that, go to mounts and storage and select wipe "data and datamedia".
Sent from my SM-T707V using XDA Premium HD app
Click to expand...
Click to collapse
trying it. hope it works.
did not work
for about deleting internal data, I went to 'mounts and storage'. used 'format /sdcard' and 'format/ data and/ data/media (/sdcard), but still has stuff in internal memory.
and to my surprise , I have been using CWM-6028. so far. I thought its name was 'NookHDplus-bootable'.
hell. stupid me.
Anyhow, CWM-6028 has been giving me troule
so, I would try other versions.
So far, I have done
1. made boot sd by burning image.
2. copy 'NookHDplus-factory-2.1.0-plain-stock' files and other versions.
3. Insert SD in device and boot CWM.
4. choose zip from sdcard.
5. install factory plain stock.
then I get message 'Failed to retouch 'system/lib/libemoji.so' (WTF is libemoji? and it is always this same file.)
E: error in sdard/nookHDplus-factort-2.2.1-plain-stock.zip(status7)
Installation aborted.
hell. And I tried every factory zip.
Am I doing something wrong?
Failed tp retouch '/system/lib/libemoji' is error message I get
Everytime I tried to install factory stock.
I tried every version of stock files. And I tried all CWM. And even tried TWRP, but it is always the same message what the hell is that emoji?
And what can I do with it?
What frustrates me the most is the fact that it installed 99% in a minute without trouble and stays there 410 minutes until it fails to install. It's driving me crazy
Does CM makes Factory reset by power button and home button does not work either.
Because I am getting message factory reset failed.
If CM is not the reason for it, well, something is wrong. Very wrong.
I am suspecting Internal memory corrupted lr something.
I should seriously consider throwing it away now.
Venrun said:
Because I am getting message factory reset failed.
If CM is not the reason for it, well, something is wrong. Very wrong.
I am suspecting Internal memory corrupted lr something.
I should seriously consider throwing it away now.
Click to expand...
Click to collapse
It is possible you have a bricked emmc. When bricked it looks like it is writing but is really read only and nothing takes. If you still have media files after a successful format data and datamedia then it is bricked. Probably best to get rid of it. You can buy a refurbished unit very cheaply these days.
Sent from my SM-T707V using XDA Premium HD app
Venrun said:
Because I am getting message factory reset failed.
If CM is not the reason for it, well, something is wrong. Very wrong.
I am suspecting Internal memory corrupted lr something.
I should seriously consider throwing it away now.
Click to expand...
Click to collapse
Assuming that your EMMC is shot, you can try running off SD card this no-emmc version of CM11 ROM: https://iamafanof.wordpress.com/201...-4-4-4-for-bricked-no-emmc-nook-hd-04nov2014/. It's best to use a card with fast randomized block read/write (which is what Class 4 cards are typically best at).
Thanks guys. By the way, what is emmc?
Is it part of CM software?
Does not sounds like hardware.
If I had factory resetted a day earlier, I would not have had problems.
Well. That is the way it is.
I finally kind of got nook working. I am running it on SD card now.
I got to thank you guys for your good advices.
Problem is that this ecmm free booting shrinks storage space.
No matter what is size of SD card, Internal storage is 900mb and SD card got 100mb. (I mean virtual Internal storage the file made in SD card) Not enough space to hold a movie.
I am happier to have tab working, but also wish to use full space of my SD.
At least I wish I can have a few Gs of storage.
Venrun said:
I got to thank you guys for your good advices.
Problem is that this ecmm free booting shrinks storage space.
No matter what is size of SD card, Internal storage is 900mb and SD card got 100mb. (I mean virtual Internal storage the file made in SD card) Not enough space to hold a movie.
I am happier to have tab working, but also wish to use full space of my SD.
At least I wish I can have a few Gs of storage.
Click to expand...
Click to collapse
Right after burning the ROM image to SDcard, it should be possible to use a disk partitioning tool such as MiniTool Partition Wizard to examine the SDcard ROM image's partitions and resize the /data partition to fill up the un-allocated space.
digixmax said:
Right after burning the ROM image to SDcard, it should be possible to use a disk partitioning tool such as MiniTool Partition Wizard to examine the SDcard ROM image's partitions and resize the /data partition to fill up the un-allocated space.
Click to expand...
Click to collapse
Thanks a lot. That sounds I can do it.
how you did it
Venrun said:
I got to thank you guys for your good advices.
Problem is that this ecmm free booting shrinks storage space.
No matter what is size of SD card, Internal storage is 900mb and SD card got 100mb. (I mean virtual Internal storage the file made in SD card) Not enough space to hold a movie.
I am happier to have tab working, but also wish to use full space of my SD.
At least I wish I can have a few Gs of storage.
Click to expand...
Click to collapse
Please tell how you made SD card work.
thanks.
rkgarg2000 said:
Please tell how you made SD card work.
thanks.
Click to expand...
Click to collapse
See http://forum.xda-developers.com/showpost.php?p=49007593&postcount=84 for some pointers on how to create a CM SD card with customized partition sizing for HD+. Although it was written for CM11, you should be able to adapt it for CM10.2 by using the appropriate ROM and GApps zip files corresponding to CM10.2.
Please confirm if my problem has any other solution
my NOOK HD+ I have CMW 10.2.1 with 6.0.4.6 recovery. Nook went to loop while booting. Now I can go to recovery and able to boot SD recovery CMW 6.0.2.8. But issue is:-
1. For any update even for Stock ROM it gives status 7 error.
2. With system recovery 6.0.4.6 when I try factory reset the TAB reboot same happen when i try to format DATA. While factory reset and DATA format happens with 6.0.2.8 position remains same.
3. When I try to make backup on internal storage both with 6.0.4.6 (TAB recovery) or 6.0.2.8 (From SD card) it makes boot,recovery and system image but give error as failed to backup /DATA.
4. I have done every thing right from various and latest ROM's ( error Status 7), Formatting boot,system but 6.0.4.6 on NOOK is intact and is in loop.
Please tell How I can over come this STATUS 7 error or DATA backup error.
thanks.
digixmax said:
See http://forum.xda-developers.com/showpost.php?p=49007593&postcount=84 for some pointers on how to create a CM SD card with customized partition sizing for HD+. Although it was written for CM11, you should be able to adapt it for CM10.2 by using the appropriate ROM and GApps zip files corresponding to CM10.2.
Click to expand...
Click to collapse
rkgarg2000 said:
my NOOK HD+ I have CMW 10.2.1 with 6.0.4.6 recovery. Nook went to loop while booting.
Click to expand...
Click to collapse
Does it boot-loop to recovery?
If so, see http://forum.xda-developers.com/showpost.php?p=55582281&postcount=1459 for potential causes and solutions.
Now I can go to recovery and able to boot SD recovery CMW 6.0.2.8. But issue is:-
1. For any update even for Stock ROM it gives status 7 error.
2. With system recovery 6.0.4.6 when I try factory reset the TAB reboot same happen when i try to format DATA. While factory reset and DATA format happens with 6.0.2.8 position remains same.
3. When I try to make backup on internal storage both with 6.0.4.6 (TAB recovery) or 6.0.2.8 (From SD card) it makes boot,recovery and system image but give error as failed to backup /DATA.
4. I have done every thing right from various and latest ROM's ( error Status 7), Formatting boot,system but 6.0.4.6 on NOOK is intact and is in loop.
Please tell How I can over come this STATUS 7 error or DATA backup error.
...
Click to expand...
Click to collapse
CWM v6.0.4.6 is not compatible with CM10.x, you need to flash back to the CWM version you previously used.
Hey guys!
I'm have a Nook HD+ running AOSP Nougat from amaces along with TWRP 3.0.2-0 as recovery.
(http://forum.xda-developers.com/nook-hd/development/marshmallow-nook-hd-hd-t3239269)
After a while of use, some apps started to crash as soon as I open them, and more and more apps started crashing over time.
I decided to get into recovery and reflash the ROM, but the recovery got stuck on the first screen, where you can see name and version of the recovery and nothing else (I believe it's called splash screen?). Since then, it always boot into the recovery and stays at the splash screen, whatever I do. Doesn't matter if I boot it normally or boot to recovery or have a bootable micro SD with recovery inserted, it always goes directly into the emmc recovery and gets stuck.
Any idea how I could rescue my tablet? Thank you very much!
N0he said:
Hey guys!
I'm have a Nook HD+ running AOSP Nougat from amaces along with TWRP 3.0.2-0 as recovery.
(http://forum.xda-developers.com/nook-hd/development/marshmallow-nook-hd-hd-t3239269)
After a while of use, some apps started to crash as soon as I open them, and more and more apps started crashing over time.
I decided to get into recovery and reflash the ROM, but the recovery got stuck on the first screen, where you can see name and version of the recovery and nothing else (I believe it's called splash screen?). Since then, it always boot into the recovery and stays at the splash screen, whatever I do. Doesn't matter if I boot it normally or boot to recovery or have a bootable micro SD with recovery inserted, it always goes directly into the emmc recovery and gets stuck.
Any idea how I could rescue my tablet? Thank you very much!
Click to expand...
Click to collapse
+1 on this, I am seeing the exact same behavior. After running a while there seems to start cascading failures of apps. Browser stopped, google play most common, MTP host stops...
TWRP hangs on the splash screen , Ive tried all (3) 3.0.2. variants.... I am running the NDE63P 7.1 build...
in my case, however, if I boot from a card into OLD Cwm, don't do anything, and then reboot from the tablet, I am then able to boot from emmc normally.
N0he said:
After a while of use, some apps started to crash as soon as I open them, and more and more apps started crashing over time.
I decided to get into recovery and reflash the ROM, but the recovery got stuck on the first screen, where you can see name and version of the recovery and nothing else (I believe it's called splash screen?).
Click to expand...
Click to collapse
Sounds like your userdata partitions got corrupted; F2FS? Anyway, you will need to find a way to re-format it manually, preferably ext4 (make_ext4fs /dev/block/bootdevice/by-name/userdata, I think).
N0he said:
Since then, it always boot into the recovery and stays at the splash screen, whatever I do. Doesn't matter if I boot it normally or boot to recovery or have a bootable micro SD with recovery inserted, it always goes directly into the emmc recovery and gets stuck.
Click to expand...
Click to collapse
When recovery cannot mount its partitions (by default, including /data and /cache), it will hang, so you have to either build a TWRP image that doesn't attempt to use /data, or use the old CWM from the external card, which doesn't understand F2FS. The external recoveries should always boot, if nothing else is broken.
mikeataol said:
in my case, however, if I boot from a card into OLD Cwm, don't do anything, and then reboot from the tablet, I am then able to boot from emmc normally.
Click to expand...
Click to collapse
Yes, all these recoveries clear the boot count, but only after they finish booting. When TWRP doesn't finish a full boot, the system is still marked for recovery.
As a side note, I really don't understand why people insist on using (highly) experimental builds without a good understanding of how to rescue from soft-bricks…
amaces said:
Sounds like your userdata partitions got corrupted; F2FS? Anyway, you will need to find a way to re-format it manually, preferably ext4 (make_ext4fs /dev/block/bootdevice/by-name/userdata, I think).
The external recoveries should always boot, if nothing else is broken.
Click to expand...
Click to collapse
The TWRP recoveries on the SD card ddont boot, they hang as well. Only the CWM boots
I was trying to ascertain if the file system was corrupted, or if just TWRP was broken.
The rom boots and runs normally from emmc, no signs anywhere that there is corruption, except subtle hints... (change settings on an app, clear data and cache on an app, and on the successful reboot into the rom those changes don't seem to have stuck.
mikeataol said:
The TWRP recoveries on the SD card ddont boot, they hang as well. Only the CWM boots
I was trying to ascertain if the file system was corrupted, or if just TWRP was broken.
Click to expand...
Click to collapse
Right, CWM is one of the recoveries on the SD card. No recovery that supports F2FS and wants to access /data will work at this point; it just happens that CWM can skip that step.
@amaces and as you suggested, booting cwm from the card
reformatting userdata (make_ext4fs /dev/block/platform/omap/omap_hsmmc.1/by-name/userdata )
allowed TWRP to work again just ducky.....
Thank you for taking your time to help me!
amaces said:
When recovery cannot mount its partitions (by default, including /data and /cache), it will hang, so you have to either build a TWRP image that doesn't attempt to use /data, or use the old CWM from the external card, which doesn't understand F2FS. The external recoveries should always boot, if nothing else is broken.
Click to expand...
Click to collapse
In my case, I am unable to boot from the microSD card at all, the device always boots into the emmc recovery no matter what I do.
amaces said:
Sounds like your userdata partitions got corrupted; F2FS?
Click to expand...
Click to collapse
I did not know what F2FS is, but from googling, I assume it is something the user would have to manually set, which did not happen in my case.
amaces said:
Anyway, you will need to find a way to re-format it manually, preferably ext4 (make_ext4fs /dev/block/bootdevice/by-name/userdata, I think).
Click to expand...
Click to collapse
Is it possible to do so without access to recovery? Can you give me some directions to where I can get the info to be able to do so? Any good posts on that, or any keyword I could research around? Would fastboot work? I'm not too sure where to start.
amaces said:
As a side note, I really don't understand why people insist on using (highly) experimental builds without a good understanding of how to rescue from soft-bricks…
Click to expand...
Click to collapse
From what I have seen in the forums, I assumed having a "rescue microSD card" would make flashing ROMs fairly save, but I guess I'll stick to stable builds from now on then. But then again, doing stupid stuff does make me learn new things, and I was willing to risk bricking my tablet.
Anyways, thank you for helping me and for all your work to keep the Nooks alive!
N0he said:
In my case, I am unable to boot from the microSD card at all, the device always boots into the emmc recovery no matter what I do.
Click to expand...
Click to collapse
Hi
You should make another card using a different MicroSD. Not all cards work for booting NOOKS.
A class 4 brand name card usually works
the disk image amace has here :https://notredame.app.box.com/s/26a4bygh9vbaw7jjq08xr5evomvaw5ww/1/3332706778/59738502081/1
has a CWM recovery and 2 TWRP recoveries to choose from on boot.
mikeataol said:
Hi
You should make another card using a different MicroSD. Not all cards work for booting NOOKS.
A class 4 brand name card usually works
the disk image amace has here :https://notredame.app.box.com/s/26a4bygh9vbaw7jjq08xr5evomvaw5ww/1/3332706778/59738502081/1
has a CWM recovery and 2 TWRP recoveries to choose from on boot.
Click to expand...
Click to collapse
I am using a card that has worked for me multiple times in the past. This is not the first time I had to reflash my recovery, it's just the first time I cannot get into the external recovery.
N0he said:
I am using a card that has worked for me multiple times in the past. This is not the first time I had to reflash my recovery, it's just the first time I cannot get into the external recovery.
Click to expand...
Click to collapse
Have you checked whether adb is working while you are sitting at the splash screen for TWRP?
If yes, then you can execute the make_ext4fs command
"make_ext4fs /dev/block/platform/omap/omap_hsmmc.1/by-name/userdata"
to format your /userdata partition.
I was able to do this while stuck on a TWRP splash screen
this will reset your file system back to ext4, (and wipe it) . if you are going to reload one of the newer roms , you'd of course want to convert it back to f2fs before installing.
the NBD90Z 161019 build is working very well for me....
N0he said:
I am using a card that has worked for me multiple times in the past. This is not the first time I had to reflash my recovery, it's just the first time I cannot get into the external recovery.
Click to expand...
Click to collapse
So, it never presents the external recovery menu, where you could select CWM before? You might need to format and re-build that SD card if that's the case.
mikeataol said:
Have you checked whether adb is working while you are sitting at the splash screen for TWRP?
If yes, then you can execute the make_ext4fs command
"make_ext4fs /dev/block/platform/omap/omap_hsmmc.1/by-name/userdata"
to format your /userdata partition.
Click to expand...
Click to collapse
Yes, do try this even with the eMMC recovery; ADB should be working, and you might be able format userdata if it was ext4 before. With some F2FS corruption, it's less likely to work, since it'll say /data is in use, and you can't unmount it.
mikeataol said:
if you are going to reload one of the newer roms , you'd of course want to convert it back to f2fs before installing.
Click to expand...
Click to collapse
I think you should stick to ext4 while testing these issues. I did notice more corruption with F2FS on the new kernel, but didn't have time to investigate yet.
My tablet randomly booted into the microSD card overnight while charging for some reason, and since then, I'm able to boot into the card cwm.
Trying to format the device, I get following error: /sbin/sh: make_ext4fs: not found
I looked into /sbin/sh and found mke2fs and mkfs.ext2, how should I proceed?
N0he said:
My tablet randomly booted into the microSD card overnight while charging for some reason, and since then, I'm able to boot into the card cwm.
Trying to format the device, I get following error: /sbin/sh: make_ext4fs: not found
I looked into /sbin/sh and found mke2fs and mkfs.ext2, how should I proceed?
Click to expand...
Click to collapse
I think you should format it mkfs.ext2 then, ....
that should allow you to boot into the internal recovery and then convert it to ext4
Thank you both for taking your time to help me!
I'm going to summarize what I did to get my tablet back to working:
1. Having the tablet shut down because of low battery seems to have been the reason why I could boot from the microSD card again. So what can be done in that situation is to boot into the emmc recovery (which gets stuck at the splash screen) and then just leave it on until it shuts itself off. Then charge it up again and try to boot into the microSD card. Worked for me.
2. To then actually fix the problem, make sure to have CWM on the microSD card. There are at least two ways to get the tablet to work again:
- Boot into CWM, then connect to a pc with adb, reformat with adb shell using "make_ext4fs /dev/block/platform/omap/omap_hsmmc.1/by-name/userdata" (didn't work for me, as it couldn't find make_ext4fs)
- Boot into CWM, install stock recovery, use it to factory reset the tablet, boot into stock ROM once to make sure, boot into CWM, flash all your stuff.