Database Info

[Q] Update from 3.1 & Tiamat 1.4.4 failed

Help for a newbie.
I followed this procedure:
1 - Copied file to sd card and renamed to update.zip (in a windows computer)
2 - turned xoom on and wento to rom manager
3 - wiped user and dalvik cache
4 - Tried to load file from zip, but it was not possible to find the update .zip file.
I get the following message:
E: Can't open /sdcard/update.zip
(bad)
Tried also without renaming and got:
E: Can't open /sdcard/update_US-Xoom-Wifi-3.2_HTJ85B-from HMJ37_stachre-solarnz-boot-img_v05.zip
After many trials rebooted.
System info showed the same 3.1 and Tiamamat 1.4.4
Opened rom manager again.
seleced install rom from sdcard
System backed up info and rebooted.
Had to reload all apps from store.
System info shows I am running 3.1 and Tiamat 1.4.4.
Also I keep receiving a message that there is a system update available.
I can't understand what I did wrong.
I g
Can anyone help?
Thank you

rogerodd said:
Help for a newbie.
I followed this procedure:
1 - Copied file to sd card and renamed to update.zip (in a windows computer)
2 - turned xoom on and wento to rom manager
3 - wiped user and dalvik cache
4 - Tried to load file from zip, but it was not possible to find the update .zip file.
I get the following message:
E: Can't open /sdcard/update.zip
(bad)
Tried also without renaming and got:
E: Can't open /sdcard/update_US-Xoom-Wifi-3.2_HTJ85B-from HMJ37_stachre-solarnz-boot-img_v05.zip
After many trials rebooted.
System info showed the same 3.1 and Tiamamat 1.4.4
Opened rom manager again.
seleced install rom from sdcard
System backed up info and rebooted.
Had to reload all apps from store.
System info shows I am running 3.1 and Tiamat 1.4.4.
Also I keep receiving a message that there is a system update available.
I can't understand what I did wrong.
I g
Can anyone help?
Thank you
Click to expand...
Click to collapse
You may have the wrong version of CWM recovery installed. You need Tiamat v3.2.0.0 R4c. If you are trying to flash thru Rom manager it may have had you update to v4.0.0.4 which is not compatible with the external sdcard. If this is the case, re-install the correct recovery version, and then redo your backup so that it is on the external sdcard where it can be safe if you need to wipe/factory reset. You can use Rom manger just to reboot into recovery, or df Quick Boot from the market and use that instead.
Good luck!

