Database Info

[KERNEL] Dual Boot 1.3 - 22/09/2011

Android's First multi version, fully working Dual Boot​
Dual boot is running 2 ROMs on phone. You can run Froyo and Gingerbread and switch between ROMs by restarting phone. All ROMS are supported in dual boot including froyo, cm7 and cm 6.2.
*** Flash 800Mhz first. I will upload 1020 and 1300Mhz versions later.
*** Partiting sdcard in cwm does not wipe data in sdcard.
*** Consider worst case and backup important sdcard data.
*** You can have your existing rom on phone as ROM1 if it is rfs, ext2 or ext4.
*** Dual boot enables data2sd for both roms.
*** ROM1 boots by default and to boot ROM2 press Home Button.
*** Press the ROM selection button between 5-20 seconds after turning on phone.
*** Here is the partitions used in dual boot.
Internal /system - ROM1 system
Internal /data - ROM2 system
sdcard ext1 - ROM1 data
sdcard ext2 - ROM2 data
sdcard swap - swap for both ROMS
Instructions to Flash dual boot kernel.
1. Download Dual Boot Kernel and update.zip files. Links are at the end of this post.
2. Upload update.zip files to sdcard.
3. Flash Dual Boot Kernel using odin one package selection and wait until Phone boots into Recovery.
5. Partition SDCARD in recovery.
- Select 'Mounts and Storage' and format data and cache and mount cache
- Go to 'Advanced' and 'Parition SD card'
- Select sdcard /data partition size you wish to have. Two data2sd partitions will be created with size you choose.
- Select swap size if you want swap on sdcard
- Wait until partitioning Done
- Go to main menu in recovery
6. Flash ROM1 or Use existing rom.
- If you want to use existing rom just reboot system now else continue.
- Go to main menu in recovery
- Select 'Mounts and Storage' and Format system and mount system
- Select 'Install zip from sdcard' and 'choose zip from sdcard'
- Select the ROM1 zip file and Press Yes to Install
- Reboot system now
Wait untill ROM1 boots
7. Flash ROM2
- Reboot to recovery mode and press Home key (ROM2) with in 5-20 seconds.
- Select 'Mounts and Storage' and format system, data and mount system
- Select 'Install zip from sdcard' and 'choose zip from sdcard'
- Select the ROM2 zip file and Press Yes to Install
- Reboot system now
Press Home key within 15 seconds and ROM2 will boot
Click to expand...
Click to collapse
Download Kernel and update.zip files:
Kernel 1.3 - 800Mhz : http://www.megaupload.com/?d=XSIAT910
Kernel 1.3 - 1000Mhz : http://www.megaupload.com/?d=EUBW0N2G
Kernel 1.3 - 1200Mhz : http://www.megaupload.com/?d=D93CH76X
Kernel 1.2 - 800Mhz : http://www.megaupload.com/?d=R22DCDOG
cm7 alpha4 : http://www.megaupload.com/?d=287BAP4D
cm6.2 alpha4 : http://www.megaupload.com/?d=LL3JXTP8
sumee 4.0 : http://www.megaupload.com/?d=DO01QB84
xxjps : http://www.megaupload.com/?d=68XJN4I1
Kyrillos7 : http://www.megaupload.com/?d=2VXAIL11
indroid5 : http://www.megaupload.com/?d=5DN5R2XF
Click to expand...
Click to collapse
How to Make update.zip
1. Download attached create_update.zip.zip file and unzip
2. Move to unzipped folder and copy your rom files to system folder
3. Open create_update.zip.bat and wait untill "Press any key" appears
4. Done. update.zip is ready. rename or upload as it is to sdcard
Click to expand...
Click to collapse
Source Code : Still in Alpha stage. Source will be out with final Release.
******* Enjoy Dual Boot *******

Excellent Work apollo5801...Waiting For it...

Great to know... Do your best!

Best of luck..
Apollo you should have reserved some posts
Tapatalked from my super smooth, ultra fast samsung galaxy s2.

Great news! Cyanogenmod, here I come -->
Sent from my speedy G3!

Great work apollo5801!! Looking forward to test it

That's plain awesome
Great News!

