Develop Bugs

[DEV] Kernel 2.6.27-community (Version 1.4 - 03/11/09)

Disclaimer: For devs only. Updating to it will wipe your device. I am not responsible of any damage of any sort or data loss or anything. Alway do a nandroid backup before updating
Kernel android-msm-2.6.27-hero-community
The purpose of that community project is to have an optimized hero kernel based on HTC kernel sources.
Current release: 1.4 [download]
Features:
- compcache with ramzswap enabled
- /system/etc/init.d init scripts support
- some init script (firstboot, userinit)
- CIFS support
- Ext4 full support
- Removed DEBUG options
- All bluetooth options (don't know if needed ??)
- Droidwall support
- Pptp support (need testing)
- IP Gre tunnel module
- SquashFS 3.4
Links:
Git
Wiki
Issues tracker
Note: devs, as a community project, you patches or configuration corrections are welcomed. Feel free to submit.
Note: if anyone needs it, in the downloads section of the git there is the patch to apply to android-msm-2.6.27 sources so they compile for Hero.
Note: this kernel does not support modaco roms, the reason is that modaco rom is dependant of scripts called from kernel ramdisk, witch is not good. If you use Modaco rom, use teknologist kernel (http://ow.ly/yCxu) witch have similar tweaks

Changelog
Version 1.4 - Nov 3rd 2009
- added ext4 full support
- some init.d scripts (firstboot, userinit)
- squashfs 3.4
Version 1.3 - Nov 3rd 2009 (test build)
Version 1.2 - Nov 3rd 2009
- added ext4dev support (ext4 support in git, update.zip coming soon)
- added pptp support
- removed kernel debuging options
- added ramzswap init.d script
Version 1.1 - Oct 29th 2009
- added support for /data/init.sh script
- added support for /system/etc/init.d/* scripts
Version 1.0.1 - Oct 29th 2009
- fixed wlan.ko
Version 1.0 - Oct 28th 2009
- compcache 0.5.4 patch
- optimized config by Teknologist

Thanks for the hard work and more importantly sharing!..... this will be very useful once Ive got my oven sorted

Lox could you also post the version number of compcache that is integrated ? (and version numbers for future addons) cant wait to test the next release
Edit: Do i need to wipe the data before i update to this kernel? because i cant turn on wifi

whats the diff between AOSF CUPCAKE thread and this? these two projects do diff jobs? which will give us a basic android rom withot sense thing?

dying4004 said:
whats the diff between AOSF CUPCAKE thread and this? these two projects do diff jobs? which will give us a basic android rom withot sense thing?
Click to expand...
Click to collapse
This is the an optimized kernel to run any rom.

Lox_Dev said:
This is the an optimized kernel to run any rom.
Click to expand...
Click to collapse
WHOA!!!
LOX u have got really close in getting those nice roms and fancy stuffs in hero. so this is the base of all roms and fancy things.
CONGRATS BRO

New version 1.1.
Now you can have init scripts in /system/etc/init.d. /data/init.sh supported too.
To run Compache and have a really faster kernel, follow this how to. Busybox is needed (here is an update.zip to install it)

Lox_Dev said:
New version 1.1.
Now you can have init scripts in /system/etc/init.d. /data/init.sh supported too.
To run Compache and have a really faster kernel, follow this how to. Busybox is needed (here is an update.zip to install it)
Click to expand...
Click to collapse
could you also add little adb how-to for adding @ moving 05ramzswap file to init.d ?

i read all the references printed in first post, but there is nowhere a description of what has been optimized.. can someone please inform ;-)

felikz said:
i read all the references printed in first post, but there is nowhere a description of what has been optimized.. can someone please inform ;-)
Click to expand...
Click to collapse
second post maybe?

jaapschaap said:
second post maybe?
Click to expand...
Click to collapse
thats just the CHANGE LOG?

@ Lox_Dev
Thanks
This 05ramzswap script is correct?
#!/system/bin/sh
insmod /system/lib/modules/lzo_decompress.ko
insmod /system/lib/modules/lzo_compress.ko
insmod /system/lib/modules/compcache/xvmalloc.ko
/system/xbin/insmod /system/lib/modules/compcache/ramzswap.ko memlimit_kb=64200 backing_swap=/dev/block/mmcblk0p3
swapon /dev/block/ramzswap0
fi;
For building the rom, is correct added this line in update-script?
show_progress 0.5 0
show_progress 0.2 0
write_raw_image PACKAGE:boot.img BOOT:
show_progress 0.2 10
Thank you and sorry my english.

MACH_SAPPHIRE=y
Click to expand...
Click to collapse
Does this option is really necessary ?

thx lox, thread sticky

I managed to use nandroid's restoring method and put new boot.img back without any data wipe. Here is how I did it: Make a nandroid backup first, and copy the latest backup files to your computer, replace original boot.img to the new one(community version). Then edit the value of boot.img in nandroid.md5 to the proper content and match your new boot.img. Finally just restore it in recovery mode.
If the wireless function isn't working after boot, you may also need to push it via adb:
adb push wlan.ko /system/lib/modules/wlan.ko
adb shell sync
(reboot again)

foxfair said:
I managed to use nandroid's restoring method and put new boot.img back without any data wipe. Here is how I did it: Make a nandroid backup first, and copy the latest backup files to your computer, replace original boot.img to the new one(community version). Then edit the value of boot.img in nandroid.md5 to the proper content and match your new boot.img. Finally just restore it in recovery mode.
Click to expand...
Click to collapse
# adb push ./boot.img /sdcard
# adb shell flash_image boot /sdcard/boot.img
I little bit more fast... (but you should make a backup before)

Poischack said:
# adb push ./boot.img /sdcard
# adb shell flash_image boot /sdcard/boot.img
I little bit more fast... (but you should make a backup before)
Click to expand...
Click to collapse
i'm on RUU 2.73.x version, for some reason fastboot and adb push won't work... anyway I just provide an alternative way.

Lox did you try to upgrade to 2.6.29?

foxfair said:
Lox did you try to upgrade to 2.6.29?
Click to expand...
Click to collapse
Clone this git if you want to play:
git://android.git.kernel.org/kernel/msm.git branch android-msm-2.6.29
You WILL need to port over some of the drivers from the Hero kernel HTC released a while back (which was 2.6.27 btw).

[15MAR][BOOTLOADER]+[RECOVERY] cLK v1.3.3

cedesmith's (L)ittle (K)ernel bootloader v1.3.3
Disclaimer
This comes with no warranties, if you use it you do it on your own risk.
Please read carefully the flowing information and make sure you know what you are doing.
I don't have time or patience for questions and support. If you use it you are on your own (well and this community).
Recovery
- CWM 3.0.1.4
Q&A
Q: What it is ?
A: A bootloader for android like magldr.
Q: Is it better then magldr ?
A1: NO, it is missing tetris .
A2: NO, magldr has some nice features like partitioning and rmnet.
Q: Can i use last 24MB of nand with this?
A: NO, SPL will erase them. When i have some time i may try to fix it.
Q: Does battery charge with this ?
A: YES, from version 1.3
Q: Does it boot WP7?
A: NO. I am only interested in android but in can load and execute any program.
Q: Should i install it ?
A: If you had to ask probably not. If has no functional benefits over magldr.
How To
Flash cLK
- make sure you have hspl
- enter SPL by holding VOL DOWN key while powering/resting the phone.
- flash with customruu like you would a windows rom and/or magldr
Flash a ROM
- download android sdk, you will need drivers and fastboot command from there
- fastboot flash recovery recovery.img
- after recovery you can reboot and use CWM or you can flash with fastboot (fastboot flash boot boot.img, fastboot flash system system.img, fastboot flash userdata userdata.img)
Start recovery / fastboot / text console
- holding down any key ( except power ) will show text console
- home key will enter recovery ( if flashed )
- back key will enter fastboot mode
Known issues
RMNET does not work.
Downloads
NBH
- RUU 1.3.3
- 1.3.3 and 1.4 are are exactly the same function wise, only tools used to build them is different (1.4 includes nbgen written by me to replace osnbtool and nbmerge)
- recovery.img
ROM
- see post #3
Source code
git link
compile on a linux machine with wine and codesourcery toolchain in path by executing "sh compile" in root of source
Credits
- codeaurrora for making LK and for making it open
- Martin Johnson for his tinboot witch was a great inspiration
- Martijn Stolk for his kernel segfault solving code and and cotulla for pointing it and his contribution to android on HD2
- all how worked on making linux kernel possible on hd2

kernel and recovery patches
17.03.2011
- small fix on get_boot_reason
- cwm off charge fully implemented, inspired by dan1j3l's code (http://gitorious.org/htc-hd2-android-libraries/cmon/blobs/master/cmon.c)
15.03.2011
- kernel patch to save reboot reason so is available on bootloader
- old patched in zip as pushed in most branches
25.02.2011
- CWM patch for charging, unpached CWM code is not properly reading kernel cmdline because /proc/cmdline file size is always 0 resulting in a always empty cmd line. I also changed the code to wait for key press then reboot phone to normal android.
20.02.2011
- cLK_power_clllapse patch adds detection of cLK to kernel and puts the reset vector at 0x11800000 where cLK will jump (+4) at power_collapse_exit
- off_mode_charging just prevents the kernel from BUG() if off mode charging and panel is off ( and not detectable )
- both of this patches are compatibile with current SD and magldr builds, please push them to your git trees

ROMS
HyperDroid-CM7 by pongster
cLK for Dummies by stirkac
Froyo Sense revolution 2.5 by arif-ali
CWM 3.0.1.4 with yes/no menu by seadersn
UD 3.1 by crawlingcity
Revolution HD v2.6 & SL v1.4 by arif-ali
TyphoonN 2.6.3 CM7 for cLK
- download cLK
- download recovery
- if you don't have it download fastboot,adb and drivers from here
- download TyphooN 2.6.3 Standard Edition rom from original thread
- download typhoon kernel(tytung_r7) and initrd for clk update
- put rom zip and clk update zip on sdcard
- unzip clk and recovery
- flash clk ruu
- fastboot flash recovery recovery.3.0.1.4_clk_1.3.3.img
- fastboot reboot
- hold HOME key down to boot recovery
- wipe data/factory reset (if not updating from my previous version)
- install zip from sdcard -> choose zip from sdcard -> TyphooN_CM7_v2.6.3.zip
- install zip from sdcard -> choose zip from sdcard -> typhoon2.6.3_tyung_r7_clk_update.zip
- wipe chache
Other?
- drop me a PM to include it on this post

clk changelog
1.4
nbgen for making .nb file
1.3.3
small fix on get_boot_reason
cwm off charge fully implemented, inspired by dan1j3l's code (http://gitorious.org/htc-hd2-android-libraries/cmon/blobs/master/cmon.c)
1.3.2
ROMHDR base addr is spl virtual 0x80000000 = 11800000 physical, LK will relocate to correct address (MEMBASE)
save reboot reason at 0x2FFB0000 (ramconsole - 0x1000 (PAGE_SIZE)) and @0x2FFB0004 XOR 0x004b4c63 (cLK signature)
added oem cmd to fastboot and oemcmd.bat for PC. supported commands are:
dmesg - kernel debug messages
smesg - spl messages
pwf addr len - dump memory
set[c,w,s] addr value - set char(1byte), word(4 byes), or string

Oh, I can't wait to try it.

Felicitari !!
Congratulation well done!
Regards,
Me

good stuff il second trying that

How do you flash those roms on that one ?
Sent from my HTC bravo using XDA App

can this be used as replacement for magldr?
if yes.. can i finally charge my battery while turned off?

Nice!!!!!!! downloading..............

good job
cant wait to try it

interesting
this is interesting, specially it is from cedesmith, seriously this man work is amazing, i was waiting for him to release his Desire HD2 as a nand build, but he surprised us with this, keep the good work man
cheers

hellfire666 said:
Nice!!!!!!! downloading..............
Click to expand...
Click to collapse
L0L downloading what
he just posted only the video
anyway nice to hear another bootloader for our Leos

faster bootloader? for replace magldr 1.11??

no offense, but I see "senior members" complaning on how people don't use search in these forums before posting the question, but let's look at this thread...
1. There is absolutely no info on why this software was written and what problems it's solving? I am sorry but most people are not mind readers.
2. Software gets "shown off" and bunch of "senior members" post replies of "thanks...." instead of using "Thanks" button. These posts are not adding any value.

hellfire666 said:
Nice!!!!!!! downloading..............
Click to expand...
Click to collapse
Errr no your not! There is no download yet wingnut!
-------------------------------------
I'm all for the HD2 dev growing and its second wind but what does this really do that magldr doesnt, Is there any advantages of using this rather then magldr because as far as I can tell it does the same (boot from nand) but without the extra functionality that we have option for on magldr?
So what would be (if any) the advantage of using this rather then magldr?
That isnt a dig or anything im just curious.

hi guys,
sorry for that question but, where is the benefit in this loader?
CLK vs. magldr???

thanks for what what does this do no info no download link nothing come come on lol this is useless

stony007_de said:
hi guys,
sorry for that question but, where is the benefit in this loader?
CLK vs. magldr???
Click to expand...
Click to collapse
is nor an replacement for magldr is an updated cmr, or an bootloader + cmr inside .i think that after watching video

cedesmith said:
Proud to present cedesmith's (L)ittle (K) v1.1
video
release and source code soon
Click to expand...
Click to collapse
OMG are you serious?
What about 24mb erasing HSPL issue?

[Jan 12][DL DesireZ v2.2][NAND][PPP/RMNET][Base 1.72.466.4][SquashFS][UTF8&Arabic]

[Jan 12][DL DesireZ v2.2][NAND][PPP/RMNET][Base 1.72.466.4][SquashFS][UTF8&Arabic]
CAN SOMEONE PLEASE CLOSE or DELETE THIS THREAD. Dandiest has started his own thread here on the NAND forum and this is no longer needed.
TO ALL: I am reposting a NAND build from the SD forums for Dandiest. His work is fantastic and this is the most stable build I have used to date at least for me and my TMOUS HD2.
Orignal thread: http://forum.xda-developers.com/showthread.php?t=881937
Dandiest does not want to maintain 2 threads but I will be updating this one as he updates his so that the same content is there. If you want to pose a question to Dandiest you will need to do it in the original forum.
Just try it, you will know.
News
12/01/2011
- Bug fix for both SD and Nand build(reloaded). update.bugfix.1201201101.7z
for SD build, only need to extract the folder in desire_z to overwrite your current desire_z folder.
for Nand build, extract the folder of .data and DLZUPDATE to the root of your SD card, you can edit the config.txt in .data to change the gps_zone. and can put your original data.img into .data.
Code:
[COLOR="Red"]
11/01/2011
Made a lot of changes, refer to the change-log below, but the upload stuck at 50% last night when upload to multiupload in order not to split the package, sigh.
Reupload today.
10/01/2011
Made some changes based on the feedback of the Nand version, am reuploading it now.
For SD build users, can not find a way to mount the yaffs2 image and no unyaffs can be found on android, thus, I have to convert it to ext2 version, who has a linux box and fast bandwidth, please contact me, thus, I only need to upload the nand version, you help me convert it to ext2 and upload. :D
[/COLOR]
09/01/2011
Nand V2.0 Testing version released, and SD will make use of the same system.img:
1. this is the test version only , but I have used it for > 1day, and quite proud of it. :D
2. I have built in with the "upgrade" facility, thus, willl provide the update for some enhancement soon, together with SD build.
3. I have enabled the Data2SD(need test, as it is most easy to do :D, thanks for Takaaki), can refer to other build for how to use it, but I have extended the .config to be able to choose from Data2 SD or data2ext4 which will be enabled soon, suggest you partition SDCard before implementing the Data2Ext4.
4. If you encountered any FC or Market problem or Any other problem, can use the same approach as SD version, do the fix permission in the Rom Manager.
5. the previous update for reverting back to stock version is still applicable to the Nand build, put the update in the folder of "DLZUPDATE" at the root of your SDCard.
6. have re-squashed the build, put some apps(Music, etc) aside in the system/app directly in order for you to replace it. others, still keep the symbol link to Squashed file, that enable you to delete the link and put your own app.
7. several not so common apps and skin have been removed, will provide it late to the data partition.
- made 2 builds, same system base, one for SD, the other for Nand. I will try to maintain 2 builds in sync going forward.
- for the system base, i made a lot of changes, some problems should be solved, but need more tests.
- for nand version, i squashed as many files as possible but keep the some level of the flexibility of customization, e.g, for app, i changed the symbol link from directory to filles, thus, you can easily overwrite a symbol link with your own app, for framework , same approach, you can also change anything you like.
- after squashed, the system is about 200mb, next i will incorporate into the data2ext4, to improve the I/O and of course, enlarge the data space.
- Provide 1G data.img. [ATTACH]476315[/ATTACH] to replace your existing one.
- If you still experience the FC. try (thanks nito2721)
Open the "Terminal" app from the application drawer. Type:
su
fix_permissions
- FOR TMOBILE users please check [URL]http://forum.xda-developers.com/showpost.php?p=10186545&postcount=708[/URL] thanks to TheGeorgiaSwagger
Changlog
Code:
[B]v2.2[/B]
- fix the boot problem and revert the kernel back to 8.6 for SD build.
- fix the data2sd, and add the data2ext4(need test).
[B]v2.1[/B]
- fixed the boot time too long for v2.0
- add rmnet support, can change easily by: touch /system/ppp to change to ppp, or just rm it for rmnet.
- fix the bug (can not process the update correctly) in initrd.gz for nand.
- add feature in initrd.gz for SD to automatically create 1g data.img.
- some other changes.
[B]v2.0[/B]
- Major release.
- Use same base with my nand version, which Squashed as many files as possible.
- Even for squashed file, it still can be replaced as the separated symbol link is kept in original place.
- New Kernel of MDJ 9.2 in order to support SquashFS and Ext4.
- System.ext2 is hence recreated with about 290M + 30M spare space, which is about 100M less than the unsquashed version.
[B]v1.0[/B]
- Major release.
[B]v0.3.2[/B]
- Optional Bugfix for high mic gain problem.
[B]v0.3.1n[/B]
- Pre-configured build for newbie.
- Reset all the file permissions to prevent any possible FC.
- Incorporate all the incremental updates except the Optional ones.
- Google Voice search.
- And more..
[B]v0.3.1[/B]
- An optional update to customize your own boot animation.
- An optional update to install the Stock Widget
[B]v0.3[/B]
- [B][COLOR="Red"]advanced power menu[/COLOR][/B]
- [B][COLOR="red"]totally rotate[/COLOR][/B]
- remove Swype from system to data
- many optimization
- this is considered as a major release.
[B]v0.2.2s[/B]
- Optional update for revert back to stock framework.
- Optional update to install Stockwidget.
[B]v0.2.2[/B]
- Include Bugfix 2010122501(auto APN)
- Add HTC stock widget
- Remove Wifi Call
- Supply some applications to be installed into data.img.
.Gmail
.Google maps
.Google translate
.current widget
.Astro file manager
.Audio widget
.Drocap2
.Quadrant benchmark
.Sms backup plus+
.some Skins
[B]v0.2.1[/B]
- Bugfix 2010122501(auto APN)
[B]v0.2[/B]
- Fixed the wifi issue and added the Ad-hoc Wireless Network Support.
- Fixed the SU issue.
- Used full stock Rom to recreate this build.
[B]v0.1[/B]
- Initial release.
Features
- Cedesmith new Initrd
- Hastarin r8.6 kernel
- Fly animation
- Latest busybox
- camera
- Massive APN from Cyanogen ROM
- Wifi fixed and added the Adhoc Wireless Network Support.
- UTF8, support multi character languages, e.g. Chinese File name etc.
- Buildin Arabic & Hebrew support
- all that work in other builds.
Download:
V2.1 for Nand
http://www.multiupload.com/PEWNGWULCX
Apps removed from V2.1 build:
http://www.mediafire.com/?vjb479v6k0mougn
For Nand build, please extract it in "DLZUPDATE", remove the apps that you may not need before reboot.
For SD build, extract it to your android folder.
IMPORTANT!
1. After first boot, open the ROM manager and run Fix permission(you can use it to fix the FC late once it happens.)
2. Reboot.
3. Use setCPU to set the CPU to 99840 or even more.
4. Install your apps
5. For stock version fans, apply the 2 optional updates I provided in "Bugfix&New Features"..[/B]
SD build V1.0
http://www.multiupload.com/E8PC0MZDW0
- please extract the "desire_z" to your sdcard
- put the AndroidApp into that folder only after you successfully boot this build.
- additional keyboards are provided in the AndroidApp, select either one you prefer.
- For stock version fans, apply the 2 optional updates I provided in "Bugfix&New Features".
Bugfix&New Features
Thanks to:
- Cedesmith
- LeTama
- Hastarin
- NetRipper
- Markinus
- gauner1986
and others
Installation:
- extract "desire_z" folder on the root of your SD card
- Run "CLRCAD.exe" then "haret.exe"
This build should be very fast and smooth, I got the Quadrant score of 2700.
the screen is similar to Desire HD, you can refer to the screen shots from MDJ's build, only difference is battery with percentage which I think is most important.
Enjoy

the rom seems no FM Radio !!!

wpullo said:
the rom seems no FM Radio !!!
Click to expand...
Click to collapse
dandiest included all of the apps he ripped from this build above. Reposting his link....
http://www.mediafire.com/?vjb479v6k0mougn
to install FM radio you need to use the built-in update utility dandiest created. In the root of your SD card you must create the following folders, "DLZUPDATE" inside that create "root" inside that create "system" inside that create "app" inside that place the file "com.htc.fm.apk."
Once you have DLZUPDATE\root\system\app in the root of your SD with the com.htc.fm.apk file inside, reboot your phone and it will automatically install the FM radio.
I've tried every nand build and this one is by far the greatest. Fast, stable, lightweight and extremely low battery consumption. Feels like the native OS. You can read other user's testimonies and if you'd like to follow dandiest's incredible work, he maintains this build in the HD2 Android Development section.

Question
How about TMOUS MMS 1024K pic size fix, is it implemented?

tjones25 said:
How about TMOUS MMS 1024K pic size fix, is it implemented?
Click to expand...
Click to collapse
Yes. Pictures larger than the max (1024K) will be compressed to ~40K. Anything smaller than the max will be sent out without being compressed. I have it running 100% from nand on my TMOUS HD2. You can also run it from your SD through WM (which i used to before magldr) and he also created a data2sd build for euro hd2 users.
Everything has been addressed in dandiest's thread. He maintains and focuses on this build only this build to make it perfect and in my opinion, he has. dandiest has expressed that he doesn't want to maintain two threads so please head over to the following link to his thread. You will not be disappointed.
http://forum.xda-developers.com/showthread.php?t=881937

fatappel said:
Yes. Pictures larger than the max (1024K) will be compressed to ~40K. Anything smaller than the max will be sent out without being compressed. I have it running 100% from nand on my TMOUS HD2. You can also run it from your SD through WM (which i used to before magldr) and he also created a data2sd build for euro hd2 users.
Everything has been addressed in dandiest's thread. He maintains and focuses on this build only this build to make it perfect and in my opinion, he has. dandiest has expressed that he doesn't want to maintain two threads so please head over to the following link to his thread. You will not be disappointed.
http://forum.xda-developers.com/showthread.php?t=881937
Click to expand...
Click to collapse
I was using the sd version, but switched build for nand...glad to see this build in nand format

change font?
i want change font, but it error?

kenzi_100c said:
i want change font, but it error?
Click to expand...
Click to collapse
font folder is squashed so it can not be changed by normal means. if you ask the build creator to make you a font update folder to use with his update utility, he will.
his thread is here if you'd like to request.....
http://forum.xda-developers.com/showthread.php?t=881937

I'm getting freezes galore on the NAND version... Not sure why, but I've downloaded it 2 times, re-installed like 4 times, but it just doesn't want to run on my device. It does run very smooth when it works for the 5min that it works though.

I have not had that issue but lets get some basics. What verson of Magldr are you using and how many times have you reflashed and/or rebooted your phone.

haha, thanks, just find this thread.
I really have no time to maintain 2 threads, instead, I'd rather spending all my spare time to improve the build itself.
a lot of time has been spent on enabling the data2sd and ext4, now, I'm excited to release the upgrade(test version) to V2.3, it is not anything like the current data2sd or ext4 or a2sd(I have studied all of those) , what's special for my build is:
1. it can be easily change from data2sd to ext, vice versa by the switcher of data_img in config.txt, if the sdcard has 2nd partition, it will automatically change to the data2ext.
2. sd card is not simply mount to overwrite the nand data partiton, instead, the original data partition in Nand is used for improve the system performance: property, misc, system, dalvik-cache are moved back to nand, no matter the data is in data.img file or on 2nd partition.
3. a switcher of "sd_boost" in config.txt is provided to improve the SD performance furthermore. for ext4, it will be mounted to loop without journal, which will significantly improve the SD IO. for data.img, a-sync will be used. while of course, the price is that there is some chance of data crapt, for data.img user, can easily copy the file, for ext user, I will provide another function to backup/restore the data in ext to/from an img file soon.

I was wondering if i could remove the animations and get the stock one?

[24.APR.2011][KERNEL] AA 0.6 OC [ext2/3/4,cifs,reiserfs,btrfs,nilfs,utf8][MAGLDR/cLK]

Use at your own risk, overclock at your own risk - I'm not responsible for damage to your device​
The kernel used in this ROM is based on MDJ S9.2, and have ported it, and have patched to the latest upstream with the relevant fixes
The git is available here, check logs and diffs for the changes made. There is a neat build script to get it compiled for yourself if you want as well in Linux or cygwin. I am using the test branch at the moment.
Howto cLK (kernel_aa_X.X.zip)
Click to expand...
Click to collapse
Download kernel
Unzip archive
run script.sh (linux) or script.bat (windows) to copy over the kernel modules to your phone (make sure adb is in your path)
grab the initrd.gz from your current rom
then, either
reboot phone into fastboot by holding the back key
run "fastboot -c "" -b 0x11800000 flash:raw boot zImage initrd.gz"
or
make boot.img by using "mkbootimg --kernel zImage --ramdisk initrd.gz --cmdline "console=null" --base 0x11800000 -o boot.img"
adb push boot.img /sdcard/
adb shell flash_image boot /sdcard/boot.img
reboot your phone
Howto MAGLDR CWM (kernel_aa_X.X.zip) & Howto cLK (kernel_aa_X.X_clk_ppp.zip)
Click to expand...
Click to collapse
Download kernel
copy archive onto the FAT partition of your SD card
reboot phone into CWM
Select Install zip from sdcard
Select choose zip from sdcard
Select the kernel from the SD
Select Yes to install the zip
reboot your phone
Differences between kernel_aa_X.X.zip and kernel_aa_X.X_clk_ppp.zip
Click to expand...
Click to collapse
my initrd (so has boot.img which will only work with cLK)
Added ppp specific stuff
Added 02recov, which allows to get ROM Manager working (works for me)
NOTE: The initrd may or may not work for everyone please report your problems with dmesg and logcat files
Thanks/credits
Click to expand...
Click to collapse
m-deejay
Cotulla (MAGLDR)
RaiderX303 (ClockworkMod)
cedesmith (cLK)
#htc-linux and #htc-linux-chat
All ROM users

Changelog
v0.6 (24/04/2011)
Add reiserfs support
Add NILFS support
Add btrfs support
v0.5 (21/03/2011)
Removed SMARTASS
Merged with master git
v0.4 (18/03/2011)
kernel patch to save reboot reason so is available on bootloader (credits to cedesmith)
v0.3 (01/03/2011)
Add back PPP support (to work with cLK)
Add cLK patches (credits to cedesmith)
more MDJ stuff config
v0.2 (14/02/2011)
re-cloned MDJ S9.2
Created branch test
Removed squashfs
Removed unnecessary PPP
Merged with master git
v0.1 (12/02/2011)
cloned MDJ S9.2
merged with master git
Previous Changelog from MDJ
Code:
S9.2:
- fixed wifi mac addresses ( http://www.gitorious.com/linux-on-wince-htc/linux_on_wince_htc/commit/4c31f2fb265ae68b82ed5e8ea4bec91208837011 )
S9.1:
- Initial Release

reserved another

Trying now
Sent from my HTC HD2 using XDA Premium App

Nice, thanks.....if i'm not wrong Mdj's kernel wasnt UV, right?

is it UV? afaik no
af974 said:
Nice, thanks.....if i'm not wrong Mdj's kernel wasnt UV, right?
Click to expand...
Click to collapse
afaik, it is not UV, I cannot see it in his changelogs

updated kernel see OP, changelog and git logs for details

Thanks so much. It's said that MDJ's kernel is extraordinary power-saving and low battery drainage. We have not seen Mr MDJ on the forum for quite a long time. We just hope you great guys to carry on the goodness of MDJ's kernel.

about time someone made a proper kernel for cLk ..thanks arif-ali

arif-ali said:
Use at your own risk, overclock at your own risk - I'm not responsible for damage to your device​
The kernel used in this ROM is based on MDJ S9.2, and have ported it, and have patched to the latest upstream with the relevant fixes
The git is available here, check logs and diffs for the changes made. There is a neat build script to get it compiled for yourself if you want as well in Linux or cygwin. I am using the test branch at the moment.
Download kernel
Unzip archive
run script.sh (linux) or script.bat (windows) to copy over the kernel modules to your phone (make sure adb is in your path)
grab the initrd.gz from your current rom
then, either
reboot phone into fastboot by holding the back key
run "fastboot -c "" -b 0x11800000 flash:raw boot zImage initrd.gz"
or
make boot.img by using "mkbootimg --kernel zImage --ramdisk initrd.gz --cmdline "console=null" --base 0x11800000 -o boot.img"
adb push boot.img /sdcard/
adb shell flash_image boot /sdcard/boot.img
reboot your phone
Download kernel
copy archive onto the FAT partition of your SD card
reboot phone into CWM
Select Install zip from sdcard
Select choose zip from sdcard
Select the kernel from the SD
Select Yes to install the zip
reboot your phone
my initrd (so has boot.img which will only work with cLK)
Added ppp specific stuff
Added 02recov, which allows to get ROM Manager working (works for me)
NOTE: The initrd may or may not work for everyone please report your problems with dmesg and logcat files
m-deejay
Cotulla (MAGLDR)
RaiderX303 (ClockworkMod)
cedesmith (cLK)
#htc-linux and #htc-linux-chat
All ROM users
Click to expand...
Click to collapse
Can you please make a cLK CWM Kernel of your to use with Typhoons build...
I have tried it this way and is not working and I think that the file structure for Typhoon builds is different that common build.
I would like to try this kernel. Is it possible plz?

zach.antre said:
Can you please make a cLK CWM Kernel of your to use with Typhoons build...
I have tried it this way and is not working and I think that the file structure for Typhoon builds is different that common build.
I would like to try this kernel. Is it possible plz?
Click to expand...
Click to collapse
what problems are you getting, any logcats or dmesg output

arif-ali said:
what problems are you getting, any logcats or dmesg output
Click to expand...
Click to collapse
it was stuck in bootscreen, i will try to send later.
Till then you can check the GL_Core kernel thread that had same issue
he made a Kernel for Typhoon builds and a kernel for all others.
you can see the differencies

arif-ali said:
what problems are you getting, any logcats or dmesg output
Click to expand...
Click to collapse
here is the logcat

@zach.antre
I have added the 0.5 kernel with wpa in OP, This is the only difference I see between my kernel and the GL kernel.
I haven't tested it, so not sure if it will work.
If you do test it, let me know how it goes.
thanks

arif-ali said:
@zach.antre
I have added the 0.5 kernel with wpa in OP, This is the only difference I see between my kernel and the GL kernel.
I haven't tested it, so not sure if it will work.
If you do test it, let me know how it goes.
thanks
Click to expand...
Click to collapse
I'll test it know, give 5 minutes and i'll report back
------------------EDIT---------------------------
After testing your kernel again i get the same issues.
System will not start, it is stuck in bootscreen.
You will find attached the logcat
I should mention that TyphooNs build is nonSense, it is CM7

Not many use this, but hey, might as well release it
updated kernel to
* Add reiserfs support
* Add NILFS support
* Add btrfs support

arif-ali said:
Not many use this, but hey, might as well release it
updated kernel to
* Add reiserfs support
* Add NILFS support
* Add btrfs support
Click to expand...
Click to collapse
Hey Arif, what exactly is reiserfs, nilfs, btrfs?

mattfmartin said:
Hey Arif, what exactly is reiserfs, nilfs, btrfs?
Click to expand...
Click to collapse
they are all file systems, similar to ext2/3/4, but some people prefer these instead
plus this is the basis for the recovery kernel as well that is available on RM, so more I can support, the better

arif-ali said:
Not many use this, but hey, might as well release it
updated kernel to
* Add reiserfs support
* Add NILFS support
* Add btrfs support
Click to expand...
Click to collapse
Hi Arif, thanks for all the good work!
1) Does this kernel work for GB, or only Froyo?
2) Does cLK version incorporate any of the new ppp wrapper stuff discussed in cedesmith's thread?
Thanks!

lukedunk said:
Hi Arif, thanks for all the good work!
1) Does this kernel work for GB, or only Froyo?
2) Does cLK version incorporate any of the new ppp wrapper stuff discussed in cedesmith's thread?
Thanks!
Click to expand...
Click to collapse
1a) personally, haven't tested this in GB, so not sure. zach.antre tested it with one of the GB roms, and didn't quite work. I still need to do some testing, to see exactly what is different to make it work. (but you can still test if you want the challenge)
1b) This kernel is used as a basis for CWR that is on RM, so the fact it works there, and the basis there is GB, I would have thought that it would work with GB, but I could be wrong
2) No, as the wrapper is still beta at the moment (and several people are still having problems). Once we know that is working effectively with no problems, I will have no problems in adding it in.

[RECOVERY][OFFICIAL][F500,LS991,H81x,US991,VS986][N,O,P] TWRP [2020-06-22]

About
TWRP is an open source, community project. TWRP development is done by roughly 4 people at this point. We also have a large support community with many people who are willing to answer questions and help people with their devices either through our IRC channel or on forums like xda-developers.
Team Win was originally formed to work on porting WiMAX to CM7 for the HTC EVO 4G. After our work on the EVO 4G we wanted to work on a project that would work on more devices than just the EVO 4G and we settled on working on a recovery. Today TWRP is the leading custom recovery for Android phones.
A custom recovery is used for installing custom software on your device. This custom software can include smaller modifications like rooting your device or even replacing the firmware of the device with a completely custom "ROM" like OmniROM
Click to expand...
Click to collapse
(Source: https://twrp.me/)
Is this the official TWRP thread?
YES until you find any further notice on https://twrp.me .
Features
<MM> (PREVIEW): Build on (Android 6.0) sources
<N> (PREVIEW): Build on (Android 7.1) sources
<O> (PREVIEW + current OFFICIAL): Build on (Android 8.1) sources
<P> (PREVIEW): Build on (Android 9.0) sources
TITAN kernel inside (build with UBER Toolchain)
Time is working (for both STOCK and CM/AOSP based)
Decrypting is supported on: MM, N, O (CM/LOS/AOSP based ROMs) and on STOCK based ROMs (N only)
DT2W (double tap to wake up) - thx for the idea ufocus removed, sorry.
see the Changelog post for all features!
Requirements
You need to have a unlocked bootloader (see FAQ #9) to install and use TWRP!
To avoid issues with some ROMs (e.g. CM) this TWRP version comes without any supersu
Known issues
decrypting STOCK (other then N) is not working - only CM / LOS / AOSP based are fully supported
on some devices (unfortunately not on mine) the screen keeps unresponsive during a backup. Please just be patient it will start working again after the backup has finished.
after flashing Nougat bootloader (e.g. v29a) TWRP may lag. This has been reported by a few but I cannot reproduce that on mine.
Download
official twrp download page (search for your device model)
unofficial / PREVIEW releases:
From time to time I may release unofficial PREVIEW versions before merging them to official builds.
Those are meant as test builds only! Keep in mind that all my changes when they go stable will be merged with the official tree so you can just wait for a stable release.
Keep in mind that unofficial versions may contain unknown bugs!! so don't rely on backups taken from these versions!
Unofficial PREVIEW downloads (most current):
1) When do you need to install a specific flavor (MM, N, O,...) ?
if you want correct time setting in TWRP
if you want to decrypt - so encrypted your device
2) Is there any other reason why I should use a specific flavor (MM, N, O,...) ?
no!
you can use ANY flavor if you don't care about the above 2 reasons
3) So I can use ANY TWRP version to install ANY ROM?
Or do I need to use a specific flavor (MM, N, O,...) when it comes to install ROMs or other ZIPs?
read 2) again!
Download Link: http://leech.binbash.rocks
BETA downloads (extremely outdated): Download section above.
Installation
Optional but highly recommended:
Backup with SALT (click) before doing ANYTHING else!
Method 1) TWRP app (recommended but requires a rooted device)
Google play store: TWRP-App
Without play store: official twrp website
I said you need an unlocked device. So ensure you have it unlocked and for official unlocked G4 models the OEM unlocking option must be enabled!
Install the app and open it. Agree to the Terms.
Select TWRP Flash.
Select your device from the device list (H811, H815) and choose a version.
The file will download to your Downloads folder.
Browse to and select the file.
Tap on Flash to Recovery.
Find out more about the app here.
Method 2) fastboot
This howto works 100% up to and including MM (scroll down for N):
I said you need an unlocked device. So ensure you have it unlocked and for official unlocked G4 models the OEM unlocking option must be enabled (see screenshot)
Connect an USB cable and get ADB running (READ the FAQ!! or the general guide above)
Boot into Android and then type on your PC to reboot into fastboot mode:
adb reboot bootloader
Type on your PC:
fastboot boot twrp.img
(replace twrp.img with the real file name you downloaded)
Then copy the twrp.img to your device while still in twrp (e.g. with a file explorer or by typing adb push twrp.img /sdcard)
Flash the twrp.img with twrp GUI to the recovery partition (choose the button at the bottom named image to show the copied image)
It is highly recommended to verify your TWRP installation by booting into Android now
fastboot reboot
Then execute: adb reboot recovery
or in a Android terminal app execute: reboot recovery
If you see TWRP afterwards then you are safe to use the key combo:
After installing TWRP correctly, you will still have the original LG factory reset screen/menu booting before TWRP, every time. So the correct and only way to get into TWRP with a key combo is to select two times "Yes" in the official LG factory reset menu, and only then you will get into TWRP (It's a restriction by LG. There is no key combo available in some / all / most LG devices to boot directly into recovery and so TWRP).
If that worked go into the reboot menu and choose reboot to recovery again so TWRP should boot up once again
Now all should be in place and TWRP should resist even booting into Android
This howto is for the Nougat bootloader (for LP or MM scroll up):
I said you need an unlocked device. So ensure you have it unlocked and OEM unlocking option is enabled (see screenshot)
Connect an USB cable and get ADB running (READ the FAQ!! or the general guide above)
Boot into Android and then type on your PC to reboot into fastboot mode:
adb reboot bootloader
Type on your PC (fastboot BOOT command has been removed from Nougat!):
fastboot flash recovery twrp.img
(replace twrp.img with the real file name you downloaded)
There is no 100% way to verify your TWRP installation so you have to take the risk but ensure you follow this next step briefly:
After installing TWRP correctly, you will still have the original LG factory reset screen/menu booting before TWRP, every time. So the correct and only way to get into TWRP with a key combo is to select two times "Yes" in the official LG factory reset menu, and only then you will get into TWRP (It's a restriction by LG. There is no key combo available in some / all / most LG devices to boot directly into recovery and so TWRP).
Do this right now!! open the factory reset screen to get into TWRP!
If you skip the step and boot into Android before doing this TWRP will be overwritten by Android so it is crucial important to do this step above directly after flashing TWRP!!!!! if you miss it you will have to flash TWRP again!
If that worked go into the reboot menu and choose reboot to recovery again so TWRP should boot up once again
Now all should be in place and TWRP should resist even booting into Android
Upgrade
Upgrading TWRP is easy. Just push the new image file to your device and flash from TWRP!
boot into TWRP (check the FAQ for a howto)
copy the new twrp.img to your device while still in twrp (e.g. enable MTP in TWRP and use a file explorer or by typing adb push twrp.img /sdcard on your PC (needs ADB installed. Again check FAQ for how to set this up))
In TWRP switch the view to show image files by choosing the button at the bottom named Image and walk to the place where you pushed the new twrp image file.
Choose the new twrp image file and when asked choose the "recovery" partition
done. You can now reboot into recovery again to check that the upgrade has worked.
Support
I have created a Telegram group for all stuff around Android : here
and another one if you want to keep up2date whenever I build something (TWRP, SHRP, LOS, /e/, ...): here
I'm normally also available in the official twrp IRC channel and besides that it is always the best way for getting direct TWRP support (channel #twrp)!
Before actually going there or if you're new to IRC please read and follow FAQ #5 What is required to get support?
Thread rules
Never ask for ETA's !
Sources
Official builds device tree: github
PREVIEW builds device tree github
Kernel: TITAN kernel
Thanks/Credits
TEAMWIN of course
@DevUt for the continues help on IRC
@jcadduono for some help with qseecomd libs
@kessaras for the TITAN kernel and for being often enough my testing *****
XDA:DevDB Information
Official TWRP, Tool/Utility for the LG G4
Contributors
steadfaster, draymond1987
Source Code: https://github.com/TeamWin/android_device_lge_g4
Version Information
Status: Stable
Current Stable Version: 3.4
Stable Release Date: 2020-06-22
Current Beta Version: any PREVIEW
Created 2016-08-18
Last Updated 2020-08-21

Changelog
Latest Official release
twrp-3.4.0-0
Release date: 2020-06-22
Compatibility: OREO (all other versions should work for flashing but enc, time and any adb commands will work with OREO only)
Download: https://twrp.me
Device Tree changelog: no changes
Summary changelog:
TWRP release notes
Previous Official(!) builds
twrp-3.3.1-2
Release date: 2020-02-28
Compatibility: OREO (all other versions should work for flashing but enc, time and any adb commands will work with OREO only)
Download: https://twrp.me
Device Tree changelog: github
Summary changelog:
you REALLY wanna now what has changed?
check it out
twrp-3.3.1-1
Release date: 2019-07-18
Download: https://twrp.me
Device Tree changelog: while the version seems to be minor this is a MAJOR change: I switched from Android-6.0 to Android-8.1, removing 5.1 support
Summary changelog:
Official TWRP now supports Oreo by default (decrypt, correct time)
This removes support for Lollipop bootloader stack - thats why the image size is almost just the half.
If you are still using an Lollipop / 5.1 bootloader stack (wth..?!) UPGRADE it - or 3.3.1-0 is the last supported for yours. You can always check the PREVIEW flavor for MM which is backwards compatible but do not expect any official builds for LP anymore.
you REALLY wanna now what else has changed?
it is way too much but here check it out and see what you have missed from not using a PREVIEW flavor ....
Latest Official release
twrp-3.3.1-0
Release date: 2019-05-22
Download: https://twrp.me
Device Tree changelog: (no changes)
Summary changelog:
https://twrp.me/site/update/2019/05/22/twrp-3.3.1-0-released.html
Latest Official release
twrp-3.3.0-0
Release date: 2019-04-10
Download: https://twrp.me
Device Tree changelog: (no changes)
Summary changelog:
https://twrp.me/site/update/2019/04/15/twrp-3.3.0-0-released.html
twrp-3.2.3-0
Release date: 2018-08-06
Download: https://twrp.me
Device Tree changelog: (no changes)
TWRP sources changelog: twrp-3.2.2-0 <--> twrp-3.2.3-0 (previous official vs. current official)
Summary changelog:
https://twrp.me/site/update/2018/08/06/twrp-3.2.3-0-released.html
twrp-3.2.2-0
Release date: 2018-07-01
Download: https://twrp.me
Device Tree changelog: (no changes)
TWRP sources changelog: twrp-3.1.1-0 <--> twrp-3.2.2-0 (previous official vs. current official)
Summary changelog:
https://twrp.me/site/update/2018/07/01/twrp-3.2.2-0-released.html
twrp-3.2.1-0
Release date: 2018-05-25
Download: https://twrp.me
Device Tree changelog: twrp-3.1.1-0 <--> twrp-3.2.1-0 (previous official vs. current official)
TWRP sources changelog: twrp-3.1.1-1 <--> twrp-3.2.1-0 (previous official vs. current official)
Summary changelog:
https://twrp.me/site/update/2017/12/09/twrp-3.2.1-0-released.html
twrp-3.1.1-1
Release date: 2017-06-21
Download: https://twrp.me
Device Tree changelog: twrp-3.1.1-0 <--> twrp-3.1.1-1 (previous official vs. current official)
TWRP sources changelog: twrp-3.1.1-0 <--> twrp-3.1.1-1 (previous official vs. current official)
Summary changelog:
decryption fixed (again) for CM/AOSP
twrp-3.0.2-1
Release date: 2017-06-15
Download: https://twrp.me/devices
Device Tree changelog: twrp-3.0.2-1 <--> twrp-3.1.1-0 (previous official vs. current official)
TWRP sources changelog: twrp-3.0.2-1 <--> twrp-3.1.1-0 (previous official vs. current official)
Summary changelog:
LL supported again
Unification of h811 and h815
many bugfixes, speed and other improvements (pls check the above changelog links!)
Latest PREVIEW release
read more about PREVIEWS and the <flavor>'s in the OP (what they are and when to use)!
twrp-<version>-PREVIEW-<buildnumber>_g4_<flavor>
Status: stable
Release date: see leech server
Download: sfX leech server (same download for all G4's)
Kernel: preview builds compile the kernel on build automatically (official not) - so the kernel differ between official and preview
Device Tree changelogs:
MM flavor - NOTE: The support for the MM flavor has reached its END OF LIFE (2020-02-28)
N flavor
O flavor
P flavor
Previous builds
twrp-3.2.1-PREVIEW-116_g4_O (only O!)
Status: testing
Release date: 2018-03-28
Download: Download Page (same download for all G4's)
Device Tree changelog: O flavor
Summary changelog:
newest TITAN
switched kernel toolchain (same then TITAN uses)
decrypting O works (aoscp tested)
complete build on O sources (TWRP)
twrp-3.2.1-PREVIEW-109_g4_N (only N!)
Status: stable
Release date: 2018-03-17
Download: Download Page (same download for all G4's)
Device Tree changelog: N flavor
Summary changelog:
Decrypting STOCK N is working now!
twrp-3.2.1-PREVIEW-106_g4_<flavor>
Status: stable
Release date: 2018-03-15
Download: Download Page (same download for all G4's)
Device Tree changelog: MM flavor and N flavor
PREVIEW vs. OFFICIAL changelog: MM PREVIEW <--> latest official TWRP and N PREVIEW <--> latest official TWRP
twrp-3.2.0-PREVIEW-43_g4_<flavor>
Status: stable
Release date: 2017-12-07
Download: Download Page (same download for h811/h815)
Device Tree changelog:
<custom-m>: https://github.com/steadfasterX/android_device_lge_g4/commits/android-6.0
<custom-n/stock>: https://github.com/steadfasterX/android_device_lge_g4/commits/android-7.1
PREVIEW vs. OFFICIAL changelog:
<custom-mm>: this PREVIEW <--> twrp-3.2.0-0
<custom-n/stock>: this PREVIEW <--> twrp-3.2.0-0
Summary changelog:
<all>: replaced LLAMA kernel with TITAN (thx @kessaras for the kernel )
<all>: updated TWRP codebase to 3.2.0 (https://github.com/omnirom/android_bootable_recovery/compare/android-7.1...android-8.0)
<all>: removed legacy LP decryption support (it MAY still work though bc of the next line)
<all>: using new decryption support by TW_CRYPTO_USE_SYSTEM_VOLD ( https://github.com/omnirom/android_bootable_recovery/commit/71c6c50d0da1f32dd18a749797e88de2358c5ba1 )
This means in theory: decrypting stock and any other ROM should be much easier now.
<custom-n>: enabled debug when decrypting (will be disabled once all decrypting tests are done)
<stock>: builds are now based on 7.1 tree (like custom-n)
<custom-mm>: in some beta versions decrypt was broken which is now fixed again
<all>: fixed time (again)
<all>: from now on I will generate md5 hashes for all unofficial / PREVIEW twrp releases
twrp-3.1.1-BETA-g4-sfXbuild3
Status: stable (it's a BETA though)
Release date: 2017-06-20
Download: Download Page (same download for h811/h815)
Device Tree changelog: previous BETA <--> this BETA
BETA vs. STABLE changelog: this BETA <--> twrp-3.1.1-0
Summary changelog:
decryption fixed (again) for CM/AOSP
BETA-5 Build id #327 (h811 + h815)
Status: stable (it's a BETA though)
Release date: 2016-12-19
Download: Download Page (same download for h811/h815)
Device Tree changelog: build #317 <--> build #327
TWRP sources changelog: build #317 <--> build #327
first working unified TWRP version for both h811 and h815 in one build. That means:
from now on there will be 1 single download file which works for both devices.
factory reset in Android will do it's job now! That means:
using the factory reset hardware key combo will just open TWRP (as it is in all builds)
but when you do a factory reset in Android settings it will boot into TWRP and wipe now
Hint: This requires the ROM uses /grow as /misc partition! Example: CM supports this in CM14.1 since 15th of Dec 2016
Other ROMs may have to change their fstab to make this working for them
BETA-4 Build id #317 (h811 + h815)
Status: stable (it's a BETA though)
Release date: 2016-12-16
Device Tree changelog: build #285 <--> build #317
TWRP sources changelog: build #285 <--> build #317
fixing an issue with cmupdater preventing to upgrade
Using /grow as /misc because the CM devs preferring this (https://review.cyanogenmod.org/#/c/177122/)
BETA-3 Build id #285 (h811 + h815)
Status: stable (but cmupdater is broken here)
Release date: 2016-12-14
Device Tree changelog: build #186 <--> build #285
TWRP sources changelog: build #186 <--> build #285
first fully working version for the h811 device
governor=intelliactive, IO scheduler=sioplus, rhsize=1024. see twrp benchmark
adding /misc to support CM internal updater! Now cmupdater would work if the CM devs will enable it again (will work up to 5th of Dec CM 14 builds nevertheless. The internal cmupdater will prevent booting into recovery after that build date... Tested on h811 and h815.).
Ensuring that factory reset by the hardware key combo will not reset the device (proven on h811 and h815 that it will NOT wipe when open "factory reset" page with hardware key combo)!
Switched back to android-6.0 branch because bigbiff recommended that
BETA-2 Build id #186 (h815)
Status: stable
Release date: 2016-11-21
Device Tree changelog: build #162 <--> build #186
TWRP sources changelog: build #162 <--> build #186
Using FIOPS I/O scheduler
read_ahead_kb=2048
Build id #162 (h815)
Status: stable
Release date: 2016-09-12
Device Tree changelog: build #91 <--> build #162
TWRP sources changelog: build #91 <--> build #162
new: build on the latest 7.0 branch of TWRP
CRITICAL fix: bug when restoring EFS! (Due to an issue in the TWRP sources it was not possible to restore EFS which is fixed now)
fix: time was not correct for CM based ROMs
fix: time was not correct for STOCK based ROMs
new: double tap will awake device
fix: minor issue for bootdevice
fix: launch qseecomd on boot to avoid issues with decryption
fix: logfile messages now all in /tmp/recovery.log instead of cmd specifics
fix: removed /firmware from backup menu --> DO NOT TRY TO RESTORE ANY PREVIOUS /firmware BACKUP! You can restore it with LG Up if you do that by mistake
... for the rest and details checkout the changelog above
Build id #091
Status: abandoned
Release date: 2016-08-18 - Removed due to a bug in twrp sources. Pls see my post here
Device Tree changelog: TeamWin official <--> build #91
TWRP sources changelog: TeamWin official <--> build #91
initial public release
making decryption work
... for the rest and details checkout the changelog above

FAQ
Frequently Asked Questions (FAQ)
What's the meaning of decryption in terms of TWRP?
When you enable full device encryption in your favorite ROM or using stock without modification then your data partition is encrypted. That means no one can access your data when you shutdown your phone.
So in twrp you will see the data partition as a big 32gb unreadable partition even if 3GB are in use when you booted (and therefore decrypted) your ROM.
You CAN still backup that data partition but it will backup the whole 32GB because of encryption.
With this twrp version when started you will be asked for the decryption password and your data partition is readable as in the ROM. When you backup now the data partition it just backups the data in use so 3 GB instead of 32GB.
Regarding any pros of not using full disk encryption in your ROM I can say it does not really matters in performance in all normal cases. You will always read that disabling decryption will give you much more power and so on but the today's spec of phones are so good you will feel a slightly diff only. Ok some users still believe that this is minimal diff is what they need but to be honest: The ONLY way to find an answer for yourself is testing on your own using the SAME ROM and same version! One time with encryption once without. Use the exact same ROM and use the exact same configuration like governors, custom kernels etc.
On the other hand you will get a minimum of security if you enable encryption but give access to everyone finding your lost phone if not!
So it's up to you if you want this risk for a minimum on performance improvement.
And just for sure:
decrypting in twrp is not permanent! Your data gets just decrypted for backing up nothing more nothing less.
[*]You talked about using IRC to get support. What is this and how can I use that?
Note: check the support topic as from now on there is also a Telegram group for that available.
Meaning of IRC => Internet Relay Chat. A very good IRC client is this one here: hexchat <-- download it and read the quick intro to get started: Quick-Start
--> when asked if you want to join a channel type in "#twrp" and after connected you will be in.
If you do not want to install anything you can simply use the webchat instead directly over here: Webchat
Howto communicate? IRC means many people talking the same time and there are some goods and bads to know about using IRC.
So please read this mini and very quick overview (especially the good manners there): Good manners in IRC (matches for all OS not for fedora only)
[*]What is that "adb" thing??
adb stands for: Android Debug Bridge and can help a lot when it comes to work with your device. It is not for developers only but they use it a lot of course.
But a normal user can use this to exchange files without the need of mounting, backing up the device, reboot the device and use it as a very comfortable way of having a terminal emulator.
I highly recommend to use FWUL to connect your device. Not for TWRP only but also for anything else adb/fastboot related.
What Logfiles have to be provided and how?
Two options are available:
Option A is the absolute minimum when reporting an error and it can be done by every user without installing anything or any special skills!! Reports without this minimal requirement will be ignored!
Option B is also very simple but you need to install ADB if not installed already. The steps are very easy and there is an easy installer available.
Keep in mind that if you have a problem and want that to be solved the more you can tell and the more you can provide the better it is. So choose your option wisely....
A) The absolute MINIMUM: recovery.log:
Start in TWRP and connect an USB cable to your device
Menu: Advanced
Menu: Copy Log
Click Home button and go to Menu: Mount
Ensure MTP is enabled (button at the bottom)
Open the file explorer on your PC and go to Sdcard
open the file "recovery.log" in a text editor (windows users: Wordpad)
copy the whole content and paste it on http://bpaste.net (choose a long duration in the drop down). After you pasted your log there a LINK WILL BE GENERATED!!! I NEED THAT URL !!!.
Here are 2 screenshots which should guide you in this:
paste the log file:
copy URL:
Report the link of that paste URL by PM or in this thread
Besides the above tell me:
ROM name or say "STOCK"
ROM version ("LL" or "MM" - if you can tell me the build number as well)
Encrypted device or not
B) But for THE BEST SUPPORT provide not recovery.log only but also dmesg by executing the following cmds on your PC:
Start in TWRP and connect an USB cable to your device. Then on your PC (requires ADB installed! Check FAQ #3 of this post!!):
adb shell
dmesg > /tmp/dmesg.txt
OPTIONAL (only when requested by me): logcat -d -b all > /tmp/logcat.txt
OPTIONAL (only when requested by me): adb pull /tmp/logcat.txt
OPTIONAL (only when requested by me): cat /proc/last_kmsg > /tmp/kmsg.txt
exit
adb pull /tmp/recovery.log
adb pull /tmp/dmesg.txt
OPTIONAL (only when requested by me): adb pull /tmp/kmsg.txt
Open all logs one by one with a text editor like wordpad or similar and paste it here: http://paste.omnirom.org (do NOT paste all in one! Every single log should have a single paste URL)
If the logfile(s) are too big to get them uploaded on paste.omnirom.org use something like gists.github.com if you have a github account or zip it and upload it at www.filedropper.com
Report the link of that paste URLs by PM or in this thread
Besides the above tell me:
ROM name or say "STOCK"
ROM version ("LL" or "MM" - if you can tell me the build number as well)
Encrypted device or not
[*]What is required to get support?
Get IRC running (see FAQ 2)
Get adb running (see FAQ 3)
Collect logs (see FAQ 4)
Go to IRC and paste your problem together with the paste URLs you done before
If you can't see me on twrp or if there are any reasons why you may not get IRC running (serious? even not the webchat??!) answer to this thread and paste your URLs here
[*]Why is the time wrong in TWRP?
most important: use the latest TWRP (atm of writing it has to be the latest BETA 3.1.1 sfx-14). This has been fixed several times on our journey for different ROMs and their versions and should work for STOCK (up to N) and on any custom ROM now very well.
if you still encounter issues: set the time zone correctly in TWRP once. then reboot into TWRP and it should be still the correct time
if you still encounter issues: scroll up to FAQ #4 A) and pull the recovery log and attach it to your post.
For reference here the previous explanations (when using the latest TWRP no actions are required anymore!! even when switching between STOCK and custom ROMS !)
Before CM12.1:
Time setting was handled with the proprietary qcom time_daemon which was responsible to save a time offset of the qcom RTC (Real Time Clock). This time_daemon gets the time from the RTC and save the offset to the current "real" system time in either /data/time or /data/system/time. That means it SHOULD work out of the box for you but as you're reading this it may not.
Since CM12.1 and newer:
The proprietary time_daemon was completely replaced with an open-source alternative provided by sony: "timekeep".
The main principal is the same: the time gets read from the RTC and then gets not written to files in the file system but instead a persistent property is written (timekeep save) each time the time or timezone changes or when Android shuts down. This property is then read at the next boot again by timekeep (timekeep restore).
The handling of timekeep is fixed since build 127 of this twrp version / official 3.0.2-1 version so it should just work for you if you have that build running (or newer).
Stock ROMs:
Stock ROMs or stock based ones like Imperium ROM uses the proprietary qcom time_daemon. That means it SHOULD work out of the box for you but as you're reading this it may not.
When you had read the above and it states it SHOULD work for you but it doesn't:
Boot into twrp:
Menu Mount: select Data to get it mounted
On your PC:
adb shell rm /data/system/time/ats_2
adb shell rm /data/time/ats_2
adb shell rm /data/property/persist.sys.timeadjust
One of the above adb cmds may fail but that doesn't matters.
Now reboot into recovery again and the time should :fingers-crossed: be fine.
If the above give you NOT the correct time:
Please follow all steps of the above FAQ #5 and additionally also give an output of the following cmd while in twrp:
adb shell mount /data
adb shell ls -la /data/time /data/system/time
[*]Does this build supports F2FS?
Yes
[*] Why are some builds about ~50% smaller then other versions of twrp for these devices?
TWRP builds with more than 30 MB contain an uncompressed kernel image and support both bootloader versions : MM and LL
TWRP builds with about 16 MB contain a compressed kernel image and will run with MM bootloader only. As soon as I found out that this was the reason for not booting TWRP on LL devices I reverted the compression to support both again
btw the kernel is build with UBER tool chain
so the short answer is just "compression".
[*]Unlocking? Rooting?
official unlock (h811, h815 EUR) http://forum.xda-developers.com/g4/general/unlock-bootloader-install-twrp-root-t3128241
unofficial unlock (any G4): https://bit.do/unlockg4
[*]Don't trust TWRP for EFS backups? Do you want to have an independent backup of EFS? Do you wanna restore EFS without TWRP?
Consider to use the brand new backup method even for locked devices! DLM Backup
words in blue are commands you have to type on your PC
boot into TWRP
connect usb cable
adb shell
Backup
For the following 2 cmds: replace /external_sd by /sdcard if you have no external SD card. HINT: you have to decrypt /sdcard first if you enabled device encryption!
dd if=/dev/block/bootdevice/by-name/modemst1 of=/external_sd/modemst1
dd if=/dev/block/bootdevice/by-name/modemst2 of=/external_sd/modemst2
dd if=/dev/block/bootdevice/by-name/fsg of=/external_sd/fsg
dd if=/dev/block/bootdevice/by-name/misc of=/external_sd/misc
Restore
For the following 2 cmds: replace /external_sd by /sdcard if you have no external SD card. HINT: you have to decrypt /sdcard first if you enabled device encryption!
dd if=/external_sd/modemst1 of=/dev/block/bootdevice/by-name/modemst1
dd if=/external_sd/modemst2 of=/dev/block/bootdevice/by-name/modemst2
dd if=/external_sd/misc of=/dev/block/bootdevice/by-name/misc
dd if=/external_sd/fsg of=/dev/block/bootdevice/by-name/fsg
[*]You can't unlock your screen after you encrypted your device?
First of all: this has absolutely nothing to do with TWRP but as I encrypt always and everything I encountered a problem after encrypting my device and I just want to share you my solution:
checkout the following tool if you have the same issue described there: http://forum.xda-developers.com/g4/development/tool-lock-screen-fix-encrypted-devices-t3499478
[*]How to open/start/boot into TWRP?
You have 2 options at least:
when Android is booted:
you can do "adb reboot recovery".
Besides that many custom ROMs have a special power option or just download one of the dozens apps letting you do this
via key combo:
The only valid and always working and supported way on getting with a hardware key combo(!) into twrp is using the factory reset screen.
After installing TWRP correctly, you will still have the original LG factory reset screen/menu booting before TWRP, every time. So the correct and only way to get into TWRP is to select two times "Yes" in the official LG factory reset menu, and only then you will get into TWRP (It's a restriction by LG. There is no key combo available in some / all / most LG devices to boot directly into recovery and so TWRP).
Any other key combo like vol up + power depends on the kernel of the ROM! So it may work or not. Factory reset will work always.
If you are interested on the background why the factory reset page cannot be bypassed read on here: https://forum.xda-developers.com/g4/development/recovery-twrp-3-touch-recovery-t3442424/post72628311
For this you have to ensure that you have the latest twrp version really installed(!) because if twrp sits in recovery it will ignore the factory reset command when going through it.
Power down and pull out the battery. Do not forget to remove any USB cable.
Press power down and hold it down. Put battery back while keeping vol down pressed. Press power button and keep now both buttons pressed. When you see the LG logo the first time just release the power button for 1 second ( do not release vol down ) and then press power again and keep both pressed until you see the factory reset screen.
Once you see that screen just go through the steps like you would do a factory reset. If twrp is installed you will just open twrp without wiping any data. Again it is mandatory to have twrp installed otherwise it would really reset your device.
For the paranoid: If you want to be sure use "adb reboot recovery" when in android. When you see twrp all is fine but just do a full backup and then go through the factory reset first.
[*]What is a system IMAGE backup and why does it fail?
Using this new option is an ALTERNATIVE method to backup in opposite to the regular file based method. It is like a bit by bit backup of the COMPLETE partition which is the reason why it is much bigger as a regular backup.
So you likely will NEVER use the Image option or when you're a paranoid one only.
HINT: This method requires an ext4 or exfat partition on your external SD card otherwise image backups will fail due to the file size.
user reports success using the internal storage as target for the backup but if you do this keep in mind that you have to move that backup to your PC manually to ensure you have it by hand for the worst case.
So you may ask now why or when should I select this method? Never. So why is this option here? The main reason is TWRP in FIsH. I want to keep both device trees identical.
.

What's the pros of having a decrypted device? Is going to be smoother, faster or what?

DaarkieDoo said:
What's the pros of having a decrypted device? Is going to be smoother, faster or what?
Click to expand...
Click to collapse
+1 for this question

I'm curious what that technical talk means as well!

It's good to see progress and interest for our device. Is it possible to add dt2w like op3 here and the date and time of nandroids fixed ?

DaarkieDoo said:
What's the pros of having a decrypted device? Is going to be smoother, faster or what?
Click to expand...
Click to collapse
When you enable full device encryption in your favorite ROM or using stock without modification then your data partition is encrypted. That means no one can access your data when you shutdown your phone.
So in twrp you will see the data partition as a big 32gb unreadable partition even if 3GB are in use when you booted (and therefore decrypted) your ROM.
You CAN still backup that data partition but it will backup the whole 32GB because of encryption.
With this twrp version when started you will be asked for the decryption password and your data partition is readable as in the ROM. When you backup now the data partition it just backups the data in use so 3 GB instead of 32GB.
Regarding any pros of not using full disk encryption in your ROM I can say it doesn't matter in performance in normal cases. You will always read that disabling decryption will give you much more power and so on but the today's spec of phones are so good you will feel a slightly diff only. The ONLY way to find an answer is testing on your own using the SAME ROM and same version! Once with encryption once without.
On the other hand you will get a minimum of security if you enable it but give access to everyone finding your lost phone if not! So it's up to you if you want this risk for a minimum on performance improvement.
And just for sure:
decrypting in twrp is *not* permanent it is just decrypted for backing up nothing more nothing less.
Hope that answers your question
.
Sent from my LG-H815 using XDA Labs

ufocus said:
It's good to see progress and interest for our device. Is it possible to add dt2w like op3 here and the date and time of nandroids fixed ?
Click to expand...
Click to collapse
I think that is possible without problems. I check that.
checked:
its not such easy as stated in your commit link. we do not have "touchpanel" there so we need to check what else we could choose maybe those: https://github.com/CyanogenMod/andr...mmit/d3c0189ab7384d42906eea9d521c4d591a160c2f
edit 2:
changing /sys/devices/virtual/input/lge_touch/tap2wake --> 1 (as set in CM) has no effect in twrp.. Need further research..
edit 3:
ok got it. double tap will be added in the next build
.
Sent from my LG-H815 using XDA Labs

steadfaster said:
edit 3:
ok got it. double tap will be added in the next build
Click to expand...
Click to collapse
How about the correct date and time? Is this also an easy one?
Sent from my LG G4 using Tapatalk

albuntu said:
How about the correct date and time? Is this also an easy one?
Sent from my LG G4 using Tapatalk
Click to expand...
Click to collapse
no afaik this is a bug in twrp 3 as it was not a problem as in twrp 2 but I cannot say for sure.
Can you tell me what ROM do you use? and more important: When you reboot is the time correct (directly after reboot!) or is it not correct and gets corrected when connected to the carriers network?
.

steadfaster said:
no afaik this is a bug in twrp 3 as it was not a problem as in twrp 2 but I cannot say for sure.
Can you tell me what ROM do you use? and more important: When you reboot is the time correct (directly after reboot!) or is it not correct and gets corrected when connected to the carriers network?
.
Click to expand...
Click to collapse
I'm on CM13 and yes, the time and date are always correct. I know for sure because i often reboot with flight mode enabled.
Sent from my LG G4 using Tapatalk

steadfaster said:
edit 3:
ok got it. double tap will be added in the next build
Click to expand...
Click to collapse
Now that was fast Thank you! Appreciate the effort. For now we can live with wrong date and time it's not that big of a deal.

I do not understand the whole thing.
The incorrect date is for me a Problem.
Imperium Stock ROM

HorstiG said:
I do not understand the whole thing.
The incorrect date is for me a Problem.
Imperium Stock ROM
View attachment 3852244
Click to expand...
Click to collapse
Please see the the comment of Dees_Troy and bigbiff (both main devs of TWRP):
https://github.com/TeamWin/Team-Win-Recovery-Project/issues/178#issuecomment-35728685
https://github.com/TeamWin/Team-Win-Recovery-Project/issues/238#issuecomment-28525937
--> Means the ROM have to save the time data and TWRP tries to read that. If the ROM do not save that time data TWRP can't know the time.
Well there is a flag for QCOM since some day:
https://github.com/TeamWin/android_...mits/8b9b9c5d869e57cb7857723592044028a8874f61
--> that one is set already in my build but it is still not working
I still looking through the code what the devs actually expecting maybe ... well lets see.
update:
ok so far I can say the following
The Qualcom Time Daemon (proprietary) need to be available in your ROM (e.g. not available in RR)
The time daemon has to run properly (it has to work actually)
The time daemon has to write into either /data/time/ats_* or /data/system/time/ats_*
If those are ok then TWRP will display the time correct. If not blame the ROM not TWRP..
.

I have 4 Files, but all without content.
It´s the same with Stock LG ROM (KTZ)
Have a look please
https://dl.dropboxusercontent.com/u/73964661/Time.zip

On my older Baby LG D290 the Time is OK

HorstiG said:
On my older Baby LG D290 the Time is OK
Click to expand...
Click to collapse
It may be not a device with RTC that would explain it. Or the time daemon in that rom works better/other.
HorstiG said:
I have 4 Files, but all without content.
It�´s the same with Stock LG ROM (KTZ)
Have a look please
https://dl.dropboxusercontent.com/u/73964661/Time.zip
Click to expand...
Click to collapse
The files are not empty so it should work for you afaik...
Which timezone do you live and can you join the twrp channel? That would make it easier for troubleshooting..
.
Sent from my LG-H815 using XDA Labs

steadfasterX said:
It may be not a device with RTC that would explain it. Or the time daemon in that rom works better/other.
The files are not empty so it should work for you afaik...
Which timezone do you live and can you join the twrp channel? That would make it easier for troubleshooting..
.
Click to expand...
Click to collapse
OT. Meine Zeitzone ist die gleiche als Deine. Bei TWRP G+ und xda habe nicht nur ich schon mehrmals das Problem angesprochen. Deshalb hatte ich etwas Hoffnung, dass Du...
Dann werde ich damit leben muessen.
Danke trotzdem und sorry for german
Sent from my LG-H815 using XDA Labs

HorstiG said:
OT. Meine Zeitzone ist die gleiche als Deine. Bei TWRP G+ und xda habe nicht nur ich schon mehrmals das Problem angesprochen. Deshalb hatte ich etwas Hoffnung, dass Du...
Dann werde ich damit leben muessen.
Danke trotzdem und sorry for german
Sent from my LG-H815 using XDA Labs
Click to expand...
Click to collapse
ok no I meant IRC channel thats much much better because it is a chat so much more responsive
but I want to investigate that further (I mean my nick says it all) - can you do the following when booted into Android and paste their results:
ls -la /dev/rtc0 /dev/rtc
hwclock -uw (<-- if this gives you an error let me know but continue with the next part)
ls -la /dev/rtc0 /dev/rtc (again)
Boot up in TWRP and paste the results of:
ls -la /dev/rtc0 /dev/rtc
If it is not the correct time in UTC do the above hwclock command again
reboot recovery (so reboot into twrp again)
let me know your results
I'm normally online daily so grab an IRC client like hexchat or pidgin and connect to the channel #twrp. you will see me there. If you do not want to install anything simply use the webchat here: http://webchat.freenode.net/?channels=twrp
.