Develop Bugs

[Q] Will installing new ROM wipe X-Parts CWM?

Hi, question: I failed time and again to get CWM working, but finally got it to work using x-parts. However, x-parts is keen to point out that it is not a fully fledged recovery and that "if you wipe the system partition for any reason, it will be gone!".
Does this not mean that if I boot into recovery and install a new ROM (Going for the FXP CM10 one, if it matters), then when I wipe the phone beforehand I'll also wipe my CWM install, thus completely bricking the device? Would appreciate any thoughts, thanks

Artemicion said:
Hi, question: I failed time and again to get CWM working, but finally got it to work using x-parts. However, x-parts is keen to point out that it is not a fully fledged recovery and that "if you wipe the system partition for any reason, it will be gone!".
Does this not mean that if I boot into recovery and install a new ROM (Going for the FXP CM10 one, if it matters), then when I wipe the phone beforehand I'll also wipe my CWM install, thus completely bricking the device? Would appreciate any thoughts, thanks
Click to expand...
Click to collapse
Yes, if you wipe the system partition there will be no more CWM. For CM10, you need to flash a custom kernel for it to work. This custom kernel will usually come with a CWM recovery so it will not be wiped when you flash a new ROM.
僕のLT18iから送られてきた

Thanks. But, to clarify, once I flash new CM10/Jellybean Kernel, my current Gingerbread install will also completely cease to function right? And I'd need to flash back to something earlier to get it to work, if I so desired?

Artemicion said:
Thanks. But, to clarify, once I flash new CM10/Jellybean Kernel, my current Gingerbread install will also completely cease to function right? And I'd need to flash back to something earlier to get it to work, if I so desired?
Click to expand...
Click to collapse
Is your bootloader unlocked?
And yes you will have to flash GB ftf using flashtool
Sent from my LT18i

Yeah, I unlocked the bootloader and rooted it ages ago, but have since neglected actually updating the ROM, decided I can't live in a GB world anymore though.
So, as I understand it, process would be flash a new GB kernel to get CWM > Wipe Everything > Install the relevant ROM and GApps > Done? Does this ROM installation include the update to JB kernel then? Thanks

Artemicion said:
Yeah, I unlocked the bootloader and rooted it ages ago, but have since neglected actually updating the ROM, decided I can't live in a GB world anymore though.
So, as I understand it, process would be flash a new GB kernel to get CWM > Wipe Everything > Install the relevant ROM and GApps > Done? Does this ROM installation include the update to JB kernel then? Thanks
Click to expand...
Click to collapse
If I am not mistaken the kernel boot img should be inside the ROM zip. Check the ROM zip. Just flash the boot img using fastboot, boot into CWM recovery and flash ROM & gapps.
僕のLT18iから送られてきた

Ah, ok, well this brings me full circle. Because I'm trying to follow the boot instructions to do so, but:
fastboot -i 0xfce flash boot boot.img
doesn't work. I've taken the boot.img out of the ROM, and put it in the platform-tools folder. But whenever I try this line, it says it can't boot it, and quotes "no error" (no longer at home so can't quote the exact error, but it's something like that). I assumed the problem was me lacking CWM, hence was trying to install that first. Fastboot devices DOES show the device, and both fastboot and adb commands work in a terminal, but I just can't get it to boot into the ROM recovery for Cyanogenmod. Driving my crazy! Thanks

fastboot flash boot boot.img, if I'm not mistaken, is the right command. I use flashtool
Sent from my Xperia Arc S using xda premium

Artemicion said:
Ah, ok, well this brings me full circle. Because I'm trying to follow the boot instructions to do so, but:
fastboot -i 0xfce flash boot boot.img
doesn't work. I've taken the boot.img out of the ROM, and put it in the platform-tools folder. But whenever I try this line, it says it can't boot it, and quotes "no error" (no longer at home so can't quote the exact error, but it's something like that). I assumed the problem was me lacking CWM, hence was trying to install that first. Fastboot devices DOES show the device, and both fastboot and adb commands work in a terminal, but I just can't get it to boot into the ROM recovery for Cyanogenmod. Driving my crazy! Thanks
Click to expand...
Click to collapse
You don't need to add -i 0xfce to the command. Just type fastboot flash boot <name of boot image>.img
僕のLT18iから送られてきた

tangosierra_ said:
fastboot flash boot boot.img, if I'm not mistaken, is the right command. I use flashtool
Sent from my Xperia Arc S using xda premium
Click to expand...
Click to collapse
Thanks, I'll give that a go, not going to be able to try for a few days now, but will. FYI, I took the line of code I was trying directly from the Cyanogenmod wiki for Anzu

tangosierra_ said:
fastboot flash boot boot.img, if I'm not mistaken, is the right command. I use flashtool
Sent from my Xperia Arc S using xda premium
Click to expand...
Click to collapse
Ok, so finally got home to try this, still throwing this out: "error: cannot load 'boot.img': No error"
I've got the right boot.img in my platform-fools folder, the relevant CM build on my SD Root along with GApps. Drivers are definitely installed correctly as fastboot devices shows the device, as do adb command when it's on - anyone got any suggestions? Would be immensely grateful if this confounded problem could be solved. Thanks

