Upgrading stock versions - Xperia Z1 Q&A, Help & Troubleshooting

First of all, first post here so hello everyone and thanks for having me
My issue is the following, I have a C6906 which I bought a couple of years ago from Ancel (one of the carriers here in Uruguay) and it has always had a branded 4.3 (14.2.A.1.136 to be precise) which has never been updated by Ancel (the version listed in XperiFirm is the same I have and my phone has never offered an OTA update). I asked Ancel about this recently to see if I could expect any official updates and was basically told "yeah, that's not happening".
So what I would like to do is upgrade the phone to Lollipop by myself, namely to 14.6.A.1.236 from the US which seems to be the most current and generic stock available. Rooting and custom ROMs are (at this point) not something I'm looking at.
So I read a bunch of stuff and I think I'm "ready" to do my upgrade, but before messing around with my phone, I wanted to have somebody else more knowledgeable check my plan and give me a couple of pointers so I avoid any snafus as much as possible
Right now I have Flashtool (0.9.21.0), XperiFirm (4.9.1) and I've used it to download/unpack the ROM I think I want (C6906_Customized US_1276-7484_14.6.A.1.236_R2D), so my questions are:
1) Are there any glaring mistakes in the tools/approach described above?
2) Since I'm doing stock -> stock, can I perform the flash/upgrade without unlocking my bootloader? As I understand it, the bootloader checks for the installed ROM signature and I would expect the new one to also be signed by Sony, but I don't know if the signature also includes my carrier (and that's why I haven't been offered an upgrade yet).
3) If the answer to 1 is negative (i.e. I have to unlock my bootloader anyway), is there any advantage in going for stock instead of some other custom ROMs? As I understand it, unlocking the bootloader removes DRM keys that might kill some functionality (like "advanced" camera algorithms), would that happen for both stock and custom ROMs?
Thanks a lot in advance for any replies/pointers :fingers-crossed:

You don't need to unlock bootloader to flash stock ROM. Unlocking is need if you want a custom kernel which is not your case. Anyway you can backup your DRM keys and use that to lock/unlock your bootloader whenever you want to. See here http://forum.xda-developers.com/showthread.php?t=2292598

Thanks... Just to confirm something else, if I try to flash without unlocking the bootloader, there's no chance the version I'm installing won't work right? If it's not a properly signed version the locked bootloader will prevent Flashtool from putting it on the phone?

Related

[Q] Vodafone UK Nexus One to Stock Nexus One

Hi all,
Apologies if this has been answered elsewhere, I checked the FAQ and a forum search and found references that this could be done but no real instructions.
My friend has a Vodafone UK Nexus One and as you probably know when Google release an OTA it's about a billion years (or at least it seems) before it's rolled out to him as it is my understanding that Vodafone have their own special build. Therefore I'm wondering if there's any way of flashing a stock ROM onto his Nexus One (probably after unlocking the bootloader) so he can get future OTA upgrades when everyone else does?
Any pointers gratefully accepted
- echo
You can unlock the bootloader if you want, or not.
If you unlock the bootloader, download the FRG83 system image from http://developer.htc.com and use fastboot to flash over the system and boot images
If you don't want to unlock it, then use SuperOneClick to gain root, install ROM Manager and use that to flash a custom recovery and boot into it. From there you can flash the stock but with root .zip from here: http://forum.xda-developers.com/showthread.php?t=927935
Thanks Rusty, that seems to answer it! Now I've just got to convince my friend that flashing like this isn't actually that difficult and dangerous
As you're not touching the radio, it's not dangerous at all. Worst case scenario is you lose your data, so take a backup first to be safe.

[Q] Custom ROMS with *only* Interop-Unlock

