This started out as a little side project on the OmniROM threads, and it's about time some things are clarified, and what exactly done, is explained.
Currently, only a modified version of TWRP 2.7 recovery is available, and we *might* support other recoveries soon
We have moved ahead of the TWRP 2.7.0.0 originally available in orig-development, to 2.7.1.0, and eventually to 2.8.0.0 too. Enjoy!
What is aw3som3?
Developers have long tried to sqeeze in ROMs into legacy devices with low internal memory, and one of the ways to do this was by using custom tailored mtd_parts, which gave the kernel a partition table to use, with resized partitions. This was widely used on many devices like the HTC G1, MT3G, Hero, Evo4G, Desire, etc.
While that was a viable option for the HTC Pico, a small "problem" that popped up was that different phones have different NAND Devices, with different partition tables and pagesizes. Incase the modified custom mtd_parts even accidentally touched the boot partition, or has been offset'ed out of the available space, a partition would be lost.
As a solution, dynamically obtain 32 mB from userdata partition, and 48 mB from the cache partition, and hax the partition table as soon as the information is got from ATAG. This should make this method work on *almost* all Pico's out there, which have partition layouts as misc:recovery:boot:system:cache:userdata:devlog and partitions in the order misc:rec..cache:devlog:userdata.
Click to expand...
Click to collapse
I've changed the partition table layout, without modifying the actual mtdblock<n>, thus no further fstab/ramdisk editing is required.
table: 0->misc::1->recovery::2->boot::3->system::4->cache::5->userdata::6->devlog
original layout : recovery:boot:system:cache:devlog:userdata:misc
new layout : recovery:boot:misc:devlog:userdata:cache:system
To developers:
In case you want to modify any of the partition size defines, there are three defines, CACHE_SIZE_LEAVE, USERDATA_SIZE_LEAVE, and DEVLOG_SIZE_LEAVE. This, will leave that much mB as defined, and take the rest, put it in system partition. The default defines are: 8, 4 and 1 respectively.
You may clone this repo, and follow the following steps:
download and compile kernel from android-4.4-recovery branch from https://github.com/thewisenerd/android_kernel_htc_pico
put compiled zImage (arch/arm/boot/zImage) in root directory (i.e. cloned directory)
run the following command to repack recovery ./repack.sh
output recovery would be in output/recovery.img
Downloads:
TWRP 2.8.0.0: http://forum.xda-developers.com/showpost.php?p=56168368&postcount=125
[*] TWRP 2.8.0.0: http://forum.xda-developers.com/showpost.php?p=55685051&postcount=108(26 sep 2014)
[*] Modified TWRP 2.8.0.0: http://forum.xda-developers.com/showpost.php?p=55430289&postcount=106(14 sep 2014)
[*] Modified TWRP 2.8.0.0: http://forum.xda-developers.com/showpost.php?p=55375649&postcount=104(11 sep 2014)
[*] Modified TWRP 2.7.1.0: http://forum.xda-developers.com/showpost.php?p=55246774&postcount=97 (05 sep 2014)
[*] Modified TWRP 2.7.0.0: http://forum.xda-developers.com/showpost.php?p=54709263&postcount=69 (09 Aug 2014)
[*] Modified TWRP 2.7.0.0: http://forum.xda-developers.com/showpost.php?p=54688800&postcount=65 (08 Aug 2014)
[*] Modified TWRP 2.7.0.0: http://forum.xda-developers.com/showpost.php?p=54484381&postcount=58 (30 Jul 2014)
[*] Modified TWRP 2.7.0.0 (resized): http://forum.xda-developers.com/showpost.php?p=53704940&postcount=6
[*] Modified TWRP 2.7.0.0: http://d-h.st/I4L
Kernel: You may use CodyKernel or the kernel provided by your ROM's developer that supports aw3som3.
Q: How to use?
A:
Wipe the system, data and cache partition.
fastboot flash the given recovery.img.
wipe the system, data and cache partitions, again. preferably use flash_erase on the partitions.
flash your preferred ROM
flash the given kernel, *with* aw3som3
you're good to go!
Sources
you can get the patches here:
PS#1: 0001-aw3som3-hax-the-partition-table.patch
PS#2: 0002-aw3som3-set-msm_nand_data.parts-later.patch
PS#3: 0003-aw3som3-rearrange-and-relay-the-partition-table.patch
thewisenerd said:
I've moved all the partition re-laying, resizing, etc, to a separate file, in drivers/misc, which should help keep clean the nand_partitions.c file, and we would have to worry only about one file, and related code. It also means that awesom3 is reduced to one patch
Click to expand...
Click to collapse
PS#1 (26Sep'14):
0001-awesom3-hax-the-partition-table.patch
0002-awesom3-allow-a-128-mB-userdata.patch
XDA:DevDB Information
awesom3, Tool/Utility for the HTC Pico (Explorer)
Contributors
thewisenerd
Version Information
Status: Stable
Created 2014-10-21
Last Updated 2014-10-21
Reserved
Questions&Answers
Q: Does this work?
A: Yes, it does
Q: Will it work on my phone?
A: no. it will blast into pieces. jk.
Yes, it should. The main reason that partitions are dynamically resized, is to avoid having to create tailor-made hex values for every type of NAND device that different picos have.
Q: why the name awesom3?
A: A couple of reasons, actually. I was using the awesome D.E. in my distro a few days before I wrote this patch. I liked that UI, mainly because it was cluster-free, and the maximum available space was always used.
Another, was a couple of twn_oc_helper scripts which I had written before this. I had decided to get rid of the scripts, once and for all, due to various reasons (you can read them here), and the working dir for those scripts was named awesom3. The name just stuck by, and voila!
misc
- setting timezone
1. settings-> Time Zone -> set timezone (closest) and offset.
Reserved
changelog
21Oct2014
- 128 mB userdata partition
- Fix wiping crash when block device is not present (credits to Ethan Yonker)
- mtp: fix log spam: findNode not finding a node is not an error (credits to that)
- Update reference to 24-hour clock (credits to Captain Throwback)
- display cpu temperature in twrp use TW_NO_CPU_TEMP := true to disable display use TW_CPU_CUSTOM_PATH := path to set custom path (credits to Jenkins)
- Add support for TrueType fonts (credits to Vojtech Bocek)
- Fix exfat-fuse handling (credits to Dees Troy)
- performance profile support (credits to Tom Hite)
- mtp: cleanup, fixes and performance improvements (credits to that)
- Update RECOVERY_VARIANT blocking to use project-path-for (credits to Matt Mower)
- Attempt to fix md5 issue with backups (credits to Captain Throwback)
- applypatch: add support for BML partitions (credits to Conn O'Griofa)
- atime is access time, let's just use mtime (credits to Jenkins)
- Remove extra slashes from zip path in openrecovery (credits to Matt Mower)
- Fixes for exfat-fuse (credits to Captain Throwback)
- recovery: Fix adb with linux 3.10 (credits to Benoit Goby)
- ADB sideload command not work (credits to Da Zhou)
- Check sehandle before fixing permissions (credits to Dees Troy)
- Attempt to automatically identify data/media devices (credits to Ethan Yonker)
older logs:
26sep'14
Fix handling of MTP fork/child process (upstream)
Include no strict aliasing for MTP (upstream)
Additional checks to prevent partitioning internal storage (upstream)
pico: use twrp.fstab (help unify recovery compilation with device tree)
removed UMS
updated MTP configs (Sachin Thomas)
aw3som3 -> awesom3
Click to expand...
Click to collapse
14sep'14
add mtp config
Click to expand...
Click to collapse
11sep'14
Add MTP support to recovery thanks mostly to bigbiff with a little help from Dees_Troy
Add command line capabilities - you can now execute various TWRP features via adb instead of the touchscreen
Add support for color in the console and give error, warning, and highlight lines different colors
Track backup and restore progress based on file sizes to provide a much more accurate indication of progress
Improve handling of /misc thanks to mdmower
Improve setting of time on Qualcomm devices thanks to [NUT]
Allow using images on slidervalue GUI objects thanks to Tassadar
Allow using variables and addition and subtraction in variables for easier theming
Add support for 1440x2560, 280x280, and 320x320 resolutions and update 240x240
Allow ui.xml file to include additional xml files to help break up the theme and make TWRP easier to maintain
Other minor fixes and improvements
Click to expand...
Click to collapse
05sep'14
updated sources to TWRP 2.7.1.0 (till 01 sep 2014)
removed TW_EXCLUDE_SUPERSU := true
removed TW_NO_EXFAT := true
Click to expand...
Click to collapse
09aug'14
use inverted logo
Click to expand...
Click to collapse
08aug'14
relay partition table
add graphic logo && text to differentiate between normal and awesom3 recovery
Click to expand...
Click to collapse
30jul'14
uses the normal pico_defconfig: !not! slimmered (this fixes *some* of the random reboots caused in recovery)
aw3som3: set msm_nand_data.parts later (0002-aw3som3-set-msm_nand_data.parts-later.patch)
Click to expand...
Click to collapse
27jun'14
resize the recovery
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Click to expand...
Click to collapse
here's mine.
it's working.
{
"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"
}
great work for this one @thewisenerd. :good:
i'm really excited for this aw3som3.
btw. what if we completely get the whole mtdblock5? we'll get a great space for /system.
it's time to use sd-ext completely.
Agaphetos said:
btw. what if we completely get the whole mtdblock5? we'll get a great space for /system.
it's time to use sd-ext completely.
Click to expand...
Click to collapse
That's a question to the users.
p.s. added that to OP
thewisenerd said:
That's a question to the users.
p.s. added that to OP
Click to expand...
Click to collapse
make a POLL for it. :good:
will you please tell me step by step procedure i am noob and don't know how to do all this stuff
I am currently using CM11 weekly 4 TWRP 2.7 recovery
the recovery has been resized, hopefully. get another beta here: http://www.solidfiles.com/d/e6d39a02c4/recovery.img
hopefully, we're just a few commits away from a complete partition table rewrite... I've decided to move devlog to the beginning, then, a 4 mB cache (you shouldn't need more), and the rest for the /system partition. What about /data? sd-ext becomes /data partition by default. I posted a poll on the FB group and most of the people are clearly fed up with internal memory being very low hence, already using sd-ext by default, why "waste" the data partition?
This would stay in beta till some more time.
a new build of twrp should be out any time soon... the kernel, slimmered down to 1.8 mB without affecting actual functionality, *and* adding back support for ext2/3 and exfat and ntfs.
the recovery's size has been slimmered too, by modifying its ramdisk compression. you might not be much interested in all that, but you should see the change in recovery size from this build itself.
and finally, here's the boot.img: http://d-h.st/5jK
proof that it works (otherwise which no one's going to download anyways):
as we are going to use complete /data partition + some moar of cache partition, 112 +
just pushed sources to git some time ago...
you can get the patches here: https://github.com/thewisenerd/android_kernel_htc_pico/commit/eaa7cd3d0d25b44ecbe026ea03dce796868adb35
slimmered recovery defconfig: https://github.com/thewisenerd/android_kernel_htc_pico/commit/1fbb5f37851d6ff4a1d40d91e71d39ac107cd8c4
Tried it on cm 11 works great thanks for the recovery and boot.img
noob question
pico hackr said:
Tried it on cm 11 works great thanks for the recovery and boot.img
Sent from my XT1033 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
how do I made this work bro?
I mean how many partitions should I have particularly their each sizes too
thanks in advance
Agaphetos said:
here's mine.
it's working.
Click to expand...
Click to collapse
instead of
Code:
http://dl-1.va.us.xda-developers.com/2/8/1/6/0/8/7/Screenshot_from_2014-06-24_202911.png?key=Kg2Fp7s86-Ky-H0UFugPJQ&ts=1403661729
use
Code:
http://forum.xda-developers.com/attachment.php?attachmentid=2816087
as your image link... that should fix image not showing.
memontalha said:
will you please tell me step by step procedure i am noob and don't know how to do all this stuff
I am currently using CM11 weekly 4 TWRP 2.7 recovery
Click to expand...
Click to collapse
theBstep said:
how do I made this work bro?
I mean how many partitions should I have particularly their each sizes too
thanks in advance
Click to expand...
Click to collapse
Its for this very reason that I wrote this patch. Users don't have to do anything, except what's written in OP.
This is out of beta now, (read: stable), and can be used.
For others: I'll be shifting to a "no userdata", "4 mB cache", and all for "system" policy soon. Hopefully, you can revert back those commits if you don't need. As a user, 150 mB has never been adequate since I had used 40int2ext, and so, I'll be making sd-ext for /data as default.
This would also involve refactoring the entire table, I've decided to move devlog a few places ahead and order it as boot:devlog:cache:system, which should, technically, make stuff easier (for me) if done in the kernel side.
Don't want that? Revert back those commits, simple as that.
p.s. after thinking about this for sometime, this would also involve editing fstabs, recoveries, etc, etc, so, we'll rather stick to the current partitioning, i.e. mtdblock3/4/5, and keep it as 1 mB userdata, rather than no userdata, so that all the mess of having to edit other stuff would be minimised.
welcome working pa's micro modular gapps (soon), which takes up about 135 mB of /system partition, which should fit, after we bring in some more space from userdata partition.
Perfect Setup Bro
Well it will be good if we use sd-ext as data default
Much System Space :laugh:
Regards : Bilal
Sent from my One M8 using XDA-FORUM, powered by appyet.com
well it's a nice work,but also make a guide on how to revert back to original partition table.
Jituv1996 said:
well it's a nice work,but also make a guide on how to revert back to original partition table.
Click to expand...
Click to collapse
Just flash a recovery and kernel that's not modded?
can i try using this recovery and boot.img with in2ext+??
will it work without any problem?
i dont wanna lose my partition
Hpsgill said:
can i try using this recovery and boot.img with in2ext+??
will it work without any problem?
i dont wanna lose my partition
Click to expand...
Click to collapse
it didnt worked for me I have to install fresh rom for using this mod .
btw thanks @thewisenerd for this aw3som3 mod ill be using it for weeklies
noobified
I tried and so far so good with cm weekly 5 :laugh: I flashed latest cody kernel by the way
the thing is how can I increase internal memory cus only system increased? do I need to add a partition again so that makes 4: fat32, sd-data, sd-cache and sd-ext
theBstep said:
I tried and so far so good with cm weekly 5 :laugh: I flashed latest cody kernel by the way
the thing is how can I increase internal memory cus only system increased? do I need to add a partition again so that makes 4: fat32, sd-data, sd-cache and sd-ext
Click to expand...
Click to collapse
nah, fat32, and sd-data would do
Its really messed up (all the "extra" partitions), considering we don't need to worry about the /cache partition.
The only partitions you need are a fat32 partition, and *one* ext2/3 partitions. Any more partitions, your headaches.
Also, I would suggest that mmcblk0p2 is directly mounted as /data, instead of using any scripts :angel:
hahaha okay as a matter of fact I followed your instructions to partition without card reader http://forum.xda-developers.com/showthread.php?t=2532212 which is really helpful
mmcblk0p2 mean I can modify it for increasing internal?
Related
_~~~ Avaritia HD ~~~__
...when a DESIRE grows inordinately strong it becomes AVARICE ...
I tested almost all Desire HD ROMs with data2sd (!).... and i didn't like any of those. The reason is that the data2sd solution is done in a bad "patchwork" way. The reason is this: A Desire HD rom needs about 350mb for the system partition (nand). But the Desire has only 250mb for system available. To make HD Rom work all the devs move system stuff to the SD. This is needed if you provide an app2sd ROM because app2sd still needs some space of the internal data partition. But this is different on a data2sd ROM. In that case you only need 1mb of the internal nand. All other ROMs STILL move system stuff to the sd for their data2sd version although there is much free space on the internal now. Thats why i decided to make my own ROM .... optimized for data2sd only. This way all the 350mb of system is installed to the nand. This way i make good use of all the free memory that you get on data2sd and thats why i wont provide an app2sd version of this ROM. Instead of making data2sd for a ROM i made a ROM for data2sd.
Apart from that i tried to improve data2sd in general and the included script has advantages you don't get on other Desire HD roms. Other HD Roms use a "loop" device for data2sd. I find that a bit risky and thats why i didnt make that default but provide this as an OPTIONAL addon. The life-of-the-edge mod is not more risky than other data2sd Roms .... the difference is that I tell you about the risk and give you to choice if you want to use it....
This ROM is still work in progress and i still won't provide a full feature list (but i think you won't miss a thing because all "usual" features are included). Instead i give you a feature list of features that won't find in any other data2sd HD-ROM.
Features: (that make this ROM unique - at least for some time )
- partition alignment with zips.
- optimized layout for data2sd (system apps on NAND)
- ReiserFS, btrfs, JFS support + recovery
- "deadline" scheduler instead of cfq/bfq which is better for a microSD
I'll add some explanations for the features in future.
Requirements:
-A second Partition in Ext2/3/4 format (same as for app2sd - min 512 but 1024 mb highly recommended max is 2048 mb)
-FULL WIPE (if you come from any other rom or a version before 0.6)
-Default nand partition layout (if you dont know what this means dont care about it .... youll have it then )
Apart from the ext2/3/4 partition this ROM also supports other filesystems (btrfs, Reiserfs, jfs). See 2nd post for "mods" to align, format you partion in the desired filesystem. And for recovery.
Download
Avaritia HD v0.7 alpha (ftp - thanks c0urier)
Avaritia HD v0.6 alpha (ftp - thanks c0urier)
Avaritia HD v0.5 alpha (ftp - thanks c0urier)
WARNING: btrfs is still experimental, jfs is made for IBM servers with battery backed hdds, and the developer of reiserfs killed his wife ... so be careful with those.
Additional info: EXT3 is recommended. Akso see /sdcard/Avaritia/ for the config file.
Pictures
{
"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"
}
Changelog (newest)
v0.7
- reverted rebase - Base is now RUU_Ace_HTC_WWE_1.32.405.6
- Cgroup errors on bfs fixed (through rebase)
Note: HTC using cgroup to speed up interactivity on CFS is not the way forward when
a sheduler MADE for interactivity (BFS) - CFS + cgroups is intended for large servers
and not for a phone.
- Dpad to wake / volume keys works now and included (see mods to "unflash")
- Power Notification widget included as default (see mods to unflash)
- Add custom Wallpaper to the default skin
- Fixed bootanimation (2 frames were too bright + made it a bit slower)
- Bluelight "fun" on boot
- Updated apks
- Some tweaks (mostly adopted from ownhere - thx ownhere)
- Some fixes.
For a complete changelog see the attached full-changelog.txt file
Known Issues and Recommendations
-As for all data to sd solution you may have slowdowns in some situations like market downloads if you have a slow microSD. Any data2sd solution is about space in the first place. But compared to other data2sd ROMs this ROM is faster.
-If you use any other filesystem you need the custom recover from 2nd post.
-FAKE quadrant scores if you use "life-on-the-edge". This does not show the real performance. This skips data base synchronization. It improves the performance (but not as much as bench suggests) at the risk of data safety.
- 720p not working. (see here)
Further Plans
Many....
Thanks
- Coutts99 for the Kernel
- ownhere for tools an help
- Sibere for data2sd/ext
- snq- : vdd, powermenu, camera etc
- woti23 for his unrestless benching
- supercurio and Unhelpful from #project-voodoo
- IEF from #alpharev
- c0urier for hosting
- all devs @ xda
GPL: kernel is an exact git-clone from coutts99 kernel till commit http://git.couttstech.com/?p=coutts...it;h=73857c9910ea276eca798f6cc6a10f424a5eace9 ... no changes to source only different .config .
Also make sure you check coutts thread:http://forum.xda-developers.com/showthread.php?t=849002
All credit for the Kernel to him
[ROM] Avaritia HD v0.1 alpha [ data2ext4 | data2btrfs]
Additional stuff:
Recovery
Clockwork 2.5.0.7 and 2.5.1.8 with support for wipe, install, Nandroid backup and restore for reiserfs, jfs, btrfs ... and ext2,3,4 of course
Custom recoveries
Alignment zip
This will format (WIPE !!!) you sd-ext in the desired format. In addition it will align the sd-ext partition to the "erase block size" of your sd-card ( 1 MiB alignment like gparted - Infos here. Zips do that for you ... ).
ALL alignment zips
Kernel
BFS kernel is here (default)
CFS Kernel is here
Mods:
- dpad to unlock (in ROM as default) + uninstall
- Power notification widget (in ROM as default) + uninstall
- The modified skin (in ROM as default) + original
- a custom splash1.img (see picture)
ALL mods
Splash1:
Looks great, will test it
----- place ------
EDIT: LOL. I was to slow for a placeholder. NVM i dont think i need it anyway... it's not a tutorial or something .....
melethron said:
----- place ------
EDIT: LOL. I was to slow for a placeholder. NVM i dont think i need it anyway... it's not a tutorial or something .....
Click to expand...
Click to collapse
hehe, sorry
what is the benefits of data2btrfs?
b3ndik said:
hehe, sorry
what is the benefits of data2btrfs?
Click to expand...
Click to collapse
Check the thread. In short btrfs is a copy on write filesystem. And overwriting is the slowest operation for a microSD. Btrfs has some options to optimize the ssd devices. Especially slow cards profit from it (for good cards it may be worse). Apart from that it doesn't need journaling to be safe because of COW. This decreases the overhead on writes.
Overall data2sd feels smoother on btrfs than on ext4 (at least for a class 2 microSD). Check the thread for more info and note that BTRFS is a BETA FILESYSTEM.
I just gave you another post directly below your original one All you have to do is edit it and use it.
Nice to see you choose the right ROM
I'm following your progress of your btrfs work a time now, and played around with it, too. I flash it to my device, lets see how it is
Please make the same with the desireZ rom
PaY87 said:
Nice to see you choose the right ROM
I'm following your progress of your btrfs work a time now, and played around with it, too. I flash it to my device, lets see how it is
Click to expand...
Click to collapse
Coutts99 recommended it and after i looked at it found it rather easy to check the structure. Not much symlinks etc. Very clean and AFAIK the ROM that is closest to stock. Still needed to adjust many things (zipalign etc).
rolfd said:
I just gave you another post directly below your original one All you have to do is edit it and use it.
Click to expand...
Click to collapse
Thx for that
animehq said:
Please make the same with the desireZ rom
Click to expand...
Click to collapse
Atm i first focus on btrfs and this rom. I also need to get familiar with cooking first. Maybe in the future, but don't wait for it. Sorry
We will wait for pays next release.
With btrfs
but good work by melethron.
PaY87 said:
Nice to see you choose the right ROM
I'm following your progress of your btrfs work a time now, and played around with it, too. I flash it to my device, lets see how it is
Click to expand...
Click to collapse
Sent from my HTC Desire using XDA App
animehq said:
Please make the same with the desireZ rom
Click to expand...
Click to collapse
If this btrfs works good, then of course i will release such version dont worry hehe
@melethron
Congrats on the rom btw
WHAT software can i make a data2btrfs in my sd card???
gn123099 said:
WHAT software can i make a data2btrfs in my sd card???
Click to expand...
Click to collapse
The best way if you are not already on a linux based system, is to grab a livecd and use gparted. Normally I would recommend Ubuntu, but Ubuntu 10.10 LiveCD got problems with btrfs + gparted. So you could try fedora or opensuse e.g.
Of course you can also use the gparted live cd or usb version.
I never tried them, but should be the same:
http://gparted.sourceforge.net/livecd.php
With gparted format your sd card to FAT32 (first partion) and then 1024MB to btrfs (second partition).
Copy the ROM to your FAT32 partition and flash it through the recovery. I recommend AmonRAs latest recovery!
Don't forget to wipe before you flash! Don't worry if you get error messages when trying wiping the sd-ext, just ignore that.
Regards
I flashed the rom in btrfs mode. Installation without problems.
Its nice to see so much space on the phone.
The only thing is that the device really seems slower now.
Of course this is not your fault, you give us a great solution for more storage, but you can feel the difference.
I will let the phone do some caching and will use it a hole day tomorrow. (Navigation included). Lets see maybe things will settle down a little.
Maybe it could be improved with a optimized kernel.
I got a class 6 sd card by the way.
PaY87 said:
The best way if you are not already on a linux based system, is to grab a livecd and use gparted. Normally I would recommend Ubuntu, but Ubuntu 10.10 LiveCD got problems with btrfs + gparted. So you could try fedora or opensuse e.g.
Click to expand...
Click to collapse
Pays, i normally use either UltimateLinux build for the meerkat or plain lynx. Are any of these distros have issue with btrfs too ?
Thanks
BL
I'll be testing this as soon as I can as I'm skeptical of Btrfs. Only way to check and test the actual Btrfs usability and performance with our device and ROMs is to use it with one. I'll try it with a class 2 SD first, then class 4 and 6 that I own. Thanks.
EDIT: Yeah, your "my data2btrfs" link talks about "advantages" where no. 1/2/4 are all speculation yet. There's no studies or widespread reliable, repeatable, and conclusive testing showing either. Basically, this is experimental.
EDIT2: Sorry can't help further. I bricked my device. Carry on.
------------------------------
- Sent via HTC Desire -
I'm giving this ROM a shot, currently downloading and partitioning it. You used coutt's btrfs_test kernel right?
Dragooon123 said:
I'm giving this ROM a shot, currently downloading and partitioning it. You used coutt's btrfs_test kernel right?
Click to expand...
Click to collapse
Read first post again...
Lol, missed it. Sorry .
F2FS FOR EVITA ANY AOSP ROM
F2FS for EVITA
AOSP only!
Current CM or most any of our AOSP ROMs around here that use a current CM based kernel.
THIS IS EXPERIMENTAL AND HAS POTENTIAL FOR DATA LOSS IF DONE IMPROPERLY. IF YOU ARE NOT COMFORTABLE WITH THAT PLEASE DO NOT ATTEMPT. I CANNOT BE AVAILABLE FOR 24/7 SUPPORT ON THIS.
These mods will provide the ability to format /data and /cache in F2FS format instead of EXT4. Use extreme caution. The will erase your entire /data partition just like a clean flash. I cannot and will not be held responsible for your failure to keep backups handy. F2FS is still considered experimental by Samsung and should be by you the user as well.
What is F2FS?
F2FS wiki
Why F2FS?
F2FS put to the test vs EXT4
How to switch?
PLEASE READ INSTRUCTIONS CAREFULLY. IF NOT FOLLOWED YOU WILL LIKELY BOOTLOOP!!
F2FS capable TWRP Recovery 2.7.1.0 KK version
F2FS capable TWRP Recovery 2.8.5.0 KK versionThis is the same as the current official TWRP built with the added F2FS support commits. When wiping a partition you will have the option to reformat in F2FS now as well.
Kernel+fstab conversion zip Flash this after converting partitions to F2FS to install a CM kernel with F2FS support built in. This zip uses an anykernel installer so it should be comparable with most current ROMS. The zip will extract your current boot.img, unpack and replace your current fstab with a new fstab to indicate you current partition types, replace kernel with F2FS capable kernel , then repack and replace the boot.img
Fstab conversion zip For use only when you are already running a F2FS kernel and only need to update fstab after switching to/from F2FS/EXT4. This installer will only unpack, edit the fstab, and repack the boot.img. This will not replace the kernel, you must already be using an F2FS kernel or be returning to EXT4 only to make use of this zip.
DOWNLOADS NOW HOSTED @ CODEFI.RE
http://downloads.codefi.re/jrior001/Evita-f2fs
Procedure for fresh conversion including new Rom flashing:
1. Backup everthing you want to keep with titanium backup or whatever backup you choose.
2. Fastboot flash the new recovery img.
3. Run a twrp backup in case things get ugly!
4. Flash new ROM now if desired.
5. Still in recovery...Goto wipe -> hit Advanced wipe. Select data and hit change partition type. Convert to F2FS. Repeat for cache.
6. Flash the Kernel+fstab conversion zip.
7. Reboot and profit. Any partition app on market can confirm new format changes.
Procedure for nightly ROM updates after F2FS conversion:
1. Flaah nightly
2. Flash kernel+fstab conversion zip.
Procedure if you want to convert back and forth after initial conversion for testing purposes:
1. Change formats of data/cache as desired (only ext4 and f2fs supported).
2. Flash fstab conversion zip to update format types before attempting boot.
Code:
CHANGELOG
V1.0 - Initial release
V1.1 - added inline_data flag to F2FS mounts
V1.2 - updated to latest kernel/fstab as of 8/9
V2.0 - updated for cm-12.0
Source:
Kernel: https://github.com/jrior001/android_kernel_htc_msm8960/tree/cm-11.0-f2fs
Recovery tree: https://github.com/jrior001/twrp-htc-evita/tree/cm-12.0
Fstab scripts: https://github.com/jrior001/f2fs_fstab_convert_script
Devs, feel free to use or modify any of this for your own work just give thanks to where it came from. It was not all my original work, I must give thanks to Metallice and a few other devs in the grouper forum whose scripts I adapted for my own work.
XDA:DevDB Information
F2FS EVITA, Kernel for the AT&T HTC One X
Contributors
jrior001
Source Code: https://github.com/jrior001/f2fs_fstab_convert_script
Kernel Special Features: f2fs support
Version Information
Status: Beta
Current Beta Version: 1.0
Beta Release Date: 2014-07-08
Created 2014-07-09
Last Updated 2015-02-26
Links and Instructions are now up. As promised, F2FS support is now possible for /data and /cache on Evita. For now there is no support for converting /system to F2FS as most have said it does not show significant gains because there is far less writing to /system partition. Also, as of now the only way to support converting /system would require specific ROMs built specifically for F2FS on system. As I have done it here we remain flexible to flash any regular nightly and still enjoy the gains of F2FS on /data and /cache. Follow instructions carefully and enjoy.
If we were building an AOSP ROM, how would we have F2FS already enabled? just wondering if there was a way to eliminate a few steps
pandasa123 said:
If we were building an AOSP ROM, how would we have F2FS already enabled? just wondering if there was a way to eliminate a few steps
Click to expand...
Click to collapse
I've been following some other devices trials and tribulations with f2fs. Most other places I'm seeing dev convert the partitions in the device trees fstab. This results in a fixed f2fs or fixed ext4 ROM. As a dev that means building 2 ROMs which is a time waster.
With these fstab scripts I modded from the grouper forums I was able to make basically any aosp ROM adaptable to f2fs or ext4 for data and cache. I have included this same script work and the needed f2fs tools into the torched installer as well as the f2fs conversion zips.
Pandasa123 I have posted all the source in the f2fs thread. You really only need the kernel commits and the f2fs capable recovery along with my scripts. You could also build a fixed f2fs ROM if you chose and I have commits on my github and on CM gerrit to use as examples for that as well. I have also pushed kernel commits to CM gerreit in hopes that intervigil will merge them to make this a lot simpler but I highly doubt that will happen.
@pandasa123, little more info...
If you look through my fstab zip scripts you'll find that they check the partitions for filesystem type, unpack the boot.img and the edit the fstab accordingly for f2fs or ext4 with all the proper mount flags and then repack the boot.img.
This seemed to me to be an easy way for any user to get their feet wet on f2fs and it takes the extra work away from the devs having to cook duplicate roms. Flash any current ROM, then flash the conversion zip to get your fstab proper based on whatever partition format you are currently on.
There is also a movement on liquid smooth to incorporate this type of conversion script into the ROM zip but its still a huge wip.
Great work, what an awesome parting gift. I have to say again, you've been such a fantastic asset to the Evita forum, easily one of the most significant and high quality contributors we've had the privilege to have here. Really wish I could get my hands on a OnePlus One now!
Sent from my Evita
timmaaa said:
Great work, what an awesome parting gift. I have to say again, you've been such a fantastic asset to the Evita forum, easily one of the most significant and high quality contributors we've had the privilege to have here. Really wish I could get my hands on a OnePlus One now!
Sent from my Evita
Click to expand...
Click to collapse
Did you try the f2fs yet? Curious for some feedback on how it feels to others. @cannondaleV2000 was helping me test this for a week or so until he bricked his ville then other day(unrelated, switching hboots failed him).
I haven't yet, I'm a stay at home dad to a seven week old little girl so I struggle to find the time to even flash a ROM recently. If I get some free time (that's a fairly big if) I'll definitely test it out. It's a real shame about his Ville, I think he got really unlucky and his PC thermalled and rebooted on him during the hboot change. Pretty sure he's getting it jtagged though.
Sent from my Evita
jrior001 said:
Did you try the f2fs yet? Curious for some feedback on how it feels to others. @cannondaleV2000 was helping me test this for a week or so until he bricked his ville then other day(unrelated, switching hboots failed him).
Click to expand...
Click to collapse
I will test and report back with benchmarks shortly.
EXT4 vs F2FS benchmarks
{
"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"
}
These were done on the same ROM (PA 4.42 stock kernel, then PA 4.42 F2FS evita kernel), followed instructions exactly, rebooted and re-ran the benchmark several times with approximately the same results. Benchmarks were performed on the /data partition. Not sure why SQLite performance took such a hit...
sephiroth2k said:
Click to expand...
Click to collapse
Generally similar to what numbers I had as well. Noticeable gains in both continuous and random write speeds.
jrior001 said:
Generally similar to what numbers I had as well. Noticeable gains in both continuous and random write speeds.
Click to expand...
Click to collapse
Yeah definitely, just curious as to why SQLite was slower with faster random write benchmarks? Seems counter-intuitive; faster writes should mean faster database writes. Also, across multiple runs Browser and Camcorder opened more quickly with F2FS but Camera was slower. IANA filesystem developer however. Thanks for this awesome contribution to the evita scene.
---------- Post added at 09:33 PM ---------- Previous post was at 09:13 PM ----------
Hey I googled a little and found this, suggested issue was "I suspect that you turned on CONFIG_DEBUG_MUTEXES in your .config." # CONFIG_DEBUG_MUTEXES is not set in ville_defconfig . Just throwing it out there
sephiroth2k said:
Yeah definitely, just curious as to why SQLite was slower with faster random write benchmarks? Seems counter-intuitive; faster writes should mean faster database writes. Also, across multiple runs Browser and Camcorder opened more quickly with F2FS but Camera was slower. IANA filesystem developer however. Thanks for this awesome contribution to the evita scene.
---------- Post added at 09:33 PM ---------- Previous post was at 09:13 PM ----------
Hey I googled a little and found this, suggested issue was "I suspect that you turned on CONFIG_DEBUG_MUTEXES in your .config." # CONFIG_DEBUG_MUTEXES is not set in ville_defconfig . Just throwing it out there
Click to expand...
Click to collapse
Its off in Evita source as well. Appreciate the effort and I will look more at that commit as well.
I decided to give the F2FS a try and so I went with the latest CarbonKat and your Torched kernel. I haven't run any benchmarks and I'm still getting all my stuff put back on here but I must say that almost everything seems faster so far. Most noticeable differences so far for me are bootup time is significantly shorter and my phone didn't slow down much at all while installing my apps from the Play Store. Before the switch to F2FS, I had noticed that my phone would lag (sometimes badly) as I would go through the My Apps list in the Play Store and continue choosing apps to install while others were still downloading/installing. Also for me most apps seem to open a little faster than before and work more smoothly.
I do have a question for you about the TWRP backup/restore process with F2FS. Specifically, lets say I backup CarbonKat with the F2FS partitions and then install something else without F2FS (or restore another backup that is not F2FS). If I want to switch back, can I then just restore my TWRP backup of CarbonKat with F2FS? If not, can you recommend a process for that? I'm probably not going to switch from this setup for a while but its hard to tell.
Also, about using the kernel+fstab zip vs just the fstab zip...I used the fstab only zip after flashing your kernel (which already has F2FS support) and that worked out fine for me. But, could I just always use the kernel+fstab zip even if the kernel I flash already has F2FS support?
Hope these questions are ok and thank you for all that you've done for our devices. This F2FS change is one of the most noticeable performance increases I've seen on my Evita and it's been my daily driver since AT&T released it back in 2012. Are there any benchmarks that you'd like me to run or any questions I might be able to answer for you on my usage/experience? If so, I may have to ask for detailed instructions if there's something I haven't needed to do before with android (still learning).
budroid said:
I decided to give the F2FS a try and so I went with the latest CarbonKat and your Torched kernel. I haven't run any benchmarks and I'm still getting all my stuff put back on here but I must say that almost everything seems faster so far. Most noticeable differences so far for me are bootup time is significantly shorter and my phone didn't slow down much at all while installing my apps from the Play Store. Before the switch to F2FS, I had noticed that my phone would lag (sometimes badly) as I would go through the My Apps list in the Play Store and continue choosing apps to install while others were still downloading/installing. Also for me most apps seem to open a little faster than before and work more smoothly.
Click to expand...
Click to collapse
That's bid difference I saw as well, apps install and load a bit quicker.
budroid said:
I do have a question for you about the TWRP backup/restore process with F2FS. Specifically, lets say I backup CarbonKat with the F2FS partitions and then install something else without F2FS (or restore another backup that is not F2FS). If I want to switch back, can I then just restore my TWRP backup of CarbonKat with F2FS? If not, can you recommend a process for that? I'm probably not going to switch from this setup for a while but its hard to tell.
Click to expand...
Click to collapse
If you ran a backup of your old ext4 /data partition and attempt to restore it, TWRP will restore it exactly as it was, in ext4. Lable your backups yo make it easier on yourself!! Twrp will restore in the same format as it was when backed up. Make sure you run the fstab script afterwards or you will bootloop while it fails to load /data.
budroid said:
Also, about using the kernel+fstab zip vs just the fstab zip...I used the fstab only zip after flashing your kernel (which already has F2FS support) and that worked out fine for me. But, could I just always use the kernel+fstab zip even if the kernel I flash already has F2FS support?
Click to expand...
Click to collapse
Yes but it will replace your kernel with a basic CM kernel w/f2fs support. If you want to run torched you made the right choice using the fstab only.
EDIT: Torched Installer includes the conversion script as well now.
budroid said:
Hope these questions are ok and thank you for all that you've done for our devices.
Click to expand...
Click to collapse
Great questions!! And your welcome, I've learned tons messing with this over the last 2 years
Flashed torched instead of Evita f2fs and speeds are much better.
sephiroth2k said:
Flashed torched instead of Evita f2fs and speeds are much better.
Click to expand...
Click to collapse
Could you please define "speeds"? Do you have any supportive data or is this just anecdotal?
Sent from my Evita
timmaaa said:
Could you please define "speeds"? Do you have any supportive data or is this just anecdotal?
Sent from my Evita
Click to expand...
Click to collapse
Torched F2FS is on the right in attached image. As you would say, read the thread - I've been posting benchmarks . I'm at work, didn't attach first try.
sephiroth2k said:
Torched F2FS is on the right in attached image. As you would say, read the thread - I've been posting benchmarks . I'm at work, didn't attach first try.
Click to expand...
Click to collapse
Yeah I've seen your earlier posts, was just wondering where the benchmarks were this time.
Sent from my Evita
timmaaa said:
Yeah I've seen your earlier posts, was just wondering where the benchmarks were this time.
Sent from my Evita
Click to expand...
Click to collapse
No problem - difference is incredible - apps install and open much faster, everything seems smoother (this is subjective of course). Thanks @jrior001 for breathing new life into my aging evita :highfive:
F2FS for ACE
AOSP only!
S-ON USERS SEE ADDITIONAL INSTRUCTIONS BELOW
Should work on all current CM12 or most any of our LP-based AOSP ROMs around here that use a current CM based kernel/trees
THIS IS EXPERIMENTAL AND HAS POTENTIAL FOR DATA LOSS IF DONE IMPROPERLY. IF YOU ARE NOT COMFORTABLE WITH THAT PLEASE DO NOT ATTEMPT. I CANNOT BE AVAILABLE FOR 24/7 SUPPORT ON THIS.
These mods will provide the ability to format /data and /cache in F2FS format instead of EXT4. Use extreme caution. The will erase your entire /data partition just like a clean flash. I cannot and will not be held responsible for your failure to keep backups handy. F2FS is still considered experimental by Samsung and should be by you the user as well.
What is F2FS?
F2FS wiki
Why F2FS?
F2FS put to the test vs EXT4
How to switch?
PLEASE READ INSTRUCTIONS CAREFULLY. IF NOT FOLLOWED YOU WILL LIKELY BOOTLOOP!!
F2FS capable TWRP Recovery This is the same link the current 2.8.1.1 TWRP built with the added F2FS support commits. When wiping a partition you will have the option to reformat in F2FS now as well.
Fstab conversion zip Fstab is the file used by the kernel to determine how to mount all partitions. CM default is all EXT4. To utilize F2FS we need to modify your fstab. This installer is for use only when you are already running a F2FS kernel and only need to update fstab after switching to/from F2FS/EXT4. This installer will only unpack, edit the fstab according to your current partitions and repack the boot.img. This will not replace the kernel, you must already be using an F2FS kernel or be returning to EXT4 only to make use of this zip.
DOWNLOADS NOW HOSTED @ CODEFI.RE
http://downloads.codefi.re/jrior001/Ace
Procedure for fresh conversion including new Rom flashing:
1. Backup everthing you want to keep with titanium backup or whatever backup you choose.
2. Fastboot flash the new TWRP recovery img if you are not already on it.
3. Run a twrp backup in case things get ugly!
4. Flash new ROM now if desired.
5. Still in recovery...Goto wipe -> hit Advanced wipe. Select data and hit "Repair or change filesystem". Convert to F2FS. Repeat for cache.
6. Flash the fstab conversion zip.
7. Reboot and profit. Any partition app on market can confirm new format changes.
Procedure for nightly ROM updates after F2FS conversion:
1. Flaah nightly ( manually, do not let OTA update flash on its own, you will not be given the chance to flash fstab zip and you WILL BOOTLOOP. Should this happen return to recovery and perform step 2)
2. Flash fstab conversion zip.
3. Reboot and profit.
Procedure if you want to convert back and forth after initial conversion for testing purposes:
1. Change formats of data/cache as desired (only ext4 and f2fs supported).
2. Flash fstab conversion zip to update format types before attempting boot.
S-ON USERS
Code:
If someone has S-ON device, you still can use it like this:
After flashing ROM, reboot to bootloader and fastboot flash boot.IMG provided in ROM.zip as normal. This is required to get any new kernel updates. Return to recovery and make your desired f2fs changes and flash the f2fs script.
After you flashed this f2fs script, the modified boot image will be located at: /tmp/newboot.img
Now we need to download it by using adb in recovery: adb pull /tmp/newboot.img boot.img
After that, you can flash boot.img via fastboot and reboot as usual. (fastboot flash boot boot.img)
Code:
CHANGELOG
V1.0 - Initial release
V2 - switch to by-name fstab entries to go with cm12 nightlies after 1/9/15
V2.1 - typo fix
V3 - corrects fstab name after file name change introduced in 1/14 nightlies and beyond
Source:
Kernel: https://github.com/OpenDesireProject/android_kernel_htc_msm7x30/tree/cm-12.0
Device tree: https://github.com/OpenDesireProject/android_device_htc_ace
Fstab scripts: https://github.com/jrior001/f2fs_fstab_convert_script
Devs, feel free to use or modify any of this for your own work just give thanks to where it came from. It was not all my original work, I must give thanks to Metallice and a few other devs in the grouper forum whose scripts I adapted for my own work.
Contributors
jrior001 @Mustaavalkosta, @paulb-nl and any others that have helped keep msm7x30 alive
Kernel Special Features: f2fs support
Version Information
Status: Beta
Current Beta Version: 1.0
Beta Release Date: 2015-01-06
Created 2015-01-06
Last Updated 2015-01-06
Important to note, all issues related to f2fs need to stay here and out of the cm12 thread. This is a experimental tweak and mustaa has enough to deal with, without unsupported drama. Please be respectful of this. Thanks and enjoy!
Cant find Convert to F2FS in recovery
hey thanks for your great effort.
I decided to do a test alongside today's [cm-12-20150107-UNOFFICIAL-ace] nightly but, unfortunately for me, I couldn't identify convert to f2fs after under change file system on the recovery [openrecovery-TWRP-ace-2.8.1.1-unofficial].
What will be the issue....
A few of you should test and let's see what happens.
Maybe am not doing something right.
am on TWRP v2.8.1.1 and S-FF with bootloader unlocked
Thanks :good:
xdagee said:
hey thanks for your great effort.
I decided to do a test alongside today's [cm-12-20150107-UNOFFICIAL-ace] nightly but, unfortunately for me, I couldn't identify convert to f2fs after under change file system on the recovery [openrecovery-TWRP-ace-2.8.1.1-unofficial].
What will be the issue....
A few of you should test and let's see what happens.
Maybe am not doing something right.
am on TWRP v2.8.1.1 and S-FF with bootloader unlocked
Thanks :good:
Click to expand...
Click to collapse
You need to go to Advanced Wipe and select data or cache partition and choose Repair or Change File System > Change File System > F2FS. This will format the partition so make sure you don't lose anything important.
Mustaavalkosta said:
You need to go to Advanced Wipe and select data or cache partition and choose Repair or Change File System > Change File System > F2FS. This will format the partition so make sure you don't lose anything important.
Click to expand...
Click to collapse
Thanks got it to work . I haven't done any major testing though but i believe i will do, will be back with my takes.
xdagee said:
Thanks got it to work . I haven't done any major testing though but i believe i will do, will be back with my takes.
Click to expand...
Click to collapse
Very good, interested what your experience is. I ran a bunch of tests when I got this working on my One XL(Evita) and found f2fs to be slightly better for heavy read/write action things like installing apps(especially that initial Google restore of apps on first boot) and more less the same or slightly better in daily use.
First of all- every next restart is rom more responsive. (it has it's own limitations, of course ) I'm not testing very much, but using as usually. Second- Gallery app doesn't show pictures until i enabled root access.. this is new problem, ringtone was unknown too, 0103 release was fine with this. So..don't know where is problem, but i see that this is good step. Thank you!!!
edit: @Mustaavalkosta , @jrior001 : this is not very good that your threads are separated. Because I see new problems that i never seen before, so I think this is problem of F2FS. In my previous installed nightly (it was one of those "smaller", so no 0103 as I wrote before, but maybe 0101?) was calculator OK, media player too, gallery too and ringtones too. Now I have problem with all - direct after restart i see pictures in gallery but after (what?) again i can't see it. Ringtone - i set ringtone and it was ok, but later it changes to "unknown" - so no ringtone. Audio player has similar problem.
...on other side - it is really good. (Musta's ROMS and this too). Thanks for your work!
Updated OP with S-ON flashing instructions courtesy of @kib0rg
..bad evening... after trying to install app- it ends in reset, system no more started..
I've just uploaded a new v2 script to go with tomorrow's nightly. There are significant changes to the fstab that warranted this new version.
can i use this only in clean new installation? I have installed 0111 version.Can i use it with dirty flash of new nightly?
I don't know what i'm doing wrong. After flashing F2FS v2 phone stuck on black screen - no cm bootscreen appears..
Edit:
after flashing v1 phone normally booting. So there is problem with v2 or after (dirty) flashing new rom I use v2 instead of v1?
Phone stacked after flashing nightly.
As much testing hasn't be done on this; which we know the reason. being that if we are able to get a much more daily driver like ROM then more people will try testing f2fs. But for yesterday as I try to update my recovery, i found out that ace_f2fs_fstab_script_cm12_v2.zip has been uploaded. I downloaded flashed alongside 20150110's nightly. After flashing, phone get stacked just after boot screen appears.
@xdagee - what CM12 nightly do you use? I think last two has problem with dialer/phone. Do you use F2FS script v1?
For clarity, v1 should be used on night lies prior to 1/10, v2 should be used for 1/10 and beyond. 1/10 and beyond will also require the latest twrp update as well.
There was a major change to the fstab in mustaa's CM repos file that determines what partitions to mount that required everything be updated to match.
jrior001 said:
For clarity, v1 should be used on night lies prior to 1/10, v2 should be used for 1/10 and beyond. 1/10 and beyond will also require the latest twrp update as well.
There was a major change to the fstab in mustaa's CM repos file that determines what partitions to mount that required everything be updated to match.
Click to expand...
Click to collapse
problem is that v2 isn't working. I have same problem as Xdagee. Of course new twrp.
danvo01 said:
problem is that v2 isn't working. I have same problem as Xdagee. Of course new twrp.
Click to expand...
Click to collapse
Hmm...I tested before I uploaded but I'll check it out tonight.
Sorrys folks, there was a typo in one of the f2fs entries that was killing it, all fixed up now. I've uploaded a v2.1 zip that's corrected.
working fine, thanks
jrior001 said:
Sorrys folks, there was a typo in one of the f2fs entries that was killing it, all fixed up now. I've uploaded a v2.1 zip that's corrected.
Click to expand...
Click to collapse
thats okay, we've got your back
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its 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.
{
"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"
}
CHANGELOG for 3.0.2-0:
-Fix a bug with the input box that affected masked inputs (passwords). This fixes decrypt of full device encryption on devices that support decrypt. This bug also impacts encrypted backups. Users are highly encouraged to stop using 3.0.1 if you use encrypted backups or if you need decrypt of data in TWRP.
-Add Greek translation to some builds.
CHANGELOG for 3.0.1-0:
-support new CM 13.0 pattern encryption (sultanqasim)
-fix slow flashing issue due to modprobe (present on only some devices) (#twrp)
-libtar updated to latest upstream and fixes (jcadduono)
-fixes for loading custom themes (_that)
-TWRP will now detect and install TWRP themes automatically through the normal zip install process (Dees_Troy)
-translation updates - added Italian, Czech and Polish and significant updates to Dutch
-progress bar improvements - progress bar updates during image flashing and better tracks progress during file system backups (tar) (Dees_Troy)
-fix input box text display (Dees_Troy)
-reboot option after zip install complete (bigbiff)
-other mostly invisible bug fixes and improvements
CHANGELOG for 3.0.0-0:
-Completely new theme - Much more modern and much nicer looking (by z31s1g)
-True Terminal Emulator - Includes arrow keys, tab and tab completion, etc. (by _that)
-Language translation - It won’t be perfect and especially some languages that require large font files like Chinese & Japanese won’t be availble on most devices. Also some languages may only be partially translated at this time. Feel free to submit more translations to OmniROM’s Gerrit. (mostly by Dees_Troy)
-Flashing of sparse images - On select devices you will be able to flash some parts of factory images via the TWRP GUI (by HashBang173)
-Adopted storage support for select devices - TWRP can now decrypt adopted storage partitions from Marshmallow
-Reworked graphics to bring us more up to date with AOSP - includes support for adf and drm graphics (by Dees_Troy)
-SuperSU prompt will no longer display if a Marshmallow ROM is installed
-Update exfat, exfat fuse, dosfstools (by mdmower)
-Update AOSP base to 6.0
-A huge laundry list of other minor fixes and tweaks
WARNING: This is our first release in a long time. We have a lot of new and somewhat aggressive changes in this new release. The changes to the graphics back-end may cause some devices to not boot up properly or have other display-related issues. If you are not in a position to reflash an older build of TWRP, then wait until you are or at least wait until others have tried the new version for your specific device. You don’t want to end up with a non-working recovery and have to wait several hours or days to get to a computer to be able to fix it.
Notes for themers: In addition to the udpated theme, we have introduced a theme version variable to the TWRP theme system. If the theme version does not match the version that TWRP expects, TWRP will reject the custom theme and load its stock theme. This change will ensure that people who update TWRP without updating their theme will still have a workable recovery. We have removed libjpeg support. The stock theme was only using a jpeg image for the splash / curtain. This change means that any custom themes will no longer be able to use jpeg images. It also means that tools used to repack recovery images with a different curtain / splash will need to be updated to use the new method.
Version number notes: For a while we’ve been using a 4 digit version number and reserved the 4th digit for device-specific updates. For instance, we find and fix a device-specific issue like decryption of data on Nexus 5, we would release that as a 2.8.7.1. After a while, some people would start asking where 2.8.7.1 was for other devices. So, going forward we have decided to change the numbering scheme to 3.0.0-2, etc. Our hope is that this version numbering scheme will more clearly identify that the 4th digit does not indicate a version change for the code base.
We need your help! The bulk of TWRP work is done by 3 people on a volunteer basis. We have pushed most of our device files to our github and we have a gerrit instance. If you have the ability, please help us maintain our official devices and/or add your device to our official device list. Thanks in advance!
CHANGELOG for 2.8.7.0:
-Initial ground work for software drawn keyboard (_that)
-Fix handling of wiping internal storage on datamedia devices (xuefer)
-Allow DataManager to set and read values from the system properties (xuefer)
-Fix crash when taking screenshots on arm64 devices (xuefer)
-Fix error message after an ORS script completes (Dees_Troy)
-Fix crashes / error when creating encrypted backups (_that, Dees_Troy)
-Add system read only option – more details below (Dees_Troy)
-Add resize2fs and GUI option to run resize2fs (Dees_Troy)
-Fix crash loop caused by empty lines in AOSP recovery command file (_that)
-Prevent duplicate page overlays such as multiple lock screens (mdmower)
Note: As always, be sure your custom theme is up to date (or remove your custom theme) before updating TWRP.
System read only option: Devices that ship with 5.0 and higher as their initial OS are using block level OTA updates. With this style of OTA update, the update script checks to see if the system partition has ever been mounted read/write. Further, the script also usually runs an SHA sum of the entire system partition to detect if any changes have been made. If any changes have been made, the OTA update will refuse to install. Since not all OEMs and devices have factory images available, we have created a new feature in TWRP that detects if the system partition has ever been mounted read/write. If not, you will be prompted asking if you want TWRP to mount system as read/write. If you choose not to allow TWRP to mount as read/write, TWRP won’t prompt to install SuperSU and TWRP won’t try to patch the stock ROM to prevent TWRP from being replaced by stock recovery. The goal of this option is to hopefully allow the user to make a raw system image backup that they can use to get back to a state where they can take OTA updates again.
resize2fs feature: On some devices like the Nexus 6, the factory images include a userdata image that is the proper size only for the 32GB units. If you flash the factory image to a 64GB Nexus 6, the data partition will appear as if it only has the free space of a 32GB device. Using the resize2fs option, TWRP can resize your data partition to take up the full space available. The resize2fs may also be useful to resize system partitions on devices where custom ROM system images don’t take up the full partition space. Lastly, resize2fs may be useful in some cases to reserve the proper space at the end of a data partition for a full disk encryption key, should your partition be formatted incorrectly for some reason.
This new version also marks our first set of full builds using our new jenkins build server. You can track the progress of builds at https://jenkins.twrp.me and we have taken additional steps to make it easier for device maintainers to step up and submit patches to our gerrit server at https://gerrit.twrp.me to help us keep devices up to date and working.
DOWNLOADS
Most devices can be updated quickly and easily within TWRP if you already have version 2.8.4.0 or higher installed
1) Download the latest version from our website on your device
2) Reboot to TWRP
3) Hit Install and tap the "Images..." button in the lower right
4) Browse to the location of the TWRP image on your device and select it
5) Select recovery from the partition list and swipe to flash
OR:
You can find more information and download links on our website.
Xiaomi Redmi Note 3 MTK
TWRP Downloads
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link
XDA:DevDB Information
[OFFICIAL][TWRP][hennessy] TWRP for Redmi Note 3 - MTK, Tool/Utility for the Xiaomi Redmi Note 3
Contributors
HostZero, jcadduono, Dees_troy, MSF Jarvis
Source Code: https://github.com/TeamWin/android_device_xiaomi_hennessy/tree/android-5.1
Version Information
Status: Stable
Created 2016-06-10
Last Updated 2016-06-10
Reserved
Device Tree Changes
OFFICIAL 3.0.2-1 Changelogs:
Code:
1. Fix NVRAM mounting issues
2. Added Sub Partition Secro
3. Added Logo Partition
4. Fixed CPU Temp Issues
I just install this TWRP in RN3MTK .
And nice .
It work less lag when scrolling .
---------------------------------------
I just try to wipe data . somehow it say "Failed to mount '/nvram' (invalid argument)" .
i second this, i get the same failed to mount nvram error
flashing works but cannot backup/write all the partitions
Not displayed temperature CPU.
> CPU: 0°
kmzway000 said:
I just install this TWRP in RN3MTK .
And nice .
It work less lag when scrolling .
---------------------------------------
I just try to wipe data . somehow it say "Failed to mount '/nvram' (invalid argument)" .
Click to expand...
Click to collapse
Thank you NVRAM will be fixed in next major update.
pashkovwins said:
Not displayed temperature CPU.
> CPU: 0°
Click to expand...
Click to collapse
CPU Temperature Cannot be fixed because on MTK Devices we cannot find CPU Temp path.
zip edition ?
'Faile to mount /nvram' When are next major update?.. by any chance, Is there a problem with using TWRP??! and I'm always appreciative of you!!! Have a nice day~~
moaa123 said:
'Faile to mount /nvram' When are next major update?.. by any chance, Is there a problem with using TWRP??! and I'm always appreciative of you!!! Have a nice day~~
Click to expand...
Click to collapse
en.miui.com/thread-208503-1-1.html
this 3.0.0 image doesn't have the same nvram error problem
moaa123 said:
'Faile to mount /nvram' When are next major update?.. by any chance, Is there a problem with using TWRP??! and I'm always appreciative of you!!! Have a nice day~~
Click to expand...
Click to collapse
https://gerrit.twrp.me/#/c/1603/
Submitted patch.
Changelogs:
Fix NVRAM Mount
OEM and secro added.
laviniu_c said:
en.miui.com/thread-208503-1-1.html
this 3.0.0 image doesn't have the same nvram error problem
Click to expand...
Click to collapse
Wait for 3.0.3-0
https://github.com/TeamWin/android_device_xiaomi_hennessey/tree/android-5.1
HostZero said:
Wait for 3.0.3-0
https://github.com/TeamWin/android_device_xiaomi_hennessey/tree/android-5.1
Click to expand...
Click to collapse
thank you! may i share this with en.miui.com/thread-293773-1-1.html ? i think mr feds64 either has a similar fix already or is working on one to get the tutorial for the unlock/twrp working properly for hennessy
laviniu_c said:
thank you! may i share this with en.miui.com/thread-293773-1-1.html ? i think mr feds64 either has a similar fix already or is working on one to get the tutorial for the unlock/twrp working properly for hennessy
Click to expand...
Click to collapse
Its fine. I have fixed NVRAM Issues and got few other backup partitions to be added. So I have fixed it, Once you will get TWRP 3.0.3-0 it will be all fixed twrp.
3.03 doesn't seem to have been built and uploaded yet?
decayed.cell said:
3.03 doesn't seem to have been built and uploaded yet?
Click to expand...
Click to collapse
Yeah Because its major release.
I am upstream Sources to MIUI 8 (6.6.30)
Then I will request for 3.0.2-1
Hi guys I have official 3.0.2 and efs backup don't work, on last release it's possible backup and restore efs partition? Thanks
Inviato dal mio Redmi Note 3 utilizzando Tapatalk
the next release 3.0.3 fixes this, in the mean time, i think this is the one i have
edit: http://en.miui.com/forum.php?mod=viewthread&tid=208503
it sees all partitions and can back/restore them
It's possible flash an old 3.0.0 twrp form your link in recovery twrp 3.0.2 mode ?
Inviato dal mio Redmi Note 3 utilizzando Tapatalk
yep, that's how i did it too after i flashed 302 and lost the partitions
---------- Post added at 03:47 PM ---------- Previous post was at 03:47 PM ----------
p.s. always backup your data before any flash.
UPDATE: I am no longer maintaining TWRP for devices that I do not possess. I am also no longer posting on XDA.
Code:
*** Disclaimer ***
All flashing is done at your own risk!
While nothing from this thread should break your device,
don't come back here blaming anyone if it does!
Introduction
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its 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.
Click to expand...
Click to collapse
Images
Installation instructions
NOTE: Read the FAQ from Post #2 to ensure that you're installing the correct version of TWRP!!
Fastboot Install Method:
You will need the platform-tools from the Android SDK on your computer. Find the Android command line tools section on the page linked and install the SDK tools package. From the SDK Manager, download only the platform-tools to get adb and fastboot binaries.
Windows users will need proper drivers installed on their computer. You can try the Naked ADB drivers or the Universal ADB drivers if you don't already have a working driver installed
On your device, go into Settings -> About and find the Build Number and tap on it 7 times to enable developer settings. Press back and go into Developer Options and enable USB debugging. From your computer, open a command prompt and type:
Code:
adb reboot download
You should now be in fastboot mode.
Download the correct image file and copy the file into the same folder as your adb and fastboot binaries. Rename the image to twrp.img and type:
Code:
fastboot flash recovery twrp.img
Code:
fastboot reboot
Alternate Installation Method (requires prior TWRP installation):
TWRP Image Install method:
Most devices can be updated quickly and easily within TWRP if you already have version 2.8.4.0 or higher installed.
Download the latest version of TWRP appropriate for your device/firmware
Reboot to TWRP
Hit Install and tap the "Install Image" button in the lower right
Browse to the location of the TWRP image on your device and select it
Select recovery from the partition list and swipe to flash
Click to expand...
Click to collapse
Device Changelog
Current version: 3.2.1-0:
Code:
[LIST]Initial official release[/LIST]
Older Device-specific versions:
Code:
[LIST]N/A[/LIST]
Click to expand...
Click to collapse
TWRP Official Changelog
Current version: 3.2.1:
Code:
[LIST]minui fixes (cryptomilk)
[*]Better android-8.0 compatibility in ROM trees (Dees_Troy)
[*]Fix missing library in android-8.0 (nkk71)
[*]Fix inconsistent SDCard naming (DevUt)
[*]Default to TWRP restore instead of adb backup restore to fix restore on fresh TWRP boot (jlask)[/LIST]
Older versions:
Code:
[SIZE="4"][COLOR="Green"]3.2.0:[/COLOR][/SIZE]
[LIST]Allow restoring adb backups in the TWRP GUI (bigbiff)
[*]Fix gzip backup error in adb backups (bigbiff)
[*]Fix a bug in TWRP's backup routines that occasionally corrupted backup files (nkk71)
[*]Better support for installing Android 8.0 based zips due to legacy props (nkk71)
[*]Support vold decrypt with keymaster 3.0 in 8.0 firmwares (nkk71)
[*]Decrypt of synthetic passwords for Pixel 2 (Dees_Troy)
[*]Support newer ext4 FBE policies for backup and restore in libtar (Dees_Troy)
[*]v2 fstab support (Dees_Troy)
[*]Bring TWRP forward to android 8.0 AOSP base (Dees_Troy)
[*]Various other minor bugfixes and tweaks[/LIST]
[SIZE="4"][COLOR="Green"]3.1.1:[/COLOR][/SIZE]
[LIST]Backups will now include adopted storage keys (Dees_Troy)
[*]Fixed an adb restore issue (bigbiff)
[*]Fixed rebooting when no OS is present (Dees_Troy)
[*]Fixed line wrapping in the GUI terminal (_that)
[*]Updated TWRP source code to AOSP 7.1.2 (Dees_Troy)[/LIST]
[SIZE="4"][COLOR="Green"]3.1.0:[/COLOR][/SIZE]
[LIST]vold decrypt on a few select HTC devices, TWRP will now attempt to use the system partition's vold and vdc binaries and libraries to decrypt the data partition (nkk71 and CaptainThrowback)
[*]adb backup to stream a backup directly to or from your PC, see documentation [URL="https://github.com/omnirom/android_bootable_recovery/commit/ce8f83c48d200106ff61ad530c863b15c16949d9"]here[/URL] (bigbiff)
[*]tweak MTP startup routines (mdmower)
[*]support new Android 7.x xattrs for backup and restore to fix loss of data after a restore (Dees_Troy)
[*]support POSIX file capabilities backup and restore to fix VoLTE on HTC devices and possibly other issues (Dees_Troy)
[*]better indicate to users that internal storage is not backed up (Dees_Troy)
[*]improve automatic determination of TW_THEME (mdmower)
[*]minimal getcap and setcap support (_that)
[*]try mounting both ext4 and f2fs during decrypt (jcadduono and Dees_Troy)
[*]shut off backlight with power key (mdmower)
[*]timeout during FDE decrypt (Dees_Troy and nkk71)
[*]support for FBE decrypt and backing up and restoring FBE policies (Dees_Troy)
[*]boot slot support (Dees_Troy)
[*]TWRP app install prompt during reboot (Dees_Troy)
[*]support for AB OTA zips (Dees_Troy)
[*]support new Android 7.x log command (Dees_Troy)
[*]update recovery sources to AOSP 7.1 (Dees_Troy)
[*]numerous bugfixes and improvements by too many people to mention[/LIST]
[SIZE="4"][COLOR="Green"]3.0.3:[/COLOR][/SIZE]
[LIST]Partial release to help support the release of the [URL="https://www.xda-developers.com/team-win-releases-their-first-official-twrp-app-in-the-play-store/"]Official TWRP app[/URL][/LIST]
[SIZE="4"][COLOR="Green"]3.0.2:[/COLOR][/SIZE]
[LIST]Fix a bug with the input box that affected masked inputs (passwords). This fixes decrypt of full device encryption on devices that support decrypt. This bug also impacts encrypted backups. Users are highly encouraged to stop using 3.0.1 if you use encrypted backups or if you need decrypt of data in TWRP.
[*]Add Greek translation to some builds.[/LIST]
[SIZE="4"][COLOR="Green"]3.0.1:[/COLOR][/SIZE]
[LIST]support new CM 13.0 pattern encryption (sultanqasim)
[*]fix slow flashing issue due to modprobe (present on only some devices) (#twrp)
[*]libtar updated to latest upstream and fixes (jcadduono)
[*]fixes for loading custom themes (_that)
[*]TWRP will now detect and install TWRP themes automatically through the normal zip install process (Dees_Troy)
[*]translation updates - added Italian, Czech and Polish and significant updates to Dutch
[*]progress bar improvements - progress bar updates during image flashing and better tracks progress during file system backups (tar) (Dees_Troy)
[*]fix input box text display (Dees_Troy)
[*]reboot option after zip install complete (bigbiff)
[*]other mostly invisible bug fixes and improvements[/LIST]
[SIZE="4"][COLOR="Green"]3.0.0:[/COLOR][/SIZE]
[LIST]Completely new theme - Much more modern and much nicer looking (by z31s1g)
[*]True Terminal Emulator - Includes arrow keys, tab and tab completion, etc. (by _that)
[*]Language translation - It won’t be perfect and especially some languages that require large font files like Chinese & Japanese won’t be availble on most devices. Also some languages may only be partially translated at this time. Feel free to submit more translations to OmniROM’s Gerrit. (mostly by Dees_Troy)
[*]Flashing of sparse images - On select devices you will be able to flash some parts of factory images via the TWRP GUI (by HashBang173)
[*]Adopted storage support for select devices - TWRP can now decrypt adopted storage partitions from Marshmallow
[*]Reworked graphics to bring us more up to date with AOSP - includes support for adf and drm graphics (by Dees_Troy)
[*]SuperSU prompt will no longer display if a Marshmallow ROM is installed
[*]Update exfat, exfat fuse, dosfstools (by mdmower)
[*]Update AOSP base to 6.0
[*]A huge laundry list of other minor fixes and tweaks[/LIST]
[U]Additional Notes[/U]
[LIST]WARNING: This is our first release in a long time. We have a lot of new and somewhat aggressive changes in this new release. The changes to the graphics back-end may cause some devices to not boot up properly or have other display-related issues. If you are not in a position to reflash an older build of TWRP, then wait until you are or at least wait until others have tried the new version for your specific device. You don’t want to end up with a non-working recovery and have to wait several hours or days to get to a computer to be able to fix it.
[*]Notes for themers: In addition to the updated theme, we have introduced a theme version variable to the TWRP theme system. If the theme version does not match the version that TWRP expects, TWRP will reject the custom theme and load its stock theme. This change will ensure that people who update TWRP without updating their theme will still have a workable recovery. We have removed libjpeg support. The stock theme was only using a jpeg image for the splash / curtain. This change means that any custom themes will no longer be able to use jpeg images. It also means that tools used to repack recovery images with a different curtain / splash will need to be updated to use the new method.
[*]Version number notes: For a while we’ve been using a 4 digit version number and reserved the 4th digit for device-specific updates. For instance, we find and fix a device-specific issue like decryption of data on Nexus 5, we would release that as a 2.8.7.1. After a while, some people would start asking where 2.8.7.1 was for other devices. So, going forward we have decided to change the numbering scheme to 3.0.0-2, etc. Our hope is that this version numbering scheme will more clearly identify that the 4th digit does not indicate a version change for the code base.
[*]We need your help! The bulk of TWRP work is done by 3 people on a volunteer basis. We have pushed most of our device files to our github and we have a gerrit instance. If you have the ability, please help us maintain our official devices and/or add your device to our official device list. Thanks in advance![/LIST]
[SIZE="4"][COLOR="Green"]2.8.7.0:[/COLOR][/SIZE]
[LIST]Initial ground work for software drawn keyboard (_that)
[*]Fix handling of wiping internal storage on datamedia devices (xuefer)
[*]Allow DataManager to set and read values from the system properties (xuefer)
[*]Fix crash when taking screenshots on arm64 devices (xuefer)
[*]Fix error message after an ORS script completes (Dees_Troy)
[*]Fix crashes / error when creating encrypted backups (_that, Dees_Troy)
[*]Add system read only option – more details below (Dees_Troy)
[*]Add resize2fs and GUI option to run resize2fs (Dees_Troy)
[*]Fix crash loop caused by empty lines in AOSP recovery command file (_that)
[*]Prevent duplicate page overlays such as multiple lock screens (mdmower)[/LIST]
[U]Additional Notes[/U]
[LIST]Note: As always, be sure your custom theme is up to date (or remove your custom theme) before updating TWRP.
[*]System read only option: Devices that ship with 5.0 and higher as their initial OS are using block level OTA updates. With this style of OTA update, the update script checks to see if the system partition has ever been mounted read/write. Further, the script also usually runs an SHA sum of the entire system partition to detect if any changes have been made. If any changes have been made, the OTA update will refuse to install. Since not all OEMs and devices have factory images available, we have created a new feature in TWRP that detects if the system partition has ever been mounted read/write. If not, you will be prompted asking if you want TWRP to mount system as read/write. If you choose not to allow TWRP to mount as read/write, TWRP won’t prompt to install SuperSU and TWRP won’t try to patch the stock ROM to prevent TWRP from being replaced by stock recovery. The goal of this option is to hopefully allow the user to make a raw system image backup that they can use to get back to a state where they can take OTA updates again.
[*]resize2fs feature: On some devices like the Nexus 6, the factory images include a userdata image that is the proper size only for the 32GB units. If you flash the factory image to a 64GB Nexus 6, the data partition will appear as if it only has the free space of a 32GB device. Using the resize2fs option, TWRP can resize your data partition to take up the full space available. The resize2fs may also be useful to resize system partitions on devices where custom ROM system images don’t take up the full partition space. Lastly, resize2fs may be useful in some cases to reserve the proper space at the end of a data partition for a full disk encryption key, should your partition be formatted incorrectly for some reason.
[*]This new version also marks our first set of full builds using our new jenkins build server. You can track the progress of builds at [url]https://jenkins.twrp.me[/url] and we have taken additional steps to make it easier for device maintainers to step up and submit patches to our gerrit server at [url]https://gerrit.twrp.me[/url] to help us keep devices up to date and working.[/LIST]
Click to expand...
Click to collapse
Downloads
NOTE: Read the FAQ from Post #2 to ensure that you're installing the correct version of TWRP!!
Download
Latest Official versions
Sources
Device tree
Click to expand...
Click to collapse
FAQ - Post #2
Known Issues
Reboot recovery option doesn't work - device will only reboot to system (needs custom-built kernel to fix)
Click to expand...
Click to collapse
Bug Reporting
If you have an issue, the first step is to post a recovery log so we can determine the cause of the issue. This is done in recovery using Advanced -> Copy Log, or adb pull /tmp/recovery.log. Once a log is uploaded we can determine how best to proceed. NOTE: Posts that are reporting bugs or issues without an accompanying recovery log will be ignored! Additionally, providing details about your device setup, including variant, firmware version, and exact steps to reproduce your issue will also be helpful in diagnosing the problem.
{
"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"
}
If your issue is determined to be a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
Click to expand...
Click to collapse
Additional Help/Support:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
Click to expand...
Click to collapse
XDA:DevDB Information
Team Win Recovery Project (TWRP), Tool/Utility for the HTC Bolt
Contributors
Captain_Throwback, OMJ, nkk71, Dees_Troy, bigbiff, _that
Source Code: https://github.com/omnirom/android_bootable_recovery
Version Information
Status: Stable
Current Stable Version: 3.2.1-0
Stable Release Date: 2017-12-09
Created 2016-12-14
Last Updated 2018-03-07
Frequently Asked Questions (FAQ)
1. Why is this device different than my previous HTC device?
With Marshmallow devices, HTC has moved to a block-based OTA system. This means that even mounting system as read-write (as TWRP typically does during startup checks) will nullify the device's ability to take an OTA. Any other changes to the system partition will also cause an OTA to fail (even if that check is removed from the OTA zip) due to "unexpected contents." Additionally, see this thread.
2. Which version of TWRP am I supposed to use?
The best version to use is 3.2.3-0, the latest official version from twrp.me.
3. Why is there a "System" backup option and a "System Image" backup option now?
The "System" option is the standard tar backup. "System Image" is a dd backup of the entire system block device (/dev/block/bootdevice/by-name/system). The "System Image" option is only relevant if your system is unmodified. This allows you to make a fully stock backup that can be restored later to take an OTA.
NOTE: You only need to choose ONE of these options when making a backup!!
[*]NOTE 2: If you are using a FAT32-formatted card, a "System Image" backup may fail (depending on your variant), due to the 4GB file limit on that format. For a successful System Image backup, internal storage or NTFS/exFAT-formatted external storage must be used (either SD card or USB-OTG)
4. How do I backup stock recovery prior to flashing TWRP?
You can't. The "fastboot boot" command appears to be disabled in ABOOT, so TWRP must be fastboot flashed over stock recovery. You can however, extract the stock recovery.img from the OTA firmware.zip when it's received and use that to install the OTA.
An alternate method to obtain a stock recovery is listed below, but it requires 2 devices (either owned by you, or help from someone else in the forum):
Someone fastboot flash twrp and immediately make a backup of boot and upload it to XDA.
Once the above is available, someone else download that boot.img to their device, and fastboot flash twrp to the BOOT partition of their device.
Once the above is done, reboot the device, which will bring up TWRP, and then backup stock RECOVERY in TWRP, and upload to XDA.
Then, from within TWRP, use the Image install feature in TWRP to flash the stock boot.img.
5. How do I restore stock system so that I can accept an OTA?
Check the "Mount system as read-only" box in the Mount menu.
Restore stock "System Image" backup (This will only work if you've made a System Image backup prior to making any modifications to /system).
Fastboot flash stock recovery (fastboot flash recovery recovery_signed.img)
NOTE: It is also possible to restore stock recovery via the TWRP GUI. Rename the stock recovery file to "recovery.emmc.win" and place in the backup folder with the stock system image. Recovery will then show as a restore option. MAKE SURE YOU REALLY WANT TO DO THIS, AS TWRP WILL BE GONE WHEN YOU REBOOT OUT OF RECOVERY!!
[*]NOTE 2: It is possible to install an OTA without using stock recovery (i.e. installing it with TWRP). TWRP will not flash the firmware.zip included in an OTA file. Please see here for a detailed description of the process.
Reboot to system, install OTA.
6. What if I have an RUU? Do I need to worry about all this OTA nonsense?
Not if you don't care about losing all your data. If you're S-ON and have an RUU available for your exact variant (model ID and CID must match) and software number (main version must be the same or newer), then you can get back to a fully stock state by relocking (fastboot oem lock) and flashing an RUU. However, if you'd prefer to take an OTA to keep your data intact, the method stated above is how to do so. Or, you can just run a custom ROM and wait for your ROM chef to update their ROM to the latest software (though you'll still have to find a way to update your firmware if you're not S-OFF)
7. After I go through all this and successfully apply an OTA, how do I make sure I have a clean starting point again?
After the OTA is applied and TWRP is flashed, it will once again detect an untouched system, which will mount system read-only and allow you to make a fully stock backup and start the process over again, this time with the new base.
8. After I restored my Data backup and boot back to Android, I'm entering the correct PIN/password, but it's telling me the password is wrong. What happened, and how do I fix it?
It appears that sometimes after restoring a backup of Data where security was enabled (such as a PIN or password lock), the device does not recognize the correct password. There are two ways to avoid this issue:
Disable security in Android before making a backup of data.
After restoring Data, while still in TWRP, use the TWRP File Manager to navigate to /data/system and delete all the locksettings.* files (such as locksettings.db, etc). When you reboot, the password will be gone.
u da man @Captain_Throwback!
Alright, against my better judgement I decided to post this thread. Based on @OMJ's testing, TWRP is working properly with decryption. The only remaining bug I'm aware of is that the "Reboot Recovery" option doesn't work, because of how I hacked the kernel to enable touch. I'm working on an alternative method to get around that, but since I can't test on the device, not sure how that will go.
Make a note of what it says in the OP under "BUGS" because if you report one without a log, it will be ignored! I hope everyone with this device enjoys this "unofficial" version of TWRP.
Captain_Throwback said:
Alright, against my better judgement I decided to post this thread. Based on @OMJ's testing, TWRP is working properly with decryption. The only remaining bug I'm aware of is that the "Reboot Recovery" option doesn't work, because of how I hacked the kernel to enable touch. I'm working on an alternative method to get around that, but since I can't test on the device, not sure how that will go.
Make a note of what it says in the OP under "BUGS" because if you report one without a log, it will be ignored! I hope everyone with this device enjoys this "unofficial" version of TWRP.
Click to expand...
Click to collapse
you are the man for sure, i still like the idea of a unencrypted device and glad its a option but im more happy knowing that twrp is now able to support both options!
Thanks bro, know you have been working hard for people who dont necessarily effect you. thanks man!
Had to update TWRP as I forgot that gunzip isn't working on builds from the 7.1 tree. Using a pre-compiled busybox binary in TWRP as a workaround. 3.0.2-2 now available on Downloads tab with this fix included.
Uploaded new version to Downloads Tab. Just some code cleanup mostly and a version bump that coincides to the release of the Official TWRP app.
Can someone test whether this TWRP build boots?
«link removed»
That's from the official TWRP Jenkins. It won't decrypt currently, but I really just want to confirm it boots. Thanks!
EDIT: @OMJ confirmed. Official support should *hopefully* be coming soon!
Captain_Throwback said:
Can someone test whether this TWRP build boots?
http://build.twrp.me/twrp/twrp-3.0.3-0-aca.img
That's from the official TWRP Jenkins. It won't decrypt currently, but I really just want to confirm it boots. Thanks!
Click to expand...
Click to collapse
yes, it boots, and as u said, doesn't decrypt
Can someone please confirm whether this TWRP boots/works/functions properly? Thanks!
https://forum.xda-developers.com/devdb/project/dl/?id=23498
EDIT: @OMJ tested that one and it didn't boot. Updated the link to a new version. I need a log from a ROM flash where the ROM zip includes a root zip to confirm it's getting extracted correctly.
3.1.0 Official is out.
Captain_Throwback said:
Alright, against my better judgement I decided to post this thread. Based on @OMJ's testing, TWRP is working properly with decryption. The only remaining bug I'm aware of is that the "Reboot Recovery" option doesn't work, because of how I hacked the kernel to enable touch. I'm working on an alternative method to get around that, but since I can't test on the device, not sure how that will go.
Make a note of what it says in the OP under "BUGS" because if you report one without a log, it will be ignored! I hope everyone with this device enjoys this "unofficial" version of TWRP.
Click to expand...
Click to collapse
Sir, you mentioned that you hacked the kernel to enable touch in recovery can you share how to did that and did you modify the kernel source code or hacked the kernel without the source code as even other htc devices are having this issue and I can see commit in source codes that'll enable touch in recovery but what if there is no kernel source any hack for that? Thanks in advance.
M.A.P said:
Sir, you mentioned that you hacked the kernel to enable touch in recovery can you share how to did that and did you modify the kernel source code or hacked the kernel without the source code as even other htc devices are having this issue and I can see commit in source codes that'll enable touch in recovery but what if there is no kernel source any hack for that? Thanks in advance.
Click to expand...
Click to collapse
https://forum.xda-developers.com/de...esire-530-guide-to-root-t3410015/post70697756
Similar procedure to that, only difference is that you don't have to deal with vmlinux since the kernel binary is simply gzip compressed.
And if dtb is combined, you'll need to extract it from the original kernel and re-append it to the modified binary.
Captain_Throwback said:
https://forum.xda-developers.com/de...esire-530-guide-to-root-t3410015/post70697756
Similar procedure to that, only difference is that you don't have to deal with vmlinux since the kernel binary is simply gzip compressed.
And if dtb is combined, you'll need to extract it from the original kernel and re-append it to the modified binary.
Click to expand...
Click to collapse
Thank you sir will check that out but why is htc doing this? I mean even some devices running 4.2.2 are having touch disabled and mine is 620g and is disabled too.
M.A.P said:
Thank you sir will check that out but why is htc doing this? I mean even some devices running 4.2.2 are having touch disabled and mine is 620g and is disabled too.
Click to expand...
Click to collapse
Well, touch isn't needed in stock recovery, so it's really just a way to save power while booted into that mode. Only custom recoveries like TWRP require working touch, so that's why we have to hack the kernel if source isn't available.
Captain_Throwback said:
Well, touch isn't needed in stock recovery, so it's really just a way to save power while booted into that mode. Only custom recoveries like TWRP require working touch, so that's why we have to hack the kernel if source isn't available.
Click to expand...
Click to collapse
Oh. but still it is difficult for devices with no kernel source. Will try the hack sir it's night yesterday.
---------- Post added at 09:50 AM ---------- Previous post was at 09:33 AM ----------
Captain_Throwback said:
https://forum.xda-developers.com/de...esire-530-guide-to-root-t3410015/post70697756
Similar procedure to that, only difference is that you don't have to deal with vmlinux since the kernel binary is simply gzip compressed.
And if dtb is combined, you'll need to extract it from the original kernel and re-append it to the modified binary.
Click to expand...
Click to collapse
Sir, can you explain it a bit more as I'm newbie in kernel stuff. I'm having boot.img for my phone and the kernel inside it can you help me how to hack the kernel sir? Thanks in advance
M.A.P said:
Oh. but still it is difficult for devices with no kernel source. Will try the hack sir it's night yesterday.
---------- Post added at 09:50 AM ---------- Previous post was at 09:33 AM ----------
Sir, can you explain it a bit more as I'm newbie in kernel stuff. I'm having boot.img for my phone and the kernel inside it can you help me how to hack the kernel sir? Thanks in advance
Click to expand...
Click to collapse
Your question doesn't belong in this thread. It belongs in Q&A.
TWRP 3.2.0-0
Download
Changelog
i flashed the latest twrp in download and said succes but cant get into it just htc and red letters did i miss somthing
Is the device tree mentioned in the post sufficient to build a lineage based rom ?