Artemicion said:
Ok, so finally got home to try this, still throwing this out: "error: cannot load 'boot.img': No error"
I've got the right boot.img in my platform-fools folder, the relevant CM build on my SD Root along with GApps. Drivers are definitely installed correctly as fastboot devices shows the device, as do adb command when it's on - anyone got any suggestions? Would be immensely grateful if this confounded problem could be solved. Thanks
Click to expand...
Click to collapse
What is the name of the .img file? It can't have any spaces inside.
僕のLT18iから送られてきた

popthosegaskets said:
What is the name of the .img file? It can't have any spaces inside.
僕のLT18iから送られてきた
Click to expand...
Click to collapse
Looks to just be "boot.img" to me, no spaces or anything.

Have you tried flashtool?
Sent from my LT18i using xda premium

tangosierra_ said:
Have you tried flashtool?
Sent from my LT18i using xda premium
Click to expand...
Click to collapse
No, guess I'll try that next. As I remember, that's what I used to flash in order to root it ages ago. Thanks

Flashable TWRP v2.8.7.0 for Sony Z3+ E6553 Ivy_Kitakami

Introduction
Disclaimer: While this TWRP has been tested by myself on my own device to flash, wipe and backup, I make no warranties as to it's performance. Use at your own risk.
WARNING: flashable version contains a kernel boot image which will be flashed to your device along with the recovery image.
Click to expand...
Click to collapse
Installation instructions
This recovery image is for the E6553 single SIM Z3+. Do not use it on another model.
This recovery image requires an unlocked bootloader. You will lose some functionality on your phone if you unlock your bootloader
Do your research and make sure you're using the latest version of the relevant tools if you do decide to unlock.
DO NOT enable MyXperia functionality if you've unlocked your bootloader. You will brick your device.
This first download of this recovery image CANNOT be flashed to your phone and must be used in fastboot mode only
The second download is a flashable recovery
Use the first version to flash the second dual-boot.zip version
Unzip the recovery.zip file to extract the recovery.img file to use in fastboot mode
Code:
C:\>adb reboot bootloader
C:\>fastboot boot recovery.img
C:\>adb push dual-boot.zip /sdcard/dual-boot.zip
C:\>adb push dual-boot.zip.md5 /sdcard/dual-boot.zip.md5
Click to expand...
Click to collapse
Now use the TWRP install feature to install dual-boot.zip. Follow the prompts of the Aroma graphical installer.
CAVEAT: this extends the boot time by about 5 - 10 seconds as ramdisk images need to be unpacked and there's a wait on a keypress to determine whether to enter recovery mode. In order to boot into recovery, press power on. When you see the yellow LED come on then press the down volume button once or twice. You will then boot into TWRP.
NOTE: the dual-boot.zip installs a new 28.0.A.8.251 kernel. If you're using the autoroot kernel from Devries you will need to flash SuperSU to re-root your device
This dual boot/recovery works by flashing the recovery image to the FOTAkernel partition. A custom ramdisk image contains the normal boot image. If the down volume keypress is detected, then the recovery ramdisk is automatically extracted from the FOTAKernel partition and flow of control switches to recovery. If no keypress is detected then the normal ramdisk is extracted and normal android boot ensues.
Those of you who installed version 1.0 please download and install this version 1.1 to fix the error with the startup of the trim area daemon
Download
Binary
Fastboot TWRP Recovery Image v2.8.7.0-e6553-1.0 for Z3+ E6553
Flashable TWRP Recovery Image v2.8.7.0-e6553-1.1 for Z3+ E6553 (MD5: 52d4b7d406308dbd457e8b94210b7c87)
Flashable TWRP Recovery Image v2.8.7.0-e6553-1.1 for Z3+ E6553 - MD5
Sources @ github
device_sony_kitakami
device_sony_ivy
Click to expand...
Click to collapse
Changelog
Code:
Current changelog: -- 29 September 2015
[new] v1.1 fix up problem in combined ramdisk preventing trim area daemon from starting correctly
[new] Flashable recovery - 28 September 2015
[new] Fixed various sys/class issues so that CPU temperature and LED / backlight control work correctly
[new] Updated to use 28.0.A.8.251 kernel (as opposed to the AOSP kernel)
[old] Initial release - 10 September 2015
Click to expand...
Click to collapse
Thanks To
The regular contributors to the Z3+ forum, among others @[NUT], @ChrisJ951, @DHGE, @Devries, @zxz0O0, @Venkat Kamesh, @AndroPlus, @Sacktreter who pass on knowledge and who make the forum a lively and cooperative place
Click to expand...
Click to collapse

People who installed version 1.0 of the Flashable TWRP must please update to version 1.1 to correct a bug.

Awesome work.
Glad you were able to get the screen working for it! Boots up fine w/o issue for me

