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...
Related
CWM-Based Recovery 6.0.4.7 Recovery for Xperia Z3 Compact!
Credits and special thanks to Koush and everyone else involved in Cyanogenmod project!
[ info ]
This Recovery is built from CWM 6.0.4.7 sources!
[ PROOF ]
{
"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"
}
[ credits / special thanks ]
Koush - for the brilliant work & coding on CWM recovery
CyanogenMod and FreeXperia Team (especially jerpelea) for too many things *
special thanks to @Androxyde for pointing me to the correct tools and thanks to @[NUT] for the kitchen which works well to slice the kernel.sin
special thanks to @Joe_Mama [a.k.a.: Stinky sweet from 4pda ]for helping out with testing and risking his devices for the sake of development!!! and NO, his phone was NOT damaged during testing
ME for creating this for u guys!
[ Requirements ]
Bootloader unlocked
working fastboot
STOCK ROM FW:
4.4.4
23.0.A.2.105 - v01
or ROMS BASED ON THAT FIRMWARE
[ features ]
standard CWM recovery 6.0.4.7!
init.d startup script support inbuilt!
kernel is insecure (ro.secure=0)
disabled kernel level RIC
adb debugging is enabled by default in OS
TIP: if u are experiencing very slow backup in CWM do this
[ WARNING ]
FOR NOW WE DONT HAVE ROOT ON LOCKED BOOTLOADER!!! IF YOU WANT TO PRESERVE YOUR TA DATA/DRM KEYS THEN DO NOT UNLOCK BOOTLOADER!!!!
for flashing this kernel you WILL NEED TO UNLOCK BOOTLOADER! Check this thread for more info (same steps as Xperia Z1 are used for Xperia Z3 Compact)
UNLOCKING BOOTLOADER WITHOUT TA BACKUP WILL LEAD TO IRREVERSIBLE LOSS OF DRM KEYS!!!
Sony has changed their bootloader unlock policy:
Certain pre-loaded content on your device may also be inaccessible due to the removal of DRM security keys. For high-end devices running recent software versions, for instance Xperia Z3, the removal of DRM security keys may affect advanced camera functionality. For example, noise reduction algorithms might be removed, and performance when taking photos in low-light conditions might be affected. The secure user data partition may also become inaccessible, and you will not be able to get any more official software upgrades if you unlock the boot loader.
Click to expand...
Click to collapse
Source: http://developer.sonymobile.com/unlockbootloader/unlock-yourboot-loader/
[ known issues ]
adb is not working in recovery (can be fixed later)
[ how to flash this kernel ] (via fastboot)
download the kernel image
save the boot.img to the folder containing fastboot binary
flash the boot.img using fastboot:
Code:
fastboot flash boot boot.img
reboot from fastboot
Code:
fastboot reboot
the device should now start booting
enjoy!
[ how to enter recovery ]
when you see the Sony logo and the LED light turns pink/amber/orange keep tapping/pressing VOLUME UP key
[ how to Root ]
for instructions on how to root please check this post
[ sources ]
https://github.com/DooMLoRD/android_device_sony_honami
for now recovery is same is same as honami
[ donations ]
Please do consider donating as I am thinking of getting the Z3 or Z3 Compact (not yet decided which one), if you want me to support this device then feel free to donate and help me buy it!
if u feel that this work has helped u OR u think that the work i put into making this is worthy of donations, then click on the following link for buying me some coffee/beer/etc
PAYPAL DONATION LINK
OR
you can buy one of my awesome apps from Play Store!
[ download links ]
PLEASE DO NOT MIRROR, REDISTRIBUTE, REPACK MY FILES
NEW:
Advance Stock Kernel with CWM Recovery v01 (FW: 23.0.A.2.105)
MD5HASH: 2f98c39bf48102dcbd7e4d106f05360f
OLD:
...
enjoy!!!
Rooting Instructions
[ how to root ]
once you have flashed the kernel from the 1st post
download the latest SuperSU update.zip from: http://download.chainfire.eu/supersu
save it on sdcard of device
reboot into recovery
flash the supersu update.zip
reboot from recovery into OS
you should now get proper root access!
[ installing busybox ]
it is highly recommended to install busybox after rooting!
just go to andorid play store and download the busybox installer.
once the installer is downloaded, install busybox in /system/xbin
reboot device after install and thats it!
regards,
DooMLoRD
Great news - thanks!
Great many thanks [emoji1]
EDIT* NM figured it out 10 seconds after posting this, of course
Welcome back @DooMLoRD
Can we expect any DoomKernel for this device? Would be great.
Thanks for the root :good::good:
I'll wait till we can back-up our TA-partition tho
Thank you DooMLoRD!!
Thanks doomlord for the quick response.
Does anyone have an idea of how long we might have to wait to be able to back up TA-partition?
Thanks, mate! My D5833 is still on 23.0.A.2.93, can I use this as well?
Ooooops, wrong topic. My bad.
And it begins!
Best news to wake up to
Thanks DooMLorD!
Sent from my D5803 using Tapatalk
Hm..
Have installed CWM -> worked
Installed supersu over CWM -> worked
But no supersu in app drawer and also busybox can not be installed -> no root privileges !?
Any suggestions?
BR
Edit:
Solution -> Installed SuperSu from playstore
Nice job.
Can we clarify (for the new and inexperienced of us).
- Unlocking the bootloader will bugger things like the Bravia-engine
- Is it possible to get root without unlocking the bootloader?
Dashers said:
Nice job.
Can we clarify (for the new and inexperienced of us).
- Unlocking the bootloader will bugger things like the Bravia-engine
- Is it possible to get root without unlocking the bootloader?
Click to expand...
Click to collapse
1. We don't know what unlocking does yet. Camera and display features all appear to still be working according to various posts but I'm not confident of that yet.
2. Nope, and potentially won't be for quite a while (months).
Firstly thanks a lot doomlord! I'm literally on my way to receive my z3c now
But does anyone know if updates will still ve available if I root and unlock but still use stock rom?
Thank you Sir!
tacocats said:
Firstly thanks a lot doomlord! I'm literally on my way to receive my z3c now
But does anyone know if updates will still ve available if I root and unlock but still use stock rom?
Click to expand...
Click to collapse
Perhaps not OTA but you can simply flash the ftf updated firmware files through flashtool. So in essense yes you can still update stock firmware updates.
Hey its you again haha thanks
:sly:
Knowledge is power
Share that sh!t my motto
Enjoy
{
"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
yo, can someone help or answer me. I can't seem to find any official/unofficial version of twrp for sm-j415gn/ds. Does anyone have any link?
lamawkalabaw said:
yo, can someone help or answer me. I can't seem to find any official/unofficial version of twrp for sm-j415gn/ds. Does anyone have any link?
Click to expand...
Click to collapse
https://forum.xda-developers.com/f/samsung-galaxy-j4-roms-kernels-recoveries-ot.8287/
There is one here.
ashyx said:
Unofficial release -TWRP recovery for the Galaxy J4 plus 2018 - SM-J415 MSM8917
{
"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"
}
TWRP 3.3.1-0 Released
May 22, 2019
TWRP 3.3.1-0 is out now for most currently supported devices.
What's new in 3.3.1-0:
* Fix selinux issues during formatting - dianlujitao
* Various fixes for toybox and toolbox builds - CaptainThrowback and bigbiff
* Flash both A and B partitions when installing a recovery ramdisk - Dees_Troy
* Add option to uninstall TWRP app from /system - Dees_Troy
* Create digest for subpartitions - bigbiff
Want to get notifications when we release new versions of TWRP? Install the TWRP app and select your device!
We need your help! The bulk of TWRP work is done by a handful of 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!
Update - 17/8/2019
TWRP 3.3.1-1 OO/PP build released
Current status - Beta
Treble supported
Bugs: brightness slider
You flash this at your own risk. Please ensure you have the stock ROM to hand downloaded from SAMMOBILE in case of problems. This will trip the knox counter.
NOTE: ON ANDROID 5.1.1> DEVICES IT IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
*****INSTALL INSTRUCTIONS:*****
Flash with ODIN in the AP slot.
1. Put your device in DOWNLOAD mode.
(Plug in the USB cable and then hold POWER + VOL DOWN + VOL UP)
2. Load the respective file below into the AP slot, uncheck Auto-reboot(not required for twrp_3.3.1-1) and hit start.
twrp_3.2.3-1_sm-j415f_30319
twrp_3.3.1-1_j415x_17819
3. After flashing and ODIN reports PASS immediately force reboot to recovery. (Not required for twrp_3.3.1-1 as it should auto reboot to recovery). You should now see TWRP recovery.
Do NOT let the device boot to the OS.
4. Flash the V3 RMM bypass zip
https://forum.xda-developers.com/showpost.php?p=79745844&postcount=627
NOTE: FAILURE TO FOLLOW THE STEPS ABOVE IMPLICITLY WILL RESULT IN STOCK RECOVERY REPLACING TWRP AT FIRST BOOT AND BECOMING RMM LOCKED FOR 7 DAYS.
I ALSO SUGGEST BACKING UP ANYTHING YOU NEED ON INTERNAL STORAGE. AT SOME POINT YOU MAY EXPERIENCE A 'VERIFICATION FAILED MESSAGE' .
THIS IS NORMAL, BUT WILL REQUIRE THE DATA PARTITION TO BE FORMATTED IN TWRP.
5. Reboot to TWRP (Do not boot to the OS yet)
***** ROOT INSTRUCTIONS:*****
OREO ONLY
1. Flash the Forced encryption disabler patch. This is only required if you wish to have full functionality in TWRP.
Flashing this will disable Samsung's forced encryption. Disabling encryption will allow TWRP to mount the data partition.
After flashing the patch it is necessary to *FORMAT* (not wipe) the /DATA partition using the FORMAT DATA button under the wipe options.
PLEASE NOTE THIS WILL DELETE EVERYTHING ON INTERNAL STORAGE AND FACTORY RESET THE DEVICE, SO BACK UP ANYTHING YOU WISH TO KEEP.
J4+J6+_oreo_forced_encryption_disabler
2. To root I suggest installing the latest Magisk beta as this is a currently supported project, SuperSu is no longer getting active development.
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
(NOTE: The DEFEX patched Oreo kernel below may be needed for full root support if certain apps do not work with root):
https://androidfilehost.com/?fid=1395089523397921797
3. Enjoy your rooted device.
PIE ONLY
1. Due to some new securities in Samsung's latest Pie kernels, root will not work with the stock kernel. The patched kernel below is required to gain root on Pie.
Features:
Dmverity, proca, five and defex disabled.
OTG and NTFS file system support.
Selinux permissive switchable.
This kernel may require the U4 bootloader.
(NOTE: flashing a custom kernel on PIe breaks the lockscreen. Ensure NO lockscreen is enabled before installing the kernel.)
J415FXXU4BSF7_patched_boot_318919
2. To root I suggest installing the latest Magisk beta as this is a currently supported project, SuperSu is no longer getting active development.
https://forum.xda-developers.com/app...mless-t3473445
3. If you wish to have access to internal storage /DATA in TWRP then encryption will need to be disabled. See step 1 of the Oreo root instructions then instead of installing the J4+J6+_oreo_forced_encryption_disabler install the zip below with TWRP:
Disable_Dm-Verity_ForceEncrypt_Quota_08.02.2019
3. Reboot.
The device will take a good 10 mins to boot first time.
Enjoy your rooted device.
DEVICE TREE: soon
PLEASE DO *NOT* DIRECT LINK TO THESE FILES. PLEASE LINK TO THIS POST
Credits: Me, my tester @kapmino269 [MENTION=6037748]Zackptg5 for the DM-VERITY & FORCEENCRYPT DISABLER @teamwin, @corsicanu for RMM V3 bypass zip.
Please note I don't own this device and spend a lot of my free time bringing these builds for you to use and benefit from.
FEEDBACK IS APPRECIATED PLEASE.
THANKS.
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
Click to expand...
Click to collapse
Here.
Kenora_I said:
Here.
Click to expand...
Click to collapse
yo thanks, but is it compatible for my model? i really am confused because i don't know if j415gn/ds and j415gn are the same.
lamawkalabaw said:
yo thanks, but is it compatible for my model? i really am confused because i don't know if j415gn/ds and j415gn are the same.
Click to expand...
Click to collapse
Lol there isnt a j415gn
Just the j415gn/ds
Anyway they are the same phone nonetheless but ive given the one specific to your phone
The devs dont put /ds for convenience probably.
Kenora_I said:
Lol there isnt a j415gn
Just the j415gn/ds
Anyway they are the same phone nonetheless but ive given the one specific to your phone
The devs dont put /ds for convenience probabl
Click to expand...
Click to collapse
Kenora_I said:
Lol there isnt a j415gn
Just the j415gn/ds
Anyway they are the same phone nonetheless but ive given the one specific to your phone
The devs dont put /ds for convenience probably.
Click to expand...
Click to collapse
gee, i owe you a lot man. I just wanted to get the best out of this phone since I'm just a student and broke. I am very nervous that i might hardbrick this since it's my only phone. Anyways, thanks again dude.
lamawkalabaw said:
gee, i owe you a lot man. I just wanted to get the best out of this phone since I'm just a student and broke. I am very nervous that i might hardbrick this since it's my only phone. Anyways, thanks again dude.
Click to expand...
Click to collapse
LOL IM NOT A DUDE
But yeah no issue lol
i kinda do this for fun anyway
i just like helping around
Yeah i hate dem hard bricks. Ive had phones become paperweights, but i seem to unbrick them in the end
Kenora_I said:
LOL IM NOT A DUDE
But yeah no issue lol
i kinda do this for fun anyway
i just like helping around
Yeah i hate dem hard bricks. Ive had phones become paperweights, but i seem to unbrick them in the end
Click to expand...
Click to collapse
lmao I'm sorry and thank you
i might ask for your help again if i had any problems.
lamawkalabaw said:
lmao I'm sorry and thank you
i might ask for your help again if i had any problems.
Click to expand...
Click to collapse
Sure! Ill be here.
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.