okantomi said:
You may have the wrong version of CWM recovery installed. You need Tiamat v3.2.0.0 R4c. If you are trying to flash thru Rom manager it may have had you update to v4.0.0.4 which is not compatible with the external sdcard. If this is the case, re-install the correct recovery version, and then redo your backup so that it is on the external sdcard where it can be safe if you need to wipe/factory reset. You can use Rom manger just to reboot into recovery, or df Quick Boot from the market and use that instead.
Good luck!
Click to expand...
Click to collapse
Rom manager says it is 4.0.0.4 but when in recovery is say CWM recovery-Tiamat-R4c-100611-1150-cwm or Tiamat v3.2.0.0 R4c ( I don't remember exectly) and the error is the same.
Also, I tried reflash recovery-Tiamat-R4c-100611-1150-cwm.zip from the SD card and get an error.
I really don't have a clue of what to do.
Any help would be welcome.

rogerodd said:
Rom manager says it is 4.0.0.4 but when in recovery is say CWM recovery-Tiamat-R4c-100611-1150-cwm or Tiamat v3.2.0.0 R4c ( I don't remember exectly) and the error is the same.
Also, I tried reflash recovery-Tiamat-R4c-100611-1150-cwm.zip from the SD card and get an error.
I really don't have a clue of what to do.
Any help would be welcome.
Click to expand...
Click to collapse
The problem is that you can't flash anything from the external sdcard with v4.0.0.4. In rom manager, see if you can find"all clockwork recoveries" and find 3.2.0.0. If not, find 3.0.2.8 or 3.0.2.5 and flash one of them, preferably the latest of those I have listed. I think those will at least recognize your sdcard. If you can't do that, you will need to reflash the correct recovery the same way you did when you rooted. Remember, never flash a zip file through adb.
Good luck!

I tried to flash recovery-Tiamat-R4c-100611-1150-cwm.img via adb.
I could flash boot sector. Then I reboot into recovery and try to apply zip from card with file update_US-Xoom-WiFi-3.2-HTJ85B-from-HMJ37_stachre_solarnz-boot-img_v05.zip, but there is a NO at the end of the name of the file and I can't go on.
Trying to rename as update.zip and run apply zip from card results in same error:
E: Can't open /sdcard/update.zip
(bad)
what should I do?
Thank you

possible bad download... download again... also, don't think this would be an update... leave it as originally named, just choose the option to choose which zip file to install from the sd card

rogerodd said:
I tried to flash recovery-Tiamat-R4c-100611-1150-cwm.img via adb.
I could flash boot sector. Then I reboot into recovery and try to apply zip from card with file update_US-Xoom-WiFi-3.2-HTJ85B-from-HMJ37_stachre_solarnz-boot-img_v05.zip, but there is a NO at the end of the name of the file and I can't go on.
Trying to rename as update.zip and run apply zip from card results in same error:
E: Can't open /sdcard/update.zip
(bad)
what should I do?
Thank you
Click to expand...
Click to collapse
It sounds like you are flashing recovery ok, but you keep overwriting it with the stock recovery.
Here is some important information that should help a lot with making your new recovery "stick"and this was taken from the Idiot's guide to flashing...in the Development section, and originally written by publicanimal:
4. Install recovery image (CWM)
Download the recovery image file and save it to your computer
Boot into flash mode with 'adb reboot bootloader'
Install your downloaded recovery image
C:\Documents and Settings\Anders> fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.img
Restart the device with 'fastboot reboot'. Timing is essential here, so be alert when the device restarts, or you will have to redo this section
Enter CWM with the following procedure
Once the Motorola logotype is shown, start counting to 3. At 3, press the Volume Down button. This should result in the text 'Android Recovery' in the top left corner. If it does not work, experiment with the timing ...
When 'Android Recovery' is shown press the Volume Up button. This should invoke the CWM recovery menu. If that works, then congratulations for reaching this far .
Here is a potential pitfall. If you are unable to enter CWM *before* the device boots into Honeycomb, then the newly installed recovery image will be overwritten by the system default recovery. If that happens, or if you see "starting fastboot protocol " your timing wasn't right and you need to reflash the recovery image and try it again.
See original post,below for more information.
http://forum.xda-developers.com/showthread.php?t=1130996

Recovering from /data mount issues

Guys,
I have had an device impacted by TWRP 2.7.X build that created the problem of not being able to mount /data and sometimes(/cache & /system) partitions.
I have managed to make it run a ROM by using information from
http://forum.xda-developers.com/showthread.php?t=1869673 & http://forum.xda-developers.com/showthread.php?t=1843062.
the problem is that the mounts are not remaining permanent and my modified boot.img does not boot the devices. So i have to mount the partition manually during the boot process over a shell and then the device boots.
Need help from experts to do a kernel which can mount sdext partition and an updated recovery image which also mounts the sdext partition as /data so that roms can be flashed easily.
I will try and do a writeup of how i made it run.

Resurrecting Pyramid
As mentioned in the earlier thread, my sensation got into trouble with TWRP 2.7 version and i was having trouble mounting /data, /system and /cache partitions.
I eventually got the /cache partition mounted by using mkfs.ext4 utility but could not get other and hence started working on a way to move both /data and /system partitions completly off SD card. Lot of people have already attempted that for other devices, feel free to go and check the threads linked in the post 1. Lets get started:
Assumptions: You have a sensation on which /data and /system partitions are an issue - not getting mounted / formatted etc. /cache is expected to be ok/working.
Requirements:
1) Your phone is booting and can go into recovery. Please get 4EXT recovery installed. You can download an img file from here
2) You have basic adb and fastboot setup on your machine(Win/Linux). Just google them out, if you dont have , there are plenty of tools out there.
3) Download Revelation 1.0.3 from here. you can choose any other ROM but i worked on this and have the boot image patched to look at /system from sd-ext.
4) download the two files attached with this thread.
Steps to recover:
1) Boot your phone in recovery. We will first get the SD Card set up. A Class 10 card is preferred, you will have a good feel on the phone.
2) Using 4EXT partition tool for sd card, create 2 sd ext partition in addition to your sdcard. I suggest first partition(which we will use as /system) to be more than 800 MB and second partition( which we will use as /data) to be more than 1024 MB.
3) Verify using the 'info' option of 4ext recovery that you can see sd-ext, sd-ext2 and sdcard partitions.
4) Extract the ROM you have downloaded using 7z/Winzip /winrar and replace the following files you have downloaded from this thread.
a) updater-script in /META-INF/com/google/android/ folder.
b) boot.img in /KERNEL folder.
5) Zip the file again and copy to your sdcard. Choose install from sdcard from the 4ext recovery menu. Choose default options in AROMA installer.
6) Reboot.
Hope your phone boots. If not, this is how you debug
Android will create a /proc/kmsg file when the kernel boots. So open two terminal(linux) windowds, in one, type this
Code:
adb pull /proc/kmsg
and in the second terminal(make sure the directory is same), type this:
Code:
cat kmsg | less
and then go through the error messages to see what is going wrong. If you can share your kmsg file created, I can try and help you debug.
Good luck !!!!!

