[KERNEL][E6653] Stock 32.0.A.6.200 with TWRP v3.0.0.0-0 - Xperia Z5 Android Development

Here is the stock kernel from the latest 32.0.A.6.200 5.1.1 firmware with TWRP 3.0.0-0
SONY RIC and dm-verity disabled so you can root your phone and modify the system partition.
Flash the boot.img with fastboot by turning your phone off and holding volume up whilst plugging it in to your computer, you will see the led light up. If the drivers and adb/fastboot are installed properly it will show up under devices. If you just unlocked your bootloader then it is set up properly, but just to be sure type this-
Code:
fastboot devices
If it shows up properly, flash the kernel.
Code:
fastboot flash boot boot.img
If you are already rooted flash this in recovery 32.0.A.6.200_TWRPv3.0.0-0.zip
After flashing press volume up to boot into TWRP, or volume down to boot in to your current recovery.
Downloads-
boot.img
32.0.A.6.200_TWRPv3.0.0-0.zip
Thanks to @tobias.waldvogel for making this much easier.
Also @AndroPlus for TWRP v3.0.0-0
Tip-
For people that have just unlocked their bootloader and want to root their device the easiest way, flash the kernel with fastboot like I said before and turn off your phone by unplugging it.
Press volume up when booting, the led will turn blue, it will go red and boot into TWRP when pressing it, now download this on your computer SuperSU v2.65
Connect your phone and transfer the file over via mtp in TWRP, now flash it and you have rooted your phone safely and fast.

Somebody test it ?

You don't need to test, i've been using using it for the past 2 weeks
Sent from my E6653 using Tapatalk

I'm testing it, Androplus kernel too unstable...
Thanks

nreuge said:
I'm testing it, Androplus kernel too unstable...
Thanks
Click to expand...
Click to collapse
We are waiting your feedback.
Bro this is stock kernel what are you testing ?

gm007 said:
We are waiting your feedback.
Bro this is stock kernel what are you testing
Click to expand...
Click to collapse
For the moment, it's fine.
I'm testing androplus kernels for more than one year (on the Z2 before) and although I appreciate his work, I'm tired of random reboots... Stock kernel is less fun for sure

@nreuge Thanks for the testing. Wondering what is the lost comparing with stock kernel to Android Plus one? Seem the tweak can be done with root in the OS anyway...

chenliangchen said:
@nreuge Thanks for the testing. Wondering what is the lost comparing with stock kernel to Android Plus one? Seem the tweak can be done with root in the OS anyway...
Click to expand...
Click to collapse
No, there are things at the kernel level that you can't do just tweaking android, e.g. additional CPU governors, hotplugs, thermal managements, etc...
But are these things really a gain if the device stability is affected?...
For the moment, I'm happy with this stock kernel

thank you very much
noob question :
I'm not familiar with Sony's this Z5 is my first .. after flashing this kernel ,will I get OTA updates ? because I'm waiting for the 6.0

korom42 said:
thank you very much
noob question :
I'm not familiar with Sony's this Z5 is my first .. after flashing this kernel ,will I get OTA updates ? because I'm waiting for the 6.0
Click to expand...
Click to collapse
You wont get ota updates after unlocking bootloader, but you can flash stock MM firmware when it's released with flashtool.

gm007 said:
You wont get ota updates after unlocking bootloader, but you can flash stock MM firmware when it's released with flashtool.
Click to expand...
Click to collapse
That's bad :crying: .. I'll wait more before customizing my Z5

*** deleted

celderic said:
Here is the stock kernel from the latest 32.0.A.6.200 5.1.1 firmware with TWRP 3.0.0-0
SONY RIC and dm-verity disabled so you can root your phone and modify the system partition.
Flash the boot.img with fastboot by turning your phone off and holding volume up whilst plugging it in to your computer, you will see the led light up. If the drivers and adb/fastboot are installed properly it will show up under devices. If you just unlocked your bootloader then it is set up properly, but just to be sure type this-
Code:
fastboot devices
If it shows up properly, flash the kernel.
Code:
fastboot flash boot boot.img
If you are already rooted flash this in recovery 32.0.A.6.200_TWRPv3.0.0-0.zip
After flashing press volume up to boot into TWRP, or volume down to boot in to your current recovery.
Downloads-
boot.img
32.0.A.6.200_TWRPv3.0.0-0.zip
Thanks to @tobias.waldvogel for making this much easier.
Also @AndroPlus for TWRP v3.0.0-0
Tip-
For people that have just unlocked their bootloader and want to root their device the easiest way, flash the kernel with fastboot like I said before and turn off your phone by unplugging it.
Press volume up when booting, the led will turn blue, it will go red and boot into TWRP when pressing it, now download this on your computer SuperSU v2.65
Connect your phone and transfer the file over via mtp in TWRP, now flash it and you have rooted your phone safely and fast.
Click to expand...
Click to collapse
Hi and thanks for this beautiful and simple guide, I have a small problem because i flashed boot.img with stock 5.1 a.200 i mean, and it start but after i press vol up it doesnt go to recovery, do i have something wrong ? many thanks and really perfect work! hope to use it soon

Related

[Q&A] [Tutorial] Xperia Z & ZL Bootloader Unlocking/Relocking