Hi,
Firstly apologies if this has already been answered elsewhere - I have had a look and couldn't find anything specific to my needs.
Basically, my question is...Is there a custom ROM for the HD7 which consists ONLY of Interop Unlock and no other changes from stock functionality?
I am looking to be able to use WP7 Root Tools on my HD7 but I do not want to use one of these crazy custom ROMS - no offense to the guys who put in the hard work to make 'em, it's just not what I'm looking for - I just want a stock Mango ROM, but I want it to be interop-unlocked.
Here's the progress I've made so far:
-My device is currently unbranded Europe (was previously O2UK but flashed an unbranded NoDo ROM back in the day) upgraded all the way to 8107. This means that I'm on a bootloader version > 5.10. Fortunately then, I am capable of using this method to downgrade my bootloader as I have a 401 (European) phone. I have the original unbranded NoDo ROM which I flashed when it first came out, which should have a low enough bootloader version.
-After that, I should be capable of flashing an RSPL/HSPL to my device, although I'm not sure exactly how to go about that. The instructions in this thread seem like a good place to start.
-Once that is achieved, I could theoretically grab the 7720 ROM from here, and edit it to include Interop Unlock. Then, flash it to my phone, run WP7 Root Tools, and I'm good to go! This is obviously the part I'm most likely to have issues with, I'm not exactly a ROM chef, and it doesn't look very beginner friendly
Hence my question: Is there a custom ROM already out there (presumably it would have to have Mango v1 drivers) which will be as close to stock as possible but with InteropUnlock so I can run WP7RootTools?
OR: Can I simplify these steps in any way?
Thanks for any replies... meanwhile, I'm going to continue my research!
Yeah...I'd say your on the right track. Use ansars SLSPL method for Europe devices to downgrade your SPL and using Shadows tutorial to install RSPL/HSPL. You can also get the 2nd rom needed for the SLSPL method from Shadows tutorial. The hard part is going to be adding in an unlock to the rom. I know this isn't the answer that your wanting but your best bet would be to find a custom rom that is as close to stock as possible!
Heh, thanks. I figured as much.
Well, it turns out that this needn't necessarily be as complicated as all that - I've just discovered that my student App Hub registration is still live (I could have sworn it had run out, as I was unable to dev-unlock my phone) but since updating to that latest Tango which just became available today, I am able to dev-unlock my phone again!
So, slightly different question: are dev-unlocks only possible with the most recent firmware? (Surely unlikely given the current status of firmware rollouts)
The reason I was unable to unlock my phone previously was possibly because of registry tweaks made down the line - I kept getting "error check the phone's time and date are correct" when the time and date were obviously correct.
If it is still possible to dev-unlock a device running Mango, then I can simply use ansar's SLSPL method to go straight to Mango 7720, dev-unlock, Interop-unlock, install WP7RootTools and mission accomplished
EDIT: Well, there goes that plan - while my device is currently on 401 (Europe firmware) it is not actually a 401 device (as it was previously o2UK branded) so I can't use ansar's method....time to go and find me a USB Y-cable!

Help with network branded firmware