Hi,
I followed your instructions but the Aroma installer always stops and the log shows this:
Code:
AROMA INSTALLER version 2.56
(c) 2012 by amarullz xda-developers
ROM Name : Revelation
ROM Version : 1.0.3
ROM Author : SebastianFM
Device : HTC Sensation/XE/4G
Start at : Fri Jan 2 00:00:31 1970
line 4 col 1: syntax error, unexpected BAD, expecting IF or STRING or '!' or '('
line 44 col 70: syntax error, unexpected BAD
2 parse errors
Installer Error (Status 6)

Jack Daniel's said:
Hi,
I followed your instructions but the Aroma installer always stops and the log shows this:
Code:
AROMA INSTALLER version 2.56
(c) 2012 by amarullz xda-developers
ROM Name : Revelation
ROM Version : 1.0.3
ROM Author : SebastianFM
Device : HTC Sensation/XE/4G
Start at : Fri Jan 2 00:00:31 1970
line 4 col 1: syntax error, unexpected BAD, expecting IF or STRING or '!' or '('
line 44 col 70: syntax error, unexpected BAD
2 parse errors
Installer Error (Status 6)
Click to expand...
Click to collapse
Pick the files from here and then try...
http://forum.xda-developers.com/htc-sensation/help/bricked-htc-corrupted-partitions-t2804222/page3

rmann said:
Pick the files from here and then try...
http://forum.xda-developers.com/htc-sensation/help/bricked-htc-corrupted-partitions-t2804222/page3
Click to expand...
Click to collapse
I tried that before.
Same result but it shows one error less.
Code:
...
line 4 col 1: syntax error, unexpected BAD, expecting IF or STRING or '!' or '('
1 parse errors
Installer Error (Status 6)

Jack Daniel's said:
I tried that before.
Same result but it shows one error less.
Code:
...
line 4 col 1: syntax error, unexpected BAD, expecting IF or STRING or '!' or '('
1 parse errors
Installer Error (Status 6)
Click to expand...
Click to collapse
Which recovery are you using... I have re-tested the script and it works ok for me.

rmann said:
Which recovery are you using... I have re-tested the script and it works ok for me.
Click to expand...
Click to collapse
I get the same exact error as Jack Daniel's.
I am using as recovery 4EXT Recovery Touch v1.0.0.5 RC5.

antiziclon said:
I get the same exact error as Jack Daniel's.
I am using as recovery 4EXT Recovery Touch v1.0.0.5 RC5.
Click to expand...
Click to collapse
did you try to update the recovery to the latest version?

rzr86 said:
did you try to update the recovery to the latest version?
Click to expand...
Click to collapse
Just tested with v1.0.0.6 RC3 build 8, same error

antiziclon said:
Just tested with v1.0.0.6 RC3 build 8, same error
Click to expand...
Click to collapse
redownload the zip file
after that i am out of ideas

ok, I found out the issue.
The issue is on the encoding of the "updater-script" file.
It needs to be in Unix encoding. If you use Windows (as I do) when unzipping the Zip file or when creating a new file with a text editor, the encoding gets changed and it is not Unix encoding.
To solve it:
- Open the file in Notepad++.
- Go to Edit --> EOL Conversion --> UNIX
It will change the enf of lines to comply with Unix encoding. Then add the file to the Rom zip file and you are ready to go
Enjoy!

