Related
Hi,
I use cyanogenMod nightlies, now RC1. Nearly everythings works as it should. When I try to connect my Legend via USB, I have some strange problems with the USB-storage. I'm running a Linux-System and when I activate USB-Storage, the SD-Card will only be exported as /dev/uba, so as it wouldn't have any partition. I can mount /dev/uba as root, no problem, but this worked as it should before I tried SuperFroyo. I had to partition my sdcard for this with an additional swap and ext3-partition. As I liked cyanogenMod better, I tried to revert everything, also repartitioning my sdcard. From this time, I have this strange behaviour. If I boot into recovery and activate USB-Storage from ClockworkMod, it works as before. I know, the sdcard works. I have tried to repartition and reformat it now several times, from recovery and directly with a cardreader attached to my computer. I have also wiped completely my phone along with removing /system via adb. I'm quite puzzled and thankfull for every hint.
*bumb*
no one? In the meantime I tried to repartition with swap and ext-partition as for SuperFroyo, but still the same. Somehow I've got the feeling that while SuperFroyo was installed, some setting deep inside the handset was changed that isn't reverted even when whiping or deleting whole /system. I'm thankfull for any hint!
Have U been updating your Linux box lately? Which distro do U use?
Sent from my HTC Legend
I didn't update, I'm running Debian. And as written before, when I activate usb-storage from ClockworkMod it works as it should and gets automounted.
Damnit.. My company required encryption of the data on my Nexus S when I was testing ICS Beta with Email / Exchange.
Went ahead and encrypted the device.
Then, I wanted to install ICS Combo Beta 11, so I formatted /system /data /boot and tried to install from /sdcard/*.zip.
No luck.
Clockworkmod recovery cannot mount /sdcard anymore.
Wanted to try and format it, but the clockworkmod tries to mount it first, before formatting
HELP!
I'm stuck with only recovery now and no way to get the update package installed
Is there a way to install from zip via the command line?
You should be able to use fastboot to load the rom on your device. I haven't tried it this way before but it should work:
Code:
fastboot update rom.zip [-w if you want to erase data too]
Give it a spin.
The SDCard not being able to be mounted has been covered a few times but I can't recall the proper fix by heart - search around and you'll definitely get some results that can help you with that.
Greetz
Sounds like it's busted.
Sent from my Nexus S using xda premium
Can you still enable USB Mass Storage in recovery? Try reformat the SD from your desktop?
Si_NZ said:
Can you still enable USB Mass Storage in recovery? Try reformat the SD from your desktop?
Click to expand...
Click to collapse
Thought about that, but what filesystem? FAT32?
Sure
Greetz
I had the same problem with one of the first ICS betas.
Formatting to FAT32 on my Mac was not enough, I had also to reformat under Android. Hope, you backed up your data
dr911 said:
I had the same problem with one of the first ICS betas.
Formatting to FAT32 on my Mac was not enough, I had also to reformat under Android. Hope, you backed up your data
Click to expand...
Click to collapse
Definately backed up..
This was a real scare.. I couldn't mount or format from clockworkmodrecovery. All I had was the adb shell and the builtin /sbin commands.
LUCKILY I found this article;
http://forum.cyanogenmod.com/topic/...mmcblk0++mkfs++ext2__fromsearch__1#entry56396
It didn't exactly match what I was experiencing, but the key was the parted program.
Using it, I was able to reformat my media (partition 3) and am now able to repush things to it.
Stupid sdcard encryption..
Reinstalling ICS Beta 11 now
Blood pressure slowly decreasing.. damn that was a nightmare
So some lessons learned;
DON'T try to partition your SDCARD from clockworkmod or Windows or Mac. The USB storage presented to your computer is a single partiton from you mmcblk0 sd storage. If you partition it, you've got a partition inside a partition which will only make sense to your windows/mac system. Inside of Android, the partition is essentially corrupted and it won't mount.
Formatting from Windows only makes it appear to be working.. in reality you've created a second partition and it's corrupted from the Android point of view.
parted is the only way to fix it. from parted do mkfs type fat32 partiton 3 (media) that will reformat the partition correctly and give you access from Android and external USB hosts.
That's weird...
People have been able to format the SD as ext4 on a desktop using Ubuntu for example. I don't understand how that is different to mkfs.ext4 vs mkfs.vfat. I mean why am I confined to formatting on the phone itself? I'm really confused now.
On a side note. What you experienced is totally expected if you think about it carefully. It's like you have just lost the key to open your SD content by wiping the phone, of course it can no longer be mounted. But I'm not sure why it cannot be simply formatted in CWM.
nauckwj said:
Formatting from Windows only makes it appear to be working.. in reality you've created a second partition and it's corrupted from the Android point of view.
Click to expand...
Click to collapse
That means, I should check my SD Card, which I formatted under OSX with Disk Utility?
Maybe I'll do it next time I flash a new ROM, because for now it works fine.
nauckwj said:
Blood pressure slowly decreasing.. damn that was a nightmare
Click to expand...
Click to collapse
Yeah, I had a similar situation a few weeks after I got my beloved NS when I tried Whispercore. The hole NS got encrypted and formatting the system partition in CWM didn't work, but what I read it was luckily due to a problem with the CWM version. Flashing a newer Version of CWM solved the problem. First I was dying!
So, when I encrypted with ICS and got this problem I calmed down much faster
Si_NZ said:
That's weird...
People have been able to format the SD as ext4 on a desktop using Ubuntu for example. I don't understand how that is different to mkfs.ext4 vs mkfs.vfat. I mean why am I confined to formatting on the phone itself? I'm really confused now.
On a side note. What you experienced is totally expected if you think about it carefully. It's like you have just lost the key to open your SD content by wiping the phone, of course it can no longer be mounted. But I'm not sure why it cannot be simply formatted in CWM.
Click to expand...
Click to collapse
My problem was I used the Windows fdisk partitioning utility to repartition my /sdcard partition. That was part of the problem. I did also read how some people were repartitioning the /sdcard partition, which is kind of weird. I can understand why someone might want to reformat it as an ext4 filesystem, but why would you want to partition a partition?
The /sdcard partition is actually the third partition on your mmcblk0 device. If you partition it, most utilities will fail to recognize it as a valid media device anymore, because they expect to be able to read the filesystem data structures when they mount it. These won't exist if a partition table is sitting at the beginning of the blocks.
I couldn't reformat from within CWM because it first tries to mount the partition. if it fails to mount, CWM won't reformat it. Only way to reformat it was with parted, unless you have a working system installation.
Last night I was also able to reformat it from within ICS. Had to do a full factory-wipe from within ICS, then it indicated the sdcard was no longer valid and asked me if I wanted to reformat it. Once I said yes, all was back to normal.
Fun fun
I've been experiencing the dreaded "Low Internal Memory" problems on my HD2 running a MIUI GB ROM.
I was told this was because the included A2SD, well, sucks. I was advised to use Data2EXT instead. Since I wanted to start with a clean slate anyway, I decided it was time to completely wipe my HD2 and install everything anew. This is what I did:
Wiped the HD2 with Task29 (using the HD2 Toolkit)
Installed ClockworkModRecovery v1.3 150MB (I wasn't sure I actually used the 150MB version when I initially installed CWM Recovery)
Cleared data/cache with CWM Recovery
Reformatted the 1GB sd-ext partition on my SD Card (using MiniTool Partition Wizard)
Installed ROM with CWM Recovery (from zip)
Installed A2SDKiller scripts (from zip)
Rebooted phone into MIUI, but did not install anything.
Rebooted into CWM Recovery and installed the Data2SD Installer.
Rebooted into MIUI again
It seemed everything was fine. If I looked at my memory usage, instead of only 210 MB of total storage I had previously, I now had almost 1GB. I setup my Google account and started to install some apps. Somewhere along the line one of the apps hung the phone so I rebooted it again.
But when it was done rebooting, much to my surprise all installed apps were gone. In fact, the phone was behaving like it was the first time it was started (asking me for my Google credentials again, etc). At first I thought this was perhaps due to the hung app, so I did all the above steps again (including wiping the phone).
Again I installed a few apps, and this time I rebooted the phone to check if all was OK now. It wasn't. Again the phone behaved like it was the first time I booted into the new ROM and all installed apps were gone. I've tried about 5 times now and every single time with the same results.
So what could be wrong here?
just a thought (i havent checked, you can do that) but what type of ext did you create? ext2? ext3? ext4? perhaps data2sd (you called it data2ext in the title, data2sd in the post, , ,which is it? they're probably different) doesnt play nice with whichever one you created?
Hi, and thank you for your answer.
samsamuel said:
just a thought (i havent checked, you can do that) but what type of ext did you create? ext2? ext3? ext4?
Click to expand...
Click to collapse
Ext3.
perhaps data2sd (you called it data2ext in the title, data2sd in the post, , ,which is it? they're probably different) doesnt play nice with whichever one you created?
Click to expand...
Click to collapse
I'm pretty sure they are the same (since took the installation procedure from this forum post and they call it both Data2Ext and Data2SD).
I will check to see if the filesystem matters. Thanks!
I just checked and ext3 should be fine.
Zippy1970 said:
I just checked and ext3 should be fine.
Click to expand...
Click to collapse
Check to see see if there's any script left from old method in system/etc/init.d
This is a complete guess but worth a try
EDIT: this is the script that the A2SD killer removes from system/etc/init.d
delete("/system/etc/init.d/40a2sd");
delete("/system/etc/init.d/03stuff2sd");
delete("/system/etc/init.d/10apps2sd");
delete("/system/etc/init.d/04apps2sd");
delete("/system/etc/init.d/01data2whatever");
delete("/system/etc/init.d/98zipalign");
delete("/system/etc/init.d/02cachedalvikcache");
So make sure that has been removed then try flash the new zip file
Sent from my GT-I9100 using xda premium
wis1152 said:
Check to see see if there's any script left from old method in system/etc/init.d
So make sure that has been removed then try flash the new zip file
Click to expand...
Click to collapse
Yes, all those files have been deleted.
It seems to be working now. I wanted to test if changing the Ext3 partition to Ext2 would make any difference so I fired up MiniTool Partition Wizard again. I wiped the partition and formatted it as Ext2.
Or so I thought.
The partition still said it was Ext3. Then it hit me. I had forgotten that you actually have to "Apply" the changes, which I hadn't done before. So I clicked Apply and it wiped the partition and actually formatted it as Ext2.
I then redid the whole thing (install ROM & A2SDKiller scripts, reboot into ROM, reboot into CWM Recovery and installed Data2SD). And now it seems to be working fine.
Not sure which of the two actions on the Ext partition caused it to start working: the wipe or the change to Ext2.
I spoke too soon. I thought it was working since a reset didn't clear all my installed apps. But if I look at the total storage space, it's back to 216MB total. So it looks like Data2Ext isn't running...
*SIGH*
I'm just about to give up on Data2Ext. First of all, I thought I had figured out what was wrong. For some odd reason, whenever I tried to write to my 16GB microSD card on my computer using an SD adapter, it would crash every now and then. Also, partitioning through MiniTool Partition Wizard often resulted in a "Bad Disk" error. I tried this with 3 different 16GB microSD cards. All experienced the same problems when using an SD card adapter (it wasn't a broken SD adapter because I've tried several).
I then dug up an old external microSD USB card reader I had laying around. Using that, I was able to write to the microSD cards just fine and I didn't experience any problems partitioning either.
Speaking about partitioning, it took me a while to figure out that:
Partitioning through ClockWorkMod Recovery doesn't work properly. The FAT32 partition becomes incredibly slow, and the Ext partition is not recognized by Data2Ext
Ext3/Ext4 partitions don't work with Data2Ext. At least, not on my phone
Ext2 partitions only work if they are set as the primary partition
You must name the partition sd-ext or it will not work
Just a FYI for anyone finding this thread in the future.
Anyway, once I figured that out, I was finally able to get Data2Ext working. Sort of. Let me try to explain.
Previously after I had installed Data2Ext and setup some apps, a reboot of my phone would bring it back to a factory reset state. So all installed apps were gone, just like any settings I had altered. Oddly enough, if I looked at the sd-ext partition I could see the data was still there. It simply wasn't used by the phone. But after I had partitioned the sd-ext partition as Ext2, all was fine. A reboot didn't reset the phone back to factory settings.
So I happily reinstalled all my apps, restored my SMS as well as my WhatsApp backup and thought all was fine now. But I did notice the phone wasn't very stable. Every now and then it would become unresponsive for 10-20 seconds. Sometimes I got an error message that a certain app had become unresponsive and I was offered a choice to either shutdown the app or to wait. And sometimes, the phone would spontaneously reset itself.
Today the phone again became unresponsive. Oddly enough, long-pressing the power button did bring up the shutdown window. So I tapped "Shutdown". Next, the phone hung on "Shutting Down". It didn't come back to live. So I removed the battery lid and pressed the reset button.
After it had rebooted, I was greeted with a factory reset phone again. I was about to throw the phone through the window! But when I did another reboot, all my apps were back again as well as my settings. Except for the settings of my individual widgets. Those had all disappeared for some reason. Also, I got quite a few error messages that some apps had stopped unexpectedly. I rebooted again and again the phone behaved as if it were factory reset. But yet another reboot brought everything back...
I now suspect it has something to do with the phone not being able to mount sd-ext every now and then. Either way, my problems aren't solved yet so any tips are much appreciated.
Zippy1970 said:
*SIGH*
I'm just about to give up on Data2Ext. First of all, I thought I had figured out what was wrong. For some odd reason, whenever I tried to write to my 16GB microSD card on my computer using an SD adapter, it would crash every now and then. Also, partitioning through MiniTool Partition Wizard often resulted in a "Bad Disk" error. I tried this with 3 different 16GB microSD cards. All experienced the same problems when using an SD card adapter (it wasn't a broken SD adapter because I've tried several).
I then dug up an old external microSD USB card reader I had laying around. Using that, I was able to write to the microSD cards just fine and I didn't experience any problems partitioning either.
Speaking about partitioning, it took me a while to figure out that:
Partitioning through ClockWorkMod Recovery doesn't work properly. The FAT32 partition becomes incredibly slow, and the Ext partition is not recognized by Data2Ext
Ext3/Ext4 partitions don't work with Data2Ext. At least, not on my phone
Ext2 partitions only work if they are set as the primary partition
You must name the partition sd-ext or it will not work
Just a FYI for anyone finding this thread in the future.
Anyway, once I figured that out, I was finally able to get Data2Ext working. Sort of. Let me try to explain.
Previously after I had installed Data2Ext and setup some apps, a reboot of my phone would bring it back to a factory reset state. So all installed apps were gone, just like any settings I had altered. Oddly enough, if I looked at the sd-ext partition I could see the data was still there. It simply wasn't used by the phone. But after I had partitioned the sd-ext partition as Ext2, all was fine. A reboot didn't reset the phone back to factory settings.
So I happily reinstalled all my apps, restored my SMS as well as my WhatsApp backup and thought all was fine now. But I did notice the phone wasn't very stable. Every now and then it would become unresponsive for 10-20 seconds. Sometimes I got an error message that a certain app had become unresponsive and I was offered a choice to either shutdown the app or to wait. And sometimes, the phone would spontaneously reset itself.
Today the phone again became unresponsive. Oddly enough, long-pressing the power button did bring up the shutdown window. So I tapped "Shutdown". Next, the phone hung on "Shutting Down". It didn't come back to live. So I removed the battery lid and pressed the reset button.
After it had rebooted, I was greeted with a factory reset phone again. I was about to throw the phone through the window! But when I did another reboot, all my apps were back again as well as my settings. Except for the settings of my individual widgets. Those had all disappeared for some reason. Also, I got quite a few error messages that some apps had stopped unexpectedly. I rebooted again and again the phone behaved as if it were factory reset. But yet another reboot brought everything back...
I now suspect it has something to do with the phone not being able to mount sd-ext every now and then. Either way, my problems aren't solved yet so any tips are much appreciated.
Click to expand...
Click to collapse
I have similiar problem before, The ext partition always failed. Now I used Extended TWRP to create the ext partition, it is stable now.
http://forum.xda-developers.com/showthread.php?t=2120297
I can't get Data2Ext to work. I'm either getting tons of force close errors, or it's not seeing the sd-ext partition at all. I tried with Ext2/Ext3/Ext4 partitions (Ext3 didn't seem to work at all). With or without a swap partition. Nothing worked.
I also tried Data2ExtV2 and even DataOnExt. The result was always a ton of force close errors and a very unstable phone.
So anyone any ideas? It sucks only having 200MB of internal storage.
Hmmmm... That's odd. I just wiped my phone again (Task29), reinstalled MAGLDR, CWM Recovery (150MB) and my ROM without Data2Ext or anything and I'm getting the same force close errors and it's telling me I don't have enough internal storage to install apps.
So apparently there's something else going on with my phone?
What ROM are you using?
Try increasing system partition size!
Sent from my NexusHD2 using xda premium
shanman-2 said:
What ROM are you using?
Try increasing system partition size!
Sent from my NexusHD2 using xda premium
Click to expand...
Click to collapse
Actually, I found out it was because I used the wrong cache size this last time. So it's not the cause of all the other problems, but most certainly the cause of the problems this last time I flashed the ROM.
Ok, I've given up on Data2Ext. I can't get it to work. No matter what I try it's incredibly unstable and slow - if it works at all.
1. Make a backup of your SDCard.
2. Download EXTRecovery here.
3. Unzip it and place the 4EXTRecovery folder in the root of your SDCard.
4. Start MAGLDR, choose option 10, then 1, then 3 and select the folder (4EXT~), then boot from SD in the MAGLDR main menu.
5. In the 4EXTRecovery go to Advanced -> Partition SD Card -> Remove all partitions and start from scratch.
6. 1st sd-ext partition: 1024MB, skip 2nd sd-ext partition, SWAP partition is OPTIONAL, I recommend 256MB.
7. Press Yes and pick: "EXT4".
8. When it's finished, choose: "Print partitiontable" to check if it's actually there.
9. If it's there, go back to the main menu and press: "Install from SDCard".
10. Locate your ROM and install it.
Goodluck.
EDIT: Oh, I just read you've given up on it.. all this work for nothing, lol.
Ohwell, maybe I'm lucky and someone else stumbles upon this and can use it.
EDIT 2: Use DataOnEXT and have a /system size of about 285MB, 300-350MB if you have Bad Blocks!
EDIT 3: Try it with: "Jellybean 4.1.2" by Tytung, definitely works!
I am trying to restore a NC that won't boot. After making a new bootable CMW sd card, the nook will boot but has the error message
E: Can't mount /cache/recovery/command, etc.
I have tried various boot images tonight - Leapinlar's, eyeballer's, and another one. I have tried several SD cards. I still get the same error message. I have fixed the 'no boot' problem on a couple of NC's by fixing the partitions, but have not seen this error myself before.
I have searched and found this error mentioned a lot here in the forums, but have yet to find a definitive answer or solution. Is it hardware related, or SD related?
Has anyone had this error and found a solution that worked?
Thanks for any help or suggestions.
k8108 said:
I am trying to restore a NC that won't boot. After making a new bootable CMW sd card, the nook will boot but has the error message
E: Can't mount /cache/recovery/command, etc.
I have tried various boot images tonight - Leapinlar's, eyeballer's, and another one. I have tried several SD cards. I still get the same error message. I have fixed the 'no boot' problem on a couple of NC's by fixing the partitions, but have not seen this error myself before.
I have searched and found this error mentioned a lot here in the forums, but have yet to find a definitive answer or solution. Is it hardware related, or SD related?
Has anyone had this error and found a solution that worked?
Thanks for any help or suggestions.
Click to expand...
Click to collapse
You messed up your partition table. You'll need to look at this tutorial by leapinlar http://forum.xda-developers.com/showthread.php?t=1759558
sagirfahmid3 said:
You messed up your partition table. You'll need to look at this tutorial by leapinlar http://forum.xda-developers.com/showthread.php?t=1759558
Click to expand...
Click to collapse
I realize that my partitions do need to be fixed, but I can't get past the error message to run the zip files.
k8108 said:
I realize that my partitions do need to be fixed, but I can't get past the error message to run the zip files.
Click to expand...
Click to collapse
Hmm...Can you at least get ADB working on your pc? It should work even if your partitions are messed up. It sure did for my Nook Tablet. I totally bricked it and ended up repairing it from adb shell alone (had to manually remake partitions).
Type in "adb shell" in the command line. Should list your serial number. If it shows "00000000" then your ROM partition is prob. messed up.
Type in "fdisk -l /dev/block/mmcblk0" (press q to quit after observing the partitions listed). Type "blkid" If it lists your factory partition (for me, it's mmcblk0p3) and it is still intact, you can get your ROM partition's info back and that will allow you to boot successfully.
That error message is an indication that your /cache partition is not functional (probably along with your other partitions). Are you saying this error prevents you from flashing anything?
If so, your solution is to get ADB working and using fdisk to manually rebuild the partitions.
You might also try putting a ROM on SD and see if that boots. Then you can use Terminal Emulator to run fdisk.
Sent from my Nook HD+ running CM10.1 on emmc.
leapinlar said:
That error message is an indication that your /cache partition is not functional (probably along with your other partitions). Are you saying this error prevents you from flashing anything?
If so, your solution is to get ADB working and using fdisk to manually rebuild the partitions.
You might also try putting a ROM on SD and see if that boots. Then you can use Terminal Emulator to run fdisk.
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
Correct, I can not flash anything from recovery.
I did make a boot-able SD using your image (leapinlar) and the nook wouldn't boot. (It would have been great if it had!) So I'm going to keep working to see if I can understand and work ADB.
sagirfahmid3 said:
Hmm...Can you at least get ADB working on your pc? It should work even if your partitions are messed up. It sure did for my Nook Tablet. I totally bricked it and ended up repairing it from adb shell alone (had to manually remake partitions).
Type in "adb shell" in the command line. Should list your serial number. If it shows "00000000" then your ROM partition is prob. messed up.
Type in "fdisk -l /dev/block/mmcblk0" (press q to quit after observing the partitions listed). Type "blkid" If it lists your factory partition (for me, it's mmcblk0p3) and it is still intact, you can get your ROM partition's info back and that will allow you to boot successfully.
Click to expand...
Click to collapse
Yes, I got list
It says
Device Boot start end blocks ID system
Dev/block/mmcblk0p1 * 1 3865 31165952 c win95 fat32 <lba>
then I used blkid
it says
/dev/block/vold/179:1: UUID="1cd2-ff94" type="vfat"
/dev/block/mmcblk0p1: UUID="1cd2-ff94" type="vfat"
please help me now.. further..
I want to start my device.. its in cwm 6.0.4.3 recvovery mode.
and e can't moount errorss..
please help me further in adb how to delete these stupid block and get my note 2 n7100 back in life
The Issue
Hi, I have a Nook Simple Touch that gets stuck trying to boot. First I see the Barnes and Noble Screen, Next for a brief moment it tries to load a Rom and shows a small nook icon with a loading bar. Next it says "Install Failed". I am unable to do anything other than a factory reset, which doesn't help.
Background
I should add that the device previously was working fine, then one day it froze as I was highlighting some text. When I tried to boot it, it was stuck in the scenario described above. I believe it was already updated to 1.2.2 with seemingly no issues.
What I've tried:
I have tried restoring it back with noogie and a backup, and I have also tried the Nook Manager- Rescue from .zip and Rescue from backup to no avail. Still get that same blasted "Rom Restore Image" Screen followed by "Install Failed".
I have an update from Barnes and Noble called "nook_1_2_update.zip" which I tried to copy over to the nook but the file is too large.
Any ideas? I love this thing and don't want to let it go!:crying::good:
I guess You can insert an SD card with NookManager back and boot properly?
If so lets connect to Your nook via ADB, mount /boot partition and prepare copy of its files.
Code:
mount -o rw,remount rootfs /
mkdir boot
mount -t vfat /dev/block/mmcblk0p1 /boot
[B]...
copy files inside boot partition from
...[/B]
mount -o ro,remount rootfs /
umount /boot
Then put this exact copy onto new (vfat formatted) SD card, and try to boot from new card.
Let us know whats happen.
Is this booting from new SD, showing same fail screens?
Thanks so much for the assistance! I will give it a try and report back.
Also , to note, I do have an old glowlight here that has a cracked screen. Wonder if I could get a copy of it's IMG and use that too?
Trigrammaton said:
... I do have an old glowlight here that has a cracked screen. Wonder if I could get a copy of it's IMG and use that too?
Click to expand...
Click to collapse
Im not quite sure. Another version, etc...
You can use NST boot partition image from this post
For preparing another booting SD card too...
Trigrammaton said:
Thanks so much for the assistance! I will give it a try and report back.
Also , to note, I do have an old glowlight here that has a cracked screen. Wonder if I could get a copy of it's IMG and use that too?
Click to expand...
Click to collapse
If you restore the image from a different device the serial number, MAC address, etc. will be messed up. You will never be able to register the device. This may not be an issue, but just so you are aware.
nmyshkin said:
If you restore the image from a different device the serial number, MAC address, etc. will be messed up.
Click to expand...
Click to collapse
The serial number is written inside the little door for the SD card (if you haven't worn it off).
The serial number and the MAC are also on a sticker in the inside.
ucy74 said:
I guess You can insert an SD card with NookManager back and boot properly?
If so lets connect to Your nook via ADB, mount /boot partition and prepare copy of its files.
Code:
mount -o rw,remount rootfs /
mkdir boot
mount -t vfat /dev/block/mmcblk0p1 /boot
[B]...
copy files inside boot partition from
...[/B]
mount -o ro,remount rootfs /
umount /boot
Then put this exact copy onto new (vfat formatted) SD card, and try to boot from new card.
Let us know whats happen.
Is this booting from new SD, showing same fail screens?
Click to expand...
Click to collapse
Ucy - It boots from nook manager and I am able to use that utility just fine without the failed rom screen. What do you mean by "new" sd? If i put a blank sd into the slot and boot?
When you talk about ADB above and using that - I just download the sdk then use the code you pasted above to copy over the boot partition you linked to my nook (not sd) and try booting like that, correct?
Thanks! I can figure things out with a little guidance, I'm just not really well versed on some of this. Appreciate your help very much!
Trigrammaton said:
Ucy - It boots from nook manager and I am able to use that utility just fine without the failed rom screen.
Click to expand...
Click to collapse
Super, it means so You can connect to Your Nook and dump boot partition files to PC using ADB.
What do you mean by "new" sd? If i put a blank sd into the slot and boot?
Click to expand...
Click to collapse
You can copy files dumped above onto vfat formated SD card. Then try to boot from this "new" - freshly prepared card. Check whats happen.
When you talk about ADB above and using that - I just download the sdk then use the code you pasted above to copy over the boot partition you linked to my nook (not sd) and try booting like that, correct?
Click to expand...
Click to collapse
NOT SO FAST!!! Do not put linked partinion into nook! There are different cases and commands to do that. If You are new to ADB lets try to dump boot partition first, as mentioned before. Maybe there will be not necessary to replace whole partition rather than single file.
Thanks! I can figure things out with a little guidance, I'm just not really well versed on some of this. Appreciate your help very much!
Click to expand...
Click to collapse
Prepare this dumped SD first. We try to heal it to make bootable...
Thanks! I will give it a whirl this weekend and report back. Really appreciate you taking time to respond - Very kind of you!