[NST][CWR][RC2] Clockworkmod based Recovery - fixed backup issue - Nook Touch Android Development

{
"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"
}
DISCLAMER and WARNING:
I'm not responsible for bricked devices, dead SD cards, lost data. Make a backup before you try anything described here!
Making a backup with CWM only includes the following partitions: boot, system, data, cache. It doesn't include the /rom partition which contains data thats unique for every device. Use this backup method to make a full device backup.
Please do not use the restore backup function to restore backups made with versions prior and including RC1. They are faulty and restoring them damages an important bootfile of your nook. It isn't important with which version you restore, if the backup was made with Beta1, Beta2 or RC1 it will fail! Please read http://forum.xda-developers.com/showpost.php?p=19945955&postcount=37
Changelog:
RC2
changed mount options of the boot partition (fixes the bad backup issue)
updated sources to the newest ones from CM
some internal changes for the screen refresh
RC1
reboot recovery in the advanced menu is now working
boot to recovery is now a bit faster
switched to automated build environment
moved some files to the appropriate place
Beta2
Added page refresh after pushing back or select buttons, to get rid off the ghosting. Still not perfect, but good enough for a recovery.
Beta1
First release
Hi,
after some trying and hacking I was able to build a working Clockworkmod based recovery for the Nook Simple Touch.
It is still a beta-version, but everything I tested (backup, restore, mount USB, install zip) works.
If you want to try it, just write one of the imgs from the sd_xx_clockwork-....zip to a SD card with at least the capacity mentioned in the filename. Put the card in your N2E and reboot. Do not write these images directly to the Nook, it will brick your device permanetly!
To replace the standard recovery of the N2E, copy also the install_cwm_recovery_xx.zip to the sdcard, boot into CWM and use the install zip from sdcard option to install it (it just replaces uRecRam and URecImg in the /boot partition, so you can also do it manually, if you want).
There is really no need to install CWM on the device as long as you aren't developing and need it constantly. Please keep in mind that replacing the stock recovery will remove the restore function, that can be triggered by pressing the two lower buttons (or by eight failed boots). Restoring the stock recovery with install_stock_1.1_recovery.zip will bring back this function.
How to boot into recovery:
Power down the N2E
Press the power button for ca. 3 seconds, so that the device boots (you don't have to hold the power button after the 3 seconds)
As soon as the display changes to the "read forever" screen , push and hold the lower left and the lower right button until the screen changes again
Wait until you see the recovery
If you want the standard recovery back, use the install_stock_1.1_recovery.zip (See next post).
Button layout:
Both Buttons on the left: BACK
Upper button on the right: UP
Lower button on the right: DOWN
n button: SELECT
Power button: TOGGLE DISPLAY
Known bugs:
after restoring the boot partition, most of the times the recovery ends in an unresponsive state. The nook has to be rebooted by holding the power button. This is not affecting the restore!
"reboot system now" doesn't work always (sometimes you have to power cycle), experienced it only when booting from SD
Reboot to recovery by using adb reboot recovery doesn't work. (needs a new adbd binary in the uRamdisk)
DISCLAMER and WARNING: I'm not responsible for bricked devices, dead SD cards, lost data. Make a backup before you try anything described here!
Credits go to:
koush, author of Clockworkmod recovery http://www.clockworkmod.com/
Cyanogenmod-Team, for their great build environment and the Nook Color recovery
The people who wrote Noogie (SD-Card is based on Noogie) http://nookdevs.com
Tyler Montgomery (IOMonster) http://nookdevs.com , buildenv for bootable OMAP-SD-Cards

Useful update.zip's
rom_backup.zip
Makes a backup of all the files that are on the /rom partition. Saves it to the SD-card /backup/rom_backup.tgz.
This partition contains some important data, that is unique for every device (serial, MAC, ...).
install_stock_1.1_recovery.zip
Installs the recovery from the stock 1.1 update.
MinimalTouch
Automatic Rooting + Gapps by eded333
install_remount_commands.zip
Adds the commands systemrw (remount /system rewritable) and systemro (remount /system readonly).
If you have useful update.zip's that should be included here, please let me know.

Great work
I see you listed "install zip" as one of the features tested, does that mean we can create update.zip's and run them trough cwm?

ros87 said:
I see you listed "install zip" as one of the features tested, does that mean we can create update.zip's and run them trough cwm?
Click to expand...
Click to collapse
Yes, you can create update.zip's and run them trough cwm, install zip works fine. That should make some of the rooting guides and changes of the framework easier.

mali100 said:
Yes, you can create update.zip's and run them trough cwm, install zip works fine. That should make some of the rooting guides and changes of the framework easier.
Click to expand...
Click to collapse
It sure would!
I noticed that regular update zips use "update-script" while the B&N files use "updater-script", do both work?

ros87 said:
I noticed that regular update zips use "update-script" while the B&N files use "updater-script", do both work?
Click to expand...
Click to collapse
I think update-script is the old, no longer supported file-format. As far as I know CWM (since version 3) only supports updater-script with an updater-binary (that interprets the script). I only tested the latter.

make it fully working without ghosting and we have the base for custom roms, this is simply great.

very good news.
I hope, a step closer to CyanogenMod or other custom Rom...

Would it be possible to resize the image to fit in a smaller uSD?

Thanks for taking the time into making this tool available for the NST, this opens the possibilities even more for our ereader

met67 said:
Would it be possible to resize the image to fit in a smaller uSD?
Click to expand...
Click to collapse
Yes that should be possible, I almost fell of my chair when uncompressing the archive
I'm guessing he just smacked the files onto his 2GB card and made an image of it
But yes it's a problem beyond SD cards, I have my Ubuntu VM on a SSD with limited space so 2GB is not a small issue for me
With that said, there's a limit as to how small a fat32 partition can be, but 64MB is doable.

user4242 said:
make it fully working without ghosting and we have the base for custom roms, this is simply great.
Click to expand...
Click to collapse
I don't think a recovery is a good base for a custom rom. If you want to build one, use the update to 1.1 as base, you should be able to install it with this recovery.
met67 said:
Would it be possible to resize the image to fit in a smaller uSD?
Click to expand...
Click to collapse
Yes it is, I made it that big because I wanted some space for the backups. I will add an 128MB version tomorrow, when i upload a new beta with less ghosting.
ros87 said:
I'm guessing he just smacked the files onto his 2GB card and made an image of it
Click to expand...
Click to collapse
I haven't µSD-cards that small

Very cool! Do you expect to submit this upstream and have it supported in ROM Manager?

mali100 said:
I haven't µSD-cards that small
Click to expand...
Click to collapse
Showoff!, 2GB is my biggest one, kinda the crown of my collection

FletchF said:
Do you expect to submit this upstream and have it supported in ROM Manager?
Click to expand...
Click to collapse
Once it's stable and well tested, yes.
By the way, does someone know how the reboot to recovery from a running system works on other devices? Does this work on the Nook Color?
"adb reboot recovery" and "reboot to recovery" from CWM just cause a normal reboot to android.

mali100 said:
Once it's stable and well tested, yes.
By the way, does someone know how the reboot to recovery from a running system works on other devices? Does this work on the Nook Color?
"adb reboot recovery" and "reboot to recovery" from CWM just cause a normal reboot to android.
Click to expand...
Click to collapse
There's some trickery going on in u-boot:
When BootCnt is >= 8:
Code:
"checkbootcount=\
if fatload mmc ${mmcromdev}:2 0x81c00000 devconf/BootCnt 4; then\
calc.l *0x81c00000 + 1 0x81c00000;\
if itest.l *0x81c00000 < 0; then\
echo Bad Boot count (Fixed);\
mw.l 0x81c00000 0 1;\
fatsave mmc ${mmcromdev}:2 0x81c00000 devconf/BootCnt 4;\
fi;\
if itest.l *0x81c00000 > 7; then\
echo Boot count exceeded;\
echo Forced to boot into recovery mode for Factory Fallback; \
mw.b 0x81c00000 0 0x200;\
cp.s \"boot-recovery\" 0x81c00000 0xd;\
cp.s \"recovery --restore=factory --update_package=MISC:factory.zip\" 0x81c00040 0x3d;\
mw.b 0x81c00048 0xa 1; mw.b 0x81c0005a 0xa 1;\
fatsave mmc ${mmcromdev}:2 0x81c00000 BCB 0x200;\
mw.l 0x81c00000 0 1;\
fatsave mmc ${mmcromdev}:2 0x81c00000 devconf/BootCnt 4;\
else\
echo Boot count OK;\
fi;\
fi" \

mali100 said:
Once it's stable and well tested, yes.
By the way, does someone know how the reboot to recovery from a running system works on other devices? Does this work on the Nook Color?
"adb reboot recovery" and "reboot to recovery" from CWM just cause a normal reboot to android.
Click to expand...
Click to collapse
On the NC running CM7:
Boot to Recovery from Rom Manager - works
Boot to Recovery from CM power menu - works
reboot recovery from adb - works
Reboot to Recovery from CWM - boots to CM

ros87 said:
There's some trickery going on in u-boot:
When BootCnt is >= 8:
Click to expand...
Click to collapse
Thats not what i meant. Other android devices allow it to boot from a running system directly into the recovery and I would like to know what function or switch is used for this. Or do you think they just set the boot-counter to 8?

FletchF said:
On the NC running CM7:
Boot to Recovery from Rom Manager - works
Boot to Recovery from CM power menu - works
reboot recovery from adb - works
Reboot to Recovery from CWM - boots to CM
Click to expand...
Click to collapse
Ok, thanks for the info.

mali100 said:
Thats not what i meant. Other android devices allow it to boot from a running system directly into the recovery and I would like to know what function or switch is used for this. Or do you think they just set the boot-counter to 8?
Click to expand...
Click to collapse
No, but the recovery is almost certainly not called directly.
What other devices are doing I cannot say, but on the NST you write your intentions to BCB and then reboot methinks

Related

[RECOVERY] [02/02/12] ClockworkMod [5.0.2.0 and 5.8.1.0] ~Touch Version Added~

{
"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"
}
All credit for this software goes to the dev (Koushik Dutta and anyone else on his team).
** Nandroid backups made on previous versions of CWM cannot be restored in CWM 5.0.x.x. So if you have backups made in versions 2.5.x.x or 3.0.x.x, you will not be able to restore them once you've upgraded. **
HOMEPAGE
ClockworkMod.com
DOWNLOAD
Standard recovery
Link: recovery-clockwork-5.0.2.0-glacier.img - Rename to "recovery.img" for easier CLI entry
MD5: a5aea82ec2ad7b836c9c179fce0d520d - To verify, use ManD5 or the below ADB commands:
Touch recovery
Link: recovery-clockwork-touch-5.8.1.0-glacier.img - Rename to "recovery.img" for easier CLI entry
MD5: 687998d5093878147256c10ae9e98e5a - To verify, use ManD5 or these ADB commands:
Code:
adb push recovery.img /sdcard/recovery.img
adb shell md5sum /sdcard/recovery.img
INSTALLATION
- Via the ROM Manager app (version 4.4.0.3 or newer required)
- Via terminal emulator:
Code:
Move recovery.img to the root of your sdcard
Start the terminal app
su (press enter)
flash_image recovery /sdcard/recovery.img (press enter)
reboot recovery (press enter)
- Via fastboot (ADB installation and engineering bootloader version 0.85.2007 required):
Code:
Move recovery.img to a location where fastboot can find it.
Boot your phone into fastboot mode
Connect your phone via USB to your computer
fastboot devices
fastboot flash recovery recovery.img
CHANGE-LOG
5.0.0.1 through 5.0.1.0
Backups now use tar over yaffs for everything except mtd partitions. Backup speed improved.
Backups now preserve the filesystem type at time of backup. Restores will restore the appropriate filesystem type.
New color scheme
Status bar when backing up working again
Backing up of .android_secure working again
5.0.2.0
Bug-fix: root no longer lost on rom restore
5.8.0.9
Touch version - initial release (beta stage)
5.8.1.0
Major bug fixed (recovery.fstab malformed)
I'm not in any way responsible if something happens to your device. I'm simply posting this as a courtesy to the community.
I still don't know how this flew over our heads.
Either way, glad you provided every possible method to upgrade.
mackster248 said:
I still don't know how this flew over our heads.
Either way, glad you provided every possible method to upgrade.
Click to expand...
Click to collapse
Was there a 4.0? I was still on 3.0.24 still, and now I find out about this version. does anyone know its new features?
Ace42 said:
Was there a 4.0? I was still on 3.0.24 still, and now I find out about this version. does anyone know its new features?
Click to expand...
Click to collapse
As far as I know, the jump was made straight from 3.0.2.4 to 5.0.0.1. I have yet to see a changelog, but if anyone finds one, I'll add it to the OP. After poking through the menus, nothing obvious stood out, so it seems to be a bug fix and "behind the scenes" release.
-From Mr.Dutta via G+
I've just finished releasing updates to a bunch of devices to ClockworkMod Recovery 5.
Major changes:
Backups now use tar over yaffs for everything except mtd partitions. Backups got way faster.
Backups now preserve the filesystem type at time of backup. Restores will restore the appropriate filesystem type at restore.
Please update to ROM Manager 4.4.0.3 or higher and try out the new recovery!
Troubleshooting:
Flashing issues: If a recovery does not flash properly, enable erase recovery in settings and try flashing it again. Recovery flashing can be finicky at times.
Bugs: Report them to me! You can always revert back to the older recovery too from within ROM Manager!
Thanks for the heads up. Just flashed via rom manager without any issues.
I decided to flash the upgrade. The flash went perfectly. However, I can't boot into recovery while within Android. I have to power off and boot into the bootloader and then select recovery... Whenever I try to reboot to recovery via the Android UI, it reboots and hangs at the boot splash screen.. It doesn't even work if you select the option from the ROM Manager itself just hangs... I rolled back to previous version and its working again...
Possible bug??...
epolaris said:
I decided to flash the upgrade. The flash went perfectly. However, I can't boot into recovery while within Android. I have to power off and boot into the bootloader and then select recovery... Whenever I try to reboot to recovery via the Android UI, it reboots and hangs at the boot splash screen.. It doesn't even work if you select the option from the ROM Manager itself just hangs... I rolled back to previous version and its working again...
Possible bug??...
Click to expand...
Click to collapse
I'm not quite sure if that's a bug. Since there's a lot of internal changes, I'm assuming the path it takes from Android to CWM has changed. So maybe that's why we're stuck at the splash screen.
But that's not too big of a problem. So far it's much faster than the previous versions.
WOW! I just did a backup of my current Rom and it literally took like 1 minute! It's WAY faster now.
epolaris said:
I decided to flash the upgrade. The flash went perfectly. However, I can't boot into recovery while within Android. I have to power off and boot into the bootloader and then select recovery... Whenever I try to reboot to recovery via the Android UI, it reboots and hangs at the boot splash screen.. It doesn't even work if you select the option from the ROM Manager itself just hangs... I rolled back to previous version and its working again...
Possible bug??...
Click to expand...
Click to collapse
I'm not having that issue at all. I can reboot into recovery using the power menu within Faux's 1.3.1 rom and it works perfectly. I can't speak about other roms, but just letting you all know that Faux's latest works fine.
<EDIT EDIT>
lol wrong forum.
updated to 5.0.0.1. seems pretty neat.
This new recovery backs up roms really fast. With the old version it used to take my phone 2 to 3 minutes to back up. Now about a minute. Its actually kind of scaring me. I don't know if its backing it up correctly. I'm affraid to restore lol.
Sent from my HTC Glacier using xda premium
coupetastic-droid said:
This new recovery backs up roms really fast. With the old version it used to take my phone 2 to 3 minutes to back up. Now about a minute. Its actually kind of scaring me. I don't know if its backing it up correctly. I'm affraid to restore lol.
Sent from my HTC Glacier using xda premium
Click to expand...
Click to collapse
I posted the changelog on the 1st page.
"I've just finished releasing updates to a bunch of devices to ClockworkMod Recovery 5.
Major changes:
Backups now use tar over yaffs for everything except mtd partitions. Backups got way faster.
Backups now preserve the filesystem type at time of backup. Restores will restore the appropriate filesystem type at restore.
Please update to ROM Manager 4.4.0.3 or higher and try out the new recovery!
Troubleshooting:
Flashing issues: If a recovery does not flash properly, enable erase recovery in settings and try flashing it again. Recovery flashing can be finicky at times.
Bugs: Report them to me! You can always revert back to the older recovery too from within ROM Manager!"
I also added the info from his Google+ page to the OP.
Any information on whether other built in tools such as sdparted were updated too? I have been having a lot of trouble with my SD card (I couldn't get it to format through sdparted because of some error I can't remember) and the option to partition your SD card through ClockWorkMod Recovery 3.x didn't allow to set EXT to a size of 0. I was able to partition my card the way I wanted through sdparted after flashing the new 5.0.0.1 recovery, but was curious as to whether there was a change within the recovery img that allowed me to finally partition the way I wanted or if the change was something else that caused my SD card to start functioning correctly.
bstapley said:
I'm not having that issue at all. I can reboot into recovery using the power menu within Faux's 1.3.1 rom and it works perfectly. I can't speak about other roms, but just letting you all know that Faux's latest works fine.
Click to expand...
Click to collapse
+1 Same here
Sent from my HTC Glacier using XDA Premium App
Ace42 said:
I posted the changelog on the 1st page.
"I've just finished releasing updates to a bunch of devices to ClockworkMod Recovery 5.
Major changes:
Backups now use tar over yaffs for everything except mtd partitions. Backups got way faster.
Backups now preserve the filesystem type at time of backup. Restores will restore the appropriate filesystem type at restore.
Please update to ROM Manager 4.4.0.3 or higher and try out the new recovery!
Troubleshooting:
Flashing issues: If a recovery does not flash properly, enable erase recovery in settings and try flashing it again. Recovery flashing can be finicky at times.
Bugs: Report them to me! You can always revert back to the older recovery too from within ROM Manager!"
Click to expand...
Click to collapse
just did a restore and everything went perfectly fine. thanx.
I was just wondering that when I flash a rom and it calls for 3.0.2.4 recovery do I still use that or can I use the new recovery..I know it's a dumb question but just want to make sure
Sent from my virtuous doubleshot glacier using XDA App
darksoul0013 said:
I was just wondering that when I flash a rom and it calls for 3.0.2.4 recovery do I still use that or can I use the new recovery..I know it's a dumb question but just want to make sure
Click to expand...
Click to collapse
Shouldn't be a problem. Nothing was changed that would make affect how a ROM is flashed.

[i317-i317M][CWM Advanced Edition] PhilZ Touch

Main thread + features + install instructions + dev support
http://forum.xda-developers.com/showthread.php?t=2201860
PhilZ Touch 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
It also adds a full touch interface a completely configurable GUI
Since many requests to port it to i317/M, here it is finally released
Please give your feedback, what works, and any bug you could encounter
Read the features, and check if you are missing something
I would appreciate a screen shot from your device, mainly under GUI options or custom backup menu where you select partitions
To take a screen shot, just slide left
Also, do not forget to read about the powerful aroma file manager integration and double tap shortcut
Download links
Last version can be found here:
i317 (t0lteatt)
i317M (t0ltecan)
http://goo.im/devs/philz_touch/CWM_Advanced_Edition
Click to expand...
Click to collapse
Recovery (.zip) packages instructions
They come in the form of .zip files that can be flashed in cwm recovery
Download philz_touch_xxx.zip file
Put the previously downloaded philz_touch_xxx.zip file on your sd card
Boot into recovery (volume up+home+power)
Select "Install zip" and browser to your downloaded zip file.
Now select the philz_touch_xxx.zip fileyou copied in previous step
You will have PhilZ Touch Recovery flashed
Odin packages instructions
They come in the form of .tar.md5 file
boot into download mode
start odin3 and configure it as in picture below
connect phone in download mode to PC via USB
press start to flash the tar.md5 package
normally, phone should auto-reboot into recovery.
If it reboots into android and your recovery remains stock, repeat above steps and untick "autoreboot" in odin. Once flash is done, keep pressing power button until it reboots (normally will go to recovery)
when in recovery, if you choose option "reboot system now" and you get "yes - disable flash recovery", select that option to avoid stock recovery overwriting cwm
{
"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"
}
<< Root your phone and reset Yellow Triangle >>
Once in recovery, flash the attached Root_SuperSU.x.xx.Only-signed.zip file to root your phone
If you want root + busybox: flash Root_SuperSU.x.xx-Busybox.1.20.2-signed.zip file
to remove yellow triangle, use TriangleAway
Before asking for support:
Make sure your issue is recovery related
All external sdcard issues: first format in PC with primary partition, tons of people are formatting as logical and come cry
Reproduce your issue and while in recovery:
Go to Advanced / Report Error
Copy the /sdcard/clockworkmod/recovery.log and attach it here
Give detailed info about your issues
Without these, there is little chance I can help you, so, do not get mad if I do not answer
Click to expand...
Click to collapse
Request a build for a new device:
Go to sammobile.com
Search for your phone
Download the +1Gb last firmware file (ideally unbranded and in any case a European version)
Unzip downloaded file
Rename the tar.md5 file into .tar
Extract from the tar file the boot.img and recovery.img files
Post them here with exact file name of the file you downloaded from sammobile (exp: N7100XXDLL7_N7100OXADLL4_XEF.zip)
Post a link to your phone specifications, ideally, a comparison between your phone and the n7100
If they do not share same hardware, ensure there is a cm10.x source for your phone (Optional if you do not know how to check it)
You got a 100% chance for an answer and 90% chance that I release it
Click to expand...
Click to collapse
Since i317 has its own forum, I am splitting its recoveries from my previous n7100/n7105 thread
Please also take a look and read some of the last pages here, as most of your questions would be answered
http://forum.xda-developers.com/showthread.php?t=2028103
Keep thread clean for only things related to this specific recovery
Do not clutter with general support questions, kernel/ROM general issues...
interesting might try this out tonight once i get home.
Re: [21.02.2013][PhilZ Touch][i317/M]4.63 Touch Enhanced CWM 6.0.2.8-exFAT-ext4-Root
Installed and works great. I really like the layout style. Just made a back up to ext sd and like how fast it was. Advance options are nice also. Thanks!
Sent from my SGH-I317 using xda premium
I would like to get some clafificaiton about what Support for TWRP means - does this mean if I flash the Touch Enhanced Recovery - I can restore nandroids that I made on TWRP?
SOrry if that is a NOOB question - but I just wanted to be sure - to avoid doing something stupid -
Re: [21.02.2013][PhilZ Touch][i317/M]4.63 Touch Enhanced CWM 6.0.2.8-exFAT-ext4-Root
mocsab said:
I would like to get some clafificaiton about what Support for TWRP means - does this mean if I flash the Touch Enhanced Recovery - I can restore nandroids that I made on TWRP?
SOrry if that is a NOOB question - but I just wanted to be sure - to avoid doing something stupid -
Click to expand...
Click to collapse
Actually it is a fair game, you can:
- backup in TWRP format to migrate from cwm to TWRP
- Restore from TWRP backups to migrate to cwm
Backup in TWRP format is always done in the multi volume format. Restore supports both. At the end, migration should be smooth.
If you find bugs, always post a log before requesting support please
Sent from my GT-I9100 using Tapatalk 2
Phil3759 said:
Actually it is a fair game, you can:
- backup in TWRP format to migrate from cwm to TWRP
- Restore from TWRP backups to migrate to cwm
Backup in TWRP format is always done in the multi volume format. Restore supports both. At the end, migration should be smooth.
If you find bugs, always post a log before requesting support please
Sent from my GT-I9100 using Tapatalk 2
Click to expand...
Click to collapse
This is simply awesome - I look forward to using this and can see there are a lot of advantages this offers -but I want to do a lot of reading first so I am sure I understand how to use it - really cool stuff...thanks!
mocsab said:
This is simply awesome - I look forward to using this and can see there are a lot of advantages this offers -but I want to do a lot of reading first so I am sure I understand how to use it - really cool stuff...thanks!
Click to expand...
Click to collapse
Restore of TWRP backups was tested by i9300 users and reported fine too. I personally tested for i9100 too
Only part I am still unsure and need feedback is android-secure restore...
Small update
New in PhilZ Touch v4.64
fix: when disabled, virtual keys would still show for a fraction of a second on start
Click to expand...
Click to collapse
v4.64
i317/i317M
cwm: http://www.mediafire.com/file/348v6u3hcx5n793/philz_touch_4.64-i317M.zip
odin: http://www.mediafire.com/file/ckx6cvjjtcz09jn/philz_touch_4.64-i317M.tar.md5
Click to expand...
Click to collapse
Awesome recovery. I find it to be on par with TWRP except for the backups. TWRP has a better setup for backups letting you compress and select what partitions you want to back up, including EFS. This recovery seems to have flawless USB storage mounting though, which TWRP doesn't have. That saved my ass tonight.
Re: [23.02.2013][PhilZ Touch][i317/M]4.64 Touch Enhanced CWM 6.0.2.8-exFAT-ext4-Root
DeMiNe0 said:
Awesome recovery. I find it to be on par with TWRP except for the backups. TWRP has a better setup for backups letting you compress and select what partitions you want to back up, including EFS. This recovery seems to have flawless USB storage mounting though, which TWRP doesn't have. That saved my ass tonight.
Click to expand...
Click to collapse
You can have all the custom settings and selective backup and restore under the Custom Backup and Restore menu
And it supports TWRP backup and restore too...
Sent from my GT-I9100 using Tapatalk 2
That's insane. This recovery just became my daily driver.
DeMiNe0 said:
That's insane. This recovery just became my daily driver.
Click to expand...
Click to collapse
Thanks
Next updates will even make it nicer
Just installed on my Note2 and wow. This thing is so quick and smooth. Hats off to the devs. :good:
I've been running with this recovery now for a few days and all I can say is WOW! This is an amazing recovery; hands down the best i've used for android period. Phil took the best parts of CWM and TWRP and mashed them together in a sexy recovery image.
http://forum.xda-developers.com/donatetome.php?u=4666971
Click that donate button; you know you want to!
New in PhilZ Touch v4.87
v4.63 ---> 4.64
fix: when disabled, virtual keys would still show for a fraction of a second on start
v4.64 ---> 4.87
Backup and Restore:
menu Custom Backup and Restore can now be accessed in main Backup and Restore menu
support restore backups from /sdcard/0 (Android 4.2) in custom jobs and TWRP mode
add support to sd-ext ext4 partition on external storage
menu to delete custom and TWRP backup images
auto-reboot option for custom backup and restore jobs
set .android_secure path in custom jobs
smart auto detect android_secure for stock CWM backup and restore operations
fix preload was selectable in TWRP jobs (even if would not actually be processed)
progress bar is no more overwritten by text
time and battery stats are shown and refreshed during nandroid operations
on successful or cancelled nandroid jobs, user background icon is restored
on cancelled nandroid jobs, progress bar is correctly reset and user background icon is restored
User configurable gesture actions
gestures: double tap, long press/move, long press/lift, slide left, slide right
always vibrate on long press/move action validation
actions: show log, change brightness, blank screen, capture screen shot, launch Aroma File Manager
GUI
default black theme without background icon
toggle clock and battery on top
header title will be auto-shortened to not overwrite battery and clock on lower res devices
battery and clock will truly refresh indications every 15 sec
user configurable dim screen timer
user configurable turn-off screen timer
manually adjust brightness (stock kernel doesn't support lower than 65, but recovery binary will accept 25 on custom kernels)
when double tap mode is selected, you now really need to double tap the same menu to validate it
menu Set Time Zone moved to GUI settings
fix Moscow UTC time
Misc
add support to sd-ext ext4 partition on external storage
Move Clean before instal new ROM menu to Wipe Data/Factory Reset menu
fix /system was left again mounted after start up and showing log
Click to expand...
Click to collapse
I need some testers please for some of the features introduced:
- android_secure correct support
- sd-ext support
- any of the above listed new features you'd like to report about
I am pausing a bit on this one, to get users feedbacks and maybe support some new devices
After that, I am doing multi-boot and full GUI scroll revision
Download links
v4.87
i317/i317M
cwm: http://www.mediafire.com/file/eao2fga7ta3sd3d/philz_touch_4.87-i317M.zip
odin: http://www.mediafire.com/file/cdqmd5owgr0hhd7/philz_touch_4.87-i317M.tar.md5
Click to expand...
Click to collapse
When I try to make a custom backup no matter what partitions I choose, I get an "Error while backing up *PARTITION NAME HERE* image!" error. Does this for the TWRP backup option as well.
Re: [03.03.2013][PhilZ Touch][i317/M]4.87 Touch Enhanced CWM 6.0.2.8-exFAT-ext4-Root
Can someone punt new to a help section or user manual so i can read how to convert from twrp to cwm and vice versa. Thanks
Sent from my GT-N7105 using Tapatalk 2

[DEV][callisto] CWM 6.0.4.8 Advanced Edition / PhilZ Touch Recovery 6.27.9

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.27.9
for Galaxy 551 / GT-I5510 / callisto
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 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.27.9)
https://docs.google.com/file/d/0B5c3gpyMBJusbWk2U1k3OWxRMEk/edit
aromafm_callisto.zip (v1.91)
https://docs.google.com/file/d/0B5c3gpyMBJuscnQyN28xZWNKeEE/edit
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.
: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.
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
Thank it is nice recovery working like charm.
@Bhargav97 at the time of updating OTA , recovery didn't boot in system always boot back in recovery. I didn't face such problem before with your recovery.
UPDATE:
Changelog:
-PhilZ sources updated to 6.23.8 (26.03.2014)
-CM-ota compatibility fixes.
Please give feedback especially on cm-ota.
Download link updated in first post.
No luck booting back in recovery not booting in system.
Ansh2000 said:
No luck booting back in recovery not booting in system.
Click to expand...
Click to collapse
Will see to it. It's working for all devices. What's wrong? I'll try to figure it out.
@Bhargav97 any fix, recovery booting normally in system only problem occur when flash ota patch automatically.
@Bhargav97 you would like to compile TWRP for callisto.
Thanks in advance.
Ansh2000 said:
@Bhargav97 you would like to compile TWRP for callisto.
Thanks in advance.
Click to expand...
Click to collapse
I would have done it until now but you wasted my enough time in PMs. You asked the same question in 3-4 PMs. And now, here. I already started work on TWRP for armv6 devices. I first did it for Galaxy Mini. Now, I'm making it stable. Once, it gets stable, I'll make it for other devices and the last would be your device. Because, I don't see many people using this Galaxy 551 and moreover you wasted my time in PMs, so...keep waiting
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/0B5c3gpyMBJusUnZnUEc1MW9iQlk/edit?usp=sharing
Thanks for your hard work. Recovery is not booting in system always booting back in recovery except that every thing working like full philz recovery.
Ansh2000 said:
Thanks for your hard work. Recovery is not booting in system always booting back in recovery except that every thing working like full philz recovery.
Click to expand...
Click to collapse
Bhargav97 have done fixing and told me to compile.
Here is the fixed version:
https://docs.google.com/file/d/0B5c3gpyMBJusbWk2U1k3OWxRMEk/edit
And the Aroma File Manager:
https://docs.google.com/file/d/0B5c3gpyMBJuscnQyN28xZWNKeEE/edit
@Bhargav97
@chraso
Thanks, every thing is fine now booting normally on system.
Any update is coming ?
I'm posting this new version updated 16-04-2014
PhilZ-Touch v6.41.6:
https://docs.google.com/file/d/0B5c3gpyMBJusZjBnLU5ER0RvMWc
Need feedback for specially the Hardware & Virtual on-screen keys.
@chraso all hardware and virtual on screen keys working correctly and now virtual keys got transparent but philz touch background doesn't work.
Any news? As the latest Callisto ROMs require a changed recovery (b/c of partition layout), these PhilZ recoveries won't work anymore, right?
steve8x8 said:
Any news? As the latest Callisto ROMs require a changed recovery (b/c of partition layout), these PhilZ recoveries won't work anymore, right?
Click to expand...
Click to collapse
I don't have a PC nowadays so I don't think there will be any updates (atleast for the time being). You can use CWM for flashing CM11 builds and PhilZ Recovery for older ROMs. Should be alright (?)
I think unpack-repack of kernel and fstab (replacing from latest CWM) might work but I'll need somebody's help that can unpack-repack in their PC.
I'm getting:
# flash_image recoveryonly /sdcard/recovery.img * - permission denied
if I su, then run the command I get:
flash_image recoveryonly /sdcard/recovery.img
Any Solutions?

[MOD][KK/LP/MM/N] MultiROM v33x for Xperia Z1

{
"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"
}
MultiROM is a one-of-a-kind multi-boot mod. It can boot any Android ROM as well as other systems like Ubuntu Touch, once they are ported to that device. Besides booting from device's internal memory, MultiROM can boot from USB drive connected to the device via OTG cable. The main part of MultiROM is a boot manager, which appears every time your device starts and lets you choose ROM to boot. You can see how it looks on the left image below and in gallery. ROMs are installed and managed via modified TWRP recovery. You can use standard ZIP files to install secondary Android ROMs and MultiROM even has its own installer system, which can be used to ship other Linux-based systems.
Features:
* Multiboot any number of Android ROMs
* Restore nandroid backup as secondary ROM
* Boot from USB drive attached via OTG cable
https://www.youtube.com/watch?v=JDnDNxqfSaw
WARNING
It is dangerous. This whole thing is basically one giant hack - none of these systems are made with multibooting in mind. It is no longer messing with data partition or boot sector, but it is possible that something goes wrong and you will have to flash factory images again. Make backups. Always.
IMPORTANT
1. I'm not responsible for anything, you do all this on your own risk.
2. Once you have flashed and set up MultiROM, don't flash another boot.img using fastboot.
3. If you want to uninstall MultiROM, just flash the MultiROM uninstaller.
4. I am not certainly sure about the compatibility with stock Roms, I still need to test this yet.
5. Your device must not be encrypted.
When booting another ROM, you'll notice that in some cases, you can enter the recovery of the boot.img of the ROM. Please don't use it, flash everything using MultiROM TWRP.
INSTALLATION
-> Download and flash the MultiROM recovery from the DOWNLOADs section using "fastboot flash recovery <path-to-recovery.img>
-> Use the recovery to flash the latest multirom zip from the DOWNLOADs section.
-> In order to boot a secondary rom you MUST enable the "kexec workaround" option (enabled by default) in the MultiRom settings found in the recovery: BEWARE that this workaround re-flashes the boot-partition every time you boot a secondary rom, so don't boot secondary roms too often, as it may brick your device on the long term! We still need to fix kexec such that exessive utilization is less risky
That's it. You can now go to "MultiROM menu" (Top right corner in the recovery) to start flashing other ROMs.
NOTE: The touch screen doesn't work if you use a MM/N ROM as a base/primary ROM.
ALTERNATIVE INSTALLATION METHOD
-> Download the latest TWRP multirom recovery from the downloads section.
-> Use a terminal emulator, obtain su, and use the following command Adjust the following command and enter it in the shell: "dd if=/sdcard/<name-of-recovery>.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel"
-> Follow the steps in the previous method to install multirom
ADDING ROMs
Go to recovery, select "MultiROM menu" (Top right corner in the recovery) -> Add ROM. Select the ROM's zip file and confirm.
USING USB DRIVES
During installation, recovery lets you select install location. Plug in the USB drive, wait a while and press "refresh" so that it shows partitions on the USB drive. You just select the location (extX, NTFS and FAT32 partitions are supported) and proceed with the installation.
If you wanna use other than default FAT32 partition, just format it in PC. If you don't know how/don't know where to find out how, you probably should not try installing MultiROM.
If you are installing to NTFS or FAT32 partition, recovery asks you to set image size for all the partitions - this cannot be easilly changed afterward, so choose carefully. FAT32 is limited to maximum of 4095MB per image - it is limitation of the filesystem, I can do nothing about that.
Installation to USB drives takes a bit longer, because the flash drive is (usually) slower and it needs to create the images, so installation of Ubuntu to 4Gb image on my pretty fast USB drive takes about 20 minutes.
Enumerating USB drive can take a while in MultiROM menu, so when you press the "USB" button in MultiROM, wait a while (max. 30-45s) until it searches the USB drive. It does it by itself, no need to press something, just wait.
UPDATING/CHANGING ROMs
1. Primary ROM (Internal)
-> Flash ROM's ZIP file as usual, do factory reset if needed (it won't erase secondary ROMs)
-> Go to "MultiROM menu" (Top right corner in the recovery) in recovery and do Inject curr. boot sector. if it is not done directly during installation of the Rom.
2. Secondary Android ROMs
If you want to change the ROM, delete it and add new one. To update ROM, follow these steps:
-> Go to "MultiROM menu" (Top right corner in the recovery) -> List ROMs and select the ROM you want to update.
-> Select "Flash ZIP" and flash ROM's ZIP file.
SOURCEs
Multirom: https://github.com/XperiaMultiROM/multirom/
TWRP: https://github.com/XperiaMultiROM/android_bootable_recovery
CREDITS
Tasssadar
Olivier
Garcia98
Thunder07
skin1980
Envious_Data
[NUT]
AndroPlus
Panic Brothers
Myself5
Diewi
XDA:DevDB Information
MultiROM v33x for Xperia Z1, ROM for the Sony Xperia Z1
Contributors
drakonizer
ROM OS Version: 2.3.x Gingerbread
Version Information
Status: Alpha
Created 2016-10-22
Last Updated 2016-11-02
Great job Dev
Hey @drakonizer i tried to flash the recovery bit I'm facing a black screen after rebooting in recovery. I'm on cm12.1 with m5kernel 11.2. I probably did something wrong but what?... I only flashed the recovery
Will 4.4 as primary work
benplay64 said:
Hey @drakonizer i tried to flash the recovery bit I'm facing a black screen after rebooting in recovery. I'm on cm12.1 with m5kernel 11.2. I probably did something wrong but what?... I only flashed the recovery
Click to expand...
Click to collapse
You should have flashed the TA update to enable booting directly to recovery. If not, the recovery won't work. Booting into recovery only works using the hardware button combo, and not from Android/adb.
pokepokepoke said:
Will 4.4 as primary work
Click to expand...
Click to collapse
It should, but I haven't tried.
So I have to flash stock ROM before?? If yes my device will wait before having multirom
benplay64 said:
So I have to flash stock ROM before?? If yes my device will wait before having multirom
Click to expand...
Click to collapse
You'll have to either flash latest stock completely out flash the TA update from the general section
drakonizer said:
You'll have to either flash latest stock completely out flash the TA update from the general section
Click to expand...
Click to collapse
So I can only flag the TA update with flash tool over cm?!
benplay64 said:
So I can only flag the TA update with flash tool over cm?!
Click to expand...
Click to collapse
Yes. It should work.
drakonizer said:
Yes. It should work.
Click to expand...
Click to collapse
Thanks you're the boss I will try it now
Updated recovery and multirom zip added with support for Android Nougat and custom stock kernels. Please try and report.
Also, OP has been updated. Looks like Multirom is pretty stable for daily use now. I personally tried it with N as primary and LP as secondary and it worked like a charm.
If users of amami/togari want me to port it for their devices, please PM me so that I can send you test builds. Once I deem them to be stable, I will open threads for them.
drakonizer said:
Updated recovery and multirom zip added with support for Android Nougat and custom stock kernels. Please try and report.
Also, OP has been updated. Looks like Multirom is pretty stable for daily use now. I personally tried it with N as primary and LP as secondary and it worked like a charm.
If users of amami/togari want me to port it for their devices, please PM me so that I can send you test builds. Once I deem them to be stable, I will open threads for them.
Click to expand...
Click to collapse
Friend, i am a little lost, but i need to do that. I need 5.1 for daily use and 6.0 for tests
I am feeling lost because i know how to use twrp to backup, restore, flash zips.... the basic. I am right now using 6.0 Ressurrection Marshmallow rom, with [email protected] 16.04#1 kernel.
I read but i am from brazil and my english isnt the best ones, thats why i am lost. My idea, is, use as primary the 5.1 rom to daily use... but i am lost HOW to start, what kernel should i use...
Please, can you help?
LinkRaf said:
Friend, i am a little lost, but i need to do that. I need 5.1 for daily use and 6.0 for tests
I am feeling lost because i know how to use twrp to backup, restore, flash zips.... the basic. I am right now using 6.0 Ressurrection Marshmallow rom, with [email protected] 16.04#1 kernel.
I read but i am from brazil and my english isnt the best ones, thats why i am lost. My idea, is, use as primary the 5.1 rom to daily use... but i am lost HOW to start, what kernel should i use...
Please, can you help?
Click to expand...
Click to collapse
Okay, I will describe it in detail once more, and hopefully this will be the last time.
-> You can have any ROM as primary, but 5.1 is preferred if you want touch screen support in the multirom menu (the OS choice menu).
-> Flash the latest TA update that enables the recovery partition. The thread is available in the general section.
-> Download the latest multirom recovery from the downloads section
-> Download the latest multirom zip
-> Flash the recovery using fastboot (fastboot flash recovery recovery.img)
-> Boot into recovery using POW+VOL DOWN and use it to flash the multirom zip you downloaded earlier.
-> Enter the multirom menu by tapping the icon on the top right corner of the recovery home screen.
-> Follow the menu to install your secondary ROM.
-> Once that's done, reboot, and you should see the multirom menu pop up
If you still didn't understand, there are multiple guides and videos on the internet. The process is pretty much similar for all devices, so you don't have to look for Xperia Z1 exactly.
drakonizer said:
Okay, I will describe it in detail once more, and hopefully this will be the last time.
-> You can have any ROM as primary, but 5.1 is preferred if you want touch screen support in the multirom menu (the OS choice menu).
-> Flash the latest TA update that enables the recovery partition. The thread is available in the general section.
-> Download the latest multirom recovery from the downloads section
-> Download the latest multirom zip
-> Flash the recovery using fastboot (fastboot flash recovery recovery.img)
-> Boot into recovery using POW+VOL DOWN and use it to flash the multirom zip you downloaded earlier.
-> Enter the multirom menu by tapping the icon on the top right corner of the recovery home screen.
-> Follow the menu to install your secondary ROM.
-> Once that's done, reboot, and you should see the multirom menu pop up
If you still didn't understand, there are multiple guides and videos on the internet. The process is pretty much similar for all devices, so you don't have to look for Xperia Z1 exactly.
Click to expand...
Click to collapse
Thank you for your time! I appreciate it. Two last questions. There will be difference between primary or secundary boot? as performance?
and if i want just to install the second boot ( keep the ressurrection marshmallow as primary) it can be done too?
Thank you and sorry
LinkRaf said:
Thank you for your time! I appreciate it. Two last questions. There will be difference between primary or secundary boot? as performance?
and if i want just to install the second boot ( keep the ressurrection marshmallow as primary) it can be done too?
Thank you and sorry
Click to expand...
Click to collapse
The only difference would be boot time.
Yes, you can use MM as primary, but touch on the multirom menu will not work and you'll have to use the volume buttons and power button to move and select.
Sent from my Xperia Z1 using XDA Labs
Hallo . Can i use this on stock base?
monnett said:
Hallo . Can i use this on stock base?
Click to expand...
Click to collapse
It should, no reason not to....why don't you try and tell me?
drakonizer said:
It should, no reason not to....why don't you try and tell me?
Click to expand...
Click to collapse
iam sorry . But i faced problem when flashing twrp on adb its say "too large"
monnett said:
iam sorry . But i faced problem when flashing twrp on adb its say "too large"
Click to expand...
Click to collapse
Sorry about that...it should be fixed now. Please re-download multirom-twrp-honami-02112016.img from the downloads section and try again.
Thanks!
Friend, i am still on MM Rom, 6.0 with the same kernel, now i want to make the lollipop as my secundary boot
i flashed the twrp of multiboot via fastboot mode. I´ve turned on my z1 (power + volume down) (Could see the new twrp menu) In the INSTALL option, flashed the zip file of multiboot. After that ( i did not reboot my devce) on the addRom menu, installed a lollipop rom (that i know that works with the same kernel as my MM rom)
but it starts the install thing and get a status FAILED and erase an incomplete rom... something like this. .. and i cant install it.... i´ve tested two different lollipop rom... am i missing something?