This is fantastic. Is there any way of getting this to work with a locked bootloader?
Sent from my Xperia Z3+

AMoosa said:
This is fantastic. Is there any way of getting this to work with a locked bootloader?
Sent from my Xperia Z3+
Click to expand...
Click to collapse
I'd venture to suggest that it's highly unlikely that locked bootloader recovery could work. The DM_VERITY is almost a guarantor of that. Just search for CONFIG_DM_VERITY or Verity in the Z3+ forums for more info.
Even if an exploit works, the second it modifies the system partition, the kernel panics and refuses to boot. The only way of preventing that is to flash a new kernel or edit the ramdisk to remove the verity key. And the only way to flash a new kernel / edit the ramdisk is to unlock the bootloader.

Thank you first for development... maazing!
I have unlocked the bootloader via Sony and then used an boot.img from Devries to root as root was my primary goal. I have flashbooted as per instructions the TWRP recovery.img that is provided here by the awesome dl12345 .
However the issue is that I am unable to boot to recovery after rebooting from TWRP. In other words the flashboot works and I am able to make a backup and use TWRP well but it doesn't seem to stick.
Am I doing something wrong. Should I have flashed a ROM first from xperfirm, Flashtools, and/or can I flash a kernel without it effecting the recovery. My knowledge is sketchy but I am totally up for testing if I can help.

elladroid said:
Thank you first for development... maazing!
I have unlocked the bootloader via Sony and then used an boot.img from Devries to root as root was my primary goal. I have flashbooted as per instructions the TWRP recovery.img that is provided here by the awesome dl12345 .
However the issue is that I am unable to boot to recovery after rebooting from TWRP. In other words the flashboot works and I am able to make a backup and use TWRP well but it doesn't seem to stick.
Am I doing something wrong. Should I have flashed a ROM first from xperfirm, Flashtools, and/or can I flash a kernel without it effecting the recovery. My knowledge is sketchy but I am totally up for testing if I can help.
Click to expand...
Click to collapse
This is correct behaviour. You're not actually flashing the recovery image, just temporarily booting a recovery kernel and associated ramdisk. Sony Xperia devices don't have a recovery partition, or more accurately, they don't have a bootloader than can check and load a boot image from a recovery partition.
Technically it's possible to make the boot image check for a ramdisk on another partition and use this instead of the normal ramdisk, but this is step two. Sony should be releasing an open recovery bootloader fairly soon for the Z3+ which will allow this recovery image to be flashed. It's already been released for other devices.
Until Sony releases open recovery for Z3+ or I spend the time trying to implement a feature that probably only has days or weeks of utility (until Sony releases the open recovery for Z3+) , you're stuck with a TWRP that you need to launch every time in fastboot mode.

On the first screen immediately after the TWRP logo comes up, the battery is always being reported at being 50%. Sometimes the correct number is displayed when in the flashing screen. Otherwise works great!
Also, link to Sony Z3+ windows drivers
How to install unsigned drivers in Windows 8.1/10 with secure boot

elladroid said:
Thank you first for development... maazing!
I have unlocked the bootloader via Sony and then used an boot.img from Devries to root as root was my primary goal. I have flashbooted as per instructions the TWRP recovery.img that is provided here by the awesome dl12345 .
However the issue is that I am unable to boot to recovery after rebooting from TWRP. In other words the flashboot works and I am able to make a backup and use TWRP well but it doesn't seem to stick.
Am I doing something wrong. Should I have flashed a ROM first from xperfirm, Flashtools, and/or can I flash a kernel without it effecting the recovery. My knowledge is sketchy but I am totally up for testing if I can help.
Click to expand...
Click to collapse
New version now flashable so that you can boot into recovery...read top post carefully before using.

serrin85 said:
On the first screen immediately after the TWRP logo comes up, the battery is always being reported at being 50%. Sometimes the correct number is displayed when in the flashing screen. Otherwise works great!
Also, link to Sony Z3+ windows drivers
How to install unsigned drivers in Windows 8.1/10 with secure boot
Click to expand...
Click to collapse
Fixed in latest version

http://www.kz3.eu:18998/dual-boot.zip link gives 404 ..

deecept said:
http://www.kz3.eu:18998/dual-boot.zip link gives 404 ..
Click to expand...
Click to collapse
Yes, I've temporarily disabled the link while I resolve a problem relating to the trim area daemon not starting up due to some peculiarity of the dual boot ramdisk. I'll reinstate it as soon as I fix the problem.

dl12345 said:
Yes, I've temporarily disabled the link while I resolve a problem relating to the trim area daemon not starting up due to some peculiarity of the dual boot ramdisk. I'll reinstate it as soon as I fix the problem.
Click to expand...
Click to collapse
Oh, ok, sweet! Looking to flash this to my Z3+. More than happy to test if needed =) Great work on these!!

