[DEV][02/May/2015]unOFFICIAL TWRP|v2.8.6.1

Search This thread

kokotas

Senior Member
Oct 23, 2007
714
1,570
Athens
this program do the same things of 4ext and cwrm right?
I've been using CWM but never used 4EXT Recovery.
I guess the core functions are more all less the same for the end-user.
The extra features (like built-in NativeSD manager, File-system convertion, etc.) may be missing depending on which recovery type you'd use.
using the same backup folders?
Nope. TWPR uses different folder and different format for the backups.
There was a relevant question regarding this here.
You can convert your CWM backups to be TWRP compatible, BUT you have to do it manually.

Regards!
 

jwchips

Senior Member
Apr 16, 2007
545
159
Redmi Note 9 Pro
Xiaomi Poco F3
I've been using CWM but never used 4EXT Recovery.
I guess the core functions are more all less the same for the end-user.
The extra features (like built-in NativeSD manager, File-system convertion, etc.) may be missing depending on which recovery type you'd use.

Nope. TWPR uses different folder and different format for the backups.
There was a relevant question regarding this here.
You can convert your CWM backups to be TWRP compatible, BUT you have to do it manually.

Regards!

Hey kokatos, thanks for another brilliant app for our hd2, your work is always appreciated. Would you mind telling me where I can find the data on ext setting as I've had a good hunt but can't seem to find it. It is an option when you start to back up?

Sent from my GT-I9300 using xda app-developers app
 

kokotas

Senior Member
Oct 23, 2007
714
1,570
Athens
where I can find the data on ext setting
Enter "Settings" and you'll find a checkbox about DataOnExt.
If you have it checked you should also see a new button named "DataOnExt".
By pressing it you can :
(a) set the actual path mounted as /data in case you're using a modified method of DataOnExt,
(b) make TWRP backup userdata partition in case you have something there (like DalvikOnNand)
Sorry, I saw that link which is mention in the post .
Did you try it? Does it work ok?

Regards!
 

jwchips

Senior Member
Apr 16, 2007
545
159
Redmi Note 9 Pro
Xiaomi Poco F3

Attachments

  • uploadfromtaptalk1356624713762.jpg
    uploadfromtaptalk1356624713762.jpg
    105.8 KB · Views: 111
  • Like
Reactions: kokotas

Dark_Avenger

Senior Member
Apr 17, 2010
396
313
Sofia
That's what I thought but it isn't there. Screenshot attached.

You don't have /sd-ext partition. This option is not visible if sd-ext partition is not detected.

kokotas,
please remove the debug message about android_secure detect/size folder from the log in the next build. Log message starting with "E:" makes me think that something is not working correctly :)
Thank you very much. Appreciate your great work on cLK Black and TWRP.
 
Last edited:
  • Like
Reactions: kokotas

jwchips

Senior Member
Apr 16, 2007
545
159
Redmi Note 9 Pro
Xiaomi Poco F3
You don't have /sd-ext partition. This option is not visible if sd-ext partition is not detected.

You mean TWRP isn't detecting my sd-ext partition =). The device has a 16gb Samsung micro shdc card with a 2gb sd-ext partition that was originally formatted with cwm. Its also running DalvikOnNand on the rom fine so the sd card (and partitions) are present and readable by the device.

Sent from my GT-I9300 using xda app-developers app
 

kokotas

Senior Member
Oct 23, 2007
714
1,570
Athens
That's what I thought but it isn't there. Screenshot attached.
OK, lets see what's the problem here...

