Database Develop

CWM recovery with stock kernel? - Help

Hi,
I unlocked the bootloader, flashed CWM into it. I backed up everything through CWM recovery.
However somehow the stock rom/kernel/etc don't work with this set-up. I just have "free xperia" logo until the universe will implode.
Therefore I installed cyanogenmod and it works. But I don't have the Xperia pkgs and since I own a lot of stuff from sony..those apps are usefull.
Question 1: Can I use CWM recovery with the stock sony rom?
Question 2: I just downloaded the ftf (700MB file), how can I restore everything? If I fastboot everything inside the package will it also correct the boot problem?
Question 3: Can I install sony pkgs as a 3rd party zip like google-apps?
Thanks for the help!!

Yes, you can use stock kernel with recovery.
But, since you are unlocked, you can install DoomKernel, its based on stock , it has a recovery and root included, and it is compatible with stock roms. Install it via fastboot, then you can flash a stock ftf excluding the kernel so you don't lose custom kernel.

DrKrFfXx said:
Yes, you can use stock kernel with recovery.
Click to expand...
Click to collapse
You mean in CWM menus? and install the .ftf?

forevertheuni said:
You mean in CWM menus? and install the .ftf?
Click to expand...
Click to collapse
CWM can't flash ftf, for that you need Flashtool.
CWM can only flash flasheable zips.

If you want to keep stock rom with a working cwm recovery you have choice using advanced stock kernel or doomkernel both have a recovery working normally. If you don't want to overclock/underclock and tweak stuff choose advanced it is the stock kernel with a recovery with nothing more.
Flash ftf and then fastboot the kernel you choose, or vice versa fastboot and then flash ftf and exclude kernel in flashtool.
edit : read this http://forum.xda-developers.com/showthread.php?t=2153167

Trying to install 4.4 Rom, falling at every hurdle.

Hi There,
Just wondering if anyone had any ideas why my phone refuses to co-operate!
Basically, after getting bored of the stock rom when I first got my phone, I somehow managed to install a CM based rom. That worked, but I got bored of the fact that the camera never seemed to work right, and some apps didn't work/ were graphically buggy. Assuming it was just a badly ported graphics driver or whatever, I found a way, using FlashTool, to revert to the stock rom (C6603_10.3.1.A.0.244_Generic UK to be precise). I wasn't sure exactly what it did, but it was back how it used to be. sorted.
So, since kitkat made it's way to the XZ, I thought I'd try one of those roms, being the curious bugger that I am. The process I ended up going with eventually was:
>Downgrading Kernel to a lower version because the root explot wouldn't work on 10.3.1.A.0.244
>Rooting using "DooMLoRD_Easy-Rooting-Toolkit_v18"
>Upgrading kernel to one that would accept a recovery
>Installing TWRP
>Booting into recovery, CWM appeared instead. Strange, I thought. Oddly, mount USB wouldn't work at all, so I had to boot the phone back up to transfer the kitkat rom over
>Trying to flash the rom gave me an error number 7
>Boot Loop, at which point I just flashed 10.3.1.A.0.244 again.
I've tried this twice now, first with DooM Kernel, and then once with a different one. Neither CWM or TWRP have worked properly. Any help? Or am I just cursed?
Cheers

Tried this again, did literally everything I could think of and still no dice. Help? Have I somehow forced my phone to be on stock software forever?

If you dont unlock your bootloader, you can not use any kind of custom kernel.
That means aosp or aokp based firmwares can not run over locked bootloader.
Locked bootloader checks sign of kernel, if not certificated you will stuck on bootloop.
If you want to use any kind of custom rom... basicly.
1. Backup ta partition. " so you can revert any time you want."
2. Copy firmware zip file tou your internal or external sdcard.
3. Flash custom kernel. "Most of kernel have recovery option build in".
4. Boot in recovery mod. "Mostly press volume down while booting"
5. Insall custom rom.
6.a wipe dalvik-cache
6.b factory reset
Old setting might work or not with new rom. So first try to wipe dalvik- cache. If you stuck on boot loop or any kind of problem, just boot in recovery again and run factory reset.
Sent from my C6603 using Tapatalk