That day is not far when g3 vil become a space craft.. Lolzz.. Great wrk apollo5801
Sent from my GT-I5800 using XDA App

great news

wow.....great news !
what's the another system?

dxdiag32 said:
wow.....great news !
what's the another system?
Click to expand...
Click to collapse
Windws 8

shebu18 said:
Windws 8
Click to expand...
Click to collapse
no its cm7 n froyo for now..

dxdiag32 said:
wow.....great news !
what's the another system?
Click to expand...
Click to collapse
Both are Android OS.
You get to boot two different ROMs. Got it?

rudolf895 said:
no its cm7 n froyo for now..
Click to expand...
Click to collapse
you mean cm7 is working for sg3 now?

dxdiag32 said:
you mean cm7 is working for sg3 now?
Click to expand...
Click to collapse
D'uh!!!!
What has been Marcellusbe working his ass of for??

think bout it.... MIUI and CM7 with dual boot NICE!
This just might be the best thing ever happened to G3

Anyways great work by apolo. This can be counted as epic developement alongwith cm7 port. Hope sumday we can dual boot wp7 and cm7 together.
Sent from my GT-I5800 using XDA App

Nice work. Thanq. I clicked thanks.I wud like to thank a million times.
And We do not want this valuable thread to b polluted with unwanted posts. Ofcourse even mine is an unwanted post

brjshshrma said:
No need to hit thanx as i didnt help u in anyway. I just edited in respect of a gud developer.
Sent from my GT-I5800 using XDA App
Click to expand...
Click to collapse
Thanks for editing the post. So seem reasonable n good person.

brjshshrma said:
No need to hit thanx as i didnt help u in anyway. I just edited in respect of a gud developer.
Sent from my GT-I5800 using XDA App
Click to expand...
Click to collapse
LOL man...he can still see the post...Rudolf quoted it

[RECOVERY] CWM based recovery v5.5.0.4 + repacked Touch CWM v5.8.1.8

ClockworkMod Recovery for the Transformer TF101​
NEW: Repack of Koush's touch clockworkmod recovery v5.8.1.8 to address the reboot to recovery issue.
This recovery is not mine and I take no credit for it. I only made a small change to the official recovery found here
and repacked it into a flashable zip.
Here is a diff of the hacky but working fix.
Code:
diff -Naur org/init.rc new/init.rc
--- org/init.rc 2012-04-02 21:18:24.875745175 +0100
+++ new/init.rc 2012-04-02 20:58:55.855745201 +0100
@@ -31,6 +31,8 @@
service ueventd /sbin/ueventd
critical
[COLOR="Green"]+service clearmisc /sbin/clear-misc.sh
+[/COLOR]
service recovery /sbin/recovery
service adbd /sbin/adbd recovery
diff -Naur org/sbin/clear-misc.sh new/sbin/clear-misc.sh
--- org/sbin/clear-misc.sh 1970-01-01 01:00:00.000000000 +0100
+++ new/sbin/clear-misc.sh 2012-04-02 20:58:55.855745201 +0100
@@ -0,0 +1,4 @@
[COLOR="Green"]+#!/sbin/sh
+# This clears the boot flag from misc which forces
+# this device to continuously boot into recovery
+/sbin/dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=1 count=13[/COLOR]
Even though these recoveries have been tested by me, I won't be responsible for any loss of data or any damages done by using it.
IF YOU ARE NEW HERE PLEASE READ THE NEXT LINE VERY CAREFULLY!
See here if you are having trouble with a recovery loop from another version of recovery...
Did you get that? Just in case please read it again before posting about not seeing recovery being updated!
Download
Touch Recovery v5.8.1.8 (repacked from official with the fix above)
MD5: 0b7f3c5986847e37c1dffcb53a9b79af
ClockworkMod Recovery v5.5.0.4 roach-tf101-r2
MD5: a352abf783746eb29a0f98159ca3c439
Changelog
v5.5.0.4 roach-tf101-r2
-Standard 5.5.0.4 recovery
-Installs from the Internal sdcard
-Tar backups (Not compatible with backups from version 3.2.0.1 and below)
-Power off option re-added as I find this useful
v3.2.0.1 roach-tf101-r1
- Fixed Dock keys (Left shift and Caps Lock were reversed)
- Added advanced backup from solarnz
- Tweaked mounts to improve performance
v3.1.0.1 (R3-240511-1908)
- Initial release for Asus Transformer
- Modified to skip /data/media or /sdcard in nandroid backups.
- Modified formatting /data to remove directories and folders so we can keep media.
- Place a file called eraseData in the clockworkmod directory on your EXTERNAL sdcard to revert to the normal restoration method
Mod Edit:
Installation Instructions
Method 1 Flashing through CWM
Download the recovery zip file
Place the recovery zip on the sdcard where clockworkmod can read it.
Reboot into recovery using "adb reboot recovery" or "hold volume down and power for 3 seconds, let go of power only, then press volume up when prompted on screen"
In recovery, select flash zip from sdcard and select the recovery zip you downloaded
Once it has flashed the zip file, be sure to reboot your transformer so it complete the flashing process.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Credit: http://forum.xda-developers.com/showthread.php?t=1093818
Older versions
v3.2.0.1 roach-tf101-r1
MD5: b28dca7b9dce48627e5e849586f633d1

