Related
I updated my phone to Cognition 2.1.2, and think i bricked it. I was on Cognition 2.1.1, i disabled the lag fix as per the instructions, and then installed cognition 2.1.2 with Rom manager. when my phone rebooted it seemed to work fine. Then i realized that there was no calculator app installed anymore. I went into the settings screen, but when i clicked on any of the options it would highlight, but not do anything. I rebooted, but i got stuck on an ATT boot loop.
I then pulled the battery, got into the download mode with the button combo, and did an odin oneclick back to stock. however, when it rebooted it went into the stock recovery console and gave an error message "cant mount \dev\block\ stl11"
After that i tried updating with odin 3 to JH2. Everything went ok, but when it reboots it still goes to recovery, but this time it gives me a differnet error
Code:
format_vfat_device -> argv[4] : android
format_vfat_device -> argv[5] : /dev/block/mmcblk0p1
run_program: child exited with status 1
E: Can't mount /dev/block/mmcblk0p1
(No such File or Directory)
E:copy_dbdata_media:Can't mount SDCARD:copy default media content failed.
I can boot into download and recovery with the button combos
I can use adb when in recovery , I'm not sure what to do though (I can't mount with shell, nor can i get to su
I can't get to ClockWork Mod Recovery as it was'nt the last update.zip, and when i try to reinstall packages it says
Code:
E:can't mount SDCARD:update.zip
Installation aborted.
I'm pretty sure this has to do with the lag fix. I think that odin can't wipe the ext4 partition even though i disabled the lag fix.
Please help, am i completely bricked? If so should i return to att even though its been rooted? I guess i could say it was from the OTA.
I would suggest making sure that you disable the lagfix by
Code:
adb shell
touch /sdcard/voodoo/disable-lagfix
Reboot, and it will probably say "converting back to rsf blah blah blah" It takes like friggin 10 minutes to disable
Then I would try to replace the update.zip with the clockwork recovery update.zip. I uploaded it here: http://dl.dropbox.com/u/115587/update.zip To do this I would use
Code:
adb push [local path to update.zip] /sdcard/update.zip
In my case since I'm using a mac (I put it in my downloads folder) I did
Code:
adb push ~/Downloads/update.zip /sdcard/update.zip
Then try to go into recovery mode and reinstall packages, hopefully clockwork will come up and you can restore a good version of your phone
Hope it helps
Laundry? Do you have insurance on it?
Sent from my 42 node TI 89 cluster
i dont know a whole lot about adb or even know if this is possible, but is there a way to reformat the internal sd card in adb like there is in the stock settings menu? if you reformat that should get rid of all traces of anything including lagfixes correct?
I am unable to use the touch command because it can't mount the Internal SD. it gives me
Code:
touch not found
even when i touch files that i now were there.
I wonder if i could flash the voodoo kernal back on to it if it would take care of it. is there a .tar of it that can be flashed with odin 3?
Is there a way to see what partitions are on the internal sd, and like di11igaf said, is there a way to reformat with adb?
Also i don't think warranty covers putting it through the laundry and w/ insurance it costs like $125 to replace
Wow this one is a bit of a headscratcher.
Have you tried manually flashing in a voodoo compliant kernel just to see if it will boot? It's not mounting the internalSD, which is bizarre, but I do know that stock kernels can't read EXT4 data- now I don't know why your internalSD might get switched over, and I have very little expectation that this will work, but at this point what's the harm?
I thought of manually flashing in a voodoo kernal, but the only ones I can find are update.zip or with clockwork mod methods neither of which i can get to. Is there a voodoo kernal that can be flashed with odin3?
Edit: I just flashed unhelpfuls kernal and i am now getting a different error message
Code:
E:Can't mount /dev/block/stl11
(Invalid argument)
I have flashed a voodoo kernel but it just tries to create the ext4 partition, fails and reboots. The problem is that there is now no /dev/block/mmcblk0p1 or /dev/block/mmcblk0p2. There is still a /dev/block/mmcblk0 but since we both tried to flash stock with Odin we no longer have root to attempt recreating the partitions. We also can't flash anything from recovery since there is no /sdcard.
We need a rooted ROM that is flashable with Odin. The e3 recovery also has an option to reformat the internal sdcard but I've only found it with i9000 ROMS where the captivate power button doesn't work to select it.
Trump211 said:
I thought of manually flashing in a voodoo kernal, but the only ones I can find are update.zip or with clockwork mod methods neither of which i can get to. Is there a voodoo kernal that can be flashed with odin3?
Edit: I just flashed unhelpfuls kernal and i am now getting a different error message
Code:
E:Can't mount /dev/block/stl11
(Invalid argument)
Click to expand...
Click to collapse
This may sound crazy, but do you happen to have the update.zip from ROM Manager on the root of your sdcard? From the sounds of it, once you switch back to the voodoo kernel your phone is able to mount your SD again, now it's just encountering errors on your NAND. If you can get into clockwork recovery go in there and have it format your SDCard, once you've done that, try to flash back with Odin one click and see if everything starts working again.
Zilch25 said:
This may sound crazy, but do you happen to have the update.zip from ROM Manager on the root of your sdcard? From the sounds of it, once you switch back to the voodoo kernel your phone is seeing that, now it's just encountering errors on your NAND. If you can get into clockwork recovery go in there and have it format your SDCard, once you've done that, try to flash back with Odin one click and see if everything starts working again.
Click to expand...
Click to collapse
that wont work, I have been messing with this all morning. The op has a corrupted internal SD card. Nothing will fix this because it wont mount. Its just like any other sd card that gets corrupted.
I even went as fas as flashing eugene's froyo that dont brick from the vibrant forums. thats the only 2.2 rom that will partition the internal sd. but a corrupted sd is a whole other ballgame. Just get another phone.
Devin5277 said:
that wont work, I have been messing with this all morning. The op has a corrupted internal SD card. Nothing will fix this because it wont mount. Its just like any other sd card that gets corrupted.
I even went as fas as flashing eugene's froyo that dont brick from the vibrant forums. thats the only 2.2 rom that will partition the internal sd. but a corrupted sd is a whole other ballgame. Just get another phone.
Click to expand...
Click to collapse
You did catch the part where after flashing the voodoo compliant kernel he's no longer getting the error where he can't mount the internalSD, and is instead getting a message about a partition on the NAND not initiating? The theory here is that perhaps SOMEHOW the internalSD has got some EXT4 data on it that the stock kernel can't understand, so it refuses to mount it, the voodoo enabled kernel DOES understand it, and as such will mount it. The objective is to get that internalSD formatted again so that he can switch back to a stock kernel and have it recognized
I'd also like to add that eugene's kernel also doesn't read ext4 =P Noticing a pattern here?
Another thing that might be worth trying... though doubtful. Do an Odin 1 click, yank the battery as soon as it completes before it gets a chance to boot again. Restart Odin and get your phone back into download mode, and flash in the Voodoo kernel, see what errors it spits out on first boot (if any)
Trump211 said:
I thought of manually flashing in a voodoo kernal, but the only ones I can find are update.zip or with clockwork mod methods neither of which i can get to. Is there a voodoo kernal that can be flashed with odin3?
Edit: I just flashed unhelpfuls kernal and i am now getting a different error message
Code:
E:Can't mount /dev/block/stl11
(Invalid argument)
Click to expand...
Click to collapse
Zilch25 said:
You did catch the part where after flashing the voodoo compliant kernel he's no longer getting the error where he can't mount the internalSD, and is instead getting a message about a partition on the NAND not initiating? The theory here is that perhaps SOMEHOW the internalSD has got some EXT4 data on it that the stock kernel can't understand, so it refuses to mount it, the voodoo enabled kernel DOES understand it, and as such will mount it. The objective is to get that internalSD formatted again so that he can switch back to a stock kernel and have it recognized
I'd also like to add that eugene's kernel also doesn't read ext4 =P Noticing a pattern here?
Click to expand...
Click to collapse
No worries bro, was just trying to help. You probably have more exp when It comes to this, I was just letting the OP know what worked for me in the same situation. Seems like the captivate is a little different beast.
for the record I wasnt talking about flashing another kernal. I was talking about flashing a 2.2 rom ( which thru odin) repartitions the internal sd to stock, which will cut out the ext 4 lag fix issue. It did for me anyway.
With the cant mount issues, I think its currupted. ATT gave my friend another phone with next day shipping. they also said that phones are soft bricking like crazy because of the ota update. so I dont think the OP will have much of a issue saying it was the ota update and getting another phone.
Devin5277 said:
No worries bro, was just trying to help. You probably have more exp when It comes to this, I was just letting the OP know what worked for me in the same situation. Seems like the captivate is a little different beast.
for the record I wasnt talking about flashing another kernal. I was talking about flashing a 2.2 rom ( which thru odin) repartitions the internal sd to stock, which will cut out the ext 4 lag fix issue. It did for me anyway.
With the cant mount issues, I think its currupted. ATT gave my friend another phone with next day shipping. they also said that phones are soft bricking like crazy because of the ota update. so I dont think the OP will have much of a issue saying it was the ota update and getting another phone.
Click to expand...
Click to collapse
Sorry I didn't mean to come off harsh My theory here is that SOMEHOW voodoo is writing EXT4 data to the internalSD outside of the NAND area and in some cases it's corrupting it in such a way that the internalSD cannot be read by the stock kernel (since it has no EXT4 support) so in theory if you can get the internalSD mounted again it can be reformatted to allow a stock kernel to return to use... if this is the case, or at least close enough to what's happening it would fully explain why the froyo kernel with repartition couldn't touch the internalSD (It couldnt mount or read it due to the limitations for file systems in a stock kernel)
Looks like the sdcard on mine has had it. I got root and ffdisk and parted still give I/O errors when trying to read or write to /dev/block/mmcblk0.
kakalaky said:
Looks like the sdcard on mine has had it. I got root and ffdisk and parted still give I/O errors when trying to read or write to /dev/block/mmcblk0.
Click to expand...
Click to collapse
Is this after using a Voodoo kernel? And are you attempting to perform the ffdisk and parted commands while using a voodoo kernel, or stock? I'm just trying to gather as much information as possible on this problem, so forgive all the questions
I'm about to try parted with a voodoo compliant kernal (unhelpful's) But for some reason adb isn't finding my phone when its in recovery. Does this have something to do with the unhelpfuls kernal, or should i just uninstall and reinstall the drivers a few more times?
Trump211 said:
I'm about to try parted with a voodoo compliant kernal (unhelpful's) But for some reason adb isn't finding my phone when its in recovery. Does this have something to do with the unhelpfuls kernal, or should i just uninstall and reinstall the drivers a few more times?
Click to expand...
Click to collapse
Nah, make sure you have the phone plugged in when you turn it on and go into recovery. For some reason plugging it in when it's already in recovery doesn't work. At least it doesn't for me...
Ok, i tried that, but its still not connecting. Tried multiple usb ports, and uninstalled/reinstalled drivers. If i put it in download mode it gets recognized instantly.
Trump211 said:
Ok, i tried that, but its still not connecting. Tried multiple usb ports, and uninstalled/reinstalled drivers. If i put it in download mode it gets recognized instantly.
Click to expand...
Click to collapse
Not sure =/ I had it running last night without too much issue, but I did have to juggle it around a bit before it would find the device. You might want to try doing an adb kill-server before you try to connect in case the system still thinks its running
My nook color recently got stuck on the boot screen for CM7 where the blue android text just chills out in the left corner. This happened right after my nook ran out of battery power.
I have gotten it to boot all the way into CM7 occasionally. However, it is not reliable at all, so I've tried to restore it to stock and reflash the whole thing.
I tried to do this by booting into recovery and then flashing the restore to 1.01 stock zip file, but when the nook rebooted it was still stuck on the android text. I have tried flashing everything related to restoring nooks, but to no avail.
I thought that maybe my CWR was broken, so I tried making a CWR sd card but even when I flashed the restore zip, my nook's boot still gets stuck on the android text.
What do you think I should try to do now?
You are able to boot into cwr though? If so have you tried downloading the stock image file again? Could be the file is corrupt.
I just downloaded it again and it still doesn't work.
I don't think that the problem is the zip files. I think that CWR is the problem since I've tried formatting /system and /data and tried repartitioning boot, but nothing happens...
I just tried to restore my nook to stock through ADB, but it still tried to boot into CM7. I guess that rules out CWR as the problem...
I also made an ext4 compatible CWR SD and tried the restore 1.01 zip again. This time I got past the android text and instead got to the grey android text from the rooted nook boot. However, it just sat there, stuck in a loop.
Odd, that even after wiping system and data that you'd have anything to boot into. You aren't leaving a bootable sd card in place are you?
I make sure to take out the SD card before rebooting.
Is it possible to check to see if CWR/ADB is actually writing to the correct partitions?
EDIT: I do not think that my nook is keeping any changes that I make to it...
I managed to boot into CM7 and I uninstalled a few apps and changed the max clock to 800mhz. Then I rebooted and eventually got back into CM7 and my apps magically came back and my max clock was reset to 1.1ghz.
okay that is very odd. Unfortunately I've never run into this or even read about it before. Hopefully someone here will be able to give you a tip that will help you fix this.
I've been having same issue for a week now. I tried everything I was able to find here but nothing is wokring. It seems like my nook became a read-only device. No matter what I do it goes back to previous stage.
I was running CM7 RC4 and system hung so I rebooted and that was it. It displays "Android_" on the bottm for about 10-15 sec and reboot.
I tried
CWR 3.0.0.5
- Repratition to stock nook.
- Getting error when I try to format system and data - I thought it was because CM7 was setting system to ext4.
- ADB and DD boot.img, System.img and copy Factory to mmcblk0p3
- Try to restore from back up I made
- Nothing works but goes back to boot loop
CWR 3.0.0.6 - One I got from CM7 install to emmc thread
- System format works
- Install latest nightly
- Restore from back up
- ADB can't find device - This is odd and couldn't find a way to fix it yet.
- Tried to install Stock zip but going back to CM7 boot loop
CWR 3.0.1.0
- Can't format data/system
- ADB to delete partitions and create them again but it doesn't help
- Tried all zip files to bring it back to stock - no go
- ADB to copy Factory.zip to emmc partition - umount and mount again then file I copied is gone.
- Deleted partitions and reboot but some how I got back to CM7 loop
I see people start to talking about CM7 boot loop issue. I saw this thread and man this is same issue I'm having! Let me know if you some how resolved this issue. I will do the same if I can find one.
Naw, I haven't resolved it yet...
I will post the solution if I do though!
Perhaps it's just a coincidence, but I am also stuck running RC4. Maybe there's some weird glitch in RC4 that makes the file system read only or something...?
I went from RC4 to stable with no problem. I did notice that CWR was not mounting the system and data partitions so I did have to do that when updating. Not sure why they aren't mounting automatically.
From the Dummies guide link....Here...
First visit this link:
http://forum.xda-developers.com/showthread.php?t=922870
Download either the Rootpack, or the Clockwork Recovery image (1gb).
Next visit this link and download the 1.0.0 or 1.0.1 restore to stock files:
http://forum.xda-developers.com/showthread.php?t=914690
From this link you should also download the very last zip on the page. It is titled-flashable boot repartition zip. or something of the like. If you followed all these steps and still nothing, I would recommend flashing this as it can fix a completely screwed boot partition.
I had to use that last file after my hard crash. Seems that te /boot gets corrupted and tis seemed to fix it for me. After this you will probably need to do a full wipe and reinstall.
My order was...
rebuild /boot
reflash to stock
reflash to CM7
not sure why this worked...just did.
edit: just noticed my H key isn't always working...makes me type like a alf drunk brit..
deadbot1 said:
From the Dummies guide link....Here...
First visit this link:
http://forum.xda-developers.com/showthread.php?t=922870
Download either the Rootpack, or the Clockwork Recovery image (1gb).
Next visit this link and download the 1.0.0 or 1.0.1 restore to stock files:
http://forum.xda-developers.com/showthread.php?t=914690
From this link you should also download the very last zip on the page. It is titled-flashable boot repartition zip. or something of the like. If you followed all these steps and still nothing, I would recommend flashing this as it can fix a completely screwed boot partition.
I had to use that last file after my hard crash. Seems that te /boot gets corrupted and tis seemed to fix it for me. After this you will probably need to do a full wipe and reinstall.
My order was...
rebuild /boot
reflash to stock
reflash to CM7
not sure why this worked...just did.
edit: just noticed my H key isn't always working...makes me type like a alf drunk brit..
Click to expand...
Click to collapse
I tried this too but mine didn't come back.
Hmm. dunno. Maybe you can get samuelhalff to chime in...he was helping another guy out with something similar. searc in the threads for his name and your problem...wasn't to long ago.
edit---http://forum.xda-developers.com/showthread.php?t=1022941 this was the thread I was talking about...doesn't appear they came up with a solution.
I tried all the things you suggested guys, but nothing worked...
Although I think I made some kind of progress... I tried to dd stock boot.img and system.img files onto my nook and now CM7 just bootloops instead of hangs!
Hopefully we can get this sorted out soon, or else I may try what one member suggested about microwaving it so that you can get a new one...
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
Hi, so i was trying to install:
http://forum.xda-developers.com/p9/development/rom-ncs-rom-v1-1-08-16-2016-t3440269
I have unlocked bootloader and i have latest TWRP, i have no idea what went wrong but everytime i try to boot now it says encryption was interrupted and can't continue, and everytime i try to flash image or wipe everything it keeps saying unable to mount /data and /storage. I really have no idea what to do, any help would be appreciated, please.
Did you try to go in the recovery and mount the system from there? Or just format the phone and install the rom through sd card
well i tried flash again the ROM and it worked now, but i had to install TWRP revision 3 guess it fixes some encryption stuff?
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.