Q&A for [Tutorial] Xperia Z & ZL Bootloader Unlocking/Relocking
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
4.4.4 Bootloader Unlock?
I have an Xperia Z C6616 (10.5.1.A.0.283) that I rooted using easy root via flashtool. However, in the service menu, it says I am unable to unlock the bootloader. Is this true? Will I be forced to flash back to 4.3 to unlock it?
japansam23 said:
I have an Xperia Z C6616 (10.5.1.A.0.283) that I rooted using easy root via flashtool. However, in the service menu, it says I am unable to unlock the bootloader. Is this true? Will I be forced to flash back to 4.3 to unlock it?
Click to expand...
Click to collapse
If it says you cannot unlock your bootloader, then you cannot unlock it at all, regardless of which firmware version is installed.
The C6616 bootloader is permanently locked because Bell requested it be that way and there's no way (either officially or unofficially) around it, unfortunately.
Sent from my C6603 using Tapatalk
If it says you cannot unlock your bootloader, then you cannot unlock it at all, regardless of which firmware version is installed.
The C6616 bootloader is permanently locked and there's no way (either officially or unofficially) around it, unfortunately.
Click to expand...
Click to collapse
Well thats incredibly frustrating. Is there any way then to flash new roms or install a recovery? Also, it might not matter, but before I updated to 4.4, it listed my model number as C6606.
Bootloader Issue
Hey guys, ran into a little issue. I flashed my phone with a stock ROM, C6603_10.3.A.0.423_Generic ES.ftf.
Figuring It'd be fine, I then proceeded to attempt to unlock my bootloader. However, this time after flashing this stock ROM, unlocking the bootloader would cause my phone to crash, resulting in having to reflash the stock rom again.
Any ideas?
Cheers.
Please help!
Hello, I need help with unlocking the bootloader for my Sony Xperia Z please. This is the first time I am doing this, so I am a extremely novice on these things. All I want is to flash the sony rom and install android 5 lollipop on my Xperia Z
I have done all the steps mentioned above but when I type the command fastboot.exe -I 0x0fce getvar version it just says waiting for device.
I don't know if my phone is even in fastboot mode. I have turned the developer mode on phone setting with USB debugging set to ON. When I connect my phone to the computer I press power and volume up for around 10 second before plugging in the USB. The phone vibrates 3 times and there is a sound in computer but nothing else happens. When I type the command adb devices, it shows no device attached.
I don't know if this is due to me not installing the drivers but I was tried to install Flashtool-drivers-1.5-20140318.exe file, the installation failed. So I went to advance startup setting and disable driver signing. It then installed. I also downloaded the fastboot package and clicked all the exe files. And my phone has its rooting status: Bootloader unlock allowed: Yes
Please help!
Kathmandu13 said:
I don't know if my phone is even in fastboot mode. I have turned the developer mode on phone setting with USB debugging set to ON. When I connect my phone to the computer I press power and volume up for around 10 second before plugging in the USB. The phone vibrates 3 times and there is a sound in computer but nothing else happens.
Click to expand...
Click to collapse
You're holding the wrong key combination.
Power your phone OFF first.
When the phone is off, hold volume UP only while connecting your device to your PC. Do not press the power button. The LED should light up blue when done correctly. You can then stop pressing the volume key.
Sent from my C6603
kingvortex said:
You're holding the wrong key combination.
Power your phone OFF first.
When the phone is off, hold volume UP only while connecting your device to your PC. Do not press the power button. The LED should light up blue when done correctly. You can then stop pressing the volume key.
Sent from my C6603
Click to expand...
Click to collapse
Oh Thank you so much! I think I unlocked the bootloader now
So what do I need to do now to install custom ROM?
If I understood correctly, I need to flash the current Sony ROM and install different one? Then again what is root? Is unlocking bootloader rooting? Also is the information on the forum up to date? because according to it the newest firmware is 10.3.1.A.0.244/10.3.1.A.2.67. But my firmware is 10.5.1.A.0.292. Please help, I tried finding these information but can't find them.
Kathmandu13 said:
Oh Thank you so much! I think I unlocked the bootloader now
So what do I need to do now to install custom ROM?
If I understood correctly, I need to flash the current Sony ROM and install different one? Then again what is root? Is unlocking bootloader rooting? Also is the information on the forum up to date? because according to it the newest firmware is 10.3.1.A.0.244/10.3.1.A.2.67. But my firmware is 10.5.1.A.0.292. Please help, I tried finding these information but can't find them.
Click to expand...
Click to collapse
In my own opinion, you shouldn't even unlock your bootloader without getting better known to the entire device and its ROMS/Kernels and etc.,
Anyway, I tink that you haven't made TA pratition backup even, and if I'm right, then you've erased your DRM keys forever without a way getting them back.
But if you have made TA partition backup, then we can proceed to explain next thing.
To flash a custom ROM, you don't have to flash newer nor older software version.
All you have to do is go to your favourite ROM thread and read the instructions very carefully, otherwise you're risking to brick/soft-brick your device.
But on different ROMs can be different flashing guides, for example, we can take "Validus" ROM:
VALIDUS
Flashing instructions are : (I'm going to quote them)
1. Make sure you have CWM installed and a working nandroid backup
2. Download the ROM.
3. Place the ROM on your SD-Card.
4.Extract boot.img included in zip and fastboot flash it via Flashtool or CMD
5. Reboot to recovery.
6. Wipe data-factory reset/cache partition/dalvik cache
7. Flash the ROM.
Optional- Flash GApps.
8. Reboot and Enjoy Validus!
Click to expand...
Click to collapse
So in overall, that mean at first you've to have CWM (ClockWorkMod Recovery) (but I think that it's not necessary if you would flash boot.img with it either way)
Secondly, you've to put the entire ROM in your SD Card (not in phone memory), you can include gapps as well,
Third, you need to extract the file named "boot.img" from the ROM which you've downloaded (Now i'm talking about VALIDUS and ONLY IF YOU'RE GOING TO INSTALL THIS ROM EXACTLY), but don't remove it from .rar/.zip.
After you've done everything what is written above, you can flash boot.img using the command prompt and fastboot file, which you were using to unlock your bootloader.
The command is this : fastboot flash boot boot.img
Then, write fastboot reboot and as soon as your LED will change color, push the volume up rocker and then you will be in recovery. After that, go to "Apply Update" --> "Choose from files" or sth (don't remember now), --> "Validus.zip/.rar". and optional you can flash gapps either.
And then pus the button to "Reboot now".
That's all - you've newest Validus build.
But the main point is that for example you would take Pabx rom, you'll have to do everything using CMD (fastboot)
PABX's ROM YUGA L
Look at yourself and compare everything.
Validus ROM is customized than Pabx ROM. It has more customatizations either : APPS, Control, Mods, Gesture and etc., and Pabx ROM is pure-stock L (I think).
I hope I anwered to all ur questions, if not - quote me
Thanks!
LaurynasVP said:
In my own opinion, you shouldn't even unlock your bootloader without getting better known to the entire device and its ROMS/Kernels and etc.,
Anyway, I tink that you haven't made TA pratition backup even, and if I'm right, then you've erased your DRM keys forever without a way getting them back.
But if you have made TA partition backup, then we can proceed to explain next thing.
To flash a custom ROM, you don't have to flash newer nor older software version.
All you have to do is go to your favourite ROM thread and read the instructions very carefully, otherwise you're risking to brick/soft-brick your device.
But on different ROMs can be different flashing guides, for example, we can take "Validus" ROM:
VALIDUS
Flashing instructions are : (I'm going to quote them)
So in overall, that mean at first you've to have CWM (ClockWorkMod Recovery) (but I think that it's not necessary if you would flash boot.img with it either way)
Secondly, you've to put the entire ROM in your SD Card (not in phone memory), you can include gapps as well,
Third, you need to extract the file named "boot.img" from the ROM which you've downloaded (Now i'm talking about VALIDUS and ONLY IF YOU'RE GOING TO INSTALL THIS ROM EXACTLY), but don't remove it from .rar/.zip.
After you've done everything what is written above, you can flash boot.img using the command prompt and fastboot file, which you were using to unlock your bootloader.
The command is this : fastboot flash boot boot.img
Then, write fastboot reboot and as soon as your LED will change color, push the volume up rocker and then you will be in recovery. After that, go to "Apply Update" --> "Choose from files" or sth (don't remember now), --> "Validus.zip/.rar". and optional you can flash gapps either.
And then pus the button to "Reboot now".
That's all - you've newest Validus build.
But the main point is that for example you would take Pabx rom, you'll have to do everything using CMD (fastboot)
PABX's ROM YUGA L
Look at yourself and compare everything.
Validus ROM is customized than Pabx ROM. It has more customatizations either : APPS, Control, Mods, Gesture and etc., and Pabx ROM is pure-stock L (I think).
I hope I anwered to all ur questions, if not - quote me
Click to expand...
Click to collapse
Thank you very much for your reply and yes perhaps you are right. I should not mess with my phone's software. My skill and knowledge on this is extremely limited. I think I did unlock my bootloader but I will leave it on that. My phone still runs fine for now. Unless I find some tutorial videos which I can understand, I will stay away from flashing my phone
Thanks again for help.
Kathmandu13 said:
Thank you very much for your reply and yes perhaps you are right. I should not mess with my phone's software. My skill and knowledge on this is extremely limited. I think I did unlock my bootloader but I will leave it on that. My phone still runs fine for now. Unless I find some tutorial videos which I can understand, I will stay away from flashing my phone
Thanks again for help.
Click to expand...
Click to collapse
Well, you shouldn't be afraid of flashing stock 5.0.x, as you're not flashing custom kernels. To flash pabx's rom, you just need to connect your phone via USB to PC, whilst holding Volum +. (Phone need to be turn on). Then blue led will show up and you're ready to write commands via CMD prompt, wich you can open in sdk/platform-tools/ (or simply download ADB and fastboot drivers).
To open them, just with holding RMB click on "open command prompt here", then write this command:
fastboot devices
Click to expand...
Click to collapse
And if it will show you like CXXXXXX (or something like that, if not even first letter is C, it's alright), you're ready to go.
Then download all files needed from Pabx site (ROM and gapps). Extract both in ADB-Fastboot driver's folder (in which are fastboot.exe, adb.exe). It should be these files: userdata.img, system.img, boot.img.
And then you just simple need to flash these IMGs:
fastboot flash userdata userdata.img
fastboot flash system system.img
fastboot flash boot boot.img
Click to expand...
Click to collapse
And then just type
fastboot reboot
Click to expand...
Click to collapse
.
Your phone will reboot and will load ~ 1-3 minutes.
Well, personally I don't encourge you to do that, I'm just suggesting. It's your choice to do that or not. I just have given you all the instructions.
Hope I helped you
Hi,
I have problem unlocking bootloader on my C6603. I successfully rooted it with easyroot, made TA backup, my phone says that unlocking bootloader is allowed but whenever i tried to do this it either fails or goes to bootloop. I was investigating a bit more and found some information saying that phone has to be simlock free with some certificates(???) and s1tool gives me answer that my simlock unlock is tampered. Is it the reason why i can't unlock bootloader? If so, is there any way to unlock it anyway?
Thanks in advance.
Sent from my C6603 using XDA Free mobile app
Unlocking Xperia Z bootloader
Hi guys
I 've got a trouble, i tried to unlock bootloader by flashtool and "classic" method. I've done it step by step like in video tutorial but finally cmd shows me that command.
I've checked it on other computer but it also failed.Installed all components + pc com.
Greetings.
Please someone tell me where is this goddamned "fastboot_with_Android_USB_file.rar" to download? It's almost four hours im searching everywhere to find it,but i can't.
Xperia Z2 stuck! help!!!
Hi guys, yesterday i tried to relock th bootloader of my xperia z2, and it was really easy, but now it doesn´t turn on, it´s stuck in flash mode, does anyone know what can i do to fix this? thanks a lot!
nikin101 said:
Hi guys, yesterday i tried to relock th bootloader of my xperia z2, and it was really easy, but now it doesn´t turn on, it´s stuck in flash mode, does anyone know what can i do to fix this? thanks a lot!
Click to expand...
Click to collapse
Did you relock while on a custom rom or kernel? Try flashing a stock FTF.
Sent from my C6603
kingvortex said:
Did you relock while on a custom rom or kernel? Try flashing a stock FTF.
Sent from my C6603
Click to expand...
Click to collapse
Yes, i think i did that. And how do i do that? And where can i download the stock FTF? Thanks, i'm new in this
nikin101 said:
Yes, i think i did that. And how do i do that? And where can i download the stock FTF? Thanks, i'm new in this
Click to expand...
Click to collapse
How to package and flash stock roms in FTF format
I wrote that guide for the Xperia Z, but the method is identical for the Z2. You will probably have to wipe data if you're coming from a custom rom.
Sent from my C6603
kingvortex said:
How to package and flash stock roms in FTF format
I wrote that guide for the Xperia Z, but the method is identical for the Z2. You will probably have to wipe data if you're coming from a custom rom.
Sent from my C6603
Click to expand...
Click to collapse
I can't find the words to thank you! I will try that today. Thanks a lot.
nikin101 said:
I can't find the words to thank you! I will try that today. Thanks a lot.
Click to expand...
Click to collapse
You're welcome.
Sent from my C6603

Unlocking bootloader and installing Custom recovery [Sprout4] [Marshmallow 6.0]

So i have successfully installed a custom recovery on my phone running Marshmallow and also unlocked the bootloader!
Its quite simple actually!
I am not responsible for any damage you make to your phone!
Steps-
1. Download the zip file from the link and extract it.
2. Install both the drivers and then proceed!(The drivers are universal and work for Windows 98,xp,vista,7,8,8.1,10 but in 8,8.1,10 you might need to turn off the digital signature verification-Make good use of google)
3.After installing the drivers , connect your phone in switched on and remember to turn on usb debugging in the dev options!
4. Open the unlock_bootloader_... and run the .bat file and follow the on screen steps( All the data will be formatted so make a backup beforehand)
5.After doing this you will void your warranty so make sure you know what you are doing!
6. Open the one click installer folder and replace the recovery.img with any recovery that you want.
7. Now again connect your phone in switched on mode and usb debugging on and run the .bat file of recovery installer.. and follow the on screen steps!
8.As soon as the the recovery installation is over do not let teh phone reboot just press the vol up button as the installation process stops and then go to recovery!
9.Boom!! Now you have a phone with unlocked bootloader and a custom recovery installed on marshmallow!!
10.Flash custom Kernels,Boot Animations, Logos and root your phone running marshmallow and brag!
Downloads--
Bootloader and Recovery.zip(27.4 MB)
Press Thanks:good: if this helped and if you have any querries just use the section below!
Recovery Kernel?
Hi bro just a quick question did you use the MM kernel in the custom recovery?
On our None AOSP standard Mediatek devices the rom does a Kernel check to ensure both the boot and recovery Kernels are of the same version eg KK boot = KK Recovery LP boot = LP Recovery so I just wondered if the MM Kernel still works in the Philz recovery or are you still using a kernel from a older version of android eg KK or LP.
Hope that makes sense to you :laugh:
How to open the unlock_bootloader ??? There is no such option
how about rooting? what method did you use?
bigrammy said:
Hi bro just a quick question did you use the MM kernel in the custom recovery?
On our None AOSP standard Mediatek devices the rom does a Kernel check to ensure both the boot and recovery Kernels are of the same version eg KK boot = KK Recovery LP boot = LP Recovery so I just wondered if the MM Kernel still works in the Philz recovery or are you still using a kernel from a older version of android eg KK or LP.
Hope that makes sense to you :laugh:
Click to expand...
Click to collapse
Actually i didn't work on the recovery, i just made the one click thing, i inserted any random recovery i found working on 6.0 .
cheeze.keyk said:
how about rooting? what method did you use?
Click to expand...
Click to collapse
i flashed a custom kernel and then the super su beta zip
akash.kotwani said:
How to open the unlock_bootloader ??? There is no such option
Click to expand...
Click to collapse
in the zip you will find a .bat file, open that and follow on screen instructions
How to relock bootloader if I ever want to?
net_freak said:
How to relock bootloader if I ever want to?
Click to expand...
Click to collapse
Well i did not make anything that can do that but you'll probably find it in other threads. You can also flash bootloader.using the stock rom file via sp flash tools to relock it just untick everything else but bootloader!
Unlocking bootloader is necessary? Can I not just do it with it locked bootloader?
net_freak said:
Unlocking bootloader is necessary? Can I not just do it with it locked bootloader?
Click to expand...
Click to collapse
You can but unlocking the bootloader opens up many other things for devs!
divyesh bansal said:
You can but unlocking the bootloader opens up many other things for devs!
Click to expand...
Click to collapse
Will the fastboot method to flash twrp work ? I'm on Android 6.0
net_freak said:
Will the fastboot method to flash twrp work ? I'm on Android 6.0
Click to expand...
Click to collapse
Yes it does, the tool is also all about it. In the one click recovery intaller folder replace the recovery.img with your twrp(you will have to rename twrp.img file to recovery.img) and follow the steps in the first post in this thread!
divyesh bansal said:
Yes it does, the tool is also all about it. In the one click recovery intaller folder replace the recovery.img with your twrp(you will have to rename twrp.img file to recovery.img) and follow the steps in the first post in this thread!
Click to expand...
Click to collapse
Thanks. . can I use all in one tool kit by @Faiyaz5yaz for the same

[TWRP][EXPERIMENTAL] suzuran twrp 3.0

Hello people,
I was able to successfully build twrp 3.0 for suzuran (our device, duh!) and thought I'd share the recovery.img so you can test and see what works and what doesn't.
The recovery was built in a CM13 similar environment (PAC), so there might be some issues when working with stock kernel.
Since this is an experimental build (I tested main functionalities and they work, but didn't get down to the nitty-gritty), here's a small disclaimer:
By flashing or booting the attached recovery you're risking damaging you device, or losing the data on your device!
Neither I nor anyone else but YOU is responsible should any bad unintended problems appear!
If you're feeling adventurous then feel free to flash the recovery.img (along with Androplus kernel) and try the sweetness that is TWRP 3.0 :good:
Download link:
April 3, 2016 (3.0.1)
March 25, 2016
March 21, 2016
March 12, 2016
Known issues:
Temperature reading is botched
Crypto might not be working, like AT ALL
usb connection doesn't work (only if you use this recovery with Androplus kernel)
There could be more problems, which is why this is EXPERIMENTAL for now
And now let's get to the sources!
kernel:
[url]https://github.com/oshmoun/kernel/tree/aosp/LA.BF64.1.2.2_rb4.7[/URL]
device sources:
[url]https://github.com/oshmoun/device-sony-suzuran/tree/master[/URL]
[url]https://github.com/oshmoun/device-sony-kitakami/tree/master[/URL]
[url]https://github.com/SonyCM/device-sony-common/commits/cm-13.0[/URL]
And now to thank the people who helped in this endeavor:
TWRP team for the awesome recovery!
@nilezon for the TWRP flags (which I still need to go through to check if I missed/need anything, especially crypto flags...)
FXP team for device sources, Especially @adfad666
All of the Sony AOSP contributors, they're awesome people!
It doesn't work on my Android 6.0 device:crying:
doesn't work on sony mm, stuck at sony logo
iMaeGoo said:
It doesn't work on my Android 6.0 device:crying:
Click to expand...
Click to collapse
tanto124 said:
doesn't work on sony mm, stuck at sony logo
Click to expand...
Click to collapse
Could you tell me if you have E5823 or E5803, I have an E5823 and it's working fine.
Also, are you sure you're not FLASHING the recovery.img? You need to just BOOT it directly from fastboot
oshmoun said:
Could you tell me if you have E5823 or E5803, I have an E5823 and it's working fine.
Also, are you sure you're not FLASHING the recovery.img? You need to just BOOT it directly from fastboot
Click to expand...
Click to collapse
E5823, version 32.1.A.1.163, bootloader unlocked, in fastboot mode, using command "fastboot boot TWRP3.img".
And it stucks at SONY logo.
iMaeGoo said:
E5823, version 32.1.A.1.163, bootloader unlocked, in fastboot mode, using command "fastboot boot TWRP3.img".
And it stucks at SONY logo.
Click to expand...
Click to collapse
this is really weird, did the MM update also change something in the bootloader in an inconvenient way?
Could you try the other recovery.img from nilezon's thread? If that boots using "fastboot boot recovery.img" then we'll know the problem is somewhere in the .img itself
EDIT: oh, also could you please check if your download wasn't corrupt? Here's the md5 hash of the file so you can check
69650eaccdd8b24a3efc0ef1b4bdffb8
oshmoun said:
this is really weird, did the MM update also change something in the bootloader in an inconvenient way?
Could you try the other recovery.img from nilezon's thread? If that boots using "fastboot boot recovery.img" then we'll know the problem is somewhere in the .img itself
EDIT: oh, also could you please check if your download wasn't corrupt? Here's the md5 hash of the file so you can check
69650eaccdd8b24a3efc0ef1b4bdffb8
Click to expand...
Click to collapse
69650eaccdd8b24a3efc0ef1b4bdffb8
The img's MD5 is right.
I'll try to boot Z5C_TWRP_152_v2_nilezon on my device later.
It worked before I upgraded to MM.
oshmoun said:
this is really weird, did the MM update also change something in the bootloader in an inconvenient way?
Could you try the other recovery.img from nilezon's thread? If that boots using "fastboot boot recovery.img" then we'll know the problem is somewhere in the .img itself
EDIT: oh, also could you please check if your download wasn't corrupt? Here's the md5 hash of the file so you can check
69650eaccdd8b24a3efc0ef1b4bdffb8
Click to expand...
Click to collapse
I have no idea.
Z5C_TWRP_152_v2_nilezon doesn't work on MM.
I flash Android 5.1 and try your TWRP3.0, still stuck at SONY logo(with no LED light).
Z5C_TWRP_152_v2_nilezon can work on 5.1.
Now I'm flashing MM again.
iMaeGoo said:
I have no idea.
Z5C_TWRP_152_v2_nilezon doesn't work on MM.
I flash Android 5.1 and try your TWRP3.0, still stuck at SONY logo(with no LED light).
Z5C_TWRP_152_v2_nilezon can work on 5.1.
Now I'm flashing MM again.
Click to expand...
Click to collapse
Thanks! Guess the issue lies in the MM update somewhere.
You just said that nilezon's recovery works on 5.1, but did you try it after flashing 5.1, or are you basing that statement on previous tests?
The issue here might be that you didn't downgrade the bootloader when you flashed 5.1 again, which would mean the issue will persist.
Hello,
I tried booting(didn't flash) with MM and it seemed to boot into recovery fine. Used it to do a cache wipe, but afterwards phone is stuck on boot screen. I can turn it off with power + volume, but it doesn't seem like I can go back to fast boot.
t4656 said:
Hello,
I tried booting(didn't flash) with MM and it seemed to boot into recovery fine. Used it to do a cache wipe, but afterwards phone is stuck on boot screen. I can turn it off with power + volume, but it doesn't seem like I can go back to fast boot.
Click to expand...
Click to collapse
You should be able to go into fastboot mode by turning device off, holding vol+ button, then connecting the device to your computer through usb
oshmoun said:
You should be able to go into fastboot mode by turning device off, holding vol+ button, then connecting the device to your computer through usb
Click to expand...
Click to collapse
Yeah thanks. Took something like 10 tries before it finally went into fastboot. Not sure what went wrong there. Also on my first try I was able to boot into your build of twrp. But afterwards when I try it just gets stuck on the logo again.
t4656 said:
Yeah thanks. Took something like 10 tries before it finally went into fastboot. Not sure what went wrong there. Also on my first try I was able to boot into your build of twrp. But afterwards when I try it just gets stuck on the logo again.
Click to expand...
Click to collapse
This is so freaky what the heck!!!
Could you flash bootloader from 5.1 ftf and see if it works properly then?
I'll (finally) update to MM today , so I'll witness the issues first hand.
oshmoun said:
Thanks! Guess the issue lies in the MM update somewhere.
You just said that nilezon's recovery works on 5.1, but did you try it after flashing 5.1, or are you basing that statement on previous tests?
The issue here might be that you didn't downgrade the bootloader when you flashed 5.1 again, which would mean the issue will persist.
Click to expand...
Click to collapse
I tried nilezon's recovery after flashing 5.1 and it worked.
I use FlashTool to write FTF file to my phone fully, include kernel.
Maybe it's my problem...
Thank you for your patience!
iMaeGoo said:
I tried nilezon's recovery after flashing 5.1 and it worked.
I use FlashTool to write FTF file to my phone fully, include kernel.
Maybe it's my problem...
Thank you for your patience!
Click to expand...
Click to collapse
nope, not your problem, it's everyone's
seems like my twrp version just refuses to boot sometimes.
Was able to successfully replicate the fastboot issue on 5.1 bootloader, so it's definitely this recovery.
Now the question is if it's a TWRP 3 issue, or just in the way I built it
EDIT: I guess this post answers my question
http://forum.xda-developers.com/showpost.php?p=65808636&postcount=137
another twrp 3 recovery is having the same issue
guess I'll have to make this recovery flashable in order for it to work properly
EDIT 2: wow, Androplus kernel seems to go well with TWRP 3. Updated first post with new instructions on how to use this.
oshmoun said:
nope, not your problem, it's everyone's
seems like my twrp version just refuses to boot sometimes.
Was able to successfully replicate the fastboot issue on 5.1 bootloader, so it's definitely this recovery.
Now the question is if it's a TWRP 3 issue, or just in the way I built it
EDIT: I guess this post answers my question
http://forum.xda-developers.com/showpost.php?p=65808636&postcount=137
another twrp 3 recovery is having the same issue
guess I'll have to make this recovery flashable in order for it to work properly
EDIT 2: wow, Androplus kernel seems to go well with TWRP 3. Updated first post with new instructions on how to use this.
Click to expand...
Click to collapse
Can not detect external SD or USB OTG (yet)
Can not detect external SD or USB OTG (yet)
Can not detect external SD or USB OTG (yet)
This will do the job until a proper dev makes a better version.
Maybe I had better wait...:crying::crying::crying:
iMaeGoo said:
Can not detect external SD or USB OTG (yet)
Can not detect external SD or USB OTG (yet)
Can not detect external SD or USB OTG (yet)
This will do the job until a proper dev makes a better version.
Maybe I had better wait...:crying::crying::crying:
Click to expand...
Click to collapse
ummm, my sdcard is getting detected :|
I'll post screenshots soon
EDIT: attached screenshots
oshmoun said:
ummm, my sdcard is getting detected :|
I'll post screenshots soon
EDIT: attached screenshots
Click to expand...
Click to collapse
Can external storages be found in Android system?
iMaeGoo said:
Can external storages be found in Android system?
Click to expand...
Click to collapse
everything concerning external sdcard function is working here as far as i tested (both in Stock mm rom and twrp3)
oshmoun said:
Could you tell me if you have E5823 or E5803, I have an E5823 and it's working fine.
Also, are you sure you're not FLASHING the recovery.img? You need to just BOOT it directly from fastboot
Click to expand...
Click to collapse
it's E5823 running 32.1.A.1.163 . I am sure that I was just booting , downloaded file is okay .

[Kernel] [6.0.1] [23.5.A.1.291] [Advanced stock with TWRP] [UB]

Stock kernel with TWRP recovery SGP621
Sony RIC disabled
TWRP 3.0.2
Download
From here and unzip
Flash via flashtool or fastboot
Code:
fastboot flash boot boot.img
Root
Flash this in recovery
Credits
tobias.waldvogel for his awesome tool
TWRP team
shoey63 for guiding me
there is a low interest in the devs for this tablet. So, everything is appreciated..
Thanks for your work, in an few hours I'll test it.
wulfiss said:
there is a low interest in the devs for this tablet. So, everything is appreciated..
Thanks for your work, in an few hours I'll test it.
Click to expand...
Click to collapse
you are welcome buddy!
Thanks alot, I'd love to have TWRP 3.0.2 on stock rom.
But I can seem to get it to work, tried on a customized US an a customized DE stock image, latest version.
Doesn't boot on either, screen stays black when I try to turn on the tablet.
ipharus said:
Thanks alot, I'd love to have TWRP 3.0.2 on stock rom.
But I can seem to get it to work, tried on a customized US an a customized DE stock image, latest version.
Doesn't boot on either, screen stays black when I try to turn on the tablet.
Click to expand...
Click to collapse
No boot screen at all? What's your tablet model?
SGP-612
ipharus said:
SGP-612
Click to expand...
Click to collapse
Is your bootloader unlocked? If so send me your kernel.sin from the firmware.
codfx said:
Is your bootloader unlocked? If so send me your kernel.sin from the firmware.
Click to expand...
Click to collapse
Yes bootloader is unlocked. kernel.sin for Custom DE attached (SGP612_Customized DE_1290-4946_23.5.A.1.291_R2D)
I don't get it to work either. SGP611, using SGP611_23.5.A.1.291_1290-0168_R4D customized UK. Won't boot, only flashes its red little light. Did you find any solution to it? Would be awesome to get this kernel.
Hi,
Have I sent you the correct file? Did you get the time to have a look at it?
No stress, just wonderin :angel:
is there a way to unlock bootloader using kinds of special hardware (like HTC xtc2clip)
(thanks O2 for locking the bootloader -_-)
Hey
Something new about black screen ?
Same problem here.
SGP621
Thank you
vmille said:
Hey
Something new about black screen ?
Same problem here.
SGP621
Thank you
Click to expand...
Click to collapse
If you are getting a black screen after flashing the kernel, just force restart the device. Then the device will boot fine.
Could a version of this be build with the device name "scorpion"? It won't let me install this ROM since the device name doesn't match (it seems to be empty in this image whereas that ROM requires it to be "scorpion").
Edit: nevermind, figured out I can modify the script in side the ROM to remove the check instead.
Thanks for a working TWRP for my old tablet
codfx said:
If you are getting a black screen after flashing the kernel, just force restart the device. Then the device will boot fine.
Click to expand...
Click to collapse
I get a black screen as well, tried to force reboot, same issue.
danw84 said:
I get a black screen as well, tried to force reboot, same issue.
Click to expand...
Click to collapse
what's your device model?
codfx said:
what's your device model?
Click to expand...
Click to collapse
SPG611
danw84 said:
SPG611
Click to expand...
Click to collapse
This kernel is only for SGP621. It's clearly mentioned in OP.
Think you!
Not easy for an old man, but after several times it went perfect.
Not able to tell you what I did exactly but I have SGP621, french 6.01.
SGP612 boot.img
Hi,
I made a boot.img for the SGP612 [6.0.1] [23.5.A.1.291] unlocked BL.
Sony RIC disabled
TWRP 3.0.2
(DRM fix)
Root and Xposed is NOT included. I recommend flashing Magisk v12 later in TWRP and enable Magisk Core Only Mode and Magisk Hide in the settings. Then it will pass the SafetyNet test and you can use su.
To flash the boot.img, put your SGP612 into fastboot mode (Volume Up + connect USB) and then run:
Code:
fastboot flash boot boot.img
If you have a backup of your TA partition, before you unlocked, see the rootkernel thread by tobias.waldvogel, how the DRM fix works.
Thanks to codfx for give me the idea for a SGP612 counterpart and to tobias.waldvogel for his tool :good:

[KERNEL] 7.1.1 [41.2.A.2.199] Xperia XZ [F8331/F8332]

Hey guys, here are the modified rootable kernels for the Xperia XZ [F8331 & F8332] 7.1.1 fw
Kernel F8332
Kernel F8331
Thanks to tobias.waldvogel for his awesome resources.
Don't forget to flash the recovery. Here's the link
Recovery
Also, recovery can be accessed only through the official way i.e.
Power off >> Press the power key and the volume down key simultaneously >> As soon as the SONY logo appears, release ONLY the power key, don't release the volume down key >> After 20-30 seconds the device will enter recovery mode.​
arjun.arora said:
Hey guys, here's the modified rootable kernel for the Xperia XZ Dual 7.1.1 fw
Kernel
Thanks to tobias.waldvogel for his awesome resources.
Don't forget to flash the recovery. Here's the link
Recovery
Also, recovery can be accessed only through the official way i.e.
Power off >> Press the power key and the volume down key simultaneously >> As soon as the SONY logo appears, release ONLY the power key, don't release the volume down key >> After 20-30 seconds the device will enter recovery mode.​
Click to expand...
Click to collapse
Thank you
Working fine
DRM Fixed and RIC enabled
karrouma said:
Thank you
Working fine
DRM Fixed and RIC enabled
Click to expand...
Click to collapse
Glad it worked for you..
thanks a lot
Can someone please upload the same kernel for F8331 (NOT dual)? Thanks.
Papanik said:
Can someone please upload the same kernel for F8331 (NOT dual)? Thanks.
Click to expand...
Click to collapse
same kernel works with both single and dual
karrouma said:
same kernel works with both single and dual
Click to expand...
Click to collapse
OK thanks a lot.
Papanik said:
OK thanks a lot.
Click to expand...
Click to collapse
I'm not quite sure of that buddy.. Has someone tested it on the single sim version..
Extract and share the kernel.sin from the ftf file.. I'll modify it..
arjun.arora said:
I'm not quite sure of that buddy.. Has someone tested it on the single sim version..
Extract and share the kernel.sin from the ftf file.. I'll modify it..
Click to expand...
Click to collapse
No different between F8332 and F8331 kernel or fota-kernel (recovery)... Only difference are system.*.sin cach.*.sin userspace.*.sin oem.*.sin
please give me some detail instruction to install it!
my Knowledge: backup TA -> unlock bootloader -> flash this kernel -> flash recover -> flash SuperSU -> done??
after that, if i want to roll back to stock, i must do that: push TA back to phone by recovery -> reflash stock rom by flashtool.??
is this right?
and one more question : is this kernel use for stock rom and all thing will work fine??
link_it said:
please give me some detail instruction to install it!
my Knowledge: backup TA -> unlock bootloader -> flash this kernel -> flash recover -> flash SuperSU -> done??
after that, if i want to roll back to stock, i must do that: push TA back to phone by recovery -> reflash stock rom by flashtool.??
is this right?
and one more question : is this kernel use for stock rom and all thing will work fine??
Click to expand...
Click to collapse
I don't know much about the ta backup part, please make a search..
link_it said:
please give me some detail instruction to install it!
my Knowledge: backup TA -> unlock bootloader -> flash this kernel -> flash recover -> flash SuperSU -> done??
after that, if i want to roll back to stock, i must do that: push TA back to phone by recovery -> reflash stock rom by flashtool.??
is this right?
and one more question : is this kernel use for stock rom and all thing will work fine??
Click to expand...
Click to collapse
Are you on FW41 (android 7.1.1)?
If "YES" you must downgrade to MM rom and not patched "dirty-cow" vulnerable for backup TA partition (if you don't backed up later. If you have ta backup skip this step)
Then update to N 7.1.1
After update to 7.1.1:
1- unlock bootloader (backup data and internal sd, device wiped all data!)
2- go to "fastboot mode" (power off phone, when hold volume up plug your phone to pc, blue light led must be on)
3- flash that image for drm-fix and disable dm-verify with this code
Code:
fastboot flash boot boot.img
4- reboot phone complete
Code:
fastboot reboot
5- again power off and go to fastboot mode. And flash recovery now:
Code:
fastboot flash recovery twrp-***-kagura.img
fastboot reboot
6- now go to recovery and install supersu zip package.
If you want go to complete stock you need TA.img (save that several place in your PC and better save on cloud storage like google drive)
If you need, flash TA.img and flash FTF stock rom and phone back to theirs factory state.
** and for knowledge: this is not custom kernel!!!
This is custom boot.img. The kernel inside that file is completely stock. Only "ramdisk" patched for allow you to root your device and fix drm.
completery understand
GenomeX said:
Are you on FW41 (android 7.1.1)?
If "YES" you must downgrade to MM rom and not patched "dirty-cow" vulnerable for backup TA partition (if you don't backed up later. If you have ta backup skip this step)
Then update to N 7.1.1
After update to 7.1.1:
1- unlock bootloader (backup data and internal sd, device wiped all data!)
2- go to "fastboot mode" (power off phone, when hold volume up plug your phone to pc, blue light led must be on)
3- flash that image for drm-fix and disable dm-verify with this code
Code:
fastboot flash boot boot.img
4- reboot phone complete
Code:
fastboot reboot
5- again power off and go to fastboot mode. And flash recovery now:
Code:
fastboot flash recovery twrp-***-kagura.img
fastboot reboot
6- now go to recovery and install supersu zip package.
If you want go to complete stock you need TA.img (save that several place in your PC and better save on cloud storage like google drive)
If you need, flash TA.img and flash FTF stock rom and phone back to theirs factory state.
** and for knowledge: this is not custom kernel!!!
This is custom boot.img. The kernel inside that file is completely stock. Only "ramdisk" patched for allow you to root your device and fix drm.
Click to expand...
Click to collapse
many thanks for your guide. Since Z3, i've never unlock bootloader yet, so i have a bit confused because of TA partition
i'll do it on next week, after my holiday
I tried but it didn't boot.
Pedimento said:
I tried but it didn't boot.
Click to expand...
Click to collapse
Working fine with my xz dual
karrouma said:
Working fine with my xz dual
Click to expand...
Click to collapse
Mine is XZ , not dual.
Pedimento said:
Mine is XZ , not dual.
Click to expand...
Click to collapse
Same kernek. It should works
Followed the guide but it didn't boot. The problem is boot.img i think.
karrouma said:
Same kernek. It should works
Click to expand...
Click to collapse
Me too. It stuck on Sony logo. Xperia xz single sim
djgigi94 said:
Me too. It stuck on Sony logo. Xperia xz single sim
Click to expand...
Click to collapse
Share the single sim kernel.sin from the firmware..

Categories

Resources