Related
I was using win32DiskImager to write cm7 to an sd card. I had my Nook connected to my computer and accidentally wrote to the Nook instead of the SD card. Now, every time I boot up the Nook, I get a message that says the Nook encountered a problem and needs to be rebooted.
Which steps should I take to write the stock firmware to the Nook?
First, ask a mod to move this post to General or Q&A.
Second, provide details about what exactly you had and were trying to do, including OS versions and other relevant info.
I had stock 1.2 with CWR. I was trying to get my Nook back to complete stock (Like just out of the box) and run a separate firmware from my SD. I used a zip to remove CWR from the nook emmc. I was trying to write the CM7 SD image to my SD card, but forgot my Nook was still connected to my PC. Instead of choosing the SD card to write to with Win32DiskImager, I chose the Nook to write to. Now I can't even view the file folders on my Nook while connected to my PC. I have an SD card with CWR on it. If I need to flash something to the emmc I can do it that way.
There are stock images. People have them and will post. Don't panic.
Sent from my Samsung-SPH-D700 using XDA App
I've tried flashing some of the stock images I've seen. I still get the reboot message.
natoe33 said:
I've tried flashing some of the stock images I've seen. I still get the reboot message.
Click to expand...
Click to collapse
Man, sounds like you wiped your partitions. Let's hope that you only wiped your /media partition.
-Get a bootable CWM sdcard.
-Boot to CWM Recovery
-Connect nook to pc
-Assuming you have adb up and running. Run the following commands:
Code:
$ adb shell
# fdisk -l /dev/block/mmcblk0
That should give you a print out of your partition layout. Post here so we can see where you're at.
-Racks
How do I insert code like you did?
This is what I got. (I think I did this right)
Code:
~ # fdisk -l /dev/block/mmcblk0
fdisk -l /dev/block/mmcblk0
Disk /dev/block/mmcblk0: 7944 MB, 7944011776 bytes
255 heads, 63 sectors/track, 965 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 * 1 9 72261 c Win95 FAT32 (LB
A)
/dev/block/mmcblk0p2 10 18 72292+ c Win95 FAT32 (LB
A)
/dev/block/mmcblk0p3 19 56 305235 83 Linux
/dev/block/mmcblk0p4 57 935 7060567+ 5 Extended
/dev/block/mmcblk0p5 57 114 465853+ 83 Linux
/dev/block/mmcblk0p6 115 236 979933+ 83 Linux
/dev/block/mmcblk0p7 237 281 361431 83 Linux
/dev/block/mmcblk0p8 282 935 5253223+ c Win95 FAT32 (LB
A)
~ #
Well thats a good sign. All your partitions are still intact. Have you tried the 8-Failed reboots? Then clearing data by holding "Power & Home" Until the clearing data screen comes up?
natoe33 said:
This is what I got. (I think I did this right)
Code:
~ # fdisk -l /dev/block/mmcblk0
fdisk -l /dev/block/mmcblk0
Disk /dev/block/mmcblk0: 7944 MB, 7944011776 bytes
255 heads, 63 sectors/track, 965 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 * 1 9 72261 c Win95 FAT32 (LB
A)
/dev/block/mmcblk0p2 10 18 72292+ c Win95 FAT32 (LB
A)
/dev/block/mmcblk0p3 19 56 305235 83 Linux
/dev/block/mmcblk0p4 57 935 7060567+ 5 Extended
/dev/block/mmcblk0p5 57 114 465853+ 83 Linux
/dev/block/mmcblk0p6 115 236 979933+ 83 Linux
/dev/block/mmcblk0p7 237 281 361431 83 Linux
/dev/block/mmcblk0p8 282 935 5253223+ c Win95 FAT32 (LB
A)
~ #
Click to expand...
Click to collapse
I tried the 8 failed reboot thing. Now I'm stuck at "Read Forever".
EDIT: I got it to work. Thanks. <======= noooooooooooooob
natoe33 said:
I tried the 8 failed reboot thing. Now I'm stuck at "Read Forever".
EDIT: I got it to work. Thanks. <======= noooooooooooooob
Click to expand...
Click to collapse
Good to hear. Now unplug your nook before you burn another image to it! .
Racks
Sent from my NookColor using Tapatalk
Post your final solution for future reference
daemonfly said:
Post your final solution for future reference
Click to expand...
Click to collapse
Nothing too exciting. I must have messed something up while trying to 8 failed boot reset.
Made a second run at the 8 fails and did the BN update to 1.2. Pretty anti-climactic.
racks11479 said:
Good to hear. Now unplug your nook before you burn another image to it! .
Racks
Sent from my NookColor using Tapatalk
Click to expand...
Click to collapse
Yeah. Fool me once...
http://forum.xda-developers.com/showthread.php?t=945838
Keep this handy for next time. It's a CWR SD card image of stock 1.1
Burn to SD card and boot, it will do everytihng for you.
get an SD card reader, dont rely on your nook as the reader..... You can get USB SD readers for like 20 bucks
It sounds like you didn't overwrite any of your firmware, but rather you ran the disk imager on the /media partition of your Nook. Your firmware stayed intact, but when you tried to boot the device it saw the bootable partition information on internal storage and got confused. That would explain why none of your fixes from CWR appeared to help, because CWR usually doesn't touch the /media partition.
Help - I did the same thing but I don't think I was so lucky!
My Nook Color boots - but when I connect it to my PC the size of the USB drive reads as only 1 GB. I'm afraid I messed up the partitions.
I tried the 8-reboots, but I still have the wrong disk size.
Tried getting ADB to work earlier today but was not able to recognize the nook.
I would really appreciate some help.
vgramatges said:
My Nook Color boots - but when I connect it to my PC the size of the USB drive reads as only 1 GB. I'm afraid I messed up the partitions.
I tried the 8-reboots, but I still have the wrong disk size.
Tried getting ADB to work earlier today but was not able to recognize the nook.
I would really appreciate some help.
Click to expand...
Click to collapse
The "new partitioned" Nook Colors have only a 1 GB /media storage space, and a 7 GB system+data+apps partition. The old ones were the other way around.
It seems to be working fine in every other respect - I got the upgrade to 1.3 to work, and then got it rooted, so I will try to get ADB working and then will check the partitions using the command suggested earlier in this thread.
Thank you for the quick reply!
** MUCH RELIEVED **
I run a pure ICS ROM, with all the Samsung apps and addons removed.
But I still have a 500Mb partition mounted under "/preload". Samsung stuff.
This renders 500Mb of RAM useless since the "pure" ICS does not store anything there. This could be used for /data instead.
Now, can anyone point me to a .pit file I can use that does not have that partition included, or better still, how do I edit or create my own .pit file. I tried fdisk but with no luck.
[email protected]:/ # df -kh
Filesystem Size Used Available Use% Mounted on
tmpfs 415.3M 32.0K 415.3M 0% /dev
tmpfs 415.3M 0 415.3M 0% /mnt/asec
tmpfs 415.3M 0 415.3M 0% /mnt/obb
/dev/block/mmcblk0p9 503.9M 282.1M 221.8M 56% /system
/dev/block/mmcblk0p7 98.4M 4.1M 94.4M 4% /cache
/dev/block/mmcblk0p1 19.7M 8.2M 11.5M 42% /efs
/dev/block/mmcblk0p10 2.0G 368.6M 1.6G 18% /data
/dev/block/mmcblk0p12 503.9M 8.4M 495.6M 2% /preload
You shouldn't be trying to mess with PIT. Believe me.
Also, you misspelled Storage. That's not RAM.
Sent from my GT-I9100 using XDA App
Sorry, storage ofcourse.
My basic plan was to just backup /data, remove the /preload & /data partition and recreate /data with a size of 2.5Gb. But nooo... fdisk does not want me to do this.
Been using Linux for 15 years so I thought that would work.
Are there no recoveries with partitioning tools out there? Like CWM but not only with sdcard-partitioning.
This kind of worries me too, it seldom is good... fdisk output:
The number of cylinders for this disk is set to 1923584.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)
Command (m for help): p
Disk /dev/block/mmcblk0: 15.7 GB, 15758000128 bytes
1 heads, 16 sectors/track, 1923584 cylinders
Units = cylinders of 16 * 512 = 8192 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 1923456 15387647+ ee EFI GPT
Partition 1 does not end on cylinder boundary
Command (m for help): v
Partition 1 does not end on cylinder boundary
Partition 1: sector 0 greater than maximum 16
2048 unallocated sectors
Command (m for help):
Let me explain it straight : Bootloader and PIT are tightly linked together. PIT is set by samsung and mapped directly to the bootloader initialization. If you bork the PIT, the bootloader is borked too, leading to device not booting at all (even in download mode).
Just leave that partition alone and enjoy your phone. You certainly won't even use those 500MB.
And by the way, a phone's storage partitionning is not a hard drive. You don't just fdisk like on a computer.
bodhisattva99 said:
Sorry, storage ofcourse.
My basic plan was to just backup /data, remove the /preload & /data partition and recreate /data with a size of 2.5Gb. But nooo... fdisk does not want me to do this.
Been using Linux for 15 years so I thought that would work.
Are there no recoveries with partitioning tools out there? Like CWM but not only with sdcard-partitioning.
This kind of worries me too, it seldom is good... fdisk output:
The number of cylinders for this disk is set to 1923584.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)
Command (m for help): p
Disk /dev/block/mmcblk0: 15.7 GB, 15758000128 bytes
1 heads, 16 sectors/track, 1923584 cylinders
Units = cylinders of 16 * 512 = 8192 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 1923456 15387647+ ee EFI GPT
Partition 1 does not end on cylinder boundary
Command (m for help): v
Partition 1 does not end on cylinder boundary
Partition 1: sector 0 greater than maximum 16
2048 unallocated sectors
Command (m for help):
Click to expand...
Click to collapse
If it were that easy, someone would have done it already. I suggest just symlinking the partition to a folder if you really want to use the extra space... If you're adventurous, find a way of using it for Dalvik.
XpLoDWilD said:
Let me explain it straight : Bootloader and PIT are tightly linked together. PIT is set by samsung and mapped directly to the bootloader initialization. If you bork the PIT, the bootloader is borked too, leading to device not booting at all (even in download mode).
Just leave that partition alone and enjoy your phone. You certainly won't even use those 500MB.
And by the way, a phone's storage partitionning is not a hard drive. You don't just fdisk like on a computer.
Click to expand...
Click to collapse
Thanks for a great answer. Case closed I guess.
I moved dalvik there by soft linking it and so far everything seems to work fine.
After a reboot the filesystem is mountrd RO. Not quite sure where to change that. Something like /etc/fstab.... Anyone?
EDIT: Found it, init.rc....
OK, next dumb question, as the init.rc gets overwritten on reboot, where is the original?
bodhisattva99 said:
OK, next dumb question, as the init.rc gets overwritten on reboot, where is the original?
Click to expand...
Click to collapse
I believe it's in initramfs packed with the kernel.
oinkylicious said:
I believe it's in initramfs packed with the kernel.
Click to expand...
Click to collapse
OK, that sucks since I cannot recompile it.
I solved it by a script in /system/etc/init.d/ , its an ugly 5-minuter but it does the job.
Works on every reboot, if the dalvik is already moved nothing happens, I just get some stderr. Takes a few seconds the first time.
Will extend tomorrow if a "wipe dalvik-cache" is done from recovery. It wont handle that right now.
----- script -----
mount /preload -o remount,rw,nosuid,nodev,noatime,noauto_da_alloc
chmod 0771 /preload
mv /data/dalvik-cache /preload/
ln -s /preload/dalvik-cache /data/dalvik-cache
----- script -----
Ahh, no more wasted space!
bodhisattva99 said:
OK, that sucks since I cannot recompile it.
Click to expand...
Click to collapse
Sure you can, it's pretty straightforward. [GUIDE]Unpack/Repack initramfs in zImage (i9100)
XpLoDWilD said:
You shouldn't be trying to mess with PIT. Believe me.
Also, you misspelled Storage. That's not RAM.
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
You can tell people this multiple times mate but they tend not to listen until one day you see a post: "Halp, ma fone.. it b0rk"
oinkylicious said:
Sure you can, it's pretty straightforward. [GUIDE]Unpack/Repack initramfs in zImage (i9100)
Click to expand...
Click to collapse
Many thanks! Some play for to tomorrow then.
Intratech said:
You can tell people this multiple times mate but they tend not to listen until one day you see a post: "Halp, ma fone.. it b0rk"
Click to expand...
Click to collapse
OK, OK, I got the message...
Sorry wasn't directed at you... was just a general statement.
Intratech said:
Sorry wasn't directed at you... was just a general statement.
Click to expand...
Click to collapse
No prob, better than I learn it the hard way...
You boy have a heart of a Jedi. Full respect. Hopefully no one will cry like an Ewok soon
Sent from my GT-I9100 using xda premium
Sorry for all the stupid questions but I only had the S2 for three days.
OK, here goes... nothing...
Seems to repack fine. Lets just hope I did the scripting OK.
Will upload once I've tried it out myself...
[email protected] ~/work/android/initramfs-tools $ ./repack boot.img initramfs-bodhisattva99_v1.0.cpio
---------------------------kernel repacker for i9100---------------------------
Extracting gzip'd kernel from boot.img (start = 17972)
CPIO compression type detected = gzip | offset = 193180
CPIO image MAX size:1921884
Head count:2115064
Making head.img ( from 0 ~ 193180 )
Making a tail.img ( from 2115064 ~ 10031364 )
Current ramdsize using cat : 3272192 with required size : 1921884 bytes
Current ramdsize using gzip -f9 : 1916756 with required size : 1921884 bytes
gzip -f9 accepted!
Merging [head+ramdisk] + padding + tail
Now we are rebuilding the zImage
Image ---> piggy.gzip
piggy.gzip ---> piggy.gzip.o
Compiling head.o
Compiling misc.o
Compiling decompress.o
Compiling lib1funcs.o
Create vmlinux.lds
head.o + misc.o + piggy.gzip.o + decompress.o + lib1funcs.o---> vmlinux
vmlinux ---> zImage
New zImage size:5740672
Padding new zImage to 8388608 bytes
Padding sufiles to new_zImage
new_zImage has been created
Cleaning up...
finished...
Haha... lets try it!
Well,all this is nice and you have my respect for being fearless with these matters,but some months ago there was another interesting idea for the proper use of the hidden partition.A hidden porn stash.Works like a charm.
I don't remember who proposed that,but kudos to him.
OK, can someone explain to me how to build a CWM flashable .zip with the new zImage?
Been searching forum for 2 hours and I can only find how to build application zips, not kernel...
It should also prefferably have a script in it that runs the following after updating the kernel/boot.img
rm -rf /data/dalvik-cache
ln -s /preload/dalvik-cache /data/dalvik-cache
bodhisattva99 said:
OK, can someone explain to me how to build a CWM flashable .zip with the new zImage?
Been searching forum for 2 hours and I can only find how to build application zips, not kernel...
It should also prefferably have a script in it that runs the following after updating the kernel/boot.img
rm -rf /data/dalvik-cache
ln -s /preload/dalvik-cache /data/dalvik-cache
Click to expand...
Click to collapse
Flash with mobile odin
Sent from my GT-I9100 on CM9 using Tapatalk
The below post is actually a PM I sent to ros87, but it look like he hasn't been on the forums in a while, so I thought I'd ask the general populous. Besides, if I manage to get out of this one, then it might help someone else.
--------------------------
To make a long story short, I have a NST that will not boot from the internal memory. I can boot from SD card images no problem (noogie, cwm, n2T-Recovery). When I boot from noogie, I can see the internal storage.
How I managed to get here:
- tried to follow the "Backup/Restore N2E" instructions from Windows, so used MiniTool Partition Wizard to delete the NST partitions
- THEN I realized the backup I took a long time ago wasn't a full device backup, but individual partition backups:
Code:
07/14/2011 09:09 PM 79,675,392 nook_backup_BOOT.img
07/14/2011 09:41 PM 251,641,856 nook_backup_CACHE.img
07/14/2011 09:58 PM 840,941,568 nook_backup_DATA.img
07/14/2011 09:30 PM 301,973,504 nook_backup_DISK.img
07/14/2011 09:22 PM 199,229,440 nook_backup_FACTORY.img
07/14/2011 09:04 PM 251,641,856 nook_backup_NOOK.img
07/14/2011 09:19 PM 16,777,216 nook_backup_ROM.img
I wasn't having any luck with Windows-based tools, so I switched to Linux. I've attempted to rebuild the partitions and copy over the data from my backups using dd:
Code:
dd if=/home/kenny/host/Nook\ Backup/nook_backup_BOOT.img of=/dev/sdb1 bs=1M
dd if=/home/kenny/host/Nook\ Backup/nook_backup_ROM.img of=/dev/sdb2 bs=1M
dd if=/home/kenny/host/Nook\ Backup/nook_backup_FACTORY.img of=/dev/sdb3 bs=1M
dd if=/home/kenny/host/Nook\ Backup/nook_backup_DISK.img of=/dev/sdb5 bs=1M
dd if=/home/kenny/host/Nook\ Backup/nook_backup_NOOK.img of=/dev/sdb6 bs=1M
dd if=/home/kenny/host/Nook\ Backup/nook_backup_CACHE.img of=/dev/sdb7 bs=1M
dd if=/home/kenny/host/Nook\ Backup/nook_backup_DATA.img of=/dev/sdb8 bs=1M
The commands seemed to work and I do see the right kind of data in the partitions, but it still won't boot.
Here's a dump of the current state of things:
Code:
fdisk -l /dev/sdb
Disk /dev/sdb: 1958 MB, 1958739968 bytes
128 heads, 32 sectors/track, 934 cylinders
Units = cylinders of 4096 * 512 = 2097152 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000001
Device Boot Start End Blocks Id System
/dev/sdb1 * 1 38 77808 c W95 FAT32 (LBA)
/dev/sdb2 39 46 16384 c W95 FAT32 (LBA)
/dev/sdb3 47 141 194560 83 Linux
/dev/sdb4 142 934 1624064 5 Extended
/dev/sdb5 142 285 294896 83 Linux
/dev/sdb6 286 405 245744 c W95 FAT32 (LBA)
/dev/sdb7 406 525 245744 83 Linux
/dev/sdb8 526 926 821232 83 Linux
--------------------------
df -h
/dev/sdb5 279M 183M 94M 67% /media/boot
/dev/sdb7 233M 6.2M 224M 3% /media/cache
/dev/sdb2 16M 119K 16M 1% /media/rom
/dev/sdb3 184M 106M 77M 58% /media/factory
/dev/sdb8 790M 20K 782M 1% /media/boot_
/dev/sdb6 237M 104M 133M 44% /media/NOOK
/dev/sdb1 75M 58M 18M 78% /media/boot__
I'm not entirely sure I got the partitions created in the format or order the nook wants. Luckily, since I do have the contents of the partitions, I do feel like I can get out of this mess, but just haven't managed to find the right sequence yet.
What I'd love to try is using a good, full backup that someone else has made, and then use my individual partition backups to rewrite the sections that are unique to my nook. Unfortunately, the torrent containing the one full backup that someone posted is long dead.
So, If there's anything anyone can think of that will help me revive this thing, I'd be ever so grateful. If you need more information, I'll get it.
Thanks!!!
"What I'd love to try is using a good, full backup that someone else has
made, and then use my individual partition backups to rewrite the
sections that are unique to my nook. Unfortunately, the torrent containing
the one full backup that someone posted is long dead."
You can boot into CWR, and you can probably pull a copy of the factory.zip file from one of your restored partitions.
But I think that where you are is a fixable point at this time - somehow (perhaps because you restored partition by partition and thus weren't able to get a correct set of names tied to them) the names are wrong on some pretty important partitions - system, data and boot!
The partitions at a very fast glance look OK to me in terms of size, number and order.
This, though:
/dev/sdb5 279M 183M 94M 67% /media/boot
/dev/sdb8 790M 20K 782M 1% /media/boot_
/dev/sdb1 75M 58M 18M 78% /media/boot__
/sdb5 should be /system;
/sdb8 should be /data (I seem to remember that Linux calls it 'userdata' when the disk is mounted)
/sdb1 should be boot -- no terminal underscores.
You can rename the partitions using parted in Linux. I would start there - boot noogie, use linux parted to address the problem with partition 1. Try renaming 5 as system and 8 as userdata (I don't have the output to hand to show you exactly what this will look like in parted)
the syntax at the CLI is
(parted) name 1 boot
(parted) quit
for partition 1 to get the name boot
(but also use the parted print command to look to see what the partitions are being called by the disk. There may be others that need tuning, but it looks as if the df command actually did find out what the disk was calling the partitions, which is helpful.)
gparted may work also, and it's a little less intimidating to use if there's a rename partition command in it.
If you can get it to boot even enough to fail, your restore image should be visible to the device and it will eventually see that it's failed enough times to force a reset.
Thanks for the detailed reply!
Since I wrote the above message, I did play with the partitions a little more to get the order to better match what I found in the Nook Touch Partition Hacking thread. Here's how it looks in gParted, after I did the labeling (parted wouldn't name a FAT32 partition):
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Still no luck trying to boot after the renaming.
Then I tried using CWM to flash the factory.zip I was able to extract from my backup. It flashed successfully, but still no boot.
I still question my partition table a bit simply because I haven't been able to find a really good reference as to what the table on a stock Nook should look like.
Kaishio said:
I still question my partition table a bit simply because I haven't been able to find a really good reference as to what the table on a stock Nook should look like.
Click to expand...
Click to collapse
That's what I see:
fdisk -l /dev/block/mmcblk0
Code:
Disk /dev/block/mmcblk0: 1958 MB, 1958739968 bytes
128 heads, 32 sectors/track, 934 cylinders
Units = cylinders of 4096 * 512 = 2097152 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 * 1 38 77808 c Win95 FAT32 (LBA)
/dev/block/mmcblk0p2 39 46 16384 c Win95 FAT32 (LBA)
/dev/block/mmcblk0p3 47 141 194560 83 Linux
/dev/block/mmcblk0p4 142 926 1607680 5 Extended
/dev/block/mmcblk0p5 142 285 294896 83 Linux
/dev/block/mmcblk0p6 286 405 245744 c Win95 FAT32 (LBA)
/dev/block/mmcblk0p7 406 525 245744 83 Linux
/dev/block/mmcblk0p8 526 926 821232 83 Linux
mount
Code:
rootfs / rootfs ro 0 0
tmpfs /dev tmpfs rw,mode=755 0 0
devpts /dev/pts devpts rw,mode=600 0 0
proc /proc proc rw 0 0
sysfs /sys sysfs rw 0 0
tmpfs /sqlite_stmt_journals tmpfs rw,size=4096k 0 0
/dev/block/mmcblk0p2 /rom vfat rw,sync,noatime,nodiratime,uid=1000,gid=1000,fmask=0117,dmask=0007,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,errors=remount-ro 0 0
/dev/block/mmcblk0p5 /system ext2 ro,errors=continue 0 0
/dev/block/mmcblk0p8 /data ext3 rw,nosuid,nodev,noatime,nodiratime,errors=continue,data=ordered 0 0
/dev/block/mmcblk0p7 /cache ext3 rw,nosuid,nodev,noatime,nodiratime,errors=continue,data=ordered 0 0
Really appreciate the responses.
...but I'm still stuck. I made my partitions match exactly what ApokrifX posted, restored from my backups, but no boot. So strange. I'll keep messing with it though.
Maybe I'll have to ninja into barnes and noble and take a full device backup of one of the display units.
Don’t really know what to suggest...
Do you see anything on the screen when it fails to boot?
Were you able to find someone else full backup?
Can you boot noggie, take full backup and try to understand what’s messed up in it by comparing?
I have a theory that all the B&N Nook products have some sort of unbrick mode built in. I have not had a chance to try with a NST but it works fine for my Nook tablet.
1. Create partition table and format partitions see how I did this here http://forum.xda-developers.com/showthread.php?t=1225196
2. set up the first partition with MLO uboot uImage and recovery
3. Get hold of a update file from B&N Site and strip the leading signapk bits and put it on a blank sdcard after renaming it as gossamer_update.zip
4 Start up the nook it should boot from internal emmc see the presence of the special update.zip on sdcard and upgrade / downgrade reinstall etc
just look at some of the posts in the B&N Tablet threads and all this stuff works on that, grepping the source for uboot on the NST gives the gossamer name
meghd00t said:
I have a theory that all the B&N Nook products have some sort of unbrick mode built in. I have not had a chance to try with a NST but it works fine for my Nook tablet.
1. Create partition table and format partitions see how I did this here http://forum.xda-developers.com/showthread.php?t=1225196
2. set up the first partition with MLO uboot uImage and recovery
3. Get hold of a update file from B&N Site and strip the leading signapk bits and put it on a blank sdcard after renaming it as gossamer_update.zip
4 Start up the nook it should boot from internal emmc see the presence of the special update.zip on sdcard and upgrade / downgrade reinstall etc
just look at some of the posts in the B&N Tablet threads and all this stuff works on that, grepping the source for uboot on the NST gives the gossamer name
Click to expand...
Click to collapse
Cool.
OR he can actually use your approach and his backup of all partition to create whole nook image as well! :good:
Thanks m. I only had a few minutes today to mess with it, and while I didn't have any success, it wasn't the best attempt. I'll do more when I have more time.
That being said, to answer ApokrifX's earlier question, I don't see anything change on the screen for a failed boot. If it said Rooted Forever before, that's what stays. If it was CWM's "rebooting" message, that's what stays.
At this point, I'm wondering, rather than trying for a full restore, if I should just focus on getting any sort of boot from emmc. So far, I've had not been able to get any response with a SD card removed. What's the simplest way to show/test any sort of boot from internal memory?
Kaishio said:
At this point, I'm wondering, rather than trying for a full restore, if I should just focus on getting any sort of boot from emmc. So far, I've had not been able to get any response with a SD card removed. What's the simplest way to show/test any sort of boot from internal memory?
Click to expand...
Click to collapse
I wish I can answer that.
Might be coping noogie.img content to first nook partition?
I would PM to mali100 to get clarification first.
ApokrifX said:
Might be coping noogie.img content to first nook partition?
Click to expand...
Click to collapse
That should work, but the boot partition has to start on the correct sector.
mali100 said:
That should work, but the boot partition has to start on the correct sector.
Click to expand...
Click to collapse
Mali,
Do you mean alignment, or something else?
I thought, it is same way everywhere:
“Disk boot sector” (Partition loader) finds first/last active partition, loads its first sector and jumps to it.
“Active partition boot sector” finds boot file by name or have its offset, loads it (partially) and jumps to it.
No idea how it works with noogie, but gotta be something similar?
Another Q:
In Kaishio case, could it be that partitions have correct sizes, but wrong offsets, thus booting process fails?
As I understand it the restrictions are
1. Geometry 128Heads * 32Sectors per track
2. 1st partition has to be type Win95 LBA
3. 1st partition has to be bootable
4. MLO has to be uppercase and the first file on the file system
I had to fiddle a long time with sfdisk to get these rules right.
Kaishio said:
Code:
fdisk -l /dev/sdb
Disk /dev/sdb: 1958 MB, 1958739968 bytes
128 heads, 32 sectors/track, 934 cylinders
Units = cylinders of 4096 * 512 = 2097152 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000001
Device Boot Start End Blocks Id System
/dev/sdb1 * 1 38 77808 c W95 FAT32 (LBA)
/dev/sdb2 39 46 16384 c W95 FAT32 (LBA)
Click to expand...
Click to collapse
meghd00t said:
As I understand it the restrictions are
1. Geometry 128Heads * 32Sectors per track
2. 1st partition has to be type Win95 LBA
3. 1st partition has to be bootable
4. MLO has to be uppercase and the first file on the file system
I had to fiddle a long time with sfdisk to get these rules right.
Click to expand...
Click to collapse
Looks like he had satisfied first 3 conditions.
IMO, if "MLO has to be uppercase", then bootloader is searching for it by name, so it doesn’t have to be "the first file on the file system"
---------- Post added at 04:36 PM ---------- Previous post was at 04:25 PM ----------
Funny: http://overoinfo.blogspot.com/2010/03/creating-bootable-microsd-card.html
It is very important that these three files have precisely these names and are loaded into the boot partition in a very specific order. The Overo boot loader does not use the names per-se but instead loads the FIRST installed file on the boot partition (MLO) which does look for specific name 'u-boot.bin' when it is time to load the boot loader. The boot loader also looks for the specific name uImage to load the Linux kernel.
Click to expand...
Click to collapse
I.e. only u-boot.bin and uImage names are important.
MLO has to be FIRST installed file on the boot partition.
It can have any name.
Hi,
I succesfullly rooted my Nook glowlight, but when I tried to go back to stock with my nook backup I found the backup was not ok (just 77MB) and now I have a bricked NSTG that won't get past the "Install Failed" screen.
I've tried almost every method I could find in the forums, but none worked for me.
Is there anything else beside n2T and Alpha-Format I could try to revive my device?
TIA
I think the most careful way to proceed here is to get a shell going and inspect the damage.
If you were lucky you just wiped out the first partition and the partition tables.
Reinstating the partition tables might make undamaged partitions visible.
It's important to preserve the device dependent info on the /rom partition.
If you copy over ClockworkRecovery onto an SD card you should be able to boot that.
Without selecting anything on the menus you should be able to get ADB working.
With an ADB shell you can run fdisk -l /dev/block/mmcblk0
As soon as you can get access to /rom I'd suggest that you back that up.
I'm sure somebody has other ways to get shell access.
Renate NST said:
I think the most careful way to proceed here is to get a shell going and inspect the damage.
If you were lucky you just wiped out the first partition and the partition tables.
Reinstating the partition tables might make undamaged partitions visible.
It's important to preserve the device dependent info on the /rom partition.
If you copy over ClockworkRecovery onto an SD card you should be able to boot that.
Without selecting anything on the menus you should be able to get ADB working.
With an ADB shell you can run fdisk -l /dev/block/mmcblk0
As soon as you can get access to /rom I'd suggest that you back that up.
I'm sure somebody has other ways to get shell access.
Click to expand...
Click to collapse
thanks for that I'll give it a try...
Sadly, I'm on a W7 box (not mine) and all I can see in the device manager is a nook with a yellow sign in it
ADB devices returns a blank list....
I tried updating the drivers for the nook: first uninstalled anything nooklike with usbdeview, and then pointed W7 to a folder where I had downloaded usbdrivers from this thread http://forum.xda-developers.com/showthread.php?t=1354487 but W7 keeps telling there are no drivers for nook in that folder.
If I boot without SD then the nook is recognized and USB drivers install fine. It's booting with CWM that the device is not recognized.
Stuck
There are drivers and drivers.
As a composite USB device the Nook uses both the stock Windows Mass Storage driver and the Google ADB driver.
See: http://forum.xda-developers.com/wiki/BN_Nook_Simple_Touch/Installing_ADB
Renate NST said:
There are drivers and drivers.
As a composite USB device the Nook uses both the stock Windows Mass Storage driver and the Google ADB driver.
See: http://forum.xda-developers.com/wiki/BN_Nook_Simple_Touch/Installing_ADB
Click to expand...
Click to collapse
It worked:
D:\nook_root\adbshell>adb devices
List of devices attached
11223344556677 recovery
D:\nook_root\adbshell>adb shell
~ # fdisk -l /dev/block/mmcblk0
fdisk -l /dev/block/mmcblk0
Disk /dev/block/mmcblk0: 1958 MB, 1958739968 bytes
4 heads, 16 sectors/track, 59776 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Device Boot Start End Blocks Id System
~ #
completely noob with the nook, can't seem to find /rom and Win32DiskImager does not find a device to read from to perform said backup
The best bet would be to check with somebody with a Glow to see if the partitioning is the same as the Touch.
They could have even changed the exact size of partitions over time for the same model.
In any case, here are my partitions. You might try partitioning and not formatting and see if all the pieces fit properly.
Code:
Disk /dev/block/mmcblk0: 1958 MB, 1958739968 bytes
128 heads, 32 sectors/track, 934 cylinders
Units = cylinders of 4096 * 512 = 2097152 bytes
Partition Format Id Start End Size (bytes) Mount
--------- ------ -- ----- --- ------------- --------
Total 0 933 1,958,739,968
mmcblk0p1 vfat 0c 1 38 79,691,776 /boot
mmcblk0p2 vfat 0c 39 46 16,777,216 /rom
mmcblk0p3 ext2 83 47 141 199,229,440 /factory
mmcblk0p4 05 142 926 1,646,264,320
mmcblk0p5 ext2 83 142 285 301,989,888 /system
mmcblk0p6 vfat 0c 286 405 251,658,240 /media
mmcblk0p7 ext3 83 406 525 251,658,240 /cache
mmcblk0p8 ext3 83 526 926 840,957,952 /data
Unused 927 933 14,680,064
Renate NST said:
The best bet would be to check with somebody with a Glow to see if the partitioning is the same as the Touch.
They could have even changed the exact size of partitions over time for the same model.
In any case, here are my partitions. You might try partitioning and not formatting and see if all the pieces fit properly.
Code:
Disk /dev/block/mmcblk0: 1958 MB, 1958739968 bytes
128 heads, 32 sectors/track, 934 cylinders
Units = cylinders of 4096 * 512 = 2097152 bytes
Partition Format Id Start End Size (bytes) Mount
--------- ------ -- ----- --- ------------- --------
Total 0 933 1,958,739,968
mmcblk0p1 vfat 0c 1 38 79,691,776 /boot
mmcblk0p2 vfat 0c 39 46 16,777,216 /rom
mmcblk0p3 ext2 83 47 141 199,229,440 /factory
mmcblk0p4 05 142 926 1,646,264,320
mmcblk0p5 ext2 83 142 285 301,989,888 /system
mmcblk0p6 vfat 0c 286 405 251,658,240 /media
mmcblk0p7 ext3 83 406 525 251,658,240 /cache
mmcblk0p8 ext3 83 526 926 840,957,952 /data
Unused 927 933 14,680,064
Click to expand...
Click to collapse
mmmm, a bit risky isn't it ?
I think I'll read the rest of the internets before proceeding I need to understand this.....
thanks again
srgarfi said:
mmmm, a bit risky isn't it ?
Click to expand...
Click to collapse
Well, you don't have anything at all in your partition table, not even the correct CHS.
If you tried this configuration and you can't mount the partition, then no harm is done.
It will only mount if the partition formatting makes sense.
Renate NST said:
If you tried this configuration and you can't mount the partition, then no harm is done.
It will only mount if the partition formatting makes sense.
Click to expand...
Click to collapse
Oh, ah, that changes everything! It's worth a try.
I need to find a dummy guide to perform this operations, any clues?
Edit: Found this, looks like a start http://forum.xda-developers.com/showthread.php?t=1279091
thanks again
booted in gparted live and took a peek at the Nook. This is what I found (sorry I don't know yet how to post images):
Device information
Model: B&N Ebook Disk
Size: 182 GiB
Path: /dev/sdb
Partition table: msdos
Heads: 255
Sectors/track: 63
Cylinders: 238
Total sectors: 3825664
Sector size: 512
Physical characteristics being so different I'm affraid trying to convert heads/cylinders from Renate's Touch to my Glo schema would be useless.
Could someone with a NSTG please share partition information?
Thank you all,
srgarfi said:
Physical characteristics being so different...
Click to expand...
Click to collapse
Well, they are not real physical differences.
You can juggle heads and sectors/track as long as the size of a cylinder stays the same.
It may be that the Glow has gone to a bigger cylinder, but it's suspicious that it's not a power of two.
Renate NST said:
You can juggle heads and sectors/track as long as the size of a cylinder stays the same.
Click to expand...
Click to collapse
Not good at math, I can't get an exact match
Here is a script that will partition your Nook internal SD card like the listing above.
You can either copy this to the SD card, chmod 777 it and run it
or just copy and paste it to the Windows command line window running ADB.
Then you can try some mounts and see what you've got.
(nookpart.sh is zipped.)
was about to try the script (thanks again!) but nook is stuck at "rooted forever" screen and nothing I do awakes it: power on, power on 30 sec, power on and n, plug it to pc, and every combination. Took off the sd and tried combinations again, nothing. I've searched a bit and all other cases resumed to reboot by pressing long power. Not this one....no hard reset available? Every piece of equipment must have a big red switch =)
Should I stop messing around and buy another one? (not in the states anymore, it will take like 40+ days to deliver here...)
EDIT: false alarm, battery was too low to power on. Where did the full charge go? I dunno....30 more minutes before I can try
Renate NST said:
Here is a script that will partition your Nook internal SD card like the listing above.
You can either copy this to the SD card, chmod 777 it and run it
or just copy and paste it to the Windows command line window running ADB.
Then you can try some mounts and see what you've got.
(nookpart.sh is zipped.)
Click to expand...
Click to collapse
Executed the script:
Code:
D:\nook_root\adbshell>adb shell sh /sdcard/nookpart.sh
Command (m for help): Command action
e extended
p primary partition (1-4)
Partition number (1-4): First cylinder (1-934, default 1): Using default value 1
Last cylinder or +size or +sizeM or +sizeK (1-934, default 934):
Command (m for help): Command action
e extended
p primary partition (1-4)
Partition number (1-4): First cylinder (39-934, default 39): Using default value
39
Last cylinder or +size or +sizeM or +sizeK (39-934, default 934):
Command (m for help): Command action
e extended
p primary partition (1-4)
Partition number (1-4): First cylinder (47-934, default 47): Using default value
47
Last cylinder or +size or +sizeM or +sizeK (47-934, default 934):
Command (m for help): Command action
e extended
p primary partition (1-4)
Selected partition 4
First cylinder (142-934, default 142): Using default value 142
Last cylinder or +size or +sizeM or +sizeK (142-934, default 934):
Command (m for help): First cylinder (142-926, default 142): First cylinder (142
-926, default 142): Using default value 142
Last cylinder or +size or +sizeM or +sizeK (142-926, default 926):
Command (m for help): First cylinder (286-926, default 286): First cylinder (286
-926, default 286): Using default value 286
Last cylinder or +size or +sizeM or +sizeK (286-926, default 926):
Command (m for help): First cylinder (406-926, default 406): First cylinder (406
-926, default 406): Using default value 406
Last cylinder or +size or +sizeM or +sizeK (406-926, default 926):
Command (m for help): First cylinder (526-926, default 526): First cylinder (526
-926, default 526): Using default value 526
Last cylinder or +size or +sizeM or +sizeK (526-926, default 926):
Command (m for help): Partition number (1-8): Hex code (type L to list codes): C
hanged system type of partition 1 to c (Win95 FAT32 (LBA))
Command (m for help): Partition number (1-8): Hex code (type L to list codes): C
hanged system type of partition 2 to c (Win95 FAT32 (LBA))
Command (m for help): Partition number (1-8): Hex code (type L to list codes): C
hanged system type of partition 6 to c (Win95 FAT32 (LBA))
Command (m for help): Partition number (1-8):
Command (m for help):
Disk /dev/block/mmcblk0: 1958 MB, 1958739968 bytes
128 heads, 32 sectors/track, 934 cylinders
Units = cylinders of 4096 * 512 = 2097152 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 * 1 38 77808 c Win95 FAT32 (LB
A)
/dev/block/mmcblk0p2 39 46 16384 c Win95 FAT32 (LB
A)
/dev/block/mmcblk0p3 47 141 194560 83 Linux
/dev/block/mmcblk0p4 142 926 1607680 5 Extended
/dev/block/mmcblk0p5 142 285 294896 83 Linux
/dev/block/mmcblk0p6 286 405 245744 c Win95 FAT32 (LB
A)
/dev/block/mmcblk0p7 406 525 245744 83 Linux
/dev/block/mmcblk0p8 526 926 821232 83 Linux
Command (m for help): The partition table has been altered.
Calling ioctl() to re-read partition table
D:\nook_root\adbshell>
From CWM tried to mount /boot and failed. Took off the SD, booted nook (fingers crossed) and it displayed the "install failed" screen.
Nice try, thanks for the patience :good:
No, that's what I expected.
The partitioning worked fine
You had already bashed the boot partition.
Now try:
Code:
mkdir /rom
mount -t vfat /dev/block/mmcblk0p2 /rom
ls -l /rom
Looks like there was already a /rom
Code:
D:\nook_root\adbshell>adb shell
~ # mkdir /rom
mkdir /rom
mkdir: can't create directory '/rom': File exists
~ # mount -t vfat /dev/block/mmcblk0p2 /rom
mount -t vfat /dev/block/mmcblk0p2 /rom
mount: mounting /dev/block/mmcblk0p2 on /rom failed: Device or resource busy
~ # ls -l /rom
ls -l /rom
-rwxrwxrwx 1 root root 1088 Jan 1 02:30 bcb
drwxrwxrwx 2 root root 2048 Jan 1 02:30 devconf
~ #
Hmm, I thought of that at the last moment.
Code:
mkdir /stuff
mount -t vfat /dev/block/mmcblk0p2 /stuff
ls -l /stuff
Renate NST said:
Hmm, I thought of that at the last moment.
Code:
mkdir /stuff
mount -t vfat /dev/block/mmcblk0p2 /stuff
ls -l /stuff
Click to expand...
Click to collapse
yes, works, but I don't get it?
Code:
~ # mkdir /stuff
mkdir /stuff
~ # mount -t vfat /dev/block/mmcblk0p2 /stuff
mount -t vfat /dev/block/mmcblk0p2 /stuff
~ # ls -l /stuff
ls -l /stuff
-rwxrwxrwx 1 root root 1088 Jan 1 02:30 bcb
drwxrwxrwx 2 root root 2048 Jan 1 02:30 devconf
~ #
in the meantime I booted noogie and did a backup of the semibricked nook just in case.... =)
Now I'll write CWM to the SD and boot again
That means that the partitioning is correct and that your /rom is intact.
Make a good backup of your personalized stuff:
Code:
adb pull /stuff
Now you have to fix up the boot partition.
I'd probably try to install the factory.zip
Code:
mkdir /fact
mount -t ext2 /dev/block/mmcblk0p3 /fact
ls -l /fact
Code:
adb pull /fact/factory.zip
adb pull /fact/rombackup.zip
Then copy factory.zip to the external SD card and do a CWR update with that.
This all started out in a Glowlight 4 (7.8", 2019) thread: https://forum.xda-developers.com/nook-touch/general/glowlight-plus-7-8-2019-t3934677
An SD card was soldered to test points on the circuit board of a Glow4 to allow for extra storage.
Since it looks like this same technique should work on Glow2 & Glow3 I've broken the thread out here.
The Glow4 has test points labelled by function and has been tested and proven to work with SD cards.
http://www.temblast.com/blogs/glow4/blog.htm#sdcard
The Glow3 has test points labelled by function and has not yet been tested.
The Glow2 has test points, but they are not labelled by function.
I will try to "wiggle" out the pinout soon.
Since the only difference between the models will only be wiring, I suspect that the bulk of this thread will be on configuration and use.
I wiggled the Glow2, the pinout for SD2 is:
TP159 D0
TP160 D1
TP161 D2
TP162 D3
TP163 Cmd
TP164 Clk
TP165 /CD
TP165 VDD
TP167 Gnd
The Glow3, while it's labelled, seems to be on SD3, which is not configured.
I'm still looking at this.
Thanks! I look forward learning more about mounting the sdcard and editing fstab etc.
One more question: Does this method have any restriction on the size of the sdcard and how it's formated? Many old(er) android devices with external storage can only take sdcard of size up to 32Gb, and (independent of that) sometimes people are told to format the sdcard using the device itself, but other times we're suppose to format it in advance (fat32? ext4?).
THANKS!
case-sensitive said:
Does this method have any restriction on the size of the sdcard and how it's formated?
Click to expand...
Click to collapse
This is not so much a method as simply putting in an option that they couldn't be bothered with.
I don't have anything bigger than 16GB on hand.
32GB is the limit for SD 2.0 spec.
Most of the 4GB to 16 GB cards that I have tried are SD 3.0 spec.
You can see this with mmcinfo in uboot.
Formatting things VFAT is only useful if you want to use UMS.
I wouldn't recommend that, VFAT is old and stupid and there are issues with timezones on timestamps.
ext2 is kind of the logical choice.
mkfs.ext2 is included in busybox for formatting.
TLDR: This works on the Glow2 & Glow4 relatively easily.
On the Glow3 you'd need to sacrifice the WiFi to make it work. This works on the Glow3, but you need a modified kernel and a hwcfg change.
http://www.temblast.com/blogs/glow2/blog.htm
http://www.temblast.com/blogs/glow3/blog.htm
http://www.temblast.com/blogs/glow4/blog.htm
Apparently there is already a default place for external SD cards: /mnt/media_rw/extsd
This has a link from /storage/extsd
Since the directory already exists you don't need to modify /init.rc
If you want to use vfat formatted disks and have them hot swappable you don't even have to modify /fstab.E70Q50
My choice is to use an ext2 formatted disk and since it will be internal and not swappable, I don't need or want vold, the volume daemon.
You need to tweak /fstab.E70Q50 (get rid of any line that mentions "extsd").
Code:
/dev/block/mmcblk1p1 /mnt/media_rw/extsd ext2 defaults defaults
You can split the SD card into separate partitions if you want.
You'd have to add some more entries in /fstab.E70Q50 and some mkdirs in /init.rc
For partitioning/formatting cards:
Code:
# busybox fdisk /dev/block/mmcblk1
d [color=red]<-- delete partition[/color]
n [color=red]<-- new partition[/color]
w [color=red]<-- actually write the changes[/color]
#busybox mkfs.ext2 /dev/block/mmcblk1p1
Be very careful when you are talking about mmcblk? and mmcblk?p?
case-sensitive said:
Many old(er) android devices with external storage can only take sdcard of size up to 32Gb...
Click to expand...
Click to collapse
Code:
[email protected]_6sl:/ # df
Filesystem Size Used Free Blksize
...
/mnt/media_rw/extsd 114.4G 20.0K 114.4G 4096
...
[email protected]_6sl:/ # mount
...
/dev/block/mmcblk1p1 /mnt/media_rw/extsd ext2 rw,relatime,errors=continue 0 0
On the Glow2 I ran into a hiccup.
I soldered some 30 gauge wire directly to the micro SD card.
The SD2 is there and fine, but the NtxHwCfg (at least on mine) had to be patched.
Code:
# dd if=/dev/block/mmcblk0 of=/sdcard/hwcfg skip=1024 count=1
This will get you a 512 byte file.
Look at the byte at hex address 0x4f
For the SD card to work this value must be 0x02 (it was 0x00 on mine)
Be very careful modifying the file and writing it back to the internal SD:
Code:
# dd if=/sdcard/hwcfg of=/dev/block/mmcblk0 seek=1024 count=1
Hey! It says "skip" in the first example and "seek" in the second. I warned you!
Well, more sloppiness on NTX/B&N's part.
*.rc files are organized by board names
Usually they shovel the files into the ramdisk.
This means that you have bunches of useless files that aren't used by your hardware.
The Glow2 is a E60QD0 board, the Glow3 is a E60QQ0 board, the Glow4 is a E70Q50 board.
The init.<board>.rc file should load the fstab.<sameboard> file.
On the Glow2 (at least mine) they did sloppy copy/paste and the init.E60QD0.rc loads fstab.E60Q50
I edited init.E60QD0.rc to load fstab.E60QD0
(Then made sure that fstab.E60QD0 had the correct contents.)
Likewise, init.<board>.usb.rc is sloppy.
They don't use the approved syntax of ${ro.serialno}, but instead use $ro.serialno
I get tired of the warnings in the console log.
Also, a lot of redundant junk (the VID/PID stuff can be moved to the "on boot" section).
If you are using a Glow2 and you just installed the 5.0 update and you had previously modified the hwcfg,
then you will have to set it back to the original version to allow the added SD card to work properly.
See: https://forum.xda-developers.com/showpost.php?p=80114208&postcount=623
I had previously said that an SD card and WiFi were not compatible on the Glow3.
It turns out that it's a bit more complicated.
SD2 is the WiFi interface.
SD3 goes to the test points.
The software currently has the WiFi enable/disable switching the SD3 interface, which is wrong.
I've got the hardware itself working
Code:
eBR-1A # mmcinfo
Device: FSL_USDHC
Manufacturer ID: 27
OEM: 5048
Name: SD32G
Tran Speed: 25000000
Rd Block Len: 512
SD version 3.0
Clock: 50000000
High Capacity: Yes
Capacity: 31104958464 Bytes
Bus Width: 4-bit
Boot Partition for boot: No boot partition available
Now I just have to fix the software.
Ok, so I've patched the kernel to make this work on the Glow3.
This also needs a change to the ntxcfg. You can do that with dd or some other tool.
Is anybody ready for this? Do you have the soldering iron warmed up?
Code:
/mnt/media_rw/extsd 28.5G 20.0K 28.5G 4096
I've got to make a version of the image without my stuff in it.
I usually don't like heavily modded images.
The one thing I put in is a rooted adbd.
So, who's ready for the glow3?
You need a new kernel.
If you have access to fastboot you can test drive it with "fastboot boot p1mod.img".
Later you can "fastboot flash boot p1mod.img" to make it permanent.
If you don't (and you're brave and have a good recovery) you can "dd if=p1mod.img of=/dev/block/mmcblk0p1"
You will need to patch the NTX hwcfg.
If this is patched but you are still running the old kernel the WiFi will probably not work, but the glow3 will still be functional.
Code:
# dd if=/dev/block/mmcblk0 skip=1024 count=1 of=/sdcard/hwcfg
[color=red]Use your favorite hex file editor either on of off the glow3 to change address 0x4f from 0x02 to 0x00.
modfile hwcfg 4f 00[/color]
# dd if=/sdcard/hwcfg seek=1024 count=1 of=/dev/block/mmcblk0
If you have access to the u-boot command line you can do it there instead:
Code:
eBR-1A # mmc read 910000 400 1
MMC read: dev # 0, block # 1024, count 1 ... 1 blocks read: OK
eBR-1A # mm.b 91004f
0091004f: 02 ? 00
00910050: 01 ? q
eBR-1A # mmc write 910000 400 1
MMC write: dev # 0, block # 1024, count 1 ... 1 blocks write: OK
eBR-1A #
So, if you get through with all this and reboot it should boot up just fine.
There is a rooted adbd in there so that should not be a problem.
The fstab has been modified to mount your new SD card.
Since that is probably still the original filesystem it will not mount correctly.
You can do an "ls -l /dev/block" and see both mmcblk1 and mmcblk1p1.
You probably noticed that your old /sdcard is empty.
This is an artifact of the fstab not finishing and therefore the nonencrypted is not triggered nor the late_start.
Just do a "start sdcard" and the /sdcard will populate.
So now, just do a "busybox fdisk /dev/block/mmcblk1" to repartition and a "busybox mke2fs /dev/block/mmcblk1p1".
The fstab presumes ext2, a reasonable choice for something used as big storage. If not, just change it.
Reboot and everything should be good.
Good luck.
I've been talking about the NTX hardware configuration, but I don't think that I mentioned or released the utility that I use to dump it.
Availible in the signature, there is NtxHwCfg which can dump or compare NTX configurations.
There is a version for Win32 and one for Android.
http://www.temblast.com/android.htm
It's interesting that the B&N updates don't modify the NTX config.
The Glow2 has version 2.5 vs. the Glow3 with 2.8 vs. the Glow4 with 3.1!
So that means that the u-boots all have to be different.
Code:
C:\>ntxhwcfg hwcfg3 hwcfg4
0b Version 2.8 3.1
0f Size 65 70
10 PCB E60QQ0 (69) E70Q50 (84)
12 AudioCodec No (0) ALC5672 (6)
14 Wifi RTL8189 (8) RTL8723DS (14)
15 BT No (0) RTL8723DS (8)
17 TouchCtrl neonode_v2 (8) ektf2132 (9)
...