Develop Bugs

[Guide] 2012 WFS CWM/Root

Intro: People with 2012 WFS reported to have no CWM visuals (i also do)
*NOTE: Even if you DID install this CM based rom wont work only stock based one*
CWM:
1. Unlock bootloader via HTCdev.com (look for guides there are plenty here)
2.Download http://www.mediafire.com/?pqtgftm40909r31 *updated*
3.Extract to C:/
4.Go to fastboot
4.Open Command prompt
5.type cd c:/WFS
6.type fastboot flash recovery recovery.img
7.wait for flashing to finish
8.Remove battery
9.Go to bootloader
10. click recovery wait for visuals
ROOTING:
*same as other methods*but..
1.move the cursor up then down until you see ( back button enabled)
2.Backup
3.Flash root.zip
Credits to fellow member pashaa for sharing recovery file
*NOTE* Dont blame me if anything happens to your device. I've Warned yah!
If you cant understand or want help post here and i'll try to help you out
ScreenShot of my recovery below

i dont get any visuals of black screen..just htc logo...and would you mind telling which cwm recovery version is this?? and will it work ony on this particular recovery?

vshl2995 said:
i dont get any visuals of black screen..just htc logo...and would you mind telling which cwm recovery version is this?? and will it work ony on this particular recovery?
Click to expand...
Click to collapse
modded 5.0.2.8
Sent from my Nexus 7 using xda premium

are youu sure you downloaded the recovery file correctly because it works for m
e??? all other recovery doesn't work except for that one
Sent from my Nexus 7 using xda premium

ngoralph said:
are youu sure you downloaded the recovery file correctly because it works for m
e??? all other recovery doesn't work except for that one
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
no i havent done this right now..i was asking because i tried to do the same procedure with official recovery some days ago..actually its my girlfriend's phone not mine and she is eating my head off because of low memory!!! anyway thanxx..ill try this asap and report back..!!

Link updated
Sorry for inconvenience
http://www.mediafire.com/?pqtgftm40909r31

WORKS
Works gr8...great job :good::good:

Confirmed, works here too. THX!

Thanks man,great job!.Finally I have visual recovery!Flashing ROMs or ZIPs allways conected to PC is not a pleasure!

sorinaugusto said:
Thanks man,great job!.Finally I have visual recovery!Flashing ROMs or ZIPs allways conected to PC is not a pleasure!
Click to expand...
Click to collapse
you can flash cm roms before?????

No,for my phone just Roms based on stock works.I have flashed and was working EQDKP roms,WildChild roms ,Superior sense rom,Kims mod rom.I have tried CM 7 and MIUI but did not work.But I am very interested to try CM roms or MIUI,so if you have any solutions for this please share with us.Thanks again.

cwm
I`m so Happy! It works on my wildfire s 2012! Thank you very, very much for your gift .

custom
ngoralph, i have one question - Can i flash a custom ROMs or kernels? or can i flash cyanogen any version (may be on stock kernel, if it`s possible?). Answer please, and thanks again!

Can i flash a custom ROMs or kernels? or can i flash cyanogen any version (may be on stock kernel, if it`s possible?).
Click to expand...
Click to collapse
I can answer this question: it is impossible. There are certain problems in work of this Mod. The first: does'nt making full nandroid backup. The second: does'nt flashing boot.img. It is necessary to develop this program still. But something, already is able: root, interface modding, ect....

Howdy.
I have flashed this recovery image and for the first time, can boot into recovery and see what I'm meant to see! Thanks. Previously (2012 hardware) I just hung on the white HTC logo screen.
Now, if I select backup and restore, press the power button, all the text disappears and I'm left with the central hat image... but nothing much happens. Pressing power again brings me back to the main menu. Same thing with -power off. The top option of reboot system now works just fine.
Any ideas? I'd like to backup my current system before flashing WildChild 3, you know - just in case anything goes wrong!
EDIT: immediate edit. cancel all of the above, I'm just new to recovery (obviously!). I went through the main menu a few times, it told me the back button was now active and away I go - backing up as we speak! Apologies!!! and thanks!

cwm
You must press one time into recovery volume + and several time volume - , while apear "back button is enable" and then such as in any cmw.

nitnit said:
You must press one time into recovery volume + and several time volume - , while apear "back button is enable" and then such as in any cmw.
Click to expand...
Click to collapse
i dont fully understand you but click volume up then down then up then downthenvolume up then down until back button enabled shows up

nitnit said:
ngoralph, i have one question - Can i flash a custom ROMs or kernels? or can i flash cyanogen any version (may be on stock kernel, if it`s possible?). Answer please, and thanks again!
Click to expand...
Click to collapse
haven't tried cm roms on stock kernel would anyone here like to try???

Uksus17 said:
I can answer this question: it is impossible. There are certain problems in work of this Mod. The first: does'nt making full nandroid backup. The second: does'nt flashing boot.img. It is necessary to develop this program still. But something, already is able: root, interface modding, ect....
Click to expand...
Click to collapse
agree with you here but i dont think anyone is willing and able to work on this recovery.

