Database Info

[Release]FeaMod Recovery 1.4 - based on CWM Recovery v. 5.5.0.4.

I've ported the CWM Recovery v. 5.0.2.7 to the Samsung Galaxy I9001 device.
Download it here and follow the instructions to install it. I will post any changes or updates again in this very first post.
Disclaimer: Flashing software onto your device might void your guarantee and may brick your phone. Use the attached software on your own risk. I am not responsible for any bricked device due to this software. You've been warned.
Credits and huge thanks go to:
Koush - for writing the original ClockworkMod Recovery
Ilarrain- for patching graphics.c for the Galaxy Ace device
YardE - providing init.d support to the custom kernel
Riversource - for providing scripts which make the handling of smd files super easy
All the users on this forum who have tested my former versions and helped to debug it - you're great
Are there any differences to "stock" CWM recovery which I can see?
Yes, there are. I've removed additional "No"'s in some functions. I've also changed the background logo and the name of the recovery (though "CWM Recovery" is still there due to make proper credits and copyright thing things). And of course there is the custom kernel included!
How to install/update
If you already have a FeaModRecovery version on your device it's simple:
Download one of the update.zip packages (starting with version 1.3) and copy it to one of your sdcards. Reboot into recovery and install the package (install zip from sdcard -> choose zip from ...).
If you're still on stock recovery or another one follow the the step-by-step instructions on the bottom of the post.
What about the version numbers?
The first number represents major updates (for example update to CWM 6 thus FeaMod v. 2)
The second number represents minor updates. For example if CWM goes up to 5.0.2.8 or I change something on my version.
The third number on some versions represents the kernel since it's a custom one and included in the whole package. So if only the last number changes, I have made "only" changes to the kernel.
Downloads
SMD files to flash via Odin
download FeaMod v1.1: http://www.mediafire.com/?oxxn0676fikkdaw
download FeaMod v1.2: http://www.mediafire.com/?u9996yn6i7rc92z
Hint:
For those who experience boot loops. Before you flash a new version copy the content of your external sdcard onto your pc and format it afterwards. This should help. After you've successfully flashed and rebooted into your system you can copy the files back on your external sdcard.
zip files OC/UV kernel to flash via FeaMod Recovery
WARNING:
Applying the FeaMod Recovery with the FeaCore_OC/UV kernel is dangerous and may brick your phone. In any case it will drain your battery faster when running on 1.8 GHz all the time. Only install it when you know what you are doing! Otherwise install a package without a OC/UV supporting kernel.
FeaMod Recovery 1.3.1 with FeaCore Phoenix OC stable release: http://mediafire.com/?al9s0abvdjrmg6e
FeaCore Phoenix includes:
-BFQ I/O scheduler 2 r1
-SIO I/O scheduler
-OC up to 1.8 GHz
-smartassV2 governor (ondemand is default)
-JFS and CIFS support
-tun included
-bootanimation support
-new boot sound
- I8150 GPU librarys
-cleancache
FeaMod Recovery 1.4 with FeaCore Phoenix OC stable release: http://www.mediafire.com/?jqfbvxflev1jcoz
zip files without OC/UV kernel to flash via FeaMod Recovery
FeaMod Recovery 1.3.1 with FeaCore Phoenix nonOC stable release: http://mediafire.com/?5unogie5i58x85r
FeaMod Recovery 1.4 with FeaCore Phoenix nonOC stable release:http://www.mediafire.com/?ben9s5a8bz1d3gc
if you wanna change your bootanimation, copy your downloaded bootanimation.zip to /system/media/sanim.zip (yes you have to rename it to sanim.zip). Change the modus to 644 (rw-r--r--).
How to change the bootanimation:
Copy the bootanimation.zip to your sdcard and start adb shell:
Code:
mount -o rw,remount /system
cd sdcard
dd if=bootanimation.zip of=/system/media/sanim.zip
chmod 644 /system/media/sanim.zip
Changelog:
FeaMod v.1.1:
+ Performing a factory reset aka wipe data now doesn't delete the external sdcard anymore.
+ Performing a backup with no changes in the mount menu will automatically backup .android_secure as well.
+ The external sd card will no longer be "backuped" unless you manually mount the sd-ext in the mount menu.
FeaMod v.1.1.1:
+Kernel changes: initd support - implemented by YardE. BFQ I/O Scheduler implemented by me
FeaModRecovery v.1.2:
-Included the rest of the changes made by Koush
-You can now select wheter you wanna make the backup onto internal or external sdcard
-I've decided to let go the backup of the external sdcard (save .android_secure of course). Because it can destroy your internal sdcard when not properly handled and backing up the external sdcard on the external sdcard doesn't make any sense at all.
FeaModRecovery v.1.3:
- fixed a bug which led to a md5 mismatch when recovering only single partitions (advanced recovery).
- reimplement the reboot into recovery option. This option now makes sense again (see next point).
- I provide you from now on with update.zip packages to update FMR from within an already installed FMR.
FeaModRecovery v.1.4:
- https://github.com/CyanogenMod/android_bootable_recovery/commits/ics/
Kernel (FeaCore_1.0 and FeaCore_1.0_OC/UV):
- update to jhash3 (for better reliability on data connections)
- implemented BrainFuck Scheduler as main scheduler (CFS is gone for the moment)
- implemented interactive governor (ondemand is still default and already very aggressive)
- implemented BFQ I/O
- init.d support (thx to YardE)
Kernel FeaCore Phoenix (OC and nonOC):
-jhash (battery drain is too high with jhash3)
-CFS as CPU scheduler
-SmartassV2 as new governor (ondemand is default)
-CFQ, BFQ, SIO and Deadline as I/O schedulers (SIO is default)
-supports Boot animation
-custom Boot sound
-cleancache patches
-I8150 GPU libraries
How to use
Start the FeaMod Recovery by pressing your Power Button and the Volume Up button simultaneously. Hold both keys until the Samsung Logo appears. Release both keys after additional 2-3 seconds and wait. The system now boots into FeaMod Recovery.
Navigate in the menu: Volume Up/Volume Down buttons
Select item: Menu Button
Return to start screen: Return button
Additional hints
Old versions (all versions until v.1.1.1): To backup your external-sd too, you need to mount the sd-ext partition in FeaMod Recovery:
Select mounts and storage -> mount /sd-ext.
Warning:
Don't backup your external sdcard if its content is larger than the space on your internal sdcard left!!!
If not manually mounted only your apps on the sd-ext will be saved.
In case the system won't recognize your external sdcard: Copy the content of your external sdcard to your PC and format it within your ROM. Copy the files back onto the newly formatted external sdcard. Thx to Igor_999 for stumbling across that problem
Sources on github:
https://github.com/manveru0/FeaMod-Recovery
Have fun with it!
Do it step by step ;-)
For Odin related things, look also at the attached image.
Important: You have to install busybox under /system/xbin/ in order to get the init scripts working.
Get "Busybox Installer" from the market. That version let you choose the location to install it.
1. If you don't have at least XXKP4, download it from samsungmobile (you need to register, but it's worth it)
Browse through the forum and go to our devices, there you'll find the ROMs. If your comfortable with your ROM
go to step 3.
2. Download Odin 4.43 from here and flash the files. If you have a one package file, download AriesVE.ops from this post and select that one in Odin
under OPS file. If you downloaded XXKP4 select the bootloader.tar as the BOOT file, the MODEM file as the phone file, the PDA file as the PDA file and the CSC file as the CSC file. Flash it and wait until your phone has rebooted back into the system.
3. Download FeaMod Recovery v.1.2.
4. Open Odin again and select the AriesVE.ops as the OPS file. Tick the one package option under OPTION. The select the FeaMod file as the One Package file. Flash it! After 10 to 15 secs your device will reboot into your system.
6. Copy the Universal Adrenaline v.13 zip file (download it from here: http://forum.xda-developers.com/showthread.php?t=1236779) to your internal or external sdcard.
5. Shut your device down and reboot into FeaMod Recovery v.1.2. by holding the Volume up and Power Button simultaneously until the Samsung Logo appears, hold it for 2,3 seconds longer and release both buttons. Welcome to FeaMod zone :-D
6. Make a full backup either to your external or internal sdcard (look at the options you got) just to be sure.
7. Go to mount and storage -> mount /system
8. Go to advanced and select fix permissions.
9. Go to install zip from sdcard and select your fresh copy of adrenaline shot v. 13.
10. Reboot into system.
you got it! You now have FeaMod Recovery v.1.2. with the latest kernel from YardE and me which supports init.d and has BFQ as the default I/O scheduler. And you should have the applied adrenaline shot by now. Test it either with a terminal (you should have the /system/etc/init.d folder) or by the quadrant benchmark (you should get at least 2500 points). In case there are any questions left, ask for.

Nice. I just flashed it and its backing up right now. It seems to work like a charm. Thanks!

it's looks like this right??

hi. sorry i don't get it. what is the function for this? is it to backup my current ROM?

OK, I had a bad day today, but this made my day!
Thank you sooo MUCH!
So, now... Custom ROMs much more easily?

budakmaran said:
it's looks like this right??
Click to expand...
Click to collapse
Yes, thats correct!

AWESOME
I've said it before and i'm saying it again You are awesome!!! Thnx a lot.
And also a big thank you to netchip without whom i dont think we could have had this
I'm soooo happy! now cyanogen mod to look forward tooo

Nice cwm works but somehow my sdcard is causing problems.... I will format it in windows and try it again
Because the problem is that my phone freezes and turns off when my sdcard is in my device
Sent from my GT-I9001

Blumdum said:
Nice cwm works but somehow my sdcard is causing problems.... I will format it in windows and try it again
Because the problem is that my phone freezes and turns off when my sdcard is in my device
Sent from my GT-I9001
Click to expand...
Click to collapse
You can also format your sdcard in CWM Recovery if your phone doesn't freeze in CWM:
mounts and storage -> format /sd-ext

sweeeeeeet ill try this later looking forward to cyanogen mod now we have working cwm

manveru0 said:
You can also format your sdcard in CWM Recovery if your phone doesn't freeze in CWM:
mounts and storage -> format /sd-ext
Click to expand...
Click to collapse
ok the ext-sdcard seems to work after i formatted the card
just have to copy back the files

Hi manveru0,
wonderful job dude! Thanks a lot! (I've clicked on the thanks button but when you see the number of users on this part of the forum I dare write you a note )
I've installed and backuped my device and it worked like a charm.

traedre said:
Hi manveru0,
wonderful job dude! Thanks a lot! (I've clicked on the thanks button but when you see the number of users on this part of the forum I dare write you a note )
I've installed and backuped my device and it worked like a charm.
Click to expand...
Click to collapse
you are welcome. Thank you, good to hear

Am I right that there is init.d support included?
Sent from my GT-I9001 using XDA App

Nice work! Thanks for all the guys!
---------- Post added at 02:49 AM ---------- Previous post was at 02:38 AM ----------
Hi,
the file I downloaded from http://www.mediafire.com/?1wbb668gs2t7d0k has a different MD5.

Works like a CHARM! LOVing it!

Very nice work! There is one problem. Members from the site 4pda.ru actively using CWM. Only for Skype both cameras are becoming as rear, front camera disappears. The guys were asked to write about this issue. It is strange that this is not who did not notice. Itself is not using Skype. Check it out please.

quest221 said:
Nice work! Thanks for all the guys!
---------- Post added at 02:49 AM ---------- Previous post was at 02:38 AM ----------
Hi,
the file I downloaded from http://www.mediafire.com/?1wbb668gs2t7d0k has a different MD5.
Click to expand...
Click to collapse
Yep, that's perfectly okay because I have uploaded a new file with a fixed bug yesterday evening. See also the first post

manveru du bist ein konig
thanks for one package
i will test it today
btw what for a cpu government was there setted up before?

problem this cwm in skype. 2 back camera, no working front camera, only back... fix it please.
sorry my english...

[SCRIPT][DUAL-BOOT][I9305] db

(Sorry for english !!)
!! Some problems with Android 5.1.x installed on External.
[Dual-Boot] I9305 [SCRIPT]
Hi. Because i dont find any kernel/script for I9305 with Dual-Boot, i try to make this script for test roms (but can be use day by day without problem).
This script help to patch .zip rom/kernel/gapps (and other i think) for install him on SDCARD. (without touch your internal rom).
How can you do this? Need to repartition your sdcard in 3 parts
1. With your sdcard data (files/music..etc)
2. external System (for system rom)
3. external Data (for data rom)
What you need to know !!!!
- Thanks on @Nicene Nerd for this App. I'm inspired from him.
- I'm not a developer.
- I don't now so much about linux (so, script not have a best optimization)
- This script is better good for people who test roms (like Lollipop).
- If you dont try this script, don't say anything. (only if you have some problem/stucks)
- Install on Internal roms like: Amcha / N4 / ..etc (big roms)..because i try to install on external rom and dosen't work
- Rom like Nameless / RR / ..etc can be install on external
- Anyone who want help me to make this script better, say here where need to edit (with what) and who can code help
- Say here what rom/kernel/script work or dosen't work to install on external. For modify script
What you need.
MiniTool Partition Wizard (or other program to repartition sdcard)
USB Cable (for repartition)
A phone (i9305 of course)
SDCARD 16gb (or more) Class 10 (if you have class 4 or other..your external rom run slow)
Backup your sdcard data (for safe)
Backup your phone (for safe)
ROM with root permision.
Water (because is good for your health)
First time you need to repartition sdcard
First partition: FAT32 (split memory from this..is good option)
Second: 1600 mb (1,6 gb) for system
Third: 2500 mb (2,5 gb) minimum memory for data
How can do this:
On MiniTool show your sdcard (like this)
{
"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"
}
1. Right click on him > Split
2. On New Partition Size you need to have minimum (system + data) 1600 + 2500 = 3600 mb (3,6 gb)..If you want more memory on data, you can type more than 3600 mb (i need more so i split 7000 mb)
After write your value, press ok
Now look like this
3. Right click on new partition (H on me) > Delete
Now you have unallocated partition
4. Right click on unallocated partiton > Create > Ok (on warning)
5. On box you need to edit:
Create As: Primary
File System: Ext4
Partition Size: 1600 (because is system partition)
After this. Press Ok
6. Right click on unallocated partition > Create > Ok (on warning)
Create As: Primary
File System: Ext4
Partition Size: dont modify
After this. Press Ok
7. Before press Apply, check if look like this
Now you can press Apply and wait
Good
After sdcard was partitioned, go to next step
Put my script on your SDCARD
(Why in sdcard? because internal/external rom view the sdcard everytime)
(internal/external rom have separated 'internal memory')
1. Unrar on desktop (right click on archive > extract here)
2. Copy 'db' folder to your sdcard
3. Check if 'db' folder is on your sdcard
4. With file explorer (i use Root Browser), go to db folder and install 'terminal.apk'
5. After install run him
On terminal:
Type: su (for superuser permision)
Type: cd /mnt/extSdCard/db (or anywhere is db folder location..on LolliPop is: cd extSdCard/db)
Type: sh db.sh
Now you are in script menu
Option: 1 -> Save Internal BOOT.IMG
Option: 2 -> Flash Internal BOOT.IMG and Reboot phone (if not reboot, try to reboot manualy)
Option: 3 -> Mount Internal partitions on root direcotry (/.dbSystem & /.dbData)
Option: 4 -> Clean Internal partitions (use this if you are in External rom)
Option: 5 -> Save External BOOT.IMG
Option: 6 -> Flash External BOOT.IMG and Reboot phone (if not reboot, try to reboot manualy)
Option: 7 -> Mount External partitions on root direcotry (/.dbSystem & /.dbData)
Option: 8 -> Clean External partitions (use this if you are in Internal rom)
Option: 9 -> Patch file for External rom (file like rom/gapps/pa-gapps/kernel..etc)
Option: 0 -> uMount /.dbSystem & /.dbData
Option: fb -> Flash manualy BOOT.IMG file
Option: ie/ei (hidden command) -> I'm work on this.. Is a experimental function. Don't use it
Patch files for external rom:
1. Copy on 'db' folder rom who want to patch, gapps archive and kernel your need
2. Run script on terminal
3. Need to save your Internal boot.img (Option 1 on menu)
4. Option 8 to clean your external partitions (if was used before with other rom).
5. Option 9 to patch
6. Type rom/gapps/kernel..etc archive name like: my_rom.zip > And press enter
7. Wait to patch (all patched files have pre name ext-
NOTE: If you patch rom/kernel (with boot files), you need to watch if script modify any fstab file. If no, external rom not work!
8. After you patch all you archive need..go to recovery (i use TWRP 2.8.5.0) and flash him but need to kep order:
- First ROM zip
- Second GAPPS (or PA-GAPPS) (or without this)
- Third KERNEL (if is need)
- .. other patched scripts
9. After flashing, reboot and wait to new external rom start up
(if you have any error (boot loop/other) you can flash internal boot stored in "sdcard/db/.db/.imgs/boot-int.zip")
10. After your external rom is ON, install 'terminal.apk' from sdcard
11. Run script on terminal
12. Save your External BOOT.IMG (Option 5)
13. Enjoy with your external rom.
(To switch rom you have option 2 and 6 or flash manualy .zip stored in "sdcard/db/.db/.imgs/boot-*.zip")
I forgot something?
Another explain: http://forum.xda-developers.com/showpost.php?p=59570171&postcount=11
Changelog
Version 1.3:
+ Removed experimental (duplicate partitions)
+ Removed rsync
+ Add check "Where i am now" for check what system mounted (internal/external) for optimized script
+ On start, check if rom/kernel changed and you can save new rom much easy
+ Disabled some options from menu (depend where are you (internal/external) rom)
+ On mount/ckeab internal/external partitions, now check if is mounted property
+ Terminal updated at last version
Version 1.2:
+ Some bug fixes (major bug fixes)
+ Add rsync for Duplicate Partition (ie/ei command. hidden command because not work now
+ Patch init. files from kernel (work with pureSTOCK / pureCM kernel) (i'm not tested, but you can flash now a big rom (like Amcha/N4 Lite) in external rom)
Version 1.1:
+ Some bug fixes
+ Mkdir folder check after create
Version 1.0:
+ It's alive !

thanks fro this script, but i have a question:
if I understand how it works, every time I have to save the rom I'm using...it creates a backup of rom in flashable zip format.
to switch from one to another rom I have to flash the zip saved...so what is the difference with a nand backup/restore?
and what are the performance and the lag of a rom thst run on sd card?

LeoDeos said:
thanks fro this script, but i have a question:
if I understand how it works, every time I have to save the rom I'm using...it creates a backup of rom in flashable zip format.
to switch from one to another rom I have to flash the zip saved...so what is the difference with a nand backup/restore?
and what are the performance and the lag of a rom thst run on sd card?
Click to expand...
Click to collapse
Script was patched a .zip file for install on External partitions (system/data).
And modify boot.img (mounts).
Difference on nand backup/restore and this is time and to swich internal to external is much faster. (only flash boot.img for swich)
I make a Benchmark and score is 30k with Nameless (0303 version).. When you copy some file in sdcard (with usb) or you install a apk file (depend so much what sdcard you have).. have some lags..but if i use day by day i dont have lag.
I dont now if i explain so good how script works because i dont now so much english..
Look at uploaded image. How much time need to change rom from ..3 minutes..all i need is to flash boot.img (for internal/external) and reboot..
This is a good option in my opinion

il3gal said:
Script was patched a .zip file for install on External partitions (system/data).
And modify boot.img (mounts).
Difference on nand backup/restore and this is time and to swich internal to external is much faster. (only flash boot.img for swich)
I make a Benchmark and score is 30k with Nameless (0303 version).. When you copy some file in sdcard (with usb) or you install a apk file (depend so much what sdcard you have).. have some lags..but if i use day by day i dont have lag.
I dont now if i explain so good how script works because i dont now so much english..
Look at uploaded image. How much time need to change rom from ..3 minutes..all i need is to flash boot.img (for internal/external) and reboot..
This is a good option in my opinion
Click to expand...
Click to collapse
ok understand...
but i'm not still sure of utility of the external boot.
foe example: i can flash stock rom on internal and save boot.img...
after i flash aosp rom always on internal and save boot.img with another name.
in this case the time to switch one to another rom is the same 3 minutes.
i wrong?

LeoDeos said:
ok understand...
but i'm not still sure of utility of the external boot.
foe example: i can flash stock rom on internal and save boot.img...
after i flash aosp rom always on internal and save boot.img with another name.
in this case the time to switch one to another rom is the same 3 minutes.
i wrong?
Click to expand...
Click to collapse
hmm..but system files and data files where is? same in internal? You cant..
You need other partitions for system / data if you want another rom
For internal partition mount points is mmcblk0p13 (system) and mmcblk0p16 (data)
For external is mmcblk1p2 (system) and mmcblk1p3 (data)
Hm..understand?

il3gal said:
hmm..but system files and data files where is? same in internal? You cant..
You need other partitions for system / data if you want another rom
For internal partition mount points is mmcblk0p13 (system) and mmcblk0p16 (data)
For external is mmcblk1p2 (system) and mmcblk1p3 (data)
Hm..understand?
Click to expand...
Click to collapse
maybe i explain wrong.
so i try to repeat well.
1) flash stock rom on internal.
2) backup stock rom (option 1 of your script)
3) full wipe and flash aosp rom always on internal.
4) backup aosp rom (always with option 1 of your script)
(if i'm not wrong we will have 2 backup zip file)
5) switch rom (option 2 of your script)
its possible?

LeoDeos said:
maybe i explain wrong.
so i try to repeat well.
1) flash stock rom on internal.
2) backup stock rom (option 1 of your script)
3) full wipe and flash aosp rom always on internal.
4) backup aosp rom (always with option 1 of your script)
(if i'm not wrong we will have 2 backup zip file)
5) switch rom (option 2 of your script)
its possible?
Click to expand...
Click to collapse
aaaaaa...no..