Successful Pyramid rescue
I have a sensation with corrupted emmc caused by TWRP, /data cannot be mounted.
I followed your instructions and addition re script encoding and successfully installed Revelation to partitioned sdcard.
Phone boots and works.
That's great, thanks.
I have some questions:
1. Is 512 MB sufficient for swap partition? What would be the optimal size?
2. My sensation is s-on unlocked, and I had to flash boot via fastboot after install, 4ext did not flash it despite smartflash option turned on. Is that normal?
2. Superuser does not seem to work, I have no root. I checked with root validator and I have su binary, superuser and busybox, but no root is given to apps that require it, su binary update fails, and there are no logs left in superuser to check (or I simply don't know where to look).
Thank you.

rmann said:
As mentioned in the earlier thread, my sensation got into trouble with TWRP 2.7 version and i was having trouble mounting /data, /system and /cache partitions.
I eventually got the /cache partition mounted by using mkfs.ext4 utility but could not get other and hence started working on a way to move both /data and /system partitions completly off SD card. Lot of people have already attempted that for other devices, feel free to go and check the threads linked in the post 1. Lets get started:
Assumptions: You have a sensation on which /data and /system partitions are an issue - not getting mounted / formatted etc. /cache is expected to be ok/working.
Requirements:
1) Your phone is booting and can go into recovery. Please get 4EXT recovery installed. You can download an img file from here
2) You have basic adb and fastboot setup on your machine(Win/Linux). Just google them out, if you dont have , there are plenty of tools out there.
3) Download Revelation 1.0.3 from here. you can choose any other ROM but i worked on this and have the boot image patched to look at /system from sd-ext.
4) download the two files attached with this thread.
Steps to recover:
1) Boot your phone in recovery. We will first get the SD Card set up. A Class 10 card is preferred, you will have a good feel on the phone.
2) Using 4EXT partition tool for sd card, create 2 sd ext partition in addition to your sdcard. I suggest first partition(which we will use as /system) to be more than 800 MB and second partition( which we will use as /data) to be more than 1024 MB.
3) Verify using the 'info' option of 4ext recovery that you can see sd-ext, sd-ext2 and sdcard partitions.
4) Extract the ROM you have downloaded using 7z/Winzip /winrar and replace the following files you have downloaded from this thread.
a) updater-script in /META-INF/com/google/android/ folder.
b) boot.img in /KERNEL folder.
5) Zip the file again and copy to your sdcard. Choose install from sdcard from the 4ext recovery menu. Choose default options in AROMA installer.
6) Reboot.
Hope your phone boots. If not, this is how you debug
Android will create a /proc/kmsg file when the kernel boots. So open two terminal(linux) windowds, in one, type this
Code:
adb pull /proc/kmsg
and in the second terminal(make sure the directory is same), type this:
Code:
cat kmsg | less
and then go through the error messages to see what is going wrong. If you can share your kmsg file created, I can try and help you debug.
Good luck !!!!!
Click to expand...
Click to collapse
Ok try to make that in unix

Extreme lag
Hi there,
I followed all the staps, but when the rom was installed, it was very laggy and i experinced a lot of force closes. Is this because the partions are to small or because the sd is to slow EDIT: its a class 4 card?
Greetings,
Danil

Extreme unuseful slow
With my sensation XE i also followed all steps. Revelation 1.0.3 is booting, but not to use at all, it stucks in every step, cant even receive a call, can't go to any menu. Pls someone help me out of here. Do I need a swap partition? Or are the partitions to small? sd-ext has 1024Mib; sd-ext2 1537Mib.

danilandroid said:
Hi there,
I followed all the staps, but when the rom was installed, it was very laggy and i experinced a lot of force closes. Is this because the partions are to small or because the sd is to slow EDIT: its a class 4 card?
Greetings,
Danil
Click to expand...
Click to collapse
Hi Danil, could you solve the problem? I encounter same symptoms. My Phone: Sensation XE; Revelation 1.0.3. Cant use it at all , it boots but gets totally stuck. Have original sd, dont know the class. Greetings dididoner

dididoner said:
Hi Danil, could you solve the problem? I encounter same symptoms. My Phone: Sensation XE; Revelation 1.0.3. Cant use it at all , it boots but gets totally stuck. Have original sd, dont know the class. Greetings dididoner
Click to expand...
Click to collapse
probably you need a sdcard with high speed of w/r but i am not sure

Lag
rzr86 said:
probably you need a sdcard with high speed of w/r but i am not sure
Click to expand...
Click to collapse
I'm going to buy a sd-card class 10 and than I will try the same thing agian. I will report later.
@ rmann Btw thanks for the amazing thread, I was completely stuck and now my phone is alive again kinda.
Danil