Great work mate
However it would be great to install the updates also from /sdcard and not only from /Removable/MicroSD...I will give a look to that

gnufabio said:
Great work mate
However it would be great to install the updates also from /sdcard and not only from /Removable/MicroSD...I will give a look to that
Click to expand...
Click to collapse
I'm already on the case, the first post was just a taster of things to come.

Is there a reason that /BOOT is not backed up using Backup/Restore option in CWM. It would make switching ROMS & Kernels much easier. I asked this question in the original CWM thread, but never got an aswer

hi,
good job, how to update the actual clockworkmod recovery ???
I apply the zip from recovery, but update not apply ::-(
Regards

Working towards rom manager support too?
Sent from my Transformer TF101 using XDA Premium App

does 3.2.0.1 skip internal storage too?
Also I would really Install Updates from Internal Storage, Install Updates from SdCard that would be awesome if you 2 guys could do that lol

brookfield said:
Is there a reason that /BOOT is not backed up using Backup/Restore option in CWM. It would make switching ROMS & Kernels much easier. I asked this question in the original CWM thread, but never got an aswer
Click to expand...
Click to collapse
It's not currently backed up by CWM because the transformer has no /boot partition. There is however another way to back this data up so you will see this in a future update.

006fazer said:
hi,
good job, how to update the actual clockworkmod recovery ???
I apply the zip from recovery, but update not apply ::-(
Regards
Click to expand...
Click to collapse
I had the wrong link. fixed now.

Warboy said:
does 3.2.0.1 skip internal storage too?
Also I would really Install Updates from Internal Storage, Install Updates from SdCard that would be awesome if you 2 guys could do that lol
Click to expand...
Click to collapse
It does skip internal media unless you put a file called eraseData into the clockworkmod folder on your MicroSD card.
The ability to Install updated from the internal sdcard will be in the next version.

i download the good file, but upate don't work !

Roach, how did you compile it?

try this http://www.mediafire.com/?o4e36tmkd2xqb11
Roach made a small mistake making the update.zip. You simply have to rename /kernel folder to /recovery

Updated but still have the old recovery.
Sent from my Transformer TF101 using XDA Premium App

love you roach!
Sent from my Transformer TF101 using XDA Premium App

david279 said:
Updated but still have the old recovery.
Sent from my Transformer TF101 using XDA Premium App
Click to expand...
Click to collapse
I uploaded the wrong file lol, fixed now and MD5 updated. Apologies for the inconvenience

gnufabio said:
Roach, how did you compile it?
Click to expand...
Click to collapse
I used ubuntu.

Awesome nice to see Clockwork Recovery being updated. Maybe after you're done working on this one, you could port TeamWin Recovery Project over too for fun or something I used to use Clockwork on my phone but then made the switch to TWRP for a new feel.
Source for TWRP: https://github.com/TeamWin/Team-Win-Recovery-Project/
TWRP Image: http://forum.xda-developers.com/showpost.php?p=16130864&postcount=263
Overall, feels cleaner.
Aside from that suggestion rant, this version looks nice and looking forward to your additional updates for Clockwork Recovery. Hoping for ROM Manager support in the future.

Roach2010 said:
I used ubuntu.
Click to expand...
Click to collapse
I meant: did you used make or android's mm?

gnufabio said:
I meant: did you used make or android's mm?
Click to expand...
Click to collapse
Oh, Sorry. I used make. You will need to setup a full build environment if you want to compile recovery.

CWM 6.0.4.8 Advanced Edition / PhilZ Touch Recovery 6.40.1

CWM 6.0.4.8 Advanced Edition / PhilZ Touch Recovery 6.40.1
Main thread + Features + Dev support
http://forum.xda-developers.com/showthread.php?t=2201860
CWM 6.0.4.8 Advanced Edition / PhilZ Touch Recovery 6.40.1​
PhilZ Recovery is a CWM Advanced Edition that adds all the features you could ever miss in CWM.
It is a well proven recovery for many phones.
Please give your feedback, what works, and any bug you could encounter.
Read the features at the Main thread, and check if you are missing something.
To take a screen shot, just slide left!
And don't forget to read about powerful aroma file manager integration and double-tap shortcut (in FAQs).
How to install recovery?
From download link below, you'll get a 'recovery.img' file. Put that recovery.img file at root directory of your
sdcard. (means not in any folder)
Now, go to terminal emulator.
Give command:
Code:
su
You'll be asked to grant superuser permissions, grant it.
Now, give the following command:
Code:
flash_image recoveryonly /sdcard/recovery.img
Wait until it executes the command (4-5 seconds), it is installing the recovery.
Now, normally reboot to recovery and enjoy new recovery!
Download links
Latest version can be found here:
recovery.img (v6.40.1)
https://docs.google.com/uc?id=0B5c3gpyMBJusXzRMMG1tLUxRMWM&export=download
aromafm_beni.zip (v1.91)
https://drive.google.com/uc?id=0B5c3gpyMBJusc204SHRZdTBucHc&export=download
Click to expand...
Click to collapse
Special thanks to:
@Phil3759 : For this awesome open source recovery.
@chraso: For hosting and compatible flags.
AndroidARMv6 Team: For keeping this device alive.
Cyanogenmod Team: For making all these possible.
XDA:DevDB Information
PhilZ Touch Recovery for Galaxy Fit, Tool/Utility for the Samsung Galaxy Fit GT 5670
Contributors
Bhargav97, chraso, Phil3759
Version Information
Status: Stable
Current Stable Version: 6.40.1
Stable Release Date: 2014-05-04
Created 2014-05-07
Last Updated 2014-05-07

:FAQs:​
Q: Wanna know about Aroma File manager?
Visit the aroma file manager main thread for more info---> Aroma file manager main thread
Aroma file manager is a touch file manager which can be used while in recovery. It has options for copy, paste, delete,
change permissions and many others. Also, it has a Terminal inside. So, if you forgot to give correct permissions to any
file you can do that directly from recovery. This file manager has got many themes, font, icons, etc. options and it's UI
is fully customizable.
Q: How to start this File manager in Recovery?
Rename the downloaded file to 'aromafm.zip'.
Create a folder 'aromafm' inside 'Clockworkmod' folder on your sdcard.
Now, move that 'aromafm.zip' file to the 'aromafm' folder.
We're ready now, when you want to use it in recovery just double tap anywhere OR go to "philz Settings" and select
"Aroma File Manager" and it will start up.
If you also want to browse /data, /system and /sd-ext then mount them in the "mounts & storage" option in recovery.
Q: Problems with Aroma file manager startup?
After doble-tapping OR selecting 'Aroma file Manager' option under 'philz settings' if recovery gives error: 'aromafm.zip
not found at /clockworkmod/aromafm' then, wait for 4-5 seconds and again select 'Aroma file Manager', because it maybe
busy mounting sdcard.
If still doesn't work, you've made mistakes in steps mentioned in first post, please do again carefully.
Q: Does your phone every time reboots to recovery?
This happens very rare when you flash the recovery using any bad app or via any wrong (not proper) method. What you can do
is:
-If you've made a backup of your current ROM then just restore only it's "boot" and then select 'reboot to system'.
OR
-You don't have a backup? Then just flash the ROM which you are using currently again and wipe 'dalvik-cache'. Then reboot
to system. Booting process will take time.

NEW: Now you can enjoy the full version of the recovery! Thanks to @Phil3759 for uploading necessary
commits for armv6. And, everything is expected to be bug-free. Please report the bug here if you find any.
SCREENSHOTS:
Main menu and PhilZ Settings
{
"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"
}
GUI Preferences: all is applied live (no reboot). Up to 14 menu height settings, scroll sensitivity, touch accuracy...
27 color settings + 5 alpha transparency levels for every GUI element
Change background image with a custom png (of your device resolution), a solid color (27 presets) or revert to original
cwm image
User configurable touch gestures (feel free to request for new actions)
Setup your time-zone + 30mn offset, super wipe option to install a new ROM
Backup and Restore any partition in a complete freedom, include modem (.img + .bin) and efs (.img + .tar)
Custom backups can also be restored by original CWM Advanced Restore Menu
TWRP Backup and Restore Support + md5 + single/multivolume format
Support multi-cpu compression, md5 check toggle and custom .android_secure path
Choose ors backup volume target
Flash multiple zip files in a raw
Aroma File Manager + Terminal Emulator: launch with a gesture action (double tap is default)
Full Wipe to Install a new ROM (sdcard is preserved)
Free Browse Mode to install zip files: select a default folder to start with and browse up to the root

i tried your recovery by creating a zip update
you should work more on it because the graphic in some aroma installer or aroma file manager doesnt work too good!
and just feels the normal CWM and not Philz recovery !
But any way, Good Job!

Rminsh said:
i tried your recovery by creating a zip update
you should work more on it because the graphic in some aroma installer or aroma file manager doesnt work too good!
and just feels the normal CWM and not Philz recovery !
But any way, Good Job!
Click to expand...
Click to collapse
Aroma File Manager has no LDPI resources. If you want it for LDPI, you can do it, it's an Artist's work. I'm not gonna do it.
Please read the first post carefully. It has no GUI options: So, no themes and all that.
It's not at all like normal CWM in terms of functions. It has got many important functions, atleast for me.
Most important part:
I've worked on this advanced only version for 20-25 days already and made it fully stable.
And...I've worked for almost 2 months on FULL VERSION. Discussed a lot with Phil3759 and finally came to conclusion that it won't work on armv6 unless it's (libtouch_gui) specially compiled for armv6, Which Phil3759 didn't have time and resources for.
So, Be happy with this recovery. No one can give you better philz recovery than this, atleast at present.

Installed your recovery.
Selected clean install ROM option.
Installed a ROM.
Selected Reboot System.
Phone rebooted into your recovery.
Tried various ROMS all rebooted into your recovery and not to the newly installed ROM.
Flashed CWM 6.0.4.6 and installed a ROM and rebooted to installed ROM successfully.
Any ideas what is wrong?
I do like the Aroma FM.
jemail

jemail said:
Installed your recovery.
Selected clean install ROM option.
Installed a ROM.
Selected Reboot System.
Phone rebooted into your recovery.
Tried various ROMS all rebooted into your recovery and not to the newly installed ROM.
Flashed CWM 6.0.4.6 and installed a ROM and rebooted to installed ROM successfully.
Any ideas what is wrong?
I do like the Aroma FM.
jemail
Click to expand...
Click to collapse
Yep...you're correct.
It won't boot into system.
I finally figured out that it is a problem in androidarmv6 sources. You can see change #6205 if you want.
It was maybe fixed just 4-5 days ago by androidmeda and I'll be again making the recovery and give you all for testing.
This is not only problem of your device but it is also there in: tass, gio and beni.

Bhargav97 said:
Aroma File Manager has no LDPI resources. If you want it for LDPI, you can do it, it's an Artist's work. I'm not gonna do it.
Please read the first post carefully. It has no GUI options: So, no themes and all that.
It's not at all like normal CWM in terms of functions. It has got many important functions, atleast for me.
Most important part:
I've worked on this advanced only version for 20-25 days already and made it fully stable.
And...I've worked for almost 2 months on FULL VERSION. Discussed a lot with Phil3759 and finally came to conclusion that it won't work on armv6 unless it's (libtouch_gui) specially compiled for armv6, Which Phil3759 didn't have time and resources for.
So, Be happy with this recovery. No one can give you better philz recovery than this, atleast at present.
Click to expand...
Click to collapse
i read that!
pay attention: the aroma that use in every CWM works fine
but in your recovery it has a bad graphic and kind of blue!
i mean before you create this Philz recovery we had a older version that works perfect!
http://forum.xda-developers.com/showthread.php?t=2483327

Rminsh said:
i read that!
pay attention: the aroma that use in every CWM works fine
but in your recovery it has a bad graphic and kind of blue!
i mean before you create this Philz recovery we had a older version that works perfect!
http://forum.xda-developers.com/showthread.php?t=2483327
Click to expand...
Click to collapse
It works perfect just in the sense: It reboots to system successfully. It lacks Aroma file manager also. And, Aroma file manager with that original green colour doesn't come with armv6 sources nor it will come if you download from original thread.
I'll be fixing reboot to system soon.
That recovery doesn't even have Touch, GUI options and all that.

UPDATE:
-Updated PhilZ sources to 6.23.9 (26.03.2014).
-CM-OTA compatibility fixes.
-Reboot to system bug fixed.
Download link updated in first post.

Bhargav97 said:
UPDATE:
-Updated PhilZ sources to 6.23.9 (26.03.2014).
-CM-OTA compatibility fixes.
-Reboot to system bug fixed.
Download link updated in first post.
Click to expand...
Click to collapse
Thanks for this.
Reboot system is working
Aroma File manager is working
I will test and report any bugs if find them.
Does this version reformat ext4 partitions as ext3 when doing a restore?
jemail

jemail said:
Thanks for this.
Reboot system is working
Aroma File manager is working
I will test and report any bugs if find them.
Does this version reformat ext4 partitions as ext3 when doing a restore?
jemail
Click to expand...
Click to collapse
It reformates the partition to the state in which it was in your backup file. The working of this PhilZ Recovery will be the same way as your CWM 6.0.4.7 works. Nothing different except features.

Tested, worked fine with aroma file manager. Flashed cm 11 has no error.
Keep your work
Here is temporary flashable zip file

As I reported previously in another Clockworkmod thread here, this version also does not restore SD-Ext Ext4 formatted partitions correctly. SD-Ext Ext4 partitions are restored as Ext3 not Ext4.
You can verify this by
1. Create an Ext4 partition on your sdcard using MiniTool Partition Wizard.
2. In CWM create a nandroid backup.
3. Immediatley restore the backup.
4. Check sdcard partition structure in MiniTool Partition Wizard, you will find the partition you created as Ext4 is now reported as Ext3.
Can you confirm this?
Can you remove all background images from your release, maybe except the ClockworkMod Logo. Background images make reading the output from operations difficult.
jemail

jemail said:
As I reported previously in another Clockworkmod thread here, this version also does not restore SD-Ext Ext4 formatted partitions correctly. SD-Ext Ext4 partitions are restored as Ext3 not Ext4.
You can verify this by
1. Create an Ext4 partition on your sdcard using MiniTool Partition Wizard.
2. In CWM create a nandroid backup.
3. Immediatley restore the backup.
4. Check sdcard partition structure in MiniTool Partition Wizard, you will find the partition you created as Ext4 is now reported as Ext3.
Can you confirm this?
Can you remove all background images from your release, maybe except the ClockworkMod Logo. Background images make reading the output from operations difficult.
jemail
Click to expand...
Click to collapse
1) I don't have your device but in my Galaxy 5 it works fine. I make backup (have an sd-ext and has some stuff also inside) and then restore it and everything is still fine. Link2sd still detects it as ext4. Even if it's a bug, it is not related to my PhilZ Recovery but to the androidarmv6 sources and I maybe can't do anything for it (don't have time to submit a patch for review...maybe I don't have that expertise too).
2) Which logo you mean? The one with Big Green Android? I would prefer to keep it that way...don't wanna make it lean more towards an unofficial build. However, I won't be able to do it (even if I want to) right now because my PC is busy and I can't compile on it right now.
Once I get my PC free, I'll make TWRP for your device and provide a final (final for some time) update for PhilZ Recovery (less probability though for PhilZ update).