deecept said:
Oh, ok, sweet! Looking to flash this to my Z3+. More than happy to test if needed =) Great work on these!!
Click to expand...
Click to collapse
Download back online and problem fixed
Those who downloaded the 1.0 please download this 1.1 version and install to correct the problem with trim area daemon startup. Thanks

dl12345 said:
Download back online and problem fixed
Those who downloaded the 1.0 please download this 1.1 version and install to correct the problem with trim area daemon startup. Thanks
Click to expand...
Click to collapse
HI dl12345,
this recovery support Dual model? E6533

hi.question...i get remote: dtb not found error when trying to boot the recovery..any ideas?

didnt get a thing... how do i install?

please, release TWRP for 6533 too
we need custom recovery so bad

Dathrex said:
please, release TWRP for 6533 too
we need custom recovery so bad
Click to expand...
Click to collapse
Pleaseee ????

Brother, please, help us with twrp to E6533, please.
Enviado de meu E6533 usando Tapatalk

Another TWRP 2.8.7 for Fota Partition with working brightness

TWRP updated to 2.8.7.2 including latest commits. Download at the bottom (see Dec25 file). Selinux permissive is set, so, should work on all roms. Remember, unzip and flash in fastboot.
$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
I know there is a bunch of different TWRP recoveries for our Z1, including the official one. Well. This one is for Fota. It was compiled in Z1 build environment with all the appropriate flags. And brightness is working fine. Why brightness is important? Because at maximum brightness your phone will overheat to over 65 degrees during flashing. And thanks to previously wrong value, the brightness level in other TWRPs is 15 times the maximum one.
You can flash this one in fastboot like this: fastboot flash recovery recovery.img. Just make sure that your kernel does not have inbuilt TWRP, because 2 identical recoveries will conflict with each other. Unzip first...
For those who would like to know what's new, look here: https://gerrit.omnirom.org/#/q/project:android_bootable_recovery
In this build, I have also reduced default vibration to 28/28/28, but you can set in Settings to whatever you want.

can you publish your settings to get brightness working ? would be nice to complete official sources from twrp !

hawkeyexp said:
can you publish your settings to get brightness working ? would be nice to complete official sources from twrp !
Click to expand...
Click to collapse
My commit was merged about 2 months ago by Slimroms. See their /device/sony/rhine-common. There is a flag for brightness that should be 255 instead of 4095. So, the changes are not in TWRP sources, but in the rhine tree...
Edit: Here is the commit: https://github.com/SlimRoms/device_sony_rhine-common/commit/7d64159d87d948926ebd40485deb18f9c292abbe

ok will try it out if it works with my tree

Thanks for posting.
I guess since this is FOTA it will not work with roms with recovery in boot like Jaguar?
Sent from my Z1 using Tapatalk

Gawis said:
Thanks for posting.
I guess since this is FOTA it will not work with roms with recovery in boot like Jaguar?
Sent from my Z1 using Tapatalk
Click to expand...
Click to collapse
That's right, but I am planning to update Jaguar's kernel. So, when it is done, I will
post it without recovery, so this one can work.
But it really makes no difference...

optimumpro said:
My commit was merged about 2 months ago by Slimroms. See their /device/sony/rhine-common. There is a flag for brightness that should be 255 instead of 4095. So, the changes are not in TWRP sources, but in the rhine tree...
Edit: Here is the commit: https://github.com/SlimRoms/device_sony_rhine-common/commit/7d64159d87d948926ebd40485deb18f9c292abbe
Click to expand...
Click to collapse
Is working fine - thx !

Does this one work with the aosp android 6.0 rom that's around here?
Sent from my C6903 using Tapatalk

swa100 said:
Does this one work with the aosp android 6.0 rom that's around here?
Sent from my C6903 using Tapatalk
Click to expand...
Click to collapse
Try, but there is a separate branch for TWRP for M. And anyway, M is not usable yet and won't be for a long time...

Thanks for this one!
I do however seem to experience an issue when trying another ROM like CM.
With your ROM I can reboot into this recovery but with CM I get a black screen. When using another older TWRP recovery I used when rooting both ROMS boot fine into recovery.
Sent from my Z1 using Tapatalk

@optimumpro is there any chance to make a flashable zip with it? Thanks

matcho13579 said:
@optimumpro is there any chance to make a flashable zip with it? Thanks
Click to expand...
Click to collapse
Use Rashr app to install this...

Hey there~
For some reason this recovery is not working for me at all. It won't start after flashing it, just a black screen.
The original twrp 2.8.7.0 from twrp.me is working, though. But I'd rather get your version to work because of the brightness control.
Could you help me please? >.<

Snowblond said:
Hey there~
For some reason this recovery is not working for me at all. It won't start after flashing it, just a black screen.
The original twrp 2.8.7.0 from twrp.me is working, though. But I'd rather get your version to work because of the brightness control.
Could you help me please? >.<
Click to expand...
Click to collapse
Are you sure you are doing everything right? Does your kernel have a builtin recovery? If that's the case, you will have problems. Have you updated your bootloader with Emma? Before flashing (in fastboot), do this: fastboot erase recovery; and then fastboot flash recovery recovery.img. Make sure you are not mistyping: the command means fastboot has to flash recovery.img to recovery partition. If you have FOTA, then there is a chance flash recovery may not work.