eryen said:
If you dont unlock your bootloader, you can not use any kind of custom kernel.
That means aosp or aokp based firmwares can not run over locked bootloader.
Locked bootloader checks sign of kernel, if not certificated you will stuck on bootloop.
If you want to use any kind of custom rom... basicly.
1. Backup ta partition. " so you can revert any time you want."
2. Copy firmware zip file tou your internal or external sdcard.
3. Flash custom kernel. "Most of kernel have recovery option build in".
4. Boot in recovery mod. "Mostly press volume down while booting"
5. Insall custom rom.
6.a wipe dalvik-cache
6.b factory reset
Old setting might work or not with new rom. So first try to wipe dalvik- cache. If you stuck on boot loop or any kind of problem, just boot in recovery again and run factory reset.
Sent from my C6603 using Tapatalk
Click to expand...
Click to collapse
Hey, thanks for your reply!
I had unlocked the bootloader when I first got the phone and just assumed it would be permanent. Would flashing it back to stock firmware re-lock the bootloader?
But yes, assuming my boot loader is still unlocked ( I have tried to check and it doesn't seem to be locked) I have been through those steps basically. I am fine to flash a kernel with a recovery but the recovery never works properly/ at all. I can root the phone no problem though.

Best to extract the boot.img from the zip file of the ROM you want to flash, and flash that first. Then flash the ROM from its recovery.
Sent from my C6603 using xda app-developers app

shoey63 said:
Best to extract the boot.img from the zip file of the ROM you want to flash, and flash that first. Then flash the ROM from its recovery.
Sent from my C6603 using xda app-developers app
Click to expand...
Click to collapse
Cheers, I'll give that a go - I was under the impression that you weren't supposed to flash kernels that weren't designed for the currently installed ROM though? It just seems that any kernel I flash isn't working properly so I didn't think doing that would play any nicer with the phone

SuburbanKnight said:
Cheers, I'll give that a go - I was under the impression that you weren't supposed to flash kernels that weren't designed for the currently installed ROM though? It just seems that any kernel I flash isn't working properly so I didn't think doing that would play any nicer with the phone
Click to expand...
Click to collapse
You're not actually going to boot into your current rom after flashing the kernel.
Flash the kernel via fastboot, then boot into recovery and flash the rom.
All this should be covered in the installation instructions of whatever rom you're trying to flash in any case....
Sent from my C6603 using Tapatalk

Well, that seems to have done it! Thanks very much for your help.
So, I guess the moral here is that if you're on stock and need a recovery to flash a new ROM, always use the boot.img from the ROM you'll be using.
Thanks again - I'd never seen that said before but quite possibly I wasn't paying attention!

[Q] Go back to stock ROM from Cyanogenmod/CWM

Hi all
I have CM 10.2 and CWM recovery installed on my Z. Now I'm going to sell it and would like to "revert" to the stock ROM.
I realized that the Flash Tool by Bin4ry and Androxyde only works with stock, locked bootloaders so I cannot install original ROMs the "normal" way.
I assume I need to find a stock ROM image zipped in a format that is compatible with CWM recovery, and flash from there?
Thanks for all help

nope it should work with any Rom just download the ftf you want and flash it it would work with any Sony Device either Locked or Unlocked

[Q] Xperia SP C5302 Stuck in boot logo! PLEASE HELP!

I was curious about installing custom roms so i decided to try. I successfully had rooted my phone and unlocked the bootloader and i just needed CWM recovery so that I could install CM11 custom rom. I didn't put the custom rom on my phone because I'd figure I would do it after installing CWM but after flashing CWM, I couldn't even go into my stock rom! I tried everything from formatting the cache to the data, I even have TWRP flashed as well but no luck there. I don't want to mess with my phone anymore because I am quite frankly, scared. So all I want to do is remove CWM and TWRP recovery, and flash my stock rom. Oh, and I tried to flash the stock rom with flashtool, that didn't work either
Thanks for the help!
UPDATE: I DOWNLOAD ALL THE DRIVERS FOR FLASHTOOL AND TRIED INSTALLING MY STOCK ROM THROUGH FLASH BOOT AND IT WORKED! SO FAR SO GOOD.
UPDATE 2: ITS WORKING. ALL I DID WAS LOCK MY BOOTLOADER WITH FLASHTOOL AND FLASHED THE STOCK ROM!

I think you could mount the usb storage from CWM, so you could copy the rom you wanted and install it? You could have saved a lot of hassle loool

Problem Flashing Offcial Firmware

Hi, Dear xda members
Last week i soft bricked my Sony Xperia Z c6603
After flashing modified kernel, i lost everything
I couldn't reach recovery even couldn't flash one with fastboot(as my device was not recognized)
I tried flashing offcial firmware through flashtool. It succeeded flashing
But After reboot i had bootloob and the ROM didn't boot
Finally I had a solution to get my phone fixed. Here's what i did:
*Reboot to FlashMode
*In flashtool I flashed TWRP Recovery in FlashMode
Now all custom ROMs are working but when I flash an official and other ROM's based on official, I'm having bootloops
Tried to wait. NO result
Could you help me with it?
P.S the modified kernel was made by this tool http://forum.xda-developers.com/xpe...ot-automatic-repack-stock-kernel-dm-t3301605/
When i softbricked my phone I tried to fix it according to this guide http://forum.xda-developers.com/xpe...rick-sony-xperia-z-c6602-c6603-c6606-t3215134

after i flashed the cm rom, i got the same problem. after flash the stock ROM or official firmware, It keep bootloop. how you fixed It ?

315cqab said:
after i flashed the cm rom, i got the same problem. after flash the stock ROM or official firmware, It keep bootloop. how you fixed It ?
Click to expand...
Click to collapse
Do you still need the method i have gone through?

do you know how to flash the official ROM or firmware back? now i can only flash the custom ROM

315cqab said:
do you know how to flash the official ROM or firmware back? now i can only flash the custom ROM
Click to expand...
Click to collapse
Sorry even i need this. Currently i have the same problem. I cant flash official firmware or the one that is based on official. I need the solution

Same here, after install CM 14.1, i can't go back to official or rom based in Stock...

gussbravo said:
Same here, after install CM 14.1, i can't go back to official or rom based in Stock...
Click to expand...
Click to collapse
I have several problems too including not being able to run stock anymore. (endless black screen after experia logo). I tried flashtool (latest stock via xperifirm), Sony's flashtool. Companion didn't even want to flash (UEGetPhoneInfoMissingInfo), and left me wondering wether something is corrupt.
I've been running CM's for a while now and was wondering why NFC was not working. Not sure if it needs an updated firmware or what.
Other problem I've seen is that "fastboot flash recovery" always gives an error. "fastboot flash boot" works (this is how I install TWRP).
Can I try zeroing mmcblk0 or would that brick it? (does it really need to have a TA partition to accept boot connection? How does Sony init it anyways?)
I think I have a mmcblk0 backup from after unlocking (DRM lost though) but perhaps that will give me a somewhat clean situation again. Or perhaps I can compare it.
Edit: dd-ed my old mmc backup and now Xperia Companion didn't give an error anymore, did a factory reset, and after a long wait of the blue waving animation, I got it to work.
Even NFC firmware update started after rooting and deleting /data/ucf folder.
Now I want to go back to Nougat xD