hassummit.blogg.se

1. #Fastboot flash recovery cyanogenmod.exe install
2. #Fastboot flash recovery cyanogenmod.exe drivers
3. #Fastboot flash recovery cyanogenmod.exe update
4. #Fastboot flash recovery cyanogenmod.exe driver

#Fastboot flash recovery cyanogenmod.exe install

You will first have to unlock the bootloader via the command prompt (PC will be connected), then install the rooting package and then install the custom recovery – there are many to choose from, but we’ll be working with ClockWorkMod here.Īfter all that hard part is done, we’ll reach the last step – and that’s installing the Android 4.4 KitKat based CyanogenMod 11 ROM on your Xperia Z. Sounds like a lot of work, doesn’t it? Not to worry, the main idea is to flash (install) files on your Xperia Z. The procedure itself for installing KitKat 4.4 on Xperia Z is pretty simple – just a few flashes and wipeouts.The tricky part is what comes before – You’ll have to unlock your Xperia Z’ bootloader, root it and install a custom recovery. If you want to get a step ahead of other Xperia Z users and install the CyanogenMod 11 ROM on your phone to get all the latest user interface changes and cool features that Google has put under the hood then keep reading.

#Fastboot flash recovery cyanogenmod.exe update

I spent another half hour scratching my head before realising that the command in the OP refers to cwm60xx but of course the image file is cwm6050 so once I'd put right that schoolboy error that I'd made,all was good.All the Xperia Z users know better than us that Sony’s not looking to push the official Android 4.4 KitKat update for their flagship Android devices anytime soon – though Sony has confirmed that it’s working on it.

I do also have a small confession to make though that may save others some grief,don't do what I did and blindly copy and paste the fastboot commands from the OP and then wonder why fastboot can't find the recovery file.

#Fastboot flash recovery cyanogenmod.exe driver

To make sure everything was working properly as I went along I used the commandsĪnd with the new driver installed fastboot showed the device and I could continue to boot into the new recovery to make a backup then go through the process again to flash it.I then flashed Super SU and one of the trimmed down versions of Gapps and now have one very cheap (£38.99) Kitkat phone to use for work. However,for some strange reason,when I uninstalled the ZTE adb driver and installed the one shown in the video then everything worked.

#Fastboot flash recovery cyanogenmod.exe drivers

I had suspected a driver issue but my device manager showed no missing drivers and a ZTE adb driver installed so I wrongly assumed that it would work. Also Google search for 'windows 8 fastboot driver' will give you plenty of results. There's people with the same issue on my Blade III CWM thread and also few versions of fastboot drivers posted there. Fastboot is a generic Google mode (USB\VID_18D1&PID_D00D), it's not even something that you'd need a vendor specific driver. I still can't believe how winblows can have such major issues with this. Thanks again and keep up your amazing work Konstat! : ) Can someone help? What am I doing wrong, did I misse something? Since that's happening to me, I can't install CMW. I've notice that when I run the first comand, on device management, the phone get's like it lost the drivers or something like that, it show "android device" or something like that - can't remember now - with an exclamation port. I've followed this guide and installed everything needed, but when I execute "adb reboot bootloader", the phone turns black, and then when I execute "fastboot boot recovery-cwm6050-kis3.img", it keep on waiting for the devide. I've tried to install CWM on my Smart A16 (from Portugal). I had a Blade and I've used many of his great roms.