danilandroid said:
I'm going to buy a sd-card class 10 and than I will try the same thing agian. I will report later.
@ rmann Btw thanks for the amazing thread, I was completely stuck and now my phone is alive again kinda.
Danil
Click to expand...
Click to collapse
rzr86 said:
probably you need a sdcard with high speed of w/r but i am not sure
Click to expand...
Click to collapse
dididoner said:
Hi Danil, could you solve the problem? I encounter same symptoms. My Phone: Sensation XE; Revelation 1.0.3. Cant use it at all , it boots but gets totally stuck. Have original sd, dont know the class. Greetings dididoner
Click to expand...
Click to collapse
So, I bought a class 10 card, revelation is running now!! At first start it was still very slowly an got stuck allover. But at second start it is running now! Thanks for that perfect thread!!:good:
I wonderd why vipers wont start the same way? When I try to boot it , 4ext recovery is starting rightaway with little delay!

Hi, when I got the same problem with /data, /cache and /system not mounting. I followed the steps from #2 post http://forum.xda-developers.com/showpost.php?p=55157092&postcount=2
and when I try to install from zip it says that the zip isn't meant to be flashed in recovery and it aborts the installation. First I tried renaming the new_boot.img you provided to boot.img but it's the same result.

Newb Warning - I softbricked my P3110

I started experimenting with my old P3113 last night and ran into a bit of a problem. I successfully rooted using Odin 3.09, verified with root checker. I also successfully flashed TWRP 2.8.7.0 via Odin. All root and TWRP install/flashes were successful via Odin.
Following these instructions: http://forum.xda-developers.com/gal...m-dhollmen-lollipop-5-0-2-2015-02-02-t3020849
I downloaded the Dhollmen-P31xx-Kernel_20150215.zip and saved to the Download folder on the tab. From TWRP I ran a wipe and installed the .zip. I reboot the device and I am returned to TWRP recovery. TWRP tells me that the installation was successful however the log says "no MD5 file found". Does this have anything to do with why my device isn't booting properly? I've rooted other devices and flashed ROM's before but I don't understand what I missed on this one. Do I just need to try a different ROM? For reference I am still able to access download menu.
Any help would be appreciated!

Well, the "no MD5 file found" just means TWRP cannot verify the MD5 hash of the ZIP file - that's actually a security meassure to ensure the ZIP file didn't get damaged during download or transfer onto the tab.
Now ... once you flashed TWRP (which you obviously already successfully did) and flashed the Kernel (which you obviously also already successfully did) it would be about time to flash the actual Dhollmen ROM that goes along with the Kernel ... I doubt the Kernel will boot up your vanilla Samsung stock ROM.
In short (haven't read the ROM thread nor did I ever use Dhollmen, so check back to make sure it's about right): Download the ROM, download the GApps package for the ROM and download the Superuser package (if not already included in the ROM) of your choice. Put the files onto either a FAT32 formatted SD card (if you can't put them into the NAND "SD card" partition at the moment) or onto a FAT32 formatted USB stick (given you have a USB-OTG cable), plug it in (if you use a USB stick make sure your tablet is CHARGED!), boot into recovery and flash the files in one go ... ROM, Gapps, SU.
Run a wipe (Data and Cache) when everything is flashed to nuke any left-overs from the Stock ROM and reboot to system.
Keep in mind the first boot can take quite some time ... don't panic if the boot animation "just sits there" for 5<->15 minutes.
Easiest way would be to actually use a ROM that doesn't require a extra Kernel ... like Android-Andi's CyanogenMod 12.1 or Omni ROM 5.1 (use the 3110 versions for your 3113).

[U-Boot/SD] External Recoveries (TWRP 2.8/3.0 & CWM) for Nook HD/HD+

These SD card images are built in same vein as @verygreen's here, except with a few differences:
Modified, and re-built the second bootloader (uImage) to present a menu of three recovery distributions: TWRP 3.0.0-0, 2.8.7.5, and original CWM.
Replaced the CM11 kernel therein (3.0.31) with my latest from Marshmallow. While this wasn't strictly necessary, the XZ compression helps the kernel image load faster (especially on slow SD cards).
Packaged the new TWRP RAM disks in a way that U-Boot can load them. The original ramdisk.cwm is left as was for whoever needs it.
The use is pretty standard: hold the Nook/Home button for the menu, otherwise it should boot directly into the new TWRP 3.0.0-0. People still on CM12 will need the customized 2.8.7.5 because of reasons discussed on that thread (e.g., LZMA, blockimage format). The files that were replaced completely are moved in the OLD folder, just in case. Assuming everything works well, these cards should be the only things needed to root/rescue/etc a Nook HD/HD+. Bug reports are enabled, in case major issues remain.
That being said, the images live in the experimental folder here, although they will probably be moved into the respective device folders soon.
XDA:DevDB Information
External Recoveries, Tool/Utility for the Barnes & Noble Nook HD, HD
Contributors
amaces, verygreen, fattire
Version Information
Status: Testing
Created 2016-02-14
Last Updated 2016-02-14

Reserved

Did fix messages make it through?+ new recovery trial
Sorry--I TRIED to send you a message by commenting on a couple of commits, and to attach an ovation uImage. Learning to program on Ubuntu, with repo, git, useing github, etc. all in a couple of months has me rather confused. I hope you got the message
Anyway, I just tried compiling a standard cm recovery to see if it would deal better with f2fs--I don't think it does, but other than coming up upside-down on hummingbird, it does at least come up from the sd card. I'll check into it further...
I note that when I tried to install a zip (internal twrp 3.0.0-0) from TWRP 3.0..0-0 on SD Card, I did get error messages about data, but somehow didn't manage to catch them in a log. ( I will try again, if you need me to). I think the install succeeded anyway. Does something need to be changed in the recovery.fstab for running from the SD Card?

Additional testing info
I've attached a recovery log from running sd card twrp 3.0.0-0 and installing a zip.. (which as, I've said I think succeeded) . Trying to do anything with data or cache will generate error messages in any of these recoveries. I also note they can't deal with selinux contexts, apparently. I don't think the new cm rom gives as much flexibility as TWRP or even CWM, except that it will reboot into the bootloader, but it would be easier to recompile ...
FWIW

