Database Develop

Questions about unlocked bootloader and CWM

Hey all,
I have a little complicated story here:
Yesterday I got my Xperia Z, a branded T-Mobile one which was unlockable. First I rooted with the exploit and after that I made a backup of my TA partition for later uses. I had to install TWRP to set the bootloader to unlockable with this file. So by then the bootloader was unlockable again like in the very beginning.
Later I watched this video and did all the steps until the bootloader was unlocked. Then I went back to the root thread with the expliot and rooted it the same way like I did before.
My goal is to successfully flash CyanogenMod 10.1 on my Xperia Z, so I watched this video from the same guy. When he said that I needed CWM I went back to the bootloader unlocking video and did everything after unlocking the bootloader, which was flashing root, insecure fw and the kernel. I accidently used a newer one which didn't work like you can see in this picture:
{
"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"
}
The Xperia Z still works like before and I have CWM 6.0.2.8 installed, but I'm unsure if I could brick it because I accidently used another kernel beforehand. Also, I can't reboot to CWM with an adb command, but it works by pressing vol up when booting. Does that make a difference?
If so, what can I do to get CyanogenMod 10.1 on my device?
Actually I'd be really happy just to know if my bootloader is really unlocked, since I have no real proof.
CWM is also asking if I want to "Disable recovery flash" which would prevent my rom from flashing the stock recovery on boot.
Okay, that's everything for now I think. Would be really nice if someone could help me with this.
Thanks in advance!
FingerMove

FingerMove said:
Hey all,
I have a little complicated story here:
Yesterday I got my Xperia Z, a branded T-Mobile one which was unlockable. First I rooted with the exploit and after that I made a backup of my TA partition for later uses. I had to install TWRP to set the bootloader to unlockable with this file. So by then the bootloader was unlockable again like in the very beginning.
Later I watched this video and did all the steps until the bootloader was unlocked. Then I went back to the root thread with the expliot and rooted it the same way like I did before.
My goal is to successfully flash CyanogenMod 10.1 on my Xperia Z, so I watched this video from the same guy. When he said that I needed CWM I went back to the bootloader unlocking video and did everything after unlocking the bootloader, which was flashing root, insecure fw and the kernel. I accidently used a newer one which didn't work like you can see in this picture:
The Xperia Z still works like before and I have CWM 6.0.2.8 installed, but I'm unsure if I could brick it because I accidently used another kernel beforehand. Also, I can't reboot to CWM with an adb command, but it works by pressing vol up when booting. Does that make a difference?
If so, what can I do to get CyanogenMod 10.1 on my device?
Actually I'd be really happy just to know if my bootloader is really unlocked, since I have no real proof.
CWM is also asking if I want to "Disable recovery flash" which would prevent my rom from flashing the stock recovery on boot.
Okay, that's everything for now I think. Would be really nice if someone could help me with this.
Thanks in advance!
FingerMove
Click to expand...
Click to collapse
Yes your bootloader is unlocked becuase you successfully flashed unsigned kernel, now you need to download CM10.1 and inside it will give you a kernel to flash and rom to install

Maddhouse said:
Yes your bootloader is unlocked becuase you successfully flashed unsigned kernel, now you need to download CM10.1 and inside it will give you a kernel to flash and rom to install
Click to expand...
Click to collapse
Do I just have to flash via CWM or do I have to extract the boot.img out of the .zip, flash it via fastboot and then with CWM again?
(That's how it's presented in the video about flashing custom roms).

QUOTE=FingerMove;41047686]Do I just have to flash via CWM or do I have to extract the boot.img out of the .zip, flash it via fastboot and then with CWM again?
(That's how it's presented in the video about flashing custom roms).[/QUOTE]
you will have to unzip the folder and it should give you two files boot.img and a zip, zip is rom so copy that over to you phone, you can only flash kernel via adb or flashtool so what you need to do is open up cwm and install after install complete then flash CM kernel.
I am still on locked for the XZ but this is what i had to do on X Arc which i am 99.9% sure it is the same way

Maddhouse said:
you will have to unzip the folder and it should give you two files boot.img and a zip, zip is rom so copy that over to you phone, you can only flash kernel via adb or flashtool so what you need to do is open up cwm and install after install complete then flash CM kernel.
I am still on locked for the XZ but this is what i had to do on X Arc which i am 99.9% sure it is the same way
Click to expand...
Click to collapse
This is what's inside a CM10.1 nightly:
In the video about custom roms the order is like this:
1. Extract boot.img out of the .zip
2. Put cm10.1.zip and gapps.zip on sdcard
3. Flash boot.img via adb
4. Restart into cwm
5. Factory reset/wipe cache
6. Install cm10.1.zip and gapps.zip
7. Reboot and it should start CyanogenMod 10.1
Should that also work?
Sorry for so many questions and step-by-step asking, I just don't want to brick it or get bootloops, since that would completely throw me off.
Thanks in advance!
FingerMove

