Develop Bugs

[Q] Clockworkmod ROM Manager Question

I'm new to Android and recently picked up an 2013 Nexus 7. I unlocked the device and flashed 4.4 Kitkat yesterday. Today I downloaded Clockworkmod Rom Manager so I could make a backup image.
After installing ROM Mgr version 5.5.3.0, I launched the app and received the message that I needed to install the custom recovery. I followed the steps given in the app below:
1) Identified device as Nexus 7
2) Selected "Install Recovery ClockworkMod Recovery"
3) Selected 'Flash Clockworkmod Recovery'
A download overlay appeared and the download completed. After doing this, I rebooted the device into recovery mode (power + Volume UP), but the stock recovery was still there. I tried the download again using the steps above, but still no luck. When I select "Reboot into Recovery", I receive the error message "An error occurred while attempting to run privileged commands".
Question:
1) Where are these Clockworkmod Recovery downloaded files going and how can I get rid of them? If I do a full wipe of the device to clear out these junk files that I may have downloaded?
Any input would be much appreciated. My goal is to set up my device, and take a base image that I can store off of the device on an external drive.
Thanks,
Rick
Cliffs: Installed Clockworkmod ROM Manager and am doing something wrong setting up Clockworkmod Custom Recovery

Haven't used ROM manager in a long time but there should be a ROM manager folder downloads should be there. Also fastboot either cwm or twrp and you can make a back up.

shane1 said:
Haven't used ROM manager in a long time but there should be a ROM manager folder downloads should be there. Also fastboot either cwm or twrp and you can make a back up.
Click to expand...
Click to collapse
Thanks Shane. I will check for the files. I basically flashed Kitkat and now just want to make a Nandroid backup. I assume since the device is unlocked that means I'm rooted.

In order to root you have to flash supersu in recovery.

shane1 said:
In order to root you have to flash supersu in recovery.
Click to expand...
Click to collapse
Thanks, I now think I may not be rooted but rather just unlocked which was required to flash Kirkpatrick from a command line.

After you flash a recovery, http://download.chainfire.eu/365/SuperSU/UPDATE-SuperSU-v1.69.zip flash that in recovery and you'll be rooted.

shane1 said:
After you flash a recovery, http://download.chainfire.eu/365/SuperSU/UPDATE-SuperSU-v1.69.zip flash that in recovery and you'll be rooted.
Click to expand...
Click to collapse
Thanks, it makes sense now. All I did really was unlock, and flash in the bootloader and then the 4.4 image file. So, I'm not rooted, but just unlocked.
Is it necessary to root the device to take a Nandroid backup?
Rick

I just read your new to android make sure you read directions of anything you plan on flashing. Also its good to read entire threads if you have any issues cause your probably not the first to have an issue. Enjoy.
---------- Post added at 07:44 PM ---------- Previous post was at 07:43 PM ----------
Not necessary to root but you do need to flash a recovery IMO tarp is the easiest

C5Longhorn said:
Is it necessary to root the device to take a Nandroid backup?
Rick
Click to expand...
Click to collapse
No, you do not need to root to make a nandroid.

meekrawb said:
No, you do not need to root to make a nandroid.
Click to expand...
Click to collapse
It seems like most of the custom recoveries like Clockworkmod recovery and TWRP require you to be rooted.

C5Longhorn said:
It seems like most of the custom recoveries like Clockworkmod recovery and TWRP require you to be rooted.
Click to expand...
Click to collapse
Nope. You need a custom recovery to root. And to make backups. You do not need to be rooted to make backups. That is how it is on the devices I own, anyways.

HTC One M8 How to backup stock image