belfastraven said:
I've attached a recovery log from running sd card twrp 3.0.0-0 and installing a zip.. (which as, I've said I think succeeded) . Trying to do anything with data or cache will generate error messages in any of these recoveries. I also note they can't deal with selinux contexts, apparently. I don't think the new cm rom gives as much flexibility as TWRP or even CWM, except that it will reboot into the bootloader, but it would be easier to recompile ...
FWIW
Click to expand...
Click to collapse
Feeling more stupid then usual:
Are these the instructions we use(using the current files) to create the sd card from the linked thread? Thanks
For new Installs:
Download the initial sdcard image
ungzip and write to sdcard using dd (winimage or whatever for those stuck on Windows)
Instert the card into your nook and reboot
Flash the recovery image
Flash cm11 image
Flash whatever other extra things you need like gapps
remove the sdcard
reboot the nook

prsa01 said:
Feeling more stupid then usual:
Are these the instructions we use(using the current files) to create the sd card from the linked thread? Thanks
For new Installs:
Download the initial sdcard image
ungzip and write to sdcard using dd (winimage or whatever for those stuck on Windows)
Instert the card into your nook and reboot
Flash the recovery image
Flash cm11 image
Flash whatever other extra things you need like gapps
remove the sdcard
reboot the nook
Click to expand...
Click to collapse
What are you trying to do--i.e. which rom are you trying to install and what is running now? (I am not sure to which linked thread you are referring) I want to make sure I give you the correct information. You will definitely make an SD Card, (it's how you do it and what you put on it I would like to clarify) And the steps following that will be the same.

I'm using Amaces great current CM MM rom (2/22) just wanting to create the recovery sd in this thread. The link I was referring to was to the verygreen thread in the OP
Thanks

prsa01 said:
Are these the instructions we use(using the current files) to create the sd card from the linked thread? Thanks
Click to expand...
Click to collapse
No. Make the SD. Card using the method in the howto thread.
I don't have the link handy...
Basically, format card to full size, set partition to active/bookable, uncompress the download, copy milo first (has to be first directory entry, first file written after formatting).
Then copy the rest of the files.
That gives an SD card that boots to recovery that can be used to flash/backup/restore EMMC.

Thanks ST Dog, just what I needed

New Sd Card recoveries available:
I have built new versions of the recoveries by @amaces in the OP.
I have fixed a few menu issues, e.g. the correct message about which recovery you choose will now come up and the the proper default (TWRP 3.0.0-0) will be highlighted. I ihave ncreased the amount of time you have to press the n (nook) key before the recovery defaults to TWRP (3.0.0-0) , and I have compiled a new version of TWRP (3.0.0-0). The older TWRP and CWM recoveries are the same: be aware that with CWM, if you have formatted data/and or cache with f2fs, CWM will throw off error messages that it cannot mount those partitions, (or wipe them), but you could still use it to install recoveries or zips. Opengapps is now recommending TWRP for installation.
the necessary files are available in two formats -
1.-a zip of a directory containing seven files. You need a fat32-partitioned and marked-bootable empty sdcard on which you copy the MLO file first, and than the remaining files in any order. You can then add whatever installation files you want to play with. You can add whatever zips/ .img files (with twrp) you wish to flash to the card.
2. -A zip of an .img file, which can be written to any unpartitioned card which is 4G or larger. (I understand that this .img may be necessary for mac people, but it also works for me from UBUNTU)
The Nook HD hummingbird version of this works fine for me. And although I don't have an ovation, a couple of intrepid testers have tried this and found that is works.
These are now available on Android File Host:
hummingbird
ovation
I will monitor this thread for problems at least every couple of days : if you mention @belfastraven in your message I will be notified. Please don't bother @amaces who has greatly helped me for with what are now MY mistakes .
In the near future I intend to increase the time you have to press the n(nook) key further, and to put up a version of TWRP 3.0.0-0 that can be used with a mouse, in case of touch screen problems.
here are now additional zips for both Hummingbird and Ovation that will allow you to boot recovery with a mouse and use the mouse to navigate in TWRP3 (in case of broken/malfunctioning touchscreen). If you already have one of the other recoveries set up, you should just be able to replace the kernel, or the kernel and ramdisk file (which is actually TWRP3 here) to achieve this result . You need to have a USB_OTG mouse. (that is, you need to use the nooks charging cable and an adapter to connect the mouse) I have forced USB-HOST on in this particular kernel. These devices don't charge with USB host forced on, I believe, so I wouldn't recommend making this a permanent option if you ever charge your device in recovery.
The ovation version has not yet been tested, but hummingbird works well.

xx

I'm going through OP's stuff, including his guide on CM 12.1. I picked up a free Nook HD from a coworker that currently has CM 10.2 and CWm 6.0.3.2 on it. Should I be using the TWRP and CM 12.1 builds in this experimental folder with the same installation guide or should I be using the stable builds in the hummingbird folder?

Can anyone help me replacing cyanoboot with unit? There's no clear indication of which files to use for the bootloader replacement. Thanks in advance for any and all help!!

Not able to flash Stock image with custom Recovery (TWRP 3.1.1.1.)

Hello guys,
Today I wanted to update my Honor 8 (FDR-L09) because it was showing me, that there is a new update ready to install (FRD-L09C432B405) and I was on a very old firmware (something from mid 2017). So it was time for me to update.
I downloaded the latest update (FRD-L09C432B405) and tried to wipe the cache, dalvik, and Data, but for some reason it "couldn't mount /data" and the wipe failed.
After an advanced wipe it worked and I tried to flash the stock image (the update which was shown to me (FRD-L09C432B405) with TWRP (3.1.1.1.)).
Now my hassle starts:
1. The Rom couldn't get flashed because of "Error: 7" --> I fixed it with the common "Error 7 fix --> editing the update-script and removing the assert line. (And yes, I'm 100% sure that it was the right ROM.
2. Now TWRP seemingly starts to flash the rom but inbetween the lines there is "mountencrypt: failed to mount /data: no such file or directory and it ends with "unknown command [[]" and it takes just two seconds, so the flash obviously isn't succsessfull.
I tried the "failed to mount /data" fix, where I change the data system to ext3 and then back to f2fs and change it back, but it won't work.
In my frustration I did another pretty bad thing and made another advanced wipe and wiped the system too, so now I don't have an OS on my system.
Maybe it's also important to note that there was a window showing up for a very short amount of time, with something like "encryption/encrypted" showed up.
What should I do now? Is there a way to fix the "/data couldn't be mounted" problem? Or am I missing a vital step in flashing the stock rom?
Thanks for your kind help!

You can not flash an update with twrp unless you use hurupdater. You essentially bricked your phone. Look for hurupdater here on xda and follow the instructions and you'll be fine