FingerMove said:
This is what's inside a CM10.1 nightly:
In the video about custom roms the order is like this:
1. Extract boot.img out of the .zip
2. Put cm10.1.zip and gapps.zip on sdcard
3. Flash boot.img via adb
4. Restart into cwm
5. Factory reset/wipe cache
6. Install cm10.1.zip and gapps.zip
7. Reboot and it should start CyanogenMod 10.1
Should that also work?
Sorry for so many questions and step-by-step asking, I just don't want to brick it or get bootloops, since that would completely throw me off.
Thanks in advance!
FingerMove
Click to expand...
Click to collapse
1 Download the prebuilt release of CyanogenMod you wish to install. (Or if you've built CM yourself, look in the $OUT directory for the .zip.)
Optional: Download any supplemental 3rd-party applications packages for the device you wish to use. (You have to install a 3rd-party app to get the Google apps, like Gmail, Play Store, and Youtube.)
2 Place the CyanogenMod rom .zip file on the root of the SD card.
Optional: Place any supplemental packages' .zip file on the root of the SD card.
3 Extract the boot.img from the zip, you will need this file for fastboot.
4 Put the phone into fastboot mode:
5 Open a terminal on the PC and enter the following:
fastboot -i 0xfce flash boot boot.img
fastboot -i 0xfce reboot
While the device reboots, press the Volume rockers a few times to load recovery.
6 Once the device boots into the ClockworkMod Recovery, use the physical volume buttons to move up and down. On most devices, the power button is used to confirm your selection, although for some devices the power button is used as a "back" button to go up one level, in which case the home button is used to confirm the selection.
Optional/Recommended: Select backup and restore to create a backup of the current installation on the Xperia Z.
7 Select the option to wipe data/factory reset.
8 Select Install zip from sdcard.
9 Select Choose zip from sdcard.
10 Select the CyanogenMod file you placed on the sdcard. You will then need to then confirm that you do wish to flash this file.
Optional: Install any additional packages you wish using the same method.
11 Once the installation has finished, return back to the main menu, and select the reboot system now option. The Xperia Z should now boot into CyanogenMod.
http://wiki.cyanogenmod.org/w/Install_CM_for_yuga

Thanks for all your help, I just did it
Working really good here, had no bootloops or other problems

CWM Recovery and Root (Stock Kernel Sony 4.2.2)(pollux_windy)

Stock Kernel Packed with CWM
Requirements:
Sony tablet Z Wifi version aka pollux_windy
Unlocked Bootloader
Sony Firmware 4.2.2
a computer with working fastboot
Install Procedure:
connect device to pc
Open CMD/Terminal and cd to the folder you have placed the boot image
type this in CMD/Terminal:
Code:
adb reboot bootloader
Now Flash using:
Code:
fastboot flash boot boot.img
Now Reboot your tablet by:
Code:
fastboot reboot
How to Enter recovery:
The key combination to enter recovery is broken and will be fixed later on. Currently you can reboot to recovery using:
an app like Rom Manager
adb reboot recovery
using terminal emulator (su followed by reboot recovery)
Download Link: (POLLUX_WINDY ONLY)
boot.img
Credits:
Koush- for clockwork mod
DooMLoRD- for his recovery ramdisk
@dinitro - for actually taking the time to compile the cwm with stock kernel, this guy deserves all the credit
Since this is pure stock kernel with a custom recovery i assume i dont have to post the kernel sources, If there is a issue mods are welcomed to notify me via PM.
Rooting Instructions:
Download the latest zip from Here and move to device
Reboot to recovery
Flash
Reboot
​
XDA:DevDB Information
CWM Recovery and Root (Stock Kernel Sony 4.2.2), a Kernel for the Sony Xperia Tablet Z
Contributors
bluefa1con
Kernel Special Features:
Version Information
Status: Testing
Created 2013-09-05
Last Updated 2013-09-06

Woot! Thanks. Gonna try it out tonight.

drazyw said:
Woot! Thanks. Gonna try it out tonight.
Click to expand...
Click to collapse
releasing the kernel first so people can be ready when i release my dual boot for tablet z
more details on my pac thread

Damn, I spent ages getting the root on 4.2.2 sorted out this morning ! Thanks !

Thanx for your work !
I assume it will never work on with locked bootloader ?

ibis69 said:
Thanx for your work !
I assume it will never work on with locked bootloader ?
Click to expand...
Click to collapse
locked bootloader= cant flash a kernel other than stock sony kernel
there is a way to have recovery on locked bootloader but it still needs root
i am too busy these days, if only i had time i would look at xperia z root exploit and implement it on tab z
meanwhile here is what u can do
backup your TA parition
unlock bootloader and root via this method
flash back to stock sony kernel
restore your TA and your device would behave like it was never unlocked

Unlocked my bootloader a few moments ago .. Trying your kernel now.
...
It can access to the internal storage but i don't have any files to flash.
And error appears when trying to mount or install zip from the external storage.
Thank you So much we appreciate your hard work. =)

Half Alive said:
Unlocked my bootloader a few moments ago .. Trying your kernel now.
...
It can access to the internal storage but i don't have any files to flash.
And error appears when trying to mount or install zip from the external storage.
Thank you So much we appreciate your hard work. =)
Click to expand...
Click to collapse
Do u mean it doesn't show any files on internal memory? The files are in the 0 folder
I didn't test the sdcard yet
Here is a surprise coming soon
{
"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"
}
Sent from my SGP311 using Tapatalk 4

bluefa1con said:
Do u mean it doesn't show any files on internal memory? The files are in the 0 folder
I didn't test the sdcard yet
Here is a surprise coming soon
Sent from my SGP311 using Tapatalk 4
Click to expand...
Click to collapse
Just tried now flashing from the internal storage ,.. And it's Working.
Hope you can fix the external_sd problem ,.
And that Big surprise is coming soon like today ?
Can't wait to test it. :good::good:

bluefa1con said:
Do u mean it doesn't show any files on internal memory? The files are in the 0 folder
I didn't test the sdcard yet
Here is a surprise coming soon
Sent from my SGP311 using Tapatalk 4
Click to expand...
Click to collapse
with that great surprise you say,since sony roms can only be primary,what if we have already installed an aosp rom?will we be able to move it to secondary rom partition or we will have to reinstall it from scratch?finally the second rom will be stored at /cache or at /sdcard?sorry if i reveal some of your surprise with these questions

pangiotis24 said:
with that great surprise you say,since sony roms can only be primary,what if we have already installed an aosp rom?will we be able to move it to secondary rom partition or we will have to reinstall it from scratch?finally the second rom will be stored at /cache or at /sdcard?sorry if i reveal some of your surprise with these questions
Click to expand...
Click to collapse
currently the project is in its infancy, we got basic dual boot done and we got more plans
copy your data partition to some other place (sdcard etc) and copy it back when u install pac on second rom
we got big plans for this and we are talking to recovery devs to customize the recovery for RomSwitch dual boot implementation