optimumpro said:
Are you sure you are doing everything right? Does your kernel have a builtin recovery? If that's the case, you will have problems. Have you updated your bootloader with Emma? Before flashing (in fastboot), do this: fastboot erase recovery; and then fastboot flash recovery recovery.img. Make sure you are not mistyping: the command means fastboot has to flash recovery.img to recovery partition. If you have FOTA, then there is a chance flash recovery may not work.
Click to expand...
Click to collapse
Thanks for your answer. I tried flashing it exactly like you suggested, but the result was the same - black screen. My kernel does not have an inbuilt recovery and no, I didn't update my bootloader with Emma. That means I can only use FOTA, right? But I thought this recovery IS indeed for FOTA?
It's strange that the original TWRP is working, but yours doesn't.. even though they're both for FOTA..

Snowblond said:
Thanks for your answer. I tried flashing it exactly like you suggested, but the result was the same - black screen. My kernel does not have an inbuilt recovery and no, I didn't update my bootloader with Emma. That means I can only use FOTA, right? But I thought this recovery IS indeed for FOTA?
It's strange that the original TWRP is working, but yours doesn't.. even though they're both for FOTA..
Click to expand...
Click to collapse
I don't know why it is not working for you. If you post your boot.img, I can put recovery in it..

Snowblond said:
Thanks for your answer. I tried flashing it exactly like you suggested, but the result was the same - black screen. My kernel does not have an inbuilt recovery and no, I didn't update my bootloader with Emma. That means I can only use FOTA, right? But I thought this recovery IS indeed for FOTA?
It's strange that the original TWRP is working, but yours doesn't.. even though they're both for FOTA..
Click to expand...
Click to collapse
Happened to me once.
Try wiping FOTAKernel partition first, with:
Code:
fastboot erase FOTAKernel
and then flash the recovery with
Code:
fastboot flash FOTAKernel recovery.img
where recovery.img is your recovery.

drakonizer said:
Happened to me once.
Try wiping FOTAKernel partition first, with:
Code:
fastboot erase FOTAKernel
and then flash the recovery with
Code:
fastboot flash FOTAKernel recovery.img
where recovery.img is your recovery.
Click to expand...
Click to collapse
Thank you, but it's still a black screen when I try to boot in recovery. :/ I just don't understand why this version won't work with my device but the one from twrp.me without brightness control does .. -.-

Snowblond said:
Thank you, but it's still a black screen when I try to boot in recovery. :/ I just don't understand why this version won't work with my device but the one from twrp.me without brightness control does .. -.-
Click to expand...
Click to collapse
Did you try with another kernel? If it worked then, you can trace the problem to the kernel itself, and not the device or your flashing methodology.

Recovery updated to 2.8.7.2. See OP for download...

[kernel][E6533][Z3+ dual][32.2.A.0.224](RIC disable, TWRP, root,dm-verity)

Hello guys.
Today i will post a kernel that i (just run the wizard to) created for Z3+ dual variant version 32.2.A.0.224. My simple contribution!
This kernel contents:
-RIC disable
-TWRP
-root
-dm-verity
How to install it:
Run this command at command prompt,
fastboot flash boot boot.img
Or.....
Use the Flashtools in a fastboot mode, then choose the Flash option by DoomLord.
Please, Don't thanks me. All the hard work was performed by Mr. Tobias Waldvogel in this thread:
http://forum.xda-developers.com/xperia-z5/development/root-automatic-repack-stock-kernel-dm-t3301605
So, if you like this kernel, please pay a coffe for this guy!
Ps. I already tested on my Z3+ and everything it's okay, so i will not responsable about any brinks or damage in use this kernel!
Ps2: DON'T use this kernel on single model. I don't know whats happens!:silly:

Hello，i've already flashed your boot.img. then i try to flash SuperSu2.6.5.zip. Everything is just fine.
But when i enter SuperSu , the app said that i am in system-less mode.
another app can't detected root mode also.
is there anything wrong with me?
it's dual Z3+
Thanks a lot!

youngcube said:
Hello，i've already flashed your boot.img. then i try to flash SuperSu2.6.5.zip. Everything is just fine.
But when i enter SuperSu , the app said that i am in system-less mode.
another app can't detected root mode also.
is there anything wrong with me?
it's dual Z3+
Thanks a lot!
Click to expand...
Click to collapse
no need to flash superSU i think, it's already included in the kernel.

zemetal said:
no need to flash superSU i think, it's already included in the kernel.
Click to expand...
Click to collapse
Sorry guys, i have the same problem here. After a few minutes i discorvery that i used an 'update' (pretty old) superSu zip.
So, i went to the recovery and flash the supersu2.66.zip. After this all programs detected root nomally.
Sorry for inconvenience.

