A simple text editor similar in function to Notepad++ would be great.
maybe an aroma-based version will be or it will added in aroma file manager. contact amarullz.
maybe an aroma-based version will be or it will added in aroma file manager. contact amarullz.
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.
Copying/moving files/folders is virtually useless, and I would doubt that there is a more ardent amarullz fan than I.
He knows me, as I went through many hoops getting a donation to him, since Paypal was blocking transfers to Indonesia from the U.S., and he has yet to reply to me either publically or privately (emails are known to each other).
My main point, by suggesting Notepad++, is to avoid a Windows Notepad type editor which is not linux compliant, not to diverge into an amarullz thread.
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.
I'll see what I can I do.
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).
That could be possible. I think the viewer will be easy. I'll see if I can implement editing too.
Regards!
Hi kokotas,
thank you for the new version - it's great. I have a small request - please add a possibility (if it's not so hard) for changing the start-up splash (curtain.jpg) through the theme. I know that TeamWin curtain.jpg is not part of the XML engine.
thank you for the new version - it's great. I have a small request - please add a possibility (if it's not so hard) for changing the start-up splash (curtain.jpg) through the theme. I know that TeamWin curtain.jpg is not part of the XML engine.
Regards!
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]
Regards!
PS: Thanks again for letting me use your theme as a base for the new built-in theme:good:
Last edited:
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]
Regards!
Regards!
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..
[EDIT]OK, i've tried doing it using the prerecoveryboot.sh and it works
[/EDIT]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..
[EDIT]Done! I've made the selection persisted through reboots[/EDIT]
Hey MarkAtHome,
Hope you like the new ui changes
Regards!
Last edited:
Thank you for your help.
Installed at first your new 2.5.0.3 and made backups of DataOnExt and NativeSD roms without problems.
Then I inserted relpath in mkbootimg.sh like this:
/tmp/mkbootimg --base 0x11800000 --cmdline 'rel_path=NexusJB no_console_suspend=1 console=null' --kernel /tmp/zImage ...
Then installed NexusJB4.2.2 DataOnExt, but after that the bootloader said Invalid kernel image and didn't booted. Then I tried "rel_path" instead of "relpath", no luck, the same error. Then I restored the original mkbootimage.sh and the same error, can't boot from DataOnExt. Then I tried v2.5.0.2 and 2.4.7 and the CWM touch recovery, the same. Then I copied the zImage and the DataOnExt initrd to a NativeSD folder on sdcard, replaced my wish name in rel_path in startup.txt and flashed the kernel via NativeSD manager to the boot partition: the rom booted now and Black CLK show my name in boot partition:laugh:
And now I see that init.rd scripts not working in DataOnExt mode
(use the patched init.rd's), but that's not your construction zone.But what was happened with my boot partition???
Hi 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.
Regards!
PS: v2.5.0.4 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.Note: Don't forget to delete the .twrp file. Otherwise this version is unable to boot.
P.S. Holo Dark theme (the blue one
) is updated in post#5 as usual.Best!
big issue with sd-ext
Hi kokotas,
first here is my current setup:
ROM: NexusHD2-JellyBean
installation: DataOnExt / DalvikOnNand
recovery: TWRPv2.5.0.4
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
could to compile a version with busybox tar so i could confirm the issue is caused by libtar?
or any other idea how to solve this?
Hi kokotas,
first here is my current setup:
ROM: NexusHD2-JellyBean
installation: DataOnExt / DalvikOnNand
recovery: TWRPv2.5.0.4
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
could to compile a version with busybox tar so i could confirm the issue is caused by libtar?
or any other idea how to solve this?
Attachments
Hey ratelutz,
So, to get things straight, the real problem is that the created sd-ext's backup cannot be restored?
Note: Last version has some issues (I know for sure that NativeSD Manager's functions are broken - perhaps something else might have been affected too) and I will upload a quick fix in a while.
Regards!
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..
So, to get things straight, the real problem is that the created sd-ext's backup cannot be restored?
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.
Note: Last version has some issues (I know for sure that NativeSD Manager's functions are broken - perhaps something else might have been affected too) and I will upload a quick fix in a while.
Regards!
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
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
Ok, I think I just reproduced it. I will try to find out what's wrong today and post a fix later.
I'm removing the files from the 1st post to avoid unnecessary trouble.
Thank you for the help:good:
Hi Kokotas. I have a suggestion. Can you remove bootloader and recovery options from reboot menu for magldr and haret users? I mean twrp will recognize bootloader (clk, haret or magldr) if it is clk, twrp will show this options. if it isnt clk, twrp wont show these. sorry my english. Thanks.
One more Why dont you use dark avangers blue holo dark theme default?
One more
Why dont you use dark avangers blue holo dark theme default?Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
104Intro:
---------------------
Extended TWRP is based on official Team Win Recovery Project, but modified** to address some special methods & features found on The HD2,
a device which has 3 different android loaders (cLK, MAGLDR and Haret) and various Android Rom configurations (DataOnExt, NativeSD, SD, Nand).
** If you are just looking for an unmodified TWRP for the HD2, check here.
I take no credit for this. All the creative hard work was already done!
Credits to:
- agrabren, Dees_Troy, ViViDboarder, and AssassinsLament - core twrp 2 development team.
- Toastcfh – for his underappreciated dedication to the community.
- s0up and kevank - for their hard work on the web side of things.
- shift, onicrom, netarchy, kevank, myndwire, bigbiff, dkelle4, shinzul, spiicytuna, and eyeballer - the rest of Team Win.
- Amon_RA - for his great Recovery.
- Koush - for his dedication to the community and ClockworkMod.
- Akmzero, arif-ali, Evil_DevNull, gus6464, Jesusice, _jmz_, NxtGenCowboy, ohshaith55, Pyrostic, [R], and Rootzwiki - for all the help with devices and testing.
- Team's supporters and the Android Community.
Notice:
---------------------
For me, this thread is about learning while having fun. It would be ideal if it leads to something that is really useful.
So, as you may have already understood, This Is Not a release thread. If you have the time and interest to help in any way, please do. Cause together we can make sure that this project will benefit all of us.
The attached recovery image is provided for people who can't compile it from source, but want to either help in debugging or just experiment.
- Have in mind that before attaching it here, it was only tested on one HTC-HD2(Eu) powered by (black) cLK bootloader.
The performance on devices powered by MAGLDR bootloader or running the good-old WM6.X should be considered untested.
In order to exploit the full potentials of this software, Black cLK bootloader is strongly recommended! - As usual, use at your own risk. TeamWin or kokotas is not responsible for anything bad that may occur from using Extended TWRP.
- ReadMe
Features:
---------------------
- **************Mainline**************
* Ability to save custom recovery settings
* Touchscreen driven with real buttons and drag-to-scroll
* XML-based GUI that allows full customization of the layout – true theming!
* Settings are saved to the sdcard and persist through reboots
* Ability to choose which partitions to back up and which to restore
* Ability to choose to compress backups – now with pigz (multi-core processor support for faster compression times)
* Ability to backup large partitions (size>1.5GB) by splitting the backup archive.
* Basic file manager (copy, move, delete, and chmod any file)
* OpenRecoveryScript scripting engine
* On-screen keyboard in recovery! -- supports long press, backspace repeat, and swipe left deletes everything left of the cursor
* ADB sideload functionality from AOSP
* Pseudo-terminal emulator
* Decryption support
* Ability to set a timeout for auto-turning off the screen
* exFAT support for sdcard's 1st partition
* Manual screen rotation - **************Extended**************
* Proper detection of bootloader(cLK/MAGLDR/haret)
* Support for cLK's extra boot partitions
* Tweaked off-mode charging for cLK (device can wake up by pressing any key)
* Direct rebooting to selected boot partition for cLK bootloader
* Direct rebooting with selected kernel from NativeSD folder for MAGLDR bootloader
* Ability to communicate with cLK in order to change partitions' size if needed
* Built-in NativeSD manager(Backup - Restore - Delete - Fix Permissions - Wipe Data - Wipe Dalvik-Cache - [cLK]Kernel-Restore)
* Option to skip any NativeSD Rom during sd-ext's partition backup
* Option to adjust backup/restore process for DataOnExt method
*
* Nilfs2 support for sdcard's ext(2nd/3rd primary) partition
* NTFS support for sdcard's 1st primary partition
* Option for converting file system [ext2 - ext3 - ext4 - nilfs2] of sdcard's ext partition (without losing any data if there is enough space on the /sdcard)
* Option for adding a 3rd primary partition(mmcblk0p3 as /sdext2)
* Option to skip dalvik-cache during backup
* Ability to restore backups that were made using a CWM Recovery
* Ability to check SD Card's filesystem(s)
* Ability to run shell scripts from your SD Card (script location: /sdcard/TWRP/scripts)
* Ability to "run" recovery (AROMA based) apps with one click (app location: /sdcard/TWRP/app)
* Ability to select current theme (example of theme file location /sdcard/TWRP/theme/MyTheme/ui.zip)
* Ability to check the size of the backup to be restored
* Ability to take screenshot (screenshots location: /sdcard/TWRP/screenshots)
* Configurable haptic feedback
* Configurable system tweaks (cpu gov, cpu freq, i/o sched, drop_caches)
Source:
---------------------
Looks:
---------------------
- Screenshots
- Compatible themes:
Download:
---------------------
- HD2_EXTENDED_TWRP_2.6.3.4.zip
md5: 5af088d200a00e0a3efb27860a5168c6
Info: You need to have a recovery partition at least 9 MB to fit the img - HD2_EXTENDED_SD_TWRP_2.6.3.4.zip
Info: Extract to the root of your SD Card
Frequent issues:
---------------------
- If you report an issue without a log and/or without details, that's not very helpful in tracking down that issue, so, eventually, don't expect any assistance cause I am not a medium.
- If you get a "status 2" error when installing a recovery-update-package(zip) that used to work with your old recovery, change the update-binary inside the zip file with a newer one (API 3).
DON'T FORGET to check the syntax in the updater-script and verify that format() and mount() commands have the correct amount of arguments, otherwise you'll end up having other errors like "status 7".
i.e. if you use the update-binary included in the attached file below, format takes 2: format("MTD", "boot"). - If you occasionally can't boot into recovery, try increasing the size of its partition >= 10MB.
Installation:
---------------------
Post-Installation:
---------------------
- Make sure you delete /sdcard/TWRP/.twrps.
- If you're using a theme, update your theme file or temporarily switch to the default theme.
A big Thank-You for supporting/testing the ExtendedTWRP to:
---------------------
- Dark_Avenger
- NYLimited
- DarrenNewsgroup
- Nixda99
- MarkAtHome
- Robbie P
3726Info
- How to report a problem
- Provide the log file.
In order to get it connect your device to pc via usb and run in terminal:
If that fails for some strange reason then you could also try:Code:adb pull /tmp/recovery.log
Or you could just use the "Copy Log" button under "Advanced" and have the log copied to the root of your card.Code:adb pull /cache/recovery/log - Give a short description of what triggered the problem.
- If you don't have your device's setup in your signature, post that info too. For example:
Code:HD2 ver.: EU SDCard: Sandisk 32GB(c4) SDCard's Partition Table: mmcblk0p1 [vfat,30GB], mmcblk0p2 [ext4,2GB] Bootloader: cLK 1.5.1.6 NAND's Partition Table: recovery 8MB, misc 2MB, boot 4MB. userdata auto-size, system 200 MB, cache 2MB Rom: HyperDroid 6.1 - NAND - Since this is a WIP, you could also use github to report any issue.
- Theme related
- Information on Official TWRP Theming.
- Extended TWRP gives you the ability to choose between many themes.
When booting, it checks for a theme zip file on your card:
/sdcard/TWRP/theme is the location where you must create a folder named after the theme you will use and place the ui.zip inside it (i.e. /sdcard/TWRP/theme/Holo_Dark/ui.zip).
If none found then it will use the built-in theme. - For those who prefer the blue-ish TWRP default theme, I will be attaching it to this post every time something changes, so that you can use it as any external theme.
- Since version 2.6.0.0, the theming engine of the Extended TWRP differs from the official.
Instead of one ui.xml file, the new theme requires two files portrait.xml and landscape.xml with the appropriate images.
2217Hi guys,
The bug regarding cLK's extra boot partitions was there because I forgot to change a line:
at nand_partitions.c in tytung's kernel before compiling.Code:#define MSM_MAX_PARTITIONS 8
Also, after thinking about the screenshot issue, I decided to follow this way: If the system is busy, even if you accidentally press the top logo no screenshot will be taken so the running process will not be interrupted and will finish normally.
Finally, in the previous version I ported the new gui element partitionlist from mainline. That was a bit messy cause it changed a lot of things regarding backup/restore/wipe, so I had to rewrite some of the functions.
Regards!
PS:I uploaded a new compiled file at 1st post. Happy testing