Dual Boot released HERE

Is this kernel from 311 or 312 version of Tablet Z?

Rootk1t said:
Is this kernel from 311 or 312 version of Tablet Z?
Click to expand...
Click to collapse
Should work on both, I have tested on 311 because that's the device I have but both are identical besides more storage capacity
Sent from my SGP311 using Tapatalk 4

bluefa1con said:
releasing the kernel first so people can be ready when i release my dual boot for tablet z
more details on my pac thread
Click to expand...
Click to collapse
Well it seems to work perfect. Followed all the steps and it worked flawlessly. After a few days of struggling to maintain root when updating to 4.2.2 with Sony's OTA, this took 5 min. Thanks for all the work. Can't wait to try out some dual boot stuff now.

I tried this procedure on my SGP321 LTE Tablet. After flashing the boot.img, my tablet refuses to boot up. There is just a Red LED. No Sony logo or nothing. I somehow managed to get it into Fastboot mode (Blue LED) but apart from that I cannot do anything. On trying Vol - and plugging the USB at the same time, the FlashTool recognizes the Flash Mode (but there is no Green LED) I even tried flashing the FTF through the FlashTool but it gets stuck on flashing data. I really am struggling since 5 hours. Is my Tablet dead? I really cannot figure out what to do next Please help me!!

aashayjardosh said:
I tried this procedure on my SGP321 LTE Tablet. After flashing the boot.img, my tablet refuses to boot up. There is just a Red LED. No Sony logo or nothing. I somehow managed to get it into Fastboot mode (Blue LED) but apart from that I cannot do anything. On trying Vol - and plugging the USB at the same time, the FlashTool recognizes the Flash Mode (but there is no Green LED) I even tried flashing the FTF through the FlashTool but it gets stuck on flashing data. I really am struggling since 5 hours. Is my Tablet dead? I really cannot figure out what to do next Please help me!!
Click to expand...
Click to collapse
Do not worry, you just flashed the wrong kernel for your device, happens to everyone. Just simply try to flash your FTF, or you could install Cyanogenmod.

mamenyaka said:
Do not worry, you just flashed the wrong kernel for your device, happens to everyone. Just simply try to flash your FTF, or you could install Cyanogenmod.
Click to expand...
Click to collapse
I tried flashing the 4.2.2 FTF but it gets stuck on loading data. I tried flashing the boot.img from CM10.2 but that too gets stuck on 'Flashing Selected Kernel'..

aashayjardosh said:
I tried flashing the 4.2.2 FTF but it gets stuck on loading data. I tried flashing the boot.img from CM10.2 but that too gets stuck on 'Flashing Selected Kernel'..
Click to expand...
Click to collapse
You need to flash the boot.img with fastboot.

mamenyaka said:
You need to flash the boot.img with fastboot.
Click to expand...
Click to collapse
Forgive my noobness...but where do I get the original 4.2.2 boot.img from? I extracted the 4.2.2 FTF but there is no boot.img in it. On the other hand I extracted the boot.img of CM10.2 but that gets stuck on Flashing selected kernel.

How to root xperia z3+?!

Hi,
Please can anyone tell me if my device is rootable. I have an xperia z3+ version 5.0.2, build number 28.0.A.8.266, if it is possible can anyone tell in quick steps.
Thanks

Flash SuperSU via TWRP.

The safest way to do it, is by unlocking your bootloader and flashing a SuperSU-installer through either a permanent or a temporary TWRP Recovery. If your device won't boot after the flashing process, download a "rootable" kernel from here and flash that too through TWRP. Hope it helps

2minuutes said:
The safest way to do it, is by unlocking your bootloader and flashing a SuperSU-installer through either a permanent or a temporary TWRP Recovery. If your device won't boot after the flashing process, download a "rootable" kernel from here and flash that too through TWRP. Hope it helps
Click to expand...
Click to collapse
first i need to bkp TA, but i need to root and then install TWRP
any other way to root witouht recovery ?