ngoralph said:
haven't tried cm roms on stock kernel would anyone here like to try???
Click to expand...
Click to collapse
i.m using now a custom kernel on my wfs2012 (overclocked 815 MGz) without trouble, but i can`t flash any CM roms because it hapens error Status7 in CWM. I think that this CWM is too old to flash CM ROMs. But we have no any choise

[Q] z1 comact stuck

i try to root me z1 compact (i have unlocked the bootloader) but i forget to save th superuser zip into sd card....i wwant in fastboot mode and i didn t innstall the zip.........and now i am stuck on fastboot mode...and i haven t do backup..what can i do ?plz help

Could you use an external SD card reader and plug to your PC to copy the file you need? then reinsert into your phone.

how?
mkhairym said:
Could you use an external SD card reader and plug to your PC to copy the file you need? then reinsert into your phone.[/QUOTE
man i copy the supersu in the sd card but when i choose zip i press update superSU and it writes ......done
and when i prees reboot system now it gets me into recovery mode again
Click to expand...
Click to collapse

thanos kary said:
mkhairym said:
Could you use an external SD card reader and plug to your PC to copy the file you need? then reinsert into your phone.[/QUOTE
man i copy the supersu in the sd card but when i choose zip i press update superSU and it writes ......done
and when i prees reboot system now it gets me into recovery mode again
Click to expand...
Click to collapse
well a bit more info would help, like on what rom you were on, and what steps you followed? At least you're able to boot into recovery, which lets you flash other roms since you've unlocked the BL
Click to expand...
Click to collapse

listen
darkmystel said:
thanos kary said:
well a bit more info would help, like on what rom you were on, and what steps you followed? At least you're able to boot into recovery, which lets you flash other roms since you've unlocked the BL
Click to expand...
Click to collapse
listen ...i haven t done buckup and i haven t flash my rom......my phone can get in to the recovery mode ONLY....can i get out from the recovery mode ?:crying:
Click to expand...
Click to collapse

Well if you have access to your recovery you should be able to mount your SD card there and then connect it to your PC. From there you can transfer a zip file to your phone and flash it.

I don't see anything mentioned about which custom recovery he flashed.
Could this be a stock recovery that he is in? (that may not allow mounting etc.)

.....
LaZiODROID said:
I don't see anything mentioned about which custom recovery he flashed.
Could this be a stock recovery that he is in? (that may not allow mounting etc.)[/QUOTE
i have done this....... and then what? i have 4.4.4 android
This is a CWM-Based Recovery 6.0.4.6 Touch Recovery for Xperia Z1 Compact!
Credits and special thanks to Koush and everyone else involved in Cyanogenmod project!
[ info ]
This Recovery is built from CWM 6.0.4.6 sources!
I dont have this device with me and I dont intend to buy one... my friend wanted root on his phone so I created this to help him out...
all the testing was done remotely on users devices...
[ PROOF ]
[ credits / special thanks ]
Koush - for the brilliant work & coding on CWM recovery
CyanogenMod and FreeXperia Team (especially jerpelea) for too many things *
special thanks to @swedan for helping out with testing and risking his devices for the sake of development!!! and NO, his phone was NOT damaged during testing
ME for creating this for u guys!
[ Requirements ]
Bootloader unlocked
working fastboot
STOCK ROM FW:
4.4.2
14.3.A.0.757 - v04
14.3.A.0.681 - v03
4.3
14.2.A.1.142 - v02
14.2.A.1.114 - v01
or ROMS BASED ON THAT FIRMWARE
[ features ]
standard CWM recovery 6.0.4.6 - TOUCH RECOVERY!
kernel is insecure (ro.secure=0)
adb debugging is enabled by default in OS
TIP: if u are experiencing very slow backup in CWM do this
[ WARNING ]
for flashing this kernel you WILL NEED TO UNLOCK BOOTLOADER! Check this thread for more info (same steps as Xperia Z1 are used for Xperia Z1 Compact)
UNLOCKING BOOTLOADER WITHOUT TA BACKUP WILL LEAD TO IRREVERSIBLE LOSS OF DRM KEYS!!!
AND YES CAMERA STILL WORKS AFTER UNLOCKING BOOTLOADER!!!
[ known issues ]
adb is not working in recovery (can be fixed later)
[ how to flash this kernel ] (via fastboot)
download the kernel image
save the boot.img to the folder containing fastboot binary
flash the boot.img using fastboot:
Code:
fastboot flash boot boot.img
reboot from fastboot
Code:
fastboot reboot
the device should now start booting
enjoy!
Click to expand...
Click to collapse

....
darkmystel said:
thanos kary said:
well a bit more info would help, like on what rom you were on, and what steps you followed? At least you're able to boot into recovery, which lets you flash other roms since you've unlocked the BL
Click to expand...
Click to collapse
yes i get into recovery and then what i must do?
Click to expand...
Click to collapse

thanos kary said:
darkmystel said:
yes i get into recovery and then what i must do?
Click to expand...
Click to collapse
I think a little more studying should have been done before flashing things. Now that we know you can get into CWM Recovery, you can flash a custom ROM. Note that doing so will involve wiping your data/cache/system - so whatever apps you were using on your phone will be gone (along with the data for each app, like your preferences etc.)
And since your bootloader is unlocked, you can flash pretty much any ROM you like because the unlocked bootloader allows custom kernels to be flashed.
As an example, you can flash SlimKat. It is a custom ROM with a custom kernel. The page is here: http://forum.xda-developers.com/showthread.php?t=2700456. You can find the download links in post #3. There will be a ZIP file for the ROM, and then optionally, another ZIP for the Google Apps (aka GAPPS), which would allow you to sign in to your Google account, use Play Store, etc. SlimKat offers 3 gapps (which I will link here because the GAPPS link on that thread seems to take me to a login page): They have mini, normal, and full. Take your pick..
http://www.slimroms.net/index.php/downloads/dlsearch/viewcategory/1150-addons4-4
Once you've downloaded them, copy the Slimkat ZIP to your external SD card. Also copy the GAPPS zip that you chose (if you wanted that).
Put the external card back into the phone and power it up, and get back into recovery like you did earlier. In recovery, before flashing the zips, you should do your wipes (this is where it wipes your apps/data/system). But as a precaution, maybe go into "install zip from sdcard", navigate through your external card to make sure the ZIP files are available to you.
I think that most ROM install zips take care of these wipes for you, but it's a good habit to get into when flashing custom ROMs.
You're going to:
1) Wipe data/factory reset (this will wipe the data and cache)
2) Go into Advanced and wipe Dalvik cache
3) Go into Mounts and Storage and format /system
Once that's done, you're going to go to "install zip from sdcard", choose your external card, and choose the SlimKat ZIP. That will flash the ROM and kernel. Once that's done, you're going to do one more flash - which is the GAPPS zip (if you decided that you wanted it).
Once that flash is done, you should be able to just reboot and the phone will start to boot into the new ROM. Note that on first boot, it will take some time - so you may be staring at the boot animation for a few minutes.
Click to expand...
Click to collapse

root?
LaZiODROID said:
thanos kary said:
I think a little more studying should have been done before flashing things. Now that we know you can get into CWM Recovery, you can flash a custom ROM. Note that doing so will involve wiping your data/cache/system - so whatever apps you were using on your phone will be gone (along with the data for each app, like your preferences etc.)
And since your bootloader is unlocked, you can flash pretty much any ROM you like because the unlocked bootloader allows custom kernels to be flashed.
As an example, you can flash SlimKat. It is a custom ROM with a custom kernel. The page is here: http://forum.xda-developers.com/showthread.php?t=2700456. You can find the download links in post #3. There will be a ZIP file for the ROM, and then optionally, another ZIP for the Google Apps (aka GAPPS), which would allow you to sign in to your Google account, use Play Store, etc. SlimKat offers 3 gapps (which I will link here because the GAPPS link on that thread seems to take me to a login page): They have mini, normal, and full. Take your pick..
http://www.slimroms.net/index.php/downloads/dlsearch/viewcategory/1150-addons4-4
Once you've downloaded them, copy the Slimkat ZIP to your external SD card. Also copy the GAPPS zip that you chose (if you wanted that).
Put the external card back into the phone and power it up, and get back into recovery like you did earlier. In recovery, before flashing the zips, you should do your wipes (this is where it wipes your apps/data/system). But as a precaution, maybe go into "install zip from sdcard", navigate through your external card to make sure the ZIP files are available to you.
I think that most ROM install zips take care of these wipes for you, but it's a good habit to get into when flashing custom ROMs.
You're going to:
1) Wipe data/factory reset (this will wipe the data and cache)
2) Go into Advanced and wipe Dalvik cache
3) Go into Mounts and Storage and format /system
Once that's done, you're going to go to "install zip from sdcard", choose your external card, and choose the SlimKat ZIP. That will flash the ROM and kernel. Once that's done, you're going to do one more flash - which is the GAPPS zip (if you decided that you wanted it).
Once that flash is done, you should be able to just reboot and the phone will start to boot into the new ROM. Note that on first boot, it will take some time - so you may be staring at the boot animation for a few minutes.
Click to expand...
Click to collapse
man i haven t done root yet.....i have 4.4.4 android can you give instructios? and slimkat it is not support my z1 compact
Click to expand...
Click to collapse

thanos kary said:
man i haven t done root yet.....i have 4.4.4 android can you give instructios? and slimkat it is not support my z1 compact
Click to expand...
Click to collapse
When you say you want to root, it means that you want to root the current system that you are on. But from what you have described in this thread, you are currently having a problem with your phone, where it does not boot normally into the system/ROM. You boot straight into Clockworkmod Recovery, every time. Correct? If this is correct, then rooting your current ROM probably won't help your situation (because you are not able to boot normally into the system).
Slimkat is a ROM that has root access included. I believe that pretty much any custom rom has root included. I'm not sure what you mean when you say that slimkat does not support your Z1 compact. You should be able to flash Slimkat to your Z1 Compact. The link from my previous post points to the Slimkat thread, which is in the Z1 Compact Original Android Development forum, so it is made for Z1 Compact.
That said, you don't need to choose Slimkat - I provided that just as an example of a custom rom that has a custom kernel included. Look through the Xperia Z1 Compact Original Android Development forum for custom roms that use custom kernels. Most of those roms have the custom kernel included in their ZIP. Whichever custom rom you choose, make sure to READ the original post (and other posts if necessary) to get the information you need on how to install it, or to find out what files you will need for that ROM (as some roms have add-ons and stuff you may find interesting).
There are also ROMs that are stock-based. Those can be found in the Xperia Z1 Compact Android Development forum. These roms also have root included, and are built to run on the standard stock Sony kernel. Some of them may be based on a specific stock Sony kernel version, so pay attention to that.
If you want to start over, and flash a pure stock Sony ROM to your phone (also known as an FTF), you can do that at any time by downloading an appropriate FTF for your phone, and flashing it by loading the FTF with FlashTool. It will then ask you to put your phone into FlashMode (which is done by making sure the phone is OFF, then holding the VolDown button, and connecting the USB cable while still holding the VolDown button. Once the flash begins, you can let go of the VolDown button) But !! Please note that if you haven't used FlashTool before, you will need to install some drivers. They are included with FlashTool, in a folder called Drivers. You would choose the driver specific to your phone, plus the FlashMode driver, plus the Fastboot driver. If you are using Windows8, you will have to do some extra work to get those drivers to install correctly. It involves booting Win8 into a mode where Driver Signature Enforcement is disabled, then installing the drivers found in the drivers folder of FlashTool. You can easily find out how to do that by searching online.
Hope this helps... don't make any risky flashing moves if you aren't certain about them - just keep reading and searching and you will eventually find the answers you need.

zoom out
LaZiODROID said:
When you say you want to root, it means that you want to root the current system that you are on. But from what you have described in this thread, you are currently having a problem with your phone, where it does not boot normally into the system/ROM. You boot straight into Clockworkmod Recovery, every time. Correct? If this is correct, then rooting your current ROM probably won't help your situation (because you are not able to boot normally into the system).
Slimkat is a ROM that has root access included. I believe that pretty much any custom rom has root included. I'm not sure what you mean when you say that slimkat does not support your Z1 compact. You should be able to flash Slimkat to your Z1 Compact. The link from my previous post points to the Slimkat thread, which is in the Z1 Compact Original Android Development forum, so it is made for Z1 Compact.
That said, you don't need to choose Slimkat - I provided that just as an example of a custom rom that has a custom kernel included. Look through the Xperia Z1 Compact Original Android Development forum for custom roms that use custom kernels. Most of those roms have the custom kernel included in their ZIP. Whichever custom rom you choose, make sure to READ the original post (and other posts if necessary) to get the information you need on how to install it, or to find out what files you will need for that ROM (as some roms have add-ons and stuff you may find interesting).
There are also ROMs that are stock-based. Those can be found in the Xperia Z1 Compact Android Development forum. These roms also have root included, and are built to run on the standard stock Sony kernel. Some of them may be based on a specific stock Sony kernel version, so pay attention to that.
If you want to start over, and flash a pure stock Sony ROM to your phone (also known as an FTF), you can do that at any time by downloading an appropriate FTF for your phone, and flashing it by loading the FTF with FlashTool. It will then ask you to put your phone into FlashMode (which is done by making sure the phone is OFF, then holding the VolDown button, and connecting the USB cable while still holding the VolDown button. Once the flash begins, you can let go of the VolDown button) But !! Please note that if you haven't used FlashTool before, you will need to install some drivers. They are included with FlashTool, in a folder called Drivers. You would choose the driver specific to your phone, plus the FlashMode driver, plus the Fastboot driver. If you are using Windows8, you will have to do some extra work to get those drivers to install correctly. It involves booting Win8 into a mode where Driver Signature Enforcement is disabled, then installing the drivers found in the drivers folder of FlashTool. You can easily find out how to do that by searching online.
Hope this helps... don't make any risky flashing moves if you aren't certain about them - just keep reading and searching and you will eventually find the answers you need.
Click to expand...
Click to collapse
ooooohhh man i love you ,....it works with slimkat....thank you ...thank you...but i don t like this rom ..tell me if you know......how to get back to the officil from sony?
and if you can give a guide to root 4.4 android z1c

thanos kary said:
ooooohhh man i love you ,....it works with slimkat....thank you ...thank you...but i don t like this rom ..tell me if you know......how to get back to the officil from sony?
and if you can give a guide to root 4.4 android z1c
Click to expand...
Click to collapse
You could try to flash Kitslim (http://forum.xda-developers.com/showthread.php?t=2743177)
It is a slightly optimized rom based on the original Sony stock rom.
I use it and ist awesome. You have the stock feeling with this.

.....
Schlengge said:
You could try to flash Kitslim (http://forum.xda-developers.com/showthread.php?t=2743177)
It is a slightly optimized rom based on the original Sony stock rom.
I use it and ist awesome. You have the stock feeling with this.
Click to expand...
Click to collapse
i will flash this rom...but first i want to go in official rom and then i will root the rom

how to root?
thanos kary said:
i will flash this rom...but first i want to go in official rom and then i will root the rom
Click to expand...
Click to collapse
can anyone tell me how to root....i can not root with easy towel root

[Q] How to flash CWM on Xperia S Stock JB?

Hi all,
I'm messing around with my girlfriends Xperia S and śtuck on installing a custom recovery (CWM seems to be the preferred one on the S).
The System:
Stock Sony JB
Build 6.2.B.1.96
What I already did:
Root
Backup TA
Unlocked Bootloader (official way via Sony website)
What I already tried to install custom recovery:
RecoverX App on PlayStore -> Recovery not booting when tapping the sony logo while booting (black screen for some seconds then reboot to Android)
Xperia S Dual Recovery (Linux script) -> Installation successful but no chance to boot one of the recoveries via Vol +/-, no blue LED, boots directly to Android
What I'm trying to achieve:
Install CM 11 with root access
I'm kind of experienced with HTC phones and my OnePlus One so not a complete noob but it looks like Sony phones are a different thing.
I read about the need to flash a custom kernel which includes the recovery but there are seperate recovery threads on the other hand. The sticky role up threads seem out of date.
Been reading since yesterday but this only lead to more confusion.
I hope someone can help me out getting CWM (or any other recommended recovery) on this phone to install CM 11.
And how to remove the recoveries I already installed and don't work?
EDIT 13:58
After further reading this looks like the way to go:
[RECOVERY] CWM-Based Recovery 6.0.2.7 for Xperia S (UnlockedBootLoader){JB}[20130824]
Correct? I don't want to end up bricking the device by trying different things. Can I flash CM11 ROMS using this recovery? The post says "do not use this for flashing CM10.1 (u will need to use the CM kernel for that)" which keeps confusing me ...
And how do I remove the recoveries already installed (list above) but not working?

real_sl4cker said:
Hi all,
I'm messing around with my girlfriends Xperia S and śtuck on installing a custom recovery (CWM seems to be the preferred one on the S).
The System:
Stock Sony JB
Build 6.2.B.1.96
What I'm trying to achieve:
Install CM 11 with root access
I'm kind of experienced with HTC phones and my OnePlus One so not a complete noob but it looks like Sony phones are a different thing.
I read about the need to flash a custom kernel which includes the recovery but there are seperate recovery threads on the other hand. The sticky role up threads seem out of date.
Been reading since yesterday but this only lead to more confusion.
I hope someone can help me out getting CWM (or any other recommended recovery) on this phone to install CM 11.
And how to remove the recoveries I already installed and don't work?
Click to expand...
Click to collapse
First copy the zip of CM11 ROM to the phone.
Then on PC, extract the boot.img (this is the custom kernel with recovery for the ROM) from the ROM zip and flash it via fastboot using the flashtool software. Then You will have a twrp installed in Your phone due to it. Now boot into twrp and flash the ROM.
Note, after You flash the boot.img, You won't be able to boot into stock firmware. You will have to flash the CM11 ROM.
Also, if the recovery are not accessible, they are probably not installed, so no need to remove them.

Mirhawk said:
First copy the zip of CM11 ROM to the phone.
Then on PC, extract the boot.img (this is the custom kernel with recovery for the ROM) from the ROM zip and flash it via fastboot using the flashtool software. Then You will have a twrp installed in Your phone due to it. Now boot into twrp and flash the ROM.
Note, after You flash the boot.img, You won't be able to boot into stock firmware. You will have to flash the CM11 ROM.
Also, if the recovery are not accessible, they are probably not installed, so no need to remove them.
Click to expand...
Click to collapse
Thank you very much for the instructions, now there's less confusion :good:
So let's see how it works with Paranoid Android. I'll report back afterwards.
Any Android 4.4 ROM recommendation as a stable daily driver?
Looks like there is no up to date standard CM11 build for the Xperia S

real_sl4cker said:
Thank you very much for the instructions, now there's less confusion :good:
So let's see how it works with Paranoid Android. I'll report back afterwards.
Any Android 4.4 ROM recommendation as a stable daily driver?
Looks like there is no up to date standard CM11 build for the Xperia S
Click to expand...
Click to collapse
From what I have been reading, PA does seem to be stable enough to be a daily driver, just find the correct build of it. I don't know which one is as I don't use it much, do ask in the thread.
I would suggest Carbon ROM too, but it is currently having some battery drain issues, the battery works for hardly an entire day.

Mirhawk said:
From what I have been reading, PA does seem to be stable enough to be a daily driver, just find the correct build of it. I don't know which one is as I don't use it much, do ask in the thread.
I would suggest Carbon ROM too, but it is currently having some battery drain issues, the battery works for hardly an entire day.
Click to expand...
Click to collapse
Thanks. I already found the current PA build in the thread (4.5 beta2) and apart from German translations missing in PA settings up to now it performs well [emoji3]

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

[Q]E988 Boot certification verify

I have kitkat 4.2.2 stockbase, rooted, trying to install cwm but stuck in the secure booting error boot certification verify.
Previously i installed rom manager app and flash the cwm from the app. After reboot to recovery, only stock recovery that showed, then i reboot to system, install freegee in order to flash the cwm but fail as freegee doesnt support gpro kitkat.
After that i install gpro kitkat recovery and flash the cwm from the app, success, reboot to recovery but stuck on the error.
I uninstalled rom manager and freegee, but still no luck to get the flashed cwm recovery,stuck in secure booting error.
Any suggestion or thread reference? Why is very difficult to install custom rom on this device?i plan to install carbon rom :crying:
Thank you in advance.

hotmatua.parulian said:
I have kitkat 4.2.2 stockbase, rooted, trying to install cwm but stuck in the secure booting error boot certification verify.
Previously i installed rom manager app and flash the cwm from the app. After reboot to recovery, only stock recovery that showed, then i reboot to system, install freegee in order to flash the cwm but fail as freegee doesnt support gpro kitkat.
After that i install gpro kitkat recovery and flash the cwm from the app, success, reboot to recovery but stuck on the error.
I uninstalled rom manager and freegee, but still no luck to get the flashed cwm recovery,stuck in secure booting error.
Any suggestion or thread reference? Why is very difficult to install custom rom on this device?i plan to install carbon rom :crying:
Thank you in advance.
Click to expand...
Click to collapse
Start from 4.1.2 stock, root, use freegee to bypass lockdown, flash latest TWRP then flash Lollipop ROMs... There is info about everything on the forums.

ShadySquirrel said:
Start from 4.1.2 stock, root, use freegee to bypass lockdown, flash latest TWRP then flash Lollipop ROMs... There is info about everything on the forums.
Click to expand...
Click to collapse
Thank you very much Shady.. Please be kindly to review steps that i should execute when flashing to Carbon Lollipop with regards to my current state (rooted 4.4.2. stock Kitkat):
Prerequisite:
- LG Flash Tool 2014 installed in PC
- LG United Mobile Driver (i use v3.11.3) installed in PC
- Stock firmware E98810e_00.kdz (Indonesia Jellybean) -- Jellybean stock base is required to cater modem/wakelock issue
- Stock firmware E98820c_00.kdz (Indonesia Kitkat)
- ROM Manager (for current state backup/restore)
- Freegee (to cater LG security issue after success flash)
- Towelroot (to root device after success flash)
- TWRP (for recovery tool after success flash)
- Downloaded ZeKrnl 1.7 Build 11/28 - https://forum.xda-developers.com/optimus-g-pro/development/rom-e980-ze-krnl-1-6-t3255975
- Downloaded ZeKrnl 1.6 - https://forum.xda-developers.com/optimus-g-pro/development/rom-e980-ze-krnl-1-6-t3255975/page4 (to cater camera issue after flashed to Carbon)
1. Flash CWM via ROM Manager
2 Execute Backup Current ROM to sd card via ROM Manager and save copy to PC
3. Backup manual for files, apks, contacts to sd card and save copy to PC
4. Copy ZeKrnl 1.7 zip & ZeKrnl 1.6 zip to sd card
5. Turn off phone, plug usb cable to phone
6. Press & hold Volume keys (Up + Down) then plug the other end of usb into PC to until download mode showned
7. Run LG Flash Tool with administrator privilege
8. Flash E98810e firmware into the device till success
(After Success Flash to Andro 4.1.2 JB):
9. Install towelroot and root the device
10. Install freegee to cater LG security issue
11. Install latest TWRP
12. Reboot into recovery mode
13. wipe system, data, cache, dalvik cache
14. flash ZeKrnl 1.7
--Camera issue
debug.composition. type=dyn --> debug.composition. type=gpu using build prop editor and/or flash ZeKrnl 1.6 kernell
https://forum.xda-developers.com/optimus-g-pro/development/rom-e980-ze-krnl-1-6-t3255975/page8
--Deep Sleep issue
https://forum.xda-developers.com/optimus-g-pro/development/rom-e980-ze-krnl-1-6-t3255975/page10
-- SD Card issue
https://forum.xda-developers.com/optimus-g-pro/development/rom-e980-ze-krnl-1-6-t3255975/page12
-- Kernel parameter tuning sampel
https://forum.xda-developers.com/optimus-g-pro/development/rom-e980-ze-krnl-1-6-t3255975/page14
Btw looks like you are the only person that still active in this thread...really appreciate it...thank you very much

You're complicating it too much, to be honest
Just do it this way:
1. flash stock 4.1.2 and keep it that way
2. root, install Freegee, install initial recovery (twrp, cwm, doesn't mater), update it to TWRP from forums (2.8 version is preferred)
3. you're ready to flash create stock backup and flash roms.
If I remember, all those changes are already implemented in both SlimLP and Carbon. Slim has newer kernel and gpu drivers, and that's it.

So you are saying i just flash the rom as is without any further change?Noted shady...i will inform you the result

ShadySquirrel said:
You're complicating it too much, to be honest
Just do it this way:
1. flash stock 4.1.2 and keep it that way
2. root, install Freegee, install initial recovery (twrp, cwm, doesn't mater), update it to TWRP from forums (2.8 version is preferred)
3. you're ready to flash create stock backup and flash roms.
If I remember, all those changes are already implemented in both SlimLP and Carbon. Slim has newer kernel and gpu drivers, and that's it.
Click to expand...
Click to collapse
Ive tried your suggestion with the following result:
a. Flash to stock 4.1.2 (v10e) : success but then the master file i downloaded is gone
b. Root, install freegee, initial recovery: success
c. Update to twrp 2.8 using twrp manager: success
d. Flash to Carbon: fail, canot enter recovery mode with message secure booting error,boot certification verify
So i just rollback to kitkat stock

hotmatua.parulian said:
Ive tried your suggestion with the following result:
a. Flash to stock 4.1.2 (v10e) : success but then the master file i downloaded is gone
b. Root, install freegee, initial recovery: success
c. Update to twrp 2.8 using twrp manager: success
d. Flash to Carbon: fail, canot enter recovery mode with message secure booting error,boot certification verify
So i just rollback to kitkat stock
Click to expand...
Click to collapse
So, you can't boot TWRP at all? It seems that TWRP you installed isn't lokified. Are you sure you've installed TWRP 2.8? I remember flashing it directly via flashify on my device and it worked.. Also, check TWRP thread for lokified zip, I think someone posted that.
Edit: you see now why almost everyone abandoned this device

ShadySquirrel said:
So, you can't boot TWRP at all? It seems that TWRP you installed isn't lokified. Are you sure you've installed TWRP 2.8? I remember flashing it directly via flashify on my device and it worked.. Also, check TWRP thread for lokified zip, I think someone posted that.
Edit: you see now why almost everyone abandoned this device
Click to expand...
Click to collapse
Yes, i cant boot twrp, i used twrp manager apk,i think its not lokified.

hotmatua.parulian said:
Yes, i cant boot twrp, i used twrp manager apk,i think its not lokified.
Click to expand...
Click to collapse
After installing freegee's twrp, reboot to recovery. Then, it might be OK.
After that, reboot system and use flashify, the free version will do.
You can either choose to download the file or chose from your internal / external memory.
I'm using the latest version TWRP 3.0.2.0.
If it doesn't work at first, go back to start and try again...

g0at1 said:
After installing freegee's twrp, reboot to recovery. Then, it might be OK.
After that, reboot system and use flashify, the free version will do.
You can either choose to download the file or chose from your internal / external memory.
I'm using the latest version TWRP 3.0.2.0.
If it doesn't work at first, go back to start and try again...
Click to expand...
Click to collapse
Thanks for respond, i have to download the jb stockbase again as the file used for lg flash tool is missing, looks like flashtool keep it somewhere...btw, when i use flashtool to flash the jb stock (offline mode), it.doesnt complete 100%, at 99% device was successfully boot and normal but state in flashtool screen is 99% and message to.retry is showned up.
Fyi, after flashed to jb, i cant execute fastboot flash command, the result is waiting for any device, but adb devices command return expected result. Enable debugging setting is already checked also.

Quiet interesting this device...salut to programmers of this device...

hotmatua.parulian said:
Thanks for respond, i have to download the jb stockbase again as the file used for lg flash tool is missing, looks like flashtool keep it somewhere...btw, when i use flashtool to flash the jb stock (offline mode), it.doesnt complete 100%, at 99% device was successfully boot and normal but state in flashtool screen is 99% and message to.retry is showned up.
Fyi, after flashed to jb, i cant execute fastboot flash command, the result is waiting for any device, but adb devices command return expected result. Enable debugging setting is already checked also.
Click to expand...
Click to collapse
G Pro doesn't support fastboot commands (or is really limited in that field, I'm not sure what to say/think), due to some mess LG made. Mine didn't even want to 'adb reboot bootloader', it simply rebooted device back to system, and was pain in the ass for many things because It has custom download mode, it has custom boot sequence, everything is locked down... everything is different from everything else you're used to. Thank God back then a+b OTA system didn't exist, we'd never get any AOSP support not...
Do as g0at1 said - flash TWRP from Freegee, boot it to make sure it works, reboot back to system and flash newer TWRP from Flashify or any other tool like that one. I did have E988 (just Taiwan variant), and never had that much issues, nearly every time it was a straightforward 'flash JB KDZ, root it manually, Freegee, newer TWRP, backup, flash ROM', and trust me, that one was "revived" many times.
In the end, if even that doesn't help, flash CWM from Freegee, and update it with Philz Touch for E980. I think it will support Lollipop ROMs without any issues, just don't ever boot directly into it if you're not ready to mess with dd from recovery mode - always use adb.
hotmatua.parulian said:
Quiet interesting this device...salut to programmers of this device...
Click to expand...
Click to collapse
This device was one of the hardest devices to work with... and I had Note N7000 with bad MMC which nearly bricked five times running unrooted stock firmwares Samsung provided. And Tegra-based Galaxy S2 clone with many hardware and software issues on stock... And many nameless devices with chips made by "big" vendors, like Allwinner, Rockchip etc which got some older CyanogenMod version builds with some or even complete success... And I never, never had that much issues porting stuff to any of these above, as I had with G Pro. Heck, working on a overclocking and underclocking for G Pro took me nearly two months of coding, testing, scratching everything off and starting from the beginning to just get it to some functional level and make it work as intended... and when I look at that code, I still have a feeling that it isn't completed and that some fixes are still necessary. I won't even start with GPU issues, I've spent more time than I'd like to admit on patching sessions.

ShadySquirrel said:
G Pro doesn't support fastboot commands (or is really limited in that field, I'm not sure what to say/think), due to some mess LG made. Mine didn't even want to 'adb reboot bootloader', it simply rebooted device back to system, and was pain in the ass for many things because It has custom download mode, it has custom boot sequence, everything is locked down... everything is different from everything else you're used to. Thank God back then a+b OTA system didn't exist, we'd never get any AOSP support not...
Do as g0at1 said - flash TWRP from Freegee, boot it to make sure it works, reboot back to system and flash newer TWRP from Flashify or any other tool like that one. I did have E988 (just Taiwan variant), and never had that much issues, nearly every time it was a straightforward 'flash JB KDZ, root it manually, Freegee, newer TWRP, backup, flash ROM', and trust me, that one was "revived" many times.
In the end, if even that doesn't help, flash CWM from Freegee, and update it with Philz Touch for E980. I think it will support Lollipop ROMs without any issues, just don't ever boot directly into it if you're not ready to mess with dd from recovery mode - always use adb.
This device was one of the hardest devices to work with... and I had Note N7000 with bad MMC which nearly bricked five times running unrooted stock firmwares Samsung provided. And Tegra-based Galaxy S2 clone with many hardware and software issues on stock... And many nameless devices with chips made by "big" vendors, like Allwinner, Rockchip etc which got some older CyanogenMod version builds with some or even complete success... And I never, never had that much issues porting stuff to any of these above, as I had with G Pro. Heck, working on a overclocking and underclocking for G Pro took me nearly two months of coding, testing, scratching everything off and starting from the beginning to just get it to some functional level and make it work as intended... and when I look at that code, I still have a feeling that it isn't completed and that some fixes are still necessary. I won't even start with GPU issues, I've spent more time than I'd like to admit on patching sessions.
Click to expand...
Click to collapse
:good::good::good::good: salut to you...the true programmer..never quit..yes im agree with you...i had played with nexus 1,2,3 before but never found something like this...
OK then, i will try g0at1 suggestion, hopefully it works... Like you said its only JB, root, freegee, newer twrp, backup, flash custom

Update
I couldnt wait to try again,i cant download the jb stock for a while due to internet quota limitation, so i did this:
1. Flash to stock that i still have v20c 4.4.2
2. Reboot to stock recovery then reboot to system
3. Run roottool.kitkat batch script (found from http://www.gadgetstroop.com), reboot to recovery, sideload installation of root script with result success
4. Reboot to system, run Root Checker to ensure device has been rooted
5. Install cwm recovery with GPro Kitkat Recovery 6.0.4.4 with result success
6. Reboot to cwm recovery success and do nandroid backup
7. Reboot to system, install flashify, download latest twrp official 3.0.2 and flash it using flashify: success
8. Reboot to recovery, now the recovery become twrp
9. Install package Carbon 5.1 unofficial: fail with message "cant install this package on top of incompatible data"

hotmatua.parulian said:
Update
I couldnt wait to try again,i cant download the jb stock for a while due to internet quota limitation, so i did this:
1. Flash to stock that i still have v20c 4.4.2
2. Reboot to stock recovery then reboot to system
3. Run roottool.kitkat batch script (found from http://www.gadgetstroop.com), reboot to recovery, sideload installation of root script with result success
4. Reboot to system, run Root Checker to ensure device has been rooted
5. Install cwm recovery with GPro Kitkat Recovery 6.0.4.4 with result success
6. Reboot to cwm recovery success and do nandroid backup
7. Reboot to system, install flashify, download latest twrp official 3.0.2 and flash it using flashify: success
8. Reboot to recovery, now the recovery become twrp
9. Install package Carbon 5.1 unofficial: fail with message "cant install this package on top of incompatible data"
Click to expand...
Click to collapse
You forgot to wipe system, data and caches.

ShadySquirrel said:
You forgot to wipe system, data and caches.
Click to expand...
Click to collapse
Hehehe,..thats what i thought at 1st place when it comes to fail..so i reboot to system again, reboot to recovery and try again but the result is still the same....cant install on top of icompatible data..
P.S: now downloading your slim lp 5.1 beta unofficial and i want to try it 2morrow...

hotmatua.parulian said:
Hehehe,..thats what i thought at 1st place when it comes to fail..so i reboot to system again, reboot to recovery and try again but the result is still the same....cant install on top of icompatible data..
P.S: now downloading your slim lp 5.1 beta unofficial and i want to try it 2morrow...
Click to expand...
Click to collapse
I use SlimLP for a long time because it's the only one that works smoothly for me. You might not have any trouble flashing it Through the latest TWRP.
Have fun!

g0at1 said:
I use SlimLP for a long time because it's the only one that works smoothly for me. You might not have any trouble flashing it Through the latest TWRP.
Have fun!
Click to expand...
Click to collapse
Finally carbon installed successfully after I repeat the step very carefully including your reminder bout wiping...
Thank you very much, I will consult any bugs I found..

Half Day 1 issue:
- Scrambled screen layout each time booting
- Camera unstable/crash, also with apps camera mx and open camera
- i think batt is draining faster than kitkat stock
- i feel internet via wifi is slower than kitkat stock
- phone call, other person cant hear my voice

Just flashed SlimLP..Gosh its so slim and smooth...thank you very much...there issue bout the camera and scrambled screen each time I reboot the system, which camera apps I should use?