Development [Recovery] [A325x] [Stable-ish, Unofficial] TWRP 3.7.0_12.1 - Galaxy A32 4G

{
"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"
}
Code:
#include <not_my_phone.h>
#include <std_disclaimer.h>
/*
* Your warranty is... still valid?
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this Recovery
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
TWRP 3.7.0_12.1 - Samsung Galaxy A32 4G​
Current Status: Stable-ish
Supported Models:
SM-A325F: tested by @Long266 .
SM-A325M: tested by @Melky777 .
SM-A325N: not tested.
Bugs known so far:
TWRP cannot decrypt userdata if you set lockscreen. (one said it works, other it doesn't, so idk I'll just leave it here, YMMV)
Flashing anything shows many "unlock" red lines. (They are currently harmless by our knowledge).
USB-OTG
<!> There can be many more bugs unknown to me and testers. Report as soon as you face problem.
<!> PSA: I don't have the device to verify some of these bugs.
Download:
TWRP (3.7.0): https://github.com/almondnguyen/twr...a32-20230208/TWRP-3.7.0_12.1-a32-20230208.tar
Samsung USB Driver: https://developer.samsung.com/mobile/android-usb-driver.html
Odin (3.14.4): https://samfw.com/Odin/Samfw.com_Odin3_v3.14.4.zip
Disable VBMeta: https://forum.xda-developers.com/at...236537/?hash=f7249adaefe16f3aeac3256a63063f0a
(Optional) Root using Magisk: https://github.com/topjohnwu/Magisk/releases/
Install:
If you have TWRP or any custom recovery installed and bootable, you can upgrade instead; Look below.
<!> the installation will require WIPING DATA. You will also lose access to all Knox-based solutions like Secure Folder.
Backup every precious data you have on your phone.
<!> PC is required. Windows is preferred. (You probably know what you are doing when using Linux/Heimdall. We don't talk about Macs)
Unlock Bootloader:
Go to Settings > About Phone > About Software. Tap build number (10 times) until "you are now a developer" toast shows up.
Go back, go to Developer Settings.
Turn on OEM unlock toggle.
Turn off your phone, hold vol-up + vol-down, then plug in charging cable (please don't use 3rd-party charging-only cable, it must have data transfer capability).
Your device will boot into download mode with a warning. Accept it.
Hold volume-up until the phone shows the bootloader unlock panel "Unlock Bootloader?".
Press volume-up again. Now your phone bootloader is unlocked.
<!> It will now begin the process of wiping data. Let it do its job.
‎
When it reboots to OS, finish setting up your device.
Double check to make sure OEM Unlock is still ON.
‎ ‎
 
Preparing for the installation:
Download everything above onto your PC.
Install Samsung USB Driver.
Open Odin.
Connect your phone to your PC. There should be a COM entry on the top.
Make sure your phone is in Download Mode. (see step 4 of section Unlock Bootloader)
Make sure that OEM LOCK and REACTIVATION LOCK on your screen show "OFF". If it's not off, DO NOT PROCEED ANY FURTHER.
<!> For those with lock ON, use your device for 7 days without rebooting once. Then check the locks above again.
‎  
 
Installing:
Ensure phone is in Download mode.
In Odin:
Load in Userdata: VBMeta_disabler.tar file.
Load in AP: TWRP TAR file.
Prepare yourself. keep your hand on Volume-up and Power button (don't press yet).
In Odin, press Start. It will flash, then reboot. When the screen turned off, quickly press Vol-up and Power button to boot to recovery (this should take about 20~30 seconds).
<!> You should have TWRP up and running now.
‎  
 
Post-Installation:
MUST: Trigger Multi-disabler.
In TWRP, go to Advanced > Terminal.
Type multidisabler, then enter. If it fails with something about vendor free space, run it again.
Run multidisabler again.
Go to main screen. go to Wipe > Format Data, type yes then swipe.
Reboot to Recovery. Now you can do other stuff.
 
Should: Backup all vital partitions:
In TWRP, go to Backup
Backup: EFS, Modem, NVRAM.
Enjoy: Reboot your phone to have a rooted stock, install custom stuff or do whatever you want.
Upgrade:
<!> Use when you already have any custom recovery installed (TWRP, SHRP, Ofox and the likes)
Download the tar recovery image, then extract it to get recovery.img
Copy it to phone, then reboot to TWRP (Combo is Power + Volume-up)
Go: Install > Install image > select recovery.img file > select Recovery
Swipe to confirm flashing.
If success, reboot to recovery.
<!> You can also use Odin to upgrade, the steps similar to the Install section. All Post-installation, if already done, is unnecessary to do again.
GSI and related stuff:
GSI should be directly flashable now. Big credit to @Long266
Install TWRP, do all the instructions.
Download a GSI. Phh's is a good start.
Releases · phhusson/treble_experimentations
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com
If downloaded a compressed file (the extension is not .IMG; e.g: `gsi.img.gz` ), extract it to get an IMG file. Copy the IMG file to your phone.
Reboot into TWRP.
Tap Install > Install Image > Select your GSI .img file.
Select System Image, then flash.
If previously you were on stock, Wipe > Format data.
Reboot System.
Profit.
Source codes:
Kernel: https://github.com/long266/android_kernel_samsung_a32/tree/s
TWRP device: https://github.com/almondnguyen/twrp_device_samsung_a32/tree/twrp-12.1
Credits:
Devs involved in the making and maintaining of TWRP, twrpdtgen, Magisk and base software.
All the Testers.
@Long266 as tester, collab-dev.
@ianmacd for multidisabler.
@afaneh92 for a32x base tree and MTK-Samsung multidisabler.
@dronkit and @Mighty_Rearranger for Magisk-IMEI fix on MTK devices.
@klfld for GSI installation guide.
Older Release(s):
TWRP 3.6.2_12.1-20220703: https://github.com/almondnguyen/twrp_device_samsung_a32/releases/tag/TWRP-3.6.2_12.1-a32-20220703
TWRP 3.6.2_12.1-20220528: https://github.com/almondnguyen/twrp_device_samsung_a32/releases/twrp-3.6.2_12.1/
TWRP 3.6.1_11: https://github.com/almondnguyen/android_OTA/releases/TWRP-3.6.1_11-a32-B20220324
Footer Infos:
Status: Beta
Current Stable Version: 3.7.0_12.1
Created: 2022-03-24
Last Updated: 2022-07-03
chmod 550 /mnt/vendor/nvdata/md/NVRAM/NVD_IMEI must run on OS, not TWRP, since TWRP cannot mount /mnt
I can't install large IMG files to internal memory? For example a gsi?
Melky777 said:
I can't install large IMG files to internal memory? For example a gsi?
Click to expand...
Click to collapse
I should clarify that I don't own the device and all the testing was/is done by @Long266 .
These specific questions should be inquired to him instead (on his thread here: https://forum.xda-developers.com/t/...hawk-recovery-project-3-1-2021-03-24.4420469/ ).
Anyways, the bug that you are mentioning means that you can't flash images FROM internal SD card. GSI and image stuff should be flashable from other places like external SD or cache. Zip files are so far working as intended (as is they are flashable from anywhere).
To be fair, there could be flaws in his testing methodology and you should try it yourself.
Thanks Bro
I will owe the test of the A325M. I have no SD card at the moment.

			
				
Build 2022-03-25 changes:
Add backup entry for NVRAM, so in case Magisk messes up you still have a working copy intact.
Fix flashing image causing file size exceeded limit.

			
				
Updated TWRP Link, previously pointing to dead end.

			
				
It worked fine on the A325m, but I had NULL errors when I went to do some actions, and the USB OTG is not working!

			
				
Melky777 said:
It worked fine on the A325m, but I had NULL errors when I went to do some actions, and the USB OTG is not working!
Click to expand...
Click to collapse
can u send recovery.log ?

			
				
Melky777 said:
It worked fine on the A325m, but I had NULL errors when I went to do some actions, and the USB OTG is not working!
Click to expand...
Click to collapse
just skip NULL errors

			
				
How to update the TWRP version if it is already installed?
Is it enough to just flash the new TWRP version in Odin?
Or do I need to do the same steps as with the first installation (i.e. multidisabler, etc)?

			
				
YellowSM said:
How to update the TWRP version if it is already installed?
Is it enough to just flash the new TWRP version in Odin?
Or do I need to do the same steps as with the first installation (i.e. multidisabler, etc)?
Click to expand...
Click to collapse
You can use the "install Image" under TWRP.
From the <!> For more info part, download .img file instead, copy it to your phone. Then go to TWRP > Install > Install Image > select TWRP img > select Recovery to flash.
If you've done, Post-installation steps are unnecessary to do again.
edit: upgrade section added to main post.

			
				
How to deactive KC Client and
Knox Enrollment Service?

			
				
Hi, I wanted to try a GSI with this, is it safe to try it? Thanks for developing this TWRP, I can help with testing too.

			
				
Okay, I tested flashing phh's AOSP GSI, TWRP doesn't have the entry to flash to the dynamic partitions (system, vendor, product, etc). It can flash only to the super partition. Tried to flash the GSI there just in case, but i get a bootloop obviously. Restored successfully through ODIN. I wont test magisk because I don't want to lose IMEI.

			
				
klfld said:
Okay, I tested flashing phh's AOSP GSI, TWRP doesn't have the entry to flash to the dynamic partitions (system, vendor, product, etc). It can flash only to the super partition. Tried to flash the GSI there just in case, but i get a bootloop obviously. Restored successfully through ODIN. I wont test magisk because I don't want to lose IMEI.
Click to expand...
Click to collapse
try flashing via fastboot!
I saw a video of a Brazilian doing it on the A22

			
				
Long266 said:
can u send recovery.log ?
Click to expand...
Click to collapse
On the same day I removed the twrp and blocked the bootloader.

			
				
Melky777 said:
try flashing via fastboot!
I saw a video of a Brazilian doing it on the A22
Click to expand...
Click to collapse
I could install the Lineageos 19.1 GSI! I had to use this zip as a workaround ChonDoe_Flasher.zip, that allows flashing dynamic partitions even if the TWRP doesn't. I also made a treble overlay for this device (vendor.img), that fixes power profiles and all this stuff, ill upload it now if anyone is interested.
To flash the GSI you have to rename the .img file to system.img, put it in the same location than the zip and flash the zip. I have the scripts inside the zip to check if it didnt do anything weird and the source code seems safe, tried two GSIs today.
What doesnt work with the Lineage GSI or phh's AOSP is MTP and the fingerprint reader. Also i can't get encryption to work, the GSI crashes if i don't use multidisabler to remove encryption from the fstab. Everything else works flawlessly from my testing.
For file transfer i'm using ADB with this tool, it's even faster than MTP somehow Python ADB File Explorer
EDIT: Uploaded vendor.img with the overlay for this device, ill push the changes to github later.
Download here: vendor.img

			
				
klfld said:
I could install the Lineageos 19.1 GSI! I had to use this zip as a workaround ChonDoe_Flasher.zip, that allows flashing dynamic partitions even if the TWRP doesn't. I also made a treble overlay for this device (vendor.img), that fixes power profiles and all this stuff, ill upload it now if anyone is interested.
What doesnt work with the Lineage GSI or phh's AOSP is MTP and the fingerprint reader. Also i can't get encryption to work, the GSI crashes if i don't use multidisabler to remove encryption from the fstab. Everything else works flawlessly from my testing.
Click to expand...
Click to collapse
Very good job!!!
Makes a topic, I think I'm not the only one who wants to install a GSI.

			
			
			
			
			
			
			
			
			
			

			
		

	
	
	



	
	







			

		



		

			
Categories

			
		


		

			
Resources