When I was flashing a rom with aroma (miui v4 to be precise) its showed me get.prop errors.
Saying that my device is not beni and not 5670
And this happened only on this recovery and only with roms with aroma installer, rest of the roms work fine.
And for the TWRP version, TWRP cannot flash memory scripts (like cronmod's int2ext)
Can something be done for that?

Harpratap said:
When I was flashing a rom with aroma (miui v4 to be precise) its showed me get.prop errors.
Saying that my device is not beni and not 5670
And this happened only on this recovery and only with roms with aroma installer, rest of the roms work fine.
And for the TWRP version, TWRP cannot flash memory scripts (like cronmod's int2ext)
Can something be done for that?
Click to expand...
Click to collapse
Aroma installer's dev OR miui rom's dev is lazy to update the update-binary. KitKat requires new update-binary because Google changed the way getprop worked uptil Jellybean.
TWRP? I don't think I've made a TWRP for Galaxy Fit yet.
I wanna tell you only one thing: You are using everything from latest KK branch: PhilZ Recovery and TWRP (maybe you're talking about the one of Galaxy Mini), so please take some time to read on: What all Google changed in recovery with KitKat. Your int-ext script is suffering from old update-binary for sure.

MAJOR UPDATE:
PhilZ Recovery updated to 6.27.9.
PhilZ Recovery FULL VERSION now enabled (Touch, GUI options and everything!).
CWM updated to 6.0.4.8.
Ready for official support!
I seriously want feedback on this version. If it is working, we can now get our phone in "officially supported devices" list.
Download link:
https://drive.google.com/file/d/0B5c3gpyMBJusVmZUN2UxdHFtaWs/edit?usp=sharing

Awesome!
All gui and touch functions work properly.
Flashed a zip and everything works fine except reboot system and power off.
Both of them simply reboot into recovery.
Will report other bugs if found.
And nice job :good:

A little bug. Fixed it.
https://drive.google.com/file/d/0B5c3gpyMBJusSk41Q002c3lneUk/edit?usp=sharing
Give me feedback. Everything else like: screenshot double-tap shortcut for aroma fm (read first two posts to understand), GUI options, etc are especially needed for testing. Post some screenshots also.

[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!!

Development [RECOVERY] [12] [OFFICIAL] TeamWin Recovery Project

Introduction:
Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of our own features. It's a fully touch driven user interface , no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Key Features:
Touchscreen driven with real buttons and drag-to-scroll
XML-based GUI that allows full customization of the layout true theming!
Settings are saved to the sdcard and persist through reboots
Ability to choose which partitions to back up and which to restore
Ability to choose to compress backups now with pigz (multi-core processor support for faster compression times)
Onscreen keyboard
Easy selection of internal/external storage
In addition to the above new features, TWRP features a scripting engine that allows an app to send commands to the recovery for the recovery to perform during startup. We call this scripting engine OpenRecoveryScript. This engine will be put to use immediately in the GooManager app. GooManager will be able to install recoveries automatically for most supported devices. The app will also let you choose to install multiple zips from within Android, wipe, and run a backup.
We are looking for other talented developers, themers, and device maintainers if they are interested in helping with a free, open source project.
Source Code:
GitHub - https://github.com/TeamWin/android_bootable_recovery
Gerrit Instance - http://gerrit.twrp.me
If you have made your own TWRP build for an unsupported device, please let us know. We might add your build to the list of unofficial builds. Bear in mind that we are working hard to add more devices and we may add your device to our official build list later.
Hello, this is TWRP for Poco X3 Pro Global/Indian (vayu/bhima)
touch and adb work
SD card and USB OTG are working
Decryption is working
Send me a beer: Crypto(Preferred) | PayPal
Tree: https://github.com/TeamWin/android_device_xiaomi_vayu
Telegram group: https://t.me/NSSFB
Download: https://twrp.me/xiaomi/xiaomipocox3pro.html
Unofficial 12 builds: https://www.pling.com/p/1833617/

Nebrassy said:
Hello, this is an alpha build of TWRP, for Redmi note 10 Pro Global/Indian/Indian Pro Max (sweet/sweetin)
Click to expand...
Click to collapse
Are you sure you posted in the right subforum?

kamild_ said:
Are you sure you posted in the right subforum?
Click to expand...
Click to collapse
Yeah, I just copied it from my other thread and forgot to edit a part of it

Wow finally Decryption twrp for x3 pro..

anyone try in Poco X3 PRO ?
Thanks.

Can it be installed from the current Recovery on a Poco X3 PRO? Or is it not permanent?

can I flash this if I have arrow recovery?

Nice, thanks to the dev. Is there a site/tutorial which explains the differences of the current recovery systems including why for example Arrow OS has its own?
I guess device memory setup,encryption and OTG plays a big role but since I used TWRP the first time years ago I did not keep up with Android/Recovery development much.

Well, I guess that escalated quickly
This is awesome news when it comes to custom recovery.

Can flash this recovery if im on orangefox with xiaomi.eu?
No problem when boot after flash new recovery? Thanks

Can't wait for version with adb sideload working

finally internal storage working.. great job

Can I install it like a image through my present Orangefox recovery ?

Luko69 said:
Can I install it like a image through my present Orangefox recovery ?
Click to expand...
Click to collapse
yep, just done that, decryption works so I can finally access the DATA partition.

Installed via previous Orangefox, working OK, decryption OK.

Using TWRP to install OTA Updates

I have tested it flashing Arrow vanilla version.
1) Able to read and write from Pc to internal storage and sd card.
2) Able to flash rom and Gapp separately.
3) Able to backup and restore.
It is almost like a perfect twrp to me. Thank you.

Bug report :
Following guides on xiaomi.eu and xda here, before flashing ROMs, "format data".
Data is gone.
"Put the ROM into internal storage."
Connect to PC, internal storage inaccessible from PC !!!
Internal storage was accessible before data wipe.
I tried to boot into system, MIUI loaded, initialization setup done. Reboot to fastboot, flash recovery and boot twrp img, then internal storage accessible again.
So, before flashing a rom, format data.
Done, oh no, internal storage inaccessible by PC AGAIN !!!
Now I'm forced to install rom with microSD, if formatting data is required "before flashing".
I got 3 of this phone, 2 of the are having same issue.
The third is waiting to unlock bl.
Arrow's guide ([ROM] guide, not [GUIDE] guide) had this "wipe data" step "after" zip flashing. So this works.
I'm just wondering if all guides about formatting before flashing rom zip is the must order.

pl1992aw said:
Bug report :
Following guides on xiaomi.eu and xda here, before flashing ROMs, "format data".
Data is gone.
"Put the ROM into internal storage."
Connect to PC, internal storage inaccessible from PC !!!
Internal storage was accessible before data wipe.
I tried to boot into system, MIUI loaded, initialization setup done. Reboot to fastboot, flash recovery and boot twrp img, then internal storage accessible again.
So, before flashing a rom, format data.
Done, oh no, internal storage inaccessible by PC AGAIN !!!
Now I'm forced to install rom with microSD, if formatting data is required "before flashing".
I got 3 of this phone, 2 of the are having same issue.
The third is waiting to unlock bl.
Arrow's guide ([ROM] guide, not [GUIDE] guide) had this "wipe data" step "after" zip flashing. So this works.
I'm just wondering if all guides about formatting before flashing rom zip is the must order.
Click to expand...
Click to collapse
After formatting data, you need to reboot twrp, I believe it tells you that while formatting

Nebrassy said:
After formatting data, you need to reboot twrp, I believe it tells you that while formatting
Click to expand...
Click to collapse
I did reboot again into twrp, even entering fastboot and boot twrp img, but same results if I never let the miui initialize once after formatting.