bruno$0 said:
Sorry guys, i have the same problem here. After a few minutes i discorvery that i used an 'update' (pretty old) superSu zip.
So, i went to the recovery and flash the supersu2.66.zip. After this all programs detected root nomally.
Sorry for inconvenience.
Click to expand...
Click to collapse
Working wonderful with SuperSU 2.68 I have a doubt do you have a DRM Restore that works with this Android Version?

Hello, sorry for this noob question. If I flash this to my already rooted Z3+ dual, would it delete all my files and stuff here? Thanks

[/COLOR]
creepyvillager said:
Hello, sorry for this noob question. If I flash this to my already rooted Z3+ dual, would it delete all my files and stuff here? Thanks
Click to expand...
Click to collapse
No flashing a kernel doesn't wipe anything, if you're having a dilemma then take a backup of everything like apps, contacts etc using titanium backup, copy the backup folder to your external memory or computer then flash.
Hope it helps.
P. S ONLY INSTALLING A RECOVERY WIPES EVERYTHING.
---------- Post added at 09:41 AM ---------- Previous post was at 09:25 AM ----------
bruno$0 said:
Hello guys.
Today i will post a kernel that i (just run the wizard to) created for Z3+ dual variant version 32.2.A.0.224. My simple contribution!
This kernel contents:
-RIC disable
-TWRP
-root
-dm-verity
How to install it:
Run this command at command prompt,
fastboot flash boot boot.img
Or.....
Use the Flashtools in a fastboot mode, then choose the Flash option by DoomLord.
Please, Don't thanks me. All the hard work was performed by Mr. Tobias Waldvogel in this thread:
http://forum.xda-developers.com/xperia-z5/development/root-automatic-repack-stock-kernel-dm-t3301605
So, if you like this kernel, please pay a coffe for this guy!
Ps. I already tested on my Z3+ and everything it's okay, so i will not responsable about any brinks or damage in use this kernel!
Ps2: DON'T use this kernel on single model. I don't know whats happens!:silly:
Click to expand...
Click to collapse
Can you tell me how long it took for the first boot?
Cause mine is stuck at 'Starting Applications' for about 8 minutes.
Edit : Couldn't wait it took almost 20mins with no progress so shut it down using power + volume up key and went into recovery wiped dalvik/cache and installed supersu 2.66 and again wiped then rebooted. Now it's showing optimising apps. The only problem is it's not charging. Usually at this stage when i connect my charger the charger led starts glowing but now nothing. Any ideas?

njaya95 said:
Can you tell me how long it took for the first boot?
Cause mine is stuck at 'Starting Applications' for about 8 minutes.
Edit : Couldn't wait it took almost 20mins with no progress so shut it down using power + volume up key and went into recovery wiped dalvik/cache and installed supersu 2.66 and again wiped then rebooted. Now it's showing optimising apps. The only problem is it's not charging. Usually at this stage when i connect my charger the charger led starts glowing but now nothing. Any ideas?
Click to expand...
Click to collapse
Yeah, this also happens to my device when I flashed the kernel.
Edit: It just stuck at the boot screen with blinking red LED notification.

