Related
I ported my automatic boot image modifier from Linux/Ubuntu to Windows. As with the Ubuntu version, my auto-modifier redirects ROM filesystem mounts from emmc (internal memory) to SD card (external memory) in the boot image to more quickly boot a ROM hosted on SD.
Features
Simple, lightweight install. No need to separately install Cygwin and required packages.
As with the Ubuntu version, the boot image ramdisk directory is automatically modified to redirect filesystem mounts for /system, /cache and /data from emmc to SD card so you can quickly boot a ROM hosted on SD. No other changes are made, though the Perl code can be altered as necessary to further modify ramdisk.
Tested working on XP using NottachTrix 1.3.1 AT&T boot image file. For Win 7, you may need to tweak User Access Control (UAC) to launch Cygwin.
Note: The unpacker script is just a copy of “split_bootimg.pl“ found here: http://www.enck.org/tools.html (Thanks Bill.)
Instructions
1. Download cygwin-auto-modify-boot.zip (50MB) here: http://www.mediafire.com/?kz9fqzwznzizb1z
2. Unzip files to Windows c:\ . OR, if you already have a fully functioning c:\cygwin build that contains the Perl v5.14.2, cpio and gunzip binaries, you should only need to extract the directory: cygwin\home\modify-boot to c:\. In any event, you should backup your existing c:\cygwin directory prior to unzipping.
3. Copy the original boot image file (boot.img in this example) to c:\cygwin\home\modify-boot
4. Navigate to c:\cygwin and launch c:\cygwin\cygwin.bat . This opens a cygwin command window, and also generates a set of user configuration files if opened for the first time.
5. In the Cygwin command window, enter: cd ../modify-boot . Here is my directory listing after Cygwin configured my system:
6. In the Cygwin command window, enter the command: ./modify-boot.sh boot.img and press Enter at the prompts. For me, the entire process took ~30 seconds to modify a NottachTrix boot image.
If everything goes right, the system creates a “boot-repack.img” file based on the modified ramdisk and stores it in the modify-boot directory. Various log/debug data are presented on screen and stored in the modify-boot directory.
That’s all! From here you can “fastboot flash boot boot-repack.img” to boot your SD-based ROM, or store the modified image in a boot configuration directory. See http://forum.xda-developers.com/showthread.php?t=1645344
Please note: The size of my dev team has never exceeded one (me); yet I will try to field requests for help as I am able.
References and Credits
http://cygwin.com/install.html
http://www.enck.org/tools.html
http://forum.xda-developers.com/showthread.php?t=1630130
+++++
Linux/Ubuntu Version
Many have studied this excellent tutorial on how to unpack, modify and repack Android ROM boot images: http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images. Its contents form a solid baseline for customizing ROM boot images and ROMs in general. Here I attempt to automate the process of modifying boot images.
Results thus far provide an efficient means of booting ROMs that are cloned to SD card (see my clone thread: http://forum.xda-developers.com/showthread.php?t=1764680 ), as shown in the example below.
modify-boot zip: http://www.mediafire.com/?luobv279pcv827k contains five files: three Perl scripts to unpack, modify and repack a boot image, the “mkbootimg” executable, and an executive batch file to run the three Perl scripts in sequence.
Boot image modifier script: modify-bootimg-atrix.pl features a useful example of how customizations can be pre-programmed by including code to redirect ROM filesystem mounts to SD card, thus enabling us to boot SD card-based ROMs --- almost on the fly.
Of course there are many references to customizing boot images, but to my knowledge this is the first published attempt to automate the process. And since there are some interesting projects related to hosting Perl on Android (see References below), I think it would be fun to develop a CWM-flashable zip (or similar tool) that loads a Perl script interpreter and then runs a pre-programmed boot image modifier --- all on phone, without computer aiding.
Preliminaries
Linux-based OS (Ubuntu 12.04 preferred --- it's still free)
Android SDK Platform Tools (includes adb and fastboot)
Perl (Ubuntu 12.04 includes Perl 5.14.2)
Example: Boot Neutrino V2.8 GT cloned to SD card
Suppose we have already cloned Neutrino V2.8 GT ROM (/system, /cache and /data) to SD card. To boot it:
1. Download modify-boot.zip: http://www.mediafire.com/?luobv279pcv827k to Desktop and extract directory: /modify-boot to ~/Desktop
2. Extract boot.img from Neutrino V2.8 GT ROM.zip and drop it in ./modify-boot
3. Open a terminal, get root and cd ~/Desktop/modify-boot
4. Enter: “sh ./modify-boot.sh boot.img” and follow prompts (Output file: boot-repack.img)
5. Boot to fastboot and connect phone to computer
6. fastboot flash boot boot-repack.img
7. fastboot reboot
Once phone is booted, we can run a sanity check by entering:
adb shell (access Android filesystems)
# mount
Results should include the highlighted device names for filesystem mounts:
Code:
[COLOR="Blue"]/dev/block/mmcblk1p2 on /system[/COLOR] type ext4 (rw,noatime,nodiratime,errors=continue,barrier=0,nobh,data=writeback,noauto_da_alloc,discard)
[COLOR="Blue"]/dev/block/mmcblk1p4 on /data[/COLOR] type ext4 (rw,nosuid,nodev,noatime,nodiratime,barrier=0,nobh,data=writeback,noauto_da_alloc,discard)
[COLOR="Blue"]/dev/block/mmcblk1p3 on /cache[/COLOR] type ext4 (rw,nosuid,nodev,noatime,nodiratime,errors=continue,barrier=0,nobh,data=writeback,noauto_da_alloc,discard)
We can now boot a cloned Neutrino V2.8 GT ROM from SD card, and/or save the modified boot image in a safe, visible location on SD card to configure dual boot (please see: http://forum.xda-developers.com/showthread.php?t=1645344 ). Or, we can roll the modified image into a flashable zip for a standalone boot push.
Standard disclaimers apply. In short, I am not responsible for any harm you or your phone may incur by using any or all of this material.
References
http://code.google.com/p/perldroid/
http://code.google.com/p/android-scripting/
http://forum.xda-developers.com/showthread.php?t=1585009
Credits
Many thanks to the Android Community Effort ( http://android-dls.com/wiki/index.php?title=Main_Page ), and to my friend and xda member ghost_og for his “mkbootimg” command-line fix that made boot image repacking work for Atrix.
Boot modifier script: modify-bootimg-atrix.pl includes logic to search both init.rc (Blur) and init.olympus.rc (CM) in ramdisk for ROM filesystem mounts.
Hi,
If you look at my Gobstopper for 2.3.6 I do exactly this kind of thing. I unpack the boot image into kernel and initramfs, modify init.rc, package it up again and flash back to boot. The binaries and source are included if you want to take a look.
Cheers!
Is it possible to modify partitions numbers? because i use different partitions because of webtop2sd and swap partition?
Adam
NFHimself said:
Hi,
If you look at my Gobstopper for 2.3.6 I do exactly this kind of thing. I unpack the boot image into kernel and initramfs, modify init.rc, package it up again and flash back to boot. The binaries and source are included if you want to take a look.
Cheers!
Click to expand...
Click to collapse
Elegant! Does it support multiple command lines? Also, does it support AT&T yet?
sendust7 said:
Elegant! Does it support multiple command lines? Also, does it support AT&T yet?
Click to expand...
Click to collapse
There is nothing Bell specific to it, static linked binaries so no rom dependence. It doesn't do anything about multiple command lines, no, the normal boot/recovery images have any at all, let alone multiple ones.
Cheers!
Is that right?
"5. Boot to fastboot and connect phone to computer
6. fastboot flash boot-repack.img
7. fastboot reboot"
Because my output is like this:
[email protected]:/home/gtmoraes/AtrixCM9/android-sdk-linux/platform-tools# ./fastboot flash boot-repack.img
unknown partition 'boot-repack.img'
error: cannot determine image filename for 'boot-repack.img'
[email protected]:/home/gtmoraes/AtrixCM9/android-sdk-linux/platform-tools#
and, of course, the boot-repack.img is in the same folder of fastboot
---
I've tried fastboot flash boot boot-repack.img. It softbricked
Reflashing the original boot.img de-bricked it without a hassle. Guess your solution is not compatible with Morrisoft CM7 ROM
GTMoraes said:
Is that right?
"5. Boot to fastboot and connect phone to computer
6. fastboot flash boot-repack.img
7. fastboot reboot"
Because my output is like this:
[email protected]:/home/gtmoraes/AtrixCM9/android-sdk-linux/platform-tools# ./fastboot flash boot-repack.img
unknown partition 'boot-repack.img'
error: cannot determine image filename for 'boot-repack.img'
[email protected]:/home/gtmoraes/AtrixCM9/android-sdk-linux/platform-tools#
and, of course, the boot-repack.img is in the same folder of fastboot
---
I've tried fastboot flash boot boot-repack.img. It softbricked
Reflashing the original boot.img de-bricked it without a hassle. Guess your solution is not compatible with Morrisoft CM7 ROM
Click to expand...
Click to collapse
Soft-brick is usually caused by one or more of the following:
1. The three ext partitions required to host ROM on SD card either do not exist, are not big enough or are corrupt.
2. The three ext partitions exist but no ROM is installed
3. ROM is not compatible with phone
4. User does not wait long enough for phone to boot after installing ROM. First boot usually takes 3 to 5 minutes as the phone is building cache. Subsequent boots should not take longer than a minute with a Class 4 or higher SD card.
And yes, the boot command should be: fastboot flash boot {boot-image}
Cheers
I ported my automatic boot image modifier from Linux/Ubuntu to Windows. As with the Ubuntu version, my auto-modifier redirects ROM filesystem mounts from emmc (internal memory) to SD card (external memory) in the boot image to more quickly boot a ROM hosted on SD.
Features
Simple, lightweight install. No need to separately install Cygwin and required packages.
As with the Ubuntu version, the boot image ramdisk directory is automatically modified to redirect filesystem mounts for /system, /cache and /data from emmc to SD card so you can quickly boot a ROM hosted on SD. No other changes are made, though the Perl code can be altered as necessary to further modify ramdisk.
Tested working on XP using NottachTrix 1.3.1 AT&T boot image file. For Win 7, you may need to tweak User Access Control (UAC) to launch Cygwin.
hi, the size from my original boot is 8 megas, after unpack and repack the size is 4.8 megas, and does not work, my boot is from motorola xt928, did you know why change the size,,thanks
Using CM10 from SD Card (Nottachtrix on internal)
For anyone looking to run Nottachtrix (or other rom) from internal memory and CM10 from external. You'll run into the same problem I did. The init.rc and init.olympus.rc files don't contain the partition information. You need to update the fstab.olympus file in the boot.img. I've attached mine for comparison. (note, after repartitioning my SD Card several times I ended up with a phantom partition (mmcblk1p4) therefore my data is actually on mmcblk1p5.
SD card partition sizes:
System: 340mb
Cache: 700mb
Data: 1.25gb
Additional notes about my partitioning experience:
The DD command in linux (and ADB) copies the entire partition exactly to the SD card's partition, therefore you lose space if you leave it this way. I used DD, but then used fsarchiver to backup all of the sd card's partitions, repartitioned the card again, and restored the partition info with fsarchiver. This made my SD card a lot cleaner and avoided wasting any space.
Everything's running great now. Thank you everyone who made dual booting possible!
Would this tool work on Desire HD?
Need some help. I pulled the boot.img created from ROM1 using copy-boot.img (until step 5 here) and when I ran modify-boot.sh on it, I got the below message:
Unpacking boot image...
Found a secondary file after the ramdisk image. According to the spec (mkbootimg.h) this file can exist, but this script is not designed to deal with this scenario.
So, I got the boot-NottachTrix-1.3.1-att-sd-ext.img file from this thread and fastboot flashed it, thinking it is already modified, but my phone didn't boot. Then I tried running modify-boot.sh on it and then realized that it has a binary that won't run on mac.
Could someone tell me if I am on the right track with the 2nd steps above so that I can get hold of a ubuntu machine? I tried running it on a puppy linux livecd and it didn't work.
Why didn't the first step work? Is the boot.img created by the copy-boot.sh not in the right format?
Update: I forgot to mention this, but I have NottachTrix 1.3.1 installed on emmc but the size of the boot.img extracted by copy-boot.sh doesn't match that of the one attached to the above link. The one linked is size 3440640 while the one copy-boot.sh created is of size 8388608. For now, I fastboot flashed the later and got back into ROM1. I meanwhile got a livecd boot of ubuntu and ran modify-boot.sh on the one I downloaded and it created boot-repack.img successfully, but I had no success booting with it either.
irha said:
Need some help. I pulled the boot.img created from ROM1 using copy-boot.img (until step 5 here) and when I ran modify-boot.sh on it, I got the below message:
Unpacking boot image...
Found a secondary file after the ramdisk image. According to the spec (mkbootimg.h) this file can exist, but this script is not designed to deal with this scenario.
So, I got the boot-NottachTrix-1.3.1-att-sd-ext.img file from this thread and fastboot flashed it, thinking it is already modified, but my phone didn't boot. Then I tried running modify-boot.sh on it and then realized that it has a binary that won't run on mac.
Could someone tell me if I am on the right track with the 2nd steps above so that I can get hold of a ubuntu machine? I tried running it on a puppy linux livecd and it didn't work.
Why didn't the first step work? Is the boot.img created by the copy-boot.sh not in the right format?
Update: I forgot to mention this, but I have NottachTrix 1.3.1 installed on emmc but the size of the boot.img extracted by copy-boot.sh doesn't match that of the one attached to the above link. The one linked is size 3440640 while the one copy-boot.sh created is of size 8388608. For now, I fastboot flashed the later and got back into ROM1. I meanwhile got a livecd boot of ubuntu and ran modify-boot.sh on the one I downloaded and it created boot-repack.img successfully, but I had no success booting with it either.
Click to expand...
Click to collapse
I have a newer thread: Dual Boot Atrix: Simplified and Standalone: http://forum.xda-developers.com/showthread.php?t=2124668
which presents my own custom standalone tools to do the following:
Partition SD card
Copy ROM from EMMC to SD
Flash boot image via Atrix Boot Emporium
Flash another ROM of choice to EMMC
No computer required.
On first boot, elapsed time from power-up to welcome screen can be several minutes --- especially for larger ROMs --- as the system is building cache.
Hope this helps
sendust7 said:
I have a newer thread: Dual Boot Atrix: Simplified and Standalone: http://forum.xda-developers.com/showthread.php?t=2124668
which presents my own custom standalone tools to do the following:
Partition SD card
Copy ROM from EMMC to SD
Flash boot image via Atrix Boot Emporium
Flash another ROM of choice to EMMC
No computer required.
On first boot, elapsed time from power-up to welcome screen can be several minutes --- especially for larger ROMs --- as the system is building cache.
Hope this helps
Click to expand...
Click to collapse
Thank you very much! I was able to directly go to the step 4, since I manually copied the partitions already and after verifying that I could boot into the sdcard, used the steps in the "Configuring Dual Boot" thread to get it switch between the two.
It looks like my sdcard is too slow to run android from it, so I will have to find another faster card
I know that you can change the moboot default option but I was curious if it was possible to skip the boot select screen completely and boot straight into Cyanogenmod? I have no reason to boot into WebOS and can boot into recovery via the power option inside Android. It just adds polish to just see the boot splash first when the device is switched on plus it saves a few seconds of waiting around.
Thanks!
I think you could set timeout to 0.
Unfortunately, that just turned off timeout all together.
Anyone have any other ideas?
You could try deleting moboot but I don't recommend it. Might work, might break things.
Sent from my SPH-L710 using Tapatalk 2
Please mind that if your ROM becomes unbootable and you can't boot straight to the recovery, it will be more problematic to fix.
However, I think it is possible. There's a possibility to set the next image to be booted by a text file on the boot partition. I don't remember the exact name and content, but this way android makes the moboot reboot straight to the recovery. Moboot reads the file, boots the desired image and deletes the file. So you would need to create such file for booting the android image and make that file somehow permanent. I don't think changing permissions would be enough, but you could recreate it every (re)boot by some script.
I was going to point out the same thing pojir said above me. Sure, you could boot into recovery from CM9 but if you cant boot into CM9 and are stuck in a boot loop or something, then what? Just set the timer to 1 second and have it boot to CM9 by default. It shouldn't be a big problem to wait 1 second before booting begins.
HELP! my Nook HD+ was working great under 4.3 and after flashing the ROM to 4.4.2, it worked for a few days, and then I think it bricked.
Now, I can't boot the Nook HD+. When I turn on the Nook HD+, it displays the Nook HD+ boot screen, and then it sometime displays the CyanogenMod universal boot screen, but that's how far it will go. It just gets stuck at the Nook HD+ welcome screen or at the CyanogenMod Universal boot screen.
Even if I try to boot from an SD card, the same thing happens.
I cannot even get into CWD to reflash the NookHD+. I am guessing that it is bricked.
I cannot even return it to B&N because I cannot unroot it or reinstall the factory defaults rom (since I cannot get into CWD) and my warranty run out
I did not drop or damage my Nook HD+. The only thing I did was install 4.4.3, and it worked well for a while, and it just stopped suddenly one day when I turned it on.
HELP. Any suggestions? is there a way to fix this when I cannot boot from SD card or enter CWD? Is there a unbricking instruction? is my item really bricked?
I could not find if someone else had already posted a similar thread, so I am sorry if I am duplicating the question. If you know of the other thread, please post link to it here so that I can go there to get help. I am not sure if I am bad at searching previous posts/threads, but I could not find it. But I can't believe no one else had bricked their Nook HD+, so it must be here somewhere. Please help me find it. Thank you.
Others have bricked their devices and could not get it working. But most of those were stuck on the nook screen, not cyanoboot. That meant they could do a warranty exchange. But yours is stuck on cyanoboot and your warranty has expired anyway so I think you are SOL.
If you cannot get it to boot to SD and you replaced the stock recovery with CWM/TWRP, there is nothing you can do.
Sent from my BN NookHD+ using XDA Premium HD app
Have you tried booting to internal recovery? Hold n and power together when booting and releasing power first before n.
Sent from my BN NookHD+ using XDA Premium HD app
rob00 said:
HELP! my Nook HD+ was working great under 4.3 and after flashing the ROM to 4.4.2, it worked for a few days, and then I think it bricked.
Now, I can't boot the Nook HD+. When I turn on the Nook HD+, it displays the Nook HD+ boot screen, and then it sometime displays the CyanogenMod universal boot screen, but that's how far it will go. It just gets stuck at the Nook HD+ welcome screen or at the CyanogenMod Universal boot screen.
Even if I try to boot from an SD card, the same thing happens.
I cannot even get into CWD to reflash the NookHD+. I am guessing that it is bricked.
I cannot even return it to B&N because I cannot unroot it or reinstall the factory defaults rom (since I cannot get into CWD) and my warranty run out
I did not drop or damage my Nook HD+. The only thing I did was install 4.4.3, and it worked well for a while, and it just stopped suddenly one day when I turned it on.
HELP. Any suggestions? is there a way to fix this when I cannot boot from SD card or enter CWD? Is there a unbricking instruction? is my item really bricked?
Click to expand...
Click to collapse
Doesn't really sound like your bricked at all. Your boot gets too far.
Booting from SD is tricky. Try recreating an SD boot image from one of the tutorials.
leapinlar said:
Have you tried booting to internal recovery? Hold n and power together when booting and releasing power first before n.
Sent from my BN NookHD+ using XDA Premium HD app
Click to expand...
Click to collapse
Thank you for the reply. I was not able to get into the internal recovery, even thought I installed CDW into the memory. I was able to do that by pressing n ad power together, and releasing power before the n. but now, it gets stuck on the cynogemod.
Since I can't access my nook HD+ via the SD card or the internal recovery, is there a way to connect the nook HD+ via the USB from my computer and reset everything?
Thanks, I will try the SD card again, re-making a new SD boot card. If it doesn't seem to be bricked, what could it be? could it be that the Cyanogemod got corrupted? or hardware failure?
If I am not able to access my nook HD+ via the SD card or the internal recovery, isn't there a way to connect my nook to my computer via the USB cable and do a clean reset on my nook HD+??
leapinlar said:
Others have bricked their devices and could not get it working. But most of those were stuck on the nook screen, not cyanoboot. That meant they could do a warranty exchange. But yours is stuck on cyanoboot and your warranty has expired anyway so I think you are SOL.
If you cannot get it to boot to SD and you replaced the stock recovery with CWM/TWRP, there is nothing you can do.
Sent from my BN NookHD+ using XDA Premium HD app
Click to expand...
Click to collapse
IF I am really SOL, and there is no way to repair is, is there a re-purposing project I can take to re-purpose my nook HD+? The screen is Retine quality, and I wonder if it can be converted into a monitor for a computer or other use for it. Of course I rather have the nook HD+ back to working android tablet, but if it is truly bricked and SOL, it seems a waste of excellent working Retina screen not to repurpuse it.
There must be a way to connect the Nook HD+ to the computer via the USB cable and factory reset it, not? :'-(
Factory reset via usb cable connection to computer???
Is there a way to flash the internal boot sector of the Nook HD+ by connecting it to the computer via the USB cable?
I can't seem to fix my problem via the SD card or the internal boot sector. USB connection could be my last only hope.
Most of the time my nook HD+ gets stuck at the nook screen. But if I boot by pressing the power and the n key and hold it for a long time in order to enter the internal cynogemboot, that's when it gets stuck at the cynogenboot screen. Does this give any additional clue as to if my Nook is bricked or not?
:'-(
THANK YOU FOR THE INTEREST TO HELP. thank you sooo much.
When you replaced the stock recovery with CWM/TWRP you removed all chances of the device repairing itself. And there is no way to use the USB cable without something to enable ADB. And without a working operating system or recovery, that cannot happen. So unless you can successfully boot to a bootable CWM SD or boot to internal recovery, you cannot repair it. Period.
Sent from my BN NookHD+ using XDA Premium HD app
rob00 said:
Thank you for the reply. I was not able to get into the internal recovery, even thought I installed CDW into the memory. I was able to do that by pressing n ad power together, and releasing power before the n. but now, it gets stuck on the cynogemod.
Click to expand...
Click to collapse
That happened to me a couple days ago after I flashed Succulent's ROM over CM11.
It wouldn't always boot to recovery with the n and power combo, but after trying a few times, it did. Once there, I restored my backup.
So keep trying.
1480
This just happened to me. My Nook was charging and I walked by and it was turned on with the nook logo displayed. Its stuck. If I reboot it just gets stuck on the nook logo. If I reboot holding the n and power button I can get to the cyanoboot splash screen and then it freezes. If I try booting from SD card I get the same boot splash screen and freezes.
I dont get it. It was working fantastic for two days since flashing. It has been charged several times, all I did was try and charge it and its bricked!
CHD Dad said:
This just happened to me. My Nook was charging and I walked by and it was turned on with the nook logo displayed. Its stuck. If I reboot it just gets stuck on the nook logo. If I reboot holding the n and power button I can get to the cyanoboot splash screen and then it freezes. If I try booting from SD card I get the same boot splash screen and freezes.
I dont get it. It was working fantastic for two days since flashing. It has been charged several times, all I did was try and charge it and its bricked!
Click to expand...
Click to collapse
Have you tried other SDs or other versions of CWM? Sometimes the device can be very finicky to boot.
Sent from my BN NookHD+ using XDA Premium HD app
leapinlar said:
Have you tried other SDs or other versions of CWM? Sometimes the device can be very finicky to boot.
Sent from my BN NookHD+ using XDA Premium HD app
Click to expand...
Click to collapse
I have tried 3 different cards and I have tried several versions of CWM including a no-emmc version. All just freeze at the bootloader screen except the no-emmc version. I can load that version but it freezes when trying to progress from the menu. I tried very early versions to the latest and greatest and all freeze.
I've shelved it for now, its not worth the frustration. I almost took a hammer to it last night!
Appreciate the help though! I'll probably try again in a few days when I am not so tempted to toss it out the window.
I have tried your tips in your threads including looking for the no-emmc version.
Thank you everyone who have posted suggestions. I have followed your suggestions left and right. However, I am still stuck with this problem. I tried, and re-tried, and re-tried many, many, many times, with different SD cards, with different versions, including all my past image back ups. Still freezes at the nook boot screen or Cyonogem boot screen. SO frustrating.
I cannot believe that nobody who had this problem were able to find a solution. Specially, has any brilliant hacker figured out how to flash the nook via the USB cord from the computer? Since the nook in problem cannot boot from the internal memory nor the SD Card, the only other way in would be to force a re-flash via the USB cable from the computer. A hard hack, since normally the nook would have to be booted to receive connection from the USB cable from the computer. But if an imaginative hacker could figure a way to force the re-flash via the USB cable, it would be a great feat!
IF there is no solution at all, anyone knows of a way to use the Retina screen from the nook for other purposes? Maybe re-purpose it as a screen for a Raspberry-Pi or an Arduino project? It would probably mean opening up the bricked nook and harvest the beautiful retina screen, but I rather do that than throw away this bricked nook.
URRGGHH!!!
rob00 said:
Thank you everyone who have posted suggestions. I have followed your suggestions left and right. However, I am still stuck with this problem. I tried, and re-tried, and re-tried many, many, many times, with different SD cards, with different versions, including all my past image back ups. Still freezes at the nook boot screen or Cyonogem boot screen. SO frustrating.
I cannot believe that nobody who had this problem were able to find a solution. Specially, has any brilliant hacker figured out how to flash the nook via the USB cord from the computer? Since the nook in problem cannot boot from the internal memory nor the SD Card, the only other way in would be to force a re-flash via the USB cable from the computer. A hard hack, since normally the nook would have to be booted to receive connection from the USB cable from the computer. But if an imaginative hacker could figure a way to force the re-flash via the USB cable, it would be a great feat!
IF there is no solution at all, anyone knows of a way to use the Retina screen from the nook for other purposes? Maybe re-purpose it as a screen for a Raspberry-Pi or an Arduino project? It would probably mean opening up the bricked nook and harvest the beautiful retina screen, but I rather do that than throw away this bricked nook.
URRGGHH!!!
Click to expand...
Click to collapse
Fastboot recovery for Ovation:
http://www.mediafire.com/download/yky70a67davz01l/fastboot_ovation.tar.gz
This is just a continuation of:
http://forum.xda-developers.com/showthread.php?t=2273603
To make a bootable sd, partition fat32 with gparted (or at least with linux, windows partition tools mostly don't work properly), set the boot flag.
Extract the files. Copy MLO first to the SD, and then u-boot.bin and uImage. Test boot the sd, should say "entering fastboot..."
The next step involves your linux host. If you don't have one, try a live USB distro.
Copy the fastboot binary into your path or working directory. You may have to chown it to your user and/or chmod +x.
You will need to place a line in /etc/udev/rules.d/51-android.rules
Code:
SUBSYSTEM=="usb", ATTR{idVendor}=="0451", ATTR{idProduct}=="d022", MODE="0666", GROUP=""
Then you will need to reboot the host or restart udev for the rule to take affect.
Lastly, test fastboot.
Code:
bash-4.2$ fastboot
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
reboot reboot device normally
reboot-bootloader reboot device into bootloader
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address
bash-4.2$ fastboot devices
3024550263104319 fastboot
bash-4.2$ fastboot flash boot boot.img
sending 'boot' (4532 KB)... OKAY
writing 'boot'... OKAY
bash-4.2$ fastboot reboot
rebooting...
bash-4.2$
Edit: Two things I would leave alone for now would be 'update update.zip' and reboot-bootloader. The nook sd boot will give a list of emmc partitions. I would individually repair the ones I thought corrupt. Some need to be left alone..
Jon Lee said:
Fastboot recovery for Ovation:
http://www.mediafire.com/download/yky70a67davz01l/fastboot_ovation.tar.gz
This is just a continuation of:
http://forum.xda-developers.com/showthread.php?t=2273603
To make a bootable sd, partition fat32 with gparted (or at least with linux, windows partition tools mostly don't work properly), set the boot flag.
Extract the files. Copy MLO first to the SD, and then u-boot.bin and uImage. Test boot the sd, should say "entering fastboot..."
The next step involves your linux host. If you don't have one, try a live USB distro.
Copy the fastboot binary into your path or working directory. You may have to chown it to your user and/or chmod +x.
You will need to place a line in /etc/udev/rules.d/51-android.rules
Code:
SUBSYSTEM=="usb", ATTR{idVendor}=="0451", ATTR{idProduct}=="d022", MODE="0666", GROUP=""
Then you will need to reboot the host or restart udev for the rule to take affect.
Lastly, test fastboot.
Code:
bash-4.2$ fastboot
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
reboot reboot device normally
reboot-bootloader reboot device into bootloader
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address
bash-4.2$ fastboot devices
3024550263104319 fastboot
bash-4.2$ fastboot flash boot boot.img
sending 'boot' (4532 KB)... OKAY
writing 'boot'... OKAY
bash-4.2$ fastboot reboot
rebooting...
bash-4.2$
Edit: Two things I would leave alone for now would be 'update update.zip' and reboot-bootloader. The nook sd boot will give a list of emmc partitions. I would individually repair the ones I thought corrupt. Some need to be left alone..
Click to expand...
Click to collapse
Wow, I don't yet know what all this is, but thank you for such a dedicated post. I will get to work and implement your solutions, but I just wanted to thank you before I even start . Thank you, and I will post back here on my progress. Wow, what a glimpse of hope.
rob00 said:
Wow, I don't yet know what all this is, but thank you for such a dedicated post. I will get to work and implement your solutions, but I just wanted to thank you before I even start . Thank you, and I will post back here on my progress. Wow, what a glimpse of hope.
Click to expand...
Click to collapse
did anything work?
---------- Post added at 10:33 AM ---------- Previous post was at 10:25 AM ----------
Jon Lee said:
Fastboot recovery for Ovation:
http://www.mediafire.com/download/yky70a67davz01l/fastboot_ovation.tar.gz
This is just a continuation of:
http://forum.xda-developers.com/showthread.php?t=2273603
To make a bootable sd, partition fat32 with gparted (or at least with linux, windows partition tools mostly don't work properly), set the boot flag.
Extract the files. Copy MLO first to the SD, and then u-boot.bin and uImage. Test boot the sd, should say "entering fastboot..."
The next step involves your linux host. If you don't have one, try a live USB distro.
Copy the fastboot binary into your path or working directory. You may have to chown it to your user and/or chmod +x.
You will need to place a line in /etc/udev/rules.d/51-android.rules
Code:
SUBSYSTEM=="usb", ATTR{idVendor}=="0451", ATTR{idProduct}=="d022", MODE="0666", GROUP=""
Then you will need to reboot the host or restart udev for the rule to take affect.
Lastly, test fastboot.
Code:
bash-4.2$ fastboot
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
reboot reboot device normally
reboot-bootloader reboot device into bootloader
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address
bash-4.2$ fastboot devices
3024550263104319 fastboot
bash-4.2$ fastboot flash boot boot.img
sending 'boot' (4532 KB)... OKAY
writing 'boot'... OKAY
bash-4.2$ fastboot reboot
rebooting...
bash-4.2$
Edit: Two things I would leave alone for now would be 'update update.zip' and reboot-bootloader. The nook sd boot will give a list of emmc partitions. I would individually repair the ones I thought corrupt. Some need to be left alone..
Click to expand...
Click to collapse
i am unable to get mine to boot into recovery with said steps.
cyanoboot was installed on emcc.
fastboot wont boot
recovery wont boot
stuck on cyanoboot screen
any ideas?
Problem: I believe my Fire OS was accidentally deleted in the process described by the video "How to install CM12 1 on the Amazon Fire 5th gen Tablet" by Rootjunky.
I've hit a roadblock in getting my new Kindle Fire 5th Gen. up and running with Cyanogenmod. I will lay a few things out: how I got to this point and what I've tried in attempt to resolve my issue.
After I had TWRP running on my tablet I performed the back-up step, the wipe step and began the installation. During the installation TWRP reported an exception declaring that I did not have enough space to install "open_gapps-arm-5.1-stock-20151122.zip". The only difference between my setup and Rootjunky's was that I had not copied "cm-12.1-20151116-UNOFFICIAL-ford.zip", "open_gapps-arm-5.1-stock-20151122" and "SuperSU-v2.46" to my external SD card but to my internal storage. I decided that this may have been the issue and REMOVED my SD card from my tablet, copied the files to the SD card from my PC and then reinserted the card. I tried to select the .ZIP files in TWRP but it failed to recognize that the card had been reinserted. At this point I selected for the device to reboot (in hopes of it recognizing the card) and all I was met with was the "Amazon" splash screen and no continuing boot load.
To remedy this I have tried:
• To flash via Fastboot but I do not have an unlocked boot loader. When I try to flash it says "not allowed" and if I try to unlock the boot loader using either "fastboot oem unlock" or "fastboot flashing unlock" I get no results. The device is recognized, by the way.
• To upload the original Fire OS from Amazon's website and load it through the adb sideloader. This uploads successfully but the boot is stuck at the animated "Fire" splash screen.
• Attempted to perform a factory reset by using the Amazon System Recovery menu.
• Searched for over 5 hours tonight trying to find a solution.
Overall I believe the question is how do I get my device booted back up so I can restart this process and give it another shot?
Thank you all for the help in advance.
-Skye
Fixed
I decided to try to boot once more before retiring for the night and it just magically began to work.
The "Fire" splash animation displayed as the device began to install system updates.
I would say what worked was installing the Amazon Fire OS via the side loader.
However, I am new to modifying mobile technology and would like to ask a few questions for anyone to answer who should come across this thread.
• What is stored truly as ROM within the device? In other words, is it possible for me to delete enough data that the device would truly become bricked?
• Is it possible to perform a clean wipe and install from an empty storage device? I have dealt with plenty of desktop operating systems and find that a fresh hard drive is the best way to go when introducing a new Linux flavor to a growing build.
I am aware that, with root privileges and 3rd party utilities, that I could clean the system myself. However, it is easier to perform a full wipe and start from scratch.
Thank you all again.
-Skye
CieloLumine said:
I decided to try to boot once more before retiring for the night and it just magically began to work.
The "Fire" splash animation displayed as the device began to install system updates.
I would say what worked was installing the Amazon Fire OS via the side loader.
However, I am new to modifying mobile technology and would like to ask a few questions for anyone to answer who should come across this thread.
• What is stored truly as ROM within the device? In other words, is it possible for me to delete enough data that the device would truly become bricked?
• Is it possible to perform a clean wipe and install from an empty storage device? I have dealt with plenty of desktop operating systems and find that a fresh hard drive is the best way to go when introducing a new Linux flavor to a growing build.
I am aware that, with root privileges and 3rd party utilities, that I could clean the system myself. However, it is easier to perform a full wipe and start from scratch.
Thank you all again.
-Skye
Click to expand...
Click to collapse
The locked bootloader should prevent the device from getting bricked.
There are several partitions in an android device the some of them are: bootloader, recovery, system, data, cache.
System is were the rom is installed, data is your apps, settings and updated system apps.
When you install a new rom, you need to do a factory reset, which wipes data and cache.
You can wipe system, but it is usually wiped as part of the installing rom process.
Data isn't usually wiped by the rom installer, in case you are installing as an update.
Thanks
Thank you for the reply!
-Skye
Help for others
For anybody who finds themselves in a situation where you have lost your OS and you have only access to the ADB and fastboot...
You can still reboot TWRP by holding the power + volume down buttons on to power up and access Amazon's recovery mode. In recovery mode select "boot from bootloader" to enable fastboot. Connect your device to your PC and ensure you have your device driver installed and enabled. From here, use the Android SDK's fastboot.exe to send the command "fastboot boot <twrp image>". This will boot TWRP for you and enable you to give the process another go without having to reinstall the Fire OS.
You may find all commands used in these processes by referring to the scripting code of Rootjunky's batch file that helps to automate this process.
-Skye
CieloLumine said:
For anybody who finds themselves in a situation where you have lost your OS and you have only access to the ADB and fastboot...
You can still reboot TWRP by holding the power + volume down buttons on to power up and access Amazon's recovery mode. In recovery mode select "boot from bootloader" to enable fastboot. Connect your device to your PC and ensure you have your device driver installed and enabled. From here, use the Android SDK's fastboot.exe to send the command "fastboot boot <twrp image>". This will boot TWRP for you and enable you to give the process another go without having to reinstall the Fire OS.
You may find all commands used in these processes by referring to the scripting code of Rootjunky's batch file that helps to automate this process.
-Skye
Click to expand...
Click to collapse
Unbrick/Restore Stock 2015 Amazon Fire (KFFOWI/Ford) with custom recovery
Sent from my KFFOWI using Tapatalk
I think this is the one advantage of a locked boot loader. It's kinda hard to hard brick. Recovery and kernel remains intact too.
I wanted to install Gapps to my Kindle since many of the apps including the web browser are coming up as unsupported. I have rooted my Kindle Fire HD 8.9 and installed TWRP. When I rebooted my kindle to enter the recover mode, it got stuck at logo screen.
At first, when it was logo was flashing if I plugged it in, ubuntu give an error message "unable to mount Jem PVT Prod 04". I discovered that holding the volume up button made the screen go blank but not off. You can plug the kindle in and Ubuntu will recognize the kindle and allow you to access the internal storage.
How can I fix and reboot the Kindle from Ubuntu?
I researched tons of solutions but most of them require Windows which I don't run or I tried the instruction and they don't work or our incomplete.
I received a fastboot cable from Amazon today. I'll see how it works. Any advice would be appreciated.
Okay, I fixed the problem with the Fastboot Cable. Here's the steps that I did to fix it. It was loading Twrp or the bootloader so I reinstall them. I have Android SDK on my computer and my Kindle is rooted.
Step 1.
The correct twrp was difficult to find. This forum offered a site to go to but I found the site was corrupted and the website was trying to download a virus.
I found the twrp and bootload file here.
rootkindlefire.com/kindle-fire-root/how-to-root-convert-kindle-fire-hd-8-9-into-pure-android-tablet/
I placed the files in my android/sdk/platform-tools. (kfhd8-freedom-boot-8.4.3.img & kfhd8-twrp-2.6.0.0-recovery.img)
I typed into terminal "fastboot -i 0x1949 getvar product" without parenthesis. At the waiting for device command, I plugged in the Kindle with the Fastboot cable and held the Volume up button to go into fastboot mode.
I opened the android/sdk/platform-tools and right click the mouse and hit open in terminal
fastboot -i 0x1949 flash boot kfhd8-freedom-boot-8.4.3.img
fastboot -i 0x1949 flash recovery kfhd8-twrp-2.6.0.0-recovery.img
fastboot -i 0x1949 reboot
From the reboot, hit the volume up to get into twrp.
At this point, I still could go into the kindle so I thought the operating system may be corrupted.
Step 2
In twrp, I backed up the system. and rebooted into twrp.
In twrp, I hit wipe and rebooted back into twrp.
I downloaded CyanogenMod and Gapps to my platform-tools folder again.
rootkindlefire.com/kindle-fire-root/how-to-root-convert-kindle-fire-hd-8-9-into-pure-android-tablet
Step 3
I couldn't access the internal drive so I used ADB to put the files on my kindle.
Here's a video of the instructions I used.
youtu.be/NaK5OxUeDKM
Open the support document for Ubuntu instructions.
First, open terminal in the Platform Tools file and type ADB Devices. When I pushed the two files, his instructions say to use command sudo ./adb-linux push filename /sdcard/. This didn't work. I used "./adb push [filename /sdcard/." without the quotes and it worked.
Step 4
Enter twrp and install the CyanogenMod and Gapps. Reboot
This got my operating system up and running perfectly.
Now bad for a complete Noob.