I have set it up in such way that it depends on the presence of the ext partition. EDIT-START : Dark_Avenger beat me to it:D /EDIT-END
See the bold condition in the code below:
Code:
<object type="checkbox">
[B][U]<condition var1="tw_has_sdext_partition" var2="1" />[/U][/B]
<placement x="%col1_x%" y="%row7_text_y%" />
<font resource="font" color="%text_color%" />
<text>Setup recovery for DataOnExt.</text>
<data variable="tw_data_on_ext" />
<image checked="checkbox_true" unchecked="checkbox_false" />
</object>
If no ext partition is detected then no DataOnExt is possible, so that option won't be shown.
Is this the case here? EDIT-START : Never-mind, just saw your previous post /EDIT-END
If not, then I'll have to check why TWRP doesn't detect correctly the existing partitions and their sizes.
Could you attach the recovery.log here?
please remove the debug message about android_secure detect/size folder from the log in the next build. Log message starting with "E:" makes me think that something is not working correctly :)
Will do in next version. Just forgot about it while trying to fix the relevant problem.

Regards!
 
Last edited:
  • Like
Reactions: 0719andy

jwchips

Senior Member
Apr 16, 2007
545
159
Redmi Note 9 Pro
Xiaomi Poco F3
OK, lets see what's the problem here...

I have set it up in such way that it depends on the presence of the ext partition.
See the bold condition in the code below:
Code:
<object type="checkbox">
[B][U]<condition var1="tw_has_sdext_partition" var2="1" />[/U][/B]
<placement x="%col1_x%" y="%row7_text_y%" />
<font resource="font" color="%text_color%" />
<text>Setup recovery for DataOnExt.</text>
<data variable="tw_data_on_ext" />
<image checked="checkbox_true" unchecked="checkbox_false" />
</object>
If no ext partition is detected then no DataOnExt is possible, so that option won't be shown.
Is this the case here?
If not, then I'll have to check why TWRP doesn't detect correctly the existing partitions and their sizes.

Regards!

Unfortunately I cannot see the bold formatting on my mobile but I get the idea. But I *do* have a sd-ext partition that works when I'm booted into my ROM. I've tried mounting my sd-ext partition in mount settings of TWRP and it won't work.
I've checked the terminal output in TWRP (middle icon) and after 'finished running boot script' there is a error E:unknown file system: 59aaea38-xxxxxx... (this ID also goes off screen and not onto a new line so I can't grab the whole ID). Of I try to mount sd-ext I get an error :e:mount: unable to find partition for path /sd-... (this error goes off screen again). I'm 100% sure my sd-ext partition is fine as my leo512 shows my 2gb partition in device storage in the ROM.

If there's any more info you need or anything I can do to help you get to the bottom of this let me know.

Sent from my GT-I9300 using xda app-developers app
 

Dark_Avenger

Senior Member
Apr 17, 2010
396
313
Sofia
Unfortunately I cannot see the bold formatting on my mobile but I get the idea. But I *do* have a sd-ext partition that works when I'm booted into my ROM. I've tried mounting my sd-ext partition in mount settings of TWRP and it won't work.
I've checked the terminal output in TWRP (middle icon) and after 'finished running boot script' there is a error E:unknown file system: 59aaea38-xxxxxx... (this ID also goes off screen and not onto a new line so I can't grab the whole ID). Of I try to mount sd-ext I get an error :e:mount: unable to find partition for path /sd-... (this error goes off screen again). I'm 100% sure my sd-ext partition is fine as my leo512 shows my 2gb partition in device storage in the ROM.

If there's any more info you need or anything I can do to help you get to the bottom of this let me know.

Sent from my GT-I9300 using xda app-developers app
Probably full recovery.log will help here.
 

kokotas

Senior Member
Oct 23, 2007
714
1,570
Athens
I'm 100% sure my sd-ext partition is fine as my leo512 shows my 2gb partition in device storage in the ROM.
It is probably something with TWRP getting the current partitions and sizes.
If there's any more info you need or anything I can do to help you get to the bottom of this let me know.
The recovery.log could be helpful. Even though I think I can reproduce it by changing the partitions on my spare card using a PC and then inserting it in my device.

Regards!
 

jwchips

Senior Member
Apr 16, 2007
545
159
Redmi Note 9 Pro
Xiaomi Poco F3
It is probably something with TWRP getting the current partitions and sizes.

The recovery.log could be helpful. Even though I think I can reproduce it by changing the partitions on my spare card using a PC and then inserting it in my device.

Regards!

