Hello,
I want to restore my Z5C to stock FW. It came as model number E5803, but during the process of downgrade from Nougat to Lollipop for TA partition backup, model got changed to E5803. I flashed LOS Bernie's alternate build on it for few months.
Now when I downloaded the Stock E5803 Nougat FW for it, flashing the FTF with Flashtool gave me error that its not for this device. How I can revert the device back to E5803 and Flash the latest stock FW on it?
I have the TA backup as well, but when tried to restore, it needs the phone to downgraded as well.
Related
Hi,
i upgraded to the latest Build 23.0.1.A.0.167 and lost root. I have done a TA partition backup on Version EURO-LTE_17.1.A.2.36.
My question is: If i flash a rootable ftf file with flashtool now, how is the TA partition affected? Could i proceed without losing the TA partions DRM information? Or should i restore the TA partition backup afterwards?
My plan is to downgrade via flashtool and a rootable ftf file. Apply root and upgrade to the latest firmware via recovery.
Thx in advance.
Solved. I didn`t know that as long as your bootloader is locked, the TA partition isn't affected.
I have some questions regarding flashing new firmwares on the phone.
Currently I have firmware version 23.0.1.A.0.167, if I downgrade to 17.1.A.2.69 firmware using Flashtool, do I exclude the TA partition from being flashed? If I don't exclude the TA partition while downgrading will it wipe my DRM keys?
If I install custom recovery, will I still be able to receive OTA updates or updates via PC Companion? If I do receive them will they install successfully?
If I downgrade, root, install custom recovery and flash back to the 4.4.4 firmware, when 5.0x firmware is released, will I be able to install that without losing my data and root? Or will I be able to keep both?
The general steps to gaining root on the Z2 now with .167 firmware is to downgrade to .69 (exclude TA partition), run towelroot/easy root, install custom recovery, flash pre-rooted .167 (exclude TA again). Will I have to repeat them for 5.0 update? Does root persist between firmware updates?
If anyone can confirm my thoughts it would be great. Thank you guys!
chaose said:
I have some questions regarding flashing new firmwares on the phone.
Currently I have firmware version 23.0.1.A.0.167, if I downgrade to 17.1.A.2.69 firmware using Flashtool, do I exclude the TA partition from being flashed? If I don't exclude the TA partition while downgrading will it wipe my DRM keys?
If I install custom recovery, will I still be able to receive OTA updates or updates via PC Companion? If I do receive them will they install successfully?
If I downgrade, root, install custom recovery and flash back to the 4.4.4 firmware, when 5.0x firmware is released, will I be able to install that without losing my data and root? Or will I be able to keep both?
The general steps to gaining root on the Z2 now with .167 firmware is to downgrade to .69 (exclude TA partition), run towelroot/easy root, install custom recovery, flash pre-rooted .167 (exclude TA again). Will I have to repeat them for 5.0 update? Does root persist between firmware updates?
If anyone can confirm my thoughts it would be great. Thank you guys!
Click to expand...
Click to collapse
flashing TA with a FTF doesnt wipe your DRM keys
recovery i dont know if OTA verifies the fotakernel partition
it will fail anyways if you have a custom kernel or modified system
you cant update if your bootloader is unlocked but relocked you can for some reason regardless of if you restored your TA backup
you wont be able to upgrade without losing root because after upgrading you will have to reroot
downgrade to 314 or before, root, backup your DRM keys, do what you want
you dont have to keep updating your drm keys because they never change
got it. thanks !!
For downgrading to 4.4.2, is it possible to do it without an wipe of the apps and data?
Which partitions should I exclude when downgrading to 4.4.2?
Envious_Data said:
you wont be able to upgrade without losing root because after upgrading you will have to reroot
Click to expand...
Click to collapse
That really depends on how you want to upgrade, right?
The magical thing about the z2 is we'll always have root. once lollipop comes out we would just need to create a rooted flashable zip and flash in recovery.
o0 Matt 0o said:
That really depends on how you want to upgrade, right?
The magical thing about the z2 is we'll always have root. once lollipop comes out we would just need to create a rooted flashable zip and flash in recovery.
Click to expand...
Click to collapse
Yup
Im going to have my phone rooted nearly imediately after lolipop comes anyway
I'm running stock 5.0.2 Build 23.1.A.1.28. My bootloader is locked again (was unlocked for CM 12), TA Partition is woking. Can I update to latest 5.1 Build 23.4.A.0.546 without loosing root?
[email protected] said:
I'm running stock 5.0.2 Build 23.1.A.1.28. My bootloader is locked again (was unlocked for CM 12), TA Partition is woking. Can I update to latest 5.1 Build 23.4.A.0.546 without loosing root?
Click to expand...
Click to collapse
There is a way
Use PRF creator to create a pre-rooted zip of your chosen update
Make sure to install recovery for LB and also to add it to your PRF zip
Flash it and enjoy your new update.
Something gone wrong.
I downloaded Sony PC Companion to get the update files.
Then I created FTF following this tutorial:
http://forum.xda-developers.com/xperia-z/development/noobs-guide-create-stock-firmware-ftf-t2188129
I choosed to include all: Kernel, FOTAKernel, Modem and LTALabel
At Step 3 I selected
Device: Sony Xperia Z2 D6503
Version: 23.4.A.0.546
Branding: Unbranded
Then I created a PRF
http://forum.xda-developers.com/crossdevice-dev/sony/tool-prfcreator-easily-create-pre-t2859904
I used:
New created FTF
philz_touch_6.41.6-sirius-v01-FW_402-DooMLoRD.zip
UPDATE-SuperSU-v2.46.zip
Then I put flashable-prerooted.zip to external SD, rebooted to philz Touch and installed ZIP from SD. Recovery finished without error, so I rebooted my device.
But after reboot it still show Android 5.02 under Settings -> About device, root seems to work, but busybox doesn't work anymore and worst of all, I don't have recovery anymore.
Any idea, what happend?
[email protected] said:
I'm running stock 5.0.2 Build 23.1.A.1.28. My bootloader is locked again (was unlocked for CM 12), TA Partition is woking. Can I update to latest 5.1 Build 23.4.A.0.546 without loosing root?
Click to expand...
Click to collapse
Do You have already 23.4.A.0.546 ftf for z2?
mr.loverlover said:
Do You have already 23.4.A.0.546 ftf for z2?
Click to expand...
Click to collapse
Damn. I didn't look at this while converting to ftf, thought pc companion will always load the latest regardless of provider when choosing the repair option.
Ok that was my fault. But why did this break my busybox and recovery?
I got it fixed with Z2-lockeddualrecovery2.8.15-RELEASE.installer, which also flashed busybox.
I want to restore my Moto Z XT1650-03 to factory state so I'm looking for the official RETEU firmware.
Currently, the bootloader is unlocked and I have 7.0.0 installed with no-verity patch. Otherwise, stock.
I have the 7.1.1 OTA notification but it fails to install. I think the reason might be because of the no-verity patch or because of the unlocked bootloader.
I am looking for the correct firmware for my phone. (RETEU)
Help would be appreciated.
I've the same problems. OTA Update always made an error, even after reset all data.
I tried to flash like described in other thread (HOW TO UPDATE....), managed to flash older NPLS25.86-30-12 and then sideload the 7.1.1 update. All seemed to be fine, until the next reboot of device, then boot loop (?!).
Now I'm even unable to reflash the 7.0 because of a downgrade error... I didn't made any greater changes, only the open bootloader.
Flash 7.0 firmware stock, remove lines command GTP and Bootloader in Script
Byte_76 said:
I want to restore my Moto Z XT1650-03 to factory state so I'm looking for the official RETEU firmware.
Currently, the bootloader is unlocked and I have 7.0.0 installed with no-verity patch. Otherwise, stock.
I have the 7.1.1 OTA notification but it fails to install. I think the reason might be because of the no-verity patch or because of the unlocked bootloader.
I am looking for the correct firmware for my phone. (RETEU)
Help would be appreciated.
Click to expand...
Click to collapse
On Fastboot
Flash this:
https://www.androidfilehost.com/?fid=817550096634787129
You will receive 7.11
Worked on me.
Basically, I've searched for this question but no concrete answer to be found. I am following a rooting tutorial and it says to flash stock firmware through Odin and then flash TWRP.
I have found the stock firmware for my country (Android 8), but other cell carrier than mine, and the phone is currently running Android 9.
Can I just flash TWRP without flashing a stock firmware beforehand, or is it necessary to flash a stock firmware first, and if so, what about the different carrier and a previous Android version?
xShx72 said:
Basically, I've searched for this question but no concrete answer to be found. I am following a rooting tutorial and it says to flash stock firmware through Odin and then flash TWRP.
I have found the stock firmware for my country (Android 8), but other cell carrier than mine, and the phone is currently running Android 9.
Can I just flash TWRP without flashing a stock firmware beforehand, or is it necessary to flash a stock firmware first, and if so, what about the different carrier and a previous Android version?
Click to expand...
Click to collapse
Before flashing TWRP, it is a good idea to flash the latest firmware to get the latest version of the modem, which will be useful for use with custom ROM.
Carefully read the TWRP flashing instructions so there are no surprises.
If you don't want to change the original firmware, then flash TWRP.
beware, latest firmware may bring new security updates such as vaultkeeper or RMM protection to your device.
you can flash different CSC with modded Odin (not recommended) but you can't downgrade bootloader.
use Samloader or Bifrost to download from official Samsung server for your region.