{
"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"
}
LG P940 development thread
Prada 3.0
Various threads about the P940 are lingering around all over the forums.
This thread is dedicated to have all info about development process, root, custom additions, etc for the LG P940 (Prada 3.0) in one place.
Recently, I started to get some custom awesomeness going on the P940.
The current status can be seen below. Please don't ask for ETA.
Status
Clockworkmod recovery: released (http://forum.xda-developers.com/showthread.php?p=30862503)
CyanogenMod 9 (Android 4.0): released (http://forum.xda-developers.com/showthread.php?t=1973100)
CyanogenMod 10 (Android 4.1): released (http://forum.xda-developers.com/showthread.php?t=2044274)
CyanogenMod 10.1 (Android 4.2): released (http://forum.xda-developers.com/showthread.php?t=2092937)
Click to expand...
Click to collapse
Device repository: https://github.com/milaq/android_device_lge_p940
Kernel repository: https://github.com/milaq/android_kernel_lge_p940
Click to expand...
Click to collapse
fastboot access via omap4boot / install CWM, root, etc: http://forum.xda-developers.com/showthread.php?p=40694480
Click to expand...
Click to collapse
LG update tool root prodecure by Walhalla: http://forum.xda-developers.com/showpost.php?p=28568521&postcount=8
Service manual (thx to Ygrek-Ix & BigBoyPL): http://milaq.net/downloads/android/p940/EN_LG-P940_SVC_ENG.pdf
Signing keys leaked! We can now sign any boot/recovery image and even bootloaders.
http://forum.xda-developers.com/showthread.php?t=1971014
Click to expand...
Click to collapse
But either way, you can participate here to show lg what crap they were up to:
Petition to unlock bootloaders on LG Phones: http://www.change.org/petitions/lg-...opportunity-to-unlock-bootloader-in-lg-phones
P940 now fully supported in the "LG Notifications" app: https://github.com/mborjesson/LG-Op...mmit/74999b2ccfeffc1f5829cf554a24b734cd7a6955
WARNING: The following stuff is ONLY for advanced users, who know what they are doing. I take no responsibility whatsoever for raging, screaming, crying, frustration, failing, confusion, etc.
These are now update.zips. That means they can be conveniently be flashed via recovery.
Cifs module (for mounting remote shares): http://milaq.net/downloads/android/p940/cifs_p940_v20d.zip
Patched framework with power animations (CRT screen off animation when display shuts off): http://milaq.net/downloads/android/p940/framework_power-animations_p940_v20d.zip
Click to expand...
Click to collapse
Feel free to report any findings and/or contribute (e.g. pull requests, sharing thoughts or investigations).
OEM stuff
Stock images (V20d)
Recovery: http://milaq.net/downloads/android/p940/v20d-recovery.img
Boot: http://milaq.net/downloads/android/p940/v20d-boot.img
Partitions
x -> /dev/block/mmcblk0p1
u -> /dev/block/mmcblk0p2
boot -> /dev/block/mmcblk0p3
recovery -> /dev/block/mmcblk0p4
divxkey -> /dev/block/mmcblk0p5
misc -> /dev/block/mmcblk0p6
nv -> /dev/block/mmcblk0p7
fota -> /dev/block/mmcblk0p8
reserved -> /dev/block/mmcblk0p9
system -> /dev/block/mmcblk0p10
userdata -> /dev/block/mmcblk0p11
cache -> /dev/block/mmcblk0p12
system2 -> /dev/block/mmcblk0p13
fat -> /dev/block/mmcblk0p14
persist -> /dev/block/mmcblk0p15
mlt -> /dev/block/mmcblk0p16
Click to expand...
Click to collapse
Stock kdz image list: http://lg-phone-firmware.com/index.php?id_mod=14
Stock rom tweaks (v20d)
build.prop tweaks
Code:
ro.lge.capp_lockscreen
[true/false] - set to false to use the default ics lockscreen
Click to expand...
Click to collapse
Code:
ro.lge.capp_touch_scroller
[true/false] - set to false to have the default ics scrolling (fling) behaviour
Click to expand...
Click to collapse
Code:
persist.sys.sound_enable
[0,2] - 0 to disable bootsound, 2 to enable
Click to expand...
Click to collapse
service menu
In dialer enter
Code:
3845#*940#
Click to expand...
Click to collapse
cwm for prada
1. Root your phone first.
2. Dump your boot.ing and recovery.img.
dd if=/dev/block/mmcblkp03 of=/sdcard/boot.img
dd if=/dev/block/mmcblkp04 of=/sdcard/recovery.img
3. run install install-2nd-init.bat within adb env.
4. check my snapshot.
5. At this time, staill have isuue here, let's go on.
Credit wkpark. http://cafe.naver.com/androidhacker/98
http://dl.xda-developers.com/attach...3ee8733d1/50257299/1/2/5/2/5/4/4/12080006.jpg
http://forum.xda-developers.com/attachment.php?attachmentid=1252543&d=1344581863
thanks for pointing this out but unfortunately, this is a 2nd init recovery.
the whole purpose of a recovery is to not only serve as an installer/backuptool but also as a second chance if you mess something up. if you screw up your system partition your pretty much OOL.
in order to start building custom roms, we need at least a fake flash version of a recovery. but this is not possible atm because the bootloader sends "--wipe-data" on recovery boot, which ultimately results in not beeing able to apply a custom update.zip.
we need to either hack the b/l to not send any arguments (which is risky) or we need a signed recovery image which ignores the wipe-data argument.
we can then utilise 2nd init to tweak the system/serve an own initrd. but for a recovery we need the real deal.
cheers
WOW~~!
nice work!!!
:good::good::good:
well folks,
i revisited the 2nd-init recovery idea after countless efforts to circumvent the drm and writing several mails to lg internals w/o getting any further.
i'm just digging deeper into the method utilized here:
http://forum.xda-developers.com/showthread.php?t=1826378
i'll keep you posted,
cheers
I wait to cwm and cm 7 or miui based on gb
milaq said:
well folks,
i revisited the 2nd-init recovery idea after countless efforts to circumvent the drm and writing several mails to lg internals w/o getting any further.
i'm just digging deeper into the method utilized here:
http://forum.xda-developers.com/showthread.php?t=1826378
i'll keep you posted,
cheers
Click to expand...
Click to collapse
hello milaq, p940&ku5400 is opensource now. we can ge it here:
http://www.lg.com/lgecs.downloadFil...merModelCode=LGKU5400&DownFileType=opensource
hope this useful.
thanks for the headsup. any of such is much appreciated (as many stuff for the prada is in korean, chinese, etc.)
these are the opensource gpl components for the ku5400 (which essentially is the p940 for the eastern market). you can get the zips for the p940 here http://www.lg.com/global/support/opensource/opensource-detail.jsp?detailCustomerModelCode=LGP940
this includes the kernel sourcecode which allowed me to build e.g. the cifs. module.
unfortunately we are still st(r)uck with an encrypted bootloader. therefore it is not possible to boot any custom kernel atm.
Cwm is ready?
do you have plans to port cm 7 or miui?
1. yes, but i'd rather test it a bit before releasing it publicly.
2. no. gb is deprecated and i wont spend any minute on it. even ics is getting old so why should anyone would want to maintain gb if ics is up and running
1.on ~ you know when it will be made available to the CWM
2. You can enter service are init.d for scripts?
milaq said:
thanks for the headsup. any of such is much appreciated (as many stuff for the prada is in korean, chinese, etc.)
these are the opensource gpl components for the ku5400 (which essentially is the p940 for the eastern market). you can get the zips for the p940 here http://www.lg.com/global/support/opensource/opensource-detail.jsp?detailCustomerModelCode=LGP940
this includes the kernel sourcecode which allowed me to build e.g. the cifs. module.
unfortunately we are still st(r)uck with an encrypted bootloader. therefore it is not possible to boot any custom kernel atm.
Click to expand...
Click to collapse
can we have a custom rom based on the LG's kernel ?
any news?
Support! P940 has great spec with low price!
managed to write CWM for locked bt?
that is not the oc kernel?
Does anybody know if it is possible to make the light in the navigation buttons stay on when you use the phone? I think they turn out very fast.
any news mr Milaq?
Clockworkmod release (testing)
I decided that the custom recovery is ready to be released publicly.
For information and downloads see this thread:
http://forum.xda-developers.com/showthread.php?p=30862503
Related
Hello Guys !
In this thread you will find my custom Kernel for the Sony Xperia C
Please be sure to read (and re-read) this Carefull to avoid unnecessary questions.
Changelogs
Changelog Beta Test 1 and 2 (July 03 2014)
Kernel Based on Stock Sources with some few fixs (Linux 3.4.5)
(check my github for an full commit history, don't want an long Changelog here)
Compiled with Google's 4.6 ToolChain (Stock MTK ToolChain)
I made several kernel Compilations, the only difference is the Build Type and some MTK configs (Keep im mind that i don't own this phone)
I have no way to know if these will boot or not (but they should ...), you can always restore your System
Bugs
- You tell me
---> If you find bugs / issues, please provide an logcat / dmesg
Downloads
All Downloads are on the XDA dev DB
GPL Compliance:
{
"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"
}
Kernel 3.4.5
GitHub Repo
I do respect the GPL, but using someone else's work without proper credits is just LACK OF RESPECT.
The inclusion of this kernel in your ROMS is NOT allowed.
Instead add a link to my kernel thread as a recommendation on your thread.
I Don't support KANGS!
Fail to comply and i will drop this project
Credits:
superdragonpt
Sony
I would also like to thank:
bgcngm, for the MTK Unpack / Repack kernel scripts
XDA:DevDB Information
[KERNEL] [3.4.5] Xperia_C (MT6589) [03-07-2014], Kernel for the Sony Xperia C
Contributors
superdragonpt
Kernel Special Features:
Version Information
Status: Testing
Beta Release Date: 2014-07-03
Created 2014-07-03
Last Updated 2014-07-05
INFO
Mandatory Requirements
Unlocked Bootloader
CWM / CTR Recovery
FULL CWM BackUp, in case things get nasty ...
USB debugging ON (check under Settings>Developer Options) in case you get into bootloop, you can adb reboot, and get back to CWM and Restore your System
Unlocking BootLoader / Installing CWM:
You can find more info on This Thread
How to Flash
Reboot to CWM / CTR
Flash the Kernel.zip
Reserved
Reserved
WOW !!! Many Many Many thanks for your awesome contribution !!
Gonna try it out now, will report
someone find a way to unlock XPERIA C bootloader?
test 2 makes phone stuck in sony logo in bootloops. checking test 1...
edit: test 1 same think
I tried both files and I Got stock and rebooting again and again on Sony logo.
khashayar_khk said:
I tried both files and I Got stock and rebooting again and again on Sony logo.
Click to expand...
Click to collapse
same here
OK then, i assume you have the requirements? Unlock bt and cwm installed?
Where you able to get adb? If so provide the logs.
I will make another compilation today...
Regards
superdragonpt said:
OK then, i assume you have the requirements? Unlock bt and cwm installed?
Where you able to get adb? If so provide the logs.
I will make another compilation today...
Regards
Click to expand...
Click to collapse
I have the cwm but the bootloader is unlockable.I don't know adb pleas tell me more about it and I really appreciate your hard work.
Ok there's an 3rd Kernel Compilation for download.
Regards
superdragonpt said:
Ok there's an 3rd Kernel Compilation for download.
Regards
Click to expand...
Click to collapse
I tried the 3rd file same results rebooting again and again on Sony logo.
superdragonpt said:
Mandatory Requirements
Unlocked Bootloader
Click to expand...
Click to collapse
does it mean when you install CWM you unlocked the bootloader?
zenxus31 said:
does it mean when you install CWM you unlocked the bootloader?
Click to expand...
Click to collapse
I think the bootloader is steal locked az you see we can not have any kernel and if we flash a Rom we have many bugs with it such as SIM card
khashayar_khk said:
I think the bootloader is steal locked az you see we can not have any kernel and if we flash a Rom we have many bugs with it such as SIM card
Click to expand...
Click to collapse
only RIL?
zenxus31 said:
only RIL?
Click to expand...
Click to collapse
What's ril?
There's some confusion around the bootloader issue...
There are some units (check OP and the thread link) that came with an different bootloader.
The users with that bootloader, are the ones that CAN install CWM Recovery.
--> IF you can install CWM on That bootloader, it means it's UNlocked, thus enabling system RW.
(Dont forget that having root is advisable)
--> An LOCKED bootloader, haves no RW Acess, meaning you can't flash CWM/ or any other thing, since the system is write protected.
This kernel is only meant to be tested with Xperia users that own that specific bootloader.
--> This kernel is based on the official sources, and it should boot "out of the box", but since this is MTK code, i know it can be messy...
Will make some changes and upload some new compilations
BTW: Anyone with stock Rom, can upload the rom's build.prop, i'll need to check some info from there...
Regards
EDIT:
Kernel Test4 and 5 are online.
On CWM:
wipe Dalvik and then flash the kernel.zip
And please if you can do an dmesg/logcat and send it to me
khashayar_khk said:
What's ril?
Click to expand...
Click to collapse
well it is responsible for the signals of phones..
superdragonpt said:
There's some confusion around the bootloader issue...
There are some units (check OP and the thread link) that came with an different bootloader.
The users with that bootloader, are the ones that CAN install CWM Recovery.
--> IF you can install CWM on That bootloader, it means it's UNlocked, thus enabling system RW.
(Dont forget that having root is advisable)
--> An LOCKED bootloader, haves no RW Acess, meaning you can't flash CWM/ or any other thing, since the system is write protected.
This kernel is only meant to be tested with Xperia users that own that specific bootloader.
--> This kernel is based on the official sources, and it should boot "out of the box", but since this is MTK code, i know it can be messy...
Will make some changes and upload some new compilations
BTW: Anyone with stock Rom, can upload the rom's build.prop, i'll need to check some info from there...
Regards
EDIT:
Kernel Test4 and 5 are online.
On CWM:
wipe Dalvik and then flash the kernel.zip
And please if you can do an dmesg/logcat and send it to me
Click to expand...
Click to collapse
i attached the build.prop
EDIT: oops sorry i forgot to multiquote
I don't mean to crash anyone's dreams but..this phone's bootloader simply cannot be unlocked..i also installed CWM but under the service menu it still says bootloader unlock allowed:No which means no custom kernel..no kitkat ROM..
Its never going to work
This is never going to work dude... Try hacking ramdisk...several Xperia SP bootloader locked phones are getting ROMs..and installing Recovery never means that bl is unlocked or writable...
Posting this here because it seems that @Chainfire prefers to do technical work publicly, and I think we need his help.
This is the userdebug boot image for the LG G5. I also have a flashable TOT with this in it so it it is actually usable, but I (nor anyone else that I am aware of) will provide that until we have it 100% working as we don't want any possibility or rooting someone's phone. These were both provided by tungkick, so if anyone wants to donate or give thanks they belong to her (I am just the messenger for now as her english is not very good).
The userdebug boot has root enabled by default, but the system is in read-only mode (just like how the Galaxy S7 was with its eng boot). It would be EXTREMELY helpful if someone who knows what they are talking about (i.e. Chainfire) could take a look at this and talk to tungkick through Skype or PM. We also have a Skype chat and if you would like to to contribute ways to get this to work I can add you to it
EDIT: I am adding the flashable TOT with the userdebug boot.img. If you attempt to flash this PLEASE have a backup of your data in case something goes wrong!!! I believe this should work on all variants, so please post if this works for you!
*You may brick your device, break your phone, or start a nuclear war with this. I am warning you now, please take this into consideration before you go around flashing things*
{
"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"
}
Bumping this
Although you caused us to lose the main people working towards root originally, if this works I may take back my feelings about you
Can you not run
Code:
mount -o remount,rw /system
Any news with this? I want muh roots
tabp0le said:
Can you not run
Code:
mount -o remount,rw /system
Click to expand...
Click to collapse
Doesn't work, we tried... This is why we need @Chainfire help. We think is has to do with modifying the actual SU binary
Nathamio said:
Any news with this? I want muh roots
Click to expand...
Click to collapse
Lol so do we. I promise we will keep you updated!
I just want to thank everyone who has been working on rooting our device. If I had a way to contribute I would, but sadly I do not. Keep up the good work!
I thought there was root for the G5 available already?
mkdr said:
I thought there was root for the G5 available already?
Click to expand...
Click to collapse
Only for certain models (T-Mo and H850 international in Europe). This could mean we can root all models.
I hope root will come to the H860 . C'mon @Chainfire, I'm sure you can find the key easily ^^
It's really a great phone, but I'm missing the good optimizations we can have with root...
YassGo said:
I hope root will come to the H860 . C'mon @Chainfire, I'm sure you can find the key easily ^^
It's really a great phone, but I'm missing the good optimizations we can have with root...
Click to expand...
Click to collapse
me too waiting for root. @Chainfire
please make it happen
Guys, please stop summoning him. He has been asked already.
It is actually the userdebug kernel, not eng. Fixed that.
Honestly Annoying said:
It is actually the userdebug kernel, not eng. Fixed that.
Click to expand...
Click to collapse
Ah, hmmm. Again, I might be talking out my buthole but.....
If this is a user-debug build, ADB commands that didnt work before might work now no? An enginering build would have root by default but a user debug build might have enough for you to push through & use commands that might not work on a normal build.
For example, Have you guys tried to use 'adb disable-verity' on this build? Pushing SU for root would be easy at this point no?
JF-GINO said:
Ah, hmmm. Again, I might be talking out my buthole but.....
If this is a user-debug build, ADB commands that didnt work before might work now no? An enginering build would have root by default but a user debug build might have enough for you to push through & use commands that might not work on a normal build.
For example, Have you guys tried to use 'adb disable-verity' on this build? Pushing SU for root would be easy at this point no?
Click to expand...
Click to collapse
You are 100% correct, but in order to do that we have to run the system as userdebug also.
When we put the userdebug kernel inside the userdebug TOT, it gives a bootloop. This is because on a standard user build the data is set to encrypt, while userdebug is unencrypted. Since our userdebug system is TECHNICALLY a user system (all we did is change the build.prop to userdebug), it throws a bootloop. If we can get past that then we would be good to go and everything would work, such as disabling dm-verity and then pulling that dm-verityless boot.img and pushing it regularly.
Honestly Annoying said:
You are 100% correct, but in order to do that we have to run the system as userdebug also.
When we put the userdebug kernel inside the userdebug TOT, it gives a bootloop. This is because on a standard user build the data is set to encrypt, while userdebug is unencrypted. Since our userdebug system is TECHNICALLY a user system (all we did is change the build.prop to userdebug), it throws a bootloop. If we can get past that then we would be good to go and everything would work, such as disabling dm-verity and then pulling that dm-verityless boot.img and pushing it regularly.
Click to expand...
Click to collapse
Wait,. so if the kernel already has encryption disabled,. then Im not sure where the problem is. Encription is not on the Rom level, its located in the ramdisk on of the kernel.
Maybe you should :
A) flash your TOT
b) then push your kernel
c) then 'fastboot format userdata' - wipe it,
reboot and see if it takes?
Or is there encryption or a hash check in the bootloader?
Also, what are you adding to your build.prop?
ro.secure=0
ro.debuggable=1
ro.kernel.android.checkjni=1 ??
JF-GINO said:
Wait,. so if the kernel already has encryption disabled,. then Im not sure where the problem is. Encription is not on the Rom level, its located in the ramdisk on of the kernel.
Maybe you should :
A) flash your TOT
b) then push your kernel
c) then 'fastboot format userdata' - wipe it,
reboot and see if it takes?
Or is there encryption or a hash check in the bootloader?
Also, what are you adding to your build.prop?
ro.secure=0
ro.debuggable=1
ro.kernel.android.checkjni=1 ??
Click to expand...
Click to collapse
Do you have a skype? I would like to add you to a chat we have and explain more in depth
What model are you working on? And also how did you build a TOT? I can't find it anywhere on XDA.
JF-GINO said:
Wait,. so if the kernel already has encryption disabled,. then Im not sure where the problem is. Encription is not on the Rom level, its located in the ramdisk on of the kernel.
Maybe you should :
A) flash your TOT
b) then push your kernel
c) then 'fastboot format userdata' - wipe it,
reboot and see if it takes?
Or is there encryption or a hash check in the bootloader?
Also, what are you adding to your build.prop?
ro.secure=0
ro.debuggable=1
ro.kernel.android.checkjni=1 ??
Click to expand...
Click to collapse
Bootloader checks if the further images (boot, recovery, system) are signed digitally - if not, either it won't boot, or if the BL is unlocked, it will display a quite nice warning about the system being insecure.
Encryption check is not enforced, but if encryption is disabled WHILE userdata is encrypted, it will bootloop. Your method of wiping data should work (or flashing the TOT without userdata and formatting the device).
{
"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"
}
Team Win Recovery Project (TWRP) is an open-source software custom recovery image for Android-based devices. It provides a touchscreen-enabled interface that allows users to install third-party firmware and back up the current system, functions often unsupported by stock recovery images. It is, therefore, often installed when rooting Android devices, although it isn't dependent on a device being rooted to be installed.
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!
DOWNLOAD:
https://drive.google.com/open?id=10i5ddHcV0lt8JJ7nV1bJjqc1XXjLCp8n
Note this is just a hobby, but feel free to report bugs.
Kernel source: Prebuilt stock kernel
Boot to fastboot ( volume down and power )
in fastboot type:
Link comes later when stable
fasboot reboot and hold power up and volume
Click to expand...
Click to collapse
Note: this twrp is working with the orginal system, when ota happens just flash twrp again.
BUGS:
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
Contributors
@bassbounce ( Compiled )
@Manish4586 ( Device tree )
Device tree: https://github.com/Manish4586/android_device_xiaomi_jasmine-twrp
Source Code: https://github.com/omnirom/android_bootable_recovery/
Version Information:
Status: testing
Created 17-9-2018
Last Updated 17-9-2018
Nice! So this is supposed to work without A/B conflicts - unlike the other TWRP project?
Edit: Awesome! This works great so far. I now have permanent TWRP on my device. It updates partition details perfectly and I was able to flash Magisk without an issue.
Thanks a lot for your work!
thedisturbedone said:
Nice! So this is supposed to work without A/B conflicts - unlike the other TWRP project?
Click to expand...
Click to collapse
U are right, this twrp just boots the stock android, the other did not do that.
bassbounce said:
U are right, this twrp just boots the stock android, the other did not do that.
Click to expand...
Click to collapse
Thank you. Edited my initial post with results. This would open our device to a lot of possibilities.
I have September update, can i install this?
ki69 said:
I have September update, can i install this?
Click to expand...
Click to collapse
I dont know, i didnt test it on the september .
bassbounce said:
Yes, it should be no problem.
Click to expand...
Click to collapse
Thanks man, can you build it for mi a2 lite (daisy) ?
Touch screen don't work
After flash twrp touch screen don't work
My device rooted and install magisk
s.arthit1993 said:
After flash twrp touch screen don't work
My device rooted and install magisk
Click to expand...
Click to collapse
Try flashing stock boot img
This is work for my Mi A2 Rooted Whit Magisk V17.1 ?
Unfortunately, I'm not a developer.
Can someone compile the code and make an available download for this image, please?
Many Thanks!
MMN said:
Unfortunately, I'm not a developer.
Can someone compile the code and make an available download for this image, please?
Many Thanks!
Click to expand...
Click to collapse
same problem here, I don't know how to download or install it, I would like to try it
Adairo said:
same problem here, I don't know how to download or install it, I would like to try it
Click to expand...
Click to collapse
Fastboot flash boot file.img
Restart phone and boot in to recovery volume up and power key.
If it works please report here,
I don't know if twrp works with the September update which is pulled back.
Also I need a 6gb 128 a2 to test this.
DOWNLOAD:
Some ppl reported touch problems we look in to that
Dont download yet
nvm
wi-fi does not work
bassbounce said:
Fastboot flash boot file.img
Restart phone and boot in to recovery volume up and power key.
If it works please report here,
I don't know if twrp works with the September update which is pulled back.
Also I need a 6gb 128 a2 to test this.
Click to expand...
Click to collapse
You have changed the file. The difference is enormous. Which one is correct?
-> twrp-jasmine-0.1.img (27.276kb) -> Link removed in the cited post
-> boot.img (37.252kb) -> Link in post #1
Mi A2 6/128GB is here.
dimaxxxxx said:
wi-fi does not work
Click to expand...
Click to collapse
And yes: wifi does not work on both images
WiFi not working, help please.
Testing without wifi:
* Magisk v17.1 (via TWRP/zip) -> works
* SuperSU (via Magisk) -> works
* SELinux-Manager (via TWRP/zip) and go to permissive mode -> works
* xposed (xposed-v90.2-sdk27-beta3, via TWRP) -> bootloop - I'll try direct installation through Magisk when wifi works.
What's about error message when deleting the cache in TWRP:
unable to find partition for path '/cache'?
To all restore the stock boot.img. To fix it
We need to find a solution. Don't flash the twrp.
{
"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"
}
This kernel is (just barely a little) experimental. Use at your own risk.
Feel free to skip past the first 5 pages when reading over this thread.
This kernel assumes a few things about you, the user:
1. You have a ROG Phone 5
2. You have read all warnings and instructions
3. You are rooted (implying an unlocked bootloader)
4. You have an installation method
5. You have a backup boot image
6. You have disabled Always-on Panel
Releases will be labeled with the commit hash of their source. The newest firmware is recommended for this kernel, but not necessarily required. I am not responsible for any issues or damage caused by installing this kernel, so have a backup ready before proceeding.
Skywalker Releases
(Descending, By Date)
Downloads for : ASUS ROG Phone 5 | AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Thank you to everyone that has contributed to kernel development.
Specific credit is provided by maintaining accurate commit history.
Skywalker-I005
Skywalker-I005 has 8 repositories available. Follow their code on GitHub.
github.com
Current Kernel Improvements
CAF 5.4.166 / LA.UM.9.14.r1-18600-LAHAINA.0
CAF LA.UM.9.14.r1-18600-LAHAINA.0 CNSS
CAF LA.UM.9.14.r1-18600-LAHAINA.0 cam / vid
CAF LA.UM.9.14.r1-18500-LAHAINA.0 disp / snd
Boeffla Wakelock Blocker v1.1.0
Wireguard v1.0.20210606
Patched SafetyNet commandline
Magisk process detection patch
Disable watermark boosting
Multicolor LED / PlayStation / Nintendo HID
Tuxera ExFAT / NTFS modules
Umbrella Core [WIP] / Raccoon City
Optimization from Kirisakura / StarKissed
raccoon_city (originally written for the Shield Tablet) is a new take on "interactive" by using a combination of low latency timers and the kernel scheduler to scale more aggressively (or less, if configured that way) based on workload, in addition to capping the max inactive frequency. The purpose is to provide a balance between good battery life and performance without handicapping the device.
umbrella_core (originally written for the Note 4 and ported to hundreds of other devices) takes raccoon_city a step further with automation. In addition to the full array of user settings, this governor features a smart mode that will adjust the base values within a set range to further optimize battery and performance.
The difference between these governors and the batterysaver implementation (also available) is the lack of arbitrary caps on max values during normal use. By controlling the workload, this allows better control over when the next frequency is reached, instead of whether it is available at all.
The default configuration idles at a max of about 800 mHz, but can be configured for each cluster, much like most settings.
Restoring Stock / Rooted Boot Image
Boot / DTBO Images [Root / Stock] - 5 / Pro / Ultimate (NOT S)
These images are NOT built from source. These are the stock images from the firmware provided by Asus that are extracted with payload dumper and uploaded without modification. 18.0840.2202.231 18.0840.2201.226 18.0840.2112.211...
forum.xda-developers.com
Building / Compiling Custom Kernels
[SOURCE] ASUS_I005_1-kernel (MacOS / Linux)
WARNING: This is NOT a custom kernel! GPL requires that source is released for Android kernels. It does not, however, require that the source is tracked. https://www.asus.com/supportonly/ROG%20Phone%205%20(ZS673KS)/HelpDesk_Download/ Each...
forum.xda-developers.com
Hi! Twisterumbrella thanks for the development, how can i instalo this kernel? I dont have twrp since its not developed, but i have that system versión as well as unlocked no and root. I Will be glad to test when i have a proper way yo installing this.
Thanks!!
Can you provide me a .IMG file instead. For fastboot flash boot
Thx
Therazorsedge said:
Can you provide me a .IMG file instead. For fastboot flash boot
Thx
Click to expand...
Click to collapse
I would thoroughly recommend waiting for a final release
twistedumbrella said:
I would thoroughly recommend waiting for a final release
Click to expand...
Click to collapse
Release wen
Obsolete post. Please disregard.
twistedumbrella said:
As it stands, the V18.0830.2101.86 kernel will cause a bootloop on the newest firmware, bot older firmware is untested. This is not to say the kernel will not function on the corresponding firmware, which is why it is being released.
This kernel assumes a few things about you, the user:
1. You have a ROG Phone 5
2. You are capable of reading
3. You are rooted (implying an unlocked bootloader)
4. You have an installation method
5. You have a backup boot image
If anyone is still on V18.0830.2101.86 and knows what they are doing, the package is attached to test out. Again, you should have a backup boot image handy.
Note: A patched WW-18.0840.2103.26 boot image has been attached in case of emergency. It was made with a Tencent device, so results may vary.
Should it be determined that the build works on older firmware, we know we are waiting on source updates from Asus and I can start pressuring them to publish it.
Should the kernel also fail on older builds, then I will know I need to take another look at the build process and see where it went wrong.
StarKissed/StarKissed_I005_1
Contribute to StarKissed/StarKissed_I005_1 development by creating an account on GitHub.
github.com
Click to expand...
Click to collapse
Hallo
Flashed your kernel and after restart my devices get into reboot wich I could not come out of. When I try flash my saved boot.img my device not connect to adb command like before (sound from pc confirm connection).
Checked and found a dive is missing but QUALcom USB 1.1 is drives installed. Any advice?
Thanks for kernel, but after installed the kernel I come into a boot loop. So I went into fastboot mode for flashing my saved patched boot.img.
But my Rog did not connect to my PC in fastboot mode. I can see that an Android drive missing (attached file) and installed QC drives but still no connection. Solution?
Before I installed kernel there was no problem with ADB/USB connection my Rog.
Obsolete post. Please disregard.
twistedumbrella said:
V18.0830.2101.86?
Unlocked bootloader?
Magisk installed and working?
Click to expand...
Click to collapse
Yes!
Obsolete post. Please disregard.
ltth said:
Yes!
Click to expand...
Click to collapse
twistedumbrella said:
V18.0830.2101.86?
Unlocked bootloader?
Magisk installed and working?
Click to expand...
Click to collapse
Fixed!! I had to, install this file first "android_winusb" then Android ADB drives.
Obsolete post. Please disregard.
ltth said:
Fixed!! I had to, install this file first "android_winusb" then Android ADB drives.
Click to expand...
Click to collapse
I better checked my system version and it`s V18.0840.2103.26 and tried to install the kernel via EX-kernelmanager with no success. BootLoop.
Sent in a support ticket casually reminding Asus of the GPL for the kernel. Hopefully it doesn't take too much longer to publish updated source.
ROG Phone 5 - Support
www.asus.com
Asus has just released new firmware and source for V18.0840.2104.47
The next kernel release will require updating to V18.0840.2104.47
twistedumbrella said:
ROG Phone 5 - Support
www.asus.com
Asus has just released new firmware and source for V18.0840.2104.47
The next kernel release will require updating to V18.0840.2104.47
Click to expand...
Click to collapse
I have unlocked bootloader and rooted with LSposed installed. Wont i the get this update in settings?. Do i have to manually apply this update? just a doubt whether to wait till i recieve the update notification or shall i go ahead with manual update
i am on WW_18.0840.2103.26 firmware. Thanks in advance
Obsolete post. Please disregard.
twistedumbrella said:
That was just announcing that the source has updated for the current firmware.
Click to expand...
Click to collapse
Thanks for the info.
But just now i came to know that once unlocked i wont get any software update notification. So i have to manually update
Team Win Recovery Project
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"
}
Code:
Disclaimer:
I am not responsible about any damage of any kind that this custom binary may cause.
Please pay attention to this post & related ones before proceeding and follow the guide correctly. I will not offer support for any issues that have been already stated.
Your Knox Warranty Bit will be blown once you flash this or others custom binaries, preventing you to use Knox features. It can't be resetted in any way, so think twice before flashing this.
Bugs can be reported here in XDA or via the community's Telegram Group. Please be more clear as possible and make sure you provide detailed info when reporting bugs.
How do I flash and set it up correctly?
Please notice that the following guide is meant for full stock devices, if you've already rooted your device you can skip it and flash directly the recovery without any extra steps.
Before starting, make sure to backup all your data and important files stored in your phone, since this procedure will format your data partition.
Download Odin3, Samsung's Android USB Drivers, the latest TWRP's tar and a disabled vbmeta image.
Make sure your phone's bootloader is unlocked, follow the guide below in case it isn't:
How to unlock bootloader ?
Open the Settings app, enter Developer Options and enable OEM unlocking (If you don't see Developer Options, enter into About phone>Software info and tap "Build number" 10 times to show it).
Enter Download Mode: to do so power off your device, connect it to a computer via an USB cable and hold both volume up and volume down buttons.
Long press volume up to unlock the bootloader. This will wipe your data and your phone will automatically reboot.
Go through the initial setup. Skip through all the steps since data will be wiped again later. Make sure to connect the device to Internet during the setup.
Enter Developer Options and check that the OEM unlocking option exists and is grayed out. This means our bootloader is unlocked and your phone has no KnoxGuard lock set.
How to install ?
Connect your phone to your PC and boot in Download Mode (power off your device and hold both volume up and volume down buttons).
Open Odin3, select the TWRP tar by clicking the "AP" button and the patched vbmeta tar by clicking "USERDATA", then press the Start button.
Reboot your phone in recovery mode: while it still plugged in your PC, hold both the power and volume up buttons.
Once TWRP has booted you need to format again your data partition in order to be able to boot in system again. To do so touch Wipe>Format Data and follow the instructions in screen.
Bugs:
-
Thanks:
TWRP team
- Samsung opensource kernel
- @BlackMesa123 for device tree and kernel Samsung Galaxy A52s.
Sources:
- Kernel tree : https://github.com/samsung-778/android_kernel_samsung_sm7325/tree/twrp-12.1
Changelog: 11/05/2023
- Support Android 13 decrypt with no password
CHECK LINK LAST ON POST
Hello
nguyenhung9x2018
could you let me know if i can use these files for galaxy m625f as i am not finding anything on the subject for this model, could you help me with this? Thank you very much in advance
rickgermano said:
Hello
nguyenhung9x2018
could you let me know if i can use these files for galaxy m625f as i am not finding anything on the subject for this model, could you help me with this? Thank you very much in advance
Click to expand...
Click to collapse
Samsung Open Source
opensource.samsung.com
Great to see the development got started for the Galaxy A73! Eagerly looking for more under specified forum!
nguyenhung9x2018 said:
Samsung Open Source
opensource.samsung.com
Click to expand...
Click to collapse
Hello! Thanks for the link , but this zip I can do the installation by odin ?
rickgermano said:
Hello! Thanks for the link , but this zip I can do the installation by odin ?
Click to expand...
Click to collapse
it is tar, you can install it with odin
How do I disable vb meta?
Update link download vbmeta disable
nguyenhung9x2018 said:
Update link download vbmeta disable
Click to expand...
Click to collapse
Any updates on decryption?
Are we going to have any Custom ROMs for this phone?
n0tluke192 said:
Are we going to have any Custom ROMs for this phone?
Click to expand...
Click to collapse
i think no, cuz it uses f2fs
xS1lent said:
i think no, cuz it uses f2fs
Click to expand...
Click to collapse
I build rom custom for a73xq , it booted, but RIL broken
nguyenhung9x2018 said:
I build rom custom for a73xq , it booted, but RIL broken
Click to expand...
Click to collapse
Excuse me, but how do YOU create a custom ROM? If the DATE section is not decrypted???Tell me how is this possible???
kissa67zwi said:
Excuse me, but how do YOU create a custom ROM? If the DATE section is not decrypted???Tell me how is this possible???
Click to expand...
Click to collapse
its because of f2fs and encryption im working with a very lovely dev hes helping me decrypt theres an issue with this recovery might have to rebuild and see but for now if you want to use twrp on oneui5 you can use android 12 bootloader (flash via) i dont recommend this as stuff like vaultkeep will be broken
Cockat0o said:
its because of f2fs and encryption im working with a very lovely dev hes helping me decrypt theres an issue with this recovery might have to rebuild and see but for now if you want to use twrp on oneui5 you can use android 12 bootloader (flash via) i dont recommend this as stuff like vaultkeep will be broken
Click to expand...
Click to collapse
thank you for your efforts, and with respect to YOU and YOUR friend- I will look forward to YOUR efforts and updates.....I'm just using LIGICK now and it works..... I have UI5, but I'll wait for DATA decryption
Any custom kernel available?
So can mount r/w
rajnimal nimal said:
Доступно ли какое-либо пользовательское ядро?
Так можно смонтировать r/ w
Click to expand...
Click to collapse
вроде бы ещё пока нет
rajnimal nimal said:
Any custom kernel available?
So can mount r/w
Click to expand...
Click to collapse
There is no custom core yet... And RO2RW hasn't been made for SAMSUNG yet...I am also waiting for the issue to be resolved
Just a heads up, samsung open sourced their initial android 13 build right after they send out 2023 january security update. So they are gonna follow a build late it seems.
https://opensource.samsung.com/uploadSearch?searchValue=SM-A736
I hope to contribute to this phone's development but in it's current state I do not have enough knowledge to be useful. Once it's matured enough and I got enough taste of oneui you can be sure to see me again mate, good luck with the work ahead.