Click for log. Sorry I missed your edit. Also I have to wait a few mins for the sd card to be usable in the ROM as it takes a while to check for errors on each boot. Do they know if it has any implications as I thought it only checked the fat partition for errors?

Sent from my GT-I9300 using xda app-developers app
 
  • Like
Reactions: kokotas

jwchips

Senior Member
Apr 16, 2007
545
159
Redmi Note 9 Pro
Xiaomi Poco F3
Thanks! Will check it out.
EDIT-START : Just read it. It seems that the mmcblk0p2 is not accessible while mmcblk0p3 is your 2GB ext partition. Do you have an unknown(?) partition before your ext? [/EDIT-END]
One last thing: 'cat /proc/partitions' when in TWRP

Regards!

New log here. Umm not as far as I'm aware - this is my girlfriends phone with one of my old cards. Afaik it should just be formatted by Cwm with 2gb sd-ext and 0mb swap.

Sent from my GT-I9300 using xda app-developers app
 

kokotas

Senior Member
Oct 23, 2007
714
1,570
Athens
New log here. Umm not as far as I'm aware - this is my girlfriends phone with one of my old cards. Afaik it should just be formatted by Cwm with 2gb sd-ext and 0mb swap.
I think I know what happened but I am not sure why..
Let me explain what I mean based on your log.
Code:
...
I:Processing '/sd-ext'
E:Unknown File System: '59aaea38-d680-49a2-ae07-f12089951eb8'
...
The What :
Regardless of the recovery.fstab settings, TWRP double-checks the file-system by running a simple blkid cmd.
i.e. "blkid /dev/block/mmcblk0p2" has an output like this:
Code:
/dev/block/mmcblk0p2: UUID="03e7b28e-1686-46c0-9b07-9a9be7b33b5a" TYPE="ext3"
TWRP processes that output so that we get just the file-system type (in the above example it would return 'ext3').
However, in your case, instead of the file system type, TWRP returned the UUID while parsing the output of blkid.
The Why:
I can't think of a reason now.:confused: You could run "blkid /dev/block/mmcblk0p2" and post the output here.
I could also edit the code so that it would never return the UUID.

Regards!
 

