A simple text editor similar in function to Notepad++ would be great.
Unfortunately, amarullz has not addressed the bugs reported re v1.80 upon it's release, way back when.maybe an aroma-based version will be or it will added in aroma file manager. contact amarullz.
The way it is now, the name for each extra 'boot' partition is parsed from the kernel's cmdline arg : "relpath=...". If you want to set a Rom name (instead of 'NAND') just edit the installation package and add that arg in the mkbootimg.sh.Can I set a name for boot partition which is showed in your black clk bootloader and your XBoot app.
XBoot is not working in JB 4.2.2 Tytung 2.1, access root all 2 seconds and do nothing.
I'll see what I can I do.With the latest v22.214.171.124 version the progress bar for backup/restore is not updated correctly.
Yes I could, but afaik nothing in misc is worth of saving. If you think you need that partition backup, do it manually (dump_image).hi kokotas. can you add support for back up & restore misc partition for magldr users?
That could be possible. I think the viewer will be easy. I'll see if I can implement editing too.Any chance of a simple text editor or viewer in TWRP? I have had a few times when I wanted to check the contents of a file before/after moving/renaming it.
Regards!You cannot change the teamwin slide-up curtain. It’s not part of the XML or theme engine.
Hey Dark_Avenger,please add a possibility (if it's not so hard) for changing the start-up splash (curtain.jpg) through the theme.
Not a big issue... just came to my mind. One additional request - in the backup partition list the selected partitions are not persisted. Boot, system and data partitions are always preselected, but I have to select SD-Ext all the time. Is it possible to remember the selected partitions like it was before?Hey Dark_Avenger,
I'll give it a shot. Since the card is read before loading up the theme resources, I believe it is possible.
[EDIT]Unfortunately, gui_init() is called before the card is processed, so this is difficult...[/EDIT]
It is a nice idea. But the way it is now, the curtain is shown too soon, even before the settings file is read. This means that there is no way for the recovery to know which is the selected theme at that point. The only workaround that I can think of is to show the curtain after the card (hence the settings file) is read. I'm just chary of it showing for only a few ms - not being a noticeable splash screen..Not a big issue... just came to my mind.
This is due to the new partitionlist element and it always reset to those 3 basic partitions, as you said. I'll see if I can make some changes to it..One additional request - in the backup partition list the selected partitions are not persisted. Boot, system and data partitions are always preselected, but I have to select SD-Ext all the time. Is it possible to remember the selected partitions like it was before?
Thank you for your help.The way it is now, the name for each extra 'boot' partition is parsed from the kernel's cmdline arg : "relpath=...". If you want to set a Rom name (instead of 'NAND') just edit the installation package and add that arg in the mkbootimg.sh.
As for the xBoot.apk I will update it soon.
Hi Nixda99,But what was happened with my boot partition???
Will try itHi Nixda99,
Maybe the log during the installation could help in case there was an error executing mkbootimg. If you try it again have a look at it.
Btw, I updated the Xboot.apk too. I tested it on tytung's JB (DataOnExt Installation) and it worked fine.
PS: v126.96.36.199 is up:fingers-crossed:
Thank you, kokotas . Positive feedback from me - custom splash screen (curtain.jpg) from the current theme is working fine. Partitions persists is working too.PS: v188.8.131.52 is up:fingers-crossed:
The logs seem clear, but I will check them again. I just did a backup and restore of /data and /sd-ext and it worked. Maybe I'll compile and send you a version with more debugging messages..issue: when i perform a backup the sd-ext part is corrupted. it does not matter if i enable DataOnExt option or not. i did some tests and my finding is that it started with the change from busybox tar to libtar.
on the attached screenshot you can see how the backup file looks like
i attached 2 recovery.logs one with DataOnExt Option enabled an one without
Unfortunately there is no (easy) way to return to busybox tar, since I removed all the relevant code. However, libTar will get more stable eventually.could to compile a version with busybox tar so i could confirm the issue is caused by libtar?
Ok, I think I just reproduced it. I will try to find out what's wrong today and post a fix later.hi kokotas,
that's right. if I restore the sd-ext the file and folders are like you can see on the screenshot. I also unpacked the backupfile with zip/7zip and the filestructure is messed up
Sent from my NexusHD2 using xda app-developers app
adb push recovery.img /sdcard/recovery.img adb shell erase_image recovery adb shell flash_image recovery /sdcard/recovery.img
fastboot erase recovery fastboot flash recovery recovery.img fastboot oem boot-recovery
[B][COLOR="Red"]WARNING!!![/COLOR] This way of flashing will erase your current Rom on NAND too! You will probably want to do this [COLOR="Red"]ONLY IF[/COLOR] you need to increase the size of the 'recovery' partition![/B]
misc ya 1M [U]recovery rrecov|ro|nospr 8M recovery.img[/U] boot yboot|ro 5M system ya 150M cache ya 2M userdata ya|asize|hr allsize
Dropped the logic: If cLK => mtd else => yaffs2
adb pull /tmp/recovery.log
adb pull /cache/recovery/log
HD2 ver.: EU SDCard: Sandisk 32GB(c4) SDCard's Partition Table: mmcblk0p1 [vfat,30GB], mmcblk0p2 [ext4,2GB] Bootloader: cLK 184.108.40.206 NAND's Partition Table: recovery 8MB, misc 2MB, boot 4MB. userdata auto-size, system 200 MB, cache 2MB Rom: HyperDroid 6.1 - NAND
#define MSM_MAX_PARTITIONS 8