I love DooMKernel by DooMLoRD , but he does not have Z3 (also Z3 Compact).
So I started to port DooMKernel for Z3 and Z3 Compact.
Please do not ask me to add something, I don't know much about kernel and git right now...
{
"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"
}
* banner by MysticEnforcer
View attachment 2995202
View attachment 2995203
juggly.cn and other Japanese website - please do not use this thread as a source.
I have Japanese post at androplus.org
Download from official website
Changelog
What is FOTA kernel recovery?
NOTE: this is old info
Xperia doesn't have recovery partition for user,
but we have FOTA kernel partition for OTA.
Since we have to unlock bootloader and OTA won't work on unlocked,
we can re-use useless FOTA kernel as recovery partition using Dees-Troy's "extract_elf_ramdisk".
With FOTA kernel recovery, you can update your recovery without updating kernel.You can flash images to FOTA kernel by fastboot command like
Code:
fastboot flash recovery fotakernel.img
To enter into FOTA recovery, press power key when LED is on.
How to restore DRM functions?
When you unlock bootloader you will lose X-Reality, noise reduction and so on,
but you can restore them!
Original thread is here, but I updated steps for Z3 and Z3 Compact.
1. Download zip from original thread
* Choose KitKat version (for 4.4) or Lollipop version (for 5.0)
2. Place zip in internal or external storage of your device
3. Reboot into recovery and do Factory Reset
4. Reboot into flashmode and flash FTF with Flashtool
Any FTF is OK, but of cource use FTF for same version you are using now.
Wipe: Check APPSLOG and CACHE
Exclude: Don't check
5. Close Flashtool, unplug and plug your phone and reopen Flashtool, then relock bootloader
Click BLU icon to show relock button and click it.
6. Flash FTF (same as 4.)
7. Close Flashtool, unplug and plug your phone and reopen Flashtool, then unlock bootloader
Click BLU icon to show unlock button and click it.
8. Reboot into fastboot mode and flash my kernel
9. Reboot into recovery and install DRM Restore zip
10. Reboot
11. Done!
After doing this, do not restore old data since it will revert DRM restore.
You can restore system with recovery and use Titanium Backup or something to restore app data.
Note: When you flash new ROM (not kernel), you must flash DRM Restore zip.
If you get "net::ERR_NAME_NOT_RESOLVED" when connecting xda,
please disable PrototypeProtection with Titanium Backup or something similar.
How to use F2FS?
Read this:
http://forum.xda-developers.com/xperia-s/s-development/tutorial-migrate-filesystem-to-f2fs-ext4-t3004755
Kernel sources
https://github.com/WedyDQ10/android_kernel_sony_msm8974ac
I should learn how to use git before creating custom kernel...
Credits
DooMLoRD
Faux123
Dees_Troy & TeamWin
Phil3759
Myself5
glocklee
pec0ra
and many other people involved in Z3 development
DO NOT talk about rooting with locked bootloader here.
XDA:DevDB Information
AndroPlusKernel for Z3 Compact, Kernel for the Sony Xperia Z3 Compact
Contributors
AndroPlus, [#APK_cont]
Source Code: https://github.com/WedyDQ10/android_kernel_sony_msm8974ac
Kernel Special Features:
Version Information
Status: Stable
Created 2014-12-28
Last Updated 2016-04-09
great! can't wait to test it... i'll see what the result is
Thanks for this. Also, I donated to Doomlord lately, in the hope he might end up buying a Z3C (and also just a general thank you for all he's done for the Android development community).
AndroPlus said:
I love DooMKernel by DooMLoRD , but he does not have Z3 (also Z3 Compact).
So I started to port DooMKernel for Z3 and Z3 Compact.
Please do not ask me to add something, I don't know much about kernel and git right now...
View attachment 2995202
View attachment 2995203
juggly.cn and other Japanese website - please do not use this thread as a source.
I have Japanese post at androplus.org
Features
Fixed entering to recovery -v4
CPU OverClock upto 2.89GHz -v3
Intelli-Plug driver v3.8 -v2
Intelli-thermal v2 -v2
Intelli-KSM -v2
Sound Control driver v3.6 -v2 [Not working]
PowerSuspend drivers -v2
Force FastCharge -v2
kernel level Color Control -v2
kernel mode NEON -v2
msm_cpufreq_limiter "Snake Charmer" -v2
per-core overall stats -v2
NTFS R/W support -v2
I/O schedulers -v2
BFQ
FIOPS
CPU governor (Some are not tested) -v2
Intelli-active
LionHeart
SmartAssV2
LagFree
Wheatley
Disabled ric -v1
CWM -v1
TWRP Recovery -v1
PhilZ touch recovery -v1
CPU OverClock upto 2.8 GHz -v1
GPU OverClock -v1
CPU Undervolting -v1
SIO I/O scheduler -v1
Requirements
Xperia Z3 Compact [D5803 & D5833]
stock 4.4.4
23.0.A.2.105 or .93 -v1~
DO NOT use this kernel with CM or CM based ROM.
This kernel is only for stock or stock based ROM.
Unlocked bootloader
Apps such as FauxClock
Download
v4 - Z3 Compact D5803 23.0.A.2.105
v4 - Z3 Compact D5833 23.0.A.2.93
v3a - Z3 Compact D5803 23.0.A.2.105 (beta)
How to flash
1. Reboot into bootloader
2. Flash kernel using fastboot
Code:
fastboot flash boot AndroPlusKernel_[B][version and variant][/B].img
3. Reboot
Code:
fastboot reboot
Kernel sources
https://github.com/WedyDQ10/AndroPlusKernel_leo
I should learn how to use git before creating custom kernel...
Credits
DooMLoRD
Faux123
Dees_Troy & TeamWin
Phil3759
and many other people involved in Z3 development
DO NOT talk about rooting with locked bootloader here.
Click to expand...
Click to collapse
It doesn't work, it goes into bootloop, i couldn't even boot into cwm afterwards
i had the to reflash CWM thrugh fastboot and then i could boot my device.
firast i thought it could be related to cooperate mail, so i removed password and account
and tried to flash the kernel again, same bootloop again. so i'll wait to there is a stable one
or am i doing something wrong?
fw xxx.105 rooted with cwm on it and all kinf of other stuff
shafiq01 said:
It doesn't work, it goes into bootloop, i couldn't even boot into cwm afterwards
i had the to reflash CWM thrugh fastboot and then i could boot my device.
firast i thought it could be related to cooperate mail, so i removed password and account
and tried to flash the kernel again, same bootloop again. so i'll wait to there is a stable one
or am i doing something wrong?
fw xxx.105 rooted with cwm on it and all kinf of other stuff
Click to expand...
Click to collapse
What happened, I don’t experienced anything but seamlessly perfect… I love this kernel and my experience now in my z3c is absolutely great! Try to re download maybe you got the corrupted downloaded.
shafiq01 said:
It doesn't work, it goes into bootloop, i couldn't even boot into cwm afterwards
i had the to reflash CWM thrugh fastboot and then i could boot my device.
firast i thought it could be related to cooperate mail, so i removed password and account
and tried to flash the kernel again, same bootloop again. so i'll wait to there is a stable one
or am i doing something wrong?
fw xxx.105 rooted with cwm on it and all kinf of other stuff
Click to expand...
Click to collapse
One member confirmed it's working on his D5803 .105, so it might be corrupted download.
Please redownload from mirror (mega).
AndroPlus said:
One member confirmed it's working on his D5803 .105, so it might be corrupted download.
Please redownload from mirror (mega).
Click to expand...
Click to collapse
Indeed, I believed it is corrupted copy… for me .105, I highly recommend using this kernel, truly awesome! the graphic really works very well now, the battery perform very fine as well, I liked the new version of the cwm too! I think a lot of benefits will provide this to your z3c device, many thanks @AndroPlus you rock men! Cheers
flashed on my z3c with .105. no bootloops, haven't come across any other issues yet. I will say that my battery life seems to be lasting a bit longer. i'll keep an eye on it for the next couple of days and report back! I still haven't played with any kernel settings. thank you for porting this over!! if you have any suggestions for the kernel settings let us know!
it is working now, you guys were correct, it was a corrupt download. I could see the first file downloaded was 8mb the next one was 18mb
thank you xda members, appreciated
Thanksss
When i use Trickster to amend sound control, device reboots, anyone else get the same, also get the same when adjusting voltage, tried -25mv, same thing occurred.
Ill post a logcat shortly
Cheers
@AndroPlus
Could you please post the MD5 hash in the OP or upload the files to a site that shows the MD5 so we can confirm the file, because flashing a corrupted kernel could harm our devices.:good:
Dsteppa said:
@AndroPlus
Could you please post the MD5 hash in the OP or upload the files to a site that shows the MD5 so we can confirm the file, because flashing a corrupted kernel could harm our devices.
Click to expand...
Click to collapse
Yes please. Or a zip file will do because Winzip or 7zip usually shows error while extracting.
spida_singh said:
When i use Trickster to amend sound control, device reboots, anyone else get the same, also get the same when adjusting voltage, tried -25mv, same thing occurred.
Ill post a logcat shortly
Cheers
Click to expand...
Click to collapse
OP says sound control driver isn't working. Use undervolt at your own risk. If it rebooted, try a lower value like -5 mv
Btw how do I get into Philz recovery? Up is for CWM, down is for TWRP. found it... camera button : )
Changed to flashable zip and uploaded to BasketBuild which can show MD5
Hello, is it possible to get the stock original kernel for Z3 Compact D5803 23.0.A.2.105 img (Not modified or rooted one ) to flash it via fastboot without restoring the whole stock ROM again? Thanks!
wrwr said:
Hello, is it possible to get the stock original kernel for Z3 Compact D5803 23.0.A.2.105 img (Not modified or rooted one ) to flash it via fastboot without restoring the whole stock ROM again? Thanks!
Click to expand...
Click to collapse
You can create stock kernel flashe zip by extracting jernel.sin from ftf, then rename to boot.img and overwrite boot.img in the zip.
AndroPlus said:
You can create stock kernel flashe zip by extracting jernel.sin from ftf, then rename to boot.img and overwrite boot.img in the zip.
Click to expand...
Click to collapse
Thanks AndroPlus, but there is two files: kernel.sin and fotakernel.sin, which one, and can I flash it via fastboot after renaming to boot.mg? easier than to include in a zip and flash via recovery.
wrwr said:
Thanks AndroPlus, but there is two files: kernel.sin and fotakernel.sin, which one, and can I flash it via fastboot after renaming to boot.mg? easier than to include in a zip and flash via recovery.
Click to expand...
Click to collapse
Oh I forgot to say you have to decrypt kernel.sin (not fotakernel) with Flashtool.
You can decrypt kernel.sin by "Tools" -> "Sin Editor" and select kernel.sin, then "Extract data".
Then you can flash kernel via fastboot:
Code:
fastboot flash boot kernel.elf
AndroPlus said:
Oh I forgot to say you have to decrypt kernel.sin (not fotakernel) with Flashtool.
You can decrypt kernel.sin by "Tools" -> "Sin Editor" and select kernel.sin, then "Extract data".
Then you can flash kernel via fastboot:
Code:
fastboot flash boot kernel.elf
Click to expand...
Click to collapse
Hey AndroPlus, I did all the steps OK, but when flashing (fastboot flash boot kernel.elf) I got this error via fastboot: FAILED (remote: image is not a boot image) ?
wrwr said:
Hey AndroPlus, I did all the steps OK, but when flashing (fastboot flash boot kernel.elf) I got this error via fastboot: FAILED (remote: image is not a boot image) ?
Click to expand...
Click to collapse
hmm...I thought it can be done with fastboot, but it seems I'm wrong...
so you have to rename kernel.elf to boot.img and overwrite boot.img in zip, then install it.
Related
Here it is. Created while updating myselfe on SUS.
http://failiem.lv/u/jiuhvld
{
"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"
}
Wow? is this new version of JB Xperia go? My version is. 400 not. 100
Whats d diffirent?
frey.derico said:
Wow? is this new version of JB Xperia go? My version is. 400 not. 100
Whats d diffirent?
Click to expand...
Click to collapse
Yes its new. Governor has chainged to ondemand. Home launcher is transparent. System is faster and battery life seems to be improved.
del
Can you root it?
Does it support custom boot by munjeni for root n cwm methode guys?
Cool!! Thank you for sharing bro!!
Sent from my ST27i using xda app-developers app
netmaniack said:
Yes its new. Governor has chainged to ondemand. Home launcher is transparent. System is faster and battery life seems to be improved.
Click to expand...
Click to collapse
How to root it?
can someone confirm if munjeni's kernel works on this?
GiorgosCyprus said:
can someone confirm if munjeni's kernel works on this?
Click to expand...
Click to collapse
I try with Phantom 1.0.8 Performance kernel and succesfully rooted this ROM
1. Download this .FTF
2. Open Flashtool ( 0.9.11.0 - latest version ). Flash .ftf via Flashtool till finish
Don't forget to safe kernel.sin ( stock JB Sony kernel )
3. Switch On and do some configuration ( Setup Wizard )
4. Flash kernel via Fastboot ( select phantom performance kernel.elf as source )
5. Reboot phone
6. Do root phone by click on Unlocked Icon at Flashtool
7. Now flashtool will send restore configuration to phone, just follow the instruction from Flashtool
8. After flashtool reboot your phone, go to Superuser, and do update su binary
9. Flash kernel via Fastboot ( select Stock JB kernel.sin as source )
10. Tada...... I have 6.2.A.1.100 JB from Sony with rooted status
Ask : Why I change back kernel to JB Stock ?
Answer : With phantom kernel, PC Companion still ask me to upgrade 6.2.A.1.100. So, change back to stock JB kernel
Now I will clean some app that I didn't need for my daily use.
Abhy-Boy said:
I try with Phantom 1.0.8 Performance kernel and succesfully rooted this ROM
1. Download this .FTF
2. Open Flashtool ( 0.9.11.0 - latest version ). Flash .ftf via Flashtool till finish
Don't forget to safe kernel.sin ( stock JB Sony kernel )
3. Switch On and do some configuration ( Setup Wizard )
4. Flash kernel via Fastboot ( select phantom performance kernel.elf as source )
5. Reboot phone
6. Do root phone by click on Unlocked Icon at Flashtool
7. Now flashtool will send restore configuration to phone, just follow the instruction from Flashtool
8. After flashtool reboot your phone, go to Superuser, and do update su binary
9. Flash kernel via Fastboot ( select Stock JB kernel.sin as source )
10. Tada...... I have 6.2.A.1.100 JB from Sony with rooted status
Ask : Why I change back kernel to JB Stock ?
Answer : With phantom kernel, PC Companion still ask me to upgrade 6.2.A.1.100. So, change back to stock JB kernel
Now I will clean some app that I didn't need for my daily use.
Click to expand...
Click to collapse
Awesome but i prefer to use this Munjeni's Method
istambul said:
Awesome but i prefer to use this Munjeni's Method
Click to expand...
Click to collapse
I have try with Munjeni V3. Use boot.img as kernel to flash, but my wifi didn't work. So I try with Phantom kernel, and wifi work fine. Hope Munjeni make new Xtreme Security ( V4 maybe ) with 6.2.A.1.100 base system file.
Abhy-Boy said:
I have try with Munjeni V3. Use boot.img as kernel to flash, but my wifi didn't work. So I try with Phantom kernel, and wifi work fine. Hope Munjeni make new Xtreme Security ( V4 maybe ) with 6.2.A.1.100 base system file.
Click to expand...
Click to collapse
I don't know exactly but my wifi is working fine, just follow step by step munjeni's OP
Abhy-Boy said:
I have try with Munjeni V3. Use boot.img as kernel to flash, but my wifi didn't work. So I try with Phantom kernel, and wifi work fine. Hope Munjeni make new Xtreme Security ( V4 maybe ) with 6.2.A.1.100 base system file.
Click to expand...
Click to collapse
If you flashed ONLY boot.img in order to make cwm or push SU BINARY you will get prob wifi or bluetooth, so dont forget to put some .ko file n wifi driver. Check package of boot.img. A.600 you will find them so wifi works well
Abhy-Boy said:
I try with Phantom 1.0.8 Performance kernel and succesfully rooted this ROM
1. Download this .FTF
2. Open Flashtool ( 0.9.11.0 - latest version ). Flash .ftf via Flashtool till finish
Don't forget to safe kernel.sin ( stock JB Sony kernel )
3. Switch On and do some configuration ( Setup Wizard )
4. Flash kernel via Fastboot ( select phantom performance kernel.elf as source )
5. Reboot phone
6. Do root phone by click on Unlocked Icon at Flashtool
7. Now flashtool will send restore configuration to phone, just follow the instruction from Flashtool
8. After flashtool reboot your phone, go to Superuser, and do update su binary
9. Flash kernel via Fastboot ( select Stock JB kernel.sin as source )
10. Tada...... I have 6.2.A.1.100 JB from Sony with rooted status
Ask : Why I change back kernel to JB Stock ?
Answer : With phantom kernel, PC Companion still ask me to upgrade 6.2.A.1.100. So, change back to stock JB kernel
Now I will clean some app that I didn't need for my daily use.
Click to expand...
Click to collapse
You returned to stock kernel but are still rooted? Also when im tying to root my phone with flashtool it says "no root exploit for this version".
this with this kernel and root
GiorgosCyprus said:
You returned to stock kernel but are still rooted? Also when im tying to root my phone with flashtool it says "no root exploit for this version".
Click to expand...
Click to collapse
Yes. You need upgrade latest Flashtool about that error.
Windows Edition - v0.9.11.0 - MD5 : A0F880F3CF420A31D86026F49A2013D7
Abhy-Boy said:
1. Download this .FTF
2. Open Flashtool ( 0.9.11.0 - latest version ). Flash .ftf via Flashtool till finish
Don't forget to safe kernel.sin ( stock JB Sony kernel )
3. Switch On and do some configuration ( Setup Wizard )
4. Flash kernel via Fastboot ( select phantom performance kernel.elf as source )
5. Reboot phone
6. Do root phone by click on Unlocked Icon at Flashtool
7. Now flashtool will send restore configuration to phone, just follow the instruction from Flashtool
8. After flashtool reboot your phone, go to Superuser, and do update su binary
9. Flash kernel via Fastboot ( select Stock JB kernel.sin as source )
10. Tada...... I have 6.2.A.1.100 JB from Sony with rooted status
Ask : Why I change back kernel to JB Stock ?
Answer : With phantom kernel, PC Companion still ask me to upgrade 6.2.A.1.100. So, change back to stock JB kernel
Now I will clean some app that I didn't need for my daily use.
Click to expand...
Click to collapse
Can you please tell me how to do it on locked Bootloader?
Mirror link in here
http://forum.xda-developers.com/showpost.php?p=46325507&postcount=37
tt1991tt said:
Mirror link: https://docs.google.com/file/d/0B5iuJcjgtKP1bTFfQ3UtVTlKTlE/edit?usp=sharing
Click to expand...
Click to collapse
That is wrong file. This is CE and You have mirrored ST27i_6.2.A.1.100_1265_2259_World_Malaysia.ftf.
{
"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"
}
Requirements:
Flashtool 0.9.13 by @Androxyde
XZDualRecovery 2.7.43 BETA or newer.
Current rooted FW version: 14.1.B.1.532 or 14.1.B.2.257.
Special features:
SuperSU integrated in system, FULL ROOT!
XZDualRecovery 2.7.75 BETA (CWM & PhilZ Touch & TWRP) pre-installed;
init.d support (read how to enable)
For both locked and unlocked bootloaders!
In the following guide I suggest you use an external SDCard but that's just good practice, you can use your internal storage or even an USB OTG storage device in TWRP if you like to install, that's no problem!... If you are modding and the likes, best is to have an external sdcard, just for safeties sake.
If you are unable to download torrent files directly, have http://zbigz.com/ do it for you!
How to update to 14.2.A.0.290:
Files:
For C6802: Download C6802_14.2.A.0.290.flashable.zip (Bittorrent: 842MB) and C6802_14.2.A.0.290_Stripped.ftf (21MB)
For C6806: Download C6806_14.2.A.0.290.flashable.zip (Bittorrent: 815MB) and C6806_14.2.A.0.290_Stripped.ftf (21MB)
For C6833: Download C6833_14.2.A.0.290.flashable.zip (Bittorrent: 760MB) and C6833_14.2.A.0.290_Stripped.ftf (21MB)
Save them somewhere you remember;
Due to a little bug inside the updater-script, you need to follow the guide in this post to make sure flashing it works OK. (Only if you downloaded the older version)
Put 'C68XX_14.2.A.0.290.flashable.zip' on (the external) SDcard1;
Put 'C68XX_14.2.A.0.290_Stripped.ftf' inside the Flashtool/firmwares folder;
Create a backup of your phone in TWRP and don't forget to backup the contents of 'SDCard' (the internal storage!);
Install XZDualRecovery 2.7.74 or newer from PC.
In TWRP -> Wipe -> advanced Wipe Tick/Check:
Dalvik-Cache
System
Cache
Data
Then 'Swipe to Right' to make it happen and go back to the TWRP home screen;
Flash 'C68XX_14.2.A.0.290.flashable.zip' in TWRP;
NOTE: do not reboot but go back to the main menu, then go to reboot->power off;
Flash everything in 'C68XX_14.2.A.0.290_Stripped.ftf';
Now reboot to system;
Once you get to the language select screen, reboot to TWRP (no need to finish the guide);
Restore the backup of DATA only, when done go back to the TWRP home screen;
In TWRP -> Wipe -> advanced Wipe Tick/Check Dalvik-cache;
Reboot to system.
The first boot will be slow and after a long wait at the boot animation you will see Android start optimizing the apps on your phone.
Video Guide:
NOTE: This guide is based on an older guide for the Xperia Z1 which has since been updated a few times, but it will give you a general idea.
shem2409 said:
Click to expand...
Click to collapse
Enjoy! :fingers-crossed:
Known XZDualRecovery Issues:
Busybox Updater/Installer: If you have XZDualRecovery installed, un-install any Busybox updating app/tool as most if not all of them will install a version of busybox which does not support the lzma compression applets XZDualRecovery depends on. The version installed together with XZDualRecovery is very stable and I have yet to hear anyone complain about it's stability.
How to report errors:
Please, before shouting out "It doesn't work!!1!" or "I lost root!" or even "My phone reboots when remounting /system RW!!" try the following:
Restore any JB 4.2.2 FTF using any means you are familiar with so you can try again.
Root it using any means you are familiar with.
Install XZDualRecovery and then try to update again using TWRP.
If it still fails something from there on: LOGS!!.
NOTE: The important ones can be found in /cache/recovery and in /sdcard1/XZDualRecovery, pack them up and send them to me or attach them to your bug report.
Thank you
XDA:DevDB Information
[STOCK][4.3] Update to 14.2.A.0.290 [Root & XZDR][LB/UB], a ROM for the Sony Xperia Z Ultra
Contributors
[NUT]
ROM OS Version: 4.3.x Jellybean
ROM Kernel: Linux 3.4.x
ROM Firmware Required: 14.1.B.1.532 or 14.1.B.2.257
Based On: STOCK
Version Information
Status: Stable
Stable Release Date: 2014-01-18
Created 2014-01-16
Last Updated 2014-01-21
Tips and Tricks
Easy switching between locked and unlocked bootloader states!
NOTE: USE TWRP ONLY for this guide.
NOTE 2: You NEED to have XZDualRecovery 2.7.43 or higher to make this work.
Create a backup, including the Trim Area (TA!)
Unlock your bootloader
Restore backup without TA
Create a new backup of your UNLOCKED TA
Restore the previous TA backup to relock your phone.
Done :good:
Now you can switch between locked and unlocked bootloaders quick and painless: no more system wipes and you can basically do whatever you want
How to enable init.d support:
Open a filemanager app and navigate to the location where the XZDualRecovery folder is located and go in to it. Open XZDR.prop as a text file and set dr.initd.active to true.
NOTE: For this ROM it means the init.d script called 99SuperSUDaemon will kick in to action, so it's best to disable (by setting chmod 644) /system/etc/install-recovery.sh for the time being or to clear it's contents.
Done
Downgrading to a 4.2 ROM:
Download C6833_14.1.B.1.532_[NUT].ftf (Bittorrent: 760MB) and flash it using FlashTool. I've also added the FTF to the downloads page on the DevDB tab, this will allow straight downloads as well.
This FTF will allow you to downgrade to .532 without loss of your IMEI :good:
ROM Status: STABLE
Update 1:
C6802 ROM uploaded and seeding.
Update 2:
C6833 ROM uploaded and seeding.
Update 3:
C6806 ROM now uploading, FTF and torrent file links have been updated.
Update 4:
C6806 ROM uploaded and seeding.
Update 5:
A little bug has been discovered in the updater-script. To be able to flash the one you possibly have downloaded already, follow the instructions in this post to get it to work properly!
I will be updating the packages soon, in the mean time I have updated the OP guide to include this small fix.
Update 6:
Removed the files from the bit-torrent seeder. I'm currently uploading them again now. It will probably take about 30 minutes to finish that, will update again once completed and seeding again.
If you have already downloaded the package, make sure to read 'Update 5' with details on that how to fix yours.
Update 7:
Files have been replaced on the seeder box. There is no need to re-download them if you follow the guide pointed to by 'Update 5'.
Enjoy again!
Good work @[NUT] :thumbup:
sent from my monx®dified 6802 using Tapatalk
290 is it lte For C6833
Sent from my C6833 using XDA Premium 4 mobile app
jpeps said:
290 is it lte For C6833
Sent from my C6833 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
If you have lte now, then that will be the same for this package
Yet another ROM! Great work, NUT!
Anyone who has tested it please do let me know. If you are unable to post here because you just registered on xda, feel free to PM me your experience!
Anyone who can upload both the c6802 files anywhere else as cant download from given links.
techpal said:
Anyone who can upload both the c6802 files anywhere else as cant download from given links.
Click to expand...
Click to collapse
Why?
Failed
Tried a few times to flash C6833_14.2.A.0.290.flashable.zip in TWRP, but each time it failed in the final step:
Code:
set_perm: some changes failed
E:Error in /sdcard/C6833_14.2.A.0.290.flashable.zip
(status 7)
So I decided to try the flashable zip from jackie099's thread, and that one was successful.
Djezpur said:
Tried a few times to flash C6833_14.2.A.0.290.flashable.zip in TWRP, but each time it failed in the final step:
Code:
set_perm: some changes failed
E:Error in /sdcard/C6833_14.2.A.0.290.flashable.zip
(status 7)
So I decided to try the flashable zip from jackie099's thread, and that one was successful.
Click to expand...
Click to collapse
Ah frack, because of this report, I just rechecked my edify script, and even though it was correct typo wise, it is trying to set permissions on a file which no longer exists in the package.
I'll redo the packages soon. Packages have been updated. If you have one downloaded already, follow this little guide to fix yours!
In the mean time, open the flashable ZIP in winzip or winrar, extract META-INF/com/google/android/updater-script
and remove this line:
Code:
set_perm(0, 0, 0644, "/system/bin/ramdisk.stock.cpio.lzma");
Put the updater-script back inside the zip, updating the one there. It should make it flash OK from there on.
Thanks for the report!
thanks for all your hard work! however, torrents do not download (understand dependent on other servers etc) hope someone can post these (C6833) Thanks
mac231us said:
thanks for all your hard work! however, torrents do not download (understand dependent on other servers etc) hope someone can post these (C6833) Thanks
Click to expand...
Click to collapse
Then your ISP is blocking them... or you are getting blocked by mine
Try http://zbigz.com to download the torrent file, they turn it in to a straight download for you.
[NUT] said:
Thanks for the report!
Click to expand...
Click to collapse
And thank you for providing a way to root .290 with a locked bootloader. :good:
Djezpur said:
And thank you for providing a way to root .290 with a locked bootloader. :good:
Click to expand...
Click to collapse
So, you fixed and flashed it and it's confirmed working?
I need that confirmation to change the Post 3 status
[NUT] said:
So, you fixed and flashed it and it's confirmed working?
I need that confirmation to change the Post 3 status
Click to expand...
Click to collapse
Yep, all is good now!
sorry for being a noob, but how to flash the stripped ftf part?
im thinking of using flashtool but im stuck on waiting for flashmode, saying i should press back button which we dont have. any help?
im stuck here
thanks before
Justin^Tan said:
sorry for being a noob, but how to flash the stripped ftf part?
im thinking of using flashtool but im stuck on waiting for flashmode, saying i should press back button which we dont have. any help?
im stuck here
thanks before
Click to expand...
Click to collapse
Set up flashtool to where it asks you to connect your phone:
Turn off your mobile, then hold Volume down while connecting your usb cable. It will then start flashing.
Holding volume up will put your device in to fastboot mode, FYI
ahh, volume down lol. great, that did the rick
thanks a lot NUT! appreciate your job hehe. great work
oh right, i still have the notification of OTA update to 290 after i flashing your ROM. is there any way to clear it?
TWRP for Transformer Pad TF201T
{
"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"
}
MUST BE ON THE HAIRYBEAN BOOTLOADER ENDING IN 27.1
Changelog 2.7.8.2
- All Upstream changes
- Small changes to the 'new theme' (thx z31s1g)
- Added flash to staging partition, via flash image feature.
Changelog 2.8.7.1
- Removed ability to flash raw .img files....
- gui: keyboard: support longpress label offset, code cleanup ( Thx @_that)
- Added flashable zip
- merged upstream changes
Changelog- 2.8.7.0
- Fully merged 2.8.7.0 source from upstream
- Removed SU from twrp ( Its useless & only takes up extra room)
Changelog- 2.8.6.5
- New theme fully implemented ( Huge thx to @z31s1g ) Still a WIP
- Fix mount -o bind error on recreating /data/media/0 (Huge thx to @xiaolu ) & ( @_that )
- All upstream merges by Team Win
Changelog 2.8.6.1
- GUI: Prevent duplicate page overlays. Thx Matt & _that
- Replace legacy DEVICE_RESOLUTION with the new TW_THEME
- Using new common repo to build recovery.
- Build with grimlocks-5.1 kernel from zombi
- All upstream changes. Thx TeamWin
Changelog- 2.8.6.0
- All upstream changes (They are on git)
- Cleaned up external mount labels
Changelog- 2.8.5.1
- Added dock sd card support to twrp
Changelog- 2.8.5.0
- Added formatting of ext sdcard for ROM2SD & DATA2SD
- Added ability to backup ext sdcard partitions
- Added reboot to recovery & reboot to bootloader from with TWRP
- Fixed error formatting /data to f2fs <- Thx Dees Troy for this fix
- A few upstream changes
Click to expand...
Click to collapse
UPGRADE INSTRUCTIONS----------------------------------------------------------------------------------------------------------------------------------------
- Flashing recovery with fastboot
- Boot tablet into fastboot.
Code:
fastboot -i 0x0B05 flash recovery foo.img
- Replace foo with the file name.
- Once flashed reboot into bootloader.
Code:
fastboot reboot-bootloader
- Enter recovery.
----------------------------------------------------------------------------------------------------------------------------------------
- - Flashabale zip
- Boot into current recovery .....
- Flash the zip it is signed so turn that on ......
- Reboot in to android, fully
- Boot into bootloader, enter newly flashed RCK ....
----------------------------------------------------------------------------------------------------------------------------------------
XDA:DevDB Information
TWRP for TF201T [KANG], Tool/Utility for the Asus Eee Pad Transformer Prime
Contributors
lj50036, hardslog
Source Code: https://github.com/zombi-x-lp
Version Information
Status: Testing
Created 2015-03-06
Last Updated 2015-03-06
DOWNLOADS
OLDER VERSIONS
TWRP [email protected] kang full mirror 1
TWRP [email protected] kang flashable zip by alias4ever full mirror 1
TWRP [email protected] kang full mirror 1
TWRP [email protected] kang flashable zip by alias4ever full mirror 1
TWRP [email protected] kang full mirror 1
TWRP [email protected] kang flashable zip by alias4ever full mirror 1
TWRP [email protected] kang full mirror 1
TWRP [email protected] kang flashable zip by alias4ever full mirror 1
TWRP [email protected] kang full mirror 1
TWRP [email protected] WILL UPLOAD
The more you know
JOIN US ON IRC !!!https://webchat.frt/
Channel: #zombi-x
HOW TO TAKE A RECOVERY LOGYou will be taking this log cause of some kind of error message .....
Once you get and error message, here is how to retrieve a recovery log ....
Using a PC with adb/fastboot installed on it, and if windows the correct drivers. ....
Code:
adb pull /tmp/recovery.log
This log will be in the same directory as the terminal/cmd window is cd'd into ....
Now you have the log, upload it to a pasting site or for download, and give us a link....
lj50036 said:
it may appear to hang on the twrp curtain, let it boot there is nothing wrong here
Click to expand...
Click to collapse
Do you want a flashable zip? Also if I make you a bootloader upgrade with this TWRP built in would you be able to test it as I don't have access to the machine any more?
flumpster said:
Do you want a flashable zip? Also if I make you a bootloader upgrade with this TWRP built in would you be able to test it as I don't have access to the machine any more?
Click to expand...
Click to collapse
I am going to make a flashable zip.... :good:
Yes I can test anything that needs testing for sure .....
Let me know, Thx Josh
lj50036 said:
I am going to make a flashable zip.... :good:
Yes I can test anything that needs testing for sure .....
Let me know, Thx Josh
Click to expand...
Click to collapse
Try this one first mate. I made this the other day for das chaos but he bricked his machine before he could test it.
Link removed for now.
This is the bootloader upgrade and twrp 2.8.4.0 and the partition table setup. If this works then it will be simple for me to make one using your file above.
The best way to test this is to use my downgrade zip to go back to 4.1.1 and then try this to upgrade.
No one else test this please unless you know what you are doing and have nvflash backups. I don't like uploading things I haven't tested myself but have no other option here.
flumpster said:
Try this one first mate. I made this the other day for das chaos but he bricked his machine before he could test it.
https://www.androidfilehost.com/?fid=95916177934537081
This is the bootloader upgrade and twrp 2.8.4.0 and the partition table setup. If this works then it will be simple for me to make one using your file above.
The best way to test this is to use my downgrade zip to go back to 4.1.1 and then try this to upgrade.
No one else test this please unless you know what you are doing and have nvflash backups. I don't like uploading things I haven't tested myself but have no other option here.
Click to expand...
Click to collapse
Got it if you would like to pull the download your call ....
Yes I will go back to stock bootloader then upgrade .....
Will let you know how I get on ....
Thx Josh
flumpster said:
Try this one first mate. I made this the other day for das chaos but he bricked his machine before he could test it.
Link removed for now.
This is the bootloader upgrade and twrp 2.8.4.0 and the partition table setup. If this works then it will be simple for me to make one using your file above.
The best way to test this is to use my downgrade zip to go back to 4.1.1 and then try this to upgrade.
No one else test this please unless you know what you are doing and have nvflash backups. I don't like uploading things I haven't tested myself but have no other option here.
Click to expand...
Click to collapse
zip flashed just fine ....
Rebooted TWRP ......
Blue bar filled to about 85% ......
Tablet did what can only be called a soft reboot ....
As in did not power all the way off, just flashed back to the bootloader screen with 'THIS DEVICE IS UNLOCKED'
But now the blue bar was gone .... It did boot into 2.8.4.0 TWRP and could not mount anything ...
A simple reboot back into TWRP and all is good ....
I am now on your WW bootloader flashed my kang TWRP and installed zombi-pop ....
Life is good ......
Thx Josh
This is fantastic for users of rom/data2SD!
Question about that, however: Will this have an option to automatically flash zips to romSD/dataSD, or will we still have to use the ROM2SD/DATA2SD zips when not flashing something that already has a script for it?
Lavrentsii said:
This is fantastic for users of rom/data2SD!
Question about that, however: Will this have an option to automatically flash zips to romSD/dataSD, or will we still have to use the ROM2SD/DATA2SD zips when not flashing something that already has a script for it?
Click to expand...
Click to collapse
Well if it is built into the ROM as it is for zombi and crombi then ....
There will be no need for the extra zips .... I am still trying to think how we can ....
Support other ROMS easily, but this is going to take some doing ..... Stay turned ..... :good:
Thx Josh
lj50036 said:
zip flashed just fine ....
Rebooted TWRP ......
Blue bar filled to about 85% ......
Tablet did what can only be called a soft reboot ....
As in did not power all the way off, just flashed back to the bootloader screen with 'THIS DEVICE IS UNLOCKED'
But now the blue bar was gone .... It did boot into 2.8.4.0 TWRP and could not mount anything ...
A simple reboot back into TWRP and all is good ....
I am now on your WW bootloader flashed my kang TWRP and installed zombi-pop ....
Life is good ......
Thx Josh
Click to expand...
Click to collapse
Cheers mate. I am in bed at the moment but I will make you another test tomorrow with your recovery added into it for you to try.
lj50036 said:
Well if it is built into the ROM as it is for zombi and crombi then ....
There will be no need for the extra zips .... I am still trying to think how we can ....
Support other ROMS easily, but this is going to take some doing ..... Stay turned ..... :good:
Thx Josh
Click to expand...
Click to collapse
I'm testing DATA2SD on a non-supported ROM (Katkiss LP with Grimlock 300t/201 kernel) and so far with this recovery and the DATA2SD zip it seems to be working fine. This looks pretty promising
lj50036 said:
TWRP [email protected] kang full mirror 1
TWRP [email protected] kang flashable zip by alias4ever full mirror 1
Click to expand...
Click to collapse
I can confirm that this works thanks to Josh's help/instruction on doing it. He is an awesome & great teacher as I learned so much from him. GREAT RECOVERY! Thanks again Josh! :good:
Thanks! I'm testing 2.8.5.1 with ZOMBi-POP
Is there any way to change partition sizes from this recovery? I can't find it
elchevi said:
Thanks! I'm testing 2.8.5.1 with ZOMBi-POP
Is there any way to change partition sizes from this recovery? I can't find it
Click to expand...
Click to collapse
No there is not yet, I am looking into making this happen...
Not sure if it will ever happen as I think I would also have to let users partition the internal storage also ...
I dont know if I am ready for the storm of bricks that may bring ....
Thx Josh
lj50036 said:
No there is not yet, I am looking into making this happen...
Not sure if it will ever happen as I think I would also have to let users partition the internal storage also ...
I dont know if I am ready for the storm of bricks that may bring ....
Thx Josh
Click to expand...
Click to collapse
Maybe choosing among some predefined templates would do the trick for most users. But yes, it can be potentially problematic hehe
Thanks!
Img vs. blob
@lj50036 - Hi Josh, a stupid question - what´s the difference between img and blob file regarding recovery??? Did they flash the same via fastboot? And why did you switched from blob to img? Just asking, to learn something new.
Thx in advance
JuraP said:
@lj50036 - Hi Josh, a stupid question - what´s the difference between img and blob file regarding recovery??? Did they flash the same via fastboot? And why did you switched from blob to img? Just asking, to learn something new.
Thx in advance
Click to expand...
Click to collapse
It is not a .img it is still a blob, but when I build it the process outputs a recovery.img
Even thought its a blob ....
if you would like to learn about blobs check this out by @_that
http://forum.xda-developers.com/showpost.php?p=36925180
Thx Josh
lj50036 said:
It is not a .img it is still a blob, but when I build it the process outputs a recovery.img
Even thought its a blob ....
if you would like to learn about blobs check this out by @_that
http://forum.xda-developers.com/showpost.php?p=36925180
Thx Josh
Click to expand...
Click to collapse
So, the name, including file format, actually doesn´t matter as the output is done right? As the file will be just pushed to recovery partition? Or should it be renamed to foo.blob???
JuraP said:
So, the name, including file format, actually doesn´t matter as the output is done right? As the file will be just pushed to recovery partition? Or should it be renamed to foo.blob???
Click to expand...
Click to collapse
It does not matter you can leave it .img or rename it .blob will not matter ....
Thx Josh
It includes DRM patch and disabled force encryption.
Because fstab.qcom has been moved to system since 8.0, I cannot modify the boot image.
Some of you guys might have a problem with TWRP encryption password. With stock kernel, /data will be encrypted in a few boots even if you set no password.
About this kernel:
- Working camera (DRM-patch)
- Disabled dm-verity (so we can use magisk)
- Can mount /data in recovery (it means we can install magisk inside /data)
- Pass both safetynet
- You can still encrypt any time
- It will not decrypt your data. In other words, you have to do factory reset (wipe data) if it's already encrypted.
- See encryption status in Setting->Security
You can download from the attachments.
41.3.A.2.24
G8231 - View attachment xzs-p3-2.24.zip Based on Nordic Combined
G8232 Dual - View attachment xzsd-p3-2.24.zip Based on Customized TH
41.3.A.0.401
G8231 - Download from a thread by @Pandemic
G8232 Dual - View attachment xzsdp3.0.401-unzip.zip Based on Customized VN (for fingerprint)
Also, patch View attachment drmfix.zip before first system boot.
41.2.A.7.76
G8231 - View attachment xzs-p2.7.76.img.zip
G8232 Dual - View attachment xzsd-p2.7.76.img.zip
41.2.A.7.65
G8231 - View attachment xzs-p2.7.65-extract-first.zip
G8232 Dual - View attachment xzsd-p2.7.65-extract-first.zip
41.2.A.7.53
G8231 - View attachment 8231-boot753noencrypt.zip
G8232 Dual - View attachment boot-7.53-noforceencrypt.zip
It's not flashable zip, so please extract before use.
It will bootloop if you flash wrong version.
{
"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"
}
How to disable by yourself? - Not for Oreo
Prerequisite:
- 32-bit linux (you can use it on liveboot drive or VM)
It doesn't work on cygwin (windows) because of its native executable. So use linux 32 bit (i386), or 64 bit (amd64) with multiarch.
- Unpack using mkbootimg tool made by xiaolu (I tried kitchen and it won't work)
- Open fstab.qcom
- Replace "forceencrypet" with "encryptable"
- Pack again
- Done!
Thanks tobias.waldvogel and xiaolu for their awesome tools.
If you have any question, feel free to ask me or some nice guys here.
zlRampageSlz said:
Some of you guys might have a problem with TWRP encryption password. With stock kernel, /data will be encrypted in a few boots even if you set no password.
About this kernel:
- Working camera (DRM-patch)
- Disabled dm-verity (so we can use magisk)
- Can mount /data in recovery (it means we can install magisk inside /data)
- Pass both safetynet
- You can still encrypt any time
You can download from attachment.
View attachment 4246515
It's not flashable zip, so please extract it before use.
View attachment 4246527
How to disable by yourself?
Prerequisite:
- 32-bit linux (you can use it on liveboot drive or VM)
It doesn't work on cygwin (windows) because of its native executable. So use linux 32 bit (i386), or 64 bit (amd64) with multiarch.
- Unpack using mkbootimg tool made by xiaolu (I tried kitchen and it won't work)
- Open fstab.qcom
- Replace "forceencrypet" with "encryptable"
- Pack again
- Done!
Thanks tobias.waldvogel and xiaolu for their awesome tools.
If you have any question, feel free to ask me or some nice guys here.
Click to expand...
Click to collapse
i'd just like to ask a question.. are we gonna be able to have the tap2wake feature back? or it's just not possible...
Thank you! Can you recover?
谢谢!超逼真可以恢复吗?
In what order to I flash recovery, root and the kernel? (I've never used a kernel before)
Great, but you can just flash twrp-3.0.2-0-kagura.img instead of a newer version and it will work perfectly. For some reason the newer twrps for xz will ask for password to decrypt data
And can you make this for g231?
tapperyaus said:
In what order to I flash recovery, root and the kernel? (I've never used a kernel before)
Click to expand...
Click to collapse
You have to unlock bootloader first before you can flash anything. Then just "fastboot flash boot <thatkernel>.img" in fastboot (blue LED). Recovery and root is optional. Normally, you have to use TWRP recovery to flash zip (su installer).
So, unlock bootloader -> flash kernel -> flash recovery -> install su in TWRP
Also, you can read detailed my tutorial here.
HellFish23 said:
Great, but you can just flash twrp-3.0.2-0-kagura.img instead of a newer version and it will work perfectly. For some reason the newer twrps for xz will ask for password to decrypt data
And can you make this for g231?
Click to expand...
Click to collapse
When you use 3.0.2-0, does it work while being encrypted? Or you have to do a factory reset to prevent further encryption.
Sure, I'll make for you guys when I'm free.
I've added G8231 kernel in the attachments.
zlRampageSlz said:
When you use 3.0.2-0, does it work while being encrypted? Or you have to do a factory reset to prevent further encryption.
Sure, I'll make for you guys when I'm free.
Click to expand...
Click to collapse
I understood the issue was twrp saying is encrypted while you didn't encrypt it yourself, may have misunderstood but I didn't test it while I actually encrypt it myself. And thanks!
Everything is working fine for the kernel, I no longer get the green photos and I can download Super Mario Run (my go to Safetynet app), but when I try to boot into recovery to flash Magisk all I get is a black screen. I tried flashing another TWRP version and still get a black screen. I'm on the dual sim variant.
Even if this problem can't be fixed, thanks for the kernel!
tapperyaus said:
Everything is working fine for the kernel, I no longer get the green photos and I can download Super Mario Run (my go to Safetynet app), but when I try to boot into recovery to flash Magisk all I get is a black screen. I tried flashing another TWRP version and still get a black screen. I'm on the dual sim variant.
Even if this problem can't be fixed, thanks for the kernel!
Click to expand...
Click to collapse
Could you give me TWRP log while installing magisk? Try using uninstaller and wiping cache first. Then flash stock kernel before install magisk again.
zlRampageSlz said:
Could you give me TWRP log while installing magisk? Try using uninstaller and wiping cache first. Then flash stock kernel before install magisk again.
Click to expand...
Click to collapse
The problem wasn't installing magisk, it was that TWRP wasn't installing correctly. Attempting to reach TWRP leads to a black screen. It's easily avoidable by booting the twrp.img through adb/fastboot (then flashing magisk there), I just can't install TWRP onto the phone.
tapperyaus said:
The problem wasn't installing magisk, it was that TWRP wasn't installing correctly. Attempting to reach TWRP leads to a black screen. It's easily avoidable by booting the twrp.img through adb/fastboot (then flashing magisk there), I just can't install TWRP onto the phone.
Click to expand...
Click to collapse
Sorry I misunderstood your question, TWRP right now cannot boot in the normal way (from fastboot/adb, or even TWRP itself). You have to hold power+vol down at the same time.
zlRampageSlz said:
Sorry I misunderstood your question, TWRP right now cannot boot in the normal way (from fastboot/adb, or even TWRP itself). You have to hold power+vol down at the same time.
Click to expand...
Click to collapse
Why can't i enter the TWRP by hold power+vol down at the same time? The screen just turned between black and logo.
Thanks.
I found the problem is that i forgot to flash recovery
Hi, Does this kernel support DoubleTap2Wake?
Ok
AWESOMEE..
Xenroe said:
Hi, Does this kernel support DoubleTap2Wake?
Click to expand...
Click to collapse
Not yet, I'll look around if I have some time.
zlRampageSlz said:
Not yet, I'll look around if I have some time.
Click to expand...
Click to collapse
Thanks, i would've flashed XZ Kernel just so i can have DoubleTap2Wake if i could.. I'll be looking forward to your update...
This kernel is good, but I have a question: When I brush the kernel, I can't enter TWRP through the combination of the volume key and the power button. Instead, my phone switch between the logo and the black screen. Do I need to write a TWRP again?(My English is not good, please fogive me:crying
{
"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"
}
I am sharing my kernel/boot.img, which is build from Sony Open Source/Qualcomm/ and android source (Very close to Stock KERNEL). Designed to keep balance security/ with high Performance and battery life.
Code:
###Disclaimer###
I am not responsible for any damage, broken or boot looping.
Please read the instructions and notes before flashing anything. Don't ask me if you don't read the instructions.Please respect and try to help each other. You may face sometimes that I cannot answer your questions/or answer your questions a bit later. I am busy with my work and don't have enough time to read and answer all your questions at the same time.
DONATE ME HERE
DONATE-HERE
##############################
Requirements-
##############################
- A working driver for your device.
USB drivers for Xperia devices
- Unlock bootloader
- A Working TWRP-with latest patch security
- YOUR firmware must match my kernel version. I used to update the kernel with latest firmware.
- Backup your stuff for future
- YOU NEED a refresh stock ROM (means you have to wipe EVERYTHING). Use flashtool to flash the latest firmware. (Remember to check Wipe USERDATA in flashtool). It seems not necessary if you have already flashed my kernel and have a working camera
- USE LATEST FLASHTOOL VERSION TO FLASH THE LATEST FIRMWARE
- (DOWNLOAD FROM HERE:- LATEST FLASHTOOL)
##############################
Features 11/MARCH/2019
##############################
- Based on latest kernel source VERSION = 4, PATCHLEVEL = 4, SUBLEVEL = 148 (47.2.A.8.24) MARCH, 2019
- Up to date with the September security update—MARCH, 2019
- Hide verifiedbootstate from /proc/cmdline in order to fix the failed SafetyNet CTS check(It can still fail through other means)-GOOGLE PAY SHOULD WORK
- Remove verifiedbootstate flag from /proc/cmdline - Disable CRC check
- Support wireguard VPN protocol
- dm-verity removed
- Sepolicy is patched for latest Oreo (deodex ROMs)
- Scheduler optimize/support for heterogeneous multi-core. Battery efficiency
- Energy Aware Scheduling (EAS) feature is enabled/optimize energy consumption for advanced multicore SoCs
- Update and add Qualcomm PM driver/APM driver updated reduce battery usage during sleeping
- Enable latest energy aware scheduling patches
- Multi-core scheduler enable/optimized
- A lot subsystems converted to use power efficient work-queues
- CAF improvements and optimized
- Enable latest energy aware scheduling patches
- Enable work-queue power-efficient mode by default
- Several other patches to improve the speed and battery usage
- Tweaked the scheduler to reduce/save power by scaling down the frequency of the CPU's or idling them,
- Tweaked to predict the best time to save power on the CPU without affecting performance
- Tweaked/optimized the scheduler to balance the load across all CPUs without any regards to the power costs.[/SIZE]
##############################
Instructions-
##############################
- Reboot into bootloader mode and following the following steps
Code:
- adb devices
- adb reboot bootloader
- fastboot devices
- fastboot flash boot boot.img (flash my kernel/boot.img)
- fastboot reboot
##############################
Downloads
##############################
XPERIA-XZ1 (G8341)+XPERIA XZ1 Dual-(G8342)-LATEST-47.2.A.8.24-(11/MARCH/2019)
##############################
XPERIA XZ1 (G8341)+(G8342)-ALL-BOOT IMAGES-[KERNEL][DRM-PATCHING]-
##############################
Source/GitHub
##############################
Kernel Source
-47.1.A.12.xxx
https://github.com/Nexusma/msm-4.4
https://github.com/toffyjan/android_kernel_Sony_lilac_poplar
https://github.com/sonyxperiadev/device-sony-lilac
IF YOU LIKE MY WORK AND WANT ME TO CONTINUE, THEN DON'T FORGET TO BUY ME COFFEE
DONATE ME HERE
DONATE-HERE
Special Thanks To:
If you can, donate and respect all the devs
@Chainfire for his great work to achieve root SuperSU
@Sultanxda for his great work in android kernel and SafetyNet CTS check
@modpunk for TWRP-recovery 3.2.1-0 and drm-fix THANK YOU
@Androxyde for Flashtool. merci beaucoup pour tout
@munjeni for his great knowledge and tools for extracting SIN images
@sToRm// for his effort on DRM work, THANKS
@SuperR. for SuperR's Kitchen , THANK YOU
@M-Rom Thanks for sharing drm-fix and patch
@serajr Thanks for DRM Fix Workaround and Sony RIC disabler @tobias.waldvogel thanks for older drmfix and his great effort.
THANK YOU SONY FOR SUPPORTING DEVs AND ALLOWING US TO UNLOCK THE BOOTLOADER
ALSO THANKS FOR EVERYONE ELSE EVEN I FORGET TO MENTION THEIR NAMES.
Thanks to XDA And everyone else who share their knowledge and works among us in xda.
Yeaaaah!! Now time to custom stock rom! [emoji7]
Wysłane z mojego G8342 przy użyciu Tapatalka
janjan said:
-
Click to expand...
Click to collapse
Finally! Will download and try your kernel tomorrow!
Is it needed to flash SuperSU, or is this kernel pre-rooted through Magisk?
Thank You! Amazing Work!
All works fine on my G8341!
xFirefly93 said:
Finally! Will download and try your kernel tomorrow!
Is it needed to flash SuperSU, or is this kernel pre-rooted through Magisk?
Click to expand...
Click to collapse
I had to patch the boot.img manually with magisk and then flash with it via TWRP.
Now Magisk SafetyNet and Xposed are working like a charm!
Gnome1911 said:
Thank You! Amazing Work!
All works fine on my G8341!
I had to patch the boot.img manually with magisk and then flash with it via TWRP.
Now Magisk SafetyNet and Xposed are working like a charm!
Click to expand...
Click to collapse
How-to do this? This is my first Android device after being away from the OS for 1,5-2 years, so I am basically a newbie from scratch on the more "advanced" stuff.. ?
Want to help me out?
xFirefly93 said:
How-to do this? This is my first Android device after being away from the OS for 1,5-2 years, so I am basically a newbie from scratch on the more "advanced" stuff..
Want to help me out?
Click to expand...
Click to collapse
Sure
Your Bootloader is unlocked and TWRP is installed?
Then just download the the Zip from the first post for your device and extract the boot.img
Download and install Magisk Manager.
When you now open open Magisk Manager on your Smartphone, you will be asked to install the latest Magisk.zip. Now press patch boot image and navigate to the extracted boot.img.
When the progress is finished boot into TWRP press install, select install img (bottom of the screen), navigate to the patched boot.img (internal memory/Magisk Manager) and press install.
After installation you can reboot and now Magisk should be working
Thank you, great work. Tried it and booting and root with magisk is fine.
Except camera doesn't take a picture. It opens buth freezes when i want to take the picture
Gnome1911 said:
Sure
Your Bootloader is unlocked and TWRP is installed?
Then just download the the Zip from the first post for your device and extract the boot.img
Download and install Magisk Manager.
When you now open open Magisk Manager on your Smartphone, you will be asked to install the latest Magisk.zip. Now press patch boot image and navigate to the extracted boot.img.
When the progress is finished boot into TWRP press install, select install img (bottom of the screen), navigate to the patched boot.img (internal memory/Magisk Manager) and press install.
After installation you can reboot and now Magisk should be working
Click to expand...
Click to collapse
Ramdisk is already patched. No need to patch it again. Flash the zip from first thread and then flash the latest magisk. Done
Xposed is also working..no issue (unofficial build)
Carlovn said:
Thank you, great work. Tried it and booting and root with magisk is fine.
Except camera doesn't take a picture. It opens buth freezes when i want to take the picture
Click to expand...
Click to collapse
It shouldn't effect your camera. Did you flash anything else maybe?
Don't tested the Cam before...
Same here. Cam freezes on focus
---------- Post added at 09:22 AM ---------- Previous post was at 09:20 AM ----------
janjan said:
Ramdisk is already patched. No need to patch it again. Flash the zip from first thread and then flash the latest magisk. Done
Xposed is also working..no issue (unofficial build)
Click to expand...
Click to collapse
I tried to flash Magisk.zip and get an error.
So i tried it as i wrote before and this worked
janjan said:
It shouldn't effect your camera. Did you flash anything else maybe?
Click to expand...
Click to collapse
I flashed part-1 of the previous drm fix. That could be the problem.
When i get home I will flash .34 to start over and check if this fixes the problem
Or does anybody know how to change back to the original secd
Does this kernel work with the DRM fix? What I mean is, can we flash the kernel, then flash the DRM fix and flash Magisk so we can have both the DRM fix for the camera and Magisk for root?
N1ghtr08d said:
Does this kernel work with the DRM fix? What I mean is, can we flash the kernel, then flash the DRM fix and flash Magisk so we can have both the DRM fix for the camera and Magisk for root?
Click to expand...
Click to collapse
The whole meaning for this is that you don't need the DRM fix with this kernel. So flashing this kernel and magisk you shuld be good to go.
Edit: Camera doesn't seem te work. I misread in the title that it said DRM fix but is dm fix...
I'm going the new firmware now then this kernel and Magisk to test.
Fingers crossed ?
---------- Post added at 11:42 AM ---------- Previous post was at 10:47 AM ----------
Ok so I upgraded the OS to 12.34 then reflashed TWRP latest from modpunk then rebooted to recovery and flashed the kernel and Magisk and I got a bootloop so....
I reflashed again with newflasher, TWRP, reboot to recovery, flash the kernel then this time I rebooted to system and again back into recovery then I flashed Magisk and it all booted fine, but here's the problem.....
The camera doesn't work. It has no DRM fix so all the pictures are that horrible green square.
Should I flash the DRM fix separately or what?
---------- Post added at 11:52 AM ---------- Previous post was at 11:42 AM ----------
So I decided to boot into recovery again and flash 2 of the 3 DRM fix files (the DRM fix and Ricoff) and they flashed fine, then I rebooted and tested the camera and it just hangs even I try to take a picture.
Does anybody have any ideas what we can do to have the DRM fix working alongside Magisk?
I am going to upload new build. Optimized more for battery improvement, remove some boosting to reduce error, bootloop, re-patched the ramdisk proper to minimize bootloop, and other tweaks.
janjan said:
I am going to upload new build. Optimized more for battery improvement, remove some boosting to reduce error, bootloop, re-patched the ramdisk proper to minimize bootloop.
Click to expand...
Click to collapse
Thank you! Is there any hope for a working camera?
Carlovn said:
Thank you! Is there any hope for a working camera?
Click to expand...
Click to collapse
Unfortunately I haven't own the device. I have only XZ1 compact. I have no issue with camera. But I will take a look when I have time.
janjan said:
Unfortunately I haven't own the device. I have only XZ1 compact. I have no issue with camera. But I will take a look when I have time.
Click to expand...
Click to collapse
Yes, please do. We really appreciate your work but we desperately want Magisk and a working camera
Thank you very much, @janjan for your effort.
There seems to be a difference in the DRM handling between XZ1 and XZ1Compact, resulting in a non-working camera on the XZ1 even if it works on the Compact.
It is really nice of you to compile this kernel for our device, but unfortunatly it doesn´t really work all the way
pergoteborg said:
Thank you very much, @janjan for your effort.
There seems to be a difference in the DRM handling between XZ1 and XZ1Compact, resulting in a non-working camera on the XZ1 even if it works on the Compact.
It is really nice of you to compile this kernel for our device, but unfortunatly it doesn´t really work all the way
Click to expand...
Click to collapse
I just found out some issue with G8342-Dual. It seems G8341 and G8342 are used two different deconfig for building Kernel. I am going to fix it now. I will try to look at DRM soon.
So don't flash G8342 boot.img yet. Going to remove the link.