Yesterday I received my one from T-Mobile UK with 1.28.61.7 on board. I am not quite a noob but I have always had devices with WWE un-branded firmwares. There is no bloatware on the device but I guess that, until s-off, I am dependant on T-Mobile to provide updates.
I am not particularly bothered about custom roms and, in the past I have usually gone with stock rooted roms so that I can go add-free and remove anything that I do not require.
Last night I lied awake thinking about the implications about what I have and I really need some informed advice about it.
If I root my device, how can I return it to stock in the future so that I can receive any ota updates that T-Mobile may eventually offer without a RUU which appear to be quite scarce?
Am I able to install custom firmwares based on higher firmwares ie. 1.29.401.12 and, if yes, will I be able to return my device back to stock without an RUU as backup?
I am most confused about the scenario which I have. I love the device apart from the 3 dot menu bar which is doing my head in and am confident in my ability to remove it but am worried about my safety net if something goes wrong. Please somebody enlighten me as to what I am and are not able to do. Thanks in advance.
bobsie41 said:
Yesterday I received my one from T-Mobile UK with 1.28.61.7 on board. I am not quite a noob but I have always had devices with WWE un-branded firmwares. There is no bloatware on the device but I guess that, until s-off, I am dependant on T-Mobile to provide updates.
I am not particularly bothered about custom roms and, in the past I have usually gone with stock rooted roms so that I can go add-free and remove anything that I do not require.
Last night I lied awake thinking about the implications about what I have and I really need some informed advice about it.
If I root my device, how can I return it to stock in the future so that I can receive any ota updates that T-Mobile may eventually offer without a RUU which appear to be quite scarce?
Am I able to install custom firmwares based on higher firmwares ie. 1.29.401.12 and, if yes, will I be able to return my device back to stock without an RUU as backup?
I am most confused about the scenario which I have. I love the device apart from the 3 dot menu bar which is doing my head in and am confident in my ability to remove it but am worried about my safety net if something goes wrong. Please somebody enlighten me as to what I am and are not able to do. Thanks in advance.
Click to expand...
Click to collapse
You have options. Firstly S-Off is not likely to come soon if at all. HTC made it such a pig to crack, the entire year I had my One X it was never (to my knowledge) posted here how to do it. But it's not really that necessary. S-Off just adds convenience for flashing kernels in recovery at the same time as a ROM. With S-on you just have to accept that a bit more faff is required using fastboot to change a kernel.
(Side note: I have not had my device arrive yet so I am staying out of the development threads. I heard a rumour you can have a flashable kernel for this phone with S-On. Anyone know if this is true?)
Once a custom recovery is on, take a backup of your stock ROM. That way if you ever really wanted to go back for an official OTA update, you could restore the backup, flash back the stock recovery and relock the bootloader. Not sure why you'd want to go this route though.
Being on XDA and knowing how to do this stuff means you can get all the features an official update will bring you, usually months before any carrier will be providing it. You'll just be going through all this extra work to get an update that has been in the custom ROMs for ages.
wnp_79 said:
You have options. Firstly S-Off is not likely to come soon if at all. HTC made it such a pig to crack, the entire year I had my One X it was never (to my knowledge) posted here how to do it. But it's not really that necessary. S-Off just adds convenience for flashing kernels in recovery at the same time as a ROM. With S-on you just have to accept that a bit more faff is required using fastboot to change a kernel.
(Side note: I have not had my device arrive yet so I am staying out of the development threads. I heard a rumour you can have a flashable kernel for this phone with S-On. Anyone know if this is true?)
Once a custom recovery is on, take a backup of your stock ROM. That way if you ever really wanted to go back for an official OTA update, you could restore the backup, flash back the stock recovery and relock the bootloader. Not sure why you'd want to go this route though.
Being on XDA and knowing how to do this stuff means you can get all the features an official update will bring you, usually months before any carrier will be providing it. You'll just be going through all this extra work to get an update that has been in the custom ROMs for ages.
Click to expand...
Click to collapse
Thanks for your answer. As I said, I am not quite a noob :silly:. The reason I am looking to go back to stock at a later date is that I believe (rightly or wrongly you tell me) that to update firmware in it's entirety, it is necessary to use an official update from the provider.
If I back up my official stock rom after I root, are you absolutely sure that when restoring this backup, I will be able to receive official ota updates? It is not that I don't believe you, just want to be 100% sure.
Edit Perhaps we are more likely to get s-off now that we are on Quallcom not Tegra?
S-off together with super cid would give us the ability to use any RUU for this device which gives us an excellent safety net.
bobsie41 said:
Thanks for your answer. As I said, I am not quite a noob :silly:. The reason I am looking to go back to stock at a later date is that I believe (rightly or wrongly you tell me) that to update firmware in it's entirety, it is necessary to use an official update from the provider.
If I back up my official stock rom after I root, are you absolutely sure that when restoring this backup, I will be able to receive official ota updates? It is not that I don't believe you, just want to be 100% sure.
Edit Perhaps we are more likely to get s-off now that we are on Quallcom not Tegra?
Click to expand...
Click to collapse
It's ok. It's always best to be sure before attempting something!
You will not loose out on anything by not using an official update. All it will be is the stock firmware with T-Mobile's add touches. More often than improvements to the stock firmware, carries tend to restrict the features of a ROM and add bloatware (like game demos you can't uninstall) because they have made a deal with a game developer to make some money forcing them upon you.
Even without a nandroid backup you'll still be able to download and flash the stock firmware somewhere here. Basically anything you do to your phone you will be able to undo if you so choose. The only exception to this is that if you re-lock your bootloader, HTC will still be able to tell that it was at some point unlocked if you wanted a warranty return.
Yeah, as long as the stock bootloader is available, you just need to flash it after restoring the backup, and the updates should arrive.
The firmware might be flashable without the RUU or OTA, it was on the One X, but it was necessary to relock the bootloader.
I say go for it, mike1986 has the stock ROM in the dev section as well as his stock like improved ROM.

is .257 rootable?

