I am unable to download the image as the link expires in 2 hours and at my connection's speed, it'll take about 3.5 hrs to download (1Mbits/second). After 2hrs, the download just pauses and cant be resumed. Any solutions? :-/
I am unable to download the image as the link expires in 2 hours and at my connection's speed, it'll take about 3.5 hrs to download (1Mbits/second). After 2hrs, the download just pauses and cant be resumed. Any solutions? :-/
What do you mean expires? Times out? You might want to get a faster connection.
Yes, times out. The link is alive only for 2 hours after it has been activated by clicking 'download'. Whether the download is active or not, it expires in 2 hours.
This is the fastest connection one can get in my area. :-/
Cant it be mirrored somewhere else? Or torrented?
Aargh. Still unable to boot. I tried turning nook on with/without usb plugged in. I'm still getting the cardboard box, which lingers 10 secs or so before going blank. I checked the sd card in root explorer on my phone to make sure i really did flash the image onto the card.
I tried booting into recovery a few days ago to do CM7, and had an error message (with triangle). Tried to install cwm (was sure I installed it at root months ago?) thru rom manager and things went downhill fast.
Any ideas before I give up and take Barnes & Noble up on my warranty? I hate to have to resort to running it over to return it lol.
This package does not show bauwks boot.. the screen should be black.
Adam, thanks for input but what does this mean to my situation? That bauwks boot refers to the cardboard box? I get that I shouldn't see that at all.
C64assembly -
Thanks for input, I used the windows method in post 1 as it is much less work than installing ubuntu 11 via usb. I actually am trying ubuntu method now, very unsuccessfully so far. It does not see my wireless adapter to download the "adam" file so I decided to copy it over instead from a dif usb drive. It till not let me copy the file to it, says there's not enough space. Still not willing to give up just yet....
#! /bin/bash
mkfifo Input
mkfifo Output
#Redirect commandline input from fifo to parted, Redirect output to fifo, background
cat Input &| - parted print >Output &
Line=""
while [ 1 ]
do
while read Line
do
if [ $Line == *Yes\/No\?* ]; then
echo "yes">Input
fi
if [ $Line == *Fix\/Ignore/\Cancel\?* ]; then
echo "fix">Input
fi
if [ $Line == *Fix\/Ignore\?* ]; then
echo "fix">Input
fi
test $Line == *userdata* && break
done<Output
test $Line == *userdata* && break
done
~ # parted /dev/block/mmcblk0 print
parted /dev/block/mmcblk0 print
Warning: /dev/block/mmcblk0 contains GPT signatures, indicating that it has a
GPT table. However, it does not have a valid fake msdos partition table, as it
should. Perhaps it was corrupted -- possibly by a program that doesn't
understand GPT partition tables. Or perhaps you deleted the GPT table, and are
now using an msdos partition table. Is this a GPT partition table?
Yes/No? yes
yes
yes
Error: The backup GPT table is not at the end of the disk, as it should be.
This might mean that another operating system believes the disk is smaller.
Fix, by moving the backup to the end (and removing the old backup)?
Fix/Ignore/Cancel? fix
fix
fix
Warning: Not all of the space available to /dev/block/mmcblk0 appears to be
used, you can fix the GPT to use all of the space (an extra 569312 blocks) or
continue with the current setting?
Fix/Ignore? fix
fix
fix
Model: MMC SEM16G (sd/mmc)
Disk /dev/block/mmcblk0: 15.9GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 131kB 262kB 131kB xloader
2 262kB 524kB 262kB bootloader
3 524kB 16.3MB 15.7MB recovery
4 16.8MB 33.6MB 16.8MB boot
5 33.6MB 83.9MB 50.3MB rom
6 83.9MB 134MB 50.3MB bootdata
7 134MB 522MB 388MB factory
8 522MB 1164MB 642MB system
9 1164MB 1611MB 447MB cache
10 1611MB 2684MB 1074MB media
11 2684MB 15.6GB 12.9GB userdata
If you see "Bauwks box" displayed on screen, let me know the test worked! if not, let me know so I can go back to the drawing board.
#! /bin/bash
export DISPLAY=:0
Timer=100
while [ $Timer -gt 0 ]
do
(( --Timer ))
(( --Timer ))
if [ $Timer -lt 7 ]; then
kill $zpid
zenity --info --text="Final Countdown to flash: $Timer"&
zpid=$!
else
kill $zpid
zenity --info --text="Flashing will commense in $Timer\n seconds, press and hold power for 10 seconds to cancel"&
zpid=$!
fi
sleep 2
done
kill $zpid
zenity --progress --text="writing all zeros to MLO" --percentage=0 &
zpid=$!
dd if=/dev/zero of=/dev/block/179:1
kill $zpid
zenity --progress --text="flashing MLO" --percentage=1 &
zpid=$!
dd if=/root/ddbackup/mmcblk0p1 of=/dev/block/179:1
kill $zpid
zenity --progress --text="writing all zeros to U-BOOT" --percentage=2 &
zpid=$!
dd if=/dev/zero of=/dev/block/179:2
kill $zpid
zenity --progress --text="flashing U-BOOT" --percentage=6 &
zpid=$!
dd if=/root/ddbackup/mmcblk0p2 of=/dev/block/179:2
kill $zpid
zenity --progress --text="writing all zeros to RECOVERY" --percentage=8 &
zpid=$!
dd if=/dev/zero of=/dev/block/179:3
kill $zpid
zenity --progress --text="flashing RECOVERY " --percentage=12 &
zpid=$!
dd if=/root/ddbackup/mmcblk0p3 of=/dev/block/179:3
kill $zpid
zenity --progress --text="writing all zeros to BOOT" --percentage=15 &
zpid=$!
dd if=/dev/zero of=/dev/block/179:4
kill $zpid
zenity --progress --text="flashing BOOT" --percentage=19 &
zpid=$!
dd if=/root/ddbackup/mmcblk0p4 of=/dev/block/179:4
kill $zpid
zenity --progress --text="writing all zeros to BOOTDATA" --percentage=21&
zpid=$!
dd if=/dev/zero of=/dev/block/179:6
kill $zpid
zenity --progress --text="flashing BOOTDATA" --percentage=23 &
zpid=$!
dd if=/root/ddbackup/mmcblk0p6 of=/dev/block/179:6
kill $zpid
mkdir /root/bootdata
umount /dev/block/179:6
mount -t vfat /dev/block/179:6 /root/bootdata
echo -n '0000' > /root/bootdata/BootCnt
zenity --progress --text="writing all zeros to FACTORY" --percentage=50&
zpid=$!
dd if=/dev/zero of=/dev/block/179:7
kill $zpid
zenity --progress --text="flashing FACTORY" --percentage=60 &
zpid=$!
dd if=/root/ddbackup/mmcblk0p7 of=/dev/block/179:7 bs=4096 count=50000
kill $zpid
zenity --progress --text="Contiuning flashing FACTORY" --percentage=60 &
dd if=/root/ddbackup/mmcblk0p7 of=/dev/block/179:7 bs=4096 skip=50000 seek=50000
kill $zpid
zpid=$!
zenity --progress --text="Syncing filesystem data" --percentage=70&
zpid=$!
sync
kill $zpid
zenity --progress --text="writing all zeros to SYSTEM" --percentage=75&
zpid=$!
dd if=/dev/zero of=/dev/block/179:8
mkfs.ext4 /dev/block/179:8
kill $zpid
zenity --progress --text="writing all zeros to RECOVERY LOG" --percentage=80&
zpid=$!
dd if=/dev/zero of=/dev/block/179:9
umount /dev/block/179:9
mkfs.ext4 /dev/block/179:9
kill $zpid
zenity --progress --text="writing all zeros to SDCARD" --percentage=90&
zpid=$!
dd if=/dev/zero of=/dev/block/179:10
kill $zpid
umount /dev/block/179:6
mkfs.vfat -F 32 /dev/block/179:10
sync
zenity --info --text="Press and hold power,\n when the screen goes blank,\n remove your sdcard"&
If you see a box, youre not booting it. Youre booting something else.
I have installed this and it seems to have installed correctly but now it hangs at the white screen that displays the nook n and read forever
---------- Post added at 06:42 PM ---------- Previous post was at 05:46 PM ----------
I noticed that mine is missing line 11, could that be the reason no matter what rom or recovery I use hangs and or boot loops?
cd ~/Downloads
tar -xvwzf ./AdamOutlerUbuntuTotalReFlash.tar.gz
ls /dev/sd?
sudo dd if=./AdamOutlerUbuntuTotalReFlash of=/dev/sdc bs=4096; sync
cd ~/Downloads
tar -xvwzf ./AdamOutlerUbuntuTotalReFlash.tar.gz
ls /dev/sd?
sudo dd if=./AdamOutlerUbuntuTotalReFlash of=/dev/sdc
I've tried several. The problem is in configuration. I eventually settled for the stock 2.6 android_4430BN_defconfig. It seems to function best for this until we have a proper 3.0 kernel.
Thats what this does. It reverts you to 1.4.0. It uses Ubuntu as a dedicated recovery. If you would like to dual boot, just remove the /root/recovery file. You can boot Ubuntu or normal by inserting and removing the sdcard. But like i said, the touchscreen is wonkey and there's no way to fix most of the problems without a 3.0 kernel.Thanks Adam very nice work. Question what if we want to revert to 1.4.0 or 1.4.0 is it possible or we will be stick it lol. Can this be supported for dual/multi boot?
~ Veronica
Sent from XDA premium using my Nook Tablet
Very good work Adam.
I have one trivial question... Why on all your projects do you use Ubuntu and not any other distro?