Top Liked Posts

  • There are no posts matching your filters.
  • 70
    [22 Dec 2011][RECOVERY] Team Win Recovery Project (twrp) v2.0.0RC0.1

    Original OP
    64
    Introduction:
    ---------------------
    Team Win Recovery Project 2.X, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. It’s a fully touch driven user interface – no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.

    Phone look:
    ---------------------
    RAsb.jpg
    AO13.jpg


    Notice:
    ---------------------
    The attached recovery images were compiled from TWRP's open source.
    They were only tested on a European version of the HTC-HD2 powered by cLK bootloader.
    The performance on devices powered by MAGLDR bootloader should be considered untested.

    Disclaimer:
    ---------------------
    As usual, use at your own risk. TeamWin, arif-ali or kokotas is not responsible for anything bad that may occur from using twrp2.

    Nobody appointed me to compile TWRP for HD2. I'm not TeamWin's member. It just happened...
    If anyone else is willing to do it and probably do it better I will be glad to step aside,​

    Key Features:
    ---------------------
    * 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)
    * 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
    * Ability to backup large partitions (size>4GB) by splitting the backup archive.

    Mainline TWRP Change-Log:
    ---------------------
    Follow up the changes in mainline project at TeamWin's page : http://www.teamw.in/project/twrp2.

    HD2's TWRP Change-Log:
    ---------------------
    • Initial TWRP versions

      1. List of changes
    • TWRP v2.4.0.0.r1 @ 2013.01.17
      1. Compiled version based on mainline code (v2.4.0.0Alpha).
      2. Fix boot partition's filesystem for MAGLDR's backup&restore to work.
      3. Fix getting fs-type from a partition created with a label.
      4. Fix the name of the backup sub-folder(htcleo instead of 0s).
    • TWRP v2.4.4.0 @ 2013.04.03
      1. Compiled version based on mainline code (v2.4.4.0).
      2. Fix boot partition's filesystem for MAGLDR's backup&restore to work.
      3. Fix the name of the backup sub-folder(htcleo instead of 0s).
    • TWRP v2.5.0.0 @ 2013.04.10
      1. Compiled version based on mainline code (v2.5.0.0).
        NOTE: Compiled unmodified source code refused to boot! So I had to change a little bit more this time, just to get it to boot up.
      2. Fix boot partition's filesystem for MAGLDR's backup&restore to work.
      3. Fix the name of the backup sub-folder(htcleo instead of 0s).
    • TWRP v2.6.0.0 @ 2013.07.09
      1. Compiled version based on mainline code (v2.6.0.0).
      2. Fix boot partition's filesystem for MAGLDR's backup&restore to work.
      3. Fix the name of the backup sub-folder(htcleo instead of 0s).
    • TWRP v2.6.1.0 @ 2013.08.31
      1. Compiled version based on mainline code (v2.6.1.0).
      2. Fix boot partition's filesystem for MAGLDR's backup&restore to work.
      3. Fix the name of the backup sub-folder(htcleo instead of 0s).
    • TWRP v2.6.3.0 @ 2013.09.14
      1. Compiled version based on mainline code (v2.6.3.0).
      2. Fix boot partition's filesystem for MAGLDR's backup&restore to work.
      3. Fix the name of the backup sub-folder(htcleo instead of 0s).
    • TWRP v2.8.6.0 @ 2015.04.30
      1. Compiled version based on mainline code (v2.8.6.0).
      2. Fix boot partition's filesystem for MAGLDR's backup&restore to work.
      3. Fix the name of the backup sub-folder(htcleo instead of 0s).
      4. Fix some ui bugs in the default theme.
    • TWRP v2.8.6.1 @ 2015.05.02
      1. It is version 2.8.6 with a quick fix over a bug in the default theme engine that was causing an error during each boot.

    Installation:
    ---------------------
    • Make sure you have adb and fastboot working. Please don't ask here questions about this - a simple web search will be enough to help you.
    • Make sure that the size of the 'recovery' partition is enough for the image to fit.
    • Make sure the name of the recovery *.img file is the one you use in the commands or in flash.cfg
    • [cLK/MAGLDR]
      Flashing the zip file from Recovery
      1. Download zip file to your computer and copy to /sdcard.
      2. Reboot phone into recovery.
      3. Select to install the zip file from your /sdcard.
      4. Reboot Phone into recovery as normal.
    • [cLK/MAGLDR]
      Flashing the *.img file while booted in Android
      1. Download the recovery file to your computer.
        If it is a zip file, extract the *.img.
      2. (Win) Open the folder you have the recovery, do a [Shift+RightClick] and select "Open command window here".
        (Lnx) Open the folder you have the recovery, RigthClick and select "Open in Terminal".
      3. Execute the commands:
        Code:
        adb push recovery-leo.img /sdcard/recovery-leo.img
        adb shell erase_image recovery
        adb shell flash_image recovery /sdcard/recovery-leo.img
      4. Reboot Phone into recovery as normal.
    • [cLK]
      Flashing the *.img file while in fastboot mode(cLK menu)
      1. Download the recovery file to your computer.
        If it is a zip file, extract the *.img.
      2. (Win) Open the folder you have the recovery, do a [Shift+RightClick] and select "Open command window here".
        (Lnx) Open the folder you have the recovery, RigthClick and select "Open in Terminal".
      3. Reboot phone into cLK menu (fastboot mode).
      4. Execute the commands:
        Code:
        fastboot erase recovery
        fastboot flash recovery recovery-leo.img
        fastboot oem boot-recovery
    • [MAGLDR]
      Flashing the *.img file while in USB Flasher mode(using DAF.exe)
      WARNING!!! This will erase your current Rom on NAND too!
      1. Download the recovery file to your computer.
        If it is a zip file, extract the *.img.
      2. Open the folder you have the recovery and place DAF.exe and flash.cfg in that same folder.
      3. Edit flash.cfg according to required recovery partition size:
        Make sure the .img file has the name that flash.cfg specifies!!
        i.e. If the *.img file is named recovery-leo.img and min-required-size = 6MB then the flash.cfg could be:
        Code:
        misc ya 1M
        [U]recovery rrecov|ro|nospr 6M recovery-leo.img[/U]
        boot yboot|ro 5M
        system ya 150M
        cache ya 2M
        userdata ya|asize|hr allsize
        Check out the info about flash.cfg.
      4. Connect the device to the computer via usb, enter MAGLDR and select USB Flasher option.
      5. Right click on DAF.exe and select Run as Administrator.
      6. Click [NEXT] when asked and wait to finish.

    Download:
    ---------------------

    Old Releases:
    ---------------------



    Special Thanks to:
    ---------------------
    * Core twrp 2 development team: agrabren, Dees_Troy, ViViDboarder, and AssassinsLament
    * Toastcfh – for his underappreciated dedication to the community
    * s0up and kevank for their hard work on the web side of things.
    * The rest of Team Win: shift, onicrom, netarchy, kevank, myndwire, bigbiff, dkelle4, shinzul, spiicytuna, and eyeballer
    * Amon_RA - for his great Recovery
    * Koush - for his dedication to the community and ClockworkMod
    * For all the help with devices and testing Akmzero, arif-ali, Evil_DevNull, gus6464, Jesusice, Pyrostic, [R], and Rootzwiki
    * As always thank you to the Team's supporters and the Android Community.
    25
    Hi guys,

    First post updated with a new compiled version (2.6). Check TeamWin's page for the official (long) change-log.
    Many thanks to the team for their efforts - a lot of work was done for this update!
    As for (our) hd2's case, there was no problem booting up this time and everything seems ready to be tested;). So... have fun with this update;)

    Regards!
    23
    Hello guys,

    Attached below is a new compiled version of TWRP - Extended:
    1. Ported commits from mainline 2.3.3.0.
    2. Changed how the DataOnExt will be handled.
      Under "Settings" you'll find a checkbox with which you can "tell" recovery that you're using DataOnExt or not.
      In case you're using a modified DataOnExt method you can set the actual path of your /data (i.e. /sd-ext/%RomName%/data) by hitting DataOnExt button.
    3. Probably fixed the .android-secure bug.
    4. Reverted the backup path(BACKUPS/htcleo/).
      So you have to create an intermediate folder named "htcleo" under BACKUPS and move your backups inside.
    5. Reverted the max size for splitting archive to 1.5GB.
    6. 1st attempt for saving the contents of your ext partition when you change the fs type (will need enough free space on your sdcard for this to work).
    7. Added option to set the number of mounts that will trigger a filesystem check under "Settings".
    8. Added option to wipe Data, Boot and (cLK)sBoot under "wipe" Menu.
    9. Added necessary code for selecting fs type (vfat / ntfs) for /sdcard but since I can't make it function properly I've disabled it in the UI. (Also in case it will work using the ntfsprogs binaries, the size of the recovery will increase to ~ 8MB)
    10. Uploaded all I've done to github repo.

    Merry Christmas and Have fun:)
    Regards!
    22
    FAQ

    FAQ from TWRP team is here

    Q: Does Rom Manager work with this
    A: No

    Q: Will you be providing support for Rom Manager
    A: Maybe, when I have time, or if Team View release it before me

    Q: Does it work with MAGLDR
    A: Yes, use AD recovery

    Q: Does this mean we cannot easily install ROMs
    A: Yes, but the code for that may be added at later date, this is Work In Porgress

    Q: Will reboot to Recovery work as normal
    A: Yes

    Q: Does Off-mode charging still work
    A: Yes, same as CWM on cLK. it will charge when off, but pressing the power button while charging will not turn the phone on

    Q: I got "failed with error: -1"
    A: make sure the recovery size is 5M, anything below that is not supported, You can check this by running adb cat "/proc/mtd | grep recovery"