Hi everyone. I tried finding info on my firmware, but somehow i couldn't find wether or not it is "rootable" it is 12.0.A.1.257, global version. Can someone confirm if it is indeed rootable. Thanks!
skojevac said:
Hi everyone. I tried finding info on my firmware, but somehow i couldn't find wether or not it is "rootable" it is 12.0.A.1.257, global version. Can someone confirm if it is indeed rootable. Thanks!
Click to expand...
Click to collapse
YES its rootable all you need to run the doomloard's event exploit from original dev section.. happy rooting
ok, I checked that thread and now have additional question for anyone who can have a time and knowledge to answer. obviously there is a new stock rom 12.0.A.2.245 for our bellowed SP. now, I have that older version 12.0.A.1.257 and though I tried updating device firmware I receive message that my phone is up to date. so I assumed this is probably due to some drug deal sony have with my operator ( the one the phone came from) and now for some reason sony would not let me update firmware (yet). so my question is next, actually there are several questions:
A. am I'm going to brick my phone if I manually download and update new firmware via flashtool regardless of sony saying my device is up to date?
B. Is this new firmware 12.0.A.2.245 so much better that is actually worth updating? (this should be A)
C. if i root this old firmware and perhaps install CW as well, and than update to the new one, am I'm going to loose both root and CW, or perhaps only CW after updating? or i will get to keep root and CW?
D. is it better to update and than root, or root and than update?
i hope this is not too much. thanks! :angel:
ps. i forgot to say, though my phone came from an operator, it is not sim locked and boot unlock status is YES
skojevac said:
ok, I checked that thread and now have additional question for anyone who can have a time and knowledge to answer. obviously there is a new stock rom 12.0.A.2.245 for our bellowed SP. now, I have that older version 12.0.A.1.257 and though I tried updating device firmware I receive message that my phone is up to date. so I assumed this is probably due to some drug deal sony have with my operator ( the one the phone came from) and now for some reason sony would not let me update firmware (yet). so my question is next, actually there are several questions:
A. am I'm going to brick my phone if I manually download and update new firmware via flashtool regardless of sony saying my device is up to date?
B. Is this new firmware 12.0.A.2.245 so much better that is actually worth updating? (this should be A)
C. if i root this old firmware and perhaps install CW as well, and than update to the new one, am I'm going to loose both root and CW, or perhaps only CW after updating? or i will get to keep root and CW?
D. is it better to update and than root, or root and than update?
i hope this is not too much. thanks! :angel:
ps. i forgot to say, though my phone came from an operator, it is not sim locked and boot unlock status is YES
Click to expand...
Click to collapse
A. no unless u r on unlocked bootloader that should brick our phone.
B. every firmware bring new advantages and disadvanteges..so i think u should upgrade it because camera has been improved! (low light photography)
C no u will loose both root and cwm
D both first update than root !! ROOT IS AWSM!!! it makes u feels that device is actually yours!!
thanks for a quick reply. so, I am going to update first and than do that "flash old kernel - root - flash new kernel" thing. and than backup the TA partition from here http://forum.xda-developers.com/showthread.php?t=2292598
I would like to save the BE and DRM keys 'cause I'm sure I'll unlock bootloader as well that entire process is what makes android so much better that sh**pple. like you said, you actually get to own your device. thanks again and thanks XDA!

Z1 Root from 136

Hi.
I'm trying to piece together how to root my Xperia Z1 that is currently on build 14.2.A.1.136 and whilst there are many guides that all link to each other, there is a lot of assumed knowledge.
I've been rooting and flashing stuff since the first XDA so it's nothing I'm new to but there's gaps in my knowledge as far as Sony devices go and it makes me a little nervous to try this without filling the gaps.
I've seen Shem's video (here http://www.youtube.com/watch?v=1aq9YTlfCgc) about downgrading to .534 using NUTs files but there's a lot of RED warning spread around various posts so, if you'll bear with me, I just have a couple of questions...
1) There's a warning on one post about backing up the TA partition before unlocking as the DRM keys will be lost. I understand what DRM keys are but is there anything else on here that's needed? Will I need to do this TA backup before I downgrade to 534 or upgrade to 290? or root?
2) I've downloaded flashtool for the Mac and the 534 FTF (FTF is just a Sony firmware file prepared for flashtool, yes?) - is this FTF file model agnostic? I've got the C6903 which is the LTE version of the Z1...
3) The stripped FTF files that are linked to under the video...are these the files you use to upgrade from 290 to 136 whilst maintaining root?
4) Am i right in thinking that I don't need to mess about unlocking my boot loader or flashing a custom bootloader if I'm not interested (at this stage anyway) about flashing a custom ROM but just keep root on stock...?
I suppose what I'm getting at is which part of all these processes is the dangerous bit where you need to take care? I hate losing anything permanently and whilst there might not be anything I need my DRM keys for (I got some free films but y'know, alternate sources are available) I don't want to lose the Bravia engine or any other functionality of my phone because, aside from anything else, it will affect the resale value and I look after all my phones as they fund my next one when I sell them on ebay.
Cheers!
Smiffy.
1) It doesn't matter when you want do the Backup, You can get Root, update and then Backup TA.
2) All the FTFs for your model support LTE then you don't have to be worry about.
3) You can use the links from the video or from the thread, there is no difference, Shem just posted them on his Video to help.
4) If you don't think to flash Custom Kernels then you don't need to Unlock your Bootloader, you still can install Custom Roms and Stock one.
There is no dangerous part here, just follow the instructions and all will be fine. BTW, if you don't want lose Warranty, do not Unlock Bootloader, and if you do, Backup TA, so one day if you will go back to stock you can Relock Bootlader. Do not relock on Custom Kernels, you will brick your phone, I think this is the most dangerous part but only if you do mistakes.

Categories

Resources