Root
(rooted kernel attached in post)
Managed to successfully root my Z3+ Dual.
How I dit it:
1. Downgraded to LP in order to back up my TA (required by the tool = E6533 (28.0.A.8.266)). Enabled developer and USB debugging.
Used this guide to back up TA, resulting TA-17042016_Z3+Dual.img.
2. Unlocked bootloader using flashtool (I obtained prior the unlock code from Sony http://developer.sonymobile.com/unlockbootloader/)
3. Read thoroughly this thread and downloaded all necessary apps (SuperSU, fastboot adb, latest MM .ftf (32.1.A.1.185) - Customized HK in my case).
Attention! In addition to what you will find in that thread, you need fastboot.
4. Flashed MM 32.1.A.1.185. Enabled developer and USB debugging.
5. Extracted the kernel (kernel.elf) in order to root it. Prepared the rooted kernel (new_kernel.img) with the provided tool. Put phone in flashboot mode (power off. keep volume up and insert usb). Checked the kernel and flashed it. Uploaded the saved TA keys (TA-17042016_Z3+Dual.img). Attention! Copy the extracted kernel, TA keys and fastboot in the same directory.
Commands used (Shift+Right click on the containing directory):
Code:
rootkernel kernel.elf new_kernel.img TA-17042016_Z3+Dual.img
- Unpacking kernel
Found elf boot image
Found appended DTB
- Unpacking initramfs
- 64-bit platfrom detected
- Disabling dm-verity
- Disabling SONY RIC
- Installing TWRP
- Found SuperSU-v2.65-20151226141550.zip
Adding service entry for SuperSU
- Configuring secd
- Configuring wvkbd
- Configuring drmserver
- Creating new initramfs
- Creating boot image
- Cleaning up
Done
fastboot boot new_kernel.img
downloading 'boot.img'...
OKAY [ 2.187s]
booting...
OKAY [ 0.562s]
finished. total time: 2.749s
fastboot flash boot new_kernel.img
sending 'boot' (24760 KB)...
OKAY [ 2.180s]
writing 'boot'...
OKAY [ 0.200s]
finished. total time: 2.380s
flash_dk TA-17042016_Z3+Dual.img DK.ftf
- Extracting device key
- Creating FTF file for device E6533
- Cleaning up
Done
6. Booted the phone and...voila!
{
"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"
}
None of this would've been possible without the hard work of tobias.waldvogel and zxz0O0.
Hope it helps!

I followed nica_ro's steps exactly as he did it. I have a Z3+ (E6553).
However, my phone shows that it's not rooted. I have access to TWRP recovery though.
It seems as if SuperSU was not installed although I also had the version 2.65 zip file (like in the guide) in the rootkernel tool directory.
Also, I tried to manually flash SuperSU through TWRP without any noticeable change.
What could have gone wrong?
Edit: Solved it! I was using Version 4.23 of rootkernel, which didn't properly integrate SuperSU. After using 4.24 I'm now fully enjoying my rooted Z3+!
Thanks nica_ro!

Chrizes said:
I followed nica_ro's steps exactly as he did it. I have a Z3+ (E6553).
However, my phone shows that it's not rooted. I have access to TWRP recovery though.
It seems as if SuperSU was not installed although I also had the version 2.65 zip file (like in the guide) in the rootkernel tool directory.
Also, I tried to manually flash SuperSU through TWRP without any noticeable change.
What could have gone wrong?
Edit: Solved it! I was using Version 4.23 of rootkernel, which didn't properly integrate SuperSU. After using 4.24 I'm now fully enjoying my rooted Z3+!
Thanks nica_ro!
Click to expand...
Click to collapse
Glad you solved it!

Guys,
I use to mod my phone since sony ericsson time. I always root my android devices just to get rid of bloat,adblock,greenify and few customization. Never unlocked my bootloader in any case. Now I am really worried about my new Z3+ Dual.. I desperately need Root accesses.. But worried about bricking my device.. I am on MM .185, Is it possible to backup TA with this FW?.. Is all the steps required to root is safe and easy? Is TA backup mandatory?

dil2abu said:
Guys,
I use to mod my phone since sony ericsson time. I always root my android devices just to get rid of bloat,adblock,greenify and few customization. Never unlocked my bootloader in any case. Now I am really worried about my new Z3+ Dual.. I desperately need Root accesses.. But worried about bricking my device.. I am on MM .185, Is it possible to backup TA with this FW?.. Is all the steps required to root is safe and easy? Is TA backup mandatory?
Click to expand...
Click to collapse
For someone who's rooting devices for a long time, you should know better.
For the moment, there is no rooting without unlocking the bootloader. The locked bootloader only boots unmodified kernel packages signed by Sony. The stock kernel only mounts unmodified /system partitions (dm-veritiy) -> No modification without unlocking.
You CAN NOT backup TA with .185, you have to DOWNGRADE to LP.266. -> E6533 (28.0.A.8.266)
TA backup is not mandatory, but recommended, especially if you want stuff like X-reality and camera de-noise.
And finally, there are no guarantees that the steps required to root are safe and easy.

nica_ro said:
For someone who's rooting devices for a long time, you should know better.
For the moment, there is no rooting without unlocking the bootloader. The locked bootloader only boots unmodified kernel packages signed by Sony. The stock kernel only mounts unmodified /system partitions (dm-veritiy) -> No modification without unlocking.
You CAN NOT backup TA with .185, you have to DOWNGRADE to LP.266. -> E6533 (28.0.A.8.266)
TA backup is not mandatory, but recommended, especially if you want stuff like X-reality and camera de-noise.
And finally, there are no guarantees that the steps required to root are safe and easy.
Click to expand...
Click to collapse
Thanks for your reply. I read somewhere in this forum that TA backup is not required, we can activate X-reality and others with a drmrestore mod?

nica_ro said:
Managed to successfully root my Z3+ Dual.
How I dit it:
1. Downgraded to LP in order to back up my TA (required by the tool = E6533 (28.0.A.8.266)). Enabled developer and USB debugging.
Used this guide to back up TA.
2. Unlocked bootloader using flashtool (I obtained prior the unlock code from Sony http://developer.sonymobile.com/unlockbootloader/)
3. Read thoroughly this thread and downloaded all necessary apps (SuperSU, fastboot adb, latest MM .ftf (32.1.A.1.185)).
Attention! In addition to what you will find in that thread, you need fastboot .
4. Flashed MM 32.1.A.1.185. Enabled developer and USB debugging.
5. Extracted the kernel in order to root it. Prepared the rooted kernel with the provided tool, checked it and flashed it. Uploaded the saved TA keys. Attention! Copy the extracted kernel, TA keys and fastboot in the same directory.
Commands used (Shift+Right click on the containing directory):
Code:
rootkernel kernel.elf new_kernel.img TA.img
- Unpacking kernel
Found elf boot image
Found appended DTB
- Unpacking initramfs
- 64-bit platfrom detected
- Disabling dm-verity
- Disabling SONY RIC
- Installing TWRP
- Found SuperSU-v2.65-20151226141550.zip
Adding service entry for SuperSU
- Configuring secd
- Configuring wvkbd
- Configuring drmserver
- Creating new initramfs
- Creating boot image
- Cleaning up
Done
fastboot boot kernel_x.img
downloading 'boot.img'...
OKAY [ 2.187s]
booting...
OKAY [ 0.562s]
finished. total time: 2.749s
fastboot flash boot kernel_x.img
sending 'boot' (24760 KB)...
OKAY [ 2.180s]
writing 'boot'...
OKAY [ 0.200s]
finished. total time: 2.380s
flash_dk TA.img DK.ftf
- Extracting device key
- Creating FTF file for device E6533
- Cleaning up
Done
6. Booted the phone and...voila!
View attachment 3721907
None of this would've been possible without the hard work of tobias.waldvogel and zxz0O0.
Hope it helps!
Click to expand...
Click to collapse
i've done everything, and after 2nd restart, i cant see any yellow light to boot to recovery/twrp. i've the bootloader, its (maybe) locked again after flash_dk. the first restart after cmd section, i can see the yellow light, but the restart after that i cant. what am i need to do to boot to recovery/twrp? i need to flash some .zip

I literally can't understand what you described. Sorry. What yellow light are you talking about?

nica_ro said:
I literally can't understand what you described. Sorry. What yellow light are you talking about?
Click to expand...
Click to collapse
a yellow light to boot to recovery. i cant see it.

It did not work for me either (no yellow/orange light while booting).
I had to flash the rootable kernel from here:
http://forum.xda-developers.com/xperia-z4/development/rootable-kernel-sxz3-ivy-marshsmellow-t3336607
followed by the recovery from here:
http://forum.xda-developers.com/xperia-z4/development/twrp-xperia-z3-fota-recovery-t3346298

1. Making new kernel called new_kernel.img then flashing kernel_x.img???
2. rootkernel tools is for Z5, script said no twrp for ivy
Update:
1. Change script from kernel_x.img to new_kernel.img flash OK
2. New rootkernel 4.4 twrp OK but not rooted
Update again:
2. Seems to partial rooted on rootkernel 4.31. Partially means sometimes root sometimes not after reboot. Just copy ivy twrp folder from 4.4.
Update 3:
1. Change rootkernel kernel.elf new_kernel.elf
2. Rooted with beta su 2.71.
3. I think it should be 6th step flash DK.ftf created in flash_dk TA.img DK.ftf with flashtool.
4. Xposed with xposed-v84-sdk23-arm64.
Many thanks to nica_ro for paving up the way.

sarjarim said:
1. Making new kernel called new_kernel.img then flashing kernel_x.img???
2. rootkernel tools is for Z5, script said no twrp for ivy
Update:
1. Change script from kernel_x.img to new_kernel.img flash OK
2. New rootkernel 4.4 twrp OK but not rooted
Update again:
2. Seems to partial rooted on rootkernel 4.31. Partially means sometimes root sometimes not after reboot. Just copy ivy twrp folder from 4.4.
Update 3:
1. Change rootkernel kernel.elf new_kernel.elf
2. Rooted with beta su 2.71.
3. I think it should be 6th step flash DK.ftf created in flash_dk TA.img DK.ftf with flashtool.
4. Xposed with xposed-v84-sdk23-arm64.
Many thanks to nica_ro for paving up the way.
Click to expand...
Click to collapse
Changed guide based on minor misunderstandings. rootkernel is now v 4.50, with fixed adb and mtp file access in TWRP for 32.2.A.0.224. All one needs now is to wait for 32.2.A.0.224 (32.2.A.0.224 Algerika DZ and Customized Malayesia are already available for download).

Didnt understand
nica_ro said:
I literally can't understand what you described. Sorry. What yellow light are you talking about?
Click to expand...
Click to collapse
You said you need fastboot? how to achieve that,, when i click fastboot text in your post it takes me to ftf.266 google drive page ??
Will you please explain a little bit more too me ??

arokososoo said:
You said you need fastboot? how to achieve that,, when i click fastboot text in your post it takes me to ftf.266 google drive page ??
Will you please explain a little bit more too me ??
Click to expand...
Click to collapse
Updated the links. Also added the rooted kernel I made. Fastboot command was missing from the adb folder, so I added it.
UPDATE: Managed to root using the same method the lastest 32.2.A.0.224.

Might there be a difference with z3 plus one sim edition?
Do you think there's any difference or a chance that it might not work if done this way with the z3+ E6553?
I'm thinkin' on rooting my device but i wanna be sure before doing anything to it... specially i don't want to lose the DRM keys ...
thanks,

Stumped for upgrading ROM
Either my eyes and brain are getting tired from days of reading, or I'm getting old, or I only root every couple of years (ever since the W810i), so I may be out of practice, but I'm embarrassingly stumped. I understand everything from post#5 but I'm stuck at choosing the proper ROM for flashing and extracting the kernel.
Z3+ Dual (E6533)
The phone came with 28.0.A.8.251, did OTA update to 28.0.A.8.266 to do the TA backup (worked). I've included two screenshots of the before and after [.251 --> .266]:
Now I need to pick the proper updated ROM before I proceed. OTA wants to install 32.1.A.1.163, Xperia Companion is showing 32.2.A.0.253 as well as XperiFirm. The closest match on XperiFirm, I think, is cda 1295-0980? Ukraine? Also, on the box it shows a cda of 1293-8962, Russia?. In the past when I have rooted there has always been a North America Generic so it was an easy pick. On XperiFirm there are numerous Generics other than North America. I'm in North America (Canada), English. What's your advice on the proper ROM to use for my rooting adventures?
Thanks.

[ROM]ASUS-ZenWatch-3-WI503Q- Swift [6 DEC-2017][STOCK-NWD1.170623.001]

{
"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"
}
Enjoy Your Asus Zenwatch 3-Swift-AND-FEEL THE SPEED
Please read the instructions and notes before flashing anything.
Code:
###Disclaimer###
I am not responsible if your phone will be damaged, broken, boot looping. YOU are choosing to make these modification.
WARNING:
IMPROPER FLASHING MAY POTENTIALLY BRICK YOUR DEVICE. SO PLEASE PROCEED AT YOUR OWN RISK. ME OR ANY OTHER DEVELOPER MENTIONED IN THIS POST WILL ASSUME NO RESPONSIBILITY FOR THIS.
IF YOU LIKE MY WORK AND WANT ME TO CONTINUE, THEN BUY ME A SHOT OF WHISKY
---------------------------------------------------------------------------------
---------------------------------------------------------------------------------
DONATE ME HERE
---------------------------------------------------------------------------------
---------------------------------------------------------------------------------
​Requirements
- An unlocked bootloader
- adb and fastboot drivers
- TWRP recovery
You can download adb and fastboot package from here. https://developer.android.com/studio/releases/platform-tools.html#download
--------------------
HOW TO FLASH THE ROM
0- Attach your devices to your PC and enable USB Debugging
1- Boot your device with TWRP from
Custom-TWRP-thanks to @Maxr1998
- adb devices
- adb reboot bootloader
- fastboot devices
- fastboot boot name-of-the-twrp.img
Or
fastboot flash recovery name-of-the-twrp.img
2- Now move the build/ROM to your watch
3- Make a backup - there's always 1% chance something goes wrong.
4- Full wipe is recommended....Wipe data/Factory reset
5- Flash the ROM
6- Reboot
7- Setup your initial settings
8- GO TO MY KERNEL THREAD AND DOWNLOAD THE LATEST VERSION AND FLASH THAT.
9- Done
--------------------
HOW TO ACHIEVE ROOT
- Reboot into TWRP
- Copy the root-wear.zip (ROOT AND BUSYBOX_1.5_AND_2.0) package inside your device
- Flash the root-wear. zip and reboot
- Open busybox and install
- Done
--------------------
HOW TO ACHIEVE ROOT AFTER FLASHING THE NEW BOOT IMAGES
- DOWNLOAD THE LATEST VERSION FROM (KERNEL THREAD)
- Reboot into TWRP
- Flash the new kernel and reboot
- Complete your device setup
- Reboot into TWRP again
- Flash root-wear.zip (ROOT AND BUSYBOX_1.5_AND_2.0) package
- Reboot
- Open busybox and install
- Done
PLEASE LOOK MY KERNEL/BOOT IMAGES THREAD FOR LATEST KERNEL
PLEASE LOOK MY KERNEL/BOOT IMAGES THREAD FOR LATEST KERNEL
PLEASE LOOK MY KERNEL/BOOT IMAGES THREAD FOR LATEST KERNEL
KERNEL/BOOT IAMGES FOR LATEST UPDATE
-NOTE: YOU NEED TO FLASH THE ROM FIRST (Setup your initial settings) AND THEN FLASH THE LATEST KERNEL FROM KERNEL THREAD
ROMs-ANDROID_WEAR_2.0 [DEODEXED][ODEXED] [LATEST]
Short changelog-[DEODEXED] [27/8/2018]
- Based on latest release NWD1.170623.001- June_1_2017 security patch
- Kernel is compiled with LINARO GCC: 4.9.4-Optimized/based on latest available source 3.18.24 Kernel
- All *apk system/data, system/app, Framework & priv-app zipalign & optimized for better RAM utilization
- Can be root - Flash the following Root/BusyBox if you want to achieve root access.
- dm-verity disabled
- forced-encryption disabled
- SELinux permissive
- init.d script support
- Tweaked for Best Performance
- adb is enabled by default
- Update script
- Tweaks to achieve better battery life
- Clean
------------------------------------------------------------
Download-Link [LATEST-27/8/2018]
BUILD_WEAR_2.0 [DEODEXED] /ROM
MD5:0ceb5c2c3261cb0026b1365940efc839
------------------------------------------------------------
BUILD_WEAR_2.0 [ODEXED] /ROM
MD5:131ab240ec04f8a5ecbf7acb6d42ad51
------------------------------------------------------------
Download-Link
ROOT AND BUSYBOX_1.5_AND_2.0
------------------------------------------------------------
------------------------------------------------------------
ROMs-MWG68_ANDROID_WEAR_1.5
Download-Link
Deodexed/ROM
MD5:3913568ed1d59d90340962b24a3a46b7
Odexed/ROM
MD5:ee3dbf24fcc19a713ddcf819e24c43bb
----------------------
Kernel Source
https://github.com/toffyjan/Asus-zenwatch-3-kernel
----------------------
IF YOU LIKE MY WORK AND WANT ME TO CONTINUE, THEN BUY ME A SHOT OF COFFEE
---------------------------------------------------------------------------------
---------------------------------------------------------------------------------
DONATE ME HERE
---------------------------------------------------------------------------------
---------------------------------------------------------------------------------
DONATE-HERE​https://www.paypal.me/JANJANXDA
paypal.me/JANJANXDA
----------------------
Special thanks to:
If you can, donate and respect all the devs and enjoy
@Chainfire for great work in android
@Maxr1998 thanks for script and twrp recovery
@superR for the kitchen
@Captain_Throwback
@SuperThomasLab for great tools
-Take a look here. And support the dev.
@Xmaster24 for system-less root-
Willi Ye for his great app
-Take a look here. And buy the donate version to support the dev.
Please always support devs and others (soon).

Thanks! What's the decryption key? Apparently I need that to download.

ups gonna fix it soon.
go gO

You meant to flash this with TWRP, right? I did that and did a wiped it (factory reset in TWRP). Seems to hang at the ASUS IN SEARCH OF INCREDIBLE loading screen. Could just be my watch of course.

jobarr said:
You meant to flash this with TWRP, right? I did that and did a wiped it (factory reset in TWRP). Seems to hang at the ASUS IN SEARCH OF INCREDIBLE loading screen. Could just be my watch of course.
Click to expand...
Click to collapse
Offcourse flashing with TWRP..You need to wipe your data too. And fast boot takes some time. 5-10 minutes. I tested on two watches and it works. Be patient
I removed boot animation so that is why see only Google with capital letters. It make the boot process a bit faster.

@janjan Nice one!
Will try it out asap. Just a small tip, could you rebase your kernel onto the swift branch of the kernel-msm repo on android.googlesource.com? That way, the commit history isn't lost and we can see all the changes you made (and improve on them as well). Precondition of course is that the repo already contains the latest MWF76 sources, I didn't check that yet. But if yes, you could just clone it, and drop the .git folder into your kernel folder, verify all is fine and commit the changes.
janjan said:
I removed boot animation so that is why see only Google with capital letters. It make the boot process a bit faster.
Click to expand...
Click to collapse
You mean splash, don't you? Did you just wipe it with zeroes or how did you do it?

After 10 minutes I still only see "ASUS IN SEARCH OF INCREDIBLE". It never even shows "Google".

jobarr said:
After 10 minutes I still only see "ASUS IN SEARCH OF INCREDIBLE". It never even shows "Google".
Click to expand...
Click to collapse
Tell me what you did. You procedure please.

Booted TWRP via "fastboot boot recovery.img"
Flashed your zip
Wiped Dalvik/cache/data
Rebooted

jobarr said:
Booted TWRP via "fastboot boot recovery.img"
Flashed your zip
Wiped Dalvik/cache/data
Rebooted
Click to expand...
Click to collapse
And you are bootloader unlocked right?
You have to wipe first and then flash the zip.

Maxr1998 said:
@janjan Nice one!
Will try it out asap. Just a small tip, could you rebase your kernel onto the swift branch of the kernel-msm repo on android.googlesource.com? That way, the commit history isn't lost and we can see all the changes you made (and improve on them as well). Precondition of course is that the repo already contains the latest MWF76 sources, I didn't check that yet. But if yes, you could just clone it, and drop the .git folder into your kernel folder, verify all is fine and commit the changes.
You mean splash, don't you? Did you just wipe it with zeroes or how did you do it?
Click to expand...
Click to collapse
I will check it out. need to prepare my self for my exam ..I try to

janjan said:
And you are bootloader unlocked right?
You have to wipe first and then flash the zip.
Click to expand...
Click to collapse
Yes. Ahhh....ok, lemme try that.

janjan said:
I will check it out. need to prepare my self for my exam ..I try to
Click to expand...
Click to collapse
Sure, school's always first. Good luck in your exam!

Maxr1998 said:
Sure, school's always first. Good luck in your exam!
Click to expand...
Click to collapse
Thank you. I didn't add too much right now. But we will do that. My last exam in wireless communication.

janjan said:
And you are bootloader unlocked right?
You have to wipe first and then flash the zip.
Click to expand...
Click to collapse
It still won't leave the ASUS screen after 5 minutes. :/

jobarr said:
It still won't leave the ASUS screen after 5 minutes. :/
Click to expand...
Click to collapse
Try to flash the kernel after flash the build. Or
Flash the root after flashing the build or
Wipe everything also your system and then flash the ROM. You have to wipe everything.
I just test again and it seems working without and issue

I wasn't bothering with rooting at the moment. Just trying to get my charging problem fixed.
You mean flash boot.img again manually (with fastboot) after flashing the zip? I tried that. No change. Tried wiping system before flashing everything, no change. I'm wondering if something really is wrong with my watch. I think I'll just load the stock stuff back on it and send it back to Amazon and get a new one I think.

jobarr said:
I wasn't bothering with rooting at the moment. Just trying to get my charging problem fixed.
You mean flash boot.img again manually (with fastboot) after flashing the zip? I tried that. No change. Tried wiping system before flashing everything, no change. I'm wondering if something really is wrong with my watch. I think I'll just load the stock stuff back on it and send it back to Amazon and get a new one I think.
Click to expand...
Click to collapse
Sounds like the best idea to me actually.. @janjan, didn't you also flash my extracted boot image with fastboot before?

jobarr said:
I wasn't bothering with rooting at the moment. Just trying to get my charging problem fixed.
You mean flash boot.img again manually (with fastboot) after flashing the zip? I tried that. No change. Tried wiping system before flashing everything, no change. I'm wondering if something really is wrong with my watch. I think I'll just load the stock stuff back on it and send it back to Amazon and get a new one I think.
Click to expand...
Click to collapse
jobarr said:
Thanks! What's the decryption key? Apparently I need that to download.
Click to expand...
Click to collapse
Maxr1998 said:
Sounds like the best idea to me actually.. @janjan, didn't you also flash my extracted boot image with fastboot before?
Click to expand...
Click to collapse
Yes I did. But actually It could be a good idea for @jobarr to try it out. I will suggest him to flash your extracted boot image and your system.img and then flash my kernel or my build.
It seems any modification or even by booting into twrp and allow modification causes boot loop and rebooting every 30 seconds. It is due to dm-verity stock kernel feature which provides integrity checking of block devices Or STATE CHECKING. I had the same issue with boot loop and then fixed the issue by flashing my build + kernel.

janjan said:
Yes I did. But actually It could be a good idea for @jobarr to try it out. I will suggest him to flash your extracted boot image and your system.img and then flash my kernel or my build.
It seems any modification or even by booting into twrp and allow modification causes boot loop and rebooting every 30 seconds. It is due to dm-verity stock kernel feature which provides integrity checking of block devices Or STATE CHECKING. I had the same issue with boot loop and then fixed the issue by flashing my build + kernel.
Click to expand...
Click to collapse
Yeah, dm-verity is a pain.. Shouldn't SuperSu also patch dm-verity? Might be worth a try as well.

[RECOVERY] TWRP 3.1.1-0 for Z5C [suzuran]

{
"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"
}
Download : Google Drive
How to flash?
1. Shutdown your Z5C
2. Connect to PC in Fastboot mode
3. Flash with this command
Code:
fastboot.exe flash recovery twrp_recovery.img
Do NOT forget to hit Thanks button :fingers-crossed:
Credits : bbs.gfan.com
Contributor : @grayleshy

Seriously, someone took my recovery and changed the theme and all?

grayleshy said:
Seriously, someone took my recovery and changed the theme and all?
Click to expand...
Click to collapse
I don't know it is yours or not? How can you be sure?
Did you left any #comment# for this? If you did I will add you as a contributor.

delete

grayleshy said:
ro.build.host=grayleshy-virtualbox
Click to expand...
Click to collapse
I see, thanks. I edit the post.

grayleshy said:
delete
Click to expand...
Click to collapse
sorry I did not go through your consent then modify the TWRP, sorry again.
your work are very nice!
thanks again.

@sceryavuz What sources did you use to compile? I tried Dirty Unicorn's and Omnirom's but I had lot of errors with both.

DJHasis said:
@sceryavuz What sources did you use to compile? I tried Dirty Unicorn's and Omnirom's but I had lot of errors with both.
Click to expand...
Click to collapse
Here : https://forum.xda-developers.com/crossdevice-dev/sony/twrp-3-1-0-z5-z5c-z5p-t3571050

this work on 7.1.1?

sceryavuz said:
GreyLeshy said:
Seriously, someone took my recovery and changed the theme and all?
Click to expand...
Click to collapse
I don't know it is yours or not? How can you be sure?
Did you left any #comment# for this? If you did I will add you as a contributor.
Click to expand...
Click to collapse
isn't there a rule about not doing this?

it's flashing well but it doesn't work on 7.1.1.
I'm new to the Z5C and currently not sure about choosing the best approach for installing TWRP.

Ilko said:
it's flashing well but it doesn't work on 7.1.1.
I'm new to the Z5C and currently not sure about choosing the best approach for installing TWRP.
Click to expand...
Click to collapse
What do you mean "it doesn't work"? How did you install TWRP?

I meant what I said, after flashing, rebooting into recovery has no effect, it boots normally. I know that I'm doing it wrong for now but looking for the right method.
BTW, just found that for being as up-to-date as possible the only way seems to flash a .33 firmware first. I already miss my ZR, everything was easier...

When I give twrp permission to modified system partition my phone fail to boot to system is there any fix for that?
I am using Xperia z5 compact E5803
Android version: 7.1.1
Build number: 32.4.A.0.160
Kernel: 3.10.48-perf-g5e25a09 (stock)

Mostafa8296 said:
When I give twrp permission to modified system partition my phone fail to boot to system is there any fix for that?
I am using Xperia z5 compact E5803
Android version: 7.1.1
Build number: 32.4.A.0.160
Kernel: 3.10.48-perf-g5e25a09 (stock)
Click to expand...
Click to collapse
I don't know what's the problem but when I flashed Greenkernel every thing works fine.It maybe the stock Kernel was the problem

Lost TWRP
I lost twrp tried to flash in fastboot mode but having errors..
I connect pc via fastboot
opening command screen
fastboot flash recovery recovery.img and getting this error
-target reported max download size of 536870912
sending recovery (19800 KB )
OKAY ( 0,757s )
writing recovery ...
failed ( remote: image is not a boot image, nor ELF )
finished. total time : 0,777s
It s first time i am having this problem.. I can flash a kernel bot cant flash a recovery.
Also not working this command too fastboot boot recovery recovery.img
I dont think i have a driver problem ( i checked many times )

Ilko said:
I meant what I said, after flashing, rebooting into recovery has no effect, it boots normally. I know that I'm doing it wrong for now but looking for the right method.
BTW, just found that for being as up-to-date as possible the only way seems to flash a .33 firmware first. I already miss my ZR, everything was easier...
Click to expand...
Click to collapse
I have the same problem you had. The device simpy wont boot into recovery. Did you manage to get it working with a .33 firmware? did you use Stock kernel?

maxi*king said:
I have the same problem you had. The device simpy wont boot into recovery. Did you manage to get it working with a .33 firmware? did you use Stock kernel?
Click to expand...
Click to collapse
Yes, in fact, it was a problem that I wasn't expecting. I was trying to boot into recovery via reboot menu or app, but it's not actually working. Simply try VolDown+power while the device is off. You can release when it vibrates.
Sent from my Funky Z5C

Ilko said:
Yes, in fact, it was a problem that I wasn't expecting. I was trying to boot into recovery via reboot menu or app, but it's not actually working. Simply try VolDown+power while the device is off. You can release when it vibrates.
Click to expand...
Click to collapse
Thank you so much! :good:
Now it works
I can't believe that I flashed my phone multiple times because I didn't manage to start into recovery :cyclops:

Can´t get twrp to work on z5c
Hi guys!
I just bought a new Z5C and already saved TA, unlocked bootloader and flashed twrp (twice - 3.0.2 with rootkernel, this 3.1.1 with fastboot). All on Android 5.1.1 (32.0.A.6.200) stock rom. Now the phone is working and rooted with SuperSU.
Problem:
I can only start the old 3.0.2 twrp inside the kernel with pressing volume up when led is yellow but I can´t start 3.1.1 with power + volume down. I don´t get a purple led and most of times it just starts Android. Sometimes it gets stuck on Sony bootscreen (guess this happens when I did correct button combination but twrp fails to start?).
Any idea where the problem is?
fastboot flash recovery twrp_recovery.img results in:
sending 'recovery' (19800 KB)...
OKAY [ 0.459s]
writing 'recovery'...
OKAY [ 0.170s]
finished. total time: 0.636s
Click to expand...
Click to collapse
So everything should be ok, right?
Kernel can not be the problem as I understand as kernel has nothing to do with recovery, right?