Basically what happens is I turn on my NC and I get the the "Cyanogen" boot screen and it say's "loading" under the logo and it gets completely stuck and won't boot up.
Well, I've tried creating a bootable SD and that does not work for me.
I even tried entering recovery and it get's stuck on the "booting into recovery..."
Someone please help me.
Thanks,
Chandler
Did you format /boot partition?
Yes, I did.
You need to make a bootable cwm sd, boot into CM7 and flash clockworkmod. It happened to me once by mistake and that's what I did to make it work.
What happened to you once by mistake?
I'm having the exact same issue. I copied the image of the installer to the boot sector of the SD card. I then ejected the card, reinserted it and copied over 7.1.
When the card is installed in the Nook, the installer runs successfully. The Nook reboots and the animated Cyanogen logo with the bot and the rotating arrow come up, and stay up. I left it for an hour, and nothing changed. Turned it off and back on several times, no difference.
Az
I formatted the boot partition by mistake and it wouldn't boot. So I made a CWM bootable sd, installed the rom again without deleting anything and went into ROM manager and flahed clockworkmod.
Thanks a lot. It worked perfectly!
Glad I could help.
I wanted to update my sister's Nook HD+ to CM11. I don't have an SD card big enough to do a nandroid backup, so I tried to back up to the internal SD card. It was working fine, then it said "backup of /data failed". I thought this was because the internal SD card ran out of space. When I tried to reboot, it found that it's stuck in a bootloop. It goes to the nook screen, then the Cyanoboot screen, then starts loading Cyanogenmod like normal. The boot animation plays then freezes, and the device reboots. I've tried clearing the cache and dalvik cache and it gets a little farther, but it's still in a bootloop. Please help! I would like to avoid doing a factory reset if at all possible.
If internal space was maxed out, would a factory reset even work any better?
If only booting is corrupted, you should just be able to simply dirty flash the same rom build or newer to fix without losing anything.
I don't know where nandroid backups are made internally but if they are accessible via usb on a pc, then you could just delete those files. If it is indeed full storage. And then dirty flash the build again if needed.
There's probably some other ways to go as well.
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.
Hi at all,
my Nook went out of power during a holiday and when I wanted to start again it stays at the caynoboot screen. I´ve tried to access the recovery to mak e a factory reset but this is also not possible. So I tried to use an image on SD card with CWM and TWRP on to get into recovery but still no success. When trying to Boot to TWRP the screen stay at Teamwin Recovery Project 3.0.1-0.
Any ideas how to get my Nook back to life?
Would be great to get some help.
Regards
Sinner
Chances are your emmc is bricked, in which case you can try running off sdcard the CM11 ROM build specially made for bricked/no-emmc available at https://iamafanof.wordpress.com/201...-4-4-4-for-bricked-no-emmc-nook-hd-04nov2014/.
digixmax said:
Chances are your emmc is bricked, in which case you can try running off sdcard the CM11 ROM build specially made for bricked/no-emmc available at https://iamafanof.wordpress.com/201...-4-4-4-for-bricked-no-emmc-nook-hd-04nov2014/.
Click to expand...
Click to collapse
Hi digixmax,
thank´s for your reply. I´ve tried to follow the instructions on the page you posted but at one point it there is a problem to go on.
I have burned the image to sd and the result is that I have got a boot CD, an ext4 (system) partition and some unallocated space. Theinstalltion guide says that I have to copy the Image (zip file) onto the sd card. So i copied the file to the first and active partition. When I boot up the TWRP I press mount and select boot (changes to blue color). TheI press the home button and the process will lead me back to the menu. After that I select install and navigate to boot but I can not see the zip file to install. I have serched all the other files also but could not find the file.
Any idea?
Regards
Sinner