[Sony Xperia Z Ultra] Coolpsi:
“Blueether” and “LordManhattan”, so far, your help has been priceless! :good: Having said that, in order to help you to help me,I will do a recap of all I have made since I asked for you help:

1.	Phone Model: C6833; out of the box I updated it, via pc companion, to .136;

2.	Made de downgrade to .532, via “androxyde” flashtool;

3.	Made the root, via “kingo Android Root”, since it didn’t worked with the suggested method (Root_with_Restore_by_Bin4ry_v33);

4.	Made the TA partition backup;

5.	Unlocked the bootloader;

6.	Installed the recovery and TWRP;

7.	Made a NAND backup in recovery;

8.	Tried to install the boot.img (pac43.img), via QuikIMG 0.2 beta, but after the process was concluded, the phone stayed stocked on the “Pac” logo. Apparently I was supposed to push the volume button up… By the time I didn´t know what to do, so, I turned off the phone, entered in recovery mode and tried again to restart it, but it stayed stocked again at the “Pac” logo.  Then, I decided to restore the NAND backup;

9.	As I realized something went wrong with the “pac43.img”, I tried to flash, also using the QuickIMG, the boot.img that I extracted from the FXP303-cm-11-20140120-UNOFFICIAL-dogo zip file – I think that’s what I was supposed to do, but I am no longer very sure about that because that part was not very clear to me on the “FXP” instructions (http://xdaforums.com/showthread.php?t=2540652), in particular the part where I was supposed to “fastboot flash boot boot.img (from cm10 zip)”. I am now realising that, the instruction mentioned the “cm10 zip”, and I did it with the zip from the ROM above mentioned (cm 11). After doing that, my phone was “bricked”, it didn’t boot, it didn’t go to recovery and the led light was red. Miraculously, or not, after a while I was able to connected to flashtool in flashboot mode, and then I flashed the .532 again. Dis this happened because of the wrong boot.img?

10.	After being again with an “untouched” .532 I rooted the phone as before, and I installed the recovery and TWRP as well as before;

11.	By that time, I had another problem, I was no longer able to access recovery (when I tried to do it, pushing the power button and waiting for the led light to push the down or up volume button, there was no light at all; even with a app from play store to boot in to recovery, the phone simply reboots), and the phone was no longer detected by QuikIMG.

12.	As for now, I have just flashed again .532 and I am staying this way until I have some news from you.

Please note some currents aspects:

1.	I am running Windows 8;

2.	When I connect the phone (powered on or off) to the pc, or when it is charging, the indicator led is red;

3.	When I connect the phone to the pc (powered on or off and with debugging on) the flashtool give this message: Device connected with USB debugging off; For 2011 devices line, be sure you are not in MTP mode;

4.	When I connect the phone to the pc in fastboot mode, the flashtool give this message (the led light is blue): Device connected in fastboot mode;

5.	When I connect the phone to the pc in flash mode, the flashtool give this message (no led light): Device connected in flash mode;

6.	QuikIMG still doesn’t detect my phone.

Last things, I think, I’ve learned from you:

1.	Every time I want to change from an AOSP rom to a stock rom, or the other way, I have to install a boot.img. Are all custom rom’s AOSP? I think not… When we talk about stock rom, are we referring only to the ftf files kind, wich we install through flashtool, or is it possible to install them through recovery mode with zip files?

2.	I can’t install ROMs with .532 ROM (4.2.2 base), so I have to upgrade. Can I do it via PC Companion? I think not… Or do I have to do it with the flashtool? What about the root, I think I will lose it…

For now, I will wait patiently for you reply, which I suppose will take some hours, considering the time zone differences, I am in Portugal, “blueether seems to be in New Zealand, and “LordManhattan” is even far away…:laugh:

---------- Post added at 12:05 PM ---------- Previous post was at 11:55 AM ----------

“Blueether” and “LordManhattan”, so far, your help has been priceless! Having said that, in order to help you to help me,I will do a recap of all I have made since I asked for you help:

1. Phone Model: C6833; out of the box I updated it, via pc companion, to .136;

2. Made de downgrade to .532, via “androxyde” flashtool;

3. Made the root, via “kingo Android Root”, since it didn’t worked with the suggested method (Root_with_Restore_by_Bin4ry_v33);

4. Made the TA partition backup;

5. Unlocked the bootloader;

6. Installed the recovery and TWRP;

7. Made a NAND backup in recovery;

8. Tried to install the boot.img (pac43.img), via QuikIMG 0.2 beta, but after the process was concluded, the phone stayed stocked on the “Pac” logo. Apparently I was supposed to push the volume button up… By the time I didn´t know what to do, so, I turned off the phone, entered in recovery mode and tried again to restart it, but it stayed stocked again at the “Pac” logo.  Then, I decided to restore the NAND backup;

9. As I realized something went wrong with the “pac43.img”, I tried to flash, also using the QuickIMG, the boot.img that I extracted from the FXP303-cm-11-20140120-UNOFFICIAL-dogo zip file – I think that’s what I was supposed to do, but I am no longer very sure about that because that part was not very clear to me on the “FXP” instructions (http://xdaforums.com/show....php?t=2540652), in particular the part where I was supposed to “fastboot flash boot boot.img (from cm10 zip)”. I am now realising that, the instruction mentioned the “cm10 zip”, and I did it with the zip from the ROM above mentioned (cm 11). After doing that, my phone was “bricked”, it didn’t boot, it didn’t go to recovery and the led light was red. Miraculously, or not, after a while I was able to connected to flashtool in flashboot mode, and then I flashed the .532 again. Dis this happened because of the wrong boot.img?

10. After being again with an “untouched” .532 I rooted the phone as before, and I installed the recovery and TWRP as well as before;

11. By that time, I had another problem, I was no longer able to access recovery (when I tried to do it, pushing the power button and waiting for the led light to push the down or up volume button, there was no light at all; even with a app from play store to boot in to recovery, the phone simply reboots), and the phone was no longer detected by QuikIMG.

12. As for now, I have just flashed again .532 and I am staying this way until I have some news from you.

Please note some currents aspects:

1. I am running Windows 8;

2. When I connect the phone (powered on or off) to the pc, or when it is charging, the indicator led is red;

3. When I connect the phone to the pc (powered on or off and with debugging on) the flashtool give this message: Device connected with USB debugging off; For 2011 devices line, be sure you are not in MTP mode;

4. When I connect the phone to the pc in fastboot mode, the flashtool give this message (the led light is blue): Device connected in fastboot mode;

5. When I connect the phone to the pc in flash mode, the flashtool give this message (no led light): Device connected in flash mode;

6. QuikIMG still doesn’t detect my phone.

Last things, I think, I’ve learned from you:

1. Every time I want to change from an AOSP rom to a stock rom, or the other way, I have to install a boot.img. Are all custom rom’s AOSP? I think not… When we talk about stock rom, are we referring only to the ftf files kind, wich we install through flashtool, or is it possible to install them through recovery mode with zip files?

2. I can’t install ROMs with .532 ROM (4.2.2 base), so I have to upgrade. Can I do it via PC Companion? I think not… Or do I have to do it with the flashtool? What about the root, I think I will lose it…

For now, I will wait patiently for you reply, which I suppose will take some hours, considering the time zone differences, I am in Portugal, “blueether seems to be in New Zealand, and “LordManhattan” is even far away…