creepyvillager said:
Yeah, this also happens to my device when I flashed the kernel.
Edit: It just stuck at the boot screen with blinking red LED notification.
Click to expand...
Click to collapse
I just found out to use this kernel i should have .244 firmware i bet you're at .185 so update it to .244 then try this kernel. I'm just downloading the firmware now using Xperifirm(https://www.google.com/url?sa=t&rct...9Q4Ht-00R24lisYcw&sig2=ac8ImW1ZY7AvFSZpG9I9mA) and i'll post what i did to the phone after the update.

zemetal said:
no need to flash superSU i think, it's already included in the kernel.
Click to expand...
Click to collapse
It's not, need to flash SuperSU I flashed 2.66 Beta

bruno$0 said:
Hello guys.
Today i will post a kernel that i (just run the wizard to) created for Z3+ dual variant version 32.2.A.0.224. My simple contribution!
This kernel contents:
-RIC disable
-TWRP
-root
-dm-verity
How to install it:
Run this command at command prompt,
fastboot flash boot boot.img
Or.....
Use the Flashtools in a fastboot mode, then choose the Flash option by DoomLord.
Please, Don't thanks me. All the hard work was performed by Mr. Tobias Waldvogel in this thread:
http://forum.xda-developers.com/xperia-z5/development/root-automatic-repack-stock-kernel-dm-t3301605
So, if you like this kernel, please pay a coffe for this guy!
Ps. I already tested on my Z3+ and everything it's okay, so i will not responsable about any brinks or damage in use this kernel!
Ps2: DON'T use this kernel on single model. I don't know whats happens!:silly:
Click to expand...
Click to collapse
Hey can you help me, how to make this kernel SELinux status permissive.

njaya95 said:
Hey can you help me, how to make this kernel SELinux status permissive.
Click to expand...
Click to collapse
I don't know. I just run the script to create the image. Sorry. in a near future when Sony release the MM for M4 dual and share the source code i will try to create a custom kernel from benning for my other device.

bruno$0 said:
I don't know. I just run the script to create the image. Sorry. in a near future when Sony release the MM for M4 dual and share the source code i will try to create a custom kernel from benning for my other device.
Click to expand...
Click to collapse
Okay ?

Running Lollipop 5.0.1 and when i flash the kernel i get not orange/yelllow LED. How do i go into recovery?
Also got no super su app.
I meant to flash it with "fastboot flash recovery boot.img" from Android/android-sdk/platform-tools. Correct?

SugnaB said:
Running Lollipop 5.0.1 and when i flash the kernel i get not orange/yelllow LED. How do i go into recovery?
Also got no super su app.
I meant to flash it with "fastboot flash recovery boot.img" from Android/android-sdk/platform-tools. Correct?
Click to expand...
Click to collapse
It's for 6.0.1 so don't flash it for 5.0.1, update the firmware then flash it cause Sony would have updated somethings in the kernel which won't work with old firmwares. The reason for boot working is maybe because of the phone rebooting from fastboot mode.
Hope it helped. [emoji4]
Sent from my E6533 using XDA-Developers mobile app

Did it need a Unlocked Boot-loader device?

sani007 said:
Did it need a Unlocked Boot-loader device?
Click to expand...
Click to collapse
offcourse.

Sorry for the noob question but I need to know the prerequisites,
Can I flash the Kernel right after flashing stock file OR....
Do I need to first unlock my bootloader
Do I need to have backed up my TA partition

hi there, i wanna update form .185 to .224. is it possible to update without wipe the data? and if it can, if i wanna root it, i just flash this kernel after fw upgrade, then flash supersu via twrp, am i right? thanks

If Xperia Z3+ Dual can't be bootloader unlocked, what's the point in this kernel?!

Unofficial TWRP based on v4.88B - WiFi working, Magisk Rootable

*IT IS FOR UNLOCKED BOOTLOADERS ONLY*
Voila ..
Alas TWRP is working on Nokia 8 NB1 based on v4.88B kernel. Wifi and Magisk root both are working on my mobile. Please and report if it is working for you as well.
Download:
https://mega.nz/#!nRgVWKqB!fWx4zO1f19Shs_I8Thkw4ycsZMMMmSYP24cK0MHIBlM
Flash:
adb reboot bootloader
fastboot flash boot_a TWRP_NB1_boot_v2.img
fastboot reboot
Click to expand...
Click to collapse
If working well, also flash boot_a partition as well.
Then following below thread to root it using MagiskManager
https://forum.xda-developers.com/nokia-8/development/pre-rooted-boot-image-nokia-nb1-v4-88b-t3798063
Check Following Post for Update:
https://forum.xda-developers.com/showpost.php?p=77307135&postcount=74
WARNING: Don't change boot slot using TWRP . I am not responsible if you brick your phone.

Many thanks!
Does this mean if you have this IMG, you can flash after any other (even older) IMGs without verify check?
With fastboot and OST LA from here?
That would be a fantastic news!!! :good:

Overall, the fastboot doesn't seem to work on my device. Once I get my phone into bootloader state it says naturally DOWNLOAD MODE but any fastboot devices command ends up with <Waiting for devices>. I've switched drivers from Nokia's one to diffrent non device specific but nothing helps. Any idea on how to fix it ?
- edit -
Came out that the adb and fastboot drivers can't be outdated so be sure to use newest from SDK Platform Tools - otherwise u won't see the device.

head66 said:
Many thanks!
Does this mean if you have this IMG, you can flash after any other (even older) IMGs without verify check?
With fastboot and OST LA from here?
That would be a fantastic news!!! :good:
Click to expand...
Click to collapse
Didn't checked by flashing it. But, logically yes. Though system partition is still encrypted. That may cause an issue. But for custom ROM developers - it can be a start. Provided - your bootloader is unlocked.

KonikoO said:
Overall, the fastboot doesn't seem to work on my device. Once I get my phone into bootloader state it says naturally DOWNLOAD MODE but any fastboot devices command ends up with <Waiting for devices>. I've switched drivers from Nokia's one to diffrent non device specific but nothing helps. Any idea on how to fix it ?
- edit -
Came out that the adb and fastboot drivers can't be outdated so be sure to use newest from SDK Platform Tools - otherwise u won't see the device.
Click to expand...
Click to collapse
Hey,
maybe that can help u.
Fastboot need Admin permissions on windows open a CMD as Admininstator.
On Linux just login into user root.

WORKING
Image is working! Thanks a lot!
Magisk is also working after patch. (With WiFi)

KonikoO said:
Overall, the fastboot doesn't seem to work on my device. Once I get my phone into bootloader state it says naturally DOWNLOAD MODE but any fastboot devices command ends up with <Waiting for devices>. I've switched drivers from Nokia's one to diffrent non device specific but nothing helps. Any idea on how to fix it ?
- edit -
Came out that the adb and fastboot drivers can't be outdated so be sure to use newest from SDK Platform Tools - otherwise u won't see the device.
Click to expand...
Click to collapse
Did you checked if USB debugging is on in the developer settings?
Powered by View 10

KonikoO said:
Overall, the fastboot doesn't seem to work on my device. Once I get my phone into bootloader state it says naturally DOWNLOAD MODE but any fastboot devices command ends up with <Waiting for devices>. I've switched drivers from Nokia's one to diffrent non device specific but nothing helps. Any idea on how to fix it ?
- edit -
Came out that the adb and fastboot drivers can't be outdated so be sure to use newest from SDK Platform Tools - otherwise u won't see the device.
Click to expand...
Click to collapse
I have it problem on Windows 10 too. If you want very strong, download any Linux-based LiveCD, flash it on USB and load. After this install adb and fastboot from LineageOS site (delete space after "https://" https:// wiki.lineageos.org/devices/bacon/build) and run commands.
P.S.: I am sorry for my bad English, but I hope help you

Wow, you are a genius! So glad to see twrp on our Nokia 8 xD but with encrypted /system. Does it mean nandroid backup is not possible at the moment? Also, with your magisk patched kernel, can i flash over or do i need to first flash twrp then reroot with your method?

corpsegrinder62 said:
Wow, you are a genius! So glad to see twrp on our Nokia 8 xD but with encrypted /system. Does it mean nandroid backup is not possible at the moment? Also, with your magisk patched kernel, can i flash over or do i need to first flash twrp then reroot with your method?
Click to expand...
Click to collapse
Flash TWRP img, then re-root using Magisk method provided in the URL.
Created another version of TWRP. Now /data is browsable, but showing garbled file names So, nanodroid is still unachievable. Don't have a backup phone, so could not take the risk of loosing my data, else could have un-encrypt ICE filesystem encryption and could have build a stock based ROM without encrypted partition.

bidhata said:
Flash TWRP img, then re-root using Magisk method provided in the URL.
Created another version of TWRP. Now /data is browsable, but showing garbled file names So, nanodroid is still unachievable. Don't have a backup phone, so could not take the risk of loosing my data, else could have un-encrypt ICE filesystem encryption and could have build a stock based ROM without encrypted partition.
Click to expand...
Click to collapse
Thanks bro. You are making tremindous progress on this phone though. Hopefully you inspire other devs to jump the train on our N8

Does this work with a locked bootloader? And if so do I just follow the steps here? Or do I need OST LA?

thank you so much for your time and effort. Much appreciated. Can the stock recovery be backed up and restored Later? Is it advised to flash it on TA 1012 Nokia 8 unlocked? How can we revert to the original state? Does OEM Unlock help in this case? Is it an image of the whole OS like previous mod attempts?

iKillua said:
Does this work with a locked bootloader? And if so do I just follow the steps here? Or do I need OST LA?
Click to expand...
Click to collapse
You need an unlocked bootloader. Else fastboot not let you overwrite /boot partition. No OST LA required.

trandafirmd said:
thank you so much for your time and effort. Much appreciated. Can the stock recovery be backed up and restored Later? Is it advised to flash it on TA 1012 Nokia 8 unlocked? How can we revert to the original state? Does OEM Unlock help in this case? Is it an image of the whole OS like previous mod attempts?
Click to expand...
Click to collapse
There is no different partition for recovery. So, just flashing the original boot partition ( boot.img ) will be enough to restore. OEM unlocked is required to decrypt the /data partition. This one is just the boot.img modification.

bidhata said:
There is no different partition for recovery. So, just flashing the original boot partition ( boot.img ) will be enough to restore. OEM unlocked is required to decrypt the /data partition. This one is just the boot.img modification.
Click to expand...
Click to collapse
Is this img suitable for restore https://mega.nz/#!yYwUWKwC!5wb2EkDhFKE2QIhI5tW0SE_uqkn2UL2uEPkTM01G5Mg?0 I can't see any 1012 img's How can I backup the boot.img from my phone?
Thank you.

trandafirmd said:
Is this img suitable for restore https://mega.nz/#!yYwUWKwC!5wb2EkDhFKE2QIhI5tW0SE_uqkn2UL2uEPkTM01G5Mg?0 I can't see any 1012 img's How can I backup the boot.img from my phone?
Thank you.
Click to expand...
Click to collapse
It is the same image for TA 1004 / TA-1012 . Taken from v4.88B update.

I realized that after the download finished. I apologize for jumping the gun. Since I'll have to unlock my bootloader, is there a way to do a full system backup through adb or otherwise? Most likely, I have a locked bootloader and before I can figure out a way to unlock it, I will have to backup as much data as possible since unlocking it will most likely wipe all my data and do a factory reset.

You can not make a backup unfortunately.

could you and other people making useless threads put it in the thread title and OP so that 99.9% of nokia 8 owners that dont have a way of unlocking the bootloader dont waste our time by having the salt rubbed in, thanks