Related
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.
Hello,
I was wondering if such a thing as described in subject exists.
I am looking for something which wipes everything but the CWM bootloader and the sd card directory.
The option is already there in cwr
Sent from my Sensation using xda premium
Is it cenwesi? I know the wiping section, but for instance there's no option to format or resize the /recovery partition for example.
goenieg said:
Is it cenwesi? I know the wiping section, but for instance there's no option to format or resize the /recovery partition for example.
Click to expand...
Click to collapse
if you format the recovery you would lose CWM. A data wipe should be suffient, if not plug it into a computer and delete everything on the "sdcard"
bdfull3r said:
if you format the recovery you would lose CWM. A data wipe should be suffient, if not plug it into a computer and delete everything on the "sdcard"
Click to expand...
Click to collapse
thanks, I now have 13 Gb available, is the rest taken by the recovery partition? is resizing an option?
(pls forgive me for being ignorant
I think the devs would have to put a wipe script in their ROMs so the user doesn't have to do it manually. At least that's what the devs at my smartphone's forum (Vibrant) do. Albeit, sometimes it is best to do some manual cleaning, and TWICE at it (the system isn't infallible).
CM7/Zeus v7alongside any rom with GB bootloader and CM7 alongside v28a
Hi!This is my"how to" for installing two roms on one OB.
1.We need to partition sdcard
partition #1 : format it to fat(will be used as sdcard)
partition #2 : format it to ext4(will be used as system of zeus and must be at least 320 MB)
partition #3 : format it to ext4(will be used as data of zeus and must be at least 400 MB)
2.Now if u want:
1.Zeus flash this
2.cm7 flash this
(DO NOT FORGET TO PUT YOUR INTERNAL ROM`S KERNEL TO /sdcard/boot/ and name it nandboot.img!)
3.cm7 alongside v28a flash first this, then flash v28a with SFT, then root your v28a and after that put files from this bin.zip to the /system/bin
3.Now if u want to boot:
1.Zeus type in the terminal
Code:
su
bootzeus
2.cm7 type in the terminal
Code:
su
bootcm7
3.v28c ICS
Code:
su
bootsd
4.your nand rom
Code:
su
bootnand
NOTE:If u change your nand rom first install your new rom and after that copy your new rom's boot.img and put it to /sdcard/boot.img and after that rename it to nandboot.img and after all this install this if your sdrom is cm7 and if Zeus this
Now partition table is:
Code:
Zeus/CM7/v28c ICS
system /dev/block/mmcblk1p2
data /dev/block/mmcblk1p3
CM10
system /dev/block/mmcblk0p8
data /dev/block/mmcblk0p9
YouTube
suleymanovemil8 said:
Hi!So is it possible to boot android from sdcard?I think changing root directory to mmcblk1 in the default kernel kommand line could help, have anyone done smthing like this before?
Click to expand...
Click to collapse
Even if it works you'll still be using the same kernel and ramdisk which will only work on ROM very similar to your base.
Sent from my LG-P970
look what i've found http://forum.xda-developers.com/showthread.php?t=1642185
suleymanovemil8 said:
look what i've found http://forum.xda-developers.com/showthread.php?t=1642185
Click to expand...
Click to collapse
I had a look. It looks promising. Its quite a cheap trick and should work on our phone.
I am on my phone now so I can't study what he did in detail and I'm not entirely sure how he handles kernel switching (yet).
It's a good find.
EDIT: Nothing to do with kernel root or command line though.
Sent from my LG-P970
xonar_ said:
I had a look. It looks promising. Its quite a cheap trick and should work on our phone.
I am on my phone now so I can't study what he did in detail and I'm not entirely sure how he handles kernel switching (yet).
It's a good find.
EDIT: Nothing to do with kernel root or command line though.
Sent from my LG-P970
Click to expand...
Click to collapse
I`ve made script for OB and it works
HTML:
cat /sdcard/boot/sdboot.img > /dev/block/mmcblk0p3
echo Rebooting to SD Rom. Please wait...
sleep 3
reboot
return 0
I have repacked zeus rom`s kernel with sd mounts and put the system partition to mmcblk1p1 but it looks like smthing goes wrong(if sdcard is inserted it reboots to recovery in a few seconds but if I remove sd card it stucks at lg logo) and it have created app, data, etc. folders on data (sd) partition
suleymanovemil8 said:
I`ve made script for OB and it works
HTML:
cat /sdcard/boot/sdboot.img > /dev/block/mmcblk0p3
echo Rebooting to SD Rom. Please wait...
sleep 3
reboot
return 0
I have repacked zeus rom`s kernel with sd mounts and put the system partition to mmcblk1p1 but it looks like smthing goes wrong(if sdcard is inserted it reboots to recovery in a few seconds but if I remove sd card it stucks at lg logo) and it have created app, data, etc. folders on data (sd) partition
Click to expand...
Click to collapse
Make so that it only mount the sd partitions if the sd card is present and is made to be bootable.
Reflashing the boot.img isn't a nice way of doing it since bad flash would result in a bootloop. Linux has the ability to reload a kernel without shutting down. I don't know if the kernel that we use can do that maybe it's worth looking into.
Sent from my LG-P970
xonar_ said:
Make so that it only mount the sd partitions if the sd card is present and is made to be bootable.
Reflashing the boot.img isn't a nice way of doing it since bad flash would result in a bootloop. Linux has the ability to reload a kernel without shutting down. I don't know if the kernel that we use can do that maybe it's worth looking into.
Sent from my LG-P970
Click to expand...
Click to collapse
as i said "and it have created app, data, etc. folders on data (sd) partition"
What if i will move /system #2 to /data partition and both of the systems will have data partition on sdcard?
PS. It worked!Now I have data partition on mmcblk1p2
here it is(this is kernel for cm10(26.10.2012))
suleymanovemil8 said:
What if i will move /system #2 to /data partition and both of the systems will have data partition on sdcard?
PS. It worked!Now I have data partition on mmcblk1p2
Click to expand...
Click to collapse
What are you going to do with the GB thats on the phone and not used?
EDIT: its rebooting to recovery because the kernel is set to reboot to recovery when it's 'panicking'.
Sent from my LG-P970
xonar_ said:
What are you going to do with the GB thats on the phone and not used?
Sent from my LG-P970
Click to expand...
Click to collapse
no this kernel boots with normal system and data at sdcard and now i will make kernel with booting from data directory and with data at sdcard)
YES! I have now two roms on one phone!
suleymanovemil8 said:
YES! I have now two roms on one phone!
Click to expand...
Click to collapse
Do a walkthrough for us! :laugh::laugh:
genarinho said:
Do a walkthrough for us! :laugh::laugh:
Click to expand...
Click to collapse
Yes ,pls
sent from my Nokia 1100 with droid 4.0
Just everyone thats reading this know that it still booting from phone and then reading data from sd. (Not true dualboot yet )
@ sulley
Why not use recovery as the phone boot.img and then normal boot then goes of two sd. CWM sources are available and can be modified so that it works as a boot manager. It will then be actual dual boot because from there you can load kernel from either sd or phone (and unload the recovery kernel and with its dying breath start the new kernel ).A project like this will take A LOT of time and will definitely be more than 6 months. Since it would be based on recovery it should be able to make it work for all phones that can use CWM and have similar boot structure. I will help out on a project like this but I can't be that involved with it since my studies will take up most of my time.
As much I understand, bootloader is needed for dualboot and it applies same on Android. So you got access to our bootloader or just directing the boot.img from 1st ROM to 2nd one? Like handshaking?
xonar_ said:
Just everyone thats reading this know that it still booting from phone and then reading data from sd. (Not true dualboot yet )
@ sulley
Why not use recovery as the phone boot.img and then normal boot then goes of two sd. CWM sources are available and can be modified so that it works as a boot manager. It will then be actual dual boot because from there you can load kernel from either sd or phone (and unload the recovery kernel and with its dying breath start the new kernel ).A project like this will take A LOT of time and will definitely be more than 6 months. Since it would be based on recovery it should be able to make it work for all phones that can use CWM and have similar boot structure. I will help out on a project like this but I can't be that involved with it since my studies will take up most of my time.
Click to expand...
Click to collapse
Well I have installed rom's kernel to the recovery partition but after booting to this new kernel i couldn't boot back tonormal kernel till i reflashed recovery from rom manager
ps.recovery partition is at mmcblk0p4 and boot mcblk0p3
genarinho said:
Do a walkthrough for us! :laugh::laugh:
Click to expand...
Click to collapse
tada!
As I expected, not real dualboot. But very much appreciting try. Keep it up
Anyway i still want to make one rom at nand and anouther on sdcard, but if i set in kernel system directory to mmcblk1p1(sdcard) it starts to boot but smthing goes wrong but it starts to boot and i know it because it creates app, data, app-private etc. folders on data partition of sdcard(mmcblk1p2), i think this is because it remounts sdcard or smthing like this.Any ideas about soving this problem?
I've messed up my nook HD. I formatted the internal partitions with CWM and now I can't boot at all into the stock ROM (shows "Install Failed").
Does someone have a zip to install the 2.0.0 ROM from CWM just like what was posted for the HD+?
Any help would be much appreciated.
houston
houstondallas said:
I've messed up my nook HD. I formatted the internal partitions with CWM and now I can't boot at all into the stock ROM (shows "Install Failed").
Does someone have a zip to install the 2.0.0 ROM from CWM just like what was posted for the HD+?
Any help would be much appreciated.
houston
Click to expand...
Click to collapse
Did you try the 8 failed boot procedure? If you formatted /rom and /factory with CWM, you are in a big hurt. That has vital info it needs to boot.
If you formatted just /rom you are repairable. But it would take some work.
Sent from my Nook HD+ Running CM10 on SD
leapinlar said:
Did you try the 8 failed boot procedure? If you formatted /rom and /factory with CWM, you are in a big hurt. That has vital info it needs to boot.
If you formatted just /rom you are repairable. But it would take some work.
Sent from my Nook HD+ Running CM10 on SD
Click to expand...
Click to collapse
8 failed boot procedure doesn't work. I can boot into CWM and CM10, but not the stock rom. I also noticed that I don't have wireless in CM10 which I imagine has something to do with what I erased.
Is there anyway I can backup /rom and /factory from another Nook HD and write it to the broken one?
houston
houstondallas said:
8 failed boot procedure doesn't work. I can boot into CWM and CM10, but not the stock rom. I also noticed that I don't have wireless in CM10 which I imagine has something to do with what I erased.
Is there anyway I can backup /rom and /factory from another Nook HD and write it to the broken one?
houston
Click to expand...
Click to collapse
No, the info that was there on /rom is device specific. Your serial number, MAC address, etc. But you can boot into CM10? That tells me your /rom partition is ok. It sounds like you messed up the factory partition. That is what holds the factory.zip that stock recovery tries to install and fails on the 8 failed boot. And if that is what it is, you can use someone else's. It is about 350MB though. And you can use the HD cwm to push it to /factory with adb. What was it you formatted, do you remember?
edit: but you cannot flash that to internal memory with that CWM, it is hard coded to flash things to SD. I am working with bokbokan to make a CWM that you can flash to internal.
Edit 2: I just look at the HD+ factory zip. If the HD factory zip is like that, it might be able to be flashed with the current HD CWM.
Sent from my Nook HD+ Running CM10 on SD
leapinlar said:
No, the info that was there on /rom is device specific. Your serial number, MAC address, etc. But you can boot into CM10? That tells me your /rom partition is ok. It sounds like you messed up the factory partition. That is what holds the factory.zip that stock recovery tries to install and fails on the 8 failed boot. And if that is what it is, you can use someone else's. It is about 350MB though. And you can use the HD cwm to push it to /factory with adb. What was it you formatted, do you remember?
edit: but you cannot flash that to internal memory with that CWM, it is hard coded to flash things to SD. I am working with bokbokan to make a CWM that you can flash to internal.
Edit 2: I just look at the HD+ factory zip. If the HD factory zip is like that, it might be able to be flashed with the current HD CWM.
Sent from my Nook HD+ Running CM10 on SD
Click to expand...
Click to collapse
I probably did format the factory partition as I can't see a MAC address in CM10 when trying to connect to WIFI. If I do a Nandroid backup of my working unit and restore it to my non-working unit, can't I go in and edit the MAC address and serial number within the factory partition?
I'm assuming I can't do any of these things yet though until you release a HD compatible CWM?
Thanks for the help btw, you're a lifesaver!
houston
houstondallas said:
I probably did format the factory partition as I can't see a MAC address in CM10 when trying to connect to WIFI. If I do a Nandroid backup of my working unit and restore it to my non-working unit, can't I go in and edit the MAC address and serial number within the factory partition?
I'm assuming I can't do any of these things yet though until you release a HD compatible CWM?
Thanks for the help btw, you're a lifesaver!
houston
Click to expand...
Click to collapse
You can do it when booted to cm10. Look in /rom. There should be a folder named /devconf. It should have a bunch of files, one of them being MACAddress. It should contain 12 bytes, numbers and upper case letters (hex) and no line return. If there are no files there, go to the next step to see if rombackup.zip exists. If it does, it contains a zip backup made of /rom at manufacture.
You can see /factory too, but you have to mount it in terminal emulator first. Open terminal emulator and type su enter. The prompt should change to #. Then type this line:
mount -t ext4 /dev/block/mmcblk0p7 /data/local/tmp
Then you can go to /data/local/tmp and look at the files there. There should be factory.zip, rombackup.zip, romrestore.zip, and fsck.zip. The first two are the most critical.
You can access files there using your root file manager. The file manager that comes with cm10 is root if you change it to root in its settings. If the files are there, back them up to your SD. (Both /rom and /factory which is displayed at /data/local/tmp now).
Sent from my HD+ rooted stock using Tapatalk
leapinlar said:
You can do it when booted to cm10. Look in /rom. There should be a folder named /devconf. It should have a bunch of files, one of them being MACAddress. It should contain 12 bytes, numbers and upper case letters (hex) and no line return. If there are no files there, go to the next step to see if rombackup.zip exists. If it does, it contains a zip backup made of /rom at manufacture.
You can see /factory too, but you have to mount it in terminal emulator first. Open terminal emulator and type su enter. The prompt should change to #. Then type this line:
mount -t ext4 /dev/block/mmcblk0p7 /data/local/tmp
Then you can go to /data/local/tmp and look at the files there. There should be factory.zip, rombackup.zip, romrestore.zip, and fsck.zip. The first two are the most critical.
You can access files there using your root file manager. The file manager that comes with cm10 is root if you change it to root in its settings. If the files are there, back them up to your SD. (Both /rom and /factory which is displayed at /data/local/tmp now).
Click to expand...
Click to collapse
That worked like a charm. Backed up the four files from my working nook and transferred them over to my non-working nook. Nook rom booted up fine and updated to 2.0.5. The only problem I have at the moment is that both units have the same MAC address. How do I edit that? I edited the MACAdress file with the correct mac address, but CM10 isn't picking it up even though I wiped cache and flashed the newest CM10 zip. Any ideas?
Quick Update
Success! Figured out where the MAC address is stored (WiFiBackupCalibration) and HEX edited it to show the correct MAC address.
Thanks again mate!
Is there a way to recover from a /rom format?
my nook hd+ can't boot into both ROM( cm10 and stock rom ).
fireit said:
Is there a way to recover from a /rom format?
my nook hd+ can't boot into both ROM( cm10 and stock rom ).
Click to expand...
Click to collapse
If your factory partition is intact, yes. But you have to boot into CWM and get adb working. Do the same commands it had the prior user do with terminal emulator using adb. There is a backup there you can unzip and restore.
Sent from my HD+ rooted stock using Tapatalk
leapinlar said:
If your factory partition is intact, yes. But you have to boot into CWM and get adb working. Do the same commands it had the prior user do with terminal emulator using adb. There is a backup there you can unzip and restore.
Sent from my HD+ rooted stock using Tapatalk
Click to expand...
Click to collapse
thank you for your reply.
i've been formatted "/ Rom" , "/ factory" by a stupid mistake.
tried to recover partition["/ dev/block/mmcblk0p5", "/ dev/block/mmcblk0p7"] through "adb shell" but had been failed.
fireit said:
thank you for your reply.
i've been formatted "/ Rom" , "/ factory" by a stupid mistake.
tried to recover partition["/ dev/block/mmcblk0p5", "/ dev/block/mmcblk0p7"] through "adb shell" but had been failed.
Click to expand...
Click to collapse
Will you just convinced me to remove those from the CWM. They should never have been there anyway. That is a very costly mistake on your part. Those partitions held vital information on your device like serial number, MAC address, which both can be recovered, but there were some other keys there that you cannot recover. You may be only able to boot from SD from now on. You might want to return it to B&N while it is still under warranty.
Sent from my HD+ rooted stock using Tapatalk
So my Nook HD+ has been running Evergreen's CM 10.1 EMMC fine for a couple weeks. I've had some lag issues so I ran Lagfix and it worked great (though that's another topic). Today, I ran Lagfix again and my HD+ froze. I pressed the power button for 12 seconds to shut it off and it wouldn't boot, just a black screen. Crap.
Ok, no panic. I try pressing the power button for 30 seconds, plug it in, etc. Nothing. Ok, no biggie, going to have to reflash, right? So I download the updated 6/13 Cm10.1 EMMC, copy it over to my CWM SD card, stick it into my HD+ and boot. Boots into CWM no problem. First thing I see is:
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
Click to expand...
Click to collapse
Well I've seen that before, so I don't panic as I seem to recall its not a serious error. So I wipe cache thinking that maybe its corrupted. Not sure if that was smart or stupid but it seems it doesn't matter, because I try and install from SDcard and I get can't mount SDcard. Yikes! I choose install from internal SD and I get can't mount EMMC. Yikes!! I try and restore a backup, there is no backup as sdcard can't mount! Ok so I reboot and try it again a few times, the same error. I try running chkdsk on the SD card on my desktop and it checks out fine, no errors. I tried swapping in another clean and newly formatted fat32 SD card with only CM10.1 on it and it won't mount either.
I try going to advance->boot to recovery and pull out the sdcard. My HD+ boots and then is stuck at the screen where it says "NOOK" in white. Right before recovery should load. Its like recovery is missing or something.
Ok, I'm getting nervous that I have a serious problem. I boot my CWM SD card again and plug the HD+ into my desktop (Windows) and run ADB. I can adb shell, so I try and mount sdcard from the shell. I get
mount: mounting /dev/block/mmcblk1p1 on /sdcard failed: no such file or directory.
Click to expand...
Click to collapse
Ok, lets try sideload: adb sideload cm.zip.
failed to write data 'protocol fault (no status)
Click to expand...
Click to collapse
Ok, I have a trick I did one time before when I had a similar problem. I try and run:
adb shell mount -t tmpfs none /sdcard
This should mount my ram as sdcard and then I can push the rom to ram and flash from there. However, the error I get is like tmpfs doesn't exist. Ok, I am no expert so at this point I am stuck.
I didn't want to wipe anything yet as I don't know what that would do. At this point being able to boot into my CWM SD card is the only thing that works and I don't want to mess with it as I am now out of my knowledge area.
Anyone know what I can do here? I mean I can't restore a backup or flash a new rom. Does the HD+ have a download mode so I can use Odin? Is fastboot an option here? I am a few days behind on my backup but I can live with a factory reset if that is called for, no problem.
I've hit panic time, please help! Thanks!
Isn't lagfix that zip that reformats your partitions? How did you flash that on an HD+?
Sent from my Galaxy Tab 2 using XDA Premium
leapinlar said:
Isn't lagfix that zip that reformats your partitions? How did you flash that on an HD+?
Sent from my Galaxy Tab 2 using XDA Premium
Click to expand...
Click to collapse
I'm glad you saw this, as I could use your Nook guruness right about now. This is it: https://play.google.com/store/apps/details?id=com.grilledmonkeydonate.lagfix&feature=search_result. Its just a GUI for fstrim and it runs it on /data.
Is there a download mode on the Nook by any chance? If I could Odin this rom on there, I think I'd be all set, but I have to say, the fact that CWM SD can't mount or find EMMC has me worried.
silkshadow said:
I'm glad you saw this, as I could use your Nook guruness right about now. This is it: https://play.google.com/store/apps/details?id=com.grilledmonkeydonate.lagfix&feature=search_result. Its just a GUI for fstrim and it runs it on /data.
Is there a download mode on the Nook by any chance? If I could Odin this rom on there, I think I'd be all set, but I have to say, the fact that CWM SD can't mount or find EMMC has me worried.
Click to expand...
Click to collapse
That sounds like a dangerous thing to be playing with. There is not a download mode and Odin is for Samsung devices.
It sounds like you borked your partitions. Did you replace the stock recovery with CWM or TWRP?
Sent from my Nook HD+ running CM10.1 on emmc.
leapinlar said:
That sounds like a dangerous thing to be playing with. There is not a download mode and Odin is for Samsung devices.
It sounds like you borked your partitions. Did you replace the stock recovery with CWM or TWRP?
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
I did initially (like 2 weeks ago) replace the stock recovery with TWRP. I've run TWRP backups a bunch since then. Of course, those are useless with CWM SD, but I have 2 CWM nandroids on my CWM SD (which I can't access since CWM can't mount the SD ). BTW I am using, and used originally, your CWM SD image.
If I screwed up my partitions, is there a fix I can perform from CWM SD or adb?
Edit: BTW, Lagfix also runs fstrim on /cache as well, I had forgotten.
silkshadow said:
I did initially (like 2 weeks ago) replace the stock recovery with TWRP. I've run TWRP backups a bunch since then. Of course, those are useless with CWM SD, but I have 2 CWM nandroids on my CWM SD (which I can;t access since CWM can't mount the SD ). BTW I am using, and used originally, your CWM SD image.
If I screwed up my partitions, is there a fix I can perform from CWM SD?
Click to expand...
Click to collapse
If you had not replaced stock recovery with TWRP you could have done the 8 failed boot reset, but you cannot with TWRP. Also those TWRP backups are worthless because the TWRP emmc backup/restore is broken for the HD+.
You can try to repair the partitions with ADB when booted to CWM. First thing I would try is to DD the boot.img and recovery.img from your CWM backups. Boot.img goes to partition 4 and recovery.img goes to p3.
Sent from my Nook HD+ running CM10.1 on emmc.
leapinlar said:
If you had not replaced stock recovery with TWRP you could have done the 8 failed boot reset, but you cannot with TWRP. Also those TWRP backups are worthless because the TWRP emmc backup/restore is broken for the HD+.
You can try to repair the partitions with ADB when booted to CWM. First thing I would try is to DD the boot.img and recovery.img from your CWM backups. Boot.img goes to partition 4 and recovery.img goes to p3.
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
I've actually been wanting to put CWM instead of TWRP, but I've been nervous about messing with recovery since I had a problem doing that on an old Samsung. Man I wish I had just bit the bullet and re-flashed CWM.
I know how to DD, but repairing the partitions is a step above what I've done before. Is there a tutorial on how to do this? Thanks!
Edit: Wait maybe I don't know how to DD. cat proc/mtd gives an error. How do I identify what to backup?
Edit2: Nevermind, I knew I saw it somewhere and there it is in your tips thread. Sorry, my bad. I'll report back after I have done it.
Ok, I'm stuck, sorry. How do I get the boot.img from my PC to my Nook? CWM won't mount SDcard. Can I just push the file to /data and then restore it from there?
Edit: Fastboot doesn't seem to work in CWM recovery?
silkshadow said:
Ok, I'm stuck, sorry. How do I get the boot.img from my PC to my Nook? CWM won't mount SDcard. Can I just push the file to /data and then restore it from there?
Click to expand...
Click to collapse
Maybe, if your /data is still ok.
Sent from my Nook HD+ running CM10.1 on emmc.
leapinlar said:
Maybe, if your /data is still ok.
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
Thanks, trying it now.
Ok:
~ # dd if=/data/boot.img of=/dev/block/mmcblk0p4
dd if=/data/boot.img of=/dev/block/mmcblk0p4
32768+0 records in
32768+0 records out
16777216 bytes (16.0MB) copied, 0.445588 seconds, 35.9MB/s
~ # dd if=/data/recovery.img of=/dev/block/mmcblk0p3
dd if=/data/recovery.img of=/dev/block/mmcblk0p3
30720+0 records in
30720+0 records out
15728640 bytes (15.0MB) copied, 0.397918 seconds, 37.7MB/s
Click to expand...
Click to collapse
Ok, this is a stupid question but how do I tell if it worked? The HD still won't boot without CWM SD card and sdcard or EMMC doesn't mount in CWM SD. Reboot ot recovery in CWM SD, then removing SD card, still gives me "nook" start up screen hang.
Was /data able to take the *.img files? If so, would it be a good idea to push the cm 10.1 rom to it and try and do a full flash? That doesn't have a boot partition though, right?
Edit: BTW, /data was empty in adb shell (except for the 2 img files i pushed there). There was a "media" subdir but it was also empty.
silkshadow said:
Ok:
Ok, this is a stupid question but how do I tell if it worked? The HD still won't boot without CWM SD card and sdcard or EMMC doesn't mount in CWM SD. Reboot ot recovery in CWM SD, then removing SD card, still gives me "nook" start up screen hang.
Click to expand...
Click to collapse
Take the card out, boot holding the power and n key. It should try to boot to recovery. Which backup did you use, stock or one you did after the CM10.1 install?
Sent from my Nook HD+ running CM10.1 on emmc.
leapinlar said:
Take the card out, boot holding the power and n key. It should try to boot to recovery. Which backup did you use, stock or one you did after the CM10.1 install?
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
The HD still doesn't boot at all without the CWM SD card in. Just black screen. I can get it to boot without the SD card only if I choose advanced->boot to recovery in CWM SD. Then it just hands at the "nook" screen (the one before Cyanogenmod boot universal boot should appear).
I *think* it was the one from CM 10.1 but I cannot be 100% sure. Its the last backup I did on the CWM SD, and I recall thinking that I should have a backup of CM 10.1 but sometimes I am an idiot and don't listen to myself.
silkshadow said:
Was /data able to take the *.img files? If so, would it be a good idea to push the cm 10.1 rom to it and try and do a full flash? That doesn't have a boot partition though, right?
Edit: BTW, /data was empty in adb shell (except for the 2 img files i pushed there). There was a "media" subdir but it was also empty.
Click to expand...
Click to collapse
no, putting the CM10.1 rom zip on /data will do no good. You can't get to it to flash it. And the cm zip does include the boot partition.
/data being empty means that data was wiped somehow.
Sent from my Nook HD+ running CM10.1 on emmc.
---------- Post added at 09:20 AM ---------- Previous post was at 09:16 AM ----------
silkshadow said:
The HD still doesn't boot at all without the CWM SD card in. Just black screen. I can get it to boot without the SD card only if I choose advanced->boot to recovery in CWM SD. Then it just hands at the "nook" screen (the one before Cyanogenmod boot universal boot should appear).
I *think* it was the one from CM 10.1 but I cannot be 100% sure. Its the last backup I did on the CWM SD, and I recall thinking that I should have a backup of CM 10.1 but sometimes I am an idiot and don't listen to myself.
Click to expand...
Click to collapse
It would be best if you could restore the boot and recovery from a stock backup. Then stock can try to repair itself.
Edit: if it will not turn on without the SD inserted, you may have also messed up xloader and bootloader partitions.
Sent from my Nook HD+ running CM10.1 on emmc.
leapinlar said:
no, putting the CM10.1 rom zip on /data will do no good. You can't get to it to flash it. And the cm zip does include the boot partition.
/data being empty means that data was wiped somehow.
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
Ouch but /data loss is not too big, especially at this point. I just want to say you are awesome and thank you so much for helping me here! Anything I can do next? I am not sure what I could've done to wipe data. My HD was lagging a bit today but nothing serious. Just ran lagfix and it froze, but as soon as it froze I shut the Nook down.
Is it strange that I cannot mount EMMC? Is it possible that CWM is not seeing /data on EMMC but just a virtual /data?
Edit: Ok, will try to restore from stock imgs right now.
Ok these are definitely the stock boot and recovery CWM backup images:
~ # dd if=/data/recovery.img of=/dev/block/mmcblk0p3
dd if=/data/recovery.img of=/dev/block/mmcblk0p3
30720+0 records in
30720+0 records out
15728640 bytes (15.0MB) copied, 0.401123 seconds, 37.4MB/s
~ # dd if=/data/boot.img of=/dev/block/mmcblk0p4
dd if=/data/boot.img of=/dev/block/mmcblk0p4
32768+0 records in
32768+0 records out
16777216 bytes (16.0MB) copied, 0.443817 seconds, 36.1MB/s
Click to expand...
Click to collapse
Here's a strange thing. I was expecting to have to go into /data and delete the older boot.img and recovery.img before pushing the new ones. However, /data was empty again.
Ok stock img (I hope) were restored. HD will still not boot (black screen) :crying:. CWM SD advanced ->boot to recovery still hangs at "nook" boot screen the first time. The 2nd time, just black screen and now nothing but black screens.
More weirdness, I've had to plug the HD in and hold down the power button to get it to boot off the CWM SD card every time I take the CWM SD card out and try to boot without it. I just noticed that when I do this the charge light is green and stays green until CWM loads and then it turns amber.
Could this be a bootloader issue? Is there a way to restore that too?
silkshadow said:
Ok these are definitely the stock boot and recovery CWM backup images:
Here's a strange thing. I was expecting to have to go into /data and delete the older boot.img and recovery.img before pushing the new ones. However, /data was empty again.
Ok stock img (I hope) were restored. HD will still not boot (black screen) :crying:. CWM SD advanced ->boot to recovery still hangs at "nook" boot screen the first time. The 2nd time, just black screen and now nothing but black screens.
More weirdness, I've had to plug the HD in and hold down the power button to get it to boot off the CWM SD card every time I take the CWM SD card out and try to boot without it. I just noticed that when I do this the charge light is green and stays green until CWM loads and then it turns amber.
Could this be a bootloader issue? Is there a way to restore that too?
Click to expand...
Click to collapse
When you say black screen without the SD in, you mean it will not turn on?
It looks like the stock stuff took. I might be able to post my stock Xloader and bootloader img files for you. Hang on.
Sent from my Nook HD+ running CM10.1 on emmc.
leapinlar said:
When you say black screen without the SD in, you mean it will not turn on?
It looks like the stock stuff took. I might be able to post my stock Xloader and bootloader img files for you. Hang on.
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
Yes, It doesn't seem to boot at all.
You.Rule. Thanks!
silkshadow said:
Yes, It doesn't seem to boot at all.
You.Rule. Thanks!
Click to expand...
Click to collapse
try dding these.
http://d-h.st/SG6
Sent from my Nook HD+ running CM10.1 on emmc.
Thank you very much! I will download and DD right now.