Hey All,
Model: HTC One M8 - 0p6b160
CID: TELUS0001
Got a HTC One M8 the other day, I have already dev unlocked it via HTC, but I'm looking to have root and if possible s-off but stay on the stock image.
I've been wanting to backup the recovery image (since there seems to be very little resources for the TELUS001 CID) but from everything I've read this can only be done once you have root using adb and dd. To get root I need to install TWRP or PHILZ.
What I'm not clear about:
Are TWRP or PHILZ replacing the recovery image? Is there actually a way to backup recovery image? or did I miss something.
When TWRP/PHILZ do a backup is it just the current installed state of the phone?
Reading a post on another forum (can't post link cause I'm new) they talk about doing a temporary flash, but I didn't seem to be able to make that work using: fastboot boot twrp-m8-recovery.img
In the future I want to go to Android L, will any of this prevent it?
Thanks

felix2000 said:
Are TWRP or PHILZ replacing the recovery image? Is there actually a way to backup recovery image? or did I miss something.
When TWRP/PHILZ do a backup is it just the current installed state of the phone?
Reading a post on another forum (can't post link cause I'm new) they talk about doing a temporary flash, but I didn't seem to be able to make that work using: fastboot boot twrp-m8-recovery.img
In the future I want to go to Android L, will any of this prevent it?
Click to expand...
Click to collapse
1 and 3. You can backup stock recovery by booting into custom recovery that is located on your computer, instead of flashing custom recovery to the phone. This is already what you have described in Item 3. Is your phone in fastboot mode? The TWRP file is located in the same folder as fastboot.exe? Are you sure you have fastboot connectivity? To check this, type "fastboot devices" (with no quotes) and see if your device ID comes up.
Also, a great many stock recoveries are already posted here: http://forum.xda-developers.com/showthread.php?t=2701376
This thread also describes the process of backing up stock recovery via fastboot.
2. Not sure what you are asking. But yes, recovery can't backup something that isn't there (just current installed state).
4. Having custom recovery will prevent install of OTA, if that is what you mean. But return to stock recovery and restore any system files altered by root allows install of OTA. Or you can just install a custom ROM based on Android L when it comes out, as custom ROMs are sure to come quickly after L is available. Maybe even sooner than your version's OTA.

[Q] Failure to update to Lollipop. Now what?

I have Vodafone IE HTC M8. I tried to upgrade to stock 5.0 (just recently arrived). As people advised, flashed stock recovery and started OTA upgrade... And got big red triangle... Have no idea why I managed to reboot (Power + VolUp). And ... Now I cannot get to recovery any more, the phone says "Software status: modified" and stays in the boot loader.
Any attempts to flash recovery fail with "signature verify fail". I tried various things: stock recovery, philz recovery. Same thing.
Any advice? I would really like to have recovery recovered...