il3gal said:
aaaaaa...no..
Click to expand...
Click to collapse
ok thanks

LeoDeos said:
ok thanks
Click to expand...
Click to collapse
I make now how i use this script ..with images..

Not meaning to rain on the parade here but it basically seems to be similar to just backing up and restoring like nand. It may not be exactly the same but it seems to be a similar thing.
Unfortunately it looks like it can't perform a proper dual boot.

Explain 2
I made a tutorial how i use this script. Skip the repartition step because is easy (repartition need to make one time..not everytime want you install external rom)
On my rom (N4 Elite Lite v5).
1. Copy what files need to patch in db directory (where is script). In my case (pa_gapps-modular-pico-5.0.1-20150221-signed.zip & nameless-5.0.2-20150318-i9305.zip)
2. Run script.
3. First time need to save your internal boot.img (kernel). (for swich roms)
(because script modify kernel (mount point on kernel) and when you swich rom, all who make script is to flash kernel for internal/external rom)
4. After you save internal kernel, go back to menu and type option 9 to patch zip rom/gapps/kernel..etc
(if rom have a included kernel, watch if script find a fstab.* file and if can be edited. If not edited, external rom not work)
(all rom/kernel/gapps..other script need to modify updater-script or update-binary (pa-gapps use this)..if not edited, you cannot install rom on external partitions
5. After i patch rom file, i need and gapps because i use Google Play Store, so, i patch and gapps (go in menu, option 9 and type gapps file name)
(Now my db directory look like this)
6. All good. Now i want to be sure about my external partitions is clean, and i go to option 8 to clean him
7. After clean, reboot in recovery and flash ROM (ext-nameless-5.0.2-20150318-i9305.zip) and after GAPPS (ext-pa_gapps-modular-pico-5.0.1-20150221-signed.zip)
8. Reboot phone and wait to rom boot complete..(first boot may during a time)
(At Total Memory, is total memory allocated on 'data' partition (from repartition) (third partition))
9. After boot is complete..install 'terminal.apk' from db folder (script folder)
10. Run script from terminal.
11. Option 5 (for save this external boot.img)
12. Voila..now i have 2 separated roms..installed in 2 separate partitions (internal system/data and external system/data)
To swich i have 2 option. From terminal (script). (example) If i'm in internal rom and i want to swich, open script an type option 6..For flash external kernel and reboot phone to boot in external rom.
From recovery: flash manualy .zip files stored in sdcard/db/.db/.imgs/boot-*.zip
Now is good explication?
djb77 said:
Not meaning to rain on the parade here but it basically seems to be similar to just backing up and restoring like nand. It may not be exactly the same but it seems to be a similar thing.
Unfortunately it looks like it can't perform a proper dual boot.
Click to expand...
Click to collapse
Is not same. Do you know dual windows on pc?
Partiton C have Windows 7 (example)
and partition D have Windows 8.1 (for example)
If you boot pc, have a question "Who windows want to boot" 7 or 8.1..and you choose.
My script is same, but for 'choose', need to flash a kernel (external/internal..depend what you want to boot)
hmm.
This script is same with http://forum.xda-developers.com/showthread.php?t=2639112 ...but is not app..and dont have some options like "backup"..

Tested with:
ROM
- AICP 8.0
- Resurrection Remix® LP
- NamelessROM
- Cyanogenmod 12
- SlimLP
KERNEL
- Boeffla 3.0-alpha9
Changelog
Version 1.1:
+ Some bug fixes
+ Mkdir folder check after create
I see some people was download script. Can give me feedback? (db_1.0.rar - [Click for QR Code] (1.11 MB, 32 views))
What rom is work and what not? (i dont have time to test all roms)

Abandoned.

il3gal said:
Abandoned.
Click to expand...
Click to collapse
why?

LeoDeos said:
why?
Click to expand...
Click to collapse
Because i dont have feedback..
I continue use this but i dont post update..
32 downloads / 0 feedback..
I think people don't understand how it works ..hm
I'm bad to explain this

il3gal said:
Because i dont have feedback..
I continue use this but i dont post update..
32 downloads / 0 feedback..
I think people don't understand how it works ..hm
I'm bad to explain this
Click to expand...
Click to collapse
i think you should leave the download link.
it could help for someone.
when i'll time and an sd card bigger i want try your method

LeoDeos said:
i think you should leave the download link.
it could help for someone.
when i'll time and an sd card bigger i want try your method
Click to expand...
Click to collapse
ok. i remove and [abandoned] .
just wait. now i try to add some things on script.

il3gal said:
ok. i remove and [abandoned] .
just wait. now i try to add some things on script.
Click to expand...
Click to collapse
thanks

+Tested with:
ROM
- AICP 9.0 (test version)
Changelog
Version 1.2:
+ Some bug fixes (major bug fixes)
+ Add rsync for Duplicate Partition (ie/ei command. hidden command because not work now
+ Patch init. files from kernel (work with pureSTOCK / pureCM kernel) (i'm not tested, but you can flash now a big rom (like Amcha/N4 Lite) in external rom)

+Tested with:
ROM
- N4 Elite Lite v7 (but i don't now how much fast is) (when i have time, i will tested)
Changelog
Version 1.3:
+ Removed experimental (duplicate partitions)
+ Removed rsync
+ Add check "Where i am now" for check what system mounted (internal/external) for optimized script
+ On start, check if rom/kernel changed and you can save new rom much easy
+ Disabled some options from menu (depend where are you (internal/external) rom)
+ On mount/ckeab internal/external partitions, now check if is mounted property
+ Terminal updated at last version
Who know a universal reboot command for any rom? Because reboot not work on N4 Elite Lite rom

Roms for GT-I8160P version guide

Hi people, here is a short instruction if you have a P or L version of the I8160 and want to update this (great) old phone. credits to xdas-e
for a while i thought that roms didnt work on the P version, because when installing roms i got the error that the rom was only for I8160, not I8160P. so yeah it is possible, maybe this is common knowledge, but i couldnt find out how before i found this information.
I have not tested this exhaustively but i believe they all should work, because i believe the only difference from the P version is that it has an NFC module.
]------- modify the rom for P version:
1.- Get the custom ROM.
2.- Get the /system/lib/tee folder contents from your GT-I8160P JB installation (from stock rom). You may need root access, although in my case I could simply move trough the hidden directories and copy the folder to my sd card.
3.- Swap the /system/lib/tee folder, and put what you got from step 2, into the zip file of step 1, same place, same everything. You may very well dispose the original /system/lib/tee folder in the zip file.
4.- Change /system/build.prop and introduce a P in every GT-I8160 entry (from GT-I8160 to GT-I8160P).
5.- (tricky one) look for the updater script file within the custom ROM zip file, and delete (or add a P) the first complete entry of the assert command (you shall see some GT-I8160 there). in my case it was located under META-INF\com\google\android\.
------- from here you have successfully modified the rom for the P version, these steps just show the installation:
6.- If you dont already have CWM, get yourself one (I used this one [JB] CWM Recovery 6).
7.- Put both zip files into your sd card; get a copy also of gapps (google apps, play store etc) for the android version of the rom.
8.- Back up all your data.
9.- Swicht off your phone and restart in recovery mode (up volume, home and power buttons pressed simultaneously).
10.- Load from the external sd card the CWM zip file.
11.- Make a full ROM backup to restore if things go wrong. Wipe data/factory reset; wipe cache partition; wipe dalvik cache (under advance options), format /system if needed (see rom instructions).
12.- Install from external sd card: a) custom CM rom; and b) gapps if you're for it.
13.- Restart.
14.- You shall be done!!! (first boot takes a long time)
good luck! my phone was crap with stock and now it works great, so basically it saved me from buying a new phone.. a big thanks to all the rom developers for this device .

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

Samsung devices (2) stuck in system boot splash

HI,
I have 2 Samsung devices with TWRP installed, and I can access the TWRP recovery menu. When I install the flash ROM and try to boot, devices are stuck in system boot forever.
Device 1: SM-T800, with LineageOS 14.1 previously. I opened an email and the device got hacked, so I did a factory reset (which failed), then re-flashed the latest TWRP and recovered rescue mode. Now when I flash the Lineage ROM (from TWRP) the device does not boot to system but keeps showing the splash screen. I think the hack might have placed immutable files under system. could I format this partition to zero it out via ADB? What other choices are there?
<EDITED>
Device 2: Galaxy S3 GT-I9300 - I solved this so i removed this section.
Thank you for any help.

Beeblebrox-BSD said:
HI,
I have 2 Samsung devices with TWRP installed, and I can access the TWRP recovery menu. When I install the flash ROM and try to boot, devices are stuck in system boot forever.
Device 1: SM-T800, with LineageOS 14.1 previously. I opened an email and the device got hacked, so I did a factory reset (which failed), then re-flashed the latest TWRP and recovered rescue mode. Now when I flash the Lineage ROM (from TWRP) the device does not boot to system but keeps showing the splash screen. I think the hack might have placed immutable files under system. could I format this partition to zero it out via ADB? What other choices are there?
Device 2: Galaxy S3 GT-I9300, with working TWRP. This device is giving a "Failed to mount /efs (Invalid argument)" error. The previous setup was shared storage with sdcard and encryption on both internal and sdcard. The sdcard got corrupted, hence the error. This post suggests running
Code:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst1
but the device does not have identifiable boot device under /dev/block. I think this might work if I can identify the boot partition name?
Thank you for any help.
Click to expand...
Click to collapse
Flash a custom ROM for i9300 via TWRP. Download a custom ROM for i9300 and the appropriate Gapps to go with the ROM, store them on external sdcard. When you are in TWRP, before you flash your ROM, select the "Wipe" option, then select "advanced wipes", on the next menu, choose the system partition, data partition, cache partition and dalvik cache partition then swipe the slider to wipe. Then go back to home screen in TWRP and choose the "Install" option, then choose your ROM file and your Gapps file then swipe to flash. When the flash is finished, select the "Reboot system" option and see if it boots into system.
If that doesn't work, we will take some steps further back and try starting from the beginning.
Keep in mind that some of the custom ROMs for i9300 may have a different partition structure and partition sizes than the stock firmware for i9300 has and may require resizing certain partitions such as the system partition by flashing a custom PIT file like the Galaxy S2 had to do before it flashed certain custom ROMs.

Hi, thanks for the input.
* I had already solved the GT-I9300 issue before your post (I should have added to thread rather than edit the original post). I solved issue with that device by including system partition in the wipe.
* For the SM-T800, I used a LineageOS-14.1 that I had stored somewhere. That also did not work, until I only flashed Lineage and did not include any GApps. If I really need it, I can always flash later. I assume the latest GApps 7.1 build conflicts with older ROMs.
An unexpected problem was the lack of current ROMs for the 2 devices. SM-T800 has nothing other than last build Lineage-14-1-20190205. The I9300 has several unofficial ROMs floating around for newer Android versions, but they are all debug/dev builds with enabled options that drain the battery very quickly.
If anyone comes across a decent ROM for either of these devices please LMK. Thanks.