It seems I managed to oem lock the phone again. Unlocked - and can normally flash recovery.
So, philz recovery works, once flashed. But the stock recovery... It does not work, at all. Trying to switch to it, getting back to bootloader (and I see some messages, quickly disappearing: "No image or wrong image". Still not good

1. Unlock your Bootloader
2. Load adb/fastboot (if you're to lazy to install this all, like me, use the version from the video https://www.youtube.com/watch?v=5xVl2dBTnmI)
3. Then load the latest Version of TRWP and flash it with fastboot
4. Download the right nandroid backup here http://forum.xda-developers.com/show...postcount=2960
5. Start Recovery on your Device and Make backup of boot (to see were the right place is to put in the nandroid)
6. Start Backup from the nandroid via TRWP on your device
7. Finish
(The only thing is, that you have got a branded HTC8)
This was the thing I did here. I think it should work for you too.
Here you can see my Thread with a similar Problem:
http://forum.xda-developers.com/htc-one-m8/help/bootl-loop-lollipop-update-t3016142

sudaltsov said:
I have Vodafone IE HTC M8. I tried to upgrade to stock 5.0 (just recently arrived). As people advised, flashed stock recovery and started OTA upgrade... And got big red triangle... Have no idea why I managed to reboot (Power + VolUp). And ... Now I cannot get to recovery any more, the phone says "Software status: modified" and stays in the boot loader.
Any attempts to flash recovery fail with "signature verify fail". I tried various things: stock recovery, philz recovery. Same thing.
Any advice? I would really like to have recovery recovered...
Click to expand...
Click to collapse
When you get the big red triangle, press & hold volume up and tap power button once to read the error log.
As some have same problem like yours, the problem maybe wrong stock recovery.
To ensure the right recovery image for you to proceed OTA, download OTA again, when it ask to install select install later. Connect your device to PC, open the Internal Storage with PC explorer, browse to Download folder, you'll have the OTA.zip there. Copy that OTA.zip to PC, open it with 7-zip then open firmware.zip that you see inside, extract out the recovery.img ---this is the correct recovery image to use.

ckpv5 said:
When you get the big red triangle, press & hold volume up and tap power button once to read the error log.
As some have same problem like yours, the problem maybe wrong stock recovery.
To ensure the right recovery image for you to proceed OTA, download OTA again, when it ask to install select install later. Connect your device to PC, open the Internal Storage with PC explorer, browse to Download folder, you'll have the OTA.zip there. Copy that OTA.zip to PC, open it with 7-zip then open firmware.zip that you see inside, extract out the recovery.img ---this is the correct recovery image to use.
Click to expand...
Click to collapse
I had the same problem. I did exactly what you said. extracted the stock recovery.img from the OTA update, flashed my M8 with this recovery, still no luck
I am on 3.28.401.9 stock rom from last OTA
unlocked
this is the error I'm getting :
{
"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"
}

snowfree52 said:
I had the same problem. I did exactly what you said. extracted the stock recovery.img from the OTA update, flashed my M8 with this recovery, still no luck
I am on 3.28.401.9
this is the error I'm getting :
Click to expand...
Click to collapse
Your error is different .. the libril-qc-qmi-1.so is modified and not pure stock. You need to replace this file with the stock one.
To make thing easier for you, just flash TWRP again and restore my 3.28.401.9 nandroid backup here : http://forum.xda-developers.com/showpost.php?p=56979449&postcount=2960
You can restore only the system part, keep your data part so you have pure stock system but your data intact.

ckpv5 said:
[/HIDE]
Your error is different .. the libril-qc-qmi-1.so is modified and not pure stock. You need to replace this file with the stock one.
To make thing easier for you, just flash TWRP again and restore my 3.28.401.9 nandroid backup here : http://forum.xda-developers.com/showpost.php?p=56827142&postcount=2920
You can restore only the system part, keep your data part so you have pure stock system but your data intact.
Click to expand...
Click to collapse
thanks for your reply. :good:
your link doesn't point to the right files I believe.
How do I flash only the system part ?

snowfree52 said:
thanks for your reply. :good:
your link doesn't point to the right files I believe.
How do I flash only the system part ?
Click to expand...
Click to collapse
Link corrected.
You don't flash, you restore with TWRP.
Read what @swedax94 wrote above and his thread
You also can read http://forum.xda-developers.com/showthread.php?t=2701376
I guided many on how to restore a backup made with TWRP

ckpv5 said:
[/HIDE]
Your error is different .. the libril-qc-qmi-1.so is modified and not pure stock. You need to replace this file with the stock one.
To make thing easier for you, just flash TWRP again and restore my 3.28.401.9 nandroid backup here : http://forum.xda-developers.com/showpost.php?p=56979449&postcount=2960
You can restore only the system part, keep your data part so you have pure stock system but your data intact.
Click to expand...
Click to collapse
ckpv5 said:
Link corrected.
You don't flash, you restore with TWRP.
Read what @swedax94 wrote above and his thread
You also can read http://forum.xda-developers.com/showthread.php?t=2701376
I guided many on how to restore a backup made with TWRP
Click to expand...
Click to collapse
OK I see, still downloading your nandroid.
I had a look at TWRP, just have to uncheck data then ? Am I correct ?
Thanks

snowfree52 said:
OK I see, still downloading your nandroid.
I had a look at TWRP, just have to uncheck data then ? Am I correct ?
Thanks
Click to expand...
Click to collapse
Yes .. uncheck data if you want to keep your data.
If you want everything fully stock, then check all boot, data and system.. it's your choice.

Should I also restore the boot part or only system is good ?
Thanks !

snowfree52 said:
Should I also restore the boot part or only system is good ?
Thanks !
Click to expand...
Click to collapse
Only system is good enough but selecting boot make no harm.
BTW @sudaltsov - how's thing going ?

ckpv5 said:
Only system is good enough but selecting boot make no harm.
BTW @sudaltsov - how's thing going ?
Click to expand...
Click to collapse
OK, did it !
Is it normal that it's still showing HTC boot logo after already 10 minutes ?

snowfree52 said:
OK, did it !
Is it normal that it's still showing HTC boot logo after already 5 minutes ?
Click to expand...
Click to collapse
Lets wait for 10 mins. If still not booting, go back to recovery select system & boot (I expect you have stock boot.img installed), then wipe dalvik & cache before reboot.
You have TWRP 2.8.4.0 installed right ?
If it's still fail to boot, then make a backup of your data then restore data from the downloaded nandroid. This will make you have a new set up phone.

ckpv5 said:
Lets wait for 10 mins. If still not booting, go back to recovery select system & boot (I expect you have stock boot.img installed), then wipe dalvik & cache before reboot.
Click to expand...
Click to collapse
It worked ! thank you
now what ? I replace TWRP recovery with the one from the OTA update then try again to install it ?

snowfree52 said:
It worked ! thank you
now what ? I replace TWRP recovery with the one from the OTA update then try again to install it ?
Click to expand...
Click to collapse
Yes..install the stock recovery then check OTA, download and install
And also note that after a successful update to lollipop, it will take some time for it to complete boot and optimizing ..

ckpv5 said:
Yes..install the stock recovery then check OTA, download and install
And also note that after a successful update to lollipop, it will take some time for it to complete boot and optimizing ..
Click to expand...
Click to collapse
Well didn't work again !
My M8 is european, the lockscreen from your nandroid is different than mine
edit : I see, in parameters, it now says my firmware is 1.54.401.10 ??? and android 4.4.2. How comes ???
I guess I restored an old nandroid of mine !
I see, I didn't put your nandroid in the right folder ! where should I put it ?

snowfree52 said:
Well didn't work again !
My M8 is european, the lockscreen from your nandroid is different than mine
edit : I see, in parameters, it now says my firmware is 1.54.401.10 ??? and android 4.4.2. How comes ???
I guess I restored an old nandroid of mine !
I see, I didn't put your nandroid in the right folder !
Click to expand...
Click to collapse
Never mind ... try again.
Remember when you extract the nandroid zip using extract to 3.28.401.9_ckpv5, there will be another folder inside it, use extract here then you get 3.28.401.9 folder

ckpv5 said:
Never mind ... try again.
Remember when you extract the nandroid zip using extract to 3.28.401.9_ckpv5, there will be another folder inside it, use extract here then you get 3.28.401.9 folder
Click to expand...
Click to collapse
That's what I didn't do !
restoring right now ! :good:

ckpv5 said:
extract out the recovery.img ---this is the correct recovery image to use.
Click to expand...
Click to collapse
That worked! Thank you very much!! There were some errors in the recovery, actually - but at least the installation process passed. Hurray! Thank you again!

How do I backup my stock recovery?

I want to be able to flash my stock recovery when I no longer want TWRP or CWM. How would I go about doing this?

tcmoffitt said:
I want to be able to flash my stock recovery when I no longer want TWRP or CWM. How would I go about doing this?
Click to expand...
Click to collapse
Hello,
Thanks for using XDA Assist.
What device do you have?
___
v7
XDA Assist

v7 said:
Hello,
Thanks for using XDA Assist.
What device do you have?
___
v7
XDA Assist
Click to expand...
Click to collapse
HTC One m8 Tmobile

Thanks for the help guys I really appreciate it. This forum is just so helpful............. ---____---

Which T-Mobile ?
If it is T-Mob US .. there's a dedicated section for T-Mob US and you can find any info there.

tcmoffitt said:
Thanks for the help guys I really appreciate it. This forum is just so helpful............. ---____---
Click to expand...
Click to collapse
This is not possible to backup your stock recovery. When you need that you can download it simply (base on your phone's build number). Also you can extract stock recovery frome your ota zip update(the file with img format inside of firmware folder)

Arsinn said:
This is not possible to backup your stock recovery.
Click to expand...
Click to collapse
Actually, the following usually works:
This has to be done before flashing custom recovery. Unlock bootloader, then fastboot boot recovery.img
With "recovery.img" being a TWRP file located in your fasboot folder. This will boot into TWRP without actually flashing it. From there, you can pick recovery in the backup options, to backup stock recovery.
But yes, I agree that stock recovery images are pretty easy to obtain from these forums, or extracting from a OTA or ROM.zip.

redpoint73 said:
Actually, the following usually works:
This has to be done before flashing custom recovery. Unlock bootloader, then fastboot boot recovery.img
With "recovery.img" being a TWRP file located in your fasboot folder. This will boot into TWRP without actually flashing it. From there, you can pick recovery in the backup options, to backup stock recovery.
But yes, I agree that stock recovery images are pretty easy to obtain from these forums, or extracting from a OTA or ROM.zip.
Click to expand...
Click to collapse
Hi, redpoint73...
Maybe I'm missing something here, but I'm not seeing an option to backup the Recovery in TWRP 2.8.7.0... Just Boot, Cache, System, Data and Android Secure are available (see attached screenshot). I remote booted TWRP from my laptop, as I did when I rooted Marshmallow around a fortnight ago, in order to keep the stock recovery intact.
It would certainly be useful to be able to backup the stock recovery via TWRP... I just haven't found a way of accomplishing it .
-----
But a possible option to backup the stock recovery would be to use the Flashify app...
Remote boot TWRP from your PC, acquire root, and then run Flashify...
Flashify PlayStore link...
https://play.google.com/store/apps/details?id=com.cgollner.flashify
XDA discussion thread...
http://forum.xda-developers.com/showthread.php?t=2349847
This app uses <dd=if/of> commands to backup and potentially restore the boot and/or recovery images.
Although it does require root to work.
I've used Flashify on my Nexus 7 and Nexus 9 in the past, but never on my M8, except to backup... never to restore, so I cannot personally vouch for it's safety on the M8.
-----
What I'm unsure of about Flashify...
@redpoint73, @ckpv5, maybe you guys could shed some light on this...
Would such a <dd=if/of> created backup of stock recovery be flashable via fastboot?
And would it be safe to do so?
I know that TWRP uses <dd=if/of> commands, having looked through TWRPs logs... but I'm not quite sure how fastboot works when it comes to flashing stuff, and I'm very wary about doing it myself or recommending it for others.
Normally, you'd just use the Flashify app to restore any recovery/boot.img backups you've previously made...
But Flashify requires root to work, and with an unrooted system, this is isn't viable. So could one use fastboot in the normal way to flash such a previously made backup of the stock recovery?
-----
Anyhow, it's not critical at the moment for me, because I've not flashed TWRP to my M8, my stock recovery remains intact.
-----
I would recommend anybody reading this seeking to root their Marshmallow M8 to just remote boot TWRP from their PC with fastboot boot twrp.img (ie., don't actually flash it), perform an unrooted Nandroid backup first...
...and then flash Chainfire in the usual way.
This leaves the stock recovery intact, which will be required for future OTAs.
And there still might be some...
My Nexus 9 receives monthly security patches from Google (probably after the StageFright debacle of last year), and it may well be that the M8 will also continue to receive security patches, despite it being nearly two years old.
So you need to be ready... with an unrooted/untouched Nandroid of your own creation and the stock recovery.
I know that Chainfires systemless root method is supposed to address this issue, but if you're going to mess with system, you should have a Nandroid backup anyway...
...just in case.
Rgrds,
Ged.

Funny, I use the fastboot boot option to boot into TWRP saving my original recovery.

From Stock 5.1.1 to Custom 5.1.1

Dear XDA Members,
I currently run stock 5.1.1 (14.6.A.1.236) with no modifications whatsoever and a locked bootloader.
I would like to install a custom rom (PAC-ROM LP-MR1 5.1.1) on my Z1C.
I did some research and these are the steps i came up with:
1. install sdk and drivers
2. unlock bootloader
3. fastboot flash recovery "fota.img" (shouldn't it specify somehow that i need it to be flashed on the fota partition?)
4. factory reset/wipe
5. install custom rom + gapps
Coming from a locked bootloader a fully stock phone is there anything else i need to do like a new bootloader or something?
Also I'll be doing it through Win 10 64bit, I hope that isn't a problem.
Any advice will be highly appreciated.
Thank you very much

ursidae1 said:
Dear XDA Members,
I currently run stock 5.1.1 (14.6.A.1.236) with no modifications whatsoever and a locked bootloader.
I would like to install a custom rom (PAC-ROM LP-MR1 5.1.1) on my Z1C.
I did some research and these are the steps i came up with:
1. install sdk and drivers
2. unlock bootloader
3. fastboot flash recovery "fota.img" (shouldn't it specify somehow that i need it to be flashed on the fota partition?)
4. factory reset/wipe
5. install custom rom + gapps
Coming from a locked bootloader a fully stock phone is there anything else i need to do like a new bootloader or something?
Also I'll be doing it through Win 10 64bit, I hope that isn't a problem.
Any advice will be highly appreciated.
Thank you very much
Click to expand...
Click to collapse
First things first... Root. If you already did that then you're on the right track.
1. If you're not doing major development stuff, don't install the whole sdk. See here - http://forum.xda-developers.com/showthread.php?p=48915118 There may be issues you'll have to work with on newer versions of Windows. I haven't done it on anything later than 7. Keep in mind, though, that you won't need the computer to flash your boot img or rom, but you will need it to unlock the bootloader.
2. -
3. You can do this with an app called Rashr on your phone with root. Just download a recovery img, then open Rashr and follow the instructions.
4-5. Boot into recovery, full wipe, (system data and caches), flash rom zip and gapps zip. Maybe best to not flash more than that at once to start, in case there's a problem and you have no way to figure out what it is.
BTW, PacMan is a great choice. I've been using it for months.

levone1 said:
First things first... Root. If you already did that then you're on the right track.
1. If you're not doing major development stuff, don't install the whole sdk. See here - http://forum.xda-developers.com/showthread.php?p=48915118 There may be issues you'll have to work with on newer versions of Windows. I haven't done it on anything later than 7. Keep in mind, though, that you won't need the computer to flash your boot img or rom, but you will need it to unlock the bootloader.
2. -
3. You can do this with an app called Rashr on your phone with root. Just download a recovery img, then open Rashr and follow the instructions.
4-5. Boot into recovery, full wipe, (system data and caches), flash rom zip and gapps zip. Maybe best to not flash more than that at once to start, in case there's a problem and you have no way to figure out what it is.
BTW, PacMan is a great choice. I've been using it for months.
Click to expand...
Click to collapse
Thanks a lot for your reply.
I was reading on the cyanogen mod wiki how-to for our phone and it doesn't require a prior root.
I did those steps on my xperia m and it worked and i had never rooted it, the only difference is that i flashed cyanogen recovery and install cm12 which basically roots the phone and then flashed fota recovery.
Should i go this way again to gain root or would you recommend an easier root method for my stock build which is the newest.
If you recommend another root method when should it occur? prior unlocking the bootloader or afterwards?
Thanks

If this is your first time unlocking your bootloader, make sure you backup your DRM-Keys! You need to be rooted for that.
They are lost when bootloader gets unlocked. Some features in regards of camera performance are lost for example.

ursidae1 said:
Thanks a lot for your reply.
I was reading on the cyanogen mod wiki how-to for our phone and it doesn't require a prior root.
I did those steps on my xperia m and it worked and i had never rooted it, the only difference is that i flashed cyanogen recovery and install cm12 which basically roots the phone and then flashed fota recovery.
Should i go this way again to gain root or would you recommend an easier root method for my stock build which is the newest.
If you recommend another root method when should it occur? prior unlocking the bootloader or afterwards?
Thanks
Click to expand...
Click to collapse
True, if bl is unlocked, then you can flash the kernel and recovery via fastboot, then flash your rom. You may need the boot.img from your rom zip file. Then use commands 'fastboot flash boot' for the boot img, and 'fastboot flash recovery' for recovery. If you're rooted already, you can just do it on the phone.

levone1 said:
True, if bl is unlocked, then you can flash the kernel and recovery via fastboot, then flash your rom. You may need the boot.img from your rom zip file. Then use commands 'fastboot flash boot' for the boot img, and 'fastboot flash recovery' for recovery. If you're rooted already, you can just do it on the phone.
Click to expand...
Click to collapse
This is fantastic.
Do you think itll be ok to fastboot flash boot boot.img from cm12.1 rom zip then fastboot flash recovery fota.img instead of the cyanogen recovery that comes with cm12.1?
Do you think that might cause an issue?

ursidae1 said:
This is fantastic.
Do you think itll be ok to fastboot flash boot boot.img from cm12.1 rom zip then fastboot flash recovery fota.img instead of the cyanogen recovery that comes with cm12.1?
Do you think that might cause an issue?
Click to expand...
Click to collapse
Should be fine. It's also a 1 second operation to extract boot.img from your rom zip, which you need already downloaded and on your SD card before you flash imgs. You might even be fine without flashing the boot img - can't hurt to try. Just flash the recovery and reboot and see if you get a purple light. Then, volume button changes purple to orange, and you're in recovery. Some recoveries don't work with some kernels, (been my experience).

levone1 said:
Should be fine. It's also a 1 second operation to extract boot.img from your rom zip, which you need already downloaded and on your SD card before you flash imgs. You might even be fine without flashing the boot img - can't hurt to try. Just flash the recovery and reboot and see if you get a purple light. Then, volume button changes purple to orange, and you're in recovery. Some recoveries don't work with some kernels, (been my experience).
Click to expand...
Click to collapse
I now have cm12.1 with cyanogen recovery.
Which recovery is best for our phone, which one do you use?
I can find 2 options:
FOTA TWRP 2.8.6.0 (http://forum.xda-developers.com/sony-xperia-z1-compact/general/fota-twrp-recovery-amami-t2909719)
XZDualRecovery (http://forum.xda-developers.com/showthread.php?t=2647480)
Thanks a lot

ursidae1 said:
I now have cm12.1 with cyanogen recovery.
Which recovery is best for our phone, which one do you use?
I can find 2 options:
FOTA TWRP 2.8.6.0 (http://forum.xda-developers.com/sony-xperia-z1-compact/general/fota-twrp-recovery-amami-t2909719)
XZDualRecovery (http://forum.xda-developers.com/showthread.php?t=2647480)
Thanks a lot
Click to expand...
Click to collapse
I have only used xzdr with stock rom. I think in the past I've had it not work for me on CM, so I just stick to straight twrp by default. I know NUT has always been hard at work and has made steady improvements, so maybe not an issue now. Personally I realized that I only need 1 recovery anyway. There's a newer Twrp here - http://forum.xda-developers.com/crossdevice-dev/sony/twrp-v2-8-6-0-f2fs-z1-z1c-z2-z3-z3c-t3098573

One important fact that has already been probably mentioned is that installing custom roms on your XPERIA will worsen your camera, esp the front one. Keep this in mind.